=== brainwash_ is now known as brainwash [12:56] So, I continue to have two-finger scrolling quit working. It seems to be after closing my laptop and it suspending for a period, but has now occured at least 3 times. The only way I've found to make it work again is to reset tweak tool to default settings and restart. I am *not* changing anything in tweak-tool between times. Thoughts? === JanC_ is now known as JanC [16:27] hi all. just upgraded from 17.04. While troubleshooting various wayland issues (on a laptop which has both nvidia and intel chipsets and use prime-select), I noticed that it still seems to be using lightdm, even though I think gdm is now the default. what's the appropriate way to switch? [16:53] can someone tell me how to downgrade to xserver (instead of wayland) on 17.10? Having all sorts of problems because my laptop has both intel and nvidia cards (think prime-select) [16:55] d1rewolf: uninstall lightdm and install/use gdm [16:56] d1rewolf: I'm using gdm now [16:56] er...brainwash ^ ;) [16:56] brainwash: although I didn't completely uninstall lightdm, I did dpkg-reconfigure gdm3 and now gdm is in use [16:57] and you cannot switch to the normal gnome session? [16:57] brainwash: I'm able to login to gnome [16:57] and configure my monitors via "Displays" [16:57] but if I log out/back in, the monitor settings disappear [16:57] this is with primeselect set to nvidia [16:58] when set to intel (mesa) it wouldn't login at all....although come to think of it that was using lightdm [16:58] so perhaps a switch to intel and then logging in with gdm will do? [16:59] I assume that with intel it would try to load gnome wayland, and with nvidia the xorg one [16:59] brainwash: I'm running with nvidia now, and it appears wayland is running [17:00] brainwash: XDG_SESSION_TYPE=wayland [17:00] is that really the case? [17:00] ok [17:02] brainwash: would that verify it was the case? [17:02] nvidia-settings doesn't work any longer....just refuses to launch [17:02] "ERROR: Unable to find display on any available system" [17:02] well yeah [17:02] it's a wayland session [17:03] therefore, not compatible with nvidia-settings [17:05] brainwash: is there a somewhat easy way to fallback to xorg instead of wayland? [17:05] brainwash: or would you happen to know a way to determine why the "Displays" section isn't storing its data? [17:06] it's painful to have to re-enable the monitors, and then try to drag them (that dragging never seems to just work) [17:07] gdm allows you to select what session you want to start [17:07] brainwash: for me, Gnome just fires up Wayland [17:07] although I see the Gnome with Wayland option as wel [17:07] this is an upgrade from 17.04 to 17.10 [17:08] you get wayland without selecting "gnome with wayland"? [17:09] brainwash: yes, I am [17:10] I suggest checking launchpad then [17:11] maybe a bug report exists [17:11] brainwash: ok, thanks [17:20] brainwash: well, mystery solved. There's a "Gnome on X11" option in the gdm menu. That seems to launch it on xorg. [17:20] still can't figure out why the heck my monitor/display settings won't save [17:26] if one has settings from gnome on 17.04 but wishes to use the default 17.10 look/feel/settings/etc, how can one roll back or default to those? [17:27] d1rewolf: maybe bug 1716341 [17:27] bug 1716341 in gnome-control-center (Ubuntu) "Settings for external monitor are deleted after reboot, suspension, log out" [High,Triaged] https://launchpad.net/bugs/1716341 [17:27] a bit busy right now, so I did not read through the report [17:27] brainwash: cool. i'll take a look. thank you [19:00] hi guys. Anyone successfully running vmware workstation on 17.10? === d1rewolf_ is now known as d1rewolf [19:13] how can one reset gnome to default settings on 17.10 (assuming you've upgraded from a 17.04 system using gnome)? Would like to try out Ubuntu's default look and feel [19:13] d1rewolf: i'd create a dummy test user [19:13] d1rewolf: alt. backup your ~/.local and ~/.config directories (there are probably others, which is why i suggest the test user) [19:15] nacc: you mean use the test user to see what's created upon login? [19:15] would hate to blow away all settings in ~/.local and ~/.config :-/ [19:16] d1rewolf: right, i have done both ways [19:16] d1rewolf: 1) create a dummy user, login as them [19:17] d1rewolf: 2) mv ~/.local ~/.local.bak; mv ~/.config ~/.config.bak [19:17] nacc: I'll give it a go. thanks ;) [19:18] Hi. Is anyone else having the swap file fail in 17.10, causing a system freeze when the RAM fills up? [19:19] CRogers: i'm using a swap file in 17.10 [19:19] CRogers: and hiya (from #ubuntu-devel) [19:19] CRogers: what does `cat /proc/swaps` say? [19:20] nacc: /dev/dm-0 partition 2096636 0 -1 [19:21] CRogers: well, that's not a swapfile :) [19:21] CRogers: how about `grep swap /etc/fstab` ? [19:21] nacc: this is what Ubuntu installs by default now. I've changed NOTHING [19:22] nacc: /dev/mapper/cryptswap1 none swap sw 0 0 [19:22] CRogers: ah, encrypted swap? [19:22] CRogers: grep SwapTotal /proc/meminfo [19:22] nacc: Does Ubuntu accudentally encrypt the swap file while encrypting the home folder? [19:23] CRogers: i don't know [19:23] nacc SwapTotal: 2096636 kB [19:23] CRogers: so you have swap :) [19:23] CRogers: wehther from swap file or swap partition, you have it [19:24] CRogers: so ... that's presumably not what's causinng your system to freeze [19:24] logfile says Failed to activate swap file [19:24] Maybe because the installer encrypted it? [19:25] CRogers: i don't think you hav ea swapfile [19:25] CRogers: it's not listed in fstab or /proc/swaps [19:25] CRogers: when did you install? [19:25] Yesterday. [19:25] CRogers: and you downloaded the iso image yesterday? [19:25] Well, I re-installed yesterday. [19:25] Yes. [19:26] CRogers: oh i wonder did you have a swap partition before? [19:26] CRogers: and did you reuse your partitions? [19:26] updater failed (like it always does) for 16.04 > 17.04 [19:27] So I figured since I'm reinstalling anyway, may as well trythe latest version. [19:27] nacc: Nope. Told it to erase the entire disk [19:27] CRogers: hrm [19:27] Didn't change any swap or partition settings. [19:28] Guess a reinstall again is the best option. [19:28] CRogers: sorry, I'm really not sure [19:29] This time, I'll just install GIMP and try to export the test file that eats up all the ram [19:29] See if it's "fixed" [19:30] nacc: thanks for trying. [19:30] nacc: did you encrypt your home folder? [19:31] when you installed? [19:31] CRogers: no, i do whole disk encryption [19:31] CRogers: and i last installed ~15.10 [19:31] have been upgrading sinnce [19:31] nacc: You have a magic I'll never understand. [19:32] I've been using Ubuntu for about 8 years, and I've had the upgrade succeed like maybe twice in all that time. [19:32] CRogers: well, i'd never do 16.04 -> 17.04 :) [19:32] CRogers: either upgrade with each release, or just do LTS->LTS [19:32] Or wait until about a year after the release, then upgrade. [19:33] CRogers: that's nonsenical for non-LTS [19:33] CRogers: they are only supported for 9 months [19:33] Yea, well I use gimp-edge ppas [19:33] to help test [19:33] so I can't not upgrade. [19:33] they only build for most recent ubuntu [19:34] (for the edge repos) [19:34] CRogers: they publish for xenial? [19:34] https://launchpad.net/~otto-kesselgulasch/+archive/ubuntu/gimp-edge?field.series_filter=xenial [19:35] nacc: Yea, I might go back if I can't get this sorted. [19:35] But for how long they will support xenial... [19:35] I can't really be updating all the time. I'm too busy. [19:36] CRogers: i assume they'd support it as long as xenial is supported [19:36] CRogers: that's basically what their pages ays [19:36] CRogers: but you'd need to ask them [19:36] No, actually, that page is wrong. [19:37] I had to upgrade to 16.10 to install edge. [19:37] forgot xenial is 16.04, but yea that wasn't workng. [19:38] Stuck on gimp 2.95 [19:38] CRogers: well, that doesn't make sense. 16.10 is eol [19:39] * CRogers shrugs [19:39] Anyway, I'll reinstall [19:40] to test [19:40] and file a bug report if it fails again.