You know I keep forgetting about podman system reset -f.
All right. They are different. I was following your agenda. Yes it was educational and like you r Univ. lecturer approach. I also forgot Vi. But it so Spartan! I did not way to become su in container and reset and then it goes to troubles.
Eolie connection lost
unlinkat /run/user/1000/doc/by-app/org.gnome.Eolie: operation not permitted
Then no change to get image for container
Error: failed to connect to the D-Bus session instance
Guys why you are making trouble to me? I feel that my dream media center where I do can immerse in the ocean of channels to be influenced by different cultures is steaming away. How connection to Eolie can influence connection of command window. FF works and NM has connection. How you explain that. I also think that container did not work correctly. I was trying to create new containers but no. Ohâ but such a trouble now.Jack you where asking about the BT and it also do not find it. I am in using adapter what comes to PCIe lane and where I do have M2 format modules for LTE and and other for WiFI+BT. WiFi work well but there is also problem where module have 2½ and 5 band wide while old smartphones are using 2½ and then can not connect as there is not change to change in NM. Mobile broadband works very well. It goes over 60 Mega regulatory and soon as 5G come I change module. It should come next year. Module heat fairly hot and I glued sheet metal to it and stopped connection cut offs. In adapter I am using noPIN SIM and it have no isues to find operator. I am very happy about the speed and lag plus it cost 17⏠per month. So this are my issues. This is good to have some challenges. Mechanical part is easy but honestly I do need more experience. I get used to standard system but not so much now use for that in SB.
Hello @juhafinlandvoaa,
Not making any trouble, just trying to help you get your container running.
Eolie listed there is a flatpak. Yes flatpaks are containers. There is very likely alot of sharing of resources between all of your flatpaks, especially those from Gnome since they want the Gnome experience to be very integrated for the user. I believe toolbox leverages the flatpak runtime or sdk in some fashion when it is entered, not sure about when it is created.
Both Firefox and NetworkManager are on the host system as part of the base commit. So they have direct access to host resources.
So did you do a podman system reset to remove containers and images from your system? If not please do that first and get back to us here.
I was, could we continue the bluetooth discussion over at the topic you started, just to keep the confusion potential down.
Just a personal note on troubleshooting, well anything. I try very hard when I am faced with a difficult technical problem to solve, to break it down into itâs separate parts and deal with one at a time. When I deal with a combination of hardware and software as potential sources of a problem, I isolate the hardware aspects from the software and focus on getting the hardware going/recognized before I tackle the software issues. This is just rule of thumb approach that many apply in their respective work areas. What I am saying basically is that when you try to solve it all at once, it is easy to miss an important step. Take your time to understand the thing youâre working on too (ie Silverblue) this is a good spot for a quick guide about all things SIlverblue, and I would be surprised if you didnât learn something new from it even though it is a bit dated. Getting to Know Fedora Silverblue | More than 140 Characters. And of course the Fedora classroom presentation of Silverblue Getting to Know Fedora Silverblue.
1 Like
I was doing new containers and trying same and after that Podman reset . After a reboot there was connection in Eolie and PC. Then again sudo ls to test not accepting any nor none passwd and creating container. I face the same problem. I am using Rawhide. Does it have something to do with this. Though not. It has something to with a permissions. Like earlier unlinkat /run/user/1000/doc/by-app/org.gnome.Eolie: operation not permitted and now:
/usr/bin/id: cannot find name for group ID 1000
mkdir: cannot create directory â//.configâ: Permission denied
touch: cannot touch â//.config/toolbox/toolbox-welcome-shownâ: No such file or directory
Other than wanting to use bleeding edge for testing, I wouldnât recommend a user to rawhide, not that itâs bad, just things break from time to time. If you are looking to run Silverblue, or workstation for that matter, in a stable setup, then Rawhide is definitely not the way to go.
It could be an selinux policy thing ⌠checking it with sudo ostree admin config-diff | grep policy will tell. If you get any output then your policy has been changed from default for the commit. If it has, you will need to get back to me since it requires a bit of steps to successfuly get back to normal.
If you donât mind a suggestion, could you place the commands you issue inside a preformatted text block </> symbol in comment window menu. And show the command prompt as $. This helps me with understanding what you type and what is the response.
I hope you werenât using unlinkat on /run/user/1000/doc/by-app/org.gnome.Eolie
It was also very strange unlink. It takes away symlink I suppose. When I was doing <podman system reset -f> then it appears <unlinkat /run/user/1000/doc/by-app/org.gnome.Eolie: operation not permitted> I was trying now <sudo ostree admin config-diff | grep policy> and then passwd and nothing. I have clue now. If I logout GUI I can log in normally. Now if then it goes so that user@user as it should be root@user, right? This happened after your famous <podman system reset -f> as an result I can not make anything.
Podman has nothing to do with your GUI. The fact there was no feedback from the check of the selinux policy is good. Podman system reset -f is for the containers and images stored on your system that you made, nothing else. I just did podman system reset -f on my system. It wiped out my containers and images, which I expected. I then entered toolbox create and was prompted to download the image from the fedora registry. It is currently in the process of creating the requested container.
[Edit] Finished creating and now entered my new toolbox. You could try podman system prune -a to prune unused data.
What are you meaning here? When you login it should be user at localhost or whatever for your prompt. Why would you login as root?
Also, since this problem would seem to be outside of the container itself from what youâre saying, it is a good idea to do an rpm-ostree update to make sure everything is fresh.
last update what I was able to fetch was ten days ago. I noticed that when log out Gnome then in log in my only passwd works and then in terminal it do not work. All right. I was using <system prune -a> and it seems fix problem. I got now responses to sudo commands and password is accepted. It is fetching image to toolbox but <vi /etc/passwd> do not accept passwd since it is diferent. How to look password if you do not know what is it?
What do you mean here specifically, why would you need your password in the terminal, and how did it not work?
You should also do rpm-ostree cleanup -m to make sure the repo metadata is fresh.
I donât know why you care about the password in toolbox period. You donât even have to enter one, just use sudo. I never have to enter my password in the toolbox container. And vi (or vim) is an editor, it is not password protected as far as I know, unless you went through great lengths to make it so.
And just for clarity sake, there is a file in any GNU linux system that resides in /etc and it is called passwd. Is this the file you mean that you want to see the user password inside your toolbox? You wonât see any actual passwords but you will see that root is nologin and around the bottom of the file will be your user info, but again no password.
I have Fedora 33 Silverblue Rawhide installed on my system so I can use the BTRFS filesystem. But I can also use toolbox in F33 SB and try to replicate some of the issues you are having with it. So the first one I get is this, when I enter a toolbox just created âŚ
/usr/bin/id: cannot find name for group ID 1000
hmm ⌠donât usually see that ⌠I think I will try installing some packages âŚ
sudo dnf install vim-enhanced java-11-openjdk* terminator
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:#1) Respect the privacy of others. #2) Think before you type. #3) With great power comes great responsibility.[sudo] password for ssnow:
Sorry, try again.
[sudo] password for ssnow:
Sorry, try again.
[sudo] password for ssnow:
Well, I owe you an appology @juhafinlandvoaa. I was, until now blissfully unaware of this bug, and it is not happening on F32 Silverblue with the toolbox image used there, so this is definitely F33 change related. I am going to do some more digging into it and will let you know what I find. First off, it shouldnât prompt for the password, and even if the decision was made to do that, respect the sudoers.
Just out of curiosity, I ran the command as normal user âŚ
dnf install vim-enhanced java-11-openjdk* terminator
and this was the result âŚ
Error: This command has to be run with superuser privileges (under the root user on most systems).
So definitely a bug and thanks for catching it. I created an issue https://github.com/containers/toolbox/issues/523 for it.
1 Like
Steven, I was so much in the work that could not correspond. Glad to hear that I could contribute something to society, though it is a reason to use Rawhide. No need to be so sentimental. Here in old continent you just say that you where wrong and I am the best. All right. In fact when I leave home I rebase to std. version and then rebase myself other side of country.
Hello Juha,
No worries, Iâm not really that sentimental. I just donât mind saying when I make a mistake. I really should have tried rawhide to understand the problem you were describing.
That is true, by using it, when we find and report bugs we are contributing to the whole community. Even if only for that one thing that one time. So you went back to stable release for now? I think there are still toolbox problems as of yesterday.
Yes, I went std. No that is not correct. It is stable version. Family also using same PC when I am away. They are not so happy always my experiments. And when I am framing in the construction side, it is challenging to make help-desk over a phone. I was reading now your post and it was the same as I got. I barely understand difference when you are out and in. juanje descripe this. Well, I would not mind to have credit to discover this. Toolbox has own Bugzilla?
I meant with Rawhide there are still toolbox problems.
Yes remote support is not always the easiest. 