[lubuntu-devel] Problem in Lu 20.04 w/ "open file" "dialogue" window showing no contents

[Sai Vinoba]

On Sat, 15 Feb 2020 16:24:06 -0800, Fritz Hudnut <este.el.paz at gmail.com> wrote:

> Chris G:
> 
> Ah, OK, thanks, I think I just recently installed chromium in Lu, and I
> just blithely ran "sudo apt install chromium-browser" in the console and
> when apt loaded the packages I saw the word "snap" but didn't realize the
> implications of it on overall function . . . .  I read your post and a few
> of the others giving other suggestions, are you saying that running your
> command would let the "open file" window show contents . . . on a temporary
> basis?  And so each time I'd want to do a photo upload I'd have to run that
> command, or that is a once and done?
> 
> I don't use chromium too much, but when I want to boost a photo up to IG I
> need that "open file" window to work, possibly trying out a "remove" and
> install from .deb file would clean out snap???  Or can I run "sudo apt rm
> snap"  or use synaptic to remove snap?  Or that would cause significant
> problems??
> 
> That was my long winded way of saying I didn't use "Software Center" to
> install . . . I used apt???  Is that any different in actuality?
> 
> On Sat, Feb 15, 2020 at 4:08 PM Chris Guiver <guiverc at gmail.com> wrote:
> 
> > Hi Fritz
> >
> > Chromium in (L)ubuntu 19.10 up is a snap, and as such runs in a
> > containerized like environment with limited access to your native file
> > system. (it isn't run in classic confinement)
> >
> > You didn't specify which directories you were unable to upload from,
> > but I suspect the confinement rules are why you're having trouble with
> > uploads. I wrote an answer on askubuntu that I'll refer you to
> >
> >
> > https://askubuntu.com/questions/1184357/why-cant-chromium-suddenly-access-any-partition-except-for-home/1184374#1184374
> >
> > The `snap connect chromium:removable-media` command in my linked post
> > will provide access to /mn/t and /media/ directories from within
> > `chromium` which was how I got around my desire to use my existing NFS
> > shares with minimal effort.
> >
> > Chris g.
> >
> > On 2/16/20, Fritz Hudnut <este.el.paz at gmail.com> wrote:
> > > wxl/devs:  ...
> >
> -- 
> Lubuntu-devel mailing list
> Lubuntu-devel at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/lubuntu-devel

Hi Fritz,
After reading this thread I installed Chromium 'snap' on my Lubuntu 20.04. I did not experience anything 'unexpected'.

I have Virtualbox shared folders and my Downloads, Documents, Pictures etc. point to Virtualbox shared folders. Only Desktop, Public, Templates folders are native. With this setup, when I tried to download a picture from internet, I was able to download to local folders which are Desktop, Public, Templates and also directly onto home directory but not inside any of the folders which are links to Virtualbox shared folders (mounted as /media/sf_<sharename>). So that explains confinement I guess. Please note, I did not run into blank folder; I got error message saying I do not have permission to access those folders. Once I tried snap connect command mentioned by Chris, I was able to download to shared folders as well. 

Same with uploading. On fresh install with default setup, I was able to upload from my native folders but permission issue with shared folders. Once snap connect command was used, was able to upload from shared folders as well. As a test I'm attaching a photo (wallpaper by Vasanth as posted on Lubuntu wallpaper contest page; random pick) from one of these shared folders. I am able to open file manager, select and attach the photo.

You mentioned that you tried on UMate, openSUSE and Manjaro but same issue. I too have UMATE 20.04 and openSUSE Tumbleweed. While in Ubuntu MATE, the chromium is a 'snap', it is normal rpm package in openSUSE! I'm thinking it will not be a snap on Manjaro as well, because it is based on Arch and they prefer their traditional packaging. 

>From what I tried and the fact that you have same issue in Lubuntu, UMATE, openSUSE and Manjaro, I am very positive that it is NOT a 'snap' package issue. 

Now, I did not try uploading on Instagram (I do not have an account). Based on the what you mentioned, that it needs a workaround (user agent manipulation) to upload to Instagram from desktop, I am assuming it would be an issue with Instagram access or Chromium-Instagram connection, or some proprietary plugins etc. rather than an issue with distribution or packaging.


Regards,
Sai
-------------- next part --------------
A non-text attachment was scrubbed...
Name: e62339c4abb2623c4d86d5e55e82c9feb6e72aff.jpeg
Type: image/jpeg
Size: 746608 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/lubuntu-devel/attachments/20200219/bc6b1671/attachment-0001.jpeg>