Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    venanks
    @venanks
    Is there any way to "blacklist" nvidia driver from being upgraded? The latest nvidia driver is very unstable as it gives a lot of problem especially waking up from sleep. I want to keep 440 version for now until 450 or newer version is stable enough. How do I tell apt to stop trying to upgrade 440 to 450?
    Uri Herrera
    @UriHerrera

    Is there any way to "blacklist" nvidia driver from being upgraded? The latest nvidia driver is very unstable as it gives a lot of problem especially waking up from sleep. I want to keep 440 version for now until 450 or newer version is stable enough. How do I tell apt to stop trying to upgrade 440 to 450?

    You can add a .pref file to /etc/apt/preferences.d. You can also use apt-mark hold $package.

    However, you can't install the Nvidia driver version 440 without uninstalling version 450, which means that the meta-packages will be uninstalled, and you will have to mark orphaned packages manually as manually installed.
    Uri Herrera
    @UriHerrera
    Otherwise, if you run apt autoremove by mistake you will end up with a broken system.
    venanks
    @venanks
    @UriHerrera Thanks for your guidance, but I need more detailed instructions. Like what should I put in the .pref files? Also how do I mark orphaned packages?
    Markus F
    @mafen
    Hi, is nitrux available for rpi4?
    Uri Herrera
    @UriHerrera

    Hi, is nitrux available for rpi4?

    Hi. We don't have ARM images yet.

    @UriHerrera Thanks for your guidance, but I need more detailed instructions. Like what should I put in the .pref files? Also how do I mark orphaned packages?

    You can find more info about using apt_preferences here https://manpages.debian.org/testing/apt/apt_preferences.5.en.html

    Likewise, you can find more info about marking packages here http://manpages.ubuntu.com/manpages/focal/man8/apt-mark.8.html#automatically%20and%20manually%20installed%20packages

    venanks
    @venanks
    Thanks Uri. I will read through and try it.
    Nicholas Jacobs
    @njakes_gitlab
    Uri, I know that Manjaro had a testing image up for a while, but is there a way to download nxd on something like ArcoLinux?
    Uri Herrera
    @UriHerrera

    Uri, I know that Manjaro had a testing image up for a while, but is there a way to download nxd on something like ArcoLinux?

    Hi @njakes_gitlab. I think that the components are available in the AUR.

    Nicholas Jacobs
    @njakes_gitlab
    Would they download into a stand alone desktop environment or just modifications to an existing plasma install?
    Uri Herrera
    @UriHerrera

    Do you mean a separate desktop session? No, the plasmoids would be available to add to a Plasma panel from the widgets sidebar.

    EDIT: I checked, the plasmoids are in the AUR, the Plasma look-and-feel package is also in there, and the Kvantum theme is too. What is not in the AUR is the desktop configuration which includes the Latte layouts among other things.

    Nicholas Jacobs
    @njakes_gitlab
    What is the name of the kvantum theme? All i can find is nx-plasma-look-and-feel.
    Uri Herrera
    @UriHerrera
    The person who uploaded it added it as part of the look-and-feel PKGBUILD
    Nicholas Jacobs
    @njakes_gitlab
    Ahh. Ok, thanks Uri. Are you still working with Manjaro on a testing build of nxd? I would love to use nitrux on a pacman/aur base
    Uri Herrera
    @UriHerrera
    We're working on the Maui apps which Manjaro includes with their Pinephone images.
    Arkaitz Silva
    @arkaitzsilva
    Hi @UriHerrera is there any reason to include nx-desktop-apps-legacy as a dependency of nx-desktop-legacy package? When I try to remove for instance firefox app which is not an essential app to use the desktop, it tries to remove the entire desktop due to this situation.
    Uri Herrera
    @UriHerrera

    Hi @arkaitzsilva. Yes, nx-desktop-* should add a working, usable desktop, and default desktop configuration to the base image, i.e., the base image is built from the rootfs and nitrux-minimal-*, nitrux-standard-* and nitrux-hardware-drivers-*. Even though the legacy branch doesn't build an immutable ISO, it's the policy for both types.

    So that nx-desktop-* can be replaced with whatever other meta-package or binary file (like an AppImage) that provides a complete desktop session.

    Arkaitz Silva
    @arkaitzsilva
    Hi @UriHerrera thanks I understand that there are some important packages that must be included in the meta packages to have fully functional distro (including nx-desktop-apps-legacy) but specially in the legacy branch which is very different to the immutable version, we are forced to not remove non essential apps included in the nx-desktop-apps-legacy package after the installation. It's not the end of the world but from the user point of view we partially lost the control about the apps included in our computer. I prefer the previous approach, nx-desktop-legacy-apps had nx-desktop-legacy as dependency and not the other way around, thanks anyway for the explanation.
    Arkaitz Silva
    @arkaitzsilva
    Hi @UriHerrera I've been checking the iso-tool solution for the legacy branch and I saw that you are including updates from kde-neon-unstable, ubuntu-groovy and devuan-ceres which are unstable repositories and some of them not included in the final version after the installation. This is the main reason why there are several packages newer than version in archive and can, at the end, cause errors when you want to install some apps using apt (like when I told you I couldn't install Kate editor). It wouldn't be better to include only packages from stable repositories in the iso creation to avoid this kind of errors? I know that in the immutable version it's not an issue but in the legacy branch where people use apt to install apps this causes isues constantly. I like Nitrux a lot but I had to be forced to install Nitrux meta packages from a minimal installation of Ubuntu to install all the packages from stable repositories (nitrux, ubuntu-bionic, ubuntu-focal, kde-neon-user and gnu-ppa). Now I have 0 dependency issues. From the user point of view is important to have a stable distro and to avoid dependency issues is as easy as use only stable repositories.
    Uri Herrera
    @UriHerrera

    Hi @UriHerrera thanks I understand that there are some important packages that must be included in the meta packages to have fully functional distro (including nx-desktop-apps-legacy) but specially in the legacy branch which is very different to the immutable version, we are forced to not remove non essential apps included in the nx-desktop-apps-legacy package after the installation. It's not the end of the world but from the user point of view we partially lost the control about the apps included in our computer. I prefer the previous approach, nx-desktop-legacy-apps had nx-desktop-legacy as dependency and not the other way around, thanks anyway for the explanation.

    Hi. I understand what you're saying, however, that can also be said for every other program or library that is installed by default, or configuration that is done to the distribution, or kernel version, or artwork, etc.

    But as I mentioned, the desktop meta-package can be replaced by something else, e.g., a meta-package that only had vanilla Plasma and KDE apps instead of Maui apps, XFCE or Gnome applications, and so on.

    Hi @UriHerrera I've been checking the iso-tool solution for the legacy branch and I saw that you are including updates from kde-neon-unstable, ubuntu-groovy and devuan-ceres which are unstable repositories and some of them not included in the final version after the installation. This is the main reason why there are several packages newer than version in archive and can, at the end, cause errors when you want to install some apps using apt (like when I told you I couldn't install Kate editor). It wouldn't be better to include only packages from stable repositories in the iso creation to avoid this kind of errors? I know that in the immutable version it's not an issue but in the legacy branch where people use apt to install apps this causes isues constantly. I like Nitrux a lot but I had to be forced to install Nitrux meta packages from a minimal installation of Ubuntu to install all the packages from stable repositories (nitrux, ubuntu-bionic, ubuntu-focal, kde-neon-user and gnu-ppa). Now I have 0 dependency issues. From the user point of view is important to have a stable distro and to avoid dependency issues is as easy as use only stable repositories.

    From neon/unstable it's only to update dependencies for Latte Dock and nothing else, from ubuntu/groovy it's only to update Inkscape and linux-firmware, and nothing else.

    devuan/ceres, devuan/beowulf, ubuntu/focal, neon/user, our repository, and the proprietary-gpu-ppa are used to install the majority of the packages, and all six repositories are enabled in the distribution by default as of the latest ISO, see nitrux-repository-settings.

    ubuntu/bionic, and ubuntu/xenial are only used to install casper and a version of plymouth that didn't depend on systemd.

    What you're describing is an inherent problem of package managers, and in the case of APT, it goes haywire in cases like this. Other (more modern) package managers do manage to resolve this kind of issue better. Point and case, why our focus is on AppImage.

    However, it seems to me that what you're asking is why don't we just use a single repository, i.e., ubuntu/focal, to which the answer is, for one, the packages in ubuntu/focal are built with systemd in mind, at one point down the list of dependencies something will ask for systemd, considering that we do not want to keep using systemd we use Devuan's repositories.

    Then, I have never been of the idea of not using recent, up-to-date software, definitely not bleeding edge which is what I consider as "unstable" but not solely LTS releases either, or "stable" as in ancient software (like Debian). Therefore, the devuan/ceres repository is used, however, there are packages that are not present in devuan/ceres that are in devuan/beowulf, so we use both.

    Additionally, since we're developing our software using recent KF5 libraries and Qt versions, we also need to fulfill that, which is why we use Neon, but only leave neon/user enabled, not neon/unstable.

    The use of the proprietary gpu-ppa is self-explanatory.

    It could be possible to only use Devuan repositories to pull most packages and still use the Neon repositories, however, I haven't tried that.

    Kaleb Ercanbrack
    @Twitch0125
    Hey everyone, I'm trying out the live image of Nitrux on my laptop and when I try to connect to wifi or use a wired connection I get spammed with these notifications in a loop:
    connectionNameHere is the name that appears when I'm doing a wired connection or a wifi connection
    1. "connection {connectionNameHere} activated"
    2. "DHCP Failed to start"
      3."Connection {connectionNameHere} deactivated"
    3. go to step 1
      if it helps I checked systemctl like this
      systemctl | grep dhcp
      and got this output
      dhcpcd.service loaded inactive dead DHCP Client Daemon
      I tried restarting dhcpcd but that didn't seem to fix anything
      sudo systemctl restart dhcpcd
    Kaleb Ercanbrack
    @Twitch0125
    update:
    I was able to fix my issue above with this... somehow
    sudo rc-service dhcpcd stop
    don't know why stopping the dhcp service would fix it. I still have internet and my network seems functional
    Arkaitz Silva
    @arkaitzsilva

    Sorry @UriHerrera I haven't explained myself well, I agree with you that it's important to have up-to-date software and I'm not against having several repositories configured, actually I added some repositories to have latest libreoffice and docker software.

    I know that Nitrux is built mainly using Focal packages but when an app is updated from groovy or kde-neon-unstable it's dependencies are also installed from these repos becoming in a potential cause of dependency issues because these packages are "newer than version in archive" and incompatible with the same packages available in the main repo (currently Focal).

    I know that apt doesn't help to fix it but this dependency issues could be avoided from the beginning not including packages that are incompatible with the ones available in the main repository.

    Including AppImages or repositories with latest software but built using the same base repository as Nitrux (like KDE Neon does for KDE software or the propietary drivers repo included in Nitrux, both are built from Focal) is fine.

    Uri Herrera
    @UriHerrera

    I know that Nitrux is built mainly using Focal packages but when an app is updated from groovy or kde-neon-unstable it's dependencies are also installed from these repos becoming in a potential cause of dependency issues because these packages are "newer than version in archive" and incompatible with the same packages available in the main repo (currently Focal).

    Yes, and no. It's not always that when a program is upgraded that its dependencies are too. However, I think also that I'm not making myself clear either.

    The current ISO does include the same repositories that were used to build it .

    And, the user can, too, choose from where to install a package from by specifying which repository APT uses to install that package, that solves the problem with dependencies. We have a blog post about it too.

    The default behavior of APT is to treat all available repositories as one giant pool of packages that it can use. This works fine when there's a single repository release, or as you mention, other repositories where their packages were built against the same release. So when the user installs a package the giant pool is used, nonetheless the user can specify which repository to use (read, release), then APT will use only that repository to install a package.

    Uri Herrera
    @UriHerrera
    So if sudo apt install myapp fails because APT wants to use the package from focal, and libraries from ceres, etc., sudo apt install myapp/focal will work. But, the custom is to use the former if it fails people think that there's a problem, even though the latter is an available option and solves the problem.
    Uri Herrera
    @UriHerrera
    There is no single main repository, focal, ceres (and beowulf) all have the same priority to APT. Nonetheless, ceres packages have higher versions (because it's newer) and thus is what APT will want to use first, except for KDE software because the Neon repository does have a higher priority than the others, to ensure that KF5 libraries and Plasma packages are correctly upgraded. But again, to APT, all repositories are but one giant pool of packages unless the user specifies which one to use.
    Prince Nna
    @Prn-Ice
    Hi, I want to try out nitrux, I've been using gnome for a while so id like to know if it's possible to install gnome as a backup desktop environment in case I need to get something done quickly while I'm adjusting.
    amitsaxena76
    @amitsaxena76
    Hi I am trying to install nitrux on an old sony vaio. I see the nitrux iso is for amd. Is there a image available for intel 64 bit?
    Uri Herrera
    @UriHerrera

    Hi I am trying to install nitrux on an old sony vaio. I see the nitrux iso is for amd. Is there a image available for intel 64 bit?

    Hi there. amd64 is the CPU instruction set, also known as x64. It doesn't mean AMD CPU's only.

    amitsaxena76
    @amitsaxena76
    oh ok thanks for the info. Will try it out
    Adam Vitali
    @adamvnz
    Hi I am wanting to install nitrux on my hp laptop. I have downloaded the iso and flashed using etcher. When booting the iso for the first time I get Error: Plymouth failed to start. That is as far as I can get with the live iso. I have downloaded it again with same issue. Can someone help as I would love to install this os and I am not sure how at the moment. Also have never had this issue with other os installs
    Uri Herrera
    @UriHerrera

    Hi I am wanting to install nitrux on my hp laptop. I have downloaded the iso and flashed using etcher. When booting the iso for the first time I get Error: Plymouth failed to start. That is as far as I can get with the live iso. I have downloaded it again with same issue. Can someone help as I would love to install this os and I am not sure how at the moment. Also have never had this issue with other os installs

    Hi there. Have you tried the debug entry (and removing xforcevesa from the entry)?

    Adam Vitali
    @adamvnz
    Hi there. That has got me in. Thank you very much
    Arkaitz Silva
    @arkaitzsilva
    Hi @UriHerrera, which option do you think could fit better to encrypt home partition in the deployed Nitrux version?
    Uri Herrera
    @UriHerrera

    Hi @UriHerrera, which option do you think could fit better to encrypt home partition in the deployed Nitrux version?

    Hi @arkaitzsilva. Well, we haven't tested encryption scenarios, though it is something that we're considering how to add to znx . You could give it a try with encfs or cryfs.

    Arkaitz Silva
    @arkaitzsilva
    Hi @UriHerrera, is there any workaround to uninstall some default apps without removing the entire nx-desktop-legacy package. I mean I like the nx-desktop-legacy package as it is except for the fact that I can’t uninstall the apps inside nx-desktop-apps-legacy package. I also can’t install docker from the official repo (to have the latest version) because docker.io is a dependency of nitrux and docker-ce from the official repo is not compatible with the one installed by default in nitrux. Is there any solution to keep your package management philosophy giving at the same time the possibility to the user to uninstall some non essential apps?¿recommended packages maybe? Thanks!
    Arkaitz Silva
    @arkaitzsilva
    I mean configure nx-desktop-apps-legacy as recommended package instead of dependency to be able to remove it after the installation?
    Uri Herrera
    @UriHerrera

    I mean configure nx-desktop-apps-legacy as recommended package instead of dependency to be able to remove it after the installation?

    Hi @arkaitzsilva, You can do it in two ways. You can replace the meta-package with one of your own or remove the meta-package and mark the packages you want to keep as manually installed.

    Arkaitz Silva
    @arkaitzsilva
    Hi again, I guess I could do that for apps if "nx-desktop-apps-legacy" were recommended package of "nx-desktop-legacy" instead of a dependency itself. When I try to remove firefox or docker.io (to install docker-ce, the latest version from official repo) apt tries to remove not only "nx-desktop-apps-legacy" but also de "nx-desktop-legacy" so in the next "apt-get autorremove" my desktop would be removed.
    Uri Herrera
    @UriHerrera

    Hi again, I guess I could do that for apps if "nx-desktop-apps-legacy" were recommended package of "nx-desktop-legacy" instead of a dependency itself. When I try to remove firefox or docker.io (to install docker-ce, the latest version from official repo) apt tries to remove not only "nx-desktop-apps-legacy" but also de "nx-desktop-legacy" so in the next "apt-get autorremove" my desktop would be removed.

    When a package is labeled as a recommended package it means that it's optional, and it doesn't get pulled unless the user specifies the package for installation. IIRC another user also asked about this.

    @UriHerrera Thanks for your guidance, but I need more detailed instructions. Like what should I put in the .pref files? Also how do I mark orphaned packages?

    You can find more info about using apt_preferences here https://manpages.debian.org/testing/apt/apt_preferences.5.en.html

    Likewise, you can find more info about marking packages here http://manpages.ubuntu.com/manpages/focal/man8/apt-mark.8.html#automatically%20and%20manually%20installed%20packages

    .

    Uri Herrera
    @UriHerrera
    But yes, if you want to remove the packages that our meta-packages install, you have to replace our meta-packages with your own, so that yours provides only the packages you want, or mark the packages as I mentioned. Of course, don't run apt autoremove before you mark the packages.
    Head-on-a-Stick
    @Head-on-a-Stick
    Why are you using pkgmaster.devuan.org for the Devuan packages? The developers recommend that deb.devuan.org be used instead to reduce the load on their main servers: https://dev1galaxy.org/viewtopic.php?pid=24966#p24966
    shitzuu
    @shitzuu
    Hi, I recently started using Nitrux. I have the latest version that is available but I experience huge lags on it and I am not able to install the available update because the base-passwd configuration jams. Below I enclose a photo with version and resource consumption during use.
    https://imgur.com/UcXQ94k
    Arkaitz Silva
    @arkaitzsilva
    Hi @UriHerrera It seems that there is some kind of problem with the recently released KDE Plasma 5.20 and the Nitrux main meta-package.
    conflicts.png