Public bug reported:
Update of the package fglrx failed
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fglrx-core 2:15.200-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
It happens really often to me, and I see:
compiz[2686]: segfault at 10 ip 7f1d60b08a23 sp 7fff50cfa560
error 4 in libgdk-3.so.0.200.0[7f1d60acb000+77000]
in kern.log
Jan 17 19:55:58 luna gnome-session[2603]: Gdk-WARNING: The program
'gnome-session' received an X Window System error.#01
Hi Gursimran,
Thanks so much for the reply. It ultimately turned out that the bug was a
hardware issue!
I really appreciate all your work for the ubuntu project in general.
Thanks a lot,
Tomás
2010/11/4 Gursimran singh Mohar
> Hi Thomas
> Thank you for taking the time to report this b
** Attachment added: "lshal"
http://launchpadlibrarian.net/39806201/lshal
--
Touchpad does not work after recent update
https://bugs.launchpad.net/bugs/528214
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in ubuntu
Public bug reported:
Binary package hint: xserver-xorg-input-synaptics
bios-version:V1.03
system-manufacturer:eMachines
system-product-name:eMachines D620
system-version:0100
Linux tomas-laptop 2.6.31-19-generic #56-Ubuntu SMP Thu Jan 28 01:26:53
UTC 2010 i686 GNU/Linux
Ubuntu 2.6.31-19.56-gene
Please someone confirm Morten's info. 3d Support for ++hd3xxx in the
kernel? no fglrx?
that's too good to be true. and too big to be unnoticed until now?
On Thu, Feb 25, 2010 at 2:54 PM, svaens wrote:
> @Morten Frisch
>
> Can it be true! A real fix in time for lucid! That will make me very
> hap
@flaim, thanks for the tip, but it seems that this is the same fix
we've been discussing for months in this bug, that has been now
supplemented with a more elegant version by felix kuelig, and that has
serious memory leak problems.
On Wed, Nov 25, 2009 at 7:57 AM, fllaim wrote:
> I've found a fi
s you were refering to?
On Sat, Nov 14, 2009 at 10:39 AM, Vancouverite wrote:
> @ Prabhakar Nagral, did this work for you?
>
> @ José Tomás Atria
>
> I can confirm that switching off fglrx power saving takes care of the
> problem for me. Further I have found that it only affects me i
do we have confirmation for this? ie, is the memory leak associated to
fglrx power saving?
On Fri, Nov 13, 2009 at 3:43 AM, Prabhakar Nagral wrote:
> thanks much..found it!
>
> Regards,
> -P
>
> --- On Fri, 13/11/09, Vancouverite wrote:
>
> From: Vancouverite
> Subject: [Bug 351186] Re: [M76] [
On Tue, Nov 10, 2009 at 3:31 PM, svaens wrote:
> So, it should be possible to achieve fast (normal) unminimizing AND no
> memory leak. And that is what vancouverite has achieved?
As long as you don't use fglrx and stick to 2d acceleration only, it
appears so, yes.
But then again, the origin of t
On Tue, Nov 10, 2009 at 2:44 PM, svaens wrote:
> So what did you do differently to now have no memory leak?
>
> On Wed, Nov 11, 2009 at 5:22 AM, Vancouverite wrote:
>>
>> I have now reverted to radeon and the current x-server-core that ships
>> with Karmic (2:1.6.4-2ubuntu4) and have had no increa
I agree that felix's patch is superior (apparently the empty buffer's
load faster than the ones containing random memory contents, besides
the already discussed security and aestethics aspects), but at least
for me, i'm experiencing memory leaks with both alternatives.
Incidentally, i seem to obse
in my experience, Felxi Kuehling's patch has performed better on this
machine. It looks prettier too :)
On Mon, Oct 26, 2009 at 2:18 PM, Malaria wrote:
> Which one is the better patch ?
>
> However, it would be great if those ppa can be maintain up to date (sync
> with the legacy xorg package).
>
rmmm. I would have thought that incomplete means that there's not
enough information to further locate the problem and hence the bug is
impossible to work on.
On Wed, Oct 14, 2009 at 5:17 PM, Aisthesis wrote:
> Incomplete because, in order to confirm that the patch is acceptable to
> be included
ehem, i don't know who is supposed to decide this, but i think that
such a visible usability bug on one of the three typical
configurations (ATI's fglrx) will be a major showstopper for many new
users.
We need to find a solution, any solution, that does not require
googling and installing some dar
ppa rep with the patch for karmic plis?
On Wed, Oct 7, 2009 at 4:45 AM, svaens wrote:
> deb package?
> What deb package, and what is the link?
> Good for jaunty? Or only Karmic ?
>
> thanks!
>
> On Wed, Oct 7, 2009 at 7:35 PM, Xavier wrote:
>
>> Downloaded deb packages from launchpad resource. I
Apparently this bug has been fixed in Catalyst version 9.8. Any chance
of backporting the driver into jaunty?
** Changed in: fglrx-installer (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: fglrx-installer (Ubuntu)
Status: Fix Released => Confirmed
--
[HD 2600/HD 3670/HD
i've been using the patched xorg, and xorg reports 3% memory usage
after 8 hours of uptime (just updated today). I'll check back in the
morning.
There are some weird artifacts for a fraction of a second when drawing
windows, though. Still, better than those horrible delays.
On Mon, Sep 28, 2009 a
Hey Timothy, could you please post the contents of your xorg.conf file
to see what did ati-config put in there? actually, if you have a copy
of your old xorg.conf, a diff between the two files would be extremely
useful.
thanks!
On Tue, Aug 18, 2009 at 11:42 AM, tmokeefe wrote:
> Some good news on
I have tested my idea, by manually disabling composite immediately
before suspend and re enabling it immediately after resume, and it works
(ie, it doesn't hang).
I have written the script to do it (dbus is a pleasure!), but i have
been looking for weeks for some way to put it in KDE's suspend/res
i was just thinking... if the resume fails when Desktop Effects are
enabled on suspend, wouldn't it be possible, as a workaround until a
proper fix is released, to execute a script that disables desktop
effects immediately before suspension, and re-enables them immediately
after resume?
i'll see i
@aidar: it's a completely different issue, this is with the propietary
fglrx driver, gentoo's is with mesa, this affects kwin when resuming
from suspension to memory, that one affects plasma, this is worked
around by changing to Xrender compositing, that one is fixed by
resetting the plasma conf.
I can confirm this issue with a HD 4650 card on a VAIO VGN-FW480j, using
kde 4.2.98 (kde 4.3 RC 3).
** Summary changed:
- [HD 3670] fglrx + desktop effects = failed resume
+ [HD 2600/HD 3670/HD 4650/ Others?] fglrx + Kwin with OpenGL desktop effects =
failed resume
--
[HD 2600/HD 3670/HD 4650/
is there any way to check the upgrade path to determine what else was
updated on april 3rd?
Because we are certain that the clean vanilla jaunty install doesn't
have this issue, right?
right?
On Thu, Jun 4, 2009 at 5:21 PM, zwaldowski wrote:
> I still maintain that the version available in Jaun
IMHO, please stop with all the discussion about what should have been
done, or if linux is ready for the desktop and whatnot.
We have a stable release that is recommended as stable to users. ALL
users.
this stable release has a known problem with intel drivers, the
problem was reported as a bug a
+1 at Bernhard. I have been following this bug closely, and i read the
whole 300+ comments, but i got lost in regards as to which packages
are affected, and what versions should introduce fixes, apart from the
backported xserver-xorg-video-intel mentioned above.
@Bryce: could you give us a little
26 matches
Mail list logo
