Public bug reported:
Since using Ubuntu 18.04.1 LTS on boot at the login screen the screen is
frozen. I tried both gdm3 and lightdm login managers, with either I
don't get into the system.
I am using Intel 2nd generation (Sandy bridge) CPU with on-board GPU: HD
Graphics 2000. I have an external 2
** Description changed:
Since using Ubuntu 18.04.1 LTS on boot at the login screen the screen is
frozen. I tried both gdm3 and lightdm login managers, with either I
don't get into the system.
I am using Intel 2nd generation (Sandy bridge) CPU with on-board GPU: HD
Graphics 2000. I hav
I'll try this first thing I get home!
Can I run the "sudo update-initramfs" during nomodeset? Or should I
remove "nomodeset" first and start in recovery mode? Since otherwise, I
am not able to get a command line.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
1. $ sudo vim /etc/default/grub
2. removed "nomodeset" (leaving emptry string for GRUB_CMDLINE_LINUX
3. $ sudo update-grub
4. $ sudo update-initramfs -u
5. $ sudo vim /etc/gdm3/custom.conf
6. remove # in front of "#WaylandEnable=false", leaving "WaylandEnable=false"
(under "[daemon]")
7. sudo rebo
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792807
Title:
Login screen freeze
To manage notifications about this bug go to:
h
I've tried that as well but that does not work either unfortunately. The
system freezes pretty much directly after the purple screen appears.
Hitting Ctrl+Alt+F4 does not do anything at that moment.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug not
I've done that now:
1. $ sudo vim /etc/default/grub
2. changed "splash" to "nosplash"
3. $ sudo update-initramfs -u
4. $ sudo update-grub
5. $ sudo reboot
Note:
* I've added the "-u" option to the update-initramfs as well (it tells me "You
must specify at least one of -c, -u, or -d", so I did "-
** Attachment added: "nosplash_2.jpg"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+attachment/5190305/+files/nosplash_2.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792
** Attachment added: "nosplash_3.jpg"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+attachment/5190314/+files/nosplash_3.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792
I noticed that I have installed (and could only find) the amd64 image. I
have a 64-bit Intel (https://ark.intel.com/products/52209/Intel-
Core-i5-2500-Processor-6M-Cache-up-to-3_70-GHz) processor. Would that
matter at all? (Maybe a dumb question, but throwing it out there anyway
;-))
--
You recei
Do you have any other possible solution or attempt I could do to get
this solved? It's pretty annoying to have to run in nomodeset all the
time. Screen res is making my eyes weird o.0 ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've just borrowed an external graphics card (ATI) from the office and
plugged it, and then it boots without a problem.
So it definitely has to do with the GPU I mentioned. It would be too
much of a coincidence if this was a hardware problem I think, since the
problem appeared immediately since th
I've solved it for me now with a new graphics card. Couldn't bare the
nomodeset anymore knowing there was an alternative solution. Imagine how
much I am attached to Ubuntu to rather buy a new graphics card then to
switch to another OS ;-).
We can keep it open if you want further investigation and
This bug is (at least in our case) caused by libblkid (through
udevd/udevadm) reporting the disklabel type as "dos" while the os-prober
script looks for "msdos". This was fixed upstream in Debian os-prober
1.76 as a fix for Debian bug #817023 for which I have attached the
patch, though I recommend
Public bug reported:
After upgrading our testing server to bionic, our web application stopped
responding entirely
after the second request. We traced this to a problem in php-apcu where it
would block upon the second
call to apcu_entry and completely lock up the php processes causing the serve
15 matches
Mail list logo
