=== himcesjf_ is now known as him-cesjf
[04:09] <Kon-> Hi, after updating the kernel on Bionic, dpkg shows I have both 4.15.0-32.35 and 4.15-32.34 installed
[04:09] <Kon-> https://images2.imgbox.com/1c/20/xLsu5m6M_o.png
[04:10] <Kon-> Package history tells me many 30.32 files were upgraded to 32.34, but then 32.35 files were installed for the first time
[04:17] <Kon-> Here's the package history showing some files were upgraded to 32.34 while 32.35 was also installed https://images2.imgbox.com/4f/5c/lA8G6cNc_o.png
[07:46] <apw> Kon-, no that is showing you you have linux-image-* at 4.15.0-32.35 and linux-image-generic at 4.15.0.32.34 ... the first is always new, the second is upgraded; but they are distinct
[07:47] <apw> the second is the meta package and comes from a different source; it is this that drives installation of the other
[07:47] <apw> this is the mechanism by which it is possible to have >1 kernel installed
=== SimonNL is now known as SimonNL_Afk
=== SimonNL_Afk is now known as SimonNL
=== jdstrand_ is now known as jdstrand
[20:50] <juliank> I'm seeing files disappearing on my btrfs system on 4.17 (a few each day). I guess I'll revert to 4.15 and see if that is affected too. Is there any data I should collect?
[20:51] <juliank> My $HOME is pretty well backed up so I'm not worrying a lot
[20:51] <tsimonq2> Git bisect? XD
[20:52] <juliank> that's with the -6 kernel
[20:53] <juliank> tsimonq2: It needs a day per step...
[20:53] <juliank> roughly
[20:53] <juliank> I see at least one new file disappearing each day
[20:53] <tsimonq2> Ah, I was half joking, but hey :)
[20:53] <juliank> today it ate my keepass keyfile
[20:54] <juliank> now I gotta copy it over again from my other machine :/
[20:54] <juliank> or the backup, I think it has a copy as well
[20:54] <juliank> And the backup server runs ZFS in raid-z2 I think, so that data is fairly safe
[20:59] <tsimonq2> Perhaps try and find a pattern...