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 Kernel
Packages, which is subscribed to linux in Ubuntu
The newly created crash report is #1787698.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1782347
Title:
[radeon] GDM3 fails to load without nomodeset
Status in gdm3 package in Ubuntu:
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
Based on my comment #6, could this be related to #1782347 in any way, as this
only happens when graphics is involved?
Please note however that #1782347 is about Ubuntu only, while this bug is about
both Ubuntu and XUbuntu.
Thanks,
MZ
--
You received this bug notification because you are a memb
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1782347/+attachment/5168073/+files/ProcEnviron.txt
** Attachment removed: "ProcEnviron.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+attachment/5168073/+files/ProcEnviron.txt
**
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1782347
Title:
[radeon] GDM3 fails to load without nomodeset
Sta
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1782347/+attachment/5168072/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
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, howe
Public bug reported:
The 'beep' command does not beep: I get no errors, not even in log files or
dmesg, but no sound can be heard.
The beep volume is ok (checked and unmuted with 'alsamixer').
This used to work in 16.04, so it is a regression.
'lsmod' shows that the 'pcspkr' module is loaded. I
** 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 Kernel
Packages, which is subscribed to linux in Ub
Forgot to add: the system reboots/shutsdown fine when running in
'single' mode, i.e.: without switching to graphics mode first.
Thanks,
MZ
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/17
** 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: Incomplete
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
http
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: "dmesg_noquiet_nomod
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
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1782347/+attachment/5165239/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1782347
Title:
[radeon] GDM3 fails to load
apport information
** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt"
https://bugs.launchpad.net/bugs/1782347/+attachment/5165240/+files/modified.conffile..etc.gdm3.custom.conf.txt
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
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
Marked as requested, as it also happens with the latest upstream kernel.
Also, booting without acpi=off takes a very long time (1 minute?) before my
passphrase is asked (the logical volume is not found at first, and the system
has to perform a lot of scanning). With acpi=off, the question is ask
Public bug reported:
Using default GRUB parameters ("quiet splash" or even "noquiet"), I'm
unable to reboot or shutdown: the Plymouth circle starts spinning, then
it stops and the system is frozen (altgr+sysrq won't work either).
If I use "acpi=off", I can reboot but obviously the system will not
This also happens on the live cd, and in Ubuntu 18.04 too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1781889
Title:
System freezes on restart or shutdown
Status in linux package in
Public bug reported:
If booting without 'nomodeset', Plymouth hangs very ofter right after
the Grub page, before the splash screen, leaving me to a useless black
screen.
(However, when booting with 'nomodeset' Unity icons can't be resized any
longer: see
https://bugs.launchpad.net/ubuntu/+source/
Public bug reported:
When booting with the 'nomodeset' Linux kernel parameter, Unity launcher
icons can no longer be resized.
** Affects: unity (Ubuntu)
Importance: Undecided
Status: New
** Package changed: linux-firmware (Ubuntu) => unity (Ubuntu)
--
You received this bug notifi
25 matches
Mail list logo
