[02:10] <lotuspsychje> anyone else had a gnome-shell crash during last updates on -desktop?
[06:08] <kr-428> Folks; anyone can point me how to revert gdm theme to "stock GNOME" in 20.04? The approaches learnt in previous versions don't seem to work anymore...
[07:27] <pickledegg> Hi there, is there a bug report for openvpn?
[08:01] <lotuspsychje> pickledegg: ask your specific issue into the channel, volunteers might know
[08:02] <lotuspsychje> pickledegg: see also #ubuntu-quality for known bugs
[09:41] <georgelappies> quick question friends, if no using 20.04 from install from daily image, do I need to do anything special when it hits live?
[09:41] <lotuspsychje> !final | georgelappies 
[09:43] <georgelappies> thanks
[11:54] <howarth> Anyone else having problems with this mornings package updates?
[11:54] <howarth> I found that the update of accountsservices caused all hell to break loose.
[11:55] <howarth> now I get crashes in gdm3 after logging in
[11:55] <howarth> A crash in /usr/lib/gdm3/gdm-session-worker
[12:15] <lotuspsychje> howarth: yeah i had a gnome-shell crash during updates
[12:16] <howarth> Weirdly , I seem to have stabilized my machine
[12:16] <lotuspsychje> after that, i rebooted fine into gnome
[12:16] <howarth> I first tried going to proposed-updates with 'apt-get update' and 
[12:17] <howarth> 'apt-get dist-upgrade
[12:17] <lotuspsychje> im staying off -proposed myself
[12:17] <howarth> using /etc/apt/preferences.d/99-downgrade-proposed 
[12:18] <howarth> I wasn't on proposed when all hell broke loose
[12:18] <howarth> only tried in to see if they missed a required associated dependency
[12:19] <howarth> As I said, weirdly coming back from proposed-updates to updates with the downgrade method seems to have eliminated the crashes (weirdly)
[12:20] <howarth> I use the method described here.... http://www.webupd8.org/2013/11/how-to-downgrade-proposed-repository.html
[12:20] <lotuspsychje> the users choice howarth 
[12:21] <lotuspsychje> but for testing cases, sure why not
[12:21] <howarth> I couldn't deal with the constant crashes from today's updates... fortunately that seemed to have purged out the problem
[12:22] <howarth> One nice benefit was that it left me on the newer 5.4.0-23 kernel
[12:22] <lotuspsychje> howarth: you know if there's a bug ID on that yet?
[12:23] <howarth> Haven't looked yet but I did click to send the bug reports back upstream
[12:23] <lotuspsychje> same auto report this morning here
[12:26] <howarth> The accountsservices launchpad doesn't show anything
[12:27] <lotuspsychje> howarth: yeah there's a difference between filing bugs yourself, and auto reports to canonical
[12:27] <howarth> I'm assuming that one is key... I known trying to manually reinstall it would knock the display back to a screen
[12:27] <lotuspsychje> howarth: those crashes do get stored in a hidden launchpad url, they can see
[12:28] <howarth> Well so far so good here...
[12:28] <lotuspsychje> cause crash reports could hold sensitive info, the public doesnt need to see
[12:29] <howarth> I am back on the 0.6.55-0ubuntu11 from updates but without the previous crashes after going to proposed-upgrades and coming back again
[12:29] <lotuspsychje> howarth: can you check /var/crash to see if you got gnome-shell crashes too?
[12:29] <lotuspsychje> !info gdm3
[12:29] <howarth> I saw that as well but not now since I went to proposed-updates and then downgraded back to updates
[12:29] <lotuspsychje> !info gdm-session-worker
[12:30] <lotuspsychje> whats that version you talk about?
[12:30] <howarth> That version is the accountsservices which was in todays updates
[12:30] <lotuspsychje> oh
[12:31] <howarth> The update set that I applied this morning when all hell broke loose was 
[12:33] <howarth> accountsservice:amd64 libaccountsservice0:amd64 command-not-found:all python3-commandnotfound:all gir1.2-accountsservice-1.0:amd64  libharfbuzz0b:amd64  libharfbuzz-icu0:amd64  libltdl7:amd64  nodejs:amd64 libnode64:amd64 nodejs-doc:all pinentry-curses:amd64 pinentry-gnome3:amd64
[12:34] <howarth> IMHO, accountservices seems the likely culprit
[12:34] <howarth> FYI, when proposed updates didn't fix the new breakage, I tried manually downgrading to  0.6.55-0ubuntu10 but that didn't work
[12:35] <howarth> At that point I used the /etc/apt/preferences.d/99-downgrade-proposed trick to downgrade back from proposed-updates to updates and everything suddenly worked correctly again
[12:35] <lotuspsychje> seems like it has happened before howarth 
[12:36] <lotuspsychje> bug #1832865
[12:37] <lotuspsychje> so seems like its a dejavu bug we getting
[12:40] <lotuspsychje> aha, bug #1843982
[12:40] <lotuspsychje> added fossa tag, and rls incoming
[12:43] <howarth> Try the dist-upgrade to proposed-updates followed by downgrade back to updates voodoo and see if it works for you
[12:43] <lotuspsychje> no, ill await this one mate :p
[12:44] <lotuspsychje> got some other bugs that i wait updates from aswell
[12:44] <howarth> I couldn't deal with all those crashes
[12:59] <takov751> greetings i have a quick question. I am missing the mediaplayer indicator in gnome 3.36. Do i need to install a package manually by any chance?
[13:05] <lotuspsychje> takov751: i assume you talk about rhythmbox ?
[13:09] <takov751> No. There is a mediaplayer indicator which shows and controls media apps ,however i just saw its only support up to 3.32
[13:10] <takov751> At the monent
[13:10] <takov751> 3.36 is still not supported
[13:56] <lotuspsychje> welcome felco 
[13:57] <felco> hello!
[13:57] <lotuspsychje> 26 april felco 
[13:57] <felco> can I dist-upgrade yet =D
[13:57] <lotuspsychje> the users choice felco 
[13:57] <lotuspsychje> wich release are you on now?
[13:58] <felco> is 20.04 avaliable?
[13:58] <felco> 19.10
[13:58] <lotuspsychje> best await final
[15:41] <qwertuttyty> The xCHI doesn 't work VL805. AMD fm2+ IOMMU anable. Kernel 5.6.2 https://paste.ubuntu.com/p/T9HqX3X5tt/  https://paste.ubuntu.com/p/qnSVC6dZ8N/
[15:41] <qwertuttyty> xhci
[15:50] <qwertuttyty> What to do, use usb 3.1 or 4.0 or not VL805?
[15:52] <qwertuttyty> xHCI VIA VL805
[15:57] <qwertuttyty> Windows -Ok
[16:01] <genii> qwertuttyty: Does not seem to be xHCI compliant. http://billauer.co.il/blog/2019/07/via-vl805-superspeed-pcie-linux/
[16:29] <luna_> i just figured out i was stupid yesterday
[17:50] <hggdh> qwertuttyty: and this is not a kernel provided by Ubuntu. You should go upstream to kernel.org
[17:59] <qwertuttyty> I am not sure that my PCI PCI VIA VL805 can be flashed most likely not impossible the Board manufacturer does not have any information about flashing this Board. Only if viewed on the VIA website. The kernel developers have stopped testing xchi VIA VL805 so it still doesn't work? In other words, it is impossible to fix it by adding a patch to the kernel for xchi VIA VL805, or there is no one or they do not want to,  there is no in
[17:59] <qwertuttyty> t in xchi VIA VL805 to make it work? Windows no problem with VL805 have driver. Not need update xchi VIA VL805 flash. this is a separate usb board. What to do, use usb 3.1 or 4.0 or not VL805?
[18:03] <qwertuttyty> https://paste.ubuntu.com/p/4KpptR76zb/
[18:13] <qwertuttyty> I am uncomfortable, I do not know English. They know that the VL805 is not working. I correctly understood that it was necessary that there were a lot of complaints from the owners of VL805 so that they fix it?
[18:20] <qwertuttyty> https://paste.ubuntu.com/p/sYQvHHmWNc/
[18:27] <qwertuttyty> Is there a list of manufacturers or chips  USB that kernel 5.6 will work with? I take it, no?
[18:35] <qwertuttyty> Buying for good luck or asking (reading) how the usb chip works for those who have already used this chip in linux while I see only such an options or use Windows for VL805.
[19:13] <qwertuttyty> http://billauer.co.il/blog/2019/07/via-vl805-superspeed-pcie-linux/ Orico but i have not orico. But it seems to be the same. One of the Chinese companies which are many.
[19:21] <qwertuttyty> So 99% of the boards and chips are Chinese-made and Chinese companies.
[19:26] <qwertuttyty> usb the boards USA or GB or RU or Idia or Germany or EU?
[19:27] <qwertuttyty> no, only Chines. Raspberry pi only  GB
[19:28] <qwertuttyty> apple for me not interesting 
[19:29] <qwertuttyty> usb the boards companies USA or GB or RU or Idia or Germany or EU? no, only Chinese. Raspberry pi only  GB
[19:30] <oerheks> interesting china rant.. did you check your sources?
[19:34] <qwertuttyty> JP? for PC?
[19:43] <qwertuttyty> I did not understand the question. And I'm not a Chinese. It is better not to philosophize and write only on business. Philosophical questions are poorly translated. https://translate...
[19:56] <gst568923> I have tested xubuntu 20.04 beta but I have this bug: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1865130/comments/62
[19:56] <gst568923> this is my log: https://pastebin.com/H6suBBm3
[19:58] <oerheks> ATI Mobility Radeon HD 3450 .. that is an old one, radeon works guaranteed with ati 5xxx and up.
[20:01] <gst568923> oerheks I have been using that graphics card for more than 10 years with the open source radeon driver and I have not had any major problems, except that I am reporting
[20:43] <valorie> gst568923: did you link that on the qatracker?
[20:44] <valorie> reporting bugs here does not get them to the developers who need to see them
[20:45] <gst568923> valorie I have linked this https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1865130/comments/62
[20:45] <valorie> excellent
[20:46] <valorie> thanks for your contribution
[20:48] <gst568923> valorie I'm trying `vbetool dpms on` to re-start the LCD black screen for the LVDS interface, but not works :(
[20:48] <valorie> :(
[22:28] <magic_ninja_work> 13 days. You all rocking and rolling?
[23:11] <Bashing-om> o/ - once more - into the fray :P