[Ubuntu-x-swat] [Bug 1561801] [NEW] Video cannot be restored after power save on AMDGPU

2016-03-24 Thread Brian Knoll
Public bug reported:

When I engage light-locker to lock my screen, it locks the screen and
disables power to the monitor, as it should.  However, I can never get
video back again after that.  Power to the monitor is never restored,
and the only way I can get my video back at that point is to restart my
display manager, for instance by SSHing in from another machine.  At
that point, the video comes back and I can use the system again.

This problem only happens on my AMDGPU-based Radeon system.  I have
another system that uses Intel video that doesn't have this problem.  I
should note, though, that in Trusty 14.04 the power save and restore
functions worked perfectly fine, and there was no issue restoring video
when I wanted the system to wake up the video.  But of course, at that
point I was using FGLRX as my video driver, which is no longer supported
or available in 16.04.

I'm very willing to help debug this, so if there is anything I can do to
help, please let me know.

Thanks,
Brian

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-video-amdgpu 1.0.1-1build2
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Thu Mar 24 20:43:48 2016
InstallationDate: Installed on 2016-03-22 (2 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160318)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-video-amdgpu
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xserver-xorg-video-amdgpu (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1561801

Title:
  Video cannot be restored after power save on AMDGPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1561801/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1561801] Re: Video cannot be restored after power save on AMDGPU

2016-03-24 Thread Brian Knoll
I should also add that I've tried disabling all of my power management
in my window manager settings, but the problem still occurs; that may or
may not be a bug in the window manager power management, but the net
effect appears to be that it is requesting the driver to cut the power
to the monitor, regardless, and then of course we end up with the same
problem we had before, which is that the video cannot come back without
a restart of the X server.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1561801

Title:
  Video cannot be restored after power save on AMDGPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1561801/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1561795] Re: Fullscreen Crash Intel GPU since Ubuntu 15.10

2016-03-24 Thread Michael Kasprzak
To quote myself elsewhere:

"I upgraded to 15.10 almost immediately after it was released, and have
been suffering from this issue ever since (15.04 worked way better than
14.04, so I had high hopes). It mainly crops up for me in Chrome, and
ruins my day when I accidentally press YouTube's fullscreen shortcut
key. The only way out has been to "killall -u myname". I had hoped to
find this problem resolved, but with Ubuntu 16.04 looming, it's kinda
crazy that it isn't.

It's worth noting it isn't a typical crash. Video becomes mostly
unresponsive, with the exception of the mouse cursor that can still be
moved (has no effect though). Audio continues to work, even YouTube and
Twitch that are streaming, there is just no longer any useful display.
Other reports seem to suggest disabling hardware acceleration in Chrome
works around the issue, but that's not really acceptable because of the
need for WebGL and such."

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

Title:
  Fullscreen Crash Intel GPU since Ubuntu 15.10

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1493170] Re: Fullscreen window goes to the background

2016-03-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xorg (Ubuntu)
   Status: New => Confirmed

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

Title:
  Fullscreen window goes to the background

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1516531] Re: Fullscreen Freeze.

2016-03-24 Thread Michael Kasprzak
FWIW I have an identical setup to Wayne Scott, but My Thinkpad is an
X230 with swivel touchscreen. I upgraded to 15.10 almost immediately
after it was released, and have been suffering from this issue ever
since (15.04 worked way better than 14.04, so I had high hopes). It
mainly crops up for me in Chrome, and ruins my day when I accidentally
press YouTube's fullscreen shortcut key. The only way out has been to
"killall -u myname". I had hoped to find this problem resolved, but with
Ubuntu 16.04 looming, it's kinda crazy that it isn't.

It's worth noting it isn't a typical crash. Video becomes mostly
unresponsive, with the exception of the mouse cursor that can still be
moved (has no effect though). Audio continues to work, even YouTube and
Twitch that are streaming, there is just no longer any useful display.
Other reports seem to suggest disabling hardware acceleration in Chrome
works around the issue, but that's not really acceptable because of the
need for WebGL and such.

