search

ublue-os / framework

OCI Images derived of ublue-os main images for Framework hardware
https://universal-blue.org/images/framework
Apache License 2.0
14 stars 3 forks source link

Kinoite Image #14

Open bmp opened 1 year ago

bmp commented 1 year ago

Hello,

I am on the bluefin-dx-framework and switched to the kinoite-framework image as available here. I experienved the following issues,

  1. Applications I had installed through a distrobox (emacs-wayland, etc. on an arch distrobox) had some trouble starting (I am guessing this was because certain gtk packages were removed).
  2. Font rendering was not respected across KDE (there was some blurriness in KDE whereas I have not experienced that in Bluefin). Interestingly, on my other KDE installations (Void and Slackware), I did not have this issue.
  3. Blackbox was not the default applicaiton to launch the distrobox app, it launches it in konsole unless I specifically choose to open blackbox.

Please let me know if I am doing something wrong as opposed to the default settings themselves.

bobslept commented 1 year ago

Well first of all thanks for reporting these issues. But I'm not really sure if I have solutions for those problems.

Currently kinoite-framework is basicly kinoite-main with specific packages and configs for framework hardware. For example shipping with tlp and a nice config for that to make that work out of the box.

So at this moment it is very slim and more comparable to the main repo then it is to the bluefin repo. I'm curious if you experience the same issues when rebasing to kinoite-main. If you compare the package list of bluefin-dx-framework versus kinoite-framework we do install fonts in there which are not available anymore when you rebase from one into the other. Maybe that has something todo with it? I'm not sure.

I've rebased from kinoite-framework to bluefin-dx-framework and back to kinoite-framework. And was not able to reproduce blurry fonts. Maybe because its in a VM, maybe because I started from kinoite in the first place. I have no idea.

As we currently follow the main repo which is fairly a stock variant of upstream with batteries included. We don't set default's like blackbox like we did in bluefin. We even don't install blackbox, it's there because the flatpak survived the rebase. Maybe this issue will explain it a little. Maybe that will change in the future but I don't know for now.

bmp commented 1 year ago

Well first of all thanks for reporting these issues. But I'm not really sure if I have solutions for those problems.

Ofcourse, thanks to all of you doing the work to make it useful for the rest of us :-)

Currently kinoite-framework is basicly kinoite-main with specific packages and configs for framework hardware. For example shipping with tlp and a nice config for that to make that work out of the box.

So at this moment it is very slim and more comparable to the main repo then it is to the bluefin repo. I'm curious if you experience the same issues when rebasing to kinoite-main. If you compare the package list of bluefin-dx-framework versus kinoite-framework we do install fonts in there which are not available anymore when you rebase from one into the other. Maybe that has something todo with it? I'm not sure.

I'll check with the kinoite-main image and report back, though would missing fonts cause such an issue? I'll check by manually layering those fonts when I go rebase to kinoite-main to see if the issue goes away.

I've rebased from kinoite-framework to bluefin-dx-framework and back to kinoite-framework. And was not able to reproduce blurry fonts. Maybe because its in a VM, maybe because I started from kinoite in the first place. I have no idea.

Would being on a VM matter for this? As long as specific rendering and font scaling is the same wouldn't it be the same?

As we currently follow the main repo which is fairly a stock variant of upstream with batteries included. We don't set default's like blackbox like we did in bluefin. We even don't install blackbox, it's there because the flatpak survived the rebase. Maybe this issue will explain it a little. Maybe that will change in the future but I don't know for now.

This makes complete sense! And will see if I have the technical chops to contribute meaningfully.

bobslept commented 1 year ago

Please make a screenshot or something if you are able to capture it that way. Maybe somebody then can recognize the behavior. We can then maybe ask the kinoite/kde users what is happening. :sweat_smile:

bmp commented 11 months ago

Okay, so finally got around to testing this. I am able to confirm the following,

  1. Applications I had installed through a distrobox (emacs-wayland, etc. on an arch distrobox) had some trouble starting (I am guessing this was because certain gtk packages were removed).

This continues to happen (for starting gpg-agent, ssh-agent, etc., I need to figure out what and how to fix this)

2. Font rendering was not respected across KDE (there was some blurriness in KDE whereas I have not experienced that in Bluefin). Interestingly, on my other KDE installations (Void and Slackware), I did not have this issue.

This is no longer an issue! The font rendering seems to be more uniform across flatpaks and native applications if I may say so!

3. Blackbox was not the default applicaiton to launch the distrobox app, it launches it in konsole unless I specifically choose to open blackbox.

This continues to be the problem, I need to check now if this change is a result of startup scripts in KDE being different from Gnome and how to fix those.

Also, I realised there were some typos in the first post now!

castrojo commented 11 months ago

It might be worth just switching your distrobox terminal to just use konsole since it's on kde instead of using blackbox?

(Though blackbox is so pretty!)

bmp commented 11 months ago

@castrojo By default, distrobox does use konsole unless I specifically run blackbox. I think it might be an issue with out ssh-agent and gpg-agent can be started using keychain in KDE as opposed to being used in .bashrc or .zshrc. Or do you mean something else?

kinoite-framework_blackbox

kinoite-framework_distrobox-konsole

castrojo commented 11 months ago
  1. Blackbox was not the default applicaiton to launch the distrobox app, it launches it in konsole unless I specifically choose to open blackbox.

I mean this part, is it "working normally" in konsole?

bmp commented 11 months ago
  1. Blackbox was not the default applicaiton to launch the distrobox app, it launches it in konsole unless I specifically choose to open blackbox.

I mean this part, is it "working normally" in konsole?

Yep, it works as expected in konsole, i.e, all exported bins for distrobox, the environment variables, etc. seem to be respected.

Some of it seems to work, i.e, all exported bins from distrobox and environment variables seem to be respected.

However, applications exported through distrobox are available in the GUI, but when I launch them through GUI they have issues with things like ssh-agent, gpg-agent etc. The workaround that I have found for now is the following, in konsole or blackbox, enter the distrobox and then run the installed application, they then respect all these variables.

PS: Agreed, blackbox is really pretty!

bmp commented 11 months ago

Additionally, when running gtk apps that I had installed in the distrobox, I would get the following error,

Failed to load module "colorreload-gtk-module"
Failed to load module "window-decorations-gtk-module"
Failed to load module "appmenu-gtk-module"

I fixed this by doing the following,

  1. Installed appmenu-gtk-module in the distrobox and restarted it.
  2. Edited ~/.config/gtk-x.0/settings.ini to removemodify the line gtk-modules=colorreload-gtk-module:appmenu-gtk-module:window-decorations-gtk-module to gtk-modules=appmenu-gtk-module

Now GTK errors seem to be fixed

bmp commented 11 months ago

Should I post this one as a seperate issue? Solaar package is missing in the kinoite-framework image, and based on what I have read up and experienced so far, that would mean it is missing in kinoite image too.