Shell good first issues

This issue requires identifying all active uses of the Nextcloud 35 development image within the LibreCode and LibreSign repositories. The goal is to create an inventory of these consumers, noting their status (active, obsolete, etc.) and whether they will require migration to a new generic 'master' image, without making any code changes.

This issue proposes adding an automated container image vulnerability scanning step to the CI pipeline. The goal is to identify security vulnerabilities in the final container image before merging changes, using an open-source scanner compatible with GitHub Actions. The implementation should include clear reporting, a documented failure policy, and local scanning instructions for contributors.

This issue aims to integrate an existing local smoke test into GitHub Actions for pull requests. The goal is to automatically run this test within the CI pipeline to catch regressions in the basic Nextcloud runtime before merging code. The implementation should orchestrate the test by building the necessary environment, executing the local test command, and ensuring proper failure reporting and cleanup.

This issue proposes adding a reusable local smoke test for the current Nextcloud Docker stack. The test should start the existing Docker Compose setup, wait for Nextcloud to be ready, and then verify core functionalities like `occ status` and database/Redis connectivity. The goal is to establish a stable baseline before future architectural changes to the Docker images.

This issue proposes adding a new `AGENTS.md` file to the repository. This file will serve as a concise index of development guidelines for contributors and AI tools, pointing to relevant documentation for specific rules regarding container images, testing, security, and more. The goal is to provide a quick overview of repository standards without duplicating detailed documentation.

Armbian image builds for Ubuntu Resolute on arm64 are failing because the generated `base-files.json` is missing the expected entry for `.resolute.arm64`. This appears to be due to a package metadata retrieval failure during the data branch rebuild on September 11, 2026, causing the Resolute release to be dropped from the JSON.

The `aiDetectType` property on Eufy devices is consistently failing to set via the `eufy_sdk_bridge` addon, reporting a "level-2 key not ready" error after a significant delay. This issue occurs despite other device properties, like `light`, being successfully set on the same devices, suggesting a specific problem with the `aiDetectType` functionality or its underlying key establishment process.

The user is reporting a bug where YouTube videos, when played in fullscreen mode, remain in portrait orientation instead of rotating to landscape. This behavior is inconsistent with other browsers like Brave, suggesting a potential issue with the current browser's handling of fullscreen video rotation.

Users are experiencing significant FPS drops during YouTube playback across various Chromium-based Android browsers and hardware. The issue persists regardless of video codec or device processor, and attempts to fix it with extensions have been unsuccessful. The reporter believes this is a Chromium engine-level problem.

This issue lists several bugs affecting ArtisanROM V3.5.0 across various Samsung models. Key problems include display refresh rate limitations, camera app crashes with specific features, S Pen functionality issues, high brightness mode (HBM) problems in sunlight, and notification/ringtone volume defaulting to maximum.

This issue proposes adding a system to evaluate the reliability of sources used in AI news briefs. It aims to assign a score to each source based on factors like domain, recency, and corroboration, and to detect and highlight conflicting information between sources. The goal is to increase trust and decision-readiness of the generated briefs by providing confidence signals and explicit conflict reporting.

The Luckfox Nova board is experiencing a boot loop due to a change in U-Boot's handling of device tree tags. Specifically, the `u-boot,dm-pre-reloc` tag on the `&uart4` node was removed in U-Boot v2026.01, causing the serial driver to be stripped from the SPL device tree. This prevents the board from initializing serial output and leads to a reset loop.

This issue is a request to update the MuseScore application icon to match the new design introduced in version 4.5. The user notes changes in the background color, gradient, and stroke thickness of the letter within the icon.

This issue reports a compilation failure during the build of Firefox 155.0.1 from the Miezhiko repository. The failure occurs specifically within the `TestArguments WriteArgument` test, indicated by an `Error 1` from `gmake` during the `xpcom/tests/misc` stage.

This is a feature request to add support for the LXQT desktop environment when building operating system images. The user has provided a command-line example demonstrating their attempt to build an image with LXQT, indicating a desire for this functionality to be officially supported.

