How long for updates to appear?
Hi, I have recently been experiencing crashing in OpenOffice wrier, which prompted me to search bugzilla.redhat.com. I found what I think is the bug responsible: https://bugzilla.redhat.com/show_bug.cgi?id=445318 The last developer comment (submitted 7 May 2008) is "fix for that checked in, will be in >= 2.4.0-12.9". As this was a month ago, I thought it should probably have been released by now. But it doesn't appear to be available (on http://download.fedora.redhat.com/pub/fedora/linux/updates/9/x86_64/). Is it usual for a fixed version to take about a month to upload? Or am I (more likely) missing something? :) Thanks, Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: How long for updates to appear?
Brian Morrison wrote: Steve Dowe wrote: Is it usual for a fixed version to take about a month to upload? Or am I (more likely) missing something? :) You need to have a look in updates-testing before it arrives in updates. If it isn't there then it will not appear in updates. It does often take some time for updates to be released, they sometimes get overtaken by events. Thanks for clarifying that. The package in question doesn't appear to be in either yet, so I'll hang tight. Best regards, Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Periodic Fedora 9 system hangs with jumpy mouse
I have this problem too. Deron Meranda wrote: Okay, so Xorg ran away last night ... it should have been a completely idle unused system. Anyway, concerning the Xorg driver module, this is a brand new install of F9 (not an upgrade). All the software is part of the base F9 repo; nothing 3rd party was added. Everything was auto-detected. Ditto. I have the most up to date versions of X, etc at the time or writing. Same kernel too (2.6.25.6-55.fc9.x86_64). The Xorg driver chosen for this was: /usr/lib/xorg/modules/drivers//radeon_drv.so My screen is 1440 x 900 x 24, monitor is DELL E198WFP Mine's 1680x1050. Using an HP Compaq 6715b laptop with ATI Radeon Express X1250, from level 3 boot, remove driver, then use 'yum install' to bring your driver back in and reboot to load it. driver may be fried. The driver is coming from the package xorg-x11-drv-ati-6.8.0-14.fc9.i386 I did an rpm verify on it, rpm -V -v xorg-x11-drv-ati-6.8.0-14.fc9.i386 and that said all the files were intact and correct. Again, same. My drivers seem to be present and correct. kde, gnome? have you tried any minimal desktops? something may, tho i would doubt, be different in how you bring up x. Haven't tried other desktops other than Gnome, but I have disabled all the fancy effects, etc. I can confirm this occurs in both KDE and GNOME on my system. The system runs perfectly fine; until that magic moment when the Xorg process runs away. Or is that the kernel that is running away? I wish I knew how to debug the kernel better; because it just doesn't appear to be a user-space problem. The cause of this problem on my system seems to be when dragging (resizing) a window. X then seems to hang, the pointer gets jumpy and the whole desktop is unresponsive. Being SSH'd in from another machine, I could see Xorg at 99-100% CPU. This never seems to happen when dragging a whole window, just when I try to resize one. I haven't noticed this happening at all by using a scroll bar (but I'm not saying this fault hasn't been triggered that way too..). The only way I can recover is a hard reboot - holding down the power button. Issuing "init 6" or "reboot" makes no difference - it just hangs, which makes me think this is kernel- rather than X-related.. :-( I'm afraid I cannot offer the same diagnostics as Deron without a little instruction, but I'd like to help to resolve this.. ;-) FWIW, I'm downloading the debug flavour of the current kernel. I'm going to reboot into that and see if I can get more output in the log(s)... Is it possible that the Radeon driver can be triggering a bug in the kernel (which hangs X)? All the best, Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Periodic Fedora 9 system hangs with jumpy mouse
The cause of this problem on my system seems to be when dragging (resizing) a window. X then seems to hang, the pointer gets jumpy I should also have added that the mouse cursor image "sticks" to the diagonal arrow - it doesn't become the normal arrow/pointer again. I have just booted up in the debug kernel and managed to re-hang X in no time at all, using the method described above... :-/ The only error message I can find, both in dmesg and messages, is this: kernel: ACPI Error (tbfadt-0453): 32/64X address mismatch in "Pm2ControlBlock": [8800] [8100], using 64X [20070126] The timestamp of this log entry roughly corresponds to the occurrence of the hang. But whether this has any bearing on the problem, I cannot say. I would guess that ACPI has some interaction with mouse events through X (e.g. polling), but judging by the position of this log entry, it appears to be during boot time. Any advice relating to debugging gratefully received... Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Periodic Fedora 9 system hangs with jumpy mouse
:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:05.0 VGA compatible controller: ATI Technologies Inc RS690M [Radeon X1200 Series] 02:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b6) 02:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 02) 10:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI Express (rev 02) 30:00.0 Network controller: Broadcom Corporation BCM4312 802.11a/b/g (rev 02) # grep -i chipset /var/log/Xorg.0.log (II) RADEON: Driver for ATI Radeon chipsets: (--) RADEON(0): Chipset: "ATI Radeon X1200" (ChipID = 0x791f) On Tue, Jul 1, 2008 at 9:26 AM, Steve Dowe <[EMAIL PROTECTED]> wrote: The cause of this problem on my system seems to be when dragging (resizing) a window. X then seems to hang, the pointer gets jumpy Although mine happens (usually) when I'm doing vertical scrolling, they may be related. In both cases there is usually a lot of bitmap moving occurring, which may be a bitblit operation of some sort, possibly involving 2D acceleration. This is interesting. It seems, on my system, somewhat related to the speed at which I drag my mouse. If I drag nice and slowly when resizing a window, I (usually, I think) get away with it. If I drag hastily, it hangs. I was going to suggest some kind of timing issue, so it seems we might be homing in on something here. I should also have added that the mouse cursor image "sticks" to the diagonal arrow - it doesn't become the normal arrow/pointer again. This is probably to be expected. I believe that the cursor/pointer movement is "hardware" assisted; which means that it runs within interrupt code and not in the main Xorg event loop. Changing the pointer graphic though must be done outside interrupts; and the Xorg process appears to be stuck. See if you see what I do: $ grep -i cursor /var/log/Xorg.0.log (II) RADEON(0): Using hardware cursor 0 (scanline 1202) (II) RADEON(0): Using hardware cursor 1 (scanline 1204) I get this: # grep -i cursor /var/log/Xorg.0.log (II) RADEON(0): Using hardware cursor 0 (scanline 1602) (II) RADEON(0): Using hardware cursor 1 (scanline 1604) Presumably this is influenced by the display dimensions and refresh rate? I have just booted up in the debug kernel and managed to re-hang X in no time at all, using the method described above... :-/ Hmmm. I should try that too. Didn't help much when I did it.. :-D I wonder if there are kernel flags set by the bootloader which can influence debugging level? The only error message I can find, both in dmesg and messages, is this: kernel: ACPI Error (tbfadt-0453): 32/64X address mismatch in "Pm2ControlBlock": [8800] [8100], using 64X [20070126] I don't know for sure, but this seems like a problem that would only occur on a 64-bit system. I only have a 32-bit system. I don't know if this would be related to your Xorg hanging, but I would have to guess that such an error would cause a process (or the kernel) to be completely aborted/panic'dnot get stuck in a 100% cpu loop. Fair enough. I suppose also that as this error was detected and presumably correctly identified, it probably has a workaround in place. Let's consider that item eliminated for now, then. One thing we could try, is to pass options to the ATI driver to disable certain features (perhaps like certain forms of acceleration??). You can do a "man radeon" to see the options available. Those would supposedly go into your /etc/X11/xorg.conf file. I don't have any good suggestions on what to try though; and it's tedious to do the trial and error thing. man radeon - excellent intro doc to the driver. The first two options are of primary interest to me: Option "SWcursor" "boolean" Selects software cursor. The default is off. Option "NoAccel" "boolean" Enables or disables all hardware acceleration. The default is to enable hardware acceleration. I'm going to try with both of these options enabled in xorg.conf and see if I can hang the machine again. If so, perhaps we should look at the kernel. Will get back to you. Any kernel-savy people have any ideas of how to collect more information about this? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Periodic Fedora 9 system hangs with jumpy mouse
I think I have the answer (below). Deron Meranda wrote: On Tue, Jul 1, 2008 at 3:59 PM, Steve Dowe <[EMAIL PROTECTED]> wrote: http://shaver.off.net/diary/2008/05/25/fsyncers-and-curveballs/ Good link, but I think it is entirely unrelated to this. Sorry, I misunderstood the reason that you mentioned FF originally. I wonder if disabling SMP at boot has any affect? Use the "nosmp" boot-time kernel option. Note though that if you're running with only one cpu and Xorg goes wild, you may not be able to ssh or do anything else, depending where at in the kernel this problem is occurring. Actually, I don't think it's kernel based.But your original suggestion about 2D acceleration was right on the mark, at least as far as my testing goes. My card is a Diamond Stealth ATI X1050; which is really a vendor repackaging of an ATI RV350 AS [Radeon 9550], an AGP version. It also supposedly has this as its chipset: "ATI Radeon 9600 AS (AGP)" (ChipID = 0x4153) and yours is a: 01:05.0 VGA compatible controller: ATI Technologies Inc RS690M [Radeon X1200 Series] (--) RADEON(0): Chipset: "ATI Radeon X1200" (ChipID = 0x791f) It looks like we have quite different ATI cards; but I don't know my Radeon product line very well. Indeed, and the only similarity between our systems is the driver, despite being 32 vs 64 bit. # grep -i cursor /var/log/Xorg.0.log (II) RADEON(0): Using hardware cursor 0 (scanline 1602) (II) RADEON(0): Using hardware cursor 1 (scanline 1604) Presumably this is influenced by the display dimensions and refresh rate? You're using hardware-assisted cursor/pointer; which is the default. I think the scanline numbers indicate at which point in the screen refresh cycle that the interrupt will be generated (but I'm kind of guessing here). It's not too important. If you disable hardware cursors in your xorg.conf, those lines should not appear in the log file. I didn't check this, but I did enable these options in my "Device" section in xorg.conf: Option "SWcursor" "on" Option "NoAccel" "on" .. and then restarted X. Boy, imagine life without hardware acceleration (no, don't!!). I had complete success with this config - no hanging issue despite really, /really/ trying to upset X with my mouse pointer. It just wouldn't hang, but I knew I was working it hard as my cpu fan speed increased :) It will be interesting if NoAccel works. Of course that's quite a drastic workaround and may make your system seem very sluggish. But it could give a clue if the system behaves differently. Given the above, I then re-enabled hardware acceleration but retained my software cursor and restarted X. The result? I managed to hang X within a few minutes of (frantically) drag-resizing a firefox window. And my mouse pointer completely disappeared this time, which confirms that it was running in sw mode. Unfortunately the system hanging on me is one of my primary workstations and I don't have the luxury of being able to tweak and play with different options as much; especially since having to do a hard reboot is so disruptive. That's ok - my work laptop doesn't mind ;-) (I will say that I haven't had a lockup in about 3 days now; previously I'd see lockups 3 or 4 times a day. I do stay up to date on patches, but the only things recently which seem even remotely plausible are a HAL and libsysfs update and some SELinux policies. I may just be lucky, we'll see how long my system stays up). In case it hangs again, try: Option "AccelMethod" "EXA" .. in xorg.conf (in the Device section). This is a new acceleration architecture which, while apparently not as mature (i.e. field-tested) as XAA (the default acceleration architecture), seems to at least hold up to my slipshod X testing method in this case. I've had an interesting evening researching this, which I wouldn't have had were it not for your suggestions. For more info on the changes in the radeon driver, check the Change Log of the xorg-x11-drv-ati-6.8.0-14.fc9 package (via Yum/Yumex), together with these links: - http://linux.softpedia.com/get/System/Hardware/ATI-Open-Source-Video-Driver-35337.shtml - http://zerias.blogspot.com/2008/02/amd-more-open-licensed-goodies.html - http://www.botchco.com/agd5f/ (http://www.botchco.com/agd5f/?p=6) - http://lists.freedesktop.org/archives/xorg/2008-February/032992.html From those, you should be able to establish a good idea of the recent (5 month) history of this driver development and the issues faced by those involved. Thanks again for your help and suggestions. Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Periodic Fedora 9 system hangs with jumpy mouse
Steve Dowe wrote: I think I have the answer (below). ... Option "AccelMethod" "EXA" Well, it was a nice theory while it lasted, but unfortunately it didn't last that long. I had another hang this morning when moving a Windows window (in a RDP window connected to a MS box). I'll keep working on it! Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Periodic Fedora 9 system hangs with jumpy mouse
... Option "AccelMethod" "EXA" Well, it was a nice theory while it lasted, but unfortunately it didn't last that long. I had another hang this morning when moving a Windows window (in a RDP window connected to a MS box). I'll keep working on it! Same section, but using Option "DRI" "off" .. seems to have had a positive effect. Might be in some way related to: https://bugzilla.redhat.com/show_bug.cgi?id=436632 HTH! -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
32 bit Java app on 64 bit Linux
Hi,
I'm trying to run Zend Studio (32 bit) on fedora 9 x84_64, but am coming
across a problem with network access. Specifically, when Zend starts up
it can perform an update check, but this fails almost immediately with a
useless message ("the server could not be contacted").
I suspect that I need a 64-32 bit compatibility library to enable
network access. Interestingly (annoyingly), a similar issue occurs when
replacing the 64 bit version of firefox with the 32 bit version. So I
think this is less of a Java issue...
Could anybody point me in the right direction please?
Thanks,
Steve
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: 32 bit Java app on 64 bit Linux
Andrew Overholt wrote: Are you running the 32-bit JRE? Check the output of the following: $ which java $ readlink -f `which java` # alternatives --config java The JRE actually installs as part of the Zend Studio product and I have had it running on 32-bit fedora before - so I assume 32-bit. However, here's the output: $ cd /usr/local/Zend/ZendStudio-5.5.1/jre/bin $ ./java -showversion java version "1.5.0_06" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05) Java HotSpot(TM) Server VM (build 1.5.0_06-b05, mixed mode) Obviously, given this I guess there's not a lot of point me doing the other commands, simply because Zend uses it's own JRE, not Fedora's. Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: 32 bit Java app on 64 bit Linux
Kevin Martin wrote: Are you sure that it's using it's own java? Just because it installed it doesn't necessarily mean it's using it (one would think so but...). It would be interesting to see what Zend is actually using (you may be able to do this in the startup script with a "set -x" or you may need to look at it with strace). I tried to strace the launcher but it seemed to cause it to hang (I'm not a dab hand with strace yet..). However, I have been looking at this all evening and have discovered it's not specifically a Java issue, but rather a 32-bit networking problem. Basically, the 32 bit apps that I have installed (on 64 bit Fedora 9) are not able to resolve domain names, but they do still have network access. I installed firefox.i386 and when trying to browse to www.google.com it responded with "Server not found". I pinged Google, got the IP address and put that straight into the address bar in FF and hey presto, web page. So I think I've been inadvertently misleading this investigation. Sorry about that! There was a really useful (if old-ish) page that helped inform me on the name resolution process in Linux: http://linuxgazette.net/issue50/tag/1.html In a nutshell, it /appears/ that calls using gethostbyname() are not working, but gethostbyaddr() is. I have no idea how to resolve this (no pun intended). Networking libraries appear to be installed correctly (AFAIK) in /lib and /lib64. Any further thoughts very welcome! Thanks, Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Ogg & Totem kill X
Hi, I have F9 with Totem and VLC installed. When I try to watch an ogg video from Red Hat's web site in Totem, the screen goes blank and I can hear my hard disk head park. I can't recover X from this - I have to hard reset the machine and boot back into the desktop. When I try the same video in VLC, VLC just dies immediately (but at least it doesn't bring the system down too). I've searched for log entries relating to this error, but there seem to be none. So... my question is, does video require DRI to be enabled in X? I had to disable DRI in my xorg.conf because it was making X hang in certain situations. Here's my xorg.conf for reference: Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 InputDevice"Keyboard0" "CoreKeyboard" EndSection Section "InputDevice" # keyboard added by rhpxl Identifier "Keyboard0" Driver "kbd" Option"XkbModel" "pc105" Option"XkbLayout" "gb" EndSection Section "Device" Identifier "Videocard0" Driver "radeon" Option"DRI" "off" EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection Any ideas, suggestions, etc appreciated. Thanks, Steve -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
F11 - package not signed
Hi, I installed F11 preview and have been keeping up with system updates - until now. When I do a yum update, I now get: Package nfs-utils-lib-1.1.4-6.fc11.x86_64.rpm is not signed Has anyone else seen this? Who/how should I contact somebody to see about getting this resolved? Thanks Steve -- 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: F11 - package not signed
On Thursday 21 May 2009 09:46:37 Rahul Sundaram wrote: > https://www.redhat.com/archives/fedora-test-list/2009-May/msg00931.html > > Use fedora-test list for any discussions about pre-releases/test up Thanks - will do. Steve -- 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
