date:20120306

[Ubuntu-x-swat] [Bug 927155] Re: [snb-m-gt2+] Viewsonic VA2012w not correctly detected (Invalid EDID)

2012-03-06 Thread Alan Pope

Hi Bryce,

Thinking back over the history of this display. It was previously one of
a pair of identical screens each plugged into ports on an nVidia 7900 in
twinview. So I would have always had an xorg.conf to maintain the
twinview settings and 3360x1050 resolution. I have also just tested a
12.04 live CD with the screen attached to another nVidia based desktop
and I get the same problem, so it does look like a monitor-specific
thing rather than a video-card related issue, and may well not be a
regression after all.

I will try the other things you suggest though.

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

Title:
  [snb-m-gt2+] Viewsonic VA2012w not correctly detected (Invalid EDID)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/927155/+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 948234] Re: xorg intel driver returns less than 3fps in glxspheres test

2012-03-06 Thread RichardHDF

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Invalid => 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/948234

Title:
  xorg intel driver returns less than 3fps in glxspheres test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/948234/+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 936552] Re: MacBookAir 4, 1 trackpad does not work with evdev/multitouch driver

2012-03-06 Thread Chase Douglas

Hi Bryce,

This seems to be a udev layer issue, which I have no idea about. I'm
removing my assignment because I don't know what to try, and I don't
have the resources to look into it right now :(.

** Changed in: xserver-xorg-input-synaptics (Ubuntu)
 Assignee: Chase Douglas (chasedouglas) => (unassigned)

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

Title:
  MacBookAir 4,1 trackpad does not work with evdev/multitouch driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/936552/+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 936552] Re: MacBookAir 4, 1 trackpad does not work with evdev/multitouch driver

2012-03-06 Thread Clint Byrum

New data point.. it failed again even with the udevadm settle... though
its happening far less often now at least.

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

Title:
  MacBookAir 4,1 trackpad does not work with evdev/multitouch driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/936552/+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 948697] Re: Xorg crashed with SIGABRT in valuator_mask_set_double()

2012-03-06 Thread Robert Hooker

** Description changed:

  This happens after an extended time with the lid closed, with the
  machine not set to suspend on lid close.
+ 
+ Backtrace:
+ [291943.052] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7fea247452f6]
+ [291943.052] 1: /usr/bin/X (0x7fea245bd000+0x18c19a) [0x7fea2474919a]
+ [291943.052] 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fea238e3000+0xfcb0) 
[0x7fea238f2cb0]
+ [291943.052] 3: /usr/bin/X (valuator_mask_set_double+0x0) [0x7fea24624ab0]
+ [291943.052] 4: /usr/lib/xorg/modules/input/synaptics_drv.so 
(0x7fea1e36f000+0xc1ae) [0x7fea1e37b1ae]
+ [291943.052] 5: /usr/lib/xorg/modules/input/synaptics_drv.so 
(0x7fea1e36f000+0x5c07) [0x7fea1e374c07]
+ [291943.052] 6: /usr/bin/X (0x7fea245bd000+0x8acc7) [0x7fea24647cc7]
+ [291943.052] 7: /usr/bin/X (0x7fea245bd000+0xb0bba) [0x7fea2466dbba]
+ [291943.052] 8: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fea238e3000+0xfcb0) 
[0x7fea238f2cb0]
+ [291943.052] 9: /lib/x86_64-linux-gnu/libc.so.6 (0x7fea22759000+0x8a249) 
[0x7fea227e3249]
+ [291943.052] 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_calloc+0x29a) 
[0x7fea227db25a]
+ [291943.052] 11: /usr/bin/X (0x7fea245bd000+0x11e526) [0x7fea246db526]
+ [291943.052] 12: /usr/bin/X (0x7fea245bd000+0x11e76c) [0x7fea246db76c]
+ [291943.052] 13: /usr/bin/X (0x7fea245bd000+0x11ed80) [0x7fea246dbd80]
+ [291943.052] 14: /usr/bin/X (0x7fea245bd000+0x141ffa) [0x7fea246feffa]
+ [291943.052] 15: /usr/bin/X (mieqProcessDeviceEvent+0x1e1) [0x7fea24725e21]
+ [291943.052] 16: /usr/bin/X (0x7fea245bd000+0x76ff6) [0x7fea24633ff6]
+ [291943.052] 17: /usr/bin/X (0x7fea245bd000+0x125613) [0x7fea246e2613]
+ [291943.052] 18: /usr/bin/X (0x7fea245bd000+0x4e721) [0x7fea2460b721]
+ [291943.052] 19: /usr/bin/X (0x7fea245bd000+0x3d64a) [0x7fea245fa64a]
+ [291943.052] 20: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) 
[0x7fea2277a76d]
+ [291943.052] 21: /usr/bin/X (0x7fea245bd000+0x3d93d) [0x7fea245fa93d]
+ [291943.052] Segmentation fault at address 0x61
+ [291943.052] 
+ Caught signal 11 (Segmentation fault). Server aborting
  
  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-core 2:1.11.4-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 1.94-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CrashCounter: 1
  Date: Tue Mar  6 22:54:50 2012
  DistUpgraded: Log time: 2012-01-09 10:06:08.081356
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
-  bcmwl, 6.20.55.19+bdcom, 3.2.0-17-generic, x86_64: installed
-  bcmwl, 6.20.55.19+bdcom, 3.2.0-18-generic, x86_64: installed
+  bcmwl, 6.20.55.19+bdcom, 3.2.0-17-generic, x86_64: installed
+  bcmwl, 6.20.55.19+bdcom, 3.2.0-18-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
-  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
-Subsystem: Apple Inc. Device [106b:00eb]
+  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Apple Inc. Device [106b:00eb]
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64+mac 
(20110427.1)
  MachineType: Apple Inc. MacBookAir4,2
  ProcCmdline: /usr/bin/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 
