Solution for PWAs not appearing as separate apps on Linux taskbars
Hi everyone, I recently Installed Microsoft Edge stable on Kubuntu Linux, and I ran into some problems using Progressive Web Applications (PWAs). Launch one Edge PWA (say, Microsoft Teams). It appears normally. Launch a second PWA (say, Microsoft Outlook). Both windows — and every PWA you launch afterward — collapse into a single taskbar group under the first PWA’s icon, identified as msedge. Pinned PWA launchers never show as running. Pinning a running PWA window produces a generic page icon that launches the bare Edge browser when clicked. Launching a PWA from the application menu briefly shows the launcher’s startup placeholder in the taskbar, which then disappears and is replaced by a separate, unassociated entry. This isn’t KDE-specific. GNOME users have also reported issues. After some troubleshooting with Claude, the issues were traced to a mismatch between how the PWAs are identified in the .desktop PWA launchers created by Edge and the app ids reported to Wayland, starting in September 2025, when Wayland was used by default. Identifier Value Example (Microsoft Outlook) Window app_id (native Wayland) msedge-_<appid>-Default msedge-_lkkahpbimdkjdjjiijflmhaeameegbcm-Default Desktop entry filename msedge-<appid>-Default msedge-lkkahpbimdkjdjjiijflmhaeameegbcm-Default StartupWMClass= in that file crx__<appid> crx__lkkahpbimdkjdjjiijflmhaeameegbcm So the solution is StartupWMClass in the .desktop launcher for the PWA to the Wayland app_id. I have a simple Bash script that will do this for all currently installed PWAs as a workaround, but the automod removed that post the last time I tried to post it. The suggested fix for Microsoft This should be a small change to Edge’s desktop-entry generation on Linux: write the Wayland app_id (msedge-_<appid>-<profile>) into StartupWMClass=, or better, make the window app_id match the desktop entry basename per the freedesktop convention. No compositor-side changes are needed — the verified workaround above demonstrates that. I’ve reported this through Edge’s in-browser feedback tool (Alt+Shift+I) with the full diagnosis. If you’re affected, sending your own feedback referencing the same details is the best way to get it prioritized — the in-browser channel is what reaches the Edge team’s triage.
[Wayland] PWAs no longer appear as separate app windows — all group under main Edge icon
Hi, Since around 2025-09-07 to 2025-09-10, I’ve noticed that on GNOME (Wayland) all installed PWAs (even across different profiles) now appear grouped under the main Edge browser icon in the GNOME Shell dash/taskbar. Previously, each PWA would open in its own window group with its own icon. This is still the behavior in Chromium/Brave/Chrome, and can be restored there by editing the PWA’s .desktop file to set: StartupWMClass=<same value as Icon> However, Edge now seems to ignore StartupWMClass completely on Wayland, breaking workspace separation and making task switching hard. Environment: Ubuntu 25.04 GNOME 48.0 / Mutter (Wayland) Kernel 6.14.0-29 Intel Iris Xe GPU Edge (latest stable, observed post 2025-09-13) Repro steps: Install any PWA (e.g. Outlook, Teams, Spotify) from Edge Launch it (from any profile) Observe that it appears grouped under the main Edge browser icon Expected: PWA shows under its own icon and window group like in Chromium-based browsers Actual: All PWAs are bundled into the main Edge window group Editing StartupWMClass in the .desktop file no longer helps This regression makes PWAs much harder to manage on Wayland. Please route to the Linux/Wayland team if possible. Thanks!PWA shortcuts don't keep asociated with window - Linux
I recently upgraded to version140.0.3485.14 (Official build) beta (64-bit) and noticed that my PWA, even if they open correctly in a independent window, don't show the "running window counter" on the taskbar. So, for example, if a open Outlook, the window open and loads the app, but if a I click the icon again, it opens another window, wich is a little annoying. I tried removing the PWA from Edge, rebooting, and installing again, but didn't work. Because the only change I made is updating Edge, I think is related to this build. (too lazy to go back or install the stable release)
MS Edge - Sidebar and copilot not working on Linux Ubuntu v24 LTS
Sidebar not syncing or accepting new app additions (+). Copilot button is dead/inactive. Sidebar settings are well configured. Using the latest version of the Ubuntu OS and MS Edge. Functionality appears to be absent as product was released without full functionality....Lame!
Edge Linux: Collections and Workspaces
Hey y'all, I use Edge Dev on both Linux (at home) and Windows (at work). I started using Collections recently, and I was upset to find it doesn't work on Edge Linux (yes, my packages are up to date). Although I haven't tried Workspaces yet, it's not working either on Linux. Even if you enable it, it doesn't show up. I can see that the tab expands, but the button doesn't appear. With Collections, enabling has no effect at all. Is this a known bug, or it just doesn't work on Edge Linux yet? Ubuntu 22.04.2 LTS x86_64. Version 115.0.1851.0 (Official build) dev (64-bit).Using FIDO2 with NFC Smartcards in Edge on Debian (this is a Linux distribution)
Some administrators prefer using Linux, Debian in this case. They are required to perform certain tasks on Microsoft's admin portals for Azure and M365, where 2FA is strictly enforced without exceptions. I experimented a bit but couldn't get it to work in Edge on Debian - the option to choose FIDO2 doesn't even appear. In Firefox on Debian, at least the option to choose FIDO2 is available in the login dialog. I'm using other apps on the same machine with NFC smart cards - everything works, but not Edge and Microsoft Entra. I found an article including compatibility tables for FIDO2 authentication with Microsoft Entra ID - Support for FIDO2 authentication with Microsoft Entra ID - Microsoft Entra ID | Microsoft Learn. Does anyone have an idea why Entra is generally only supported in Chrome on Linux and not in Edge? Any insights on NFC support for FIDO on Linux, feature timeline?
Microsoft Edge Dev crashes on a regular basis unless I'm running it from the Linux terminal
(Reposted from Microsoft Answers Community: https://answers.microsoft.com/en-us/microsoftedge/forum/msedge_crash-msedge_prevwin/microsoft-edge-dev-crashes-on-a-regular-basis/6f26ec72-32e0-4323-a294-0dcad6260a07) This started happening yesterday, and even after downgrading 2 versions back, then upgrading again, the issue won't go away. Here's what's going on: When I start Microsoft Edge Dev normally, through a shortcut on Linux, the browser opens fine, and will usually crash ~10 minutes later, or sometimes a few minutes later. But, when I start it from the terminal, it runs pretty fine, with very few crashes. Here's the output log: $ microsoft-edge-dev libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) [8447:8447:0123/133205.683161:ERROR:assistance_home_client.cc(32)] File path /home/user/.config/microsoft-edge-dev/Default MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to open nvidia-drm: /usr/lib/dri/nvidia-drm_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) failed to load driver: nvidia-drm MESA-LOADER: failed to open zink: /usr/lib/dri/zink_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) failed to load driver: zink MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) failed to load driver: kms_swrast MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) failed to load swrast driver [8447:8447:0123/133209.219594:ERROR:smartscreen_dns_resolver.cc(110)] SmartScreenDnsResolver::OnComplete Error: -7 DidTimeOut: 1 URL: https://ntp.msn.com/edge/ntp?locale=en-US&title=New%20tab&dsp=0&sp=DuckDuckGo&startpage=1&PC=U531 [8447:8447:0123/133213.657014:ERROR:object_proxy.cc(622)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented Warning: disabling flag --expose_wasm due to conflicting flags (note here: the expose_wasm warning keeps reappearing multiple times during the time the browser is open) [8447:8447:0123/133930.176470:ERROR:interface_endpoint_client.cc(695)] Message 0 rejected by interface blink.mojom.WidgetHost [27075:1:0123/150305.181159:ERROR:picture_in_picture_overlay_agent.cc(49)] Connection to PIPOverlayDriver dropped [8492:8518:0123/150655.507233:ERROR:x11_software_bitmap_presenter.cc(142)] XGetWindowAttributes failed for window 10485928 [8447:8447:0123/161844.895173:ERROR:smartscreen_dns_resolver.cc(110)] SmartScreenDnsResolver::OnComplete Error: -7 DidTimeOut: 1 URL: https://kerstinmartin.com/blog/copyright-notice [8492:8492:0123/172329.479822:ERROR:shared_image_manager.cc(197)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox. (ultimately, these two lines to appear before a crash) [0123/203750.329461:ERROR:elf_dynamic_array_reader.h(64)] tag not found Segmentation fault My computer: i7-2600 3.40Ghz 8GB DDR3 GTX 1650 4GB DDR5 1TB HDD + 500GB HDD Ubuntu 22.04.1 LTS, Kernel Linux 5.15.0-58-generic x86_64 Wayland, latest NVIDIA 525 proprietary drivers I think this has something to do with the MESA drivers not being able to open nvidia_drm, zink, kms_swrast, swrast, and some issues with libva, but I'm not 100% sure. I have submitted 1 crash report yesterday, but until this might be fixed, what can I do?
