2018-10-19 09:40:24 |
Efthimios Chaskaris |
bug |
|
|
added bug |
2018-10-19 09:44:28 |
Efthimios Chaskaris |
affects |
xorg-server (Ubuntu) |
gdm3 (Ubuntu) |
|
2018-10-19 10:11:52 |
Efthimios Chaskaris |
description |
"Started bpfilter" is located just under "Started Gnome Desktop Manager". I have found that uninstalling my Nvidia drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. |
"Started bpfilter" is located just under "Started Gnome Desktop Manager". 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. |
|
2018-10-19 10:19:49 |
Efthimios Chaskaris |
summary |
Ubuntu 18.10 hangs at "started bpfilter" |
Ubuntu 18.10 hangs at "started bpfilter" - "Started Gnome Desktop Manager" during boot |
|
2018-10-19 10:29:43 |
Efthimios Chaskaris |
description |
"Started bpfilter" is located just under "Started Gnome Desktop Manager". 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. |
"Started bpfilter" is located just under "Started Gnome Desktop Manager". 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. This bug (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in-boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. |
|
2018-10-19 14:22:23 |
Launchpad Janitor |
gdm3 (Ubuntu): status |
New |
Confirmed |
|
2018-10-19 14:38:22 |
Ricardo Portugal |
bug |
|
|
added subscriber Ricardo Portugal |
2018-10-20 18:34:42 |
Efthimios Chaskaris |
description |
"Started bpfilter" is located just under "Started Gnome Desktop Manager". 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. This bug (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in-boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. |
"Started bpfilter" is located just under "Started Gnome Desktop Manager".
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 bug (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in-boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. |
|
2018-10-20 18:48:02 |
Efthimios Chaskaris |
description |
"Started bpfilter" is located just under "Started Gnome Desktop Manager".
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 bug (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in-boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. |
"Started bpfilter" is located just under "Started Gnome Desktop Manager".
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. |
|
2018-10-21 14:28:24 |
Efthimios Chaskaris |
description |
"Started bpfilter" is located just under "Started Gnome Desktop Manager".
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. |
"Started bpfilter" is located just under "Started Gnome Desktop Manager".
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". |
|
2018-10-21 15:38:36 |
Andrej Palicka |
bug |
|
|
added subscriber Andrej Palicka |
2018-10-21 15:44:37 |
Ivan Bakharev |
bug |
|
|
added subscriber Ivan Bakharev |
2018-10-22 14:08:55 |
Sebastien Bacher |
gdm3 (Ubuntu): importance |
Undecided |
Low |
|
2018-10-22 14:08:55 |
Sebastien Bacher |
gdm3 (Ubuntu): status |
Confirmed |
Incomplete |
|
2018-10-22 14:35:43 |
Efthimios Chaskaris |
description |
"Started bpfilter" is located just under "Started Gnome Desktop Manager".
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". |
"Started bpfilter" is located just under "Started Gnome Desktop Manager".
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 with the last message being "started bpfilter".
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". |
|
2018-10-22 14:40:35 |
Efthimios Chaskaris |
description |
"Started bpfilter" is located just under "Started Gnome Desktop Manager".
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 with the last message being "started bpfilter".
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". |
"Started bpfilter" is located just under "Started Gnome Desktop Manager".
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". |
|
2018-10-22 15:06:15 |
Efthimios Chaskaris |
bug |
|
|
added subscriber Sebastien Bacher |
2018-10-22 19:17:50 |
Efthimios Chaskaris |
description |
"Started bpfilter" is located just under "Started Gnome Desktop Manager".
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". |
"Started bpfilter" is located just under "Started Gnome Desktop Manager". 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". |
|
2018-10-23 01:42:21 |
Daniel van Vugt |
gdm3 (Ubuntu): importance |
Low |
High |
|
2018-10-23 07:56:20 |
Daniel van Vugt |
bug task added |
|
mutter (Ubuntu) |
|
2018-10-23 07:56:24 |
Daniel van Vugt |
mutter (Ubuntu): status |
New |
Incomplete |
|
2018-10-23 08:11:03 |
Efthimios Chaskaris |
attachment added |
|
dmesg.txt https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+attachment/5204402/+files/dmesg.txt |
|
2018-10-23 08:11:20 |
Efthimios Chaskaris |
attachment added |
|
dpkgl.txt https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+attachment/5204403/+files/dpkgl.txt |
|
2018-10-23 08:11:47 |
Efthimios Chaskaris |
attachment added |
|
journal.txt https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+attachment/5204404/+files/journal.txt |
|
2018-10-23 08:12:38 |
Efthimios Chaskaris |
attachment added |
|
lspcik.txt https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+attachment/5204405/+files/lspcik.txt |
|
2018-10-23 08:39:23 |
Daniel van Vugt |
tags |
|
cosmic nouveau |
|
2018-10-23 08:39:32 |
Daniel van Vugt |
summary |
Ubuntu 18.10 hangs at "started bpfilter" - "Started Gnome Desktop Manager" during boot |
[nouveau] Ubuntu 18.10 hangs at "started bpfilter" - "Started Gnome Desktop Manager" during boot |
|
2018-10-23 09:00:11 |
Daniel van Vugt |
summary |
[nouveau] Ubuntu 18.10 hangs at "started bpfilter" - "Started Gnome Desktop Manager" during boot |
Ubuntu 18.10 login screen never appears when using the Nvidia driver |
|
2018-10-23 09:20:06 |
Efthimios Chaskaris |
attachment added |
|
prev_boot.txt https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+attachment/5204440/+files/prev_boot.txt |
|
2018-10-23 09:20:56 |
Efthimios Chaskaris |
description |
"Started bpfilter" is located just under "Started Gnome Desktop Manager". 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". |
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". |
|
2018-10-23 09:21:53 |
Efthimios Chaskaris |
description |
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". |
The boot process hangs with the message "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". |
|
2018-10-23 09:26:33 |
Efthimios Chaskaris |
description |
The boot process hangs with the message "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". |
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". |
|
2018-10-24 02:26:59 |
Daniel van Vugt |
description |
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". |
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". |
|
2018-10-24 02:27:02 |
Daniel van Vugt |
gdm3 (Ubuntu): status |
Incomplete |
New |
|
2018-10-24 02:27:05 |
Daniel van Vugt |
mutter (Ubuntu): status |
Incomplete |
New |
|
2018-10-25 03:01:26 |
Launchpad Janitor |
gdm3 (Ubuntu): status |
New |
Confirmed |
|
2018-10-25 03:01:26 |
Launchpad Janitor |
mutter (Ubuntu): status |
New |
Confirmed |
|
2018-10-25 17:46:45 |
Dmitry Pelevin |
bug |
|
|
added subscriber Dmitry Pelevin |
2018-11-01 03:22:09 |
Daniel van Vugt |
tags |
cosmic nouveau |
cosmic nvidia |
|
2018-11-06 05:29:42 |
Daniel van Vugt |
mutter (Ubuntu): importance |
Undecided |
High |
|
2018-11-15 11:19:17 |
Adam Niedling |
bug |
|
|
added subscriber Adam Niedling |
2018-12-11 02:31:38 |
Daniel van Vugt |
summary |
Ubuntu 18.10 login screen never appears when using the Nvidia driver |
Ubuntu 18.10 login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it) |
|
2018-12-17 05:07:40 |
Daniel van Vugt |
summary |
Ubuntu 18.10 login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it) |
Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it) |
|
2018-12-28 21:58:02 |
ccdisle |
bug |
|
|
added subscriber ccdisle |
2019-01-02 13:43:13 |
Mateusz Mikuła |
bug |
|
|
added subscriber Mateusz Mikuła |
2019-01-05 07:22:50 |
ROODE |
bug |
|
|
added subscriber ROODE |
2019-01-15 13:40:52 |
Brent Gardner |
bug |
|
|
added subscriber Brent Gardner |
2019-01-17 18:01:04 |
CrazySky |
bug |
|
|
added subscriber CrazySky |
2019-01-17 18:01:29 |
CrazySky |
bug |
|
|
added subscriber Мария |
2019-01-23 13:09:19 |
Michel-Ekimia |
bug |
|
|
added subscriber Michel-Ekimia |
2019-01-26 18:22:54 |
Gregory Starodubcev |
bug |
|
|
added subscriber Gregory Starodubcev |
2019-03-08 02:26:57 |
Daniel van Vugt |
tags |
cosmic nvidia |
cosmic disco nvidia |
|
2019-04-17 06:28:49 |
Dario Nuevo |
bug |
|
|
added subscriber Dario Nuevo |
2019-04-29 15:56:02 |
Zygmunt Krynicki |
bug watch added |
|
https://gitlab.gnome.org/GNOME/gdm/issues/435 |
|
2019-04-30 06:02:55 |
Daniel van Vugt |
description |
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". |
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". |
|
2019-04-30 06:03:02 |
Daniel van Vugt |
bug watch added |
|
https://gitlab.gnome.org/GNOME/gdm/issues/483 |
|
2019-04-30 06:03:02 |
Daniel van Vugt |
bug task added |
|
gdm |
|
2019-04-30 06:17:41 |
Jean-Baptiste Lallement |
tags |
cosmic disco nvidia |
cosmic disco nvidia rls-ee-incoming |
|
2019-04-30 06:17:52 |
Jean-Baptiste Lallement |
bug |
|
|
added subscriber Jean-Baptiste Lallement |
2019-04-30 07:28:18 |
Bug Watch Updater |
gdm: status |
Unknown |
New |
|
2019-04-30 14:02:29 |
Will Cooke |
nominated for series |
|
Ubuntu Eoan |
|
2019-04-30 14:02:29 |
Will Cooke |
bug task added |
|
mutter (Ubuntu Eoan) |
|
2019-04-30 14:02:29 |
Will Cooke |
bug task added |
|
gdm3 (Ubuntu Eoan) |
|
2019-04-30 14:02:36 |
Will Cooke |
tags |
cosmic disco nvidia rls-ee-incoming |
cosmic disco nvidia |
|
2019-04-30 14:16:33 |
Sebastien Bacher |
gdm3 (Ubuntu Eoan): assignee |
|
Iain Lane (laney) |
|
2019-04-30 14:16:39 |
Sebastien Bacher |
mutter (Ubuntu Eoan): assignee |
|
Iain Lane (laney) |
|
2019-05-18 12:25:16 |
Shannon VanWagner |
attachment added |
|
syslog.1 from gdm3 crashing machine https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+attachment/5264671/+files/syslog_ubuntu1904.txt |
|
2019-06-02 02:50:56 |
Bug Watch Updater |
gdm: status |
New |
Fix Released |
|
2019-06-02 11:30:43 |
Iain Lane |
mutter (Ubuntu Eoan): status |
Confirmed |
Invalid |
|
2019-06-02 11:30:50 |
Iain Lane |
bug task added |
|
gnome-session (Ubuntu) |
|
2019-06-02 11:31:14 |
Iain Lane |
bug task added |
|
gnome-shell (Ubuntu) |
|
2019-06-02 11:31:24 |
Iain Lane |
gdm3 (Ubuntu Eoan): status |
Confirmed |
In Progress |
|
2019-06-02 11:31:27 |
Iain Lane |
gnome-session (Ubuntu Eoan): status |
New |
In Progress |
|
2019-06-02 11:31:30 |
Iain Lane |
gnome-shell (Ubuntu Eoan): status |
New |
In Progress |
|
2019-06-02 11:31:33 |
Iain Lane |
gnome-session (Ubuntu Eoan): assignee |
|
Iain Lane (laney) |
|
2019-06-02 11:31:35 |
Iain Lane |
gnome-shell (Ubuntu Eoan): assignee |
|
Iain Lane (laney) |
|
2019-06-13 10:55:27 |
Daniel van Vugt |
summary |
Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it) |
Ubuntu login screen sometimes doesn't appear on a single GPU Nvidia system (and setting WaylandEnable=false fixes it) |
|
2019-06-13 12:19:34 |
Miguel Angel Muñoz |
bug |
|
|
added subscriber Miguel Angel Muñoz |
2019-07-22 04:04:56 |
Daniel van Vugt |
tags |
cosmic disco nvidia |
disco nvidia |
|
2019-08-26 23:40:40 |
Launchpad Janitor |
gdm3 (Ubuntu Eoan): status |
In Progress |
Fix Released |
|
2019-08-27 13:14:09 |
Launchpad Janitor |
gnome-shell (Ubuntu Eoan): status |
In Progress |
Fix Released |
|
2019-08-27 13:14:19 |
Launchpad Janitor |
gnome-session (Ubuntu Eoan): status |
In Progress |
Fix Released |
|
2019-10-02 14:03:23 |
Ricardo Portugal |
removed subscriber Ricardo Portugal |
|
|
|
2019-10-19 08:45:17 |
Mathew Hodson |
bug task deleted |
mutter (Ubuntu) |
|
|
2019-10-19 08:45:28 |
Mathew Hodson |
bug task deleted |
mutter (Ubuntu Eoan) |
|
|