On Sun, 2 Jan 2005 17:15:58 -0500, Jim <lawrence.jim(a)gmail.com> wrote:
> On Sun, 02 Jan 2005 16:49:43 -0500, nix4me <nix4me(a)cfl.rr.com> wrote:
> > Jim wrote:
> > >i installed mplayer to play DVD's and nothing starts
> > >if i go to the shell and type mplayer it gives me a bunch of options.
> > >i would prefer a gui mplayer and help would be nice.
> > >i have installed the fonts, the skins, i don't know how to wrap them together
> > >thanks
> > >
> > >
> > Use the command: gmplayer
> > error report...................snip
> Checking for GUI ... yes
> Error: X11 support required for GUI compilation
> Check "configure.log" if you do not understand why it failed.
> [root@localhost MPlayer-1.0pre6a]#
> i tried that cmd gmplayer
> [root@localhost MPlayer-1.0pre6a]# gmplayer
> bash: gmplayer: command not found
> [root@localhost MPlayer-1.0pre6a]#
> any ideas???
> James Lawrence
> Rochester NY
OK, I'm a usenet junkie. Leafnode (a tiny local news server) sits
between the LAN and the ISP's news server. It does lots of nifty things
in the background and provides an exquisitely simple, yet highly
effective, RegEx filter/killfile.
Maybe it's just me but Linux news clients don't seem to handle posts to
moderated groups very gracefully. When posting to NANAB, for example,
knode sort of hangs until it times out, showing the post as failed and
leaving it in the outbox. With leafnode, that problem is gone (or at
least not visible).
Leafnode is suitable as a stand-alone, to take advantage of the
Anyway (FWIW): http://www.tqmcube.com/leafnode.htm
There are links to the RPM I compiled (the Fedora Extras RPM is
outdated) and a simplified configuration file (the distributed config
seems spectacularly disorganized).
Comments, suggestions, edits, raves and rants are certainly welcome OFF
LIST so that I'll actually read them. List traffic has been rather heavy
* Eliminate Spam: http://www.TQMcube.com/spam_trap.htm
* RBLDNSD HowTo: http://www.TQMcube.com/rbldnsd.htm
* Multi-RBL Check: http://www.TQMcube.com/rblcheck.htm
Me too. Thanks
[mailto:email@example.com] On Behalf Of Erik P. Olsen
Sent: Tuesday, May 17, 2005 5:32 AM
To: Fedora Mailing List
I have a lot of old interesting LPs which I would love to have on CDs.
If somebody knows a way to play an LP into the PC and subsequently burn
it to a CD I am very interested in learning how to do it.
Erik P. Olsen
fedora-list mailing list
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
Once I installed the new firefox 1.0.1 I lost the java runtime
environment I had finally been able to get working with firefox 1.0.
The "About Mozilla Firefox" window says I'm running "Firefox/1.0.1
Fedora/1.0.1-1.3.2". I assume this new version of firefox is using
files from the directory tree that starts /usr/lib/firefox-1.0.1, which
means I need to make a symbolic link (using the ln -s command)
to /usr/lib/firefox-1.0.1/plugins. This is the same procedure I
successfully used before to make the link in
the /usr/lib/firefox-1.0/plugins directory.
For some reason this procedure is not working -- the new link
in /usr/lib/firefox-1.0.1/plugins appears in red instead of blue. I've
tried deleting the link (using rm -r) from both
the /usr/lib/firefox-1.0/plugins and the /usr/lib/firefox-1.0.1/plugins
directories. Although they no longer show up (using ls -al) the link
creation (using ln -s) still gives a non-functioning link. Then when I
do a locate libjavaplugin_oji.so I get --
which seems to be saying the links are still there in both firefox
directories! When I try ls -l on the /usr/lib/firefox-1.0.1/plugins
directory I get:
lrwxrwxrwx 1 root root 20 Mar 6 16:51 libjavaplugin_oji.so ->
flashing in red -- it looks like the link is linking to itself. Or
something.... Any suggestions on how to clean this up or at least to
hack through it further?
I am writing this post to check whether other people is experiencing
problems with displaying the icons of the toolbars of Open Office and
Bluefish when the gtk-qt-engine is active. (I am using FC4 and KDE.)
Thanks in advance,
I'm using an external USB disk, with the USB 2.0 controller being a
PCMCIA card. FC3 installed happily on this disk, alas it didn't boot
quite as happily from it. (Of course, I have grub on a /boot partition
of the internal IDE drive.)
Earlier Fedora versions came with the pcinitrd script of pcmcia-cs which
facilitated the creation of initrds for booting with PCMCIA, FC3 doesn't
have it. Documentation one gets from googling mostly refers to 2.4
kernels, where one has to hack /linuxrc to include cardmgr...
After experimenting a while with hacking /linuxrc and /init, I found out
that mkinitrd (which comes with FC3) already does the job, as long as
one is aware of the timing problem: PCMCIA and USB need some time to
come up before devices will be recognized.
Also, minitrd's option --with-usb always puts usb modules before modules
you specify with --with=, which is a bad thing in this case. So, just
put the usb modules after the pcmcia modules, using --with=usb-storage
etc. mkinitrd includes a "sleep 5" after loading usb-storage, and this
does the trick.
If enough people are interested I'll write up some more details.
I have been having kicker crashes now and then
on FC4 when using the KDE desktop.
It seems to occur whenever I run the 'Control Center'
program to change things.
Example: use control center to change the stye and
colors used by KDE.
Then changes take effect ok, but when I
log out, the kicker crash occurs.
When I log back in, all the changes I made
are still there and KDE acts like nothing
I have applied all the kde updates
(e.g kdebase, kdelib, kdegraphics), arts and alsa
updates, and the xorg updates found on the FC4
Note: other types of changes can be made in the
control center, and kicker crashes may
Has anyone else been having problems with kicker?
ps: yes I re-created my ~/.kde dir after updates
Does anyone know where I can find a list of supported PCI wireless card for FC
4 ? I am looking to buy a cheapo PCI Wireless card for an old desktop, but I
want to have something that will work out of the box with FC 4 (ie. I don't
really want to deal with ndiswrapper, etc).