firefox grey

[rrichter]

Binary package hint: firefox

firefox crashed any day. unstable?!

ProblemType: Bug
Architecture: i386
Date: Mon Jan 21 12:47:29 2008
DistroRelease: Ubuntu 7.10
NonfreeKernelModules: nvidia
Package: firefox 2.0.0.11+2nobinonly-0ubuntu0.7.10
PackageArchitecture: i386
SourcePackage: firefox
Uname: Linux ich-desktop 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux

[wolfger (wolfger)]

This bug was incorrectly set to "incomplete". Setting it back to "new". "Incomplete" status guidelines are:
# If you have to ask the reporter questions, set the bug to Incomplete
# Ask the submitter to provide any necessary information in a comment, and make sure you subscribe yourself to the bug report so you will get any updates to the bug via e-mail.
# In the event that a bug has been in the "Incomplete" state for more than 4 weeks, meaning it has not received a response to a request for more information, the bug status should be changed to "Invalid"

[John Vivirito (gnomefreak)]

Wolfger, please dont change status of Mozilla bugs without reading our guides. https://wiki.ubuntu.com/MozillaTeam/Bugs/States?highlight=(mozilla)
This wiki will be updated when i get time some of the tags are not used and wont be used but since UDS is going on it will wait until i get time to update it.
Thanks your helping
We do things to help us with our bug load plus everything else that the 3-6 of us do on a daily basis.

Michter,
Can you please obtaina backtrace by folloowing the directions at: https://wiki.ubuntu.com/MozillaTeam/Bugs

[wolfger (wolfger)]

John, I think we already had this conversation. Again, the link you provide me with indicates that a Mozilla bug with an incomplete status *MUST* additionally have one of a number of tags, none of which have been applied to this bug report. I am perfectly willing to play by the rules, but the Mozilla team should be following their own procedure.

Activities/Tags
(See MozillaTeam/Bugs/Tags for a detailed description on tags, their meaning as well as typical actions associated with them)
    * <none> - this is illegal, aka a triage bug: state need info always needs one of the tags below. If there is a bug that does not fit, talk to us in order to find a new one.
    * For Crashers:
          o mt-needreport - a useful crash report from the user is needed.
          o mt-needretrace - someone to do a retrace of the crash report submitted in the bug is needed.
    * For Feature Bugs:
          o mt-needtestcase - a step by step description on how to reproduce the problem is needed.
          o mt-needtester - a tester is needed which can provide responsive feedback at best in the IRC channel.
    * All Bugs:
          o likely-dup - bugs that are duplicates, but triager does not have bug number of MASTER bug at hand, can be tagged 'likely-dup'. Other triagers can then pick them, find MASTER bug and mark them appropriately.
          o mt-needsummary - someone needed to clean up the issue summary before proceeding.
          o mt-confirm - this bug looks ready for "Confirmed". Someone with experience is needed review and transition it to "Confirmed" if this report is fine.

[John Vivirito (gnomefreak)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

wolfger wrote:
| John, I think we already had this conversation. Again, the link you
| provide me with indicates that a Mozilla bug with an incomplete status
| *MUST* additionally have one of a number of tags, none of which have
| been applied to this bug report. I am perfectly willing to play by the
| rules, but the Mozilla team should be following their own procedure.
|
| Activities/Tags
| (See MozillaTeam/Bugs/Tags for a detailed description on tags, their
meaning as well as typical actions associated with them)
| * <none> - this is illegal, aka a triage bug: state need info
always needs one of the tags below. If there is a bug that does not fit,
talk to us in order to find a new one.
| * For Crashers:
| o mt-needreport - a useful crash report from the
user is needed.
| o mt-needretrace - someone to do a retrace of the
crash report submitted in the bug is needed.
| * For Feature Bugs:
| o mt-needtestcase - a step by step description on
how to reproduce the problem is needed.
| o mt-needtester - a tester is needed which can
provide responsive feedback at best in the IRC channel.
| * All Bugs:
| o likely-dup - bugs that are duplicates, but
triager does not have bug number of MASTER bug at hand, can be tagged
'likely-dup'. Other triagers can then pick them, find MASTER bug and
mark them appropriately.
| o mt-needsummary - someone needed to clean up the
issue summary before proceeding.
| o mt-confirm - this bug looks ready for
"Confirmed". Someone with experience is needed review and transition it
to "Confirmed" if this report is fine.
|

I fixed it for the moment sometime earlier this morning. It was outdated
as i have said over and over but the idea was to be taken not the exact
wording of it. Now its in a state where it can wait until i get to finda
~ date for our meeting.
- --
Sincerely Yours,
~ John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIMYxgqig4QTwcPCoRAhe6AJ0ViZDiHO2EuOvsbOBdWtoq3sMbxACeOX9+
ydZBUWeDfN0wJp3Zk3wGHVw=
=8fqC
-----END PGP SIGNATURE-----

[John Vivirito (gnomefreak)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

wolfger wrote:
| John, I think we already had this conversation. Again, the link you
| provide me with indicates that a Mozilla bug with an incomplete status
| *MUST* additionally have one of a number of tags, none of which have
| been applied to this bug report. I am perfectly willing to play by the
| rules, but the Mozilla team should be following their own procedure.
|
| Activities/Tags
| (See MozillaTeam/Bugs/Tags for a detailed description on tags, their
meaning as well as typical actions associated with them)
| * <none> - this is illegal, aka a triage bug: state need info
always needs one of the tags below. If there is a bug that does not fit,
talk to us in order to find a new one.
| * For Crashers:
| o mt-needreport - a useful crash report from the
user is needed.
| o mt-needretrace - someone to do a retrace of the
crash report submitted in the bug is needed.
| * For Feature Bugs:
| o mt-needtestcase - a step by step description on
how to reproduce the problem is needed.
| o mt-needtester - a tester is needed which can
provide responsive feedback at best in the IRC channel.
| * All Bugs:
| o likely-dup - bugs that are duplicates, but
triager does not have bug number of MASTER bug at hand, can be tagged
'likely-dup'. Other triagers can then pick them, find MASTER bug and
mark them appropriately.
| o mt-needsummary - someone needed to clean up the
issue summary before proceeding.
| o mt-confirm - this bug looks ready for
"Confirmed". Someone with experience is needed review and transition it
to "Confirmed" if this report is fine.
|
~ Im sorry if ive been a bit busy to update wikis, we once had a few
people do that so me and asacv could work on other things but when i
returned home after leave i found a few people gone so ive been playing
catch up on bugs wikis and packages. I thank you for your help and
pointing out the wiki was wrong if you relized it or not. Me and
Alexander talked about tags and there are some we are removing and maybe
adding so the tags are a bit outdated. I added this to the wiki finally.
Im the only one from Mozilla team that is doing our main wikis plus what
i normally do so please be patient if its not up to date but i tried to
explain this but i guess it came out wrong.

- --
Sincerely Yours,
~ John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIMY+2qig4QTwcPCoRAub5AJ9Naq53Ia9ygaHmeWOLQ/xq1x5aQgCfYchq
Dwvrm9NxmEOTg03dUHy2k3s=
=ulFy
-----END PGP SIGNATURE-----

[Jayson Rowe (jayson.rowe)]

Since it's been a very long time since any additional info was added to this bug, I'm just checking to see if this is still an issue, and find out what additional work should be done on this bug.

[John Vivirito (gnomefreak)]

no response since November closing bug report.