On Freitag 06 November 2009, Harry Putnam wrote:
> walt writes:
> > One caution there -- newer computer hardware demands a great deal of
> > power, and older power supplies may not be up to the task. Don't try
> > to squeak by with a wimpy power supply.
> >
> >> I thought maybe a mobo bundle would
On Friday 06 November 2009 09:18:14 Nagatoro wrote:
> On Thursday 05 November 2009 22.40.47 Alan McKinnon wrote:
> > Has anyone successfully built kde-4.3.73 from kde-testing overlays with
> > USE=semantic-desktop? If so, how did you manage?
> >
> > I get about 8 build failures with the flag set, d
Mick schrieb:
> On Wednesday 04 November 2009 22:38:40 Willie Wong wrote:
>> As you can see, keycodes 174 annd 176 are volumes up and down,
>> 160 is the mute button, 164, 162 are stop and play/pause, 144
>> and 153 are REW and FF, which I doubled up with meta keys to
>> get other features. 223
On 5 Nov, walt wrote:
> Helmut Jarausch wrote:
>> Hi,
>>
>> I've unmerged dev-java/blackdown-jdk
>> and re-emerged virtual/jdk virtual/jre app-admin/eselect
>> but
>> eselect java-vm list
>> still shows
>> [1] blackdown-jdk-1.4.2
>>
>>
>> Hwo to get rid of that entry?
>
> Maybe an old sy
Hi,
I'm not using KDE4 as my window manager (just icewm).
But I'm using some KDE applications like 'okular'.
Once I've used it (or other KDE applications) I get the
following messages several times (with some delay)
kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kbuildsycoca4.so
(18573)/ KS
Mark Knecht wrote:
> In this case I will investigate doing the cdda2wav portion on a
> different machine and then writing it on the machine I have been using
> as that drive seems to be the only one that will still generate CDs
> playable in my car.
>
> I'm not completely convinced this is a driv
With the required driver atl1c in the kernel, my toy Horace had no trouble
logging in to my ISP & actually downloaded a file for an emerge.
Can anyone who uses one of these machine advise me
how far the usual services are relevant for a netbook ?
-- hald (+dbus) vixie-cron slocate run on my de
alex ponomarev wrote:
If you're talking about console, try to look trough output of "dmesg | grep
'usb' " there must be something about your USB HID keyboard, may be some
errors about it. Also look through "lsusb", is your keyboard mentioned here?
Sorry, I forgot to say, I'm talking about conso
8 matches
Mail list logo
