Open Yorwba opened 2 years ago
Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.
* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.
I wanted to report similar bug.
As you've pointed out, the issue is that user's environment isn't passed to kde-connect.
Looks like home-manager should track environment variables it sets, and then propagate those into user's systemd units.
Do you want to rename your issue to indicate that the issue is caused by the environment not being propagated? IMO, it may sound less intimidating and more urgent to potential contributors.
Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.
* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.
Are you following the right branch?
Is there an existing issue for this?
Issue description
In my
~/.config/nixpkgs/home.nix
I havewhich I would expect to allow me to use fcitx5 to type in various languages when using GUI programs like
gnome-terminal
or selecting "Configure..." in thekdeconnect-indicator
tray icon menu.However, when using these programs, the fcitx5 keyboard switching shortcut has no effect and the fcitx5 tray icon remains blank instead of showing the currently selected keyboard layout.
With other programs like
firefox
,gedit
and evenkdeconnect-settings
, using fcitx5 works fine.Comparing the
/proc/$PID/environ
of thekdeconnect-indicator
andkdeconnect-settings
processes, I noticed that thekdeconnect-indicator
was missing the three environment variables added tohome.sessionVariables
byfcitx5.nix
, probably becausekdeconnect-indicator
is launched as a systemd unit.So I used
systemctl --user edit kdeconnect-indicator
to create a~/.config/systemd/user/kdeconnect-indicator.service.d/override.conf
file with the following content:Then I was able to use fcitx5 in the kdeconnect configuration window.
Trying the same for the
gnome-terminal-server
unit didn't work, though using"GTK_IM_MODULE=xim"
did. It seems likegnome-terminal-server
is unable to locate the fcitx5 input method module for GTK.Stracing
gedit
, it successfully locates the module via theimmodules.cache
under~/.nix-profile
:while
gnome-terminal-server
doesn't even look there:It seems like some additional plumbing is required to tell graphical programs launched by systemd units about input method engines like fcitx5.
Maintainer CC
@Kranzes @kamadorueda @adisbladis @rycee
System information