[opensuse] An annoying behaviour by latest version of Firefox in openSUSE
I, and my wife, are running the very latest Firefox (as provided by openSUSE repos) on 32-bit computers. Both of us also have the same versions of KDE (now 4.4, previously 4.3.5 for me and 4.3.1 on her computer [don't ask!]) on our computers as well as openSUSE 11.2. (I make her system 'identical' [as much as possible - if you are married you'd know exactly what I mean :-) ] - to mine to make it easier for me to maintain her system.) Since Firefox 3.6 was installed (via zypper from the oS repo.) either one or both of the following occurs: (1) after closing Firefox, just prior to shutting down the computer, on restarting the computer [say, the next day] Firefox will automatically start in the first Desktop (we both have 6 Desktops set); or (2) this is the *most* annoying PITA: during a session, if you close down Firefox but then decide to restart it for whatever reason, openSUSE/KDE/whatever gives you the error message, "Firefox is already running. ..." and won't let you start Firefox until you "close" the already "running" Firefox. As I stated, this one is really a PITA because the normal recourse for my wife is to logout and restart her session or to reboot the computer (fiddling with command lines is not her forte). If one uses "ps aux" as root, one can see that firefox *IS *still running - and sometimes one can also see that the red "!lock" in the /.mozilla/.... directory is still in place - even though FF has been shutdown. (Deleting the "!lock" does not help; "kill"-ing the PID for FF is the only way out (or restarting your logon)). At this point I have to state that this occurs 95%+ of the time. As we both love playing FREECELL I initially thought that there was a connection between the two because when FC was not played the problem with FF did not occur. But, NO, my theorum proved totally false- FF does its "nonsense" even if FC hasn't been played for a day or so. And so..... Does anyone else experience this re Firefox, or has heard about it, and/or knows how to fix this PITA? BC -- "If it weren't for electricity we'd be all watching televion by candlelight." George Gobel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
(1) after closing Firefox, just prior to shutting down the computer, on restarting the computer [say, the next day] Firefox will automatically start in the first Desktop (we both have 6 Desktops set); I have this problems sorta. While it does load on desktop 1, when I go to desktop 3 (my Internet app desktop) It's there and then when I go to
the other desktops it does not show up on them. Only on the desktop it should show up. So have you tried clicking onto the desktop it should be on and then going back to desktop 1 and see if it's still there?
or (2) this is the *most* annoying PITA: during a session, if you close down Firefox but then decide to restart it for whatever reason, openSUSE/KDE/whatever gives you the error message, "Firefox is already running. ..." and won't let you start Firefox until you "close" the already "running" Firefox.
I've had this problem a few times, and after a few moments it seems to shut down correctly on its own. Could it possibly be doing some caching so it can remember your tabs and what not? -- Michael S. Dunsavage -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 14/02/10 17:19, Michael S. Dunsavage wrote:
(1) after closing Firefox, just prior to shutting down the computer, on restarting the computer [say, the next day] Firefox will automatically start in the first Desktop (we both have 6 Desktops set);
I have this problems sorta. While it does load on desktop 1, when I go to desktop 3 (my Internet app desktop) It's there and then when I go to the other desktops it does not show up on them. Only on the desktop it should show up. So have you tried clicking onto the desktop it should be on and then going back to desktop 1 and see if it's still there?
or (2) this is the *most* annoying PITA: during a session, if you close down Firefox but then decide to restart it for whatever reason, openSUSE/KDE/whatever gives you the error message, "Firefox is already running. ..." and won't let you start Firefox until you "close" the already "running" Firefox.
I've had this problem a few times, and after a few moments it seems to shut down correctly on its own. Could it possibly be doing some caching so it can remember your tabs and what not?
AHA! Thanks for the response. So there just maybe a problem here! I have no idea where the problem lies. I've deleted the Cache directory in .mozilla but the problem still reappears, so I don't think caching has anything to do with it. But then......who knows.... BC -- "If it weren't for electricity we'd be all watching televion by candlelight." George Gobel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Basil Chupin said the following on 02/14/2010 02:28 AM:
(2) this is the *most* annoying PITA: during a session, if you close down Firefox but then decide to restart it for whatever reason, openSUSE/KDE/whatever gives you the error message, "Firefox is already running. ..." and won't let you start Firefox until you "close" the already "running" Firefox.
I've had this problem a few times, and after a few moments it seems to shut down correctly on its own. Could it possibly be doing some caching so it can remember your tabs and what not?
AHA!
Thanks for the response.
So there just maybe a problem here!
I have no idea where the problem lies. I've deleted the Cache directory in .mozilla but the problem still reappears, so I don't think caching has anything to do with it. But then......who knows....
I think, Basil, you're misreading Michael's response. It a matter of the TIME IT TAKES for FF to write out your current tab settings - to the 'sessionstore.js' file, if I understand correctly. The cache in the sense of the cache of fragments and images is not the concern. Try just waiting. Or slap a watch on the 'sessionstore.js' -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 14/02/10 23:18, Anton Aylward wrote:
Basil Chupin said the following on 02/14/2010 02:28 AM:
(2) this is the *most* annoying PITA: during a session, if you close down Firefox but then decide to restart it for whatever reason, openSUSE/KDE/whatever gives you the error message, "Firefox is already running. ..." and won't let you start Firefox until you "close" the already "running" Firefox.
I've had this problem a few times, and after a few moments it seems to shut down correctly on its own. Could it possibly be doing some caching so it can remember your tabs and what not?
AHA!
Thanks for the response.
So there just maybe a problem here!
I have no idea where the problem lies. I've deleted the Cache directory in .mozilla but the problem still reappears, so I don't think caching has anything to do with it. But then......who knows....
I think, Basil, you're misreading Michael's response. It a matter of the TIME IT TAKES for FF to write out your current tab settings - to the 'sessionstore.js' file, if I understand correctly. The cache in the sense of the cache of fragments and images is not the concern.
Try just waiting.
And how long is one supposed to wait? One minute? 5 minutes? An hour? Irrespective of how long, or my wife, waits, the error message comes up. "ps aux", as root, shows that a PID for firefox is running.
Or slap a watch on the 'sessionstore.js'
"...slap a watch on the 'sessionstore.js'". What exactly is this supposed to mean? :-) Please explain. Nevertheless, in all the many years that I have been using Firefox (and its predecessor) this problem has NEVER occurred on my, or my wife's, system - until 3.6 -- and maybe until the updates/upgrades to 11.2 which occurred at the same time. As I stated, I don't know which is causing the problem and which is why I am asking for an answer here. One of those "mysteries of life"? :-) I doubt it. BC -- "If it weren't for electricity we'd be all watching televion by candlelight." George Gobel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Basil Chupin said the following on 02/14/2010 08:14 AM:
I think, Basil, you're misreading Michael's response. It a matter of the TIME IT TAKES for FF to write out your current tab settings - to the 'sessionstore.js' file, if I understand correctly. The cache in the sense of the cache of fragments and images is not the concern.
Try just waiting.
And how long is one supposed to wait? One minute? 5 minutes? An hour?
Yes, waiting is frustrating - "a watched pot never boils". I've never timed it but its not been more than a few minutes. Heck, shutting down KDE takes a few minutes as well. Perhaps its waiting for FF and never told me. Personally I find that shut-down time annoying.
Irrespective of how long, or my wife, waits, the error message comes up.
Really? You've waited an hour?
Or slap a watch on the 'sessionstore.js'
"...slap a watch on the 'sessionstore.js'". What exactly is this supposed to mean? :-)
Please explain.
There are many tools to watch files. You can watch for writes, watch for the file to grow in size, whatever, change in its access time. Look at "tail", "ls", "fuser" for some ideas. Think of a few lines of shell. Whatever. I was deliberately vague so as to leave open options. Can we get details of your real time, file sizes and date-stamps, please. Right now this is just a p'ing contest. I've given a description of an area of investigation, and I hope you'll examine it and report back some 'metrics'. Then we can determine if or if not this is related.
Nevertheless, in all the many years that I have been using Firefox (and its predecessor) this problem has NEVER occurred on my, or my wife's, system - until 3.6 -- and maybe until the updates/upgrades to 11.2 which occurred at the same time.
Also, try this. FF needs to save state on a poper shut-down, but its crashed on me and I've been able to start it immediately, whereas I've not been able to start it imediately if I close it. I've had to wait, and seem the sessionstore.js change. So, try crashing FF and see it it will start again immediately. That, at elast, gives us a point of congruence. Don't "shut-down, wait, get frustrated, kill". Kill it to start with. While monitoring sessionstore.js for changes. Then do a close ... while monitoring sessionstore.js for changes. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Michael S. Dunsavage said the following on 02/14/2010 01:19 AM:
(2) this is the *most* annoying PITA: during a session, if you close down Firefox but then decide to restart it for whatever reason, openSUSE/KDE/whatever gives you the error message, "Firefox is already running. ..." and won't let you start Firefox until you "close" the already "running" Firefox.
I've had this problem a few times, and after a few moments it seems to shut down correctly on its own. Could it possibly be doing some caching so it can remember your tabs and what not?
This is what I have determined, and its not new to FF 3.6. I observed this behaviour some while ago. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 14 Feb 2010 05:54:46 Basil Chupin wrote:
I, and my wife, are running the very latest Firefox (as provided by openSUSE repos) on 32-bit computers.
Hi Basil How do you shut FF down from the menu or by just clicking on the X top right , I have found a few apps that dont shut down correctly with the X method but are OK when you do " file exit" Pete ( excuse any bad typing glasses got broke yesterday) -- Powered by openSUSE 11.2 Milestone 2 (x86_64) Kernel: 2.6.30-rc6-git3-4- default KDE: 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514)) "release 1" 07:07 up 21 days 21:50, 2 users, load average: 0.00, 0.01, 0.00
On 14/02/10 18:11, Peter Nikolic wrote:
On Sunday 14 Feb 2010 05:54:46 Basil Chupin wrote:
I, and my wife, are running the very latest Firefox (as provided by openSUSE repos) on 32-bit computers.
Hi Basil
How do you shut FF down from the menu or by just clicking on the X top right , I have found a few apps that dont shut down correctly with the X method but are OK when you do " file exit"
Pete ( excuse any bad typing glasses got broke yesterday)
Sorry about your spectacles, but thanks for the brave effort in not only reading my post but also responding to it :-) . (I, being short-sighted, can handle print close up; but I feel sorry for those who are long-sighted, like my wife is now.) I have tried closing FF with all of the (normal) 4 options. Nothing helps - the damn thing still does as I described :-( . But only FF. All other apps appear to be AOK. BC -- "If it weren't for electricity we'd be all watching televion by candlelight." George Gobel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2010-02-14 at 16:54 +1100, Basil Chupin wrote:
(2) this is the *most* annoying PITA: during a session, if you close down Firefox but then decide to restart it for whatever reason, openSUSE/KDE/whatever gives you the error message, "Firefox is already running. ..." and won't let you start Firefox until you "close" the already "running" Firefox.
Just wait and try later. It is doing some sort of cleaning up.
and/or knows how to fix this PITA?
Complain to the devs so that they do this faster or less intruively or something. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkt37+kACgkQtTMYHG2NR9XNcACbBasz2O9dNpjVzX068kRKJwLV DooAnRMWVx7f+p7sPdfbks2IsdTuHlbW =1JKP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 14/02/10 23:43, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sunday, 2010-02-14 at 16:54 +1100, Basil Chupin wrote:
(2) this is the *most* annoying PITA: during a session, if you close down Firefox but then decide to restart it for whatever reason, openSUSE/KDE/whatever gives you the error message, "Firefox is already running. ..." and won't let you start Firefox until you "close" the already "running" Firefox.
Just wait and try later. It is doing some sort of cleaning up.
Sorry, I missed this earlier. Is waiting for a couple of hours long enough, do you think? This is what my wife has done: switched off FF, gone to watch her favourite TV "shows" (a term I use most loosely :-D ) then returns to restart FF.
and/or knows how to fix this PITA?
Complain to the devs so that they do this faster or less intruively or something.
Aren't they here already? I thought someone stated recently, quite categorically, not to "stir s***" - so to speak - here otherwise the devs will abandon this forum, take their ball and bat, and sulk off home :-) . BC -- The calendar's days are numbered! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Basil Chupin wrote:
(2) this is the *most* annoying PITA: during a session, if you close down Firefox but then decide to restart it for whatever reason, openSUSE/KDE/whatever gives you the error message, "Firefox is already running. ..." and won't let you start Firefox until you "close" the already "running" Firefox. Just wait and try later. It is doing some sort of cleaning up.
Sorry, I missed this earlier.
Is waiting for a couple of hours long enough, do you think?
This is what my wife has done: switched off FF, gone to watch her favourite TV "shows" (a term I use most loosely :-D ) then returns to restart FF.
FWIW, I quite often see the "Firefox is already running" message on a 10.2 system with Firefox 2.whatever. That normally clears itself within a few seconds - I guess it's garbage collecting/object destructing or somesuch. I also occasionally see complete lockups. I always presume that these are due to Javascript infinite loops. Does your wife run with many extensions and/or Javascript enabled? Might be worth seeing if the problem occurs in safe mode and/or with Javascript disabled. I think I may give the google browser a try to see if it is less susceptible to such issues. Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 16/02/10 22:09, Dave Howorth wrote:
Basil Chupin wrote:
(2) this is the *most* annoying PITA: during a session, if you close down Firefox but then decide to restart it for whatever reason, openSUSE/KDE/whatever gives you the error message, "Firefox is already running. ..." and won't let you start Firefox until you "close" the already "running" Firefox.
Just wait and try later. It is doing some sort of cleaning up.
Sorry, I missed this earlier.
Is waiting for a couple of hours long enough, do you think?
This is what my wife has done: switched off FF, gone to watch her favourite TV "shows" (a term I use most loosely :-D ) then returns to restart FF.
FWIW, I quite often see the "Firefox is already running" message on a 10.2 system with Firefox 2.whatever. That normally clears itself within a few seconds - I guess it's garbage collecting/object destructing or somesuch. I also occasionally see complete lockups. I always presume that these are due to Javascript infinite loops.
Most interesting. We have *never* seen this behaviour until the latest FF (3.6).
Does your wife run with many extensions and/or Javascript enabled? Might be worth seeing if the problem occurs in safe mode and/or with Javascript disabled.
No. The only thing she does is go to various URLs reading the latest news/gossip/fashions/recipes - with the occasional visit to YouTube. And all this with no more than 2 or three tabs opened. Re extensions: we both run the same extensions and have been for quite a long time - well before 3.6 came along. In any case, there are only 4 extensions which we do run, all to do with security.
I think I may give the google browser a try to see if it is less susceptible to such issues.
Good luck :-) . BC -- The calendar's days are numbered! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2010-02-16 at 17:37 +1100, Basil Chupin wrote:
On 14/02/10 23:43, Carlos E. R. wrote:
Just wait and try later. It is doing some sort of cleaning up.
Sorry, I missed this earlier.
Is waiting for a couple of hours long enough, do you think?
That's excesive! :-( Kill it. Try compacting the sqlite database someone mentioned. :-?
Complain to the devs so that they do this faster or less intruively or something.
Aren't they here already? I thought someone stated recently, quite categorically, not to "stir s***" - so to speak - here otherwise the devs will abandon this forum, take their ball and bat, and sulk off home :-) .
I don't think they lurk here >:-) There is the suse maintainer, though. I believe. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkt6imgACgkQtTMYHG2NR9Uz0QCgg+aOBKHKbb0JH5i4lvuzVS3z cBoAn3FkmkXTFjzBN4vEMI/zcMno0NXk =G97E -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2010/02/14 16:54 (GMT+1100) Basil Chupin composed:
(2) this is the *most* annoying PITA: during a session,
How long is one of your typical sessions? How long do you wait after closing to start again?
if you close down Firefox but then decide to restart it for whatever reason, openSUSE/KDE/whatever gives you the error message, "Firefox is already running. ..." and won't let you start Firefox until you "close" the already "running" Firefox.
Just an idea: Look in your profile dir for the largest files. Likely one of *.sqlite is obscenely large. If so, try going into prefs -> security and uncheck the two "block..." boxes, then close, then see if startup works as expected. If it does, but you wish to keep those security settings on, try going to one of the Mozilla web sites and find out how to "compact" those .sqlite files. Then turn the two prefs on again and see how shutdown and startup work. -- "Our Constitution was made only for a moral and religious people. It is wholly inadequate to the government of any other." John Adams, 2nd US President Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Felix Miata said the following on 02/14/2010 09:03 AM:
Look in your profile dir for the largest files. Likely one of *.sqlite is obscenely large. If so, try going into prefs -> security and uncheck the two "block..." boxes, then close, then see if startup works as expected. If it does, but you wish to keep those security settings on, try going to one of the Mozilla web sites and find out how to "compact" those .sqlite files. Then turn the two prefs on again and see how shutdown and startup work.
Look at http://www.downloadsquad.com/2009/08/24/speed-up-firefox-by-cleaning-out-you... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 15/02/10 01:24, Anton Aylward wrote:
Felix Miata said the following on 02/14/2010 09:03 AM:
Look in your profile dir for the largest files. Likely one of *.sqlite is obscenely large. If so, try going into prefs -> security and uncheck the two "block..." boxes, then close, then see if startup works as expected. If it does, but you wish to keep those security settings on, try going to one of the Mozilla web sites and find out how to "compact" those .sqlite files. Then turn the two prefs on again and see how shutdown and startup work.
Look at http://www.downloadsquad.com/2009/08/24/speed-up-firefox-by-cleaning-out-you...
Thanks for this. Put thru this "fiddle" and it hasn't done a thing :-( . However, just before I had to go out and do some shopping I put quite a number of upgrades which also included Firefox and Thunderbird. I'll see if these have done anything good. BC -- The calendar's days are numbered! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2010-02-16 at 16:22 +1100, Basil Chupin wrote:
On 15/02/10 01:24, Anton Aylward wrote:
Look at http://www.downloadsquad.com/2009/08/24/speed-up-firefox-by-cleaning-out-you...
Thanks for this. Put thru this "fiddle" and it hasn't done a thing :-( .
The recomendation is to do: 1. Open the Firefox tools menu and click on error console. 2. Paste the following command into the code box as a single line (as pictured): Components.classes["@mozilla.org/browser/nav-history-service;1"].getService(Components.interfaces.nsPIPlacesDatabase).DBConnection.executeSimpleSQL("VACUUM"); 3. Hit [enter] or click the evaluate button. That would clean the "places" database. I have several databases: cer@nimrodel:~/.mozilla/firefox/RANDOM.default> l *sqlite - -rw-r--r-- 1 cer users 7168 2009-12-11 20:20 content-prefs.sqlite - -rw-r--r-- 1 cer users 146432 2010-02-16 15:04 cookies.sqlite - -rw-r--r-- 1 cer users 98304 2010-02-09 01:25 downloads.sqlite - -rw-r--r-- 1 cer users 338944 2010-02-14 12:32 formhistory.sqlite - -rw-r--r-- 1 cer users 94208 2010-01-14 22:05 permissions.sqlite - -rw-r--r-- 1 cer users 3715072 2010-02-16 15:04 places.sqlite - -rw-r--r-- 1 cer users 5120 2010-02-13 02:39 search.sqlite - -rw-r--r-- 1 cer users 8770560 2008-09-10 02:26 urlclassifier2.sqlite - -rw-r--r-- 1 cer users 44347392 2010-02-16 14:48 urlclassifier3.sqlite - -rw-r--r-- 1 cer users 2048 2009-02-24 02:14 webappsstore.sqlite But the big one is the urlclassifier clasifier, which I understand has to do with phising protection. I don't know how to "vacuum" all of them. Mmm... look here: http://kb.mozillazine.org/Profile_folder_-_Firefox, under "Managing profiles". You can select a profile to use, create a new profile, and delete or rename an existing profile using the Profile Manager. Profiles can become corrupted, in which case you need to create a new profile then transfer your data and settings to the new profile. To safeguard your important data you should make a backup copy of up your profile. Maybe your profile is corrupted, try that transfer procedure. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkt6qRsACgkQtTMYHG2NR9XPTACfSsL6SHrLD/oFf4H98G99J2EO V4AAn0v6/VOjMjTC8Z7cT6Sr78gQwjM0 =SRI2 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 17/02/10 01:17, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday, 2010-02-16 at 16:22 +1100, Basil Chupin wrote:
On 15/02/10 01:24, Anton Aylward wrote:
Look at http://www.downloadsquad.com/2009/08/24/speed-up-firefox-by-cleaning-out-you...
Thanks for this. Put thru this "fiddle" and it hasn't done a thing :-( .
The recomendation is to do:
1. Open the Firefox tools menu and click on error console. 2. Paste the following command into the code box as a single line (as pictured):
Components.classes["@mozilla.org/browser/nav-history-service;1"].getService(Components.interfaces.nsPIPlacesDatabase).DBConnection.executeSimpleSQL("VACUUM");
3. Hit [enter] or click the evaluate button.
That would clean the "places" database. I have several databases:
See my response a few minutes ago to Felix. It appears (a qualified statement as I stated) that some upgrades to 11.2/KDE4.4 may have solved this problem. BC -- The calendar's days are numbered! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 15/02/10 01:03, Felix Miata wrote:
On 2010/02/14 16:54 (GMT+1100) Basil Chupin composed:
(2) this is the *most* annoying PITA: during a session,
How long is one of your typical sessions? How long do you wait after closing to start again?
if you close down Firefox but then decide to restart it for whatever reason, openSUSE/KDE/whatever gives you the error message, "Firefox is already running. ..." and won't let you start Firefox until you "close" the already "running" Firefox.
Just an idea:
Look in your profile dir for the largest files. Likely one of *.sqlite is obscenely large. If so, try going into prefs -> security and uncheck the two "block..." boxes, then close, then see if startup works as expected. If it does, but you wish to keep those security settings on, try going to one of the Mozilla web sites and find out how to "compact" those .sqlite files. Then turn the two prefs on again and see how shutdown and startup work.
Thanks for this. There is one 'obscenely' large sqlite file. While I haven't yet tried your approach, doing the VACUUM thingie hasn't done a thing to that largely 'obscene' file. I'll try what you suggest at the first opportunity (and if the most recent upgrades to FF and TB haven't fixed the problem). BC -- The calendar's days are numbered! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 15/02/10 01:03, Felix Miata wrote:
On 2010/02/14 16:54 (GMT+1100) Basil Chupin composed:
(2) this is the *most* annoying PITA: during a session,
How long is one of your typical sessions? How long do you wait after closing to start again?
if you close down Firefox but then decide to restart it for whatever reason, openSUSE/KDE/whatever gives you the error message, "Firefox is already running. ..." and won't let you start Firefox until you "close" the already "running" Firefox.
Just an idea:
Look in your profile dir for the largest files. Likely one of *.sqlite is obscenely large. If so, try going into prefs -> security and uncheck the two "block..." boxes, then close, then see if startup works as expected. If it does, but you wish to keep those security settings on, try going to one of the Mozilla web sites and find out how to "compact" those .sqlite files. Then turn the two prefs on again and see how shutdown and startup work.
OK, as a follow-up to my earlier response to your post. I did not follow your suggestions above, but did do what Anton referenced (and which Carlos then also mentioned) about how to VACUUM the sqlite dbs. When I did that (?)a few days ago, nothing happened - I still got the error message stating that FF was running. In the meantime, there were some upgrades to 11.2 and KDE4.4 and this appears to have cleared this problem. If I close FF down and then restart it 2 seconds later - it restarts without an error message. (This as it is at the moment, OK :-) . What will happen tomorrow, the day after, I cannot say :-D .) Why I state that some upgrades may have been responsible for the "fix" is that I did NOT put thru on my wife's computer the VACUUM thingie - but today I see that she is able to close FF and restart it without any error messages. Again, this is at it was less than 20 minutes ago - but what will happen tomorrow..... who knows :-) . The only other thing which is now still to be resolved is why FF almost always starts up on it on accord when the computer is first started at the start of the day. Perhaps this has also been solved by the upgrades yesterday/today but I won't really know for certain until the systems (mine and my wife's) have been closed down a few times at least at night and restarted the next morning. Will report when I have some "facts" (so to speak). BC -- The calendar's days are numbered! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am 14.02.2010 06:54, schrieb Basil Chupin:
(2) this is the *most* annoying PITA: during a session, if you close down Firefox but then decide to restart it for whatever reason, openSUSE/KDE/whatever gives you the error message, "Firefox is already running. ..." and won't let you start Firefox until you "close" the already "running" Firefox.
I know this probably won't help at all, but we've had the _exact_ same problem with Thunderbird 3 on our XDMCP server. Users closed Thunderbird and logged out (aka closed the current XDMCP session) and it was still running the next morning when they returned to work, logged back in and tried to start it anew. The neverending calls and no solution in sight resulted in us reverting back to Thunderbird 2.0.0.23. To be fair that wasn't our only issue with TB3 but one of the major ones. Also, I've had nothing but trouble with openSUSE's Mozilla implementation, which is in several ways different from the "vanilla" Mozilla version. Which is why I dumped Novell's failed attempt at providing me with a usable browser and email client, and just go to mozilla.org, download the latest .tar.gz, untar it to /opt and adjust the link in /usr/bin accordingly if necessary. Never had any problems with Firefox ever since. Martin -- Rieke Computersysteme GmbH Hellerholz 5 D-82061 Neuried Email: martin@rhm.de HRB Muenchen 73617 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi, On 02/15/2010 01:27 PM, Martin Jungowski wrote:
Also, I've had nothing but trouble with openSUSE's Mozilla implementation, which is in several ways different from the "vanilla" Mozilla version. Which is why I dumped Novell's failed attempt at providing me with a usable browser and email client, and just go to mozilla.org, download the latest .tar.gz, untar it to /opt and adjust the link in /usr/bin accordingly if necessary. Never had any problems with Firefox ever since.
Please point us to the bugreports you are refering to. While I admit that there are smaller changes in openSUSE's Firefox compared with upstream they are usually not that intrusive nowadays. So please let us know about your issues since I'm really interested in fixing issues if possible. Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am 15.02.2010 13:52, schrieb Wolfgang Rosenauer:
Please point us to the bugreports you are refering to. While I admit that there are smaller changes in openSUSE's Firefox compared with upstream they are usually not that intrusive nowadays. So please let us know about your issues since I'm really interested in fixing issues if possible.
Wolfgang, the last killer was text boxes such as the input boxes in Forums, a Wiki, etc. As soon as one was active the entire system stopped responding, the mouse stopped moving, typing was extremely sluggish - the entire system was unusable. Didn't affect KDE4 but both XFCE4 and Gnome2. We're in a bit of a special situation though because we still use XDMCP for our several hundred thin clients to connect to the login server and start a remote X session over XDMCP. Martin -- Rieke Computersysteme GmbH Hellerholz 5 D-82061 Neuried Email: martin@rhm.de HRB Muenchen 73617 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 15/02/10 23:27, Martin Jungowski wrote:
Am 14.02.2010 06:54, schrieb Basil Chupin:
(2) this is the *most* annoying PITA: during a session, if you close down Firefox but then decide to restart it for whatever reason, openSUSE/KDE/whatever gives you the error message, "Firefox is already running. ..." and won't let you start Firefox until you "close" the already "running" Firefox.
I know this probably won't help at all, but we've had the _exact_ same problem with Thunderbird 3 on our XDMCP server. Users closed Thunderbird and logged out (aka closed the current XDMCP session) and it was still running the next morning when they returned to work, logged back in and tried to start it anew. The neverending calls and no solution in sight resulted in us reverting back to Thunderbird 2.0.0.23. To be fair that wasn't our only issue with TB3 but one of the major ones.
Also, I've had nothing but trouble with openSUSE's Mozilla implementation, which is in several ways different from the "vanilla" Mozilla version. Which is why I dumped Novell's failed attempt at providing me with a usable browser and email client, and just go to mozilla.org, download the latest .tar.gz, untar it to /opt and adjust the link in /usr/bin accordingly if necessary. Never had any problems with Firefox ever since.
Martin
Thanks for this. If today's upgrades to FF and TB haven't fixed the problem then I will go back to the versions from Mozilla itself (as I used to do a while back). BC -- The calendar's days are numbered! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 15/02/10 23:27, Martin Jungowski wrote:
Am 14.02.2010 06:54, schrieb Basil Chupin:
(2) this is the *most* annoying PITA: during a session, if you close down Firefox but then decide to restart it for whatever reason, openSUSE/KDE/whatever gives you the error message, "Firefox is already running. ..." and won't let you start Firefox until you "close" the already "running" Firefox.
I know this probably won't help at all, but we've had the _exact_ same problem with Thunderbird 3 on our XDMCP server. Users closed Thunderbird and logged out (aka closed the current XDMCP session) and it was still running the next morning when they returned to work, logged back in and tried to start it anew. The neverending calls and no solution in sight resulted in us reverting back to Thunderbird 2.0.0.23. To be fair that wasn't our only issue with TB3 but one of the major ones.
Also, I've had nothing but trouble with openSUSE's Mozilla implementation, which is in several ways different from the "vanilla" Mozilla version. Which is why I dumped Novell's failed attempt at providing me with a usable browser and email client, and just go to mozilla.org, download the latest .tar.gz, untar it to /opt and adjust the link in /usr/bin accordingly if necessary. Never had any problems with Firefox ever since.
Martin
Thanks, Martin. It appears that the most recent upgrades (in the past day or so) to 11.2/KDE may have solved my FF hassle - although there is still one more which is yet to be confirmed as solved. (See my response to Felix a few minutes ago.) BC -- The calendar's days are numbered! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 17/02/10 16:10, Basil Chupin wrote:
On 15/02/10 23:27, Martin Jungowski wrote:
Am 14.02.2010 06:54, schrieb Basil Chupin:
(2) this is the *most* annoying PITA: during a session, if you close down Firefox but then decide to restart it for whatever reason, openSUSE/KDE/whatever gives you the error message, "Firefox is already running. ..." and won't let you start Firefox until you "close" the already "running" Firefox.
I know this probably won't help at all, but we've had the _exact_ same problem with Thunderbird 3 on our XDMCP server. Users closed Thunderbird and logged out (aka closed the current XDMCP session) and it was still running the next morning when they returned to work, logged back in and tried to start it anew. The neverending calls and no solution in sight resulted in us reverting back to Thunderbird 2.0.0.23. To be fair that wasn't our only issue with TB3 but one of the major ones.
Also, I've had nothing but trouble with openSUSE's Mozilla implementation, which is in several ways different from the "vanilla" Mozilla version. Which is why I dumped Novell's failed attempt at providing me with a usable browser and email client, and just go to mozilla.org, download the latest .tar.gz, untar it to /opt and adjust the link in /usr/bin accordingly if necessary. Never had any problems with Firefox ever since.
Martin
Thanks, Martin. It appears that the most recent upgrades (in the past day or so) to 11.2/KDE may have solved my FF hassle - although there is still one more which is yet to be confirmed as solved. (See my response to Felix a few minutes ago.)
It looks like the latest upgrades have solved both problems: FF can be restarted without hassles even a few seconds after closing it, and FF does not automatically start on booting the system at the beginning of a day (after shutting down the computer at night). Well, this is the result after a couple of days now on both my wife's and my computers (with 11.2 32-bit oS). BC -- The calendar's days are numbered! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (9)
-
Anton Aylward -
Basil Chupin -
Carlos E. R. -
Dave Howorth -
Felix Miata -
Martin Jungowski -
Michael S. Dunsavage -
Peter Nikolic -
Wolfgang Rosenauer