Re: Update broke OpenJDK

Hello, A reinstall of OpenJDK fixed it. Before, even java -version would just be silent. Thanks! Best, Oliver On Sat, May 31, 2014 at 1:43 AM, Sudhir Khanger wrote: > On Saturday, May 31, 2014 02:37:01 AM Oliver Ruebenacker wrote: > > Hello, > > > > I just had a

Re: Update broke OpenJDK

On Saturday, May 31, 2014 02:37:01 AM Oliver Ruebenacker wrote: > Hello, > > I just had a yum update of OpenJDK, and as a result, the "java" command > simply does nothing, regardless of arguments. > > Best, > Oliver Are alternatives links intact? alternatives --list | grep open

Update broke OpenJDK

Hello, I just had a yum update of OpenJDK, and as a result, the "java" command simply does nothing, regardless of arguments. Best, Oliver -- Oliver Ruebenacker Founder at Relomics Consulting Be always grateful, but never satisfied. -- users mailing li

Re: Thunderbolt support?

On Wed, 2014-05-28 at 23:52 +0200, Henrik Frisk wrote: > Hi, > > > 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

Re: Create virt F20 on new physical /dev/sda -> OK; boot live F20 on /dev/sda now fails

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

Create virt F20 on new physical /dev/sda -> OK; boot live F20 on /dev/sda now fails

People, For the last few versions of Fedora (x86_64) I have been going through this process: - 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 virtu

Re: QuickSynergy

On 05/30/2014 10:16 AM, Liam Proven issued this missive: On 30 May 2014 18:44, Rick Stevens wrote: I use synergy all the time between F19 and F20 machines (the console is currently on an F19 box). On the F20 box (XFCE), right-click on the firewall icon and edit the current zone (I'm using "Pub

Re: QuickSynergy

On 30 May 2014 18:44, Rick Stevens wrote: > I use synergy all the time between F19 and F20 machines (the console is > currently on an F19 box). > > On the F20 box (XFCE), right-click on the firewall icon and edit the > current zone (I'm using "Public"). Click on the "Ports" tab, then click > the "

Re: QuickSynergy

On 05/30/2014 07:47 AM, Liam Proven issued this missive: 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

Re: f20 first boot screens on a 1280x768 video

I just did an install on a notebook, and there is a done button on the upper left that was not showing on my arm install due to screen size. And there was no shown keystroke to indicate done. :( On 05/30/2014 10:33 AM, Robert Moskowitz wrote: OK, this is really with Fedora-arm 20, but it is

Re: Pale moon, was Re: replacement for seamonkey?

On 17 May 2014 17:42, Fernando Cassia wrote: > On Sat, May 17, 2014 at 6:23 AM, Paul Cartwright > wrote: >> >> I am beginning to like Pale moon.. pulled in all my Chrome bookmarks ( >> awesome, automatic!), and it is VERY snappy! > > > What's the track record of this fork for security fixes? > Do

QuickSynergy

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 ser

f20 first boot screens on a 1280x768 video

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

systemctl restart network, VMs and suspend

Hello, I already filed a bugzilla issue with this [1] but I'd like to know if anybody else has troubles with VMs' network after suspend. And if others are able to do a "systemctl restart network" successfully. I mean, am I an isolated case because of some unknown configuration I have or is t