This may be a dumb question, but why can't Redhat distribute NVIDIA binary
In NVIDIA's licence (http://www.nvidia.com/object/nv_swlicense.html) it
"2.1.2 Linux Exception. Notwithstanding the foregoing terms of Section
2.1.1, SOFTWARE designed exclusively for use on the Linux operating system
copied and redistributed, provided that the binary files thereof are not
modified in any
way (except for unzipping of compressed files)."
So, what's keeping RedHat from putting the drivers in the distribution? If
it's a GPL
thing, would it be easy to just download it during installation or at
least give the option to the user?
Ok, I have had Yarrow working well for a while now, but yesterday I
started experiencing some odd issues with my mouse. All of a sudden it
stops working correctly. The only thing that seems to fix is to kill X
and run mouse-test, then restart.
Also, I have FC 1 running on a desktop which is hooked up to a KVM
switch. Whenever I go to another PC, and return, the same thing
happens, the mouse goes crazy.
Damian Menscher <menscher(a)uiuc.edu>@redhat.com on 04/07/2004 04:57:13 PM
> On Wed, 7 Apr 2004, Jeff Elkins wrote:
> > I'm getting failure messages on my nfs mounts i.e. :
> > mount to NFS server 'music.elkins' failed: server is down.
> > nsfd appears to be running and I didn't see anything suspicious in the
> > The servers are up and running and have other clients connected.
> You didn't mention what steps you took to debug it:
> Can you ping the server?
> What is the output of rpcinfo -p servername?
> Does the server have access restrictions (firewall, TCP Wrappers, etc)?
I have the same symptoms...
rpcinfo says that nfs et.al. are running.
Something has changed in test 2, since the same PC running RH9
accesses that host just fine.
Installing the OO.org 2.4 packages on F9 beta, I get this message when
Gtk-Message: Failed to load module "gnomebreakpad":
/opt/OOH680_m12/program/libstdc++.so.6: version `GLIBCXX_3.4.9' not
found (required by /usr/lib/bug-buddy/libbreakpad.so.0)
OOo then starts and seems to run ok, but it will not run from a desktop
launcher using that same command, I presume because bug-buddy can't be
I don't know what the Fedora policy is here: does it matter at this
point whether a third-party package isn't starting cleanly? Nor do I
understand the message well enough to decide who to report it to.
It seems that OOo uses it's own libstdc++ which is not compatible with
gnomebreakpad, but I've not found a way to have gnomebreakpad look
elsewhere for that library.
Any suggestions if/where to file a report, and/or how to workaround the
k3b is complaining about access to /dev/sr0
has there been a change that is causing this?
No write access to device /dev/sr0
K3b needs write access to all the devices to perform
certain tasks. Without it you might encounter problems
with HL-DT-ST - DVDRAM GMA-4082N
Solution: Make sure you have write access to /dev/sr0.
In case you are not using devfs or udev K3bSetup is
able to do this for you.
Mp3 Audio Decoder plugin not found.
K3b could not load or find the Mp3 decoder plugin.
This means that you will not be able to create Audio
CDs from Mp3 files. Many Linux distributions do not
include Mp3 support for legal reasons.
Solution: To enable Mp3 support, please install the
MAD Mp3 decoding library as well as the K3b MAD Mp3
decoder plugin (the latter may already be installed
but not functional due to the missing libmad). Some
distributions allow installation of Mp3 support via an
online update tool (i.e. SuSE's YOU).
We want to move more of the processes (like the one below) out to the
wider bug triage community so that all the bug zappers have a view into
what we are doing on the infrastructure front.
I'm open for ways we should do this... maybe the time has come for our
own mailing list? Attendance at our IRC meetings has been thin and I'm
not sure why that is. I'm open to suggestions and constructive
criticism on how we should do meetings differently.
Below is a draft of the ticket I'm going to file with Red Hat
Engineering Operations (aka Eng Ops) to auto-close Fedora 7 bugs when it
goes EOL in a few weeks. Now my secret is out... this is "the bot"
everyone loves ;-)
If you have any proposed changes to the text please reply to the list by
2008-05-26 and then I'll transfer the final version to the wiki and file
with Eng Ops.
Thanks for reading,
Request Title: Fedora 7 EOL Bug Closing
Date to run: On or after June 15, 2008
Query to select bugs: http://tinyurl.com/3osskh
User making changes & comments: fedora-triage-list(a)redhat.com
Please script changes such that only ONE email notification is sent for
Actions to take on all bugs selected in query above:
1) Change bug status to CLOSED:WONTFIX
2) Add the following comment:
=== START ====
Fedora 7 went to end-of-life status on June 13, 2008. Fedora 7 will no
longer maintained or receive updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
=== END ====