I ran "ubuntu-bug xorg" as suggested above.

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1561795

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

Title:
  Fullscreen Freeze.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1561795] [NEW] Fullscreen Crash Intel GPU since Ubuntu 15.10

2016-03-24 Thread Michael Kasprzak
Public bug reported:

Ever since I upgraded to Ubuntu 15.10, I haven't been able to exit
fullscreen without video crashing. There are rare cases when I've been
able to safely exit, but more times than not, it doesn't. This is
typically when I'm using Chrome to watch YouTube or Twitch video
streams. The only way out is switch over and do a "killall -u myname".

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
Uname: Linux 4.2.0-34-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu5
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: Thu Mar 24 19:57:24 2016
DistUpgraded: 2015-10-25 04:02:46,508 DEBUG enabling apt cron job
DistroCodename: wily
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:2203]
InstallationDate: Installed on 2015-01-03 (446 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: LENOVO 343522U
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=a630eb7a-a0ab-49aa-bdb6-8221ae278346 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to wily on 2015-10-25 (151 days ago)
dmi.bios.date: 09/12/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GCETA0WW (2.60 )
dmi.board.asset.tag: Not Available
dmi.board.name: 343522U
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGCETA0WW(2.60):bd09/12/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 343522U
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.65-3
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.4-1intel1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.4-1intel1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Thu Mar 24 19:14:03 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 728 
 vendor LGD
xserver.version: 2:1.17.2-1ubuntu9.1

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu wily

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

Title:
  Fullscreen Crash Intel GPU since Ubuntu 15.10

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1561721] [NEW] ?

2016-03-24 Thread Rhino
Public bug reported:

?

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.63  Sat Nov  7 21:25:42 
PST 2015
 GCC version:  gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Fri Mar 25 09:10:47 2016
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed
 bbswitch, 0.7, 4.2.0-35-generic, x86_64: installed
 nvidia-352, 352.63, 4.2.0-16-generic, x86_64: installed
 nvidia-352, 352.63, 4.2.0-35-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation GK208 [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:84d6]
InstallationDate: Installed on 2016-03-20 (4 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=en_NZ:en
 PATH=(custom, no user)
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic 
root=UUID=887340ed-d37e-4b69-8a06-c9b10bb1ed5c ro noprompt persistent quiet 
splash
SourcePackage: xorg
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/24/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: 870 Extreme3 R2.0
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd03/24/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn870Extreme3R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Fri Mar 25 05:52:13 2016
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.2-1ubuntu9.1

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


** Tags: amd64 apport-bug ubuntu wily

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

Title:
  ?

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1561685] Re: x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest

2016-03-24 Thread Jason Gerard DeRose
Okay, I just tried this on an Intel GPU system, and it has the same
problem.

Arrow keys are broken with 1.18.2-2ubuntu0.1, but work fine with
1.18.1-1ubuntu4.

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

Title:
  x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1561685] [NEW] x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest

2016-03-24 Thread Jason Gerard DeRose
Public bug reported:

This is an odd one. 1.18.2-2ubuntu0.1 (on the host) breaks the arrow
keys on qemu guests.

Actually, I'm not sure it breaks the arrow keys on the guest in all
scenarios, but it at least breaks them in the pre-boot menu when trying
to install a qemu VM from an ISO.

For example, if I try to install a qemu VM from ubuntu-14.04.4-desktop-
amd64.iso (in BIOS-mode):

1) I hit shift to get to the menu, hit enter to choose English (both of
which work)

2) Nothing happens when I hit the down arrow key to try and select
"Install Ubuntu"

3) I hit F4 (which works) to open the Mode selector, but then nothing
happens when I hit the down arrow to try and select "OEM install (for
manufactures)"

After I downgraded xserver-common, xserver-xorg-core to the
1.18.1-1ubuntu4 packages in Xenial proper, everything works fine again
(which is how I narrowed this bug down to xorg-server).

