I mean “I “ just marked , not you. Sorry for the confusion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879949
Title:
Can not log in
To manage notifications about this bug go to:
Where can I mark that? What is the possible root cause? Sorry, I'm
pretty inexperienced.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879949
Title:
Can not log in
To manage notifications about
Sorry, just mark the possible root cause first for further analysis for
myself and for anyone who's interested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879949
Title:
Can not log in
To
Is there information you still need? I found out, that when stuck in the
login screen I can switch to another tty. There I can login without a
gui.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(EE) NVIDIA(GPU-0): Failed to acquire modesetting permission.
(EE) NVIDIA(0): Failing initialization of X screen
...
(II) UnloadModule: "nvidia"
...
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
(EE) no screens found(EE)
** Tags added: hwe-graphics
--
You
** Attachment added: "journal.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879949/+attachment/5375294/+files/journal.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879949
Title:
Could you attach your system journal of last boot?
1. Reboot to the problematic kernel
2. When it still fails to let you login, reboot to a working kernel,
3. Dump system journal:
$ journalctl -b -1 > journal.log
Attach that "journal.log" file here.
** Changed in: linux
