[Master] Eight (8) instances of back/forward buttons

Bug #212726 reported by Janne Jokitalo
30
Affects Status Importance Assigned to Milestone
firefox-3.0 (Ubuntu)
Invalid
Medium
Unassigned
Hardy
Invalid
High
Alexander Sack
Intrepid
Invalid
Medium
Unassigned

Bug Description

Quickfix: edit your profiles localstore.rdf (Note: backup that file first :) and remove the
duplicated entries of the buttons.

After the update to beta 5, FF now has 8 times the back/forward buttons on the navigation toolbar.
Attached a screenshot.

This is an install of Ubuntu Studio, though, but I doubt it matters, it didn't for beta 4 at least.

Revision history for this message
Janne Jokitalo (astraljava) wrote :
Revision history for this message
Drew (drewwells) wrote :

Right click near your address bar, click customize, click reset defaults. Should fix the multiple back/forward buttons. I did not notice this problem on windows where I had identically configured buttons.

Revision history for this message
Janne Jokitalo (astraljava) wrote : Re: [Bug 212726] Re: Eight (8) instances of back/forward buttons

On Sun, Apr 06, 2008 at 12:41:31PM -0000, Drew wrote:
> Right click near your address bar, click customize, click reset
> defaults. Should fix the multiple back/forward buttons. I did not
> notice this problem on windows where I had identically configured
> buttons.

Thanks, it sure did. But if this keeps on happening to people, I'd say it's an
error needing a fix. I'm fine with it, though. Thanks again. :)

--
Jaska

Iulian Udrea (iulian)
Changed in firefox-3.0:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
John Vivirito (gnomefreak) wrote : Re: Eight (8) instances of back/forward buttons

Can you please run firefox-3.0 in terminal in safe mode
firefox-3.0 -safe-mode and let me know if it still happens
Also do you have compiz running?

Changed in firefox-3.0:
assignee: nobody → mozilla-bugs
status: Confirmed → Incomplete
Revision history for this message
Janne Jokitalo (astraljava) wrote : Re: [Bug 212726] Re: Eight (8) instances of back/forward buttons

On Mon, Apr 07, 2008 at 03:45:23PM -0000, John Vivirito wrote:

Hi John!

> Can you please run firefox-3.0 in terminal in safe mode
> firefox-3.0 -safe-mode and let me know if it still happens

Sorry, I already did as was suggested earlier in the comments thread, and the
extra buttons are gone. Hopefully someone else can.

> Also do you have compiz running?

Nope, I hate that thing. :)

--
Jaska

Revision history for this message
joehill (joseph-hill) wrote :

Same thing happened to me but with 2 sets of back/forward buttons. resetting worked, but I agree that this is a bug--why should it automatically set my preferences to have two sets of buttons when I only need one? I can't imagine an actual use for this or expecting most users to figure out what's wrong and how to fix it.

Revision history for this message
Alexander Sack (asac) wrote :

you can manually fix this in your profiles localstore.rdf. this happens under some (not yet figured) circumstances when firefox is running while upgrading

Revision history for this message
Alexander Sack (asac) wrote :

at least medium priority as this appears to show that bad things can happen when firefox is running while running.

we should investigate this for hardy updates.

Changed in firefox-3.0:
assignee: mozilla-bugs → nobody
importance: Low → Medium
milestone: none → ubuntu-8.04.1
status: Incomplete → Confirmed
Revision history for this message
Alfredo Pironti (alfredo.pironti) wrote :

I can confirm this bug in the Hardy release too.
I upgraded to Hardy and firefox 3 had more than 8 back forward buttons.
The "reset to defaults" worked.
Firefox 2 is still working correctly.

Alexander Sack (asac)
description: updated
Revision history for this message
Alexander Sack (asac) wrote :

On Sun, Apr 06, 2008 at 08:42:39AM -0000, Janne Jokitalo wrote:
>
> ** Attachment added: "Screenshot"
> http://launchpadlibrarian.net/13144977/Mozilla%20Firefox%203%20Beta%205.png
>

