I have sandbox-1.2.18.1

Have tried:

FEATURES="-sandbox" emerge -1 sandbox


and can still not emerge nvidia-drivers or other kernel modules like vmware due to the access violation.

Portage 2.1.2_pre3-r9 (default-linux/x86/2006.1, gcc-3.4.6, glibc-2.5-r0, 2.6.18-rc4 i686 ...

ditto, I have tried both 9626 and 8776 of nvidia-drivers and it also fails to compile a module for vmware with the same access violation message.

I have an nvidia Quadro FX card running the binary nvidia drivers and crack-attack sometimes just exits like you describe, however, not normally after 10 seconds, more like several minutes if it happens at all.

Ah, you already seem to be on that version of portage. Sorry I couldn't be more help.

I ran into this problem. I did an emerge sync in case it was an error in the ebuild which had been fixed, I got some new packages, none of which should have effected kdelibs. I noticed that there was a portage update to do though, which I took, then kdelibs compiled ok. That is with portage-2.1.1 ...

Yet another bug Sun are completely ignoring although the rest of the ones I've submitted are for JWSDP. *sigh*

Yeah, I'm pretty sure that the application has the choice of whether to use dmix or not and I think by default, it must be on these days. However, if the applet were to initalise it's sound explicitly it's possible it might have been turned off. I might investigate an open source applet that does ...

So it definitely already uses alsa so I didn't really think wrapping it with aOSS would work. And what would I wrap? All of java?

All my apps use dmix and I've even set up OSS dmix, but still the sound in java applets does not respect this, I can only assume that it is using alsa without thje dmix plugin which of course means it can't play sound at the same time as another application (I have no hardware mixing).

Any ideas ...

The source can normally be had in advance from their cvs or whatever so the Gentoo KDE devs can have the ebuilds ready and working when 3.5.1 comes out, which is why they hit the tree, hard masked before the actual release by KDE.

Thanks, that fixed it. I had thought executing the eval line once KDE was running would be enough, I'm not used to having to restart things.

This is really annoying. I can only think that there is something failing between the gpg-agent and KDE.

douglas 13740 0.0 0.0 2152 424 ? Ss 12:05 0:00 gpg-agent --daemon

So it's running, cool, although I've not been asked for my password.

KGpg when started claims that, "The use of GnuPG Agent is ...

If you are using gnucash (or gtk in general I imagine) apps that don't seem to understand unicode.... you can get your old functionality back on an app by app basis. Just set LANG and LC_ALL to be en_GB instead of en_GB.utf8 (In my case) and launch the application as usual. I've used bash aliases to ...

Can anyone explain how exactly to use JDB in kdevelop, I know it is meant to have support for it, but there doesn't seem to be a scrap of configuration and the debugging stuff is all about GDB. How an earth is it meant to be used? Any help would be much appreciated (Although not the kind of help ...

I upgraded to bluez-* 2.18 and the problem went away, I'm suspecting there was some weirdness in my 2.17 install as when I emerged that again, it also worked. Gah.

Cheers for the help.

Puggy

Fat Bastard wrote:I think the internal adapter is also affected. There was a discussion about this on debian's powerpc mailinglist a while back. I'll see if I can find it.

Edit: clickety-click.

That isn't the same issue as back in May 2004 there were only pci bluetooth devices, not usb.

Do you dual boot Gentoo/OS X? Have you upgraded your Bluetooth firmware ? If so then the following cautionary note should apply to both external and internal USB to Bluetooth adapters:
Important : Applying this firmware updater to a D-Link USB to Bluetooth adapter will make it incompatible with ...

In case anyone else actually knows the answer: My bluetooth device doesn't seem to be recognised.
I have: Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 004: ID 05ac:020f Apple Computer, Inc.
Bus 002 Device 003: ID 05ac:1000 Apple Computer, Inc.
Bus 002 Device 001 ...

You just need to emerge sync and then emerge a ~ppc kernel. The easiest way to do this on a one off basis is to . Then of course you'll need to change the symlink and copy your .config across and make oldconfig etc etc.

Puggy

I think you might need a 2.6.11+ kernel to use the atp driver.

Fair enough, I'm sure an ebuild would be welcome. Sticking a make install target in the makefile wouldn't go amiss either, I just did it manually, but that's annoying for most people or I guess some people wouldn't know how.

i dont think it will go into the kernel that fast. it makes a quite buggy impression and the driver also doesnt handle all commands from the hardware by now. But it is a way better solution then the first driver which didnt barely work

I haven't tried it yet, but apparently it emulates a ...

the driver works great. i will post my lsusb later that day because i am under mac osx right now. i will also write an ebuild for that driver . possibly it will go into portage. would be great.

Greetings,

Passi

Thanks for promising to post your usb ids. On the other issue, I imagine that it ...

Could everyone with a new revision powerbook please report back here with the output of (part of usbutils - you may want to update to version 0.71 here) and and whether or not bluetooth is working for you. Alternatively, please please, email me the results at puggy@gentoo.org.

ghostscript-gnu works perfectly though.