Bug 24962

Summary:	Clipgrab does not start from the applications menu
Product:	Mageia	Reporter:	Jose Manuel López <joselp>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	geiger.david68210
Version:	7
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	Clipgrab	CVE:
Status comment:

Description Jose Manuel López 2019-06-16 09:36:29 CEST

Description of problem: Clipgrab does not start from the applications menu


Version-Release number of selected component (if applicable): Mageia 7


How reproducible:Install Clipgrab from Rpmdrake or Konsole. After installed no run from applications menu, but if it is executed from konsole, it starts correctly

Steps to Reproduce:
1. Install Clipgrab
2. Run the application from applications menu.
3. Run the application from konsole

Comment 1 David GEIGER 2019-06-16 10:54:31 CEST

Should be fixed with clipgrab-3.8.2-1.mga7 and also it is now ported to Qt5!

CC: (none) => geiger.david68210

Comment 2 Jose Manuel López 2019-06-16 16:54:09 CEST

The update does not solve the problem

Clipgrab 3.8.2 doesn't start frome the applicationes menu.

This appears in konsole:

[jose@localhost ~]$ clipgrab
Adding Equifax CA certificate
js: Uncaught (in promise) NetworkError: A network error occurred.
js: Uncaught (in promise) NetworkError: A network error occurred.
js: Uncaught ReferenceError: spf is not defined
js: Uncaught TypeError: yt.setConfig is not a function
js: Uncaught TypeError: yt.setConfig is not a function
js: Refused to display 'https://accounts.google.com/ServiceLogin?continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Ffeature%3Dpassive%26hl%3Des%26app%3Ddesktop%26next%3D%252Fsignin_passive%26action_handle_signin%3Dtrue&uilel=3&service=youtube&passive=true&hl=es' in a frame because it set 'X-Frame-Options' to 'deny'.

Comment 3 David GEIGER 2019-06-16 16:58:24 CEST

On my system clipgrab 3.8.2 now start clicking on the applications menu using plasma 5.15.4!

Comment 4 Jose Manuel López 2019-06-16 18:25:36 CEST

Ok, fixed.

I had the application's execution path wrong after updating it.

Resolution: (none) => FIXED
Status: NEW => RESOLVED