Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Oct 25 19:02
    @UriHerrera banned @Flashwalker
Sergiy
@OldRunner_gitlab
OK. I've got it. So, in this case, can it matter that I wrote down the ISO on the Venta-flash drive?
Ventoy I meant
Sergiy
@OldRunner_gitlab
OK Uri, now I'm in. I solved the problem using the command = dd =.
I liked the responsiveness of the system. But there are still inherent bugs without fixing which I cannot install the new system - I cannot replace the old (known bug) and I cannot specify where to install the bootloader. For some reason, it only gives out disk = std = and no more options.
And one more "trifle" - the system produces this:
"nitrux @ live  ~  inxi -F
System: Host: live Kernel: 5.6.0-1021-oem x86_64 bits: 64 Desktop: KDE Plasma 5.19.4 Distro: Nitrux 1.3.1 build.310720 "
(Not 1.3.2. But 1.3.1)
I hope that this is really a "small thing" and you can fix it all.
Further I could not advance because of the above.
I will look forward to the new OS with bug fixes to install instead of the old one.
Uri Herrera
@UriHerrera

OK Uri, now I'm in. I solved the problem using the command = dd =.
I liked the responsiveness of the system. But there are still inherent bugs without fixing which I cannot install the new system - I cannot replace the old (known bug) and I cannot specify where to install the bootloader. For some reason, it only gives out disk = std = and no more options.

Right, using the "Replace" and "Install alongside" options in Calamares-qml will not work as they should. I linked both issues on the GitHub repository in the changelog. I also put what I found is causing the problem in the issues. However, as I replied to the user just above, you can uninstall Calamares-qml from the Live session and use Calamares instead.

And one more "trifle" - the system produces this:
"nitrux @ live  ~  inxi -F
System: Host: live Kernel: 5.6.0-1021-oem x86_64 bits: 64 Desktop: KDE Plasma 5.19.4 Distro: Nitrux 1.3.1 build.310720 "
(Not 1.3.2. But 1.3.1)
I hope that this is really a "small thing" and you can fix it all.
Further I could not advance because of the above.
I will look forward to the new OS with bug fixes to install instead of the old one.

Yes, the wrong package version was installed. Do apt install base-files=11.1.6+nitrux-legacy

Sergiy
@OldRunner_gitlab
Uri, thanks for the answer, I get it. Let's see how
it will work.
Sergiy
@OldRunner_gitlab
Uri, today I tried to install a new OS based on the recommendation you gave. I removed and reinstalled Calamares as you advised, but at the beginning of the installation, the system indicated that version 1.3.0 was installed, not 1.3.2. But I decided to go ahead and see what happens as a result.
Everything went fine up to 6%, but then a message about "error 127" appeared - something related to the bin and the absence of the openrc-init file and the installation was aborted.
Maybe I did something wrong, but in any case, I decided to wait until a more or less stable version of the new OS appears for installation, and in the meantime use the old version.
Hope I can use the new version in the future.
Uri Herrera
@UriHerrera

Uri, today I tried to install a new OS based on the recommendation you gave. I removed and reinstalled Calamares as you advised, but at the beginning of the installation, the system indicated that version 1.3.0 was installed, not 1.3.2. But I decided to go ahead and see what happens as a result.

Yes, it will say that because the calamares-settings-nitrux packages haven't been updated. The version number is just a text string it doesn't affect anything.

Everything went fine up to 6%, but then a message about "error 127" appeared - something related to the bin and the absence of the openrc-init file and the installation was aborted.
Maybe I did something wrong, but in any case, I decided to wait until a more or less stable version of the new OS appears for installation, and in the meantime use the old version.
Hope I can use the new version in the future.

We would need to see the complete message to know what happened.