This feature request proposes adding a dynamic badge to the Longhorn browser icon (favicon) to visually indicate the cluster's health status. The badge would change color (e.g., green for OK, yellow for degraded) to help users monitor their Longhorn cluster state without actively looking at the dashboard tab, especially during upgrades.

This issue is a task to add symlinks and icons for various Flathub applications. The list includes several applications that still need this functionality implemented, with one application already marked as complete. It appears to be a recurring task to ensure all Flathub apps have proper desktop integration.

The user is reporting that the kernel parameter `xe.enable_psr=0` is no longer necessary for a display fix on their Asus Expertbook running a 7.1.6-1 kernel with OpenSUSE Tumbleweed. They are suggesting this parameter might be redundant and can be removed.

This issue describes a recurring installation failure on Debian where the system cannot create a symbolic link for `libstdc++.so.6`. The problem appears to stem from a specific code block in the installation script, potentially outdated. The maintainer lacks the resources to test a fix and is requesting community assistance to comment out the suspect code and test on a fresh Debian installation.

The `claimable_balances_current` BigQuery table is currently disabled due to performance issues, requiring excessive slot reservations. The goal is to optimize this table's query to complete within 5-15 minutes, similar to other `*_current` tables, without increasing slot reservations. Potential solutions include adding clustering to the dbt model, analyzing the query with BQ EXPLAIN for optimization opportunities, and potentially adding a `farmfingerprint` field or making claimants JSON.

This issue proposes to move the `network_stats_agg` dbt model from an internal repository to a public one. The goal is to make this model, which provides general Stellar network statistics, accessible alongside other public network aggregates. This involves porting the SQL and YAML files, updating the schema, and carrying over existing tests and documentation.

The `arch-update` tool incorrectly lists ignored AUR packages as pending updates when using non-English locales. This is because the tool relies on a hardcoded English string `[ignored]` to filter these packages, but AUR helpers like `paru` translate this marker in localized environments. The issue also notes that repository ignores are silently hidden without any indication.

This issue proposes adding an environment variable for `auth_property_name` within the Azure AD (Entra) authentication configuration. Currently, this value is hardcoded to 'userPrincipalName' and could be made configurable via an environment variable for greater flexibility.

This feature request proposes adapting the `misp-docker` project to support running MISP in Kubernetes environments. The core idea is to maintain a single Docker image that works seamlessly for both standard Docker deployments and Kubernetes, specifically addressing non-root user execution and read-only root filesystem requirements.

This is a request to add the Nextcloud Talk desktop client to deb-get. The user has confirmed it's a new request and provided the GitHub release and website URLs. The app is described as a desktop client based on the Nextcloud Talk web application.

This issue highlights a gap in the documentation for `RTE.editor` within Page TSconfig. The current documentation incorrectly states that arrays are overridden, while the underlying code uses `ArrayUtility::mergeRecursiveWithOverrule()`, which merges arrays recursively. This discrepancy needs clarification from TYPO3 Core developers to accurately document how `RTE.editor` configurations, particularly array-based ones like `contentsCss`, are handled.

This issue appears to be a request for information or support related to a specific device (Realme 9 Pro 5G, codename 'oscar') running LineageOS version 23.2 on Android 16. The user has provided kernel source details, suggesting they might be looking for help with kernel-related aspects or device compatibility.

A bug in Longhorn v1.12.0 causes cloned volumes to get stuck in a 'not ready for workloads' state after the cloning process completes. This prevents consumer pods from attaching to the volume, requiring manual deletion of the clone PVC to resolve the issue. The problem appears to be related to the volume's readiness for attachment after the clone operation, even though the data copy is successful.

This issue highlights two documentation discrepancies regarding user-level subagents located in `~/.claude/agents/`. The README's asset table omits any mention of these agents, leaving users unsure of their migration status. Additionally, the MIGRATION.md file incorrectly states that the `~/.claude/agents/` directory does not exist, contradicting its actual presence and functionality.

The `--include-repos` flag in the `agy` tool incorrectly proposes creating symlinks for `AGENTS.md` within language package caches when the user's home directory (`~`) is recorded as a project root. This happens because the tool scans all recorded directories, including the home directory, and then recursively searches for potential symlink locations within package caches that reside under `~`.