[01:59] <lotuspsychje> good morning to all
[05:24] <lotuspsychje> noticed a few bugs on -31 passby in -announce
[05:24] <lotuspsychje> bug #1846857
[05:27] <OerHeks> i had some troubles getting bt headphone back to work, 5.0.0-31
[05:28] <lotuspsychje> to keep an eye on
[06:26] <OerHeks> Confucius: if you have no backup of your important data, it is not important
[06:28] <tomreyn> that's confusing!
[06:29] <OerHeks> Facebook: what do you mean with your data?
[06:30] <tomreyn> they should definitely send clarification requests by e-mail when user data doesn't match the profiling algorithms
[06:31] <tomreyn> help us better understand you and gain a chance to win one of these new apple ipods!
[06:33] <OerHeks> yeah, breaking iboot
[06:33] <lotuspsychje> lol
[06:35] <tomreyn> i've heard so many stories of people who ran into data loss scenarios during "I was at final stages of writing my thesis". maybe that's why i never did it.
[06:35]  * lotuspsychje likes data loss and recover it with photorec :p
[06:36]  * tomreyn likes backups
[06:36] <lotuspsychje> you get even more data back then you needed
[06:37] <tomreyn> i bet that's how facebook does it, too, then
[06:37] <lotuspsychje> haha
[06:38] <lotuspsychje> i wonder how many worms are crawling on FB data centers
[06:38] <lotuspsychje> double windows open
[06:38] <tomreyn> book worms?
[06:38] <lotuspsychje> roflol
[06:39] <lotuspsychje> facebookworm.com :p
[06:39] <lotuspsychje> you found a new biz tomreyn
[06:39] <tomreyn> this sounds like an SEO company
[06:42] <lotuspsychje> ]heh
[08:37] <lotuspsychje> !info linux-image-generic-hwe-18.04 bionic
[08:39] <tomreyn> ah i missed this
[08:40] <lotuspsychje> saw it passby on my system tomreyn, but im still on 5.3
[08:40] <lotuspsychje> hence the flicker bug :p
[08:41] <tomreyn> you have flicker bugs on 5.3 but not on 5.0?
[08:41] <lotuspsychje> the other way around
[08:41] <lotuspsychje> 5.0 flickers
[08:41] <tomreyn> yes that's what i thought how it was
[08:42] <lotuspsychje> i still got your workaround, but im gonna wait till the 5.0 series passby
[08:42] <lotuspsychje> see what 19.10 release brings us
[08:42] <tomreyn> maybe you meant s/hence/due to/
[08:42] <lotuspsychje> tomreyn: with this laptop, im going on early 20.04 devel too so
[08:43] <tomreyn> you seem to enjoy breakage ;)
[08:43] <lotuspsychje> my nuc will stay business LTS :p
[08:44] <lotuspsychje> laptop can taste a lil pre-lts :p
[08:44] <tomreyn> the little bit that half a year is.
[08:45] <lotuspsychje> i like helping the lts releases
[08:45] <tomreyn> but if 19.10 is stable enough and there's no major changes towards 20.04 planned i guess it can be fine
[08:46] <tomreyn> i like the way you're thinking there
[08:47] <lotuspsychje> also i like the progress till final
[11:00] <ducasse> good morning
[11:31] <BluesKaj> Hi folks
[11:46] <lotuspsychje> !isitoutyet
[11:47] <lotuspsychje> !isitoutyet is <reply> Not yet!
[11:47] <jeremy31> We sell no wine before its time
[11:47] <lotuspsychje> lol
[11:48]  * lotuspsychje drinks LTS wine
[11:55] <tomreyn> hmm, 18.04, that's a good year and month
[11:56] <lotuspsychje> lol
[16:58] <TJ-> I despair of users not reporting vital info when complaining things are broken!
[17:05] <tomreyn> yes, that doesn't make things easier ;)
[17:19] <TJ-> tomreyn: sometimes I also think we're being wound up
[17:24] <tomreyn> TJ-: certainly. but i try not too hard to tell those situations apart.
[17:26] <tomreyn> TJ-: unrelated to this, there was someone in #ubuntu a few days ago who had trouble with some not so old toshiba laptop, where the internal keyboard and touchpad would not work at all, and the system also froze during early boot unless we worked around with some boot parameters
[17:26] <tomreyn> this was about the worst user experience i've seen lately.
[17:27] <tomreyn> we didn't really get it fixed. they said they tried several ubuntu releases, none of them worked with the internal keyboard. but windows works out of the box.
[17:27] <tomreyn> i didn't really know how to diagnose thois, though.
[17:27] <TJ-> tomreyn: was that the user trying all sorts of i8042. options?
[17:27] <tomreyn> yes, but not only
[17:28] <tomreyn> i'm trying to find something on the logs, but it's difficult...
[17:28] <tomreyn> * irc logs
[17:28] <TJ-> I think I still have the links from when I was in-channel
[17:28] <tomreyn> he posted a good summary at some point when you weren't around, though
[17:29] <TJ-> Gusj ?
[17:29] <tomreyn> hmm, food first, i'll ping you about it later if i may and can find it on my logs
[17:29] <tomreyn> hmm yes i think so
[17:31] <TJ-> Where I got to with Gusj was suspecting the fnfxd package/service and suggested its service be masked
[17:31] <tomreyn> https://paste.ubuntu.com/p/rTtFm6rs6v/
[17:32] <TJ-> yes, that's the one
[17:33] <tomreyn> hmm i don't remember anything about this 'fnfxd' service, other than it was mentioned at some point, yes. bbl.
[17:33] <TJ-> here's my log http://paste.ubuntu.com/p/bkQfPXWfJ6/
[17:35] <tomreyn> TJ-: is this UTC?
[17:35] <tomreyn> (i'm back actually)
[17:36] <TJ-> not sure; it's weechat, let me see what time it thinks it is now :)
[17:37] <TJ-> UTC+1 a.k.a. BST
[17:37] <tomreyn> i can check how it corresponds to mine, should have the same logged
[17:37] <tomreyn> ah thanks
[17:38] <tomreyn> so Gusj was seeking support on 3 occasions
[17:40] <tomreyn> your chat is from the first occasion
[17:40] <TJ-> It's quite an old system so if there are generic model problems we'd likely have heard of, or found, them by now "DMI: TOSHIBA Satellite C55-A/Portable PC, BIOS 1.40 04/28/2014"
[17:41] <tomreyn> oh right that's actually older than i had remembered
[17:42] <tomreyn> so you think it's more likely a hardware issue? but why would it then work on windows, assuming this statement was true.
[17:44] <TJ-> Well there are a LOT of PCI BAR allocation failures for the 00:1c.* devices, which as far as I recall is a bridge chip, and the ACPI errors with "LPCB" refer to the 'south-bridge' I/O controller's Low Pin Count Bus - commonly used to connected the serial UARTs for keyboard etc.
[17:44] <TJ-> I did suggest they try acpi_osi workaround but don't know if they did. I gave the URL
[17:45] <TJ-> kernel log showing the PC BAR issues around line 408 at http://paste.ubuntu.com/p/5y2bBgCyqX/
[17:46] <TJ-> I wouldn't be surprised to find a BIOS/firmware option has changed to cause this
[17:48] <tomreyn> that's how i understood the LPCB, too. i think Gusj did try acpi_osi, yes.
[17:48] <tomreyn> right, a bad BIOS configuration was something i was wondering about, too
[17:58] <tomreyn> TJ-: i finally got my log done ;) if you're still interested (don't bother if not): http://paste.ubuntu.com/p/Xbp2MNR3R7/
[17:59] <tomreyn> i grep'ed for Gusj|tomreyn  then removed all irrelevant lines, so chats between Gusj and me should be complete, but those between Gusj and others may not be.
[18:00] <tomreyn> time zone is CEST (UTC+2)
[18:10] <TJ-> tomreyn: this thread reports the same problem across multiple Satellite models inc. C55 over several years affecting Windows too, and gives a method for what sounds like a power-off 10-second NVRAM clear procedure:  https://forums.tomsguide.com/threads/toshiba-satellite-keyboard-and-touchpad-dont-work.257867/
[18:11] <tomreyn> TJ-: nice find! i'll pass it on to Gusj in case they'll be around again
[18:26] <tomreyn> i left a message with Gusj via memoserv. Most people miss those, but maybe it'll work this time.