Bug 22753

Summary: Kalarm starts but complains about agent time out
Product: Mageia Reporter: Mauricio Andrés Bustamante Viveros <neoser10>
Component: RPM PackagesAssignee: KDE maintainers <kde>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: geiger.david68210, mageia, marja11, ouaurelien
Version: 6   
Target Milestone: ---   
Hardware: All   
OS: Linux   
URL: https://drive.google.com/open?id=1ZuPrSKtQhA4IZTH4d8pdq7j-BLlEdBbE
Whiteboard:
Source RPM: CVE:
Status comment:

Description Mauricio Andrés Bustamante Viveros 2018-03-12 17:09:50 CET
Description of problem:
If the end user tries to start Kalarm, the app opens but complains about agent error

Version-Release number of selected component (if applicable):
17.12.2-1

How reproducible:
Every time

Steps to Reproduce:
Open the kalarm application

Evidence:
Changing to vtty12, after the agent timeout appears, the end users gets the following message

https://drive.google.com/open?id=10x9HFEYVV9Ky2zvg63lNLP03zKoG-2Fj

This evidence is the first line from up to down
Marja Van Waes 2018-03-13 18:22:36 CET

Assignee: bugsquad => kde
CC: (none) => marja11

Comment 1 Nicolas Lécureuil 2018-03-13 23:26:54 CET
is akonadi started ?

CC: (none) => mageia

Comment 2 Mauricio Andrés Bustamante Viveros 2018-03-15 05:39:48 CET
I found that akonadi fails with invalid name

Attaching the latest journald in the following link

After the following line is the plasma desktop enviroment start
sddm[1459]: Session started

https://drive.google.com/open?id=1cgz3zyHjD6WBvEJgP8gnzNPgCyCx991l

I understand that akonadi must start when an application requires it, and because I did not do the procedure to disable it as documented in kde must be started automatically

If you want I can remove all akonadi configuration or remove the user profile to test, because this VM is snapshot
Comment 3 Mauricio Andrés Bustamante Viveros 2018-04-15 15:31:30 CEST
Hi 

I deleted and reinstalled all the MGA6 VM, the issue is reproducible with this new installation, but with 16 version this was not reproducible..... I am deleting the neoser10 user profile from this installation to diagnose incompayibilities between the versions
Comment 4 Mauricio Andrés Bustamante Viveros 2018-04-17 05:08:27 CEST
After two tests I found the resolution

Tests:

Uninstall the 17.X package, restart the computer
Install the 16.X package, install without uninstalling first the 16.X version

The Mageia Control Center, shows error that the package kalarm version 16 is not in the package listing, using dolphin to see the kalarm folder contains while the installation of update is running, I detect that sometimes the ics files are removed and not created after installation, sometimes only one file is created

Resolution (if is required to other user:

Install the 16.X version
Open the app, the app did not start
go to $home/.local/share/kalarm
take a backup of the ics files
Install the newest version
Open the app..... if the files are removed and did not appear after opening the app, close the app and paste the backup files again in the original location

Thanks for all guys... If this workaround is good workaround, please close this... If is not possible and is required a new kalarm version leave it open
Comment 5 David GEIGER 2019-02-18 07:28:44 CET
Is this bug still valid? as we have recently fixed some pkgs like akonadi, kmail, etc...

CC: (none) => geiger.david68210

Comment 6 Aurelien Oudelet 2020-08-16 22:30:50 CEST
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

CC: (none) => ouaurelien
Status: NEW => RESOLVED
Resolution: (none) => OLD