[00:47] <lotuspsychje> good morning
[02:01] <Bashing-om> !info ubiquity
[03:01] <CarlFK> what kernel version should I have after an apt upgrade?  
[03:03] <lotuspsychje> CarlFK: 5.4.0-26-generic
[03:04] <CarlFK> lotuspsychje: thanks.  that;s what I thought. 
[03:06] <CarlFK> I did this:  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871182/comments/11  
[03:06] <CarlFK> install -25
[03:07] <Bashing-om> !info linux-image-generic
[03:07] <CarlFK> I'm not completely opposed to re-installing but is there some quick thing I can try to get it ?
[03:08] <Bashing-om> CarlFK: ^^ " sudo apt update ; sudo apt upgrade ' ?
[03:08] <CarlFK> re-installing focal  that is.  this box/install is just to test the wifi 
[03:09] <CarlFK> Bashing-om: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[03:10] <CarlFK> apt-cache policy linux-image-generic ... Installed: (none)  Candidate: 5.4.0.26.32
[03:10] <Bashing-om> CarlFK: pastebin ' dpkg -l | grep linux- '. See if that new kernel is available in your install.
[03:12] <CarlFK> Bashing-om: http://paste.ubuntu.com/p/hdx9Dknfvc/
[03:13] <CarlFK> im removing the -25
[03:14] <Bashing-om> CarlFK: Huh ?? only partly installed "linux-headers-5.4.0-26" / I wonder why, what is not going on. disk space ' df -h ; df -i ' ?
[03:14] <Bashing-om> CarlFK: -25 might be the kernel that you are booting now !!
[03:16] <CarlFK> Bashing-om: it is.  she'll be all right mate :p 
[03:16] <Bashing-om> CarlFK: Hope you have a good plan :P
[03:17] <CarlFK> it's like a video game.  If I die, I'll have to start over 
[03:18] <Bashing-om> CarlFK: We learn most when we break it and pick up the pieces.
[03:18] <CarlFK> wth... apt upgrade... The following packages will be upgraded:   linux-image-unsigned-5.4.0-25-generic
[03:21] <Bashing-om> CarlFK: Not a good sign - our kernels are normally signed - yukkie.
[03:22] <CarlFK> Bashing-om:  did you see the bug report comment about installing -25?
[03:22] <Bashing-om> CarlFK: No - did not read it :(
[03:23] <CarlFK> there isn't much to it, other than explain why I installed linux-image-unsigned-5.4.0-25-generic_5.4.0-25.29~lp1871182_amd64.deb
[03:26] <Bashing-om> CarlFK: Sorry - I must depart -:(
[03:27] <CarlFK> no prob - 
[03:27] <CarlFK> see ya
[08:18] <danjjl> Hello, since upgrading to Ubuntu 20.04 (fresh install), the WiFi on my laptop is extremely slow. This was not the case on Ubuntu 18.04. I am having troubles finding the cause of the problem. A network timing analysis in Firefox shows that in a random GET 5s are spent blocked, 5s resolving DNS and 5s waiting.
[08:19] <danjjl> My chipset is a Intel Corporation Dual Band Wireless-AC 7265 using the iwlwifi driver
[08:20] <danjjl> (btw I am not very familiar with IRC or this channel -- do tell me if it is the wrong place to ask for help to debug this WiFi issue)
[09:25] <lotuspsychje> danjjl: system up to date?
[09:26] <danjjl> Yes
[09:26] <lotuspsychje> danjjl: wich kernel is your wifi going slow on?
[09:27] <danjjl> lotuspsychje 5.4.0-26-generic
[09:27] <lotuspsychje> danjjl: could you try booting into -25 please see if you can reproduce that?
[09:52] <danjjl> lotuspsychje : I tried booting in -24 and -25 and encounter the same issue. (I also tried disabling the 11n_disable=1 option  and checked dmesg output. For the moment I cannot find anything related to the issue)
[09:55] <lotuspsychje> ok tnx for testing that danjjl 
[09:56] <lotuspsychje> danjjl: can you pastebin your dmesg booting -26 please?
[10:06] <danjjl> lotuspsychje: https://paste.ubuntu.com/p/9ccMnSDcc7/
[10:06] <lotuspsychje> tnx lets see
[10:09] <lotuspsychje> danjjl: iwlwifi 0000:02:00.0: Direct firmware load for iwl-dbg-cfg.ini failed with error -2
[10:15] <danjjl> lotuspsychje: Yep I see that one, searching for hits the error on Google. I assumed it was non critical given wifi still works (albeit super slow) and given the -dbg- (?debug) qualifier in the filename
[10:16] <lotuspsychje> danjjl: think you better file a big for this mate
[10:16] <lotuspsychje> danjjl: you have a launchpad account?
[10:16] <danjjl> lotuspsychje yes
[10:17] <danjjl> lotuspsychje: OK submitting bug
[10:17] <lotuspsychje> danjjl: ubuntu-bug linux from terminal, add a title + description with the kernels you tested on, attach your dmesg if you like
[10:18] <danjjl> lotuspsychje nice tool! didn't know about it :)
[10:18] <lotuspsychje> thank you danjjl this way you help yourself and the community
[10:22] <danjjl> lotuspsychje: thanks for the guidance collecting the relevant info
[10:22] <lotuspsychje> thank you for reporting this danjjl 
[10:23] <lotuspsychje> danjjl: maybe also describe it was working on bionic/kernel-version
[10:24] <lotuspsychje> brb
[10:27] <nikolam> Will Ubuntu ever support booting from ZFS partition? 
[10:27] <nikolam> In contrast to ultimately requesting to destroy all partitions on the hard drive?
[10:28] <nikolam> I would like to keep dual-boot in the future.
[10:34] <nikolam> If I install on another drive with installer on ZFS, shall I be able to move all datasets to a pool built on top of disk partition.
[10:35] <nikolam> And will boot loader be able to boot from the ZFS on the partition and not on the whole drive?
[10:36] <nikolam> With even "whole drive" ZFS pool install, can I install on EXISTING pool instead?
[11:25] <excited_buddha> I have an issue with gnome-shell-theme and combination of the user theme extension. I am new to IRC 1st message, I don't know how to ask questions, if anyone can advice please reply..
[11:25] <lotuspsychje> excited_buddha: are you on 20.04?
[11:25] <excited_buddha> yes
[11:25] <coitusinteruptus> not released yet
[11:25] <excited_buddha> daily build
[11:26] <coitusinteruptus> hold your horses
[11:26] <lotuspsychje> excited_buddha: cool, then this is the right place for support, try to elaborate all your details, whats happening exactly
[11:28] <excited_buddha> thanks. So everything was installed fine. I installed the user theme extensions, then tried some shell themes. Did not liked any, now I am only using Yaru, uninstalled the extension, as I don't want it. but now when I switch the themes from appearence menu from settings to dark, the application theme switches to dark, but the shell theme is light.
[11:28] <excited_buddha> and stuck on light.
[11:28] <coitusinteruptus> we need dark
[11:30] <excited_buddha> So, I think that my link of appreance setting to shell theme (yaru dark) is broken somehow. The yaru dark (shell theme is still there), if I reinstall user theme extension I can manually select the shell theme(dark) but if I uninstall the extension it goes to light shell theme again.
[11:31] <lotuspsychje> excited_buddha: do you have gnome-tweaks installed?
[11:31] <excited_buddha> yes
[11:32] <lotuspsychje> excited_buddha: at the top you have a 3 lines menu, you can set gnome back to defaults, you could try that? or disable all shell extensions?
[11:32] <lotuspsychje> be carefull, this could reset all back to defaults
[11:33] <lotuspsychje> so backup your things/cinfigs first
[11:33] <lotuspsychje> configs
[11:34] <excited_buddha> I did not do any other customizations, I was trying the themes 
[11:34] <excited_buddha> right after I installed.
[11:35] <lotuspsychje> ok go ahead and try that then
[11:35] <excited_buddha> did it, it still is not working.
[11:35] <lotuspsychje> hmm ok
[11:35] <excited_buddha> any way to reset any other files that might have been touched by shell extension
[11:37] <excited_buddha> https://imgur.com/a/7nFvS2k this is the issue.
[11:38] <coitusinteruptus> can i run automobilista 2 on linux ?
[11:38] <lotuspsychje> excited_buddha: did you logout/back in after resetting?
[11:39] <excited_buddha> no
[11:39] <excited_buddha> I will
[11:40] <excited_buddha> now.
[11:41] <excited_buddha> still same issue.
[11:41] <lotuspsychje> excited_buddha: if you are talking about the notification area, thats normal to be white
[11:42] <excited_buddha> is that not supposed to be dark?
[11:42] <lotuspsychje> i ahve yaru dark, its also white there
[11:42] <lotuspsychje> nop
[11:42] <excited_buddha> if you install the user theme extension, then select yaru dark in shell theme
[11:42] <excited_buddha> then you  get dark notification
[11:43] <excited_buddha> yaru dark is pre installed shell theme.
[11:43] <lotuspsychje> excited_buddha: right upper corner is white too
[11:44] <excited_buddha> have you ever installed the user theme extension on your current machine
[11:44] <lotuspsychje> no, im not an extension fan really
[11:44] <excited_buddha> ok
[11:44] <lotuspsychje> i bet thats just a theme manager?
[11:44] <excited_buddha> so i guess I did not pay attention to factory install.
[11:45] <excited_buddha> the way how it was.
[11:45] <excited_buddha> I have one question lotuspsychje, reseting from gnome-tweaks, what does it do? reset to ubuntu defaults or gnome defaults?
[11:46] <lotuspsychje> gnome defaults
[11:46] <excited_buddha> so i lost all customizations that ubuntu made at fresh install after reseting?
[11:47] <lotuspsychje> customizations on gnome yes
[11:47] <lotuspsychje> not like installed packages with apt
[11:47] <excited_buddha> what would they be, for eg.
[11:47] <excited_buddha> would that impact anything? performance? animations?etc
[11:48] <lotuspsychje> excited_buddha: any tweak you can find in gnome settings or dconf editor
[11:49] <excited_buddha> can I find ubuntu edits to these settings online/ or have to do fresh install?
[11:49] <excited_buddha> btw how long till official release?
[11:49] <lotuspsychje> 23 april
[11:49] <excited_buddha> hours
[11:49] <lotuspsychje> no
[11:50] <lotuspsychje> its out when its out
[11:50] <excited_buddha> are you on 20.04 now?
[11:50] <excited_buddha> willl you be doing fresh install after release or just update:
[11:50] <excited_buddha> ?
[11:51] <excited_buddha> I MEAN which is better>
[11:51] <excited_buddha> ?
[11:51] <coconut> Hi. Does the firmware updater tool inside 20.04 still work when i replace the official ssd which comes with a laptop with a different brand ssd ? Will it still update the firmware of the replaced ssd ?
[13:14] <deadrom> hi
[13:15] <deadrom> will 20.04 release as planned tomorrow? if so: will it be eligible for an LTS upgrade from 18.04 right away?
[13:17] <oerheks> tomorrow yes, upgrade path will be available with 20.04.1 .. after 3 months or so
[13:19] <coitusinteruptus> looking forward t o20.04   im a mouse user.. and ubuntu seems my best choice.. gets better every release.. generally
[13:33] <deadrom> the LTS .1 upgrace policy sounds a bit as if people should rather be forced into fresh installs
[13:34] <coitusinteruptus> looking forward to 20.04  ubuntu overall best distro for pc illetaretes like me
[13:35] <lotuspsychje> deadrom: if you want stable, aka a lot more bugs solved then first release, await .1
[13:35] <lotuspsychje> deadrom: it all depends on your case/needs
[13:41] <coitusinteruptus> lotuspsychje  unban be from main room.. and make your name easier to spell
[13:44] <coconut> coitusinteruptus: why should she just do that ?
[13:45] <coitusinteruptus> ive been banned long enough
[13:45] <coitusinteruptus> they attack me i was just defending myself
[13:48] <coconut> coitusinteruptus: if you're banned then you have done something wrong... probably best to go to #freenode for help on unbanning.
[13:49] <coitusinteruptus> strange  how the linux fanboys arent warned or banned.. just me
[13:49] <coitusinteruptus> we need to get a grip
[13:49] <coitusinteruptus> work together
[13:49] <coitusinteruptus> we arent the common enemy
[13:49] <coitusinteruptus> china and islam is
[13:56] <oerheks> how is your rant related to ubuntu focal support?
[13:56] <oerheks> you risk a ban here too 
[13:57] <coitusinteruptus> just statign drity facts.. dirty but a fact is a fact.  man up
[13:57] <oerheks> wrong channel dud
[13:58] <coitusinteruptus> maybe.. btu at least we know its fact
[13:58] <coitusinteruptus> 20.04?  still cant drag and drop files onto desktop?  why not
[13:59] <oerheks> install gnome-tweak-tool, that gives an option
[13:59] <coitusinteruptus> hmm
[13:59] <oerheks> files on a desktop is so 2019
[14:00] <coitusinteruptus> no, its just functional ffs
[14:00] <coitusinteruptus> why not even allow it?
[14:02] <Eickmeyer> !ops
[14:02] <Eickmeyer> We need to stay on-topic in here. If you got banned, coitusinteruptus, it's for good reason.
[14:03] <popey> it's because the extension we're using doesn't have that feature
[14:08] <coitusinteruptus> hmm
[14:13] <hggdh> well
[14:13] <hggdh> you know better, mystic
[14:15] <lotuspsychje> coconut: you want to update the firmware of your ssd through ubuntu?
[14:16] <coconut> lotuspsychje: yes, although i still have to buy the laptop
[14:16] <lotuspsychje> coconut: wich brand of ssd is that?
[14:16] <coconut> let me check...
[14:19] <flying_sausages> hey guys, did anyone have success on a Linux raid system when trying to upgrade from 18.04 to 20.04? I have had problems with the grub every time
[14:19] <flying_sausages> I've got Raid1 /boot and Raid5 root
[14:19] <flying_sausages> trying to install it on all 4 disks succeeds, update-grub2 runs fine, but the system won't come back online (it's remote).
[14:23] <coconut> lotuspsychje: 1 TB SSD-station, M.2 2280, NVMe, Opal(from vendor)    OR    one of the latest samsung EVO ssd's(might put that in the laptop myself)
[14:24] <lotuspsychje> coconut: https://www.samsung.com/semiconductor/global.semi.static/Firmware_Update_Utility_UserManual.pdf
[14:26] <coconut> thnx lotusps
[14:29] <lotuspsychje> coconut: that laptop brand will be lenovo?
[14:29] <coconut> yes, as it looks now the "x1 extreme gen2"
[14:30] <coconut> or another if you recommend one...
[14:30] <lotuspsychje> coconut: some lenovo types might offer firmware updates via software centre/fwupdate but not sure if they include the ssd firmware also
[14:31] <coconut> well, we'll see
[14:31] <lotuspsychje> !hardware | coconut take a look here also
[14:32] <coconut> looooooking
[14:33] <lotuspsychje> coconut: hardware not listen, mostly also work, but sometimes some chipsets might need bypass/workarounds/bug solve
[14:37] <coconut> well... i only need to be honest with that then and supply some info
[14:39] <coconut> just hope it would not be to hard doing so
[14:39] <coconut> too
[14:40] <lotuspsychje> coconut: another methos would be, updating ssd firmware from the Os that comes on your laptop first, then install ubuntu after
[14:40] <lotuspsychje> *method
[14:41] <coconut> yeah i might do that, but still want to see how far it will update from ubuntu first
[14:43] <lotuspsychje> coconut: the users choice
[14:43] <coconut> huhuh
[14:47] <flying_sausages> fwupd no do?
[15:29] <dabbill> What package adds the hybrid graphics to the dropdown menu where the sound and shutdown options are. I upgraded from 19.10 to 20.04. The graphics options are not there in 20.04. 
[15:30] <lotuspsychje> dabbill: can you check wich driver you on, nvidia-smi ?
[15:31] <dabbill> lotuspsychje: 440.64, just updated this morning
[15:32] <lotuspsychje> dabbill: try to switch to one version down, there might be a glitch happened
[15:32] <lotuspsychje> 435
[15:32] <dabbill> lotuspsychje: I have tried 435, and several versions of 440. 
[15:32] <lotuspsychje> oh?
[15:33] <lotuspsychje> dabbill: you have the ubuntu graphics ppa enabled?
[15:34] <dabbill> lotuspsychje: yes
[15:35] <lotuspsychje> dabbill: so you dont have nvidia-settings is that what happens?
[15:35] <flying_sausages> I just did an do-release-upgrade -d and the install didn't move the nic to netstat, is this a known bug?
[15:35] <flying_sausages> anywhere I can check this?
[15:36] <lotuspsychje> dabbill: apt policy nvidia-settings to see if its installed
[15:36] <flying_sausages> allegedly it happens in debian 9 -> 10 too
[15:36] <dabbill> lotuspsychje: I have nvidia-settings
[15:37] <lotuspsychje> dabbill: what happens exactly then?
[15:38] <dabbill> lotuspsychje: I do not have this menu options. https://twitter.com/killyourfm/status/1251139096338194432 
[15:39] <lotuspsychje> dabbill: on 20.04 the nvidia drivers are included now, i would try purge the graphics ppa, try the original 435 as a test
[15:40] <dabbill> lotuspsychje: tried that :) 
[15:40] <lotuspsychje> dabbill: hybrid card with optimus?
[15:40] <dabbill> lotuspsychje: Yes, laptop has intel / nvidia cards 
[15:40] <lotuspsychje> kk
[15:40] <lotuspsychje> system up to date also i presume?
[15:41] <dabbill> lotuspsychje: as of couple hours ago
[15:41] <lotuspsychje> right
[15:41] <dabbill> in nvidia-settings I can change the PRIME Profiles
[15:41] <lotuspsychje> pastebin your dmesg please, ill go eat first, check after ok
[15:41] <lotuspsychje> or if other volunteers can take a look
[15:41] <lestac> apt policy nvidia-settings
[15:41] <lestac> nvidia-settings:
[15:41] <lestac>   Instalados: (ninguno)
[15:41] <lestac>   Candidato:  390.77-0ubuntu0.18.04.1
[15:48] <dabbill> lotuspsychje: https://pastebin.com/xQqPZ1XQ
[16:11] <lotuspsychje> dabbill: never saw those before: SGI_video_sync[4981]: segfault at e6 ip 0000562057352f92 sp 00007f07da7fa6c0 error 6 in teams[56205486f000+4bf6000]
[16:11] <lotuspsychje> dabbill: and you got a lot of wifi disconnects at the end too
[16:16] <felco> YAY, are we ready to release tomorrow?
[16:18] <lotuspsychje> yes we are, all party hats in #ubuntu-release-party felco 
[16:18] <felco> YAY \o/
[16:21] <lotuspsychje> dabbill: can you confirm you are on kernel 5.4 -26 ?
[16:23] <lotuspsychje> dabbill: check bug #1871041 see if its you?
[16:37] <lotuspsychje> dabbill: another update bug #1867361
[17:03] <AlexMax> Hi folks, I'm having a strange problem.  Whenever I switch users, or sometimes also when I use xrandr to change my scaling, there is a "ghost mouse pointer" that just hovers there doing nothing.
[17:04] <AlexMax> I can move my real mouse around, but that other mouse just hangs sits there.
[17:04] <AlexMax> It does not show up in screenshots.
[17:04] <AlexMax> I'm using X sessions
[17:05] <AlexMax> I seem to recall having some strange issues with that in Fedora as well, but I think the problems eventually went away after a while - possibly because of a kernel update?
[17:43] <dabbill> lotuspsychje: yeah, been fighting with some APs that I think are dieing. 
[17:44] <dabbill> lotuspsychje: kernel 5.4.0-26
[17:44] <dabbill> lotuspsychje: laptop is hooked to a docking station, so not worried about wifi :) 
[17:46] <dabbill> lotuspsychje: nvidia driver is working fine.
[17:58] <vertion> Hi
[18:00] <vertion> I installed focal fossa and for some reason the right speaker doesn't work... it is not a hardware issue.  I have gone into Sound settings and tested Left and Right speakers.  No sound on Right.  I have updated and restarted and had the issue since upgrade
[18:32] <coconut> flying_sausages: i don't know, i have never used fwupd before
[18:40] <flying_sausages> vertion: laptop?
[19:01] <zvrk> vertion, run 'alsamixer' and check right speaker is muted 
[20:06] <howarth> Definitely looks like 'nomodeset' got broken in 20.04
[20:07] <howarth> The live usb boots fine into safe graphics for the current 19.10 image on a GTX680 but stays stuck on a black screen for the current daily cd image of 20.04
[20:08] <howarth> This matches the breakage that I am seeing for the recovery boot (which fails unless I remove nomodeset)
[20:08] <howarth> Weirdly, it doesn't seem to be a kernel bug because i installed the focal linux-generic kernels on 19.10 and it didn't break nomodeset
[20:10] <howarth> I am assuming this may be breakage in nouveau?
[20:10] <howarth> I guess the next step is to try to install the focal nouveau packages on 19.10 and see if that breaks nomodeset
[20:20] <howarth> It is interesting that Fedora 32 stayed at 1.0.15 for nouveau rather than going to 1.0.16
[20:50] <AlexMax> Any ideas for the floating mouse cursor on my machine?
[22:07] <excited_buddha> Just had a 5min+ screen hang at lockscreen. Now ubuntu want to report the error. How do I see myself what went wrong?
[22:08] <excited_buddha> I have the report problem dialog open, it says gnome shell crash.(ubuntu 20.04)
[22:33] <tomreyn> /var/crash may have more information
[22:33] <excited_buddha> I will check.
[22:34] <tomreyn> you can run apport-unpack against .crash files there
[22:39] <excited_buddha> raceback (most recent call last):  File "/usr/bin/apport-unpack", line 77, in <module>    pr.extract_keys(f, bin_keys, dir)  File "/usr/lib/python3/dist-packages/problem_report.py", line 269, in extract_keys    raise ValueError('%s has no binary content' %ValueError: ['separator'] has no binary contentis the output of apport, Now what to do / How
[22:39] <excited_buddha> to read the unpacked crash?
[22:39] <excited_buddha> HAHA the ubuntu apport just crashed too... oh such an irony.
[22:48] <excited_buddha> I know am looking for something with grep, I don't know what to look for in these files. I think its my nvidia driver that froze my gnome shell, when using grep "nvidia" *, it gives some error in journalErrors like : Nvidia_drm is in use, Nvidia is in use by Nvidia_modset, etc... If any one can point me to what I am looking for in crash, to locate
[22:48] <excited_buddha> the cause of crash, it would be very helpful.
[22:55] <tomreyn> excited_buddha: Did you upload it? if so, do you mind sharing your /var/lib/whoopsie/whoopsie-id ?
[22:56] <excited_buddha> I can upload, I dont know where to? or you do you mean I just click the send report button or manually upload some where? tomreyn
[22:56] <tomreyn> sending the report is what i mean
[22:56] <excited_buddha> I just pressed send, let me see the ID
[22:57] <excited_buddha> you mean the file? or the data in the whoopsie-id file?
[22:57] <tomreyn> it should add a new record to the top of the URL printed by this script:    echo https://errors.ubuntu.com/user/$(sudo cat /var/lib/whoopsie/whoopsie-id)
[22:58] <tomreyn> the data in the whoopsie-id file
[22:58] <tomreyn> but it may take half an hour or so for this new record to be added
[22:59] <excited_buddha> is my ID safe to share here?
[22:59] <excited_buddha> I have it..
[22:59] <tomreyn> anyone who has it can look at the list of errors you reported at the abive location
[22:59] <excited_buddha> 6eb94b54e1a4c59d03449cc89adb98754929d50a9417d819c79ddf7849b74eadd80e756cb6a035fbd03a550bb9e9650fa0675f502f3eb98a32a9dd4daf9ef056
[23:00] <tomreyn> so this makes it https://errors.ubuntu.com/user/6eb94b54e1a4c59d03449cc89adb98754929d50a9417d819c79ddf7849b74eadd80e756cb6a035fbd03a550bb9e9650fa0675f502f3eb98a32a9dd4daf9ef056
[23:01] <excited_buddha> yes i think it is uploaded
[23:01] <tomreyn> so 03:04 is "just now"?
[23:02] <excited_buddha> the first one is gnome shell, it happened twice, I left my laptop for a few minute, screen locked(as intended) did not open when I tried to press any keys, All I got was a black screen.
[23:02] <excited_buddha> Uploaded just now
[23:02] <excited_buddha> I did not press the send on that for all this time, coz I was worried I would lose the crash, I wanted to investigate.
[23:03] <excited_buddha> Can you help me with it? or lead me in the direction of someone or soemwhere I can get help with this, coz I want to lock my screen again.
[23:05] <tomreyn> i will probably not be able to help much, but maybe i can point you at an existing error after your upload was analyzed.
[23:05] <tomreyn> s/error/bug report/
[23:05] <excited_buddha> that would be very helpful
[23:05] <excited_buddha> s/error/bug report/ what is this?
[23:07] <tomreyn> ah sorry, that's my way of saying: "i really wanted to write this: maybe i can point you at an existing bug report after your upload was analyzed."
[23:08] <tomreyn> (i.e. "please subsitute 'error' by 'bug report' in what i just said because i typed it incorrectly")
[23:09] <excited_buddha> Ah okay
[23:09] <tomreyn> i see the nvidia error messages you discussed earlier
[23:09] <excited_buddha> now I get it, thanks this, learned a new way of saying things.
[23:10] <tomreyn> ... but it's not clear (to me) whether they're symptomatic or even directly related.
[23:10] <excited_buddha> but can't say what caused the shell to not wake up (display properly) after I woke screen from lock.( maybe its X11 bugging)
[23:11] <excited_buddha> will ubuntu team take a look at it ever?
[23:11] <tomreyn> you're using X11 though, right, not wayland?
[23:11] <excited_buddha> X11.
[23:11] <excited_buddha> 20.04 has x11 i think only
[23:12] <excited_buddha> s/'i think'/only ; s/only/'i think'
[23:12] <tomreyn> these crash reports serve as a kind of stack of data which analysis is run over, developers use it to get a better idea of how often users run into the same kinds of problems, so they'll know what needs to be fixed most urgently.
[23:13] <excited_buddha> ofcourse
[23:13] <tomreyn> they may and will occasionally also inspect those reports individually while working on fixing one of these crashes
[23:13] <excited_buddha> yes I understand
[23:13] <tomreyn> there's no guarantee that someone will inspect your individual submission, though
[23:14] <tomreyn> did you install nvidia drivers using ubuntu-drivers / the ubuntu settings GUI?
[23:14] <tomreyn> GUI=graphical user interface, so the graphical "settings" application
[23:14] <excited_buddha> Yes, the latest 440, but now I am thinking to revert to 390. or maybe the xorg one. coz I dont game.
[23:15] <excited_buddha> thanks for explaining, but I am aware of GUI.
[23:16] <excited_buddha> I will make a new crash report, if it crashes again with the 390, or xorg.
[23:16] <excited_buddha> Thanks for your time tomreyn
[23:20] <tomreyn> i'm not really into nvidia very much. i know there's some listings on nvidia.com suggesting which driver should be used for which card. but i found them to be unreliable.
[23:20] <tomreyn> and sometimes contradicting
[23:20] <tomreyn> excited_buddha: you'Re welcome. i didn't get to look at your latest upload / report, yet, though
[23:20] <tomreyn> it's probably still waiting (in queue) to being (automatically) analyzed.
[23:21] <tomreyn> when it's done it'll be listed on top of your  errors.ubuntu.com link from above
[23:21] <excited_buddha> oh okay 
[23:22] <howarth> FYI, users with nvidia cards might want to check that the safe graphics boot from the live usb works. I am finding on my GTX680 that it hangs on the nomodeset that uses/
[23:23] <howarth> I am trying to pin down the origin as it doesn't exist in 19.10
[23:23] <howarth> It also causes the recovery boot to hang.
[23:24] <howarth> I know that the kernel isn't the cause since I can install focals kernel on 19.10 and nomodeset still works
[23:24] <tomreyn> did you try     nomodeset nouveau.modeset=1   ?
[23:25] <howarth> not yet, my next test is to try downgrading plymouth in 20.04 to the 19.10 version
[23:25] <howarth> that went from libplymouth4 to libplymouth5 for casper dependencies
[23:26] <howarth> I'm more interesting in finding the culprit for a sensible bug report than hacking a workaround
[23:27] <excited_buddha> howarth It worked for me in safe graphics, as I ran with it the first time I tried to install 20.04
[23:27] <howarth> It is really my only gripe with 20.04
[23:27] <howarth> what card?
[23:29] <tomreyn> lspci -knn | grep -A3 VGA | nc termbin.com 9999 
[23:29] <excited_buddha> MX 150 (laptotp)
[23:30] <tomreyn> maybe you exceeded the attention span? ;-)
[23:31] <Bashing-om> howarth: If it will help - I have GeForce GT 710. 20.04 currently on nouvea - if it will help I can see what results in installing the 440 version driver ( throw away install).
[23:31] <tomreyn> howarth's gone
[23:31] <Bashing-om> tomreyn: thanks - so much for my thoughts :(
[23:32] <valorie> bug reports discovered during test which are linked on the ISO tracker will be looked at
[23:33] <valorie> although the earlier they are reported there, the more likely to be fixed
[23:33] <excited_buddha> Hey Bashing-om Dont worry, it can help me
[23:34] <excited_buddha> If you could be so kind to do the install? and report after restarting(if needed, unlikely), opening a few apps, Locking screen, letting screen go dark/black/blank/oFF, and then try to login again.
[23:34] <excited_buddha> Bashing-om could you ?
[23:35] <Bashing-om> excited_buddha: Well I can - is on another drive - ya got time to await here for my results ?
[23:35] <excited_buddha> I do.
[23:35] <excited_buddha> ETA?
[23:36] <excited_buddha> 20 min~
[23:36] <Bashing-om> excited_buddha: Ho-kay be a whilke to back out, reboot into 20.04 and run the install. 
[23:36] <Bashing-om> while*
[23:36] <excited_buddha> i'll be here.
[23:38] <excited_buddha> valorie how can i link my crash to iso tracker? do i have to go through the iso testing instructions?
[23:39] <valorie> find the one that most closely matches how you installed
[23:39] <valorie> which testcase
[23:39] <valorie> and when you report your result there is a place to link your BR
[23:39] <valorie> just the number is needed
[23:40] <valorie> so first you find the flavor then the ISO you used, then the testcase
[23:40] <valorie> bit of drilling down
[23:40] <excited_buddha> which number? my whoopsie ID?
[23:40] <excited_buddha> been there i can do this much, then?
[23:43] <excited_buddha> i upoaded the crash for now, to make BR, do I do it in launchpad? or it done auto?
[23:43] <excited_buddha> never created a BR
[23:46] <valorie> aha!
[23:47] <valorie> well it's pretty easy -- from inside the install you are reporting about, if possible, from a term: ubuntu-bug packagename
[23:47] <valorie> if you don't know the packagename ask and we'll figure it out
[23:47] <valorie> install or live-session, I should say
[23:49] <excited_buddha> apport collecting info now
[23:51] <excited_buddha> i think this created the .chash file in /var/crash right? i already uploaded that. I ask again, what number you reffer to up, when you said "just the number is needed?
[23:52] <valorie> !bug
[23:53] <valorie> lemme see if I can find a sample BR
[23:54] <valorie> https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1872902 for instance
[23:55] <valorie> you would put in 1872902
[23:55] <valorie> once you finish the bug report in launchpad the URL will change and you can see the number in your browser