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

Background image is blurry on 2x display #1215

Open
lilydjwg opened this issue Dec 19, 2024 · 1 comment
Open

Background image is blurry on 2x display #1215

lilydjwg opened this issue Dec 19, 2024 · 1 comment

Comments

@lilydjwg
Copy link
Contributor

lilydjwg commented Dec 19, 2024

Summary

See e.g. my skin https://github.com/lilydjwg/fcitx5-skin-violet. The first screenshot was taken 4 years ago and had sharp edges, but the second screenshot taken yesterday has a blurry edge and doesn't fit well with the content.

A new screenshot:

screenshot-2024-12-19_17:54:20

It's not very noticeable with the light theme, but very noticeable with the dark one I just made.

Steps to Reproduce

  1. Use classic UI
  2. Use a 2x scale display (on Wayland, if that matters)
  3. See the edges

Expected Behavior

The edges should be sharp.

Output of fcitx5-diagnose command

System Info:

  1. uname -a:

    Linux lilyboudoir 6.10.6-arch1-1-lily #2 SMP PREEMPT_DYNAMIC Tue, 27 Aug 2024 09:33:58 +0000 x86_64 GNU/Linux
    
  2. lsb_release:

    lsb_release not found.

  3. /etc/lsb-release:

    /etc/lsb-release not found.

  4. /etc/os-release:

    NAME="Arch Linux"
    PRETTY_NAME="Arch Linux"
    ID=arch
    BUILD_ID=rolling
    ANSI_COLOR="38;2;23;147;209"
    HOME_URL="https://archlinux.org/"
    DOCUMENTATION_URL="https://wiki.archlinux.org/"
    SUPPORT_URL="https://bbs.archlinux.org/"
    BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
    PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
    LOGO=archlinux-logo
    
  5. Desktop Environment:

    Cannot determine desktop environment.

  6. XDG SESSION TYPE:

    XDG_SESSION_TYPE='wayland'
    
  7. Bash Version:

    BASH_VERSION='5.2.37(1)-release'
    

Environment:

  1. DISPLAY:

    DISPLAY=':0'
    
    
    WAYLAND_DISPLAY='wayland-1'
    
  2. Keyboard Layout:

    1. setxkbmap:

      WARNING: Running setxkbmap against an Xwayland server
      xkb_keymap {
      	xkb_keycodes  { include "evdev+aliases(qwerty)"	};
      	xkb_types     { include "complete"	};
      	xkb_compat    { include "complete"	};
      	xkb_symbols   { include "pc+us+inet(evdev)"	};
      	xkb_geometry  { include "pc(pc105)"	};
      };
      
    2. xprop:

      _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", ""
      
  3. Locale:

    1. All locales:

      C
      C.utf8
      POSIX
      en_US.utf8
      fr_FR.utf8
      ja_JP.utf8
      zh_CN.utf8
      zh_TW.utf8
      
    2. Current locale:

      LANG=zh_CN.UTF-8
      LC_CTYPE="C"
      LC_NUMERIC="C"
      LC_TIME="C"
      LC_COLLATE="C"
      LC_MONETARY="C"
      LC_MESSAGES="C"
      LC_PAPER="C"
      LC_NAME="C"
      LC_ADDRESS="C"
      LC_TELEPHONE="C"
      LC_MEASUREMENT="C"
      LC_IDENTIFICATION="C"
      LC_ALL=C
      
  4. Directories:

    1. Home:

      /home/lilydjwg
      
    2. ${XDG_CONFIG_HOME}:

      Environment variable XDG_CONFIG_HOME is not set.

      Current value of XDG_CONFIG_HOME is ~/.config (/home/lilydjwg/.config).

    3. Fcitx5 Settings Directory:

      Current fcitx5 settings directory is ~/.config/fcitx5 (/home/lilydjwg/.config/fcitx5).

  5. Current user:

    The script is run as lilydjwg (1000).

Fcitx State:

  1. executable:

    Found fcitx5 at /usr/bin/fcitx5.

  2. version:

    Fcitx version: 5.1.11

  3. process:

    Found 1 fcitx5 process:

    2207912 fcitx5
    
  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.4151.

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

    Debug information from dbus:

       Group [x11::0] has 0 InputContext(s)
    Group [wayland:] has 4 InputContext(s)
      IC [ca54128cf4f14adb939f9a2a7c67666b] program:org.telegram.desktop frontend:wayland cap:72 focus:0
      IC [9bfaa63d1f2d478e8829de3be349f53e] program:firefox-nightly frontend:wayland cap:72 focus:0
      IC [3ae05bb5ca1b4a7bb05f457731b0028a] program:org.gnome.Terminal frontend:wayland cap:72 focus:1
      IC [246792a923be42ac8c344bded98e5a0b] program: frontend:wayland cap:72 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 set to "@im=fcitx" correctly.
    Xim Server Name from Environment variable is fcitx.

  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}:

    Environment variable QT_IM_MODULE is set to "fcitx" correctly.

    fcitx5-qt4-immodule-probing not found.

  2. qt5 - ${QT_IM_MODULE}:

    Environment variable QT_IM_MODULE is set to "fcitx" correctly.

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

    QT_QPA_PLATFORM=wayland-egl
    QT_IM_MODULE=fcitx
    IM_MODULE_CLASSNAME=fcitx::QFcitxPlatformInputContext
    
  3. qt6 - ${QT_IM_MODULE}:

    Environment variable QT_IM_MODULE is set to "fcitx" correctly.

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

    QT_QPA_PLATFORM=wayland-egl
    QT_IM_MODULE=fcitx
    IM_MODULE_CLASSNAME=fcitx::QFcitxPlatformInputContext
    
  4. Qt IM module files:

    Found fcitx5 im module for qt: /usr/lib/qt/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so.
    Found fcitx5 qt5 module: /usr/lib/fcitx5/qt5/libfcitx-quickphrase-editor5.so.
    Found fcitx5 qt6 module: /usr/lib/fcitx5/qt6/libfcitx-quickphrase-editor5.so.
    Found fcitx5 im module for qt6: /usr/lib/qt6/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so.
    Found unknown fcitx qt module: /usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_fcitx5.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:

    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:

      Cannot find gtk-query-immodules for gtk 2

      Cannot find fcitx5 im module for gtk 2.

    2. gtk 3:

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

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

      Found fcitx5 im modules for gtk 3.24.43.

      "/usr/lib/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.32 at /etc/gtk-2.0/gtk.immodules.
      Version Line:

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

      Failed to find fcitx5 in immodule cache at /etc/gtk-2.0/gtk.immodules

      Cannot find fcitx5 im module for gtk 2 in cache.

    2. gtk 3:

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

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

      Found fcitx5 im modules for gtk 3.24.43.

      "/usr/lib/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 30 enabled addons:

      Simplified and Traditional Chinese Translation 5.1.7
      Classic User Interface 5.1.11
      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
      M17N 5.1.2
      Mozc 
      Status Notifier 5.1.11
      Notification 5.1.11
      Paste Primary Selection 
      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 2 disabled addons:

      Clipboard 5.1.11
      Cloud Pinyin 5.1.7
      
  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/lilydjwg/.config/fcitx5/profile:

    [Groups/0]
    # Group Name
    Name=默认
    # Layout
    Default Layout=us
    # Default Input Method
    DefaultIM=lilywb
    
    [Groups/0/Items/0]
    # Name
    Name=keyboard-us
    # Layout
    Layout=
    
    [Groups/0/Items/1]
    # Name
    Name=lilywb
    # Layout
    Layout=
    
    [Groups/0/Items/2]
    # Name
    Name=mozc
    # Layout
    Layout=
    
    [Groups/0/Items/3]
    # Name
    Name=pinyin
    # Layout
    Layout=
    
    [Groups/0/Items/4]
    # Name
    Name=keyboard-de
    # Layout
    Layout=
    
    [Groups/0/Items/5]
    # Name
    Name=keyboard-fr
    # Layout
    Layout=
    
    [Groups/0/Items/6]
    # Name
    Name=m17n_zh_pinyin
    # Layout
    Layout=
    
    [Groups/0/Items/7]
    # Name
    Name=ipa-x-sampa
    # Layout
    Layout=
    
    [GroupOrder]
    0=默认
    

Log:

  1. date:

    Thu Dec 19 17:56:34 CST 2024
    
  2. /home/lilydjwg/.config/fcitx5/crash.log:

    /home/lilydjwg/.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.

@wengxt
Copy link
Member

wengxt commented Dec 26, 2024

Issue is the image is small, and it was directly scaled to 2x (or whatever else value).

The support for svg also doesn't contain "scaling".

For png, we may want to introduce a naming scale like [email protected] to support different scale.

For svg, we want to draw it at scale directly.

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

2 participants