Closed Bug 355206 Opened 19 years ago Closed 19 years ago

corruption of user data

Categories

(Toolkit :: Startup and Profile System, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: estellnb, Unassigned)

Details

User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.1 (like Gecko) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.8.0.7) Gecko/20060911 SUSE/1.5.0.7-1.2 Firefox/1.5.0.7 Firefox can not connect to the internet any more since Foxyproxy has corrupted my user data(~/.firefox). Uninstalling of Foxyproxy did not help. Before this Foxyproxy was complaining whenever I tried to view a mms stream from iptv.orf.at with any of the plugins gxine-0.5.7-0.pm.0, xine-mozilla-plugin-0.2-051004.i586.rpm, kaffeine-mozilla-0.2-0.pm.1, xine-mozilla-plugin-0.2-051004. Video playback has been working perfectly when invoking xine and kaffeine directly but not with any of those plugins for Firefox. Reproducible: Always Steps to Reproduce: 1.install and configure foxyproxy 2.install different plugins for viewing mms-streams: 3.try to view mms stream from iptv.orf.at: foxyproxy reports errors 4.foxyproxy does always report errors on any page: nothing works 5.uninstall foxyproxy: still no more connection to the internet Actual Results: Firefox is not able to connect to the internet at all when started from the user whose ~/.firefox folder is corrupted. Firefox is still working perfectly for any other user. Expected Results: If I remove a plugin I would expect it to be removed full and correctly!! I do not post a .tar.bz2 of my ~/.firefox folder, because I have made firefox remember several passwords.
Severity: major → normal
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
No fix, so assuming this was invalid since it looks like an extension issue.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → INVALID
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.