Bug 24095 - Mageia Welcome does not replace *Install* button after installation of selected application with *Launch* button
Summary: Mageia Welcome does not replace *Install* button after installation of select...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-30 09:05 CET by Ben McMonagle
Modified: 2019-02-25 19:22 CET (History)
4 users (show)

See Also:
Source RPM: mageiawelcome-1.93
CVE:
Status comment:


Attachments
example of existing application that should have *launch* button (37.97 KB, image/png)
2018-12-30 09:06 CET, Ben McMonagle
Details

Description Ben McMonagle 2018-12-30 09:05:32 CET
Description of problem: Mageia Welcome does not remove *install* button after installation of selected application, likewise, if the application is already installed, the *install* button is still there, eg, if Abiword is already installed as part of the original installation, Mageia Welcome applications does not reflect this, and only offers the *install* button, not *launch* button.
this is different behaviour from Mga6 version


Version-Release number of selected component (if applicable):
mageiawelcome-1.17-1.mga7.noarch


How reproducible: everytime


Steps to Reproduce:
1.install application from Mga7 Mageia Welcome.
2.
3.
Comment 1 Ben McMonagle 2018-12-30 09:06:53 CET
Created attachment 10626 [details]
example of existing application that should have *launch* button
Marja Van Waes 2018-12-31 18:28:08 CET

Assignee: bugsquad => mageiatools
CC: (none) => marja11, yves.brungard_mageia

Comment 2 Ben McMonagle 2019-01-31 07:47:42 CET
still valid Mageia-7-beta2-x86_64
DATE.txt: Wed Jan 30 22:33:06 CET 2019

if, for example you install "gparted" in the above install, because the 
"install" button remains, the user is given the indication that the installation has failed, and will attempt to re-install the application.

If, however, Mageia Welcome is closed and then re-invoked, now the "install" button in this example for "gparted" has changed to "launch"
Comment 3 Lewis Smith 2019-02-01 11:41:21 CET
Classic x64 ISO end Jan: confirm Ben's comment above.

CC: (none) => lewyssmith

Comment 4 papoteur 2019-02-01 22:16:00 CET
(In reply to ben mcmonagle from comment #2)
> still valid Mageia-7-beta2-x86_64
> DATE.txt: Wed Jan 30 22:33:06 CET 2019
> 
> if, for example you install "gparted" in the above install, because the 
> "install" button remains, the user is given the indication that the
> installation has failed, and will attempt to re-install the application.
> 
> If, however, Mageia Welcome is closed and then re-invoked, now the "install"
> button in this example for "gparted" has changed to "launch"

Hello,
When you say "you install "gparted" in the above install", by which way did you the installation of gparted?
Because, I have done some update so that after an installation from the application MageiaWelcome, the list is updated.
Comment 5 Ben McMonagle 2019-02-01 22:26:00 CET
(In reply to papoteur from comment #4)
> (In reply to ben mcmonagle from comment #2)
> > still valid Mageia-7-beta2-x86_64
> > DATE.txt: Wed Jan 30 22:33:06 CET 2019
> > 
> > if, for example you install "gparted" in the above install, because the 
> > "install" button remains, the user is given the indication that the
> > installation has failed, and will attempt to re-install the application.
> > 
> > If, however, Mageia Welcome is closed and then re-invoked, now the "install"
> > button in this example for "gparted" has changed to "launch"
> 
> Hello,
> When you say "you install "gparted" in the above install", by which way did
> you the installation of gparted?
> Because, I have done some update so that after an installation from the
> application MageiaWelcome, the list is updated.

I installed Gparted via the Mageia Welcome install button.

In the Mga6 version, after the install is completed, the Mageia Welcome would refresh, and the "install" button would change to "launch" 

maybe I am not waiting long enough?
Comment 6 Sébastien Morin 2019-02-02 09:22:12 CET
Confirmed here: on a fresh install using the latest round of mga7-beta2 (Jan. 31) I tried to install "mypaint" from MageiaWelcome.
The program is installed but the MW window is not refreshed and the "install" button is not changed into "launch".
If you close MW and run it again, the "launch" button is available next to "my paint".

CC: (none) => sebsweb

Sébastien Morin 2019-02-02 09:23:46 CET

Source RPM: mageiawelcome-1.17-1.mga7.noarch => mageiawelcome-1.93

Comment 7 Lewis Smith 2019-02-02 10:37:14 CET
M7beta2.2 Classic of end Jan x64
Confirm the complaint: I installed from MageiaWelcome Tainted audio codecs, that was quickly done, but the 'install' button remained as before. Re-starting MW, that button was disabled.
Comment 8 papoteur 2019-02-02 10:59:07 CET
Hello,
This is a problem I didn't reproduce :/
This is not easy to solve, in this case.
I can add a small delay (0.5s or 1s) after the end of the installation before to refresh the applications list, but this will not give any warranty that the result will be OK in any case.
Comment 9 papoteur 2019-02-25 08:35:40 CET
Hello,
I found something that can be the source of the problem.
A correction is here since 1.94 release.
Is it OK now?
Comment 10 Sébastien Morin 2019-02-25 19:22:37 CET
Tested with mageiawelcome 1.95.

I Installed mageia-theme-extra: the "install" button was immediately transformed into the indication "installed"
I also installed MyPaint to try it with an application: the "install" button was immediately transformed into the "launch" button.
Can be closed as fixed, imho.

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


Note You need to log in before you can comment on or make changes to this bug.