Sergiy
@OldRunner_gitlab
OK. I'll try to start again, but the bad news is that now I can't start the old OS at all - the GRUB does not work, and the bootloader from another system does not see this OS anymore. But in Gparted the system is highlighted.
Now I will start the installation again and write down the message "manually", since it is not possible to copy it from the screen.
Sergiy
@OldRunner_gitlab
So, that is what I've got right now: The external command ended with errors.
Systemd-machine-id-setup completed with code 127. Output: / usr / sbin / chroot: failed to run command 'systemd-machine-id-setup': No such file or directory
Sergiy
@OldRunner_gitlab
This time I have already done absolutely everything following your prompt very carefully.
I'll leave the computer in liveOS mode for a while, maybe you can suggest something.
Uri Herrera
@UriHerrera
Yeah I was just browsing the contents of the package, you will want to disable that module from the Calamares configuration in/etc/calamares/settings.conf
Sergiy
@OldRunner_gitlab
How to do it? Delete entire file?
Uri Herrera
@UriHerrera
No, just remove - machineid from the file
Sergiy
@OldRunner_gitlab
In "- exec:@ &
I meant "- exec:"
Uri Herrera
@UriHerrera
Yes from that list remove the entry
Sergiy
@OldRunner_gitlab
OK. I'll try.
Sergiy
@OldRunner_gitlab
Uri, I cannot edit this file, it is "read only"
venanks
@venanks
@UriHerrera I get this after installing samba client:
E: samba-common: installed samba-common package post-installation script subprocess returned error exit status 1
E: smbclient: dependency problems - leaving unconfigured
E: samba-common-bin: dependency problems - leaving unconfigured
Uri Herrera
@UriHerrera

E: samba-common: installed samba-common package post-installation script subprocess returned error exit status 1
E: smbclient: dependency problems - leaving unconfigured
E: samba-common-bin: dependency problems - leaving unconfigured

To fix E: Sub-process /usr/bin/dpkg returned an error code (1) errors follow this guide https://itsfoss.com/dpkg-returned-an-error-code-1/

samba-common is blocked from installation in /etc/apt/preferences you can try removing the block but IIRC it's added because it pulls something that might use systemd

Uri, I cannot edit this file, it is "read only"

Of course, it's owned by root, you have to use sudo, i.e., sudo nano /etc/calamares/settings.conf

Sergiy
@OldRunner_gitlab
Hi Uri, I did everything as you suggested. The installation went fine, rebooted and the problems started from the first update - Discover froze and then the error "dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem" appeared.
I launched this program and have been waiting (for quite some time already) for some reaction in the Station. Unfortunately, I can not check with anything, since I have not been able to install anything yet. Hope the system will recover.
Sergiy
@OldRunner_gitlab
Uri, I decided to reinstall the OS. Hope this gives a better result.
Sergiy
@OldRunner_gitlab
Uri, I reinstalled the OS, but trying to update again nullified everything. Plymouth filed from the beginning, then the Discover freezes 51% and no further movement. I understand that the new system is still very "raw" so I will wait for a stable version. 4(!!) reinstallations are already a lot.
Thank you for everything, but I'd rather wait and not bother you with my failed experiments with this OS.
Thank God the bootloader works, so I will use other OSs for now until I see progress with your OS. Hope you will fix the bugs soon and release a working OS.
Sorry to disturb you.
Good luck.
Uri Herrera
@UriHerrera

Uri, I reinstalled the OS, but trying to update again nullified everything. Plymouth filed from the beginning, then the Discover freezes 51% and no further movement. I understand that the new system is still very "raw" so I will wait for a stable version. 4(!!) reinstallations are already a lot.
Thank you for everything, but I'd rather wait and not bother you with my failed experiments with this OS.
Thank God the bootloader works, so I will use other OSs for now until I see progress with your OS. Hope you will fix the bugs soon and release a working OS.
Sorry to disturb you.
Good luck.

Please attach screenshots and be as descriptive as possible when letting us know of issues, it's difficult to track down problems otherwise.

The problem is with libpam-runtime and its post-installation script. The solution is quite simple; edit the post-installation script and comment on the part that's failing. The script is at /var/lib/dpkg/info/libpam-runtime.postinst, and the part that fails is where the command pam-auth-update package is executed, so comment everything starting with that command all the way to the bottom of the function.

Uri Herrera
@UriHerrera
Then run sudo dpkg --configure -a and that's it.
Sergiy
@OldRunner_gitlab
Uri, thanks for the tips, but for me this story is already over. I'll wait until a stable system.
Arkaitz Silva
@arkaitzsilva
Hi @UriHerrera there is something I don’t understand about Nitrux, after a fresh installation of Nitrux using official ISO I always have dependency issues. If I’m not wrong, you use groovy and neon unstable repositories to build the ISO but after the installation the repository with newest packages is focal. This causes dependency issues when I try to install some packages/apps with apt. For example now I can’t install kate editor for this reason. Is there any reason to build the ISO with newer packages than the ones included in focal? Before the openrc change, to install Nitrux I used to install minimal version of Ubuntu and after that the nx-desktop-legacy package to have Nitrux with no dependency issues but now I can’t use this workaround due to openrc change
Uri Herrera
@UriHerrera

