steelmaverick reports that it's possible to get
 browser-eal
 tablet-browser-controls + browser-eal

using application manager in blue pill mode (without installing the microb
developer release [Mozilla based browser for maemo]).

Here are steps to reproduce (they're not the steps that steelmaverick used, and
I'd appreciate it if people read the footer to this bug and help).

Preconditions: un-metered WiFi access to the internet (configured, active,
enabled, working). bora-extras repository not configured (check application
manager). en-US locale. Device backed up, all settings, installed packages,
software, repositories, steps to retrieve all installed packages carefully
documented so you can return to this point. 4.2007.26-8 flashed. Blue pill mode
(if you don't know what this means, don't worry, it's a default)
1. open browser
2. load about:
2' Mozilla/4.0 ... Opera 8.5 ... RX-34_2007_SE4.2007.26-8
3. load http://browser.garage.maemo.org/
4. tap "installation instructions"
4' should load http://browser.garage.maemo.org/#install-pane
5. tap "this url"
5' File download
Name: microb-browser.install
Type: application/x-install-instructions
...
Address:
http://repository.maemo.org/extras/dists/3.2/install/microb-browser.install

(actually that's truncated, but i'm including the full url here)
6. tap Open
6' Add catalog
... bora-extras
7. tap OK
8. tap Cancel
9. tap Check for updates
10. multiple choice begins here.
(scroll to and) tap browser-eal
11. tap Update
Update?
browser-eal 0.0.5-1
12. tap Details
12' Installed version: 0.0.4-1
Available version: 0.0.5-1
13. tap Updating
13' Updating browser-eal requires 0 kB of device memory
14. tap Close
15. select the web browser from task navigator
16. close it
17. say the "last rites" for the browser.
<- non destructive steps end here ->
18. tap OK

10. multiple choice alternate.
(scroll to and) tap tablet-browser-controls
11. tap Update
Update?
tablet-browser-controls 0.1.13-1
12. tap Details
12' Installed version: 0.0.14-1
Available version: 0.1.13-1
13. tap Updating
13' Updating tablet-browser-controls requires 4 kB of device memory
Application packages to update: tablet-browser-controls 0.1.13-1
browser-eal 0.0.5-1
14. tap Close
15. select the web browser from task navigator
16. close it
17. say the "last rites" for the browser.
<- non destructive steps end here ->
18. tap OK

Actual results:
http://www.internettablettalk.com/forums/showpost.php?p=62184&postcount=1
the option to open a link in a new windows is gone
link details and help options are switched.

http://www.internettablettalk.com/forums/showpost.php?p=62564&postcount=18
the windows manager started going crazy when using more than one opera window
After some time of use, the system started switching between two windows and
stopped only clicking on the menu-bar.

Note:
This bug is being filed publicly to demonstrate how I'd like people to file
bugs. Please take detailed notes. Please be specific. A bit of humor is OK
especially if it outlines points of no return. Generally cursing in bug reports
will not get attention faster. Reporting bugs in talk forums will not get
things fixed faster.

Once your system is broken as such, you have the following choices, you can:
1. reflash (full rollback)
2. install microb (full forward progress to a beta, sorry)
3. switch to red pill mode and install a couple of packages:
 osso-browser-opera-eal
 tablet-browser-ui
 tablet-browser-default-plugin
-- This list isn't official, it's from jurop88
http://www.internettablettalk.com/forums/showpost.php?p=62209&postcount=6
4. install microb and then remove it from package manager
5. wait for us to provide updated packages which have dependencies that will
force a result equivalent to 4.

Unfortunately, from talking to the Application manager engineer, and from an
understanding of the goals and plans we have, there's no practical way for us
to ship packages that would properly provide for a rollback of just the
relevant packages. most attempts would result in pain for people who already
have microb installed.

Root causes:
a. the two upgradeable packages transitioned from libs to user/libs - note that
people in red pill mode could have been affected without this problem
b. misinterpretation of definition of term "dependencies" (domain: debian.
domain: legal)

I believe that future testing will include a few more tests to make sure more
upgrade paths are tested. But practically speaking, our testers didn't know to
test these variations so testing wouldn't have helped.

It is possible for someone to repackage the older versions of these files and
create a repository which lists the package as conflicting with newer versions
but upgrading these versions so that people could get opera back into working
order. I'll probably write steps for this sometime.

Open questions:
How did people get this repository installed?