gpu-manager still deletes xorg.conf

[Alistair Buxton]

To reproduce:

1. Create /etc/X11/xorg.conf
2. Wait until there is an update for some package (I don't know which one, suspect an nvidia driver one).
3. Reboot.

Result: gpu-manager deletes xorg.conf.

Expected result: gpu-manager does not delete xorg.conf.

Despite claims of a fix, this is still happening.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-drivers-common 1:0.2.91.7
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Oct 2 17:36:03 2014
InstallationDate: Installed on 2014-06-29 (94 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
SourcePackage: ubuntu-drivers-common
UpgradeStatus: No upgrade log present (probably fresh install)

[Alistair Buxton (a-j-buxton)]

With commentary:

How many cards? 1
The number of cards has changed! <-- No it hasn't.
Has the system changed? Yes <-- Wrong

System configuration has changed <-- Wrong
Single card detected
Driver is already loaded and enabled
Nothing to do
System configuration has changed
Removing xorg.conf. Path: /etc/X11/xorg.conf <-- Wrong

[Launchpad Janitor (janitor)]

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

[David Finch (ubuntu-mytsoftware)]

This started happening to me when I upgraded to 15.04 (from 14.04 stepping through 14.10). After several deletions (seemed like every update or every couple boots), I ended up disabling the gpu-manager service and making xorg.conf read-only and sticky for added measure.

gpu-manager only caught my eye because it was taking the most time according to "systemd-analyze blame", about 18 seconds. It was just luck that I killed two birds with one stone by disabling it. I have a geforce 560M with the proprietary driver and no optimus support (though the upgrade installed and tried to enable prime).

[inode77 (simon-gerber)]

Happens to me too on HP Zbook 15 with (Nvidia/Intel) only Nvidia active.
Disabled intel card in bios.

Workaround:
Add "nogpumanager" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and execute update-grub to disable gpu-manger.

/var/log/gpu-manager.log
log_file: /var/log/gpu-manager.log
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
grep dmesg status 256
dmesg status 256 == 0? No
Is nvidia loaded? yes
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is fglrx loaded? no
Was fglrx unloaded? no
Is fglrx blacklisted? no
Is intel loaded? no
Is radeon loaded? no
Is radeon blacklisted? no
Is nouveau loaded? no
Is nouveau blacklisted? yes
Is fglrx kernel module available? no
Is nvidia kernel module available? yes
Vendor/Device Id: 10de:11fc
BusID "PCI:1@0:0:0"
Is boot vga? yes
Skipping "/dev/dri/card0", driven by "nvidia-drm"
Skipping "/dev/dri/card0", driven by "nvidia-drm"
Skipping "/dev/dri/card0", driven by "nvidia-drm"
Does it require offloading? no
last cards number = 2
Has amd? no
Has intel? no
Has nvidia? yes
How many cards? 1
The number of cards has changed!
Has the system changed? Yes
main_arch_path x86_64-linux-gnu, other_arch_path i386-linux-gnu
Current alternative: /usr/lib/nvidia-346/ld.so.conf
Current core alternative: (null)
Is nvidia enabled? yes
Is fglrx enabled? no
Is mesa enabled? no
Is pxpress enabled? no
Is prime enabled? no
Is nvidia available? yes
Is fglrx available? no
Is fglrx-core available? no
Is mesa available? yes
Is pxpress available? no
Is prime available? yes
System configuration has changed
Single card detected
Driver is already loaded and enabled
Nothing to do
System configuration has changed
Removing xorg.conf. Path: /etc/X11/xorg.conf

[Manuel Iglesias Alonso (glesialo)]

It is ridiculous that this bug doesn't have the highest priority.

Imagine an inexperienced user that, after an update, finds its system unusable.

This is my /var/log/gpu-manager.log now:
  Disabled by kernel parameter "nogpumanager"

[Alberto Milone (albertomilone)]

@Alistair: the system didn't really change in your case. It's just that when you first run gpu-manager, it will have no records on any previous runs (comparing "last cards number = 0" with "How many cards? 1"), so it will try to configure your system. It should only happen the first time, unless you manually delete /var/lib/ubuntu-drivers-common/last_gfx_boot , that is.

@David: passing the "nogpumanager" parameter on boot is enough. 18 seconds is a really long time, I'm not sure that is the problem. Seeing your log might have helped.

@inode: disabling a GPU in the bios will make gpu-manager reconfigure your xorg.conf for you (only the first time, until you re-enable the GPU, etc.). If you don't like that behaviour, the boot parameter is ok for you to use.

@Manuel: sorry but your log only shows that gpumanager is disabled, so it's not much help to me. You didn't even describe how or when the "problem" happened, so I'm not sure how to help.

[Manuel Iglesias Alonso (glesialo)]

@Alberto Milone: The only reason for my previous comment is to highlight the importance of this bug.

I had exactly the same problem as 'Alistair Buxton':

  How many cards? 1
  The number of cards has changed! <-- No it hasn't.
  Has the system changed? Yes <-- Wrong

/etc/X11/xorg.conf was removed three times (not in a row but, apparently, randomly) before I decided to disable the buggy gpu-manager for good.