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, 8 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, 8 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
7 years, 10 months
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
7 years, 10 months
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.
7 years, 10 months
[Fedora QA] #152: Test Cases Management
by fedora-badges
#152: Test Cases Management
---------------------------+------------------------------------------------
Reporter: rhe | Owner: rhe
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 15
Component: Wiki | Version:
Keywords: retrospective |
---------------------------+------------------------------------------------
= problem =
We've been using mediawiki to manage tests and record results, though it's
easy to approach, it has limitations such as managing, tracking and
querying cases+results. So is it time for us to consider another solution
such as TCMS?
= analysis =
Here I quoted the suggestion from Victer Chen:
some advantages of TCMS:
* Better to record, track and query test results,
* Allow user focus on test contents instead of document maintenance.
* Share test cases
However, it couldn't be flexible as wiki. I think the most important
things need balance are below:
- Barriers
Fedora should provide very low barriers. TCMS could be configured to
allow anonymous user login and limit it's permission. Also, we can
consider using fedora account to login TCMS.
- Safety
Wiki provides the ability to rollback content easily, while TCMS
couldn't. What TCMS can do is recording all the history and allow user
recovery it manually. But if we configure the permission well, it should
not be a big problem.
= enhancement recommendation =
Work with TCMS team and package it to Fedora. Set up the system and use it
in a small scale first. If it turns out good, enlarger the scale.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/152>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
8 years, 8 months
[Fedora QA] #81: Add i18n release criteria
by fedora-badges
#81: Add i18n release criteria
---------------------------+------------------------------------------------
Reporter: jlaska | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 14
Component: Wiki | Version:
Keywords: retrospective |
---------------------------+------------------------------------------------
= problem =
See [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=571900
RHBZ#571900 - Keyboard mapping not correct (USA instead of Belgium) when
first login after install Fedora 13 Alpha]
= analysis =
* Currently we don't have i18n installation cases, so local language
install is not tested as a demand. Untranslated pages are still existing
after RC test. Such cases needed be added in test as well as release
criteria.
* Does the Fedora i18n team have any release criteria to propose?
* RHBZ #571900 pointed out the need for a better understanding of how the
language and keymap installer selections impact the installed system.
= enhancement recommendation =
Recommend reviewing the release criteria to ensure expectations are
captured around propagating language and keymap settings from install to
desktop login (/etc/sysconfig/i18n, image:Package-x-generic-16.pnggdm
etc...). It may also be advised to coordinate with the installer team so
that bugs can be filed for any missing functionality.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/81>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
8 years, 8 months
[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, 8 months
