Bug:Incompatible With Wps

Abierto
  • ¿Algo no está bien?
#514 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
22/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
javascript, linux
Área
desktop-dev

Línea de trabajo

The report names two Forge behaviours: WPS dropdowns and Zotero notification popups get tiled, and the default Super+L move shortcut clashes with the lock screen. The journal trace points into GNOME Shell's messageTray.js, not Forge code, so first check how Forge decides which new windows to tile and where its keybindings are registered. Done would mean a reproducible exception rule and a non-conflicting default shortcut, confirmed on a nested GNOME session. The issue has had no comments in 217 days and no maintainer is active, so expect little review.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug
Issue/Bug Description/Video Capture/Screenshots

I am a beginner using BazziteOS, mainly working on writing papers with WPS and Zotero, and doing some programming with VS Code.

The dropdown menus in WPS and the notification popups in Zotero trigger tiling, causing them to expand into large tiled windows. I have to manually add these applications to a floating whitelist using the shortcut Super + Shift + C.
The default window movement shortcut Super + L conflicts with the system shortcut, which causes the lock screen in BazziteOS to stop working.

Maybe above things can be improved.I spent a lot of time figuring out that the root cause of these annoying issues was Forge.

Chinese version For Chinese users how to fix locally:
我是个用BazziteOS的新手，主要是在用WPS和Zotero写论文和做一些VScode的编程。
一、WPS的下拉框和Zotero的消息提示都会出发Tilling,然后挤占一个平行的大窗口，需要手动通过快捷键添加这些程序的近白名单：Super+Shift+C。
二、默认的Super+L的移动窗口的快捷键导致BazziteOS的锁屏失效。

Steps to reproduce

No response

Distribution and Linux version
NAME="Bazzite"
VERSION="43.20260326.0 (Silverblue)"
RELEASE_TYPE=stable
ID=bazzite
ID_LIKE="fedora"
VERSION_ID=43
VERSION_CODENAME="Silverblue"
PRETTY_NAME="Bazzite"
ANSI_COLOR="0;38;2;138;43;226"
LOGO=bazzite-logo-icon
CPE_NAME="cpe:/o:universal-blue:bazzite:43"
DEFAULT_HOSTNAME="bazzite"
HOME_URL="https://bazzite.gg"
DOCUMENTATION_URL="https://docs.bazzite.gg"
SUPPORT_URL="https://discord.bazzite.gg"
BUG_REPORT_URL="https://github.com/ublue-os/bazzite/issues/"
SUPPORT_END=2026-12-02
VARIANT="Silverblue"
VARIANT_ID=bazzite-gnome
OSTREE_VERSION='43.20260326.0'
BUILD_ID="Stable (F43.20260326)"
BOOTLOADER_NAME="Bazzite Stable (F43.20260326)"
IMAGE_ID="bazzite-gnome-43.20260326"
Linux MiWiFi-RA72-srv 6.17.7-ba29.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Mar 25 07:35:02 UTC 2026 x86_64 GNU/Linux
Journal Logs from the last hour
#0   55b550df0648 i   resource:///org/gnome/shell/ui/messageTray.js:490 (5ba602774c0 @ 148)
                                                     #1   55b550df05a0 i   resource:///org/gnome/shell/ui/messageTray.js:480 (5ba60277470 @ 63)
                                                     #2   55b550df0518 i   resource:///org/gnome/shell/ui/messageList.js:735 (5ba60282ec0 @ 33)
                                                     #3   55b550df0488 i   resource:///org/gnome/shell/ui/init.js:21 (159e6c48d8d0 @ 48)
GNOME Shell version

GNOME Shell 49.1

Forge version

89

Other installed/enabled extensions
[email protected]
  名称: Forge
  描述: Tiling and window manager for GNOME
- Please report bugs/issues on https://github.com/forge-ext/forge/issues
- Needs a new maintainer.
  路径: /home/taoli/.local/share/gnome-shell/extensions/[email protected]
  URL: https://github.com/forge-ext/forge
  版本: 89
  已启用: 是
  状态: ACTIVE
Monitor Setup
Image
Other Notes

No response

Lenguaje dominante
JavaScript
Estrellas
1.3k
Forks
112
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de forge-ext/forge

Todos los issues de forge-ext/forge

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.