desktop-packages team mailing list archive

[Joachim Durchholz <jo@xxxxxxxxxxxxx>]

It's my main and only work machine, I can upgrade if and only if I can easily revert any upgrade.
I don't expect to be able to revert from Wily to Vivid, so that's not an option unless I can have guarantees.
A driver update would be fine, I can always go back to Nouveau, then reinstall the current Nvidia driver.

Given #1488206 and #1507328, and that I've been having these problems
for years now, I do not expect the driver update to fix anything, but I
can still check and see what's happening. (My bets are on a race
condition somewhere in the wakeup software stack since the symptoms are
so irreproducible, but I don't know how to validate that.)

More symptoms:

9) Sometimes (rarely), X stops recognizing the screen. I get a "default"
screen @1024x768 instead of the VGA-0, LVDS-0, and DP0...DP-6
connections in xrandr --verbose. It does not help to reboot, not even
when disconnecting from all power including battery. What does help is
installing Nouveau, then reinstalling nvidia-current.

10) Sometimes (slightly more often than symptom nr. 9), I get the same as nr. 8, shutdown does not complete. I cannot get a console through Ctrl-Alt-F1, but I can Ctrl-Alt-F7 and get a graphic screen with a greyed-out desktop and an empty dialog window (there's a white title bar and a grey dialog area, but no title, no icons, no text, no buttons, no border, entirely unresponsive).
What I could do was to Ctrl-Alt-Del to get to the lock screen. From there, I could resume my normal session (just to restore the same greyed-out-with-unresponsible-dialog behaviour). I could also start a guest session, but I didn't try anything there because I believe guest isn't in the sudoers list.
Logging in with explicit user name gave me a black screen and unresponsiveness to Ctrl-Alt-F1 and Ctrl-Alt-F7, so I power cycled the machine and called it a day.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1509326

Title:
  Various instabilities after resuming from standby

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  None of these problems are readily reproducible, I'm having a roughly
  30:70 chance of a successful standby. Things that I have seen happen:

  1) Click on Whisker menu -> Logoff ("Abmelden") button ->
  Logoff/Restart/Reboot/Standby dialog (no Hibernate option, I think
  it's blacklisted for my machine) -> Click on "Shutdown" -> no
  shutdown, I get the login screen.

  2) Trying to go to standby from the Logoff button in the login screen
  after seeing (1) -> monitor switches off, then on, login screen again.

  3) After (2), close the lid, open it, standby procedure from login
  screen -> works. Sometimes.

  4) After (2), remove machine from docking station, standby procedure
  from login screen -> works. Sometimes.

  5) Machine is in standby, I press the power button, I get some text
  mode messages, monitor flashes and shows graphic content (mostly a
  mouse cursor on some background, too fast to properly see), then the
  screen goes dark. Ctrl-Alt-F1 works, Ctrl-Alt-F7 simply makes the
  screen dark again (both the builtin laptop screen and one of the
  external, connected-through-docking-station screens).

  6) The effects from (5) can also happen right after cold booting the
  machine.

  7) I *think* on a few occasions, I tried to shutdown the machine and
  nothing happened at all.

  8) On some rarer occasions, nothing would happen after the shutdown
  command, and trying to issue another shutdown resulted in a message
  amounting to "can't do another action while the previous action is in
  progress"; I remember pstree reported some hung process that was
  connected to shutdown, and I couldn't kill it (not even kill -9). I
  cannot reproduce this, and I didn't take notes so I can't be more
  specific.

  I have no idea which of these effects are related to a common cause and which are independent.
  I have been unable to find out anything given that no individual phenomenon is reproducible with any reliability.
  I hope the attached debug info will help, but I fully expect this to require much more diagnosis.

  Hardware:
  - Docking station PR02X
  - Two 2560x1440 Dell U2515H monitors, one on each video output of the docking station
  - nVidia Quadro 2000M, using the proprietary driver (Nouveau cannot drive two 2560x1440 screens)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  346.96  Sun Aug 23 22:29:21 PDT 2015
   GCC version:  gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Oct 23 13:40:40 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-28-generic, x86_64: installed
   bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
   bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
   nvidia-346, 346.96, 3.19.0-31-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:04a3]
  InstallationDate: Installed on 2015-08-24 (59 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   upstart: indicator-sound-main-Prozess (11841) wurde von TERM-Signal beendet
   upstart: indicator-application-main-Prozess (11843) wurde von TERM-Signal beendet
  MachineType: Dell Inc. Precision M4600
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-31-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 08V9YG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/26/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
  xserver.bootTime: Thu Oct 22 10:57:03 2015
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.17.1-0ubuntu3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509326/+subscriptions