[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a606463e-7139-b2d4-e2cf-eef2ec38bf10@gmail.com>
Date: Tue, 18 Oct 2022 08:38:26 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Phillip Lougher <phillip.lougher@...il.com>
Cc: Phillip Lougher <phillip@...ashfs.org.uk>,
regressions@...mhuis.info, mirsad.todorovac@....unizg.hr,
linux-kernel@...r.kernel.org, marcmiltenberger@...il.com,
regressions@...ts.linux.dev, srw@...dewatkins.net
Subject: Re: BISECT result: 6.0.0-RC kernels trigger Firefox snap bug with
6.0.0-rc3 through 6.0.0-rc7
On 10/18/22 00:25, Phillip Lougher wrote:
>> Sorry for speaking late about my triggering cause.
>>
>> As the background, on my Debian 11 computer, I have lxd snap installed.
>> I use lxd to channel my sysadmin side by spinning up containers and
>> installing server applications there (LAMP, email, DNS).
>>
>> Back to triggering cause. I can trigger the regression when the network
>> connection drops (when Firefox shows connection problem page). Then
>> I run `lxd list` to list container instances and I get the Verneed
>> regression error.
>>
>
> This appears to be both deterministic, and appears to show something
> happening in the Firefox snap triggers an error in the Lxd snap.
>
> This will then not be a Squashfs issue. Firefox running in one
> Squashfs filesystem
> can't trigger a failure in another Squashfs filesystem. This has to be caused
> by something else.
>
Hi Phillip,
My Firefox runs from upstream tarball (not via snap), so the problem may lie
on snapd itself.
Thanks.
--
An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists