Comment 3 for bug 35833

I can confirm the "Local network browsing" returning the same error twice on my Dapper install as well Kenny.

Oh yes... I forgot to mention I am running Dapper installed fresh from the Flight 5 install CD, with recent updates (Last update at time of post: 03-24-2006).

Also, I have realized that the display module under the kde system settings actually edits the xorg.conf file! I managed to fix my display problems by launching a command terminal and restoring my old xorg.conf from the auto-backup the display module made (called xorg.conf.<n> where <n> is an integer increment).

The old xorg.conf restored my ability to load the Display module, I realized that to recreate this bug, all I needed to do was edit my xorg.conf. I believe this bug is related to possible parsing errors in the xorg.conf file. If the program can't gather the information it needs, it may fail to load. It seems this module needs a bit of work, whenever I try to use it to configure dual displays, it ends up creating an xorg.conf that doesn't realize that my Radeon 9800pro can be treated as 2 display adapters in one. This results in a faulty monitor configuration, and after this edit has been done to my xorg.conf by the program, it may be having troubles parsing it and fails to load. Even after correctly editing the file by hand, and getting a working dual monitor setup running with my video card being treated as two display adapters linked to separate monitors, the display module won't load yet again.
If kubuntu is going to be used by normal users who have no idea how to edit the xorg.conf file, then fixing the Display module is a must. Hope my logic is right here, I don't know what exactly is going on inside the internals of the program... I'm just going by instinct, observation, and an educated guess :D.