from:"Chuck McManis"

[Desktop-packages] [Bug 1580296] Re: Screen is blank and won't recover

2016-05-27 Thread Chuck McManis

Ok, we've confirmed that this bug can be fixed by applying the patch to
xfsettingsd from jkampe68 as highlighted in this XFCE Bugzilla  bug :
https://bugzilla.xfce.org/show_bug.cgi?id=11107

Once applied the screen behavior is as expected (and most importantly
the monitor re-lights after the system wakes up)

** Bug watch added: Xfce Bugzilla #11107
   https://bugzilla.xfce.org/show_bug.cgi?id=11107

-- 
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/1580296

Title:
  Screen is blank and won't recover

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am running Xubuntu 16.04, I have reproduced this problem on both the
  Gigabyte Brix system and the NUC5i7RYH system. Both use integrated
  Intel graphics.

  The symptom is that after a long period of time (like overnight) the
  screen is blanked and moving the mouse or pressing keys on the
  keyboard will not switch the screen back on. Using Ctl-Alt-Fx will let
  me bring up an alternate VT however, so I can log in and look around.
  Switching back to VT7 (where Xubuntu is) the screen goes black again
  and won't wake up.

  The only error message I can find is in lightdm.log which is as
  follows:

  [160363.826] (II) intel(0): Modeline "1920x1080"x0.0  148.50  1920 2448 2492 
2640  1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
  [161295.000] (II) AIGLX: Suspending AIGLX clients for VT switch
  [161328.781] (II) AIGLX: Resuming AIGLX clients after VT switch
  [161328.781] (EE) intel(0): sna_mode_shutdown_crtc: invalid state found on 
