Glad to hear that, Kurt. Hopefully your problem was just specific to your
setup. If not, then this complicates things.
The newer catalyst driver probably has a performance bug. Could be specific to
your card, though. I'm getting almost 2000 FPS on glxgears, which is fine by
me. (Although I've
I have the same fglrx-updates version. All the output of fglrxinfo is
the same as yours except for the renderer string and the compatibility
profile context (mine is 9.012).
If the second workaround didn't work, I would first uninstall the
proprietary driver and used the FOSS driver. If the FOSS
The newer driver included in fglrx-updates seems to have corrected this
issue. At least 4 people (including myself) have confirmed that this
issue has been fixed with fglrx-updates. I will be updating the bug
report accordingly.
** Changed in: fglrx-installer-updates (Ubuntu)
Status:
** Description changed:
- On the latest daily release of Raring, a watermark/overlay shows in the
- bottom-right corner of the screen when fglrx or fglrx-updates is
- installed. It reads Unsupported hardware and has the AMD logo above it
- on top of a semi-transparent black background.
+ The
And let's just call fglrx fix committed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098561
Title:
Unsupported hardware watermark appears when FGLRX is installed on
13.04
To manage
** Description changed:
On the latest daily release of Raring, a watermark/overlay shows in the
bottom-right corner of the screen when fglrx or fglrx-updates is
installed. It reads Unsupported hardware and has the AMD logo above it
on top of a semi-transparent black background.
This
After I test it, of course. :)
Cherry Mendoza cerisesor...@gmail.com wrote:
The shell script in the workaround failed here. The awk command produced
a \x5b that sed choked on. So, I tweaked the awk script to bracket its
output as sed character classes; that let the script finish, but I wound
up
Ok. I'll add the alternate workaround to the description when I get
home, unless you would like to. Thanks.
Cherry Mendoza cerisesor...@gmail.com wrote:
The shell script in the workaround failed here. The awk command produced
a \x5b that sed choked on. So, I tweaked the awk script to bracket
We need to get Compiz to composite the Unity plugin somehow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/762699
Title:
Unity launcher and panel do not zoom alongsize the desktop with
Enhanced
Also, aticonfig reports unsupported hardware as well:
robert@CPCUbuntu:~$ aticonfig
aticonfig: No supported adapters detected
Perhaps a new bug report should be filed for this problem?
** Description changed:
On the latest daily release of Raring, a watermark/overlay shows in the
-
** Summary changed:
- unsupported hardware overlay after upgrade to raring
+ Unsupported hardware watermark appears when FGLRX is installed on 13.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Improved the title and description, added workaround.
** Description changed:
- After upgrading to raring and installing the latest fglrx package from
- the archive I get a AMD branded overlay in the bottom RHS of the screen
- with the message 'Unsupported hardware'.
+ On the latest daily
Confirmed on 6670/turks. I'm positive this bug affects most if not all
fglrx users. Good luck with the fix. Tell me if the workaround works for
you guys or not.
robert@CPCUbuntu:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: AMD
Confirmed on Ubuntu 12.10 with Unity version 6.12.0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/784055
Title:
compiz CPU usage increases dramatically when running indicator-
multiload
To
Also confirmed on a fresh install of Raring, if it hasn't been already.
Fully updated as of writing. Seems to increase the CPU usage of unity-
panel-service on Quantal, while it increases the CPU usage of compiz on
Raring.
--
You received this bug notification because you are a member of Ubuntu
Robert Zelic, that's odd. I you sure it's not a problem specific to
yourself? If it isn't, I think we'll need a whole other bug report just
for adobe-flash-plugin. Then again, IMO, we should be focusing on open
source alternatives rather than try to bandage this semi-abandoned piece
of software.
(Added 2nd workaround, other minor edits.)
** Description changed:
Steps to reproduce:
1) Open a flash file. Be it a game, video, website, etc.
2) Right click on the flash player and select Settings
3) Try to click on something in the dialog box such as a checkbox or a tab
What is
** Description changed:
- When selecting the color of the dash from compiz-setting-manager, notify
- osd still uses the background color opacity and not the color from the
- dash in unity precise
+ Notify-OSD does not pick up the custom background colour value for
+ Unity. It uses the average
(Added workaround)
** Description changed:
Notify-OSD does not pick up the custom background colour value for
Unity. It uses the average background colour even when the user
specifies a custom background colour to be used in the Unity plugin
settings of CCSM.
Steps to reproduce:
(Added notify-osd preview command. Sorry for so many edits.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/970362
Title:
Notify OSD does not respect Unity's background color setting
To manage
This is also present in Quantal. This bug needs to get more attention.
Some people may need to zoom in on the panel/launcher/dash to be able to
see it better. It's also worth noting once again that screencasters may
need to use this feature.
** Description changed:
Binary package hint: compiz
I have this problem too. I've had it for a while. Since about 11.10 (I
started using Unity with 11.10) all the way to my current desktop. Right
now I'm running 12.10 amd64, and I've had this problem across several
machines and various Ubuntu versions including 12.04. Very annoying and
can even be
Public bug reported:
This is the same bug as Bug #995699, but for 12.10. Also, on said bug
report, it seems we've come to a conclusion that the window manager
(Compiz) is causing the problem, which is why this is filed for compiz.
I'm running a fully updated 12.10 amd64. It seems pretty much
*** This bug is a duplicate of bug 865672 ***
https://bugs.launchpad.net/bugs/865672
** Attachment added: Bug1076881.ogg
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1076881/+attachment/3428481/+files/Bug1076881.ogg
--
You received this bug notification because you are a
** Description changed:
- WORKAROUNDS:
+ Steps to reproduce:
+ 1) Open a flash file. Be it a game, video, website, etc.
+ 2) Right click on the flash player and select Settings
+ 3) Try to click on something in the dialog box such as a checkbox or a tab
+
+ What is expected to happen:
+ The
In order to get new people up to speed on this bug, I have improved the
description. I have also attached a demo video to this comment. I am
contributing to this from Bug #1076881, which was marked as a duplicate
of this. Good luck on a fix, guys.
** Attachment added: Demo video of the bug on
26 matches
Mail list logo