I also didn't have this problem when using 1.18.2-1ubuntu0.3 from the
x-staging PPA (which I had been using for several weeks), so it seems
that 1.18.2-2ubuntu0.1 introduced this regression.

Note that this issues seems to break all the arrow keys, not just the
down arrow key. If I hit shift to get to the menu, none of the arrow
keys do anything if I try to select a different language. Or if hit
enter to choose English and then hit F3 to open the Keymap selector,
none of the arrow keys work for selecting a different Keymap.

As far as the guest goes, I've tried the desktop amd64 ISO for 14.04.4,
15.10, and the latest Xenial daily, all in both BIOS-mode and UEFI-mode.
In all six scenarios, the arrow keys don't work. Same problem with the
server amd64 ISOs (although I only tried BIOS-mode in this case).

Normally I use '-vga qxl', but I also tried '-vga std' on a whim, and
the result is the same: the arrow keys don't work.

One final note is that the arrow keys work fine when used with any other
application on the host. qemu is the only place I've found any issues.

Oh, and in case it's relevant, I have an NVIDIA 970m GPU and am using
the nvidia-361 proprietary driver. Later today I'll test this with
Nouveau, and will also try this on an Intel GPU system. But as this
seems related to keyboard input rather than the GPU driver, my hunch is
the result will be the same.

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

** Description changed:

  This is an odd one. 1.18.2-2ubuntu0.1 (on the host) breaks the arrow
  keys on qemu guests.
  
  Actually, I'm not sure it breaks the arrow keys on the guest in all
  scenarios, but it at least breaks them in the pre-boot menu when trying
  to install a qemu VM from an ISO.
  
  For example, if I try to install a qemu VM from ubuntu-14.04.4-desktop-
  amd64.iso (in BIOS-mode):
  
  1) I hit shift to get to the menu, hit enter to choose English (both of
  which work)
  
  2) Nothing happens when I hit the down arrow key to try and select
  "Install Ubuntu"
  
  3) I hit F4 (which works) to open the Mode selector, but then nothing
  happens when I hit the down arrow to try and select "OEM install (for
  manufactures)"
  
  After I downgraded xserver-common, xserver-xorg-core to the
  1.18.1-1ubuntu4 packages in Xenial proper, everything works fine again
  (which is how I narrowed this bug down to xorg-server).
  
  I also didn't have this problem when using 1.18.2-1ubuntu0.3 from the
  x-staging PPA (which I had been using for several weeks), so it seems
  that 1.18.2-2ubuntu0.1 introduced this regression.
  
  Note that this issues seems to break all the arrow keys, not just the
  down arrow key. If I hit shift to get to the menu, none of the arrow
  keys do anything if I try to select a different language. Or if hit
  enter to choose English and then hit F3 to open the Keymap selector,
  none of the arrow keys work for selecting a different Keymap.
  
  As far as the guest goes, I've tried the desktop amd64 ISO for 14.04.4,
  15.10, and the latest Xenial daily, all in both BIOS-mode and UEFI-mode.
  In all six scenarios, the arrow keys don't work. Same problem with the
  server amd64 ISOs (although I only tried BIOS-mode in this case).
  
  Normally I use '-vga qxl', but I also tried '-vga std' on a whim, and
  the result is the same: the arrow keys don't work.
  
- One final note is that the arrow keys work find when used with any other
+ One final note is that the arrow keys work fine when used with any other
  application on the host. qemu is the only place I've found any issues.
  
  Oh, and in case it's relevant, I have an NVIDIA 970m GPU and am using
  the nvidia-361 proprietary driver. Later today I'll test this with
  Nouveau, and will also try this on an Intel GPU system. But as this
  seems related to keyboard input rather than the GPU driver, my hunch is
  the result will be the same.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.

[Ubuntu-x-swat] [Bug 1561623] Re: Xorg crashed with SIGABRT in OsAbort()

