Re: When I try to save html pages, nothing happens
On Monday 29 October 2007 13:11, Andrew Sackville-West wrote:
> On Mon, Oct 29, 2007 at 01:05:34PM -0700, tom arnall wrote:
> > When I try to save html pages or whatever with firefox, nothing happens.
> > (i recently screwed up the permissions on my system.) but if i start it
> > as root ('sudo'), or use iceape, all is ok.
>
> what specifically happens? do you get a save dialog at all? does it
> seem to save but leave no file?
>
> regardless of the above, based on your whole permissions history, I'd
> say you should remove and reinstall firefox as a good starting point.
>
> A
no save dialog, tho' nothing like a complaint that it can't save. it acts in
other words as if a good save except that nothing gets save, BUT if i look in
the ff error console, i find:
Error: null has no properties
Source File: chrome://mozapps/content/downloads/downloads.js
Line: 545
Error: not well-formed
Source File: file:///home/kloro/.mozilla/firefox/uvxnoydh.Default%20User/\
downloads.rdf
Line: 3125, Column: 36
Source Code:
<RDF:Description RDF:about="/tmp/É-Å(Þ·²ÎÒÒ.mp3"---
Error: uncaught exception: [Exception... "ServiceManager::\
GetService returned failure code:" nsresult: \
"0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)" location: \
"JS frame :: chrome://mozapps/content/downloads/\
downloads.js :: Startup :: line 476" data: no]
Error: null has no properties
Source File: chrome://mozapps/content/downloads/downloads.js
Line: 545
also, when i did reinstall, i got the message:
Reading changelogs... Done
Error: "/var/tmp/kdecache-kloro" is owned by uid 1000 instead of uid 0.
Link points to "/var/tmp/kdecache-rootcohchy"
Error: "/tmp/kde-kloro" is owned by uid 1000 instead of uid 0.
Link points to "/tmp/kde-root"
Error: "/tmp/ksocket-kloroyr3bC5" is owned by uid 1000 instead of uid 0.
Link points to "/tmp/ksocket-root"
Error: "/var/tmp/kdecache-kloro" is owned by uid 1000 instead of uid 0.
Link points to "/var/tmp/kdecache-rootcohchy"
apt-listchanges: Do you want to continue? [Y/n]?
thanks,
tom
Reply to: