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

Fritz Hudnut este.el.paz at gmail.com
Sun Feb 16 01:13:08 UTC 2020


Chris, et al:

So I did try running your command as a sudo, and it ran and returned w/o
protest, booting Chromium and running through the sequence brought the same
issue, nothing showing in the Downloads Directory.  Not sure what else to
try after that command, I logged out and back in and tried again--no dice.

F

On Sat, Feb 15, 2020 at 4:24 PM 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:  ...
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/lubuntu-devel/attachments/20200215/6d89b045/attachment.html>


More information about the Lubuntu-devel mailing list