I cannot open Iceweasel more then 1 time

miros84 · 02-08-2010, 12:35 PM

When I try to open two times Iceweasel I get this:

Code:

Iceweasel is already running, but is not responding. To open a new window, you must first close the existing Iceweasel process, or restart your system.

I am very suprprised, because in Windows xp I can open mozilla firefox 2,3 or more times.
And in Linux, I cannot.
Some idea?

Mr-Bisquit · 02-08-2010, 01:47 PM

Code:

$ ps -U your-username
$kill iceweasel-process-number
$su
--enter-root-password--
#apt-get -y upgrade

miros84 · 02-08-2010, 03:10 PM

It doesnot block.
I can start it, but only one time.
When I try to start it 2 times, then i recive this message and I cannot start, execute it more then 1 time.

repo · 02-08-2010, 03:13 PM

you can remove the lock file.
However, why do you want to start it twice ?

Mr-Bisquit · 02-08-2010, 08:12 PM

repo has a point there.
Just use the ctrl+N to open a new window.
If you need the functionality of gecko, then use epiphany or galeon.
Another option: virtualize and minimalize.

damgar · 02-08-2010, 08:16 PM

Check to see if you have this package installed

PHP Code:


			
gtk-qt-engine

From this thread: http://www.linuxquestions.org/questi...stable-773551/

This was a problem for me and many others. The fix was to uninstall the package. I saw no ill-effects and the problem was solved.

miros84 · 02-09-2010, 08:14 AM

Quote:

Originally Posted by repo

you can remove the lock file.
However, why do you want to start it twice ?

I have 3 screens and sometimes I want to open it 2 or 3 times and have a Iceaweasel window in each screen.

Mr-Bisquit · 02-09-2010, 11:02 PM

Try running a session with Xephyr.

evo2 · 02-10-2010, 01:00 AM

I think what you really want is only one instance but multiple windows. This is usually possible, but for some reason when you try to connect to the running instance it fails to do so. Please completely kill the iceweasel process and start it up again.

Evo2.

XavierP · 02-10-2010, 09:07 AM

Have you tried the Ctrl + N option as described by Repo? It works fine for me.

miros84 · 02-10-2010, 11:41 AM

Quote:

Originally Posted by XavierP

Have you tried the Ctrl + N option as described by Repo? It works fine for me.

That would help if I have my screens with dual veiew.
But I have them in different X.
So, when I press contrl + N, it opens a new window in the same screen, and what I want is to open a new window in another screen.
And I cannot move windows between my screens.

Mr-Bisquit · 02-10-2010, 04:19 PM

What's the default screen size?

Go with Xephyr using the following:
On screens of 1280x1024 to 1024x768 Set up two windows with measures of 45% X and Y of the original screen. This will allow you to run an instance of iceweasel in the background and two in the foreground.
You will be able to switch between them.
Just be sure to close each Xephyr session through the terminal with the proper command or ctrl+C.

jefro · 02-10-2010, 05:15 PM

I thought there was a preference file that has something like multipleinstances -false

evo2 · 02-10-2010, 08:29 PM

Quote:

Originally Posted by miros84

That would help if I have my screens with dual veiew.
But I have them in different X.
So, when I press contrl + N, it opens a new window in the same screen, and what I want is to open a new window in another screen.
And I cannot move windows between my screens.

Ok, now we have the information we need.

On the 2nd X session run.

Code:

iceweasel -no-remote

This is documented in the man page.

However, the better thing to do would be to fix your X setup.

Evo2.

miros84 · 02-11-2010, 12:10 PM

Quote:

Originally Posted by evo2

Ok, now we have the information we need.

On the 2nd X session run.

Code:

iceweasel -no-remote

This is documented in the man page.

However, the better thing to do would be to fix your X setup.

Evo2.

Code:

Iceweasel is already running, but is not responding. To open a new window, you must first close the existing Iceweasel process, or restart your system.

I got the same error, as when I try to open a new window.
In debian squeeze, it seems to be fixed.
As I see, I have to upgrade some day to debian squeeze.

Quote:

However, the better thing to do would be to fix your X setup.

What you mean to fix my x?