New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Windows 10] No notifications in "Notifications Center" #1777

Closed
JoelTroch opened this Issue Aug 4, 2015 · 11 comments

Comments

Projects
None yet
6 participants
@JoelTroch
Copy link
Contributor

JoelTroch commented Aug 4, 2015

OS: Windows 10 Pro x64 (final release with all the updates).
Mumble version: Snapshot 1.3.0704g6fe5547.

When there is an "event" in Mumble (someone connecting, someone being kicked, someone joining your channel...), there will be no notifications in the "Notifications Center" even if in Mumble's settings they are set to display them.

I didn't had that issue with "Technical Preview"/"Insider Preview" versions of Windows 10.

Things I tried and it didn't worked:

  • Add a registry key in HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Notifications\Current\Microsoft.Explorer.Notification.{6FECDCF1-3D54-462A-AE56-6698CA5A0733} ({6FECDCF1-3D54-462A-AE56-6698CA5A0733} being Mumble's GUID) and reboot.
  • Run as administrator.

Something worth a note: if you open Windows 10's "Parameters" app, go to the "System" category and the "Notifications and actions" sub-category, Mumble is not present in that list (see the following screenshot):
mumble

UPDATE: The following are random thoughts that need to be investigated and may be wrong:

  • Qt's support for Windows 10 isn't complete yet so Mumble isn't the only application affected?
  • An upgrade to Windows 10 SDK and/or Visual Studio 2015 is (are) required?
  • Manifest need tweaking?
@falkreon

This comment has been minimized.

Copy link

falkreon commented Aug 4, 2015

Can confirm in Windows 10 Home x64 and Mumble 1.2.10, just to expand the net a bit. I can't find any issues in the Qt project tracker, but it's still pretty early, they might not have caught it yet.

@mkrautz

This comment has been minimized.

Copy link
Member

mkrautz commented Aug 6, 2015

We use Win32 notifications. Maybe that's it? Only modern-style notifications work?

It worked in TP though?

@JoelTroch

This comment has been minimized.

Copy link
Contributor

JoelTroch commented Aug 6, 2015

@mkrautz It worked in TP. I don't think it's related to Win32 notifications because the "Qt system tray" example in Qt 5.5.0 works fine.
mumble
Funny thing is that "systray.exe" (the Qt example below) was automatically added to the "allowed applications to display notifications", so I suspect it's because Mumble is NOT on that list that notifications aren't displayed. Theorically, we find the way to add Mumble to that list, notifications should work again.

@mkrautz

This comment has been minimized.

Copy link
Member

mkrautz commented Aug 6, 2015

We patch Qt to disable queueing of notifications behind fullscreen windows... Mayer that's to blame...

@mkrautz

This comment has been minimized.

Copy link
Member

mkrautz commented Aug 6, 2015

I'd guess that's probably it, actually...

Since it's realtime, it make sense not to show it in the notification center...

@nschechter

This comment has been minimized.

Copy link

nschechter commented Aug 29, 2015

Hey guys, I got the newest snapshot of mumble (1.3.0.713) and it still doesn't show up in the notifications center. Any other possibilities?

@JoelTroch

This comment has been minimized.

Copy link
Contributor

JoelTroch commented Oct 10, 2015

I think upgrading Mumble to Qt 5.5 will fix this issue, Mumble is actually using Qt 5.4.2 (which is released a month before Win10 was released to the public).

But I think that upgrading Qt results in more bugs to fix?

@Flyflo

This comment has been minimized.

Copy link

Flyflo commented Nov 15, 2015

FYI the Windows 10 Fall Update fixed the problem for me.

@mkrautz

This comment has been minimized.

Copy link
Member

mkrautz commented Nov 15, 2015

That was also the response we got from people when this first showed up. Insider builds were not affected.

If this is still a problem for some, please re-open!

@mkrautz mkrautz closed this Nov 15, 2015

@CWTagpro

This comment has been minimized.

Copy link

CWTagpro commented Nov 16, 2015

Oh awesome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment