[Bug 66809] Re: fonts path mixed up /usr/share/fonts/X11 /usr/share/X11/fonts

2007-07-29 Thread sinewalker
Hi, Can confirm this is still happening in Feisty (found this bug report while looking for a solution). Running the latest FreeNX from seveas (repository: http://seveas.ubuntulinux.nl/feisty-seveas all) Running Windows NX client from NoMachine (2.1.0-17) I have not attempted swapping directorie

[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)

2008-02-26 Thread sinewalker
one wonders whether the people closing this bug as "invalid" are the same arrogant individuals who caused it in the first place, wrt the comment in the blacklist file... In any case, this bug, and especially the opportunity to witness how this ubuntu developer community "includes" all in their pro

[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)

2008-01-14 Thread sinewalker
It seems to me that this bug (or regression of a long-existing feature, which ever way you want to look at it) was introduced in order to fix issues with suspend-to-RAM or hibernate features on computers with frame buffer LCDs (as pointed out to us by Miguel Martinez on Dec 13). It also seems that

[Bug 127168] Re: vesafb sets the refresh rate too high for some LCDs

2007-11-01 Thread sinewalker
Same here, a desktop with Radeon graphics driving a Philips 190B LCD (on the VGA cable, not DVI). Interestingly, if I restart the PC and select an older kernel from before I upgraded to Gutsy (2.6.20-16-generic) then it's okay. I'm starting with the following kernel options in both cases: vga=7

[Bug 127168] Re: vesafb sets the refresh rate too high for some LCDs

2007-12-04 Thread sinewalker
No worries Leann, I'll do it tonight (in about 10 hours). I think this issue is actually pretty much the same as 129910 (tagged Critical) anyway, since that is certainly the effect I see here. But then, I didn't raise either this bug or 129910, and I don't know if Bugdan or Joshua would agree wit

[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)

2007-12-05 Thread sinewalker
Confirmed: still getting the blank ttys with 2.6.24-1 kernel. However, I also couldn't start X, and do not seem to have any evidence of my attempt in system or X logs to bring some light to the problem, sorry. System started up fine without the vga=794 in my boot options (selected 2.6.24-1 in Rec

[Bug 127168] Re: vesafb sets the refresh rate too high for some LCDs

2007-12-05 Thread sinewalker
Confirmed: bug is still present in Hardy kernel 2.6.24-1. After installing the kernel and rebooting, the splash continues to appear (centred as usual), then the screen goes black with a blinking cursor in top-left. KDM/X doesn't start. Had to reboot in Recovery mode (no VGA=) to run X and also