Just upgraded Konqueror, now can't configure it

[Greg Ward <gward@mems-exchange.org>]

Hi -- I just "upgraded" to the latest Konqueror from 2.1.1-6 to
2.1.1.0-0.potato3.  Is this an upgrade?  The version numbers are
confusing.

(In /etc/apt/sources.list, I have:
  deb http://kde.tdyc.com/ potato main crypto optional

Here are excerpts from running "apt-get install konqueror":

 # apt-get install konqueror
 Reading Package Lists... Done
 Building Dependency Tree... Done
 The following extra packages will be installed:
   kdebase-libs kdelibs3 libkonq3 
 4 packages upgraded, 0 newly installed, 0 to remove and 295 not upgraded.
 [...]
 Get:1 http://kde.tdyc.com potato/main kdebase-libs 4:2.1.1.0-0.potato3 [631kB]
 Get:2 http://kde.tdyc.com potato/main konqueror 4:2.1.1.0-0.potato3 [1661kB]
 Get:3 http://kde.tdyc.com potato/main libkonq3 4:2.1.1.0-0.potato3 [220kB]     
 Fetched 2512kB in 8s (295kB/s)                                                 
 [...]
 Setting up kdelibs3 (2.1.2-0.potato1) ...

 Setting up kdebase-libs (2.1.1.0-0.potato3) ...

 Setting up libkonq3 (2.1.1.0-0.potato3) ...

 Setting up konqueror (2.1.1.0-0.potato3) ...
 [...]

...ie. it looks like everything downloaded and installed OK.)

Anyways, here's the problem: when I start the new version and go to the
"Settings|Configure Konqueror..." menu, I get a bunch of error dialogs:

   There was an error loading module
   'Settings/FileBrowsing/kcmkonq.desktop'
   The diagnostic is:

There is *no* diagnostic message: apart from the "OK" button, that's
it.  This dialog repeats for
  'Settings/FileBrowsing/filetypes.desktop'
  'Settings/FileBrowsing/konqhtml.desktop'
  'Settings/FileBrowsing/cookies.desktop'
  'Settings/FileBrowsing/proxy.desktop'
  'Settings/FileBrowsing/useragent.desktop'

Ie., I have to hit "OK" 6 times on 6 different error dialogs just to get
to the configuration dialog.  When I finally get there, most
configuration options are gone -- all I can configure is "Enhanced
Browsing" and "Netscape Plugins".  Yayhh.

So is this a packaging error, ie. were a bunch of configuration modules
accidentally dropped on the floor between release 2.1.1-6 and
2.1.1.0-0.potato3?  Or is it something else?

Thanks --

       Greg
-- 
Greg Ward - software developer                gward@mems-exchange.org
MEMS Exchange                            http://www.mems-exchange.org