my system is running since i reinstalled some parts that i found in
synaptic after receiving an error message.
so now you can stop sending me the email messages about those bugs.
Thanks for helping me
Marius en Lia van Harten
Bergstrasse 17
49774 Vinnen
Duitsland
Tel.: 0049 (0)5432 9058786
I still seem to be having issues here. Did a fresh install of 14.04.3,
allowed updates during the install. Kernel is 3.19.0-26-generic and I
have fglrx 2:15.200-0ubuntu0.5. Still get flickering and erratic video
behaviour when I use chrome. Doesn't seem to do it when I open the dash
or am using
** Changed in: hwe-next
Status: New = Fix Released
** Changed in: hwe-next
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: hwe-next
Importance: Undecided = High
--
You received this bug notification because you are a member of Desktop
Packages, which is
This bug has caused a situation whereby I will probably have to
reinstall Ubuntu in order to get the up-to date kernel running on my
hardware.
See comments 38, 42, 51 and 53 for details.
I filed another bug report to describe my particular situation:
Wow! Just wow!
I want to say thank you to everyone for the quick resolution. I have never
had this type of support; not even something I have payed tens of thousands
of dollars in support for a year. This was really outstanding work. I was
able to do the update last night and had no issues.
I don't understand why everyone thanks Canonical here.
I mean, they messed up the SRU kernel process and broke a big number of stable
desktops in the wild (including some LTS users).
An now everyone is saying everything is great all now that an update was
pushed?
But did you think of those
Yes. I can understand what you are saying. I am looking at the overall
effort here. Yes, it probably should have been tested better or reviewed
or whatever. And I have been in those situations where I have cursed
linux. The average user is going to have serious problems and wonder why
did
I'm sharing your opinion, for inexperienced users it's a disaster and bad for
the reputation of Linux.
But I also thank the devs providing a fix in relatively short time.
Am 21. August 2015 16:34:16 MESZ, schrieb Nicolas Delvaux
1479...@bugs.launchpad.net:
I don't understand why everyone thanks
You are totaly right.
My system is running again but I am not sure what happens wenn the new
updat (upgrade) is comming.
So far so good I can use my PC and I say thanks to all off them who
helped me and the other ones.
Marius
Op 21-08-15 om 17:11 schreef QIII:
The thanks are to the individuals
I agree with you all and don't wanted to be mean with Alberto or whoever
else.
I really don't care of who is guilty (if there is ever such a who),
but what concerns me is that from the outside there have been no sign
from Canonical, the kernel team or whatever to at least acknowledge that
what
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
OK ubuntu4.2 fix the problem. Thank you.
Il 20 agosto 2015 00:53:40 CEST, igor 1479...@bugs.launchpad.net ha scritto:
Thank you, now it's ok.
--
You received this bug notification because you are subscribed to a
duplicate bug report (1485889).
https://bugs.launchpad.net/bugs/1479913
Title:
running good over here now. thank you!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU request: fglrx.ko fails because of backported GPL-only
i'm on vivid and the problem is still there, fglrx-updates-core
2:15.200-0ubuntu4.2, is it released on the proper channel or is it in
proposed?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
This is why I did before the new package was released:
sudo apt-get purge linux-headers-3.19.0-26 linux-headers-3.19.0-26-generic
linux-image-3.19.0-26-generic
sudo apt-get install linux-headers-3.19.0-25 linux-headers-3.19.0-25-generic
linux-image-3.19.0-25-generic
ls /var/lib/initramfs-tools
my bad! after a couple of tries i got it working again. Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU request: fglrx.ko fails because of
Tested, it works!
Thank you very much Ubuntu Dev Team.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU request: fglrx.ko fails because of backported
Works fine now with 3.19.0-26-lowlatency. Thanks.
On 21 August 2015 at 04:16, Zach tundr...@gmail.com wrote:
running good over here now. thank you!
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU
after a long way off struggle my system is running again thanks to all
giving tips and solutions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU request:
Fglrx bug is fixed, fglrx doing fine here. Ubuntu gnome vivid, proper
channel. Thanks to the devs.
Am 20. August 2015 15:50:53 MESZ, schrieb Flavio Elawi flavio.el...@gmail.com:
i'm on vivid and the problem is still there, fglrx-updates-core
2:15.200-0ubuntu4.2, is it released on the proper
Resolved
Awesome - thanks all!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU request: fglrx.ko fails because of backported GPL-only
works for me. Thank you!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU request: fglrx.ko fails because of backported GPL-only
'pci_ignore_hotplug'
Thank you, now it's ok.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU request: fglrx.ko fails because of backported GPL-only
'pci_ignore_hotplug' symbol
Thak you. Works for me too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU request: fglrx.ko fails because of backported GPL-only
'pci_ignore_hotplug'
Once again, I stand in awe of the Ubuntu Dev Team. Thank you very much!
On Wed, Aug 19, 2015 at 4:40 PM, Francisco Fernandez
ffernandezzab...@gmail.com wrote:
Thak you. Works for me too.
--
You received this bug notification because you are subscribed to a
duplicate bug report (1486132).
Thank you, fglrx is now working for me.
Am 20. August 2015 02:04:09 MESZ, schrieb Patrick Carroll
patrick.carr...@gmail.com:
Once again, I stand in awe of the Ubuntu Dev Team. Thank you very much!
On Wed, Aug 19, 2015 at 4:40 PM, Francisco Fernandez
ffernandezzab...@gmail.com wrote:
Thak
resolved thanxs
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU request: fglrx.ko fails because of backported GPL-only
'pci_ignore_hotplug' symbol
Status
works OK.
Thanks !
2015-08-19 7:36 GMT-03:00 ferariu napoleon darks2...@gmail.com:
resolved thanxs
--
You received this bug notification because you are subscribed to a
duplicate bug report (1484901).
https://bugs.launchpad.net/bugs/1479913
Title:
SRU request: fglrx.ko fails because
I updated to the 3.19.0-26 kernel today and the fglrx-core package
failed to install when dkms tried to install it. Switching to the fglx
packages here in the proposed branch solved my issue. It would seem that
these packages need to be promoted from the proposed branch since others
will have
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU request: fglrx.ko fails because of
This bug was fixed in the package fglrx-installer-updates -
2:15.200-0ubuntu4.2
---
fglrx-installer-updates (2:15.200-0ubuntu4.2) vivid-proposed; urgency=medium
* debian/dkms.conf.in,
debian/dkms/patches/buildfix_kernel_4.0.patch,
This bug was fixed in the package fglrx-installer - 2:15.200-0ubuntu4.2
---
fglrx-installer (2:15.200-0ubuntu4.2) vivid-proposed; urgency=medium
* debian/dkms.conf.in,
debian/dkms/patches/buildfix_kernel_4.0.patch,
debian/dkms/patches/buildfix_kernel_4.1.patch,
This bug was fixed in the package fglrx-installer-updates -
2:15.200-0ubuntu0.5
---
fglrx-installer-updates (2:15.200-0ubuntu0.5) trusty-proposed; urgency=medium
* debian/dkms.conf.in,
debian/dkms/patches/buildfix_kernel_4.0.patch,
This bug was fixed in the package fglrx-installer - 2:15.200-0ubuntu0.5
---
fglrx-installer (2:15.200-0ubuntu0.5) trusty-proposed; urgency=medium
* debian/dkms.conf.in,
debian/dkms/patches/buildfix_kernel_4.0.patch,
debian/dkms/patches/buildfix_kernel_4.1.patch,
Same problem here - please promote those packages quickly.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU request: fglrx.ko fails because of backported
Hello drizzle, or anyone else affected,
Accepted fglrx-installer-updates into vivid-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/fglrx-installer-updates/2:15.200-0ubuntu4.2 in a few hours, and then in
the -proposed repository.
Please help us by
Hello drizzle, or anyone else affected,
Accepted fglrx-installer into vivid-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/fglrx-
installer/2:15.200-0ubuntu4.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
2:15.200-0ubuntu0.5
#verification-done
Building initial module for 3.19.0-26-generic
Done.
Building initial module for 3.19.0-27-generic
Done.
Thank you!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
** Changed in: fglrx-installer (Ubuntu Trusty)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU request: fglrx.ko
Hello drizzle, or anyone else affected,
Accepted fglrx-installer-updates into trusty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/fglrx-installer-updates/2:15.200-0ubuntu0.5 in a few hours, and then in
the -proposed repository.
Please help us by
Thanks - this is now fixed for me.
Still hard to understand how 2 kernels have come out over a week with this bug
which must have effected thousands of users. Novice users who do not know how
to boot to a previous kernel now have a bricked installation and may never
return to linux. Surely
2:15.200-0ubuntu4.2
#verification-done
https://launchpad.net/ubuntu/+source/fglrx-installer-
updates/2:15.200-0ubuntu4.2
Building initial module for 3.19.0-26-generic
Done.
Finally, it works again.
--
You received this bug notification because you are a member of Desktop
Packages, which is
fix.diff Edit (395 bytes, text/plain)
mkdir catalyst15.7 cd catalyst15.7
apt-get download fglrx-core
dpkg-deb -R fglrx-core_2%3a15.200-0ubuntu4.1_amd64.deb fglrx-core
patch fglrx-core/usr/src/fglrx-core-15.200/kcl_acpi.c fix.diff
dpkg-deb -b fglrx-core
2:15.200-0ubuntu4.2
#verification-done
The build succeeds now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU request: fglrx.ko fails because of
#verification-done
updated fglrx from -proposed Worked for me on 15.04
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU request: fglrx.ko fails because of
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 Desktop
Packages, which is subscribed to fglrx-installer
This morning's 15.04 updates broke two of my machines as well. After
much hair-pulling I found this bug report.
Enabling 'proposed' and updating to the kernel contained therein, or
switching to the -15 kernel is enough to get the driver to build.
However, in both cases, attempting to enable
Confirmed, enabling proposed repositories, the problem is solved.
Xubuntu 15.04, fglrx.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU request: fglrx.ko
However, in both cases, attempting to enable multi-screen mode via
amdcccle (with screen 1 right of screen 2) causes X to crash severely,
as soon as you hit OK or Apply.
This is the screen setup I have and so is probably the reason that my
system hangs, solid, right at the login screen, when I
I know this may be an useless comment, but I managed to get here only
when I selected another kernel and found fglrx working.
I found weird Xorg log, found weird DKMS module build log (yes, why
doesn't APT get an error on building? We could notice the disaster far,
far earlier!), selected to let
#verification-done
updated from proposed to fglrx-updates 2:15.200-0ubuntu0.5 worked for me
on 14.04.3
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU
** Changed in: fglrx-installer (Ubuntu)
Assignee: ferariu napoleon (darks2810) = Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1479913
2:15.200-0ubuntu4.2 fixed it for me
On a side note, on my system (Xubuntu 15.04, Radeon HD 5670), this bug
did not cause any bricking: X went up even without fglrx drivers.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer
Hi,
I've been following this all day and helping to collect up the
duplicates, but still haven't fixed the problem; in fact, it's gotten
worse since I enabled the Proposed repository and upgraded:
Before, I was getting the login screen, but getting bounced back as soon
as I entered the password,
Well, the new FGLRX is only in proposed, so most users are still affected. The
only sane option in my point of view would be to release a new kernel without
the patch that broke things originally.
Don't forget that the fix here does nothing for people that installed FGLRX
directly from the AMD
I normaly log-in wthout username and password but now the screen is
everytime comming back to ask my log-in code how can I manage this?
Verzonden met Windows Mail
Van: Nicolas Delvaux
Verzonden: dinsdag 18 augustus 2015 16:11
Aan: Marius van Harten
Well, the new FGLRX is only
Proposed updates fixed this for me in Kubuntu, but I also had to re-
enable OpenGL in System Preferences Screen and Monitor Compositor.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
To add to my comment #35 above:
I use the Proposed Updates (to help with bugs) so don't known how the
main branch has been effected. As the default driver didn't work on my
A10 machine I had to install fglrx from the terminal (ctl+alt+f1) at
initial install. Since this bug I have had to boot back
I believe I just ran into this on my A10 system. I've went ahead and
rolled back to linux-3.19.0-25 but I'm not sure why -26 was even pushed
out if it was known to have issues...
FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol
'pci_ignore_hotplug'
I'm pretty new to Linux. I'm learning my way around but 3.19-0.25 worked
great for me on 14.04 installing .26 gives me fglrx core errors along
with a login loop. I'm glad I learned how to use grub and go back.
--
You received this bug notification because you are a member of Desktop
Packages,
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 Desktop
Packages, which is subscribed to
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 Desktop
** Changed in: fglrx-installer (Ubuntu)
Assignee: Alberto Milone (albertomilone) = (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU
To confirm, I just checked; I definitely have 2:15.200-0ubuntu4.2
installed:
term.log
...
fglrx:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.19.0-25-generic/updates/dkms/
depmod
** Changed in: fglrx-installer (Ubuntu)
Assignee: (unassigned) = ferariu napoleon (darks2810)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU request:
Kernel 3.19.0-26.28 was pushed as a security update to all Ubuntu users today
(it is no longer in the, disabled by default, proposed repository).
This means all FGLRX users on Vivid (and those that installed 14.04.2) will
lose their graphical environment as soon as they reboot.
The only
Maybe this is a stupid question, but why is a DKMS failure not
considered fatal enough to prevent the kernel upgrade from taking
place, or at least updating grub?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
today I upgraded 14.04.3 (apt-get dist-upgrade)
and I'm getting bug again.
last time I fixed it by patching fglrx by
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1479913/comments/16
manual.
at this time I downgrade fglrx to patched version.
--
You received this bug
68 matches
Mail list logo
