shartrec
(Trevor Campbell)
November 8, 2024, 5:01am
1
I have been using Conky on Fedora for quite some years but after migrating, by a complete clean install, I cannot get Conky to start correctly in my Gnome session at startup.
I have used gnome-tweaks to add Conky as a start up application and that does happen
trevor ~ ps -ef |grep conky
trevor 13563 10559 2 15:50 ? 00:00:06 /usr/bin/conky --daemonize --pause=7
trevor 14272 14184 0 15:55 pts/0 00:00:00 grep --color=auto conky
trevor ~
But the window does not show. As you can see from above, it is starting with -pause=7
which should allow the desktop to be up before anything happens. This worked perfectly on F40.
If I kill Conky and restart it from the command prompt, alt-F2
, it displays correctly.
Pre-empting the obvious question. I was using Wayland with F40.
barryascott
(Barry A Scott)
November 8, 2024, 10:31am
2
Under kde plasma I would be using a systemd user service to start conky that is ordered (after=) to only start once the desktop is working.
My guess would be you can do the same for gnome. But I am not a gnome user.
kpineda
(Kevyn Pineda)
March 23, 2025, 2:59pm
3
Hi.
I have exactly the same issue.
Could you solve it?
See my reply.How are you starting conky?
kpineda
(Kevyn Pineda)
March 23, 2025, 9:00pm
5
I use a service to run a bash script. But the conky window doesn’t appear. I use GNOME
But the process is there:
ps -ef | grep conky
user 4542 1 0 14:58 ? 00:00:00 /bin/bash /home/user/.conkystart.sh
user 4552 3647 0 14:58 pts/0 00:00:00 grep --color=auto conky
Bash:
#!/bin/bash
sleep 20 &&
conky -c "/home/user/.conky/Kurhah-MpdC-v2.4/Kurhah/Kurhah.conf"
Service:
[Unit]
Description=Iniciar Conky al arrancar
After=multi-user.target
[Service]
ExecStart=/home/user/.conkystart.sh
Environment="DISPLAY=:0"
Environment="XAUTHORITY=/home/user/.Xauthority"
Restart=always
User=user
Group=user
[Install]
WantedBy=multi-user.target
Thanks for you help!
Kevyn Pineda:
After=multi-user.target
That target is only useful for system services.
I assume you are running this as a user service.
You will need to set it up to be after one of the desktop’s user targets.
kpineda
(Kevyn Pineda)
March 23, 2025, 9:37pm
7
I tried with After=default.target
and After=graphics.target
and I couldn’t make it work.
Any ideas?
Sorry about it, I’m not familiar with services.
I created a test service to see what was required.
I’m testing on f42 kde plasma.
$ systemctl --user cat test.service
# /home/barry/.config/systemd/user/test.service
[Unit]
Description=testing user services
After=graphical-session.target
[Service]
Type=oneshot
ExecStart=timedatectl
[Install]
WantedBy=graphical-session.target
$ systemctl --user enable test.service
When I boot up and log in the service runs.
$ systemctl --user status test.service
○ test.service - testing user services
Loaded: loaded (/home/barry/.config/systemd/user/test.service; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/user/service.d
└─10-timeout-abort.conf
Active: inactive (dead) since Wed 2025-04-23 18:26:33 BST; 1min 39s ago
Invocation: ad9a48cc0ecc4878a7bdd1b3005d5002
Process: 2253 ExecStart=timedatectl (code=exited, status=0/SUCCESS)
Main PID: 2253 (code=exited, status=0/SUCCESS)
Mem peak: 1.2M
CPU: 3ms
Apr 23 18:26:33 armf42.internal systemd[1318]: Starting test.service - testing user services...
Apr 23 18:26:33 armf42.internal timedatectl[2253]: Local time: Wed 2025-04-23 18:26:33 BST
Apr 23 18:26:33 armf42.internal timedatectl[2253]: Universal time: Wed 2025-04-23 17:26:33 UTC
Apr 23 18:26:33 armf42.internal timedatectl[2253]: RTC time: Wed 2025-04-23 17:26:33
Apr 23 18:26:33 armf42.internal timedatectl[2253]: Time zone: Europe/London (BST, +0100)
Apr 23 18:26:33 armf42.internal timedatectl[2253]: System clock synchronized: no
Apr 23 18:26:33 armf42.internal timedatectl[2253]: NTP service: inactive
Apr 23 18:26:33 armf42.internal timedatectl[2253]: RTC in local TZ: no
Apr 23 18:26:33 armf42.internal systemd[1318]: Finished test.service - testing user services.