=== brainwash_ is now known as brainwash [03:19] hey i was trying out 18 beta in VM and for some reason sudo takes forever to give a password prompt.. any idea what this is? [03:20] saw this behavior basically right out of the box === hays_ is now known as hays [04:07] ‎hi guys [04:08] i have a problem.. my thunderbird give: failed to connect to server [04:08] i cant figure out whats wrong === kallesbar_ is now known as kallesbar [07:18] i have a problem.. my thunderbird give: failed to connect to server [07:18] TB 52.6.0 x64 [07:18] ubuntu 18,04 [07:19] Boyette: are you sure nothing blocks, firewall/router? [07:19] yes 100% [07:20] only thing what i can think of [07:20] if i go to ubuntu connection information [07:20] i see virbr0 [07:20] never noticed this before [07:20] does it still give it error, or does it now crash like you said in #ubuntu? [07:20] Boyette: can you start thunderbird from terminal please, lets see if we can catch usefull errors [07:20] and dont understand why its there and if thats normal [07:21] ok [07:22] only see in terminal [07:22] [calBackendLoader] Using Thunderbird's builtin libical backend [07:22] when i start that [07:23] same error [07:23] keeps loading [07:27] Boyette, I had the same with Thunderbird on 17.10 and after some time it worked again [07:27] well [07:27] Thunderbird is updated independently from Ubuntu releases [07:27] how long do i have to wait then? [07:27] :P [07:27] It did not work for a week or so, but I had no time to investigate the issue [07:28] its very strange.. it stopped working last night after 11 pm [07:28] what mail provider? [07:28] i have 4-5 different emailaccounts in there [07:28] most im hosting myself [07:28] 1 not [07:28] 1 gmail [07:28] I just wanted to say that it may be unrelated to 18.04 [07:28] well i think its unrelated to thunderbird [07:28] but to ubuntu updates or qemu which i also tried to remove last night [07:28] with me only GMail made trouble [07:29] I was guessing that GMail was disabling some old authentication methods [07:29] but then it just worked again [07:29] Boyette, do you have multiple clients? for me one clue was that it did not work on one client, but still worked on another [07:30] yes multiple clients [07:30] but all dont work anymore [07:30] oh what do u mean by clients? [07:30] I mean PCs with Thunderbird [07:31] ah [07:32] i can try on another box [07:32] but for sure that will work fine [07:35] how about this bridge i mentioned is it supposed to be there? [07:38] Boyette: it's used by libvirt, for virtualization tools [07:39] yes i read that [07:39] so i think this is related to qemu [07:40] the existings of the bridge [07:41] but if no virtualization tools are used it is not supposed to be there correct? [07:41] Boyette: it is added on install of the virtualization stack [07:42] it is the bridge that is part of libvirts "default" network [07:42] but it is just there and does nothing, unless used [07:42] so that cant be related to my issue? [07:42] OTOH it provides a great eas-of-use and simplification for those using it [07:42] because i somehow have the feeling it started to occur after trying to delete qemu [07:42] Boyette: I don't think it would be related [07:43] "trying to" somewhat feels like messing with conffiles and potentially affecting things [07:43] however when i logon to my system i still get some libvirt qemu user showing aswell [07:43] a "apt remove" or "apt remove purge" of qemu and libvirt certainly won't affect it [07:43] Boyette: yep - in general on packaging users/groups are usually not removed [07:43] because there could be files somewhere owned by them [07:44] hmm [07:44] and removing would make a readabla group/user name just a number [07:44] how can i remove that? [07:44] also if you reinstall the user later (unless it has a static id) it might conflict with itself (old uid != new uid) [07:44] really, leave the users as the remove of the package left them (in general) [07:45] ok [07:45] but of course your are in control (tihs is linux) so if you want use userdel and such tools [07:45] i dont like it to be showing on my logon screen all the time [07:45] ah on the login screen you mean [07:45] yes [07:45] yeah join the party in bug ... [07:45] (just a sec) [07:45] ok [07:46] i dont care about some usertable but the esthetics :P [07:47] https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1667113 [07:47] Launchpad bug 857651 in accountsservice (Ubuntu) "duplicate for #1667113 Unable to hide users from login screen / user switcher" [High,Triaged] [07:47] the linked bugs and askubuntu contain manual masking of the user IIRC [07:48] This affects plenty of packages, essentially all system users [07:48] hmm [07:48] so no fix for that? [07:48] e.g. if you install ceph you'll also see ceph [07:48] its annoying :) [07:49] I never said otherwise :-) [07:49] :) [07:49] but as I said - local fix by config change is in the bug [07:50] the solution that applies depends on your login manager [07:50] how to determine which one im using? [07:51] in /etc/X11/default-display-manager I think [07:51] probably lightdm for you? [07:52] yes [07:53] then https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1667113/comments/18 [07:53] Launchpad bug 857651 in accountsservice (Ubuntu) "duplicate for #1667113 Unable to hide users from login screen / user switcher" [High,Triaged] [07:54] ok thx [07:54] still my mysterious thundebrird problem is there [07:54] i removed gmail account [07:55] now i dont get any error but everything keeps just loading forever [07:56] * cpaelzer no thunderbird skill [07:56] dont think anything changed in thunderbird [07:56] but thunderbird is just suddenly unable to connect [07:57] and i think because something in ubuntu is preventing that [08:00] Boyette: did you launch thunderbird from terminal? hastebin us the whole output plz? [08:22] j@HQ:~$ thunderbird [08:22] [calBackendLoader] Using Thunderbird's builtin libical backend [08:22] thats all [08:24] Boyette: does that happen if you add a new user and add your account there? [08:38] how do u mean add a new user? [08:58] Boyette: if you can't find the GUI for that, one command is sudo adduser [09:13] do you know when the data collection choice will be introduced in bionic daily iso? it's not in 2018-04-11 version [09:51] Guys now that Ubuntu defaults to Gnome, how different the Bionic desktop environment is, compared to Debian Stretch? What does Ubuntu add on top of stock Gnome? Of course I'm only asking about the DE, I do know the core differences... [12:04] hi, so how do you create ESP in this new subiquity installer, the only options are ext4,xfs,btrfs [12:04] fernie: best to ask in #ubuntu-server [12:05] ok [12:45] hi, struggling with nvidia native drivers on bionic [12:45] I've tried the supported ubuntu-drivers autoinstall solution [12:46] after I complete the Gnome3 login, my kernel seems to hang [12:46] I'm on 4.15.0-13-generic x64 on RyZen 1800x [12:47] bodie__: when you say "my kernel seems to hang" what exactly do you mean? [12:47] I can get to the desktop if I remove the nvidia-390 driver, but I'm stuck with 1024x768 [12:47] slidinghorn: I haven't managed to pick apart the syslog yet but my reasoning for this is that my capslock key on my usb keyboard stops functioning [12:48] slidinghorn: sometimes I'm able to get as far as a black desktop with a rendered mouse cursor, but again no inputs do anything and it appears to be completely stuck [12:48] slidinghorn: I suppose that means my gpu driver is functioning but my input driver isn't :) [12:49] it never progresses any further, usually it's just stuck on a black screen [12:49] Sorry should've specified gtx1080ti [12:52] anyway, I'm stuck and not sure where I should be looking for the next step. [12:55] ax370 chipset [12:55] x370* [12:56] fwiw, I had this all working on 17.10 [12:58] bodie__: same desktop session (gnome xorg)? [12:59] brainwash: hmm, I thought so, but according to the internet a) wayland was the default in 17.10, and b) wayland doesn't work with nvidia native drivers, which I definitely was using, which leads me to conclude that it was xorg [12:59] brainwash: I was just using the default gnome selection [13:00] bodie__: can it boot cleanly to the console using systemd.unit=multi-user.target ? [13:00] probably I had wrong conclusions about some of that, but I know it was using the native drivers because I installed and used them for cuda [13:00] I have commented out the ppa [13:00] haven't read through this, but maybe it's bug 1756226 [13:00] bug 1756226 in ubuntu-drivers-common (Ubuntu) "nvidia-driver-390 fails to start GUI" [High,In progress] https://launchpad.net/bugs/1756226 [13:00] and uninstalled 'em [13:00] brainwash: that looks somewhat hopeful [13:01] TJ-: I'm booted into the console right now [13:01] but this is after removing the native drivers [13:01] TJ-: not sure if that answers the question === derekcat_ is now known as derekcat [13:06] bodie__: I was trying to determine if it were purely an Xorg/GUI issue [13:28] TJ-: I was thinking maybe I have an incompatible config left over from when I was using the CUDA nvidia PPA [13:29] I'd run a dpkg --force-overwrite using their nvidia-390 driver after dist upgrading to bionic [13:29] so it's definitely possible that's the culprit [13:29] but after that I removed and purged all of that stuff [13:29] so I'd think anything that install had written would've been reverted / removed then [13:30] I'm just not well-versed enough in gnu/linux to know where to start picking this apart [13:30] currently looking at the bug reports from brainwash [13:40] check /var/log/Xorg.*.log files [13:44] xorg logs were moved to the home dir [13:44] (if i remember right) [13:45] akik: I still have them in /var/log [13:48] ~/.local/share/xorg/Xorg.0.log [13:49] on a bionic vm i ran into this when trying to access it from /var/log [13:51] akik: only if Xorg is run as non root [13:55] brainwash: do you mean with startx? [13:56] TJ-: do I need to be concerned about fb/wfb being loaded? should I blacklist those? [13:56] akik: I mean how Xorg is started (root vs non root) [13:56] fwiw, I _do_ get to the graphical Gnome login screen at the correct native resolution [13:57] it's just once I click "login" with the correct password that it freezes [13:57] brainwash: usually it's done with the dm. how else? [13:58] that is not the point [13:58] Xorg with or without root rights [13:58] bodie__: OH! I think you've got the intel microcode bug.. did the system get a BIOS/firmware update recently? [13:59] akik: "Xorg has traditionally always been suid root because it needed direct hardware access. With the advent of kms all hardware access is done by the kernel, so the primary reason for the X server running with root rights is no longer relevant." [13:59] bodie__: we're seen a series of regressions on Dells especially, that have the intel microcode firmware update applied. I fix was found end of last week and should be getting out to the archives [14:00] akik: the nvidia driver (still?) requires the traditional way [14:00] akik: and therfore logs will be in /var/log [14:01] TJ-: I'm on AMD x370 / RyZen on the firmware update where they made fast ram work. I think it was revision 5 [14:01] so, at least 3-6 months ago, iirc. time has been passing a bit quick lately [14:02] it's a Gigabyte motherboard. I had some issues with the HD Audio front panel too. [14:02] RLC1220 [14:03] the biggest recent change to the system was the dist-upgrade to bionic :) [14:03] besides getting cuda [14:03] but that's all removed and purged now ... [14:11] bodie__: OK, so not the intel microcode then! [14:13] bodie__: we saw tens/hundreds of Dells affected and was tracked down to an attempt in a single code path to take an already-held lock, resulting in ...hang/freeze. [14:13] bodie__: so it's possible you're seeing the same thing... the updated kernels should be out soon [14:13] :think: :think: :think: [14:13] so, like, something I can give a shot with a kernel compile yet or nah? [14:14] tyhicks was dealing with it and produced some test builds, I'm not sure atwhat point the fixes will get to the archives [14:15] Hi there. Anyone noticed an issue with systemd user units not creating a user journal? [14:21] luxifer: what do you mean? journalctl --user prints output also from my user units [14:21] fernie: doesn't for mine [14:22] I've created a new system user, created a user unit with it and ran it [14:22] however, neither systemctl --user status ... nor journalctl --user prints output from the process [14:22] the process is running fine though and a can see its output in the global journal [14:26] luxifer: have you tried the --user-unit option? (source: https://unix.stackexchange.com/questions/109490/where-is-why-is-there-no-log-for-normal-user-systemd-services ) [14:28] bodie__: see bug #1759920 [14:28] bug 1759920 in linux (Ubuntu Artful) "intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)" [High,Fix committed] https://launchpad.net/bugs/1759920 [14:28] :+1: TJ- [14:30] bodie__: that lists where to find the kernels that fixed that issue, I think they are still in -proposed in some cases. Not sure if 4.15 has been patched also at this point, or if it needs it. You may have a different issue of course [14:39] I wonder if there's a stable gentoo kconf I should just be trying instead [14:40] seems like they often have good support for newer architectures [14:40] and ryzen seems to have been a pain in the ass so far [14:40] pardon my crassness [14:42] disabling c-states from bios gets rid of the random crashes when mostly idling ..but then it crashes when resuming from suspend [14:54] slidinghorn: I have... to no avail [14:54] besides "journalctl --user" should print any user-journal available, shouldn't it? [15:02] TJ-: do you know where I would find the events that occurred after I passed the Gnome login entry? [15:02] TJ-: I think all of the events I'm looking at in the Xorg.0.log are from before I logged in, because I do get a graphical login, working mouse and kb, etc [15:02] bodie__: possibly /var/log/kern.log if it's a kernel issue. $HOME/.xsession-errors [15:04] there's nothing in kern.log from today [15:04] that might just be me being dumb, hold up [15:05] yeah I'd booted to the gui last night, not today [15:06] I'll keep looking... [15:09] hmm, okay, so at the end of my Xorg.0.log, when I last saw the unexpected behavior, I got a bunch of messages from "dix" saying I couldn't enable various devices (12,10,7,etc.) [15:10] trying to sort out whether this is due to unplugging and replugging the USB, but I see messages later which correlate to that [15:10] the "dix" messages came right after NVIDIA(0): Setting mode "DFP-6:nvidia-auto-select" [15:11] and then a partial log message at the very end of the file [15:11] TJ-: ^ [15:14] bodie__: not sure, but I know nvidia is a mess currently [15:16] maybe I should try manually installing an nvidia driver without the ubuntu-drivers process [15:16] that's more likely to mess things up! [15:23] all I really know is it worked in 17.10. [15:24] I just wanted an updated zsh.... [15:24] I don't suppose I can roll back the dist-upgrade lol [16:51] bodie__: I suggest filing a new bug report if you want the issue to be fixed [16:56] bodie__: you might like to know there is a lot of work going on as we speak to solve the nvidia issue [16:56] bug 1756226 [16:56] bug 1756226 in ubuntu-drivers-common (Ubuntu) "nvidia-driver-390 fails to start GUI" [High,In progress] https://launchpad.net/bugs/1756226 [16:58] that's the one I've linked before [16:58] so, it's the same issue? [17:00] Possibly, but devs are working on it currently [17:00] I'm in the middle of trying to install the suggested items from bionic-proposed [17:00] good to know TJ- :) [17:01] is https://wiki.ubuntu.com/Testing/EnableProposed still current? [17:02] I mean, substituting bionic for xenial [17:18] there are many conflicting suggested solutions in 1756226. [18:12] so, I tried installing the suggested packages from 1756226 bionic-proposed, but all of them were already up to date (after adding the deb in sources.list) [18:12] (and updating) [18:12] so, not sure where to go from here [18:13] guess I could just run at 1024x768 without native drivers, or try nouveau, until the release [18:13] bodie__: what packages (or which comment0? [18:13] libglvnd0, xserver-xorg-core, and libgl1-mesa-glx [18:13] this is with native nvidia drivers from ubuntu-drivers autoinstall [18:14] bodie__: ... there is no mentione of those packages in that bug? [18:14] bodie__: LP: #1756226 ? [18:14] Launchpad bug 1756226 in ubuntu-drivers-common (Ubuntu) "nvidia-driver-390 fails to start GUI" [High,In progress] https://launchpad.net/bugs/1756226 [18:14] bodie__: the 'fix' there is to edit a config file [18:14] sorry, this was from 1752033 [18:14] LP: #1752033 [18:14] Launchpad bug 1752033 in KiCad "Track cleanup too aggressive" [Medium,Fix committed] https://launchpad.net/bugs/1752033 [18:15] LP: #1752053 [18:15] Launchpad bug 1752053 in nvidia-graphics-drivers-390 (Ubuntu) "nvidia-390 fails to boot graphical display" [Critical,Fix released] https://launchpad.net/bugs/1752053 [18:15] 53, not 23 [18:15] nacc, I'll go check that one... got mixed up [18:15] bodie__: the 53 bug is fix released, so you don't need proposed for it [18:16] gotcha [18:16] nacc, the reason I didn't think 6226 would solve the problem is that I'm using a single gpu [18:17] bodie__: some of the comments imply that even intel + nvidia setups had the problem [18:18] nacc, I'm on a ryzen desktop with just the nvidia gpu [18:19] bodie__: i'd still try, i guess -- dunno [18:19] worth a shot [18:22] nacc, I don't suppose it could have anything to do with drm/modeset? [18:23] bodie__: it's certainly possible, you could try with nomodeset too [18:23] I'm able to get to the login/wm picker, so does that mean the nvidia driver is working by that point? [18:23] bodie__: yes, i think so [18:23] hm. [18:57] OK, I'm ssh'd into the impacted system. so I should be able to watch what happens when the login freezes [18:59] I logged in and got the usual hanging login screen behavior, but the system is definitely not frozen [19:00] dmesg doesn't have any relevant info [19:00] perhaps this is relevant: NVRM: Your system is not currently configured to drive a VGA console [19:00] on the primary VGA device. The NVIDIA Linux graphics driver [19:00] requires the use of a text-mode VGA console. Use of other console [19:00] drivers including, but not limited to, vesafb, may result in [19:01] corruption and stability problems, and is not supported. [19:01] !paste | bodie__ [19:01] bodie__: For posting multi-line texts into the channel, please use https://paste.ubuntu.com | To post !screenshots use https://imgur.com/ !pastebinit to paste directly from command line | Make sure you give us the URL for your paste - see also the channel topic. [19:05] my mistake [19:11] bodie__: don't worry about that one, its due to nvidia not having a driver that can handle graphics-mode consoles [19:11] bodie__: check in the Xorg.0.log where-ever it is ! [19:12] bodie__: which display manager? check either /var/log/lightdm/ or /var/log/gdm3/ I think it is [19:23] TJ-: gdm is running [19:24] TJ-: there's nothing in /var/log/gdm3 [19:26] TJ-: what am I looking for in the xorg log? [19:27] bodie__: any sign of problems ! [19:27] bodie__: it might be /var/log/gdm/ --- I don't use gnome so not sure [19:28] https://paste.ubuntu.com/p/BSPtcjMPZN/ [19:28] that looks a bit odd that the session opened and closed so quickly [19:30] restarting GDM didn't do much of anything [19:30] https://paste.ubuntu.com/p/59wbrcTJjK/ [19:31] can't seem to find the gdm logs [19:31] gpu-manager.log looks normal [19:31] boot.log looks OK [19:32] someone said they can be in the user directory, possibly somewhere under $HOME/.local/ [19:52] ~/.local/share/xorg/Xorg.0.log [19:53] i noticed that .Xauthority is not in home dir anymore but in /run/user/1000/gdm/Xauthority [19:55] at least it has the same data [19:56] good idea to move it to a tmpfs, stops the 'root owns users' file problem [19:56] and it can't remain over a reboot [20:11] graphical.target is active/active... [20:11] is it possible there's some reason the nvidia driver just isn't seeing the displayport connected to the particular output of the gpu? [20:12] it's possible. Is an X server running ( "ps -efly | grep Xorg" ) ? [20:13] bodie__: if it is from a console can you do something like "xrandr -d :0 -qv" (set -d to the display the Xorg instance shows is used by the ps command) [20:13] yes, that lists 5 processes [20:15] TJ-: what am I looking for? It shows "xrandr program version 1.5.0" [20:15] it's just waiting now [20:17] oh, you mean --verbose. that just hangs [20:17] bodie__: xrandr should report the outputs and modes [20:19] TJ-: the xorg process is /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 [20:19] bodie__: weird, no display number shown [20:19] I figured it was -displayfd [20:20] bodie__: I see " /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch" [20:20] bodie__: the display is the :0 [20:21] TJ-: maybe there's some issue with users [20:22] there's no :0 in bionic daily for Xorg process [20:22] i have the same options than bodie__ === powersj_ is now known as powersj === icey_ is now known as icey === graingert_ is now known as graingert [20:30] still doesn't explain why my input devices aren't doing anything... I don't think I've ever seen a keyboard with a nonfunctioning capslock except during boot [20:36] TJ-: here's my xorg log... https://paste.ubuntu.com/p/fVHH6NK9yY/ the end looks a bit suspicious with the devices (including power button) removed [20:37] "Power Button: device is a keyboard" [20:39] > xinput --list / "unable to connect to X server" [20:41] bodie__: maybe: env DISPLAY=:0.0 XAUTHORITY=/run/user/121/gdm/Xauthority xinput --list [20:42] modprobe doesn't think libinput exists [20:46] bodie__: could some of the kernel command-line options be affecting this? "vga=normal nofb nomodeset video=vesafb:off" [20:49] bodie__: this Xorg.0.log was from the user's $HOME ? I ask because "[ 7.152] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Apr 11 14:56:22 2018" [20:58] TJ-: no, from /var/log/Xorg.0.log [20:58] akik: that just hangs [20:58] bodie__: oh, good - thought the log file was lying ! [20:58] TJ-: possibly [20:59] should I just remove those kernel flags? [20:59] bodie__: it's worth a try but I don't think those are causing the X server issue else nvidia would be writing (WW) and (EE) into the log [21:05] Could someone check if they're virt-manager installed, and if so, if gir1.2-spiceclientgtk-3.0 is also installed? [21:07] TJ-: it appears i do [21:08] nacc: maybe you can loan some brain cells then. Despite "apt-get install --reinstall --install-recommends virt-manager" "gir1.2-spiceclientgtk-3.0 " and "gir1.2-spiceclientglib-2.0" do not get installed [21:08] they are Recommends of virt-manager [21:08] TJ-: do any of the recommends get installed? [21:10] libvirt-daemon-system is installed [21:10] TJ-: if you remove it? [21:10] that could be due to libvirt-bin though going by it's rdepends [21:13] nacc: ahhh, it's --reinstall ... it ignores --install-recommends [21:14] is that a bug? [21:15] TJ-: i don't know :) [21:15] OK, I'm sitting here at the login screen before attempting to log in, and the xorg log doesn't show the bit where input devices got removed [21:15] keyboard, mouse, and display still working [21:15] nacc: nor me! I'll report it and see what is said [21:15] now's the time I should ask xorg questions [21:17] Is there a way to do a 16.04 -> 18.04 upgrade currently, or is `do-release-upgrade` not able to do this? (Asking because of https://askubuntu.com/questions/1024147/cant-do-release-upgrade-d-from-16-04-to-18-04) [21:17] teward: do-release-upgrade -d [21:17] should work [21:17] nacc: read the ask ubuntu post [21:18] hrm [21:18] OP of said post did that on a 16.04 box and got a different error [21:18] hrm, maybe it's not possible until it releases [21:18] dunno [21:18] stating: "Upgrades to the development release are only available from the latest supported release." [21:18] nacc: that's what I thought. who shoudl I be prodding for this question? [21:18] -devel? or the release team? [21:18] teward: i'd ask bdmurry [21:18] *bdmurray [21:18] ack [21:19] nacc: thanks, I'll prod bdmurray [21:19] hi [21:19] teward: np [21:19] is anyone able to hibernate ubuntu? [21:19] i installled kernel 4.16.1 [21:19] have enough swap [21:19] older versions were hibernating [21:19] so what is the problem [21:20] both pm-hibernate and hibernate doesnt work [21:20] mattfly: so you're not using hte ubuntu kernel? [21:20] it didnt work either [21:21] I updated because on ubuntu 17.10 i had the same issue [21:21] but updating the kernel to this one solved it [21:21] mattfly: you said 'older versions were hibernating' [21:21] mattfly: if you were not using the ubuntu kernel, then no, they weren't. [21:22] yeah [21:22] any idea how to make it works? [21:25] hmmmmmmm https://paste.ubuntu.com/p/qFWBz9BxKw/ [21:25] I nuked my xorg.conf [21:25] then ran this [21:27] same hang after installing xorg-dev and generating... [21:34] about the user journal issue I've asked about: It only seems to affect "system" accounts - i.e. UIDs < 1000 [21:36] is this expected behavior or should I file a bug? [21:39] anyone know how to hibernate ubuntu 18.04 [21:39] ? [21:40] mattfly: 1. have a large enough swap partition/file 2. configure initramfs-tools [22:00] tsimonq2: saw 2 instances of wifi icon on lubuntu bionic today [22:00] lotuspsychje: Known bug, not just Lubuntu. [22:00] aha cool [22:01] lotuspsychje: bug 1761606 [22:01] bug 1761606 in network-manager-applet (Ubuntu) "Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session." [Undecided,Confirmed] https://launchpad.net/bugs/1761606 [22:01] for the rest, works like a charm [22:01] \o/ [22:02] hey TJ- i have enough swap [22:02] let me add affected, i had it on the installed lubuntu [22:02] but the hibernate or pm-hibernate either systemctl hibernate does not work [22:03] it is better to wait go for official release of ubuntu 18 [22:03] ie get the beta [22:03] laptop: That's up to you, but you could expect the official release to be a bit more polished. [22:04] tsimonq2: experience tells us that if you want polish you'd better wait for the .1 release [22:04] would the updates fix the beta [22:04] tsimonq2: added comment and affected [22:04] luxifer: mhhh, depends.] [22:04]