[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (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/1724362
T
Yes all changes were saved, the disk problems were on an external drive
not the OS drive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724362
Title:
Not booting - 17.10 Beta 2
To manage notificat
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724362
Title:
Not booting - 17.10 Beta 2
To manage notifications about this bug go to:
https:
I have no idea why that's happening ... is it the same if you boot the
Ubuntu kernel? Did you double check that your changes to custom.conf got
saved (since you're having disk problems)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I only have Ubuntu on Xorg, or Unity to choose from on the sign in
screen.
System is all updated.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724362
Title:
Not booting - 17.10 Beta 2
To
Also update your system, seems there was a gnome-shell bug affecting
some AMD/Nvidia cards. It sounds similar to your problem and has been
fixed. Bug #1723577 for reference.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Double check on the login screen that you don't have an Xorg session
selected (click the gear icon next to "Sign In").
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724362
Title:
Not booting - 17.1
I just tried command
echo $XDG_SESSION_TYPE
and it returned
x11
So I would say no ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724362
Title:
Not booting - 17.10 Beta 2
To manage notific
I installed the upstream Kernel you advised and re-commented custom.conf
and booted up with the RC5 Kernel without issue.
Problem fixed ... thank you.
Does that mean i'm now using wayland ?
Thanks !!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Thanks. Unfortunately I don't see any errors or other useful information
about the problem in kern.log either.
Could you test the latest upstream kernel so we'll know whether or not
the problem has already been fixed? Currently this is 4.14-rc5, which
can be downloaded here:
http://kernel.ubuntu.
Hi Seth,
Thanks for coming back to me on this issue.
And you are spot on I made the change to custom.conf you mentioned above
and it has booted straight up into Ubuntu looking normal again.
I have attached kern.log file... please excuse all the BTRFS errors in
there i'm having issues with a cor
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724362
Title:
Not booting - 17.10 Beta 2
To manage notificat
Sounds like this is probably a problem in the graphics driver. When you
boot in recovery mode you're getting a reduced-functionality graphics
environment, which means that the logs that were attached don't show us
anything about what happens when you try to boot normally. Could you
attach the /var/
13 matches
Mail list logo
