[00:30] <sacarasc> Hey, what's the metapackage for installing what was build-essentials? Tried to install that using apt but it said it wasn't found. (18.04)
[00:32] <krytarik> Just minus the 's' :)
[00:32] <sacarasc> Ah, great, thanks.
[07:29] <shree> how to overcome slow boot prblm in ubuntu...?
[08:04] <SlidingHorn> fresh install - stuck in a login loop (studio) - Been through the instructions here to no avail (permissions, ownership & reinstalling lightdm) https://askubuntu.com/questions/223501/ubuntu-gets-stuck-in-a-login-loop
[08:09] <alkisg> Try installing openbox, it's very small, and logging in from there, to see if it works in 2d mode
[08:10] <SlidingHorn> just attempted startx from TTY and got
[08:12] <SlidingHorn> oops "/usr/lib/Xorg: symbol lookup error: /usr/lib/xorg/modules/drivers/nouveau_drv.so: undefined symbol: exaGetPixmapDriverPrivate
[08:13] <SlidingHorn> I won't be using nouveau anyway, so I'm going to see if installing the nvidia drivers works
[08:29] <SlidingHorn> installing the proprietary drivers and rebooting fixed it.  Nvidia GeForce GTX 1060 6GB for the recod
[08:30] <alkisg> Noone will work on that if you don't file a bug report...
[08:30] <alkisg> IRC isn't for bug reports
[08:34] <SlidingHorn> I'm perfectly aware of that, but it's also nice to have it in a logged chat as well in case someone else who has the problem.  Appreciate your "concern" though.
[09:20] <katnip> is there a difference between full-upgrade and dist-upgrade?
[09:26] <alkisg> Mostly old vs new syntax to say the same thing...
[09:43] <katnip> so either is ok?
[09:44] <ducasse> katnip: they do the same thing, it's mostly that full-upgrade is a clarification since a lot of users thought dist-upgrade would put you on a newer ubuntu release
[09:45] <katnip> ok gotcha
[09:59] <shree> hi
[10:00] <shree> i have booting problem
[11:29] <shree> hello
[15:17] <TJ-> wow! just done an upgrade and the nouveau driver is causing all sorts of problems at boot time. characters missing at random rather like a 'Matrix' movie cascading display, and when I can use the screen dmesg shows a backtrace in the module
[15:18] <lotuspsychje> TJ-: is that one xorg?
[15:18] <TJ-> nouveau_cli_init
[15:18] <TJ-> lotuspsychje: no, console
[15:18] <lotuspsychje> ah
[15:18] <TJ-> the kernel DRM driver
[15:19] <TJ-> Xorg never managed to start from what I can see
[15:19] <lotuspsychje> ati here, so cant test atm
[15:21] <lotuspsychje> im still struggline with network card bug
[15:22] <lotuspsychje> tryed all kinds of things ipv6 disable
[15:23] <TJ-> is that at boot time?
[15:23] <lotuspsychje> TJ-: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1755248
[15:24] <TJ-> 2nd boot it was fine. Weird.
[15:25] <lotuspsychje> both cards worked fine few weeks ago
[15:27] <lotuspsychje> !info netplan.io xenial
[15:28] <lotuspsychje> !info netplan xenial
[15:29] <lotuspsychje> !info netplan
[15:29] <TJ-> lotuspsychje: does it only affected wired interfaces? The syslog attached show wifi connects and get's an IPv4 address via DHCP but the wired interfce tries DHCP but doesn't get a reply
[15:29] <powersj> lotuspsychje: netplan.io is called nplan in xenial
[15:30] <powersj> (assuming that's what you were looking for)
[15:30] <lotuspsychje> TJ-: yep wifi works like a charm on both machines, network cards tryes to connect, then disconnects eth right after
[15:30] <lotuspsychje> powersj: ah tnx
[15:31] <TJ-> lotuspsychje: is this affecting multiple wired PCs on your LAN?
[15:32] <lotuspsychje> TJ-: didnt test other machines on my own lan, good idea..the bug is 2 different single machines eth with same isp
[15:32] <lotuspsychje> customers laptop xenial, and own desktop bionic
[15:33] <lotuspsychje> TJ-: lemme grab eth cable for bionic laptop holdon
[15:33] <TJ-> lotuspsychje: I'd want to confirm 1st that on the LAN other wired devices can get a DHCP lease. I'd also want to check any switches and cabling if they can't get a DHCP lease
[15:34] <TJ-> lotuspsychje: I've not seen any reports of systemic wired issues, especially for 16.04. What kernel is the 16.04 system using?
[15:35] <lotuspsychje> TJ-: hmm got same issue, doesnt wanna connect eth
[15:36] <lotuspsychje> TJ-: perhaps an isp dhcp issue, as its same isp?
[15:36] <TJ-> surely the DHCP server is in the gateway/router?
[15:37] <lotuspsychje> TJ-: ill check in a bit, but it all worked fine few weeks ago
[15:37] <TJ-> after all the wifi side of the router has given out a DHCP lease
[15:38] <lotuspsychje> yeah
[15:38] <TJ-> are the PCs directly connected to the ports on the router, or are they via a separate switch?
[15:38] <TJ-> if the latter then I'd suspect the cable from switch to router
[15:38] <lotuspsychje> TJ-: yeah they going tru my linksys 4-port switch
[15:39] <lotuspsychje> to divide the ip's
[15:39] <TJ-> right, so the PC's get a link UP since that is between PC <> switch ... but if switch isn't connecting to router then no DHCP
[15:40] <lotuspsychje> vdsl2 router[15:40] <TJ-> has one of the connectos pulled free of the port so it's not connecting but looks to be plugged in? do the ports have LEDs on them?
[15:40] <lotuspsychje> leds working all on vdsl2 modem
[15:40] <lotuspsychje> lemme test cable straight to modem holdon
[15:44] <lotuspsychje> ok thats working ffs..
[15:46] <TJ-> lotuspsychje: so, cable or port on switch
[15:47] <lotuspsychje> cable on modem works
[15:48] <TJ-> power-cycle the switch maybe?
[15:48] <lotuspsychje> yeah gonna do that
[15:49] <lotuspsychje> TJ-: that sagem modem only got 1 port, so thats why i need the switch
[16:03] <lotuspsychje> TJ-: solved
[16:04] <TJ-> lotuspsychje: how?
[16:04] <lotuspsychje> TJ-: booting switch did it
[16:05] <TJ-> lotuspsychje: one bug down then :)
[16:05] <lotuspsychje> TJ-: perhaps faulty communicate between them<,
[16:05] <lotuspsychje> TJ-: yeah ill mark it solved
[16:05] <lotuspsychje> gonna rearrange cables first grrr
[16:06] <TJ-> netgear dumb switches have a reputation for this kind of problem if they've been running for a long time
[16:48] <lotuspsychje_> TJ-: its a linksys
[16:48] <lotuspsychje_> TJ-: all cables fixxed now :p
[18:36] <beta-tester> hello, i have an issue with ubuntu 18.04 (beta2 and daily-build). when i double tap on my touchpad ubuntu does not recognized the double tap as double click as usual like in ubuntu 17.10.1 and older. a double tap is recognized as single click.
[18:37] <lotuspsychje> beta-tester: yeah they changed something about that recently
[18:37] <lotuspsychje> not sure how that works exactly yet
[18:37] <lotuspsychje> beta-tester: try gnome-tweak-tools to change mouse settings
[18:38] <beta-tester> is it a bug or a feature? a double click with a mouse shows the normal behavior. 
[18:42] <beta-tester> shall i write a bug report?
[18:43] <lotuspsychje> beta-tester: have you tested gnome-tweak-tool?
[18:44] <beta-tester> not yet... have to reboot... one moment
[19:07] <beta-tester> ok, i am back. i tried all available settings of the normal settings panel of ubuntu - no luck. i installes gnome-tweak-tools and run gnome-tweaks and tried all available settings fo touchpads ... and also without luck.
[19:23] <beta-tester> interesting, i also tried my noteboot with touchpad, and there it is working as normal. attached the keyboard-touchpad-combo to the noteboot, and there that touchpad double tap isn't working as well. so it is a kind of device driver issue?
[19:26] <beta-tester> the keyboard-touchpad-combo is a Logitech K400 (ID 046d:c52b Logitech, Inc. Unifying Receiver). double tap was working til ubuntu 17.10.1 but not anymore since ubuntu 18.04 daily-build.
[19:28] <beta-tester> https://secure.logitech.com/assets/46733/19/wireless-touch-keyboard-k400r.jpg