Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

主题使用svg素材,在KDE Wayland 200%缩放环境下出现素材缩放模糊 #1176

Open
sanweiya opened this issue Nov 10, 2024 · 0 comments

Comments

@sanweiya
Copy link

Summary

屏幕截图_20241111_001434

Steps to Reproduce

输入法的尺寸符合预期,但是文字和背景有明显的清晰度差异。
output_image

Expected Behavior

这是在xfce X11环境下使用双倍尺寸svg素材、设置更大的边距得到的截图,可以模拟正确缩放之后的效果。
output_image2

Output of fcitx5-diagnose command

完整输出 fcitx5-diagnose.txt

System Info:

  1. uname -a:

    Linux Fedora 6.11.6-300.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Nov  1 16:16:00 UTC 2024 x86_64 GNU/Linux
    
  2. lsb_release -a:

    LSB Version:	n/a
    Distributor ID:	Fedora
    Description:	Fedora Linux 41 (KDE Plasma)
    Release:	41
    Codename:	n/a
    
  3. lsb_release -d:

    Description:	Fedora Linux 41 (KDE Plasma)
    
  4. /etc/lsb-release:

    /etc/lsb-release not found.

  5. /etc/os-release:

    NAME="Fedora Linux"
    VERSION="41 (KDE Plasma)"
    RELEASE_TYPE=stable
    ID=fedora
    VERSION_ID=41
    VERSION_CODENAME=""
    PLATFORM_ID="platform:f41"
    PRETTY_NAME="Fedora Linux 41 (KDE Plasma)"
    ANSI_COLOR="0;38;2;60;110;180"
    LOGO=fedora-logo-icon
    CPE_NAME="cpe:/o:fedoraproject:fedora:41"
    DEFAULT_HOSTNAME="fedora"
    HOME_URL="https://fedoraproject.org/"
    DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f41/system-administrators-guide/"
    SUPPORT_URL="https://ask.fedoraproject.org/"
    BUG_REPORT_URL="https://bugzilla.redhat.com/"
    REDHAT_BUGZILLA_PRODUCT="Fedora"
    REDHAT_BUGZILLA_PRODUCT_VERSION=41
    REDHAT_SUPPORT_PRODUCT="Fedora"
    REDHAT_SUPPORT_PRODUCT_VERSION=41
    SUPPORT_END=2025-12-15
    VARIANT="KDE Plasma"
    VARIANT_ID=kde
    
  6. Desktop Environment:

    Desktop environment is kde.

  7. XDG SESSION TYPE:

    XDG_SESSION_TYPE='wayland'
    
  8. Bash Version:

    BASH_VERSION='5.2.32(1)-release'
    

Environment:

  1. DISPLAY:

    DISPLAY=':0'
    
    
    WAYLAND_DISPLAY='wayland-0'
    

此处省略长篇幅不相干内容

Fcitx State:

  1. executable:

    Found fcitx5 at /usr/bin/fcitx5.

  2. version:

    Fcitx version: 5.1.11

  3. process:

    Found 2 fcitx5 processes:

     126190 fcitx5
     259175 fcitx5-diagnose
    
  4. fcitx5-remote:

    fcitx5-remote works properly.

  5. DBus interface:

    Using dbus-send to check dbus.

    Owner of DBus name org.fcitx.Fcitx5 is :1.34.

    PID of DBus name org.fcitx.Fcitx5 owner is 126190.

    Debug information from dbus:

       Group [wayland:] has 5 InputContext(s)
      IC [c85e1155d39540d3918811b1fafdfe2a] program:org.kde.konsole frontend:wayland cap:72 focus:1
      IC [1b1258e91137481686df45591d4e52fa] program:org.kde.dolphin frontend:wayland cap:90072 focus:0
      IC [d670867d4f7740acac77eab7ee4ac32a] program:org.mozilla.firefox frontend:wayland cap:72 focus:0
      IC [88bed87c119c45bcb3596751061510a1] program:org.kde.dolphin frontend:wayland cap:8000d0072 focus:0
      IC [250a6aa69102451f9b13aaef2b152021] program: frontend:wayland cap:72 focus:0
    Group [x11::0] has 2 InputContext(s)
      IC [8b0551f334724c9092e03e3d13e149cc] program:wechat frontend:fcitx4 cap:800072 focus:0
      IC [80755d8687d448cbbc9e2dc9eaf40773] program:wechat frontend:fcitx4 cap:800072 focus:0
    Input Context without group
    

Fcitx Configure UI:

  1. Config Tool Wrapper:

    Found fcitx5-configtool at /usr/bin/fcitx5-configtool.

  2. Config GUI for qt:

    Found fcitx5-config-qt at /usr/bin/fcitx5-config-qt.

  3. Config GUI for kde:

    kcmshell5 not found.

Frontends setup:

