[radeon] Dual monitor loop login

Bug #1865444 reported by Mel on 2020-03-02
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Undecided
Unassigned

Bug Description

Ubuntu version 20.04 desktop gnome 3 no virtualisation

Can’t login using dual monitors the error oops something went wrong until I unplug a monitor then login acts as expected

also since last update

No mouse pointer on login screen
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-02-29 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220)
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: gnome-shell 3.35.91-1ubuntu2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
Tags: focal package-from-proposed
Uname: Linux 5.4.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1865444

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

tags: added: focal
Changed in gnome-shell (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected package-from-proposed
description: updated

apport information

apport information

apport information

apport information

apport information

I can see quite a few graphics-related errors in your log but can't tell what type of GPU it is and also the log is truncated.

Please run:

  lspci -k > lspcik.txt
  journalctl -b0 > journal.txt
  journalctl -b-1 > prevjournal.txt
  xrandr > xrandr.txt # while both monitors are plugged in

and attach the resulting text files here.

Mel (bloodrunkhunter) wrote :
Mel (bloodrunkhunter) wrote :
Mel (bloodrunkhunter) wrote :
Mel (bloodrunkhunter) wrote :
tags: added: radeon
summary: - Dual monitor loop login
+ [radeon] Dual monitor loop login
Daniel van Vugt (vanvugt) wrote :

Thanks. The only relevant error I can find in there is strange:

Mar 02 11:49:30 mel-Aspire-M5600-AM3600 gnome-shell[3916]: gnome-shell: Fatal IO error 0 (Success) on X server :0.

and

Feb 29 20:58:53 mel-Aspire-M5600-AM3600 gnome-shell[3068]: gnome-shell: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

So it sounds like Xorg is crashing...

--------------------------------------------------------

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

Mel (bloodrunkhunter) wrote :

Okay after some experimenting

I found switching to Wayland brings up both monitors after login

But no mouse pointer

Daniel van Vugt (vanvugt) wrote :

Thanks. That confirms it was Xorg crashing, which might be the fault of the radeon driver.

Also the missing mouse pointer is bug 1867080.

affects: gnome-shell (Ubuntu) → xorg-server (Ubuntu)
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

Daniel van Vugt (vanvugt) wrote :

It appears this system is using the 'radeon' Xorg driver when it shouldn't. Modern systems should be using the default 'modeset' driver. Please remove any config file you might have that is forcing the 'radeon' driver to be used.

Timo Aaltonen (tjaalton) wrote :

modeset is only used on intel and newer nvidia's by default, fwiw

Launchpad Janitor (janitor) wrote :

[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]

Changed in xorg-server (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers