We could, but I wouldn't recommend it, as I might explode. I had the discussion with timeless a few months ago and it came down to that goddamn sonuva***** UI spec. . . .

Anybody who defines their homepage as about:blank obviously does so intentionally, so warning them about it everytime they open their browser is high stupidity.

That I can agree with you...

OK, so I alerted timeless to bugs #2405 and #3179 and they've been assigned.

I mentioned the fullscreen and itT bugs, too, so we'll see on those.

Also, bug #3061 has been fixed, so you can file new bugs under the correct version, just be sure to include the build version (should be 3.2008.19-3 for most of you right now, confirm in Control Panel), as that's particularly critical for these frequently-updated pre-release builds.

Ah, looks like I'm no longer needed.

Oh, don't get your panties in a bunch.

Part of my desire for the 4.1 version now goes back to bug #630, in that I'd like to try and provide as little incentive as possible for developers and other Nokians to avoid Bugzilla.

Besides, there are plenty of people who can't or wont use Bugzilla, and their bug reports still need to go to the right places (and Bugzilla bugs might also need some attention to be imported quickly before we hit release).

I still have to spend hours to just get the examples to just rebuild using "dpkg buildpackage" on Chinook (for the ARM target).

Would it be too much to ask to take a clean install of Ubuntu, Redhat, Suse, or whatever, and follow the instructions EXACTLY (or better yet, do a script) with all the apt-get update/upgrade whatevers and make sure all the hello-world applications will build from the .tgz files by just going into the directory and typing dpkg-buildpackage.

For the statusbar: http://maemo.org/development/documen...for_maemo.html, I can't find a single app that will build properly (and worse, the hello-world-(statusbar/home/taskman) seems to want to delete libtool, then complains it can't find it). config.sub and config.guess are there, but I have to delete the symlinks and manually copy the files.

Nokia might complain about lack of interest, but I don't have weeks to devote to figuring out how to set up the build environment - which with the build system - autogen, automake, config*, then with the includes and libs for osso, hildon, dbus, gtk and all the other stuff is dependent on so many things EVERY ONE OF WHICH MUST BE CORRECT. And it never seems to be correct "out of the box". There is some hidden step, command, process, whatever. Some library or archive that needs a -dev which isn't obvious and requires a lot of searching, just to get to the next missing piece.

I don't have this problem with Ubuntu, or Fedora or most other distributions. There is usually a package manager with search that will show that an XYZ-dev exists.

If in order to build target binaries with osso, hildon, etc, I need to do apt-get install on a lot of files, or add archives, or whatever, please document it.

There isn't an official "on system" build, but I might go to that (I had to for my Zaurus).

Most here probably already have everything all set up correctly so it just works for you. But I can't read your mind, nor do I have your /scratchbox directory with everything perfectly configured. I can only follow instructions.

So PLEASE PLEASE PLEASE write up a HOWTO to set up the build environment for Diablo when it comes out. And I don't mind patching or hacking the hello world programs or doing post install updates or anything else as long as I know what is required and that at the end I can just download the tarball, unpack it, and type dpkg buildpackage and have it just work for all the examples at http://maemo.org/development/documentation/how-tos/4-x/ that link to tarballs? Even if there is a 4.1 howto full of patches it would make things so much easier.

I haven't done it yet, but you mentioned an on-tablet build environment, and that's the way I'm going. (I sorta had one, back in my broken Chinook install, but I didn't have room to install headers for many libraries.) I think it's the most suitable way, for light work. You might not want to compile KDE that way, but apps will probably do fine.

20-4: New additions are underlined.

I believe, it would be more readable if you created a new entry for new bugs and just edited the original post when a bug is fixed

I have encountered an issue in backup/restore utility. (You are asked to create a backup before you perform an os update. This is a nice touch. And needed :-) as my n810 does not want to boot after update )

When you start creating a backup, there is a progress dialog which allows you to cancel the action. I clicked on the cancel: I got a confirmation window "blah blah was canceled blah blah", new a NEW backup file appeared in the list. It was quite a small file, so I believe it was incomple, likely corrupted. (Did not dare to do back up from it)