Linux desktop is really buggy

You will meet hundreds problems when using linux as a desktop.
usually, we can get a solution via searching internet.
solved, you though you are a geek, actually not.
get stuck, you go to windows. But i did not.

I solved several problems today, some is not yet.

enable HDMI audio using ALSA. also works on flash, youtube.

the grub is buggy. hd0,hd1 is not like sda,sdb, they change when you change boot order in BIOS. make a GPT boot partition.

fonts fixed.

ibus on kde not success.

copy .Xauthority to /root to let root use X11 functions.


There are lots of config, some can be configured, some cannot.
They are hidden from users. And not so smart, the program donnot like to guess,
donnt like to assert sometime. They fail-fast dumbly or fail without error message. But I cannot do it myself now, have to bear the crap stuff.
So linux desktop to me now means "10x time to make things done".

If someone say he feel home at linux, or a linux fan, I doubt it.

Cannot connect to DISPLAY after su

[i copy it from http://jianmingli.com/wp/?p=724]

Cause:

X win cookie not carried over after sudo login as another user.

Solutions One:

1. Login as first user (user1).
2. Run 'echo $DISPLAY'

 
bash-3.00$ echo $DISPLAY
localhost:10.0
 

2. Run 'xauth list'

xauth list
box.my.com/unix:10  MIT-MAGIC-COOKIE-1  4f76c629f8cdbf26ce4ae646cc24448c
box.my.com/unix:11  MIT-MAGIC-COOKIE-1  1acd10ab0fd098a86aba7aa691d7c067
box.my.com/unix:12  MIT-MAGIC-COOKIE-1  e007ee6844c417a6b866d66c7bbcbc7d

For Solaris 10, xauth is in the /usr/openwin/bin directory.
3. sudo to second user (user2) with command like

sudo su - user2

4. Set $DISPLAY env to the same as user1's.

 
DISPLAY=localhost:10.0; export DISPLAY
 

5. Run "xauth add" and append the entry from user1's "xauth list" that matches the display number. For example, user1 $DISPLAY is localhost:10.0, so we'll append box.my.com/unix:10entry.

xauth add box.my.com/unix:10  MIT-MAGIC-COOKIE-1  4f76c629f8cdbf26ce4ae646cc24448c

6. Test with xclock:

 
xclock

neoe's config-driven development

I began to write a new program.
I write in different ways each time.
this time I begin with a rich config file.
I realized I applied a new approach.
It can be called config-driven development, just the name, you know things are great different having the same name.

pros:
features are determined early.
the input data(const, configurable parameters, etc...) is determined early.
the config file is written in neoe-way(called "smart simple") on contrary of "xml verbose dumb way".
if config file is good enough, it acts like a script language.

cons:
more efforts on code.

project getting fatter

I see a lot of opensource projects get fatter and fatter. Is it a good phenomena? Maybe not.
getting fatter it will get out of control, out of capacity of understanding of human.
There are also some projects keep fit over years. I admire them.