Yonke imikhiqizo Community Forum

When I go to see a firefox bug such as the following, https://www.mozilla.org/en-US/security/advisories/mfsa2026-10/

There appears to be more details in https://bugzilla.mozilla.org/show_bug.cgi?id=2014390 located at the bottom. When I try to view the details it asks me to log in. I do not see any reason I should have to log in to view the issue as I only intend to view the bug. Why does it require a login ?

Hello Firefox, hello Mozilla, hello community. I have some very important suggestions. Some applications and programs have taken a great path, namely decentralized web technologies. The current internet has become an insecure environment despite all the extreme methods of protecting privacy through the Firefox browser and any other secure technology. I must tell you that keeping up with the times and helping develop the internet and the decentralized Web 3 is undoubtedly the greatest blessing that has come to us, privacy-conscious users and enthusiasts. For example, decentralized domains, decentralized web technologies, and blockchain, which caused a great rift in its early stages, have become almost like the atomic foundation of the current internet. We want decentralized privacy. Firefox and Mozilla, of course, are non-profit companies and organizations. We ask your esteemed team, engineers, and great scientists to help make the Firefox browser keep pace with the developments of decentralization and to help you balance the delicate line between decentralization and centralization of the internet and the World Wide Web. Now there is a rising browser, a brave browser, and this browser is truly bold. With the growth of users who love decentralization, we, as users, feel envious that our beloved browser is not using it. Decentralization means we want to access the web and decentralized networks through the Firefox browser. Thank you. Decentralized internet and privacy are two sides of the same coin.

I have an app on my tablet that requires permissions, but the app doesn't specify which permissions it needs or how to set those permissions. How do I find what permissions the app needs and how do I set them?

Thanks.

Host OS Failure Subject: App Freeze/Crash on Log Export – System Logcat Daemon Failure (MT6765 Platform) Device Info: MediaTek MT6765 | Android 13+ (Based on OnBackInvokedCallback logs) Package: net.thunderbird.android (com.fsck.k9)

Description When attempting to debug synchronization issues in Thunderbird for Android, the application freezes or crashes immediately upon tapping Export logs. Real-time log monitoring reveals that this is not an internal application crash, but a cascading failure triggered when Thunderbird invokes the native Android dumpstate framework on a device with severe system partition corruption. Steps to Reproduce

  1. Navigate to Settings > General settings > Debugging.
  2. Toggle on Enable debug logging and replicate the primary mail issue.
  3. Return to the Debugging menu and tap Export logs.

Expected Behavior The app packages local IMAP/POP3 commands and synchronization records into an exportable text file.

Actual Behavior

The app freezes. The underlying Android logging engine (logd) is completely dead, preventing the file generation tool from completing its routine. Diagnostic Log Excerpts The system-wide dumpstate utility explicitly fails to capture data because the device's logging directories are missing or corrupted:

logcat: Logcat read failure: No such file or directory

command 'logcat -L -b all...' failed: exit code 1

Furthermore, critical Hardware Abstraction Layers (HALs) return null pointers, suffocating UI threads when input fields are called:

Warning: Skipping "android.frameworks.displayservice... (null) 08-04 19:19:37.807 17942 17942 I InputMethodManager: invalidateInput

Developer Note

This issue is entirely environmental and not a flaw in the Thunderbird application codebase. Thunderbird successfully renders its interface (MessageHomeActivity), but when it commands the OS to compile diagnostic logs, the host device's broken firmware crashes the calling process.