Fedora :: Azureus Cause FC12 To Hang?
Feb 20, 2010Just upgraded to FC12, but when running azureus, it hang the entire system.Anybody had the same problem. I tried both yum installed and download from azureus site.
View 2 RepliesJust upgraded to FC12, but when running azureus, it hang the entire system.Anybody had the same problem. I tried both yum installed and download from azureus site.
View 2 Repliesafter downloading azureus/vuze, the README simply instructed me to launch the azureus script. I did this and it crashed. I have included the log if anyone can zero in on the problem. It is a long time since I installed this program and I am migrating to another computer. I would have expected to build the program but (as noted) the README suggests otherwise. A private site I use requires me to run an old version of azureus.
Some basic system info:
[tim@library ~]$ uname -r
2.6.35.6-45.fc14.i686
[code]...
I have a tricky problem which I could soIve with a c program. I wrote one and found I didnt have gcc so I tried to install it. I was told I needed to install packages. I acknowledged and an error was generated gcc-4.4.2-7.fc12.i686 requires libgomp = 4.4.2-7.fc12 I try to install libgomp and go round again.
View 2 Replies View RelatedI installed Azureus from their site. It works well. The only problem is when Azureus tries to apply updates, I get this error message:
"The folder <path-where-I-installed-Vuze> is not writable. This will prevent future software updates from being applied."
There was a link the the Vuze wiki, and the problem is that I (or is it the Azureus updater?) do not have permissions to write to that directory, or words to that effect.
How do I apply the proper permissions so that when an update from Azureus is downloaded, it is applied?
The wiki offers this solution:
Quote:
But this looks like something that I have to do manually, each time...
How do I set it up, so that the updater has the permissions and uses the proper password to do it automatically, when I restart Vuze?
I'm using Ubuntu 9.10
when ever i try to install updates i get shown an error & the updates stop the error i get says "librpmio.so.0 is needed by package abrt-1.0.3-1.fc12.i686 (updates) librpm.so.0 is needed by package abrt-1.0.3-1.fc12.i686 (updates)"
View 12 Replies View RelatedI've been using F15 through the early releases and now with the final release, and in all of them I've had the same issue:
It will install fine in Parallels, however about 30 seconds to 1 minute after launch, it will hang and completely freeze. This will happen even in run level 3 with no gui running. It doesn't *appear* to happen at the same time every time.
I've tried, disabling networking, sound, and a few other things in the VM to see if that has an effect, but it doesn't seem to make a difference.
I've also tried making a copy of my F14 VM and upgrading. The same issue persists in this case as well.
I have had no issues with F15 on the metal on different machines, as a matter of fact it's been great and required very little hardware work-arounds. Similarly, F14 has run fine and continues to run fine on Parallels on this machine.
I saw that AMZ recently updated the rpm for Fedora to be compatible with FC 11, however the install is still broken on FC12 (obviously since it's built for 11).
My main question is has anyone found a decent workaround, that won't completely hose your system? Should I just wait until they build an rpm for FC12?
Not wanting to speculate why, in the repositories, Fedora doesn't *also* provide a on-KVM enabled kernel counterpart to the default KVM enabled kernel that *is* supplied, I must say I'm frustrated that they haven't done this simple thing.
Considering that everyone who upgrades to KVM enabled FC12 from a previous non-KVM release of Fedora (like FC10) ... considering that these people will be guaranteed to no
longer be able to run VirtualBox or VMWare Workstation after upgrading, is a disappointing oversight by / or intent of Fedora (one that manifests in *lost productivity*).
And try though you may to install the kernel source RPM and compile it after running "make xconfig" to disable KVM support, you usually can't! Fedora kernel compile attempts often die very early in the "make" process, indicating something like ...
"Kernel compile error: No rule to make target `missing-syscalls'
or some other silliness. And when you successfully compile a "kernel.org" kernel, and try to boot it, you get all kinds of missing library errors (etc).
Given that it would be simple to provide both a KVM enabled kernel (as they do), and also a non-KVM enabled kernel (which they don't) so the rest of us can seamlessly continue to run VirtualBox and/or VMWare Workstation after an upgrade - and avoid getting entangled with deciding whether use KVM or XEN for guest O/S's... it's a frustrating misstep to not have done this basic thing (i.e. include a non-KVM kernel). It was a rude awakening when we tried to launch VirtualBox only to have it fail after the upgrade.
Anyway, has anyone successfully compiled their own kernel for FC12 and not get errors after boot? If so, which sources did you use; and what kernel version? In the meantime I'll try out other kernels and compile options.
Has anyone managed to install retroshare on fedora? Where can i find a howto?
View 4 Replies View RelatedI am running fedora 10 on my laptop. I use a usb Western digital "MyBook" 500Gb (ext3). I am using this hard drive since more than 1 year now. Lately I run into a single problem when I read a precise file. The laptop becomes totally unresponsive and I have to manually shutdown the computer. After start-up I can find that the /var/log/message file of my previous session has grown very quickly with "[sdb] Sense Key : No Sense [current]" and "[sdb] Add. Sense: No additional sense information" messages.
I found various similar question on the web, most of the answer were hardware dependent and kernel related. I tried various kernel hoping that my specific problem would be fixed in the next one but with no success (all the kernel since fedora 10 release and two testing one: 2.6.29.5-84.fc10 and 2.6.29.6-93.fc10), I don't have access to a Fedora 11 machine.
I replaced the usb cable and check that the power supply was working correctly.
I am joining part of /var/log/message and the results of lsusb (related to the external hard drive).
I have a GRUB2 USB multiboot setup. Plus I have a multiboot setup on my computer with Ubuntu 9.10, PCLinuxOS, Windows XP, and Fedora 13. The issue I'm having is different but the same. On my USB multiboot, Fedora will hang up on certain devices. Things such as touchpad, bluetooth, etc. On my PC it hangs up on first the bluetooth, then I unplug, then the USB hub, then the mouse and finally the external hard drive. It detects the devices but it freezes on detection. I did get this error before the device detection began:
Quote:
dracut; dracut-005-3.fc13
dracut: FATAL: Don't know how to handle 'root=(0,4)'
dracut: Refusing to continue
dracut: FATAL: Don't know how to handle 'root=(0,4)'
dracut: Refusing to continue
this is on the PC and the problem with the USB is that it will hang up when detecting devices.
I have Fedora 13 installed on a new PC and have two types of intermittent boot hangups. What logs exist within Fedora 13 that may help me identify the cause or causes of these hangups? Todate, a reboot gets over the problems but I wish to get this sorted whilst the PC is still under warranty.
View 6 Replies View Relatedi am working on a client server real-time gui application written in C++ for Redhat. There is an issue with this application that it makes the system hang. i am not able to sort out the issue as it happens randomly. Sometimes with in half an hour it makes the system hang, sometimes it takes 4 or 5 hours when it receives realtime data. Is there any way to debug this issue. I tried valgrind..but it was not of much use..
View 4 Replies View RelatedWhy my fedora 12 always hang and not responding?it is any problem with my installation process?when my fedora not responding,the only thing that i can do is restart it again.i did this again and again..
View 5 Replies View RelatedI recently upgraded my CPU (just before the release of FC12), to a 64-bit compatible Intel Core 2 E7600. Upon the release of FC12 I moved to the 64 bit version (via a clean install).
I noticed that NVIDIA does not work (as many topics on this forum confirm). So I reinstalled and used the FC12 default drivers (I think they are called Nouveau-drivers). This seemed to work, so I ran "yum update", and now all X-windows fail.
KDE complaints: "kstartup4 does not exist or fails" and GNOME also complains (sorry forgot the exact error message)
I'd be happy to send logs, but if these are required, which log you want and where I can find it.
how to get or KDE or GNOME running ? (preferably KDE)
System:
Intel Core 2 Duo E7600 (3.1 GHz)
3 GB Memory (800MHz)
Nvidia Geforce 9600 GT
Mobo: Foxconn P35A01
Trying to start Tomcat6, I get the following in catalina.out
dl failure on line 696Error: failed /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/lib/i386/client/libjvm.so, because /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/lib/i386/client/libjvm.so: cannot enable executable stack as shared object requires: Permission denied
Every time I open empathy, I am seeing that message. The messenger itself doesn't have a problem (as far as I can see), but that message really bothers me.
View 4 Replies View RelatedIt was a long time since my last post on this forum. The reason for this was that since FC7 I've moved to Debian Etch and then to Ubuntu, but now I'm back trying FC12 amd64 on my machine and seen how it changed.Almost everything is going well until now. After almost two years I see that a great development was made to build and gui to yum, but synaptic is still superior, imho.
Well, as I said, everything is going well with one exception: the *.tar.gz files.
Doesn't matter if I use the gui or the cli. If I try to compress or decompress any file to tar.gz it fails with the error message bellow. All other file types work perfectly.
Code:
/bin/gtar: Child returned status 1
/bin/gtar: Exiting with failure status due to previous errors
As I said, I'm running FC12 amd64. Gnome environment.
I have just installed fc12, and everything seemed to go well. After reboot I get a line asking for First login:From what I've found, this should be the firstboot thing, but I don't know the login, and can't find any answer with a search.
View 6 Replies View Relatedis it me, or is the rapidsvn in FC12 have no menu?I cant find anyway to do "file > edit > preferences", theres no menu bar at all.I've used rapidsvn since FC8 and this is the first time I cant find the menubar lol.
View 1 Replies View RelatedI'd like to see all messages given out by my fc12 system. So no graphical interface shows up when I shall type the bootloader-password or log-in with my user.
View 1 Replies View RelatedI install CentOS 5.4 on a customer's workstation. They out-of-date nature of Enterprise is not at all working out for him. Since Enterprise is essentially FC6, is it possible to just upgrade him to FC12, or am I looking at a wipe and reinstall?
View 7 Replies View RelatedI installed Fedora Core 12 on a Dell Latitude 610 laptop. Networking isn't working. I tried to start networking with '/etc/rc.d/init.d network start': there were no errors or warning messages, but before and afterwards, I could not ping anything.
I tried to configure and start networking with system-config-network. The ethernet network card shows up, but the activate button is greyed out.
I can ping the loopback address 127.0.0.1 after I start networking with '/etc/rc.d/init.d network start' but I don't really know what that means.
lspci tells me that my network "card" is a "NexXtreme BCM5751 Gigabit Ethernet PCI Express".
I know the eternt cable is good because I used it on another machine.
I have been unable to burn CD's / DVD's while logged into FC12 with a full GDM session or with just the Gnome Greeter running. If I drop to single user mode and use wodim I can burn w/o issue.
GDM 2.28.2
KERNEL 2.6.32.9-70.fc12.x86_64
I've looked at a couple of threads on this subject but can't cure my Pb. I have a floppy drive that I rarely use. Last time was on an earlier version of FC without problems.
View 8 Replies View RelatedI have 2 Fedora 12 installs with this problem. Before installing FC 12, xset led 3 worked fine.
The command:
SHOULD turn on the scroll lock LED.
With FC 12, it doesn't.
In Xorg.log, I see: (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(I believe before FC12, I was using driver "kbd".) The man page for kbd shows the options needed for program control of the LEDs.
The new driver appears to be "evdev". I've read some of the HAL documentation and I think this driver uses the file: /usr/share/hal/fdi/policy/10osvendor/10-leds.fdi
I see nothing about program control in this file.
Anyway, anyone have any idea why xset led stopped working and how to go about fixing it?
Do we have netdump client for Fedora 12 ?
I have downloaded a netdump-server package for the my netdump-server but can't find
netdump client for my FC12 client.
When I installed it via yum, it says code...
I'd like to reproduce the way I got to f12 from f11, but obviously to f13 basically I started out on the f11 rawhide repos, then as f12 got released a yum update updated my fedora-release and then hey presto I was automatically upgraded to f12 final release if I now turn on my rawhide repos, as f13 is nearing completion, will I be updated to the latest f13 release (RC3 I believe) and then as f13 gets released my fedora-release will be updated and i will then be upgraded to f13 final as happened before?I don't want to download a whole dvd iso and then upgrade when f13 is final, I'd like to do a gradual transition ie..
f12 -> f13 RC3 via rawhide
f13 RC3 -> f13 Final via yum update
My system (recently installed FC12) is reporting that there are 563 updates available. When I try and install the updates I get to the stage of "Getting list of updates" and receive the message "The package identifier was not well formed". The details are "Package_ID cannot not be parsed". It further says that "This normally indicates an internal error and should be reported."
View 4 Replies View Relatedso i recently had a problem with preupgrade (power cut mid process). anyway it seems that my system is now f13. In any event it seems that there are 785 f12 packages still remaining.yum list installed | grep f12 output can be seen here.How can I mas remove these fc12 packages?
View 2 Replies View Related