Bug:Incompatible With Wps

Aperta
  • Qualcosa non va?
#514 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
22/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
javascript, linux
Ambito
desktop-dev

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
JavaScript
Stelle
1.3k
Fork
112
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di forge-ext/forge

Tutte le issue di forge-ext/forge

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.