Closed
Bug 291698
Opened 19 years ago
Closed 19 years ago
xulrunner installed as root will only open an empty (see through) window when lanching xul apps as a regular user
Categories
(Toolkit Graveyard :: XULRunner, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: remi2402, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 Build Identifier: Mozilla XULRunner 1.8b2 2005042305 I created an ebuild for gentoo which basically just copies the content of the tarball to /opt/xulrunner and symlinks /usr/bin/xulrunner to /opt/xulrunner/xulrunner. When launching `xulrunner mybrowser/application.ini` as a user, XULRunner opens an empty window (just WM borders and nothing inside, I can see and click on other apps under this window) However, if I launch it with root first, then launching it as a regular user works fine. Removing xulrunner from my system with portage leaves those three files : stratos xulrunner # find . ./components ./components/xpti.dat ./components/compreg.dat ./chrome ./chrome/app-chrome.manifest Reproducible: Always Steps to Reproduce: 1. run the xul app as root 2. then run it as a user Actual Results: Mybrowser-0.2 worked fine
Comment 1•19 years ago
|
||
This is something we intend to fix for 1.9, but it probably won't be fixed for 1.8 (the developer preview). The problem is generating the app-chrome.manifest from installed-chrome.txt. The solution is to run some variation of "xulrunner -register" when installing (this would be an RPM post-install script, I don't know how that maps to debian packages). The -register and -unregister flags will also be needed to register xulrunner as a GRE provider in /etc/gre.conf (doesn't work yet, but planned for 1.8).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•19 years ago
|
||
WFM with recent branch and trunk nightlies.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•8 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•