RE: Issues running TigerVNC on Debian WSL-2

From	<mwoodpatrick@gmail.com>
Newsgroups	linux.debian.user
Subject	RE: Issues running TigerVNC on Debian WSL-2
Date	2022-04-18 13:20 +0200
Message-ID	<EdxAd-9y13-3@gated-at.bofh.it> (permalink)
References	(1 earlier) <EdenU-9mj7-3@gated-at.bofh.it> <Edhvr-9oiJ-1@gated-at.bofh.it> <Edhvr-9oiJ-5@gated-at.bofh.it> <Edj4d-9p3P-1@gated-at.bofh.it> <Edlpn-9qy6-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Definitely not due to a full filesystem

Regards

Mark

-----Original Message-----
From: Greg Wooledge <greg@wooledge.org> 
Sent: Sunday, April 17, 2022 3:16 PM
To: debian-user@lists.debian.org
Subject: Re: Issues running TigerVNC on Debian WSL-2

On Sun, Apr 17, 2022 at 03:44:33PM -0400, The Wanderer wrote:
> I don't think this is something he broke himself; from the little I've 
> found, this appears to be something that's recommended or even 
> required for WSLg (the Windows Subsystem for Linux GUI) to work.

*shudder*

> > (You've also forgotten the sticky bit on your mounted directory.)
> 
> While that's certainly not ideal, I can't see how it could cause the 
> exhibited behavior in this case; from what I can find reading up on 
> the sticky bit to refresh my memory, having it unset should just 
> result in being able to do *more* things with/inside the directory 
> than would be the case if it were set.

Well, some applications may check the permissions on the directory, see that
they are set wrong, and refuse to operate.  I have no idea whether their VNC
server is one of them, but there's certainly precedent.

But as soon as I saw they had made a symlink from a standard location to a
nonstandard location, I *immediately* thought of AppArmor, because that has
been an issue so many times in the past with so many apps.

I don't know precisely why the EAGAIN errno is happening, but it isn't
EACCES so it's not a direct refusal by file system permissions, and it's not
EPERM so it's not a direct refusal for not being superuser.  It's also not
ENOSPC (disk full), so I don't think it's due to a full file system, but it
doesn't take much effort to check that, so I would check anyway.

Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Issues running TigerVNC on Debian WSL-2 <mwoodpatrick@gmail.com> - 2022-04-17 16:40 +0200
  Re: Issues running TigerVNC on Debian WSL-2 Greg Wooledge <greg@wooledge.org> - 2022-04-17 16:50 +0200
    RE: Issues running TigerVNC on Debian WSL-2 <mwoodpatrick@gmail.com> - 2022-04-17 20:10 +0200
      Re: Issues running TigerVNC on Debian WSL-2 Greg Wooledge <greg@wooledge.org> - 2022-04-17 20:10 +0200
        Re: Issues running TigerVNC on Debian WSL-2 Mark Wood-Patrick <mwoodpatrick@gmail.com> - 2022-04-17 20:20 +0200
        Re: Issues running TigerVNC on Debian WSL-2 The Wanderer <wanderer@fastmail.fm> - 2022-04-17 21:50 +0200
          Re: Issues running TigerVNC on Debian WSL-2 Greg Wooledge <greg@wooledge.org> - 2022-04-18 00:20 +0200
            Re: Issues running TigerVNC on Debian WSL-2 The Wanderer <wanderer@fastmail.fm> - 2022-04-18 02:20 +0200
              RE: Issues running TigerVNC on Debian WSL-2 <mwoodpatrick@gmail.com> - 2022-04-18 13:20 +0200
            RE: Issues running TigerVNC on Debian WSL-2 <mwoodpatrick@gmail.com> - 2022-04-18 13:20 +0200

csiph-web