Bug 371628 - If Kalarm started twice it crashes
Summary: If Kalarm started twice it crashes
Status: CLOSED FIXED
Alias: None
Product: kalarm
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: David Jarvie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-24 20:40 UTC by RJ
Modified: 2020-08-17 23:51 UTC (History)
0 users

See Also:
Latest Commit: 6bd68f98d675e30fab24713e63dfe72cdfd6f4f5
Version Fixed In: 16.08.3

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description RJ 2016-10-24 20:40:14 UTC 
First start looks like this: 

kalarm
log_kidentitymanagement: IdentityManager: There was no default identity. Marking first one as default.
log_akonadicore: not referenced  19
log_akonadicore: not referenced  18
Shortcut for action  "newDisplay" "New Display Alarm" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action  "newCommand" "New Command Alarm" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action  "newEmail" "New Email Alarm" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action  "newAudio" "New Audio Alarm" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action  "edit_undo" "О&тменить действие" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Shortcut for action  "edit_redo" "&Повторить" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
log_kalarm: No writable active calendar

Second:
"Message recipient disconnected from message bus without replying"

Reproducible: Always

Steps to Reproduce:
1. Start KAlarm
2. Start second instance of KAlarm
3. Crash

Actual Results:  
crash

Expected Results:  
If Kalarm already running and one tries to start second instance of KAlarm just popup first one.
Comment 1 David Jarvie 2016-10-27 19:39:04 UTC 
I can confirm that KAlarm crashes when a second instance is started. As you say, this shouldn't happen.

The message about "No writable active calendar" indicates that you won't be able to save alarms to disk. This should have been fixed in KAlarm version 2.11.10-5, which will be in KDE Applications 16.08.3. See bug 362962 for details on how to get round that issue with earlier KAlarm versions.
Comment 2 David Jarvie 2016-10-30 18:10:48 UTC 
The crash has now been fixed in KAlarm version 2.11.10-5 (which will be in KDE Applications 16.08.3), by commit 6bd68f98d675e30fab24713e63dfe72cdfd6f4f5 in branch Applications/16.08.

Starting a second instance now pops up the first one if it is running in the system tray, as expected.