You are not logged in.

#1 2018-10-06 19:44:40

shaoyu0209
Member
From: Taiwan
Registered: 2016-10-28
Posts: 42

[SOLVED] Qt applications launched by rofi ignores Qt theme

WM: i3-gaps
Qt theme is configured to Adapta, as is GTK+ theme.
https://i.imgur.com/K6hJZIr.png
This affects all Qt applications but not GTK+ ones.
The one on the left is launched with rofi whereas the one on the right is launched from a terminal.
Why is this and how do I set rofi to launch the applications properly?

Many thanks

Last edited by shaoyu0209 (2018-10-06 20:38:22)

Offline

#2 2018-10-06 19:46:59

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: [SOLVED] Qt applications launched by rofi ignores Qt theme

Read the Code of Conduct and only post thumbnails http://wiki.archlinux.org/index.php/Cod … s_and_code



Moving to NC...


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2018-10-06 19:52:59

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,541
Website

Re: [SOLVED] Qt applications launched by rofi ignores Qt theme

Is the theme properly applied if you start rofi from a terminal then start a program from that rofi?

If so, I'd gather you are exporting the relevant environment variable in the wrong place.  But to know the right place you'd have to tell us how you start X and what is in your relevant configs.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#4 2018-10-06 19:58:05

shaoyu0209
Member
From: Taiwan
Registered: 2016-10-28
Posts: 42

Re: [SOLVED] Qt applications launched by rofi ignores Qt theme

Trilby wrote:

Is the theme properly applied if you start rofi from a terminal then start a program from that rofi?

If so, I'd gather you are exporting the relevant environment variable in the wrong place.  But to know the right place you'd have to tell us how you start X and what is in your relevant configs.

Yes! If I launch rofi from terminal the application launched will be in the proper Qt theme.
I have this in my i3 config

bindsym $mod+d exec rofi -show combi

and this in .zprofile and .zshrc

export QT_QPA_PLATFORMTHEME=qt5ct

Offline

#5 2018-10-06 20:00:23

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,541
Website

Re: [SOLVED] Qt applications launched by rofi ignores Qt theme

Trilby wrote:

... tell us how you start X

And post full configs, not a single line.  Context matters, that's the whole point.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#6 2018-10-06 20:09:07

shaoyu0209
Member
From: Taiwan
Registered: 2016-10-28
Posts: 42

Re: [SOLVED] Qt applications launched by rofi ignores Qt theme

here

zstyle ':completion:*' auto-description '%d:'
zstyle ':completion:*' completer _list _expand _complete _ignored _match _correct _approximate _prefix
zstyle ':completion:*' completions 1
zstyle ':completion:*' expand prefix suffix
zstyle ':completion:*' glob 1
zstyle ':completion:*' list-colors ''
zstyle ':completion:*' list-prompt %SAt %p: Hit TAB for more, or the character to insert%s
zstyle ':completion:*' list-suffixes true
zstyle ':completion:*' matcher-list 'm:{[:lower:][:upper:]}={[:upper:][:lower:]}' 'r:|[.,]=** r:|=**' 'l:|=* r:|=*'
zstyle ':completion:*' max-errors 3 numeric
zstyle ':completion:*' menu select=1
zstyle ':completion:*' select-prompt %SScrolling active: current selection at %p%s
zstyle ':completion:*' substitute 1
zstyle ':completion:*' verbose true
zstyle ':completion:*' rehash true
zstyle :compinstall filename '/home/shaoyu/.zshrc'

autoload -Uz compinit && compinit
~/.vocab
alias p="proxychains -q"
alias ls="ls --color"
alias def="sdcv --use-dict='Concise Oxford English Dictionary (En-En)'"
alias i3conf="vim ~/.config/i3/config"
alias barconf="vim ~/.config/polybar/config"
alias pacman="pacaur --color always"
alias mv="mv -iv"
alias cp="cp -iv"


export EDITOR=vim
export QT_QPA_PLATFORMTHEME=qt5ct
export GTK2_RC_FILES=/home/shaoyu/.gtkrc-2.0
export PATH="$PATH:/home/shaoyu/.bin:/home/shaoyu/.gem/ruby/2.5.0/bin"

and i3 config

# This file has been auto-generated by i3-config-wizard(1).
# It will not be overwritten, so edit it as you like.
#
# Should you change your keyboard layout some time, delete
# this file and re-run i3-config-wizard(1).
#

# i3 config file (v4)
#
# Please see https://i3wm.org/docs/userguide.html for a complete reference!

set $mod Mod4

