Bug 403463 - Snap install classic mode app does not work
Summary: Snap install classic mode app does not work
Status: RESOLVED DUPLICATE of bug 404358
Alias: None
Product: Discover
Classification: Applications
Component: Snap Backend (show other bugs)
Version: 5.14.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-21 14:48 UTC by Felipe Peter
Modified: 2019-02-28 10:15 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Repeatedly started CLion installation (176.39 KB, image/png)
2019-01-21 14:48 UTC, Felipe Peter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Felipe Peter 2019-01-21 14:48:38 UTC
Created attachment 117594 [details]
Repeatedly started CLion installation

SUMMARY
Discover shows some weird behaviour when I tried to install CLion.

STEPS TO REPRODUCE
1. Search for clion
2. Click install
3. Discover tells me that this snap application needs security confinement measures disabled
4. Click Proceed

OBSERVED RESULT
A new task appears, but nothing obvious happens. Task progress stays at 0%. Furthermore, the Install button is still available. So I can perform the procedure again, which adds a second task that does not progress.

EXPECTED RESULT
The bloody app gets installed. 

I can't remember whether I ever used Discover and it did what I wanted it to do. Please don't get this wrong, I really want the app to be usable, which is why I started submitting bug reports recently, but this app is a showstopper for KDE neon. My father wants to migrate away from Windows and I would love to recommend KDE neon, as I am using it myself (installing stuff from CLI), but I don't dare because of Discover. Sorry, didn't know where to place this rant.
Comment 1 Felipe Peter 2019-01-23 01:25:15 UTC
I tried installing using CLI today and realized that the internet connection to the snap server is horrible at the place I am at. That explains why the task progress seems to be stuck at 0%.

Leaving the points:
1. Why can I start the installation twice?
2. Why does Discover give so little feedback on what is going on compared to CLI? (I will create a ticket for the app download case.)
3. Why can I not close Discover in such cases when the download takes 7h? (see Bug 403465)
Comment 2 Nate Graham 2019-02-06 04:23:36 UTC
Which Linux distro and which version of Plasma or Discover are you using?
Comment 3 Felipe Peter 2019-02-08 15:49:05 UTC
Operating System: KDE neon 5.14
KDE Plasma Version: 5.14.5
Qt Version: 5.11.2
KDE Frameworks Version: 5.54.0
Kernel Version: 4.15.0-43-generic
OS Type: 64-bit
Comment 4 Christoph Feck 2019-02-18 21:46:38 UTC
Information was added with comment #3; changing status for inspection.
Comment 5 Patrick Silva 2019-02-28 10:15:20 UTC

*** This bug has been marked as a duplicate of bug 404358 ***