Having the same problem.
Best guess is that nvidia-glx and nvidia-glx-new are stepping on each
others toes. Doesn't affect performance but shows up as a residual
config.
--
package nvidia-glx None failed to install/upgrade: subprocess post-removal
script returned error exit status 2
https://bug
I do not have desktop effects enabled and have the problem.
On 4/24/07, muj0 <[EMAIL PROTECTED]> wrote:
>
> disabling desktop effects seems to have solved the problem for me as
> well. Should this be filed against desktop effects?
>
> --
> log out or switch user results in crash
> https://bugs.lau
*** This bug is a duplicate of bug 36252 ***
https://bugs.launchpad.net/bugs/36252
I hope this offers a clue as to what's going on:
I have two external drives, one ejects properly, the other does not.
The smaller drive is set up as two EXT3 partitions, both under 100GB. This
ejects without
*** This bug is a duplicate of bug 36252 ***
https://bugs.launchpad.net/bugs/36252
The workaround noted above did not fix the problem for me. Having the
problem on a 500gb usb drive.
In case there's any confusion as to whether this is a bug or a
"feature", I assure you that that not being abl
I'll second using Wicd as a temporary fix.
On 4/23/07, bedfojo <[EMAIL PROTECTED]> wrote:
>
> I found a workaround: compile and install the latest version of
> ndiswrapper (1.42) from its website. Use wicd instead of network-
> manager. All works perfectly now.
>
> --
> NetworkManager finds wirele
I can confirm the black screen on log out using the resricted driver
with an ati radeon xpress 200m.
Editing /etc/X11/gdm/gdm.conf so AlwaysRestartServer=true is a valid
workaround. I cannot speak to issues with hibernation but can also
second the fact that this is a bug that was introduced some t
I think it's safe to say that this bug can now be closed.
Not sure what fixed it or even when, but the memory leak is gone now. Thanks
for all of your efforts.
On 3/26/07, Kevin Kubasik <[EMAIL PROTECTED]> wrote:
>
> Can we confirm its still an issue in the beta?
>
> ** Changed in: beagle (Ubunt
It APPEARS no longer to be an issue over the last week or so.
I'd feel more comfortable if I can keep an eye on it for another few days
before declaring it a squashed bug.
Thanks.
On 3/26/07, Kevin Kubasik <[EMAIL PROTECTED]> wrote:
>
> Can we confirm its still an issue in the beta?
>
> ** Chang
After running the supplied command line, Network Manager attached to the
wireless network without resorting to hardware buttons.
Is there anything I can do or test to aid in your ndiswrapper /
wpa_supplicant investigation?
- Jonathan
On 3/8/07, Scott Robinson <[EMAIL PROTECTED]> wrote:
>
> Inste
beagled, by itself, gives the same memory leak.
On 2/28/07, dBera <[EMAIL PROTECTED]> wrote:
>
> No, the attachment is somehow getting attached.
>
> Also I meant, if you run
> $ beagled
> (i.e. enable all backends)
> do you still get the memory spike ?
> and the same question for
> $ beagled --ba
I was trying to attach the file when replying via email. This time I
will attach the logs through the web page.
I am trying beagled without arguments now and will get back to you.
Looking through the logs I noticed that in addition to the backends I
ran in earlier tests, beagled reports starting
>> When you run all the backends, you still get the memory problem ?
I ran each backend separately and did not encounter the memory problem.
I attached the log file with my last message and am attaching it again with
this one. If it is not getting through for some reason, please let me know.
On
Haven't had any luck narrowing the culprits; when I run only one of the 5
backends you specified at a time the memory bug doesn't come up.
I've attached a copy of the most current log file. Looking through it, I
noticed that it complained about being unable to find EvolutionDataServer. I
did doubl
Will do and get back to you. Thanks for the help. You guys do a huge service
for all of us.
--
beagled uses >250 Megs RAM when Idle
https://launchpad.net/bugs/87198
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Correction: "Memory: 3104.4" should read "304.4"
--
beagled uses >250 Megs RAM when Idle
https://launchpad.net/bugs/87198
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
After 5 1/2 hours of light, intermittent usage beagled is up to 305
megs.
Virtual: 381.8
Resident: 315.6
Writable: 304.4
Shared: 11.2
Memory: 3104.4
I won't bother including the output for beagle-info as it looks pretty much
identical to what I've previously posted.
Please let me kno
In the 3 hours and 15 minutes since I booted this morning, I've seen beagled
memory usage slowly inch it's way up to the following:
Virtual: 249.2
Resident: 193.7
Writable: 182.8
Shared: 11.3
Memory: 182.8
I haven't noticed any ties between specific apps or activities and a climb
in m
The 280 MB number was taken from the "Memory" column of the System Monitor
utility.
I have rebooted to find beagled using 35 megs at first. In the last hour of
normal system usage I've watched that number climb up to 84 megs. I am
keeping a close eye on the number now to see if I can determine wha
Public bug reported:
Binary package hint: beagle
Appears to be different than bug # 33341 (now closed) and #69752
(dealing with spikes).
Using Feisty with beagle version 0.2.16-0ubuntu4.
I am not seeing heavy CPU and memory spikes as with previous releases,
but a steady and very high RAM requir
Should have mentioned: This is on Feisty.
--
NetworkManager finds wireless network, does not connect
https://launchpad.net/bugs/85468
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Starting from a cold boot, Network Manager finds available wireless
networks but does not automatically connect.
Manually choosing a wireless network via NetworkManager results in an
unsuccessful attempt to connect.
In order to connect, the wireless card must be turned off t
Thank you! It works again.
On 2/13/07, Andrew Ash <[EMAIL PROTECTED]> wrote:
>
> Could you please try again with version 1.4.5-0ubuntu4 ?
>
> It looks to me from
>
> http://archive.ubuntu.com/ubuntu/pool/main/a/amarok/amarok_1.4.5-0ubuntu4.diff.gz
> that --with-libmtp has been enabled now.
>
> Tha
Public bug reported:
Binary package hint: amarok
mtp-device (PlaysForSure) support had been in Amarok but was removed
during a recent 1.4.5 build.
Requires libmtp2.
./configure --with-libnjb --with-libmtp --with-libgpod --prefix=`kde-
config --prefix`
Required for Creative Zen and others...
*
This bug has been preventing me from using Edgy. I propose that the
importance is upgraded to CRITICAL. This needs to be fixed before Edgy
ships.
The bcm43xx/fwcutter solution is not a replacement for a working
ndiswrapper. That solution has it's own set of bugs and problems.
--
ndiswrapper in e
24 matches
Mail list logo