2016-03-24 Thread Apport retracing service
*** This bug is a duplicate of bug 1543192 ***
https://bugs.launchpad.net/bugs/1543192

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1543192, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1561623/+attachment/4610067/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1561623/+attachment/4610070/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1561623/+attachment/4610083/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1561623/+attachment/4610085/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1561623/+attachment/4610086/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1561623/+attachment/4610087/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1561623/+attachment/4610088/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1543192
   Xorg crashed with SIGABRT in OsAbort()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1561618] Re: package xkb-data 2.10.1-1ubuntu1 [modified: usr/share/X11/xkb/symbols/gr] failed to install/upgrade: impossible de créer un lien symbolique de secours de « ./usr/shar

2016-03-24 Thread Apport retracing service
** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1561618

Title:
  package xkb-data 2.10.1-1ubuntu1 [modified:
  usr/share/X11/xkb/symbols/gr] failed to install/upgrade: impossible de
  créer un lien symbolique de secours de «
  ./usr/share/X11/xkb/symbols/gr » avant d'installer une nouvelle
  version: Lien croisé de périphéque invalide

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1561618/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1561618] [NEW] package xkb-data 2.10.1-1ubuntu1 [modified: usr/share/X11/xkb/symbols/gr] failed to install/upgrade: impossible de créer un lien symbolique de secours de « ./usr/sh

2016-03-24 Thread Arbiel Perlacremaz
Public bug reported:

My fstab file contains the mounting with the bind option of a /home/…/filename 
on the corresponding xkb/symbols/filename.
I tried a reinstalling of the xkb packets and got the present error message.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: xkb-data 2.10.1-1ubuntu1 [modified: usr/share/X11/xkb/symbols/gr]
ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
Uname: Linux 3.13.0-77-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Thu Mar 24 16:15:07 2016
Dependencies:
 
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DuplicateSignature: package:xkb-data:2.10.1-1ubuntu1 [modified: 
usr/share/X11/xkb/symbols/gr]:impossible de créer un lien symbolique de secours 
de « ./usr/share/X11/xkb/symbols/gr » avant d'installer une nouvelle version: 
Lien croisé de périphéque invalide
ErrorMessage: impossible de créer un lien symbolique de secours de « 
./usr/share/X11/xkb/symbols/gr » avant d'installer une nouvelle version: Lien 
croisé de périphéque invalide
InstallationDate: Installed on 2014-05-30 (663 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Dell Inc. Vostro 3550
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-77-generic 
root=/dev/mapper/victor-root ro quiet splash nomdmonddf nomdmonisw
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.5
 apt  1.0.1ubuntu2.11
SourcePackage: xkeyboard-config
Title: package xkb-data 2.10.1-1ubuntu1 [modified: 
usr/share/X11/xkb/symbols/gr] failed to install/upgrade: impossible de créer un 
lien symbolique de secours de « ./usr/share/X11/xkb/symbols/gr » avant 
d'installer une nouvelle version: Lien croisé de périphéque invalide
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/18/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd02/18/2014:svnDellInc.:pnVostro3550:pvrNotSpecified:rvnDellInc.:rn:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Vostro 3550
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Mar 24 17:11:02 2016
xserver.configfile: default
xserver.errors:
 RADEON(G0): [XvMC] Failed to initialize extension.
 Error loading keymap 
/var/lib/xkb/server-17ADDC480211589580CCE86EE8D14EA1392425A2.xkm
 Error loading keymap 
/var/lib/xkb/server-59AA3993CA9ABEC7ED9221D97990DF3246549A14.xkm
 Error loading keymap 
/var/lib/xkb/server-17ADDC480211589580CCE86EE8D14EA1392425A2.xkm
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5539 
 vendor CMO
xserver.version: 2:1.15.1-0ubuntu2.7

** Affects: xkeyboard-config (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty ubuntu

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1561618

Title:
  package xkb-data 2.10.1-1ubuntu1 [modified:
  usr/share/X11/xkb/symbols/gr] failed to install/upgrade: impossible de
  créer un lien symbolique de secours de «
  ./usr/share/X11/xkb/symbols/gr » avant d'installer une nouvelle
  version: Lien croisé de périphéque invalide

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1561618/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


Re: [Ubuntu-x-swat] [Bug 1541082] Re: blotchy GUI graphics for images in 16.04 PPC

2016-03-24 Thread Fritz Hudnut
@Martin:

As I mentioned on the other bug report, the new xserver-xorg-video-ati has
not eliminated the issue of blotchy low spec background images, in my PM
3,1 the blotchiness of pictures continues; even though words and icons are
very crisp and clear, the backgrounds are not.

F

On Sun, Mar 20, 2016 at 5:03 PM, Martin Wimpress <1541...@bugs.launchpad.net
> wrote:

> ** Also affects: xserver-xorg-video-ati (Ubuntu)
>Importance: Undecided
>Status: New
>
> ** No longer affects: ubuntu-mate
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1541082
>
>

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1541082

Title:
  blotchy GUI graphics for images in 16.04 PPC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1541082/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1561548] [NEW] Xorg crashed with SIGABRT

2016-03-24 Thread Coya DeBrojara
*** This bug is a duplicate of bug 1550031 ***
https://bugs.launchpad.net/bugs/1550031

Public bug reported:

Duplicate bug #1550031

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.18.1-1ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Thu Mar 24 14:46:58 2016
ExecutablePath: /usr/lib/xorg/Xorg
InstallationDate: Installed on 2016-03-19 (4 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160216)
ProcCmdline: /usr/lib/xorg/Xorg -core :1 -seat seat0 -auth 
/var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
ProcEnviron:
 
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
 ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
 ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
 ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
 ?? ()
Title: Xorg crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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


** Tags: amd64 apport-crash need-amd64-retrace xenial

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1550031
   Xorg crashed with SIGABRT

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

Title:
  Xorg crashed with SIGABRT

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1316873] Re: Left mouse button stops working

