| [02:26] <Cheesasaurus_Rex> I'm having a problem. My fonts are being displayed at 120dpi even when I set it to 96dpi. The only way I can seem to get 96dpi is to force it with startx. | |
| [02:26] <Cheesasaurus_Rex> This has only happened to me in Xubuntu. | |
| [02:36] <xodiak> Maybe a simple question.... Which is lighter on resources, Gnome or KDE? | |
| [02:36] <Cheesasaurus_Rex> Gnome is | |
| [02:36] <xodiak> Thanks | |
| [02:36] <Cheesasaurus_Rex> welcome | |
| [02:37] <godlygeek> xodiak: xfce is lighter still, try xubuntu! :) | |
| [02:43] <godlygeek> Cheesasaurus_Rex: and, actually, kde is lighter on memory than gnome by most benchmarks i've seen. | |
| [02:44] <Cheesasaurus_Rex> I'll believe that | |
| [02:44] <Cheesasaurus_Rex> but Ubuntu requires less RAM to run than Kubuntu | |
| [02:44] <Cheesasaurus_Rex> although that doesn't necessarily mean that KDE requires more than gnome... | |
| [02:46] <godlygeek> Here, for example: http://ktown.kde.org/~seli/memory/desktop_benchmark.html :) | |
| [02:47] <Cheesasaurus_Rex> hm, interesting | |
| [02:47] <Cheesasaurus_Rex> so it uses less resources despite all that bloat, eh? | |
| [02:47] <Cheesasaurus_Rex> would you happen to have an answer to my question above, godlygeek? | |
| [02:47] <godlygeek> i don't know anything about fonts, i'm afraid... | |
| [02:48] <godlygeek> i don't even know how you'd be able to tell that you're getting 120 instead of 96 dpi fonts... :) | |
| [02:48] <Cheesasaurus_Rex> you'd know | |
| [02:48] <Cheesasaurus_Rex> The fonts would be sort of huge | |
| [02:49] <godlygeek> why would the number of dots per inch affect the number of characters per inch? | |
| [02:49] <godlygeek> if it does, i'd expect larger DPI to mean smaller font sizes... | |
| [02:50] <Cheesasaurus_Rex> it uses more dots to draw the font | |
| [02:50] <Cheesasaurus_Rex> that's why | |
| [02:51] <godlygeek> that only makes sense if dots == pixels... | |
| [02:51] <Cheesasaurus_Rex> they do | |
| [02:52] <godlygeek> but, you can't change the number of pixels per inch... | |
| [02:52] <godlygeek> that's fixed... | |
| [02:52] <Cheesasaurus_Rex> No, but you can change how many pixels they use for fonts | |
| [02:52] <godlygeek> but then that's not dpi... it's dots per glyph, or something... | |
| [02:53] <Cheesasaurus_Rex> I didn't come up with the terminology | |
| [02:53] <Cheesasaurus_Rex> so you'll have to ask someone else that | |
| [02:56] <mr_sukor> help | |
| [02:56] <godlygeek> Cheesasaurus_Rex: xdpyinfo | grep resolution ? | |
| [02:57] <Cheesasaurus_Rex> that gives me 121x120 when I don't force it with startx, but that shouldn't matter | |
| [02:58] <Cheesasaurus_Rex> you can set the font DPI in the User Interface in the Settings Manager | |
| [02:58] <Cheesasaurus_Rex> I have it set to 96 there, and it's still giving me 120dpi fonts | |
| [03:00] <godlygeek> are you passing startx any params? | |
| [03:01] <Cheesasaurus_Rex> when I boot normally, no | |
| [03:01] <godlygeek> you said that it works when you use startx, right? | |
| [03:01] <Cheesasaurus_Rex> when I do startx -- -dpi "96x96" yeah | |
| [03:02] <Cheesasaurus_Rex> I think it might be a driver issue since it was fine until I installed the nvidia driver | |
| [03:02] <godlygeek> then the problem is that x isn't using 96 dpi by default - which has nothing to do with the xubuntu settings... | |
| [03:02] <Cheesasaurus_Rex> no | |
| [03:02] <Cheesasaurus_Rex> even if it uses 121x120, it should use 96 dpi | |
| [03:02] <godlygeek> no? | |
| [03:02] <godlygeek> i don't think it can... | |
| [03:02] <Cheesasaurus_Rex> because before I installed this driver | |
| [03:02] <Cheesasaurus_Rex> I would get 96dpi | |
| [03:03] <godlygeek> but that's probably because the nvidia driver install regenerated xorg.conf... | |
| [03:03] <godlygeek> and removed the part that would allow for 96 dpi fonts. | |
| [03:03] <Cheesasaurus_Rex> It shouldn't because it wasn't there to begin with. | |
| [03:03] <godlygeek> what's this do: grep DisplaySize /etc/X11/xorg.conf | |
| [03:06] <Cheesasaurus_Rex> nothing, but it was never there to begin with, even in a backup before I installed the driver in Xubuntu | |
| [03:06] <Cheesasaurus_Rex> *not even | |
| [03:08] <godlygeek> Cheesasaurus_Rex: *shrug*... are you against adding it and seeing if it makes things work? | |
| [03:08] <Cheesasaurus_Rex> I already tried that | |
| [03:08] <Cheesasaurus_Rex> I only came here as a last resort :/ | |
| [03:10] <godlygeek> well... to me it would make sense that the app can't override settings in the server... | |
| [03:11] <Cheesasaurus_Rex> but to me it doesn't, because it did before, until I got the driver | |
| [03:12] <godlygeek> that's proof, though, that it's a change at the server level that's affecting things. | |
| [03:12] <godlygeek> that might mean that the old driver chose 96 dpi as its default res, and the nvidia one chooses 120... | |
| [03:12] <godlygeek> When you add the DisplaySize setting to the "Monitor" section, does /var/log/Xorg.log report 96 dpi? | |
| [03:14] <Cheesasaurus_Rex> no, it didn't | |
| [03:14] <godlygeek> what did you put for DisplaySize, and what's your monitor's resolution? | |
| [03:15] <Cheesasaurus_Rex> I don't remember, but I know that didn't work. | |
| [03:15] <Cheesasaurus_Rex> It's 1440x900. | |
| [03:17] <godlygeek> if it broke when you changed something at the server level, and you can fix it by changing a server parameter, there's no way you can fix it without changing something at the server level... | |
| [03:18] <godlygeek> that's not font-specific, that's just knowledge of the architecture... | |
| [03:18] <godlygeek> it means that the old driver did something differently from the new driver WRT choosing DPI... | |
| [03:18] <godlygeek> and that you'll need to tell the new driver what to use for the DPI. | |
| [03:18] <Cheesasaurus_Rex> well | |
| [03:19] <Cheesasaurus_Rex> I've used this driver in Ubuntu too | |
| [03:19] <Cheesasaurus_Rex> (as opposed to Xubuntu) | |
| [03:19] <Cheesasaurus_Rex> without this problem | |
| [03:20] <godlygeek> *shrug* - alright, maybe i'm wrong... but everything i'm seeing on the internet says that you need to have the x-server running at the desired DPI before tweaking anything with the fonts. | |
| [03:33] <godlygeek> Cheesasaurus_Rex: btw - the supposed bloat of KDE apps is because of their massive shared libraries... | |
| [03:33] <godlygeek> Cheesasaurus_Rex: but, that means that the cost for running a single KDE app is relatively much greater than running an entire desktop, where the shared libraries are actually being shared. | |
| [04:04] <xodiak> godlygeek: catching up here. I am on xubuntu because this old system can't handle ubuntu too well. (don't remember where) but I saw an option where I could choose between Gnome and KDE | |
| [04:05] <xodiak> Gnome was selected by default so I thought that I was using it. (total noob here so forgive the stupidity) | |
| [04:54] <lobazo> please help me i can't restart cups in a terminal i wrote sudo /etc/init.d/cupsys restart it's says ok. but my printer hp 3740 is flinking | |
| [06:01] <___Alex___> is xubuntu 8.04 less buggy than it's gnomish cousin? | |
| [06:03] <___Alex___> how about xubuntu 8.04 vs 7.10? are they equally stable, or is 7.10 more stable? | |
| [06:10] <zoredache> please define how 'stablility' should be measured? To me it sounds like a meanlingless word | |
| [06:17] <Yashy> like BSD, break it down to sizes you're comfortable working with... | |
| [06:34] <bloodboy> http://img297.imageshack.us/img297/883/av1894tg1.gif | |