[ISSUE] qt5ct, problems with qt5ct.sh

[ISSUE] qt5ct, problems with qt5ct.sh

[furryfixer]

[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]

New issue by furryfixer on void-packages repository

https://github.com/void-linux/void-packages/issues/42891

Description:
Presumably applies to qt6 as well. I would like to further the discussion touched on in ** ##40619** about the desirability of including or activating **"/etc/profile.d/qt5ct.sh**" when installing the qt5ct package.  What brought this to my attention was the failure of icon themes in Plasma5 when started from the user's command line, as opposed to using a login manager.  Having forgotten about my prior installation of qt5ct, it took some time to decipher the problem.

Most login/display managers will reliably set $XDG_CURRENT_DESKTOP, but it will not be set with startx, or startplasma-wayland when a logged-in user starts directly from a tty.  In the latter case, qt5ct.sh will set QT_QPA_PLATFORMTHEME=qt5ct, even though the user is starting KDE Plasma.  This problem will also affect users of LXQT, who also may prefer not setting the theme to qt5ct.

Admittedly, starting Plasma or LXQT without a login manager is an uncommon use case, which is why I am ambivalent about removing qt5ct.sh.   I would just suggest that the pros/cons should be weighed vs. the alternative of asking the user to set QT_QPA_PLATFORMTHEME on their own.

Re: qt5ct, problems with qt5ct.sh

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 214 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/42891#issuecomment-1476861379

Comment:
you can always set XDG_CURRENT_DESKTOP yourself when doing startx

Re: qt5ct, problems with qt5ct.sh

[furryfixer]

[-- Attachment #1: Type: text/plain, Size: 237 bytes --]

New comment by furryfixer on void-packages repository

https://github.com/void-linux/void-packages/issues/42891#issuecomment-1476878871

Comment:
> you can always set XDG_CURRENT_DESKTOP yourself

Yes, and/or set QT_QPA_PLATFORMTHEME.

Re: qt5ct, problems with qt5ct.sh

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

New comment by github-actions[bot] on void-packages repository

https://github.com/void-linux/void-packages/issues/42891#issuecomment-1596374375

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

Re: [ISSUE] [CLOSED] qt5ct, problems with qt5ct.sh

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]

Closed issue by furryfixer on void-packages repository

https://github.com/void-linux/void-packages/issues/42891

Description:
Presumably applies to qt6 as well. I would like to further the discussion touched on in ** ##40619** about the desirability of including or activating **"/etc/profile.d/qt5ct.sh**" when installing the qt5ct package.  What brought this to my attention was the failure of icon themes in Plasma5 when started from the user's command line, as opposed to using a login manager.  Having forgotten about my prior installation of qt5ct, it took some time to decipher the problem.

Most login/display managers will reliably set $XDG_CURRENT_DESKTOP, but it will not be set with startx, or startplasma-wayland when a logged-in user starts directly from a tty.  In the latter case, qt5ct.sh will set QT_QPA_PLATFORMTHEME=qt5ct, even though the user is starting KDE Plasma.  This problem will also affect users of LXQT, who also may prefer not setting the theme to qt5ct.

Admittedly, starting Plasma or LXQT without a login manager is an uncommon use case, which is why I am ambivalent about removing qt5ct.sh.   I would just suggest that the pros/cons should be weighed vs. the alternative of asking the user to set QT_QPA_PLATFORMTHEME on their own.