-novtswitch
  ProcEnviron:
-  
+ 
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic 
root=UUID=95622cbd-b253-48f0-9a5d-a0948c98f97a ro quiet splash 
i915.i915_enable_rc6=1 i915.i915_enable_fbc=0 i915.semaphores=1 
i915.lvds_downclock=1 pcie_aspm=force usbcore.autosuspend=1 
drm.vblankoffdelay=1 vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
-  valuator_mask_set_double (mask=0x61, valuator=4, data=0) at 
../../dix/inpututils.c:509
-  EventProcessTouchEvent (hw=0x7fea2587df50, pInfo=0x7fea2585a860, 
ev=) at ../../src/eventcomm.c:579
-  EventReadHwState (pInfo=0x7fea2585a860, comm=0x7fea25875f80, 
hwRet=0x7fea2587d270) at ../../src/eventcomm.c:730
-  SynapticsGetHwState (hw=0x7fea2587d270, priv=0x7fea25875dd0, 
pInfo=0x7fea2585a860) at ../../src/synaptics.c:1576
-  ReadInput (pInfo=0x7fea2585a860) at ../../src/synaptics.c:1592
+  valuator_mask_set_double (mask=0x61, valuator=4, data=0) at 
../../dix/inpututils.c:509
+  EventProcessTouchEvent (hw=0x7fea2587df50, pInfo=0x7fea2585a860, 
ev=) at ../../src/eventcomm.c:579
+  EventReadHwState (pInfo=0x7fea2585a860, comm=0x7fea25875f80, 
hwRet=0x7fea2587d270) at ../../src/eventcomm.c:730
+  SynapticsGetHwState (hw=0x7fea2587d270, priv=0x7fea25875dd0, 
pInfo=0x7fea2585a860) at ../../src/synaptics.c:1576
+  ReadInput (pInfo=0x7fea2585a860) at ../../src/synaptics.c:1592
  Title: Xorg crashed with

Re: [Ubuntu-x-swat] [Bug 948053] Re: nvidia-96 and nvidia-173 uninstallable on Precise

2012-03-06 Thread Martin Pitt

Bryce Harrington [2012-03-06 18:48 -]:
> Is it possible for us to toggle off -173 and -96 from being shown in
> jockey until we think it'll work?  Might help quell some of the bug
> reports we get.

That already happens. In one of the previous cycles I changed Jockey
to compare the xorg-video-abi-* between the server and the driver, and
only show a driver if they match.

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

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

Title:
  nvidia-96 and nvidia-173 uninstallable on Precise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bug/948053/+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 948697] Re: Xorg crashed with SIGABRT in valuator_mask_set_double()

2012-03-06 Thread Robert Hooker

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/948697/+attachment/2827467/+files/CoreDump.gz

** Visibility changed to: Public

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

Title:
  Xorg crashed with SIGABRT in valuator_mask_set_double()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/948697/+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 940564] Re: nvidia-graphics-drivers (295.20-0ubuntu1), is causing failed restarts & shutdowns

2012-03-06 Thread Doug McMahon

Decided to revisit this on a new 2 day old Beta1 install
Was using the .10 drivers from the get go, fully updated regularly, no 
restart/shutdown issues.

Updated nvidia-current tonight to the .20, just like clockwork after 3 normal 
restarts over the course of an hr. or the 4th one failed.
Again here now real issue for 12.04, likely that the .10 package will remain 
viable for install. Just wonder if this may become more than a rare issue once 
the user hardware base increases, time will tell

