[00:27] <alex_mayorga> Hi! Someone wants me to get Valgrind for bug 907012 Can someone hand hold me through it?
[00:27] <ubot4> Launchpad bug 907012 in indicator-datetime (Ubuntu) "indicator-datetime uses 80% of RAM or 3.1g (affects: 1) (heat: 8)" [Undecided,Incomplete] https://launchpad.net/bugs/907012
[00:32] <alex_mayorga> problem is this is a service not an actual program, so I don't know where to start
[07:40] <lalatenduM> here is a bug on guake :https://bugs.launchpad.net/ubuntu/+source/guake/+bug/75013
[07:40] <ubot4> Launchpad bug 75013 in pdns (Ubuntu) "syslog error - unable to load libgmysqlbackend.so" [Undecided,Invalid]
[07:40] <lalatenduM> it is in confirmed
[07:41] <lalatenduM> though I am in bugsquad team I am not bale to change it to triaged , not sure why? need help
[07:42] <micahg> lalatenduM: only Ubuntu bug control can set the triaged state
[07:42] <micahg> and that doesn't look like the right bug number
[07:43] <lalatenduM> micahg, the bug number is Bug #750139
[07:43] <ubot4> Launchpad bug 750139 in guake (Ubuntu) "Guake size is messed up (affects: 5) (heat: 12)" [Undecided,Confirmed] https://launchpad.net/bugs/750139
[07:43] <lalatenduM> ubot4, yes that is the bug I am taking about
[07:43] <lalatenduM> Actaully I am trying to fix it
[07:44] <micahg> lalatenduM: ah,feel free to set to in progress and assign to yourself if you're working on it, just note that in the bug
[07:45] <lalatenduM> micahg, yup i was going to do that now, will do it
[07:46] <lalatenduM> micahg, DONE
[07:46] <lalatenduM> sorry done*
[07:46] <lalatenduM> :P
[07:47] <micahg> lalatenduM: do you have an importance you think it should have?
[07:47] <lalatenduM> micahg, let me think..
[07:48] <lalatenduM> micahg, it should be low , because it doesn't effect the function of guake
[07:49] <micahg> lalatenduM: ok, thanks, setting it for you
[07:49] <lalatenduM> thanks micahg :)
[07:49] <micahg> lalatenduM: thank you for your work
[07:50] <lalatenduM> thank you too sir!
[07:50] <micahg> you're welcome
[12:23] <wagafo> I think bug 907688  can be marked as triaged.
[12:23] <ubot4> Launchpad bug 907688 in update-motd (Ubuntu) "man for update-motd belongs incorrect category (affects: 1) (heat: 8)" [Undecided,Confirmed] https://launchpad.net/bugs/907688
[16:56] <roadmr> Hello all! due to a recent change, 32-bit Ubuntu defaults to using a PAE kernel, but by default PAE is not enabled in Virtualbox, so anyone trying to run Ubuntu on VBox won't be able to do so unless they explicitly enable PAE. Should this be a bug?
[16:57] <brendand> roadmr - a bug in what :)
[16:58] <micahg> roadmr: well, that's a hard one, in most cases, people don't need PAE for virtual machines as they're small
[16:58] <micahg> roadmr: seemingly something like testdrive should be fixed though :)
[16:58] <roadmr> micahg: I agree. So it's not a virtualbox bug (unless the fix were to enable PAE by default)
[16:58] <roadmr> nor is it a bug in the linux kernel
[16:59] <roadmr> or in ubuntu (not a bug, it's a decision)
[16:59] <roadmr> but I wonder where this should be noted so that people aren't confused when their VMs fail to boot :)
[17:00] <micahg> right, it's a settings issue, so there should be a note on pages where we ask people to test ISOs with reference to 12.04 and beyond, and stuff like testdrive where we control the settings, it should be enabled for 12.04 and beyond ISO testing
[17:00] <brendand> i wonder why VirtualBox doesn't have PAE on my default? won't a non-PAE image work with PAE on?
[17:00] <roadmr> brendand: yes it'd work
[17:00] <tray76> Let's see.. got vbox open right now.
[17:00] <micahg> brendand: possible performance impact
[17:00] <tray76> yup.
[17:01] <roadmr> micahg: well I agree that documenting this is a valid solution. Any idea on where this should be done?
[17:01] <brendand> micahg - i thought that was being considered in the decision making (that led to it being enabled by default)
[17:01] <micahg> roadmr: not offhand
[17:01] <brendand> although VMs to run on low memory, which is where i think the problems start to be seen
[17:01] <micahg> brendand: right, for our testing purposes, but virtualbox serves a lot of other OSs
[17:02] <brendand> s/to/tend to/
[17:02] <roadmr> micahg: OK, no problem, I'll figure out a good forum to raise this issue
[17:02] <brendand> micahg - yeah. but it can be set to on at least when the OS type is given as Ubuntu?
[17:02] <micahg> roadmr: ISO tracker probably wouldn't be a bad place if it has help links somewhere
[17:02] <roadmr> micahg: thanks! Anyway I think all this discussion is enough for me to call the bug invalid, as PAE is now a requirement for Ubuntu anyway
[17:02] <roadmr> micahg: actually, that's probably a good place - the official requirements page
[17:03] <micahg> brendand: true, that logic could be upstreamed, idr if you select an OS version with the OS type though as it's only 12.04 and beyond
[17:04] <brendand> micahg - i don't think so :(
[17:04] <roadmr> nah, it's just Ubuntu or Ubuntu 64-bit
[17:05] <micahg> well, in 2013 when desktop lucid is EOL, that would make sense to upstream PAE by default :)


