On 2/18/25 12:21 PM, Daniel P. Berrangé wrote:
On Tue, Feb 18, 2025 at 02:50:52PM +, Daniel P. Berrangé wrote:
On Tue, Feb 18, 2025 at 09:33:43AM -0500, Laine Stump wrote:
On 2/18/25 4:26 AM, Daniel P. Berrangé wrote:
On Mon, Feb 17, 2025 at 03:11:56PM -0500, Laine Stump wrote:
On 2/17/25
On Tue, Feb 18, 2025 at 02:50:52PM +, Daniel P. Berrangé wrote:
> On Tue, Feb 18, 2025 at 09:33:43AM -0500, Laine Stump wrote:
> > On 2/18/25 4:26 AM, Daniel P. Berrangé wrote:
> > > On Mon, Feb 17, 2025 at 03:11:56PM -0500, Laine Stump wrote:
> > > > On 2/17/25 5:28 AM, Daniel P. Berrangé wrot
On Tue, Feb 18, 2025 at 09:33:43AM -0500, Laine Stump wrote:
> On 2/18/25 4:26 AM, Daniel P. Berrangé wrote:
> > On Mon, Feb 17, 2025 at 03:11:56PM -0500, Laine Stump wrote:
> > > On 2/17/25 5:28 AM, Daniel P. Berrangé wrote:
> > > > On Mon, Feb 17, 2025 at 02:14:49AM -0500, Laine Stump wrote:
> >
On 2/18/25 4:26 AM, Daniel P. Berrangé wrote:
On Mon, Feb 17, 2025 at 03:11:56PM -0500, Laine Stump wrote:
On 2/17/25 5:28 AM, Daniel P. Berrangé wrote:
On Mon, Feb 17, 2025 at 02:14:49AM -0500, Laine Stump wrote:
But sometimes XDG_RUNTIME_DIR isn't set in the user's environment.
Do you have
On Mon, Feb 17, 2025 at 03:11:56PM -0500, Laine Stump wrote:
> On 2/17/25 5:28 AM, Daniel P. Berrangé wrote:
> > On Mon, Feb 17, 2025 at 02:14:49AM -0500, Laine Stump wrote:
> > > But sometimes XDG_RUNTIME_DIR isn't set in the user's environment.
> >
> > Do you have examples of scenarios in which
On 2/17/25 3:11 PM, Laine Stump wrote:
On 2/17/25 5:28 AM, Daniel P. Berrangé wrote:
On Mon, Feb 17, 2025 at 02:14:49AM -0500, Laine Stump wrote:
But sometimes XDG_RUNTIME_DIR isn't set in the user's environment.
Do you have examples of scenarios in which this happens, and
yet the /run/user/N
On 2/17/25 5:28 AM, Daniel P. Berrangé wrote:
On Mon, Feb 17, 2025 at 02:14:49AM -0500, Laine Stump wrote:
But sometimes XDG_RUNTIME_DIR isn't set in the user's environment.
Do you have examples of scenarios in which this happens, and
yet the /run/user/ directory is still being created, as
On 2/17/25 5:02 AM, Martin Kletzander wrote:
On Mon, Feb 17, 2025 at 02:14:49AM -0500, Laine Stump wrote:
==
I'm sending this as an RFC just because what it's doing feels kind of
dirty - directly examining XDG_RUNTIME_DIR seems like an "end run"
around the Glib API. If anyone has a better i
On Mon, Feb 17, 2025 at 11:31:32AM +, Richard W.M. Jones wrote:
> On Mon, Feb 17, 2025 at 02:14:49AM -0500, Laine Stump wrote:
> > ==
> >
> > I'm sending this as an RFC just because what it's doing feels kind of
> > dirty - directly examining XDG_RUNTIME_DIR seems like an "end run"
> > aro
On Mon, Feb 17, 2025 at 02:14:49AM -0500, Laine Stump wrote:
> ==
>
> I'm sending this as an RFC just because what it's doing feels kind of
> dirty - directly examining XDG_RUNTIME_DIR seems like an "end run"
> around the Glib API. If anyone has a better idea of what to do, please
> give detai
On Mon, Feb 17, 2025 at 02:14:49AM -0500, Laine Stump wrote:
> But sometimes XDG_RUNTIME_DIR isn't set in the user's environment.
Do you have examples of scenarios in which this happens, and
yet the /run/user/ directory is still being created, as
that rather sounds like something is broken out
On Mon, Feb 17, 2025 at 02:14:49AM -0500, Laine Stump wrote:
==
I'm sending this as an RFC just because what it's doing feels kind of
dirty - directly examining XDG_RUNTIME_DIR seems like an "end run"
around the Glib API. If anyone has a better idea of what to do, please
give details :-)
==
==
I'm sending this as an RFC just because what it's doing feels kind of
dirty - directly examining XDG_RUNTIME_DIR seems like an "end run"
around the Glib API. If anyone has a better idea of what to do, please
give details :-)
==
When running unprivileged (i.e. not as root, but as a reg
13 matches
Mail list logo