I guess there would be no consideration of making the .10 driver
'nvidia-current' & making use of nvidia-current-updates for .20 or
higher

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

Title:
  nvidia-graphics-drivers (295.20-0ubuntu1),  is causing failed restarts
  & shutdowns

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/940564/+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 948234] Re: xorg intel driver returns less than 3fps in glxspheres test

2012-03-06 Thread RichardHDF

Hi Bryce,

I do not think this has anything to do with the NVidia card. There is
unfortunately no option to turn the card off in the BIOS. The reason I
believe it has nothing to do with the NVidia card, is because I recently
had the same hardware setup running in Arch Linux, and the intel card
tested fine on glxspheres. I am not experiencing issues with bumblebee.

Please do not mark the bug as invalid before you have taken the time to
try and understand the issue. I know this is crunch time for the devs,
because you want to meet the deadlines before 12.04 is released, but
automatically shifting the blame to bumblebee doesn't count as squashing
a bug.

The glxspheres was run against my intel card after I purged the
bumblebee install from my system. Glxspheres reports an inferior frame
rate as opposed to results I got on Arch Linux previously. It should be
capped at 30 fps; I'm getting 2.9 max fps (note with bumblebee not even
installed on my pc).

I would appreciate you reconsidering the status of this bug.

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

Title:
xorg intel driver returns less than 3fps in glxspheres test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/948234/+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 948162] Re: It's a system generated file.

2012-03-06 Thread Naimuddin Shek

I was launching it from gnome-terminal.
It said that apport service failed to start.

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

Title:
  It's a system generated file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/948162/+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 947250] Re: System Restart on Intel MotherBoard DX58SO

2012-03-06 Thread Piyush Roy

** Package changed: ubuntu => xorg (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/947250

Title:
  System Restart on Intel MotherBoard DX58SO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/947250/+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 946589] Re: Xorg crashes in Precise with Dual Screens

2012-03-06 Thread Britt Yazel

Isn't the kernel used in Precise a 3.2 kernel? Or will I need the 3.3
kernel to fix this bug?

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

Title:
  Xorg crashes in Precise with Dual Screens

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/946589/+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 947250] [NEW] System Restart on Intel MotherBoard DX58SO

2012-03-06 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

I am not sure how to reproduce it. But I found that the problem is
predominant when I enable power related options in the mother board
(DX58SO) like EIST and others. It seems some application loading or any
task initaition causes this system restart, this application or task
could be anything. Tha last time it happened when youtube video was
going to load (Firefox 10). I have never got the problem when the system
is idle.

Addtionally, this bug is valid of all non LTS Ubuntu Versions.

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


** Tags: bot-comment
-- 
System Restart on Intel MotherBoard DX58SO
https://bugs.launchpad.net/bugs/947250
You received this bug notification because you are a member of Ubuntu-X, which 
is subscribed to xorg 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 947350] Re: Display wont go higher than 1024x768

2012-03-06 Thread Matthew

Will do, I'll report back here with the requested info as soon as I can.

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

Title:
  Display wont go higher than 1024x768

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/947350/+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 947871] Re: fglrx (not installed): fglrx kernel module failed to build [KCL_fpu_begin: Error: 'TS_USEDFPU' undeclared (first use in this function)]

2012-03-06 Thread Launchpad Bug Tracker

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

** Changed in: fglrx-installer (Ubuntu)
   Status: New => Confirmed

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

Title:
  fglrx (not installed): fglrx kernel module failed to build
  [KCL_fpu_begin: Error: 'TS_USEDFPU' undeclared (first use in this
  function)]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/947871/+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 947871] Re: fglrx (not installed): fglrx kernel module failed to build [KCL_fpu_begin: Error: 'TS_USEDFPU' undeclared (first use in this function)]

2012-03-06 Thread Daniel van Vugt

** Summary changed:

- fglrx (not installed): fglrx kernel module failed to build
+ fglrx (not installed): fglrx kernel module failed to build [KCL_fpu_begin: 
Error: 'TS_USEDFPU' undeclared (first use in this function)]

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

Title:
  fglrx (not installed): fglrx kernel module failed to build
  [KCL_fpu_begin: Error: 'TS_USEDFPU' undeclared (first use in this
  function)]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/947871/+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 948232] Re: fglrx 2:8.920-0ubuntu1: fglrx kernel module failed to build

2012-03-06 Thread Daniel van Vugt

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

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


** This bug has been marked a duplicate of bug 947871
   fglrx (not installed): fglrx kernel module failed to build [KCL_fpu_begin: 
Error: 'TS_USEDFPU' undeclared (first use in this function)]

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

Title:
  fglrx 2:8.920-0ubuntu1: fglrx kernel module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/948232/+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

1 2 >

1 - 100 of 172 matches

Mail list logo