middle click paste and vim
Is anyone else seeing this regression in Fedora 10 updates-testing? I have found on a Fedora 10 x86_64 box with the rpmfusion nvidia drivers installed that middle clicking to paste text in vim is no longer working properly. In the past, I have always been able to select some text in one gnome terminal window, go to a secnd gnome terminal window (which has vi open in insert mode) and use a middle mouse button click to paste the text at the insertion point in vi. Now I find that when I do this the text doesn't go in at the insertion point in vi but is placed in the beginning of the file. Does a bugzilla exist for this yet? Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
swig-1.3.39-1.fc10 install problems
Has anyone else noticed that swig-1.3.39-1.fc10 has dependency problems? I am seeing... Loaded plugins: refresh-packagekit adobe-linux-i386 | 951 B 00:00 fedora | 2.8 kB 00:02 rpmfusion-free | 2.7 kB 00:00 rpmfusion-free-updates | 2.8 kB 00:00 rpmfusion-nonfree| 2.7 kB 00:00 rpmfusion-nonfree-updates| 2.8 kB 00:00 updates | 3.4 kB 00:00 Setting up Update Process Resolving Dependencies -- Running transaction check --- Package swig.i386 0:1.3.39-1.fc10 set to be updated -- Processing Dependency: perl(example) for package: swig-1.3.39-1.fc10.i386 -- Processing Dependency: perl(the) for package: swig-1.3.39-1.fc10.i386 -- Processing Dependency: perl(it) for package: swig-1.3.39-1.fc10.i386 -- Processing Dependency: perl(argv) for package: swig-1.3.39-1.fc10.i386 -- Running transaction check --- Package jython-demo.i386 0:2.2.1-0.1.Release_2_2_1.1.2.fc10 set to be updated -- Processing Dependency: jython = 2.2.1-0.1.Release_2_2_1.1.2.fc10 for package: jython-demo-2.2.1-0.1.Release_2_2_1.1.2.fc10.i386 --- Package swig.i386 0:1.3.39-1.fc10 set to be updated -- Processing Dependency: perl(the) for package: swig-1.3.39-1.fc10.i386 -- Processing Dependency: perl(it) for package: swig-1.3.39-1.fc10.i386 -- Processing Dependency: perl(argv) for package: swig-1.3.39-1.fc10.i386 -- Running transaction check --- Package jython.i386 0:2.2.1-0.1.Release_2_2_1.1.2.fc10 set to be updated -- Processing Dependency: libreadline-java = 0.8.0-16 for package: jython-2.2.1-0.1.Release_2_2_1.1.2.fc10.i386 -- Processing Dependency: oro for package: jython-2.2.1-0.1.Release_2_2_1.1.2.fc10.i386 -- Processing Dependency: mysql-connector-java for package: jython-2.2.1-0.1.Release_2_2_1.1.2.fc10.i386 --- Package swig.i386 0:1.3.39-1.fc10 set to be updated -- Processing Dependency: perl(the) for package: swig-1.3.39-1.fc10.i386 -- Processing Dependency: perl(it) for package: swig-1.3.39-1.fc10.i386 -- Processing Dependency: perl(argv) for package: swig-1.3.39-1.fc10.i386 -- Running transaction check --- Package jakarta-oro.i386 0:2.0.8-4.2.fc10 set to be updated --- Package libreadline-java.i386 0:0.8.0-22.fc10 set to be updated --- Package mysql-connector-java.i386 1:3.1.12-6.fc10 set to be updated -- Processing Dependency: jta = 1.0 for package: 1:mysql-connector-java-3.1.12-6.fc10.i386 -- Processing Dependency: log4j for package: 1:mysql-connector-java-3.1.12-6.fc10.i386 --- Package swig.i386 0:1.3.39-1.fc10 set to be updated -- Processing Dependency: perl(the) for package: swig-1.3.39-1.fc10.i386 -- Processing Dependency: perl(it) for package: swig-1.3.39-1.fc10.i386 -- Processing Dependency: perl(argv) for package: swig-1.3.39-1.fc10.i386 -- Running transaction check --- Package geronimo-specs-compat.i386 0:1.0-2.M2.fc10 set to be updated -- Processing Dependency: geronimo-specs = 1.0-2.M2.fc10 for package: geronimo-specs-compat-1.0-2.M2.fc10.i386 --- Package log4j.i386 0:1.2.14-4.3.fc10 set to be updated --- Package swig.i386 0:1.3.39-1.fc10 set to be updated -- Processing Dependency: perl(the) for package: swig-1.3.39-1.fc10.i386 -- Processing Dependency: perl(it) for package: swig-1.3.39-1.fc10.i386 -- Processing Dependency: perl(argv) for package: swig-1.3.39-1.fc10.i386 -- Running transaction check --- Package geronimo-specs.i386 0:1.0-2.M2.fc10 set to be updated -- Processing Dependency: mx4j = 2.0.1 for package: geronimo-specs-1.0-2.M2.fc10.i386 --- Package swig.i386 0:1.3.39-1.fc10 set to be updated -- Processing Dependency: perl(the) for package: swig-1.3.39-1.fc10.i386 -- Processing Dependency: perl(it) for package: swig-1.3.39-1.fc10.i386 -- Processing Dependency: perl(argv) for package: swig-1.3.39-1.fc10.i386 -- Running transaction check --- Package mx4j.i386 1:3.0.1-7.8.fc10 set to be updated -- Processing Dependency: jakarta-commons-logging = 1.0.1 for package: 1:mx4j-3.0.1-7.8.fc10.i386 -- Processing Dependency: javamail = 1.2-5jpp for package: 1:mx4j-3.0.1-7.8.fc10.i386 -- Processing Dependency: bcel = 5.0 for package: 1:mx4j-3.0.1-7.8.fc10.i386 -- Processing Dependency: axis = 1.1 for package: 1:mx4j-3.0.1-7.8.fc10.i386 -- Processing Dependency: jaf for package: 1:mx4j-3.0.1-7.8.fc10.i386 --- Package swig.i386 0:1.3.39-1.fc10 set to be updated -- Processing Dependency: perl(the) for package: swig-1.3.39-1.fc10.i386 -- Processing Dependency: perl(it) for package: swig-1.3.39-1.fc10.i386 -- Processing Dependency: perl(argv) for package: swig-1.3.39-1.fc10.i386 -- Running transaction check --- Package axis.i386 0:1.2.1-4.1.fc10 set to be updated -- Processing Dependency: jakarta-commons-httpclient for package: axis-1.2.1-4.1.fc10.i386 -- Processing Dependency: wsdl4j for package:
fwbackups failure in Fedora 10
Is anyone else seeing this failure in fwbackups under Fedora 10? I find that when I start fwbackups, click on the One-Time Backup, select a directory in my user account and then select a directory on an external usb firewire drive (ext3) which I have write permission to that the backup fails with an alert saying... Error initializing. An error occurred initializing the backup operation: 'OldToKeep' This is the only error message I see. Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
nvidia and Error: couldn't find RGB GLX visual or fbconfig
I am running into an issue with the nvidia drivers under Fedora 10 x86_64 producing the error... Error: couldn't find RGB GLX visual or fbconfig when I run the 64-bit version of glxgears or glxinfo unless I am root. Do we need the... Section DRI Group0 Mode 0666 EndSection for the nvidia drivers in xorg.conf under Fedora 10? The /usr/bin/nvidia-config-display program doesn't add that to the xorg.conf file it creates. Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
nvidia and Error: couldn't find RGB GLX visual or fbconfig
To answer my own question, we finally pinned this issue down to the inappropriate use of LD_LIBRARY_PATH in a set of user accounts which was causing the wrong GL libraries to be used with the nvidia drivers. It is interesting that one gets the error... Error: couldn't find RGB GLX visual or fbconfig when running 64-bit software but this error is suppressed when running 32-bit software under x86_64 Fedora 10 with the nvidia drivers. In the 32-bit case, the software runs using software rendering. Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Graphics card recommendation?
On two different Fedora 10 x86_64 boxes (one AMD and the other Intel based) both equipped with Radeon X1650 Pro graphics cards, the radeon driver has been a total nightmare. The fglrx drivers (which we have been using in the past) no longer are available for pre-HD radeon cards. The free radeon drivers work well except for one nasty flaw... spontaneous reboots back to the BIOS at random times. Disabling the kernel modeset feature does nothing to eliminate these. We finally gave up and replaced one of the machine's X1650 Pro with a Nvidia 8600GT using the non-free nvidia drivers. The machine has been rock solid ever since the switch over. I finally gave up on the second machine and ordered a Nvidia 9600GT for it as well. I have tested x86_64 Fedora 11 on a MacBook Pro with X1600 graphics and found the new DRI2 based radeon driver to be unusable because of improper rendering (like drawing black to the top of the screen when Pymol opens its viewer window or rendering progress bars up in the menu bar). Google has its work cut out for them if their OS is based on linux. I hope they plan to throw a lot of money at driver development because this issue is frankly killing Linux as a platform here in our lab. Mac OS X's X11 graphics support looks rock solid by comparison. Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
yum update issues
Is there a workaround for the following? On a x86_64 Fedora 10 workstation with the updates-testing repo enabled, I am finding that 'yum update' periodically fails. These are of the form... Transaction Summary ==Install 2 Package(s) Update 5 Package(s) Remove 1 Package(s) Total download size: 23 M Is this ok [y/N]: y Downloading Packages: (1/7): jack-audio-connection-kit-0.116.1-5.fc10.x86_64.rpm | 200 kB 00:00 (2/7): kernel-2.6.27.25-170.2.72.fc10.x86_64.rpm | 20 MB 00:34 (3/7): kmod-nvidia-180.51-1.fc10.8.x86_64.rpm | 25 kB 00:00 (4/7): kmod-nvidia-2.6.27.25-170.2.72.fc10.x86_64-180.51-1.fc10.8.x86_64.rpm | 2.6 MB 00:02 (5/7): openjpeg-libs-1.3-5.fc10.x86_64.rpm | 62 kB 00:00 (6/7): sudo-1.7.1-3.fc10.x86_64.rpm | 367 kB 00:00 (7/7): xorg-x11-drv-openchrome-0.2.903-7.fc10.x86_64.rpm | 182 kB 00:00 --Total 560 kB/s | 23 MB 00:42 Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Check Error: package kernel-2.6.29.1-42.fc10.x86_64 (which is newer than kernel-2.6.27.25-170.2.72.fc10.x86_64) is already installed package kernel-2.6.29.2-52.fc10.x86_64 (which is newer than kernel-2.6.27.25-170.2.72.fc10.x86_64) is already installed package kernel-2.6.29.3-60.fc10.x86_64 (which is newer than kernel-2.6.27.25-170.2.72.fc10.x86_64) is already installed package kernel-2.6.29.4-75.fc10.x86_64 (which is newer than kernel-2.6.27.25-170.2.72.fc10.x86_64) is already installed package kernel-2.6.29.5-84.fc10.x86_64 (which is newer than kernel-2.6.27.25-170.2.72.fc10.x86_64) is already installed Error Summary It appears that when a new kernel in the updates repo appears, yum tries to update to it despite the fact that the update-testing repo contains a new series of kernels (2.6.27.2.72 vs 2.6.29.x). Isn't this a flaw in yum? Shouldn't it realize that the updates-testing repo's kernel has provided a newer version and not attempt to install the older on from the updates repo at all? Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
gnome-mplayer-0.9.5-3.fc10.x86_64 from installed has depsolving problems
Has anyone else noticed that current updates-testing for Fedora 10 has issues with gnome-mplayer? I am finding that yum update fails with the error... Setting up Update Process Resolving Dependencies -- Running transaction check -- Processing Dependency: libgpod.so.3()(64bit) for package: gnome-mplayer-0.9.5-3.fc10.x86_64 --- Package libgpod.i386 0:0.7.0-1.fc10 set to be updated --- Package libgpod.x86_64 0:0.7.0-1.fc10 set to be updated --- Package rhythmbox.i386 0:0.11.6-22.r6096.fc10 set to be updated --- Package rhythmbox.x86_64 0:0.11.6-22.r6096.fc10 set to be updated -- Finished Dependency Resolution gnome-mplayer-0.9.5-3.fc10.x86_64 from installed has depsolving problems -- Missing Dependency: libgpod.so.3()(64bit) is needed by package gnome-mplayer-0.9.5-3.fc10.x86_64 (installed) Error: Missing Dependency: libgpod.so.3()(64bit) is needed by package gnome-mplayer-0.9.5-3.fc10.x86_64 (installed) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
reverting to DRI1 in F11?
Are there any flags for the video driver in the xorg.conf file that would revert the radeon drivers in Fedora 11 to the older DRI1 code or has that code been totally removed from the driver? I ask because the current radeon driver in rawhide still renders outside of the pymol viewer windows under Fedora 11 on a X1600 graphics card (MacBook Pro v2.1 actually). When started, pymol draws a black rectangle from the bottom of the Pymol viewer window all the way to the top of the screen such that the Nautilus menus are covered in black. Also the Ray Tracing demo in pymol does the same thing. The progress bar for the ray tracing isn't drawn within the boundaries of the Pymol viewer window but is placed in the Nautilus menu bar in the top of the screen instead. I am hoping that reverting to DRI1 might eliminate these artifacts (which don't exist under the radeon driver in Fedora 10). Jack ps This same issue is seen with the blender program when you select its menus within the blender windows. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Discovery Studio 1.7 restarts xserver
Does anyone else here have access to Discovery Studio 1.7? I am finding that when I try to start this program under x86_64 Fedora 10 under the radeon drivers using a X1650 Pro graphics card that the xserver restarts. There are no errors left behind in the messages log for this event but it is completely reproducible. Never had this issue with the non-free drivers. Jack ps This is a severe bug since the user has all of his open programs quit suddenly. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: nVidia vs. ATI graphics card for fedora
Kevin, Our experience here with x86_64 Fedora 10 linux and the radeon drivers on a couple machines with Radeon X1650 Pro cards has been very uneven. One of the boxes is very fragile to spontaneous reboots when running the free drivers and using UCSF Chimera to work with MD trajectories. The other box still has a habit of blanking the screen for minutes at time despite having the nomodeset flag passed to the kernel. I am afraid things will only get worse under Fedora 11. So far, testing on a MacBook Pro with X1600 graphics, I find that pymol still renders outside of its windows. While I appreciate the aims of these changes to X11 and the free drivers, the problem is that Fedora has become destablized. It is really exposing the limitations of a monolithic kernel when the graphics drivers keep taking down the entire box. Jack ps We run a large amount of OpenGL software (free and commercial) and have found the non-free drivers to be more compatible in general. Hopefully this will improve over time. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: nVidia vs. ATI graphics card for fedora
I haven't seen this issue mentioned yet, but ATI has just depreciated all hardware older than the HD series of cards as of the 9.3 release... http://support.amd.com/us/gpudownload/linux/legacy/Pages/radeon_linux.aspx?type=2.4.1product=2.4.1.3.9lang=English This means 9.4 and beyond will no longer promise support for these cards (although it may still work for a short while). I should have saw this coming when I couldn't get 9.2 or 9.3 to produce video on my X1650 under x86_64 Fedora 10. We are all stuck with the free drivers now. Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
screen blanks with nomodeset
Is anyone else still having the stock ati drivers in Fedora 10 occasionally blank out the screen? I have been resorting to the use of the nomodeset kernel argument in an attempt to disable modesetting, but, while less frequent, the black screens still appear. Normally, it will return back to the same display but on occasion, I get a reboot. This is on a Radeon X1650 Pro with Fedora 10 x86_64. Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: screen blanks with nomodeset
Chris, The worst part is that the fglrx drivers have stopped working on my machine with X1650 Pro graphics. The kernel level drivers seem to work okay, but when X starts up, I only get a black screen. This issue doesn't occur on a MacBook Pro with X1600 graphics so it appears to be specific to that particular graphics card. I tried rawhide over the weekend and the new DRI2 ati drivers have there on slew of issues (like rendering out of windows for pymol). Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
black screen with fglrx drivers
Has anyone else had problems with the fglrx 9.2 and 9.3 drivers under x86_64 Fedora 10? I am finding that the rpmfusion rpms provide a functional graphics up to the point that X windows should start the server. At this point am stuck with a black screen and no particular error message in Xorg.0.log. This is with the current testing updates applied (to avoid issues with the radeon drivers). Thanks in advance for any information. Jack X.Org X Server 1.5.3 Release Date: 5 November 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.18-128.1.1.el5 x86_64 Current Operating System: Linux fourier.med.uc.edu 2.6.27.21-170.2.56.fc10.x86_64 #1 SMP Mon Mar 23 23:08:10 EDT 2009 x86_64 Build Date: 10 March 2009 07:20:43PM Build ID: xorg-x11-server 1.5.3-15.fc10 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Apr 1 14:47:00 2009 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout single head configuration (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Videocard0 (**) |--Input Device Keyboard0 (**) Option AIGLX on (==) Automatically adding devices (==) Automatically enabling devices (==) FontPath set to: catalogue:/etc/X11/fontpath.d, built-ins (**) ModulePath set to /usr/lib64/xorg/modules/extensions/fglrx,/usr/lib64/xorg/modules (**) Extension Composite is enabled (II) Cannot locate a core pointer device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AllowEmptyInput. (WW) AllowEmptyInput is on, devices using drivers 'kbd' or 'mouse' will be disabled. (WW) Disabling Keyboard0 (II) Open ACPI successful (/var/run/acpid.socket) (II) Loader magic: 0x7aec00 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 4.1 X.Org XInput driver : 2.1 X.Org Server Extension : 1.1 X.Org Font Renderer : 0.6 (II) Loader running on linux (--) using VT number 7 (--) PCI:*(0...@8:0:0) ATI Technologies Inc RV530 [Radeon X1600] rev 0, Mem @ 0xc000/268435456, 0xd020/65536, I/O @ 0x3000/256, BIOS @ 0x/131072 (--) PCI: (0...@8:0:1) ATI Technologies Inc RV530 [Radeon X1600] (Secondary) rev 0, Mem @ 0xd021/65536 (II) System resource ranges: [0] -1 0 0x - 0x (0x1) MX[B] [1] -1 0 0x000f - 0x000f (0x1) MX[B] [2] -1 0 0x000c - 0x000e (0x3) MX[B] [3] -1 0 0x - 0x0009 (0xa) MX[B] [4] -1 0 0x - 0x (0x1) MX[B] [5] -1 0 0x000f - 0x000f (0x1) MX[B] [6] -1 0 0x000c - 0x000e (0x3) MX[B] [7] -1 0 0x - 0x0009 (0xa) MX[B] [8] -1 0 0x - 0x (0x1) MX[B] [9] -1 0 0x000f - 0x000f (0x1) MX[B] [10] -1 0 0x000c - 0x000e (0x3) MX[B] [11] -1 0 0x - 0x0009 (0xa) MX[B] [12] -1 0 0x - 0x (0x1) MX[B] [13] -1 0 0x000f - 0x000f (0x1) MX[B] [14] -1 0 0x000c - 0x000e (0x3) MX[B] [15] -1 0 0x - 0x0009 (0xa) MX[B] [16] -1 0 0x - 0x (0x1) MX[B] [17] -1 0 0x000f - 0x000f (0x1) MX[B] [18] -1 0 0x000c - 0x000e (0x3) MX[B] [19] -1 0 0x - 0x0009 (0xa) MX[B] [20] -1 0 0x - 0x (0x1) MX[B] [21] -1 0 0x000f - 0x000f (0x1) MX[B] [22] -1 0 0x000c - 0x000e (0x3) MX[B] [23] -1 0 0x - 0x0009 (0xa) MX[B] [24] -1 0 0x - 0x (0x1) MX[B] [25] -1 0 0x000f - 0x000f (0x1) MX[B] [26] -1 0 0x000c - 0x000e (0x3) MX[B] [27] -1 0 0x - 0x0009 (0xa) MX[B] [28] -1 0 0x - 0x (0x1) MX[B] [29] -1 0 0x000f - 0x000f (0x1) MX[B] [30] -1 0 0x000c - 0x000e (0x3) MX[B] [31] -1 0 0x - 0x0009 (0xa) MX[B] [32] -1 0 0x - 0x (0x1) IX[B] [33] -1 0 0x - 0x (0x1) IX[B] [34] -1 0 0x - 0x (0x1) IX[B] [35] -1 0 0x - 0x (0x1) IX[B] [36] -1 0 0x - 0x (0x1) IX[B] [37] -1 0 0x - 0x
pymol issues with fedora 10 testing
Is anyone else seeing these issues with Fedora 10 testing? I am seeing two problems. The first only occurs on x86_64 where when pymol is started for the first time upon each login (using the radeon drivers for X11), only the Pymol viewer window appears. The Pymol Tk window on the top never appears. I have to manually kill the pymol with ctrl-c and restart it. At this point restarting pymol always works correctly for the second and successive attempts. I am thinking that this has to be related to the recent update of tk-8.5.3-5.fc10. I don't get any errors in the terminal window which starts pymol or the messages log. The second problem I am seeing is with the fglrx 9.2 drivers packaged by rpmfusion. I find that these video drivers on both i386 and x86_64 cause the Pymol demos to be rendered in a slow jerky fashion with the entire Pymol viewer window flashing. This didn't occur with the previous fglrx 9.1 drivers. Jack ps Getting X11 to be stable for 3D usage these days has really become a nasty game of Russian roulette. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
AdobeReader_enu install_browser hang
Has anyone else run into this problem with the recent Fedora releases? I have noticed that over time many of my Fedora machines (both i386 and x86_64) develop problems with the AdobeReader_enu rpm installations. The problem always centers on the install_browser_plugin script that is executed postinstall hanging. After this starts to happen on a Fedora box, I always have to manually upgrade the AdobeReader_enu rpm manually with --noscripts and then move the plugin over to /usr/lib/mozilla/plugins by hand. Any idea why this hang in the install_browser_plugin script occurs and how it can be avoided? Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
RE: update to xorg-x11-drv-ati-6.10.0-1.fc10.x86_64 breaks X
I found, after upgrading from Fedora 8 x86_64 to Fedora 10 x86_64, that the radeon driver support for my Radeon X1650 Pro graphics card seemed to work well except for one major problem. The X server seemed to have issues with mode resets at random intervals. The screen goes black and then comes back as before. The X11 log file doesn't show a complete X server restart but just mode related lines repeating. Fortunately the current Catalyst 9.1 based flgrx packages are behaving well at the moment so I was able to switch over to those. Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
grubby fatal error unable to find a suitable template
While upgrading a Fedora 8 x86_64 system on a software RAID-1 mirror, I ran into a problem that prevents rpm from installing kernels in the grub.conf. The Fedora 10 upgrade of the Fedora 8 system completed without errors except that the upgraded boot loader didn't work but just presented the text... GRUB Having seen this before in upgrades on other Fedora system, I just repeated the upgrade process but selected the third option to create a new boot loader. This allowed the installed Fedora 10 to boot without problems. However when I did the first yum update, the kernel rpm installation showed the error... grubby fatal error unable to find a suitable template This resulted in no entry being added to grub.conf. When I compared the grub.conf.rpmsave, it has... default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora (2.6.27.5-117.fc10.x86_64) root (hd0,0) kernel /vmlinuz-2.6.27.5-117.fc10.x86_64 ro root=/dev/md1 nodmraid rhgb quiet initrd /initrd-2.6.27.5-117.fc10.x86_64.img whereas the grub.rpm present now shows... default=0 timeout=0 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora (2.6.27.5-117.fc10.x86_64) root (hd0,0) kernel /vmlinuz-2.6.27.5-117.fc10.x86_64 ro root=UUID=3adeca51-506e-4b51-aea7-c0ca9525ec36 nodmraid initrd /initrd-2.6.27.5-117.fc10.x86_64.img I was able to add an entry for the newly installed kernel and use /dev/md1 for root and this boots the new kernel fine. Does anyone know how to eliminate this problem? Where are the grub templates stored? I am assuming the use of the UUID label is causing the problem for grubby. I found bugzilla 124246 for this issue but it doesn't seem to have a solution other than the vague recommendation to not use the old grub.conf but have a separate template file (whatever that means). Thanks in advance for any advice as I am really worried about updating the kernel now. Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
RE: pymol vs Fedora 10
The problems with pymol crashing under Fedora 10 using the radeon drivers appear to be resolved now (at least in fedora-testing). FYI. Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
pymol vs Fedora 10
I was disappointed to find that pymol 1.1r2pre fails under i386 Fedora 10 on a Radeon X600 chipset with following error... PyMOL(TM) Molecular Graphics System, Version 1.1r2pre. Copyright (C) 2008 by DeLano Scientific LLC. All Rights Reserved. Created by Warren L. DeLano, Ph.D. Other Major Authors and Contributors: Ralf W. Grosse-Kunstleve, Ph.D. PyMOL is user-supported open-source software. Although some versions are freely available, PyMOL is not in the public domain. If PyMOL is helpful in your work or study, then please volunteer support for our ongoing efforts to create open and affordable scientific software by purchasing a PyMOL Maintenance and/or Support subscription. More information can be found at http://www.pymol.org;. Enter help for a list of commands. Enter help command-name for information on a specific command. Hit ESC anytime to toggle between text and graphics. OpenGL graphics engine: GL_VENDOR: DRI R300 Project GL_RENDERER: Mesa DRI R300 20060815 x86/MMX/SSE2 TCL GL_VERSION: 1.3 Mesa 7.3-devel Mesa 7.3-devel implementation error: radeon_program_pair.c::allocate_input_registers(): Don't know how to handle inputs 0x8 Please report at bugzilla.freedesktop.org pc=0* Hardware program NODE 0: alu_offset: 0, tex_offset: 0, alu_end: -1, tex_end: -1, flags: *WARN_ONCE* File r300_render.c function r300Fallback line 363 Software fallback:!fp-translated *** Mesa 7.3-devel implementation error: radeon_program_pair.c::allocate_input_registers(): Don't know how to handle inputs 0x8 Please report at bugzilla.freedesktop.org pc=1* Hardware program NODE 0: alu_offset: 0, tex_offset: 0, alu_end: -1, tex_end: -1, flags: Segmentation fault It would appear that this error is the same one reported here... http://www.mail-archive.com/[EMAIL PROTECTED]/msg36389.html The situation with video drivers and Fedora is really getting out of hand. Fedora 9 has come and gone yet there was never usable fglrx drivers from ATI for that release. Now with Fedora 10, the radeon drivers themselves are unuseable for software like pymol. I'll file a bugzilla for this but it looks like we have to wait for upstream to fix it. Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
dock condensing broken in Fedora 8
Has anyone else seen the following issue? After doing a long delayed yum update on Fedora 8, we are now finding that the Gnome dock no longer condenses icons in it. Prior to that update, after a certain number of entries in the dock, the windows for the same program would be overlaid so that they where accessible in a pop-up menu. Now the additional windows just get added to the dock and the icons in the dock get progressively smaller in width. Is this fixable short of upgrading to Fedora 9 or 10? Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: usb plugins cause reboots
Doh! The problem appears to be that someone broke off the plastic sheath that covers the top of the contacts on that usb port. Without that tab of plastic, usb plugs apparently can short across the free standing contacts. Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
printing to Bonjour printers under Fedora 9?
Is there decent support in Fedora 9 for printing to Bonjour printers? I understand that avahi is supposed to provide that functionality. However the HJ Deskjet I have attached to an Apple Airport Extreme basestation via usb and exposed as a Bonjour printer doesn't show up in the Printer setup utility in Fedora 9. Is there a particular set of steps to enable such Bonjour printers to be seen in Fedora 9's printer setup utility? Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: printing to Bonjour printers under Fedora 9?
I was able to connect to the Bonjour printer after enabling the mDNS access on the firewall and installing the missing avahi-tools package. Hopefully this package can be installed by default in Fedora 10 and later to limit the effort required to getting Bonjour access working. Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
f9 wireless reconnection problems
I am seeing a problem under Fedora 9 x86_64 with the madwifi wireless drivers in use. What I find is that on occasion the wireless connection will drop and the NetworkManager will attempt to reconnect to the wireless network. However this process always fails as follows. A dialog appears saying that the wireless network (correctly) requires a WPA2 password (which it refers to as a secret). The dialog is preloaded with the saved password for this wireless network. However when I click the show password checkbox, the password is always shown as a long series of digits rather than the plain text that it should be. If I re-enter the password as text and click connect, the reconnection to the wireless network always fails. Are there know issues with error-recovery in the NetworkManager for dropped wireless connections? I ask about this because I know there are issues with the madwifi driver (I am using the svn) with smp but I am in a poor wifi spot so the drop may just be a flaw in the driver with low s/n. The current issue smells more like a problem with the password keychain support in the NetworkManger. Thanks in advance for any insights. Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
rawhide and PCI: No MMCONFIG
Is anyone running rawhide having this problem? I updated a MacBook Pro from Fedora 10 to development and the current kernel-2.6.26-0.131.rc9.git9.fc10.x86_64 fails to boot with an error PCI: No MMCONFIG. Is MMCONFIG support broken across the board in that kernel? I can boot under the current f10 kernel. Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
xorg.conf font setting kills gnome
I ran into an issue with the xorg.conf settings under Fedora 9 this week which was pretty painful to debug. We found one Fedora 9 machine which had stopped allowing users to log into the gnome desktop. The desktop background would appear but the login would freeze. Oddly the KDE logins worked fine. After reinstalling all of the gnome related packages, I discovered that under the KDE desktop that gnome applications would fail to launch with the error... The program 'gedit' received an X Window System error. This probably reflects a bug in the program. The error was 'BadName (named color or font does not exist)'. (Details: serial 352 error_code 15 request_code 45 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) It appears the the xorg.conf on this machine contained the lines... Section Files # RgbPath is the location of the RGB database. Note, this is the name of the # file minus the extension (like .txt or .db). There is normally # no need to change the default. # Multiple FontPath entries are allowed (they are concatenated together) # By default, Red Hat 6.0 and later now use a font server independent of # the X server to render fonts. FontPath unix/:7100 EndSection and removing this solved the issue. Shouldn't gnome be more tolerant to this issue like KDE? I might not have figured out this problem if KDE wasn't available on that machine to allow me to debug the problem (since no error messages related to these font failures were logged anywhere in /var/log). Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
F9 and MacBook Pro v2,1 audio?
Has anyone had luck with audio under Fedora 9 on a MacBook Pro v2,1 machine? I had audio working for a short while by updating all of the alsa packages in F9 to build with the latest 1.0.17rc tarballs and building/installing the 1.0.17rc3 alsa-drivers. This was with the Sound settings all set to use OSS. I originally had the audio working with this configuration but seemed to have messed up my alsamixer settings while experimenting. Can any with working audio on one of these MacBook Pro v2,1 let me know their exact alsamixer settings? Also, even when the audio was working originally it on briefly had working desktop sound effects. Currently, the test buttons in the Sound preference panel produces tones but when I click the play button for any of the sound effects in the other panel, I get no sound (with any output method). I must admit to being very confused about the driver situation. I have read that the 2.6.25 kernels have issues with the snd-hda-intel kernel driver and that alsa oss must be used. However the snd-hda-intel kernel module still appears to be required which is puzzling. I've tried to find a svn or cvs for the snd-hda-intel source code (in case newer fixes exist) but have had no luck. Thanks in advance for any advice. Jack ps Also if one uses OSS, shouldn't something like esound be installed to allow programs to share the audio device? I noticed that their is a pulseaudio-esound-compat package installed. If one has to deinstall pulseaudio itself, doesn't that mean that the actual esound package needs to be installed instead? I did try building the pulseaudio srpm from development under Fedora 9 and installing that. This did at least eliminate the error alerts that appeared before when attempting to use the Test button in the Sound preference panel with the PulseAudio Server selected. However I could never get any of the sound applications to produce audio that way. I assume that the snd-hda-intel driver is being used by the PulseAudio Server and that is non-functional for me. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
EDAC i5000 NON-FATAL ERRORs
I noticed that after upgrading the kernel on a Fedora 7 x86_64 box is the latest kernel (the box hadn't been rebooted for some months) that I am now seeing the following in my messages log... May 25 04:30:56 fourier kernel: EDAC i5000 MC0: NON-FATAL ERRORS Found!!! 1st NON-FATAL Err Reg= 0x1 May 25 04:30:56 fourier kernel: EDAC MC0: CE row 1, channel 0, label : (Branch=0 DRAM-Bank=3 RDWR=Read RAS=14339 CAS=672, CE Err=0x1) These messages always occur on DRAM-Bank 3 and are always NON-FATAL. The messages appear roughly once an hour and are rarely repeated immediately. This machine contains a Tyan Tempest i5000XL motherboard with ECC memory installed. Does anyone know if the recent kernels had any changes which made these motherboard chipset report ECC memory errors which were not reported in the past? I haven't been able to reproduce these errors in memtest86 yet with or without ECC. So I am wondering if I am seeing noise from the EDAC driver or real ECC errors. Thanks in advance for any insights on this. Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
