NX Server - BIG HEADACHE - BIG FIX
by Mickey
I am on a Fedora 17 box
I Can connect to Server Computer using ssh -x jim(a)192.168.x.x
PROBLEM:
[root@desktop bin]# /usr/NX/bin/nxserver --status
NX> 900 Connecting to server ...
NX> 204 Authentication to NX server failed.
NX> 110 NX Server is stopped.
NX> 999 Bye.
SOLVING PROBLEM:
OMG!.. Thank you!! I have been working this issue for about 4 Days!.. I
found this thread that outlined the exact problem I was having.. linking
the
authorized_keys2 file to authorized_keys fixed everything!..
cd /usr/NX/home/nx/.ssh
ln -s authorized_keys2 authorized_keys (On the Server Computer)
This is strange to me since I have 4 different computers with the
nxserver. None of the others needed to have the authorized_keys2 file
linked to the
other filename.
I have gave up trying to install Nomachine NX-Server on Fedora for last
few years, because of this same problem. And now I finally got it working.
11 years, 8 months
Printer disabled on boot
by Aaron Konstam
I am using F17. Recently something strange is happening when I try to
print. On boot the printer is disabled and I can't figure out why. In
these cases I have to go into system-config-printer ans enable the
printer. It is very annoying. Any solutions out there? Printing has
worked since the release of F17. What could have changed?
--
=======================================================================
He has not acquired a fortune; the fortune has acquired him. -- Bion
=======================================================================
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam(a)sbcglobal.net
11 years, 8 months
F16 => F17 PreUpgrade Invalid Device ID Dumps to dracut Shell
by Brian Hanks
I delayed the upgrade of my main Fedora machine after reading all of
the issues that were happening with the preupgrade process. I've done
several fresh installs without issue, so I suspected that my delay would
have provided enough time for the preupgrade issues to be worked out. I
was wrong.
I started with a fully updated F16 box and ran preupgrade. There were
video issues during the process, but after a long wait with a blank
screen it rebooted. When booting into the F17 kernel it dies on an
invalid device id error and drops to a dracut shell. I've validated
that the device id in question is in fact correct. I've tried to
replace that device id with the actual device name (/dev/sda3). I've
tried to run grub2-mkconfig and I've tried to reinstall grub2. Nothing
works. Thankfully, I am able to boot into an F16 kernel (with some
errors), so the machine it completely dead.
I've searched all over and not found any reference to this exact
problem. Any ideas?
I'm really trying to avoid doing a fresh install because I don't want
to recreated the installation and config of my entire machine, servers,
and dev environment. Any insight would be greatly appreciated.
Thanks,
Brian Hanks
11 years, 8 months
ftp with TLS auth
by Michael J Gruber
Hi there,
I'ven been struggling to find an ftp client in Fedora which supports TLS
auth. Tried ftp, lftp, ncftp, even dolphin (KDE file manager); all fail
with "must use TLS auth".
Is this due to our use of GNU TLS rather than OpenSSL for many packages?
Firefox with FireFTP works...
Michael
(everything F16 with updates)
11 years, 8 months
Why did they f*ck with GIMP?
by Fedora User
People must have too much time on their hands. Add some features; maybe
clean up some code. But why on earth make major UI changes to a program
that consistently did exactly what it was supposed to do exactly as it
was supposed to do it - - - and now doesn't. Ugh!
11 years, 8 months
Fedora 17 in a CHROOT on Ubuntu - and the wrong dependency on rpmlib(X-CheckUnifiedSystemdir)
by Marc Wäckerlin
Hi
I am working in Ubuntu and compiling RPMs for Fedora. That's why I install Fedora in
a **chroot** environment. That works fine with Fedora 16, but fails with Fedora 17 due
to the wrong "rpmlib(X-CheckUnifiedSystemdir)" dependency.
I Do not upgrade and I cannot use dracut, because Fedora 17 is in a chroot and cannot
boot. So the instructions at http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum
do **not** help.
How to solve the problem? What does dracut do, why(*) does rpm fail, where does this
dependency come from? How can I either fake this dependency or prevent RPM from requiring
it? I need a deep inside knowledge on what's going on, what dracut does and what rpm does.
What have the fedora-guys patched to get thie wrong dependency, and how can I undo it?
----
(*) I mean technically *why*, not user-view answers like "to prevent upgrades without
fs-migration", this kind of answer does not help, but technical answers like "dracut
creates content X in file Y, then the dependency is ignored in rpm"
----------
Background information:
I use the chroots on an Ubuntu server running a Jenkins build server to build packages
for all available Debian, Ubuntu, openSUSE and - as soon as possible - Fedora
distributions.
I setup a chroot the following way:
1. download all basic RPM files
2. unpack the RPM file into a chroot dir using rpm2cpio to get the basig filesystem
3. within the chroot, call rpm for all packages to run installation scripts an update
rpm database
In the attachment you find my setup chroot script "susebootstrap.sh". It is originally
build for openSUSE, but also works for Fedora with correct parameters; i.e.
Install Fedora 16 i686 in a chroot:
URL=http://mirror.switch.ch/ftp/mirror/fedora/linux/releases/16/Fedora/i386/os \
HW="i686 noarch" OS=fedora VERSION=16 PKGS="bash rpm yum fedora-release" \
susebootstrap.sh
Install Fedora 17 i686 in a chroot:
URL=http://mirror.switch.ch/ftp/mirror/fedora/linux/releases/17/Fedora/i386/os \
HW="i686 noarch" OS=fedora VERSION=17 PKGS="bash rpm yum fedora-release" \
susebootstrap.sh
Installing Fedora 16 works, installing Fedora 17 fails due to the
"rpmlib(X-CheckUnifiedSystemdir)" dependency.
The very last step fails, after echo of "... install more basic packages" the
command "${CHROOT} -r -- yum -y -q groupupdate Base" fails with:
---------------------------------------------------------------------------------
... install more basic packages
ERROR You need to update rpm to handle:
rpmlib(X-CheckUnifiedSystemdir) is needed by filesystem-3-2.fc17.i686
RPM needs to be updated
You could try running: rpm -Va --nofiles --nodigest
Your transaction was saved, rerun it with:
yum load-transaction /tmp/yum_save_tx.2012-09-13.08-29.pr4OBd.yumtx
**** ERROR aborted. Status of last operation: 1
---------------------------------------------------------------------------------
Thank you
Regards
Marc
11 years, 8 months
freezing mouse (perhaps OT)
by Ranjan Maitra
Dear friends,
I am not sure that Fedora has anything to do with this: quite likely,
this is my old computer (9+ years-old, Dell Precision 650 running F17
LXDE spin, every software component zealously updated).
For the past seven or ten days, my USB mouse has been freezing on me.
This happens quite frequently when any GUI (including sylpheed, but
most often firefox) is used. Disconnecting and reconnecting the USB
mouse takes care of the problem till the next freeze. At all points of
time, the keyboard is usable and I can type and move the focus using the
keyboard and appropriate keys.
My question is: what is causing this behavior? Is it a bad graphics
card (or hopefully, some software component). Or something else? Any
suggestions?
Many thanks and best wishes,
Ranjan
--
Important Notice: This mailbox is ignored: e-mails are set to be
deleted on receipt. For those needing to send personal or professional
e-mail, please use appropriate addresses.
____________________________________________________________
FREE 3D MARINE AQUARIUM SCREENSAVER - Watch dolphins, sharks & orcas on your desktop!
Check it out at http://www.inbox.com/marineaquarium
11 years, 8 months
Fedora 16 to 17
by Jeffrey Ross
I'm about to take the plunge and upgrade, I've upgraded systems in the
past with varying degrees of initial success and eventually everything
works out ok.
My problem this time is I have 2 systems running F16 x86_64 the Systems
are almost identical and I know they will cause me some grief so I'm
looking for some suggestions.
System 1 -
/boot - md1 - sd[ab]1
/ - md127 - sd[ab]2
swap - md3 - sd[ab]3
/usr - md5 - sd[ab]5
/var - md6 - sd[ab]6
/home - md7 - sd[ab]7
System 2 -
/boot - md127 - sd[ab]1
/ - md2 - sd[ab]2
/var - md3 - sd[ab]3
swap - md5 - sd[ab]5
/home - md6 - sd[ab]6
System 1 is obviously going to give me issues due to the separate / and
/usr partitions, looking at the space available on root there maybe barely
enough to move /usr to the / partition, however there is room to move / to
the /usr partition. How much sense does it make to move the partitions
(in single user mode) and if I move / to the existing /usr partition how
to I tell the kernel where the new / partition is during startup?
Next issue and it affects both systems is that /var is a separate
partition, I found on the release notes for upgrading via YUM that there
are some extra steps due to the separate partition.
Lastly is the raid1 setup also going to cause me grief? if so any
suggestions on how to deal with it?
System 1 is all superblock 0.90 and System 2 is all superblock 1.2 except
boot which is 0.90
Thanks, Jeff
11 years, 8 months
no zoom in korganizer?
by George Avrunin
On a fully-updated F17 x86_64, I decided to try korganizer again after not
using it for a couple of years. I would like to zoom vertically in the
calendar section to increase the vertical space per hour (mostly in the work
week view, but also in the day view). From the documentation I can find, I
should be able to go to Views -> Zoom -> In Vertically, but all the options
in Views -> Zoom are grayed out (in/out x horizontal/vertical).
I tried with a scratch user account and got the same result, so it's at
least not obviously an issue with my configuration. Is the zoom disabled on
F17 or do I have a more subtle problem?
George
11 years, 8 months