date:20130417

[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [gm45] Mouse moves erratically after executing xrandr --panning

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/508752/+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 772856] Re: [ironlake] GPU locks up on Intel DH55HC system with IGP when playing Minecraft for a while

[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [ironlake] GPU locks up on Intel DH55HC system with IGP when playing
  Minecraft for a while

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/772856/+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 1092269] Re: Ubuntu 12.04 hangs once, twice a day.

[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Ubuntu 12.04 hangs once, twice a day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1092269/+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 1167301] Re: Mirroring display works only with 1024x768 (4:3) resolution whereas my laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9)

2013-04-17 Thread Gizmo Chicken

Regarding Ubuntu 13.04:  I have a similar problem with an AMD Radeon HD
6670 card connected to two monitors. One monitor (connected via DVI) has
resolution 1440x900 (16:10) and the other monitor (connected via HDMI)
has resolution 1360x768 (16:9).

In my case, when using the "mirror displays" option with the above
described hardware setup, the highest resolution available is 1024x768
(4:3).

I'll just add that:

-  In an earlier daily release of Ubuntu 13.04 (back in late December of
2012, if I recall correctly), the highest resolution available was
1360x768 (16:9) when using the "mirror displays" option on the same
hardware setup as described above.  So something related to this problem
in 13.04 seems to have changed in late December of 2012.

-  Up until very recently,  Ubuntu 12.10 also offered a resolution of
1360x768 (16:9) when using the "mirror displays" option on the same
hardware setup as described above.  But in a very recent update of
(sometime in April of 2013), 12.10 also now only offers a resolution of
1024x768 (4:3) when using the "mirror displays" option on the same
hardware setup. So something related to this problem in 12.10 seems to
have changed in early April of 2013.

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

Title:
  Mirroring display works only with 1024x768 (4:3) resolution whereas my
  laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1167301/+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 1169325] Re: Latest linux-headers-3.8.0-18 with Nvidia causes freeze on boot

2013-04-17 Thread GonzO

Addendum: this fix works with *all* nVidia drivers in the repositories,
it is not specific to 310.  I've tried it with all of them -- 304, 310,
313 and their -updates counterparts.

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

Title:
  Latest linux-headers-3.8.0-18 with Nvidia causes freeze on boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1169325/+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 1169325] Re: Latest linux-headers-3.8.0-18 with Nvidia causes freeze on boot

2013-04-17 Thread GonzO

It's *Plymouth*, of all things.

Workaround: Your normal grub boot line parameters are "quiet splash
$vt_handoff".  If your boot parameters are "vga=normal nofb nomodeset",
this kernel boots and works 100%.  I know this because I'm writing this
on Raring, with that kernel, and those parameters, whereas I was
freezing before.

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

Title:
  Latest linux-headers-3.8.0-18 with Nvidia causes freeze on boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1169325/+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 904476] Re: HDMI wired to Nvidia does not work in a Nvidia Optimus Enabled Laptop

2013-04-17 Thread Tim

Hi all,

Similar problem here for me with my Asus N56VZ.

Hardware:
- Intel 3rd Gen (Ivy Bridge) integrated graphics chipset
- nVidia Geforce GT650M (Optimus).

Ubuntu 12.10
Linux kernel 3.7.0-7-generic
nvidia-319.12
bumblebee 3.1-1~quantalppa1
(xorg-edgers)
xserver-xorg 1:7.7+1ubuntu4

For me, xrandr -q doesn't list the HDMI port, even when plugged in:

Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 32767 x 32767
LVDS1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm 
x 194mm
   1920x1080  60.0*+   59.9  
   1680x1050  60.0 59.9  
   1600x1024  60.2  
   1400x1050  60.0  
   1280x1024  60.0  
   1440x900   59.9  
   1280x960   60.0  
   1360x768   59.8 60.0  
   1152x864   60.0  
   1024x768   60.0  
   800x60060.3 56.2  
   640x48059.9  
VGA1 disconnected (normal left inverted right x axis y axis)


My VGA port does work though.

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

Title:
  HDMI wired to Nvidia does not work in a Nvidia Optimus Enabled Laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/904476/+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 1170054] Re: [NV34] [PPC] KMS no outputs detected - blankscreen

2013-04-17 Thread Str8bs

** Description changed:

  [Problem]
  Machine boots to blank screen. Xorg.0.log shows "no devices detected" and "no 
screens found"
  
  [Steps to reproduce]
  Boot Raring daily live ISO or install from alternate and reboot.
  
  [Workarounds]
  None Found
  Failed attempts:
  remove "quiet splash" from yaboot kernel appends
  kernel boot parameters tried separately = video=offb:off, video=ofonly, 
nomodeset
  create minimal xorg.conf per nouveau wiki and repeat kernel boot parameters
  create minimal xorg.conf using FBDEV and repeat kernel boot parameters
+ increase sleep to 10 before exec lightdm in /etc/init/lightdm.conf
  
  [System Environment]
  lspci-nnvv attached
  GNU/Linux 3.8.0-7-powerpc64-smp ppc64
  PowerPC G5 1.6Ghz Nvidia FX5200 Ultra
  diplay connected via DVI port to VGA adapter
  processor : 0
  cpu   : PPC970, altivec supported
  clock : 1600.00MHz
  revision  : 2.2 (pvr 0039 0202)
  
  timebase  : 
  platform  : PowerMac
  model : PowerMac7,2
  machine   : PowerMac7,2
  motherboard   : PowerMac7,2 MacRISC4 Power Macintosh
  detected as   : 336 (PowerMac G5)
  pmac flags: 
  L2 cache  : 512K unified
  pmac-generation   : NewWorld
  
  [SEPARATE Issue] noted for clarity - may complicate problem on this hardware
  This hardware has known "phantom / ghost" port issue on TV-1. Prior to 12.10, 
all that was needed to boot with nouveau KMS was video=TV-1:d. I mention as 
others with the same hardware, but connected via the "Apple Display Connector" 
port may report ability to fall back to FBDEV booting with nomodeset. That has 
never been the case for my hardware due to the "phantom port."  Link is 
clarification of this SEPARATE issue. 
https://bugs.freedesktop.org/show_bug.cgi?id=39866
  
  Forthcoming logs all booted with kernel appends video=TV-1:d
  drm.debug=0x4 plymouth:debug . "quiet splash" have been removed from
  yaboot kernel appends.
  
  Thank you.

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

Title:
  [NV34] [PPC] KMS no outputs detected - blankscreen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1170054/+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 1169004] Re: friendly-recovery: failsafeX dialog is completely unusable

2013-04-17 Thread Greg Ward

> I've recently installed 13.04 on my laptop, so I'll try it there next.

Good: failsafe-x is no longer completely broken in 13.04. It can now be
controlled with the mouse and keyboard. Hooray!

It still has several bugs, though, which I'll report separately.

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

Title:
  friendly-recovery: failsafeX dialog is completely unusable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1169004/+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 1170174] [NEW] Freeze when starting up - screen won't turn on, fan runs.

2013-04-17 Thread NoBugs!

Public bug reported:

After updating 13.04 today, shutting down, starting up, screen would not
light up. Pressed power a couple times, restarted, and after waiting
awhile the fan started going loudly. Plugging in and re-starting again
made it work.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
Uname: Linux 3.8.0-17-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,regex,workarounds,gnomecompat,scale,put,move,resize,grid,mousepoll,imgpng,place,session,expo,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Apr 17 18:09:53 2013
DistUpgraded: 2013-03-23 09:12:22,824 DEBUG enabling apt cron job
DistroCodename: raring
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: This is the first time
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Device [106b:00a1]
   Subsystem: Apple Inc. Device [106b:00a1]
InstallationDate: Installed on 2012-03-07 (406 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
MachineType: Apple Inc. MacBook4,1
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic 
root=UUID=d7cc0fdf-615d-40c5-9ed5-f42b9add ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to raring on 2013-03-23 (25 days ago)
dmi.bios.date: 02/09/08
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MB41.88Z.00C1.B00.0802091535
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F22788A9
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 2
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F22788A9
dmi.modalias: 
dmi:bvnAppleInc.:bvrMB41.88Z.00C1.B00.0802091535:bd02/09/08:svnAppleInc.:pnMacBook4,1:pvr1.0:rvnAppleInc.:rnMac-F22788A9:rvrPVT:cvnAppleInc.:ct2:cvrMac-F22788A9:
dmi.product.name: MacBook4,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.9~daily13.04.15-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.43-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1
xserver.bootTime: Wed Apr 17 17:54:43 2013
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.13.3-0ubuntu5
xserver.video_driver: intel

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


** Tags: amd64 apport-bug compiz-0.9 freeze raring ubuntu

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

Title:
  Freeze when starting up - screen won't turn on, fan runs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1170174/+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 1068920] Re: Pointer screen crossings broken in Xorg server 1.13.0 (regression)

2013-04-17 Thread deschmit

Any one know if this will be fixed in ubuntu 13.04?

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

Title:
  Pointer screen crossings broken in Xorg server 1.13.0 (regression)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1068920/+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 1130827] Re: SIGABRT - cannot run in framebuffer mode [cirrus]

*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889

** This bug has been marked a duplicate of bug 982889
   X trying to start before plymouth has finished using the drm driver

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

Title:
  SIGABRT - cannot run in framebuffer mode [cirrus]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1130827/+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 1132075] Re: [hybrid] Xorg crashed with SIGABRT in sna_memcpy_plane / nvc0_xv_csc_update

** Changed in: xorg-server (Ubuntu)
   Importance: Medium => Low

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

Title:
  [hybrid] Xorg crashed with SIGABRT in sna_memcpy_plane /
  nvc0_xv_csc_update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1132075/+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 1130954] Re: [hybrid] Xorg crashed with SIGABRT in __libc_message()

** Description changed:

  $ lsb_release -rd
  Description:  Ubuntu Raring Ringtail (development branch)
  Release:  13.04
  
+ the following issue happened while running the image test in the System
+ Testing application
  
