4:37 p.m.
Earlier this month, I posted that Firefox would not start for me. Ed Greshko kindly
showed my his output when he started Firefox from the command line. I noticed a bunch of
Gnome stuff and assumed that there was some sort of dependency I was missing, installed
Gnome, and it seemed to work. Ed noted that I was solving a small problem with a big
hammer, but to me, if installing gnome (a one-command fix) worked, then I didn't
really care what the problem was as long as it was fixed.
Well, Ed was right in his criticism. The problem popped up again in a few days. I now
know the problem, and I know a workaround, but I don't know the fix. Here it is:
Firefox will only allow one invocation of itself on my machine. Sometimes, if I invoke
the program by clicking an icon, it will come up with an error message that says you can
only have one copy running. However, sometimes that message does not appear, and it
simply dies silently. Moreover, I don't remember ever getting that error message when
I run it from command line, and I'm a very terminal-oriented guy.
But that's OK. The *problem* is that if I kill firefox by clicking on the kill-window
button rather than the Quit button, the window goes away, but firefox continues in the
background. Thus, if I kill firefox by closing the window, I can't start it again
without running ps, finding the process, and manually killing it. It's an easy
workaround, but a minor inconvenience.
Worse, however, if I forget to do that and log out, appearently the next time I turn on
KDE, it comes on as a background process but never shows a window. Once again, that's
not a huge problem now that I know to look for it.
I still don't know the fix, but the workaround is easy.
So, installing Gnome "fixed" the problem because I ended up cleanly exiting and
restarting the machine, not because of anything Gnome did.
Sigh.
3:14 a.m.
On 23 March 2014 23:37, Bill Oliver <vendor(a)billoblog.com> wrote:
Earlier this month, I posted that Firefox would not start for me. Ed
Greshko kindly showed my his output when he started Firefox from the
command line. I noticed a bunch of Gnome stuff and assumed that there was
some sort of dependency I was missing, installed Gnome, and it seemed to
work. Ed noted that I was solving a small problem with a big hammer, but
to me, if installing gnome (a one-command fix) worked, then I didn't really
care what the problem was as long as it was fixed.
Well, Ed was right in his criticism. The problem popped up again in a few
days. I now know the problem, and I know a workaround, but I don't know
the fix. Here it is:
Firefox will only allow one invocation of itself on my machine.
Sometimes, if I invoke the program by clicking an icon, it will come up
with an error message that says you can only have one copy running.
However, sometimes that message does not appear, and it simply dies
silently. Moreover, I don't remember ever getting that error message when
I run it from command line, and I'm a very terminal-oriented guy.
But that's OK. The *problem* is that if I kill firefox by clicking on the
kill-window button rather than the Quit button, the window goes away, but
firefox continues in the background. Thus, if I kill firefox by closing
the window, I can't start it again without running ps, finding the process,
and manually killing it. It's an easy workaround, but a minor
inconvenience.
Worse, however, if I forget to do that and log out, appearently the next
time I turn on KDE, it comes on as a background process but never shows a
window. Once again, that's not a huge problem now that I know to look for
it.
I still don't know the fix, but the workaround is easy.
So, installing Gnome "fixed" the problem because I ended up cleanly
exiting and restarting the machine, not because of anything Gnome did.
Sigh.
Did you try with a new Firefox profile? it could well be some setting or
extension in your current profile that's causing those issues.
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
--
Ahmad Samir
10:07 a.m.
On 03/26/14 12:28, Ahmad Samir wrote:
<<<<>>>>
<<<>>>
<<>>
<>
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
10:06 a.m.
On 03/26/14 03:33, Patrick O'Callaghan wrote:
On Wed, 2014-03-26 at 02:36 +0600, g wrote:
> and so, be prepared to hear from some gmail and cell phone
> users who will deny that such can easily be done, as well
> as replying interspersed, therefore they do not. :-)
IN Gmail it's trivially easy. Hint: select the relevant part before
hitting Reply. Note that this will also avoid top-posting. In some
phones (Blackberry, I'm looking at you) it's virtually impossible.
not being a user of gmail, as you are, i will take your word for it.
[never known you to lie yet. ;-) ]
it is interesting how _some_ gmail users _think_ they know
everything about everything, yet they show exactly how little
they when trying to impress others.
i have been using mozilla from day one of internet and email
starting out with netscape 2.01. my 1st isp ran a linux system
that id'ed as being an oos system. they caught hackers using
traps that were set for oos attacks. clever move on admin's part.
i dislike seeing original moz devs being replaced with devs that
think they need to 'keep up with the joneses' by trying to follow
the ways of gaagle chrome.
that is about it for this thread, as it seems that op seems to
being content with his system as it is.
later.
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
1:28 a.m.
On 25 March 2014 21:27, g <geleem(a)bellsouth.net> wrote:
On 03/25/14 23:17, Ahmad Samir wrote:
>
> On 25 March 2014 18:00, g <geleem(a)bellsouth.net> wrote:
<<>>
>> maybe in your experiences, but mine has been just to rename
>> users's ".mozilla" directory and when firefox was called,
>> firefox created a new ".mozilla" directory.
>>
>>
>
> A Firefox profile directory is ~/.mozilla/firefox/<profile_dir> ,
> c.f.
>
> http://kb.mozillazine.org/Profile_folder_-_Firefox#Linux
well, excuse my presuming that intelligent linux users, including
many new linux users, reading my post would know that the
"_user_profiles_" are in the user's directory, aka, "~". which
is
the *top* _directory_ of the _profile_directory_.
Apparently I am not that intelligent. :)
and to correct what you posted, actual path of to the
"<profile_dir>"
as you put it is;
/home/[username]/.mozilla/firefox/wxzy1234.default/
aka;
~/.mozilla/firefox/wxzy1234.default/
were in, 'wxyz1234' is a random mix of letters and numbers.
therefore, all a user need do is rename ".mozilla", firefox will
rebuild entire new path, starting with ".mozilla" in the users
home directory. it does not have to _pre-exist_.
As far as a I am concerned, this is not a mudslinging contest, it's
about helping a user who posted about a problem with an application
he's using.
A Firefox profile directory is under ~/.mozilla/firefox/ by default,
it can have whatever name you select (you use the Firefox profile
manager to create it manually or edit ~/.mozilla/firefox/profiles.ini
manually). You can also edit ~/.mozilla/firefox/profiles.ini and set
an absolute path to the profile directory in any other location.
Now, can we get back on topic ( "a user has a problem with firefox not
closing cleanly when all its windows are closed")?
btw, in your haste to correct me, i do notice that you did not
get far enough into my post to see the following:
=+=+=+=+=+=+=+=+=
>> btw, you will not hurt my feelings, and i doubt any of followers
>> of this list if you would cut the 'dead wood' when you reply.
>>
>> thank you.
=+=+=+=+=+=+=+=+=
I replied two hours later and I did read that but I thought you were
talking about the above quotes.
[...]
--
Ahmad Samir
3:36 p.m.
On 03/26/14 01:43, Joe Zeff wrote:
On 03/25/2014 12:27 PM, g wrote:
> in case you are not aware, "dead wood" means portions of a post
> that are not related or reference to what one is replying to.
I'd like to add to that the fact that other poster's signatures,
including anything added by the list software, is always deadwood
and should never be included.
and so, be prepared to hear from some gmail and cell phone
users who will deny that such can easily be done, as well
as replying interspersed, therefore they do not. :-)
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
4:33 p.m.
On Wed, 2014-03-26 at 02:36 +0600, g wrote:
and so, be prepared to hear from some gmail and cell phone
users who will deny that such can easily be done, as well
as replying interspersed, therefore they do not. :-)
IN Gmail it's trivially easy. Hint: select the relevant part before
hitting Reply. Note that this will also avoid top-posting. In some
phones (Blackberry, I'm looking at you) it's virtually impossible.
poc
2:43 p.m.
On 03/25/2014 12:27 PM, g wrote:
in case you are not aware, "dead wood" means portions of a
post
that are not related or reference to what one is replying to.
I'd like to add to that the fact that other poster's signatures,
including anything added by the list software, is always deadwood and
should never be included.
2:27 p.m.
On 03/25/14 23:17, Ahmad Samir wrote:
On 25 March 2014 18:00, g <geleem(a)bellsouth.net> wrote:
<<>>
> maybe in your experiences, but mine has been just to rename
> users's ".mozilla" directory and when firefox was called,
> firefox created a new ".mozilla" directory.
>
A Firefox profile directory is ~/.mozilla/firefox/<profile_dir> ,
c.f.
http://kb.mozillazine.org/Profile_folder_-_Firefox#Linux
well, excuse my presuming that intelligent linux users, including
many new linux users, reading my post would know that the
"_user_profiles_" are in the user's directory, aka, "~". which is
the *top* _directory_ of the _profile_directory_.
and to correct what you posted, actual path of to the "<profile_dir>"
as you put it is;
/home/[username]/.mozilla/firefox/wxzy1234.default/
aka;
~/.mozilla/firefox/wxzy1234.default/
were in, 'wxyz1234' is a random mix of letters and numbers.
therefore, all a user need do is rename ".mozilla", firefox will
rebuild entire new path, starting with ".mozilla" in the users
home directory. it does not have to _pre-exist_.
btw, in your haste to correct me, i do notice that you did not
get far enough into my post to see the following:
=+=+=+=+=+=+=+=+=
> btw, you will not hurt my feelings, and i doubt any of followers
> of this list if you would cut the 'dead wood' when you reply.
>
> thank you.
=+=+=+=+=+=+=+=+=
in case you are not aware, "dead wood" means portions of a post
that are not related or reference to what one is replying to.
in closing, KAFBA. ;-)
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
12:17 p.m.
On 25 March 2014 18:00, g <geleem(a)bellsouth.net> wrote:
On 03/25/14 18:52, Ahmad Samir wrote:
On 25 March 2014 13:08, g <geleem(a)bellsouth.net> wrote:
<<<>>>
>> thinking about that, a new profile is just about as easy a check
>> to make as disabling add-ons.
>
>
> It could be a pref in the profile not just an extension causing the
> problem. Or maybe a corrupt *.sqlite database. Or a huge/corrupt
> sessionrestore.js file... etc.
which is another point for creating a new user.
>> which is quicker?
>>
>> closing firefox, renaming profile directory, starting firefox.
>
>
> As far as I can see, that wouldn't work, just renaming the profile
> directory would prevent Firefox from starting at all, it'll give you
> an error about not being able to load the profile; you'd have to
> rename it then create a new empty dir with the same name for Firefox
> to start.
maybe in your experiences, but mine has been just to rename users's
".mozilla" directory and when firefox was called, firefox created a
new ".mozilla" directory.
A Firefox profile directory is ~/.mozilla/firefox/<profile_dir> , c.f.
http://kb.mozillazine.org/Profile_folder_-_Firefox#Linux
btw, you will not hurt my feelings, and i doubt any of followers of
this list if you would cut the 'dead wood' when you reply.
thank you.
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
--
Ahmad Samir
11 a.m.
On 03/25/14 18:52, Ahmad Samir wrote:
On 25 March 2014 13:08, g <geleem(a)bellsouth.net> wrote:
<<<>>>
> thinking about that, a new profile is just about as easy a check
> to make as disabling add-ons.
It could be a pref in the profile not just an extension causing the
problem. Or maybe a corrupt *.sqlite database. Or a huge/corrupt
sessionrestore.js file... etc.
which is another point for creating a new user.
> which is quicker?
>
> closing firefox, renaming profile directory, starting firefox.
As far as I can see, that wouldn't work, just renaming the profile
directory would prevent Firefox from starting at all, it'll give you
an error about not being able to load the profile; you'd have to
rename it then create a new empty dir with the same name for Firefox
to start.
maybe in your experiences, but mine has been just to rename users's
".mozilla" directory and when firefox was called, firefox created a
new ".mozilla" directory.
btw, you will not hurt my feelings, and i doubt any of followers of
this list if you would cut the 'dead wood' when you reply.
thank you.
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
7:52 a.m.
On 25 March 2014 13:08, g <geleem(a)bellsouth.net> wrote:
On 03/25/14 13:30, Ahmad Samir wrote:
<<>>
> Usually I'd try with a new profile first, if the problem doesn't
> happen there, then I try to track down why it's happening in the
> original profile. (i.e. I wasn't implying he just ditches his old
> profile :)).
thinking about that, a new profile is just about as easy a check
to make as disabling add-ons.
It could be a pref in the profile not just an extension causing the
problem. Or maybe a corrupt *.sqlite database. Or a huge/corrupt
sessionrestore.js file... etc.
which is quicker?
closing firefox, renaming profile directory, starting firefox.
As far as I can see, that wouldn't work, just renaming the profile
directory would prevent Firefox from starting at all, it'll give you
an error about not being able to load the profile; you'd have to
rename it then create a new empty dir with the same name for Firefox
to start.
selecting "Help > Restart with Add-ons Disabled", click
[Restart].
[...]
one would need a stop watch to find out. :-)
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
--
Ahmad Samir
6:08 a.m.
On 03/25/14 13:30, Ahmad Samir wrote:
<<>>
Usually I'd try with a new profile first, if the problem
doesn't
happen there, then I try to track down why it's happening in the
original profile. (i.e. I wasn't implying he just ditches his old
profile :)).
thinking about that, a new profile is just about as easy a check
to make as disabling add-ons.
which is quicker?
closing firefox, renaming profile directory, starting firefox.
selecting "Help > Restart with Add-ons Disabled", click [Restart].
one would need a stop watch to find out. :-)
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
2:30 a.m.
On 24 March 2014 18:16, Ian Malone <ibmalone(a)gmail.com> wrote:
On 24 March 2014 08:14, Ahmad Samir <ahmadsamir3891(a)gmail.com> wrote:
> On 23 March 2014 23:37, Bill Oliver <vendor(a)billoblog.com> wrote:
>>
>>
>> Firefox will only allow one invocation of itself on my machine.
>> Sometimes, if I invoke the program by clicking an icon, it will come up with
>> an error message that says you can only have one copy running. However,
>> sometimes that message does not appear, and it simply dies silently.
>> Moreover, I don't remember ever getting that error message when I run it
>> from command line, and I'm a very terminal-oriented guy.
>>
>> But that's OK. The *problem* is that if I kill firefox by clicking on the
>> kill-window button rather than the Quit button, the window goes away, but
>> firefox continues in the background. Thus, if I kill firefox by closing the
>> window, I can't start it again without running ps, finding the process, and
>> manually killing it. It's an easy workaround, but a minor inconvenience.
>>
>> Worse, however, if I forget to do that and log out, appearently the next
>> time I turn on KDE, it comes on as a background process but never shows a
>> window. Once again, that's not a huge problem now that I know to look for
>> it.
>>
>> I still don't know the fix, but the workaround is easy.
> Did you try with a new Firefox profile? it could well be some setting or
> extension in your current profile that's causing those issues.
Or use about:addons to disable all plugins+extensions and see if the
problem goes away (Firefox staying resident and preventing-relaunch if
not killed so far as I can make out from this thread). If that does
stop it happening then re-enable them one-by-one* and see if it comes
back (* "other elimination strategies are available").
Usually I'd try with a new profile first, if the problem doesn't
happen there, then I try to track down why it's happening in the
original profile. (i.e. I wasn't implying he just ditches his old
profile :)).
There may be something else going on as normally using the launcher
a
second time will just trigger firefox to open another window on the
same profile, which it sounds like it doesn't on your machine. (While
you can open a second window from within firefox itself that might
also have implications for programs that try to open links in a
browser.)
--
imalone
http://ibmalone.blogspot.co.uk
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
--
Ahmad Samir
8:33 p.m.
On 03/25/14 03:45, Bill Oliver wrote:
<<>>
It happened after doing one of those "you have 1 billion
upgrades
waiting, continue?" things that I get every now and then. I'll
admit I tend to just hit "yes" rather than carefully look at all
zillion of the files that is in yum updates.
And, yeah, I have about a billion addons, too. And they haven't
always played well together in the past. In particular some of
the security addons futz with the addons that run a lot of scripts.
And, oddly, it makes a difference in which *order* the addons are
added.
well now. that narrows things down a bit. lhid.
I was kinda hoping to avoid testing each of my addons for being a
bad actor.
now you are about to understand the word perseverance. :-)
me thinks you exaggerate a wee bit on the numbers.
because no other users profess to having problems such as yours,
i tend to lean to either a bad configuration, conflict of add-ons,
or a bad add-on.
if you want to stay with all the add-ons you have, be content to
use <ctrl+q> to shut down firefox. options and procedures are as
in previous post.
ie, for a quick and easy check, disable add-ons and restart
firefox. or, set up a new user to see what happens.
choice is yours to make. i, nor anyone else can make it for you.
sink, swim, or just tread water.
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
4:45 p.m.
On Tue, 25 Mar 2014, g wrote:
which leads to a question, did this problem start after an
upgrade, update or addition of an add-on?
ria, such factors could also lead to solution.
hth.
my apologies.
much luck in finding solution.
It happened after doing one of those "you have 1 billion upgrades
waiting, continue?" things that I get every now and then. I'll admit I
tend to just hit "yes" rather than carefully look at all zillion of the
files that is in yum updates.
And, yeah, I have about a billion addons, too. And they haven't always
played well together in the past. In particular some of the security
addons futz with the addons that run a lot of scripts. And, oddly, it
makes a difference in which *order* the addons are added.
I was kinda hoping to avoid testing each of my addons for being a bad
actor.
billo
2:37 p.m.
On 03/24/14 22:16, Ian Malone wrote:
<<>>
Or use about:addons to disable all plugins+extensions and see if the
problem goes away (Firefox staying resident and preventing-relaunch
if not killed so far as I can make out from this thread). If that
does stop it happening then re-enable them one-by-one* and see if it
comes back (* "other elimination strategies are available").
There may be something else going on as normally using the launcher
a second time will just trigger Firefox to open another window on
the same profile, which it sounds like it doesn't on your machine.
(While you can open a second window from within Firefox itself that
might also have implications for programs that try to open links in
a browser.)
Ian,
you brought up something that my 'chemo brain' forgot.
Bill Oliver,
my apologies, following procedure is what i used to recommend when
i was a subscriber to mozilla list.
1- to check if problem is an add-on or in user's configuration,
create a new user.
2- if problem is still present, problem is in Firefox install,
solution - removal of Firefox installation files, reinstall
Firefox.
3- if not present, problem is with an add-on or user
configurations.
4- to locate where with user, open just 1 window of Firefox,
a- select 'Help' in main menu bar.
b- select 'Restart with Add-ons Disabled'.
c- when "Restart with Add-ons Disabled' window pops up,
click [Restart] button.
5- when Firefox restarts, close Firefox with [X] button or
'File > Quit' from main menu bar. (do not use <ctrl+q>)
6- after restart, if all is well, problem is with an add-on,
then see below.
if not, problem is in a configuration.
7- if configuration, open a terminal,
a- ]$ ps -e|grep Firefox
for pid, then
]$ kill -s9 pid
b- from a file browser of terminal, rename directory
/home/~/.mozilla to /home/~/.mozilla.bad.
c- restart Firefox, try closing with [X] button or
'File > Quit' from main menu bar. (do not use <ctrl+q>)
d- if ok, great. if not, something is wrong with Firefox's
default user settings. reinstall Firefox.
8- if an add-on,
a- open add-ons tab with <ctrl_shift+a> or from main menu
bar 'Tools > Add-ons'.
b- in tab, enable first half of add-ons, restart Firefox.
c- if ok, open add-ons tab, select half of second half of
remaining add-ons, restart Firefox.
d- if ok, repeat above.
9- if at any time you add 1/2 and get a fail, disable add-ons
by 1/2 to narrow in on problem add-on.
using 1/2 x 1/2 gives a quick zero in on bad add-on. be aware
that it is possible that some add-ons interact with others and
it is possible that you may have to make a choice of which of
2 add-ons you want to eliminate.
which leads to a question, did this problem start after an
upgrade, update or addition of an add-on?
ria, such factors could also lead to solution.
hth.
my apologies.
much luck in finding solution.
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
11:16 a.m.
On 24 March 2014 08:14, Ahmad Samir <ahmadsamir3891(a)gmail.com> wrote:
On 23 March 2014 23:37, Bill Oliver <vendor(a)billoblog.com>
wrote:
>
>
> Firefox will only allow one invocation of itself on my machine.
> Sometimes, if I invoke the program by clicking an icon, it will come up with
> an error message that says you can only have one copy running. However,
> sometimes that message does not appear, and it simply dies silently.
> Moreover, I don't remember ever getting that error message when I run it
> from command line, and I'm a very terminal-oriented guy.
>
> But that's OK. The *problem* is that if I kill firefox by clicking on the
> kill-window button rather than the Quit button, the window goes away, but
> firefox continues in the background. Thus, if I kill firefox by closing the
> window, I can't start it again without running ps, finding the process, and
> manually killing it. It's an easy workaround, but a minor inconvenience.
>
> Worse, however, if I forget to do that and log out, appearently the next
> time I turn on KDE, it comes on as a background process but never shows a
> window. Once again, that's not a huge problem now that I know to look for
> it.
>
> I still don't know the fix, but the workaround is easy.
Did you try with a new Firefox profile? it could well be some setting
or
extension in your current profile that's causing those issues.
Or use about:addons to disable all plugins+extensions and see if the
problem goes away (Firefox staying resident and preventing-relaunch if
not killed so far as I can make out from this thread). If that does
stop it happening then re-enable them one-by-one* and see if it comes
back (* "other elimination strategies are available").
There may be something else going on as normally using the launcher a
second time will just trigger firefox to open another window on the
same profile, which it sounds like it doesn't on your machine. (While
you can open a second window from within firefox itself that might
also have implications for programs that try to open links in a
browser.)
--
imalone
http://ibmalone.blogspot.co.uk
10:08 p.m.
On 03/24/14 08:58, Bill Oliver wrote:
On Mon, 24 Mar 2014, g wrote:
>
>> <ctrl+q> kills the process.
>
> is that not what you want, to able to kill window and process?
>
Yeah, it'll work. I just have to remember it. I use GUIs by muscle
memory, so I'll likely close the window 10 or 20 times before I
remember...
((GBWG))
been there my self. but, it only took 6 or 8 times.
as long as you have perseverance, you will make it. ;-)
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
10:04 p.m.
On 03/24/14 08:57, Bill Oliver wrote:
On Sun, 23 Mar 2014, Joe Zeff wrote:
> On 03/23/2014 07:06 PM, g wrote:
>
>>
>> 24.4.0
>>
>
> Maybe if you upgraded to the newest version this would Just Go Away.
>
g's not having the problem, I am :-)
lol.
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
9:36 p.m.
On 03/24/14 08:17, Joe Zeff wrote:
On 03/23/2014 07:06 PM, g wrote:
>
> 24.4.0
>
Maybe if you upgraded to the newest version this would Just Go Away.
if i was having problem op is having, i would well consider it. ;-)
right now, i would rather stay where i am because i do am not having
problems that have been release in new versions.
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
9:06 p.m.
On 03/24/14 05:07, Bill Oliver wrote:
On Mon, 24 Mar 2014, g wrote:
<<<>>>
>
> just what version and release are you having problems with?
>
> have you tried using <ctrl+q> to kill window?
>
KDE 4.12.3
4.3.4
Firefox 27.0.1
24.4.0
% uname -a
Linux localhost.localdomain 3.13.6-200.fc20.x86_64 #1 SMP Fri Mar 7
17:02:28 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Linux localhost.localdomain 2.6.32-431.5.1.el6.x86_64 #1 SMP Wed Feb 12
00:41:43 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
]$ cat /etc/centos-release
CentOS release 6.5 (Final)
<ctrl+q> kills the process.
is that not what you want, to able to kill window and process?
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
9:04 p.m.
On 03/24/14 05:37, Joe Zeff wrote:
<>
If you haven't already, open a bugzilla on it. The situation is
odd
enough that it should get somebody's attention fairly quickly,
especially if your report includes an offer to get whatever debug info
is needed.
are you ever living in a dream world when relating to mozilla.org.
the devs pay little mind to bugzilla as for something like bill's
problem.
the bug is well known in mozilla land and it is a 'put up with it or
up grade to later version where bug does not exist' routine.
moz devs used to be good at fixing bugs until gaagle chrome came out.
gaagle devs do not fix bugs, they just make new releases with more
'bells and whistles'. so, to try to 'keep up with the joneses', moz
devs started doing same thing.
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
6:37 p.m.
On 03/23/2014 03:38 PM, Bill Oliver wrote:
The problem is that the process doesn't quit when I kill the window (hit
the "x" on the upper right edge of the frame -- which it used to do).
Instead, I have to choose File->Quit from the Firefox menu. The process
should die when I kill the window. I don't want to start a second
instantiation or open a second window. I want the program to stop when
kill the window, so that when I start the program a day later it doesn't
crash because of a process that is no longer attached to an existing
window.
If you haven't already, open a bugzilla on it. The situation is odd
enough that it should get somebody's attention fairly quickly,
especially if your report includes an offer to get whatever debug info
is needed.
6:07 p.m.
On Mon, 24 Mar 2014, g wrote:
On 03/24/14 04:38, Bill Oliver wrote:
<>
> The problem is that the process doesn't quit when I kill the window
> (hit the "x" on the upper right edge of the frame -- which it used to
> do). Instead, I have to choose File->Quit from the Firefox menu.
> The process should die when I kill the window. I don't want to start
> a second instantiation or open a second window. I want the program
> to stop when kill the window, so that when I start the program a day
> later it doesn't crash because of a process that is no longer
> attached to an existing window.
just what version and release are you having problems with?
have you tried using <ctrl+q> to kill window?
KDE 4.12.3
Firefox 27.0.1
% uname -a
Linux localhost.localdomain 3.13.6-200.fc20.x86_64 #1 SMP Fri Mar 7
17:02:28 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
<ctrl+q> kills the process.
billo
6:03 p.m.
On Mon, 24 Mar 2014, Ed Greshko wrote:
On 03/24/14 05:37, Bill Oliver wrote:
But that's OK. The *problem* is that if I kill firefox by clicking on the
kill-window button rather than the Quit button, the window goes away,
but firefox continues in the background. Thus, if I kill firefox by closing the
window, I can't start it again without running ps, finding the
process, and manually killing it. It's an easy workaround, but a minor
inconvenience.
FWIW, I mostly use chrome, but I have seen cases where firefox continues to run in the
background. If memory serves me, in my case, it was due to the
flash-plugin not exiting.
Instead of using ps, you can simply use "killall /usr/lib64/firefox/firefox"
(note I'm running 64bit)
Worse, however, if I forget to do that and log out, appearently the next time I
turn on KDE, it comes on as a background process but never shows
a window. Once again, that's not a huge problem now that I know to look for
it.
You may find it helpful to do two things...
1. Create a ~/.bash_logout which contains the killall command to make sure firefox is
dead, dead on logout.
2. If you are using KDE and your "session management" is set to "Restore
previous session" it may be helpful to add firefox to the "Applications to be
excluded...." list.
Great suggestions. Thanks.
billo
6:02 p.m.
On 03/24/14 04:38, Roger Heflin wrote:
I actually wanted 2 separate users that were somewhat isolated from
each other so the separate profiles was useful.
in such case, using "firefox --no-remote -P <profilename>" is
the proper way.
so far, op has not stated he is want to open in 2 profiles.
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
6:02 p.m.
On 03/24/14 04:47, David wrote:
<>
Mozilla's advice is:
"Firefox refuses to close using red X; have to right click on screen
bottom to close"
<https://support.mozilla.org/en-US/questions/976081>
This specifically says "win XP" but I have seen others say this aboutit
in Linux also.
this is true. linux users are not so eager to be supportive to report
problems. we usually just work around or up grade. ;-)
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
5:59 p.m.
On 03/24/14 04:38, Bill Oliver wrote:
<>
The problem is that the process doesn't quit when I kill the
window
(hit the "x" on the upper right edge of the frame -- which it used to
do). Instead, I have to choose File->Quit from the Firefox menu.
The process should die when I kill the window. I don't want to start
a second instantiation or open a second window. I want the program
to stop when kill the window, so that when I start the program a day
later it doesn't crash because of a process that is no longer
attached to an existing window.
just what version and release are you having problems with?
have you tried using <ctrl+q> to kill window?
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
5:47 p.m.
On 3/23/2014 6:38 PM, Bill Oliver wrote:
On Mon, 24 Mar 2014, g wrote:
>
>
> On 03/24/14 03:37, Bill Oliver wrote:
> <>
>> I still don't know the fix, but the workaround is easy.
>
> the "fix" is not a 'fix'. it is using the correct procedure.
>
> try this, when you have firefox window open you have _2_built-in_
> options to open another window;
>
> 1- <ctrl+n>
> 2- <alt+f><n>
>
> enjoy. :-)
>
The problem is that the process doesn't quit when I kill the window (hit
the "x" on the upper right edge of the frame -- which it used to do).
Instead, I have to choose File->Quit from the Firefox menu. The process
should die when I kill the window. I don't want to start a second
instantiation or open a second window. I want the program to stop when
kill the window, so that when I start the program a day later it doesn't
crash because of a process that is no longer attached to an existing
window.
billo
Mozilla's advice is:
"Firefox refuses to close using red X; have to right click on screen
bottom to close"
<https://support.mozilla.org/en-US/questions/976081>
This specifically says "win XP" but I have seen others say this aboutit
in Linux also.
Good luck.
--
David
5:47 p.m.
On 03/24/14 05:37, Bill Oliver wrote:
But that's OK. The *problem* is that if I kill firefox by
clicking on the kill-window button rather than the Quit button, the window goes away, but
firefox continues in the background. Thus, if I kill firefox by closing the window, I
can't start it again without running ps, finding the process, and manually killing it.
It's an easy workaround, but a minor inconvenience.
FWIW, I mostly use chrome, but I have seen cases where firefox continues to run in the
background. If memory serves me, in my case, it was due to the flash-plugin not exiting.
Instead of using ps, you can simply use "killall /usr/lib64/firefox/firefox"
(note I'm running 64bit)
Worse, however, if I forget to do that and log out, appearently the next time I turn on
KDE, it comes on as a background process but never shows a window. Once again, that's
not a huge problem now that I know to look for it.
You may find it helpful to do two things...
1. Create a ~/.bash_logout which contains the killall command to make sure firefox is
dead, dead on logout.
2. If you are using KDE and your "session management" is set to "Restore
previous session" it may be helpful to add firefox to the "Applications to be
excluded...." list.
--
Getting tired of non-Fedora discussions and self-serving posts
5:38 p.m.
On Mon, 24 Mar 2014, g wrote:
On 03/24/14 03:37, Bill Oliver wrote:
<>
> I still don't know the fix, but the workaround is easy.
the "fix" is not a 'fix'. it is using the correct procedure.
try this, when you have firefox window open you have _2_built-in_
options to open another window;
1- <ctrl+n>
2- <alt+f><n>
enjoy. :-)
The problem is that the process doesn't quit when I kill the window (hit the
"x" on the upper right edge of the frame -- which it used to do). Instead, I
have to choose File->Quit from the Firefox menu. The process should die when I kill
the window. I don't want to start a second instantiation or open a second window. I
want the program to stop when kill the window, so that when I start the program a day
later it doesn't crash because of a process that is no longer attached to an existing
window.
billo
5:38 p.m.
I actually wanted 2 separate users that were somewhat isolated from
each other so the separate profiles was useful.
On Sun, Mar 23, 2014 at 5:10 PM, g <geleem(a)bellsouth.net> wrote:
On 03/24/14 03:54, Roger Heflin wrote:
<>
> if you want to run 2 separated copies you need to setup another
> profile and start it like this: firefox --no-remote -P <profilename>
that is another way. but more to go thru than simply using
<ctrl+n> or <alt+f><n>.
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
5:10 p.m.
On 03/24/14 03:54, Roger Heflin wrote:
<>
if you want to run 2 separated copies you need to setup another
profile and start it like this: firefox --no-remote -P <profilename>
that is another way. but more to go thru than simply using
<ctrl+n> or <alt+f><n>.
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
4:54 p.m.
If you run firefox with one already running it tries to contacts the
current running firefox version and may try to open a tab on the
already running window, that may be the no error piece.
if you want to run 2 separated copies you need to setup another
profile and start it like this: firefox --no-remote -P <profilename>
On Sun, Mar 23, 2014 at 4:37 PM, Bill Oliver <vendor(a)billoblog.com> wrote:
Earlier this month, I posted that Firefox would not start for me. Ed
Greshko kindly showed my his output when he started Firefox from the command
line. I noticed a bunch of Gnome stuff and assumed that there was some sort
of dependency I was missing, installed Gnome, and it seemed to work. Ed
noted that I was solving a small problem with a big hammer, but to me, if
installing gnome (a one-command fix) worked, then I didn't really care what
the problem was as long as it was fixed.
Well, Ed was right in his criticism. The problem popped up again in a few
days. I now know the problem, and I know a workaround, but I don't know the
fix. Here it is:
Firefox will only allow one invocation of itself on my machine. Sometimes,
if I invoke the program by clicking an icon, it will come up with an error
message that says you can only have one copy running. However, sometimes
that message does not appear, and it simply dies silently. Moreover, I
don't remember ever getting that error message when I run it from command
line, and I'm a very terminal-oriented guy.
But that's OK. The *problem* is that if I kill firefox by clicking on the
kill-window button rather than the Quit button, the window goes away, but
firefox continues in the background. Thus, if I kill firefox by closing the
window, I can't start it again without running ps, finding the process, and
manually killing it. It's an easy workaround, but a minor inconvenience.
Worse, however, if I forget to do that and log out, appearently the next
time I turn on KDE, it comes on as a background process but never shows a
window. Once again, that's not a huge problem now that I know to look for
it.
I still don't know the fix, but the workaround is easy.
So, installing Gnome "fixed" the problem because I ended up cleanly exiting
and restarting the machine, not because of anything Gnome did.
Sigh.
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
4:50 p.m.
On 03/24/14 03:37, Bill Oliver wrote:
<>
I still don't know the fix, but the workaround is easy.
the "fix" is not a 'fix'. it is using the correct procedure.
try this, when you have firefox window open you have _2_built-in_
options to open another window;
1- <ctrl+n>
2- <alt+f><n>
enjoy. :-)
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
3677
days inactive
3680
days old
40 comments
9 participants
participants (9)
-
Ahmad Samir -
David -
Ed Greshko -
g -
Ian Malone -
Joe Zeff -
Patrick O'Callaghan -
Roger Heflin -
William Oliver