why does gparted say "can't operate" but run anyway?
by newbiesforever from LinuxQuestions.org on (#56ZBZ)
Every time I run gparted in a terminal, it says Quote:
but then the terminal runs it anyway. It therefore does not pose a practical problem.
What the error message means is almost incidental to me; it interests me only because it's saying gparted "can't operate" and then it...operates anyway. My assumption is that it's not that simple, possibly due to ambiguous wording.
Does "can't operate" mean not that gparted won't run (since it obviously does run), but that the system can't "boot with systemd as init system (PID 1)," whatever that means? I have no idea why it can't; but again, since gparted is running normally and so is the entire system, I don't care. I just saw this odd message enough times to wonder why it's there.
| System has not been booted with systemd as init system (PID 1). Can't operate. |
What the error message means is almost incidental to me; it interests me only because it's saying gparted "can't operate" and then it...operates anyway. My assumption is that it's not that simple, possibly due to ambiguous wording.
Does "can't operate" mean not that gparted won't run (since it obviously does run), but that the system can't "boot with systemd as init system (PID 1)," whatever that means? I have no idea why it can't; but again, since gparted is running normally and so is the entire system, I don't care. I just saw this odd message enough times to wonder why it's there.