Bug #1764087 “Wrongly boots into low graphics mode using kernel ...” : Bugs : xorg-server package : Ubuntu

Revision history for this message

Dave Goldsbrough (daveg-k) wrote on 2018-04-15:

#1

BootLog.txt Edit (5.5 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (61.7 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.7 KiB, text/plain; charset="utf-8")
DpkgLog.txt Edit (92.4 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (15.0 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (13.9 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (518 bytes, text/plain; charset="utf-8")
MonitorsUser.xml.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.6 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (927 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.9 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (151.4 KiB, text/plain; charset="utf-8")
UnitySupportTest.txt Edit (611 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (30.2 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (6.3 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (9.6 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (13.5 KiB, text/plain; charset="utf-8")
xserver.devices.txt Edit (421 bytes, text/plain; charset="utf-8")
xserver.outputs.txt Edit (1.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Dave Goldsbrough (daveg-k) wrote on 2018-04-21:

#2

output from various commands to grab info during crash Edit (388.8 KiB, text/plain)

I can see warnings and errors, but have no idea what to do to fix.

Revision history for this message

Chris Perry (clissold345) wrote on 2018-04-22:

#3

This sounds like the error that I'm getting. I did a system update on 19th April. Ubuntu 16.04. Lenovo T61. Is display info (see below) relevant to the bug?

As a workaround the following command makes the wifi work:

sudo service network-manager restart

        *-display:0
             description: VGA compatible controller
             product: Mobile GM965/GL960 Integrated Graphics Controller (primary)
             vendor: Intel Corporation
             physical id: 2
             bus info: pci@0000:00:02.0
             version: 0c
             width: 64 bits
             clock: 33MHz
             capabilities: msi pm vga_controller bus_master cap_list rom
             configuration: driver=i915 latency=0
             resources: irq:16 memory:f8100000-f81fffff memory:e0000000-efffffff ioport:1800(size=8) memory:c0000-dffff
        *-display:1 UNCLAIMED
             description: Display controller
             product: Mobile GM965/GL960 Integrated Graphics Controller (secondary)
             vendor: Intel Corporation
             physical id: 2.1
             bus info: pci@0000:00:02.1
             version: 0c
             width: 64 bits
             clock: 33MHz
             capabilities: pm bus_master cap_list
             configuration: latency=0
             resources: memory:f8200000-f82fffff

Revision history for this message

Dave Goldsbrough (daveg-k) wrote on 2018-04-22:

#4

Thanks for the workaround to make wifi work - that could come in useful.

I'm unsure whether your display info is relevant or not. As far as I am aware I only have one graphics controller/card/GPU integrated into the Processor - Intel® Core™ i5 CPU M 520 @ 2.40GHz × 4 and that is Intel® Ironlake Mobile with just the laptop screen as a monitor. Your output suggests 2 and/or 2 monitors?

For completeness I add the following:-

sudo lshw -c display

  *-display
       description: VGA compatible controller
       product: Core Processor Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 02
       width: 64 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:26 memory:f2000000-f23fffff memory:d0000000-dfffffff ioport:1800(size=8) memory:c0000-dffff

Revision history for this message

Chris Perry (clissold345) wrote on 2018-04-23:

#5

This might be the same bug as #1764445

Revision history for this message

Dave Goldsbrough (daveg-k) wrote on 2018-04-23:

#6

You could well be right Chris that https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764445 raise one day later appears to be having the same effect, although the ubuntu version, and the architecture is different.

Revision history for this message

Dave Goldsbrough (daveg-k) wrote on 2018-04-24:

#7

gpu-manager.log Edit (1.9 KiB, text/plain)

Now this is interesting!
As part Ubuntu updates the kernel was updated on 23rd April 2018 to 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

On 3 consecutive occasions no the laptop has booted fine!

I decided to look around /ver/log and noticed this for the first time
-rw-r--r-- 1 root root 1929 Apr 24 09:04 gpu-manager.log and I now attach it for anyone to see.

If you look at this log you will see that it provides many negative answers to questions regarding which graphics card is present. But this small extract here shows that it eventually found "/dev/dri/card0".

Vendor/Device Id: 8086:46
BusID "PCI:0@0:2:0"
Is boot vga? yes
Skipping , driven by "i915"
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card0", driven by "i915"
Found "/dev/dri/card0", driven by "i915"
output 0:
card0-LVDS-1
Number of connected outputs for /dev/dri/card0: 1
Does it require offloading? yes
last cards number = 1

If you recall, this bug was reporting that card could not be found and was therefore booting into low graphics mode.

So, is my system fixed? Has the new kernel fixed it?

Revision history for this message

Chris Perry (clissold345) wrote on 2018-04-24:

#8

Hi Dave, I'm using the new kernel (4.13.0-39-generic) and I still get the error (though my laptop did start up once without the error).

Revision history for this message

Dave Goldsbrough (daveg-k) wrote on 2018-04-25: Re: [Bug 1764087] Re: Wrongly boots into low graphics mode

#9

Download full text (5.2 KiB)

Hello Chris,
Writing to you direct rather than through the bug - hope you don't mind.
I too had my first failure today using the new kernel, manifesting itself
in the same way.
It's getting a bit tiresome now and I have little faith in it being
corrected. I have spent quite a bit of time researching the issue and
trying a few things out to no avail. There are other things needing my
attention just now.
So, it was always in my plans to install 18.04 LTS at some stage. Rather
than do a fresh install of 16.04 LTS which I had thought was a way of
hopefully overcoming the problem, I may as well go for 18.04 LTS.
I just need to plan things out so that I manage to safely backup my
documents and all my settings (I have very low vision and my settings are
important to me). The planning and preparation in itself will take some
time.
When I get round to it I will let you know how things go.
Best Regards
Dave

On 24 April 2018 at 22:29, Chris Perry <email address hidden> wrote:

> Hi Dave, I'm using the new kernel (4.13.0-39-generic) and I still get
> the error (though my laptop did start up once without the error).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1764087
>
> Title:
> Wrongly boots into low graphics mode
>
> Status in xorg package in Ubuntu:
> New
>
> Bug description:
> Description: Ubuntu 16.04.4 LTS
> Release: 16.04
>
> Lenovo T410 with VGA compatible controller [0300]: Intel Corporation
> Core Processor Integrated Graphics Controller [8086:0046] (rev 02)
>
> Booting from latest kernel ThinkPad-T410 4.13.0-38-generic
> #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64
> x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi
> connection insofar as it does not connect to my router.
>
> Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar
> 7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the
> time but occasionally has the same effects.
>
> I have had to submit this report after booting from 4.13.0.37 in order
> to submit bug.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: xorg 1:7.7+13ubuntu3
> ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
> Uname: Linux 4.13.0-37-generic x86_64
> .tmp.unity_support_test.0:
>
> ApportVersion: 2.20.1-0ubuntu2.15
> Architecture: amd64
> CompizPlugins: No value set for `/apps/compiz-1/general/
> screen0/options/active_plugins'
> CompositorRunning: compiz
> CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
> CompositorUnredirectFSW: true
> CurrentDesktop: Unity
> Date: Sun Apr 15 10:40:31 2018
> DistUpgraded: Fresh install
> DistroCodename: xenial
> DistroVariant: ubuntu
> ExtraDebuggingInterest: Yes, if not too technical
> GraphicsCard:
> Intel Corporation Core Processor Integrated Graphics Controller
> [8086:0046] (rev 02) (prog-if 00 [VGA controller])
> Subsystem: Lenovo Core Processor Integrated Graphics Controller
> [17aa:215a]
> InstallationDate: Installed on 2016-09-24 (567 days ago)
> InstallationMedia: Ubuntu 16.04.1 LTS...

Hello Chris,
Writing to you direct rather than through the bug - hope you don't mind.
I too had my first failure today using the new kernel, manifesting itself
in the same way.
It's getting a bit tiresome now and I have little faith in it being
corrected. I have spent quite a bit of time researching the issue and
trying a few things out to no avail. There are other things needing my
attention just now.
So, it was always in my plans to install 18.04 LTS at some stage.  Rather
than do a fresh install of 16.04 LTS which I had thought was a way of
hopefully overcoming the problem, I may as well go for 18.04 LTS.
I just need to plan things out so that I manage to safely backup my
documents and all my settings (I have very low vision and my settings are
important to me). The planning and preparation in itself will take some
time.
When I get round to it I will let you know how things go.
Best Regards
Dave

On 24 April 2018 at 22:29, Chris Perry <clissold345@googlemail.com> wrote:

> Hi Dave, I'm using the new kernel (4.13.0-39-generic) and I still get
> the error (though my laptop did start up once without the error).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1764087
>
> Title:
>   Wrongly boots into low graphics mode
>
> Status in xorg package in Ubuntu:
>   New
>
> Bug description:
>   Description:  Ubuntu 16.04.4 LTS
>   Release:      16.04
>
>   Lenovo T410 with VGA compatible controller [0300]: Intel Corporation
>   Core Processor Integrated Graphics Controller [8086:0046] (rev 02)
>
>   Booting from latest kernel ThinkPad-T410 4.13.0-38-generic
>   #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64
>   x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi
>   connection insofar as it does not connect to my router.
>
>   Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar
>   7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the
>   time but occasionally has the same effects.
>
>   I have had to submit this report after booting from 4.13.0.37 in order
>   to submit bug.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu3
>   ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
>   Uname: Linux 4.13.0-37-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.1-0ubuntu2.15
>   Architecture: amd64
>   CompizPlugins: No value set for `/apps/compiz-1/general/
> screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   CurrentDesktop: Unity
>   Date: Sun Apr 15 10:40:31 2018
>   DistUpgraded: Fresh install
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>    Intel Corporation Core Processor Integrated Graphics Controller
> [8086:0046] (rev 02) (prog-if 00 [VGA controller])
>      Subsystem: Lenovo Core Processor Integrated Graphics Controller
> [17aa:215a]
>   InstallationDate: Installed on 2016-09-24 (567 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
> (20160719)
>   MachineType: LENOVO 2519Y11
>   ProcEnviron:
>    LANGUAGE=en_GB:en
>    PATH=(custom, no user)
>    XDG_RUNTIME_DIR=<set>
>    LANG=en_GB.UTF-8
>    SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic
> root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash
> vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 02/14/2013
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: 6IET85WW (1.45 )
>   dmi.board.name: 2519Y11
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Available
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:
> pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:
> ct10:cvrNotAvailable:
>   dmi.product.family: ThinkPad T410
>   dmi.product.name: 2519Y11
>   dmi.product.version: ThinkPad T410
>   dmi.sys.vendor: LENOVO
>   version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.83-1~16.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
>   version.xserver-xorg-core: xserver-xorg-core N/A
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
>   xserver.bootTime: Sun Apr 15 08:52:27 2018
>   xserver.configfile: default
>   xserver.errors:
>
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.19.5-0ubuntu2~16.04.1
>   xserver.video_driver: modeset
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087/+subscriptions
>

Chris Perry (clissold345) on 2018-04-25

Changed in xorg (Ubuntu):
status:	New → Confirmed

Revision history for this message

Dave Goldsbrough (daveg-k) wrote on 2018-04-25: Re: Wrongly boots into low graphics mode

#10

Needs cross-referencing to this bug https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1766307

Bug Watch Updater (bug-watch-updater) on 2018-05-05

Changed in xorg-server:
importance:	Unknown → High
status:	Unknown → Won't Fix

Revision history for this message

Dave Goldsbrough (daveg-k) wrote on 2018-05-05:

#11

Cross reference now to a lightdm bug which has been raised as a consequence of
https://bugs.freedesktop.org/show_bug.cgi?id=106407
saying it is not a xorg bug

Revision history for this message

Dave Goldsbrough (daveg-k) wrote on 2018-05-06:

#12

Dissapointed by the lack of progress on this bug, I decided to research and experiment more to a point where I am now happy with the way my boot up and shut down processes are working to my satisfaction, albeit not perfect.
You will notice I also raised the bug direct on xorg bug service https://bugs.freedesktop.org/show_bug.cgi?id=106407
and it was the response in there that made me appreciate it was not an xorg bug but that the problem lay elsewhere.

I decided to experiment with my grub file - some nagging thing suggested it might go back several months this when I was having problems related to not being able to disable accelerated graphics on shutdown.

During my problems I had assumed I was using an intel graphics driver - my recollections and log outputs never suggested otherwise. Indeed examining > System Settings > Details confimed it was "Graphics Intel® Ironlake Mobile". Little minor things were though not right. One example - when clicking on the date in the system tray it did not display all my upcoming calendar appts from my google calendar.

This is now an extract from /etc/default/grub file

#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force apm=power_off"
# the above line is the original from install - not satisfactory
# GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
# the above line is OK but the splash moving dots just keep going!
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
# the above line results in it booting into low graphics
GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset"
# trying the above line to see if removing "splash" cures the moving dots
GRUB_CMDLINE_LINUX=""

You will see it was the addition of the nomodeset param that "solved" the low graphics problem initially mentioned in this bug but it brought with it other issues like the moving splash dots persisting in every screen I opened. (I found the process' connected by ps -ef | grep plymouth and then killed the last one off which got rid of the dots)

This then led me to removing the splash param in the grub file and now although I get scrolls of info saying what is happening during boot and no ubuntu splash, I can live with that.

Importantly, I should add the addition of the "nomodeset" param means > System Settings > Details now shows "Graphics llvmpipe (LLVM 5.0, 128 bits)". Clicking on date in the system tray displays my google calender recent entries so all in all I am a happy bunny.

I will leave it to others to decide the status of this bug. Hopefully, my story may help others get to the bottom of their similar issues.

Dissapointed by the lack of progress on this bug, I decided to research and experiment more to a point where I am now happy with the way my boot up and shut down processes are working to my satisfaction, albeit not perfect.
You will notice I also raised the bug direct on xorg bug service https://bugs.freedesktop.org/show_bug.cgi?id=106407
and it was the response in there that made me appreciate it was not an xorg bug but that the problem lay elsewhere.

I decided to experiment with my grub file - some nagging thing suggested it might go back several months this when I was having problems related to not being able to disable accelerated graphics on shutdown.

During my problems I had assumed I was using an intel graphics driver - my recollections and log outputs never suggested otherwise.  Indeed examining  > System Settings > Details confimed it was "Graphics Intel® Ironlake Mobile".  Little minor things were though not right.  One example - when clicking on the date in the system tray it did not display all my upcoming calendar appts from my google calendar.

This is now an extract from /etc/default/grub file

#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force apm=power_off"
# the above line is the original from install - not satisfactory
# GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
# the above line is OK but the splash moving dots just keep going!
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
# the above line results in it booting into low graphics
GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset"
# trying the above line to see if removing "splash" cures the moving dots
GRUB_CMDLINE_LINUX=""

You will see it was the addition of the nomodeset param that "solved" the low graphics problem initially mentioned in this bug but it brought with it other issues like the moving splash dots persisting in every screen I opened. (I found the process' connected by ps -ef | grep plymouth and then killed the last one off which got rid of the dots)

This then led me to removing the splash param in the grub file and now although I get scrolls of info saying what is happening during boot and no ubuntu splash, I can live with that.

Importantly, I should add the addition of the "nomodeset" param means > System Settings > Details now shows "Graphics llvmpipe (LLVM 5.0, 128 bits)".  Clicking on date in the system tray displays my google calender recent entries so all in all I am a happy bunny.

I will leave it to others to decide the status of this bug.  Hopefully, my story may help others get to the bottom of their similar issues.

Daniel van Vugt (vanvugt) on 2018-09-14

affects:	xorg (Ubuntu) → xorg-server (Ubuntu)
summary:	- Wrongly boots into low graphics mode + Wrongly boots into low graphics mode using kernel 4.13.0-38 (mostly + works with 4.13.0-37)

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2018-09-14: Status changed to Confirmed

#13

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2018-10-08:

#14

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in lightdm (Ubuntu):
status:	New → Confirmed

Revision history for this message

Dave Goldsbrough (daveg-k) wrote on 2018-10-22:

#15

I need to update this bug. Since raising the bug, the machine has been updated to Ubuntu 18.04 but still has some issues.
Please cross reference with bug https://bugs.launchpad.net/bugs/1766974
The grub file remains the same:-
GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset"
which results in lots of scrolling messages which I am happy to put up with.
The nain issue is the often errors of:-
intel ips 0000:00:1f.6: failed to disable graphics turbo
during boot and shutdown. This app arrantly is on +pci:0000:00:1f.6 and I gather is occurring 100s of time in the background.

In About my graphics is still showing as llvmpipe (LLVM 6.0, 128 bits) - no idea what this is or how it happened - simething to do with "nomodeset" ?

I will do a "apport-collect" to do a full collect and update.

Revision history for this message

Dave Goldsbrough (daveg-k) wrote on 2018-10-22: Dependencies.txt

#16

Dependencies.txt Edit (25.0 KiB, text/plain)

apport information

tags:	added: apport-collected bionic
description:	updated

Revision history for this message

Dave Goldsbrough (daveg-k) wrote on 2018-10-22: LightdmUsersConfig.txt

#17

LightdmUsersConfig.txt Edit (451 bytes, text/plain)

apport information

Revision history for this message

Dave Goldsbrough (daveg-k) wrote on 2018-10-22: ProcCpuinfoMinimal.txt

#18

ProcCpuinfoMinimal.txt Edit (971 bytes, text/plain)

apport information

Revision history for this message

Dave Goldsbrough (daveg-k) wrote on 2018-10-22: ProcEnviron.txt

#19

ProcEnviron.txt Edit (115 bytes, text/plain)

apport information

Brad Figg (brad-figg) on 2019-07-24

tags:

added: cscc

Revision history for this message

Dave Goldsbrough (daveg-k) wrote on 2019-07-25:

#20

I forgot all about this bug until the tag of cscc was added.

As reported previously the machine is now running 18.04.2 LTS fairly well. All updates including kernels have been done,

Graphics now state Intel® Ironlake Mobile and the /etc/default/grub file contains the line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

So all is well with the world.

Kai-Heng Feng (kaihengfeng) on 2019-07-29

Changed in linux (Ubuntu):
status:	Confirmed → Fix Released

Daniel van Vugt (vanvugt) on 2019-07-30

Changed in lightdm (Ubuntu):
status:	Confirmed → Invalid
Changed in xorg-server (Ubuntu):
status:	Confirmed → Invalid

	Status	Importance	Assigned to
X.Org X server	Won't Fix	High	freedesktop-bugs #106407
lightdm (Ubuntu)	Invalid	Undecided	Unassigned
linux (Ubuntu)	Fix Released	Undecided	Unassigned
xorg-server (Ubuntu)	Invalid	Undecided	Unassigned

Ubuntu
xorg-server package

Wrongly boots into low graphics mode using kernel 4.13.0-38 (mostly works with 4.13.0-37)

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntuxorg-server package

Wrongly boots into low graphics mode using kernel 4.13.0-38 (mostly works with 4.13.0-37)

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
xorg-server package