# Font for window titles. Will also be used by the bar unless a different font
# is used in the bar {} block below.
font pango:Inconsolata 14
font pango:Font Awesome 5 Brands-Regular-400 14
for_window [class="^.*"] border pixel 0

# This font is widely installed, provides lots of unicode glyphs, right-to-left
# text rendering and scalability on retina/hidpi displays (thanks to pango).
#font pango:DejaVu Sans Mono 8

# Before i3 v4.8, we used to recommend this one as the default:
# font -misc-fixed-medium-r-normal--13-120-75-75-C-70-iso10646-1
# The font above is very space-efficient, that is, it looks good, sharp and
# clear in small sizes. However, its unicode glyph coverage is limited, the old
# X core fonts rendering does not support right-to-left and this being a bitmap
# font, it doesn’t scale on retina/hidpi displays.
exec_always --no-startup-id ~/programming/polybar.sh
exec_always --no-startup-id fcitx &
exec compton
gaps inner 25
bindsym $mod+F1 gaps inner current plus 5
bindsym $mod+F2 gaps inner current minus 5
bindsym $mod+Home exec i3lock && systemctl suspend
# screenshot
bindsym $mod+y exec python ~/programming/tired.py
bindsym --release Print exec maim -s > ~/Pictures/screenshots/$(date +%Y%m%d-%H%M%S)"-screenshot.png"

#screen brightness
bindsym XF86MonBrightnessUp exec xbacklight -inc 5
bindsym XF86MonBrightnessDown exec xbacklight -dec 5

# volume control
bindsym XF86AudioRaiseVolume exec pamixer -i 5
bindsym XF86AudioLowerVolume exec pamixer -d 5
bindsym XF86AudioMute exec pamixer -t



# Use Mouse+$mod to drag floating windows to their wanted position
floating_modifier $mod

# start applications
bindsym $mod+Return exec i3-sensible-terminal
bindsym $mod+t exec firefox
bindsym $mod+n exec nautilus


# kill focused window
bindsym $mod+Shift+q kill

# start dmenu (a program launcher)
bindsym $mod+d exec --no-startup-id rofi -show combi
# There also is the (new) i3-dmenu-desktop which only displays applications
# shipping a .desktop file. It is a wrapper around dmenu, so you need that
# installed.
# bindsym $mod+d exec --no-startup-id i3-dmenu-desktop

# change focus
bindsym $mod+h focus left
bindsym $mod+j focus down
bindsym $mod+k focus up
bindsym $mod+l focus right

# alternatively, you can use the cursor keys:
bindsym $mod+Left focus left
bindsym $mod+Down focus down
bindsym $mod+Up focus up
bindsym $mod+Right focus right

# move focused window
bindsym $mod+Shift+h move left
bindsym $mod+Shift+j move down
bindsym $mod+Shift+k move up
bindsym $mod+Shift+l move right

# alternatively, you can use the cursor keys:
bindsym $mod+Shift+Left move left
bindsym $mod+Shift+Down move down
bindsym $mod+Shift+Up move up
bindsym $mod+Shift+Right move right

# split in horizontal orientation
bindsym $mod+g split h

# split in vertical orientation
bindsym $mod+v split v

# enter fullscreen mode for the focused container
bindsym $mod+f fullscreen toggle

# change container layout (stacked, tabbed, toggle split)
bindsym $mod+s layout stacking
bindsym $mod+w layout tabbed
bindsym $mod+e layout toggle split

# toggle tiling / floating
bindsym $mod+Shift+space floating toggle

# change focus between tiling / floating windows
bindsym $mod+space focus mode_toggle

# focus the parent container
bindsym $mod+a focus parent

# focus the child container
#bindsym $mod+d focus child

# Define names for default workspaces for which we configure key bindings later on.
# We use variables to avoid repeating the names in multiple places.
set $ws1 "1"
set $ws2 "2"
set $ws3 "3"
set $ws4 "4"
set $ws5 "5"
set $ws6 "6"
set $ws7 "7"
set $ws8 "8"
set $ws9 "9"
set $ws10 "10"

# switch to workspace
bindsym $mod+1 workspace $ws1
bindsym $mod+2 workspace $ws2
bindsym $mod+3 workspace $ws3
bindsym $mod+4 workspace $ws4
bindsym $mod+5 workspace $ws5
bindsym $mod+6 workspace $ws6
bindsym $mod+7 workspace $ws7
bindsym $mod+8 workspace $ws8
bindsym $mod+9 workspace $ws9
bindsym $mod+0 workspace $ws10

