My son was using the computer and it happened. Firefox, just watching a YouTube video.
dmesg -T from anywhere close to time: [Tue Aug 16 23:47:22 2022] snd_hda_codec_hdmi hdaudioC1D0: HDMI: pin NID 0x7 not registered [Tue Aug 16 23:49:03 2022] rfkill: input handler enabled [Tue Aug 16 23:49:04 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [Tue Aug 16 23:49:05 2022] rfkill: input handler disabled [Tue Aug 16 23:50:07 2022] Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 [Wed Aug 17 00:00:02 2022] audit: type=1400 audit(1660712401.679:68): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=955987 comm="cups-browsed" capability=23 capname="sys_nice" [Wed Aug 17 00:19:12 2022] rfkill: input handler enabled [Wed Aug 17 00:19:14 2022] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [Wed Aug 17 00:19:15 2022] rfkill: input handler disabled [Wed Aug 17 00:24:25 2022] snd_hda_codec_hdmi hdaudioC1D0: HDMI: pin NID 0x7 not registered The HDMI output is connected to DVI so those repeating messages in the log relate to no sound output on HDMI. (No duh!) At midnight, the system starts recording Coast to Coast, but the system lost the mouse on Sunday long before that was set to kick off. Oh, and I think there was a question about Wayland or X.org. It is running Wayland. On Tue, Aug 16, 2022 at 8:38 PM Paul Boniol <paul.bon...@gmail.com> wrote: > Unplugging/replugging and trying a different port did not help. I did not > see if there would be any difference plugging it into the front instead of > the back. A reboot did not help (seeing that it didn't respond at all under > Windows regardless of what was running.) I did not try a different mouse > though. The keyboard does continue to function, and is how I continued > using it till I'd get fed up. Yes, it won't happen until we forget about it. > > On Mon, Aug 15, 2022 at 7:32 PM Csaba Toth <csaba.toth...@gmail.com> > wrote: > >> Yea, that's Murphy's law. Whenever it happens again, I'd wonder if >> plugging in-out your mouse would help, or plugging in another pointer >> device. Although if it affects the whole Gnome session... does the keyboard >> still function? Meaning: is the whole Gnome session getting f-ed somehow or >> it's something with the input device section or the USB hub or something... >> dmesg may help whenever it happens again. By Murphy's law we have to stop >> talking about it for it to happen again :D >> >> On Mon, Aug 15, 2022 at 2:12 PM Paul Boniol <paul.bon...@gmail.com> >> wrote: >> >>> Csaba: If I understand correctly, no, it is only within the Gnome >>> session while Brave is running (but does affect all programs running under >>> Gnome). Once I exit Brave, the mouse appears to function normally, and once >>> I return to the login screen it also functions normally (but unable to >>> click in Windows if I boot to that). It is a mini-tower, no touch screen or >>> trackpad. Of course it was happening every few minutes last night, but so >>> far today it hasn't since I'm asking the experts 😀, so I can't see any >>> recent dmesg that would be applicable. >>> >>> Howard: It is Ubuntu 20.04. For various issues I experience, I have been >>> thinking about wiping and installing 22.04, or some other flavor of Linux. >>> As far as what I'm running within Gnome, sometimes it happens all >>> by itself. Now under the hood there are various server programs running. >>> MythTV just cause I haven't gotten around to killing it yet, already >>> migrated the videos to Emby (that was a project, even with a DB query!). >>> Emby. X2Go, but no active sessions running, and thinking of killing it as >>> well since I haven't needed it for a while. CUPS. Probably a few other >>> common services. (It does have parts of KDE and Light also installed for >>> various programs.) >>> >>> On Mon, Aug 15, 2022 at 10:38 AM Howard White <hwh...@vcch.com> wrote: >>> >>>> Curious Paul. Seems there is more of a combination problem here. I >>>> use >>>> Brave quite a bit on Ubuntu 20.04 and 22.04 without issues; both on >>>> laptops and desktops. I probably don't run the same mix of >>>> applications. Clearly you are not holding your tongue correctly ;) >>>> >>>> Howard >>>> >>>> On 8/15/22 02:44, Paul Boniol wrote: >>>> > So this seems really weird. It appears that after using Brave browser >>>> > for a while in Linux, the mouse will stop registering any click, not >>>> > only in Brave but usually everything. Sometimes the pointer >>>> disappears, >>>> > but not always. Timing can range from immediately after starting >>>> Brave >>>> > to roughly 30 minutes later. I can't identify anything in common >>>> > triggering it. (Though Gnome's Activities click [tiling of windows] >>>> > appears to definitely cause it.) >>>> > >>>> > There are a few reports of similar to Brave, but all I've seen just >>>> say >>>> > the issue was closed because there were no additional comments after >>>> 30 >>>> > days... >>>> > >>>> > A year or so ago I had disabled hardware acceleration because the l >>>> > browser would just freeze on occasion. I just verified it is still >>>> off. >>>> > I'm not sure of any other setting could effect the mouse? >>>> > >>>> > It doesn't seem to happen if I am not using Brave browser. >>>> > >>>> > It just started happening after a recent update. I can force >>>> reinstall >>>> > of a previous version... (Of course I'm sure it was probably updated >>>> for >>>> > security reasons...) >>>> > >>>> > Any thoughts? >>>> > >>>> > ---Paul. >>>> > >>>> > -- >>>> > -- >>>> > You received this message because you are subscribed to the Google >>>> > Groups "NLUG" group. >>>> > To post to this group, send email to nlug-talk@googlegroups.com >>>> > To unsubscribe from this group, send email to >>>> > nlug-talk+unsubscr...@googlegroups.com >>>> > For more options, visit this group at >>>> > http://groups.google.com/group/nlug-talk?hl=en >>>> > <http://groups.google.com/group/nlug-talk?hl=en> >>>> > >>>> > --- >>>> > You received this message because you are subscribed to the Google >>>> > Groups "NLUG" group. >>>> > To unsubscribe from this group and stop receiving emails from it, >>>> send >>>> > an email to nlug-talk+unsubscr...@googlegroups.com >>>> > <mailto:nlug-talk+unsubscr...@googlegroups.com>. >>>> > To view this discussion on the web visit >>>> > >>>> https://groups.google.com/d/msgid/nlug-talk/CAL9PgS0F4ko8FyFh8mgKo_c0b7f5X%2BQ660Jv81nB%3DvnDbCFf%2Bw%40mail.gmail.com >>>> > < >>>> https://groups.google.com/d/msgid/nlug-talk/CAL9PgS0F4ko8FyFh8mgKo_c0b7f5X%2BQ660Jv81nB%3DvnDbCFf%2Bw%40mail.gmail.com?utm_medium=email&utm_source=footer >>>> >. >>>> >>>> -- >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "NLUG" group. >>>> To post to this group, send email to nlug-talk@googlegroups.com >>>> To unsubscribe from this group, send email to >>>> nlug-talk+unsubscr...@googlegroups.com >>>> For more options, visit this group at >>>> http://groups.google.com/group/nlug-talk?hl=en >>>> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "NLUG" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to nlug-talk+unsubscr...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/nlug-talk/90a24b30-9f4f-2eed-bb6b-a873c0e73a32%40vcch.com >>>> . >>>> >>> -- >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "NLUG" group. >>> To post to this group, send email to nlug-talk@googlegroups.com >>> To unsubscribe from this group, send email to >>> nlug-talk+unsubscr...@googlegroups.com >>> For more options, visit this group at >>> http://groups.google.com/group/nlug-talk?hl=en >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "NLUG" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to nlug-talk+unsubscr...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/nlug-talk/CAL9PgS2oiKDARv7zxdwmtZeF%3D-XKKHL91RqZsG7qNGre-H854Q%40mail.gmail.com >>> <https://groups.google.com/d/msgid/nlug-talk/CAL9PgS2oiKDARv7zxdwmtZeF%3D-XKKHL91RqZsG7qNGre-H854Q%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> -- >> You received this message because you are subscribed to the Google Groups >> "NLUG" group. >> To post to this group, send email to nlug-talk@googlegroups.com >> To unsubscribe from this group, send email to >> nlug-talk+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/nlug-talk?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "NLUG" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to nlug-talk+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/nlug-talk/CA%2BKhHxL%3Da1-Y0eLpb8ons7Ux%3DF8k6z-bEOd%2B8x3sAFMWm52btA%40mail.gmail.com >> <https://groups.google.com/d/msgid/nlug-talk/CA%2BKhHxL%3Da1-Y0eLpb8ons7Ux%3DF8k6z-bEOd%2B8x3sAFMWm52btA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to nlug-talk@googlegroups.com To unsubscribe from this group, send email to nlug-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to nlug-talk+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/nlug-talk/CAL9PgS0sYMSoXQGQmtcpymXy6S39jbCUW_Tp4v8DKUhXEo1%3DKA%40mail.gmail.com.
