[00:56] <n-iCe> I'm staying in xubuntu.
[01:02] <Makerblaker> good idea!
[01:02] <n-iCe> I know.
[01:02] <n-iCe> I have been using it for years, suddenly I get bored and try others distros
[01:02] <n-iCe> And always going back to xubuntu.
[10:06] <gnrp> hm, anybody knows how you can *spontaenously* change the DNS server system-wide with dnsresolv?
[10:16] <gnrp> I mean, like being on a computer, having a connection established, and then wanting (without GUI) to change the DNS server
[10:16] <diogenes_> gnrp, try with dnsmasq
[10:16] <gnrp> diogenes_: Can you replace resolvconf with that?
[10:17] <gnrp> sorry, resolvconf was the name I was meant to say, not dnsresolv
[10:17] <diogenes_> gnrp, it takes over the systemd-resolved
[10:27] <gnrp> Uhm, wanted to thank him, but now it's too late
[16:00] <zoidberg> Hi there
[16:02] <zoidberg> i found a problem with the latest installation media, as when i install from that, the resulting system is broken, it does not come back from sleep (resulting in a black screen) and updating kernels make problems with the resume device not being found
[16:02] <zoidberg> i installed with a crypted lvm
[16:02] <zoidberg> i tested it with 2 thinkpad x230 t with different downloads (the md5 is ok)
[16:02] <zoidberg> and a t410
[16:03] <zoidberg> its all the same with all devices  so it shouldnt be the hardware.
[16:03] <zoidberg> also an older installation which i moved with my disk from my t410 to my x230 works fine (with the same kernel)
[16:04] <zoidberg> these behaviours are really strange
[16:06] <brainwash> which xubuntu release is that?
[16:07] <n-ice> hi
[16:07] <zoidberg> 18.10
[16:11] <zoidberg> brainwash: the 18.10 iso was downloaded via torrent and http mirror
[16:11] <zoidberg> so it is not a problem with the mirror
[16:11] <n-ice> uhm
[16:11] <n-ice> let me read
[16:11] <n-ice> using usb?
[16:11] <zoidberg> yes
[16:12] <n-ice> format it as ext4
[16:12] <n-ice> then use unetbootin to make the usb install
[16:12] <n-ice> then try again
[16:12] <n-ice> is what I would do
[16:12] <zoidberg> i dd the iso to the usb stick
[16:12] <zoidberg> i doubt formating it in ext would make any difference
[16:12] <n-ice> I would try what I said above.
[16:12] <brainwash> it's most likely this bug then  bug 1801609
[16:13] <zoidberg> ah
[16:13] <brainwash> intel gpu related
[16:13] <zoidberg> ok
[16:13] <zoidberg> but its only with new installations
[16:13] <brainwash> possible
[16:14] <zoidberg> also it is not possible to install new kernels, as update-initramfs moans that the resume variable is not set
[16:14] <brainwash> read comment #24
[16:14] <brainwash> it may be the case that the xorg intel driver is not installed
[16:15] <brainwash> so, either replace install/setup the intel driver correctly, or disable or replace light-locker
[16:15] <zoidberg> i have one of those broken systems here
[16:16] <brainwash> for kernel related questions I would suggest to head over to #ubuntu-kernel
[16:16] <zoidberg> i will see if te module is loaded
[16:16] <zoidberg> ok
[16:16] <zoidberg> i will now try 18.04
[16:16] <zoidberg> if that works
[16:17] <zoidberg> and kubunut
[16:17] <brainwash> 18.04 is the LTS release
[16:17] <zoidberg> to rule out that it is a problem with the iso
[16:17] <brainwash> with long term support
[16:17] <zoidberg> i know but i can update from 18.04 to 18.10 if the update doesnt work its something else
[16:17] <zoidberg> as i wrote the update of the initramfs fails as well
[16:20] <zoidberg> now i will try kubuntu 18.10
[16:21] <zoidberg> ah, but that probably doesnt use xorg
[16:21] <zoidberg> :-(
[16:22] <n-iCe> try lubuntu
[16:23] <zoidberg> i am pretty sure there is something wrong with the iso file, but we'll see
[16:24] <brainwash> what problem are you trying to fix?
[16:24] <knome> n-iCe, try #lubuntu (:
[16:24] <n-iCe> why
[16:25] <brainwash> I don't think that switching to kubuntu will solve a kernel related problem
[16:25] <knome> me neither
[16:25] <n-iCe> he wanted to try kubuntu I recommended lubuntu which is lightweight so he can check faster the error
[16:25] <knome> and i'm pretty sure there is nothing "wrong" with the ISO, as the checksum is correct...
[16:26] <knome> n-iCe, the comment was partly ironic.. :P
[16:26]  * n-iCe laughs
[16:26] <knome> and tbh, i don't think changing the flavor - to kubuntu, lubuntu, ubuntu mate or what have you - really helps in this case...
[16:26] <zoidberg> i dont think that this is a kernel related error, if it woirks with kubuntu i have proven that
[16:28] <knome> i don't have the numbers, but i'm pretty sure it's damn hard to match the md5sum of any ISO. given the benefit of doubt, i'm pretty sure something should be much more messed up than this.
[16:28] <knome> the issue you are having isn't exactly an uncommon one...
[16:28] <zoidberg> which one
[16:28] <zoidberg> the waking up one
[16:28] <knome> yes
[16:29] <zoidberg> or the update-initramfs one
[16:29] <knome> let's put it this way: if the ISO was faulty, i'm pretty sure you wouldn't have an installed system at this point
[16:29] <zoidberg> because i could live with the not coming back from sleep for the next 2 or 3 kernels
[16:29] <brainwash> the black screen on resume bug has already been explained
[16:30] <knome> all kinds of things are done to the files on the ISO when installing, so if anything was wrong with the files regarding, say kernels, the installation would have failed
[16:30] <zoidberg> this is what i am wondering about as well, but it is so reproducable
[16:31] <knome> maybe your hardware has some specific common things?
[16:32] <zoidberg> this is what i thouht as well, but i tested it with 2 different thinkpads
[16:32] <knome> yes -- all thinkpads though :P
[16:32] <zoidberg> and even took the hdd from the t410 (xubuntu 18.10) and put it in the x230 and it worked
[16:32] <zoidberg> yes all thinkpads but different cpu and graphics
[16:33] <zoidberg> also what does update-initramfs have to do with the cpu
[16:35] <knome> shouldn't have to do anything -- but again, as we do not know where the issue is, it's just guesswork.
[16:35] <knome> but again, it's unlikely the ISO, because a broken ISO would likely lead to the md5sum not matching -- or the installation failing completely
[16:36] <zoidberg> i dont mean broken when downloading, but broken on the server
[16:36] <knome> you mean "has a bug"?
[16:36] <zoidberg> maybe some commit somewhere broke something
[16:37] <knome> sure, it likely has many bugs ;)
[16:37] <knome> you're the first one reporting this issue.
[16:37] <zoidberg> maybe there are not that many crypted fresh installations...
[16:38] <zoidberg> because it should work as far as i know
[16:38] <knome> 19.04 is coming out very soon, you could try that
[16:38] <knome> well this isn't xubuntu-specific, and i'm sure there are enough similar ubuntu installations that we would have a bug report for this
[16:39] <zoidberg> is it? maybe its a installer bug. i will see. if it doesnt work as well i will report a bug
[16:40] <zoidberg> i could even bisect this problem but nobody got time for that ;-)
[16:40] <knome> due to be released on the 18th
[16:41] <zoidberg> hmmm yea
[16:42] <knome> (the hint is in the version number: 19 for 2019, 04 for april... and releases usually happen around the halfway point of a month)
[16:45] <zoidberg> jap i know but most of the time i dont realize
[16:45] <knome> heh :)
[16:47] <zoidberg> most of the time it is a oh a release, nnnnice
[16:48] <zoidberg> because newer is always better
[16:48] <zoidberg> as new bugs are better than old ones
[16:48] <knome> well, for me it's the "oh it's already april of XX" symptom
[16:48] <knome> or "wait, it's the UI freeze week" panic
[16:49] <knome> not so much lately any more, but historically it has always taken me by surprise..
[16:50] <knome> anyway, time for other adventures... good luck with the issue(s)!
[16:50] <knome> o/
[17:05] <zoidberg> knome: thank you