Closed Bug 53674 Opened 25 years ago Closed 24 years ago

prefs for composer invisible

Categories

(SeaMonkey :: Preferences, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: spam, Assigned: mcafee)

References

Details

Attachments

(1 file)

2000-09-21-17 linux in preferences the items for composer (and subitem) isn't visible anymore: text is missing. (Functionality is OK however; it is possible to click the empty items.)
..and in 2000-092121 they returned. WFM.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
..and in 2000-092321 they vanished again. Reopening. In addition: When opening composer twisty and clicking what should have read "New Page Settings", js error appears in console: chrome://communicator/content/pref/prefutilities.js line 1: redeclaration of const nsIFilePicker
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Note: Using the SEA build (others are too large for comfort these days.)
i cannot repro this on linux --then again, i'm using the installer (non-tarball blob) bits 2000.09.25.08 for commercial. i'll try this out using the sea mozilla blob soon... cc'ing beppe to see if she sees this...
just tested this using the 2000.09.25.08 mozilla SEA (which has the installer, i realize now ;)... but i cannot seem to repro, although i do get the same js error in the console.
*** Bug 54071 has been marked as a duplicate of this bug. ***
The word "composer" is invisible on my system. Redhat 6.1 2000092808 I've used the installer, the strait .tar.gz, and the SEA. I think they all act the same for me.
this is one weird bug. The composer menus in prefs come and go - every second build almost. Right now they are there - 2000093009 I can't find any checkins that should alter this back and fort. Wondering if i now have to start not only mozilla browser but also installed components before all is initiated right and can be used by normal users? Another thing that seems to come/go is two menuitems in composer; Edit and Insert. (filed another bug on that) These two are also visible in 2000093009, but i've now "learned" to start ALL components as root before i begin using them as normal user. This is just a hypothesis of course, but someone who know which file(s) to look for should perhaps test it out.
Yeah, it looks like Mozilla has some real permissions issues. If I run Mozilla as root (ack!!), the word "composer" does appear in my prefs. And if I subsequently run Mozilla as a normal user, it's still there. Check out bug 41057
Depends on: 54904
--> Default owner Do you still see this?
Assignee: matt → mcafee
Status: REOPENED → NEW
this bug is really old, marking WFM, as it does on both Linux, w2k.
Status: NEW → RESOLVED
Closed: 25 years ago24 years ago
Resolution: --- → WORKSFORME
mass verification of WorksForMe bugs: to find all bugspam pertaining to this, set your search string to "IfItWorksForSlappyTheSquirrelThenItWFM". if you think this particular bug is *still* an open issue, please make sure of the following before reopening: a. that it's still a problem with ***recent trunk builds*** on the all appropriate platform[s] b. provide clear steps to reproduce (unless a good test case is already in the bug report), making sure it pertains to the original problem (avoid morphing as much as possible :)
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: