Oops, sorry. That is the log from when it was working. We need a log
from when it is broken, so please...
1. Reinstall the Nvidia driver to reproduce the problem.
2. After you have reproduced the problem and the machine fails to boot,
force a reboot and enter recovery mode.
3. Run this command
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+attachment/5204404/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
** Attachment added: "dpkgl.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+attachment/5204403/+files/dpkgl.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
@seb128 I'm just trying to explain where the two messages are in
relation to each other in this command-like environment you are stuck
in. Having one line before the other is not an issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
These commands were run in a normal boot of Ubuntu, without the Nvidia
drivers.
** Attachment added: "lspcik.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+attachment/5204405/+files/lspcik.txt
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+attachment/5204402/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Pedro,
I can't seem to find any significant CPU usage by gnome-shell when the
terminal is busy, using Ubuntu 18.10.
Can you please try live booting 18.10 and tell us if you find that is better
now?
http://releases.ubuntu.com/18.10/ubuntu-18.10-desktop-amd64.iso
** Changed in: gnome-shell
Also,
Everyone please REMOVE or DISABLE all your extensions before measuring
the CPU usage of gnome-shell. We are not interested in the performance
problems introduced by extensions here.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Sounds like the real issue is that the login screen is not appearing.
Please run these commands and attach the output files from each:
1. lspci -k > lspcik.txt
2. dpkg -l > dpkgl.txt
3. dmesg > dmesg.txt
4. journalctl -b > journal.txt
** Also affects: mutter (Ubuntu)
Importance:
Thank you for your bug report. What Ubuntu version are you using? Do you
have any apparmor denial or such in the journal log?
How did you start the deb binary, are you sure it didn't get hijacked by
the snap being first in the path?
What's the output of "snap interfaces gnome-system-monitor"?
Sorry but I don't understand the description, ""Started bpfilter" is
located just under "Started Gnome Desktop Manager"." what does that
mean? Where is that displayed? Why is it an issue to have "Started
bpfilter" displayed under "Started Gnome Desktop Manager"?
--
You received this bug
Thanks for the detail. I'm closing the main bug target since it's fixed
in the current Ubuntu version. We can open a trusty-targetted line if we
plan to SRU there but the bug seems minor and we fixes only major issues
and security problems on trusty at this point.
** Changed in:
Fresh Ubuntu 18.04 on Dell XPS13 9360, Intel video - can also reproduce
this bug
--
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/1758512
Title:
No virtual terminals (CTRL+ALT+F?) when
101 - 113 of 113 matches
Mail list logo
