[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gdm3 (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/1571227
tea for one, I suspect that this issue was fixed when LP: #1686257 was
fixed this week. Could you install all updates and see if GDM works for
you now?
Victor, it sounds like you are affected by LP: #1559576 The workaround
for that bug is to install xserver-xorg-legacy
** Changed in: gdm3
I have actually used Ubuntu 16.10, installed using ubuntu-gnome-desktop*
and ran into the same issue.
My configuration however is a bit more complex, as I have 2 NVIDIA GTX
970 FTW with the latest nvidia drivers from ppa:graphics-drivers/ppa
(which I could only get running after also enabling
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571227
Title:
Hello Tim
Thank you for your reply and advice.
Yes, I did install gnome-shell manually via synaptic, I have done this
at least half a dozen times with vanilla Ubuntu (inc Unity) 12.04 and
14.04.
Previously, I have never encountered a problem.
The instruction "sudo apt-get install
Oh you installed gnome-shell/gdm manually onto Ubuntu? You might be
missing some dependencies, try run
sudo apt-get install ubuntu-gnome-desktop^
reboot, if its still not working install
sudo apt-get install gnome-session-wayland
reboot, if its still not working uncomment the following line in
I have edited custom.conf as advised and here is the extended report.
Hopefully, this will now help.
Thanks in advance
** Attachment added: "journal04.log"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1571227/+attachment/4641624/+files/journal04.log
--
You received this bug
You want to use the following for the debug section
[debug]
# Uncomment the line below to turn on debugging
# More verbose logs
# Additionally lets the X server dump core if it crashes
Enable=true
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
gdm3 custom.conf herewith
** Attachment added: "custom.conf"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1571227/+attachment/4641184/+files/custom.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is another journalctl report
Copy of gdm3 custom.conf sent separately
If the custom.conf is still incorrect, please let me know which line to
alter.
Thanks
** Attachment added: "journal03.log"
Apr 19 17:45:07 mark-desktop gdm-x-session[832]: Unable to load file
'/etc/gdm3/custom.conf': Key file contains line 'More verbose logs'
which is not a key-value pair, group, or comment
You only want to uncomment the Debug line, not the comment "More verbose
logs" line. Can you try again
--
You
Hello Tim
Extended log report attached as requested
** Attachment added: "journal02.log"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1571227/+attachment/4640001/+files/journal02.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
There doesnt seem anything useful in that Log, can you uncomment the
debug line in /etc/gdm3/custom.conf and get the journal log again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571227
Title:
Hello Tim
Thanks for the instruction, I have attached a log report.
Hopefully it will help you investigate.
Kind regards
Mark
From: Tim <t...@feathertop.org>
To: markexh...@yahoo.co.uk
Sent: Sunday, 17 April 2016, 11:36
Subject: [Bug 1571227] Re: Unable to arrive at Desktop usin
-set gdm3 as display manager
- boot and wait until it fails
- switch to VT1 (ctl+alt+F1)
- run: `journalctl > ~/journal.log
- attach that file to this bug (after you unbreak you computer and login via
lightdm!)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
571227] Re: Unable to arrive at Desktop using gdm3
hey tea for one,
that log is incomplete
you need to do something like
`journalctl > journal.log`
and then attach that (it will be thousands of lines)
as an aside some of the earlier intel GPU's work better when booted with
"nom
hey tea for one,
that log is incomplete
you need to do something like
`journalctl > journal.log`
and then attach that (it will be thousands of lines)
as an aside some of the earlier intel GPU's work better when booted with
"nomodeset" kernel param.
--
You received this bug notification
** Attachment added: "journalctl01"
https://bugs.launchpad.net/bugs/1571227/+attachment/4638594/+files/journalctl01
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571227
Title:
Unable to arrive
requested.
I hope it is helpful.
Kind regards
Mark
From: Tim <t...@feathertop.org>
To: markexh...@yahoo.co.uk
Sent: Sunday, 17 April 2016, 2:07
Subject: [Bug 1571227] Re: Unable to arrive at Desktop using gdm3
Also what GPU are you using?
--
You received this bug notifica
Also what GPU are you using?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571227
Title:
Unable to arrive at Desktop using gdm3
To manage notifications about this bug go to:
It could be an issue with your graphics drivers, though I am surprised
you were blocked from switching to a VT?
Can you get logs by running `journalctl` and attach them here using
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
21 matches
Mail list logo
