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

[Fritz Hudnut]

Chris:

User, OK, so am I, can't remember if I saw your name in the ancient "PPC"
days of yore, or not . . . .  But, subsequent to my last email I used
Software Center to remove chromium, because I couldn't get to the Downloads
directory in either U-Mate or Lu 20 . . . and then I tried to manually
download it trying to use Gdebi, but the file was a .zip file and
extracting it just put a directory on my desktop . . . and I ran out of
time on it.

I might try later on to download it as .deb file, there was a command in
your thread that someone used, but I wasn't sure if that brings in chrome
or chromium, generally I wanted chromium . . . but for the purpose of
getting pics up on IG, whatever works would suffice.

Appreciate the conversation on it.

F

On Sat, Feb 15, 2020 at 9:55 PM Chris Guiver <guiverc at gmail.com> wrote:

> The `snap connect` command doesn't need `sudo` to run, it'll open a
> dialog box asking for user permission (in order to elevate
> privileges).
>
> I would run snap commands without `sudo`` so anything that needs user
> level permissions will still have them, where as if `sudo` is used it
> may mean you'll need `sudo` for all features to operate. Removing the
> snap, and installing it correctly without `sudo` should resolve this.
> Sorry I don't know how `sudo` will impact chromium nor what it's
> effects will be.
>
> Loading or saving to a ~/Downloads directory (ie.
> /home/guiverc/Downloads/ for my box) should not require the snap
> connect to operate; as a users $HOME directory should be accessible
> for any snap I believe. As stated in my last paragraph, I'd be tempted
> to remove the chromium & start agin without using `sudo` (except for
> the `apt install` which does require sudo).  The other thing I'd check
> (probably first) is the owner of the ~/Downloads/ directory, and
> probably files in that directory, to ensure they are owned by you &
> not 'root' from a prior errant `sudo` command).
>
> Your alternative is to wait to see if a developer with more knowledge
> than me (I'm a user) provides other alternatives. Because wrong use of
> `sudo` can create problems, I tend to err on the side of caution & not
> use it unless I know it's required, or I get errors (such as enter
> `apt install cowsay` without sudo) which ~clearly hints at elevated
> privileges being required ("are you root?" for my apt install
> example).
>
> Chris g.
>
> On 2/16/20, Fritz Hudnut <este.el.paz at gmail.com> wrote:
> ...
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/lubuntu-devel/attachments/20200216/b72028b1/attachment.html>