- the following issue happened while running the image test in the System 
Testing application
+ #3  0x7f569012da46 in malloc_printerr (ptr=0x7f56921916b8, 
str=0x7f5690230825 "free(): invalid pointer", action=3) at malloc.c:4902
+ buf = "7f56921916b8"
+ #4  _int_free (av=, p=0x7f56921916a8, have_lock=0) at 
malloc.c:3758
+ __func__ = "_int_free"
+ #5  0x7f56924b2538 in RegionUninit (_pReg=) at 
../../../include/regionstr.h:162
+ #6  RegionEmpty (_pReg=0x7f56934b8fc0) at ../../../include/regionstr.h:190
+ #7  DamageEmpty (pDamage=0x7f56934b8fb0) at 
../../../miext/damage/damage.c:1904
+ #8  0x7f568ec87a0b in sna_pixmap_move_to_cpu (flags=2, 
pixmap=0x7f5693323740) at ../../../src/sna/sna.h:464
+ #9  sna_accel_post_damage (sna=0x7f5692191010) at 
../../../src/sna/sna_accel.c:13886
+ region = {extents = {x1 = 1366, y1 = 0, x2 = 1366, y2 = 0}, data = 
0x7f56927ac2a0 }
+ dst = 0x7f56934ad7f0
+ src = 0x7f5693323740
+ n = -1826786592
+ screen = 0x7f56931fe910
+ dirty = 0x7f56931d72e0
+ flush = 
+ #10 sna_accel_flush (sna=0x7f5692191010) at ../../../src/sna/sna_accel.c:13976
+ priv = 0x7f56931d72e0
+ busy = 6
+ 
  
  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-core 2:1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-7.14-generic 3.8.0
  Uname: Linux 3.8.0-7-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.8-0ubuntu4
  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
  Date: Wed Feb 20 13:14:23 2013
  DistUpgraded: 2013-02-18 07:52:05,459 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Device [1043:1c12]
-  Advanced Micro Devices [AMD] nee ATI Manhattan [Mobility Radeon HD 5400 
Series] [1002:68e0] (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Device [1043:1c12]
+  Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Device [1043:1c12]
+  Advanced Micro Devices [AMD] nee ATI Manhattan [Mobility Radeon HD 5400 
Series] [1002:68e0] (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Device [1043:1c12]
  InstallationDate: Installed on 2012-12-08 (74 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: ASUSTeK Computer Inc. B43J
  MarkForUpload: True
  ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch -background none
  ProcEnviron:
-  
+ 
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-7-generic 
root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
-  raise () from /lib/x86_64-linux-gnu/libc.so.6
-  abort () from /lib/x86_64-linux-gnu/libc.so.6
-  ?? () from /lib/x86_64-linux-gnu/libc.so.6
-  ?? () from /lib/x86_64-linux-gnu/libc.so.6
-  DamageEmpty ()
+  raise () from /lib/x86_64-linux-gnu/libc.so.6
+  abort () from /lib/x86_64-linux-gnu/libc.so.6
+  ?? () from /lib/x86_64-linux-gnu/libc.so.6
+  ?? () from /lib/x86_64-linux-gnu/libc.so.6
+  DamageEmpty ()
  Title: Xorg crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to raring on 2013-02-18 (2 days ago)
  UserGroups:
-  
+ 
  dmi.bios.date: 08/06/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: B43J
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr203:bd08/06/2010:svnASUSTeKComputerInc.:pnB43J:pvr1.0:rvnPEGATRONCORPORATION:rnB43J:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.name: B43J
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.9~daily13.02.19-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver

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

** Description changed:

  Error message visible on the display, requesting that I send an error
  report. There were no apparent problems with the functionality of the
  computer at the time.
+ 
+ #8  
+ #9  fbBlt (srcLine=0x7f93dc3527dc, srcStride=, 
srcStride@entry=1522, srcX=195, dstLine=0x7f93d824ff50, 
dstLine@entry=0x7f93d824f000, dstStride=, dstStride@entry=196, 
dstX=-784, dstX@entry=0, width=width@entry=6272, height=9, height@entry=14, 
alu=alu@entry=3, pm=pm@entry=4294967295, bpp=bpp@entry=32, 
reverse=reverse@entry=0, upsidedown=upsidedown@entry=0) at ../../fb/fbblt.c:178
+ startmask = 0
+ endmask = 0
+ nmiddle = 196
+ destInvarient = 1
+ startbyte = 0
+ endbyte = 0
+ _ca1 = 0
+ _cx1 = 0
+ _ca2 = 4294967295
+ _cx2 = 0
+ #10 0x7f93d3c3b560 in fbBltStip (src=, 
srcStride=srcStride@entry=1522, srcX=, 
dst=dst@entry=0x7f93d824f000, dstStride=dstStride@entry=196, dstX=dstX@entry=0, 
width=width@entry=6272, height=14, alu=alu@entry=3, pm=4294967295, bpp=32) at 
../../fb/fbblt.c:785
+ #11 0x7f93d3c412cd in fbGetImage (pDrawable=, x=208, 
y=1027, w=196, h=, format=, planeMask=4294967295, 
d=0x7f93d824f000 "") at ../../fb/fbimage.c:256
+ srcStride = 1522
+ dst = 0x7f93d824f000
+ dstStride = 196
+ #12 0x7f93d3e6007c in ExaCheckGetImage 
(pDrawable=pDrawable@entry=0x7f93daf087d0, x=x@entry=118, y=y@entry=623, 
w=w@entry=196, h=h@entry=14, format=format@entry=2, 
planeMask=planeMask@entry=4294967295, d=d@entry=0x7f93d824f000 "") at 
../../exa/exa_unaccel.c:409
+ pScreen = 0x7f93d971db10
+ pExaScr = 0x7f93d971d650
  
  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-core 2:1.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6
  Uname: Linux 3.8.0-5-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CrashCounter: 1
  CurrentDmesg:
-  
+ 
  Date: Mon Feb 11 14:29:07 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: No
  GraphicsCard:
-  Advanced Micro Devices [AMD] nee ATI Cedar PRO [Radeon HD 5450/6350] 
[1002:68f9] (prog-if 00 [VGA controller])
-Subsystem: XFX Pine Group Inc. Device [1682:3035]
+  Advanced Micro Devices [AMD] nee ATI Cedar PRO [Radeon HD 5450/6350] 
[1002:68f9] (prog-if 00 [VGA controller])
+    Subsystem: XFX Pine Group Inc. Device [1682:3035]
  InstallationDate: Installed on 2013-02-01 (10 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130201)
  MachineType: Dell Inc. Precision WorkStation 470
  MarkForUpload: True
  ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch
  ProcEnviron:
-  
+ 
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-5-generic 
root=UUID=9a9e8a61-35f6-4ed1-8eb7-d18b30128fe2 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
-  fbBlt () from /usr/lib/xorg/modules/libfb.so
-  fbBltStip () from /usr/lib/xorg/modules/libfb.so
-  fbGetImage () from /usr/lib/xorg/modules/libfb.so
-  ?? () from /usr/lib/xorg/modules/libexa.so
-  ?? () from /usr/lib/xorg/modules/libexa.so
+  fbBlt () from /usr/lib/xorg/modules/libfb.so
+  fbBltStip () from /usr/lib/xorg/modules/libfb.so
+  fbGetImage () from /usr/lib/xorg/modules/libfb.so
+  ?? () from /usr/lib/xorg/modules/libexa.so
+  ?? () from /usr/lib/xorg/modules/libexa.so
  Title: Xorg crashed with SIGABRT in fbBlt()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
-  
+ 
  dmi.bios.date: 05/18/2005
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0C9316
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/18/2005:svnDellInc.:pnPrecisionWorkStation470:pvr:rvnDellInc.:rn0C9316:rvr:cvnDellInc.:ct3:cvr:
  dmi.product.name: Precision WorkStation 470
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.0-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu2
  xserver.bootTime: Mon Feb 11 15:56:16 2013
  xserver.configfile: default
  xserver.d

[Ubuntu-x-swat] [Bug 1094097] Re: Xorg crashed with SIGSEGV in mieqMoveToNewScreen()

There haven't been any other reports of a crash like this in raring
since we updated to xserver 1.13.1; I'm wondering if the point release
update may have solved this issue.  Have you seen any further crashes
like this in the last month or so?

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: xorg-server (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  Xorg crashed with SIGSEGV in mieqMoveToNewScreen()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1094097/+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 1094097] Re: Xorg crashed with SIGSEGV in mieqMoveToNewScreen()

** Description changed:

  The Xorg server crashed after automatically monitor switch off(time
  depend). More exactly after reactivating the monitor with a random key
  stroke.
  
  Unfortunally I am not able to reproduce until now.
+ 
+ #14 
+ #15 0x7f9d35b64d24 in mieqMoveToNewScreen (screen=0x7f9d371b7510, 
dev=0x7f9d373e43a0, event=) at ../../mi/mieq.c:490
+ #16 mieqMoveToNewScreen (dev=0x7f9d373e43a0, screen=0x7f9d371b7510, 
event=, event=) at ../../mi/mieq.c:488
+ #17 0x7f9d35b65632 in mieqProcessDeviceEvent 
(dev=dev@entry=0x7f9d373e43a0, event=event@entry=0x7f9d35e09540 , 
screen=screen@entry=0x7f9d371b7510) at ../../mi/mieq.c:526
+ handler = 0x0
+ mevent = {any = {header = 255 '\377', type = ET_RawMotion, length = 
624, time = 9504392}, device_event = {header = 255 '\377', type = ET_RawMotion, 
length = 624, time = 9504392, deviceid = 2, sourceid = 11, detail = {button = 
0, key = 0}, touchid = 0, root_x = 3, root_x_frac = 0, root_y = -8005, 
root_y_frac = 2.81377125, buttons = "\237\257w\325\314\226N\300", '\000' 
, valuators = {mask = "\000\000\000\000", mode = 
"\000\000\000\000", data = {0 , 43, -131, 0, 0, 0, 0, 0}}, 
mods = {base = 0, latched = 0, locked = 0, effective = 0}, group = {base = 0 
'\000', latched = 0 '\000', locked = 0 '\000', effective = 0 '\000'}, root = 0, 
corestate = 0, key_repeat = 0, flags = 0}, changed_event = {header = 255 
'\377', type = ET_RawMotion, length = 624, time = 9504392, deviceid = 2, flags 
= 11, masterid = 0, sourceid = 0, buttons = {num_buttons = 3, names = {0, 
2744574139, 1077155028, 3581390751, 3226375884, 0 , 
1078296576, 0, 3227541504, 0 , 4, 1222, 5734, 48000, 0, 147, 
0, 0, 0, 0, 0, 0, 0, 910, 4974, 95000, 0, 148, 0, 0, 0, 0, 0, 0, 0, 0, 
4294967295, 0, 0, 261, 0, 0, 0, 0, 0, 0, 0, 0, 4294967295, 0}}, num_valuators = 
0, valuators = {{min = 260, max = 0, resolution = 0, mode = 0 '\000', name = 0, 
scroll = {type = SCROLL_TYPE_NONE, increment = 0, flags = 0}}, {min = 0, max = 
0, resolution = 0, mode = 0 '\000', name = 0, scroll = {type = 
SCROLL_TYPE_NONE, increment = 0, flags = 0}} , {min = 0, max 
= 0, resolution = 0, mode = 0 '\000', name = 0, scroll = {type = 
SCROLL_TYPE_NONE, increment = 0, flags = -224198896}}, {min = 1, max = 0, 
resolution = 903922496, mode = 157 '\235', name = 899849099, scroll = {type = 
4070768399, increment = 4.9406564584124654e-324, flags = 0}}, {min = 925659720, 
max = 32669, resolution = 0, mode = 0 '\000', name = 0, scroll = {type = 
SCROLL_TYPE_NONE, increment = 0, flags = 0}}, {min = 0, max = 0, resolution = 
0, mode = 0 '\000', name = 0, scroll = {type = SCROLL_TYPE_NONE, increment = 0, 
flags = 0}}}, keys = {min_keycode = 0, max_keycode = 0}}, touch_ownership_event 
= {header = 255 '\377', type = ET_RawMotion, length = 624, time = 9504392, 
deviceid = 2, sourceid = 11, touchid = 0, reason = 0 '\000', resource = 3, 
flags = 0}, dga_event = {header = 255 '\377', type = ET_RawMotion, length = 
624, time = 9504392, subtype = 2, detail = 11, dx = 0, dy = 0, screen = 3, 
state = 0}, raw_event = {header = 255 '\377', type = ET_RawMotion, length = 
624, time = 9504392, deviceid = 2, sourceid = 11, detail = {button = 0, key = 
0}, valuators = {mask = "\003\000\000\000", data = {20.081369613967336, 
-61.17812603324932, 0 }, data_raw = {43, -131, 0 }}, flags = 0}}
+ #18 0x7f9d35b657b8 in mieqProcessInputEvents () at ../../mi/mieq.c:623
+ screen = 0x7f9d371b7510
+ event = {any = {header = 255 '\377', type = ET_Motion, length = 424, 
time = 9504392}, device_event = {header = 255 '\377', type = ET_Motion, length 
= 424, time = 9504392, deviceid = 11, sourceid = 11, detail = {button = 0, key 
= 0}, touchid = 0, root_x = 56, root_x_frac = 0.842097521, root_y = 171, 
root_y_frac = 0.989590883, buttons = '\000' , valuators = 
{mask = "\003\000\000\000", mode = "\000\000\000\000", data = 
{1409.7536925293261, 1820.111585156938, 0 }}, mods = {base = 
0, latched = 0, locked = 0, effective = 0}, group = {base = 0 '\000', latched = 
0 '\000', locked = 0 '\000', effective = 0 '\000'}, root = 0, corestate = 0, 
key_repeat = 0, flags = 0}, changed_event = {header = 255 '\377', type = 
ET_Motion, length = 424, time = 9504392, deviceid = 11, flags = 11, masterid = 
0, sourceid = 0, buttons = {num_buttons = 56, names = {1062704052, 171, 
1065178580, 0, 0, 0, 0, 0, 0, 0, 0, 3, 0, 0, 0, 3355013832, 1083574019, 
1130438418, 1083994226, 0 }}, num_valuators = 0, valuators = 
{{min = 0, max = 0, resolution = 0, mode = 0 '\000', name = 0, scroll = {type = 
SCROLL_TYPE_NONE, increment = 0, flags = 0}} }, keys = 
{min_keycode = 0, max_keycode = 0}}, touch_ownership_event = {header = 255 
'\377', type = ET_Motion, length = 424, time = 9504392, deviceid = 11, sourceid 
= 11, touchid = 0, reason = 0 '\000', resource = 56, flags = 1062704052}, 
dga_event = {header = 255 '\377', type = ET_Motion, length = 424, time = 
9504392, subtype = 11, detail = 11, dx = 0, dy = 0, screen = 56, state = 
37812}, raw_event =

[Ubuntu-x-swat] [Bug 1156875] Re: Xorg crashed with SIGSEGV in search_linear_cache() using abiword

2013-04-17 Thread federico soffientini

with the last driver I haven't more the bug...now I can use the browser firefox 
and chromium without the crash of the system like in description
thank you so much

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

Title:
  Xorg crashed with SIGSEGV in search_linear_cache() using abiword

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1156875/+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 562005] Re: Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs no longer function while using proprietary drivers

2013-04-17 Thread Martin Spacek

Xubuntu 12.10 updated to nvidia 304.88 a day or so ago, and now
brightness controls are even more uneven than before. I've tried
regenerating xorg.conf using nvidia-settings, and re-adding [Option
"RegistryDwords" "EnableBrightnessControl=1"] to the Device section, but
that hasn't helped. I also tried nvidia 313.30 from xorg-edgers, but
brightness controls seemed to be just as uneven.

3 years and this still hasn't been fixed. I'm waiting hopefully for
nouveau to finally implement proper power management implemented, so I
can ditch this nvidia crap for good. Linus perfectly expressed my
frustration with this company with his simple gesture:

http://www.youtube.com/watch?v=YxHqi8tx048

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

Title:
  Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs
  no longer function while using proprietary drivers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-certification/+bug/562005/+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 1156875] Re: Xorg crashed with SIGSEGV in search_linear_cache() using abiword

Are you able to reproduce this bug using the latest version of the
driver?  (2:2.21.6-0ubuntu3)  It includes a slew of SNA fixes, so would
be worth re-testing to see if the crash can be reproduced.

I didn't spot an obvious fix in the sna code changelog but these things
can tend towards the obscure...

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  Xorg crashed with SIGSEGV in search_linear_cache() using abiword

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1156875/+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 1156875] Re: Xorg crashed with SIGSEGV in search_linear_cache() using abiword

"at ../../../src/sna/kgem.c:3056"

So, looks like an SNA bug in the -intel driver.


** Package changed: xorg-server (Ubuntu) => xserver-xorg-video-intel
(Ubuntu)

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

Title:
  Xorg crashed with SIGSEGV in search_linear_cache() using abiword

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1156875/+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 1121597] Re: Xorg crashed with SIGABRT in DamageRegister()

*** This bug is a duplicate of bug 1155136 ***
https://bugs.launchpad.net/bugs/1155136

** This bug is no longer a duplicate of bug 1123166
   Xorg crashed with SIGABRT in DamageRegister() [sna]
** This bug has been marked a duplicate of bug 1155136
   X Server crashes after pressing [Super] + [P] in  DamageRegister()

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

Title:
  Xorg crashed with SIGABRT in DamageRegister()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1121597/+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 1163425] UnitySupportTest.txt

apport information

** Attachment added: "UnitySupportTest.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646917/+files/UnitySupportTest.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] xserver.outputs.txt

apport information

** Attachment added: "xserver.outputs.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646923/+files/xserver.outputs.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] xdpyinfo.txt

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646921/+files/xdpyinfo.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] XorgLog.txt

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646918/+files/XorgLog.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646913/+files/ProcInterrupts.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] xserver.devices.txt

apport information

** Attachment added: "xserver.devices.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646922/+files/xserver.devices.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646914/+files/ProcModules.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] UdevLog.txt

apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646916/+files/UdevLog.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] Xrandr.txt

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1163425/+attachment/3646920/+files/Xrandr.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] XorgLogOld.txt

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646919/+files/XorgLogOld.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1163425/+attachment/3646915/+files/UdevDb.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646900/+files/CurrentDmesg.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] BootLog.txt

apport information

** Attachment added: "BootLog.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646899/+files/BootLog.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1123166] Re: Xorg crashed with SIGABRT in DamageRegister() [sna]

*** This bug is a duplicate of bug 1155136 ***
https://bugs.launchpad.net/bugs/1155136

** This bug has been marked a duplicate of bug 1155136
   X Server crashes after pressing [Super] + [P] in  DamageRegister()

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

Title:
  Xorg crashed with SIGABRT in DamageRegister() [sna]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1123166/+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 1131021] Re: Xorg crashed with SIGABRT in DamageRegister()

*** This bug is a duplicate of bug 1155136 ***
https://bugs.launchpad.net/bugs/1155136

** This bug is no longer a duplicate of bug 1123166
   Xorg crashed with SIGABRT in DamageRegister() [sna]
** This bug has been marked a duplicate of bug 1155136
   X Server crashes after pressing [Super] + [P] in  DamageRegister()

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

Title:
  Xorg crashed with SIGABRT in DamageRegister()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1131021/+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 1132953] Re: Xorg crashed with SIGABRT in DamageRegister()

*** This bug is a duplicate of bug 1155136 ***
https://bugs.launchpad.net/bugs/1155136

** This bug is no longer a duplicate of bug 1123166
   Xorg crashed with SIGABRT in DamageRegister() [sna]
** This bug has been marked a duplicate of bug 1155136
   X Server crashes after pressing [Super] + [P] in  DamageRegister()

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

Title:
  Xorg crashed with SIGABRT in DamageRegister()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1132953/+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 1155136] Re: X Server crashes after pressing [Super] + [P] in DamageRegister()

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  X Server crashes after pressing [Super] + [P] in  DamageRegister()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1155136/+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 1156612] Re: Xorg crashed with SIGABRT in DamageRegister()

*** This bug is a duplicate of bug 1155136 ***
https://bugs.launchpad.net/bugs/1155136

** This bug is no longer a duplicate of bug 1123166
   Xorg crashed with SIGABRT in DamageRegister() [sna]
** This bug has been marked a duplicate of bug 1155136
   X Server crashes after pressing [Super] + [P] in  DamageRegister()

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

Title:
  Xorg crashed with SIGABRT in DamageRegister()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1156612/+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 1158197] Re: Xorg crashed with SIGABRT in DamageRegister()

*** This bug is a duplicate of bug 1155136 ***
https://bugs.launchpad.net/bugs/1155136

** This bug is no longer a duplicate of bug 1123166
   Xorg crashed with SIGABRT in DamageRegister() [sna]
** This bug has been marked a duplicate of bug 1155136
   X Server crashes after pressing [Super] + [P] in  DamageRegister()

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

Title:
  Xorg crashed with SIGABRT in DamageRegister()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1158197/+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 1160440] Re: Xorg crashed with SIGABRT in DamageRegister()

*** This bug is a duplicate of bug 1155136 ***
https://bugs.launchpad.net/bugs/1155136

** This bug is no longer a duplicate of bug 1123166
   Xorg crashed with SIGABRT in DamageRegister() [sna]
** This bug has been marked a duplicate of bug 1155136
   X Server crashes after pressing [Super] + [P] in  DamageRegister()

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

Title:
  Xorg crashed with SIGABRT in DamageRegister()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1160440/+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 1161663] Re: Xorg crashed with SIGABRT in DamageRegister()

*** This bug is a duplicate of bug 1155136 ***
https://bugs.launchpad.net/bugs/1155136

** This bug is no longer a duplicate of bug 1123166
   Xorg crashed with SIGABRT in DamageRegister() [sna]
** This bug has been marked a duplicate of bug 1155136
   X Server crashes after pressing [Super] + [P] in  DamageRegister()

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

Title:
  Xorg crashed with SIGABRT in DamageRegister()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1161663/+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 1163425] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646912/+files/ProcEnviron.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646911/+files/ProcCpuinfo.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] MonitorsUser.xml.txt

apport information

** Attachment added: "MonitorsUser.xml.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646910/+files/MonitorsUser.xml.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1163425/+attachment/3646909/+files/Lsusb.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1163425/+attachment/3646908/+files/Lspci.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] LightdmLog.txt

apport information

** Attachment added: "LightdmLog.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646907/+files/LightdmLog.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] LightdmGreeterLogOld.txt

apport information

** Attachment added: "LightdmGreeterLogOld.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646906/+files/LightdmGreeterLogOld.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] LightdmGreeterLog.txt

apport information

** Attachment added: "LightdmGreeterLog.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646905/+files/LightdmGreeterLog.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] LightdmDisplayLog.txt

apport information

** Attachment added: "LightdmDisplayLog.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646904/+files/LightdmDisplayLog.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] HookError_cloud_archive.txt

apport information

** Attachment added: "HookError_cloud_archive.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646903/+files/HookError_cloud_archive.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] GconfCompiz.txt

apport information

** Attachment added: "GconfCompiz.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646902/+files/GconfCompiz.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] DpkgLog.txt

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1163425/+attachment/3646901/+files/DpkgLog.txt

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1163425] Re: [hybrid] "Displays" detects a secondary unknown display when there is nothing connected

apport information

** Tags added: apport-collected compiz-0.9 ubuntu

** Description changed:

  The "Display" control panel shows a secondary screen on my laptop when
  there is nothing connected to the HDMI or DisplayPort outputs. An
  screenshot showing the problem is attached.
  
  After "playing" with this screen, TTY doesn't work and the shutdown
  process hangs before entering TTY.
  
  I am using a MUXed hybrid graphics laptop (Intel Ironlake / AMD 5650m)
  and this may be related to other problems I have with this system (bugs
  #1162526 and #1163418).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu18
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Tue Apr  2 13:20:39 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-03-30 (2 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130328)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup26.0-0ubuntu1
   gnome-control-center-signon 0.1.5-0ubuntu1
   gnome-control-center-unity  1.2daily13.04.01-0ubuntu1
   indicator-datetime  12.10.3daily13.03.26-0ubuntu1
+ --- 
+ .tmp.unity.support.test.0:
+  
+ ApportVersion: 2.9.2-0ubuntu8
+ 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
+ DistUpgraded: Fresh install
+ DistroCodename: raring
+ DistroRelease: Ubuntu 13.04
+ DistroVariant: ubuntu
+ DkmsStatus:
+  bcmwl, 6.20.155.1+bdcom, 3.8.0-15-generic, x86_64: installed
+  bcmwl, 6.20.155.1+bdcom, 3.8.0-16-generic, x86_64: installed
+  bcmwl, 6.20.155.1+bdcom, 3.8.0-17-generic, x86_64: installed
+  bcmwl, 6.20.155.1+bdcom, 3.8.0-18-generic, x86_64: installed
+ ExtraDebuggingInterest: Yes, if not too technical
+ GraphicsCard:
+  Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
+Subsystem: Hewlett-Packard Company Device [103c:1436]
+  Advanced Micro Devices [AMD] nee ATI Madison [Mobility Radeon HD 5650/5750 / 
6550M] [1002:68c1] (rev ff) (prog-if ff)
+ InstallationDate: Installed on 2013-03-30 (18 days ago)
+ InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130328)
+ MachineType: Hewlett-Packard HP ENVY 14 Notebook PC
+ MarkForUpload: True
+ NonfreeKernelModules: wl
+ Package: xorg-server (not installed)
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-18-generic 
root=UUID=67db7fed-d0f3-4c33-9a58-eb3860cfc7be ro quiet splash acpi_osi=Linux 
acpi_backlight=legacy vt.handoff=7
+ ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
+ Tags:  raring ubuntu compiz-0.9
+ Uname: Linux 3.8.0-18-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ dmi.bios.date: 12/01/2011
+ dmi.bios.vendor: Hewlett-Packard
+ dmi.bios.version: F.26
+ dmi.board.asset.tag: Base Board Asset Tag
+ dmi.board.name: 1436
+ dmi.board.vendor: Hewlett-Packard
+ dmi.board.version: 59.24
+ dmi.chassis.asset.tag: CNU03538DZ
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Hewlett-Packard
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.26:bd12/01/2011:svnHewlett-Packard:pnHPENVY14NotebookPC:pvr0492102419162:rvnHewlett-Packard:rn1436:rvr59.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
+ dmi.product.name: HP ENVY 14 Notebook PC
+ dmi.product.version: 0492102419162
+ dmi.sys.vendor: Hewlett-Packard
+ version.compiz: compiz 1:0.9.9~daily13.04.15-0ubuntu1
+ version.ia32-libs: ia32-libs N/A
+ version.libdrm2: libdrm2 2.4.43-0ubuntu1
+ version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu2
+ version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
+ version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu2
+ version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu5
+ version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
+ version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
+ version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu3
+ version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
+ xserver.bootTime: Wed Apr 17 20:03:53 2013
+ xserver.configfile: default
+ xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
+ xserver.logfile: /var/log/Xorg.0.log
+ xserver.version: 2:1.13.3-0ubuntu5
+ xserver.video_driver: intel

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bu

[Ubuntu-x-swat] [Bug 1167231] Re: Xorg crashed with SIGABRT in OsAbort() - Cannot mirror screen in good resolution

*** This bug is a duplicate of bug 1167301 ***
https://bugs.launchpad.net/bugs/1167301

** This bug has been marked a duplicate of bug 1167301
   Mirroring display works only with 1024x768 (4:3) resolution whereas my 
laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9)

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

Title:
  Xorg crashed with SIGABRT in OsAbort() - Cannot mirror screen in good
  resolution

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1167231/+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 1124296] Re: Xorg crashed with SIGABRT in dl_open trying to load mesa i915 driver module

Hi Charlie,

Did this crash just the once following the upgrade?  Perhaps with mesa
upgraded it was in an inconsistent state, which would be cleared by
rebooting after the upgrade (which is why it's recommended by the
installer).

We've just posted 9.1.1 recently.  When you upgrade this time can you
check if anything similar occurs?


** Summary changed:

- Xorg crashed with SIGABRT in dl_open
+ Xorg crashed with SIGABRT in dl_open  trying to 
load mesa i915 driver module

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Xorg crashed with SIGABRT in dl_open 
  trying to load mesa i915 driver module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1124296/+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 1169004] Re: friendly-recovery: failsafeX dialog is completely unusable

2013-04-17 Thread Greg Ward

Update on 12.10: it's not just keyboard-unusable, it's also mouse-
unusable. I just tried failsafe-x on my desktop system running 12.10,
and it is completely unusable. X works perfectly on this system, my
mouse is hooked up and working fine, everything is good. Details...

Steps to reproduce:
1) logout of X session
2) login on text console as root
3) "service lxdm stop" (or whatever your display manager is)
4) "service failsafe-x start"

Expected behaviour:
* initial dialog (acknowledge failsafe mode) is both keyboard controllable and 
mouse controllable
* second dialog (choose action)  is both keyboard controllable and mouse 
controllable

Actual behaviour:
* initial dialog works just fine
* neither keyboard nor mouse works to control the second dialog

When I move my mouse around, I do see flickering in that second dialog,
like when you mouse over different GUI widgets and the focus highlight
moves around. But the mouse pointer is invisible, and I cannot figure
out a way to click on "OK" or any of the radio buttons. And the keyboard
does nothing.

IOW: I see the exact same behaviour on my desktop and laptop running
12.10. I've recently installed 13.04 on my laptop, so I'll try it there
next.


** Summary changed:

- friendly-recovery: failsafeX dialog is not keyboard controllable
+ friendly-recovery: failsafeX dialog is completely unusable

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

Title:
  friendly-recovery: failsafeX dialog is completely unusable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1169004/+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 1110426] Re: poulsbo GMA3600 crashed X - AddScreen/ScreenInit failed for driver 0

Try blacklisting gma500_gfx.  The X server appears to be properly
ignoring that anyway, but perhaps it's causing some problems.

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => Incomplete

** Summary changed:

- poulsbo GMA3600 crashed X - AddScreen/ScreenInit failed for driver 0
+ [poulsbo] GMA3600 crashed X - AddScreen/ScreenInit failed for driver 0

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

Title:
  [poulsbo] GMA3600 crashed X - AddScreen/ScreenInit failed for driver 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1110426/+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 1167301] Re: Mirroring display works only with 1024x768 (4:3) resolution whereas my laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9)

** Changed in: xorg-server (Ubuntu)
   Status: New => Triaged

** Changed in: xorg-server (Ubuntu)
Milestone: ubuntu-13.04 => None

** Changed in: xorg-server (Ubuntu)
   Importance: High => Wishlist

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

