Skip to main content ↑ ↓
Topic: cannot start any programs after booting (Read 727 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

cannot start any programs after booting

Hi
Had this issue on 2 out of 5 of my artix systems, still not solved, today fired up the work laptop and got the same problem over there.

Power up, it will boot, go into Mate desktop. Try starting any programs, like terminal or browser, it will show "starting..." on the taskbar for like 10 seconds but  the program wont start.
Plus its a hit and miss with whats in the autostart, conky will be fine, syncthing tray and pipewire sometimes start, sometimes not.

When I log out then back in the problem is not there anymore , system work fine.

help needed please

edited: managed to fix the system on work laptop, had a detailed look on openrc settings, found openrc-settingsd not getting started on boot, added is as default and this fixed the problem on the laptop. Tried the same on two other desktops with same trouble but no luck.
I guess it will have something to do with elogind/dbus and associated goodness.

Re: cannot start any programs after booting

Reply #3 –
AID! I'm new to the topic, I've been using Artix with Runit for a few months, and I tried other initializers that I liked better, but they failed (although this is for another topic).

Now, the same thing happens to me as @amlu, Yesterday I did a system update, something really big, I don't know what it was, but I think it was about 300 packages, about 700mb. The curious thing is that before updating, they "moved" (I don't know if it is the correct term), 2 repositories, I think something related to Galaxy and another one, again I clarify, I don't remember exactly. After this, in about 4 packages, it was mentioned to me that they were in at least 2 different repositories, I think one was Galaxy and I don't remember the other.
Apparently the packages were the same, but not wanting to choose, I left the default option, which was the first.

Well, after the installation, the desktop was affected, many icons were no longer visible. I log out and log back in, and this was "solved".

Then, when I restarted the PC, EVERYTHING was already broken; First, something that I never realized existed in Artix (which, due to my lack of knowledge, I assume NOT), is that when logging in, in the Desktops/Graphic Servers selection, "Wayland" was defaulted, instead of Plasma (X11), but, Wayland is used with SystemD, so what is it doing there? Well as it was, the situation is that when entering the Desktop, whatever the option chosen, the result is THE SAME; The desktop icons and the entire visual environment are visible, but when it comes to running a program, it simply does not start.
The folders open, but for example, when wanting to change the system time, it mentions an error:
"Could not Authenticate/Execute action: 3. The current engine only allows auxiliary authorization, but this action does not have an auxiliary program."
Then, if you want to open a program from the console, it mentions another error: "Bus Error".

I'm sorry I can't provide more information, it's all I can do at the moment, since as I said at the beginning, I'm a newbie to this topic, I'm looking forward to someone who can guide me to solve this, since I wouldn't like to reinstall the entire thing. system.

Thank you very much in advance.

A cordial greeting.

PS: I'm sorry if the writing is poorly written, my native language is Spanish, and I am using a translator to write this, I hope you can understand.

Re: cannot start any programs after booting

Reply #4 –
Hello Magician33,

Can you confirm for us if this issue is reproducible with live media of the most recent images?

Also, can you post for us the logs from your update?

Re: cannot start any programs after booting

Reply #5 –
Quote from: Magician33 – on
Then, when I restarted the PC, EVERYTHING was already broken; First, something that I never realized existed in Artix (which, due to my lack of knowledge, I assume NOT), is that when logging in, in the Desktops/Graphic Servers selection, "Wayland" was defaulted, instead of Plasma (X11)
This is not our fault; the people at KDE changed the session starters in /usr/share/xsessions/; before plasma-workspace-6, plasma.desktop would launch X11, now it launches Wayland. This affected our Qt-based weekly ISOs, but was quickly spotted and fixed. For the record, the session filename for X11 is now plasmax11.desktop, but all decent login managers will remember your previous session choice so you only have to select it once.
This is a major version bump, so existing Plasma users should be affected and there is a flood of bug reports about it.

Re: cannot start any programs after booting

Reply #6 –
Quote from: notabot – on
Hello Magician33,

Can you confirm for us if this issue is reproducible with live media of the most recent images?

Also, can you post for us the logs from your update?

If you are referring to whether the error also happens within a "live" environment, I understand that it does not, but this is not the case, I have not tested what you intend, because the idea is to repair what is already broken, not to find out if this is an exception to the rule or not, let me explain?

Regarding the reports you ask of me, I would love to be able to provide them to you, but I don't know how to do what you tell me. Please could you direct me?

Thank you so much !

Quote from: nous – on
Quote from: Magician33 – on
Then, when I restarted the PC, EVERYTHING was already broken; First, something that I never realized existed in Artix (which, due to my lack of knowledge, I assume NOT), is that when logging in, in the Desktops/Graphic Servers selection, "Wayland" was defaulted, instead of Plasma (X11)
This is not our fault; the people at KDE changed the session starters in /usr/share/xsessions/; before plasma-workspace-6, plasma.desktop would launch X11, now it launches Wayland. This affected our Qt-based weekly ISOs, but was quickly spotted and fixed. For the record, the session filename for X11 is now plasmax11.desktop, but all decent login managers will remember your previous session choice so you only have to select it once.
This is a major version bump, so existing Plasma users should be affected and there is a flood of bug reports about it.

I appreciate you giving me some context, although honestly, as I said, I'm a bit of a novice user, and there are still specifics I don't understand.
I am willing to understand, but what happens to me is that from every comment I read, a multitude of extra questions emerge, for example:

- How is it that even though your system lacks SystemD, you can send an update with Wayland, when it depends on SystemD?

- On the other hand, I get confused: Don't they inspect the updates that "are"? I don't know how this is actually handled, but I'm surprised that it's like some kind of sieve.

I'm sorry if you feel my questions are too "probing", but I have a curious soul. I hope this level of honesty and desire to know does not bother you.

Thank you very much for your answers, if I can provide any necessary information so that you can see what errors I have, please just let me know.

A big hug.

Re: cannot start any programs after booting

Reply #7 –
Quote from: Magician33 – on
- How is it that even though your system lacks SystemD, you can send an update with Wayland, when it depends on SystemD?

That's not correct. Wayland doesn't depend on systemd.

Re: cannot start any programs after booting

Reply #8 –
Magician33:

Quote
Regarding the reports you ask of me, I would love to be able to provide them to you, but I don't know how to do what you tell me. Please could you direct me?

Here is a link to an article on how to review log files from the command line.

I think you will be able to find much of the information on where to look in the man pages.  You can reach them in terminal by issuing
Code: [Select]
man (command)

Alternatively, if you are more comfortable in a web browser, you can find all the manpages online here.
 

Re: cannot start any programs after booting

Reply #9 –
Quote from: Magician33 – on
I appreciate you giving me some context, although honestly, as I said, I'm a bit of a novice user, and there are still specifics I don't understand.
We all were novice once. If I were in your shoes, I'd refrain from regular updating until I got confident in my fixing skills (which is kind of the chicken-egg problem, as the more you fix the sharper your skills become, oh well).

Quote from: Magician33 – on
- On the other hand, I get confused: Don't they inspect the updates that "are"? I don't know how this is actually handled, but I'm surprised that it's like some kind of sieve.
It's a very real fact that developers can't possibly test every software / settings combination out there and rely on guinea pigs end users for testing and feedback.