F14 fully updated. I tried installing the latest Google Earth 64-bit
tarball (version 18.104.22.1685) and got this:
$ sudo sh GoogleEarthLinux.bin
Verifying archive integrity... All good.
Uncompressing Google Earth for GNU/Linux 22.214.171.1245..............................................................
./setup.sh: setup.data/bin/Linux/amd64/setup.gtk2: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
I've seen this "bad Elf interpreter" message in other contexts, but can
simply never remember what it means (something about 32-bit binary on a
64-bit system I think). Any pointers welcome.
Easily Dual Boot Windows 7 and F14?
Perhaps I am missing something.
Trying to easily dual boot a Windows 7 computer
with Fedora 14.
Seems the installer does not do this?
(Windows 7 installed, then install F14)
Any help would be appreciated.
Is it possible to get gnome-volume-manager style auto mount/umount of
USB drives in /media (or elsewhere) when nobody is logged into the
desktop? The behavior when I'm logged in (auto-mounting in a directory
named after the Volume Name, auto-unmounting, etc) is exactly what I
would like when I'm not logged in. It doesn't matter if the mount
point is owned by root, as I just want to back up some files in a cron
job but only if there's a drive plugged in.
I suppose I could script it all, except: 1. I'm not a very skilled
script writer, 2. I don't really know where to start to accomplish
this, and 3. It seems to me that there's already something on the
system that does perfectly what I want.
My Number One PC, currently running F14, has a weird trouble,
which I haven't yet managed to describe very well.
It boots, showing what my workspace switcher calls #1, with my
gnome terminal and its usual tabs (which work). But the switcher fails to
change to any other workspace, and if you click the window selector, it
seems to think no windows are open. (The window list remains all but
invisible, also as if there were none.) None of the methods listed in the
Workspace Switcher help gets me to any other workspace. (I have 18 of
them, btw; I know that may be marginal -- but the preferences dialog no
longer lets me change the number. No way to do so even appears.)
I can add more windows on top of the terminal, but if I minimize
one, it disappears; and I have found no way to get back to it. (All I've
tried do work when open.)
I had supposed this to be a trouble of the machine, which
normally only I ever use. The other day, I added my wife to the Users
list, just in case, and yesterday I logged her in for the first time.
Beginning, in a very sleepy condition, to configure her desktop, I
discovered the Workspace Switcher worked fine there.
So I added a third userid, btth2 (my normal being btth -- who
want to keep typing out "Beartooth"?). The switcher works there, too.
This would appear to tell me the trouble is in how btth is
configured, somehow -- I can't imagine how.
I'd like to add all my data, and all I can of my tweaks and
configurations (*except*, I hope, the source of the trouble!), to btth2;
delete btth; and rename btth2 -- in effect, moving btth to the new name
and back. That might save me finding the weirdness, reporting it, and
getting my swiftly senescing skull around the directions for coping with
Can I do all that? How?
Or is there something better to do instead? (The trouble is on my
main PC, which is of course the newest, biggest, fastest I have; and I
miss it. <snimper, whiff>)
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
I have precious (very precious!) little idea where up is.
I need your help.
I have installed NFS-server on my Fedora 14.
Server is 192.168.1.101
Client is 192.168.1.100
I have stoped my iptables like this:
# su -c 'service iptables stop'
I'm not sure, that I have to write in /etc/hosts.allow and /etc/hosts.deny
>From the client side I do:
# sudo mount.nfs 192.168.1.101:/home/booch/Temp /home/booch/data/
And I have got thos error:
mount.nfs: access denied by server while mounting 192.168.1.101:
Please! Help me to resolve that problem!
Thank you very much in advance!
*+9 72 54 285 952 3
*+9 72 54 285 952 3*
Yet again I'll be very grateful for any help you can give me.....
I just upgraded to F13 on my 2 systems & on both of them, I seem to be
unable to print. The 2 machines are
a) my desktop
Linux Fedora-Blue 126.96.36.199-61.fc13.i686.PAE #1 SMP Tue Oct 19 04:24:06
UTC 2010 i686 i686 i386 GNU/Linux
which was fresh-installed because preupgrade wouldn't reboot(Grrrr)
and b) my laptop which was preupgraded.
The printer is an Epson Stylus DX6050 which "always" worked before....
Strange thing is that under previous Fedoras, I had to fight to get the
scanner recognised, this time, the scanner is recognised & working, but
I can't get any of the print commands to offer me anything but a "write
.pdf to file".
Can anyone suggest what I've forgotten to check?????????
As ever, great thanks for any suggestions!
On Sun, 28 Nov 2010 19:33:54 -0500
I started this topic by saying:
> I need to run X with the fvwm window manager, but the F14 X server
> doesn't play nice with fvwm - or with twm. When fvwm or twm calls
> XCreateFontSet(), the X server dies with a SIGSEGV.
> To get around this, I have copied the F13 /usr/bin/Xorg server binary
> and /usr/lib/xorg/modules directory contents to my F14 system, and
> they work just fine with the F14 fvwm, F14 X libraries, and F14 fonts.
> While this workaround works, it's not exactly a good long term fix.
> Note that this workaround means the problem is with the F14 X server
> or its loadable modules, not the F14 fvwm.
> When twm is used, it calls XCreateFontSet() with a base_font_name_list
> argument different from that in the fvwm XCreateFontSet() call, and
> the F14 server dies, so the problem is not the font asked for by fvwm.
This gets stranger and stranger ...
Before trying to dig into the X server code, I wanted some clues about
where to look, so I put this into root's .xserverrc:
exec /usr/bin/ltrace /usr/bin/Xorg :0
I deleted root's .xinitrc, .fvwmrc, and .fvwm directory and, as root
(only root can ltrace /usr/bin/Xorg) I ran:
xinit fvwm 2>/tmp/Xorg.out
The ltrace output in /tmp/Xorg.out has 176 calls to memmove(), all
with five arguments, like this example:
memmove(0xa352c50, 0xa3535e0, 1648, 0x806892f, 0x40001c)
Can anyone shed some light on what is going on here? The first three
arguments appear to be the usual three memmove() arguments: dest, src,
and count. The extra two aren't documented anywhere I can find, and
memmove() has always been a three-argument function.
To further confuse things, memmove() isn't the only call with too many
arguments. clock_gettime() is supposed to have two arguments, but
it's called 694 times with five arguments. There may well be other
calls with strange argument counts, but the output has 371800 lines,
and I'm not up to examining all of them.
Dick St. Peters, stpeters(a)NetHeaven.com
Gatekeeper, NetHeaven, Saratoga Springs, NY
I have two printers advertised via avahi-daemon as AirPrint printers.
When avahi-daemon starts up, they're seen via the bonjour devices on the
network. (See log, below.)
After some time, usually within the hour, the bonjour devices can no
longer see the printers, but the local avahi-browser application thinks
they're still there, and there are no errors in any of the logs.
Restarting the daemon immediately makes the printers visible again.
$ avahi-daemon --debug
Found user 'avahi' (UID 495) and group 'avahi' (GID 488).
Successfully dropped root privileges.
avahi-daemon 0.6.27 starting up.
Successfully called chroot().
Successfully dropped remaining capabilities.
Loading service file /services/AirPrint-Marilyn_HP.service.
Loading service file /services/AirPrint-PSC-2200-Series.service.
Loading service file /services/ssh.service.
Loading service file /services/udisks.service.
Joining mDNS multicast group on interface wlan0.IPv4 with address
New relevant interface wlan0.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::211:95ff:febc:e5f3 on wlan0.*.
Registering new address record for 192.168.123.10 on wlan0.IPv4.
Registering HINFO record with values 'I686'/'LINUX'.
Server startup complete. Host name is sds-desk.local. Local service
cookie is 2690789964.
Service "sds-desk" (/services/udisks.service) successfully established.
Service "sds-desk" (/services/ssh.service) successfully established.
Service "AirPlay PSC-2200-Series @ sds-desk"
(/services/AirPrint-PSC-2200-Series.service) successfully established.
Service "AirPlay Marilyn_HP @ sds-desk"
(/services/AirPrint-Marilyn_HP.service) successfully established
Here's one of the service files:
# cat /etc/avahi/services/AirPrint-PSC-2200-Series.service
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">
<name replace-wildcards="yes">AirPlay PSC-2200-Series @ %h</name>
<txt-record>note=Hewlett-Packard PSC 2200 Series</txt-record>
And the avahi-daemon.conf file
# grep -v '#' /etc/avahi/avahi-daemon.conf