▲ 43 ▼ Ubuntu/Snap Permissions Prompting: A Deep Dive (discourse.ubuntu.com) submitted 3 months ago by novafunc@discuss.tchncs.de to c/linux@lemmy.ml 18 comments fedilink hide all child comments
[–] jdr@lemmy.ml 22 points 3 months ago (2 children) Are they still trying to make snap happen? It's not going to happen. permalink fedilink source hideshow 4 child comments replies: [–] wilmo@lemmy.ml 11 points 3 months ago* (2 children) Its also for my experience the worst way to use apps. The fact that I can't "update" my software without closing it first. Why can I do that with all other package formats? I get it won't be the new version until I reopen the app but still. Its unnecessary friction. Also with the prompting last I used it Firefox couldn't download anything with it enabled. Like you ship Ubuntu with like 4 major snaps including the security center and it hasn't or hadn't worked with your shipped snaps for at least a year? permalink fedilink source parent hideshow 4 child comments replies: [–] caseyweederman@lemmy.ca 7 points 3 months ago* Just wait until you find out about Ubuntu "Oops! All Snaps" Core Edition. permalink fedilink source parent [–] atzanteol@sh.itjust.works -3 points 3 months ago (1 child) The fact that I can't "update" my software without closing it first. Why can I do that with all other package formats? I get it won't be the new version until I reopen the app Asked and answered. permalink fedilink source parent hideshow 2 child comments replies: [–] wilmo@lemmy.ml 3 points 3 months ago (1 child) Not really though? Or rather - then answer the other half. Why are flatpaks, deb, rpm, arch, etc. ALL able to update in place? But with snaps we need that sucker closed? It sucks to use like that. permalink fedilink source parent hideshow 2 child comments replies: [–] atzanteol@sh.itjust.works -1 points 3 months ago (2 children) Because the app isn't updated until it's restarted. Do you think you applied that Firefox security update because you updated the flatpak? Because you haven't if you left your browser running. permalink fedilink source parent hideshow 4 child comments replies: [–] wilmo@lemmy.ml 4 points 3 months ago* (1 child) Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good. I don't care if Firefox isn't updated until I restart it. I just don't want that terrible workflow: Click update all. Firefox is open, therefore won't update until you close it and click update again. Every other package manager: Click update. All apps update. When I am ready to close Firefox it'll be updated next time I use it. permalink fedilink source parent hideshow 2 child comments replies: [–] atzanteol@sh.itjust.works -1 points 3 months ago (1 child) Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good. Hence my "asked and answered" response. 🙄 permalink fedilink source parent hideshow 2 child comments replies: [–] itslilith@lemmy.blahaj.zone 3 points 3 months ago the question asked was "why can't snap do this thing, that every other package manager can" stop being obtuse on purpose. permalink fedilink source parent [–] brax@sh.itjust.works 2 points 3 months ago The problem is that you have to break your workflow to update shit, or you have to do updates multiple times to work around the things you're doing. permalink fedilink source parent [–] thingsiplay@lemmy.ml 7 points 3 months ago Snap is already a big part of Ubuntu since years. So what do you mean by "its not going to happen"? permalink fedilink source parent
[–] wilmo@lemmy.ml 11 points 3 months ago* (2 children) Its also for my experience the worst way to use apps. The fact that I can't "update" my software without closing it first. Why can I do that with all other package formats? I get it won't be the new version until I reopen the app but still. Its unnecessary friction. Also with the prompting last I used it Firefox couldn't download anything with it enabled. Like you ship Ubuntu with like 4 major snaps including the security center and it hasn't or hadn't worked with your shipped snaps for at least a year? permalink fedilink source parent hideshow 4 child comments replies: [–] caseyweederman@lemmy.ca 7 points 3 months ago* Just wait until you find out about Ubuntu "Oops! All Snaps" Core Edition. permalink fedilink source parent [–] atzanteol@sh.itjust.works -3 points 3 months ago (1 child) The fact that I can't "update" my software without closing it first. Why can I do that with all other package formats? I get it won't be the new version until I reopen the app Asked and answered. permalink fedilink source parent hideshow 2 child comments replies: [–] wilmo@lemmy.ml 3 points 3 months ago (1 child) Not really though? Or rather - then answer the other half. Why are flatpaks, deb, rpm, arch, etc. ALL able to update in place? But with snaps we need that sucker closed? It sucks to use like that. permalink fedilink source parent hideshow 2 child comments replies: [–] atzanteol@sh.itjust.works -1 points 3 months ago (2 children) Because the app isn't updated until it's restarted. Do you think you applied that Firefox security update because you updated the flatpak? Because you haven't if you left your browser running. permalink fedilink source parent hideshow 4 child comments replies: [–] wilmo@lemmy.ml 4 points 3 months ago* (1 child) Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good. I don't care if Firefox isn't updated until I restart it. I just don't want that terrible workflow: Click update all. Firefox is open, therefore won't update until you close it and click update again. Every other package manager: Click update. All apps update. When I am ready to close Firefox it'll be updated next time I use it. permalink fedilink source parent hideshow 2 child comments replies: [–] atzanteol@sh.itjust.works -1 points 3 months ago (1 child) Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good. Hence my "asked and answered" response. 🙄 permalink fedilink source parent hideshow 2 child comments replies: [–] itslilith@lemmy.blahaj.zone 3 points 3 months ago the question asked was "why can't snap do this thing, that every other package manager can" stop being obtuse on purpose. permalink fedilink source parent [–] brax@sh.itjust.works 2 points 3 months ago The problem is that you have to break your workflow to update shit, or you have to do updates multiple times to work around the things you're doing. permalink fedilink source parent
[–] caseyweederman@lemmy.ca 7 points 3 months ago* Just wait until you find out about Ubuntu "Oops! All Snaps" Core Edition. permalink fedilink source parent
[–] atzanteol@sh.itjust.works -3 points 3 months ago (1 child) The fact that I can't "update" my software without closing it first. Why can I do that with all other package formats? I get it won't be the new version until I reopen the app Asked and answered. permalink fedilink source parent hideshow 2 child comments replies: [–] wilmo@lemmy.ml 3 points 3 months ago (1 child) Not really though? Or rather - then answer the other half. Why are flatpaks, deb, rpm, arch, etc. ALL able to update in place? But with snaps we need that sucker closed? It sucks to use like that. permalink fedilink source parent hideshow 2 child comments replies: [–] atzanteol@sh.itjust.works -1 points 3 months ago (2 children) Because the app isn't updated until it's restarted. Do you think you applied that Firefox security update because you updated the flatpak? Because you haven't if you left your browser running. permalink fedilink source parent hideshow 4 child comments replies: [–] wilmo@lemmy.ml 4 points 3 months ago* (1 child) Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good. I don't care if Firefox isn't updated until I restart it. I just don't want that terrible workflow: Click update all. Firefox is open, therefore won't update until you close it and click update again. Every other package manager: Click update. All apps update. When I am ready to close Firefox it'll be updated next time I use it. permalink fedilink source parent hideshow 2 child comments replies: [–] atzanteol@sh.itjust.works -1 points 3 months ago (1 child) Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good. Hence my "asked and answered" response. 🙄 permalink fedilink source parent hideshow 2 child comments replies: [–] itslilith@lemmy.blahaj.zone 3 points 3 months ago the question asked was "why can't snap do this thing, that every other package manager can" stop being obtuse on purpose. permalink fedilink source parent [–] brax@sh.itjust.works 2 points 3 months ago The problem is that you have to break your workflow to update shit, or you have to do updates multiple times to work around the things you're doing. permalink fedilink source parent
[–] wilmo@lemmy.ml 3 points 3 months ago (1 child) Not really though? Or rather - then answer the other half. Why are flatpaks, deb, rpm, arch, etc. ALL able to update in place? But with snaps we need that sucker closed? It sucks to use like that. permalink fedilink source parent hideshow 2 child comments replies: [–] atzanteol@sh.itjust.works -1 points 3 months ago (2 children) Because the app isn't updated until it's restarted. Do you think you applied that Firefox security update because you updated the flatpak? Because you haven't if you left your browser running. permalink fedilink source parent hideshow 4 child comments replies: [–] wilmo@lemmy.ml 4 points 3 months ago* (1 child) Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good. I don't care if Firefox isn't updated until I restart it. I just don't want that terrible workflow: Click update all. Firefox is open, therefore won't update until you close it and click update again. Every other package manager: Click update. All apps update. When I am ready to close Firefox it'll be updated next time I use it. permalink fedilink source parent hideshow 2 child comments replies: [–] atzanteol@sh.itjust.works -1 points 3 months ago (1 child) Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good. Hence my "asked and answered" response. 🙄 permalink fedilink source parent hideshow 2 child comments replies: [–] itslilith@lemmy.blahaj.zone 3 points 3 months ago the question asked was "why can't snap do this thing, that every other package manager can" stop being obtuse on purpose. permalink fedilink source parent [–] brax@sh.itjust.works 2 points 3 months ago The problem is that you have to break your workflow to update shit, or you have to do updates multiple times to work around the things you're doing. permalink fedilink source parent
[–] atzanteol@sh.itjust.works -1 points 3 months ago (2 children) Because the app isn't updated until it's restarted. Do you think you applied that Firefox security update because you updated the flatpak? Because you haven't if you left your browser running. permalink fedilink source parent hideshow 4 child comments replies: [–] wilmo@lemmy.ml 4 points 3 months ago* (1 child) Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good. I don't care if Firefox isn't updated until I restart it. I just don't want that terrible workflow: Click update all. Firefox is open, therefore won't update until you close it and click update again. Every other package manager: Click update. All apps update. When I am ready to close Firefox it'll be updated next time I use it. permalink fedilink source parent hideshow 2 child comments replies: [–] atzanteol@sh.itjust.works -1 points 3 months ago (1 child) Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good. Hence my "asked and answered" response. 🙄 permalink fedilink source parent hideshow 2 child comments replies: [–] itslilith@lemmy.blahaj.zone 3 points 3 months ago the question asked was "why can't snap do this thing, that every other package manager can" stop being obtuse on purpose. permalink fedilink source parent [–] brax@sh.itjust.works 2 points 3 months ago The problem is that you have to break your workflow to update shit, or you have to do updates multiple times to work around the things you're doing. permalink fedilink source parent
[–] wilmo@lemmy.ml 4 points 3 months ago* (1 child) Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good. I don't care if Firefox isn't updated until I restart it. I just don't want that terrible workflow: Click update all. Firefox is open, therefore won't update until you close it and click update again. Every other package manager: Click update. All apps update. When I am ready to close Firefox it'll be updated next time I use it. permalink fedilink source parent hideshow 2 child comments replies: [–] atzanteol@sh.itjust.works -1 points 3 months ago (1 child) Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good. Hence my "asked and answered" response. 🙄 permalink fedilink source parent hideshow 2 child comments replies: [–] itslilith@lemmy.blahaj.zone 3 points 3 months ago the question asked was "why can't snap do this thing, that every other package manager can" stop being obtuse on purpose. permalink fedilink source parent
[–] atzanteol@sh.itjust.works -1 points 3 months ago (1 child) Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good. Hence my "asked and answered" response. 🙄 permalink fedilink source parent hideshow 2 child comments replies: [–] itslilith@lemmy.blahaj.zone 3 points 3 months ago the question asked was "why can't snap do this thing, that every other package manager can" stop being obtuse on purpose. permalink fedilink source parent
[–] itslilith@lemmy.blahaj.zone 3 points 3 months ago the question asked was "why can't snap do this thing, that every other package manager can" stop being obtuse on purpose. permalink fedilink source parent
[–] brax@sh.itjust.works 2 points 3 months ago The problem is that you have to break your workflow to update shit, or you have to do updates multiple times to work around the things you're doing. permalink fedilink source parent
[–] thingsiplay@lemmy.ml 7 points 3 months ago Snap is already a big part of Ubuntu since years. So what do you mean by "its not going to happen"? permalink fedilink source parent