test April 2008

test@lists.fedoraproject.org

192 participants
404 discussions

NVIDIA Question
by David St.Clair 17 Jan '22

17 Jan '22

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

10 20

Mouse goes crazy
by Jonathan Villa 17 Jan '22

17 Jan '22

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. ???

8 7

Re: rawhide report: 20050419 changes
by Ray Strode 22 Nov '15

22 Nov '15

Hi, > Will yelp in FC4 be able to search and display man/info pages Yea, man and info pages work for me. --Ray

2 2

Mouse Wheel gone
by Christian Menzel 22 Nov '15

22 Nov '15

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

3 3

Re: NFS failure
by Fulko.Hew＠sita.aero 22 Nov '15

22 Nov '15

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 9

Problem running OOo downloaded from openoffice.org
by Joe Smith 17 Aug '08

17 Aug '08

Installing the OO.org 2.4 packages on F9 beta, I get this message when starting: $ /opt/OOH680_m12/program/soffice 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 started. 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 problem? <Joe

4 9

rpmfluff: a lightweight tool for generating broken RPMs
by David Malcolm 23 Jul '08

23 Jul '08

This may be of interest to people working on tools such as rpmlint. Hope this helps Dave

2 1

Some things to focus testing on for F9Beta
by Will Woods 03 Jun '08

03 Jun '08

Fedora 9 will have a lot of new and exciting things. Naturally, we want those things to be stable and well-polished for the final release. With that in mind, here's a list of things that deserve especially close attention. 1) PackageKit This *replaces* pup and pirut, by default, on all new installs. If you're following rawhide, *please* disable or remove pup and pirut and test this. It's very important that you file bugs about *any* problems with PackageKit. Use the "gnome-packagekit" component in bugzilla for bugs about confusing (or missing) UI pieces, and "PackageKit" for bugs about backend errors, missing capabilities, or other (non-UI) problems. 2) NetworkManager At long last, NetworkManager is installed and enabled by default for all new installs. It is *supposed* to play nice with the system configuration set up by Anaconda and the old system-config-network tool. I'd recommend that all testers install and enable NetworkManager if possible. File bugs about network configuration problems (not honoring static IP configurations, for instance) against "NetworkManager". 3) Upstart Upstart has replaced sysvinit. Everything should be working as it did in F8, but if you have problems with serial consoles, boot-time arguments, changing runlevels (using telinit or similar), or the like, make sure bugs get filed. The runlevels are now controlled by the Upstart event scripts in /etc/event.d. If you have problems changing runlevels file bugs against "event-compat-sysv". Other upstart bugs should probably be filed under "upstart". 4) evdev Xorg is now using the new "evdev" generic input driver. This driver is intended to automatically handle all input devices recognized by the kernel - keyboards, mice, joysticks, whatever. Unfortunately its handling of keyboards is still a bit messy and probably won't be ready for F9. Therefore, ajax modified it to let the old, working driver claim your keyboard. So as of F9Beta, keyboards *should* work just like they did in F8. If you have *new* problems with your keyboard layout (and you're not having lingering evdev problems from older rawhide[1]), check Xorg.0.log to see if evdev has claimed your keyboard. If so, file a bug against "xorg-x11-drv-evdev". Otherwise, use "xorg-x11-drv-keyboard". If there's any other things that people think need closer attention.. now would be a good time to mention them. Happy testing! -w [1] https://redhat.com/archives/fedora-test-list/2008-March/msg00710.html

19 32

radeon driver: no EXA since latest updates
by Gianluca Cecchi 16 May '08

16 May '08

It seems that starting at 23/04 with xorg-x11-server-1.4.99.901-23.20080415.fc9 I'm not able to use EXA accel anymore and so no xvideo with my Sapphire X1900 card. 01:00.0 VGA compatible controller: ATI Technologies Inc R580 [Radeon X1900 XT] (Primary) Leaving AccelMethod EXA in xorg.conf I get: 1) rhgb freeze at mid startup point (with both 2.6.25-1 and 2.6.25-8 kernels). I need to switch off keeping power button pressed 2) if I boot without rhgb and without quiet I get black screen with cursor circle when starting gdm part and only able to move mouse but no console switch able I can press power button and get clean shutdown (without screen changes) 3) if I boot as in 2) and specifying init level 3 I can get a console If I log as normal user and do a startx I get gnome but after few seconds screen freezes. I need to switch off keeping power button pressed 4) if I comment out the option about EXA in xorg.conf it seems ok (just in that session) Is there a particular option for EXA in this latest updates? BTW: also fglrx doesn't work (tried with -1 kernel, not available for -8 yet). I get a (II) Loading /usr/lib/xorg/modules/drivers//fglrx_drv.so dlopen: /usr/lib/xorg/modules/drivers//fglrx_drv.so: undefined symbol: miZeroLin eScreenIndex (EE) Failed to load /usr/lib/xorg/modules/drivers//fglrx_drv.so Not tried radeonhd in these days (I have installed xorg-x11-drv-radeonhd-1.1.0-0.7.20080404git.fc9.i386) because it doesn't provide xvideo yet... My system is an updated rawhide x86. Relevant packages now are: xorg-x11-server-Xorg-1.4.99.901-26.20080415.fc9.i386 xorg-x11-drv-ati-6.8.0-10.fc9.i386 kernel-2.6.25-8.fc9.i686 Any help? See below my current xorg.conf Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" EndSection Section "ServerFlags" Option "AIGLX" "on" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "us+inet" EndSection Section "Device" Identifier "Videocard0" Driver "radeon" # Option "AccelMethod" "EXA" EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection Section "Extensions" Option "Composite" "Enable" Option "DAMAGE" "Enable" Option "RENDER" "Enable" Option "RandR" "on" EndSection Section "Module" Load "drm" Load "v4l" Load "GLcore" Load "type1" Load "vbe" EndSection Section "DRI" Mode 0666 EndSection (extmod, dri, freetype, glx, dbe are not specified as they are loaded automatically, as in log file: (II) "extmod" will be loaded by default. (II) "dbe" will be loaded by default. (II) "glx" will be loaded by default. (II) "freetype" will be loaded by default. (II) "dri" will be loaded by default. (II) "dri2" will be loaded by default. ) Gianluca

1 1

Shutdown fails (NetworkManager?)
by Leon Stringer 11 May '08

11 May '08

Hi, My F9 system intermittently refuses to shut down with: nm-system-settings: Could not get the system bus. Make sure the message bus daemon is running! Message: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused Can anyone suggest how to fix this or is it a bug? Thanks, Leon...

2 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test April 2008