*** This bug is a duplicate of bug 1798790 ***
https://bugs.launchpad.net/bugs/1798790
Due to no reply to comment #8 I'm just going to assume this is a
duplicate of bug 1798790, which seems most likely. Otherwise maybe bug
1705369.
** This bug has been marked a duplicate of bug 1798790
Ubu
> - We add oem-priority because it affects our clients directly but we don't
> have any contract with
> Canonical.
You didn't add it though, overlook?
Also do you have anyone able to reproduce we can contact for
testing/getting extra informations?
--
You received this bug notification because
Just a note :
- We add oem-priority because it affects our clients directly but we
don't have any contract with Canonical.
- Let us know what tag we could use when we want to raise a business
impacting problem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** No longer affects: oem-priority
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811668
Title:
oem-config fails on Nvidia GPU machine on 18.04.1
To manage notifications about this bug go to:
https
per current oem project, we don't have this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811668
Title:
oem-config fails on Nvidia GPU machine on 18.04.1
To manage notifications about this
** Changed in: oem-priority
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811668
Title:
oem-config fails on Nvidia GPU machine on 18.04.1
To manage notifications a
** Changed in: oem-priority
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811668
Title:
oem-config fails on Nvidia GPU machine on 18.04.1
To manage notifications abou
Please follow the instructions in comment #8.
** Changed in: gnome-shell (Ubuntu)
Status: Expired => Incomplete
** Changed in: gdm3 (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think that is a real important problem, could anybody at least
reproduce the issue ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811668
Title:
oem-config fails on Nvidia GPU machine on 18.04.1
[Expired for OEM Priority Project because there has been no activity for
60 days.]
** Changed in: oem-priority
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/181166
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811668
Tit
> gnome-shell[30907]: Failed to create backend: No resources
I don't think that's an error. It's just telling you the Nvidia driver
doesn't support Wayland (which always gets tried first). In theory gdm3
is then meant to drop back to Xorg in this case (as Seb says). But some
Nvidia users (includin
Well, the upstream discussion/other bug are about gdm failing to
fallback from wayland (which it uses by default) to xorg on nvidia
machines where wayland is not working, that could be the issue here as
well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Many thanks for being so quick to answer.
I was wondering if this could have something to do gnome-shell greeter
using wayland ?
We pause our nvidia powered machines shipment for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
The log has those errors
gnome-shell[30907]: Failed to create backend: No resources
gnome-session[30496]: gnome-session-binary[30496]: WARNING: App
'org.gnome.Shell.desktop' exited with code 1
gnome-session-binary[30496]: WARNING: App 'org.gnome.Shell.desktop' exited with
code 1
Which seems the
Please find attached the Journal log with the user oem-config wizard and
one reboot
** Attachment added: "Journal log with the user oem-config wizard and reboot"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1811668/+attachment/5229316/+files/journal.log.trim
--
You received this b
Salut Sebastien
It happens on a dual GPU ( nvidia 1080 ti) ( threadripper CPU thus NO
other GPU)
Getting the systemd log now.
Still no way to upload files using ubuntu-bug on a command line system (
without logging with a browser ) or do you see a simple way to grab all
log files using command l
Thank you for your bug report. Could you attach the journalctl log from
a boot hitting the issue of not getting the greeter? Is the
configuration a dual GPU or nvidia only?
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
** Changed in: ubiquity (Ubuntu)
Status: New => Inc
Reproduced on a 1080 ti desktop
Not reproductible on a 1050 ti prime laptop.
** Also affects: oem-priority
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
20 matches
Mail list logo
