nspluginscan crashes on startup; Protocol not supported: http

[Bruce Miller]

Binary package hint: kdebase

Have *_zero_* functionality in konqueror

Following a disk crash which wiped out (a carefully backed-up) /home drive, performed a clean install of Kubuntu Lucid Lynx beta 1 on 2010-03-20. Have reported in separate bug that KDE appears to load neither a WM nor a DE, that is, it is totally unusable.

on first start-up, a dialog consistently reports crash of nspluginscan. Despite having installed debug packages recommended by KDE crash dialog, it consistently claims insufficient information to report to KDE.

Also receive every few seconds a dialog box stating:
"Could not delete /home/bruce/.kde/share/apps/konqueror/autosave/owned-by-1.nn" (where nn are digits)

I have had several previous and serious KDE problems because of years of cruft accumulated in the config ("dot" files) of my home directory. Because of the wipeout of my data drive, this was a brand-new, empty home partition.

All attempts to load a website fail with the error: Protocol not supported http

ProblemType: Bug
Architecture: amd64
Date: Mon Mar 22 10:16:33 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info'
NonfreeKernelModules: nvidia
Package: konqueror 4:4.4.1-0ubuntu3
ProcEnviron:
 PATH=(custom, user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SourcePackage: kdebase
Uname: Linux 2.6.32-16-generic x86_64

[Bruce Miller (brm0423)]

Forgot to include:
this problem affects the amd64 instance only. My ia32 setup, which has been running Kubuntu 10.04 Alpha versions since 2009.11, continues to run routinely.

[Jonathan Thomas (echidnaman)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!