2016-03-24 Thread Eric Broneer
I recently switched from an HDD to an SSD. I installed a fresh Ubuntu
14.04.4 on the SSD. Everything works just fine, except the left button
randomly stops working *only in the work space*. It responds in opened
applications, just not on the top bar or the left application launch
bar. Right click and scroll work fine.

Silly but useful workaround without having to exit fully from the
session : [Ctl][Alt][L] and retype your password.

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

Title:
  Left mouse button stops working

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1561454] Re: Xenial Beta 2: Installation icon is very small

2016-03-24 Thread Skyman
The icon can be seen in the upper left corner.

** Attachment added: "Xenial-desktop-unreadable-icon.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1561454/+attachment/4609617/+files/Xenial-desktop-unreadable-icon.jpg

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

Title:
  Xenial Beta 2: Installation icon is very small

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1561454] [NEW] Xenial Beta 2: Installation icon is very small

2016-03-24 Thread Skyman
Public bug reported:

The installation icon on the desktop is very small and one is not able to 
identify what is intended for.
Resolution: 1024x768

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CasperVersion: 1.368
CurrentDesktop: KDE
Date: Thu Mar 24 10:31:29 2016
LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu xenial

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

Title:
  Xenial Beta 2: Installation icon is very small

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1561452] [NEW] Cannot activate third display

2016-03-24 Thread Aki Tuomi
Public bug reported:

When trying to extend desktop to third display, following error is
given. It can be configured as mirror of DP-1-2 but not as extended
display.

# xrandr --verbose --output eDP1 --primary --output DP-1-2 --right-of eDP1 
--output DP-1-4 --right-of DP-1-2 --mode 1920x1080
screen 0: 5760x1080 1525x286 mm  95.92dpi
crtc 0:1920x1080  60.05 +0+0 "eDP1"
crtc 4:1920x1080  60.00 +1920+0 "DP-1-2"
crtc 5:1920x1080  60.00 +3840+0 "DP-1-4"
xrandr: Configure crtc 5 failed
crtc 0: disable
crtc 1: disable
crtc 2: disable
crtc 3: disable
crtc 4: disable
crtc 5: disable
crtc 6: disable
crtc 7: disable
screen 0: revert
crtc 0: revert
crtc 1: revert
crtc 2: revert
crtc 3: revert
crtc 4: revert
crtc 5: revert
crtc 6: revert
crtc 7: revert

