Public bug reported:
Is there any reason to stick with 304.xx series from release to release
while it is already considered legacy?
http://www.nvidia.com/object/unix.html
** Affects: nvidia-graphics-drivers-304 (Ubuntu)
Importance: Undecided
Status: New
** Tags: saucy
--
You
after glamor is available is this on plan?
--
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/1224718
Title:
RadeonSI / GLAMOR Support
To manage notifications about this bug go
Public bug reported:
See: http://www.phoronix.com/scan.php?page=news_itempx=MTQ2MDA
** Affects: mir (Ubuntu)
Importance: Undecided
Status: New
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: saucy
** Also affects: mir (Ubuntu)
Importance:
Public bug reported:
$ sudo apt-get install mesa-utils-extra
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
I think we should hide xdiagnose icon by default. What do you think
Alberto?
--
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/1183771
Title:
xdiagnose's shortcut launched nothing
To manage
Not working on my raring box. And even if it runs, I still feel that it
is useless to end users.
--
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/1183771
Title:
xdiagnose's shortcut launched
From my experience on Saucy, it doesn't matter whether proprietary
driver is enabled or not.
The message is just a warning at the end of configure, not a stopper.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Hi,
The upstream Mesa fix won't get distributions' libOSMesa right
automatically.
It seems that libOSMesa need to be compiled without --enable-shared-
glapi while other Mesa components need --enable-shared-glapi
Therefore, distributions need to build libOSMesa separately, which is
not been done
** Bug watch added: freedesktop.org Bugzilla #47824
https://bugs.freedesktop.org/show_bug.cgi?id=47824
** Changed in: mesa
Remote watch: freedesktop.org Bugzilla #53179 = freedesktop.org Bugzilla
#47824
--
You received this bug notification because you are a member of Ubuntu-X,
which is
The upstream fix basically make it _possible_ to compile OSMesa without
shared glapi.
It seems that Mesa components except OSMesa do need --enable-shared-
glapi .
So I currently work around this issue as I don't install libosmesa* from
the repository.
Instead, I compile libOSMesa manually as:
#
** Tags added: saucy
--
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/1066599
Title:
Wine is unable to detect OSMesa correctly when compiling from source
To manage notifications about this bug
** Also affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
--
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/763331
Title:
There should be easy way to
The bug for vdpau-video MIR should be
https://bugs.launchpad.net/ubuntu/+source/vdpau-video/+bug/1075783
--
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/763331
Title:
There should be
I filed MIRs for gstreamer-vaapi, intel-vaapi-driver and vdpau-video.
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1075774
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1075780
https://bugs.launchpad.net/ubuntu/+source/vdpau-video/+bug/705754
I don't know how
** Summary changed:
- Trere should be easy way to install VA-API helper packages
+ There should be easy way to install VA-API helper packages
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
Six Screens!
** Attachment added: 6s.jpg
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/972109/+attachment/2993809/+files/6s.jpg
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
Public bug reported:
Please check the attachment first to see what is Six Screens
This issue is from a friend of mine. He is testing Ubuntu 12.04 Beta1
His laptop is Lenovo IdeaPad Y450.
http://shop.lenovo.com/us/laptops/ideapad/y-series/y450
And the laptop's discrete graphic is NVIDIA GeForce
** Attachment added: Six Screens! Oops!
https://bugs.launchpad.net/bugs/948899/+attachment/2828709/+files/646ee0e2jw1dqmuqgfnstj.jpg
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
** Tags added: precise
--
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/948899
Title:
Six Screens For GeForce GT 130M
To manage notifications about this bug go to:
Seemingly related information I found in ArchWiki
https://wiki.archlinux.org/index.php/NVIDIA#Corrupted_screen:_.22Six_screens.22_issue
** Also affects: archlinux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is
20 matches
Mail list logo
