[01:22] <Bashing-om> Squarism: I have no issues running 18.04 wayland . However, my use case is light .
[01:22] <Squarism> Bashing-om, light?
[01:24] <Bashing-om> Squarism: I have not installed other than defaults , I have no issues at all with wayland .
[01:24] <Squarism> Bashing-om, ok - sounds great
[01:24] <Squarism> Bashing-om, running it as default?
[01:25] <Bashing-om> Squarism: I find that wayland in fact is smoother and faster than Xorg :)
[01:25] <Bashing-om> Squarism: There are many apps that are not wayland ready yet .
[01:25] <Squarism> Hope i can enjoy that too. Haven installed 18.04 yet but anticipating it alot
[01:27] <Bashing-om> Squarism: I also have xubuntu-core 18.04 installed; it too is stable on my system . 
[01:29] <Squarism> Bashing-om, you adapted early? Isnt 18.04 to be release on the 29th?
[01:38] <valorie> Squarism: lots of us in here have installed it and are testing
[01:39] <Squarism> great stuff
[01:39] <Squarism> ill install on the 29th i think
[01:39] <valorie> I tested before that, but am running bionic on both of my machines as of beta2 day
=== brainwash_ is now known as brainwash
[03:45] <Squarism> is it easy to flip between wayland and X11 or does it require some sort of reinstall?
[03:46] <flocculant> I believe you do it at the login screen somewhere
[04:26] <Bashing-om> Squarism: Chenge the session at the password screen . Click on the cog icon at the lower right of the password entry box is the drop down to choose the session.
[04:27] <flocculant> Bashing-om: thanks - thought it was something like that :)
[04:28] <Bashing-om> flocculant: :D Took me a bit to tumble to it .
[04:29]  * flocculant only boots ubuntu to a vm to see if bugs I see in xubuntu are more generic :p
[04:29] <flocculant> ahah - we can blame not-Xubuntu for this ...
[04:31] <Bashing-om> flocculant: Well, Xubuntu must have it more together :)
=== kallesbar_ is now known as kallesbar
[05:52] <Squarism> which of the bigger window managers are more innovative? I get the feeling that many are like "we have icons and windows, now we done". In a way I miss windows crazy re-hauls and dig osx innovative features. Sure i understand they have resources to try dramatic changes like the opensource alternatives dont have.
[06:03] <Bashing-om> Squarism: Boot a live (k)ubuntu and see what you then think :)
[06:14] <lotuspsychje> !flavors | Squarism test some
[06:14] <ubottu> Squarism test some: Recognized Ubuntu flavors build on Ubuntu and provide a different user experience out of the box. They are supported both in #ubuntu and in their flavor channel. For a list, see https://www.ubuntu.com/download/ubuntu-flavours
[06:15] <Squarism> lotuspsychje, thanks
[06:15] <Squarism> will check them out
[06:16] <Squarism> What about lightdm? Is there any flavor for that?
[06:16] <lotuspsychje> Squarism: alot of software out there to pimp your eyecandy aswell, like conky
[06:16] <lotuspsychje> Squarism: ubuntu 14.04 & 16.04 have unity
[06:19] <Squarism> lotuspsychje, does lightdm relate to unity? Im not totally clear what layer im talking about. lightdm is a "display manager" ive learned. Is that what gnome is too?
[06:20] <lotuspsychje> Squarism: gnome uses gdm
[06:30] <Squarism> oh ok
[06:39] <ducasse> Squarism: lightdm is just the login screen, it only starts your session - it's not a desktop environment or window manager
[06:49] <Squarism> ducasse, oh ok
[06:53] <ducasse> Squarism: in addition to the above, there are a couple of desktops that don't have their own flavor, like cinnamon and enlightenment. and there are tons of window managers if you don't need a full desktop or want to make your own.
[07:06] <katnip> i thought i read somewhere that xorg was the choice and wayland would be discontinued
[07:06] <lotuspsychje> katnip: untrue
[07:06] <katnip> ok
[07:06] <lotuspsychje> katnip: wayland is still worked on
[07:06] <katnip> just looking for a confirmation
[07:07] <katnip> i prefer it too but i'm in xorg now
[07:07] <lotuspsychje> katnip: ubuntu 18.04 is using xorg by default, but wayland is still choosable at login
[07:07] <katnip> yes
[07:08] <katnip> i used to use wayland all the time, then some fake news site said it would be discontinued
[07:08] <lotuspsychje> url?
[07:08] <ducasse> probably russian trolls
[07:08] <katnip> oh god, this was nearly a month ago
[07:08] <katnip> yeah
[07:08] <lotuspsychje> katnip: you cant recall?
[07:09] <katnip> lotuspsychje, no, too long
[07:09] <katnip> fake news if you say it's staying around
[07:09] <ducasse> it's most likely just a misunderstanding of it not being default in bionic
[07:09] <katnip> i prefer myself too
[07:10] <katnip> wayland*
[07:10] <katnip> ill go back into it and see if anything i have dont work
[07:16] <lotuspsychje> katnip: we have users confirming better nvidia experience on latest driver ppa on wayland
[07:19] <katnip> ill have to stay in xorg
[07:19] <katnip> wayland, things didnt work lik the keyboard
[07:19] <katnip> i dont have nvidia
[07:19] <katnip> laptop
[07:19] <katnip> with external keyboard/monitor/mouse
[07:20] <katnip> i tried wayland again just now and it's completely out of wack, keyboard would not work, an app or two would not open at all
[07:21] <katnip> which is odd, because everything used to work before
[07:26] <ducasse> and wayland is *so* easy to debug :P
[07:27] <katnip> dont know what happened
[07:27] <katnip> used to be great
[07:27] <katnip> Client: HexChat 2.14.1 • OS: Ubuntu "bionic" 18.04 • CPU: Intel(R) Core(TM) i7 CPU       M 620  @ 2.67GHz (2.09GHz) • Memory: Physical: 3.6 GiB Total (2.2 GiB Free) Swap: 3.8 GiB Total (3.8 GiB Free) • Storage: 0 bytes / 0 bytes (0 bytes Free) • Uptime: 10m 49s
[08:27] <ducasse> do the bionic server images now use the new installer? if so, are images with the old one still available?
[08:41] <sveinse> Out of box bionic installer still fails on Lenovo P51. Segfault in kernel from noveau driver. This is noteable since the P51 is listed on the Canonicals approved for Ubuntu list
[08:42] <lotuspsychje> !nomodeset | sveinse 
[08:42] <ubottu> sveinse: A common kernel (boot)parameter is nomodeset, which is needed for some graphic cards that otherwise boot into a black screen or show corrupted splash screen. See http://ubuntuforums.org/showthread.php?t=1613132 on how to use this parameter
[09:09] <sveinse> thanks, nomodeset worked
[09:10] <TJ-> sveinse: that needs a bug report if there's a segfault
[09:12] <sveinse> I have an image (literally) of the oops
[09:12] <TJ-> that's often the case, you can attach it to a bug report.
[09:12] <TJ-> we've had a few reports but not collected much accurate info so far
[09:13] <sveinse> where do you want me to post a report?
[09:14] <TJ-> !bug
[09:14] <ubottu> If you find a bug in Ubuntu or any of its derivatives, please report it using the command « ubuntu-bug <package> » - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs.
[09:30] <sveinse> If I'm dualbooting between 17.10 and 18.04 on two partitions on on drive, which of them is best to manage the bootloader?
[09:30] <TJ-> sveinse: good question!
[09:31] <TJ-> sveinse: either :) Not many changes in GRUB between the 2, but maybe 17.10 in case you end up deleting 18.04 due to bugs ?
[10:11] <sveinse> Would it be aviseable to reinstall 18.04 when it is formally released, or just stay with the development version and keep it updated until it morphs into a released version?
[10:17] <TJ-> sveinse: stay, the release is just the same packages from a single point in time
[10:56] <bodie__> hey folks
[10:56] <bodie__> I've been struggling with login/xorg issues for a few days on bionic with native nvidia drivers
[10:57] <bodie__> today I ssh'd into the machine and halted gdm
[10:57] <bodie__> I was then able to switch to another terminal on the attached kb/monitor and restart gdm 
[10:58] <bodie__> and that allowed me to log into the desktop successfully
[10:59] <bodie__> I have no idea why, but I also noticed that disabling gdm using systemctl didn't affect the next boot
[11:00] <bodie__> for a starting point, I think disabling the boot into gdm would at least make the system usable
[11:02] <TJ-> bodie__: that's timing/race condition by the sound of it
[11:02] <TJ-> something wasn't ready when the GUI started first time
[11:02] <TJ-> bodie__: but that is a good bit of diagnostics since you're significantly reduced the problem space
[11:02] <TJ-> bodie__: add that info to the bug report :)
[11:02] <erle-> bodie__, have you tried using lightdm as a workaround?
[11:03] <erle-> or maybe it is the same?
[11:04] <bodie__> I assume that's the "unity" login option.  I tried that and gnome2 and both have the same issue
[11:04] <bodie__> TJ-, now that I have a functioning desktop I'll definitely do that ;) I have a tab open to Launchpad just now!
[11:05] <katnip> wow, a lot of updates this morning
[11:07] <bodie__> TJ-: I've never filed a report on LP.  Is there a contrib doc?
[11:10] <TJ-> !bug | bodie__ 
[11:10] <ubottu> bodie__: If you find a bug in Ubuntu or any of its derivatives, please report it using the command « ubuntu-bug <package> » - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs.
[11:11] <TJ-> bodie__: I think the correct package might be the nvidia-XXX (XXX being the version) to begin with
[11:14] <JimBuntu> TJ-, is correct, the Ubuntu drivers are named like that. There is also an ubuntu-drivers autoinstall command
=== brainwash_ is now known as brainwash
[11:55] <bodie__> TJ-, I've sent my public key to the keyserver, but when I sign the code of conduct with that key, I get an error.  As you can see, the key is registered: https://keyserver.ubuntu.com/pks/lookup?fingerprint=on&op=index&search=0xBAA2F70290B90EB87F923C38C71FE7F2B22B57F5
[11:57] <bodie__> https://answers.launchpad.net/launchpad/+question/115867
[12:03] <bodie__> OK, guess it just hadn't synced....
[12:05] <TJ-> bodie__: time is great healer... except when it comes to bugs!
[12:07] <erle-> bodie__, no, DM (display manager) is the login screen itself, not the login type
[12:10] <bodie__> time is the great state mangler :P 
[12:11] <bodie__> I personally feel the next universe release shouldn't include it
[12:11] <bodie__> erle-, I must have misunderstood the question
[12:11] <bodie__> erle-, I haven't tried that.  I can't seem to persist disabling gdm using systemctl 
[12:12] <erle-> if you install another DM with apt-get it will ask you which one to load by default
[12:12] <JimBuntu> bodie__, but the repo shows no new commits for a very long time, unsure if the dev team are still active.
[12:13] <bodie__> erle-, if lightdm is supported, i'll give it a try
[12:16] <erle-> bodie__, lightdm was default when Unity was still there
[12:49] <gregl> I downloaded the daily image and burnt it on a usb thumb drive,but when I go to install there isn't a ufi install option.. Is there one and if so where can i get it?
[12:51] <lotuspsychje> gregl: are you going to install singleboot or dualboot?
[12:51] <gregl> single
[12:52] <lotuspsychje> gregl: did you disable fastboot & secureboot?
[12:53] <gregl> I have been running it for the last few years, so i would assume they are disabled
[12:53] <gregl> I will check though..
[12:54] <gregl> lotuspsychje, ^^^
[12:57] <gregl> lotuspsychje, This is from my fstab  /boot/efi was on /dev/sdb1 during installation
[12:59] <gregl> I downloaded the daily image and burnt it on a usb thumb drive,but when I go to install there isn't a efi install option.. Is there one and if so where can i get it?     Anyone else care to help?
[13:00] <lotuspsychje> gregl: holdon, im getting someone
[13:00] <lotuspsychje> idle here a bit plz
[13:00] <gregl> lotuspsychje, Ok thanks,I though you may have got called away..
[13:02] <lotuspsychje> gregl: on irc you need some patience, as we have users worldwide living their lives beyond irc too
[13:02] <TJ-> gregl: there is no "EFI install option"
[13:02] <TJ-> gregl: you select the 'boot mode' in the PC's own firmware boot menu
[13:03] <lotuspsychje> TJ-: 16.04 had an uefi option in setup, perhaps he means that?
[13:03] <lotuspsychje> to install in uefi mode
[13:03] <TJ-> gregl: if it uses CSM/BIOS/Legacy mode it'll use syslinux to start in BIOS mode. If it starts the installer in EFI mode it'll start GRUB (not syslinux) and you'll see GRUB in the boot menu title
[13:04] <TJ-> lotuspsychje: it does? where do you see that?
[13:04] <lotuspsychje> TJ-: lemme check if i can find a pic of that
[13:04] <gregl> TJ- Ok then I guess I will continue and see what happens.. I previous installs I have to make an efi partition.. I guess things change..
[13:05] <TJ-> the firmware controls which mode is used, the OS can't change it
[13:05] <TJ-> gregl: if the system already has an EFI-SP it'll be used
[13:06] <TJ-> gregl: assuming the system booted via GRUB and is in EFI mode
[13:07] <lotuspsychje> EriC^^: <gregl> I downloaded the daily image and burnt it on a usb thumb drive,but when I go to install there isn't a ufi install option.. Is there one and if so where can i get it?
[13:08] <gregl> It does have that partition and did boot from GRUB, I didn't want to update but do a fresh install, so perhaps I will wait..
[13:08] <TJ-> gregl: well it'll use the EFI-SP but reinstall te latest GRUB into it
[13:09] <TJ-> gregl: there's only the grubx64.efi/shimx64.efi/grub.cfg-base in there
[13:09] <lotuspsychje> TJ-: think it looked like this: https://i.stack.imgur.com/qSFES.png
[13:12] <TJ-> lotuspsychje: well that makes sense, but it's not a choice, it's a warning that system is in EFI mode and if re-partitioning would wipe out an existing BIOS boot (since presumably there's an MBR with the boot-loader core image in the sectors 1-2047 which would be over-written by a GPT)
[13:14] <EriC^^> gregl: what does your partition table look like?
[13:14] <EriC^^> that error msg is kind of late, i think by the time you're selecting the time zone it had already started the install process
[13:15] <TJ->  that's after partitioning and before writing the changes
[13:15] <lotuspsychje> EriC^^: oh that pic was an example for TJ- 
[13:15] <gregl> EriC^^,  Hate to ask,but how would i get that?
[13:16] <EriC^^> gregl: type "sudo parted -ls" in a terminal
[13:16] <gregl> tnx
[13:16] <TJ-> gregl: you already told us there's an EFI-SP 
[13:16] <TJ-> 14:08:15         gregl | It does have that partition and did boot from GRUB
[13:17] <gregl> TJ-,  Yes I posted a snipit from my fstab This is from my fstab  /boot/efi was on /dev/sdb1 during installation
[13:22] <EriC^^> gregl: what's the actual problem?
[13:23] <gregl> sorry it took so long.. https://pastebin.com/y9p6py18
[13:25] <EriC^^> gregl: looks good to me
[13:26] <EriC^^> what's the problem you're facing?
[13:26] <gregl> EriC^^, I wanted to do a fresh install and when I went to partition efi wasn't a choice. I've had to use it for the last 3 or 4 installs or the machine won't boot to the OS..
[13:27] <EriC^^> gregl: when the installer booted, did it present a black and white grub menu? or a set of options in the middle of the screen?
[13:27] <gregl> EriC^^, a set of options
[13:34] <hunter87> hello, i was using ubuntu 18.04 just fine but some updates (latest kernel and nvidia driver 3.90-48) i cant' get it to boot to gdm anymore, removing nvidia drivers doesnt' solve the problem but i can boot directly to gnome shell using startx with nouveu (can't with nvidia driver). i've tryied purgin every trace of nvidia driver , installing the one provided by ppa:graphics-drivers/ppa
[13:34] <hunter87> but nothing so far i'm out of ideas
[13:38] <lotuspsychje> hunter87: on xorg or wayland?
[13:38] <hunter87> nvidia-smi works fine via tty and looking at lsmod every nvidia module seems loaded
[13:38] <hunter87> xorg
[13:39] <lotuspsychje> hunter87: wich driver versions did you try exactly?
[13:39] <hunter87> installing latest nvidia-driver-390 gives 390.48
[13:40] <hunter87> the one from the ppa is 390.96 and cant boot from that also
[13:40] <lotuspsychje> hunter87: have you tried switching to another version for your card?
[13:41] <lotuspsychje> hunter87: check ubuntu-drivers list
[13:42] <hunter87> gives nvidia-driver-390
[13:42] <lotuspsychje> only that driver?
[13:42] <hunter87> yes
[13:43] <lotuspsychje> so weird, it should show your other supported drivers aswell
[13:43] <flocculant> hunter87: did you purge nvidia? did you lose the nvidia file blacklisting nouveau?
[13:44] <hunter87> if i try to install nvidia-384 it install nvidia-driver-390 anyway
[13:44] <hunter87> yes tried to purge 
[13:45] <hunter87> and i have blacklist nouveau when using nvidia driver
[13:45] <hunter87> just checked
[13:46] <Rumen> Hello there, I have Ubuntu 18.04 / 64. The issue: Missing icons in the status bar. Sometimes they appear, but in most of the times - no. Mega, Dropbox, Classic menu indicator, Weather etc ... Anybody have clue how to fix that?
[13:46] <lotuspsychje> Rumen: not all indicators work yet on 18.04
[13:47] <EriC^^> gregl: that means it booted in legacy mode, you want it to give you a black and white grub menu so it's in uefi mode
[13:47] <Rumen> Yep, but these works sometimes after I start that script:  https://gist.github.com/molotovbliss/67c54e628c55c48891fd322983c2011a
[13:47] <EriC^^> gregl: try using the one time boot options menu and select usb uefi 
[13:47] <EriC^^> next time around
[13:47] <lotuspsychje> Rumen: for those that i tested: qbittorent, nightlight,..
[13:48] <hunter87> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053 here someone suggest to use proposed list
[13:48] <ubottu> Launchpad bug 1752053 in nvidia-graphics-drivers-390 (Ubuntu) "nvidia-390 fails to boot graphical display" [Critical,Fix released]
[13:48] <hunter87> it solved nothing for me ç_ç
[13:48] <gregl> EriC^^, ok thanks for your time. I will try it tomorrow..
[13:49] <lotuspsychje> Rumen: your on xubuntu?
[13:49] <Rumen> No, Ubuntu 18.04
[13:49] <Rumen> LTS
[13:49] <lotuspsychje> kk
[13:50] <Rumen> Sometimes they appears, another times - NO
[13:50] <Rumen> Can't get when and how ... and why ...
[13:50] <lotuspsychje> Rumen: yeah not sure why yet either, lets await final?
[13:50] <Rumen> OK 
[13:51] <Rumen> Is there any way to start them?
[13:51] <Rumen> Somehow ... manually 
[13:52] <lotuspsychje> Rumen: all i have is gnome-tweak-tool to enable/disable indicators
[13:52] <Rumen> This script sometimes succeed to start them but not every time https://gist.github.com/molotovbliss/67c54e628c55c48891fd322983c2011a
[13:53] <Rumen> Thanks I will give it a try now
[13:56] <BluesKaj> i really should join here more oftern since I am runing Bionic :-)
[13:56] <lotuspsychje> BluesKaj: wb mate :p
[13:56] <lotuspsychje> BluesKaj: has been pretty active lately
[13:57] <BluesKaj> hey lotuspsychje, i thought i should try to get back in the goove again
[13:59] <lotuspsychje> BluesKaj: hows kde bionic anyway? didnt see much of those passing by?
[14:00] <Rumen> KDE works under Bionic? 
[14:00] <BluesKaj> lotuspsychje, seems fine aprt from some higher end nvidia drivers needing a patch , but that might affect all bionic 'buntus, not sure
[14:00] <lotuspsychje> !flavors | Rumen 
[14:00] <ubottu> Rumen: Recognized Ubuntu flavors build on Ubuntu and provide a different user experience out of the box. They are supported both in #ubuntu and in their flavor channel. For a list, see https://www.ubuntu.com/download/ubuntu-flavours
[14:00] <Rumen> In this case the Aegisub should start and compile, but it doesn't 
[14:03] <hunter87> i'd like to install the older nvidia-390 version, (https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/390.25-0ubuntu1) this one that last week was working
[14:03] <hunter87> but from apt-cache showpkg nvidia-driver-390 it only list the last version (the 48 one)
[14:03] <hunter87> do you know if it is possible to recover the old package?
[14:04] <lotuspsychje> hunter87: normally ubuntu-drivers list would be able to see all your drivers
[14:04] <lotuspsychje> not sure why it only shows 1
[14:05] <lotuspsychje> hunter87: another idea would be recoverymode++fix broken packages
[14:05] <lotuspsychje> remove ppa, revert to default drivers
[14:05] <lotuspsychje> as a test
[14:11] <hunter87> i'm removing bionic-proposed lowering its priority, removed ppa graphics and purging '*nvidia*' ... and removing blacklist from nouveu leìts see if this time gdm boot..
[14:11] <lotuspsychje> ok
[14:13] <hunter87> lol booted me to text mode
[14:14] <lotuspsychje> try !nomodeset to get in
[14:14] <hunter87> in grub?
[14:14] <lotuspsychje> !nomodeset
[14:14] <ubottu> A common kernel (boot)parameter is nomodeset, which is needed for some graphic cards that otherwise boot into a black screen or show corrupted splash screen. See http://ubuntuforums.org/showthread.php?t=1613132 on how to use this parameter
[14:15] <hunter87> i have already GRUB:CMDLINE_LINUX_DEFAULT="nomodeset"
[14:15] <hunter87> GRUB_CMDLINE_LINUX_DEFAULT="nomodeset"
[14:18] <lotuspsychje> hunter87: ok, where does your system get stuck on atm?
[14:18] <hunter87> was in text mode and did sudo systemctl restart gdm3.service 
[14:18] <hunter87> now black screen and can't even tty
[14:20] <lotuspsychje> hmm reboot?
[14:20] <hunter87> yes but can access via ssh
[14:20] <lotuspsychje> hunter87: wich card are you on anyway?
[14:20] <hunter87> nvidia gtx 980
[14:20] <lotuspsychje> kk
[14:21] <BluesKaj> hunter87, did update grub after the nomodeset edit?
[14:21] <hunter87> yes
[14:21] <BluesKaj> ok
[14:23] <BluesKaj> what about recovery mode ?
[14:24] <hunter87> will try
[14:25] <lotuspsychje> seems like something got scrambled
[14:25] <hunter87> but what i do not understand is that now that i've removed nvidia driver
[14:25] <hunter87> gdm does not load
[14:25] <hunter87> but if from tty i login and do startx it loads just fine
[14:25] <lotuspsychje> hunter87: after purge of nvidia, normally you should fallback to nouveau
[14:25] <lotuspsychje> unless you blacklisted it?
[14:25] <hunter87> yes i'm with nouveau
[14:26] <lotuspsychje> ok so if nouveau doesnt boot, we try to nomodeset into the system or recoverymode and install an nvidia- driver
[14:26] <hunter87> but nouveau with startx works (gdm not)
[14:27] <BluesKaj> i thought he already tried the nvidia driver
[14:27] <lotuspsychje> startx is not the right way anymore hunter87 
[14:27] <lotuspsychje> BluesKaj: he gets stuck on latest 960 driver from ppa
[14:27] <hunter87> nono
[14:27] <hunter87> 390 from default
[14:27] <BluesKaj> don't use a ppa driver 
[14:28] <hunter87> not using ppa
[14:28] <lotuspsychje> oh?
[14:28] <BluesKaj> use the recommended driver 
[14:28] <lotuspsychje> <hunter87> i'd like to install the older nvidia-390 version, (https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/390.25-0ubuntu1) 
[14:28] <hunter87> i was on default list with nvidia-driver-390 (subversion 25) last week and it was working
[14:28] <BluesKaj> think it's probly the nvidia-390
[14:29] <hunter87> than i got an update to nvidia-driver-390 (sub version 48) and upon reboot it does not work anymore
[14:29] <hunter87> i tried to enable bionic-proposed like some people said in https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053 but no luck
[14:29] <ubottu> Launchpad bug 1752053 in nvidia-graphics-drivers-390 (Ubuntu) "nvidia-390 fails to boot graphical display" [Critical,Fix released]
[14:30] <hunter87> than i tried https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa this ppa with a newer version no luck either
[14:31] <hunter87> and it seems i cannot find the 390-25 driver from last week anymore
[14:32] <lotuspsychje> hunter87: have you tryed booting another kernel?
[14:33] <hunter87> yes i only have 2 tried both of them.. rebooting in recovery right now
[14:33] <BluesKaj> think I'll stick with nouveau for now
[14:33] <hunter87> cant debug or understand why gdm fails
[14:34] <hunter87> even with nouveau
[14:34] <lotuspsychje> hunter87: could be that loginloop bug aswell
[14:34] <BluesKaj> should be runninig sddm
[14:35] <BluesKaj> hunter87,^
[14:35] <hunter87> sddm?
[14:36] <BluesKaj> doesn't ubuntu use sddm login, lotuspsychje
[14:36] <BluesKaj> ?
[14:36] <lotuspsychje> BluesKaj: ubuntu-desktop uses gdm3 on gnome now
[14:36] <BluesKaj> ok, thanks for the heads up, lotuspsychje
[14:36] <hunter87> mm i'll try to install lightdm let'see
[14:37] <lotuspsychje> np
[14:40] <hunter87> fuck gdm, with lightdm it boots..
[14:42] <lotuspsychje> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1705369
[14:42] <ubottu> Launchpad bug 1705369 in gdm3 (Ubuntu) "Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)" [High,Confirmed]
[14:42] <lotuspsychje> related?
[14:43] <hunter87> seems related but was not using wayland
[14:43] <hunter87> trying to reinstall nvidia driver.. finger crossed
[14:45] <lotuspsychje> hunter87: answer #50 says he had to uninstall gdm3 too
[14:45] <lotuspsychje> weird things going on jesus
[14:46] <lotuspsychje> also read #93 hunter87 
[14:47] <hunter87> it works!
[14:47] <hunter87> nvidia driver + lightdm
[14:48] <hunter87> gdm3 was fucked up somehow, but didnt need to uninstall
[14:48] <lotuspsychje> !yay | hunter87 
[14:48] <ubottu> hunter87: Glad you made it! :-)
[14:48] <hunter87> in the future in my lab we will have to update every workstation to 18.04 it will be fun xD
[14:49] <hunter87> thanks for the help lotuspsychje 
[14:49] <dupondje> hunter87: dual screen perhaps?
[14:49] <lotuspsychje> hunter87: perhaps add your experience to the bug?
[14:49] <hunter87> yes usually dual screen but right now i detached the second monitor to reduce the number of possible source of bugs
[14:51] <dupondje> ah ok, because https://gitlab.gnome.org/GNOME/mutter/issues/81 :)
[14:51] <dupondje> causes black screens with multiple monitors
[14:56] <hunter87> well i need to go thanks again for your help :)
[14:56] <lotuspsychje> laterz
=== J03Y_1 is now known as J03Y
=== J03Y is now known as j03y
[15:14] <jack_> hello everyone , i update my ubuntu  18.04 today,after restart my computer ,i can launch the system :(,told me "try(hd0,0):NTFS5:no ang0......."
=== larry__ is now known as lapaga
[15:20] <zanshin> jack_: This may help https://unix.stackexchange.com/questions/55398/getting-ntfs5-no-ang0-error-message-when-booting-linux-mint
[15:21] <jack_> thx
[16:37] <bodie__> TJ-, not quite sure what full path to the package for the bug report I should be using
[16:38] <bodie__> I have bionic/nvidia-driver-390 since that's the path in launchpad, but that isn't registered as a project
[16:38] <lotuspsychje> !find unity desktop
[16:38] <ubottu> desktop is not a valid distribution: artful, artful-backports, artful-proposed, bionic, bionic-backports, bionic-proposed, kubuntu-backports, kubuntu-experimental, kubuntu-updates, partner, precise, precise-backports, precise-proposed, stable, testing, trusty, trusty-backports, trusty-proposed, unstable, utopic, utopic-backports, utopic-proposed, vivid, vivid-backports, vivid-proposed, wily, wily-backports, wily-proposed, xenial, xenial-backports, xenia
[16:39] <bodie__> not sure if that's a response to me lotuspsychje :) 
[16:40] <bodie__> here's the path in LP: https://packages.ubuntu.com/bionic/nvidia-driver-390
[16:41] <bodie__> the "failing command" on the bug report email is "affects bionic/nvidia-driver-390
[16:41] <bodie__> "
[16:41] <teward> bodie__: `ubuntu-bug nvidia-driver-390` doesn't work?
[16:41] <teward> assuming you run it on the CLI from an 18.04 install, that is.
[16:41] <bodie__> I'm using the email instructions, but it's not that clear on how to identify the package name
[16:43] <teward> LP's email interface is not useful
[16:43] <teward> but you'd be doing `affects $distribution/$distro_series/$package`, so `affects ubuntu/bionic/nvidia-driver-390`
[16:44] <bodie__> gotcha
[16:44] <bodie__> I had some explanation written up -- it doesn't look like ubuntu-bug lets you write a description of the problem before pushing send
[16:46] <teward> well `ubuntu-bug` usually gives you a *link* you open in a web browser to create the bug, and it lets you add details during that timeframe
[16:46] <bodie__> ah, ok
[16:46] <bodie__> if this attempt fails then I'll go with that approach
[16:47] <bodie__> teward, I don't suppose there's an SMS integration for LP, too? ;) 
[16:47] <teward> bodie__: nobody has SMS integration in their BTS>
[16:47] <teward> SMS is expensive :P
[16:47] <bodie__> and no gnupg plugin...
[16:50] <bodie__> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1763774
[16:50] <ubottu> Launchpad bug 1763774 in nvidia-graphics-drivers-390 (Ubuntu) "nvidia-driver-390 GDM black screen / hang after login" [Undecided,New]
[16:50] <lotuspsychje> we seen this issue today already
[16:51] <lotuspsychje> gdm3 replaced by lightdm, did the trick
[16:53] <bodie__> yeah?  I'll give that a try :) 
[16:54] <lotuspsychje> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1705369
[16:54] <ubottu> Launchpad bug 1705369 in gdm3 (Ubuntu) "Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)" [High,Confirmed]
[16:54] <bodie__> thx!
[16:54] <lotuspsychje> #50 and #93
[16:54] <bodie__> I did have it working in 17.10, fwiw
[16:55] <bodie__> lotuspsychje, worked for me.
[16:55] <lotuspsychje> bodie__: add your experience to the bug plz?
[16:56] <lotuspsychje> and add yourself affected
[16:56] <bodie__> will do 
[16:56] <lotuspsychje> tnx mate
[16:56] <bodie__> :+1:
[16:57] <bodie__> done
[16:57] <lotuspsychje> tnx, that helps the community bodie__ 
[17:04] <bodie__> o7
=== akem__ is now known as akem
[17:58] <sublime48> hi, I installed 18.04 Beta 2 on my built PC today...experiencing very slow wi-fi (ubuntu got 3 mbps on speedtest.net, mbp got 100 mbps)
[17:58] <sublime48> i3-8100 on a H370N WIFI
[20:07] <katnip> https://news.softpedia.com/news/ubuntu-18-04-lts-integrates-canonical-livepatch-for-rebootless-kernel-updates-520680.shtml
[21:38] <terminalator> I've upgraded to 18.04 beta. After a while a noticed that installed packages (rtorrent, feh and a few others) are constantly removed after doing upgrades. Is this normal?
[21:44] <brainwash> terminalator: doesn't look normal to me
[21:44] <terminalator> brainwash: Hmmm, I see.
[21:45] <terminalator> Stange indeed
[21:50] <brainwash> you do upgrades manually?
[21:51] <brainwash> I mean it would help to see what apt is actually doing
[21:52] <brainwash> as in what is the terminal output
[21:59] <nacc> terminalator: what brainwash said, as upgrade shouldn't remove anything
[21:59] <nacc> dist-upgrad and full-upgrade can
[22:00] <terminalator> I may have found the issue
[22:01] <terminalator> I have, thanks for pointing me in right direction all
[22:02] <terminalator> I'm using a script that does automatic upgrades when logging in
[22:02] <valorie> when full-upgrade removes something, that sounds like a good thing
[22:02] <nacc> valorie: right
[22:02] <terminalator> I has dist-upgrade in it
[22:02] <nacc> it usually means the thing removed is broken by a new package
[22:03] <valorie> I never upgrade
[22:03] <nacc> terminalator: however, both feh and rtorrent are still available in the repos, so you could look at what is in them
[22:03] <valorie> only full-upgrade
[22:03] <nacc> valorie: nor i :)
[22:03] <terminalator> nacc: Would you recommend removing dist-upgrade from my upgrade script?
[22:04] <nacc> terminalator: why are you scripting this? rather than using unattended-upgrades
[22:56] <jerichowasahoax> got what i needed out of /topic, thank you
[23:45] <mattfly> hi
[23:45] <mattfly> Why is ubuntu bionic consuming so much battery ?
[23:45] <mattfly> since ubuntu 16.04 i have this problem
[23:49] <mattfly> also I am having some lagging behaviour, desktop animations get stuck
[23:51] <akem> Check if something's using too much CPU maybe.
[23:52] <akem> Gnome-shell may have troubles, there is still an annoying bug with it.
[23:52] <akem> AFAIK.