Jump to content
Sign in to follow this  
Alexandra

Kaspersky Password Manager Beta for Mac. Important information.

Recommended Posts

Section 1. Downloading, installing, and getting started with the beta version of Kaspersky Password Manager for Mac

Beta specifics:

Important! Create a new My Kaspersky account on beta.ucp.kaspersky-labs.com and use it for the beta testing only. Delete the beta account after the beta testing is over.

How to get the beta version of the application

Download and open the PKG file of the beta version of Kaspersky Password Manager for Mac using the link in the topic for a corresponding version.

Important! After installation is completed, you must create a new My Kaspersky account. You can’t use the application without connecting to My Kaspersky.

The installation specific features:

To install Kaspersky Password Manager, open the PKG file from a relevant topic and follow the instructions of the Installation Assistant.

Uninstalling Kaspersky Password Manager and data deletion

To uninstall Kaspersky Password Manager, quit the application from the application icon and drag Kaspersky Password Manager.app from Applications to Trash.

To delete the local data, delete the following folders:

~/Library/Containers/com.kaspersky.kpmbeta

~/Library/Containers/com.kaspersky.kpmbeta.agent

~/Library/Containers/com.kaspersky.kpmbeta.bl.resolver

~/Library/Group Containers/2Y8XE5CQ94.com.kaspersky.kpmbeta

In case a new beta version of Kaspersky Password Manager is released, you need to delete the application and its data, download the distribution package of the new beta version and install the application.

Attention! Don’t install a new beta version over an old one, unless you are asked to do so.

Attention! Data sync doesn’t work, if you use cloned virtual machines for testing.

Section 2. Sending bug reports 

During the beta testing forum messages are strictly moderated—messages that don’t contain information about bugs will be deleted from topics for bug tracking. 

A bug report must contain the following information:

1. The application build number, the name and version of the OS where the problem appears.

2. If the problem happens regularly, i.e. you can reproduce it.

3. Steps to reproduce the problem.

4. The results that you expect by doing what you’ve been doing.

5. The actual result (e.g. the bug)

6. Traces and dumps of the application performance obtained when the error occurred (see the sections 3.1 and 3.2 below).

7. If a new bug is detected in the GUI of the application, take a screenshot or record a video. A single screenshot or a video is worth a thousand words J

After you send bug reports you may be asked some questions about it (see the section 3). After that, the moderator moves your bug report to a relevant “bug topic” which contains a link to a special table (bug list) in the first post. You will be able to track the status of the error(s) you’ve reported (find out if they were accepted, fixed or rejected) using this table only. The release of a new beta version doesn’t mean that bug(s) you’ve reported have already been fixed—the fix may be delayed or denied. The order in which bugs are fixed is determined by their priority. Priority of a bug depends on its severity.

There is a topic for bug reports and their discussion:

Kaspersky Password Manager for Mac <The application version>.

Section 3. Providing information to Kaspersky Lab developers (the most important part) 

To send required information to the application developers, use the following file sharing services:

1. ftp://data8.kaspersky-labs.com/—logins and passwords for Kaspersky Lab FTP account are sent individually. Old accounts still work.

2. http://files.mail.ru/—you can upload files up to 100 MB without signing in. If you’re are signed in, you can upload files up to 1 GB.

3. http://disk.narod.ru—convenient and fast but requires a Yandex account.

4. The best option to upload a screenshot is to use the forum upload or upload screenshots to http://savepic.ru. Don’t change the size of your image.

 

While testing, the Kaspersky Password Manager may crash or the OS may hang. If this happens unexpectedly, try to remember your last actions:

·         What you did in the application.

·         What you changed in system preferences.

·         Which applications you installed.

Describing the problem, try to recall when it appeared, what the preconditions were, and what you did to fix it.

Describe the problem in details in the forum topic “Kaspersky Password Manager for Mac <application version>”.

Kaspersky Lab specialists may ask you to provide:

1.      Traces—file(s) that contain Kaspersky Password Manager event log, which will help the developers to localize and fix the problem.

2.      Dump files—file(s) where all information about the application state at the moment of a crash is logged.

Attention! In the beta version, traces are turned off by default. To turn on tracing, choose Help > Enable tracing in the application menu.

All trace files are stored in following folders:

·         ~/Library/Containers/com.kaspersky.kpmbeta/Data/Library/Logs/Kaspersky Lab

·         ~/Library/Containers/com.kaspersky.kpmbeta.agent/Data/Library/Logs/Kaspersky Lab

·         ~/Library/Containers/com.kaspersky.kpmbeta.bl.resolver/Data/Library/Logs/Kaspersky Lab

Create a ZIP-archive with trace files and upload it to one of the recommended file sharing services. Make sure to post the name of the archive and the link for downloading it in a relevant topic.

To investigate the reasons of the application crash or hang, the dump file is required. The dump file is a file where information about the application state at the moment of a crash is logged.

You will receive a system notification about a crash and a dump creation.

Dump files are stored in this folder:

~/Library/Logs/DiagnosticReports

After you find the dump files, compress them to ZIP-archive and upload it to any recommended file sharing service.

Make sure to post the name of the archive and the link for downloading it in a relevant topic.

Section 4. General tips.

We recommend using a separate OS or virtual machine for beta testing. Do not test the beta version of the application on computers where your important information is stored. Errors can make the system unstable or lead to data loss in some cases. Do not forget to back up your data.

Do not test the beta version of the application on unstable systems. In this case, it is hard to detect what was the reason of a problem and if this problem is caused by the tested application or not. This is extremely important when the application crashes or hangs. Don’t make a post on forum about a single OS crash or hanging. Keep in mind that this problem can be not related to the application performance. Try to reproduce the problem, first with Kaspersky Password Manager installed, then without it.

Do not confirm or deny the errors found by other beta testers, unless you are asked to do so. Keep in mind that each beta participant has a unique hardware and software configuration, so one tester can discover an error, while another can’t. When publishing a bug report, specify the OS version and the exact build number of the Kaspersky Password Manager beta version.

Before publishing a bug report, try to find it in the “bug list”. There is always a possibility that the bug you have found is already known and published.

Do not ask what’s going on if your bug is still not fixed after update. Every bug has its priority and requires a particular time to be fixed

Share this post


Link to post
Guest
This topic is now closed to further replies.
Sign in to follow this  

×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.