[00:29] hello world! [00:30] quit [00:30] quit() [00:30] --help [00:31] how to quit in termux? huhuhu === guiverc2 is now known as guiverc [00:35] anyone tries new ubuntu desktop yet? [00:47] 22.04.2? yeah [00:49] 23.04 ? [00:49] oh [00:52] I've got a 22.04 Ubuntu server system (intel x59 chipset), with vfio passthru KVM (GPU + USB3 4port Hub). The VM is running windows 11. If I run Audio through the HDMI of the GPU, the VM hard freezes while watching/listening to media, but is fine if audio is run off a USB DAC. Is this likely just a nVidia driver issue and will be solved with an AMD GPU? [01:05] deepSleep: I've heard stranger theories [01:07] hmm [01:08] I want that HDMI audio output to work, means that the speakers for the pc audio are different from that of other devices plugged into the TV [01:08] not a great setup [01:08] sold all my old AMD cards during the GPU frenzy === chris14_ is now known as chris14 [01:40] Hi there. I installed kubuntu desktop over my ubuntu 22.04 installation. All works well, except when I apply a theme. It does not change the bottom panel. SDDM was chosen as the display manager if that helps. Any ideas on what could be causing this? [01:41] Also, if i installed the kubuntu-desktop package, is it safe to remove the ubuntu-desktop package [02:06] hi all. having a bit of an issue with refind bootloader. it finds grub (for ubuntu) but does not seem to find the direct vmlinuz [02:13] Yo. I am in the midst of an upgrade to loony lobster(tm) and it is asking if I want to change my apport config [02:13] they are taking out the word 'crash' in this line: - 'problem_types': ['Bug', 'Package', 'Crash'], [02:13] I am not sure what it does to do that [02:13] also what does this mean? @@ -20,7 +20,7 @@ [02:19] I will take my answer "on the air" /me predends this is a radio show [02:42] semitones: There is also #ubuntu-next that may have more lobster users. [02:53] thanks! [03:02] jhutchins, they told me that lobster is offtopic in -next now [03:03] FYI, this is on regular Ubuntu with the ubuntu-studio metapackage installed. I was going about my business when it prompted me that I could upgrade to lunar lobster [03:04] the apport was the only config file the upgrade prompted me was changing, and did I want to accept the changes. I am just curious what will change with Apport as a result of the new config file [03:06] maybe there is a launchpad somewhere that talks about this change? [03:07] https://github.com/canonical/apport/blob/main/etc/apport/crashdb.conf [03:08] this version of the file does not look like the one I was prompted about... [03:14] semitones: Looks like that was part of a fairly large security update. https://launchpad.net/ubuntu/+source/apport/2.26.1-0ubuntu2 [03:15] Specifically look at the changelog line: * Disable Launchpad crash reports for 23.04 release [03:15] In this changelog it describes turning off Launchpad crash reports for 22.10, but then turning them on again for 23.04. Is that what I'm seeing? https://launchpad.net/ubuntu/lunar/+source/apport/+changelog [03:15] Eickmeyer, thanks for the link, reading [03:17] semitones: 99.9% of the time, you're going to want the maintainer version of apport config files. [03:18] That is what I went with -- I am just trying to find out what changed, and it is surprisingly difficult. [03:18] I don't understand why commenting the entire line *enables* interactive crash reports [03:19] It doesn't really matter. In this case it's going to do the right thing. [03:19] and if the maintainer version is removing the word "crash" does that mean that in 22.10, my system was set up to generate launchpad reports, but now it won't generate them? I'm just trying to understand what the change will be [03:20] Every time a new version is released, they disable some more advanced crash reporting because there's no sense in reporting crashes that can no longer be fixed after release for a regular release. [03:20] They keep it on for LTS, but for regular release it's disabled. [03:21] Reason being is that the focus becomes the next regular release. [03:21] And, there will be no further release of the regular release. [03:21] Eickmeyer, that makes sense, let me see if I understand [03:22] When 22.10 was the current release, it was set to report bugs [03:22] at some point, lobster came out, so my config file was updated to disable the advanced crash reporting [03:23] now what I've upgraded to lobster, this change to my config file has turned crash reporting back on, because I'm on the latest point release again. Is that correct? [03:24] Not exactly. Before 22.10 was released, it would send all crashes to Launchpad and another crash reporting system. After release, the Launchpad reports get disabled, but the other crash reporting system remains. Same thing happened when 23.04 was released. And so on. [03:24] It looks like you upgraded to 23.04 during beta. Is that correct? [03:28] No, I just updated today. This just happened [03:28] Maybe something else changed this config file, and now the installation of 23.04 is just replacing it with the default? [03:28] Oh, I see. That's strange then. Either way, your system is fine and I wouldn't worry about it too much. [03:29] No sense in making a mountain out of a molehill. [03:29] But yes, 23.04 did replace it with the default upon upgrade for sure. [03:29] Yeah for sure, just trying to understand what the diff is telling me -- trying to get more ubuntu-literate :) [03:30] There was a thread on reddit recently with someone's "what to do after installing ubuntu" guides, and one of his recommendations was to disable apport [03:30] which I thought was weird [03:30] Well, The @@ xx,yy @@ is just line numbers and + is line insertions and - is line deletions. It's not tha big of a deal. [03:30] so when I got this diff, it made me curious about what settings apport actually has, and if they were changed for lunar lobster [03:30] Yeah, don't listen to those "what to do after installing ubuntu" things. They're all opinionated and horrible advice. [03:31] Yeah, I don't follow them, but I do read them to see what people's opinions are, and how people try to find solutions [03:32] The thing is, if you turn apport off, you are basically doing nothing to contribute to Ubuntu or help the developers. That's bad. [03:32] That's taking without giving. [03:33] yeah I think so too [03:34] so with the current apport settings, it reports a lot of things to the whoopsie database, but only generates the interactive, launchpad reports if you invoke 'ubuntu-bug' from the terminal, or if a package fails to install, as far as I understand the "problemtype" line of the config [03:34] Anyhow, the best way to learn more about diffs would be looking at the page I just showed you and looking at the diff there. That's literally the difference between the old upload of apport and the new one. Study it and you might learn what changed. It's a bunch of shell scripting and maybe some python. [03:37] semitones: If you really want to dive head-first into some stuff, you can take a look into some of the stuff that brought Edubuntu back to life: https://code.launchpad.net/~edubuntu-dev/ubuntu-cdimage/+git/ubuntu-cdimage/+merge/437167 [03:38] Very basic diff there, but shows you with some color and context how diffs work. [03:38] thanks! I'll take a look out of curiousity -- i looked in the 'available diffs' and didn't see the diffs for /etc/apport/crashdb.conf, but the reports for the security hole and patch are more than interesting enough :) [03:38] Cool. [03:46] test [03:46] ubuntu: pong === ubuntu is now known as Guest4263 [03:47] Hello, I have 3 monitors and the 3rd monitor won't use offer the resolution 1280 x 1024? All 3 worked on a previous OS and with Ubuntu the other 2 monitors are ok? [03:47] Guest4263: i would guess so [03:48] To elucidate, 2 montiors have the 1280 x 1024 resolution, however the 3rd monitor on Ubuntu doesn't offer 1280 x 1024? [03:48] i wonder why that is [03:48] what resolution does it offer? [03:48] jay321, Moi aussi. [03:50] Guest4263: if you rotate monitor 1 to monitor 3 position, does it not support the 1280 x 1024 resolution? [03:51] Toadisattva, 1600 x 900, 1400 x 900, 1368 x 768, 1280 x 800, 1280 x 720, 1024 x 768, 1024 x 768 (using this), 1024 x 576 and 960 x 540. [03:51] it's not mirroring another display or rotated or anything is it? [03:52] jay321, no, the lack of resoution options remains with the monitor1. [03:53] Guest4263: you know what im thinking is that the frequency speification is different on the their device in xorg.conf [03:53] Toadisattva, Screen Display shows Monitor1 as Unknown Display. Monitors 2 and 3 show the brand. [03:56] jay321, /etc/X11/xorg.conf.d shows no files? [03:57] Here's my gpu specs: https://dpaste.org/9G7K8 [03:58] sorry my linux skills are older systems : -(, let me do some searching [03:58] jay321, here's the monitor spec output: https://dpaste.org/Nfr6h [03:59] wait so one is hooked up via display port, one is via hdmi, and one via vga? [03:59] jay321, thx, I'm on Ubuntu 22.04. [03:59] Toadisattva, yes, all on the 1 gpu. [04:00] and you said you used a diffferent os and were able to get the 1280x1024 over the vga? [04:00] Toadisattva, yes, on Windows and LinuxMint. [04:00] hmm okay [04:01] I've moved to Ubuntu for a few reasons, but having trouble fixing the monitor resolution since a few weeks. [04:02] Guest4263: who is the monitor manufacturer? china? [04:02] been struggling a bit with 22.04 myself, kinda miffed they ended support for 20.04 yesterday [04:02] feels very unpolished compared to 20.04 [04:02] jay321, AOC. [04:03] jay321, AOC 22B2W LCD 21.5” 54.7 cm. [04:03] is there a hdmi or display port on the monitor that is hooked up with the vga at all and if so have you tried connecting it via one of them to see if it hits the correct resolution? [04:04] says there is an hdmi connection, is this correct? [04:04] also curious what aspect ratio it's showing in the display settins for each respecitve monitor [04:04] jay321, all 3 montiors have a Display Port, HDMI and VGA port. [04:04] Toadisattva: oh good point! [04:05] Guest4263: can you switch monitor 3 to display port from vga? [04:05] I imagine the card only has one of each port? [04:06] Toadisattva, Monitor1 1024 x 768(4:3), Monitor2 1280 x 1024(5:4) and Monitor3 1280 x 1024(5:4). [04:06] Toadisattva, yes. [04:06] I think that's it, set that bad bad to 5:4 [04:06] bad boy* [04:07] Toadisattva, how do I set that, as the GUI in Screen Dispplay only offers 1600 x 900, 1400 x 900, 1368 x 768, 1280 x 800, 1280 x 720, 1024 x 768, 1024 x 768 (using this), 1024 x 576 and 960 x 540. [04:07] oh it doen't igve you the option to change it [04:08] I tried a TUI command: video=VGA:1280x1024@75, but no change. [04:08] the three monitors are identical? [04:08] On the old Mint OS, support had me install some NVIDIA drivers, but I think I've done that already for Ubuntu. [04:09] Toadisattva, yes. [04:09] are you on the default mesa drivers? [04:09] Guest4263: what's the output of this command? cd /sys/kernel/debug/dri/0; echo [[:upper:]]* [04:10] Toadisattva, not sure, just a standard Ubuntu install and I think I installed some NVIDIA drivers? [04:10] *Run sudo -i first, to have access there [04:12] alkisg, https://dpaste.org/W9nvy [04:12] Guest4263: no, sudo -i first, not sudo in front [04:12] sudo -i , then run the line I said [04:12] alkisg, output is [[:upper:]]* [04:13] sudo -i cd /sys/kernel/debug/dri/0 ls | nc termbin.com 9999 [04:13] alkisg, output is DVI-D-1 HDMI-A-1 VGA-1 [04:14] OK, so, you should have put this instead: video=VGA-1:1280x1024@75 [04:14] As your output is named VGA-1, not VGA [04:18] alkisg, ran command and rebooted and no change. === ubuntu is now known as Guest5558 [04:18] test [04:19] working [04:19] what's the output of : cat /proc/cmdline [04:19] alkisg, BOOT_IMAGE=/BOOT/ubuntu_f5lz6p@/vmlinuz-5.19.0-41-generic root=ZFS=rpool/ROOT/ubuntu_f5lz6p ro quiet splash vt.handoff=1 [04:20] it looks like you can switch from wayland back to xrandr and manually set it: https://askubuntu.com/questions/1432677/ubuntu-22-04-problem-with-monitor-resolution [04:20] not sure if this will bork anything else though [04:21] That video= option is supposed to show up there. Did you add it to /etc/default/grub and did you run sudo update-grub. ? [04:22] alkisg, I haven't changed any grub. [04:22] alkisg, Just a default Ubuntu 22.04 fresh install. [04:24] Guest5558: where did you read about the `video=...` method to fix the resolution issues? It appears that it didn't have the full instructions on how to apply the fix [04:25] alkisg, I actually ran the correct command, but mis typed in this chat. https://ubuntuforums.org/showthread.php?t=2485770&p=14138205#post14138205 === ingodwetryst is now known as Guest3717 [04:25] "to force using a kernel parameter like this, video=desired_display:1280x1024@75." [04:26] alkisg, yep. [04:26] OK so it didn't have enough details for you to understand that this is supposed to go to /etc/default/grub.cfg [04:26] alkisg, ok, I'll do that now. [04:26] Before I tell you how to edit the grub configuration, what's the output of this? xrandr | nc termbin.com 9999 [04:26] And this: lspci -nn -k | grep -A4 VGA [04:27] alkisg, https://termbin.com/mnw5 [04:28] alkisg, here? https://dpaste.org/Py9iB [04:28] Guest5558 , and: lspci -nn -k | grep -A4 VGA | nc termbin.com 9999 [04:29] alkisg, https://termbin.com/lugg [04:29] Guest5558: yes there, GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=VGA-1:1280x1024@75" and then run sudo update-grub. Hopefully the nvidia driver will respect that, let's see [04:31] alkisg, VGA-0, not VGA-1 right? [04:32] You said: output is DVI-D-1 HDMI-A-1 VGA-1 [04:32] So VGA-1 [04:32] alkisg, xrandr https://dpaste.org/xUE8u [04:32] We want the kernel name, not the xorg name [04:32] So VGA-1 [04:32] alkisg, that's the old forum post, the monitors have been reconnected since that old post. [04:33] sudo -i cd /sys/kernel/debug/dri/0 echo [[:upper:]]* [04:33] Didn't you say that command showed VGA-1 20 minutes ago? [04:34] alkisg, you're right, VGA-1. However xrandr outputs VGA-0. [04:36] > We want the kernel name, not the xorg name [04:36] alkisg, ok [04:36] alkisg, echo upper https://dpaste.org/QSGTW [04:36] > yes there, GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=VGA-1:1280x1024@75" and then run sudo update-grub. Hopefully the nvidia driver will respect that, let's see [04:41] alkisg, unfortunately, same resolution? === ubuntu is now known as Guest3483 [04:42] boo [04:42] cat /proc/cmdline [04:43] alkisg, BOOT_IMAGE=/BOOT/ubuntu_f5lz6p@/vmlinuz-5.19.0-41-generic root=ZFS=rpool/ROOT/ubuntu_f5lz6p ro quiet splash video=VGA-1:1280x1024@75 vt.handoff=1 [04:44] alkisg, cat grub https://dpaste.org/qm1jR === Bocaneri is now known as Guest2961 [04:45] xrandr | nc termbin.com 9999 [04:46] alkisg, https://termbin.com/qwvs [04:49] id like to install 3 linux os on my 1 Tb ssd drive and have storage partition-how should i partion the drive (using bios no swap, no separate home dir)? [04:49] Then the nvidia driver ignored that setting. You'll need to use xrandr --addmode or a xorg.conf [04:50] ext 4 for each os i assume but what size type and flags for the bios grub partion [04:50] keep in mind 22.04 uses wayland [04:52] This is xorg, see the output of xrandr [04:52] It doesn't say XWAYLAND [04:53] maybe it needs the xrandr label of vga-0? [04:53] * Toadisattva shooting in the dark here [04:53] Toadisattva, I have run VGA-0 command, but not added to grub. === Guest2961 is now known as Sauvin [04:54] I wonder if the situation changes if one one monitor is connected to the vga port. [04:54] s/one one/only one/ [04:55] and if monitors are shuffled [04:55] remove the label entirely [04:55] topcat001, I've moved cables around on the monitors. [04:55] Toadisattva, what label? [04:56] in the grub just do video=VGA-1:1280x1024@75 [04:56] how about just one monitor (any one) connected to the vga port? [04:56] and it should apply it to all 3 monitors [04:56] sorry [04:56] do [04:57] in the grub just do video=1280x1024@75 [04:57] without specifying the monitor [04:57] Toadisattva, so change this to what? GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=VGA-1:1280x1024@75" [04:57] remove the vga-1 [04:57] Toadisattva, k. [04:58] grabbing that from here under Set Custom Resolution for Multiple Displays - https://ubuntuhandbook.org/index.php/2021/05/custom-screen-resolution-ubuntu-wayland-xorg/ [04:59] Toadisattva, grub is now GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=:1280x1024@75" [04:59] yeah give it a go [04:59] rebooting... [04:59] lets see what happens [04:59] `ls /sys/class/drm/*/edid` should show the edids it's getting. Then I'd run them through edid-decode to see the modes listed; might help [04:59] (focusing on the vga) [05:02] Toadisattva, same issue. === ubuntu is now known as Guest6476 [05:02] boo okay was worth a shot [05:02] Toadisattva, yes, thx. [05:08] you remembered to run sudo update-grub before the reboot right? [05:09] Toadisattva, not after the last change, I'll do it now. === ubuntu is now known as Guest8560 [05:12] Toadisattva, unfortunately no change. [05:12] bah, okay [05:14] Guest6476: also try this in grub (remove the video= parameter completely), then update-grub, then reboot: drm.edid_firmware=VGA-1:edid/1280x1024.bin [05:17] alkisg, so back to the original grub? [05:18] Guest8560: yes, i.e. remove video= and add the drm= [05:20] It all depends on if the nvidia driver plays well or not. All the other in-kernel drivers do respect these settings [05:20] Unfortunately I don't have nvidia so I wasn't able to test, the last time I was testing all these options [05:21] any reason not just to switch back to mesa and go that route? [05:21] alkisg, so this is the grub now GRUB_CMDLINE_LINUX_DEFAULT="quiet splash drm.edid_firmware=VGA-1::edid/1280x1024.bin" [05:21] You mean nouveau? I guess performance? In any case if drm= also fails, then a xorg.conf or an xrandr command will do [05:21] Guest8560: right [05:23] sorry yeah I did mean nouveau [05:25] alkisg, unfortunately, same issue. [05:25] Guest8560: btw, do set a nickname, even if it's johndoe; it's easier to remember who we're talking to: /nick johndoe === ubuntu is now known as Guest616 [05:25] Is it there in cat /proc/cmdline ? [05:25] just for kicks can you run echo $XDG_SESSION_TYPE in a terminal [05:25] alkisg, ok. [05:25] If it's there and it wasn't working, then you'll have to use xrandr or xorg.conf [05:26] xrandr --addmode VGA-1 1280x1024; xrandr --output VGA-1 --mode 1280x1024 [05:26] alkisg, BOOT_IMAGE=/BOOT/ubuntu_f5lz6p@/vmlinuz-5.19.0-41-generic root=ZFS=rpool/ROOT/ubuntu_f5lz6p ro quiet splash drm.edid_firmware=VGA-1::edid/1280x1024.bin vt.handoff=1 [05:26] *or VGA-0, whatever xorg uses [05:26] Guest616: that's wrong [05:26] You have two :: [05:26] Remove one : and try it again [05:29] alkisg: if the edid fw load worked there is also a kernel message. I use custom edids for some setups. [05:29] topcat001: no idea what nvidia does though, they may ignore the kernel edid completely and re-read it themselves [05:31] right. However, they can at least verify if /sys/class/drm/*/edid is getting the right one [05:43] test [05:43] check [05:44] thx. I'm the monitor issue, still remains after BOOT_IMAGE=/BOOT/ubuntu_f5lz6p@/vmlinuz-5.19.0-41-generic root=ZFS=rpool/ROOT/ubuntu_f5lz6p ro quiet splash drm.edid_firmware=VGA-1:edid/1280x1024.bin vt.handoff=1 [05:44] real quick just run echo $XDG_SESSION_TYPE and let me know what you get back [05:45] Toadisattva, x11 [05:45] okay so you are on xorg [05:45] just wanted to check [05:46] Toadisattva, ok [05:46] I noticed it didn't have a size for vga [05:46] it? [05:48] there is this one to set the size wtih xrandr https://unix.stackexchange.com/questions/286084/what-does-the-size-parameter-of-xrandr-do#286089 [05:48] you may have already tried that [05:48] the xrandr readout didn't have a size for the vga* [05:49] kotgc: xrandr --addmode VGA-0 1280x1024; xrandr --output VGA-0 --mode 1280x1024 [05:51] alkisg, https://dpaste.org/FXc0i [05:52] kotgc: you mistyped, 0124 [05:52] alkisg, https://dpaste.org/Nx7N0 [05:53] kotgc: output of: xrandr | nc termbin.com 9999 [05:53] alkisg, https://termbin.com/f4px [05:54] kotgc: and do you have an /etc/X11/xorg.conf file? [05:54] hey, I have these kept back packages after a fresh install of 22.04 libglib2.0-0 libglib2.0-0:i386 libglib2.0-bin libglib2.0-data [05:54] (if so, pastebin it) [05:55] How do I upgrade them? [05:55] They seem to have some dependency loop keeping them from being upgradable [05:56] No, only an empty directory /etc/X11/xorg.conf.d. [05:56] OK, then we go to the last resort, let's see if nvidia will respect a xorg.conf, let me prepare one... [05:57] nvidia, respecting things? [05:57] :p [05:59] kotgc: output of this please: xrandr --verbose | nc termbin.com 9999 [05:59] bblinky1: true, it's really not cooperative :) Can you pastebin the whole terminal output of a `sudo apt full-upgrade` ? [05:59] alkisg, https://termbin.com/2dsq [06:00] alkisg: will you be ok with the output of nala in place of apt? [06:00] bblinky1, https://www.youtube.com/watch?v=IVpOyKCNZYw&ab_channel=JimFeig I'm starting to understand now. [06:04] alkisg: https://pastebin.pl/view/76472fb5 [06:06] kotgc: sudo wget https://termbin.com/bifq -O /etc/X11/xorg.conf [06:06] kotgc: if it has problems booting, go to recovery console and: sudo rm /etc/X11/xorg.conf [06:06] there it is [06:07] kotgc: indeed nvidia gives 0 shards about consumer linux drivers [06:07] bblinky1: I think that's just phased updates you're seeing, https://wiki.ubuntu.com/PhasedUpdates [06:08] alkisg: ok... So I should basically just let it be? [06:08] bblinky1: yes [06:08] Cool, thanks [06:09] Didn't even know about this "phased updates" feature of ubuntu [06:09] !phasedupdates | bblinky1 [06:09] bblinky1: Since Ubuntu 21.04, APT may hold back some updates on some systems while they are being phased in. This is called "phased updates". See https://ubottu.com/y/phased and https://help.ubuntu.com/community/PhasedUpdates for more info. [06:09] cool [06:09] I wonder how this makes sense on glib.. [06:10] But I suppose it's some expanssion of the testing repo? [06:12] Ah, it's all in the link [06:12] Thanks [06:16] test [06:16] alkisg, I think I did it right, but same issue? https://dpaste.org/rRQdf [06:17] jkotra: xrandr | nc termbin.com 9999 === toozej8517927 is now known as toozej851792 [06:22] Sorry, I meant kotgc ^ [06:23] alkisg, https://termbin.com/mxpl [06:25] kotgc: well, we tried our best. Revert everything, then try to switch to nouveau :D [06:26] alkisg, thank you. I'll research what nouveau is. [06:43] !nouveau | kotgc [06:43] kotgc: nouveau is an open-source nvidia driver included by default since Ubuntu 10.04. Currently, 3D rendering is only partially supported. More information can be found at http://nouveau.freedesktop.org/wiki/ | See !nvidia for the closed-source Nvidia driver. [06:46] hi all hoping someone can help me with a partion table for windows and ubuntu and minux/antix (debian based) using gpt but dont know what i need to partion ext4 for os/home and what for the grub (bios legacy-no uefi) [06:47] i know windows needs ntfs and another partion but will install windows first and then linux ubuntu after [06:47] l88l, if your boot process is legacy/bios then no ESP is required, if it's uefi then an ESP is required (all OSes use the same format for ESP; ie. following the standard) [06:47] no uefi [06:48] no ESP is required.. only partition what you'll use (all Ubuntu releases do not require ESP; though many ISO/installers create it by default [06:49] grub doesn't require any partition if you're not using uEFI.. it'll install to the /boot directory so it'll use whatever you partition for that (if nothing is partitioned, it'll just be a directory on / & simplier is usually better) [06:51] ty === shokohsc4 is now known as shokohsc === elastic_dog is now known as Guest8731 === mrelcee_ is now known as mrelcee [08:43] where does dkms or nvidia driver (packaged by Ubuntu) put the secure boot keys? [08:43] my bios forgot them [08:44] I want to reimport them [08:44] All I can ask is someone prepeare the libOIS in version 1.5.1 and put it into repository [08:44] great , for some reason my snap doesn';t link to libOIS which is build on demand ; I get : /snap/opendungeons-plus/110/usr/games/opendungeons-plus: error while loading shared libraries: libOIS.so.1.5.0: cannot open shared object file: No such file or directory [08:44] The people using my snap will be upgraded to buggy, useless piece of software , great ! [08:50] paul424: ravage already answered you about that issue yesterday? [08:50] partly [08:51] why someone cannot prepare a new version of libOIS and put it into repos ? [09:14] Is there any integration for self encrypting nvme drives? [09:24] paul424, in a snap a lib outside snap will not help you anyway [09:24] the creator of that snap has to add that to the snap [09:34] so how is the new 23.04 releaese like then? [09:34] good / bad? [09:35] !discuss | dreamcat4 [09:35] dreamcat4: Want to talk about Ubuntu, but don't have a support question? /join #ubuntu-discuss for non-support Ubuntu discussion, or try #ubuntu-offtopic for general chat. Thanks! [09:35] ah sorry [09:51] how to remove bluetooth module, I tried with `modprop -r` but I get: modprobe: FATAL: Module bluetooth is in use [09:53] ice9: You have to stop the systemd bluetooth.service first [09:53] (and disable it if you do not want to autostart it) === Atque_ is now known as Atque [10:11] ravage, I am the creator, I administer the opendungeons-plus as well develop it :D !!!! [10:12] then just compile the lib in your snap [10:12] as a part [10:12] you can find the staging libs required from the existing package [10:13] ravage, MAN , that's what I DO [10:13] but it doesn't work for some reason [10:13] after I moved to core 20 from core 18 [10:13] why would you do that [10:13] ravage, https://pastebin.com/gR57Dp9v [10:13] i would better move to 22 [10:14] ravage, hmm I needed the pybind11 which is availaible in core20 and core22 [10:14] i can have a look at that snap adter lunch [10:14] ravage, oki that would be supper [10:14] ravage, naahh I hang around on many channel but not on #ubuntu and #snappy on regular basis [10:15] yeap autojoin to #ubuntu added :D === andre is now known as Guest4126 [10:56] Hello! I am just realizing, this is running on my system (I wanted to update it) /snap/snap-store/638/usr/bin/snap-store --gapplication-service AND, I got hooked up on the name gapplication-service, maybe any of you guess why? Now, snap-store has no manual entry? No man page? and the --help and ----help-gapplication does not give too much [10:56] information either? Is this how stuff supposed to be under Linux? [10:57] yes-ubuntu: what's the actual question, I'm not quite understanding [11:00] ikonia: 1. I can not find man page for snap-store, I can not find explanation of what --gapplication-service actually does / is for? 2. I got here since I was about to update snap-store, and it is running (while I did not start it, it is not an open application / program at this current moment), hence I will have to kill the process manually vial [11:00] kill... [11:05] yes-ubuntu: snap store is a snap that presents the interface to download naps [11:05] snaps [11:05] the next part is a command argument [11:06] not sure why you want to kill it [11:06] it will auto update when there is a newer version [11:06] if you don't want the snap store, just stop it or remove the snap [11:07] ikonia: I've just seen a message that I have 13 days left to update snap and when I do snap refresh snap, I get that there are still processes running. [11:08] ikonia: however, my 1st point still stands, I got curious what the --gapplication-service does with the snap-store and I could find no information about ti? [11:08] I'd imagine look at the man page of snap, or the snap documentation [11:08] it's basically saying 'run this as an application' [11:09] here is a useful post on how to terminate correctly the snap store to allow it to update [11:09] https://discourse.ubuntu.com/t/how-to-close-the-snap-store-to-allow-snapd-to-update-it/30627/2 [11:10] looks like because it's launched as an app that it stays running even after the app is closed [11:10] (I didn't know that) [11:13] ikonia: yes, snap has a man page, however, there is no reference to --gapplication-service for snap-store ? And, snice snap-store is a separate part of snap, shouldn't it have it's own doc? [11:21] it's an argument for gnome desktop integration [11:21] it's not actually part of the snap === ff is now known as Guest1620 === evilgry is now known as Evilgry === Evilgry is now known as Evilgry2 === Evilgry2 is now known as Evilgry [11:56] We are having issues with the ptpd daemon (IEEE 1588-2008 time sync ) running in worker mode. We are seeing the process stop responding intermittently, and it appears to hang. It's UDP Recv-Q in netstat grows and grows continuously, like it's stuck and no longer able to process packets on the sockets it has opened. The ptpd daemon is running [11:56] 2.3.1-debian1-4 on Ubuntu Focal on arm64. There does not appear to be a newer version available to try. I have captured some core dumps and strace output. Can anyone offer guidance on how to proceed ? [11:58] AMDavid: no logfiles? verbose mode? debug mode? [11:59] AMDavid: can you put your dumps and strace outputs online and refer url to it? [11:59] well yes not much appears to have happened since 2015: https://sourceforge.net/p/ptpd/code/HEAD/tree/ [12:01] oh appears there's also: https://github.com/ptpd/ptpd [12:02] AMDavid: any reason you don't use NTP? [12:03] tarzeau I'm not able to trigger the issue on demand, but I will try to enable debug logs for next time. Will post a link to the files. linuxptp seems to be more active but does not work on our robot platform. We need more accuracy than NTP can offer unfortunately [12:11] dumps and strace file: https://s3.amazonaws.com/dcc_stuff/ptpd_not_responding.tar [12:11] hello [12:12] greetings from Brazil [12:13] hello mauro_melfi [12:13] Hello, good mornig [12:13] good morning [12:14] where are you from? I'm Brazilian [12:14] I updated ubuntu to version 23.04 (I was lts before) and the audio stopped working. I've tried fiddling with pulseaudio and pipewire, but I'm getting nowhere. Can anyone with a good heart direct me? A thousand thanks [12:14] i'm from italy [12:14] mauro_melfi: pulseaudio -k didn't help (as user)? [12:14] have you searched your computer audio Drive? [12:15] mauro_melfi: i keep having problems too with audio, with 23.04 AND 22.04 - funny thing is firefox (not snap) fails more, and installing google chrome works (youtube or discopolofreszzz) [12:16] AMDavid: what hw exactly you run your arm64 stuff on? [12:17] pulseaudio -k didn't help :( [12:17] AMDavid: how long does it work well until it doesn't work? have you tried later kernel with 22.04? debian 12 arm64? [12:19] AMDavid: i was able to locate the problem, it's right in there: [12:19] /* do the protocol engine */ [12:19] protocol(&rtOpts, ptpClock); [12:19] /* forever loop.. */ [12:19] ;) [12:29] tarzeau hw is Nvidia Jetson AGX Xavier https://www.nvidia.com/en-gb/autonomous-machines/embedded-systems/jetson-agx-xavier/ . Nvidia only support Ubuntu (20.04 or 18.04), so I've not tried a newer kernel than the one that Nvidia distribute (5.10.104-tegra) or Debian. We are using PTPD over wifi (there are mobile robots), whereas wired ethernet [12:29] is likely the norm. I'm wondering intermittent wifi network issues are triggering an issue with the ptpd code. [12:32] over wifi? and wifi is good? [12:34] AMDavid: i mean if you got spare hw, try if you can upgrade to 22.04. they use custom kernel? i'd go with debian arm64 (been using debian 11 on 20+ raspberry pies 3+4) [12:34] unfortunately i never got my hands on the jetson from nvidia (they had that phase years ago to get a devel board) [12:35] Sync over wifi is working and gives better granularity than wired. Thanks for the suggestion, will try to get a device on Debian and see if the issue occur on that OS as well. [12:36]