Webinterface menue in 2 rows after update
-
Problem is the GUI itself. If it was W3C compliant then fonts would not be an issue.
http://validator.w3.org/
-
Yeah - I'm not suggesting there is nothing wrong. I'm suggesting they will fix it fast, so I'm not that worried now that they know.
-
I am having the same issue here with Firefox 31.0 running under openSUSE 13.1/KDE4.11.5. Cleaning the cache does not help.
The menue issue is very annoying because it prevents me even from using the "System" menu at all. I am always pushed into the "Help" menu.
Thanks for the hint to manually restrict fonts. As it took me some time to find the right version of all.css to change, I give here the full path:
/usr/local/www/themes/pfsense_ng/all.cssRegards,
Peter -
I wouldn't put my money on them cleaning this mess up:
https://redmine.pfsense.org/issues/3841
The Bug was outright REJECTED.
Go figure.
-
The bug was rejected because there were several opened around the same time with identical descriptions and none of them had relevant information about the actual issue, they were ones who needed to clear their caches or who didn't indicate that they had already done so or tried other browsers, etc.
If there isn't one left open that is specific to the Linux font issue, one could be submitted and it would be kept open since that is a valid and confirmed issue.
-
If there isn't one left open that is specific to the Linux font issue, one could be submitted and it would be kept open since that is a valid and confirmed issue.
That was the one already linked above. I guess noone's going to file another one.
-
WELL,
then please reopen that bug.I've now tried it all on ubuntu14.04/firefox, including clearing the cache, (via menu, via ctrl-F5, reloading via F5, ctrl-shift-r, yoou name it), opening the whle thing in only one tab, on one window or fullscreen, all of that. UI keeps being unusable.
Ah, and well, if you close bugs as being dupes, then do it soas everybody can see it? Might help in not getting flak. Rejecting the bug deliversa some other message.
-
AH well,
if someone could be so kind as to post the urls for the System menu pages?
-
I'd prefer a fresh bug with the correct info in the title/description rather than buried in comments.
It works fine on my Ubuntu 14.04 laptop and an Lubuntu 14.04 VM (see attached) - Which is where I tested it myself, though others around use different flavors (e.g. Mint)
It is a LOT more subtle issue than it's being made out to be.
EDIT: Screenshots are Firefox 31, but Chromium is the same.
-
AH well,
if someone could be so kind as to post the urls for the System menu pages?
Here's the best source of info for the URLs:
2.2: https://github.com/pfsense/pfsense/blob/master/usr/local/www/fbegin.inc#L99
2.1.x: https://github.com/pfsense/pfsense/blob/RELENG_2_1/usr/local/www/fbegin.inc#L99 -
Could you please be so kind? I am not registered in the tracker.
And i'd love to put hits off as far minor, but if you're stuck with it, it is NOT. No user mgr, no routing, no DNS setting, no LOGOUT ….
Glad you can get to the update page vie the dashboard.
If you're stuck with it, it really really sucks.
and, by the way:
/system_advanced_admin.php
/system_camanager.php
/system_firmware.php
/system.php
/system_hasync.php
/index.php?logout
/pkg_mgr_installed.php
/system_gateways.php
/wizard.php?xml=setup_wizard.xml
/system_usermanager.php -
I'm not saying it's minor – for those it affects it is major -- I'm saying it's more subtle, as in it's not as obvious as people are saying. Whinging about a lack of testing for example.
For reference, on my Lubuntu VM I don't have Tahoma installed, nor do I have Verdana or Arial or Helvetica which may be a better thing to check for. What fonts do you have installed? Maybe it's not just that Tahoma is missing but that Tahoma is missing but you have Verdana, etc. What add-on font packages do you have installed? ttf-liberation? ttf-mscorefonts-installer? Something else?
EDIT: The reasoning for wanting to know the above is so that more of us can replicate and confirm a potential fix.
-
I'm not saying it's minor – for those it affects it is major -- I'm saying it's more subtle, as in it's not as obvious as people are saying. Whinging about a lack of testing for example.
Right you are! Now i got your idea.
For reference, on my Lubuntu VM I don't have Tahoma installed, nor do I have Verdana or Arial or Helvetica which may be a better thing to check for. What fonts do you have installed? Maybe it's not just that Tahoma is missing but that Tahoma is missing but you have Verdana, etc. What add-on font packages do you have installed? ttf-liberation? ttf-mscorefonts-installer? Something else?
EDIT: The reasoning for wanting to know the above is so that more of us can replicate and confirm a potential fix.
Hmm, no ttf-liberation. ttf-mscorefonts=yes.
I just tried with firefox in safe mode, all add-ons deactivated. no change.
I'll try the ttf-liberatio way now. maybe that's it. Will keep you posted here.
-
no change after installing the ttf-liberation either.
font-browser sais i have verdana.
Will now try rebooting the firewall once over (did the reboot automatically after the upgrade, but who knows).
-
ttf-mscorefonts-installer seems to be the one that causes it. It adds Verdana and Arial but not Tahoma, and since removing Verdana from the CSS line appears to be what "fixes" it for people then Arial must be OK.
After adding that package I can replicate it locally.
$ fc-list | egrep -ci '(tahoma|verdana|arial|helve)' 16 $ sudo apt-get remove ttf-mscorefonts-installer [...] $ fc-list | egrep -ci '(tahoma|verdana|arial|helve)' 0That narrows it down…
-
I created https://redmine.pfsense.org/issues/3842 with the correct and relevant information. That should let us dial in and test a fix a lot easier.
-
aye,
firewall-reboot didn't fix it,
subsequent laptop-reboot didn't fix it.BUT REMOVING ttf-mscorefonts-installer FIXED it!!!!
There ya go!
Now, thing is, having verdana on the system makes some sense if you exchange .docs.
I can live with that for the moment, but i think it needs fixing.
-
http://en.wikipedia.org/wiki/Core_fonts_for_the_Web
These should be the ones tested for on every major OS and 3-4 major browsers.
-
Removing Verdana from our list of fonts in CSS is probably the best fix. In other threads, people have said that has also been enough to make it render properly.
-
Find "#navigation" in /usr/local/www/themes/pfsense_ng/all.css
Change from
width: 750px;
TO
width: 950px;So it reads like:
#navigation {
position: fixed;
top: 0px;
left: 100px;
width: 950px;
padding: 0px;
height: 28px;
z-index: 3;
}
Reload the browser css or alt-f5 to clear cache
Not the prettiest, however prettier than it started.
