I'm also experiencing the memory leak. It takes about 30-40mins to use
up 700MB of RES memory. At that point the computer becomes completely
unresponsive. I think the problem is neither Qt 4.7 or libtorrent
because pmap shows that the memory that is leaking is anonymous.
a2a0 02004
On 08/06/2010 03:59 AM, Janos Zsitvai wrote:
Actually, it seems that a symlink from clang to clang++ would be all
that's needed. (And to c++-analyzer fromccc-analyzer.)
I can confirm that the symlink to clang++ works. It compiled my c++
files without library errors.
Can this be added to the
Anton Korobeynikov 584...@bugs.launchpad.net wrote on 5 Aug 2010, 01:29
PM:
Subject: [Bug 584759] Re: clang package should also contain clang++
I believe that C++ frontend is definitely included. clang -x c++ is
your friend.
That didn't work, it still gives the same error I've seen when I built
Public bug reported:
Binary package hint: clang
The packages summary for the clang package currently reads:
Clang project is a new C, C++, Objective C and Objective C++ front-end
for the LLVM compiler. Some of its goals include the following:
.
*A single unified parser for C,
I tested the linux-image-2.6.27-2-generic kernel, but on _hardy_. No blank
screen problems or garbled splash screen.
I'm not ready to do an upgrade to ibex for a full test until at least the first
beta (can't loose data or time as I use my computer daily).
--
Blank screen when using usplash
Well, if the Ubuntu kernel hasn't diverged that far from the mainline
.27-rc kernel then the problem should be fixed. The blank screen bug is
only the result of a broken implementation of HR-Tick that is only in
2.6.{25,26} (at least as far as I know). HR-Tick was fixed when the
merge window
It seems that the commit that went into 2.6.27 can't be backported to
.26. But, hrtick, what is causing the problem, can be disabled.
The patch to disable hrtick that applies on a vanila 2.6.26.2 kernel and
should also apply to Ubuntu's kernel is below. That patch (or similar)
should go into
This seems similar to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/258381.
And that is a kernel regression/bug in hrtimer.
Does the boot splash display at all? Or does it go blank when entering
graphical mode,
Or lock up (and/or go blank) midway thruough the boot splash.
I regularly
Public bug reported:
Binary package hint: linux-image-2.6.26-5-generic
The kernel that is going into Ubuntu 8.10 has a bug that (as far as I
know hasn't been fixed in upstream 2.6.26). The problem is that when
using a 2.6.25 or 2.6.26 kernel the screen blanks out when entering
graphical mode
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
Blank screen when using usplash and kernel = 2.6.25
https://bugs.launchpad.net/bugs/258381
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Is there some current workaround for this regression? I have a friend
that I installed Ubuntu on his computer and he uses my nfs server. It's
easy for him to right click and mount the drive from nautilus (he's
using 7.10). But if he upgrades to 8.4, he would have to use the cli to
mount the drive.
I guess I wasn't clear enough in my last message. I already solved my
problem - sorry about that.
The problem was three fold:
1. The hidden .nvidia* file: causing the nvidia driver not to load because it
thought it had the wrong version. Removing the file fixed the problem.
2. XGL: was
It seems the problem was two fold:
There was a hidden in /lib/linux-restricted-modules/ that confused Xorg byt
thinking it had the wrong driver version.
I ran: sudo rm /lib/linux-restricted-modules/.nvidia* and it fixed that problem.
The second problem was that GLX and Direct Rendering wouldn't
** Summary changed:
- Broken Nvidia driver after upgrade to Gusty (7.10)
+ [Gusty] Broken Nvidia driver after upgrade to Gusty (7.10)
--
[Gusty] Broken Nvidia driver after upgrade to Gusty (7.10)
https://bugs.launchpad.net/bugs/138933
You received this bug notification because you are a member
The GeForce4 card is supported by the nvidia-glx driver (not the legacy
driver). run:
sudo apt-get remove nvidia-glx-legacy; sudo apt-get install nvidia-glx
Also what might be the problem is a hidden file in
/lib/linux-restricted-modules/ try running:
sudo rm
I seem to be having the same problem. I reported this as:
bug #138933: [Gusty] Broken Nvidia driver after upgrade to Gusty (7.10)
What might be the problem is a hidden file in /lib/linux-restricted-modules/
try running:
sudo rm /lib/linux-restricted-modules/.nvidia*
Also see these bug reports
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
Status: New = Confirmed
--
Broken Nvidia driver after upgrade to Gusty (7.10)
https://bugs.launchpad.net/bugs/138933
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Attachment added: Xorg.log using Nvidia driver
http://launchpadlibrarian.net/9234944/Xorg.0.log.nvidia
--
Broken Nvidia driver after upgrade to Gusty (7.10)
https://bugs.launchpad.net/bugs/138933
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Attachment added: xorg.conf using Nvidia driver
http://launchpadlibrarian.net/9235406/xorg.conf.nvidia
--
Broken Nvidia driver after upgrade to Gusty (7.10)
https://bugs.launchpad.net/bugs/138933
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Attachment added: Xorg.log using nv driver
http://launchpadlibrarian.net/9235414/Xorg.0.log.nv
--
Broken Nvidia driver after upgrade to Gusty (7.10)
https://bugs.launchpad.net/bugs/138933
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Attachment added: xorg.conf using nv driver
http://launchpadlibrarian.net/9235422/xorg.conf.nv
--
Broken Nvidia driver after upgrade to Gusty (7.10)
https://bugs.launchpad.net/bugs/138933
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Attachment added: lspci output
http://launchpadlibrarian.net/9235436/lspci.txt
--
Broken Nvidia driver after upgrade to Gusty (7.10)
https://bugs.launchpad.net/bugs/138933
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Public bug reported:
Binary package hint: nvidia-glx
I just upgraded to Gusty from Fiesty a few days ago. Now, the Nvidia
driver doesn't work (it worked in Fiesty)! In the restricted-manager I
selected nvidia-glx (I have a Nvidia GeForce4 MX 440) and restarted,
but the X server couldn't load and
** Attachment added: dmesg with nvidia driver
http://launchpadlibrarian.net/9235520/dmesg.nvidia.txt
--
Broken Nvidia driver after upgrade to Gusty (7.10)
https://bugs.launchpad.net/bugs/138933
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Attachment added: dmesg with nv driver
http://launchpadlibrarian.net/9235527/dmesg.nv.txt
--
Broken Nvidia driver after upgrade to Gusty (7.10)
https://bugs.launchpad.net/bugs/138933
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Xorg still works with the nv driver.
I did notice _very_ interesting lines in dmesg when using the nvidia
driver:
[ 43.196323] nvidia: module license 'NVIDIA' taints kernel.
[ 43.270935] NVRM: The NVIDIA GeForce4 MX 440 GPU installed in this system is
[ 43.270941] NVRM: supported through
I had the same problem after upgrading to Gusty. dmesg was full of
nothing but:
device-mapper: ioctl: error adding target to table
device-mapper: table: 254:1: linear: dm-linear: Device lookup failed
And udevd was using 70%CPU!
Removing all *evms* pakages fixed the problem. Hopefully the
I had the same problem after upgrading to Gusty. dmesg was full of
nothing but:
device-mapper: ioctl: error adding target to table
device-mapper: table: 254:1: linear: dm-linear: Device lookup failed
And udevd was using 70%CPU!
Removing all *evms* pakages fixed the problem. Hopefully the
I've been having the same error message, and my Intel IPW3945 Wireless
adapter would be extremely hard to get working. I would have to modprobe
and other manual things, and still it wouldn't work.
I'm using a custom 2.6.23-rc3 git kernel (kernel.org). The module
(ipw3945) would load, and so would
I compiled intel_rng as a module, but still get the error message and
still having trouble getting wireless to work. I have to run this script
after I'm logged-in to connect to a network, else it only shows
connections but not able to connect:
sudo su
modprobe -r ipw3945
killall ipw3945d
I changed some BIOS settings, hoping to make the system more stable. I used the
recommended most stable options.
After changing the BIOS I no longer get a garbled screen when using the 3D
driver (at least that I can remember?). Instead the screen only goes out of
sync or just black.
I also
** Attachment added: xorg.conf.feistyfinal
http://librarian.launchpad.net/7388779/xorg.conf.feistyfinal
--
xserver bug: random lockups, blank/garbled screen, resolution changes
https://bugs.launchpad.net/bugs/93925
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: Xorg.0.log.feistyfinal
http://librarian.launchpad.net/7388780/Xorg.0.log.feistyfinal
--
xserver bug: random lockups, blank/garbled screen, resolution changes
https://bugs.launchpad.net/bugs/93925
You received this bug notification because you are a member of Ubuntu
Bugs,
I've done a fresh install of Kubuntu 7.4, yet still I'm having the same
problem.
My motherboard has a build in graphic card (Trident), but I'm using (and
want to use) the Radeon 9250 SE graphic card. Also the Radeon card has
support for running dual displays. I'm using the VGA output, not the DVI
I also have experienced a crackling of the sound in Amarok. Although, it
happens with mp3s that have been ripped.
I'm using Feisty and my sound card is a VIA Technologies, Inc. VT82C686
AC97.
I would think it's an error of amarok-xine like you said.
--
Crackling sound during MP3 podcast
Ok, I removed all the other modes. I thought it was working until the
screen went out of sync, and because I removed all the modes I wasn't
able to change modes, although after a few minuets it went back to
normal. Also, a little while latter it did black out on me, and I
couldn't use the
Ok, I ran memtest for almost 2hrs, and it did 8 full passes. Still it
reported 0 errors. Are there any other hardware tests? Because
apparently my ram has no problems.
I was able to copy the xorg.conf file from a SystemRescue LiveCD I had.
It seems not to crash, but I get this error:
Error:
Public bug reported:
Just at random the computer will either:
1) Loose the correct resolution: the monitor will read out of sync and I'll
have to cycle through the resolutions with ctrl+alt++
2) Garbled blocky colors: the screen will display a weird blocky color pattern,
and usually the
I've attached the following outputs/files into a tar.bz2 file:
lspci -vv
cat /proc/mtrr
dmesg
xorg.conf
Xorg.0.log
** Attachment added: bzip tarball of important files
http://librarian.launchpad.net/6872038/system-info.tar.bz2
--
xserver bug: random lockups, blank/garbled screen, resolution
** Changed in: xorg (Ubuntu)
Sourcepackagename: xorg = xserver-xorg-video-ati
--
xserver bug: random lockups, blank/garbled screen, resolution changes
https://launchpad.net/bugs/93925
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Forgot to also include: glxinfo -t -l
** Attachment added: glxinfo output
http://librarian.launchpad.net/6872121/glxinfo.txt
--
xserver bug: random lockups, blank/garbled screen, resolution changes
https://launchpad.net/bugs/93925
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Description changed:
Just at random the computer will either:
1) Loose the correct resolution: the monitor will read out of sync and I'll
have to cycle through the resolutions with ctrl+alt++
2) Garbled blocky colors: the screen will display a weird blocky color
pattern, and usually
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Unconfirmed = Confirmed
--
xserver bug: random lockups, blank/garbled screen, resolution changes
https://launchpad.net/bugs/93925
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
GRR!!! Ok, it keeps happening (5+ times in the last 30min)! And I'm
trying to get work done. I've had to hard-reboot many times.
Most of the time what happens is the screen goes blank (no out of sync
warning), and the keyboard is unresponsive. If I can ssh in, I see that
X is using 99% cpu. I try
44 matches
Mail list logo
