[00:14] <FurretUber> When I initialize a QEMU/libvirt virtual machine with using QXL screen, if I change resolution it generally freezes/crashes
[00:16] <FurretUber> Using QEMU with -vga qxl and a Artful/Bionic guest, it's nearly 100% reproducible. tsimonq2: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1755912 as you are one of the four users that should be able to see it
[00:16] <ubottu> Error: launchpad bug 1755912 not found
[00:16] <tsimonq2> Oh hai.
[00:16] <tsimonq2> Looking.
[00:17] <FurretUber> I have noticed another problem: as I boot any VM using QXL, it uses approximately 128 MB of swap that is never freed
[00:18] <FurretUber> Even with more than 3 GB of free memory
[00:19] <tsimonq2> FurretUber: Poked.
[00:22] <FurretUber> Thank you, I'm worried with this bug
[00:24] <tsimonq2> No problem.
[00:24] <tsimonq2> FurretUber: Other than that, how's testing going? ;)
[00:26] <CuChulaind> Bashing-om, Are you available again?
[00:26] <FurretUber> After the Beta release it's mostly stable, Pidgin is being troublesome (one freeze and one crash), a few small bugs in Xfce4 (one we went until very late debugging in #xubuntu-devel)
[00:27] <FurretUber> After the beta, had nearly no issues by using Bionic as my main system
[00:27] <CuChulaind> I had a great amount of help earlier this evening with my video and setup, especially trying to get my system to shut down properly. It had been working, but now for some reason it is not. When I use the software shutdown or reboot, my system just hangs on the desktop screen. 
[00:29] <CuChulaind> This morning Bashing-om worked with me to set my ascpi to Windows 2015, and my video driver to xorg nouveau which seemed to have been working. Those settings are still in place but my system won't shut down
[00:29] <CuChulaind> any ideas what other setting I need to check?
[00:32] <FurretUber> Some critical (to me, not in Launchpad :p) hardware issues were addressed in the linux mainline (one caused a panic on boot, another limited greatly power management and a regression caused problems with Ethernet), and it's being evaluated to backport the fixes
[00:33] <FurretUber> But I found things as strange as this: https://bugs.launchpad.net/ubuntu/+source/htop/+bug/1766030
[00:33] <ubottu> Launchpad bug 1766030 in htop (Ubuntu) "CPU usage has a color with no description" [Undecided,New]
=== brainwash_ is now known as brainwash
[02:07] <paddy> I'm using 18.04beta2 and have xpad installed. When I try to connect my xbox one controller through bluetooth it only shows the mac address and when I go to connect it doesn't connect. I have done sudo modprobe xpad and then lsmod shows that xpad is there but still doesn't work. I reboot and xpad isn't in lsmod list
[02:10] <paddy> sudo dkms install -m xpad -v 0.4
[02:10] <paddy> Module xpad/0.4 already installed on kernel 4.15.0-15-generic/x86_64
[02:13] <valorie> please test the RC instead of the beta
[02:13] <valorie> that is weeks old
[02:13] <valorie> https://lists.ubuntu.com/archives/ubuntu-release/2018-April/004438.html
[02:21] <Bashing-om> paddy: valorie : Adam Conrad as asking for testing the final: http://iso.qa.ubuntu.com/qatracker/milestones/389/builds .
[02:24] <valorie> right, it's called final but it's not actually final
[02:24] <valorie> it's the release candidate-with-a-couple-of-known-bugs
[02:24] <Bashing-om> valorie: Oops .. You did pass Adam's request :)
[02:24] <valorie> yup, I'm testing now
[02:25] <valorie> <--- kubuntu release manager
[02:25] <ChmEarl> trying to lighten my initrd.img.. with `modules=dep` in initramfs.conf, the size is 20MB.. I need it barely over 10MB
[02:28] <Bashing-om> valorie: Good to keep in mind .. maybe then I not step on so many toes :)
[02:45] <valorie> my toes are fine, lol
[02:48] <Bashing-om> valorie: :D
[03:52] <CuChulaind> Bashing-om, you there?
[03:53] <Bashing-om> CuChulaind: I be in and out .. focused elsewhere . What's up ?
[03:54] <CuChulaind> Bashing-om, thank you. Machine won't shut down again. I didn't touch any of the settings from last night. Any ideas what I should look at now? Ascpi is the same, as well as the same video driver
[03:56] <Bashing-om> CuChulaind: How have you been shutting down ? File system now corrupted ?
[03:57] <CuChulaind> I shut down last night /this morning, worked well. Started up computer today, tried to log out, as I had add myself to the docker group (so as not to need sudo), and it locked up. 
[03:58] <CuChulaind> Shut down when we were done earlier was via the gui (vs cli)
[04:00] <Bashing-om> CuChulaind: If you shut down from terminal, does the system generate any errors back to the terminal ?
[04:01] <CuChulaind> I have yet to try anything else. When it didn't log me out, I did a hard reboot, upon successful start, I tried shutdown via gui to see if that worked, It hung did another hard shutdown. What command do you recommend I execute? Simple sudo shutdown?
[04:03] <Bashing-om> CuChulaind: ' sudo systemctl poweroff ' .
[04:03] <CuChulaind> Will do and report back
[04:08] <CuChulaind> Bashing-om, at command execution, I entered password, upon hitting enter, total freeze, nothing sent to the CLI.
[04:08] <CuChulaind> Bashing-om, looking through logs now
[04:09] <Bashing-om> CuChulaind: :( ........
[04:12] <CuChulaind> Bashing-om, I'll take a look around and see what I can find. Will let you know if I see anything that stands out, Probably tomorrow or so if that's ok?
[04:12] <CuChulaind> Bashing-om, I still have very little on here, and nothing I need to save, i can relatively easily do  a fresh install
[04:15] <Bashing-om> CuChulaind: try the less invassiv ' sudo systemctl reboot ' as a test to try amd isolate where the failure might be . 
[04:18] <CuChulaind> Bashing-om, No issue with reboot command from CLI
[04:19] <CuChulaind> Bashing-om, Going to now try it from the GUI FWIW
[04:20] <Bashing-om> CuChulaind: That do give us pause for thought - ' sudo systemctl halt ' ?
[04:21] <CuChulaind> Bashing-om, I have NO clue. Just successfully did a reboot, and a shutdown using the GUI
[04:22] <FurretUber> Is it really impossible to set the language when booting in UEFI mode or I`m missing a option?
[04:23] <CuChulaind> Bashing-om, If you think of anything to check, please let me know. I'm calling it a night early
[04:24] <FurretUber> I think the two options (~Try Ubuntu without installing~ and ~Install Ubuntu~) should be merged into one
[04:24] <FurretUber> Using maybe-ubiquity as a options, so the Ubiquity window will open
[04:25] <FurretUber> And te user is able to choose a language
[04:31] <FurretUber> This is one idea? https://paste.ubuntu.com/p/PGzby4hQqH/
[04:32] <Bashing-om> CuChulaind: Shutdown issues can be a real pain .. as when the file system is unmounted, no more logging is possible.
[04:41] <FurretUber> I reported against ubiquity, but the problem is in the grub.cfg used in the ISOs: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766047
[04:41] <ubottu> Launchpad bug 1766047 in ubiquity (Ubuntu) "Impossible to choose a language when booting in UEFI, as Ubiquity never opens due to problematic grub config" [Undecided,New]
[04:47] <CuChulaind> Bashing-om, FWIW just ran what I could recall may have been different scenarios during shutdown (laptop plugged in, not plugged in, various combos of programs I may have had open in the pst etc), and now it doesn't hang. Will try to be more aware of the machine status on each shutdown now
[04:50] <Bashing-om> CuChulaind: My shut down process is to close all apps out then shutdown the system .
[05:00] <FurretUber> May somebody mention me? I`m testing a pidgin bug
[05:00] <Bashing-om> FurretUber: workie ?
[05:01] <FurretUber> Well, another bug happened o.o
[05:02] <FurretUber> The indicator messages did not work
[05:02] <FurretUber> I was trying to test https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1765846
[05:02] <ubottu> Launchpad bug 1765846 in pidgin (Ubuntu) "Pidgin freezes if two windows with chat are closed" [Undecided,New]
[05:56] <luna_> Installing 18.04 RC1 now
[05:57] <lotuspsychje> good to hear that luna
[05:57] <luna_> thanks Adam Conrad and Simon Quigley for the heads up
[05:58] <luna_> updating to Beta 2 now to update to RC1 after that
[05:58] <lotuspsychje> !final | luna_ 
[05:58] <ubottu> luna_: If you install a development version of Ubuntu Bionic and keep up with package updates, then you will be upgraded to the official release of 18.04 when it comes out. To make sure, type « sudo apt update && sudo apt full-upgrade » in a terminal.
[05:58] <lotuspsychje> just keep your system up to date, at all times and you be good
[06:06] <luna_> done
[06:38] <valorie> luna_: please file bug reports when you find something!
[06:39] <valorie> this is the last chance to get those things fixed
[06:39] <valorie> if possible
[06:39] <valorie> `ubuntu-bug packagename` in the commandline
[06:40] <luna_> valorie: will do if i found something only thing i found so far was that qt was to new to run my version of Telegram so had to download a new version of Telegram from their website
[06:46] <valorie> hmmm
[06:47] <valorie> there is telegram-desktop packaged
[06:47] <valorie> !info telegram-desktop
[06:47] <ubottu> telegram-desktop (source: telegram-desktop): official telegram messaging app. In component universe, is optional. Version 1.2.15-1build1 (bionic), package size 16775 kB, installed size 29986 kB
[06:47] <valorie> luna_: why did you get it from their website?
[06:47] <luna_> valorie: did not know there was a package thanks
[06:48] <luna_> changed to the package now thanks
[06:48] <valorie> cool
[06:56] <guiverc> should 18.04 bugs be marked in some special way?
[07:09] <tsimonq2> guiverc: Not really, have a specific one that needs attention?
[07:23] <guiverc> thanks tsimonq2, not really - https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1765897 is what i was thinking of .. (badly worded; but its me) .. i suspect b/c my monitors have weird placement i'm getting video glitches (left of 2nd monitor) only in gnome in X  (not wayland, nor mate)
[07:23] <ubottu> Launchpad bug 1765897 in meta-gnome3 (Ubuntu) "vertical graphic lines glitch (on secondary top monitor)" [Undecided,New]
[07:34] <flocculant> is it right that there's no way to set llanguage and keyboard on uefi live session?
[07:34] <flocculant> llanguage isn't Welsh - just fat fingers :p
[07:52] <luna_> valorie: that package works better then the tarball from Telegrams website thanks :)
[07:53] <valorie> lovely!
[09:46] <sadmo> hi u all
[09:46] <sadmo> anyone there?
[09:46] <lol-md5> no
[09:46] <lol-md5> chat ded ofc
[09:47] <sadmo> :D
[09:48] <sadmo> I have a problem with 18.04 install
[09:48] <sadmo> could someone help me?
[09:48] <sadmo> i can't install latest ubuntu 18.04 beta. I have an NVIDIA 1070 so I have a problem with drivers. I boot from usb with nomodeset, install, reboot with nomodeset, then I install the NVIDIA drivers and then I can't boot anymore even with nomodeset
[10:04] <katnip> when is the 'freeze'
[10:04] <lol-md5> https://wiki.ubuntu.com/BionicBeaver/ReleaseSchedule katnip 
[10:04] <katnip> ty
[10:08] <sadmo> please someone who would like to support me?
[10:10] <flocculant> patience is a virtue seldom seen on irc 
[10:10] <lol-md5> i'm mildly surprised they weren't using a web client
[10:13] <katnip> how can i have both chrome and ff default? i do
[10:14] <katnip> i wonder if i reinstall ff
[10:14] <lol-md5> you can't have two browsers as default
[10:14] <katnip> it wont sync either
[10:14] <katnip> i do
[10:15] <lol-md5> oh
[10:15] <lol-md5> oh there's a discrepancy between settings i think
[10:15] <katnip> both ff and chrome are default
[10:15] <lol-md5> ask in #ubuntu how to set a browser as default, as i think there's no difference
[10:15] <katnip> hexchat opens a link in ff instead of chrome
[10:16] <katnip> i have it set in the preferences/settings in ubuntu 18.04
[10:16] <katnip> weird
[10:16] <katnip> what is the command to reinstall an app
[10:17] <flocculant> apt install --reinstall afaik
[10:17] <katnip> thanks
[10:20] <katnip> i had to just remove ff as it didnt work and to open a link with chrome in hexchat i had to
[10:20] <katnip> very odd
[10:20] <katnip> never seen that
[12:17] <CoJaBo> so, I have a crash that's not logged by netconsole, isn't affected by the "reboot on panic" kernel parameters, and the system ignores nmi-watchdog; is there anything I can do at this point beyond blindly replacing parts?
[13:26] <flocculant> anyone know if tomcat is still expected to be installable still ? http://iso.qa.ubuntu.com/qatracker/testcases/1410/info
[14:36] <howarth> Is anyone seeing the following issue with the bionic installer? On a 2008 MacPro, I am finding that the installer doesn't seem to reboot completely after the install is finished and I click restart.
[14:36] <howarth> This issue didn't occur with the Artful installer on the same machine.
[14:37] <howarth> I get the black screen with system log entries being output but it never seems to actually reboot and I have to do a hard reset.
[14:38] <howarth> Otherwise the installation looks fine but it is rather rough to force a reboot like that.
[14:38] <flocculant> howarth: different people see similar at different times on the same machines be it hardware or vm
[14:38] <howarth> With just bionic or with artful as well?
[14:39] <flocculant> I've booted a vm 5 times recently and seen the remove media 4 times
[14:39] <fcanela> hello, is there a place in which I could see the changes done to bionicbeaver daily build each day?
[14:39] <flocculant> howarth: since years
[14:39] <fcanela> some development public repository or so
[14:39] <howarth> Odd that artful seemed so immune to it
[14:39] <howarth> I did tons of installs on the same hardware and never tripped over that until bionic
[14:40] <flocculant> fcanela: close would be checking the manifest against an old one - but rather pointless now 4 days before release, unless of course you grab a current manifest and check against artfukl
[14:40] <flocculant> howarth: artful wasn't immune to it
[14:41] <fcanela> flocculant: where can I find those manifest?
[14:42] <fcanela> I am just curious, flocculant, so no problem if there is just boring or small changes
[14:42] <flocculant> if you want to see the changes to the daily build historically you likely won't find it 
[14:43] <fcanela> i am fine with a repo in which I can see different versions of a file
[14:43] <fcanela> or something like that
[14:43] <flocculant> no idea I'm afraid
[14:43] <fcanela> I am curious about where the release is currently hosted
[14:43] <fcanela> (i suppose launchpad)
[14:43] <fcanela> and how it is build collaborativelly
[14:44] <flocculant> and you'd not read all the changes made since bionic started on lp on all of the packages before it releases I would doubt :)
[14:46] <flocculant> fcanela: this is the manifest for the current daily http://cdimage.ubuntu.com/ubuntu/daily-live/current/bionic-desktop-amd64.manifest
[14:46] <fcanela> thanks, I will dig into docs
[14:46] <howarth> Wonder how long after bionic is released that we will have to wait for a 14.16 kernel?
[14:47] <howarth> It would be nice if they go get the suspend issues ironed out enough to make it usable on radeon drivers.
[14:47] <flocculant> howarth: be a short while I expect 
[14:48] <flocculant> howarth: I assume you mean for cathartic or cantankerous or whatever c we'll get 
[14:48]  * flocculant personally hopes for the second :D
[14:48] <howarth> Currently it still corrupts the graphics irreversibly every five or six entries back from suspension 
[14:49] <flocculant> well - that's better than no network on every suspend
[14:49]  * flocculant reported that a while back - but doesn't actually suspend so isn't too worried if no-one else is
[15:06] <guardian> is there any advantage waiting for next week end to install bionic?
[15:07] <guardian> I understood from now to release package updates are only bug fixes and I somewhat expect the same to happen after bionic is released
[15:11] <howarth> I suspect they are close to just doing tweaks to the installer and the setup packages at this point.
[16:02] <mattfly> hi
[16:02] <mattfly> any hope for this bug: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1762885
[16:02] <ubottu> Launchpad bug 1762885 in sddm (Ubuntu) "SDDM fails to start on laptops modern NVidia cards" [Undecided,New]
[16:06] <tinch1> Hello, I have a question about installing Ubuntu Budgie 18.04 beta 2 on my new laptop.
[16:07] <tinch1> I've disabled secure boot in bios and fast boot in windows options. Both things you're meant to do.   On my old machine in the built in installer it would just auto-partition your HDD for you, but on this one it doesn't appear.   I'm wondering whether it's connected to ubuntu not being able to read my windows SSD and access the files.   The GUI installer comes up, but the one click "install next to windows" wizard check box does no
=== tomreyn_ is now known as tomreyn
[16:36] <brainwash> mattfly: isn't this fixed in sddm 0.17.0-1ubuntu7 ?
[16:37] <mattfly> no, i dont think so
[16:37] <mattfly> im on blender-2.79b-linux-glibc219-x86_64.tar.bz2
[16:37] <mattfly> aw sorry
[16:37] <mattfly> verrsion (0.17.0-1ubuntu7).
[16:37] <mattfly> of sddm
[16:40] <brainwash> mattfly: so, it's not related to bug 1763977
[16:40] <ubottu> bug 1763977 in sddm (Ubuntu) "Sddm service fails in Bionic" [High,Fix released] https://launchpad.net/bugs/1763977
[16:40] <brainwash> correct?
[16:40] <mattfly> no sddm doesnt fail to start
[16:41] <mattfly> this is my bug: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1762885
[16:41] <ubottu> Launchpad bug 1762885 in sddm (Ubuntu) "SDDM fails to start on laptops modern NVidia cards" [Undecided,New]
[16:41] <mattfly> it is not displayed
[16:41] <mattfly> you have a black screen, if you type your password and hit enter it logs in, you just cant see sddm
[16:45] <brainwash> mattfly: I would add the nvidia driver to the list of affected packages, and also forward the issue to https://github.com/sddm/sddm/issues
[16:46] <mattfly> okay
[16:48] <dieg> Hi, I recently upgraded from 17.10 to 18.04. The software center on this version seems to always be stuck at Installing 0%. I think it could be a bug, is it happening to somebody else ?
[16:48] <dieg> I have tried reinstalling the package so far and clearing the cache, but still the same.
[17:33] <MikeRL> Are the major memory leaks in GNOME patched yet?
[17:36] <MikeRL> I saw one as patched, but how bad is it?
[17:41] <katnip> what does this mean on the release date : Warning /!\ FinalRelease,
[17:43] <MikeRL> Hmm. I think I'll download it and try myself.
[17:46] <katnip> anyone have an idea?
[19:05] <jmgb4> Hey fellas, I am looking at upgrading my system to 18.04 before its officially released. Is there a specific guide I should follow? I tried one already and its not pulling any 18x updates
[19:06] <jmgb4> Im actually following this guide right now, not pulling updates. https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes
[19:07] <lol-md5> i think https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes#Upgrading_from_Ubuntu_16.04_LTS_or_17.10 assumes that 18.04 has been released
[19:08] <jmgb4> Thats stupid
[19:08] <jmgb4> Lol
[19:08] <jmgb4> Well theres my problem
[19:10] <tomreyn> do-release-upgrade -d
[19:10] <tomreyn> jmgb4: ^
[19:10] <jmgb4> Niiooce
[19:10] <jmgb4> That did it
[19:11] <jmgb4> I love it. Installing could take several hours. I call BS on that
[19:14] <lapaga> https://itsfoss.com/upgrade-ubuntu-version/
[19:56] <flocculant> jmgb4: so why do you think it won't take hours? because it didn't for you?
[19:59] <matlock> any experts on snap or snapcraft here? https://forum.snapcraft.io/t/snapcraft-breaking-over-nested-cmake-not-moving-built-files-into-staging-prime-and-dependency-issues/5084
[19:59] <matlock> I am trying to build this on 18.04 beta, so we'll have a decent working GUI rss reader ready for 18.04 final
[20:23] <tomreyn> matlock: i think there is #snaps
[21:12] <flying_sausages> hey guys, I just made a fresh 16.04, what's the best way to upgrade to 18.04?
[21:25] <flying_sausages> turns out just this will do the trick $ sudo do-release-upgrade
[21:41] <BionicMac> +1 excellent RC -- flawless install on (K) and Ubuntu-gnome everything detected on the iMac. Nuff said. =) Thanks to all that play a part in the *ubuntu-dev and community for that matter. 
[21:41] <BionicMac> Hats off. Peace
[22:27] <wagle> i take it u1804 is real now?
[22:27] <wagle> upgrade was bumpy
[22:29] <wagle> gets very confused about what to tell me about what is happening, uses scary language, but seems to be getting somewhere
[22:30] <BionicMac> wagle: First spin of a 18.04 Release Canditate is ready for testing.
[22:30] <wagle> ah, that would be it then
[22:31] <BionicMac> Solid. I did a fresh install of Ubuntu-gnome and Kubuntu. Solid.
[22:31] <wagle> it's all been working fine for me
[22:32] <wagle> except for this "partial upgrade" thing, which sounds like "your apt repository is corrupt!  dependency hell time!"
[22:32] <wagle> but I guess not
[22:34] <wagle> hmm..  "livepatch now"
[22:34] <BionicMac> I've been full-upgrade daily for a month. Np. Fresh install from yesterday's RC.
[22:35] <wagle> I gues I needed it to pile up..  its not telling eachday to upgrade
[22:35] <BionicMac> https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes
[22:36] <BionicMac> command central ^ should find everything ya need.= including download links.
[22:38] <BionicMac> wagle: https://kubuntu.org/news/bionic-18-04-release-candidate-images-ready-for-testing
[22:41] <wagle> BionicMac: cool, thanks!
[22:44] <mjw99> Is there anyway to get some traction on this Java issue (https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1739631), that now has an upstream fix, before Bionic is released?
[22:44] <ubottu> Launchpad bug 1739631 in ca-certificates-java (Ubuntu) "Fresh install with JDK 9 can't use the generated PKCS12 cacerts keystore file" [Undecided,Confirmed]
[23:54] <donofrio> do I do-release-update from current packages of 18.03 install or just keep doing dist-upgrades and enjoy this great release?
[23:58] <Bashing-om> !final | donofrio 
[23:58] <ubottu> donofrio: If you install a development version of Ubuntu Bionic and keep up with package updates, then you will be upgraded to the official release of 18.04 when it comes out. To make sure, type « sudo apt update && sudo apt full-upgrade » in a terminal.
[23:59] <donofrio> apt full-upgrade = apt-get dist-upgrade?