Bhibb

  • Sep 13, 2024
  • Joined Oct 21, 2019
  • 4 best answers
  • @Bhibb,
    Appreciate the Info!
    I am considering the Framework as an upgrade to a 2016 Asus ROG 16 inch. I am reading about a number of issues that to be fair... are not surprising for a new product from a young company. One possible deal-breaker for me is that the 180 watt USB power brick does not seem capable of fully satisfying demand, resulting in battery drain while running demanding workloads, at around 10 to 15% per hour.
    This could possibly be worked around with 240 watt USB power bricks under development, but its concerning for a premium product whose main selling points are to some degree theoretical at this point.
    It would be interesting to see what ends up being your experience.

    Of course, we could end up with 240 watt bricks and a significantly more efficient GPU, making this all moot.... Eventually.

    • @Bhibb I agree, it looks great. Even running on my new UW monitor at 5120x1440.

      @ReillyBrogan Is the bottom panel's width predefined when installing a fresh Solus Plasma? I'm asking cause the live CD and after first install, the bottom panel was not full width.

    • Axios o to me it more maybe how things are updated rather than the application having issues with it
      that being said constant flatpak checks would prob be prudent.
      Maybe a nice script or something in autorun that check every so many days or could be set to whatever a person wanted.
      At the moment I dont have any flatpaks that have complained about things.

      I think three main commands for flatpak would be update,repair,remove would fix about anything.
      Dunno just thinking

      I think you are right, all of it. I have not even scratched the surface or explored all the flatpak CLI commands so I don't know the limits. See @Bhibb 's post above, he rigged it to regress a package! the wetgeek command I posted way up also has a 'remove/old/unused packages' built into it and once in a while it will rip stuff out which might be key, too.

      Axios I dont understand what makes zoom so sensitive to things
      picks at my brain cells..lol

      mine too🙂. there has go to be 1500 variables but the process of elimination is fun sometimes🙂

    • lf-araujo @Bhibb

      ok.
      plan A--budgie solus. Zoom won't launch
      plan B xfce solus. Zoom won't launch.
      plan C arch endeavour. Launches just fine. the zoom package is from their AUR and not flatpak. AUR version is 5.17.5-1 .
      I'm in arch now so flatpak version in solus is 5.17.5.2543.

      Have no idea what the hyphen ("5-1")means in relation to "5.2543" means with the DOT. which package came before? flatpak version after this one?

      that's info if anyone needs it.
      I have a Plan C at least.
      edit: rebooting to budgie

      • @Bhibb Hi. Don't remember every directory I deleted to be honest. Use the search function on your file manager. I remember that flatpak files are under /home/yourusername/.var/app/ , also from the repo should be here /usr/share/ . Another important step is that after you have deleted everything, reinstall from the repo and the file you should use to open the app should be "bitwarden-desktop" located here /usr/share/bitwarden-desktop/. I manually added the entry on my menu pointing on that file. Hope this helps you.

      • @Bhibb in the end that didn't work. but thank you so much for responding with help.
        @FAb7D that didn't work either, but I kept your config! I don't even have the .local/share/flatpak/exports/share/applications/ONLYOFFICE Desktop Editors...my entry stops with /applications and contains only a mimelist file, but thank you.
        ji-roth you are next up🙂 thank you

      • Sorry, for the late reply @Bhibb. I was certain that I answered you a little while back, but apparently I was wrong.

        Anyhow, I think it might be cadence that uses ~/.pulse/ so that might be why you aren't seeing it. I haven't been modifying any PulseAudio configs myself and can't really commend on if it is correct or not, but configs are usually ~/.config so it is probably fine.