ssh to another host on the local lan. I tried running firefox from the CLI, it starts then crashes. Other apps work fine gthumb , xchat, emacs. I thought I might need some special incantation and have found several floating around but no joy. I have also noticed that when I 'exit' from the remote host after running say gthumb or attempting to run firefox that I have to ctrl-C or I don't get the prompt back, however if i log in and don't run any graphical apps it logouts without a problem. Makes me think I am forgetting an option but I have tried various things with firefox and i get the same results.
Another thing about the logout hang is that it doesn't occur when I have used only emacs but if run gthumb or something similar then it will hang on logout and require a ctrl-c.
I haven't to the best of my recollection ever tried running FF(or any other graphical app) on a remote host thru ssh, not generally what I use ssh for but I decided to try it out. Is it broken or have I not properly mixed my dog hair and bat poop. I get the following no matter what recipe I try:
(ssh session from f10 to f11(armadillo)):
[maximus@armadillo ~]$ firefox
debug1: client_input_channel_open: ctype x11 rchan 3 win 65536 max 16384
debug1: client_request_x11: request from 127.0.0.1 46745
debug1: channel 1: new [x11]
debug1: confirm x11
debug1: client_input_channel_open: ctype x11 rchan 4 win 65536 max 16384
debug1: client_request_x11: request from 127.0.0.1 46746
debug1: channel 2: new [x11]
debug1: confirm x11
debug1: channel 1: FORCE input drain
debug1: channel 1: free: x11, nchannels 3
Xlib: extension "Generic Event Extension" missing on display "localhost:11.0".
Xlib: extension "Generic Event Extension" missing on display "localhost:11.0".
Xlib: extension "Generic Event Extension" missing on display "localhost:11.0".
Xlib: extension "Generic Event Extension" missing on display "localhost:11.0".
Xlib: extension "Generic Event Extension" missing on display "localhost:11.0".
Xlib: extension "Generic Event Extension" missing on display "localhost:11.0".
debug1: client_input_channel_open: ctype x11 rchan 3 win 65536 max 16384
debug1: client_request_x11: request from 127.0.0.1 46747
debug1: channel 1: new [x11]
debug1: confirm x11
debug1: channel 1: FORCE input drain
debug1: channel 1: free: x11, nchannels 3
Xlib: extension "Generic Event Extension" missing on display "localhost:11.0".
debug1: channel 2: FORCE input drain
debug1: channel 2: free: x11, nchannels 2
/usr/lib/firefox-3.1b3/run-mozilla.sh: line 131: 2546 Segmentation fault "$prog" ${1+"$@"}
--
"Any fool can know. The point is to understand" --Albert Einstein
Bored??
http://fiction.wikia.com/wiki/Fuqwit1.0http://fiction.wikia.com/wiki/Coding_the_Magic_into_the_Eight_Ball
A few impressions from a quick F11 preview test. I burned the livecd iso to
CD - then test booted the CD on a Dell D610 laptop. Worked but rather slow
since files constantly being pulled from the CD. With the livecd still
running I did a "yum install livecd-tools" and then plugged in a usbkey and
made a bootable F11 Preview usbkey with a persistent storage area.
This booted nicely and quite fast. Wireless networking in gnome worked well
to a WPA2 access point, and I noted that the NetworkManager options at last
has the option to make the wireless connection available to all users -
although I did not test this I presume that this means it will have wireless
active on bootup next time.
A few tests on the menus and everything worked that I tested. No major
faults apart from when I shut down using the gnome direct shutdown and the
system hung before it shut down propoerly. There is an existing bz on hang
during shutdown so it is possible what I saw was the same bug.
Anyway first impressions are favourable and this looks generally like F11
will be a good release.
One thing that needs to be clarified is how the availability of ext4 will
affect install decisions for systems already running F10. Although I did
not install to HD, when F11 is released the decision will need to be made to
switch over to ext4 or not for at least some of the partitions on the system
- at present I use / and /opt as separate partitions with /home as a
subdirectory of /opt - without a /boot separate partition then I guess the
only option will be to keep the root partition as ext3 for the present
since grub won't honour ext4 yet. However if the main HD was re-partitioned
to make a new /boot partition then I guess /boot left as ext3 with anaconda
reformatting the root partition as ext4 for the install will be a way
forward?
For /opt I suppose that making a backup ahead of the install and then
getting the install to reformat /opt as ext4 as well and then copying back
(rsync -X) to /opt from backup will preserve the files intact on the
reformatted partition?
I guess that most people develop their own way of "upgrading" from one
release to the next but this is an area that is generally not extensively
documented apart from lots of bits of answers spread out over many questions
on forums. I prefer clean installs every time but I still need to keep user
areas and personalised files etc in /opt preserved for use in the new
system.
--
View this message in context: http://www.nabble.com/F11-Preview---test-with-usbkey-tp23311298p23311298.ht…
Sent from the Fedora Test List mailing list archive at Nabble.com.