No problem. Just wait until it happens again and eventually one of the
crash reports will be more usable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782347
Title:
[radeon] GDM3 fails to load
Bug #1787698 was reported to be useless, possibly because the machine
was not up-to-date, which isn't the case because mine was; so I can't be
more helpful here...
Thanks,
MZ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The newly created crash report is #1787698.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782347
Title:
[radeon] GDM3 fails to load without nomodeset
To manage notifications about this bug go to:
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (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/1782347
Thanks. Unfortunately crash bug 1783999 is partially corrupt and not
debuggable. So please send more crash reports as soon as you find
them...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782347
Thanks, I did step #2 (#3 was useless because #2 didn't fail) and the
newly-created bug report is #1783999.
Thanks,
MZ
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification
Mostly the same, yes. That's just a dumb bot... You can choose to either
do as it asks or to ignore it and set 'Confirmed'.
Separately, I still think something might be crashing, and when it does
you wouldn't really know a crash had occurred. Only the absence of a
working system is a hint. Please
apport information
** Description changed:
Both with the livecd (usb drive) and the installed version, I must boot with
the 'nomodeset' kernel parameter at GRUB; otherwise GDM3 will not boot (the
screen will keep on flashing in semi-textual mode, with a white mouse arrow
stuck).
This,
Isn't it the same logs I provided with apport-collect before?
Thanks,
MZ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782347
Title:
[radeon] GDM3 fails to load without nomodeset
To manage
** Changed in: gdm3 (Ubuntu)
Status: Confirmed => New
** Changed in: linux (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782347
Title:
[radeon]
** Attachment added: "dmesg_noquiet_nomodeset.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+attachment/5167533/+files/dmesg_noquiet_nomodeset.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "journalctl_noquiet_nomodeset.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+attachment/5167534/+files/journalctl_noquiet_nomodeset.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Nothing crashed, so I skipped Your points #2 and #3.
As for #1, here's the log:
* when booting with 'noquiet nomodeset'
* and when booting with 'noquiet single' (I must add 'single' because starting
gdm without 'nomodeset' halts the machine).
Thanks,
MZ
** Attachment added:
** Attachment added: "journalctl_noquiet_single.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+attachment/5167536/+files/journalctl_noquiet_single.txt
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status:
** Attachment added: "dmesg_noquiet_single.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+attachment/5167535/+files/dmesg_noquiet_single.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, next please run these commands and send us the resulting files:
dmesg > dmesg.txt
journalctl > journal.txt
And in case something is crashing please also do:
1. Apply the workaround from bug 994921.
2. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Sorry, no improvements.
I booted the live cd in single mode, modified /etc/gdm3/custom.conf as
follows, then exited the single mode and continued the normal boot
process.
1) First attempt:
#WaylandEnable=false
I can see the purple background for a moment, then I'm sent back to text
mode and the
Please edit your /etc/gdm3/custom.conf and comment out:
WaylandEnable=false
Now you should be able to boot without 'nomodeset'...?
** Changed in: gdm3 (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this
apport information
** Tags added: apport-collected
** Description changed:
Both with the livecd (usb drive) and the installed version, I must boot with
the 'nomodeset' kernel parameter at GRUB; otherwise GDM3 will not boot (the
screen will keep on flashing in semi-textual mode, with a white
Logs were taken when booting with 'nomodeset'; otherwise the machine is
unbootable.
Thanks,
MZ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782347
Title:
[radeon] GDM3 fails to load without
20 matches
Mail list logo