Fills .xsession-errors with "Warning: more than one line!" spew

Bug #181716 reported by era
2
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: firefox

I discovered a large number of these error messages in my .xsession-errors. Hunting through Google hits for this error message was initially inconclusive, but I think I finally found the culprit.
http://www.google.com/codesearch?q=%22Warning%3A+more+than+one+line%21%22&hl=en&btnG=Search+Code

I have the "Popup ALT Attribute" extension and previously, that has been preventing these messages (I think) but now that I upgraded to Gutsy, they are back.

At a minimum, it would be useful if these messages could indicate which application they come from; but if they are important, perhaps .xsession-errors is not the right place for them, and if they are unimportant, maybe they should simply be suppressed. (Personally, I would favor the latter, or perhaps they could end up in Firefox's error console.)

If they have to be printed, standard error would seem marginally more correct than standard output. If the application name cannot reliably be discovered, then surely at least the process ID could be added to the message.

See also bug #162976

Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 181716] Fills .xsession-errors with "Warning: more than one line!" spew

On Thu, Jan 10, 2008 at 09:01:56AM -0000, era wrote:
> Public bug reported:
>
> Binary package hint: firefox
>
> I discovered a large number of these error messages in my .xsession-errors. Hunting through Google hits for this error message was initially inconclusive, but I think I finally found the culprit.
> http://www.google.com/codesearch?q=%22Warning%3A+more+than+one+line%21%22&hl=en&btnG=Search+Code
>

doesn't sound like a firefox bug.

 status incomplete

 - Alexander

Changed in firefox:
status: New → Incomplete
Revision history for this message
era (era) wrote :

I am fairly sure this is a Firefox bug, because I have added comments to the upstream bug long, long ago. At least, it used to be the case that tooltips with line breaks in them would cause this behavior.

I went off to look for the upstream bug to add that information here, but couldn't find it; the search facility at bugzillla.mozilla.org is increasingly inadequate (I get "truncated at 200 bugs" for basically all my searches, unless it's "zarro boogs found").

I am also unable to (easily) repro this. E.g. http://modp.com/wiki/htmltitletooltips should have all the complicated variations, but none of them cause this message to be emitted. Maybe I have some extension here at home which prevents it. I'll have another look from my work computer again tomorrow.

Revision history for this message
era (era) wrote :

Actually the comment I distinctly remember submitting somewhere is right here: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/19250/comments/2

Like I wrote above, I'll still need to see which site still triggered this warning.

Revision history for this message
era (era) wrote :

Another reason I know this is Firefox: because of problems such as this, I have a wrapper which diverts its standard output and standard error to different files, so in my case, it's not actually polluting my .xsession-errors, just everybody else's.

I have some 200 tabs open and I'm not sure I haven't navigated away from the page which triggered this, so I may not be able to provide instructions for how to repro this.

Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 181716] Re: Fills .xsession-errors with "Warning: more than one line!" spew

On Fri, Jan 11, 2008 at 09:28:12PM -0000, era wrote:
> Another reason I know this is Firefox: because of problems such as this,
> I have a wrapper which diverts its standard output and standard error to
> different files, so in my case, it's not actually polluting my
> .xsession-errors, just everybody else's.
>
> I have some 200 tabs open and I'm not sure I haven't navigated away from
> the page which triggered this, so I may not be able to provide
> instructions for how to repro this.
>

OK, reopen or open a new bug through Firefox->Help->Report a Problem
if you can reproduce.

 status invalid

Thanks,

 - Alexander

Changed in firefox:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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