Interestingly, if you find an installed package and click Run in Ubuntu
Software, the application will run.
Install: NO
Remove: NO
Run: Yeah
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This appears to have resolved in a later update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615173
Title:
package rhythmbox-plugins 3.4-1ubuntu1 failed to install/upgrade:
trying to overwrite
Public bug reported:
Notification on restart after rhythmbox-plugins failed to install during
dist-upgrade.
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: rhythmbox-plugins 3.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
AMD's fglrx does not support the HD 4200 in that version of Ubuntu. The
last Ubuntu release supported by the AMD proprietary driver was 12.04.1.
Adapters prior to the HD 5000 series are not supported. This bug is not
related to your issue.
--
You received this bug notification because you are
Did you follow the instructions at
https://wiki.ubuntu.com/Testing/EnableProposed for enabling selective
installation and then install all packages explicitly from there?
That is: fglrx-updates/wily-proposed, fglrx-amdcccle-updates/wily-
proposed, fglrx-core-updates/wily-proposed?
--
You
Ease follow the instructions in the link I provided to enable selective
installation and install the packages explicitly from wily-proposed as I
suggested. If you set selective installation, you will update only
those packages.
--
You received this bug notification because you are a member of
Please follow ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1493888
Title:
FGLRX incompatible with gcc 5
To manage notifications about this bug go to:
For those with dual graphics: Although it is not supposed to be
required any longer, I answer this question often enough on the Ubuntu
Forums that I recommend the following:
If you have fglrx installed and end up with a blank/black screen, go
into recovery mode, mount your filesystem read/write.
-proposed works like a champ on my R9 290X
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1493888
Title:
FGLRX incompatible with gcc 5
To manage notifications about this bug go to:
Before enabling -proposed, it might be worthwhile to review the
documentation at https://wiki.ubuntu.com/Testing/EnableProposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1493888
Title:
FGLRX
Alberto --
This is the second time I have been involved in a major disaster
affecting the fglrx driver. It took quite some time to fix the one
that I reported a few months ago.
I asked that that bug be raised to "critical" as it affected an entire
class of users.
I understand that the heat is
*** This bug is a duplicate of bug 1493888 ***
https://bugs.launchpad.net/bugs/1493888
Sergey --
Have you posted the .debs somewhere? If you have, would you mind
letting me add that to a blog article I wrote yesterday?
You may PM me on Ubuntu Forums. I'm QIII there.
--
You received
Doing the upgrade over does seem to work. Meh.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494184
Title:
package software-center 13.10-0ubuntu8 failed to install/upgrade:
triggers looping,
Yes. It works in 14.04.3.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.3 LTS
Release:14.04
Codename: trusty
$ fglrxinfo
display: :0 screen: 0
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: AMD
*** This bug is a duplicate of bug 1338706 ***
https://bugs.launchpad.net/bugs/1338706
The next time Samsung tech support tells you they don't support Linux,
ask them "Isn't that a bit odd, considering Samsung is a member of The
Linux Foundation?"
--
You received this bug notification
The thanks are to the individuals handling the bug and arriving at a
solution. Alberto Milone, for instance, has been in on a couple of bugs
I've reported/followed.
Bugs happen. It's a fact of life. They get reported and they get fixed
(hopefully).
From a systemic viewpoint, however, this
Enabling -proposed without pinning may cause you to end up downloading
and updating other packages you don't want. This is not fixed until
there is no need for -proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That this was changed from High to Critical then back down to High when
it affects an entire class of users and renders their systems unusable
brings to mind two words. You may take your pick:
Asinine
Incompetent
--
You received this bug notification because you are a member of Ubuntu
Bugs,
That this bug was found in proposed and not fixed before it was moved
out of proposed to the main repo brings to mind one of two words. You
may take your pick:
Asinine
Incompetent
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Kubuntu 14.04.3
Expected behavior: Kernel would install and rebuild fglrx package.
Observed behavior: After upgrading to kernel 3.19.0.26, fglrx driver
failed. After uninstall/reinstall, the build failed. fglrx driver does
not work. Graphics effects do not work.
Dropping back to kernel 3.19.0.25 works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1485835
Title:
fglrx-updates-core 2:15.200-0ubuntu0.3: fglrx-updates-core kernel
module failed to build
I don't see anywhere that anyone used the fact that it works in 15.04 as
an excuse. I do see that the fact was used as an indicator that fixing
this problem was unlikely to cause regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Dmitry --
Unfortunately, your GPU is no longer supported by AMD with a driver that
will work with the current version of X server. There is nothing anyone
at Canonical or any other Linux distributor can do. That is really not
related to this particular bug. Since you have already removed the
fglrx-amdcccle (and -updates) is now pulled in automatically when you
install the driver in the terminal, so there is no need to specify them
any longer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
BTW -- I added a reference on my blog to this bug and suggested looking
at post #77. Don't know if anyone will ever see that in the backwaters
of the interwebzz ...
I also answer a lot of questions on the Ubuntu Forums.
But I guess that's what I can do to get out the news.
--
You received
Hey, I only reported the bug and confirmed the fix in userland. Thank
the folks at Canonical for fixing it!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1424491
Title:
apt-get fails to install
Post #77 was on a fresh install with all updates.
Installing fglrx-updates draws in fglrx-amdcccle-updates without need to
specify it separately.
Notice that Alberto said it is in trusty-proposed. It may take some
time for it to hit the main repo.
--
You received this bug notification because
Going to try Ubuntu 12.04.5 - 14.04.2 tonight.
The Ubuntu GNOME folks may have some work to do on their end, too. So
that may be a bit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1424491
Title:
It certainly works for Trusty. You should probably hold off on Precise
if you are running it until Alberto lets us know that it's fixed.
For those of you who have never done this before, please reference
https://wiki.ubuntu.com/Testing/EnableProposed
Make sure to read the part about pinning in
That's an avoidance or a work-around, not a fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1424491
Title:
apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5
To manage
We'd be happy to answer that on ubuntuforums.org or on IRC at #ubuntu.
Let's let Alberto and crew work on this bug here.
:)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1424491
Title:
apt-get
Alberto -
Might I suggest that this be raised from High to Critical?
The Hardware Enablement Stack should have enabled rather than disabled
to the point where the point releases are impossible to use for an
entire class of users.
--
You received this bug notification because you are a member
14.04.1, 12.04.4, 14.10 and 15.04 (development) all work. You could use
14.04(.2) or 12.04(.5) until this is sorted out and then upgrade.
Just don't install the Hardware Enablement Stack for now.
It's not skin off of anyone's nose if you decide to go back to Windows.
--
You received this bug
That would be a different bug and should be reported separately. This
one is specifically about installing the fglrx driver (the proprietary
AMD graphics driver)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hey, folks. The bug is about the two releases referenced and fglrx-
installer. The more chatter we add, the more the developers are going
to have to wade through.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For clarity:
I attempted the following on my test machine:
1. Upgrade from 14.04.1 with the driver installed. I always recommend
against this, but I attempted it anyway in the interest of testing.
2. From a fresh installation of 14.01.1, install the driver, remove the
driver, upgrade and then
** Description changed:
Activity: Install fglrx AMD driver on 12.04.5 and 14.02.2
Expected behavior: fglrx would intall
Observed behavior: fglrx is not installed as follows
Attempt to install fglrx fails as follows:
zack3@ZACK3:~$ sudo apt-get install
Public bug reported:
Activity: Install fglrx AMD driver on 12.04.5 and 14.02.2
Expected behavior: fglrx would intall
Observed behavior: fglrx is not installed as follows
Attempt to install fglrx fails as follows:
zack3@ZACK3:~$ sudo apt-get install fglrx-updates xvba-va-driver
** Attachment added: history.log
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1424491/+attachment/4325142/+files/history.log
** Description changed:
Activity: Install fglrx AMD driver on 12.04.5 and 14.02.2
Expected behavior: fglrx would intall
Observed
Sorry for one more comment, Julian...
OK folks, we have been given an answer and have been asked not to post
further here. This is not a problem with anything Canonical can
control.
I've contacted the package manager at webupd8.org. If I get any info or
a resolution, I will post it on Ubuntu
Public bug reported:
Description:Ubuntu Trusty Tahr (development branch)
Release:14.04
apt:
Installed: 0.9.15.4ubuntu3
Candidate: 0.9.15.4ubuntu4
Version table:
0.9.15.4ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
***
** Summary changed:
- dist-upgrade attempts to remove webupd8's oracle-jave7-installer
+ dist-upgrade attempts to remove webupd8's oracle-java7-installer
** Description changed:
Description:Ubuntu Trusty Tahr (development branch)
Release:14.04
apt:
Installed:
Public bug reported:
Motherboard: http://www.gigabyte.us/products/product-page.aspx?pid=3894
Sound: snd-hda-intel, Realtek ALC889 codec
xx@:~$ lsb_release -rd
Description:Ubuntu Trusty Tahr (development branch)
Release:14.04
xx@:~$ uname -a
Linux Zack
Please advise additional files/info needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302335
Title:
Sound stopped working after updates April 3, 2014. Sound setting show
only dummy output
@Heikki --
I'll try to remove all and start from the top with only vainfo, xvba-va-
driver, libva-egl1, libva-glx1.
However, there is another bug reported against xvba-va-driver in
Precise.
Will go find it and post back.
--
You received this bug notification because you are a member of Ubuntu
Find other bug at Bug #969579
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974205
Title:
VA API doesn't work with fglrx driver from restricted repos
To manage notifications about this bug go to:
No improvement after cleanup and reinstall:
$ vainfo
libva: VA-API version 0.32.0
Xlib: extension XFree86-DRI missing on display :0.
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/x86_64-linux-gnu/dri/fglrx_drv_video.so
xvba_video: XVBA_CreateContext(): status 11
libva error:
On a hunch, I modified my xorg.conf.
I removed
load dri
Now, all seems well. Suggest perhaps issue is with xorg.conf conflict?
$ vainfo
libva: VA-API version 0.32.0
Xlib: extension XFree86-DRI missing on display :0.
libva: va_getDriverName() returns 0
libva: Trying to open
In a 64 bit installation, I did not find fglrx_drv_video.so.
However, if I installed XvBA, I found a symlink to the XvBA .so in
/usr/lib/va/drivers which was called fglrx_drv_video.so, but that still
left me with failed initialization.
--
You received this bug notification because you are a
With the XvBA package installed and a symlink as described by Heikki, my
vainfo output is now:
$ vainfo
libva: VA-API version 0.32.0
Xlib: extension XFree86-DRI missing on display :0.
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/x86_64-linux-gnu/dri/fglrx_drv_video.so
Exactly the same output from vainfo.
Minor differences in environment: Kubuntu Precise, ATI HD 5870
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974205
Title:
VA API doesn't work with fglrx
Pardon me for the additional post. To confirm original entry by Stefan
$ apt-cache policy libva-dev libva-egl1 libva-glx1 libva-tpi1 libva-x11-1
libva1 vainfo
libva-dev:
Installed: (none)
Candidate: 1.0.15-4
Version table:
1.0.15-4 0
500 http://us.archive.ubuntu.com/ubuntu/
@ blue print
Your question on reinstalling would probably best be handled on
ubuntuforums.
In your post, make a reference to this bug report and specifically to
your post #95.
If I have a chance, I'll look for you post there and lend a hand. If I
don't, there are a lot of other people who
Fortunately, I keep my ear to the ground and was aware of this problem
before I updated. I would have been able to dig myself out of it, but
it would certainly have raised by blood pressure.
Since the fix was made available in -updates, this worked for me:
Completely uninstall Catalyst 10.9.
Scratch this. On attempt last night, worked flawlessly.
--
Installation of fglrx-amdcccle 2:8.721-0ubuntu5 crashes video
https://bugs.launchpad.net/bugs/545762
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
No problem this time. It installed just like I thought it should, as
has been the case with the AMD/ATI prereleases in the past.
Gremlins, I guess.
On 03/28/2010 03:00 PM, Robert Hooker wrote:
You dont have the problem anymore? I'm closing it for now in that case,
but please feel free to
By the way, it was late last night. I don't want to impugn the
developers or the responsible MOTU.
I suspect this goes back to the fact that the AMD/ATI driver is a pre-
release.
So this may have to go back to AMD/ATI.
--
Installation of fglrx-amdcccle 2:8.721-0ubuntu5 crashes video
Public bug reported:
Release: Lucid Lynx
Package: fglrx-amdcccle 2:8.721-0ubuntu5
Expected behavior: Installation expected to drive video properly
Actual behavior: After installation, system allowed me to select user and
enter password. Immediately thereafter, however, the screen went
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/41808146/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/41808147/CurrentDmesg.txt
** Attachment added: DkmsStatus.txt
http://launchpadlibrarian.net/41808148/DkmsStatus.txt
** Attachment
[ 15.612398] nvidia: module license 'NVIDIA' taints kernel.
[ 15.612408] Disabling lock debugging due to kernel taint
The nVidia module is not being inserted into the kernel at boot time.
Also nVidia lists the card as legacy. They are making no more updates
to the driver. Xorg has moved
Sorry folks. I hadn't checked in on this in some time.
I believe the issue has turned out to be that the said GPU is in
nVidia's legacy pile and is no longer supported.
This was a very old test machine which I no longer use.
--
nVidia GeForce2 MX 400 video driver fails in karmic
I have the same problems for both the 32 and 64 bit versions on 32 and
64 bit machines..
Happens both after installing updates from repos in Alpha 5 AND when
using latest Alpha 6 images on CD for a fresh install.
In the case of fresh install, I encounter the problems directly from the
CD when:
Confirm SYMLINK message, both on attempt to run LiveCD and attempting to
install both 32 bit and 64 bit versions.
Also encountered this error attempting to reboot after using apt-get
upgrade prior to attempting to use new ISO image.
AMD Phenom II X4
8GB
ATI HD3200
--
Karmic Alpha 6 will not
Sorry --
32 bit installation attempted on
Pentium IV
1GB
GeForce2 MX/MX 400
--
Karmic Alpha 6 will not boot from Live CD
https://bugs.launchpad.net/bugs/432176
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Public bug reported:
Release: karmic (squeeze/sid).
lspci:
01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400]
(rev b2)
On restart after upgrading from 9.04 (where card worked with 3D
acceleration) to 9.10, X failed to start. Was forced to log in from
command
If anyone is still interested.
I was going to CP the link, but didn't get the C part, apparently.
www.x.org's bug site directed me to bugzilla.
Apparently this is a regression from an earlier version of Xorg.
The bug was reopened very recently with
Priority: High
Severity: Major
It's not
The problem is not Linux, Ubuntu, Compiz or your video card.
I looked at www.x.org's bug reports and was directed to bugzilla.
Sorry. Forgot to CP the link.
This is a regression from an earlier Xorg bug. It was recently
reopened.
Priority: High
Severity: Major.
--
restricted drivers (ATI)
67 matches
Mail list logo