Steps to reproduce:
1. Take one Dell Precision M4800 laptop
2. Attach two external displays with DP
3. Install ubuntu 16.04 
4. displays are not extended to third display

Expected behaviour:
In 14.04 and 15.10 display was automatically activated and extended. This is 
what I hoped.

Actual behaviour:
Display stays blank and cannot be activated even with xrandr.

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Output of ubuntu-bug"
   
https://bugs.launchpad.net/bugs/1561452/+attachment/4609607/+files/ubuntu-bug.txt

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1561452

Title:
  Cannot activate third display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1561452/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1554004]

2016-03-24 Thread Dariusz Gadomski
(In reply to Kevin Brace from comment #17)
Hi Kevin

> I am a little getting lost.
> Are you saying that the current master branch OpenChrome code produces a
> blank screen after OS boots?

That's true.

> One known configuration that causes this is if you use DVI to VGA adapter.
> Another configuration is if you use VX900 chipset (or possibly CX700, VX700,
> VX800, or VX855 chipset) where VGA is not available, device is detected via
> weird known device table, and LCD enable option is not listed in the weird
> known device table.
> If you can clarify your particular system configuration, that will be
> appreciated.

The device has a DVI *and* VGA output and while using DVI output
(without adapter of any kind) we're getting a blank output. VGA output
to VGA display works fine - this is what we use currently as a work-
around.

This is another issue however and is probably related to the topic you
mentioned above and is not related to this bug.

> I do understand that Canonical people do not want to tinker with the code,
> and "think" that the current code is stable.
> It is not.
> Between Version 0.2.904 (used by Ubuntu 10.04 LTS and 12.04 LTS) and Version
> 0.3.3, the previous developer broke VGA detection code if DVI to VGA adapter
> is used.
> This is a fatal regression.
> One of the reason why I am holding up Version 0.3.4 release is due to this.

I fully agree with you and I also want to see this fixed and present in
Ubuntu. Unfortunately the rules (btw. those are Ubuntu rules rather than
Canonical) are very strict and I don't think they can be bypassed in any
way other that those described at the wiki pages (SRU and MRE).

However, I would still like to provide any help necessary in making sure
the new releases will be included in upcoming Ubuntu releases. Would you
mind if we continue the discussion on the openchrome-devel mailing list?

Thank you,
Dariusz

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in Ubuntu.
https://bugs.launchpad.net/bugs/1554004

Title:
  Segfault on X startup with VX900

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1096046] Re: Touchpad not working after last apt-get upgrade

2016-03-24 Thread Christopher M. Penalver
anubhav agrawal, it will help immensely if you filed a new report with Ubuntu 
by ensuring you have the package xdiagnose installed, and that you click the 
Yes button for attaching additional debugging information running the following 
from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1096046

Title:
  Touchpad not working after last apt-get upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1096046/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1388612] Re: [GM965] GPU lockup running OpenGL applications on Dell Vostro 1510

2016-03-24 Thread Christopher M. Penalver
Andrea Bini, to see if this is already resolved, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

** Tags added: wily

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1388612

Title:
  [GM965] GPU lockup running OpenGL applications on Dell Vostro 1510

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1554004] Re: Segfault on X startup with VX900

2016-03-24 Thread Bartosz Kosiorek
After apply the patch it is working perfectly for wily and trusty.
Thanks.

** Tags removed: verification-done-trusty verification-needed-wily
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in Ubuntu.
https://bugs.launchpad.net/bugs/1554004

Title:
  Segfault on X startup with VX900

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp