bug
305 TopicsEdge 144 Creates Multiple GNOME Menu Icons
Starting in Edge 144, there are now 2 icons displaying in the GNOME applications menu. com.microsoft.Edge.desktop microsoft-edge.desktop Both of these files are installed as part of the RPM; the first has "NoDisplay=true" at the bottom, but that doesn't seem to work as intended. I think this value needs to be in the first section, under "[Desktop Entry]", in order for it to work properly.46Views1like1CommentOffice v2508 feature update (new vbe7.dll) breaks library compatibility with LTSC VL versions
Since the Jan 2026 updates, some `accde` or `mde` libraries built with the semi-annual enterprise channel (v2508, Build 19127.20484) can no longer be used with the volume-licensed version of Office LTSC (tested with the Jan 2026 release of Office 2024 LTSC VL, v2408, Build 17932.20638). The reason for this seems obvious: The v2508 feature update contains an updated vbe7.dll. Apparently, this change is backwards-compatible (code compiled with the old dll will run with the new dll) but not completely forwards-compatible (code compiled with the new dll might not run with the old dll, even if the new RegExp class is not used). That's a problem for us. We can't just tell our customers to upgrade, because those with an Office 2024 LTSC volume license already use the latest version available to them. Does Microsoft consider this a bug or "by design"? If the latter, what is Microsoft's recommendation for software vendors who want to build software that runs on all currently-supported versions of Access? We currently plan to work around this issue by installing v2502 of the semi-annual enterprise channel on our "build VMs" (32 and 64 bit) and use those to build our software. (Reverting dev machines to an old Office version is not an option for obvious security reasons.) Repro On a PC with v2508 or newer: 1. Create a new mylibrary.accdb with a module with the following code: Public Function GetColorCode() As Long GetColorCode = vbRed End Function 2. File/Save as/Create accde. 3. Copy mylibrary.accde to a PC with v2507 or older (for example, with the current version of Office 2024 LTSC volume license). On a PC with v2507 or older: 4. Create a new database. 5. Create/Module/Tools/References 6. Add a reference to mylibrary.accde 7. Add the following code to the module: Sub Test() Debug.Print GetColorCode() End Sub 8. Debug/Compile Expected result: The database compiles. Actual result: "Compile error: Can't find project or library". The "references" window opens automatically and highlights "mylibrary". Notes We are not library developers, but we are still impacted by this issue, since the software we ship consists of a (modifiable) startup mdb referencing an (unmodifiable) mde containing the business logic. If you want to try to reproduce this issue but don't have a volume license of Office 2024 LTSC lying around (we certainly don't), you can install a trial version with the Office Deployment Tool and the following configuration file: <Configuration> <Add OfficeClientEdition="64" Channel="PerpetualVL2024"> <Product ID="ProPlus2024Volume"> <Language ID="en-us" /> </Product> </Add> </Configuration>173Views0likes5CommentsThe return of the performance leak - this time with subreports
Anyone remember the v2405 bug that caused loading and closing forms to become slower over time? We found something similar in the current release (tested with semi-annual 2508 (19127.20484)), just with sub reports instead of forms. Here are the repro instructions: Repro instructions Table 1. Create a "numbers" table with a PK field "nr" (Long Integer). 2. Fill it with the numbers from 1 to 100: Dim i For i = 1 To 100 CurrentDb.Execute "INSERT INTO numbers (nr) VALUES (" & i & ")" Next i Sub report 3. Create a new empty report in design view, using the "numbers" table as the record source. 4. In the detail section, add two text boxes "Text1" and "Text2" next to each other, both with the "nr" field as their control source. 5. Reduce the size of the detail section to one "row", containing just the two text boxes. Remove the page header/footer. 6. Add an Format event handler to the detail section with the following content: Me.Text2.Visible = False 7. Save the report as "sub". Main report 8. Create another report "main", which contains nothing but the "sub" report as a subreport in its detail section. Set the record source of "main" to "SELECT * FROM numbers WHERE nr <= 10" Reproduce problem 9. Create the following method in a module: Sub report_loop() Dim i As Long Dim start_time As Single Dim report_name As String Dim path As String report_name = "main" For i = 1 To 40 path = Environ("Temp") & "\testreport.pdf" start_time = Timer DoCmd.OpenReport report_name, acViewPreview DoCmd.OutputTo acOutputReport, report_name, acFormatPDF, path DoCmd.Close acReport, report_name Debug.Print Timer - start_time Next End Sub 10. Run report_loop. Observe that each report export gets slower and slower. Analysis Compare the first and last number in the immediate window: on my machine it's 0.4s for the first report and 2.3s for the last. Note that if you run report_loop again, it will start slow! In other words, each report export causes MS Access to "leak performance" that is only regained after restarting Access. We were able to reproduce this issue with Microsoft 365 semi-annual channel, Version 2508 (19127.20484). I'll do more tests tomorrow and try different older versions to find out when this bug was introduced. Workarounds If you move the visibility code from the Format event to the Print event, the problem still occurs, but slower (0.4s -> 0.72s instead of 0.4s -> 2.3s). The workaround that worked for us was to use =IIf(...) in the control source instead of modifying the visibility. Obviously, that only works for text boxes, not for lines or other controls.149Views1like6CommentsiPhone Edge 144 "Send to devices" - "No Device found"
About a week ago, when Edge was on version 143, everything worked as expected. After updating to version 144, the “Send to devices” feature no longer detects any Windows computers on the same network. No settings were changed on my end — the only change was updating Edge to the latest version on both iPhone and Windows. Any ideas?279Views5likes2Comments[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!1.6KViews10likes17CommentsLatest Stable Linux build of Edge crashes when I download something.
When I download something from the internet and When I click save as the browser crashes, using RPM linux build on Fedora and using the latest stable version at the time of writing this discussion version Version 143.0.3650.139 (Official build) (64-bit)81Views0likes0CommentsNew Outlook: Shadow contacts not stored in Outlook.com, no sync/export and missing Birthday calendar
I’m reporting a reproducible data‑integrity issue in the New Outlook for Windows that affects Outlook.com contact storage and synchronization. 🔍 Summary When a contact is created in the New Outlook, the client appears to save it successfully. However, the resulting contact is not stored in the user’s Outlook.com account as a normal cloud contact. Instead, it becomes what I would describe as a local “shadow contact” in the New Outlook cache. ⚠️ Observable Behavior • The contact appears in Outlook.com → People, but does not show “Stored in: Outlook” • The contact does not appear in Outlook.com CSV exports • The contact does not sync to mobile devices connected to the same account • The contact does not populate the Outlook.com Birthday calendar • The contact is lost if the New Outlook app is reinstalled or its local store is cleared 🧪 Steps to Reproduce 1. Open the New Outlook for Windows 2. Create a new contact and add a birthday 3. Save the contact 4. Open Outlook.com → People 5. Locate the contact — it will appear, but the “Stored in: Outlook” field is missing 6. Export contacts from Outlook.com (CSV) — the contact will not be present 7. Check a mobile device configured with the same Microsoft account — the contact will not be present 8. Check the Outlook.com Birthday calendar — the birthday will not appear 9. Reinstall the New Outlook app — the contact will be gone ✅ Expected Behavior • Contacts created in the New Outlook should be stored as first‑class Outlook.com contacts • They should appear with a proper “Stored in: Outlook” location • They should sync across devices, export via Outlook.com, and populate the Birthday calendar ❌ Actual Behavior • Contacts created in the New Outlook are effectively “shadow contacts” stored in a local cache • They look normal in the New Outlook UI, but they are incomplete, non‑synchronizing objects from the service’s perspective 📉 Impact • Silent data loss risk for users who assume contacts are in Outlook.com when they are not • Inconsistent contact and birthday data across devices and services • Split contact store model: • Real Outlook.com contacts • Local shadow contacts created by New Outlook 📎 What I’ve Already Done • Submitted feedback through the New Outlook (Help → Feedback → Report a Problem) • Submitted a detailed report via the Windows Feedback Hub • Contacted Microsoft Support, who advised that escalation must occur via Feedback 📣 Request I’m posting this here to document the issue publicly and to ask: • Can anyone from the Outlook / Exchange / Outlook.com team confirm this behavior? • Can other users reproduce this with the steps above? Given the data‑integrity implications, I’m hoping this can be brought to the attention of the relevant engineering team. Any confirmation, additional data points, or official guidance would be appreciated.107Views0likes1CommentMicrosft teams wont minimize on endevourOS (arch based)
Not sure if this is the correct place to put this since its my first time using this site but here we go Teams wont minimze when minize is pressed. Ive installed the Gnome look and added minimize, resize and close buttons to the install via cli Ive disabled boot on startup and keep running when closed if that matters11Views0likes0CommentsNew Outlook Randomly Assigning/Overriding Categories to Calendar Items
I use Categories to color code and organize my calendar. In the New Outlook, the system is randomly assigning categories to some of my calendar items. For example, I have one item that has no category assigned, but now it uses my "Misc Meeting" category. Another one I'd already labeled with the "Analyst Team" category and now it's added "Phone Call" to the item (which is making the wrong color display). In both of these examples, if I right click to access the categories and correct them (or even just "Clear all categories"), once I submit, after a few seconds the incorrect category labels and colors come back. Help?209Views0likes1Comment