# move focused container to workspace
bindsym $mod+Shift+1 move container to workspace $ws1
bindsym $mod+Shift+2 move container to workspace $ws2
bindsym $mod+Shift+3 move container to workspace $ws3
bindsym $mod+Shift+4 move container to workspace $ws4
bindsym $mod+Shift+5 move container to workspace $ws5
bindsym $mod+Shift+6 move container to workspace $ws6
bindsym $mod+Shift+7 move container to workspace $ws7
bindsym $mod+Shift+8 move container to workspace $ws8
bindsym $mod+Shift+9 move container to workspace $ws9
bindsym $mod+Shift+0 move container to workspace $ws10

# reload the configuration file
bindsym $mod+Shift+c reload
# restart i3 inplace (preserves your layout/session, can be used to upgrade i3)
bindsym $mod+Shift+r restart
# exit i3 (logs you out of your X session)
bindsym $mod+Shift+e exec "i3-nagbar -t warning -m 'You pressed the exit shortcut. Do you really want to exit i3? This will end your X session.' -b 'Yes, exit i3' 'i3-msg exit'"

# resize window (you can also use the mouse for that)
mode "resize" {
        # These bindings trigger as soon as you enter the resize mode

        # Pressing left will shrink the window’s width.
        # Pressing right will grow the window’s width.
        # Pressing up will shrink the window’s height.
        # Pressing down will grow the window’s height.
        bindsym h resize shrink width 10 px or 10 ppt
        bindsym j resize grow height 10 px or 10 ppt
        bindsym k resize shrink height 10 px or 10 ppt
        bindsym l resize grow width 10 px or 10 ppt

        # same bindings, but for the arrow keys
        bindsym Left resize shrink width 10 px or 10 ppt
        bindsym Down resize grow height 10 px or 10 ppt
        bindsym Up resize shrink height 10 px or 10 ppt
        bindsym Right resize grow width 10 px or 10 ppt

        # back to normal: Enter or Escape or $mod+r
        bindsym Return mode "default"
        bindsym Escape mode "default"
        bindsym $mod+r mode "default"
}

bindsym $mod+r mode "resize"

Last edited by shaoyu0209 (2025-04-05 16:24:04)

Offline

#7 2018-10-06 20:21:50

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,541
Website

Re: [SOLVED] Qt applications launched by rofi ignores Qt theme

Ok ... one more try:

Trilby wrote:

... tell us how you start X


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#8 2018-10-06 20:23:04

shaoyu0209
Member
From: Taiwan
Registered: 2016-10-28
Posts: 42

Re: [SOLVED] Qt applications launched by rofi ignores Qt theme

Oops sorry!
I use startx and this is my .xinitrc

xrdb ~/.Xresources
redshift &
xinput set-prop "SynPS/2 Synaptics TouchPad" 284 {0 1 0}
xinput set-prop "SynPS/2 Synaptics TouchPad" 281 1
feh --bg-scale ~/Pictures/wallpaper.*
exec i3

Offline

#9 2018-10-06 20:29:59

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,541
Website

Re: [SOLVED] Qt applications launched by rofi ignores Qt theme

Sigh ... and do you start x manually from a tty running zsh, or do you have a zsh_profile start X automatically?  I'd guess the latter which would cause this problem as you don't export QT_QPA_PLATFORMTHEME until the end of your zshrc.  Exporting that variable in your xinitrc instead would make a lot more sense.

If you run startx manually from a tty, is that tty running zsh?

Last edited by Trilby (2018-10-06 20:30:47)


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#10 2018-10-06 20:38:01

shaoyu0209
Member
From: Taiwan
Registered: 2016-10-28
Posts: 42

Re: [SOLVED] Qt applications launched by rofi ignores Qt theme

Recently I started using .zprofile to autostart X in tty1.
I just moved that the variable to .xinitrc and it seems to have solved the issue.
How does this actually work though?
Thank you!

Offline

#11 2018-10-06 20:47:16

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,541
Website

Re: [SOLVED] Qt applications launched by rofi ignores Qt theme

How does what work?


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#12 2018-10-06 20:48:41

shaoyu0209
Member
From: Taiwan
Registered: 2016-10-28
Posts: 42

Re: [SOLVED] Qt applications launched by rofi ignores Qt theme

Why doesn't rofi load the applications correctly when the variable is still exported later?

Offline

#13 2018-10-06 21:00:14

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,541
Website

Re: [SOLVED] Qt applications launched by rofi ignores Qt theme

Because it is exported later ... and thus not inherited by your WM or in turn by rofi.

Environment variables are so named because they are passed through processes environments.  They are not global variables.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

Board footer

Powered by FluxBB