On Fri, Sep 29, 2017 at 02:15:42PM +0200, Gabriel Paubert wrote:
> On Fri, Sep 29, 2017 at 01:36:19PM +0200, Mathieu Malaterre wrote:
> > On Fri, Sep 29, 2017 at 12:40 PM, Gabriel Paubert <paub...@iram.es> wrote:
> > > On Fri, Sep 29, 2017 at 12:10:20PM +0200, Christian Zigotzky wrote:
> > >> On 29 September 2017 at 11:42AM, Gabriel Paubert wrote:
> > >> > Hi Christian,
> > >> >
> > >> > The right mouse button, i.e., the one that pops up a menu.
> > >> >
> > >> I understand. Yes, you're right. There is a problem. I can open the menu
> > >> but
> > >> selecting a menu point doesn't work. Thanks for the hint.
> > >
> > > Ok, in my case it is way more drastic: SIGSEGV causing
> > > InstantProcessDeath(TM).
> > >
> > > There is a trace in the kernel log, with a blurb about "invalid signal
> > > frame" and not much more.
> > >
> > > This is with v4.13/v4.14 kernels.
> >
> > Could you please report the bug with the content of syslog.
>
> I'm away from the machine until next Friday, and running firefox on
> remote display on a slow link is painful, to put it mildly.
Hmm, well, I just got a very similar Firefox crash on my PB G4 a few minutes
ago:
Sep 30 11:25:23 localhost vmunix: Compositor[5787]: bad frame in
handle_rt_signal32: a2c00b50 nip b5b8037c lr b5b80350
Sep 30 11:25:23 localhost vmunix: Chrome_ChildThr[7685]: bad frame in
handle_rt_signal32: b016de60 nip b54b737c lr b54b7350
I might not have used Firefox for a while on that machine, and it was
updated (Debian stable) earlier this morning.
Gabriel