pipe 0, disabling CRTC:21

  If I send a SIGHUP to the session manager it restarts and the screen
  wakes up with the Login screen again, that of course loses all my open
  windows from the previous session so it isn't really optimal.

  The lightdm log seems to suggest that it tried to "wake up" but that
  something happened that wasn't supposed to. When it isn't in this
  state (say for example I am up and running and I use Ctl-Alt-F2 to
  switch to Vt2 and then switch back to lightdm it works as expected and
  there is no error.

  I've set every parameter of every screen saver locker blanker etc to
  never suspend block or shutdown. And the screen still blanks. That
  makes me wonder what agency is turning off the screen.

  Let me know where to look and I'll add data to this bug. The situation
  is quite reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue May 10 11:30:30 2016
  DistUpgraded: 2016-04-29 22:17:07,822 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Haswell-ULT Integrated Graphics 
Controller [1458:d000]
  InstallationDate: Installed on 2016-03-18 (53 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: GIGABYTE MMLP5AP-00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=7a790f8d-8940-4397-a820-c35ca84f7696 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-30 (10 days ago)
  dmi.bios.date: 08/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MMLP5AP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/29/2013:svnGIGABYTE:pnMMLP5AP-00:pvr1.x:rvnGIGABYTE:rnMMLP5AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: MMLP5AP-00
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git201

[Desktop-packages] [Bug 1581302] Re: Monitor remains blanked with Intel Graphics

2016-05-20 Thread Chuck McManis

Ok, I've done the overnight test (monitors blanked) and both systems
recovered (relit the monitors) in the morning. So for me at least the
jkempke68 patch has fixed the problem.

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

Title:
  Monitor remains blanked with Intel Graphics

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-settings package in Ubuntu:
  New

Bug description:
  Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display Port 
or HDMI
  Running Xubuntu 16.04 - latest all current patches

  Sometimes the monitor remains blanked even when the session has
  reactivated.

  I have been able to reproduce this problem by letting the monitor
  remain in the 'blanked' state for > 60 minutes, or powering off the
  monitor. When the monitor is powered back on and the session is woken
  up with mouse or keyboard input, it does wake up but the monitor
  remains blanked.

  I was able to prove to myself the session was awake by leaving it with
  terminal opened to full screen with VIM running on an NFS mounted file
  system. I could type and save at the black monitor screen and see that
  the file got updates from a different system. So the session is "live"
  but the computer has forgotten to re-establish the DisplayPort link.

  An error appears in the lightdm logs about setting a CRTC, if you
  activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr
  --output DP1 --auto` it also registers that CRTC error. HOWEVER, if
  you ssh in from a different machine, tell bash to export DISPLAY=:0
  (set $DISPLAY to ':0') and then type 'xrandr --output DP1 --auto' the
  screen turns on again! This also happens on a Gigabyte BRIX system
  (same NUC reference design but in that case a core i3 rather than a
  Core i7).

  To reproduce, turn off the monitor, wait an hour, and turn it on
  again.

  You can also kill HUP the lightdm process and that will restart a new
  session (but open windows in the previous session are lost).

  So interesting questions, why does typing xrandr "locally" give you
  the error but running it from an ssh session work?

  Since xrandr and restarting the session can both "fix" the problem,
  the driver seems to know how to turn the display on if told correctly.

  How can I find out where the code is getting the CRTC error?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu May 12 20:33:01 2016
  InstallationDate: Installed on 2016-05-08 (4 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch
  LightdmLog:
   [+80180.09s] DEBUG: Seat seat0 changes active session to 
   [+80189.53s] DEBUG: Seat seat0 changes active session to 64
   [+80222.67s] DEBUG: Seat seat0 changes active session to c4
   [+80222.67s] DEBUG: Session c4 is already active
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1581302] Re: Monitor remains blanked with Intel Graphics

2016-05-19 Thread Chuck McManis

I've run both my systems monitor's through a full
idle->blank->sleep->wakeup cycle by setting the power managment settings
to do that, and with this patch they both have come back. The final step
will be to leave them overnight and verify I can wake them both up in
the morning. Will update when I've done that.

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

Title:
  Monitor remains blanked with Intel Graphics

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-settings package in Ubuntu:
  New

Bug description:
  Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display Port 
or HDMI
  Running Xubuntu 16.04 - latest all current patches

  Sometimes the monitor remains blanked even when the session has
  reactivated.

  I have been able to reproduce this problem by letting the monitor
  remain in the 'blanked' state for > 60 minutes, or powering off the
  monitor. When the monitor is powered back on and the session is woken
  up with mouse or keyboard input, it does wake up but the monitor
  remains blanked.

  I was able to prove to myself the session was awake by leaving it with
  terminal opened to full screen with VIM running on an NFS mounted file
  system. I could type and save at the black monitor screen and see that
  the file got updates from a different system. So the session is "live"
  but the computer has forgotten to re-establish the DisplayPort link.

  An error appears in the lightdm logs about setting a CRTC, if you
  activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr
  --output DP1 --auto` it also registers that CRTC error. HOWEVER, if
  you ssh in from a different machine, tell bash to export DISPLAY=:0
  (set $DISPLAY to ':0') and then type 'xrandr --output DP1 --auto' the
  screen turns on again! This also happens on a Gigabyte BRIX system
  (same NUC reference design but in that case a core i3 rather than a
  Core i7).

  To reproduce, turn off the monitor, wait an hour, and turn it on
  again.

  You can also kill HUP the lightdm process and that will restart a new
  session (but open windows in the previous session are lost).

  So interesting questions, why does typing xrandr "locally" give you
  the error but running it from an ssh session work?

  Since xrandr and restarting the session can both "fix" the problem,
  the driver seems to know how to turn the display on if told correctly.

  How can I find out where the code is getting the CRTC error?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu May 12 20:33:01 2016
  InstallationDate: Installed on 2016-05-08 (4 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch
  LightdmLog:
   [+80180.09s] DEBUG: Seat seat0 changes active session to 
   [+80189.53s] DEBUG: Seat seat0 changes active session to 64
   [+80222.67s] DEBUG: Seat seat0 changes active session to c4
   [+80222.67s] DEBUG: Session c4 is already active
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 1581302] Re: Monitor remains blanked with Intel Graphics

2016-05-19 Thread Chuck McManis

This has worked to re-display my screen power is removed and then
re-applied to the monitor, I'm doing further testing to see if it also
fixes the issue with lockscreen blanking and sleeping.

On Thu, May 19, 2016 at 8:25 AM, Jan  wrote:
> Please try the patch mentioned here:
> https://bugs.launchpad.net/bugs/1308105
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1581302
>
> Title:
>   Monitor remains blanked with Intel Graphics
>
> Status in lightdm package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display 
> Port or HDMI
>   Running Xubuntu 16.04 - latest all current patches
>
>   Sometimes the monitor remains blanked even when the session has
>   reactivated.
>
>   I have been able to reproduce this problem by letting the monitor
>   remain in the 'blanked' state for > 60 minutes, or powering off the
>   monitor. When the monitor is powered back on and the session is woken
>   up with mouse or keyboard input, it does wake up but the monitor
>   remains blanked.
>
>   I was able to prove to myself the session was awake by leaving it with
>   terminal opened to full screen with VIM running on an NFS mounted file
>   system. I could type and save at the black monitor screen and see that
>   the file got updates from a different system. So the session is "live"
>   but the computer has forgotten to re-establish the DisplayPort link.
>
>   An error appears in the lightdm logs about setting a CRTC, if you
>   activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr
>   --output DP1 --auto` it also registers that CRTC error. HOWEVER, if
>   you ssh in from a different machine, tell bash to export DISPLAY=:0
>   (set $DISPLAY to ':0') and then type 'xrandr --output DP1 --auto' the
>   screen turns on again! This also happens on a Gigabyte BRIX system
>   (same NUC reference design but in that case a core i3 rather than a
>   Core i7).
>
>   To reproduce, turn off the monitor, wait an hour, and turn it on
>   again.
>
>   You can also kill HUP the lightdm process and that will restart a new
>   session (but open windows in the previous session are lost).
>
>   So interesting questions, why does typing xrandr "locally" give you
>   the error but running it from an ssh session work?
>
>   Since xrandr and restarting the session can both "fix" the problem,
>   the driver seems to know how to turn the display on if told correctly.
>
>   How can I find out where the code is getting the CRTC error?
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: lightdm 1.18.1-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
>   Uname: Linux 4.4.0-22-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2
>   Architecture: amd64
>   CurrentDesktop: XFCE
>   Date: Thu May 12 20:33:01 2016
>   InstallationDate: Installed on 2016-05-08 (4 days ago)
>   InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
> (20160420.1)
>   LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch
>   LightdmLog:
>[+80180.09s] DEBUG: Seat seat0 changes active session to
>[+80189.53s] DEBUG: Seat seat0 changes active session to 64
>[+80222.67s] DEBUG: Seat seat0 changes active session to c4
>[+80222.67s] DEBUG: Session c4 is already active
>   SourcePackage: lightdm
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1581302/+subscriptions

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

Title:
  Monitor remains blanked with Intel Graphics

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display Port 
or HDMI
  Running Xubuntu 16.04 - latest all current patches

  Sometimes the monitor remains blanked even when the session has
  reactivated.

  I have been able to reproduce this problem by letting the monitor
  remain in the 'blanked' state for > 60 minutes, or powering off the
  monitor. When the monitor is powered back on and the session is woken
  up with mouse or keyboard input, it does wake up but the monitor
  remains blanked.

  I was able to prove to myself the session was awake by leaving it with
  terminal opened to full screen with VIM running on an NFS mounted file
  system. I could type and save at the black monitor screen and see that
  the file got updates from a different system. So the session is "live"
  but the computer has forgotten to re-establish the DisplayPort link.

  An error appears in the lightdm logs about setting a CRTC, if you
  activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr
  --output DP1 --auto` it also registers that CRTC error. HOWEVER, if
  yo

[Desktop-packages] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled

2016-05-19 Thread Chuck McManis

And the title here really needs to be changed that this isn't an nVidia
bug, that probably confuses people trying to find it.

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

Title:
  Xfce resets TV mode to NULL when power cycled

Status in Mythbuntu:
  Confirmed
Status in xfce4-settings:
  Confirmed
Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Invalid
Status in xfce4-settings package in Ubuntu:
  Confirmed

Bug description:
  I had an HTPC with Mythbuntu 12.04 installed.  Upon upgrading a new
  behavior that if the TV is power cycled it no longer detects a link
  with the HTPC.

  When this happens I can find in the xorg log that there is an
  accompanying log item:

  [ 39829.509] (II) NVIDIA(0): Setting mode "NULL"

  After debugging with NVIDIA at
  https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being-
  detected/ we've deteremined it's a X client that reacts to the RANDR
  events causing the mode to be set to NULL.

  Working through the list in an Xfce environment, the culprit is
  xfsettingsd.  If xfsettingsd is running, it causes the TV to come up
  in a NULL mode.  If it's killed, it remains in the mode it was
  previously running in.

  
  Until this is fixed, this behavior can be worked around with a simple shell 
script:
  ==
  #!/bin/sh
  #Fix TV state when HDMI link is lost.
  #By Mario Limonciello 

  OUTPUT="HDMI-0"
  BAD_MODE="1280x720"
  GOOD_MODE="1920x1080"

  for MODE in $BAD_MODE $GOOD_MODE; do
   DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
   sleep 2
  done
  ==

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled

2016-05-19 Thread Chuck McManis

I have confirmed that this patch allows my NUC derived systems to
recover the display when the monitor is switched off and then switched
on again. This for a NUC5i7RYH and a Gigabyte BRIX (GB-BXi5H-4200)

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

Title:
  Xfce resets TV mode to NULL when power cycled

Status in Mythbuntu:
  Confirmed
Status in xfce4-settings:
  Confirmed
Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Invalid
Status in xfce4-settings package in Ubuntu:
  Confirmed

Bug description:
  I had an HTPC with Mythbuntu 12.04 installed.  Upon upgrading a new
  behavior that if the TV is power cycled it no longer detects a link
  with the HTPC.

  When this happens I can find in the xorg log that there is an
  accompanying log item:

  [ 39829.509] (II) NVIDIA(0): Setting mode "NULL"

  After debugging with NVIDIA at
  https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being-
  detected/ we've deteremined it's a X client that reacts to the RANDR
  events causing the mode to be set to NULL.

  Working through the list in an Xfce environment, the culprit is
  xfsettingsd.  If xfsettingsd is running, it causes the TV to come up
  in a NULL mode.  If it's killed, it remains in the mode it was
  previously running in.

  
  Until this is fixed, this behavior can be worked around with a simple shell 
script:
  ==
  #!/bin/sh
  #Fix TV state when HDMI link is lost.
  #By Mario Limonciello 

  OUTPUT="HDMI-0"
  BAD_MODE="1280x720"
  GOOD_MODE="1920x1080"

  for MODE in $BAD_MODE $GOOD_MODE; do
   DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
   sleep 2
  done
  ==

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled

2016-05-19 Thread Chuck McManis

Ok I have confirmed that the patch in #115 (Saved the Patch by jkampe68
(http://bug-attachment.xfce.org/attachment.cgi?id=6590) as .patch file.)
fixes the issue on NUC derived systems (Intel graphics, I've got a
NUC5i7RYH and a Gigabyte BRIX) where the screen attached to the display
port output does not come back on when power is re-applied to the
monitor. The next step is validating that the screen can recover after a
"sleep state" which has been initiated by light-lock.

I pulled the git repo applied the patch, ran autogen.sh then make, then
make install. Rebooted and verified the new settingsd was running (

cmcmanis@charliehorse:~$ xfsettingsd --version
xfsettingsd 4.12.0git-56abfbd (Xfce 4.12)

Copyright (c) 2008-2011
The Xfce development team. All rights reserved.

Please report bugs to .
cmcmanis@charliehorse:~$ 

Power cycled the monitor, and where previously this would always cause
it to not come back, it now returns. System is Xubuntu 16.04 otherwise
vanilla install.

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

Title:
  Xfce resets TV mode to NULL when power cycled

Status in Mythbuntu:
  Confirmed
Status in xfce4-settings:
  Confirmed
Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Invalid
Status in xfce4-settings package in Ubuntu:
  Confirmed

Bug description:
  I had an HTPC with Mythbuntu 12.04 installed.  Upon upgrading a new
  behavior that if the TV is power cycled it no longer detects a link
  with the HTPC.

  When this happens I can find in the xorg log that there is an
  accompanying log item:

  [ 39829.509] (II) NVIDIA(0): Setting mode "NULL"

  After debugging with NVIDIA at
  https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being-
  detected/ we've deteremined it's a X client that reacts to the RANDR
  events causing the mode to be set to NULL.

  Working through the list in an Xfce environment, the culprit is
  xfsettingsd.  If xfsettingsd is running, it causes the TV to come up
  in a NULL mode.  If it's killed, it remains in the mode it was
  previously running in.

  
  Until this is fixed, this behavior can be worked around with a simple shell 
script:
  ==
  #!/bin/sh
  #Fix TV state when HDMI link is lost.
  #By Mario Limonciello 

  OUTPUT="HDMI-0"
  BAD_MODE="1280x720"
  GOOD_MODE="1920x1080"

  for MODE in $BAD_MODE $GOOD_MODE; do
   DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
   sleep 2
  done
  ==

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled

2016-05-19 Thread Chuck McManis

Scratch that, forgot to autogen.sh first, did it earlier but did not
repeat after resolving the last dependency. So not it compiled, on to
testing.

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

Title:
  Xfce resets TV mode to NULL when power cycled

Status in Mythbuntu:
  Confirmed
Status in xfce4-settings:
  Confirmed
Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Invalid
Status in xfce4-settings package in Ubuntu:
  Confirmed

Bug description:
  I had an HTPC with Mythbuntu 12.04 installed.  Upon upgrading a new
  behavior that if the TV is power cycled it no longer detects a link
  with the HTPC.

  When this happens I can find in the xorg log that there is an
  accompanying log item:

  [ 39829.509] (II) NVIDIA(0): Setting mode "NULL"

  After debugging with NVIDIA at
  https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being-
  detected/ we've deteremined it's a X client that reacts to the RANDR
  events causing the mode to be set to NULL.

  Working through the list in an Xfce environment, the culprit is
  xfsettingsd.  If xfsettingsd is running, it causes the TV to come up
  in a NULL mode.  If it's killed, it remains in the mode it was
  previously running in.

  
  Until this is fixed, this behavior can be worked around with a simple shell 
script:
  ==
  #!/bin/sh
  #Fix TV state when HDMI link is lost.
  #By Mario Limonciello 

  OUTPUT="HDMI-0"
  BAD_MODE="1280x720"
  GOOD_MODE="1920x1080"

  for MODE in $BAD_MODE $GOOD_MODE; do
   DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
   sleep 2
  done
  ==

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled

2016-05-19 Thread Chuck McManis

Trying to implement the suggestion in #115, I've got the git repo from
xfce.org and applied the patch, did the configure which ends with:

Build Configuration:

* Installation prefix:   /usr
* Debug Support: full
* Xrandr support:yes
* UPower support:no
* Libnotify support: no
* Xcursor support:   yes
* Xorg libinput support: no
* Embedded settings dialogs  no
* Sounds settings supportno
* Libxklavier support:   yes
* Mime settings (gio-unix):  yes

But attempting a build gives the error:

make[4]: Entering directory 
'/home/cmcmanis/src/xfce4-settings/dialogs/appearance-settings'
  CC   xfce4_appearance_settings-main.o
main.c:44:34: fatal error: appearance-dialog_ui.h: No such file or directory
compilation terminated.
Makefile:667: recipe for target 'xfce4_appearance_settings-main.o' failed

So presumably there is a missing step here somewhere.

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

Title:
  Xfce resets TV mode to NULL when power cycled

Status in Mythbuntu:
  Confirmed
Status in xfce4-settings:
  Confirmed
Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Invalid
Status in xfce4-settings package in Ubuntu:
  Confirmed

Bug description:
  I had an HTPC with Mythbuntu 12.04 installed.  Upon upgrading a new
  behavior that if the TV is power cycled it no longer detects a link
  with the HTPC.

  When this happens I can find in the xorg log that there is an
  accompanying log item:

  [ 39829.509] (II) NVIDIA(0): Setting mode "NULL"

  After debugging with NVIDIA at
  https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being-
  detected/ we've deteremined it's a X client that reacts to the RANDR
  events causing the mode to be set to NULL.

  Working through the list in an Xfce environment, the culprit is
  xfsettingsd.  If xfsettingsd is running, it causes the TV to come up
  in a NULL mode.  If it's killed, it remains in the mode it was
  previously running in.

  
  Until this is fixed, this behavior can be worked around with a simple shell 
script:
  ==
  #!/bin/sh
  #Fix TV state when HDMI link is lost.
  #By Mario Limonciello 

  OUTPUT="HDMI-0"
  BAD_MODE="1280x720"
  GOOD_MODE="1920x1080"

  for MODE in $BAD_MODE $GOOD_MODE; do
   DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
   sleep 2
  done
  ==

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1580296] Re: Screen is blank and won't recover

2016-05-12 Thread Chuck McManis

See also 15801302 about monitor blanking. You can get the monitor back
on with xrandr --output DP1 --auto *if* you do that from an SSH session
(not from one of the alternate terminals)

-- 
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/1580296

Title:
  Screen is blank and won't recover

Status in xorg package in Ubuntu:
  New

Bug description:
  I am running Xubuntu 16.04, I have reproduced this problem on both the
  Gigabyte Brix system and the NUC5i7RYH system. Both use integrated
  Intel graphics.

  The symptom is that after a long period of time (like overnight) the
  screen is blanked and moving the mouse or pressing keys on the
  keyboard will not switch the screen back on. Using Ctl-Alt-Fx will let
  me bring up an alternate VT however, so I can log in and look around.
  Switching back to VT7 (where Xubuntu is) the screen goes black again
  and won't wake up.

  The only error message I can find is in lightdm.log which is as
  follows:

  [160363.826] (II) intel(0): Modeline "1920x1080"x0.0  148.50  1920 2448 2492 
2640  1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
  [161295.000] (II) AIGLX: Suspending AIGLX clients for VT switch
  [161328.781] (II) AIGLX: Resuming AIGLX clients after VT switch
  [161328.781] (EE) intel(0): sna_mode_shutdown_crtc: invalid state found on 
pipe 0, disabling CRTC:21

  If I send a SIGHUP to the session manager it restarts and the screen
  wakes up with the Login screen again, that of course loses all my open
  windows from the previous session so it isn't really optimal.

  The lightdm log seems to suggest that it tried to "wake up" but that
  something happened that wasn't supposed to. When it isn't in this
  state (say for example I am up and running and I use Ctl-Alt-F2 to
  switch to Vt2 and then switch back to lightdm it works as expected and
  there is no error.

  I've set every parameter of every screen saver locker blanker etc to
  never suspend block or shutdown. And the screen still blanks. That
  makes me wonder what agency is turning off the screen.

  Let me know where to look and I'll add data to this bug. The situation
  is quite reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue May 10 11:30:30 2016
  DistUpgraded: 2016-04-29 22:17:07,822 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Haswell-ULT Integrated Graphics 
Controller [1458:d000]
  InstallationDate: Installed on 2016-03-18 (53 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: GIGABYTE MMLP5AP-00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=7a790f8d-8940-4397-a820-c35ca84f7696 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-30 (10 days ago)
  dmi.bios.date: 08/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MMLP5AP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/29/2013:svnGIGABYTE:pnMMLP5AP-00:pvr1.x:rvnGIGABYTE:rnMMLP5AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: MMLP5AP-00
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue May 10 11:00:37 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button

[Desktop-packages] [Bug 1581302] [NEW] Monitor remains blanked with Intel Graphics

2016-05-12 Thread Chuck McManis

Public bug reported:

Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display Port or 
HDMI
Running Xubuntu 16.04 - latest all current patches

Sometimes the monitor remains blanked even when the session has
reactivated.

I have been able to reproduce this problem by letting the monitor remain
in the 'blanked' state for > 60 minutes, or powering off the monitor.
When the monitor is powered back on and the session is woken up with
mouse or keyboard input, it does wake up but the monitor remains
blanked.

I was able to prove to myself the session was awake by leaving it with
terminal opened to full screen with VIM running on an NFS mounted file
system. I could type and save at the black monitor screen and see that
the file got updates from a different system. So the session is "live"
but the computer has forgotten to re-establish the DisplayPort link.

An error appears in the lightdm logs about setting a CRTC, if you
activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr
--output DP1 --auto` it also registers that CRTC error. HOWEVER, if you
ssh in from a different machine, tell bash to export DISPLAY=:0 (set
$DISPLAY to ':0') and then type 'xrandr --output DP1 --auto' the screen
turns on again! This also happens on a Gigabyte BRIX system (same NUC
reference design but in that case a core i3 rather than a Core i7).

To reproduce, turn off the monitor, wait an hour, and turn it on again.

You can also kill HUP the lightdm process and that will restart a new
session (but open windows in the previous session are lost).

So interesting questions, why does typing xrandr "locally" give you the
error but running it from an ssh session work?

Since xrandr and restarting the session can both "fix" the problem, the
driver seems to know how to turn the display on if told correctly.

How can I find out where the code is getting the CRTC error?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu May 12 20:33:01 2016
InstallationDate: Installed on 2016-05-08 (4 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch
LightdmLog:
 [+80180.09s] DEBUG: Seat seat0 changes active session to 
 [+80189.53s] DEBUG: Seat seat0 changes active session to 64
 [+80222.67s] DEBUG: Seat seat0 changes active session to c4
 [+80222.67s] DEBUG: Session c4 is already active
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lightdm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  Monitor remains blanked with Intel Graphics

Status in lightdm package in Ubuntu:
  New

Bug description:
  Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display Port 
or HDMI
  Running Xubuntu 16.04 - latest all current patches

  Sometimes the monitor remains blanked even when the session has
  reactivated.

  I have been able to reproduce this problem by letting the monitor
  remain in the 'blanked' state for > 60 minutes, or powering off the
  monitor. When the monitor is powered back on and the session is woken
  up with mouse or keyboard input, it does wake up but the monitor
  remains blanked.

  I was able to prove to myself the session was awake by leaving it with
  terminal opened to full screen with VIM running on an NFS mounted file
  system. I could type and save at the black monitor screen and see that
  the file got updates from a different system. So the session is "live"
  but the computer has forgotten to re-establish the DisplayPort link.

  An error appears in the lightdm logs about setting a CRTC, if you
  activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr
  --output DP1 --auto` it also registers that CRTC error. HOWEVER, if
  you ssh in from a different machine, tell bash to export DISPLAY=:0
  (set $DISPLAY to ':0') and then type 'xrandr --output DP1 --auto' the
  screen turns on again! This also happens on a Gigabyte BRIX system
  (same NUC reference design but in that case a core i3 rather than a
  Core i7).

  To reproduce, turn off the monitor, wait an hour, and turn it on
  again.

  You can also kill HUP the lightdm process and that will restart a new
  session (but open windows in the previous session are lost).

  So interesting questions, why does typing xrandr "locally" give you
  the error but running it from an ssh session work?

  Since xrandr and restarting the session can both "fix" the problem,
  the driver seems to know how to turn the display on if told correctly.

  How can I find out where the c

[Desktop-packages] [Bug 1580296] [NEW] Screen is blank and won't recover

2016-05-10 Thread Chuck McManis

Public bug reported:

I am running Xubuntu 16.04, I have reproduced this problem on both the
Gigabyte Brix system and the NUC5i7RYH system. Both use integrated Intel
graphics.

The symptom is that after a long period of time (like overnight) the
screen is blanked and moving the mouse or pressing keys on the keyboard
will not switch the screen back on. Using Ctl-Alt-Fx will let me bring
up an alternate VT however, so I can log in and look around. Switching
back to VT7 (where Xubuntu is) the screen goes black again and won't
wake up.

The only error message I can find is in lightdm.log which is as follows:

[160363.826] (II) intel(0): Modeline "1920x1080"x0.0  148.50  1920 2448 2492 
2640  1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
[161295.000] (II) AIGLX: Suspending AIGLX clients for VT switch
[161328.781] (II) AIGLX: Resuming AIGLX clients after VT switch
[161328.781] (EE) intel(0): sna_mode_shutdown_crtc: invalid state found on pipe 
0, disabling CRTC:21

If I send a SIGHUP to the session manager it restarts and the screen
wakes up with the Login screen again, that of course loses all my open
windows from the previous session so it isn't really optimal.

The lightdm log seems to suggest that it tried to "wake up" but that
something happened that wasn't supposed to. When it isn't in this state
(say for example I am up and running and I use Ctl-Alt-F2 to switch to
Vt2 and then switch back to lightdm it works as expected and there is no
error.

I've set every parameter of every screen saver locker blanker etc to
never suspend block or shutdown. And the screen still blanks. That makes
me wonder what agency is turning off the screen.

Let me know where to look and I'll add data to this bug. The situation
is quite reproducible.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Tue May 10 11:30:30 2016
DistUpgraded: 2016-04-29 22:17:07,822 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Haswell-ULT Integrated Graphics 
Controller [1458:d000]
InstallationDate: Installed on 2016-03-18 (53 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: GIGABYTE MMLP5AP-00
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=7a790f8d-8940-4397-a820-c35ca84f7696 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to xenial on 2016-04-30 (10 days ago)
dmi.bios.date: 08/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MMLP5AP-00
dmi.board.vendor: GIGABYTE
dmi.board.version: 1.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/29/2013:svnGIGABYTE:pnMMLP5AP-00:pvr1.x:rvnGIGABYTE:rnMMLP5AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: MMLP5AP-00
dmi.product.version: 1.x
dmi.sys.vendor: GIGABYTE
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue May 10 11:00:37 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVideo BusKEYBOARD, id 7
 inputPower Button KEYBOARD, id 8
 inputLogitech K400KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   10147 
 vendor ACI
xserver.version: 2:1.18.3-1ubuntu2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubuntu xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xo

[Desktop-packages] [Bug 1580296] Re: Screen is blank and won't recover

[Desktop-packages] [Bug 1581302] Re: Monitor remains blanked with Intel Graphics

[Desktop-packages] [Bug 1581302] Re: Monitor remains blanked with Intel Graphics

Re: [Desktop-packages] [Bug 1581302] Re: Monitor remains blanked with Intel Graphics

[Desktop-packages] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled

[Desktop-packages] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled

[Desktop-packages] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled

[Desktop-packages] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled

[Desktop-packages] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled

[Desktop-packages] [Bug 1580296] Re: Screen is blank and won't recover

[Desktop-packages] [Bug 1581302] [NEW] Monitor remains blanked with Intel Graphics

[Desktop-packages] [Bug 1580296] [NEW] Screen is blank and won't recover

12 matches

Site Navigation

Mail list logo

Footer information