[00:32] <xclaesse[m]> Hi, I'm testing Ubuntu 22.04, one issue I have is my wired networkd device does not appear. Wifi works fine. Is that a known issue? Any workaround possible?
[00:38] <xclaesse[m]> sarnold: When I plug a usb to ethernet device, I see that in journald: https://pastebin.com/Ltt6iVp4
[00:38] <xclaesse[m]> I think it's apparmor that prevents NetworkManager to get the new device, or something?
[00:39] <xclaesse[m]> I also see the message "kernel: r8152 3-4.1:1.0 enx5c857e356334: renamed from eth0" but it's not shown in "ifconfig"
=== mort7 is now known as mort
[09:01] <pmjdebruijn> is there anything special about ubuntu-minimal server installs? as installing man/man-db doesn't result in a working man setup
[09:03] <pmjdebruijn> and unminimize depends on snapd again
=== rdr_ is now known as rdr
[09:21] <jhy> Hello! I installed 22.04 as a test and found interesting bug that chrome and electron lose keyboard layout after unfocus somehow and default to I guess english one. Anyone have idea what might be causing this?
[10:03] <lotuspsychje> jhy: chrome is not really a supported package from the ubuntu repos, and how did you install electron?
[10:05] <jhy> It's mattermost desktop app which is acting similarly and it's on top of electron
[10:08] <jhy> I installed chromium and it has same problem
[10:08] <jhy> Is it "supported"?
[10:08] <jhy> Firefox doesn't have the problem or any text editor I tried
[10:10] <lotuspsychje> jhy: both chromium and firefox are now snaps, bugs related should also be filed towards their contact (snap info snapname)
[10:11] <lotuspsychje> lemme check recent chromium bugs holdon
[10:11] <jhy> I'm betting something deeper is causing this as it's on all chrome/electron/chromium
[10:12] <lotuspsychje> that might be jhy itsnot like your apps are crashing?
[10:13] <jhy> No they're not crashing. After start the mattermost has the correct layout but after unfocus and focus back it loses it
[10:14] <jhy> After boot I mean
[10:14] <lotuspsychje> jhy: ok
[10:14] <lotuspsychje> jhy: the routes for chromium bugs are; https://github.com/electron/electron/issues
[10:14] <lotuspsychje> and think for electron its their git; https://github.com/electron/electron/issues
[10:15] <Chunkyz> lotuspsychje, you pasted the same link twice. :-)
[10:15] <jhy> I tried checking there but didn't find anything related but I guess I could try make my own issue. and what chunky said
[10:15] <lotuspsychje> oops sorry
[10:15] <lotuspsychje> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
[10:16] <lotuspsychje> jhy: search that git for existing bugs first ok
[10:20] <jhy> I'll try those methods for now. Thanks lotuspsychje :)
[10:21] <lotuspsychje> jhy: could it be this? https://github.com/electron/electron/issues/28119
[10:21] <ubottu> Issue 28119 in electron/electron "[Bug]: Electron does not pass unrecognized locales through to the application" [Open]
[10:28] <jhy> Don't believe so
[10:30] <lotuspsychje> ok
[10:41] <jhy> Hi again. I pinpointed the issue with few boots accidentally as I was booting up for other things
[10:41] <jhy> It resets the locale of those apps when I open terminal
[10:41] <jhy> :D
[10:42] <jhy> All works fine until I open terminal
[10:54] <jhy> oh... My .bashrc breaks something but how it breaks those apps is beyond me
[11:03] <jhy> So... this command: `setxkbmap -option "nbsp:none"` defaults the locale of chrome/electron/chromium in ubuntu 22.04 
[11:04] <jhy> I've had this command since 16.04 to stop myself of inserting non-breaking whitespace to vim
[11:04] <jhy> funny
[11:30] <jhy> Oh well, I guess I'll find an alternative to that command
[14:49] <lotuspsychje> anyone on jammy with nvidia graphics that can test polari on wayland? on intel 620 it seems to launch
[14:51] <ravage> lotuspsychje: launches
[14:51] <lotuspsychje> tnx to test ravage 
[14:51] <lotuspsychje> Eickmeyer: ^
[14:51] <Eickmeyer> Wierd.
[14:52] <lotuspsychje> wich nvidia driver are you using ravage ?
[14:52] <ravage> 510.60.02-0ubuntu1
[14:52] <Eickmeyer> I'll re-test, but E:TakingVehicleToShop
[14:52] <lotuspsychje> kk tnx
[14:52] <lotuspsychje> ok hf Eickmeyer 
[14:52]  * Eickmeyer rolls eyes
[14:52] <Eickmeyer> Thanks. :)
[14:53]  * ravage goes back to Xorg because wayland almost messes up everyrthing else :D
[14:53] <lotuspsychje> heh
[14:53] <lotuspsychje> work in progress
[14:54] <xclaesse[m]> Hi, I'm testing Ubuntu 22.04, one issue I have is my wired networkd device does not appear. Wifi works fine. Is that a known issue? Any workaround possible?
[14:54] <ravage> xclaesse[m]: new hardware? did it work on the previous version?
[14:56] <ravage> does it show up in "nmcli d s" ?
[14:56] <xclaesse[m]> it was working fine on 20.04
[14:56] <xclaesse[m]> now even ifconfig does not show the iface
[14:56] <ravage> did you do an upgrade from 20.04?
[14:57] <xclaesse[m]> enp3s0f0         ethernet  unmanaged  --         
[14:58] <xclaesse[m]> yes, that's the one I think
[14:58] <xclaesse[m]> Yes it's an upgrade, that went terribly wrong, but that's my fault for not waiting for stable release
[14:58] <ravage> ok
[14:59] <ravage> try "sudo nmcli dev set enp3s0f0 managed yes" first
[14:59] <blb613988> is there anything else broken beside the iface not showing up?
[14:59] <blb613988> xclaesse[m]: ^
[15:00] <ravage> if that does not solve it try "sudo touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf; sudo systemctl restart NetworkManager"
[15:01] <xclaesse[m]> note that even an usb-ethernet device does not work
[15:01] <xclaesse[m]> ravage: did not change anything
[15:01] <xclaesse[m]> blb613988: I have a loooong list of regressions unfortunately. Getting a bit worried about this releae tbh. But nothing related to my wired network issue.
[15:02] <ravage> xclaesse[m]: the official upgrade from 20.04 will not be ready until the 22.04.1 release. you will not get any prompt before that. first upgrade is from 21.10
[15:03] <xclaesse[m]> blb613988: the most annoying to me: all webkit apps are broken (that's reported already), firefox snap often does not startup or takes super long and cannot open new windows
[15:03] <xclaesse[m]> ravage: that worked!
[15:03] <xclaesse[m]> thanks
[15:03] <ravage> great :)
[15:04] <ravage> xclaesse[m]: nvidia card? then make sure you stay on Xorg for now
[15:04] <blb613988> xclaesse[m]: ok, thanks, then I'll wait until may
[15:04] <ravage> you can choose the session type after you select your username on the login screen
[15:04] <ravage> wayland still has a lot of issues for me too
[15:04] <xclaesse[m]> firefox snap also does not remember open tabs when restarting, not even pinned.
[15:05] <blb613988> you can use firefox from an AppImage. Forget snap
[15:05] <xclaesse[m]> intel
[15:05] <ravage> ok. intel support is usually fine
[15:05] <xclaesse[m]> firefox does not work at all with X
[15:05] <xclaesse[m]> but webkit does
[15:05] <xclaesse[m]> it's one or the other :P
[15:06] <ravage> chromium does not even open on wayland for me
[15:06] <ravage> but thats another snap thing
[15:06] <xclaesse[m]> but anyway, I'm not complaining, it's beta ;-)
[15:06] <lotuspsychje> theres a big webkit bug being worked on right now
[15:07] <xclaesse[m]> oh and l2tp VPN is broken too, that has been reported into launchpad too
[15:08] <xclaesse[m]> yes, I think it went down to mesa now: https://gitlab.freedesktop.org/mesa/mesa/-/issues/6236
[15:08] <ubottu> Issue 6236 in mesa/mesa "webkitgtk blank webview with mesa 22 and Intel Comet Lake" [Opened]
[15:08] <xclaesse[m]> I'm not too worried, that's going to be fixed
[15:08] <xclaesse[m]> Firefox I'm much more worried, because clearly snap is not up for the task at all
[15:09] <ravage> we are all worried about snap :)
[15:09] <lotuspsychje> xclaesse[m]: bug #1966418
[15:09] <ubottu> Bug 1966418 in webkit2gtk (Ubuntu) "[jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc)" [High, Confirmed] https://launchpad.net/bugs/1966418
[15:09] <ravage> but when 2 corporations make a deal the community has to obey i guess
[15:10] <xclaesse[m]> for an essential package in an LTS release that clearly should be reverted immediately, IMHO
[15:10] <xclaesse[m]> give it more time to mature into intermediary releaes
[15:10] <xclaesse[m]> but not my call
[15:12] <xclaesse[m]> lotuspsychje: thanks, found that link already. It's bad enough that it even show when googling the issue :/
[16:33] <lotuspsychje> seems like bug #1965673 is solved on my journal logs now
[16:33] <ubottu> Bug 1965673 in ibus (Ubuntu) "Object 0x... of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management" [Undecided, Fix Released] https://launchpad.net/bugs/1965673
[17:17] <lotuspsychje> tarzeau: im just noticing a lot of noise on journalctl -f regarding photoqt, you might wanna check that
[19:28] <tarzeau> lotuspsychje: could you copy paste that into a file and put it somewhere online with link to it?
[19:29] <tarzeau> lotuspsychje: could as well just put it up on the developer page (github.com) an issue?
[20:09] <lotuspsychje> tarzeau: sure, tomorrow
[20:11] <tarzeau> great, thanks!
[20:13] <lotus|NUC> ; )