Title:
  Mirroring display works only with 1024x768 (4:3) resolution whereas my
  laptop has 1366x768 (16:9) and the external monitor 1920x1080 (16:9)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1167301/+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 1110426] Re: poulsbo GMA3600 crashed X - AddScreen/ScreenInit failed for driver 0

** Description changed:

  Upgrading from Quantal to Raring.
  Using GMA3600 crap video processor in a XS36x shuffle.
  
  #5  0xb771053e in FatalError (f=f@entry=0xb771ae7c "AddScreen/ScreenInit 
failed for driver %d\n") at ../../os/log.c:793
- args = 0xbfd259c4 ""
- args2 = 0xbfd259c4 ""
- beenhere = 1
+ args = 0xbfd259c4 ""
+ args2 = 0xbfd259c4 ""
+ beenhere = 1
  #6  0xb75dff17 in InitOutput (pScreenInfo=0xb778e280 , 
argc=argc@entry=11, argv=argv@entry=0xbfd25b34) at 
../../../../hw/xfree86/common/xf86Init.c:928
- i = 
- j = 
- k = 
- scr_index = -1
- modulelist = 
- optionlist = 0xb8984160
- screenpix24 = 
- pix24 = 
- pix24From = 
- pix24Fail = 0
- autoconfig = 
- sigio_blocked = 0
- configured_device = 
+ scr_index = -1
+ optionlist = 0xb8984160
+ pix24Fail = 0
+ sigio_blocked = 0
  #7  0xb7585f46 in main (argc=11, argv=0xbfd25b34, envp=0xbfd25b64) at 
../../dix/main.c:204
- i = 
- alwaysCheckForInput = {0, 1}
+ alwaysCheckForInput = {0, 1}
  
  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-core 2:1.13.1.901-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4
  Uname: Linux 3.8.0-2-generic i686
  .tmp.unity.support.test.1:
  
  ApportVersion: 2.8-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Jan 30 11:44:01 2013
  DistUpgraded: 2013-01-30 10:54:44,931 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller 
[8086:0be2] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device [1297:4012]
  MachineType: Shuttle Inc. XS36V
  MarkForUpload: True
  ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch -background none
  ProcEnviron:
  
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-2-generic 
root=UUID=bc32c5ef-32fa-47ec-83d5-050107bbae6e ro quiet splash 
elevator=deadline mem=4G video=LVDS-1:d vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   OsAbort ()
   ?? ()
   FatalError ()
  Title: Xorg crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to raring on 2013-01-30 (0 days ago)
  UserGroups:
  
  dmi.bios.date: 06/19/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: XS36V
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  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.:bvr1.05:bd06/19/2012:svnShuttleInc.:pnXS36V:pvr1.0:rvnShuttleInc.:rnXS36V:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: XS36V
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz 1:0.9.9~daily13.01.25-0ubuntu1
  version.libdrm2: libdrm2 2.4.41-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.1.901-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.19-0ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu1
  xserver.bootTime: Wed Jan 30 11:44:00 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
  
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
  
  xserver.version: 2:1.13.1.901-0ubuntu2

** Description changed:

  Upgrading from Quantal to Raring.
  Using GMA3600 crap video processor in a XS36x shuffle.
+ 
+ [11.012] (**) FBDEV(0): claimed PCI slot 0@0:2:0
+ [11.012] (II) FBDEV(0): using default device
+ [11.012] (**) FBDEV(0): Depth 24, (--) framebuffer bpp 32
+ [11.012] (==) FBDEV(0): RGB weight 888
+ [11.012] (==) FBDEV(0): Default visual is TrueColor
+ [11.012] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
+ [11.012] (II) FBDEV(0): hardware: psbfb (video memory: 4320kB)
+ [11.013] (II) FBDEV(0): checking modes against framebuffer device...
+ [11.013] (EE) FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument
+ [11.013] (II) FBDEV(0):   mode "1280x720_60" test failed
+ [11.013] (II) FBDEV(0):   mode "1

[Ubuntu-x-swat] [Bug 1162896] Re: Black screen when resume from suspend

Not enough information has been provided to make this a useful bug
report.  See http://wiki.ubuntu.com/X/Reporting for instructions on
reporting X issues.

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  Black screen when resume from suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1162896/+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 1163425] Re: [hybrid] "Displays" detects a secondary unknown display when there is nothing connected

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command in a terminal after
reproducing the issue, and it it will automatically gather debugging
information needed for this bug:

  apport-collect 1163425


** Summary changed:

- "Displays" detects a secondary unknown display when there is nothing connected
+ [hybrid] "Displays" detects a secondary unknown display when there is nothing 
connected

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  [hybrid] "Displays" detects a secondary unknown display when there is
  nothing connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163425/+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 1165306] Re: Xorg crashed with SIGABRT in __libc_start_main()

This is probably a dupe of bug #982889.  Try adding sleep to your
lightdm.conf as described in that bug and see if it works around the
issue.

** Description changed:

  Xorg sometimes don't start at boot.
  
- #2  0x7f7ea445f2ae in OsAbort ()
- #3  0x7f7ea4464223 in ?? ()
- #4  0x7f7ea4464a9d in FatalError ()
- #5  0x7f7ea42f07d2 in ?? ()
- #6  0x7f7ea1ff9ea5 in __libc_start_main (main=0x7f7ea42f0110, argc=9, 
ubp_av=0x7fffea6a6a58,
- init=, fini=, rtld_fini=,
- stack_end=0x7fffea6a6a48) at libc-start.c:260
- unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 4991247855042815178, 
140181897152504,
- 140737126230608, 0, 0, -4991204797383056182, 
-4919836772781005622},
-   mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x7f7ea4468370 
<__libc_csu_init>,
-   0x7fffea6a6a58}, data = {prev = 0x0, cleanup = 0x0, canceltype 
= -1538882704}}}
- #7  0x7f7ea42f0821 in _start ()
+ #4  0x7f7ea4464a9d in FatalError (f=f@entry=0x7f7ea4468442 "no screens 
found")
+ at ../../os/log.c:793
+ args = {{gp_offset = 8, fp_offset = 48, overflow_arg_area = 
0x7fffea6a6910, 
+ reg_save_area = 0x7fffea6a6850}}
+ args2 = {{gp_offset = 8, fp_offset = 48, overflow_arg_area = 
0x7fffea6a6910, 
+ reg_save_area = 0x7fffea6a6850}}
+ beenhere = 1
+ #5  0x7f7ea42f07d2 in main (argc=9, argv=0x7fffea6a6a58, envp=)
+ at ../../dix/main.c:207
+ alwaysCheckForInput = {0, 1}
+ 
  
  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-core 2:1.13.3-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  .tmp.unity.support.test.0:
  
  ApportVersion: 2.9.2-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
  CrashCounter: 1
  Date: Fri Apr  5 13:24:41 2013
  DistUpgraded: 2013-03-19 00:10:58,994 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.2.10: added
  ExecutablePath: /usr/bin/Xorg
  GraphicsCard:
   Advanced Micro Devices [AMD] nee ATI Juniper XT [AMD Radeon HD 6000 Series] 
[1002:68ba] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:040b]
  InstallationDate: Installed on 2013-02-07 (57 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch
  ProcEnviron:
  
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-16-generic 
root=UUID=5f72727e-ae34-4862-9f87-af6ca6d14636 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   OsAbort ()
   ?? ()
   FatalError ()
  Title: Xorg crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to raring on 2013-03-18 (18 days ago)
  UserGroups:
  
  dmi.bios.date: 11/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0402:bd11/16/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPROGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.9~daily13.03.29-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.5-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Sat Apr  6 08:21:40 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech Unifying Device. Wireless PID:101b MOUSE, id 8
   inputLogitech Unifying Device. Wireless PI

[Ubuntu-x-swat] [Bug 1169004] Re: friendly-recovery: failsafeX dialog is not keyboard controllable

2013-04-17 Thread Brian Murray

I was unable to recreate this on Raring (13.04) with a Lenovo X201
Tablet.  Either way though this is a bug with the failsafeXServer which
is provided by xdiagnose so I am changing the package appropriately.

** Package changed: friendly-recovery (Ubuntu) => xdiagnose (Ubuntu)

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

Title:
  friendly-recovery: failsafeX dialog is not keyboard controllable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1169004/+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 1169004] [NEW] friendly-recovery: failsafeX dialog is not keyboard controllable

You have been subscribed to a public bug:

1. boot my laptop into recovery mode with no external mouse connected
   (only the laptop's builtin trackpad)
2. from the "Recovery Menu", select "failsafeX"

(This is a Lenovo ThinkPad T500 with Synaptics trackpad -- pretty
vanilla hardware that normally works perfectly with both gpm and
X.org.)

Expected behaviour:
- failsafe dialogs are controllable by keyboard (or by builtin trackpad)

Actual behaviour:
- initial dialog is keyboard controllable (space or enter clicks the
  "OK" button)
- but the second dialog ("What would you like to do?") is completely
  unresponsive: I cannot use tab or arrow keys to select different
  radiobuttons, I cannot use space or enter to click OK, the builtin
  trackpad does not work. There is no way to get into the failsafe X
  session. The only way out is Ctrl-Alt-F2 back to a text console
  followed by manual recovery. It's not quite failsafe!

Workaround: connect a USB mouse. Or reboot with USB mouse connected. I
think. If a USB mouse is connected *and working*, then the trackpad
magically starts working. But the USB mouse isn't always recognized, I
think. Unclear what it takes to make it work.

Anyways, even if the trackpad worked perfectly with or without a mouse
connected, this GUI should still be entirely keyboard controllable.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: friendly-recovery 0.2.25
ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
Uname: Linux 3.5.0-27-generic x86_64
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
Date: Sun Apr 14 21:57:34 2013
InstallationDate: Installed on 2012-09-30 (196 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: friendly-recovery
UpgradeStatus: Upgraded to quantal on 2012-11-22 (143 days ago)

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


** Tags: amd64 apport-bug quantal
-- 
friendly-recovery: failsafeX dialog is not keyboard controllable
https://bugs.launchpad.net/bugs/1169004
You received this bug notification because you are a member of Ubuntu-X, which 
is subscribed to xdiagnose in Ubuntu.

___
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 1157678] Re: [ffe] unplugging an external monitor from laptop results in corrupted screen. Logging out fixes it.

2013-04-17 Thread Bug Watch Updater

** Changed in: xserver-xorg-video-intel
   Status: Incomplete => Fix Released

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

Title:
  [ffe] unplugging an external monitor from laptop results in corrupted
  screen.  Logging out fixes it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1157678/+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 1162046] Re: [gm45] Xv video falls apart and flickers when obstructed by 2 windows

