ManjaroThis forum is for the discussion of Manjaro Linux. Note: This forum does not have any official participation.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You might try reinstalling SDDM. If it doesn't work, try switching to LightDM or XDM. Graphical.target is systemd standard equipment. Have you disabled or masked it?
You might try reinstalling SDDM. If it doesn't work, try switching to LightDM or XDM. Graphical.target is systemd standard equipment. Have you disabled or masked it?
No, havent done anything but switching themes and stuff. Reinstalling didnt help. Still the same error.
UNIT LOAD ACTIVE SUB DESCRIPTION
basic.target loaded active active Basic System
bluetooth.target loaded active active Bluetooth Support
cryptsetup.target loaded active active Local Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Preparation for Local File Systems
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User System
network.target loaded active active Network
nss-lookup.target loaded active active Host and Network Name Lookups
paths.target loaded active active Path Units
remote-fs.target loaded active active Remote File Systems
slices.target loaded active active Slice Units
sockets.target loaded active active Socket Units
sound.target loaded active active Sound Card
swap.target loaded active active Swaps
sysinit.target loaded active active System Initialization
time-set.target loaded active active System Time Set
timers.target loaded active active Timer Units
veritysetup.target loaded active active Local Verity Integrity Protected Volumes
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
20 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
So graphical.target is there and active but i still get this error. WTF!!!!!
I can see that "systemctl --user list-units --type=target" gives fewer results.
systemctl --user list unity --type=target gives me
Code:
UNIT LOAD ACTIVE SUB DESCRIPTION
basic.target loaded active active Basic System
default.target loaded active active Main User Target
paths.target loaded active active Paths
sockets.target loaded active active Sockets
timers.target loaded active active Timers
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
5 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
now graphical.target is not listed
Quote:
Originally Posted by ondoho
If you didn't remove it yet
It is still there
Quote:
Originally Posted by ondoho
you could show us the offending .service file
Code:
[Unit]
Description=System tray icon to monitor external GPU on/off status with Bumblebee
[Service]
Type=simple
ExecStart=bbswitch-monitor
Restart=always
[Install]
WantedBy=graphical.target
Quote:
Originally Posted by ondoho
the PKGBUILD and any additional installation instructions.
there is no PKGBUILD but only a "desc", "files" and "mtree" archive with "mtree.uncompressed" inside
desc:
Code:
%NAME%
bbswitch-monitor
%VERSION%
0.1.2-1
%BASE%
bbswitch-monitor
%DESC%
System tray icon to monitor external GPU on/off status with Bumblebee
%URL%
https://github.com/MicroDroid/bbswitch-monitor
%ARCH%
x86_64
%BUILDDATE%
1633258598
%INSTALLDATE%
1633258605
%PACKAGER%
Unknown Packager
%SIZE%
35007
%LICENSE%
MIT
%VALIDATION%
none
%DEPENDS%
bbswitch
%PROVIDES%
bbswitch-monitor
[Unit]
Description=System tray icon to monitor external GPU on/off status with Bumblebee
[Service]
Type=simple
ExecStart=bbswitch-monitor
Restart=always
[Install]
WantedBy=graphical.target
I think whoever wrote this service file wanted to execute a little graphical tray utility via systemd. That's not how systemd works, it does not cater to desktop environemnts in this particular way.
It was wise of them to remove the repo, I guess.
If you still want to autostart it you should do it via XDG or in some startup script.
By clicking on the link I provided, and then further links in that article.
There's many different methods, even one involving systemd, lol.
I guess at least one of them is already implemented on your system, about which you provided no information at all so far.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.