Closed Bug 1822842 Opened 1 year ago Closed 1 year ago

Allow to enable and disable Windows-native notification Windows Event Log messages

Categories

(Toolkit Graveyard :: Notifications and Alerts, defect, P3)

Firefox 111
Desktop
Windows

Tracking

(firefox-esr102 unaffected, firefox111 wontfix, firefox112 fixed, firefox113 fixed)

RESOLVED FIXED
113 Branch
Tracking Status
firefox-esr102 --- unaffected
firefox111 --- wontfix
firefox112 --- fixed
firefox113 --- fixed

People

(Reporter: gstoll, Assigned: nrishel)

References

(Regression)

Details

(Keywords: regression)

Attachments

(2 files)

This was reported on Reddit, and I see it on the latest nightly.

I've attached a screenshot, and here are the details from one of the events:

Log Name: Application
Source: Firefox Nightly Notification Server
Date: 3/16/2023 9:00:07 AM
Event ID: 0
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-2J49KLU
Description:
The operation completed successfully.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Firefox Nightly Notification Server" />
<EventID Qualifiers="0">0</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2023-03-16T14:00:07.1472524Z" />
<EventRecordID>36989</EventRecordID>
<Correlation />
<Execution ProcessID="46020" ThreadID="0" />
<Channel>Application</Channel>
<Computer>DESKTOP-2J49KLU</Computer>
<Security />
</System>
<EventData>
<Data>Error: Pipe write succeeded! (HandlePipeMessages:231)</Data>
</EventData>
</Event>

See Also: → 1822817

I should note that the notifications seem to display just fine for me, so that's not a problem.

Yeah, this was oversight on our (the implementors) parts: we dump some debug logging to the Windows Event Log and didn't implement a log level. I'll turn this ticket into that.

Technically, I think this will want to be a per-installation Windows registry entry that sets the log level. The log level should default to only logging errors.

Depends on: 1783051
Keywords: regression
Regressed by: 1781929
Summary: Windows-native notifications cause errors to show up in Windows Event Log → Allow to enable and disable Windows-native notification Windows Event Log messages

Set release status flags based on info from the regressing bug 1781929

:nalexander we only log on notification invocation. A quick and easy way to implement this would be an about:config log level that gets passed along as an argument to the notification.

Assignee: nobody → nrishel
Status: NEW → ASSIGNED
Attachment #9324068 - Attachment description: Bug 1822842 - Trim down notification server event viewer logging unless . r=nalexander → Bug 1822842 - Trim down notification server event viewer logging unless `alerts.useSystemBackend.windows.notificationserver.verbose=true`. r=nalexander

Nick, could you set a severity on this bug? Looks late for 111, what do we want to do with this issue for 112?

Flags: needinfo?(nalexander)

This has minor impact on users aside from mild confusion if checking through the event viewer. Changes are trivial to audit so probably a good beta uplift candidate since we're still making a mess?

Severity: -- → S4
Priority: -- → P3
Pushed by nrishel@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/7544895e82c1
Trim down notification server event viewer logging unless `alerts.useSystemBackend.windows.notificationserver.verbose=true`. r=nalexander
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 113 Branch
Flags: needinfo?(nalexander)

The patch landed in nightly and beta is affected.
:nrishel, is this bug important enough to require an uplift?

  • If yes, please nominate the patch for beta approval.
  • If no, please set status-firefox112 to wontfix.

For more information, please visit auto_nag documentation.

Flags: needinfo?(nrishel)

Comment on attachment 9324068 [details]
Bug 1822842 - Trim down notification server event viewer logging unless alerts.useSystemBackend.windows.notificationserver.verbose=true. r=nalexander

Beta/Release Uplift Approval Request

  • User impact if declined: Noisy false positive errors visible to users in Windows Event Logs.
  • Is this code covered by automated tests?: No
  • Has the fix been verified in Nightly?: Yes
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): Follows existing patterns in code (adding and parsing an argument to flip a a switch), trivial to audit.
  • String changes made/needed:
  • Is Android affected?: No
Flags: needinfo?(nrishel)
Attachment #9324068 - Flags: approval-mozilla-beta?

Comment on attachment 9324068 [details]
Bug 1822842 - Trim down notification server event viewer logging unless alerts.useSystemBackend.windows.notificationserver.verbose=true. r=nalexander

Approved for 112.0b8

Attachment #9324068 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: