[00:16] <zerothis> well, after a more complete investigation, I realize that xwiimote takes my controller options out of the hands of cwiid devs who have no longer update cwiid but have otherwise never bothered me and into the hands of Xorg devs who have given me over 20 years of grief. Also xwiimote is complete only for developers & not end users. So, back to cwiid.
[00:41] <Jbmorris289> I hope my question still in history...
[11:02] <zap0> hi,  i have lubuntu on a acer netbook..  it's awesome!    i've got a old acer laptop Pentuim-M.. 32bit..   what's the chances i can get it to run lubuntu ?
[11:02] <zap0> here is the spec:    https://www.cnet.com/products/acer-aspire-1694wlmi-15-4-pentium-m-760-win-xp-home-1-gb-ram-100-gb-hdd-series/specs/
[11:04] <antis> can you check with the lubuntu 16.04 lts live dvd (or alternatively boot-stick)?
[11:04] <antis> -> 32-bit version of course
[11:07] <zap0> good idea!    i'm torrenting the latest lubuntu now..   is the live-cd version different?
[11:08] <zap0> im getting this one:   http://lubuntu.net/   the 1st link,  the:  [Download lubuntu (Intel x86) desktop CD]
[11:08] <zap0> i'll try to put that only a USB stick
[11:09] <zap0> that one/
[11:09] <zap0> should i be trying 16.04  and not 17.04 ?
[11:10] <antis> btw. why lubuntu.net still does not redirect to http://lubuntu.me/ ??
[11:10] <zap0> .net  sounded more official than  .me   and google returns it higher in the results
[11:10] <antis> zap0, 16.04 (LTS = Long Term Support)
[11:11] <zap0> ok,  but is 17.04  for such an old laptop more risky?
[11:11] <antis> this question goes to the web-designers :)
[11:16] <antis> zap0, it depends. if you plan to maintain a laptop e.g. for a friend, then it is a bad idea to go with the unstable versions. especially with the unstable versions you should urgently backup your important data in case you render your system unusable - experience… ^^
[11:18] <zap0> it's an idle laptop i have, for me, for personal use.    1) has win-XP on it and none of my data.    2) it's for me.    3) i have a spare laptop HDD, so might test it on that first, so i don't render the current working winXP on it dead.
[11:18] <zap0> not that i could ever see myself ever wanting to do ANYTHING in xp..   at least all the peripherals still work.
[11:20] <zap0> i suppose a live-CD would be a good test without the need to remove the current win-xp HDD
[11:30] <antis> if your HDD is big enough, you can start with a parallel installation (so XP is kept alive). You can chose it from installation CD/DVD. However, the 16.04 version is more "safe" to use. And regardless of all that: You should backup your important stuff. One oportunity to do regular backups is the "BackInTime" tool. :)
[12:05] <zap0> the live-USB booted :)      teh sound icon appears, but the option below it "sound settings", when clicked, does nothing.
[12:06] <zap0> am i to presume that means i need a specific sound driver
[12:09] <antis> hm… not sure. have you tried playing a sound file? please also check all the controls in alsamixer
[12:13] <zap0> i plugged in a ethernet cable.   the thing registered that it was ether.. and said something similiar,  but the browser can't surf the net.   the DHCP assigned an IP.   i can see in the dialog it got an IP
[12:14] <zap0> im a bit new to commandline stuff for linux...  what do i use to query the current state of the network connectins/ether?
[12:15] <zap0> i put an additional DNS IP into the network connections dialog,  but that didn't seem to help it's ability to surf
[12:17] <antis> when using wlan (wifi) you might check with: nmcli devices wifi
[12:17] <zap0> i can ping other boxes on our lan.
[12:17] <antis> this will output the available wifi networks
[12:18] <zap0> currently thought trying to get the ether to work would be an easier task than the wifi
[12:19] <antis> it is easy! :P
[12:20] <antis> sorry, I am too much into more "advanced" stuff… you can right click on the icon and see available wifi hotspots right from the task bar
[12:20] <zap0> w00t!  i surfed to a web server on our LAN via IP address.. and it played sounds!    so audio works.    but DNS currently doesn't.
[12:22] <antis> zap0, cool :)
[12:24] <antis> You should not fiddle with custom settings in network unless you have a very special setup! do you have a lan (cable) or a wireless connection?
[12:28] <antis> in terminal, you can check settings via "ifconfig". however you should see the same in NetworkManager -> Taskbar->Settings->Network-Connections
[12:40] <antis> zap0, still with me? :)
[12:41] <zap0> it's in the other room, I'm back and forth.    DVD drive works, ether works, wifi works, sound works!  so far so good!
[12:42] <antis> hehe, awesome
[12:42] <zap0> browser still can't resolve anything..  DNS?!?
[12:43] <zap0> is there a command line app for testing DNS..  i only know of curl, but that doesn't appear to be installed.
[12:44] <antis> the most simple way to test it: ping some.url.com
[12:44] <antis> alternatively you can use the browser
[12:45] <antis> this is not of any problem at all. it's only your network configuration is messed up.
[12:46] <antis> you might simply reboot (thus reset the live system's settings) and it might work.
[12:47] <zap0> ping  google.com  didn't work, tried a few others.. including our ISP..  didn't work.
[12:48] <antis> yeah, think so :)
[12:49] <antis> your connection (ipv4 i guess) should read something like "Automatic (DHCP)". If this is not set, it will not work unless you define the gateway as your DNS server (e.g. something like 192.168.1.1).
[12:52] <antis> you can check with the NetworkManager tool
[12:58] <zap0> i'm completely baffled.  i don't understand how i get DNS to work
[12:58] <zap0> i've tried DHCP.   i tried manual with all the settings that im fairly confident are correct.
[12:59] <zap0> i can ping google servers via IP address.
[13:01] <antis> yep, because the Domain Name Server (DNS) is not found in your network :) -> you can try and set it to e.g. "8.8.8.8" manually on the live system. or you can simply install and be happy everything works fine afterwards. :)
[13:07] <zap0> i tried manually setting our ISP's DNS.. and it doesn't work.
[13:07] <antis> so what?
[13:08] <antis> if your network works fine, why bothering about a misconfigured dns?
[13:08] <zap0> because i want to know that it works.
[13:09] <zap0> im not installing something where the DNS doesn't even work
[13:12] <antis> well… it works.
[13:13] <antis> what happens is: the name "google.com" is looked up on a DNS server (which has to be reachable via IP!). it is common, that the router also provides a DNS mapping, which redirects and syncs with another online server (8.8.8.8 is the google DNS). However, if you configure that manually, it will not work unless you know exactly how your network has to be configured. :)
[13:13] <antis> So, you might be just happy by rebooting your computer into the live system.
[13:14] <antis> Then open firefox, open the website of choice and be happy.
[13:16] <zap0> im not sure what you mean;  is the DNS settings going to magically start working just be rebooting?
[13:16] <antis> yep!
[13:16] <antis> it will reset your settings to "automatic", which is the default.
[13:21] <zap0> that hasn't helped.
[13:26] <antis> zap0, please enter in terminal: ifconfig
[13:26] <antis> what does it output for "eth0" and "wlan0"?
[13:26] <antis> the second line on each block should read something like "inet address:…" if this shows you IP different from 192.168.… there's a problem with your router configuration.
[13:26] <zap0> ifconfig is not installed.   can't install anything cause apt-get needs to use DNS to resolve addresses.
[13:27] <antis> nah… ifconfig is available on the live system
[13:27] <zap0> my router is likely not the issue... it's got 5 other machines, including  lubuntu netbook running on it just fine.
[13:27] <antis> so, what is your ip address?
[13:29] <zap0> it got a DHCP from the router, and it was as expected  the x.x.x.  was good and the .x  was very much the next in line given the number of other machines on the network.
[13:29] <antis> so is it something like 192.168.27.11?
[13:29] <zap0> the gateway ip says  x.x.x.1  (as expected, same as the other machines on our network)
[13:29] <zap0> yes
[13:30] <antis> ok, then you seem to have an ip assigned. now can you do "ping 8.8.8.8"?
[13:30] <zap0> i do understand about basic network;  i don't know much about linux and how it is configured.
[13:31] <zap0> yes.  i can ping  local boxes,  our router, our ISP's DNS, 8.8.8.8
[13:31] <antis> if you understand about basic network, you should also know about how to configure a DNS.
[13:31] <antis> so now you can't ping google.com?
[13:32] <antis> (works fine here btw.)
[13:32] <zap0> correct,  i try to ping google.com  and it returns  ``Name resolve not working``  or something similar.
[13:33] <zap0> i see lots of old posts on the interwebs/Stackoverflow.. saying  edit  /etc/resolv.conf
[13:33] <antis> check the output of the following: cat /etc/resolv.conf
[13:33] <zap0> but then some newer ones, saying that is not required anymore
[13:34] <zap0> ok.  back in a moment... in the meantime... look at this post with 33 votes:   https://askubuntu.com/questions/368435/how-do-i-fix-dns-resolving-which-doesnt-work-after-upgrading-to-ubuntu-13-10-s
[13:34] <zap0> that make sense?
[13:34] <antis> you should not actually edit this file (read the warning in the file!).
[13:35] <antis> you can try it however - doesn't break anything
[13:38] <zap0> in /etc/resovle.conf   it had  127.0.0.53     and some comments about looking at systemd-res..--status   which has piles of misc stuff..  but the very last line from the systemd  thingy had our routers x.x.x.1  address (which it must have gotten during DHCP, as i've not told it that).
[13:39] <zap0> teh router is setup to use the ISPs DNS. that's how all the boxes on the LAN get there DNS by just asking the router x.x.x.1   (so i know they router is very capable of forwarding DNS requests)
[13:40] <antis> ok
[13:41] <zap0> so should i look at this etc/NetworkManager.conf  file and edit that, like in that link above?
[13:42] <antis> i would not do so
[13:42] <antis> but it won't break anything at least
[13:42] <antis> :)
[13:43] <antis> your /etc/resolv.conf file should also read a line like "search …"
[13:44] <zap0> teh  /etc/NetworkManager/NetworkManager.conf  had trivial stuff in it that didnt' even look like that post.
[13:45] <zap0> the /etc/resolve.conf only has  1 line:   nameserver 127.0.0.53
[13:45] <zap0> (and some comment descrip lines).. but not and commented out lines.
[13:46] <zap0> but not any commented out lines.
[13:46] <antis> ah ya know what? i have an idea of what your problem might be… ^^
[13:48] <antis> you told me you running multiple laptops, right? does any of them have the same domain name like the "new one"?
[13:48] <antis> you get that by taking a look into "cat /etc/hosts"
[13:49] <zap0> teh only other linux is the a netbook running lubuntu too.  but it's off and not been on the network for about 24hrs.
[13:52] <antis> that doesn't matter -> it is registered with an ip address for the same name in the DNS lookup table in the network gateway… ^^ You can try and change your domain name in the live system.
[13:54] <antis> I need to look it up, because it's been some time. Basically you open the file "/etc/hosts" with a text editor. Now lookup the line containing "172.0.1.1" and change the host name. From Terminal you can do that by the following command:
[13:54] <antis> sudo leafpad /etc/hosts&
[13:55] <antis> After that, you need to restart the network service. Wait a second…
[13:59] <zap0> i've been trying re-starting network service.
[13:59] <zap0> i've tried  wifi
[13:59] <antis> that would not work
[13:59] <zap0> and i've tried wired.
[13:59] <zap0> none of them seem to work.
[13:59] <antis> change your hostname
[13:59] <zap0> where?
[13:59] <antis> ah, the other file is called "/etc/hostname"… and then i found it
[14:00] <antis> sudo hostnamectl set-hostname some-host-name
[14:00] <antis> now "ping your-host" should work
[14:05] <antis> ok, one thing to do after changing the hostname via "hostnamectl" command:
[14:05] <antis> Also change the entry reading "127.0.1.1" in "/etc/hosts" to point to your new hostname.
[14:05] <antis> Should read something like "127.0.1.1    my-new-hostname"
[14:08] <antis> Please note, this is only temporary to make it work for the live system. As a general hint: You should always chose a hostname different from the default during installation to avoid name clashes.
[14:08] <zap0> the hostname appears to be lubuntu
[14:09] <zap0> i  have nothing on the network even remotly like that name
[14:10] <antis> what does /etc/hostname include?
[14:11] <antis> you set the names btw.
[14:14] <zap0> im just at the point now were im losing complete faith in this OS..  like wtf.. how can setting an IP address fail so bad
[14:15] <antis> then ditch it :)
[14:15] <antis> the problem however is not the os
[14:16] <zap0> who is it then?
[14:18] <antis> it is you - sorry, i have to say that… :)
[14:19] <antis> there is absolutely no problem with the installation , the live system or anything. everything works perfectly… the dns config is always on your side. same is valid for any other os btw.
[14:20] <antis> when running more than one device with whatever os on it in a network, you should actually learn about trouble shooting.
[14:21] <zap0> can you see how i can't take what you say as right, cause " there is absolutely no problem with the installation"    yet i can here without name resolution.
[14:21] <antis> so where is the problem?
[14:21] <antis> it is your network configuration, right?
[14:22] <antis> the installation provides you chance to set the hostname. if you chose same name twice, funny stuff can happen…
[14:22] <zap0> i don't know.   but i have multiple machines on the network work fine.  i have a netbook running lubuntu that can use DNS just fine.   i have tried MANY configs now, and many alternative dns.. (my router, the ISP, 8.8.8.8)
[14:24] <zap0> i google the problem and there are piles of results or people with same issues
[14:24] <antis> hehe
[14:24] <antis> so, you think this is an issue wiht the distro?
[14:26] <zap0> this seems to sum it up:  https://ubuntuforums.org/showthread.php?t=2356729
[14:26] <zap0> starting to smell like 17.04 sepcific fuck ups
[14:26] <zap0> specific/
[14:26] <antis> hm… you tried with 17.04?
[14:27] <zap0> the iso i downloaded from lubuntu.net  was 'latest'
[14:27] <antis> so why didn't you listen and use 16.04?
[14:27] <zap0> i think it's 17.
[14:31] <zap0> if you're going to take that tone, then i'll make a similar remark in teh same tone:  wtf is up with releasing a OS and promoting it on the front page if it's still so broken that it can't even get DNS settings right.     that's a pretty fundamental thing for a OS.. it's not like you can do anything without DNS
[14:31] <antis> same question here: why does lubuntu advertise the latest version so much?
[14:33] <antis> have you read the full comment? "…When I add 8.8.8.8 to  Additional DNS Servers name lookup works…"
[14:33] <zap0> i tried that.  it didn't work.
[14:34] <antis> well… to me this doesn't sound like a bug…
[14:35] <antis> but… give me few minutes. i will download an boot lubuntu 17.04 live dvd and see how it goes here
[14:36] <zap0> torrenting 16.04 now..
[14:36] <zap0> the website designer for the torrent link needs to get his hipster glasses fixed.
[14:36] <antis> :) doing the check with 17.04
[14:41] <zap0> i read in one forum..  no idea if even related, but.. said something like:  `bug might be related to ifup detecting ipv6 on first boot and then screwing something up`
[14:41] <zap0> no idea if that would be relavent to you testing
[14:49] <antis> dear lubuntu team: why do you advertise the 17.04 (or latest in general) version so much? i'd rather like to see the 16.04 (LTS) version as default download and 17.04 for those, who like to try out the new stuff.
[14:53] <zap0> yes.  it should say:  17.04  is a bit bleedying edge, use at own risk.
[14:55] <antis> i cannot actually test core processes like ifup/ifdown, but i want to see with my own eyes, that this is a problem in the driver (kernel module). if so, i am very sorry for my rudeness above…
[14:58] <zap0> i care not for artificial politeness nonsense.  at that point, you were probably right to think the issue was my noobness.   it still might be, (althougth i doubt it).  i care more about getting it working then possibly looking like a moron.
[14:58] <zap0> feel free to say it as you see it.
[14:59] <zap0> the 16.04 usb is done.... going to other room to boot the 16.04... back in 5.. maybe 10
[15:00] <antis> ok, need some minutes to burn 17.04 image
[15:05] <zap0> antis,  16.04 booted... it messed up the screen res big time!  could hardly see the UI..  but after 4 attempts.. guessed a drop down entry that might work.. and it reset at 1024x768 and was readable again!  anyhoo.. guess what works flawlessly?  DNS !!! ;)
[15:15] <zap0> only the wired connection.  the wifi can now ping IPs but can't resolve names :(
[15:22] <zap0> this one looks quick to skim with step by step fix:     http://www.hecticgeek.com/2017/04/ubuntu-17-04-systemd-dns-issues/
[15:23] <zap0> although no idea how step2 can possibly work if DNS can't resolve the apt-get repo URLs
[15:25] <zap0> it's starting to look more like systemd is to blame..
[15:25]  * zap0 gets on the bandwagon
[15:28] <antis> zap0, hi
[15:28] <zap0> boo!
[15:29] <antis> any news?
[15:29] <zap0> 16.04 wired works.   16.04 wifi doesn't resolve names.    switch back to wired, wired works still.
[15:30] <zap0> that is tiny progress.  but as it's a laptop, i'd like it if wifi could resolve names.
[15:31] <antis> and i'm pretty sure it can. haven't had any such problems with like 6 different netbooks, laptops etc.
[15:33] <zap0> i upgraded the netbook from 12 to 14 to 16 to 17  in 1 day
[15:34] <zap0> it works fine
[15:34] <antis> ok, fine
[15:34] <zap0> so maybe i get 16.04 working, then upgrade to 17 will "just work"
[15:34] <antis> i won't recommend upgrading to 17
[15:34] <zap0> now i agree.
[15:40] <antis> ok. you should know i rendered my system unusable once just because upgrading from 15.04 to 15.10. So what I did is backup and fallback to 14.04 -> worked totally fine. Then no problem upgrading to 16.04, which i think is the best Lubuntu (and debian based distros) so far. However you might have hit that trap and just met a little piece of untested wifi network adapter.