Has anyone successfully got this working between two Fedora 20 machines?
The app says that the default port -- 24800 -- is not available. I
don't know why, I can't see anything taking it in the firewall or
anything, but anyway, changing to different ports doesn't seem to
help... the client and server never connect.
Can anyone give me any pointers as to how to start to troubleshoot this?
Thanks in advance.
Liam Proven * Profile: http://lproven.livejournal.com/profile
Email: lproven(a)cix.co.uk * GMail/G+/Twitter/Flickr/Facebook: lproven
MSN: lproven(a)hotmail.com * Skype/AIM/Yahoo/LinkedIn: liamproven
Cell: +44 7939-087884
> Date: Sat, 31 May 2014 13:35:38 +0930
> From: Tim <ignored_mailbox(a)yahoo.com.au>
> To: users(a)lists.fedoraproject.org
> Subject: Re: Create virt F20 on new physical /dev/sda -> OK; boot live
> F20 on /dev/sda now fails
> Message-ID: <1401509138.1661.5.camel(a)fluffy.lan.cameratim.com>
> Content-Type: text/plain; charset="UTF-8"
> On Sat, 2014-05-31 at 11:40 +1000, Philip Rhoades wrote:
>> but now for going from F19 to F20 and booting on the new F20 the
>> process stops at:
>> [OK] Reached target Paths
>> [OK] Reached target Basic System
> I encountered the same stalling point, but with an ordinary install.
> Out of the two or three recent bouts of install grief, this one was due
> to the device numbering. During install, thanks to booting from a DVD,
> the install thought that the system root was /dev/sde instead
> of /dev/sda, and configured things like that. Check your kernel line
> the boot menu for the wrong device name, and either correct it, or use
> the UUID of the drive partition, instead.
> Oddly enough the next entry in my grub.cfg file was for a recovery boot
> mode, and that one had used the UUID, instead of the wrong device name.
> I'm not impressed with the current install routine, and that was just
> one of the things about it that annoyed me.
Ah . . well spotted - I should have seen that - thanks!
> George Orwell's '1984' was supposed to be a warning against tyranny,
> a set of instructions for supposedly democratic governments.
A great (but sad) sig!
GPO Box 3411
Sydney NSW 2001
I get the following error after running gedit from the commandline after a
recent update. it works but gives the error
I tried removing and re-installing but error persists. From the gui its
simple work around I use gedit filename 2>/dev/null which hides the
(gedit:2401): Gtk-CRITICAL **: gtk_tree_view_get_cell_area: assertion
'gtk_widget_get_realized (GTK_WIDGET (tree_view))' failed
(gedit:2401): Gdk-CRITICAL **: gdk_window_get_origin: assertion
'GDK_IS_WINDOW (window)' failed
could someone please help explain/ fix error
*Dr P Singh*
fax 086 637 8639
tel 031 2607686
I just had a yum update of OpenJDK, and as a result, the "java" command
simply does nothing, regardless of arguments.
Founder at Relomics Consulting <http://www.relomics.com>
Be always grateful, but never satisfied.
I'm seeing different things about thunderbolt support and Linux. Anyone
have any experience? Specifically I would like to connect a PCIe
thunderbolt expansion unit to my MBP running Fedora 20. It is my impression
it will not work...
For the last few versions of Fedora (x86_64) I have been going through
- install a new SATA drive as /dev/sda
- boot to the previous Fedora now on /dev/sdb
- create a new virtual system using the latest Fedora on the new
physical drive on /dev/sda
- get the new virtual Fedora on /dev/sda as ready as possible
- then re-boot to the new live system on /dev/sda
This process has been working fine for the last few versions but now for
going from F19 to F20 and booting on the new F20 the process stops at:
[OK] Reached target Paths
[OK] Reached target Basic System
I can still do a live boot on /dev/sdb and run the new F20 as a virt
machine using physical drive /dev/sda OK but it was a nice process to
reduce down time to be able to get the new Fedora as ready as possible
as a virtual machine and then reboot it as the live machine. Has
something changed that stops me doing this now?
GPO Box 3411
Sydney NSW 2001
OK, this is really with Fedora-arm 20, but it is still first boot.
The system I am installing on physically has a hdmi p1080 video, but via
an hdmi/vga adapter (that still supports p1080) goes through a KVM that
only supports 1024x1024 to a 16:9 monitor so all I get is 1024x768.
This is not a problem, operationally, but first boot is not smart for
Thus on the set root password screen (and I am assuming the create user
screen) the OK button is not visible. What is the keystroke to accept
what I entered?
what would be the device for a Kensington Slimblade which is connected
to a PS/2 port with an USB-->PS/2 adapter? The device doesn`t seem to
appear anywhere when connected like that.
And what are virtual keyboards for, and why do I supposedly have two
| ~ $ xinput --list
| ⎡ Virtual core pointer id=2 [master pointer (3)]
| ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
| ⎜ ↳ Kensington Kensington Slimblade Trackball id=8 [slave pointer (2)]
| ⎣ Virtual core keyboard id=3 [master keyboard (2)]
| ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
| ↳ Power Button id=6 [slave keyboard (3)]
| ↳ Power Button id=7 [slave keyboard (3)]
| ↳ AT Translated Set 2 keyboard id=9 [slave keyboard (3)]
| ~ $
There is only one power button, and it is not at the keyboard.
Fedora release 20 (Heisenbug)