Every so often firefox just decides to spilt pages up into what looks like each frame. Basically it opens new windows for each element of the webpage. Before I upgraded to 1.5.0.1 it would happen every few days or longer. I'd just kill the browser and restart it. Now with 1.5.0.1 it's happening every few hours or so. Is this just happening to me? I don't think it's website related. Konqueror works just fine. Nick
Nick Zentena wrote:
Every so often firefox just decides to spilt pages up into what looks like each frame. Basically it opens new windows for each element of the webpage. Before I upgraded to 1.5.0.1 it would happen every few days or longer. I'd just kill the browser and restart it. Now with 1.5.0.1 it's happening every few hours or so. Is this just happening to me? I don't think it's website related. Konqueror works just fine.
I have never seen this. A frame is a frame. Do you have an example URL where this is happening for you, and is it repeatable every time?
On Saturday 18 February 2006 09:50, Anders Johansson wrote:
Nick Zentena wrote:
Every so often firefox just decides to spilt pages up into what looks like each frame. Basically it opens new windows for each element of the webpage. Before I upgraded to 1.5.0.1 it would happen every few days or longer. I'd just kill the browser and restart it. Now with 1.5.0.1 it's happening every few hours or so. Is this just happening to me? I don't think it's website related. Konqueror works just fine.
I have never seen this. A frame is a frame. Do you have an example URL where this is happening for you, and is it repeatable every time?
It's happening on various websites. It doesn't happen when you first go to the website but after a period of time the browser starts breaking the page into windows. With older versions I could keep the browser open for days and it would be okay. The newer version of the browser starts having the problem earlier. If I reload the page about 50% of the time it's okay for a little while. If I close the window most of the time it kills the browser. The new windows won't have the browser bar etc. Nick
On Saturday 18 February 2006 09:36, Nick Zentena wrote:
Every so often firefox just decides to spilt pages up into what looks like each frame. Basically it opens new windows for each element of the webpage. Before I upgraded to 1.5.0.1 it would happen every few days or longer. I'd just kill the browser and restart it. Now with 1.5.0.1 it's happening every few hours or so. Is this just happening to me? I don't think it's website related. Konqueror works just fine.
Nick
Hi Nick, I'd uninstall Firefox and remove every trace of it from your system and reinstall from a fresh rpm. I've followed the update/upgrade path like most and have never seen the behavior you've described. regards, Carl
On Saturday 18 February 2006 09:55, Carl Hartung wrote:
I'd uninstall Firefox and remove every trace of it from your system and reinstall from a fresh rpm. I've followed the update/upgrade path like most and have never seen the behavior you've described.
I think this isn't an issue that'll be that easy to fix. I've had the issue with a clean SuSE 10.0 install. With a self compiled copy of the latest firefox. I think it used to happen with 9.3 to but I don't really remember. It's just gotten to the point that it's just too often. Nick
On Saturday 18 February 2006 10:04, Nick Zentena wrote:
I think this isn't an issue that'll be that easy to fix. I've had the issue with a clean SuSE 10.0 install.
I don't know what else to suggest, Nick. I haven't seen or heard of this behavior before... not since I've been using mozilla.org software, which is several years.
With a self compiled copy of the latest firefox.
I thought the whole point of running an rpm package based distribution like SUSE was to limit the hassle of building/installing 'home brew' software and, theoretically, to reduce the frequency of circumstances just like this? There may be some other inconsistency in your system or it could be your build. Who knows? I suggest a reasonable course of action would be to try a package that is presently being used by many others who aren't experiencing this problem. regards, Carl
On Saturday 18 February 2006 10:52, Carl Hartung wrote:
I thought the whole point of running an rpm package based distribution like SUSE was to limit the hassle of building/installing 'home brew' software and, theoretically, to reduce the frequency of circumstances just like this? There may be some other inconsistency in your system or it could be your build. Who knows? I suggest a reasonable course of action would be to try a package that is presently being used by many others who aren't experiencing this problem.
Well waiting for RPMs is great when it works. But when they give you the same problem you're trying to fix nothing is lost by compiling the tarball. Nick
On Saturday 18 February 2006 12:19, Nick Zentena wrote:
On Saturday 18 February 2006 10:52, Carl Hartung wrote:
I thought the whole point of running an rpm package based distribution like SUSE was to limit the hassle of building/installing 'home brew' software and, theoretically, to reduce the frequency of circumstances just like this? There may be some other inconsistency in your system or it could be your build. Who knows? I suggest a reasonable course of action would be to try a package that is presently being used by many others who aren't experiencing this problem.
Well waiting for RPMs is great when it works. But when they give you the same problem you're trying to fix nothing is lost by compiling the tarball.
Either this logic is fragmented or I've misinterpreted your meaning: If a correctly installed 'factory' rpm version of Firefox exhibits this bizarre behavior there is definitely an underlying inconsistency somewhere in that system. It could be anything from a conflicting library installed that rpm knows nothing about to an obsolete plug-in that has somehow been overlooked during an update/upgrade. Whatever that inconsistency is, installing Firefox again... particularly from tarball... is hardly likely to fix a problem like that. Have you launched Firefox from a shell to see if it spits out any error messages during this behavior? Carl
On Saturday 18 February 2006 14:03, Carl Hartung wrote:
Have you launched Firefox from a shell to see if it spits out any error messages during this behavior?
Ya it mentions something about opening windows. Right now I'm running it from the shell but of course it's pretty stable at the moment. I'll post the error message when it finally screws up. Nick
On Sunday 19 February 2006 14:54, Nick Zentena wrote:
On Saturday 18 February 2006 14:03, Carl Hartung wrote:
Have you launched Firefox from a shell to see if it spits out any error messages during this behavior?
Ya it mentions something about opening windows. Right now I'm running it from the shell but of course it's pretty stable at the moment. I'll post the error message when it finally screws up.
Which version are you running now, the 'home brew' or factory rpm? Carl
On Sunday 19 February 2006 15:08, Carl Hartung wrote:
On Sunday 19 February 2006 14:54, Nick Zentena wrote:
On Saturday 18 February 2006 14:03, Carl Hartung wrote:
Have you launched Firefox from a shell to see if it spits out any error messages during this behavior?
Ya it mentions something about opening windows. Right now I'm running it from the shell but of course it's pretty stable at the moment. I'll post the error message when it finally screws up.
Which version are you running now, the 'home brew' or factory rpm?
The SuSE rpm. I deleted the tarball version awhile back. Nick
On Sunday 19 February 2006 15:13, Nick Zentena wrote:
On Sunday 19 February 2006 15:08, Carl Hartung wrote:
On Sunday 19 February 2006 14:54, Nick Zentena wrote:
On Saturday 18 February 2006 14:03, Carl Hartung wrote:
Have you launched Firefox from a shell to see if it spits out any error messages during this behavior?
Ya it mentions something about opening windows. Right now I'm running it from the shell but of course it's pretty stable at the moment. I'll post the error message when it finally screws up.
Which version are you running now, the 'home brew' or factory rpm?
The SuSE rpm. I deleted the tarball version awhile back.
If the behavior reappears: copy the error messages to a text file and save them to share with us, then shut down Firefox, move the ad blocking plug-in somewhere for safekeeping, delete the file ~/.mozilla/pluginreg.dat, and launch it again from a shell for another test. This will firmly establish that the ad blocking plug-in *is* or *is not* somehow involved. The fact that the errant behavior is occurring somewhere between the parsing and displaying of pages leads me to suspect that certain elements may be being wrongly interpreted or misconstrued as pop-ups or frames. This is the same area of functionality that pop-op stopping and ad blocking software adapts in browsers. Carl
On Sunday 19 February 2006 15:34, Carl Hartung wrote:
If the behavior reappears: copy the error messages to a text file and save them to share with us, then shut down Firefox, move the ad blocking plug-in somewhere for safekeeping, delete the file ~/.mozilla/pluginreg.dat, and launch it again from a shell for another test. This will firmly establish that the ad blocking plug-in *is* or *is not* somehow involved. The fact that the errant behavior is occurring somewhere between the parsing and displaying of pages leads me to suspect that certain elements may be being wrongly interpreted or misconstrued as pop-ups or frames. This is the same area of functionality that pop-op stopping and ad blocking software adapts in browsers.
Carl
This is from the test account. So no adblock just the system wide plugins. Java,flash,pdf reader. The website that most often causes problems is: http://expattalk.com/ But Ebay does it to eventually. I don't think it's site related. It's just the other sites are used more often. (Gecko:28738): Gdk-WARNING **: GdkWindow 0x3743d76 unexpectedly destroyed (Gecko:28738): Gdk-CRITICAL **: gdk_window_set_user_data: assertion `window != NULL' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_set_back_pixmap: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (Gecko:28738): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_move_resize: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_show_unraised: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_resize: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_hide: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_set_user_data: assertion `window != NULL' failed (Gecko:28738): Gdk-CRITICAL **: _gdk_window_destroy_hierarchy: assertion `window != NULL' failed (Gecko:28738): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (Gecko:28738): Gdk-WARNING **: GdkWindow 0x3743d6c unexpectedly destroyed (Gecko:28738): Gdk-CRITICAL **: gdk_window_set_user_data: assertion `window != NULL' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_set_back_pixmap: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (Gecko:28738): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_resize: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_hide: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_move_resize: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-WARNING **: GdkWindow 0x3743d6e unexpectedly destroyed (Gecko:28738): Gdk-CRITICAL **: gdk_window_show_unraised: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-WARNING **: GdkWindow 0x3743d82 unexpectedly destroyed (Gecko:28738): Gdk-WARNING **: GdkWindow 0x3743d00 unexpectedly destroyed (Gecko:28738): Gdk-CRITICAL **: gdk_window_hide: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_set_user_data: assertion `window != NULL' failed (Gecko:28738): Gdk-CRITICAL **: _gdk_window_destroy_hierarchy: assertion `window != NULL' failed (Gecko:28738): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_set_user_data: assertion `window != NULL' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_set_back_pixmap: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (Gecko:28738): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_resize: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_hide: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_move_resize: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_show_unraised: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_set_user_data: assertion `window != NULL' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_set_back_pixmap: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (Gecko:28738): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_resize: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_hide: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_move_resize: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_show_unraised: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_show_unraised: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_show_unraised: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_show_unraised: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_show_unraised: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_hide: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_set_user_data: assertion `window != NULL' failed (Gecko:28738): Gdk-CRITICAL **: _gdk_window_destroy_hierarchy: assertion `window != NULL' failed (Gecko:28738): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_hide: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_set_user_data: assertion `window != NULL' failed (Gecko:28738): Gdk-CRITICAL **: _gdk_window_destroy_hierarchy: assertion `window != NULL' failed (Gecko:28738): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (Gecko:28738): Gdk-WARNING **: GdkWindow 0x3743d79 unexpectedly destroyed (Gecko:28738): Gdk-CRITICAL **: gdk_window_set_user_data: assertion `window != NULL' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_set_back_pixmap: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (Gecko:28738): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_move_resize: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_show_unraised: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_resize: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-WARNING **: GdkWindow 0x3743d4e unexpectedly destroyed (Gecko:28738): Gdk-CRITICAL **: gdk_window_set_user_data: assertion `window != NULL' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_set_back_pixmap: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (Gecko:28738): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_resize: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_hide: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_move_resize: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_show_unraised: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_move_resize: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_show_unraised: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-WARNING **: GdkWindow 0x3743dfb unexpectedly destroyed (Gecko:28738): Gdk-WARNING **: GdkWindow 0x3743df7 unexpectedly destroyed (Gecko:28738): Gdk-CRITICAL **: gdk_window_show_unraised: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_show_unraised: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_show_unraised: assertion `GDK_IS_WINDOW (window)' failed (Gecko:28738): Gdk-CRITICAL **: gdk_window_show_unraised: assertion `GDK_IS_WINDOW (window)' failed
On Monday 20 February 2006 10:30, Nick Zentena wrote: <snip> What does "rpm -qa | grep gtk-qt-engine" tell you? Carl
On Monday 20 February 2006 12:32, Carl Hartung wrote:
On Monday 20 February 2006 10:30, Nick Zentena wrote: <snip>
What does "rpm -qa | grep gtk-qt-engine" tell you?
gtk-qt-engine-0.6cvs20050229-11 Looking at the Novell website that appears to be the version that shipped with 10.0 http://www.novell.com/products/linuxpackages/professional/gtk-qt-engine.html Did I miss an update? Doesn't look like any newer final releases. Nick
On 2/20/06, Nick Zentena
On Sunday 19 February 2006 15:34, Carl Hartung wrote:
If the behavior reappears: copy the error messages to a text file and save them to share with us, then shut down Firefox, move the ad blocking plug-in somewhere for safekeeping, delete the file ~/.mozilla/pluginreg.dat, and launch it again from a shell for another test. This will firmly establish that the ad blocking plug-in *is* or *is not* somehow involved. The fact that the errant behavior is occurring somewhere between the parsing and displaying of pages leads me to suspect that certain elements may be being wrongly interpreted or misconstrued as pop-ups or frames. This is the same area of functionality that pop-op stopping and ad blocking software adapts in browsers.
Carl
This is from the test account. So no adblock just the system wide plugins. Java,flash,pdf reader.
<snipped GTK errors>
Nick,
I still think there is something wrong with the toolkit. Get the GTK
sources and related libraries, build it and link Firefox against the
manually built libs. Follow the instructions at
http://developer.mozilla.org/en/docs/Build_Documentation.
\Steve
--
Steve Graegert
On Monday 20 February 2006 13:40, Steve Graegert wrote:
Nick,
I still think there is something wrong with the toolkit. Get the GTK sources and related libraries, build it and link Firefox against the manually built libs. Follow the instructions at http://developer.mozilla.org/en/docs/Build_Documentation.
\Steve
Hi Steve! I also want to confirm with you, Nick, that you're running 'ldconfig' and 'SuSEconfig' after installing software with rpm from the comand line? Carl
Nick, On Saturday 18 February 2006 07:04, Nick Zentena wrote:
On Saturday 18 February 2006 09:55, Carl Hartung wrote:
I'd uninstall Firefox and remove every trace of it from your system and reinstall from a fresh rpm. I've followed the update/upgrade path like most and have never seen the behavior you've described.
I think this isn't an issue that'll be that easy to fix. I've had the issue with a clean SuSE 10.0 install. With a self compiled copy of the latest firefox. I think it used to happen with 9.3 to but I don't really remember. It's just gotten to the point that it's just too often.
Then I would not be looking at Firefox itself. Do you run some kind of caching proxy or other software that interposes itself between the browser and the servers it's accessing? Are you using any uncommon add-ins or plug-ins that might be altering or adulterating the HTML or the DOM tree? Is it possible you're using outdated versions of such add-ins or plug-ins? In any event, the unusualness of your symptoms and the fact that they span versions and builds strongly suggest their orginate outside Firefox proper.
Nick
Randall Schulz
On Saturday 18 February 2006 11:21, Randall R Schulz wrote:
Then I would not be looking at Firefox itself. Do you run some kind of caching proxy or other software that interposes itself between the browser and the servers it's accessing? Are you using any uncommon add-ins or plug-ins that might be altering or adulterating the HTML or the DOM tree? Is it possible you're using outdated versions of such add-ins or plug-ins?
In any event, the unusualness of your symptoms and the fact that they span versions and builds strongly suggest their orginate outside Firefox proper.
No nothing usual. The only reasons I think it's firefox is it doesn't happen with Konqueror and it got worse with the latest update. Nick
Nick, On Saturday 18 February 2006 09:15, Nick Zentena wrote:
On Saturday 18 February 2006 11:21, Randall R Schulz wrote:
...
In any event, the unusualness of your symptoms and the fact that they span versions and builds strongly suggest their orginate outside Firefox proper.
No nothing usual. The only reasons I think it's firefox is it doesn't happen with Konqueror and it got worse with the latest update.
You don't think that the fragmentation of frames into separate windows is unusual? Did anyone report to you they've had the same problem? The fact that it's getting worse is consistent with their being add-in(s) or plug-in(s) that are incompatible and as the interface between browser and add-in or plug-in changes over time (or as bugs that were relied on are fixed), the symptom worsens. I'm no expert, but I do believe that one could write add-in code to create these symptoms (by altering the HTML or DOM), so it's perfectly plausible that it's a malfunctioning add-in. Anyway, what is your hypothesis? Apart from trying different versions and building your own version of the software, what have you done to diagnose the problem? Have you tried eradicating (or cleaning out) your ~/.mozilla/firefox directory? Have you looked there for anything that could survive re-installs and rebuilds (as Ken Schneider suggested)?
Nick
Randall Schulz
On Saturday 18 February 2006 12:39, Randall R Schulz wrote:
Nick,
On Saturday 18 February 2006 09:15, Nick Zentena wrote:
On Saturday 18 February 2006 11:21, Randall R Schulz wrote:
...
In any event, the unusualness of your symptoms and the fact that they span versions and builds strongly suggest their orginate outside Firefox proper.
No nothing usual. The only reasons I think it's firefox is it doesn't happen with Konqueror and it got worse with the latest update.
You don't think that the fragmentation of frames into separate windows is unusual? Did anyone report to you they've had the same problem?
No unusual plugins etc. The plugin directory includes flash and adblock. The problem happened before I installed adblock.
Anyway, what is your hypothesis? Apart from trying different versions and building your own version of the software, what have you done to diagnose the problem? Have you tried eradicating (or cleaning out) your ~/.mozilla/firefox directory? Have you looked there for anything that could survive re-installs and rebuilds (as Ken Schneider suggested)?
To be honest when it happened about once a week I ignored it. Easy enough to quit the program and relaunch the program. Right now I'm running a clean test user. If that screws up then it can't be the settings. Nick
Nick Zentena wrote:
On Saturday 18 February 2006 09:55, Carl Hartung wrote:
I'd uninstall Firefox and remove every trace of it from your system and reinstall from a fresh rpm. I've followed the update/upgrade path like most and have never seen the behavior you've described.
I think this isn't an issue that'll be that easy to fix. I've had the issue with a clean SuSE 10.0 install. With a self compiled copy of the latest firefox. I think it used to happen with 9.3 to but I don't really remember. It's just gotten to the point that it's just too often.
Nick
I had a problem with scrollbars recently. Found out one day that it was actually a problem with my touchpad. Moral of the story, it could be something goofy in hardware. (I've noticed that double-clicking some things makes a separate window appear.) hth, ken -- "This world ain't big enough for the both of us," said the big noema to the little noema.
Carl, On Saturday 18 February 2006 06:55, Carl Hartung wrote:
...
Hi Nick,
I'd uninstall Firefox and remove every trace of it from your system and reinstall from a fresh rpm. I've followed the update/upgrade path like most and have never seen the behavior you've described.
Gack. This isn't Windows. Let's leave the "reinstalling will cure what ails you" superstition there.
regards,
Carl
Randall Schulz
On Saturday 18 February 2006 10:06, Randall R Schulz wrote:
Gack. This isn't Windows. Let's leave the "reinstalling will cure what ails you" superstition there.
Yeah, right. People *never* foul up their Linux boxes by installing software incorrectly <roll eyes>. Whatever.
On Sat, 2006-02-18 at 10:35 -0500, Carl Hartung wrote:
On Saturday 18 February 2006 10:06, Randall R Schulz wrote:
Gack. This isn't Windows. Let's leave the "reinstalling will cure what ails you" superstition there.
Yeah, right. People *never* foul up their Linux boxes by installing software incorrectly <roll eyes>.
Not if they use the standard suse installation method which is rpm (and of course suse rpm's). Now if they want to use tar and "make install" that's another issue. In the OP's case simply renaming or deleting ./mozilla/firefox might have fixed the problem whereas re-installing would not remove faulty settings in ./mozilla/firefox which remain until removed and/or fixed. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Saturday 18 February 2006 10:55, Ken Schneider wrote:
Not if they use the standard suse installation method which is rpm (and of course suse rpm's).
This isn't what he did. I suspected as much from his original description of the problem.
Now if they want to use tar and "make install" that's another issue.
This is what he did.
In the OP's case simply renaming or deleting ./mozilla/firefox might have fixed the problem whereas re-installing would not remove faulty settings in ./mozilla/firefox which remain until removed and/or fixed.
I didn't just write "reinstall"... I said "uninstall Firefox and remove every trace of it from your system and reinstall from a fresh rpm." regards, Carl
On Saturday 18 February 2006 11:05, Carl Hartung wrote:
On Saturday 18 February 2006 10:55, Ken Schneider wrote:
Not if they use the standard suse installation method which is rpm (and of course suse rpm's).
This isn't what he did. I suspected as much from his original description of the problem.
Actually I have done YAST updates but I've also tried compiling the latest release version in a user directory. Running it out of the directory. I'm going to try setting up a new user and see if that user has the same problems. If not I guess that will point to the something in the user settings being corrupt. Nick
On 2/18/06, Nick Zentena
On Saturday 18 February 2006 11:05, Carl Hartung wrote:
On Saturday 18 February 2006 10:55, Ken Schneider wrote:
Not if they use the standard suse installation method which is rpm (and of course suse rpm's).
This isn't what he did. I suspected as much from his original description of the problem.
Actually I have done YAST updates but I've also tried compiling the latest release version in a user directory. Running it out of the directory. I'm going to try setting up a new user and see if that user has the same problems. If not I guess that will point to the something in the user settings being corrupt.
If the RPM and a source build expose the same problem I'd suspect the
toolkit to be the culprit. You may also want to try running firefox
using a different window manager, preferably a very simple one like
mwm or twm.
\Steve
--
Steve Graegert
On Saturday 18 February 2006 06:36 am, Nick Zentena wrote:
Every so often firefox just decides to spilt pages up into what looks like each frame. Basically it opens new windows for each element of the webpage. Before I upgraded to 1.5.0.1 it would happen every few days or longer. I'd just kill the browser and restart it. Now with 1.5.0.1 it's happening every few hours or so. Is this just happening to me? I don't think it's website related. Konqueror works just fine.
1. Stop going to "those" pr0n sites. 2. Reinstall. 3. Reboot. :) -- kai www.perfectreign.com <?=$strOffensiveSignature?>
participants (8)
-
Anders Johansson -
Carl Hartung -
kai -
ken -
Ken Schneider -
Nick Zentena -
Randall R Schulz -
Steve Graegert