We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirm
[This is an automatic notification.]
Hi Konstantin,
This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?
Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
n
** Tags added: karmic
--
fglrx module not loaded, Cannot allocate memory
https://bugs.launchpad.net/bugs/480668
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu
FWIW, I have the same issue with a Radeon Mobility X1400.
--
fglrx module not loaded, Cannot allocate memory
https://bugs.launchpad.net/bugs/480668
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
Looking at the attachments in this bug report, I noticed that
"Xorg.1.log" was flagged as a patch. A patch contains changes to an
Ubuntu package that will resolve a bug, since this was not one I've
unchecked the patch flag for it. In the future keep in mind the
definition of a patch. You can lea
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
