Bug 348815 - Won't open
Summary: Won't open
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: mail (show other bugs)
Version: unspecified
Platform: unspecified Microsoft Windows
: NOR grave
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-07 06:34 UTC by Sara
Modified: 2017-01-07 22:26 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sara 2015-06-07 06:34:02 UTC
Maybe I'm an idiot, but I have tried kontact E5 and Kontact 14 both for Windows.  I'm on Win7, and they installed fine, I see kontact in my start menu, but when I click the icon, I get the spinning cursor for about 15 seconds and then nothing happens.  I have tried it with the processes tab of the Task Manager open and no new .exes show in the list, nothing changes.  Nothing in services either.  I've tried also loading the kmail.exe as well as the akonaditray.exe which I heard from another post the kmail program opened for after someone else started, all to no avail.  I'm not sure what I'm doing wrong, but I'd appreciate any feedback.  This PIM/mail program has exactly what I need and I would love nothing more than to be able to use it. 

Reproducible: Always

Steps to Reproduce:
1. Click contact Shortcut, or any .exes from the Kontact folder
2. Wait
3. Check Task Manager for processes

Actual Results:  
Nothing at all. 

Expected Results:  
Something to open
Comment 1 Denis Kurz 2016-09-24 19:22:47 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:26:53 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.