/srv/irclogs.ubuntu.com/2017/05/07/#lubuntu.txt

zerothiswell, 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:16
Jbmorris289I hope my question still in history...00:41
=== Jbmorris289_ is now known as Jbmorris289
zap0hi,  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
zap0here 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:02
antiscan you check with the lubuntu 16.04 lts live dvd (or alternatively boot-stick)?11:04
antis-> 32-bit version of course11:04
=== Rayyan is now known as Guest20413
zap0good idea!    i'm torrenting the latest lubuntu now..   is the live-cd version different?11:07
zap0im getting this one:   http://lubuntu.net/   the 1st link,  the:  [Download lubuntu (Intel x86) desktop CD]11:08
zap0i'll try to put that only a USB stick11:08
zap0that one/11:09
zap0should i be trying 16.04  and not 17.04 ?11:09
antisbtw. 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 results11:10
antiszap0, 16.04 (LTS = Long Term Support)11:10
zap0ok,  but is 17.04  for such an old laptop more risky?11:11
antisthis question goes to the web-designers :)11:11
antiszap0, 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:16
zap0it'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
zap0not that i could ever see myself ever wanting to do ANYTHING in xp..   at least all the peripherals still work.11:18
zap0i suppose a live-CD would be a good test without the need to remove the current win-xp HDD11:20
antisif 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. :)11:30
=== sahumada_ is now known as sahumada
zap0the live-USB booted :)      teh sound icon appears, but the option below it "sound settings", when clicked, does nothing.12:05
zap0am i to presume that means i need a specific sound driver12:06
antishm… not sure. have you tried playing a sound file? please also check all the controls in alsamixer12:09
zap0i 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 IP12:13
zap0im a bit new to commandline stuff for linux...  what do i use to query the current state of the network connectins/ether?12:14
zap0i put an additional DNS IP into the network connections dialog,  but that didn't seem to help it's ability to surf12:15
antiswhen using wlan (wifi) you might check with: nmcli devices wifi12:17
zap0i can ping other boxes on our lan.12:17
antisthis will output the available wifi networks12:17
zap0currently thought trying to get the ether to work would be an easier task than the wifi12:18
antisit is easy! :P12:19
antissorry, I am too much into more "advanced" stuff… you can right click on the icon and see available wifi hotspots right from the task bar12:20
zap0w00t!  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:20
antiszap0, cool :)12:22
antisYou 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:24
antisin terminal, you can check settings via "ifconfig". however you should see the same in NetworkManager -> Taskbar->Settings->Network-Connections12:28
antiszap0, still with me? :)12:40
zap0it's in the other room, I'm back and forth.    DVD drive works, ether works, wifi works, sound works!  so far so good!12:41
antishehe, awesome12:42
zap0browser still can't resolve anything..  DNS?!?12:42
zap0is there a command line app for testing DNS..  i only know of curl, but that doesn't appear to be installed.12:43
antisthe most simple way to test it: ping some.url.com12:44
antisalternatively you can use the browser12:44
antisthis is not of any problem at all. it's only your network configuration is messed up.12:45
antisyou might simply reboot (thus reset the live system's settings) and it might work.12:46
zap0ping  google.com  didn't work, tried a few others.. including our ISP..  didn't work.12:47
antisyeah, think so :)12:48
antisyour 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:49
antisyou can check with the NetworkManager tool12:52
zap0i'm completely baffled.  i don't understand how i get DNS to work12:58
zap0i've tried DHCP.   i tried manual with all the settings that im fairly confident are correct.12:58
zap0i can ping google servers via IP address.12:59
antisyep, 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:01
zap0i tried manually setting our ISP's DNS.. and it doesn't work.13:07
antisso what?13:07
antisif your network works fine, why bothering about a misconfigured dns?13:08
zap0because i want to know that it works.13:08
zap0im not installing something where the DNS doesn't even work13:09
antiswell… it works.13:12
antiswhat 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
antisSo, you might be just happy by rebooting your computer into the live system.13:13
antisThen open firefox, open the website of choice and be happy.13:14
zap0im not sure what you mean;  is the DNS settings going to magically start working just be rebooting?13:16
antisyep!13:16
antisit will reset your settings to "automatic", which is the default.13:16
zap0that hasn't helped.13:21
antiszap0, please enter in terminal: ifconfig13:26
antiswhat does it output for "eth0" and "wlan0"?13:26
antisthe 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
zap0ifconfig is not installed.   can't install anything cause apt-get needs to use DNS to resolve addresses.13:26
antisnah… ifconfig is available on the live system13:27
zap0my router is likely not the issue... it's got 5 other machines, including  lubuntu netbook running on it just fine.13:27
antisso, what is your ip address?13:27
zap0it 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
antisso is it something like 192.168.27.11?13:29
zap0the gateway ip says  x.x.x.1  (as expected, same as the other machines on our network)13:29
zap0yes13:29
antisok, then you seem to have an ip assigned. now can you do "ping 8.8.8.8"?13:30
zap0i do understand about basic network;  i don't know much about linux and how it is configured.13:30
zap0yes.  i can ping  local boxes,  our router, our ISP's DNS, 8.8.8.813:31
antisif you understand about basic network, you should also know about how to configure a DNS.13:31
antisso now you can't ping google.com?13:31
antis(works fine here btw.)13:32
zap0correct,  i try to ping google.com  and it returns  ``Name resolve not working``  or something similar.13:32
zap0i see lots of old posts on the interwebs/Stackoverflow.. saying  edit  /etc/resolv.conf13:33
antischeck the output of the following: cat /etc/resolv.conf13:33
zap0but then some newer ones, saying that is not required anymore13:33
zap0ok.  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-s13:34
zap0that make sense?13:34
antisyou should not actually edit this file (read the warning in the file!).13:34
antisyou can try it however - doesn't break anything13:35
zap0in /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:38
zap0teh 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:39
antisok13:40
zap0so should i look at this etc/NetworkManager.conf  file and edit that, like in that link above?13:41
antisi would not do so13:42
antisbut it won't break anything at least13:42
antis:)13:42
antisyour /etc/resolv.conf file should also read a line like "search …"13:43
zap0teh  /etc/NetworkManager/NetworkManager.conf  had trivial stuff in it that didnt' even look like that post.13:44
zap0the /etc/resolve.conf only has  1 line:   nameserver 127.0.0.5313:45
zap0(and some comment descrip lines).. but not and commented out lines.13:45
zap0but not any commented out lines.13:46
antisah ya know what? i have an idea of what your problem might be… ^^13:46
antisyou told me you running multiple laptops, right? does any of them have the same domain name like the "new one"?13:48
antisyou get that by taking a look into "cat /etc/hosts"13:48
zap0teh only other linux is the a netbook running lubuntu too.  but it's off and not been on the network for about 24hrs.13:49
antisthat 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:52
antisI 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
antissudo leafpad /etc/hosts&13:54
antisAfter that, you need to restart the network service. Wait a second…13:55
zap0i've been trying re-starting network service.13:59
zap0i've tried  wifi13:59
antisthat would not work13:59
zap0and i've tried wired.13:59
zap0none of them seem to work.13:59
antischange your hostname13:59
zap0where?13:59
antisah, the other file is called "/etc/hostname"… and then i found it13:59
antissudo hostnamectl set-hostname some-host-name14:00
antisnow "ping your-host" should work14:00
antisok, one thing to do after changing the hostname via "hostnamectl" command:14:05
antisAlso change the entry reading "127.0.1.1" in "/etc/hosts" to point to your new hostname.14:05
antisShould read something like "127.0.1.1    my-new-hostname"14:05
antisPlease 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
zap0the hostname appears to be lubuntu14:08
zap0i  have nothing on the network even remotly like that name14:09
antiswhat does /etc/hostname include?14:10
antisyou set the names btw.14:11
zap0im just at the point now were im losing complete faith in this OS..  like wtf.. how can setting an IP address fail so bad14:14
antisthen ditch it :)14:15
antisthe problem however is not the os14:15
zap0who is it then?14:16
antisit is you - sorry, i have to say that… :)14:18
antisthere 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:19
antiswhen running more than one device with whatever os on it in a network, you should actually learn about trouble shooting.14:20
zap0can 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
antisso where is the problem?14:21
antisit is your network configuration, right?14:21
antisthe installation provides you chance to set the hostname. if you chose same name twice, funny stuff can happen…14:22
zap0i 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:22
zap0i google the problem and there are piles of results or people with same issues14:24
antishehe14:24
antisso, you think this is an issue wiht the distro?14:24
zap0this seems to sum it up:  https://ubuntuforums.org/showthread.php?t=235672914:26
zap0starting to smell like 17.04 sepcific fuck ups14:26
zap0specific/14:26
antishm… you tried with 17.04?14:26
zap0the iso i downloaded from lubuntu.net  was 'latest'14:27
antisso why didn't you listen and use 16.04?14:27
zap0i think it's 17.14:27
zap0if 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 DNS14:31
antissame question here: why does lubuntu advertise the latest version so much?14:31
antishave you read the full comment? "…When I add 8.8.8.8 to  Additional DNS Servers name lookup works…"14:33
zap0i tried that.  it didn't work.14:33
antiswell… to me this doesn't sound like a bug…14:34
antisbut… give me few minutes. i will download an boot lubuntu 17.04 live dvd and see how it goes here14:35
zap0torrenting 16.04 now..14:36
zap0the website designer for the torrent link needs to get his hipster glasses fixed.14:36
antis:) doing the check with 17.0414:36
zap0i 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
zap0no idea if that would be relavent to you testing14:41
antisdear 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:49
zap0yes.  it should say:  17.04  is a bit bleedying edge, use at own risk.14:53
antisi 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:55
zap0i 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
zap0feel free to say it as you see it.14:58
zap0the 16.04 usb is done.... going to other room to boot the 16.04... back in 5.. maybe 1014:59
antisok, need some minutes to burn 17.04 image15:00
zap0antis,  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:05
zap0only the wired connection.  the wifi can now ping IPs but can't resolve names :(15:15
zap0this one looks quick to skim with step by step fix:     http://www.hecticgeek.com/2017/04/ubuntu-17-04-systemd-dns-issues/15:22
zap0although no idea how step2 can possibly work if DNS can't resolve the apt-get repo URLs15:23
zap0it's starting to look more like systemd is to blame..15:25
* zap0 gets on the bandwagon15:25
antiszap0, hi15:28
zap0boo!15:28
antisany news?15:29
zap016.04 wired works.   16.04 wifi doesn't resolve names.    switch back to wired, wired works still.15:29
zap0that is tiny progress.  but as it's a laptop, i'd like it if wifi could resolve names.15:30
antisand i'm pretty sure it can. haven't had any such problems with like 6 different netbooks, laptops etc.15:31
zap0i upgraded the netbook from 12 to 14 to 16 to 17  in 1 day15:33
zap0it works fine15:34
antisok, fine15:34
zap0so maybe i get 16.04 working, then upgrade to 17 will "just work"15:34
antisi won't recommend upgrading to 1715:34
zap0now i agree.15:34
antisok. 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.15:40
=== anon is now known as Guest5657
=== Pip is now known as Guest27348
=== teward_ is now known as teward
=== nOOb__ is now known as LargePrime

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!