=== nt0__ is now known as nt0
[01:22] <feoh> Hi all. Does anyone on off chance know how to enter emoji in 20.04? The advertise right click doesn't work, and I can't ctrl+. because 1Password hooks that keystroke :)
[01:24] <feoh> Ah, pardon, scratch that. Just read that Firefox doesn't use the standard input controls
[02:54] <lotuspsychje> good morning
[03:04] <feoh> Morning!
[03:05] <lotuspsychje> hey feoh 
[03:07] <feoh> lotuspsychje: How's life? Staying healthy and sane I hope :)
[03:07] <lotuspsychje> yes sir, trying to remain at home as much possible
[03:10] <feoh> Us too. Lucky enough to be gainfully employed in jobs where we can both remote work.
[03:12] <lotuspsychje> ah thats nice mate
[03:17] <feoh> So how goes the release testing? 20.04 is coming along nicely
[03:17] <feoh> I've been totally impressed that when I see an issue before I can report it it's fixed in a few hours :)
[03:17] <lotuspsychje> good, think i filed around 15 bugs atm
[03:21] <lotuspsychje> things are shaping pretty nice
[03:22] <lotuspsychje> first everyone presumed fossa was going to be a flat release
[03:22] <lotuspsychje> but a lot of cool candy inside already
[03:38] <feoh> Oh totally. The Gnome improvements alone are bonkers!
[03:38] <lotuspsychje> yeah not bad
[03:39] <feoh> Also dropping Python2 is a nice step. Puts more pressure on the "Python 3 isn't a real thing until they pry my Python 2 out of my cold dead hands" crowd :)
[03:40] <lotuspsychje> heh
[04:05] <feoh> Have a great night.
[04:05] <lotuspsychje> nite
=== Katnip is now known as yarddog
=== yarddog is now known as Guest63603
=== Guest63603 is now known as katnip
=== pavlushka_ is now known as pavlushka
=== leden__ is now known as leden
[12:18] <shemgp> hello, anyone knows how to test subiquity in focal server daily iso? I tried it and it seems to be using debian installer.
[14:25] <tim23423424> hello everyone - I'm running Ubuntu 20.04 on a ThinkPad P50 with I think an Nvidia GPU. Yesterday my external monitor (an LG plugged in with HDMI) worked fine, and then after doing an apt update/upgrade I rebooted and am having some weird issues where screen refresh seems to be quite messed up, but only when the Desktop is visible. It looks like the desktop background isn't being drawn except for the top left corner (and my des
[14:25] <tim23423424> kground image fits into that smaller top left corner). I also deleted ~/.config/monitors.xml  -- before I did that my monitor wasn't appearing at all and the Displays part of Settings was seeing the monitor but telling me "for hardware reasons" it wasn't working
[14:27] <oerheks> i think your thinkpad has a short key FN , to switch internal/external/both, what happens if you toggle this?
[14:29] <tim23423424> hmm, I have an external keyboard plugged in, the laptop keyboard has a symbol of three rectangles within a larger rectangle which is maybe the only one that I could interpret as "monitor toggle", it doesn't seem to do anything
[14:32] <oerheks> FN + F7 ??
[14:33] <tim23423424> F7 has a little camera symbol next to it. Toggling does nothing
[14:34] <tim23423424> (FWIW in case it wasn't clear, Settings->Displays now works to turn this monitor on, but I get weird non-refreshing happening only when the Desktop is visible)
[14:34] <tim23423424> and only in a certain region of the Desktop
[14:34] <oerheks> oke, and did you try to reset the monitor with its own keys to factory standard?
[14:35] <tim23423424> not yet, trying now...
[14:36] <tim23423424> now I'm back to the monitor not working at all - Settings says "Changes cannot be applied. This could be due to hardware limitations". It sees the monitor but can't set my SEttings to use it
[14:37] <tim23423424> unplugged monitor, plugged back in, now Settings doesn't see it at all
[14:41] <tim234234241> (this is me, joining on a different computer so I can try to reboot my Ubuntu machine to improve things)
[14:44] <tim234234241> wow, ok, resetting the monitor's internal settings, removing ~/.config/monitors.xml, and rebooting, seems to have done the trick
[14:44] <tim234234241> not sure what was going on
[14:47] <oerheks> obviously, such bugs are hard to repeat :-(
[14:47] <oerheks> good you found it.
[14:50] <tim234234241> thanks for your help!
[14:52] <lotuspsychje> cookie oerheks 
[14:53] <lotuspsychje> anyone else has a rather long loading time on the games section of the snap store?
[15:21] <lotuspsychje> the game list is long i know, but on i5 with ssd, 6sec wait
[15:58] <dg14> hi all.
[15:58] <oerheks> :-)
[15:58] <dg14> python-minimal is a transaction package?
[15:59] <dg14> because, i had to backport nodejs v12 (from nodesource)
[16:01] <dg14> it's possible to focal to set a screensaver? because of my monitor remains always powered on. 
[16:14] <ducasse> dg14: see 'man xset' if you're using x11
[16:17] <dg14> ok thanks. 
[16:17] <dg14> settings are permanent? 
[16:18] <dg14> even if i use dm-tool lock ?
[16:23] <anon_linux> Olá a todos
[16:23] <oerheks> download url in the topic, anon_linux 
[16:23] <anon_linux> Where do I download Ubuntu 20.04
[16:24] <dg14> do-release-upgrade -d
[16:24] <anon_linux> thanks bro
[16:27] <dg14> gsd-wacom[3029] trap int3 ip:7fd4ac2520d5 sp:7ffd7b666460 error:0 in libglib-2.0.so.0.6400.1 ? 
[17:03] <longstride> hey everyone, I ran apt-get dist-upgrade today.  I restarted my computer, got the login screen, entered my password and...nothing.  Monitors went into sleep mode and the only thing I could do was manually shut off my computer and boot into my 19.10 install.  Any way I can revert back to my working install of 20.04?
[17:04] <lotuspsychje> longstride: in this stage its not wise to upgrade to a devel version yet
[17:05] <longstride> lotuspsychje: I am in full agreement lol
[17:05] <lotuspsychje> longstride: can you still enter recoverymode?
[17:06] <longstride> Yes I tried that once already, although I have no idea what to do there really
[17:06] <longstride> I got a menu with a few options, tried a few, then rebooted normally, still no luch
[17:06] <longstride> luck
[17:06] <lotuspsychje> longstride: lets try
[17:07] <ngaio> longstride, you don't need to manually switch it off. See this: https://en.wikipedia.org/wiki/Magic_SysRq_key#Uses
[17:08] <ngaio> see the discussion about "magic SysRq", and also getting a text console using Ctrl-Alt-F2 or similar
[17:08] <ngaio> both of these can be really very useful
[17:10] <longstride> ngaio: thanks!  I will make a note of this
[17:10] <ngaio> this is probably more use friendly discussion of the magic sysrq keys: https://www.howtogeek.com/119127/use-the-magic-sysrq-key-on-linux-to-fix-frozen-x-servers-cleanly-reboot-and-run-other-low-level-commands/
[17:10] <ngaio> the bottom line is don't poweroff unless  you really really have to, and most of the time, you do not have to
[17:10] <ngaio> (I'm speaking from recent experience with failing graphics hardware)
[17:14] <longstride> so I've printed that page, I'll give it a try if I run into that situation again
[17:14] <longstride> lotuspsychje, is there anything specific I can do in recovery mode?
[17:34] <longstride> sorry if I missed anything.  I restarted my computer, booted into 20.04, tried to log in, same black screen.  Except this time I was able to get back to the login screen using ctrl + alt + f1
[17:36] <longstride> Is there any way to try booting with safe graphics, like I had to when I first installed 20.04?
[17:54] <ngaio> longstride, are you using the nvidia driver?
[17:54] <ngaio> the proprietary one that is
[18:46] <longstride> ngaio: yes I am
[18:47] <ngaio> boot up, ctrl-alt-f1
[18:47] <ngaio> sudo nano /etc/default/grub
[18:47] <ngaio> Change the line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="nomodset"
[18:48] <ngaio> ctrl-o to save the file, ctrl-x to exit
[18:48] <ngaio> sudo update-grub
[18:48] <ngaio> sudo reboot
[18:48] <ngaio> longstride, then hopefully it will work
[18:49] <ngaio> note that is nomodset, NOT nomodeset
[18:49] <longstride> ctrl+alt+f1 at the login screen?
[18:49] <ngaio> yes
[18:50] <longstride> Thanks!  I will try this right away
[18:58] <phpdave11> new update to ubuntu 20.04 installed php7.4 but i need php7.3 installed for compatibility with my application.   i can manually install php7.3 packages but as soon as i install "composer", it automatically installs php7.4.  anyone know how to prevent php 7.4 from being installed on 20.04?
[19:01] <lordcirth_> phpdave11, does installing php7.4 uninstall 7.3? It shouldn't
[19:01] <longstride> ngaio: no luck.  But I noticed an error message during boot, flashed by realy quick.  It said "initramfs unpacking failed: decoding failed".  Any significance?
[19:03] <phpdave11> no, it keeps both versions installed
[19:05] <lordcirth_> phpdave11, then you should be able to choose to run your app in 7.3, I think.
[19:07] <phpdave11> i see.  so i may just have to symlink /usr/bin/php7.3 to /usr/bin/php
[19:09] <phpdave11> another thing i noticed... python-pip no longer installs correctly.  anyone else notice this?  here's the output from apt-get install:  https://gist.github.com/phpdave11/d583c1f57ef4e7e7b74488aec14cbdc9
[19:31] <lordcirth_> phpdave11, /usr/bin/php is already using update-alternatives, so use that instead of symlinking manually
[19:58] <phpdave11> thanks ill look into update-alternatives
=== nt0_ is now known as nt0
[21:41] <pnwise> Does anyone know what would be the default python version for the new server
[21:41] <pnwise> Seem like 3.8?
[21:41] <pnwise> new = 20.04
[21:45] <valorie> !info python
[21:45] <ubottu> Package python does not exist in focal
[21:45] <valorie> ha!
[21:46] <pnwise> !info python3
[21:46] <ubottu> python3 (source: python3-defaults): interactive high-level object-oriented language (default python3 version). In component main, is important. Version 3.8.2-0ubuntu1 (focal), package size 46 kB, installed size 188 kB
[21:46] <pnwise> Thanks!
[21:54] <tomreyn> pnwise: risking that you may already know: the "rmadison" utility can help you find these things out, too, or https://packages.ubuntu.com
[21:56] <pnwise> thanks!@
[21:56] <pnwise> https://packages.ubuntu.com/focal/
[21:56] <pnwise> gives internal server error tho
[21:56] <pnwise> have not heard of rmadison too
[21:58] <tomreyn> pnwise: when you run into internal errors, just reload the page. it's been that way for a year or so.
[21:58] <tomreyn> some bug in the server configuration
[22:03] <pnwise> this is embarrassing 
[22:05] <tomreyn> despite the official look, i am told this site is community maintained