The remaining corner case described in comment#10 is now filled as
#1170117

The attachments related to that corner case were moved to that bug.

** Attachment removed: "video file I could reproduce with"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1162046/+attachment/3641317/+files/testcase.ts

** Attachment removed: "window layout example"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1162046/+attachment/3641318/+files/fbrun-layout.jpg

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

Title:
  [gm45] Xv video falls apart and flickers when obstructed by 2 windows

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1162046/+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 1170117] Re: [gm45] Xv video corruption when obstructed by shaped windows (corner case)

** Attachment added: "window layout example"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1170117/+attachment/3646846/+files/fbrun-layout.jpg

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

Title:
   [gm45] Xv video corruption when obstructed by shaped windows (corner
  case)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1170117/+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 1170117] Re: [gm45] Xv video corruption when obstructed by shaped windows (corner case)

** Attachment added: "video file I could reproduce with"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1170117/+attachment/3646845/+files/testcase.ts

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

Title:
   [gm45] Xv video corruption when obstructed by shaped windows (corner
  case)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1170117/+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 1170117] Re: [gm45] Xv video corruption when obstructed by shaped windows (corner case)

< a copy of https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-
video-intel/+bug/1162046/comments/10 >

The fix arrived with the updates today.
Most of the corruption is gone. Almost all the frames now get though undamaged.
Thanks for the fix.

BUT

Some of the video frames still get damaged when drawn.
However, it does depend on the video content (and possibly on (absolute) window
positions)

I attach a short captured dvb-t video to be played with mplayer2 using Xv output
and a picture with the example fbrun dialogue positions.

Steps:
Fluxbox with a round-cornered theme.
mplayer2 with the testcase.ts file, pause it as soon as it starts
fbrun #1, so it's bottom-left corner perfectly matches with the mplayer2's
bottom-left corner
fbrun #2 somewhere in the video area, preferably far from the fbrun #1
unpause mplayer.

I observed damage between fbrun #2 and the right edge of the Xv video.

Notes:
fbrun's windows don't seem to be resizeable, mplayer opens a window 1:1 to the
input (so, exactly defined again)

It seems to depend a bit on the position of the Xv window on the screen.
It does rarely work when the Xv is close to screen edges
=> preferably position the Xv window somewhat in the middle of the screen.

PS:
Alternatively you can start mplayer with "-fixed-vo -loop 0" as arguments for
mplayer instead of pausing/unpausing
That will give you a continuous loop in the same Xv window.

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

Title:
[gm45] Xv video corruption when obstructed by shaped windows (corner
case)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1170117/+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 1170117] [NEW] [gm45] Xv video corruption when obstructed by shaped windows (corner case)

Public bug reported:

This is a followup to #1162046

The issue is almost fixed, but the corruption wasn't eradicated completely.
This time the actual video content matters (guess: partial frame updates?)

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

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

Title:
   [gm45] Xv video corruption when obstructed by shaped windows (corner
  case)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1170117/+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 1134492] Re: xserver-xorg-lts-quantal breaks Kubuntu

2013-04-17 Thread David Kalnischkies

General:
Limiting a solution to Conflicts would be bad, that should work with Breaks 
too, as Conflicts should be avoided like the plague (if we can). And just doing 
it on Conflicts (or Breaks) does make it apply to a lot of cases there we don't 
want it to happen (think: libfoogtk2-0 conflicts/breaks with libfoogtk3-0) so 
we need some more heuristic here than just this (aspcud is just based on 
numbers, so it works here, but fails then the solution is not just a numbers 
game).

I can only really comment on that with an example though (a dpkg/status
file and sources.list might be enough until a test surfaces. Setting up
a system to test just this isn't exactly easy …). Frankly, I don't see
why this is considered "high" though: switching X-stacks doesn't sound
like an everyday task, so I guess everyone could live with a slightly
longer commandline to type (aka: copy&paste) and a "low" or similar…


Quick-Review (just looking at diff, no applied or anything)
1. A user can easily have more architectures configured than just two, so 
comparing architectures is dangerous.
2. Not all of these architectures are a good choice (think: armel on armhf or 
armhf on a amd64 crossbuilder).
3. Please do a patch against trunk. We can always try to backport it later.
4. MarkInstall (and for that matter MarkDelete) can fail and you should do 
something sensible if they do, not just ignore it
5. Do we really want to do something even if the removed package is M-A:foreign 
?

Serious nitpick: Don't name a variable iPkg if you use Pkg in the same
context, while its definition is far away. It's very easy to miss (which
I did initially and wondered why you renamed Pkg to iPkg and wanted to
nitpick about unneeded renames first…)

Lesser nitpick: Instead of Z, use P as an iterator. If you are used to
APT code you know immediately which iterators are G, P, V, D, … no such
hint for Z (okay, at times P stands for Provides, but every rule has an
exception – and usually its Prv instead).

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

Title:
  xserver-xorg-lts-quantal breaks Kubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1134492/+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 1161102] Re: 1002:5a62 Gdk-WARNING: gnome-session: Fatal IO error 11 (Hulpbron is tijdelijk onbeschikbaar) on X server :0.#012

All those errors are just symptoms.  The real issue seems to be that
your GPU locked up, as shown in your Xorg.0.log.  Unfortunately, the
logs are scant on details as to why that happened...

** Description changed:

  This time it when browsing quickly through some pictures using eye of
  gnome picture viewer. But it happens regularly on several occasions also
  when using flash or HTLM5 streams. The Session crashes either by
  freezing compiz/unity or even a complete logout. So filing a bug report
  immediately is problematic.
+ 
+ [81.659] (II) RADEON(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 
1344  768 771 777 806 -hsync -vsync (48.4 kHz)
+ [  2382.895] [mi] EQ overflowing.  Additional events will be discarded until 
existing events are processed.
+ [  2382.916] 
+ Backtrace:
+ [  2383.080] 
+ Backtrace:
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-33.52-generic-pae 3.2.31
  Uname: Linux 3.2.0-33-generic-pae i686
  .tmp.unity.support.test.0:
  
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: i386
  CheckboxSubmission: 7570a87475d07d1f6be2b328fd182199
  CheckboxSystem: b1865df84255b8716d3bcc269ff410d1
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  Date: Wed Mar 27 21:38:04 2013
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
   ndiswrapper, 1.57, 3.2.0-32-generic-pae, i686: installed
   ndiswrapper, 1.57, 3.2.0-33-generic-pae, i686: installed
   virtualbox, 4.1.12, 3.2.0-32-generic-pae, i686: installed
   virtualbox, 4.1.12, 3.2.0-33-generic-pae, i686: installed
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Advanced Micro Devices [AMD] nee ATI RC410 [Radeon Xpress 200M] [1002:5a62] 
(prog-if 00 [VGA controller])
     Subsystem: Toshiba America Info Systems Device [1179:ff31]
  InstallationMedia: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 
20120427-09:21
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
  MachineType: TOSHIBA Satellite L20
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-33-generic-pae 
root=UUID=11480fdb-c8a6-4240-9173-d48a05f9c00d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/08
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V2.50
  dmi.board.name: Satellite L20
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV2.50:bd12/25/08:svnTOSHIBA:pnSatelliteL20:pvrPSL2XE-01400WDU:rvnTOSHIBA:rnSatelliteL20:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite L20
  dmi.product.version: PSL2XE-01400WDU
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.7.12-0ubuntu1
  version.libdrm2: libdrm2 2.4.39-0ubuntu0.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.12
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

** Package changed: xorg-server (Ubuntu) => xserver-xorg-video-ati
(Ubuntu)

** Changed in: xserver-xorg-video-ati (Ubuntu)
   Importance: Undecided => High

** Summary changed:

- 1002:5a62 Gdk-WARNING: gnome-session: Fatal IO error 11 (Hulpbron is 
tijdelijk onbeschikbaar) on X server :0.#012
+ GPU lockup on radeon while browsing through pictures in eye of gnome

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

Title:
  GPU lockup on radeon while browsing through pictures in eye of gnome

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1161102/+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 1170074] Re: mesa 9.1 regressed Tibia on nouveau

Maarten, see if you can get this issue sorted.

** Changed in: mesa (Ubuntu)
   Status: New => Triaged

** Changed in: mesa (Ubuntu)
 Assignee: Canonical X.org (canonical-x) => Maarten Lankhorst (mlankhorst)

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

Title:
  mesa 9.1 regressed Tibia on nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1170074/+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 1170074] Re: mesa 9.1 regressed Tibia on nouveau

and tmp in this case seems to be an x86 op code (linear_func), which
seems to come from the nouveau code for the nv50.  So this is likely a
very hardware-specific issue.

There's a few nv50 patches in the 9.1.x tree that aren't included in our
mesa, but probably unrelated to this issue.  Might be worth testing.
*shrug*

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

Title:
  mesa 9.1 regressed Tibia on nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1170074/+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 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor

2013-04-17 Thread Krastanov

The packages can not be tested on 13.04 because of:

xserver-xorg-core:
 Depends: libaudit1 (>=1:2.2.1) but it is not installable
  Depends: libc6 (>=2.17) but 2.15-0ubuntu20.1 is to be installed
 Depends: libudev1 (>=183) but it is not installable

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

Title:
  Inconsistent mouse events for Acer T231H multitouch monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1015183/+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 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)

2013-04-17 Thread James M. Leddy

Unfortunately, the patch to gnome-settings-daemon didn't get in soon
enough to make the raring release, and we're past feature freeze. But at
the same time, we also don't have a new enough x11proto-core to use the
XF86MicMute keysym anyway. The first version that works is
xproto-7.0.24, released on March 29th, and the latest version debian has
is 7.0.23.

In any case, I've created a PPA that allows intersted people to try the
new functionality present in g-s-d (using F20). Please only proceed if
you are confident in what you're doing. If you're using a thinkpad, the
first thing you need to do is edit your /lib/udev/keymaps/module-lenovo
file so that 'micmute' is 'f20', since we will be using f20 for that
key. Other laptops already have proper udev keymap files.

