NVIDIA Question
by David St.Clair
This may be a dumb question, but why can't Redhat distribute NVIDIA binary
drivers?
In NVIDIA's licence (http://www.nvidia.com/object/nv_swlicense.html) it
says:
"2.1.2 Linux Exception. Notwithstanding the foregoing terms of Section
2.1.1, SOFTWARE designed exclusively for use on the Linux operating system
may be
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?
Thanks,
--
David St.Clair
dstclair(a)cs.wcu.edu
1 year, 10 months
Mouse goes crazy
by Jonathan Villa
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.
Any ideas?
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.
???
1 year, 10 months
Re: digikam and kipi-plugins?
by Rex Dieter
Per Bothner wrote:
> The Rawhide version of digikam is the very latest (0.10.0-rc1),
> but it fails to find any of the "Kipi plugins", even though I've
> installed the kipi-plugins package. This might be an upstream
> issue, since 0.10.0 is pretty bleeding edge and the kipi-plugins
> may even more bleeding-edge. Gwenview does seem to be see the
> plugins, so I'm wondering if there is there might be a
> Fedora-specific problem before I complain upstream ...
The f10 builds seem to work fine for me (finding the plugins), so perhaps
this is rawhide-specific?
To be clear, digikam's Settings -> configure digikam -> Kipi Plugins is
empty?
-- Rex
8 years
Mouse Wheel gone
by Christian Menzel
Since the latest xorg-X11 upgrade I receive the already mentioned XKB
error and the mouse wheel is not working anymore.
Has anybody seen this behavior?
Regards
Chris
8 years
Re: NFS failure
by Fulko.Hew＠sita.aero
Damian Menscher <menscher(a)uiuc.edu>@redhat.com on 04/07/2004 04:57:13 PM
wrote:
> 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
logs.
> > 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.
8 years
[Fedora QA] #46: Write Test cases for LXDE components.
by fedora-badges
#46: Write Test cases for LXDE components.
----------------------+-----------------------------------------------------
Reporter: johannbg | Owner: johannbg
Type: task | Status: new
Priority: major | Milestone:
Component: Test Day | Version:
Keywords: |
----------------------+-----------------------------------------------------
An ticket to keep track on LXDE components that need test cases and how to
debug pages
* PCManFM: File manager, provides desktop icons
* LXPanel: Feature-rich desktop panel
* LXSession: Standard-compliant X11 session manager with
shutdown/reboot/suspend support via HAL ( FEI
https://fedoraproject.org/wiki/Features/HalRemoval )
* LXSession-edit: GUI to configure what’s automatically started in
LXDE
* lxde-settings-daemon: XSettings Daemon
* LXInput: Keyboard and mouse settings dialog
* LXRandR: Configuration tool for monitors and external projectors
* LXAppearance: Feature-rich GTK+ theme switcher able to change GTK+
themes, icon themes, and fonts
* LXTask: Lightweight task manager derived from xfce4 task manager
* LXTerminal: Desktop-independent VTE-based terminal emulator
* LXLauncher: Open source replacement for the Asus Launcher on the
EeePC
* LXShortcut: Small utility to edit application shortcuts, used by
lxpanel and lxlauncher
* LXNM (still under development): Lightweight network manager for LXDE
supporting wireless connections (not yet in Fedora )
* LXRandR (still under development): Monitor configuring tool
* Openbox: Lightweight, standard-compliant, and highly-configurable
window manager.
* GPicView: A very simple, fast, and lightweight image viewer
featuring immediate startup
* Leafpad: Lightweight and simple text editor
* XArchiver: Lightweight, fast, and desktop-independent gtk+-based
file archiver
* LXDM: Display manager
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/46>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
8 years, 10 months
Fedora install support for netbooks -- small screen size
by Robert Moskowitz
I am doing another FC12 install on my ASUS 701ee. This is a test
system, and I end up installing every month or so.
Of course with the small screen size, I end up pressing <cntl-N> a lot,
as I cannot see the Next button. And on some screens I just miss some
options, like getting to customize the install packages. I am always
forgetting the key combo to turn that check box on.
Is there some way to either get the ability to pan the screen around or
scroll the screen so that on Netbooks that SHOULD be a popular install
platform for Fedora, can have workable installation?
12 years, 11 months
[Fedora QA] #49: F13 X.org Test Week
by fedora-badges
#49: F13 X.org Test Week
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: adamwill
Type: task | Status: new
Priority: major | Milestone: Fedora 13
Component: Test Day | Version:
Keywords: |
----------------------+-----------------------------------------------------
So of course there will be an X.org Test Week for Fedora 13. This here's
the ticket for organizing it. Current status: I am about to start mailing
driver maintainers to get their take on when would be a good time.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/49>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
13 years, 7 months
[Fedora QA] #48: NFSv4 Test Day
by fedora-badges
#48: NFSv4 Test Day
----------------------+-----------------------------------------------------
Reporter: jlaska | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 13
Component: Test Day | Version:
Keywords: |
----------------------+-----------------------------------------------------
On Mon, 2010-01-18 at 11:06 -0500, caiqian(a)redhat.com wrote:
> I'd recommend next Tuesday (1/26), next Thursday (1/28), or any
> > Tuesday/Thursday after. This will be influenced by the amount of
> > prep work needed (see next step).
>
> Next Tuesday will be working for me. Steve, are you able to be online at
that date to provide helps if necessary?
>
> > = Step#3 - Create the Wiki page =
> >
> > This should help you think about what needs testing, and perhaps
> > designing the tests in such a way that might be helpful for a
> > distributed testers to attack. I'm not thinking of any good
> > distributed test scenarios for NFS, but I'm also not aware of the
testing
> > involved.If you can start with a outline of what testing you'd like to
see
> > covered, we might be able to get a better sense for how to make it a
> > good fit for a Fedora test event.
>
> I will be create a wiki page for it. I have not looked them in details
yet. Overall, we will be running some automated NFS tests like,
>
> * connectathon - git://fedorapeople.org/~steved/cthon04
> * new server test that - git://linux-nfs.org/~iisaman/pynfs.git
>
> Does it sound like a good fit for a test day?
>
It's not something I'd envision a strong level of community participation
on. Mainly, since Fedora QA doesn't have a lot of experience/skill in
this technical area. That said ... I'm sure there are communities that
might be interested in participating? So, some questions to help explore
our options ...
1. What external customers/communities should we solicit for attendance?
2. What is required to participate?
1. What distro? F12, Rawhide, other?
2. Installed system or Live image?
3. System requirements (single system or multiple)?
4. Can a virtual lab be used?
3. What test feedback is needed?
1. Is there a hardware-specific component where community contributor
feedback would be helpful (i.e. like xorg-x11-drv-* test days where
testers all have different hardware?)
2. Is there software-specific components where community feedback is
needed? (for example, running tests against different versions of nfs
(client+server), or across F-12, F-11 and rawhide)?
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/48>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
13 years, 9 months