this is a duplicate ...

 status incomplete
 tag likely-dup

 - Alexander

Changed in firefox-3.0:
status: Confirmed → Incomplete
Revision history for this message
Janne Jokitalo (astraljava) wrote :

On Wed, May 14, 2008 at 10:01:40AM -0000, Alexander Sack wrote:
> this is a duplicate ...

That's funny, cause I seem to recall other similar bugs being marked as dupes of
this, and as it says in the topic, ( [Master] ) are being marked as such. /me
shrugs

> status incomplete

What more info is required, then? People have reported just the same incidents
all around (okay not _just_, ie. not eight, but other numbers). What procedures
are needed for further debugging?

> tag likely-dup

Of what?

--
Jaska

Revision history for this message
Alexander Sack (asac) wrote :

On Wed, May 14, 2008 at 12:12:29PM -0000, Janne Jokitalo wrote:
> On Wed, May 14, 2008 at 10:01:40AM -0000, Alexander Sack wrote:
> > this is a duplicate ...
>
> That's funny, cause I seem to recall other similar bugs being marked as dupes of
> this, and as it says in the topic, ( [Master] ) are being marked as such. /me
> shrugs
>
> > status incomplete
>
> What more info is required, then? People have reported just the same incidents
> all around (okay not _just_, ie. not eight, but other numbers). What procedures
> are needed for further debugging?
>
> > tag likely-dup
>
> Of what?
>

Yeah, sorry for that. I should read the email footer more carefully
...

 status confirmed
 tag -likely-dup

 - Alexander

Changed in firefox-3.0:
status: Incomplete → Confirmed
Revision history for this message
Alexander Sack (asac) wrote :

upgrade behaviour should improve after RC1 is out as we include at least one more patch that should guard xulrunner from corrupting its XUL cache. However, though that bug might cause this bug in most cases, I think that not all cases will be covered.

In anyway, after RC1 is out we should track duplicates of this bug and in case this issue reappears, take appropriate measures.

Unmilestoning as we cannot reproduce and next upload will hopefully fix all cases.

Changed in firefox-3.0:
assignee: nobody → asac
milestone: ubuntu-8.04.1 → none
Revision history for this message
Alexander Sack (asac) wrote :

targetting for hardy release anyway.

Changed in firefox-3.0:
status: New → Confirmed
importance: Undecided → High
assignee: asac → nobody
assignee: nobody → asac
Revision history for this message
Alexander Sack (asac) wrote :

anyone ever saw this again after 3.0.0 came out?

Changed in firefox-3.0:
status: Confirmed → Incomplete
Revision history for this message
Tux (peter-hoogkamer) wrote :

I have done an upgrade from on a Vmware 5.5.0 Workstation with Hardy Heron to Intrepid Beta and did not see this bug.

Tux

description: updated
description: updated
description: updated
Revision history for this message
Alexander Sack (asac) wrote :

danielbohry, we can only process english bug reports. please dont replace english text in description with some translated content. Thanks.

description: updated
Revision history for this message
Tux (peter-hoogkamer) wrote :

Could this be theme related? Since Janne does not use the default theme. This should not matter, but could be an issue.

Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 212726] Re: [Master] Eight (8) instances of back/forward buttons

On Fri, Nov 07, 2008 at 02:44:43PM -0000, Tux wrote:
> Could this be theme related? Since Janne does not use the default theme.
> This should not matter, but could be an issue.
>

unlikely. from the previous investigations its kind of a
localstore.rdf corruption. Initial cause is most likely a crash or
something.

Is this still reproducible by anyone?

 - Alexander

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in firefox-3.0:
status: Incomplete → Invalid
Revision history for this message
Alexander Sack (asac) wrote :

i would think this is fixed; haven't received any reports for ages.

Changed in firefox-3.0 (Ubuntu Hardy):
status: Confirmed → Invalid
Changed in firefox-3.0 (Ubuntu Intrepid):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.