Closed Bug 307316 Opened 19 years ago Closed 17 years ago

Unable to launch Deer Park 2 from Linux desktop icon

Categories

(Firefox :: Shell Integration, defect)

1.0 Branch
x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: kc7rcy, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050721 Firefox/1.0.6 (Ubuntu package 1.0.6)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20050904 Firefox/1.0+

Downloaded the linux installer for Deer Park 2 Sep 02 build and Sep 04 build.
I installed it to Ubuntu Linux and created a desktop shortcut pointing to
/usr/local/firefox/firefox.  Clicking on the icon, Deer Park briefly flashes
onto the screen and then closes.  This occures regardless of using Gnome or KDE.
 This occured regardless of the install directory- have also tried installing to
/home.  This occures both with and without the default installation of Firefox
that comes with Ubuntu.  I am able to launch Deer Park 2 from the desktop icon
if it is run as root.  Also using sudo /usr/local/firefox/firefox from a
terminal window it will launch.  NO themes or extensions installed.

Reproducible: Always

Steps to Reproduce:
1.Install Deer Park 2 on Ubuntu Linux
2.Create a desktop icon application link pointing to /usr/local/firefox/firefox
3.Click on icon

Actual Results:  
Deer Park briefly (less than 1 second) flashes onto screen then closes.

Expected Results:  
Browser window should stay open
Does it happen when you start Firefox with safe mode? http://kb.mozillazine.org/Safe_mode You probably have a bad extension or theme. Try removing it and then starting again.
Summary: Unable to launch Deer Park 2 from Linuz desktop icon → Unable to launch Deer Park 2 from Linux desktop icon
works for me in Fedora F7. 

Because of missing feedback, see comment #1, i close this bug as incomplete. 
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
Version: unspecified → 1.0 Branch
You need to log in before you can comment on or make changes to this bug.