Uri, thanks for the tips, but for me this story is already over. I'll wait until a stable system.

Problems with packages like that one will continue to happen, remember that Ubuntu uses systemd, and these packages are from Ubuntu. Using Discover, or any other graphical frontend will make no difference whatsoever when the problem itself is with the packaging scripts that expect systemd services or programs to be present and that will fail otherwise.

Uri Herrera
@UriHerrera

Hi @UriHerrera there is something I don’t understand about Nitrux, after a fresh installation of Nitrux using official ISO I always have dependency issues. If I’m not wrong, you use groovy and neon unstable repositories to build the ISO but after the installation the repository with newest packages is focal.

HI @arkaitzsilva. No, the newest ISO is built from scratch, cleanly using Travis CI. All the previous ISO files were built locally from a three-year-old root filesystem of a previous version of Nitrux, and each new ISO file was basically an incremental upgrade over the previous. The newest ISO is indeed generated using the Ubuntu base rootfs of focal, Neon repositories both user and unstable (unstable is used to upgrade only a handful of packages, specifically Latte Dock dependencies), Devuan beowulf (which is the release of Devuan that matches Ubuntu focal both of which match Debian bullseye; used for elogind and policykit), our repository, and the Proprietary GPU Drivers PPA for the Nvidia drivers.

The ISO sources included in the released file are focal and Neon/user.

This causes dependency issues when I try to install some packages/apps with apt. For example now I can’t install kate editor for this reason. Is there any reason to build the ISO with newer packages than the ones included in focal? Before the openrc change, to install Nitrux I used to install minimal version of Ubuntu and after that the nx-desktop-legacy package to have Nitrux with no dependency issues but now I can’t use this workaround due to openrc change

In your example of installing Kate, I just tried and indeed is because some libraries are from Neon/unstable libkf5parts-data and libkf5parts5, however, I would strongly advise you to not install our packages as is to a vanilla Ubuntu installation, i.e, installed using the released Ubuntu ISO file.

If you want to tweak our ISO you can fork our tooling, that is definitely a better way. You may also submit PRs for review.

Arkaitz Silva
@arkaitzsilva
Hi @UriHerrera there are a couple of things I don’t understand about Nitrux iso-tool. The script itself is easy to read and understand but I don’t know how to run it because there are a lot of commands that can ruin the host OS. Is the script executed in some kind of virtual environment to keep the OS where is executed safe?. There are some Bug comments in some commands that cause error when the build.sh is executed, I understand the reason and I comment them because otherwise the script stops with an error. I don’t know if it’s the correct way to skip this error and in some point of the script there is a fix to that commands.
Uri Herrera
@UriHerrera

Hi @UriHerrera there are a couple of things I don’t understand about Nitrux iso-tool. The script itself is easy to read and understand but I don’t know how to run it because there are a lot of commands that can ruin the host OS. Is the script executed in some kind of virtual environment to keep the OS where is executed safe?. There are some Bug comments in some commands that cause error when the build.sh is executed, I understand the reason and I comment them because otherwise the script stops with an error. I don’t know if it’s the correct way to skip this error and in some point of the script there is a fix to that commands.

Yes, run them in a container, we use Travis to automate the whole process.

Arkaitz Silva
@arkaitzsilva

Hi @UriHerrera, I'm trying to build the legacy branch iso running the build.sh file from the official ubuntu focal image with docker and I'm always getting errors processing the bootstrap.sh through runch bin.
I tried also from Ubuntu, KDE Neon and Nitrux VM and there are always errors in different points but the bootstrap.sh never finishes successfully.

Which image/distro are you using to test the script locally with a successful ending as is in github repository?

Uri Herrera
@UriHerrera
Hi @arkaitzsilva. I don't use them locally, it's very likely that they fail because of something that was added for Travis. You can open an issue.
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