[SOLVED] Daemon disappeared after update

Topic: [SOLVED] Daemon disappeared after update (Read 980 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.

[SOLVED] Daemon disappeared after update

30 September 2021, 07:11:08

- System: Artix, Plasma , OpenRC
- Daemon: ckb-next-daemon

After today update and restart `ckb-next` don't works anymore, a poupup appear inviting me to enable the `ckb-next-daemon`.
Prove package is installed:

Code: [Select]

Tony-Haupt-PC:[tony]:~$ yay ckb-next
5 aur/ckb-next-git 1:0.4.4.r100.gdc4dc54c-2 (+12 1.21) 
    Corsair Keyboard and Mouse Input Driver, git master branch
4 aur/ckb-next 0.4.4-3 (+33 2.23) (Installed)
    Corsair Keyboard and Mouse Input Driver, release version
3 universe/ckb-next-suite66 20210921-1 (3.8 KiB 1.2 KiB) 
    ckb-next script for suite66
2 universe/ckb-next-s6 20210928-1 (3.6 KiB 517.0 B) 
    s6 init script for ckb-next
1 universe/ckb-next 0.4.4-3 (1.1 MiB 2.8 MiB) (Installed)
    Corsair Keyboard and Mouse Input Driver, release version
==> Packages to install (eg: 1 2 3, 1-3 or ^4)
==> q
 there is nothing to do

Prove Daemon was running before last restart (file:///var/log/rc.log.1.gz):

Code: [Select]

rc shutdown logging started at Sun Sep 12 15:37:04 2021

 * Caching service dependencies ...
 [ ok ]
local             | * Stopping local ...
urandom           | * Saving random seed ...
NetworkManager    | * Stopping NetworkManager ...
sddm              | * Stopping sddm ...
openrc-settingsd  | * Stopping openrc-settingsd ...
ckb-next-daemon   | * Stopping Corsair Keyboards and Mice Driver ...
 [ ok ]
 [ ok ]
 [ !! ]

Daemon don't exist anymore:

Code: [Select]

:~# rc-update add ckb-next-daemon default
 * rc-update: service `ckb-next-daemon' does not exist

Error-message by reinstall `ckb-next`:

Code: [Select]

/tmp/alpm_hkOFrv/.INSTALL: Zeile 42: systemctl: Kommando nicht gefunden.
/tmp/alpm_hkOFrv/.INSTALL: Zeile 47: systemctl: Kommando nicht gefunden.
(1/1) reinstalling ckb-next                                                                                                    [############################################################################] 100%
/tmp/alpm_5x5S8l/.INSTALL: Zeile 72: systemctl: Kommando nicht gefunden.
error: command failed to execute correctly

Does anyone know how to solve this topic?

Re: Daemon disappeared after update

Reply #1 – 30 September 2021, 13:17:06

See if there is a ckb-next in /etc/init.d If not when I get a chance I will write an openrc pkg for it when I get a chance

Edit: I've added 'ckb-next-openrc' in the universe repo, which contains the openrc script

Re: Daemon disappeared after update

Reply #2 – 01 October 2021, 09:35:41

Quote from: ndowens – on 30 September 2021, 13:17:06

See if there is a ckb-next in /etc/init.d If not when I get a chance I will write an openrc pkg for it when I get a chance

Edit: I've added 'ckb-next-openrc' in the universe repo, which contains the openrc script

Thank you very much, that's speed!

I solve temporarily the issue installing `5 aur/ckb-next-git 1:0.4.4.r100.gdc4dc54c-2 (+12 1.19) (Installed: 1:0.4.4.r105.ge15ff771-1)` and enabling the daemon manually, see:

Code: [Select]

Tony-Haupt-PC:[tony]:~$ yay ckb-next
5 aur/ckb-next-git 1:0.4.4.r100.gdc4dc54c-2 (+12 1.19) (Installed: 1:0.4.4.r105.ge15ff771-1)
    Corsair Keyboard and Mouse Input Driver, git master branch
4 aur/ckb-next 0.4.4-3 (+33 2.18) 
    Corsair Keyboard and Mouse Input Driver, release version
3 universe/ckb-next-suite66 20210921-1 (3.8 KiB 1.2 KiB) 
    ckb-next script for suite66
2 universe/ckb-next-s6 20210928-1 (3.6 KiB 517.0 B) 
    s6 init script for ckb-next
1 universe/ckb-next 0.4.4-3 (1.1 MiB 2.8 MiB) 
    Corsair Keyboard and Mouse Input Driver, release version
==> Packages to install (eg: 1 2 3, 1-3 or ^4)
==> q
 there is nothing to do
Tony-Haupt-PC:[tony]:~$ sudo pacman -Syy
[sudo] password for tony: 
:: Synchronizing package databases...
 system                                                                                            262.6 KiB   779 KiB/s 00:00 [############################################################################] 100%
 world                                                                                            1922.5 KiB  10.3 MiB/s 00:00 [############################################################################] 100%
 galaxy                                                                                           1930.4 KiB  25.5 MiB/s 00:00 [############################################################################] 100%
 universe                                                                                           73.9 KiB   114 KiB/s 00:01 [############################################################################] 100%
 extra                                                                                            1571.4 KiB  2.41 MiB/s 00:01 [############################################################################] 100%
 community                                                                                           5.8 MiB  9.12 MiB/s 00:01 [############################################################################] 100%
Tony-Haupt-PC:[tony]:~$ yay ckb-next
6 aur/ckb-next-git 1:0.4.4.r100.gdc4dc54c-2 (+12 1.19) (Installed: 1:0.4.4.r105.ge15ff771-1)
    Corsair Keyboard and Mouse Input Driver, git master branch
5 aur/ckb-next 0.4.4-3 (+33 2.18) 
    Corsair Keyboard and Mouse Input Driver, release version
4 universe/ckb-next-suite66 20210921-1 (3.8 KiB 1.2 KiB) 
    ckb-next script for suite66
3 universe/ckb-next-s6 20210928-1 (3.6 KiB 517.0 B) 
    s6 init script for ckb-next
2 universe/ckb-next-openrc 20210930-1 (3.1 KiB 662.0 B) 
    OpenRC script for ckb-next
1 universe/ckb-next 0.4.4-4 (1.1 MiB 2.8 MiB) 
    Corsair Keyboard and Mouse Input Driver, release version
==> Packages to install (eg: 1 2 3, 1-3 or ^4)
==> q
 there is nothing to do

sorry for asking, maybe for you a silly question but, is the solution now to uninstall my temporarily solution and just install

Code: [Select]

2 universe/ckb-next-openrc 20210930-1 (3.1 KiB 662.0 B) 
    OpenRC script for ckb-next

or I have to make something different? Sorry again for my confusion.

Re: Daemon disappeared after update

Reply #3 – 01 October 2021, 10:07:02

the *-openrc package will pull in ckb-next itself from universe, so you can uninstall the git version as the one it will pull will conflict.

Re: Daemon disappeared after update

Reply #4 – 01 October 2021, 16:14:04

Quote from: ndowens – on 01 October 2021, 10:07:02

the *-openrc package will pull in ckb-next itself from universe, so you can uninstall the git version as the one it will pull will conflict.

Thanks for your reply and efforts.

Edit:
Sorry, the solution didn't work.
```ckb-next-openrc``` installs two versions of ''ckb-next'' the version ''4.4.3'' and the version ''4.4.4''.
That cause the ''mute-key'' assign to indefinite status and appear in different color than normal assigned (from blue to green).

I rolled back to git-version for the moment, can you check this behavior at your side or review the code please?

Re: [SOLVED] Daemon disappeared after update

Reply #5 – 03 October 2021, 14:44:08

Quote from: tony26102 – on 01 October 2021, 16:14:04

Thanks for your reply and efforts.

Edit:
Sorry, the solution didn't work.
```ckb-next-openrc``` installs two versions of ''ckb-next'' the version ''4.4.3'' and the version ''4.4.4''.
That cause the ''mute-key'' assign to indefinite status and appear in different color than normal assigned (from blue to green).

I rolled back to git-version for the moment, can you check this behavior at your side or review the code please?

I don't see how it is installing two versions. You can use pacman and not a AUR helper for the package.

Re: [SOLVED] Daemon disappeared after update

Reply #6 – 03 October 2021, 15:01:35

Quote from: tony26102 – on 01 October 2021, 16:14:04

```ckb-next-openrc``` installs two versions of ''ckb-next'' the version ''4.4.3'' and the version ''4.4.4''.

False. Even with an AUR helper, it installs universe/ckb-next 0.4.4-4:

Code: [Select]

$ pikaur -S ckb-next
Reading repository package databases...
Reading local package database...

:: Third-party repository package will be installed:
 universe/ckb-next                                          -> 0.4.4-4

:: New dependencies will be installed from third-party repository:
 libdbusmenu-qt5 (for ckb-next)                             -> 0.9.3+16.04.20160218-5
 quazip (for ckb-next)                                      -> 1.1-1

:: Proceed with installation? [Y/n]
:: [v]iew package details   [m]anually select packages
>>

Make sure you have added universe repo and put Artix mirrors before Arch mirrors in /etc/pacman.conf.
https://wiki.artixlinux.org/Main/Repositories

Re: [SOLVED] Daemon disappeared after update

Reply #7 – 20 October 2021, 10:31:31

If I well understood, by removing the momentary solution with `sudo pacman -Rn ckb-next` (as for other packages too) the daemon is not switched off in `/etc/rc.conf` automatically and also not disabled.

So, installing `ckb-next-openrc`, if a former packages was present, enabled and afterwards uninstalled... appears than two daemons.

As already said, this is also the case of printer-drivers and other packages requires enabling and start.

Honestly, I don't know if there is intention to change this at all and where to change (in pacman or in singular package) but, for sure, such a change make the installation of packages much more comfortable even for new users. Example install.script:

```
if (any ckb-next package is installed)
stop fist daemon, disable daemon, uninstall package
else install ckb-next-openrc, enable daemon, start daemon
```