[00:10] <noarb> before doing `do-release-upgrade`, it's usually recommeded to do a `apt update; apt upgrade`... is there any additional benefit to dist-upgrade or full-upgrade as well?
[00:22] <rfm> noarb, ubuntu rarely if ever does an update that removes packages, so dist- or full- wouldn't do anything beyond retular update
[00:37] <yukiup> thank you for ubuntu 21.10!
[01:06] <sdfgsdfgs> hey is it possible to change to the old Unity shell on ubuntu 20 or 21 (the desktop ? with cmd+1 or cmd+2 shortcuts and docker style simple things like on OSX)
[01:10] <yukiup> find what you want https://distrowatch.com/
[01:11] <Bashing-om> !unity | sdfgsdfgs
[01:12] <guiverc> sdfgsdfgs, ubuntu-unity-desktop is available for year.month releases (not snapped for Ubuntu Core 20 etc though)
[01:35] <dez_> Hello
[01:37] <Bashing-om> dez_: Ubuntu support question ?
[01:44] <dez_> Anybody here?!
[01:47] <yukiup> no
[01:47] <dez_> nice
[02:14] <ailaG> Hi. I'm fairly new to linux on desktop, and I've managed to cause Ubuntu to not recognize my touchpad, even though if I run an image from a usb drive it does. KDE's settings say "No touchpad found". Help? I've apt installed everything I found, somehow that didn't work :)
[02:14] <sdfgsdfgs> so it was working before ?
[02:14] <sdfgsdfgs> eh
[02:16] <ailaG> Yeah it was
[02:17] <ailaG> It was working, then I found that after it woke up from sleep it stopped working. modprobe psmouse stuff got it back, minus my settings. So I started messing with it and seem to have made it worse.
[02:18] <ailaG> BTW I do have experience with using Linux on servers so I can run commands and stuff
[02:22] <ailaG> sdfgsdfgs ?
[03:11] <Endermen1094> why was there not a opsion to install ubuntu on a duel boot system
[03:13] <guiverc> Endermen1094, there is; http://iso.qa.ubuntu.com/qatracker/milestones/428/builds/238228/testcases/1301/results shows a testcase for impish final
[03:13] <guiverc> you didn't provide release details - but it's there for Ubuntu Desktop & flavors (it's called "Installed Alongside" if using a ISO with `calamares` so differences can apply for specific release/iso etc)
[03:14] <guiverc> s/Installed Alongside/Install Alongside/ ^
[03:19] <Endermen1094>  i used the  OS: Ubuntu 20.04.3 LTS x86_64
[03:19] <Endermen1094>
[03:22] <Endermen1094> also it didn't give a promnt to manige space from my existing install (Gentoo) for it and ubuntu
[03:23] <donofrio> turns out snapd was killing my do-release-upgrade
[04:02] <guiverc> Endermen1094, the ISO you download dictates what installer you use; Ubuntu 20.04.3 Desktop's default ISO uses `ubiquity`, Ubuntu 20.04.3 Server's default installer is `subiquity` etc... how it appears depends on what 20.04.3 ISO you opted to download & install  (ubiquity & calamares have it) but you can always pre-prepare your disk yourself (gparted; gnome-disks, kde partition manager etc) then manually use whatever you've prepared (what I tend
[04:02] <guiverc> to do)
[04:03] <smk> Hello I m new to Ubuntu, I am facing an issue with my laptop after installing Ubuntu, can someone help
[04:04] <smk> My laptop heats up too much while using Ubuntu and when i switch back to windows my laptop doesn't heat up
[04:05] <sdfgsdfgs> maybe ubuntu community will be best to answer this question, it does involve you !
[04:06] <sdfgsdfgs> What is the best way to share an external monitor between 2 different servers, a linux and osx
[04:06] <donofrio> help, why does this message happen when I try to startxfce4? https://dpaste.org/GtSb
[04:06] <sdfgsdfgs> there has to be a better way than vnc and ssh xforwarding stuff
[04:19] <Bashing-om> sdfgsdfgs: See: https://help.ubuntu.com/community/SynergyHowto .
[04:40] <noel> hallo help me
[04:40] <noel> hahhahaa
[04:41] <lotuspsychje> ask a question first noel
[04:41] <noel> no no, its done thx
[04:42] <lotuspsychje> !yay
[04:44] <noel> what time is there?..
[04:45] <lotuspsychje> noel: come to #ubuntu-discuss we can chitchat
[07:43] <aslan> I need to download chrome and vivaldi via the terminal
[07:48] <lotuspsychje> aslan: the chrome version of ubuntu is chromium browser, sudo snap install chromium
[08:18] <repz> Hi there, i am having an issue upgrading from 20.04 to 21.10, openmpi-bin does not want to end its installation but i am not sure of what to do about it. "update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link /usr/bin/mpicc"
[08:23] <tomreyn> repz: this is about the update-alternatives mechanism, a set of symbolic links in /etc/alternatives which can be used to pick a preferences out of a set of choices, e.g. your preferred compiler version or text editor.
[08:24] <tomreyn> these choices are provided by (debian=.deb) packages. this openmpi-bin seems to be buggy in that it provides the same choice twice (if i'm interpreting this correctly).
[08:24] <repz> yes i get that but i am not familiar with mpicc/openmpi and i'm not sure how to get rid of this issue (any apt operation is locked for now)
[08:25] <repz> hmm ok
[08:26] <tomreyn> can you show    update-alternatives --list mpi | nc termbin.com 9999
[08:27] <tomreyn> looks like debian has a matching bug report (through it's old, might be something similar) slave link same as main link
[08:27] <repz> keep getting the same message
[08:27] <tomreyn> - "slave link same as main link"
[08:27] <tomreyn> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896189
[08:27] <repz> yes i found it but not the fix
[08:29] <tomreyn> were you saying that running    update-alternatives --list mpi    gives you the same error message?
[08:29] <tomreyn> (and nothing else?)
[08:29] <repz> yes nothing else
[08:31] <tomreyn> and    ls -l /etc/alternatives/mpi* | nc termbin.com 9999    ?
[08:32] <tomreyn> and what about     update-alternatives --display mpi | nc termbin.com 9999
[08:33] <tomreyn> repz: this is a bit cruel but i think it will let you proceed and not break anything:   sudo rm -f /etc/aternatives/mpi* /var/lib/dpkg/alternatives/mpi*
[08:34] <repz> already tried
[08:34] <repz> without luck
[08:34] <repz> https://termbin.com/qg6q https://termbin.com/vuq4m
[08:39] <tomreyn> hmm, try to   sudo dpkg -P openmpi-bin && sudo update-alternatives --remove-all mpi ; sudo rm -f /etc/aternatives/mpi* /var/lib/dpkg/alternatives/mpi*; sudo apt update && sudo apt install openmpi-bin
[08:40] <repz> wow
[08:40] <repz> seems to do the job
[08:41] <repz> thanks a lot
[08:41] <repz> (i was about to swith to manjaro)
[08:42] <tomreyn> good. it might return after you   sudo apt upgrade && sudo apt full-upgrade
[08:42] <tomreyn> but i assume not
[08:42] <repz> I wonder what did I missed, maybe a repository updates but i am just out of the `do-release-upgrade`
[08:43] <tomreyn> it's either a packaging bug, or you messed up your package system by installing software from incompatible sources
[08:43] <repz> never messed with mpi
[08:43] <tomreyn> try this: apt list --installed | grep ',local\]$' | nc termbin.com 9999
[08:44] <tomreyn> and show   apt policy
[08:44] <repz> this local grep does not catch anything
[08:44] <tomreyn> ok, the first would have shown packages without upgrade path
[08:45] <tomreyn> the second shows where packages may be installed from now
[08:45] <repz> https://termbin.com/xw90 (i think i adopted thi termbin, wasnt aware of it)
[08:46] <repz> https://termbin.com/drv1
[08:46] <tomreyn> okay, that's clean as can be, only official sources. so i guess it's really a packaging bug in the openmpi-bin package
[08:47] <tomreyn> those are rare but can occur, usually just in packages in the "universe" (community maintained) section
[08:48] <repz> yes thanks a lot for your time
[08:48] <tomreyn> note that hirsute only has another 3 months of support, you probably want to upgrade to impish (21.10)
[08:53] <repz> yes i am aware of that, that was the original plan but the release upgrade crashed in the middle bc of openmpi-bin. I usually stick to LTS, I installed this laptop since 18.04 release but i need newer releases of some packages (i even copmile some), that's why i wanted to upgrade to std / switch to manjaro/arch
[08:54] <tomreyn> repz: understandable- there are some ppa's which provide backports. but that could obviously get you into the same trouble.
[08:56] <repz> yes i am not a fan of it, i used ubuntu to have something 'stable' but i find myself struggling more with updates and custom setup :D
[08:59] <tomreyn> that's pretty inevitable when you do programming - you may need to build packages / dependencies on your own
[09:00] <tomreyn> at least in some cases
[09:00] <repz> zsh / awesomewm is not programing but yes :D
[09:01] <tomreyn> well, building custom software then ;)
[09:01] <repz> yes, i dived too much into customisation
[09:03] <tomreyn> i don't think you'll ever run into such problems if you can limit yourself to main + restricted apt sources. but that's pretty difficult.
[09:04] <repz> yes just bad luck, i'm on the road to 21.10, i'll see
[09:05] <tomreyn> 🍀🍀🍀
[09:22] <Donald_> Hello, My Ubuntu desktop just freezes, is there any way that I can find the root cause?
[09:23] <Donald_> The magic key was not working, I had to reboot my laptop by holding power button.
[09:24] <eggroll> the answer may be in the logs(next question answer=i dont know but i think you could look at dmesg tail -50 or something like that{this is where you ask someone else about how to enterpret and search for pid etc )
[09:25] <tomreyn> Donald_: which ubuntu release, which magic key did you try? did it freeze before? if not, what may have changed since it started doing so?
[09:26] <tomreyn> logs from before the system stopped responding should be available at    journalctl -b -1 -e    if you only rebooted once since (otherwise decrease "-1" further)
[09:26] <eggroll> ty tomreyn
[09:26] <Donald_> I am on Ubuntu20.04 LTS, I have tried "Alt + PrintSrc/SysRq + reisub".
[09:27] <tomreyn> it's AltGr, not just Alt
[09:27] <tomreyn> !sysrq
[09:28] <tomreyn> oh, i guess i'm wrong there, this must be specific to my localized keyboard
[09:29] <tomreyn> eggroll: you can safely test sysrq by switching to a tty...
[09:29] <tomreyn> !tty
[09:29] <Donald_> It was freezing when I was using Google Chrome.
[09:29] <tomreyn> ... and then pressing Alt-Sysrq-h which will print help to screen
[09:30] <tomreyn> how much RAM does this system have?
[09:31] <tomreyn> vmstat -s | head -n1
[09:31] <Donald_> 32 GB
[09:31] <Donald_> journalctl -b -1 -e, this only show some yellow text(warning?), no errors(red) found.
[09:32] <tomreyn> hmm, 32GB RAM is plenty, unless you were running anything that's a major memory hog.
[09:32] <tomreyn> if nothing was logged at the time, then the system probably didn't make it to log it before it froze.
[09:34] <Donald_> Yeah, that ram is enough for me.
[09:34] <Donald_> https://i.imgur.com/BwbWQhN.png
[09:34] <Donald_> You can check the screenshot there.
[09:35] <TJ-> worth noting Ubuntu defaults to disabling many of the magic sysrq functions
[09:35] <tomreyn> Donald_: you're running SAR there, maybe it can hint on what happened.
[09:37] <tomreyn> Donald_: other than that, if this system willfreeze repeatedly, you should probably run a memtest overnight and maybe prepare for some kernel debugging
[09:38] <tomreyn> https://help.ubuntu.com/community/DebuggingSystemCrash
[09:39] <tomreyn> i think current ubuntu releases only allow for U (emergency unmount) and B (reboot) of the 'reisub' sequence
[09:41] <tomreyn> that's for security reasons, settings can be changed in /etc/sysctl.d/10-magic-sysrq.conf
[09:42] <Donald_> noted, I will run a memtest.
[09:44] <tomreyn> !memtest | Donald_
[09:44] <tomreyn> !testing | Donald_
[09:45] <tomreyn> memtest86+ is an installable package. for newer systems, if you prefer uefi booting, you need to prepare a usb stick with the free version from memtest86.com instead
[09:46] <tomreyn> (you can also place that efi executable on your efi system partition)
[09:47] <tomreyn> high temperatures could also cause the system to shutdown (but usually not just freeze then)
[10:04] <Donald_> @tomreyn, noted, thanks, very helpful.
[10:10] <yxhuvud> Hi, I have a question. How do I enable pipewire for audio on 21.10? The howtos I found suggest using some example files from the pipewire dir, but those examples doesn't seem to be packaged so they fail at that step.
[10:59] <RomanSteam> ravage, tomreyn, Mekaneck, I actually solved my problem with Steam recently
[10:59] <RomanSteam> There's a bug in Ubuntu installer
[11:00] <RomanSteam> When I choose "install proprietary ... for graphics, media, Wi-Fi etc", it installs nvidia driver, but it doesn't work fine, and when trying to switch to another one, system crashes and lots of bugs appear
[11:00] <RomanSteam> But!
[11:01] <RomanSteam> If I choose not to install them, and then install them manually, by switching in the "additional drivers" menu, it works flawlessly. And steam runs successfully. Even with nvidia.
[11:03] <RomanSteam> There's something wrong with the installation process of Ubuntu. Some months ago I also discovered that it is extremely necessary to disconnect from the Internet during the installation
[11:04] <RomanSteam> Otherwise it'll not install properly and random bugs'll appear.
[11:31] <jsmooth> I'm trying ot use Docker via Laravel Sail, but it says bind failed becuase port 3306 is in use. Im trying ot figure out command to tell me which service is using it
[11:34] <EriC^^> jsmooth: sudo lsof -i :3306
[11:36] <jsmooth> Here's the output...not sure how to use it https://gist.github.com/longcurve/6237adacb894073f99d8187e30c5a99a
[11:37] <ogra> jsmooth, you typoed ... try again 🙂 (missing the colon before the port number)
[11:37] <ogra> jsmooth, also it is an i not a small L
[11:38] <jsmooth> Basically same output I updated the gist
[11:39] <ogra> still no colon ... better just copy/paste the command from EriC^^'s line directly
[11:43] <jsmooth> docker-pr 4067 root    4u  IPv4  45779      0t0  TCP *:mysql (LISTEN)
[11:43] <ogra> there you go
[11:43] <jsmooth> I think it's saying docker-prune is hte service
[11:45] <ogra> ps ax|grep 4067
[11:45] <ogra> that will giv you the full command
[11:45] <ogra> *give
[11:45] <jsmooth> Oh.it's docker-proxy
[11:45] <jsmooth> No idea what to do
[11:46] <ogra> i dont touch docker with a ten foot pole so i cant tell you either 🙂 perhaps ask in some docker channel
[11:46] <ogra> <- lxd user if it comes to containers ...
[11:46] <jsmooth> I have no idea what lxd is
[11:47] <ogra> linuxcontainers.org
[11:47] <ogra> ubuntus default container technology
[11:50] <cantthinkofanick> Anybody else seeing graphics issues after upgrading to 21.10? Gnome or "Ubuntu" on Wayland hangs for a while, then shows a corrupted screen with a "working" mouse. Gnome or "Ubuntu" on X11 gets a reddish tint (very visible on white backgrounds).
[11:53] <tomreyn> RomanSteam: it's probably just a matter of version you'd install. the installer will install the package versions it comes with (be sure to always use the latest installer), package updates are only installed after it first booted, and partially only applied after second boot.
[11:54] <tomreyn> cantthinkofanick: is there anything on your system logs on it? which graphics driver are you using?
[11:55] <jsmooth> #docker has no answer, but stopping and starting docker service didn't solve it
[11:56] <cantthinkofanick> I see some stuff regarding amdgpu that might be related but I'm really unsure. When Gnome on Wayland freezes I see a lot of "kernel: [96292.285192] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!" in the syslog.
[11:57] <cantthinkofanick> tomreyn: I'm using an AMD card, of course.
[11:57] <tomreyn> cantthinkofanick: which one?   lspci -knnd ::0300 | nc termbin.com 9999
[11:58] <tomreyn> cantthinkofanick: and which kernel?  cat /proc/{version*,cmdline} | nc termbin.com 9999
[11:58] <tomreyn> cantthinkofanick: and which mainboard?    journalctl -b | grep DMI:
[11:58] <cantthinkofanick> tomreyn: Dumping some info here:
[11:58] <cantthinkofanick> 06:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5)
[11:59] <cantthinkofanick> Oh, sorry, now I get it. :) Links coming in.
[12:00] <cantthinkofanick> tomreyn: https://termbin.com/ksux
[12:00] <cantthinkofanick> https://termbin.com/w7qk
[12:00] <RomanSteam> tomreyn, anyway, I'm using the latest installer
[12:00] <cantthinkofanick> tomreyn, motherboard: ASUS System Product Name/ROG STRIX B550-A GAMING, BIOS 1401 12/03/2020
[12:01] <tomreyn> cantthinkofanick: did you have kernel oopses?    journalctl -b | fgrep 'cut here' | wc -l
[12:01] <cantthinkofanick> tomreyn, nope, the reply there was zero.
[12:01] <cantthinkofanick> (I have rebooted the system since, though, so if that gets cleared it might not show.)
[12:02] <tomreyn> cantthinkofanick: did you have kernel oopses during the previous kernel uptime?    journalctl -b -1 | fgrep 'cut here' | wc -l
[12:03] <tomreyn> cantthinkofanick: you may want a newer AGESA for this graphics card, get a bios update. your current bios version is version 1401, build date 12/03/2020
[12:04] <tomreyn> cantthinkofanick: https://bugzilla.kernel.org/show_bug.cgi?id=205089 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870971 discuss the error you quoted initially - i have not read it, yet
[12:04] <cantthinkofanick> tomreyn, none there either - but the system doesn't crash per se, it just doesn't show graphics properly. Even with the Wayland picture completely corrupted I can use a text terminal on a different TTY completely fine. Yes, updating firmwares and bios may be a good way forward.
[12:05] <tomreyn> cantthinkofanick: did this corruption occur by the time you were playing a game?
[12:06] <cantthinkofanick> tomreyn, no this was directly after an upgrade from 21.04 to 21.10. The GUI misbehaved on first login.
[12:06] <tomreyn> cantthinkofanick: the kernel.org report suggests an amdgpu firmware upgrade. but i'd still do the bios, too
[12:07] <cantthinkofanick> tomreyn, yep, thanks a lot for the tip, I'll try and see what happens.
[12:11] <tomreyn> cantthinkofanick: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/amdgpu/picasso_sdma.bin is the git log for the amdgpu firmware file. you can download the latest at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/amdgpu/picasso_sdma.bin?id=d7b50e61669dc137924337d03d09b8986eb752a3 and place that in /lib/firmware/amdgpu/ as picasso_sdma.bin (after moving the old one out of the
[12:11] <tomreyn> way/deleting it)
[12:11] <tomreyn> file sha1sum is f0aa630a93f5f6c2e262a010f6b497b39b093b91
[12:12] <tomreyn> this is not a safe way to handle updates, of course.
[12:14] <tomreyn> cantthinkofanick: just in case you haven't spotted it, yet: bios version 2423 (release date 2021/08/17) is current https://rog.asus.com/motherboards/rog-strix/rog-strix-b550-a-gaming-model/helpdesk_bios
[12:16] <cantthinkofanick> tomreyn, thanks, yes, I just downloaded it (and Freedos to try and run the installer). Thanks for the link to the AMD firmware I was more unsure of that one. :)
[12:17] <tomreyn> cantthinkofanick: you can just place the contents of the (extracted) zip file on a fat32 formatted first partition on a usb stick, then load it from the within the existing bios.
[12:17] <jsmooth> I just cannot find how to get whatever to stop using port 3306
[12:18] <tomreyn> jsmooth: is the default port for mysql servers (mysql community edition, mariaddb server, percona server etc.)
[12:19] <tomreyn> *this (3306) is
[12:19] <jsmooth> Far as I can tell, mysql and mariadb servers are not running
[12:20] <tomreyn> as you previously seemed to have found out, it is docker-proxy what's hogging the port.
[12:21] <tomreyn> i also don't work much with docker, but i can search the web: https://stackoverflow.com/questions/39130263/docker-proxy-using-port-when-no-containers-are-running
[12:23] <cantthinkofanick> tomreyn, Things have sure gotten a bit easier since the late nineties. :)
[12:23] <tomreyn> easier? not sure, more complex for sure.
[12:24] <stefano> ciao a tutti
[12:25] <eggroll> in terms of partitions what do i need for a dual install debian based os and ubuntu (separate home partitions for each) many thanks in advance
[12:25] <tomreyn> eggroll: 2 or more partitions
[12:26] <tomreyn> unless you use lvm, then you *might* get away with one.
[12:27] <tomreyn> but i'd try to have them share only the ESP really, otherwise you may run into problems due to one using a newer and the other using an older version of some software
[12:28] <tomreyn> you should have only the newer OS manage grub, and disable it on the older.
[12:30] <tomreyn> an alternative, sometimes better, approach to having two OS installations available in a multi-boot setup is to use virtualization for one of them
[12:31] <lusy> ciao
[12:31] <lusy> ho un problema
[12:31] <eggroll> so my os partitions can be ext4 and other partition with the boot info is like 500MB but what type and which flags are needed guessing boot but what else
[12:31] <tomreyn> !it | lusy, stefano
[12:33] <tomreyn> eggroll: i think the only flag which really matters on an all linux system is the ESP / EFI flag (if it's a UEFI booting system)
[12:33] <tomreyn> eggroll: whichubuntu release are you installing, and how?
[12:34] <eggroll> the latest ubuntu stable and parrot os
[12:34] <eggroll> which is debian based
[12:35] <tomreyn> the latest stable ubuntu release would be 21.10, since two days or so
[12:35] <eggroll> not sure how much i should allow for each OS
[12:35] <eggroll> lol reading that a minute ago
[12:36] <eggroll> lets say the one prior for now
[12:36] <tomreyn> that'll have 3 more months of support - i'd rather go with the latest if you're installing fresh
[12:36] <tomreyn> (or lts)
[12:37] <eggroll>  i fresh install  like i change my jocks, thanks all the same for the warning my important shit is on other drives
[12:39] <eggroll> fair point but
[12:39] <tomreyn> i'd do 1 GB for /boot nowadays (if separate), 10 GB *minimum* for the rest (better 20 or 25 if a desktop)
[12:41] <eggroll> thanks man, yeah is a desktop with a few programs and much gui de etc
[12:42] <beuys> Hello! When I do "apt update && apt upgrade", I often get new packages. Does Ubuntu not inform the user when there are new updates?
[12:44] <tomreyn> beuys: i think that on both current desktop and server releases, updates would be installed automatically by default - but you can choose otherwise.
[12:45] <tomreyn> in fact, on desktops it may just present a graphical update prompt
[12:45] <beuys> tomreyn: I am using the Desktop. So maybe manual updates are not really supported and Ubuntu expects you to use the automatic approach.
[12:46] <beuys> tomreyn: I get such a prompt sometimes. But very rarely.
[12:46] <beuys> tomreyn: But when I check manually, there often are updates available.
[12:47] <tomreyn> beuys: check your settings: software-properties-gtk --open-tab=2
[12:47] <tomreyn> navigate tot he "updates" tab, if it's not already there
[12:48] <beuys> Aha. Yes, it says "Download and install automatically".
[12:49] <beuys> I am changing it to "display immediately"
[12:49] <tomreyn> also make sure that (at least) the first two checkboxes are checked
[12:50] <beuys> Id don't see checkboxes.
[12:50] <pantalaimon> Hi, I'm having trouble with the usrmerge package when upgrading to Ubuntu 21.10: It aborts with > Both /lib/x86_64-linux-gnu/libc.so.6 and /usr/lib/x86_64-linux-gnu/libc.so.6 exist.
[12:51] <tomreyn> beuys: well, i'm guessing what you're seeing since i don't even know which ubuntu release you'Re running
[12:51] <beuys> tomreyn: I think 20.04
[12:51] <tomreyn> lsb_release -ds
[12:52] <beuys> Ubuntu 20.04.3 LTS
[12:52] <tomreyn> pantalaimon: check what file type they are, what which one is older
[12:52] <tomreyn> pantalaimon: ls -l /lib/x86_64-linux-gnu/libc.so.6 /usr/lib/x86_64-linux-gnu/libc.so.6
[12:53] <beuys> Can I check if hardware acceleration works correctly? I tried to start Chromium, but it is insanely slow.
[12:55] <tomreyn> beuys: okay, on 20.04 you don't need to check any boxes - i'm still on 18.04
[12:55] <ioria> pantalaimon, can we see the full error ?
[12:55] <beuys> tomreyn: Ok, thanks!
[12:56] <tomreyn> beuys: if you paste this into the url bar of chromium, it should tell the HW acceleration status chrome://gpu/
[12:57] <tomreyn> note that chromium is a snap (thus running in a sandbox) on 20.04 LTS
[12:58] <beuys> tomreyn: Yeah, I know about the snap approach. Installing it again and then will test the url ...
[12:59] <beuys> tomreyn: Hmm... that is a lot of output.
[13:00] <beuys> Looks like some stuff is accelerated some stuff is not.
[13:00] <tomreyn> there's not just 1|0
[13:00] <beuys> Rasterization: Software only. Hardware acceleration disabled
[13:00] <beuys> Video Decode: Software only. Hardware acceleration disabled
[13:00] <beuys> :/
[13:00] <beuys> Is there a similar url for Firefox?
[13:02] <pantalaimon> tomreyn: ioria: https://paste.ubuntu.com/p/xWrYctcNPW/
[13:03] <ioria> pantalaimon, apt-cache policy usrmerge
[13:03] <beuys> Hmm.. there is about:support. But it has no easy answer :)
[13:04] <lusy> hello
[13:04] <pantalaimon> usrmerge:
[13:04] <pantalaimon>   Installed: 25ubuntu1
[13:04] <pantalaimon>   Candidate: 25ubuntu1
[13:04] <pantalaimon>   Version table:
[13:04] <pantalaimon>  *** 25ubuntu1 500
[13:04] <pantalaimon>         500 http://de.archive.ubuntu.com/ubuntu impish/main amd64 Packages
[13:04] <tomreyn> !paste | pantalaimon
[13:04] <lusy> I have the damaged hd, with ubuntu I can recover files such as excel, word
[13:05] <ogra> pantalaimon, is that when doing do-release-upgrade ? or do you try upgrading in any other way (which you should not)
[13:05] <tomreyn> beuys: about:support in firefox, scroll down to Graphics
[13:05] <beuys> tomreyn: Yeah, I see it. Seems to support HW acceleration on most aspects.
[13:05] <pantalaimon> ogra: this is during do-release-upgrade
[13:05] <tomreyn> lusy: this appears to be a statement. do you have an ubuntu support question?
[13:05] <ogra> pantalaimon, from 20.04 to 20.10 ?
[13:05] <ogra> er
[13:06] <ogra> 21.04 to 21.10
[13:06] <ioria> pantalaimon, 21.10 has libc6 2.34
[13:06] <pantalaimon> ogra: 21.04 -> 21.10
[13:06] <beuys> Anybody here using Chromium on Ubuntu 20.04? It seems impossible slow to me.
[13:06] <ioria> pantalaimon, but you have libc-2.33.
[13:06] <ogra> beuys, daily ... and happily ...
[13:06] <beuys> ogra: Via Snap?
[13:06] <tomreyn> beuys: what exactly is slow? how much RAM does this system have, how much available?
[13:06] <pantalaimon> ioria: I know, the upgrade did not finish
[13:06] <ogra> beuys, indeed
[13:07] <ioria> pantalaimon, ho, so it's a failed distro upgarde
[13:07] <pantalaimon> ioria: yes
[13:07] <beuys> tomreyn: Funny, it got fast now. Strange. Maybe something blocked it from the CPU or it did something in the background.
[13:08] <ioria> pantalaimon, and the process stopped ?
[13:08] <lusy> i wanted to know if i can recover word and excel files from my hd which is damaged
[13:08] <tomreyn> beuys: looks like you found a way to prevent answering the questions
[13:08] <ioria> pantalaimon, or it's still running someway ?
[13:09] <pantalaimon> ioria: yes it won't install any new packages until the usrmerge script is successufll
[13:09] <pantalaimon> dropped me back to the shell
[13:09] <tomreyn> lusy: testdisk and photorec
[13:09] <ioria> pantalaimon, you need to purge usrmerge
[13:09] <ioria> pantalaimon,  sudo apt purge usrmerge
[13:10] <tomreyn> lusy: the best approach is to first create an image of the full disk, or the parts that you need to recover data from, using ddrescue. you must store this image on a separate storage, though, not on the same disk.
[13:10] <lusy> I tried but failed
[13:11] <ioria> pantalaimon,  if it fails, we need to manually purge it
[13:11] <pantalaimon> ioria: thank you, it's gone
[13:11] <tomreyn> lusy: then create a copy of the image and work on that only, keeping the good image unmodified.
[13:11] <ioria> pantalaimon,  ok
[13:11] <pantalaimon> /usr/lib/x86_64-linux-gnu/libc.so.6 still points to libc-2.33.so though
[13:11] <pantalaimon> and I have a distinct /lib/x86_64-linux-gnu/libc.so.6
[13:12] <ioria> pantalaimon,  that's weird, because the first thing to get updated is libc6
[13:12] <tomreyn> lusy: how is the disk broken? physically? how do you know? and how did recovering data using testdisk and/or photorec fail? which tool did you use, which error messages were there?
[13:13] <ioria> pantalaimon,  run  'do-release-upgrade -c'
[13:14] <pantalaimon> Checking for a new Ubuntu release
[13:14] <pantalaimon> No new release found.
[13:14] <ioria> pantalaimon,  cat /etc/issue
[13:14] <pantalaimon> Ubuntu 21.10
[13:14] <ioria> i knew it
[13:15] <ioria> pantalaimon,  apt-cache policy apt  libc6  | nc termbin.com 9999
[13:15] <pantalaimon> https://termbin.com/kcmg
[13:16] <ioria> pantalaimon,  it's ok
[13:16] <ioria> pantalaimon,  sudo apt update
[13:16] <pantalaimon> All packages are up to date.
[13:17] <ogra> paradigm, dpkg -S  /usr/lib/x86_64-linux-gnu/libc.so.6
[13:17] <ioria> pantalaimon,  apt -s install usrmerge | nc termbin.com 9999
[13:17] <lusy> tomreyn: thank you, it's hard for me to do what you say
[13:18] <pantalaimon> ioria: https://termbin.com/2m6n
[13:18] <ogra> err sorry paradigm, that was for pantalaimon
[13:18] <ioria> pantalaimon,  sudo apt autopurge
[13:18] <tomreyn> lusy: you're welcome. it's difficult to help without more details, though.
[13:19] <tomreyn> and yes, data recovery is difficult
[13:19] <pantalaimon> ioria: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[13:19] <ogra> pantalaimon, dpkg -S  /usr/lib/x86_64-linux-gnu/libc.so.6
[13:19] <pantalaimon> ogra: dpkg-query: no path found matching pattern /usr/lib/x86_64-linux-gnu/libc.so.6
[13:20] <ogra> so your package system does not even know what file that is, where it comes from
[13:20] <ioria> it's a sym link
[13:20] <BluesKaj> Hi folks
[13:21] <ioria> pantalaimon,  let's try to install it again;  sudo apt install usrmerge
[13:21] <pantalaimon> I guess without usrmerge /lib/x86_64-linux-gnu/libc.so.6 will still be used
[13:21] <pantalaimon> I'm just surprised, wasn't usrmerge introduced a few releases ago?
[13:22] <ogra> pantalaimon, well, usrmerge sould have moved everything from /usr/lib to /lib around the 20.04 timeframe
[13:22] <pantalaimon> ioria: still Both /lib/x86_64-linux-gnu/libc.so.6 and /usr/lib/x86_64-linux-gnu/libc.so.6 exist.
[13:22]  * pantalaimon nods
[13:22] <ioria> pantalaimon,  can you install the pkg or stiil get errpors ?
[13:22] <ogra> err the other way around indeed
[13:22] <ogra> from lib to usr/lib
[13:22] <pantalaimon> ioria: still the same error, Both /lib/x86_64-linux-gnu/libc.so.6 and /usr/lib/x86_64-linux-gnu/libc.so.6 exist.
[13:23] <ioria> pantalaimon,  ok, cd /var/lib/dpkg/info
[13:23] <ioria> pantalaimon,  done ?
[13:24] <pantalaimon> ioria: just cd?
[13:24] <ioria> pantalaimon,  yes
[13:24] <pantalaimon> I'm in that directory now
[13:25] <ioria> pantalaimon,  sudo rm usrmerge.*
[13:25] <pantalaimon> I'll do sudo mv usrmerge.* /tmp/ just to be sure ^^
[13:25] <ioria> pantalaimon,  ok;  sudo apt-get -f install
[13:26] <pantalaimon> it completed oO
[13:26] <ioria> pantalaimon,  ok;  dpkg -l usrmerge | nc termbin.com 9999
[13:26] <pantalaimon> https://termbin.com/74ytn
[13:27] <ioria> pantalaimon,  it's ok; well done
[13:27] <pantalaimon> thank you!
[13:27] <ioria> no problem ; afk
[13:32] <paradigm> ogra: no worries
[13:37] <calimero200> sa vient de moi ou les autre réseaux sons dead??
[13:38] <ogra> !fr | calimero200
[13:38] <calimero200> OK
[13:50] <donofrio> anyone here use ubuntu on wsl2, I'm unable to get x to connect to VcXsrv even after adding VcXsrv to the firewall rules ;(
[13:52] <donofrio> I just get https://dpaste.org/GtSb
[13:56] <TRS> Hey Gang, which Distro has squid v5.2 (latest) included? I'm using ubuntu and 4.13 is all is will offer in apt. Thanks for the help.
[13:58] <pantalaimon> TRS: it's in Debian unstable, so likely it will trickle into the next version of Ubuntu
[13:58] <pantalaimon> https://packages.debian.org/sid/squid
[14:08] <TRS> pantalaimon: Thx.
[14:09] <TRS> pantalaimon: Do you happen to know if there are any pre packaged vAppliances for a squid proxy for download?
[14:49] <nikolam> Why Firefox from Snap in the first run tries to "import" my firefox profile that I am not using with it.. it says "Importing existing firefox profiles from /home/username/.mozilla/firefox"
[14:49] <nikolam> It is doing it without even asking if it is allowed
[14:50] <nikolam> Am I allowed to actually control where my profile data resides and what app is using it without default actions done without asking for permission..
[14:50] <nikolam> Is data now copied..?
[14:53] <ravage> You have root on your system. So you are allowed to control everything. I assume the import will copy data yes.
[14:54] <ravage> As the whole concept of snaps to keep things separated
[14:54] <oerheks> nikolam, not copied, just used. if you really want a clean profile, rename/remove ~/.mozilla ?
[14:54] <oerheks> it is a feature, not a bug
[14:55] <ravage> Are you sure it places the live dir outside the snap?
[14:56] <ravage> I have actually not tried it. Will face that with 22.04 I guess
[15:02] <nikolam> Where it wants to copy my data?
[15:02] <nikolam> Copy it into Snap storage?
[15:02] <nikolam> it is all not very transparent
[15:03] <nikolam> Make access right so that snap can access it
[15:03] <nikolam> Really no info what it is actually trying to do with my FF data
[15:03] <ducasse> ravage: it can't place it inside the snap, that's read only
[15:04] <nikolam> So what it is importing, like the list of the profiles? I have different profiles for different browsers
[15:04] <nikolam> Maybe I should just uninstall Ubuntu provided Firefox snap and never use it.
[15:05] <oerheks> nikolam, suddely you don't trust firefox?
[15:06] <nikolam> I don't think if someone would send bug report about Firefox in snap, that would be handled by Ubuntu anyway, since it's not Ubuntu compiled Firefox or something?
[15:06] <nikolam> I don't like snaps in general. They are Ubuntu-only and push uncompiled binaries from unknown source outside Ubuntu as I understand.
[15:06] <nikolam> I would rather get Firefox elsewhere.
[15:07] <nikolam> Why would I use it if I can't send bugs for it to distro I use
[15:07] <kostkon> nikolam, they are not Ubuntu only though
[15:07] <srv> why dont you use APT if is you have problems with snap to install firefox just advise but i really dont know the problem
[15:07] <nikolam> But binaries. Pushed to most used distro. As default browser.
[15:08] <nikolam> srv, That is great, except for the thing that Ubunut seems to be pushing to not to maintain Firefox in Ubuntu anymore in the future, that could just prolong the issue
[15:09] <oerheks> ...  seems to be pushing to not to maintain Firefox in Ubuntu anymore .. the opposite, we do.
[15:09] <oerheks> better, we share linux wide, but if you don't like snaps, use flatpak/compile from source?
[15:10] <ravage> also im pretty sure the .deb version still exists in 20.04 right?
[15:11] <TJ-> Bug #1943840
[15:13] <nikolam> oerheks, but who does provide binaries inside snap and who compiles them?
[15:14] <oerheks> ravage, yes https://launchpad.net/ubuntu/+source/firefox
[15:14] <oerheks> nikolam, the firefox team, ofcourse, and the source is available, tht is why firefox is included in many linux distros
[15:15] <oerheks> but snap is safe, better security due to sandboxing, and update mechanism
[15:15] <nikolam> It exists but by default during 21.04 -> 21.10 is uninstalled and snap is installed .. or it were first update action after update. Then it tries to "migrate" user data without asking and "Not sure" what it means by that
[15:15] <nikolam> oerheks, Who compiled it.
[15:16] <ravage> mozilla is in charge of the snap
[15:16] <oerheks> nikolam, time to check out launchpad for the maintainer info
[15:17] <oerheks> i just wonder why you suddenly care?
[15:17] <nikolam> But if mainteiner does not compiles it, it just maintains binary blob
[15:18] <nikolam> because binary blob distribution is not what Linux distros usually do.
[15:18] <oerheks> sure the maintainer compiles/tests it.
[15:18] <nikolam> And maintainer is outside Ubuntu?
[15:19] <Mekaneck> pretty sure the ubuntu guys test it too
[15:19] <ravage> a maintainer is just one person or a team that manages a package
[15:19] <ravage> when they compile something for ubuntu it is inside ubuntu
[15:19] <oerheks> 'outside'??
[15:19] <nikolam> But not compile it , as I understand snap with Firefox is just binary distribution made by someone in between Ubuntu and Mozilla.
[15:19] <ravage> you can ask to be a maintainer at any time
[15:20] <ravage> the snap is compiled and managed by Mozilla
[15:20] <oerheks> yes, on the pavement of 110 Southwark Street :-D
[15:20] <nikolam> If it is not compiled by Ubuntu buys, then, it is not Ubuntu package.
[15:20] <Mekaneck> sigh
[15:20] <nikolam> ravage, ok, then Ubunut does not ship Firefox anymore. Ok great. Won't use it anymore.
[15:20] <oerheks> you understand wrong.. but i leave you with it, no answer will satify you.
[15:20] <ogra> nikolam, snap packages have per-app home dirs, your profile will go to ~/snap/iirefox/current/.mozilla i guess ... if yu want to modify profiles, do it there
[15:20] <geomarcin> hello
[15:21] <ravage> whatever :D
[15:21] <Mekaneck> nikolam: have a look at Help -> About Firefox
[15:21] <nikolam> ogra, yes and Ubuntu does not provide it itself, but somone else and push it as binary blob in snap. I got it, thanks.
[15:21] <Mekaneck> in firefox that is
[15:21] <ravage> im not the biggest fan of the idea too. but as we are way over the topic here maybe #ubuntu-discuss ?
[15:21] <Mekaneck> what does it state nikolam?
[15:22] <ogra> nikolam, the firefox snap is maintained hand in hand between ubuntu devs and mozilla devs ... the mozilla devs prefer bugs in https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox
[15:22] <oerheks> !fud
[15:22] <geomarcin> anybody can help me with bluetooth dogle
[15:22] <Mekaneck> ravage: agreed
[15:22] <Mekaneck> nikolam: take the discussion to #ubuntu-discuss please
[15:22] <ogra> nikolam, for details read https://discourse.ubuntu.com/t/feature-freeze-exception-seeding-the-official-firefox-snap-in-ubuntu-desktop/24210
[15:24] <nikolam> No no, thank you all, I understood it, who maintains what. I got it. Future bug reports directly to Mozilla. I got it, thanks for the links.
[15:24] <oerheks> geomarcin, ask, wait and see?
[15:24] <srv> nikolam even firefox-esr is for debian i thin you can even install it on ubuntu you can try but thats is up to you
[15:24] <oerheks> what ubuntu version, what usb dongel specs?
[15:24] <nikolam> srv, I would rather download binary distribution form Firefox site. Thanks.
[15:25] <geomarcin> is Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
[15:26] <geomarcin> kubuntu 21.10
[15:26] <ogra> nikolam, why not just use the deb from the ubuntu archive if you dont like the snap ? it is still there and maintained (as the discourse topic tells you), just not installed by default
[15:27] <Mekaneck> ogra: the deb will disappear with the next release ;)
[15:27] <Mekaneck> FF will become snap only
[15:27] <ogra> merpnderp, yes ... but thats not today 🙂
[15:27] <ravage> also.. we left that topic already :)
[15:27] <nikolam> ogra, That is great idea, but I would be "The only one having problem" then because migration to snap is automatic from 21.10.
[15:27] <ogra> yeah, me shuts up
[15:27] <nikolam> yes, let's drop the topic, whe got answers.
[15:28] <ogra> oherwise -> #ubuntu-discus 🙂
[15:28] <ogra> *other
[15:28] <TJ-> ^s
[15:28] <oerheks> geomarcin, what ID nr does 'lsusb' in terminal  show?
[15:28] <geomarcin> us 003 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
[15:30] <oerheks> oh, that silicon device nr is a troublemaker .. https://askubuntu.com/questions/1208296/bluetooth-adapter-configuration-issue-id-0a120001
[15:32] <geomarcin> hmm  i will try but i think time to find another device for use bt here
[15:32] <TJ-> CSR is one of the best devices out there *if it is a genuine CSR chipset* and not a fake
[15:33] <oerheks> TJ-, indeed, i just finished this discussion; https://gist.github.com/nevack/6b36b82d715dc025163d9e9124840a07
[15:37] <geomarcin> oh no not helped here time to look for anothe device
[15:38] <oerheks> my last url github seems to have a fix, but i am still reading elsewere for more..
[16:58] <whoever> hi i have a question about eclipse IDE , i set up a simple hello world but when i try to run it iget launcher error
[17:18] <Mekaneck> whoever: better to ask them for support i guess
[17:22] <rfm> whoeverr: I googled "eclipse launcher error" and got quite a few likely-looking hits, there appear to be several possible causes.
[17:22] <rfm> whoever, you probably ought to look through them yourself to see if you have one that matches
[17:23] <rfm> whoever, but https://stackoverflow.com/questions/7070968/eclipse-executable-launcher-error-unable-to-locate-companion-shared-library  looks likely,being a failure on the first use after installing.
[17:28] <darkwolf> hola hola hoooola
[17:32] <Mekaneck> darkwolf: if you have a ubuntu support question just ask, casual talk is in #ubuntu-offtopic
[17:32] <darkwolf> que dice este?? estos droides jajaja
[17:32] <ravage> !es | darkwolf
[17:33] <darkwolf> ok thank you a mistake sorry
[17:33] <ldsh> Hi, I did update to 21.10 and Conky doesn't seem to start on startup any-more. It's still on the list of "Startup Application Preferences", and I tried adding some delay, but no conky showing up. If I start manually, it works fine. Do you know where I can look for the log of what is happening at startup?
[17:36] <GrandPa-G> I have a client that set up a Ubuntu server for me to access remotely. They have limited technical skills so I have to tell them what to do, but I don't know this first step.
[17:36] <lotuspsychje> ldsh: did you try the wayland vs the xorg test?
[17:36] <ldsh> lotuspsychje, Yes, I tried Wayland Gnome, X11 Gnome and Wayland Ubuntu
[17:37] <GrandPa-G> They set it up with phasephrase login. What do I tell them to do to allow me to login (using Putty). As a second choice, what do I tell them to do to just set my userid with a regular password ssh connect?
[17:38] <lotuspsychje> ldsh: you can try dmesg, journal logs to see more of what could be happening
[17:46] <ldsh> lotuspsychje, I see some elements in syslog: "systemd-xdg-autostart-generator[3082]: Exec binary 'conky-p5' does not exist: No such file or directory"
[17:46] <ldsh> I'll investigate this. Thanks!
[17:47] <repz> Hi, I have an issue with sudo, everytime i call it, it return `unable to resolve <laptop_hostname>  despite my /etc/hosts and /etc/hostname being well configured.
[17:49] <lotuspsychje> ldsh: can this help you? https://help.ubuntu.com/community/SettingUpConky
[17:51] <ldsh> lotuspsychje, I'm following their default way for autostart on Ubuntu, and it was working all fine this morning before I update.
[17:54] <ldsh> I'm testing something, rebooting
[17:55] <tomreyn> GrandPa-G: the easiest for the two sides will be that you set it up yourself on a VM or spare computer and use this to guide them through the process.
[17:56] <GrandPa-G> tomreyn, that is not possible for me to set up the vm. that is not my question
[17:56] <tomreyn> GrandPa-G: you can actuall yhave them install an ssh key from you stored on launchpad for you to be able to authenticate securely.
[17:57] <tomreyn> GrandPa-G: i'm not suggesting that you set up the server hosted at the client, but that you set up another one on your end so that you can guide them
[17:57] <GrandPa-G> tomreyn, what do I tell them to just allow a regular password me for now. Then I can add the key aftwards and they can set it back
[17:58] <tomreyn> you tell them to install with a regular user (suggest a username) and a secure (password generated generated) password, and to transfer the password to you on a secure channel, or at least a separate channel.
[17:58] <tomreyn> *password generator generated
[17:59] <lotuspsychje> ldsh: there seems to be a wayland bug on conky, but not sure its your issue yet bug #1947185
[17:59] <tomreyn> GrandPa-G: you also want to ask them to set up an ssh server (i don't think this happens unless you explicitly select it)
[18:00] <Auprivave> where is the interfaces file located in Ubuntu?
[18:00] <tomreyn> Auprivave: are you asking how to configure networking on ubuntu?
[18:01] <GrandPa-G> tomreyn, they can log in through ssh but somehow they set up the key.
[18:01] <Auprivave> I cant see the hotspot from my android phone
[18:01] <Auprivave> tomreyn: hi Tom. yes. from Ubuntu 21.10
[18:01] <GrandPa-G> tomreyn, they set up a userid for me, but it keeps asking for a passphrase
[18:02] <Auprivave> GrandPa-G: i might have same issue with my ubuntu 21.04 server
[18:02] <tomreyn> GrandPa-G: did they set a password for the user? are they able to login and get a shell?
[18:02] <Auprivave> Tom will solve everything for us
[18:03] <ldsh> lotuspsychje, Seems like they suggest to start conky twice and killing it inbetween quite strange
[18:03] <GrandPa-G> tomreyn, that I don't know, will have to ask.
[18:03] <tomreyn> Auprivave: are you asking about ubuntu 21.10 now, or 21.04, and desktop or server?
[18:03] <Auprivave> tomreyn: hotspot does not show up when running ubuntu 21.10
[18:04] <tomreyn> GrandPa-G: in fact i don't think oyu can install without setting a password at all, so they must have set one.
[18:04] <Auprivave> server is another issue. not critical though. It just asks for a password even though im using ssh.
[18:05] <tomreyn> Auprivave: so you've installed ubuntu 21.10 desktop, and you're trying to connect to your android hosted wireless hotspot, but it does not show in the list of access points?
[18:05] <GrandPa-G> tomreyn, so if I have them nuke my userid, then just do a sudo adduser username, it should be asking for a plain password, correct - no passphrase?
[18:05] <Auprivave> tomreyn: exactly. it worked with 21.04, but not 21.10
[18:06] <ldsh> lotuspsychje, Could be linked, however, strange that it didn't worked when I tried with x11. My test right now was to use "killall conky" in command line which seems to have found something (if I do a second time, it tels no process found)
[18:06] <Auprivave> oh. focal is 20.04 :D
[18:09] <lotuspsychje> ldsh: i dont seem to find much on your exact error online neither, so not sure at this stage
[18:10] <ldsh> Ok, I4l try different ways with reboot to check. I'll tell if I found something
[18:10] <lotuspsychje> good luck ldsh
[18:10] <tomreyn> GrandPa-G: password and passphrase are effectively the same thing, just passphrase is used to refer to more complex / longer / multi word password
[18:10] <Auprivave> i find the Redis-server package puzzling. Solved the Allocmem dependensie, but when trying to install redis-server_6.0.16 there is a missing dependensy: redis-tools (= 5:6.0.16-1~bpo11+1)
[18:10] <Auprivave> i cant locate redis-tools (= 5:6.0.16-1~bpo11+1)
[18:12] <Auprivave> redis-server in Ubuntu repo is ancient. Maitainers seems to have left it for dead. It just seems very strange. Why is there there no updated package for such a widely used database?
[18:13] <tomreyn> GrandPa-G:    sudo adduser mysupportuser && sudo add mysupportuser sudo && sudo apt install openssh-server     should be enough
[18:13] <tomreyn> GrandPa-G: don#t make them nuke the existing user, you can do that for them later
[18:14] <GrandPa-G> tomreyn, what password will mysupportuser have?
[18:14] <Auprivave> GrandPa-G: you set the passwd afterwards
[18:14] <tomreyn> GrandPa-G: the one they will be setting when prompted
[18:14] <tomreyn> Auprivave: does ubuntu 21.10 list other wireless entworks, though?
[18:15] <GrandPa-G> tomreyn, of course, silly me. I will tell them and see what happens, thanks
[18:15] <Auprivave> tomreyn: it does indeed. thats the strange part.
[18:15] <ldsh> lotuspsychje, My bad, now it works with X11 and not wayland, seems to be same as in the bug #1947185 Seems I did something wrong when I tried with x11 previously.
[18:15] <ldsh> Thanks for the help!
[18:16] <tomreyn> GrandPa-G: you're welcome. if this fails somehow, i'd ask them to install again, make sure they set up a new user during installation, note down the password they are setting there, and install openssh-server (sshd)
[18:16] <tomreyn> Auprivave: do other computers still see the hotspot? have you restarted the hotspot since?
[18:17] <Auprivave> tomreyn:  will test with 21.04 on my RPi to make absolutely sure.
[18:19] <tomreyn> Auprivave: if it's still listed there, then chances are that the desktop does not / no longer support the (outdated?) wireless protocol the android hotspot provides. or that its driver does not support this protocol (maybe you need a restricted driver for this)
[18:32] <tomreyn> Auprivave: those version numbers do not seem to exist on ubuntu
[18:33] <Auprivave> tomreyn: thanks. okay. Redis is pretty hopeless when it comes to maintaining.
[18:33] <tomreyn> 21.04 and 21.10 have redis-server version 6.0.15-1
[18:34] <Auprivave> tomreyn: cheacked wifi on my pi and my mac. they work. so issue is only with ubuntu 21.10 on my thinkpad here.
[18:34] <tomreyn> which wireless chipset does it have? which driver is loaded? lspci -knn | grep -EA3 '(Network|Ethernet) controller' | nc termbin.com 9999
[18:34] <Auprivave> tomreyn: weird. I get redis-serer 5.* when intalling on 21.04 and 21.10. I will check up on that. could be a repo issue.
[18:35] <tomreyn> the ubuntu package version is "5:6.0.15-1", which will be based on upstream version 6.0.15
[18:35] <Auprivave> much loved Broadcom on thinkpad x260
[18:36] <tomreyn> that's a company
[18:37] <Auprivave> its the Broadcom BCM4356
[18:37] <Auprivave> brcmfmac driver in use
[18:37] <ogra> typically using the brcmfmac driver
[18:37] <tomreyn> about "server is another issue. not critical though. It just asks for a password even though im using ssh." - using ssh doesn't mean that you're not going to authenticate with a password
[18:38] <ogra> (it is also not a PCI but SDIO device, lspci will likely not retun anything for it)
[18:38] <tomreyn> https://askubuntu.com/questions/739676/broadcom-bcm4356-driver looks like lspci output
[18:39] <ogra> err, i thought you talk about the Pi
[18:39] <tomreyn> oh, no, this is about a desktop computer
[18:39] <ogra> ah, sorry
[18:39] <tomreyn> the pi was just meant to be used to cross check whether the AP is available
[18:39] <tomreyn> no worries
[18:41] <tomreyn> i would not really know why the wireless client can't see the AP, though
[18:41] <Auprivave> pubkeyauthentification set to yes on the server. What setting in sshd_config did i miss?
[18:42] <ogra> brcmfmac pretty much lives from its firmware files ... check dmesg for firmware load issues
[18:42] <Auprivave> i will try to purge the kernel driver like they guy recommends trying.
[18:43] <tomreyn> don't do that if it's your only way to get online
[18:43] <Auprivave> downloaded the firmware.deb
[18:43] <Auprivave> got a cable as well. and hopefully the firmware deb package will be a safe way back in
[18:44] <Auprivave> love purging stuff. makes me feel very powerfull
[18:45] <ogra> until you purged too mch 😉
[18:45] <tomreyn> ssh/sshd: public key authentication is on by default on servers. you should ensure that a public key is configured at the right place on the server and that the ssh client tries to authenticate using the corresponiding private key. keep an eye on the servers' system logs while trying to authenticate
[18:46] <Auprivave> aah.. right. better check the logs. using Mosh and openssh.
[18:46] <tomreyn> permissions on both sides' key material also must not be too loose (nor too restrictive)
[18:46] <Auprivave> tomreyn: it could be the permissions
[18:53] <tomreyn> that, or solar flares. or something else.
[18:57] <Auprivave> oh boy :D how the f did i do this: d????????? ? ? ? ?            ? .
[18:57] <Auprivave> d????????? ? ? ? ?            ? ..
[18:57] <tomreyn> file system inconsistency
[18:58] <tomreyn> unmount, run fsck
[18:59] <Auprivave> drwxr-xr-x 30 thor thor 4096 Oct 17 19:59 ..
[18:59] <Auprivave> -rw-------  1 thor thor  108 Apr 30 21:47 authorized_keys
[18:59] <Auprivave> -r--------  1 thor thor  108 Apr 30 21:43 cicciolina.pub
[19:00] <Auprivave> this is no good? right?
[19:00] <Auprivave> i set password auth to no in the sshd config. So okay,like you said, it defaults to password if there is an issue
[19:01] <tomreyn> !paste | Auprivave
[19:02] <Auprivave> tomreyn: sorry. something i overlooked. Mosh askes for password, while regular ssh configname wont give me access now
[19:03] <tomreyn> "regular ssh configname"?
[19:03] <tomreyn> i don't know what you're meaning to say
[19:04] <Auprivave> ssh (name from ssh config) gives Connection refused.
[19:05] <Auprivave> password auth is set to no, but i can still log in with Mosh and password. wow!
[19:05] <tomreyn> connection refused would be a tcp level disconnect.
[19:06] <Auprivave> that explains. Mosh sneaks in via UDP
[19:06] <Auprivave> so im almost locked out of the server now
[19:09] <Auprivave> tomreyn: thanks. will look at it tomorrow. Interesting that Mosh can give a backdoor like that. Have a good one :)
[19:09] <tomreyn> you, too
[19:32] <linsux> ubuntu usb cannot boot on old ide notebook
[19:33] <ioria> linsux, really ? how did you do the stick ?
[19:33] <linsux> dd
[19:34] <ioria> linsux, what happens when you start it ?
[19:34] <linsux> no display
[19:34] <linsux> i tried ubuntu iso, server live iso and ubuntu-mate iso
[19:34] <ioria> linsux, what version ?
[19:34] <linsux> all the same
[19:34] <linsux> latest lts
[19:35] <ogra> 64 bit ?
[19:35] <linsux> yes
[19:35] <ioria> linsux, what's the laptop specs ? ram in particular
[19:35] <ogra> (i mean, is the hardware 64bit 🙂 )
[19:35] <linsux> yah it's 64bit hardware, 4g ram
[19:36] <linsux> it's core 2 duo t9400 something
[19:36] <linsux> it's old
[19:36] <ioria> linsux, it should work
[19:36] <linsux> so i want to install mate
[19:37] <ioria> linsux, no display at all or you get to the main manu at least ?
[19:37] <ioria> *menu
[19:37] <linsux> no display at all with fan spinning
[19:37] <ioria> linsux, dd again ad sync
[19:38] <linsux> fedora 64bit and debian 11 64bit no problem
[20:08] <bodom> Hi there! I have some trouble getting an USB3 card to run in ubuntu. I have the same card working in the same PC with a different linux (system rescue cd)
[20:14] <alkisg> bodom: which card?
[20:15] <bodom> alkisg: 02:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) (prog-if 30 [XHCI])
[20:17] <alkisg> What's the usb id?
[20:17] <bodom> how can i see it?
[20:18] <alkisg> Run: lsusb
[20:18] <bodom> Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
[20:19] <alkisg> So the problem is that your motherboard usb ports are not functioning?
[20:20] <alkisg> That's an internal usb hub of your board, right?
[20:20] <bodom> Nope, the MB USB1/2 ports are functioning. This is a PCI-Express internal USB3.0 card and it is not functioning
[20:21] <tomreyn> https://www.via-labs.com/product_show.php?id=48
[20:21] <alkisg> OK if it's a pci card, we need the output of this instead: lspci -nn -k | nc termbin.com 9999
[20:22] <bodom> tomreyn: not this one, probably a chinese clone
[20:22] <oerheks> How do you tell it is not working?
[20:24] <bodom> alkisg: https://termbin.com/udfb
[20:24] <bodom> oerheks: i plug stuff in and nothing happens
[20:25] <alkisg> 02:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01)
[20:25] <alkisg> 	Subsystem: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483]
[20:25] <alkisg> 	Kernel driver in use: xhci_hcd
[20:25] <alkisg> Which means a driver is properly loaded
[20:25] <alkisg> Run: dmesg -w
[20:25] <alkisg> Then insert a device, then check for errors
[20:26] <cbreak> bodom: does nothing happen in dmesg either?
[20:26] <cbreak> or journalctl?
[20:28] <bodom> alkisg, cbreak: tried two different divices which i am sure they are working. Dmesg is silent while i plug or unplug them
[20:28] <alkisg> Hmm, that's odd. What about: udevadm monitor
[20:30] <bodom> alkisg: nothing there too
[20:30] <Ronalds_Mazitis_> how do You code/compile using GLSL
[20:30] <Ronalds_Mazitis_> ?
[20:30] <Ronalds_Mazitis_> I am on 21.04
[20:30] <Ronalds_Mazitis_> banned on ##programming :D
[20:31] <Ronalds_Mazitis_> (sorry again)
[20:32] <alkisg> bodom: I would try an ubuntu version with a kernel similar to the one where it's working. Which kernel does your rescue cd use?
[20:34] <bodom> alkisg: 5.10.70, while i have 5.4.0 here on ubuntu 20.04 LTS. Can i upgrade just the kernel?
[20:34] <alkisg> bodom: sure, sudo apt install linux-generic-hwe
[20:34] <alkisg> It will get you 5.11
[20:35] <alkisg> sudo apt install linux-generic-hwe-20.04
[20:35] <bodom> alkisg: thanks, i'm trying that
[20:38] <tomreyn> searching the web about this seems to suggest it's a firmware issue, fixed by a windows-only firmware upgrade.
[20:39] <tomreyn> iommu=soft works around it
[20:42] <bodom> tomreyn: thanks, getting windows to upgrade it is too complicated, easiest to just get a new card :) Will the iommu=soft workaround slow i/o down?
[20:43] <cbreak> Ronalds_Mazitis_: OpenGL has functions to compile and link shaders. Use them.
[20:43] <Ronalds_Mazitis_> cbreak so it is c?
[20:43] <cbreak> what?
[20:43] <cbreak> GLSL? No.
[20:43] <cbreak> GLSL is GLSL. It's a programming language that is not C.
[20:45] <Ronalds_Mazitis_> oh ok
[20:47] <cbreak> Ronalds_Mazitis_: https://www.shadertoy.com
[20:47] <Ronalds_Mazitis_> wait so
[20:48] <Ronalds_Mazitis_> but I need some sort of compiler and extension to compile how to
[20:48] <Ronalds_Mazitis_> I believe opengl is installed in my ubuntu
[20:49] <cbreak> no
[20:49] <tomreyn> bodom: iommu=soft tells the kernel to use a software IOMMU (software bounce buffering (SWIOTLB)) rather than to rely on the hardware provided. it's most likely slower than the hardware implementation
[20:51] <Ronalds_Mazitis_> I want to compile on ubuntu not in that site
[20:52] <Ronalds_Mazitis_> google gives me answers in c
[20:52] <Ronalds_Mazitis_> that include opengl libraries
[20:54] <oerheks> !info glslang-tools
[20:54] <oerheks> dunno how to use that one
[20:58] <Ronalds_Mazitis_> https://cs.lmu.edu/~ray/notes/openglexamples/
[20:58] <noarb> does chrome use a different certicate store than update-ca-certificates uses? Should chrome running a system with an installed root certificate accept TLS connections, or does the certificate have to be manually installed into chrome, as well?
[20:58] <Ronalds_Mazitis_> Uploaded file: https://uploads.kiwiirc.com/files/b9895734f79d67229d20d83b56360e8d/pasted.txt
[20:59] <Ronalds_Mazitis_> I have dependecies installed something is wrong with triangle code
[21:00] <tomreyn> noarb: there's no chrome in ubuntu
[21:08] <cbreak> Ronalds_Mazitis_: glsl is compiled on the system where you run the program
[21:08] <bodom> alkisg, tomreyn: looks like the hew kernel fixed it
[21:08] <cbreak> as part of the GPU Driver / OpenGL runtime, there will be a GLSL compiler
[21:08] <cbreak> just call the OpenGL API
[21:08] <Ronalds_Mazitis_> dude I know cbreak
[21:09] <Ronalds_Mazitis_> https://uploads.kiwiirc.com/files/b9895734f79d67229d20d83b56360e8d/pasted.txt
[21:09] <cbreak> yeah? You fail at linking to OpenGL
[21:09] <cbreak> but that's unrelated to GLSL
[21:09] <cbreak> it's basic OpenGL
[21:10] <cbreak> and glut it seems...
[21:10] <cbreak> just link to the libraries for it
[21:10] <cbreak> cmake can help with that.
[21:10] <cbreak> or just hard code it, for a toy that's enough
[21:14] <Ronalds_Mazitis_> oh yeah I forgot I have to make makefile
[21:53] <noarb> I'm trying to just use curl and wget because I didn't know there wasn't a chrome or chromium package in ubuntu. I've installed a root certificate onto my machine, but when I try to connect via https it is untrusted. I have a Root I -> TLS CA II -> End user cert. If i just trust the TLS CA II it does work, though. Do I need to distribute the signed intermediate cert from the server in order to trust
[21:53] <noarb> connections from the root cert? Or is the root alone not enough, does the bundle need to be trusted?
[21:54] <leftyfb> noarb: chrome is not available from the official ubuntu repo's, but chromium does have a snap and google chrome is available to install via a .deb package from google.com/chrome
[21:55] <cbreak> you can use firefox too if you want a gui
[21:55] <cbreak> or links or lynx if you don't
[21:55] <tomreyn> noarb: root CA certificates should be installed on clients, intermediates and server certificates on servers
[21:56] <cbreak> if you want to check server side SSL configuration, try https://www.ssllabs.com/
[21:56] <noarb> I am using the .deb from google.com/chrome, but I'm having some trouble with certs. I installed to the system, but I think chrome uses a different keystore
[21:57] <noarb> tomreyn: should only the root be installed on the clients? Then does the server distribute its own key, and also the intermediate that signed it (which is signed by the trusted root)?
[21:57] <tomreyn> noarb: right
[21:57] <cbreak> normally it gives you the whole chain
[21:57] <tomreyn> hmm no, root CA certificate isn't usually part of the distributed chain
[21:59] <cbreak> It would give you every certificate up to the root
[21:59] <srv> i thouhgt firefox come pre install on ubuntu on the iso either way yo install it on a hard ware = pc otr in a vm i thight the only place where you have to install it was on windows on their wsl2 when installing ubuntu  but i dont know now
[22:03] <tomreyn> cbreak / noarb: https://security.stackexchange.com/questions/65332/ssl-root-certificate-optional
[22:04] <cbreak> tomreyn: yes. But you still have to send every certificate up to the root
[22:04] <cbreak> otherwise, how would anyone verify that all the certificates in the chain up to the root are valid?
[22:06] <tomreyn> cbreak: clients have the root certificate, receive all the other certificates from the servers they are connecting to, then build the full chain from that (via signatures)
[22:06] <cbreak> yes, as I said.
[22:06] <cbreak> you need to send up the whole chain up to the root.
[22:07] <tomreyn> right
[22:07] <cbreak> that way, clients can use the public key of the root to verify the first certificate in the chain, the one pointing to the first intermediate CA
[22:07] <cbreak> then continue until they reach the leaf
[22:18] <srv> anyway i think fire fox is an internet browser that is almost dead ppl use more and more chrome or chrmium
[22:18] <srv> chromium
[22:18] <srv> *
[22:19] <leftyfb> !ot | srv
[22:19] <oerheks> i doubt that, srv
[22:21] <leftyfb> srv: I'm pretty sure firefox still gets installed by default with all supported versions of ubuntu
[22:48] <cbreak> srv: https://backlinko.com/browser-market-share, chromium isn't even on the list
[22:57] <donofrio> anyone here use ubuntu on wsl2, I'm unable to get x to connect to VcXsrv even after adding VcXsrv to the firewall rules ;(
[22:57] <donofrio> I just get https://dpaste.org/GtSb
[22:57] <leftyfb> !wsl | donofrio
[22:59] <calwig> Windows 10 is Trash
[23:01] <srv> ???
[23:01] <donofrio> leftyfb, there are seven people in that empty channel, one of them is me.
[23:01] <oerheks> startxfce4 on wsl2 ???
[23:02] <oerheks> interesting...
[23:02] <leftyfb> calwig: let’s not
[23:02] <donofrio> been using gui ubuntu inside of w10 for last four years... https://www.tinyurl.com/donofrioworkremmina2020 and now that I converted and upgraded my install to 20.04 inside wsl2 it doesn't connect to x server
[23:03] <leftyfb> donofrio: feel free to contact Microsoft then
[23:03] <donofrio> leftyfb, is is ok to be mute on conversation that you do not know about...I'm talking to the other 1024 people here..
[23:04] <leftyfb> donofrio: wsl is not supported here. Neither is the custom X server that Microsoft is running to get GUI to work.
[23:06] <donofrio> seems like others like the idea at least....oerheks thought it was interesting...
[23:07] <leftyfb> Sure, doesn’t mean it’s supported here
[23:07] <leftyfb> donofrio: https://sourceforge.net/projects/vcxsrv/ feel free to go there for support
[23:07] <cbreak> an X server doesn't connect to things, it is connected to
[23:08] <cbreak> what connects to an X server is an X client, which is part of an application
[23:08] <cbreak> although I think ubuntu's again in the process of switching to wayland, for the second time
[23:09] <donofrio> cbreak, I can pivot to wayland too just would like to know the steps to get it working with xfce
[23:10] <ogra> cbreak, already happened (21.10 is wayland)
[23:11] <cbreak> interesting.
[23:11] <donofrio> ogra, so if I do do-release-upgrade -d from my state currently what would I use for wayland client?
[23:11] <oerheks> the only headache was a clipboard that is wayland compatible ..
[23:11] <ogra> donofrio, that is not how wayland works
[23:11] <donofrio> ogra, ah I am open to learn
[23:11] <ogra> wayland is a protocol, not an app
[23:12] <donofrio> so is X I thought?
[23:12] <ogra> you have a wayland compositor that drives yur desktop ... and app clients that talk to it
[23:12] <ogra> in case of Ubuntu gnome-shell is the compositor
[23:12] <donofrio> ok does a wayland app client exist in w10 (that you know of?)
[23:13] <donofrio> I know it
[23:13] <donofrio> is built in to w11
[23:13] <ogra> i have not used windows since XP (and even that only in VMs), no idea
[23:13] <donofrio> ogra, fair, just had to ask
[23:14] <donofrio> I only use it because moost companies these days are windows desktop shops and linux servers
[23:14] <ogra> i guess your best bet is to follow leftyfb's suggestion and ask at https://sourceforge.net/projects/vcxsrv/
[23:25] <donofrio> ogra, that is not any type of path they do x protocol not wayland
[23:26] <ogra> you said you are using 20.04 +
[23:26] <ogra> s/+//
[23:26] <ogra> that uses Xorg
[23:26] <testingbutidcc> is there an early access for ubuntu 22.04
[23:27] <srv> lol
[23:27] <calwig> yes there is, you first have to install Windows 11, then youc an preview Ubuntu 22.04
[23:27] <calwig> :P
[23:29] <ogra> testingbutidcc, isos shoudl show up on cdimage.ubuntu.com next week or the week after
[23:29] <ogra> the toolchain has been bootstrapped last week and the initial basic set of packages is building AFAIK
[23:31] <leftyfb> calwig: please stop
[23:31] <leftyfb> !ubuntu+1 | testingbutidcc
[23:31] <calwig> but its fun bashing Windows
[23:32] <leftyfb> calwig: this is a support channel. It's offtopic here
[23:32] <calwig> I know
[23:33] <srv> why tso agresis i think ppl that install ubuntu on there pc or dual boot are no supirior to ppl that probably want to continue use windows as their main machine but at the same time uses ubuntu either way on vm or throught wsl2
[23:33] <srv> why calwig is so agresisve
[23:33] <oerheks> lets not do this, srv
[23:33] <leftyfb> !ot | srv


[09:21] <ulysses__> Greetings. I want to install VMware Server on my laptop, and I have two question: 1. Is the real-time clock function compiled in the Ubuntu kernel (2.6.31)? 2. Was the parallel port PC-style hardware option (CONFIG_PARPORT_PC) built and loaded as kernel module?
[09:35] <joaopinto> ulysses__, for the second question: grep CONFIG_PARPORT_PC /boot/config-*
[09:36] <ulysses__> joaopinto: thanks
[09:45] <ulysses__> Good bye.
[10:04] <JanC> well, the parallel port driver is built as a module, but not loaded by default AFAIK...
[23:08] <dem0buntu> hi there, anyone awake :P
[23:09] <dem0buntu> can someone point me to a place so I can get tips fixing my kernel panic on wubi?
[23:10] <dem0buntu> btw, default kernel works like a champ, but every new wubi install I make at some point breaks newer kernels
[23:10] <dem0buntu> and I cant fix them


[06:19] <HiddenDjinn> question, does apt replace apt-get in trusty or in xenial?
[07:34] <flocculant> knome:re OEM -  flocculant brought this up some time ago and was put of caring by knome who did a good job
[07:36] <flocculant> HiddenDjinn: xenial - and it's not replaced as such, just added
[07:37] <HiddenDjinn> flocculant: ok, thanks
[07:39] <flocculant> knome: further - given that testing we get for normal iso's is pretty pathetic so not really why anyone would think adding things is useful
[07:39] <flocculant> s/not really sure
[07:39] <HiddenDjinn> flocculant: i got you
[07:40] <HiddenDjinn> s/not really why/not really sure why/
[07:40] <HiddenDjinn> fixed that for you
[07:41] <flocculant> and by adding things - I mean making testing harder - not the OEM thing - which I cared about once ;)
[07:43] <HiddenDjinn> oem thing?
[07:43] <HiddenDjinn> i dropped out of the linux world for a bit...i think i need background
[07:45] <flocculant> HiddenDjinn: a discussion that happened while I was asleep
[07:46] <flocculant> installing system - without user data - user adds that at first boot - like you get when you buy a pc pre-loaded windows
[07:46] <HiddenDjinn> flocculant: ok...contemplating sleep myself, soon
[08:09] <flocculant> ochosi bluesabre - some I suppose useful info - I appeared to have an iso kicking about here from 3rd Jan - lock was broken there
[08:11]  * flocculant suggests that we add lock/suspend testing to the post install test which currently doesn't test much
[08:11] <flocculant> !team | ^^
[08:12] <dkessel> makes sense, +1
[08:13] <flocculant> knome: re OEM - at least in vm - reboot to end user crashes ...
[08:15] <flocculant> flexiondotorg: before I start digging around - should oem work in a vm? just getting black screen here ...
[08:30] <flocculant> knome: one more OEM point - while you say we don't support it - we don't say that anywhere and OEM install is there on our iso just like it is anyone else's
[08:35] <flexiondotorg> flocculant Last time I tested, yes it does,
[08:35] <flexiondotorg> But I'm seeing some regressions in Ubiquity when testing on Friday night.
[10:22] <akxwi-dave> flocculant: agree  +1
[11:44] <ochosi> knome, bluesabre: we should have a brief discussion at some point about an inactive team members cleanup
[11:44] <bluesabre> alrighty
[11:58] <flocculant> flexiondotorg: thanks
[11:58] <flocculant> ochosi bluesabre - thoughts on adding lock to a testcase?
[11:59] <flocculant> can't see a problem with it tbh - better than not knowing *when* it failed
[12:04] <knome> ochosi, i'm around for that now for example
[12:05] <knome> tbe, now would be a very good time even
[12:06] <knome> flocculant, re: OEM: yes, i understand it's one more thing to test - but also yes, it's on our ISO whether we want it or not
[12:07] <knome> flocculant, and iirc i didn't say we don't want it, it wasn't the highest priority then (and it still isn't)
[12:07] <knome> flocculant, i might recall wrong as well though :P
[12:07] <flocculant> :D
[12:07] <knome> but yes, the problem is testing, but it's also a problem if somebody does an OEM install and then the end user is left with a completely broken or awkward system
[12:08] <knome> i don't know if we can hide the OEM option either?
[12:08] <flocculant> indeed
[12:08] <knome> i mean, completely remove it from xubuntu
[12:08] <flocculant> though oem install is something that we'd not be supporting 'personally' so would be a case of report it
[12:08] <knome> yes... at least primarily
[12:09] <flocculant> not sure whether that's possible
[12:09] <knome> my gut feeling is that most of the issues with OEM comes from upstream anyway
[12:09] <knome> i'm pretty sure we can't
[12:09] <knome> and aren't qualified enough to look
[12:09] <flocculant> :)
[12:09] <flocculant> you and me both then ;)
[12:09] <knome> yep ;)
[12:10] <flocculant> easy enough to add it to the testcase list - and make it optional or something
[12:10] <knome> so i guess the least thing we could do is run the OEM installation once or twice (not per cycle or within regular testing - literally just once or twice) and report any issues we find
[12:10] <knome> and yeah, optional testing could work as well, as long as we make it clear that it's probably the least important thing and the fact that it is a test doesn't mean it's supported - or will be
[12:10] <flocculant> we could have a 'Final BETA test' like we currently have for core
[12:11] <flocculant> eg - just sits there all cycle adding up as tests get run
[12:11] <knome> i'm thinking the OEM install is most useful with LTS's anyway
[12:11] <flocculant> but
[12:11] <knome> hmmh, not sure if we want to put more stuff on the final beta
[12:11] <knome> it's already quite busy
[12:12] <flocculant> my point re testing remains - if 1 or 2 people are testing it only on vm - what point is there in that
[12:12] <knome> not only for testing, but if bugs appear, it's likely that the other bugs will be always higher priority
[12:12] <knome> true
[12:12] <flocculant> well Beta or something - just flinging ideas about atm
[12:12] <knome> but then i'm not sure how much hardware is really concerned with the OEM stuff
[12:12] <knome> i mean it's a regular install, you only flip one bit and leave one software thing for after the installation
[12:12] <flocculant> well what oem is going to send a vm?
[12:13] <flocculant> or why would you oem install a vm?
[12:13] <knome> normally, you wouldn't
[12:13] <knome> i'm just trying to think of anything related to hardware that could break OEM
[12:13] <knome> and can't come up with anything
[12:14] <knome> in other words, hardware-related stuff happens regardless of OEM
[12:14] <flocculant> and then we really get into makeing sure that 'our' minimum specs are good - if we test oem it should install and run satisfactorily on our minimum
[12:14] <knome> sure, but again, it's the same installation really
[12:14] <flocculant> yes
[12:14] <knome> only the personal data input is moved after the installation
[12:14] <knome> but sure, maybe once a cycle - or once an LTS cycle
[12:15]  * knome checks our minimum specs
[12:15] <flocculant> but if some oem or charity came along and decided they were going to chuck xubuntu oem on a bunch of machines they have for charity and it fails to run - that's our problem isn't it?
[12:15] <flocculant> we've said it works for Xubuntu
[12:15] <knome> we offer anything without liability...
[12:16] <flocculant> yea - I know that ;)
[12:16] <knome> if we look at the "xubuntu at..." series, we can find many orgs are doing something like this with xubuntu
[12:16] <flocculant> all I'm saying is that ^^ is something we need to consider amongst eveerything else on the subject
[12:16] <knome> i don't think they are using OEM tbh, but...
[12:16] <knome> absolutely
[12:17] <flocculant> yea I know - which is where my original 'shoudl we do this' came from :
[12:17] <flocculant> )
[12:17] <knome> we say our minimum to install/try is 256MB
[12:17] <knome> and to use is 512MB
[12:17] <knome> i've considered many times what is the point of having two numbers anyway
[12:17] <flocculant> mmm
[12:17] <knome> if you try with 256MB, are you *really* going to get a 256MB extra piece of memory to run it?
[12:17] <bluesabre> flocculant, I am in favor of adding that test
[12:18] <flocculant> I'd not want to run firefox and some other app at the same time on 512MB
[12:18] <knome> me neither
[12:18] <flocculant> I'd have no screen in no time at all :D
[12:18] <knome> but what is bearable is subjective
[12:18] <flocculant> yea
[12:18] <knome> and we do word it like:
[12:18] <bluesabre> knome, install with 256, run with 512... don't imagine that's a typical use case
[12:18] <knome> Once installed, you should have at least 512 MB of memory.
[12:19] <knome> bluesabre, my point is, if you try/install with any amount less than the minimum to run, are you really going to add more memory after trying/installing?
[12:19] <flocculant> personally I'd be for upping that
[12:19] <knome> let's take that for the council meeting as well to hear what ochosi has to say
[12:20] <flocculant> you'd be nuts to do that - you'd add the memory and then think mmm what can I install I couldn't before I guess
[12:20] <knome> then at least pop those both to the same level at 512MB
[12:20] <knome> flocculant, exactly
[12:20] <bluesabre> knome, nope
[12:20] <flocculant> frankly I think we should be saying 1G
[12:20] <flocculant> anyway
[12:20] <ochosi> i don't have time for a real meeting, but a 5min thing
[12:20] <knome> that's our recommended
[12:20] <ochosi> i'm @work atm
[12:20] <knome> let's do a 5min for the team member stuff then
[12:20] <knome> here or want to take it privatE?
[12:21] <knome> (privacy of concerned persons etc)
[12:21]  * flocculant wanders off till later
[12:21] <knome> flocculant, hf and ttyl :)
[12:21] <flocculant> yup
[12:21] <flocculant> about more this week to cover point release
[12:22] <ochosi> knome: maybe private, but the ppl in question should mostly have received notice previously
[12:22] <knome> invited you two to a channel
[12:23] <knome> ochosi, bluesabre: ^
[13:03] <ochosi> knome: sry, had to leave
[13:03] <ochosi> i have another 4min window *now*
[13:03] <ochosi> :)
[13:04] <ochosi> and i'm in said channel (alone)
[13:04] <knome> no you're not
[13:12] <jjfrv8> flocculant, +1 to the lock/suspend testing
[16:03] <flocculant> back
[16:20] <akxwi-dave> front
[16:21] <akxwi-dave> :-)
[16:21] <flocculant> sideways shuffle
[16:21] <akxwi-dave> old man shuffle....
[16:21] <flocculant> \o/
[16:36] <flocculant> mp done for suspend/lock
[16:37] <flocculant> akxwi-dave: if you've time https://code.launchpad.net/~flocculant/ubuntu-manual-tests/1656882/+merge/314860
[16:37] <flocculant> if not it will ping slickymaster :)
[16:39] <akxwi-dave> :-) approved...
[16:40] <flocculant> super :)
[16:47] <flocculant> akxwi-dave: all done - on tracker now
[16:49] <flocculant> and failed test on tracker too ;)
[16:49] <akxwi-dave> :-)   must admit, I always forget about  lock/suspend as its the first thing i turn off on any laptop... so never use it
[16:51] <flocculant> not something I ever do unless someone else says it is broken ...
[16:51] <flocculant> and if people are running dev but not telling anyone - we don't know
[16:52] <flocculant> hence grabbing a1fa into here the other day :)
[18:30] <flocculant> ochosi bluesabre appear to have found the lock culprit
[18:30] <flocculant> grabbed old lightdm packages and worked through them till it stopped working
[18:43] <flocculant> https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/comments/7
[18:43] <flocculant> *appears* to be lightdm this time
[18:48] <flocculant> bluesabre: I assume you can set the importance on that bug from undecided to something entirely more suitable - like critical or something :p
[18:52]  * flocculant wonders if it started failing with 1.21.2-0ubuntu1 - the one I can't appear to find
[19:02] <flocculant> bluesabre: also robert ancell doesn't appear to be online so I can't ping him - maybe you will see him about later
[20:36] <flocculant> caught him in -desktop
[20:51] <flocculant> should have known he would want lightdm.log
[20:52] <flocculant> hopefully they'll be able to add whatever broke to regression tests for locking functionality
[20:53] <flocculant> paraphrasing r_ancell


[08:19] <zhsj> hi, could someone retry the build https://launchpad.net/ubuntu/+source/golang-golang-x-tools/1:0.6.0+ds-1/+build/26311726
[10:18] <ginggs> zhsj: .
[11:01] <paride> @pilot in
[12:19] <adrien>  \o
[12:29] <adrien> I'm doing +1 (I actually started on yesterday but I was digging in and tooling); can someone retry dolphin on armhf? retry-autopkgtest-regressions --blocked-by-tests dolfin | grep armhf
[12:29] <adrien> there have been many timeouts on armhf over the week-end and this one has shown timeouts too
[13:03] <jawn-smith> adrien: I'm on it
[13:23] <adrien> jawn-smith: \o/
[13:23] <adrien> and thanks :)
[13:24] <jawn-smith> yw!
[13:59] <adrien> ftr coq packages are blocked by 3 FTBFS: two of them will be fixed by merging from debian and one of them will also be fixed by merging but it does so by dropping 32-bit arches and I think there's a better fix (from upstream); I've added a report on LP with update-excuse tag and debian bug watch
[14:32] <paride> @pilot out
[14:38] <adrien> can someone retry-autopkgtest-regressions --blocked-by-tests gnustep-base | grep amd64
[14:38] <adrien> thanks :)
[14:39] <adrien> basically, gnustep-base uses httpbin.org for some of its tests and the host been unreliable but it seems fixed now so there's a window for making this pass
[14:39] <adrien> I think it's safe to do it on all arches; I'll let you judge if you want to do on more
[14:40] <adrien> there's also a patch upstream to use example.org/net instead but there's no reason to wait on that (it's not part of a release yet but I'm filling a bug in debian)
[15:00] <lvoytek> @pilot in
[15:11] <ginggs> adrien: gnustep-base triggered (on all arches)
[15:11] <adrien> thanks :) hopefully the timing is right and it passes
[18:58] <kanashiro[m]> vorlon: I'd like to ask if it is possible to remove containerd/1.7.2-0ubuntu2 (source and binaries) from mantic-proposed. I filed this bug with more details of what is happening LP: #2024490
[18:58] -ubottu:#ubuntu-devel- Launchpad bug 2024490 in containerd (Ubuntu) "[RM] Remove containerd from mantic-proposed" [Undecided, New] https://launchpad.net/bugs/2024490
[18:59] <lvoytek> @pilot out
[19:00] <kanashiro[m]> sorry, this should have gone to #ubuntu-release
[19:05] <seb128> kanashiro[m], removed
[19:05] <kanashiro[m]> seb128: thank you!
[19:05] <seb128> np!
[20:02] <adrien_> kanashiro[m]: btw, I'm looking at rack-related migrations and I'm wondering why it Replaces: ruby-rack (<< 3.0.0-1); disclaimer: I'm not familiar with these packages and I might also be unaware of some trick
[20:10] <adrien_> ftr, R packages seem to often need https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Converting-a-package-to-use-registration  which is part of https://github.com/edzer/intervals/commit/a8078e662b857fbee418e0c545c9805012b5f011 AFAIU
[20:10] -ubottu:#ubuntu-devel- Commit a8078e6 in edzer/intervals "address various CRAN issues"
[20:12] <adrien_> unfortunately I'm not sure all these packages are well-maintained
[20:12] <adrien_> s/packages/sources/
[20:15] <kanashiro[m]> adrien_: those are new packages and some code there used to be in ruby-rack before 3.0. I need to work on the transition to ruby-rack 3 in the debian side
[20:16] <kanashiro[m]> it is in my todo list
[20:22] <adrien_> kanashiro[m]: ok; so, is ruby-rack 3.0.0-1 usable? I'm asking because of https://launchpad.net/ubuntu/+source/ruby-rack/3.0.0-1ubuntu1
[20:22] <adrien_> and https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses.html#ruby-rack
[20:24] <kanashiro[m]> adrien_: some apps still do not support ruby-rack version 3 upstream, if you check the bug in the end of the excuses entry you'll see that I added the block-proposed tag to not let it migrate until I make sure everything is good to go
[20:26] <adrien_> kanashiro[m]: ah, right, sorry for the noise; I've been using other frontends to excuses today and they're not showing bugs!
[20:26] <adrien_> thanks!
[20:26] <kanashiro[m]> yw :)
[20:28] <kanashiro[m]> adrien_: I suppose you are working on a +1 maintenance shift, right? If you want to submit patches to the packages blocking ruby-rack I'd be happy in reviewing them, but I'd like to tackle them in Debian first
[20:31] <adrien_> right, +1; there are quite a few things stuck at the moment and which seem to only need small nudges so I'm focusing on these at the moment; or at least analyzing the current set of excuses so that subsequent people on +1 have an easier time
[20:31] <adrien_> (plus I really don't know ruby)
[20:31] <adrien_> but I might have a look
[20:31] <kanashiro[m]> it is up to you :)
[20:31] <adrien_> it probably depends on whether I have the courage to look at the 50 or so R packages with issues :D
[20:32] <kanashiro[m]> have fun!
[20:44] <adrien> hah, for R: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034683
[20:44] -ubottu:#ubuntu-devel- Debian bug 1034683 in src:r-base "r-base: new upstream release unintentionally uploaded to unstable" [Serious, Open]
[20:44] <adrien> > r-base (4.3.0-1) unstable; urgency=medium
[20:44] <adrien> > .
[20:45] <adrien> >   * New upstream release (into 'experimental' while Debian is frozen)
[20:45] <adrien> spot the issue
[20:45] <sarnold> oops
[20:45] <sarnold> how bad is that to undo?
[20:46] <adrien> it seems it was fine for debian but for us, r-base probably needs to be removed from proposed for now
[20:48] <sarnold> ah nice, it looks like debian gets to just sit back and let things run their course... I bet that'd work for us, too?
[20:49] <adrien> dunno, I don't have enough experience to judge :)
[20:50] <adrien> but I can say that there are 23 packages impacted by the "registration" issue with native code bindings
[20:51] <adrien> at least one project is maybe abandonned (I looked at two, maybe three, so the ratio is not good)
[21:08] <mitya57> Hi! I'm getting 500 error when trying to retry an autopkgtest: https://autopkgtest.ubuntu.com/request.cgi?release=mantic&arch=armhf&package=python-hypothesis&trigger=sphinx-rtd-theme%2F1.2.2%2Bdfsg-1
[22:28] <bluca> for the cloud autopkgtest environment, is it LXD running the relevant ubuntu version under test? I need to reproduce the exact same running environment, to debug some weird test issues
[22:29] <bluca> if some documentation on how to replicate locally exist, would greatly appreciate a pointer
[22:57] <bdmurray> lxd is only used for the armhf instances otherwise we are launching instances with openstack and connecting to them via ssh
[23:01] <bluca> is that qemu VMs then?
[23:02] <bluca> (never used openstack, not familiar with it)
[23:07] <bluca> found https://packaging.ubuntu.com/html/auto-pkg-test.html#executing-the-test
[23:14] <bdmurray> I would start with using qemu as a backend and see if you can recreate the issue
[23:18] <bdmurray> mitya57: I restarted a service and was able to submit the test again