You are not logged in.
Pages: 1
Hello!
I did a pacman -Syu this morning and upgraded phoenix to 0.5-4. It seems I have the same problem I had with mozilla a few weeks back (in this thread): Entering text causes it to freeze. With mozilla the problem was resolved by disabling find-as-you-type.. Problem is I don't know how to do this with phoenix. Trying to type about:config causes it to freeze, there are no meny options and I can't find any config file.
Removing the .phoenix and /opt/phoenix and reinstalling makes no difference. I guess find-as-you-type is enabled by default.
Any ideas?
"Plurality should not be assumed without necessity" or "keep it simple"
- William of Ockham (1285-1349)
Offline
I don't have that problem with 0.5-4, but I have had it in the past (with mozilla too).
I know this is arcane and probably not the solution you need, but check to make sure your lo loopback interface is up. If it isn't for some reason, mozilla/phoenix freezes as soon as it receives keyboard input.
Offline
I actually am writing this in mozilla 1.3-2 (disabeling type ahead find fixed it) so that seems to rule out that option. For the record ifconfig lo spits out the following data, this means loopback is enabled?
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Thanks anyway. I probably should go and bug (or debug?) the folks at mozilla.org instead..
"Plurality should not be assumed without necessity" or "keep it simple"
- William of Ockham (1285-1349)
Offline
Thanks apeiro - I have had the 'freeze' all to often so went with Opera instead (yukkers) - never thought about the lo being disabled (which it was ).
Offline
I'd say that looks disabled...?
I'm not sure, but here's what my 'ifconfig lo' looks like:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:357467 errors:0 dropped:0 overruns:0 frame:0
TX packets:357467 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:97429142 (92.9 Mb) TX bytes:97429142 (92.9 Mb)
note the large # of packets/bytes.
it's probably really easy to turn back on tho, probably you have
INTERFACES=(!lo eth0)
in your rc.conf just un-exclaim the lo.
or add it if it's not there and add
lo="lo 127.0.0.1"
Hapy.
Offline
You might be correct on lo not being in use. Still it is uncommented in the rc.conf and the entry for it is there.. :?
"Plurality should not be assumed without necessity" or "keep it simple"
- William of Ockham (1285-1349)
Offline
The problem appears to be conntected to fonts (and find-as-you-type). I made a fresh install of Arch today and on first boot phoenix (0.5-4) worked fine. When I edited XF86Config to load freefonts the old problem reoccured. Reversing the change, re-installing phoenix, removing .phoenix .mozilla and every fontcache on the system didn't fix it.. :?
I have mozilla working with freefonts (works only after disabeling find-as-you-type),, though it seems like icewm decided to not use them in mid-session... Ah., well. Time to sleep.
Offline
This problem remains still remains in Mozilla Firebird. Fortunatly I found a workaround:
To disable find-as-you-type pull up your favorite editor and edit /opt/firebird/lib/mozilla-1.5b/defaults/pref/all.js (I'm using the firebird-head package from incoming, the path might be different for other packages).
pref("accessibility.typeaheadfind", true);
Change true to false.
pref("accessibility.typeaheadfind", false);
Enjoy.
Offline
Pages: 1