The second thing is to make sure keycode 198 is maped to 'F20' as far as
X is concerned. This is easily done with

xmodmap -e "keycode 198 = F20"

To make it permant, edit your ~/.Xmodmap file

And finally install gnome-settings-daemon from the PPA:

https://launchpad.net/~jm-leddy/+archive/micmute
https://wiki.archlinux.org/index.php/Xmodmap

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

Title:
  Does not handle microphone mute button (KEY_MICMUTE)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/408903/+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 1134492] Re: xserver-xorg-lts-quantal breaks Kubuntu

2013-04-17 Thread Brian Murray

** Tags added: precise

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

Title:
  xserver-xorg-lts-quantal breaks Kubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1134492/+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 1170074] Re: mesa 9.1 regressed Tibia on nouveau

tmp = 0x4 

Strange that is set to '4'.
Memory addresses usually look like 0x88e6e08.

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

Title:
  mesa 9.1 regressed Tibia on nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1170074/+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 1170074] Re: mesa 9.1 regressed Tibia on nouveau

** Description changed:

  Yesterday, a game I played (Tibia) worked.
  Today, I got some updated Mesa packages, and now it segfaults on startup.
  http://static.tibia.com/download/tibia985.tgz
  
  Commit Log for Wed Apr 17 19:25:39 2013
  
  Upgraded the following packages:
  libegl1-mesa (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libegl1-mesa-drivers (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libgl1-mesa-dri (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libgl1-mesa-dri:i386 (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libgl1-mesa-glx (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libgl1-mesa-glx:i386 (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libglapi-mesa (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libglapi-mesa:i386 (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libgles2-mesa (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  
  Installed the following packages:
  libllvm3.2 (3.2-2ubuntu4)
  libllvm3.2:i386 (3.2-2ubuntu4)
  libxcb-dri2-0:i386 (1.8.1-2ubuntu2)
  
  [   34.621515] init: cups-browsed main process ended, respawning
  [   37.073179] show_signal_msg: 39 callbacks suppressed
  [   37.073185] Tibia[2369]: segfault at 4 ip f73a5be0 sp 
ff9d1e38 error 4 in libc-2.17.so[f726e000+1ad000]
  [   51.128347] Tibia[2443]: segfault at 4 ip f72febe0 sp 
ffbf1ed8 error 4 in libc-2.17.so[f71c7000+1ad000]
  [   59.645480] init: cups-browsed main process ended, respawning
  
  #0  0xf7bd5be0 in ?? () from /lib/i386-linux-gnu/libc.so.6
- #1  0xf766caa7 in ?? () from /usr/lib/i386-linux-gnu/libdricore9.1.1.so.1
- #2  0xf766caf0 in ?? () from /usr/lib/i386-linux-gnu/libdricore9.1.1.so.1
- #3  0xf766ccca in ?? () from /usr/lib/i386-linux-gnu/libdricore9.1.1.so.1
- #4  0xf711d2a5 in ?? () from /usr/lib/i386-linux-gnu/libgallium.so.0
- #5  0xf7120b14 in translate_sse2_create ()
-from /usr/lib/i386-linux-gnu/libgallium.so.0
- #6  0xf71198c2 in translate_create ()
-from /usr/lib/i386-linux-gnu/libgallium.so.0
- #7  0xf78cb458 in nv50_vertex_state_create ()
-from /usr/lib/i386-linux-gnu/dri/nouveau_dri.so
- #8  0xf70dd45c in cso_set_vertex_elements ()
-from /usr/lib/i386-linux-gnu/libgallium.so.0
- #9  0xf71e4cf0 in ?? () from /usr/lib/i386-linux-gnu/libgallium.so.0
- #10 0xf71e4646 in st_validate_state ()
-from /usr/lib/i386-linux-gnu/libgallium.so.0
- #11 0xf71f7f44 in st_draw_vbo () from /usr/lib/i386-linux-gnu/libgallium.so.0
- #12 0xf75d8474 in vbo_exec_vtx_flush ()
-from /usr/lib/i386-linux-gnu/libdricore9.1.1.so.1
- #13 0xf75ca41f in ?? () from /usr/lib/i386-linux-gnu/libdricore9.1.1.so.1
- #14 0xf75d5c6f in vbo_exec_FlushVertices ()
-from /usr/lib/i386-linux-gnu/libdricore9.1.1.so.1
- #15 0xf7526b9d in _mesa_BindFramebuffer ()
-from /usr/lib/i386-linux-gnu/libdricore9.1.1.so.1
+ #1  0xf766caa7 in memcpy (__len=143552024, __src=0x4, __dest=)
+ at /usr/include/i386-linux-gnu/bits/string3.h:51
+ #2  do_realloc (p=0x88e6e08) at ../../../../../src/mesa/x86/rtasm/x86sse.c:30
+ used = 143552024
+ tmp = 0x4 
+ #3  reserve (p=p@entry=0x88e6e08, bytes=bytes@entry=1)
+ at ../../../../../src/mesa/x86/rtasm/x86sse.c:41
+ #4  0xf766caf0 in emit_1ub (p=p@entry=0x88e6e08, b0=)
+ at ../../../../../src/mesa/x86/rtasm/x86sse.c:66
+ csr = 
+ #5  0xf766ccca in emit_op_modrm (p=0x88e6e08, op_dst_is_reg=, 
+ op_dst_is_mem=1 '\001', dst=..., src=...)
+ at ../../../../../src/mesa/x86/rtasm/x86sse.c:148
+ #6  0xf711d2a5 in init_inputs (index_size=0, p=0x88e6ad0)
+ at translate/translate_sse.c:1117
+ buf_max_index = {file = 0, idx = 14, mod = 2, disp = 1072}
+ buf_base_ptr = {file = 0, idx = 14, mod = 2, disp = 1064}
+ elt = {file = 0, idx = 12, mod = 3, disp = 0}
+ tmp_EAX = {file = 0, idx = 0, mod = 3, disp = 0}
+ buf_stride = {file = 0, idx = 14, mod = 2, disp = 1068}
+ buf_ptr = {file = 0, idx = 14, mod = 2, disp = 1460}
+ variant = 0x88e707c
+ instance_id = {file = 0, idx = 14, mod = 2, disp = 1972}
+ #7  build_vertex_emit (p=p@entry=0x88e6ad0, func=func@entry=0x88e6e08, 
+ index_size=index_size@entry=0) at translate/translate_sse.c:1338
+ fixup = -224223202
+ #8  0xf7120b14 in translate_sse2_create (key=key@entry=0xbaa0)
+ at translate/translate_sse.c:1507
+ #9  0xf71198c2 in translate_create (key=key@entry=0xbaa0)
+ at translate/translate.c:42
+ translate = 0x0
+ #10 0xf78cb458 in nv50_vertex_state_create (pipe=0x884a418, num_elements=3, 
+ elements=0x88e6784) at nv50_vbo.c:121
+ so = 
+ transkey = {output_stride = 32, nr_elements = 3, element = {{
+   type = TRANSLATE_ELEMENT_NORMAL, 
+   input_format = PIPE_FORMAT_R32G32_FLOAT, 
+   output_format = PIPE_FORMAT_R32G32_FLOAT, input_buffer = 0, 
+   input_offset = 24, instance_divisor = 0, output_offset = 0}, {
+   type = TRANSLATE_ELEMENT_NORMAL, 
+   input_format = PIPE_FORMAT_R32G32B32A32_FLOAT, 
+   output_format = PIPE_FORMAT_R32G32B32A32

[Ubuntu-x-swat] [Bug 112310] Re: Setting Wacom pen button to double click doesn't work

2013-04-17 Thread levien

This seems to be fixed in 12.04, albeit with a new syntax. To assign a
double-click to a button, either run something like:

xsetwacom --set "Wacom Graphire2 4x5 stylus" Button 3 "button 1 button
1"

(source: https://gist.github.com/i-e-b/2894651)

or better, create a file /usr/lib/X11/xorg.conf.d/10-wacom.conf with the
following line:

Option "Button 3" "button 1 button 1"

This fixes the problem for me.

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

Title:
  Setting Wacom pen button to double click doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/112310/+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 581663] Re: Wacom stylus buttons no longer emit double click events in Xorg

2013-04-17 Thread levien

In 12.04, it will also work to create
/usr/lib/X11/xorg.conf.d/10-wacom.conf with the following line:

Option "Button 3" "button 1 button 1"

This fixes the problem for me.

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

Title:
  Wacom stylus buttons no longer emit double click events in Xorg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/581663/+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 1170074] Re: mesa 9.1 regressed Tibia on nouveau

apt-get install libgl1-mesa-dri-dbg:i386 libgl1-mesa-glx-dbg:i386
xserver-xorg-core-dbg

Better backtrace with debug symbols.
http://paste.ubuntu.com/5716822/

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

Title:
  mesa 9.1 regressed Tibia on nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1170074/+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 1170074] Re: mesa 9.1 regressed Tibia on nouveau

** Description changed:

  Yesterday, a game I played (Tibia) worked.
  Today, I got some updated Mesa packages, and now it segfaults on startup.
- http://static.tibia.com/download/tibia985.tgz (33 MB, available as 32-bit 
binary only, so you might need ia32-libs-multiarch on 64-bit Ubuntu)
+ http://static.tibia.com/download/tibia985.tgz
  
  Commit Log for Wed Apr 17 19:25:39 2013
- 
  
  Upgraded the following packages:
  libegl1-mesa (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libegl1-mesa-drivers (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libgl1-mesa-dri (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libgl1-mesa-dri:i386 (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libgl1-mesa-glx (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libgl1-mesa-glx:i386 (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libglapi-mesa (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libglapi-mesa:i386 (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libgles2-mesa (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  
  Installed the following packages:
  libllvm3.2 (3.2-2ubuntu4)
  libllvm3.2:i386 (3.2-2ubuntu4)
  libxcb-dri2-0:i386 (1.8.1-2ubuntu2)
  
+ [   34.621515] init: cups-browsed main process ended, respawning
+ [   37.073179] show_signal_msg: 39 callbacks suppressed
+ [   37.073185] Tibia[2369]: segfault at 4 ip f73a5be0 sp 
ff9d1e38 error 4 in libc-2.17.so[f726e000+1ad000]
+ [   51.128347] Tibia[2443]: segfault at 4 ip f72febe0 sp 
ffbf1ed8 error 4 in libc-2.17.so[f71c7000+1ad000]
+ [   59.645480] init: cups-browsed main process ended, respawning
+ 
+ #0  0xf7bd5be0 in ?? () from /lib/i386-linux-gnu/libc.so.6
+ #1  0xf766caa7 in ?? () from /usr/lib/i386-linux-gnu/libdricore9.1.1.so.1
+ #2  0xf766caf0 in ?? () from /usr/lib/i386-linux-gnu/libdricore9.1.1.so.1
+ #3  0xf766ccca in ?? () from /usr/lib/i386-linux-gnu/libdricore9.1.1.so.1
+ #4  0xf711d2a5 in ?? () from /usr/lib/i386-linux-gnu/libgallium.so.0
+ #5  0xf7120b14 in translate_sse2_create ()
+from /usr/lib/i386-linux-gnu/libgallium.so.0
+ #6  0xf71198c2 in translate_create ()
+from /usr/lib/i386-linux-gnu/libgallium.so.0
+ #7  0xf78cb458 in nv50_vertex_state_create ()
+from /usr/lib/i386-linux-gnu/dri/nouveau_dri.so
+ #8  0xf70dd45c in cso_set_vertex_elements ()
+from /usr/lib/i386-linux-gnu/libgallium.so.0
+ #9  0xf71e4cf0 in ?? () from /usr/lib/i386-linux-gnu/libgallium.so.0
+ #10 0xf71e4646 in st_validate_state ()
+from /usr/lib/i386-linux-gnu/libgallium.so.0
+ #11 0xf71f7f44 in st_draw_vbo () from /usr/lib/i386-linux-gnu/libgallium.so.0
+ #12 0xf75d8474 in vbo_exec_vtx_flush ()
+from /usr/lib/i386-linux-gnu/libdricore9.1.1.so.1
+ #13 0xf75ca41f in ?? () from /usr/lib/i386-linux-gnu/libdricore9.1.1.so.1
+ #14 0xf75d5c6f in vbo_exec_FlushVertices ()
+from /usr/lib/i386-linux-gnu/libdricore9.1.1.so.1
+ #15 0xf7526b9d in _mesa_BindFramebuffer ()
+from /usr/lib/i386-linux-gnu/libdricore9.1.1.so.1
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libosmesa6 9.1.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.9.2-0ubuntu8
  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
  Date: Wed Apr 17 20:06:28 2013
  DistUpgraded: 2013-01-20 23:37:37,647 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.2.10, 3.8.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
-Subsystem: CardExpert Technology Device [10b0:0401]
+  NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
+    Subsystem: CardExpert Technology Device [10b0:0401]
  InstallationDate: Installed on 2011-10-21 (544 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-18-generic 
root=UUID=913f3daa-e25c-4d49-a07e-9215b9e553eb ro quiet splash elevator=noop 
vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to raring on 2013-01-20 (86 days ago)
  dmi.bios.date: 01/27/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: EP45-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd01/27/2010:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EP45-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.9

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

** Description changed:

  Xorg sometimes don't start at boot.
+ 
+ #2  0x7f7ea445f2ae in OsAbort ()
+ #3  0x7f7ea4464223 in ?? ()
+ #4  0x7f7ea4464a9d in FatalError ()
+ #5  0x7f7ea42f07d2 in ?? ()
+ #6  0x7f7ea1ff9ea5 in __libc_start_main (main=0x7f7ea42f0110, argc=9, 
ubp_av=0x7fffea6a6a58, 
+ init=, fini=, rtld_fini=, 
+ stack_end=0x7fffea6a6a48) at libc-start.c:260
+ result = 
+ unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 4991247855042815178, 
140181897152504, 
+ 140737126230608, 0, 0, -4991204797383056182, 
-4919836772781005622}, 
+   mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x7f7ea4468370 
<__libc_csu_init>, 
+   0x7fffea6a6a58}, data = {prev = 0x0, cleanup = 0x0, canceltype 
= -1538882704}}}
+ not_first_call = 
+ #7  0x7f7ea42f0821 in _start ()
+ 
  
  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-core 2:1.13.3-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.9.2-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
  CrashCounter: 1
  Date: Fri Apr  5 13:24:41 2013
  DistUpgraded: 2013-03-19 00:10:58,994 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.2.10: added
  ExecutablePath: /usr/bin/Xorg
  GraphicsCard:
-  Advanced Micro Devices [AMD] nee ATI Juniper XT [AMD Radeon HD 6000 Series] 
[1002:68ba] (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Device [1043:040b]
+  Advanced Micro Devices [AMD] nee ATI Juniper XT [AMD Radeon HD 6000 Series] 
[1002:68ba] (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Device [1043:040b]
  InstallationDate: Installed on 2013-02-07 (57 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch
  ProcEnviron:
-  
+ 
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-16-generic 
root=UUID=5f72727e-ae34-4862-9f87-af6ca6d14636 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
-  raise () from /lib/x86_64-linux-gnu/libc.so.6
-  abort () from /lib/x86_64-linux-gnu/libc.so.6
-  OsAbort ()
-  ?? ()
-  FatalError ()
+  raise () from /lib/x86_64-linux-gnu/libc.so.6
+  abort () from /lib/x86_64-linux-gnu/libc.so.6
+  OsAbort ()
+  ?? ()
+  FatalError ()
  Title: Xorg crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to raring on 2013-03-18 (18 days ago)
  UserGroups:
-  
+ 
  dmi.bios.date: 11/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO GEN3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0402:bd11/16/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPROGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.9~daily13.03.29-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.5-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Sat Apr  6 08:21:40 2013
  xserver.configfile: default
  xserver.devices:
-  inputPower Button KEYBOARD, id 6
-  inputPower Button KEYBOARD, id 7
-  inputLogitech Unifying Device. Wireless PID:101b MOUSE, id 8
-  inputLogitech Unifying Device. Wireless PID:2008 KEYBOARD, id 9
-  inputEee PC WMI hotkeys   KEYBOARD, id 10
+  inputPower Button KEYBOARD, id 6
+  inputPower Button KEYBOARD, id 7
+  inputLogitech Unifying Device. Wireless PID:101b MOUSE, id 8
+  inputLogitech Unifying Device. Wireless PID:20

[Ubuntu-x-swat] [Bug 1170074] Re: mesa 9.1 regressed Tibia on nouveau

$ gdb Tibia
(gdb) run
(gdb) bt full
http://paste.ubuntu.com/5716784/

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

Title:
  mesa 9.1 regressed Tibia on nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1170074/+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 1170074] Re: mesa 9.1 regressed Tibia on nouveau

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Canonical X.org (canonical-x)

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

Title:
  mesa 9.1 regressed Tibia on nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1170074/+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 1170074] Re: mesa 9.1 regressed Tibia on nouveau

** Description changed:

  Yesterday, a game I played (Tibia) worked.
  Today, I got some updated Mesa packages, and now it segfaults on startup.
- http://static.tibia.com/download/tibia985.tgz
+ http://static.tibia.com/download/tibia985.tgz (33 MB, available as 32-bit 
binary only, so you might need ia32-libs-multiarch on 64-bit Ubuntu)
  
  Commit Log for Wed Apr 17 19:25:39 2013
+ 
  
  Upgraded the following packages:
  libegl1-mesa (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libegl1-mesa-drivers (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libgl1-mesa-dri (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libgl1-mesa-dri:i386 (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libgl1-mesa-glx (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libgl1-mesa-glx:i386 (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libglapi-mesa (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libglapi-mesa:i386 (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  libgles2-mesa (9.0.3-0ubuntu1) to 9.1.1-0ubuntu2
  
  Installed the following packages:
  libllvm3.2 (3.2-2ubuntu4)
  libllvm3.2:i386 (3.2-2ubuntu4)
  libxcb-dri2-0:i386 (1.8.1-2ubuntu2)
  
- [   34.621515] init: cups-browsed main process ended, respawning
- [   37.073179] show_signal_msg: 39 callbacks suppressed
- [   37.073185] Tibia[2369]: segfault at 4 ip f73a5be0 sp 
ff9d1e38 error 4 in libc-2.17.so[f726e000+1ad000]
- [   51.128347] Tibia[2443]: segfault at 4 ip f72febe0 sp 
ffbf1ed8 error 4 in libc-2.17.so[f71c7000+1ad000]
- [   59.645480] init: cups-browsed main process ended, respawning
- 
  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libosmesa6 9.1.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic x86_64
  .tmp.unity.support.test.0:
- 
+  
  ApportVersion: 2.9.2-0ubuntu8
  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
  Date: Wed Apr 17 20:06:28 2013
  DistUpgraded: 2013-01-20 23:37:37,647 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.2.10, 3.8.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
-    Subsystem: CardExpert Technology Device [10b0:0401]
+  NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
+Subsystem: CardExpert Technology Device [10b0:0401]
  InstallationDate: Installed on 2011-10-21 (544 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-18-generic 
root=UUID=913f3daa-e25c-4d49-a07e-9215b9e553eb ro quiet splash elevator=noop 
vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to raring on 2013-01-20 (86 days ago)
  dmi.bios.date: 01/27/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: EP45-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd01/27/2010:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EP45-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.9~daily13.04.15-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Wed Apr 17 19:35:23 2013
  xserver.configfile: default
  xserver.devices:
-  inputPower Button KEYBOARD, id 6
-  inputPower Button KEYBOARD, id 7
-  inputMicrosoft Microsoft 5-Button Mouse with IntelliEye(TM) MOUSE, 
id 8
-  inputBTC USB Multimedia Keyboard KEYBOARD, id 9
-  inputBTC USB Multimedia Keyboard KEYBOARD, id 10
+  inputPower Button KEYBOARD, id 6
+  inputPower Button KEYBOARD, id 7
+  inputMicrosoft Microsoft 5-Button Mouse with IntelliEye(TM) MOUSE, 
id 8
+  inputBTC USB Multimedia Keyboard KEYBOARD, id 9
+  inputBTC USB Multimedia Keyboar

[Ubuntu-x-swat] [Bug 1170074] Re: mesa 9.1 regressed Tibia on nouveau