The environment variable checked by this script only shows the environment under current shell. It is still possible that you did not set the environment to the whole graphic desktop session. You may inspect the actual environment variable of a certain process by using xargs -0 -L1 /proc/$PID/environ for a certain process that you find not working.

Xim:

  1. ${XMODIFIERS}:

    Environment variable XMODIFIERS is "@im=ibus" instead of "@im=fcitx". Please check if you have exported it incorrectly in any of your init files.

    Please set environment variable XMODIFIERS to "@im=fcitx" using the tool your distribution provides or add export XMODIFIERS=@im=fcitx to your ~/.xprofile. See Input Method Related Environment Variables: XMODIFIERS.

    Xim Server Name from Environment variable is ibus.

  2. XIM_SERVERS on root window:

    Xim server name is the same with that set in the environment variable.

  3. XIM encoding:

    Your LC_CTYPE is set to C whose encoding is not UTF-8. You may have trouble committing strings using XIM.

Qt:

  1. qt4 - ${QT4_IM_MODULE}:

    Please set environment variable QT_IM_MODULE to "fcitx" using the tool your distribution provides or add export QT_IM_MODULE=fcitx to your ~/.xprofile. See Input Method Related Environment Variables: QT_IM_MODULE.

    fcitx5-qt4-immodule-probing not found.

  2. qt5 - ${QT_IM_MODULE}:

    Please set environment variable QT_IM_MODULE to "fcitx" using the tool your distribution provides or add export QT_IM_MODULE=fcitx to your ~/.xprofile. See Input Method Related Environment Variables: QT_IM_MODULE.

    It is OK to use qt5 built-in Wayland im module if your compositor fully supports text-input protocol used by qt5.

    Using fcitx5-qt5-immodule-probing to check the actual im module to be used under current environment:

    QT_QPA_PLATFORM=wayland
    QT_IM_MODULE=
    IM_MODULE_CLASSNAME=QtWaylandClient::QWaylandInputContext
    
  3. qt6 - ${QT_IM_MODULE}:

    Please set environment variable QT_IM_MODULE to "fcitx" using the tool your distribution provides or add export QT_IM_MODULE=fcitx to your ~/.xprofile. See Input Method Related Environment Variables: QT_IM_MODULE.

    It is OK to use qt6 built-in Wayland im module if your compositor fully supports text-input protocol used by qt6.

    Using fcitx5-qt6-immodule-probing to check the actual im module to be used under current environment:

    QT_QPA_PLATFORM=wayland
    QT_IM_MODULE=
    IM_MODULE_CLASSNAME=QtWaylandClient::QWaylandInputContext
    
  4. Qt IM module files:

    Found fcitx5 qt5 module: /lib64/fcitx5/qt5/libfcitx-quickphrase-editor5.so.
    Found fcitx5 qt6 module: /lib64/fcitx5/qt6/libfcitx-quickphrase-editor5.so.
    Found fcitx5 im module for qt5: /lib64/qt5/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so.
    Found fcitx5 im module for qt6: /lib64/qt6/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so.

    Following error may not be accurate because guessing Qt version from path depends on how your distribution packages Qt. It is not a critical error if you do not use any Qt application with certain version of Qt or you are using text-input support by Qt under Wayland.
    Cannot find fcitx5 input method module for Qt4.

Gtk:

  1. gtk - ${GTK_IM_MODULE}:

    Please set environment variable GTK_IM_MODULE to "fcitx" using the tool your distribution provides or add export GTK_IM_MODULE=fcitx to your ~/.xprofile. See Input Method Related Environment Variables: GTK_IM_MODULE.

    It is OK to use gtk built-in Wayland im module if your compositor fully supports text-input protocol used by gtk.

    Using fcitx5-gtk2-immodule-probing to check the actual im module to be used under current environment:

    GTK_IM_MODULE=ibus
    

    Using fcitx5-gtk3-immodule-probing to check the actual im module to be used under current environment:

    GTK_IM_MODULE=wayland
    

    Using fcitx5-gtk4-immodule-probing to check the actual im module to be used under current environment:

    GTK_IM_MODULE=wayland
    
  2. gtk-query-immodules:

    1. gtk 2:

      Found gtk-query-immodules for gtk 2.24.33 at /usr/bin/gtk-query-immodules-2.0-64.
      Version Line:

      # Created by /usr/bin/gtk-query-immodules-2.0-64 from gtk+-2.24.33
      

      Found fcitx5 im modules for gtk 2.24.33.

      "/usr/lib64/gtk-2.0/2.10.0/immodules/im-fcitx5.so" 
      "fcitx" "Fcitx5 (Flexible Input Method Framework5)" "fcitx5" "/usr/locale" "ja:ko:zh:*" 
      "fcitx5" "Fcitx5 (Flexible Input Method Framework5)" "fcitx5" "/usr/locale" "ja:ko:zh:*" 
      
    2. gtk 3:

      Found gtk-query-immodules for gtk 3.24.43 at /usr/bin/gtk-query-immodules-3.0-64.
      Version Line:

      # Created by /usr/bin/gtk-query-immodules-3.0-64 from gtk+-3.24.43
      

      Found fcitx5 im modules for gtk 3.24.43.

      "/usr/lib64/gtk-3.0/3.0.0/immodules/im-fcitx5.so" 
      "fcitx" "Fcitx5 (Flexible Input Method Framework5)" "fcitx5" "/usr/locale" "ja:ko:zh:*" 
      "fcitx5" "Fcitx5 (Flexible Input Method Framework5)" "fcitx5" "/usr/locale" "ja:ko:zh:*" 
      
  3. Gtk IM module cache:

    1. gtk 2:

      Found immodules cache for gtk 2.24.33 at /lib64/gtk-2.0/2.10.0/immodules.cache.
      Version Line:

      # Created by gtk-query-immodules-2.0-64 from gtk+-2.24.33
      

      Found fcitx5 im modules for gtk 2.24.33.

      "/usr/lib64/gtk-2.0/2.10.0/immodules/im-fcitx5.so" 
      "fcitx" "Fcitx5 (Flexible Input Method Framework5)" "fcitx5" "/usr/locale" "ja:ko:zh:*" 
      "fcitx5" "Fcitx5 (Flexible Input Method Framework5)" "fcitx5" "/usr/locale" "ja:ko:zh:*" 
      
    2. gtk 3:

      Found immodules cache for gtk 3.24.43 at /lib64/gtk-3.0/3.0.0/immodules.cache.
      Version Line:

      # Created by gtk-query-immodules-3.0-64 from gtk+-3.24.43
      

      Found fcitx5 im modules for gtk 3.24.43.

      "/usr/lib64/gtk-3.0/3.0.0/immodules/im-fcitx5.so" 
      "fcitx" "Fcitx5 (Flexible Input Method Framework5)" "fcitx5" "/usr/locale" "ja:ko:zh:*" 
      "fcitx5" "Fcitx5 (Flexible Input Method Framework5)" "fcitx5" "/usr/locale" "ja:ko:zh:*" 
      
  4. Gtk IM module files:

    1. gtk 2:

      All found Gtk 2 immodule files exist.

    2. gtk 3:

      All found Gtk 3 immodule files exist.

    3. gtk 4:

      All found Gtk 4 immodule files exist.

Configuration:

Fcitx Addons:

  1. Addon Config Dir:

    Found fcitx5 addon config directory: /usr/share/fcitx5/addon.

  2. Addon List:

    1. Found 28 enabled addons:

      Simplified and Traditional Chinese Translation 5.1.7
      Classic User Interface 5.1.11
      Cloud Pinyin 5.1.7
      DBus 5.1.11
      DBus Frontend 5.1.11
      Emoji 5.1.11
      Fcitx4 Frontend 5.1.11
      Full width character 5.1.7
      IBus Frontend 5.1.11
      Lua IME API 5.0.13
      Input method selector 5.1.11
      Keyboard 5.1.11
      KDE Input Method Panel 5.1.11
      Lua Addon Loader 5.0.13
      Status Notifier 5.1.11
      Notification 5.1.11
      Pinyin 5.1.7
      Extra Pinyin functionality 5.1.7
      Punctuation 5.1.7
      Quick Phrase 5.1.11
      Spell 5.1.11
      Table 5.1.7
      Unicode 5.1.11
      DBus Virtual Keyboard 5.1.11
      Wayland 5.1.11
      Wayland Input method frontend 5.1.11
      XCB 5.1.11
      X Input Method Frontend 5.1.11
      
    2. Found 1 disabled addons:

      Clipboard 5.1.11
      
  3. Addon Libraries:

    All libraries for all addons are found.

  4. User Interface:

    Found 3 enabled user interface addons:

    Classic User Interface
    KDE Input Method Panel
    DBus Virtual Keyboard
    

Input Methods:

  1. /home/cx/.config/fcitx5/profile:

    [Groups/0]
    # Group Name
    Name=默认
    # Layout
    Default Layout=us
    # Default Input Method
    DefaultIM=pinyin
    
    [Groups/0/Items/0]
    # Name
    Name=keyboard-us
    # Layout
    Layout=
    
    [Groups/0/Items/1]
    # Name
    Name=pinyin
    # Layout
    Layout=
    
    [GroupOrder]
    0=默认
    

Log:

  1. date:

    Mon Nov 11 00:34:24 CST 2024
    
  2. /home/cx/.config/fcitx5/crash.log:

    /home/cx/.config/fcitx5/crash.log not found.

Warning: the output of fcitx5-diagnose contains sensitive information, including the distribution name, kernel version, name of currently running programs, etc.

Though such information can be helpful to developers for diagnostic purpose, please double check and remove as necessary before posting it online publicly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant