[00:29] <rog> hello world!
[00:30] <rog> quit
[00:30] <rog> quit()
[00:30] <rog> --help
[00:31] <rog> how to quit in termux? huhuhu
[00:35] <mannydion> anyone tries new ubuntu desktop yet?
[00:47] <deepSleep> 22.04.2? yeah
[00:49] <mybalzitch> 23.04 ?
[00:49] <deepSleep> oh
[00:52] <deepSleep> 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] <mybalzitch> deepSleep: I've heard stranger theories
[01:07] <deepSleep> hmm
[01:08] <deepSleep> 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] <deepSleep> not a great setup
[01:08] <deepSleep> sold all my old AMD cards during the GPU frenzy
[01:40] <xrandr> 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] <xrandr> Also, if i installed the kubuntu-desktop package, is it safe to remove the ubuntu-desktop package
[02:06] <tweak> 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] <semitones> 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] <semitones> they are taking out the word 'crash' in this line: -        'problem_types': ['Bug', 'Package', 'Crash'],
[02:13] <semitones> I am not sure what it does to do that
[02:13] <semitones> also what does this mean? @@ -20,7 +20,7 @@
[02:19] <semitones> I will take my answer "on the air" /me predends this is a radio show
[02:42] <jhutchins> semitones: There is also #ubuntu-next that may have more lobster users.
[02:53] <semitones> thanks!
[03:02] <semitones> jhutchins, they told me that lobster is offtopic in -next now
[03:03] <semitones> 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] <semitones> 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] <semitones> maybe there is a launchpad somewhere that talks about this change?
[03:07] <semitones> https://github.com/canonical/apport/blob/main/etc/apport/crashdb.conf
[03:08] <semitones> this version of the file does not look like the one I was prompted about...
[03:14] <Eickmeyer> semitones: Looks like that was part of a fairly large security update. https://launchpad.net/ubuntu/+source/apport/2.26.1-0ubuntu2
[03:15] <Eickmeyer> Specifically look at the changelog line: * Disable Launchpad crash reports for 23.04 release
[03:15] <semitones> 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] <semitones> Eickmeyer, thanks for the link, reading
[03:17] <Eickmeyer> semitones: 99.9% of the time, you're going to want the maintainer version of apport config files.
[03:18] <semitones> That is what I went with -- I am just trying to find out what changed, and it is surprisingly difficult.
[03:18] <semitones> I don't understand why commenting the entire line *enables* interactive crash reports
[03:19] <Eickmeyer> It doesn't really matter. In this case it's going to do the right thing.
[03:19] <semitones> 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] <Eickmeyer> 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] <Eickmeyer> They keep it on for LTS, but for regular release it's disabled.
[03:21] <Eickmeyer> Reason being is that the focus becomes the next regular release.
[03:21] <Eickmeyer> And, there will be no further release of the regular release.
[03:21] <semitones> Eickmeyer, that makes sense, let me see if I understand
[03:22] <semitones> When 22.10 was the current release, it was set to report bugs
[03:22] <semitones> at some point, lobster came out, so my config file was updated to disable the advanced crash reporting
[03:23] <semitones> 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] <Eickmeyer> 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] <Eickmeyer> It looks like you upgraded to 23.04 during beta. Is that correct?
[03:28] <semitones> No, I just updated today. This just happened
[03:28] <semitones> Maybe something else changed this config file, and now the installation of 23.04 is just replacing it with the default?
[03:28] <Eickmeyer> Oh, I see. That's strange then. Either way, your system is fine and I wouldn't worry about it too much.
[03:29] <Eickmeyer> No sense in making a mountain out of a molehill.
[03:29] <Eickmeyer> But yes, 23.04 did replace it with the default upon upgrade for sure.
[03:29] <semitones> Yeah for sure, just trying to understand what the diff is telling me -- trying to get more ubuntu-literate :)
[03:30] <semitones> 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] <semitones> which I thought was weird
[03:30] <Eickmeyer> 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] <semitones> 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] <Eickmeyer> Yeah, don't listen to those "what to do after installing ubuntu" things. They're all opinionated and horrible advice.
[03:31] <semitones> 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] <Eickmeyer> 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] <Eickmeyer> That's taking without giving.
[03:33] <semitones> yeah I think so too
[03:34] <semitones> 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] <Eickmeyer> 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] <Eickmeyer> 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] <Eickmeyer> Very basic diff there, but shows you with some color and context how diffs work.
[03:38] <semitones> 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] <Eickmeyer> Cool.
[03:46] <ubuntu> test
[03:46] <jay321> ubuntu: pong
[03:47] <Guest4263> 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] <jay321> Guest4263: i would guess so
[03:48] <Guest4263> To elucidate, 2 montiors have the 1280 x 1024 resolution, however the 3rd monitor on Ubuntu doesn't offer 1280 x 1024?
[03:48] <jay321> i wonder why that is
[03:48] <Toadisattva> what resolution does it offer?
[03:48] <Guest4263> jay321, Moi aussi.
[03:50] <jay321> Guest4263: if you rotate monitor 1 to monitor 3 position, does it not support the 1280 x 1024 resolution?
[03:51] <Guest4263> 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] <Toadisattva> it's not mirroring another display or rotated or anything is it?
[03:52] <Guest4263> jay321, no, the lack of resoution options remains with the monitor1.
[03:53] <jay321> Guest4263: you know what im thinking is that the frequency speification is different on the their device in xorg.conf
[03:53] <Guest4263> Toadisattva, Screen Display shows Monitor1 as Unknown Display. Monitors 2 and 3 show the brand.
[03:56] <Guest4263> jay321, /etc/X11/xorg.conf.d shows no files?
[03:57] <Guest4263> Here's my gpu specs: https://dpaste.org/9G7K8
[03:58] <jay321> sorry my linux skills are older systems : -(, let me do some searching
[03:58] <Guest4263> jay321, here's the monitor spec output: https://dpaste.org/Nfr6h
[03:59] <Toadisattva> wait so one is hooked up via display port, one is via hdmi, and one via vga?
[03:59] <Guest4263> jay321, thx, I'm on Ubuntu 22.04.
[03:59] <Guest4263> Toadisattva, yes, all on the 1 gpu.
[04:00] <Toadisattva> and you said you used a diffferent os and were able to get the 1280x1024 over the vga?
[04:00] <Guest4263> Toadisattva, yes, on Windows and LinuxMint.
[04:00] <Toadisattva> hmm okay
[04:01] <Guest4263> I've moved to Ubuntu for a few reasons, but having trouble fixing the monitor resolution since a few weeks.
[04:02] <jay321> Guest4263: who is the monitor manufacturer? china?
[04:02] <Toadisattva> been struggling a bit with 22.04 myself, kinda miffed they ended support for 20.04 yesterday
[04:02] <Toadisattva> feels very unpolished compared to 20.04
[04:02] <Guest4263> jay321, AOC.
[04:03] <Guest4263> jay321, AOC 22B2W LCD 21.5” 54.7 cm.
[04:03] <Toadisattva> 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] <jay321> says there is an hdmi connection, is this correct?
[04:04] <Toadisattva> also curious what aspect ratio it's showing in the display settins for each respecitve monitor
[04:04] <Guest4263> jay321, all 3 montiors have a Display Port, HDMI and VGA port.
[04:04] <jay321> Toadisattva: oh good point!
[04:05] <jay321> Guest4263: can you switch monitor 3 to display port from vga?
[04:05] <Toadisattva> I imagine the card only has one of each port?
[04:06] <Guest4263> Toadisattva, Monitor1 1024 x 768(4:3), Monitor2 1280 x 1024(5:4) and Monitor3 1280 x 1024(5:4).
[04:06] <Guest4263> Toadisattva, yes.
[04:06] <Toadisattva> I think that's it, set that bad bad to 5:4
[04:06] <Toadisattva> bad boy*
[04:07] <Guest4263> 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] <Toadisattva> oh it doen't igve you the option to change it
[04:08] <Guest4263> I tried a TUI command: video=VGA:1280x1024@75, but no change.
[04:08] <Toadisattva> the three monitors are identical?
[04:08] <Guest4263> On the old Mint OS, support had me install some NVIDIA drivers, but I think I've done that already for Ubuntu.
[04:09] <Guest4263> Toadisattva, yes.
[04:09] <Toadisattva> are you on the default mesa drivers?
[04:09] <alkisg> Guest4263: what's the output of this command?   cd /sys/kernel/debug/dri/0; echo [[:upper:]]*
[04:10] <Guest4263> Toadisattva, not sure, just a standard Ubuntu install and I think I installed some NVIDIA drivers?
[04:10] <alkisg> *Run sudo -i first, to have access there
[04:12] <Guest4263> alkisg, https://dpaste.org/W9nvy
[04:12] <alkisg> Guest4263: no, sudo -i first, not sudo in front
[04:12] <alkisg> sudo -i <enter>, then run the line I said
[04:12] <Guest4263> alkisg, output is [[:upper:]]*
[04:13] <alkisg> sudo -i <enter> cd /sys/kernel/debug/dri/0 <enter> ls | nc termbin.com 9999 <enter>
[04:13] <Guest4263> alkisg, output is DVI-D-1 HDMI-A-1 VGA-1
[04:14] <alkisg> OK, so, you should have put this instead: video=VGA-1:1280x1024@75
[04:14] <alkisg> As your output is named VGA-1, not VGA
[04:18] <ubuntu> alkisg, ran command and rebooted and no change.
[04:18] <Guest5558> test
[04:19] <Oraclezb> working
[04:19] <alkisg>  what's the output of : cat /proc/cmdline
[04:19] <Guest5558> 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] <Toadisattva> 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] <Toadisattva> not sure if this will bork anything else though
[04:21] <alkisg> 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] <Guest5558> alkisg, I haven't changed any grub.
[04:22] <Guest5558> alkisg, Just a default Ubuntu 22.04 fresh install.
[04:24] <alkisg> 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] <Guest5558> alkisg, I actually ran the correct command, but mis typed in this chat. https://ubuntuforums.org/showthread.php?t=2485770&p=14138205#post14138205
[04:25] <alkisg> "to force using a kernel parameter like this, video=desired_display:1280x1024@75."
[04:26] <Guest5558> alkisg, yep.
[04:26] <alkisg> 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] <Guest5558> alkisg, ok, I'll do that now.
[04:26] <alkisg> Before I tell you how to edit the grub configuration, what's the output of this?  xrandr | nc termbin.com 9999
[04:26] <alkisg> And this: lspci -nn -k | grep -A4 VGA
[04:27] <Guest5558> alkisg, https://termbin.com/mnw5
[04:28] <Guest5558> alkisg, here? https://dpaste.org/Py9iB
[04:28] <alkisg> Guest5558 , and: lspci -nn -k | grep -A4 VGA | nc termbin.com 9999
[04:29] <Guest5558> alkisg, https://termbin.com/lugg
[04:29] <alkisg> 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] <Guest5558> alkisg, VGA-0, not VGA-1 right?
[04:32] <alkisg> You said: output is DVI-D-1 HDMI-A-1 VGA-1
[04:32] <alkisg> So VGA-1
[04:32] <Guest5558> alkisg, xrandr https://dpaste.org/xUE8u
[04:32] <alkisg> We want the kernel name, not the xorg name
[04:32] <alkisg> So VGA-1
[04:32] <Guest5558> alkisg, that's the old forum post, the monitors have been reconnected since that old post.
[04:33] <alkisg> sudo -i <enter> cd /sys/kernel/debug/dri/0 <enter> echo [[:upper:]]*
[04:33] <alkisg> Didn't you say that command showed VGA-1 20 minutes ago?
[04:34] <Guest5558> alkisg, you're right, VGA-1.  However xrandr outputs VGA-0.
[04:36] <alkisg> > We want the kernel name, not the xorg name
[04:36] <Guest5558> alkisg, ok
[04:36] <Guest5558> alkisg, echo upper https://dpaste.org/QSGTW
[04:36] <alkisg> > 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] <ubuntu> alkisg, unfortunately, same resolution?
[04:42] <Toadisattva> boo
[04:42] <alkisg> cat /proc/cmdline
[04:43] <Guest3483> 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] <Guest3483> alkisg, cat grub https://dpaste.org/qm1jR
[04:45] <alkisg> xrandr | nc termbin.com 9999
[04:46] <Guest3483> alkisg, https://termbin.com/qwvs
[04:49] <l88l> 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] <alkisg> Then the nvidia driver ignored that setting. You'll need to use xrandr --addmode or a xorg.conf
[04:50] <l88l> ext 4 for each os i assume but what size type and flags for the bios grub partion
[04:50] <Toadisattva> keep in mind 22.04 uses wayland
[04:52] <alkisg> This is xorg, see the output of xrandr
[04:52] <alkisg> It doesn't say XWAYLAND
[04:53] <Toadisattva> maybe it needs the xrandr label of vga-0?
[04:53]  * Toadisattva shooting in the dark here
[04:53] <Guest3483> Toadisattva, I have run VGA-0 command, but not added to grub.
[04:54] <topcat001> I wonder if the situation changes if one one monitor is connected to the vga port.
[04:54] <topcat001> s/one one/only one/
[04:55] <topcat001> and if monitors are shuffled
[04:55] <Toadisattva> remove the label entirely
[04:55] <Guest3483> topcat001, I've moved cables around on the monitors.
[04:55] <Guest3483> Toadisattva, what label?
[04:56] <Toadisattva> in the grub just do video=VGA-1:1280x1024@75
[04:56] <topcat001> how about just one monitor (any one) connected to the vga port?
[04:56] <Toadisattva> and it should apply it to all 3 monitors
[04:56] <Toadisattva> sorry
[04:56] <Toadisattva> do
[04:57] <Toadisattva> in the grub just do video=1280x1024@75
[04:57] <Toadisattva> without specifying the monitor
[04:57] <Guest3483> Toadisattva, so change this to what? GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=VGA-1:1280x1024@75"
[04:57] <Toadisattva> remove the vga-1
[04:57] <Guest3483> Toadisattva, k.
[04:58] <Toadisattva> 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] <Guest3483> Toadisattva, grub is now GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=:1280x1024@75"
[04:59] <Toadisattva> yeah give it a go
[04:59] <Guest3483> rebooting...
[04:59] <Toadisattva> lets see what happens
[04:59] <topcat001> `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] <topcat001> (focusing on the vga)
[05:02] <ubuntu> Toadisattva, same issue.
[05:02] <Toadisattva> boo okay was worth a shot
[05:02] <Guest6476> Toadisattva, yes, thx.
[05:08] <Toadisattva> you remembered to run  sudo update-grub before the reboot right?
[05:09] <Guest6476> Toadisattva, not after the last change, I'll do it now.
[05:12] <Guest8560> Toadisattva, unfortunately no change.
[05:12] <Toadisattva> bah, okay
[05:14] <alkisg> 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] <Guest8560> alkisg, so back to the original grub?
[05:18] <alkisg> Guest8560: yes, i.e. remove video= and add the drm=
[05:20] <alkisg> It all depends on if the nvidia driver plays well or not. All the other in-kernel drivers do respect these settings
[05:20] <alkisg> Unfortunately I don't have nvidia so I wasn't able to test, the last time I was testing all these options
[05:21] <Toadisattva> any reason not just to switch back to mesa and go that route?
[05:21] <Guest8560> alkisg, so this is the grub now GRUB_CMDLINE_LINUX_DEFAULT="quiet splash drm.edid_firmware=VGA-1::edid/1280x1024.bin"
[05:21] <alkisg> 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] <alkisg> Guest8560: right
[05:23] <Toadisattva> sorry yeah I did mean nouveau
[05:25] <ubuntu> alkisg, unfortunately, same issue.
[05:25] <alkisg> Guest8560: btw, do set a nickname, even if it's johndoe; it's easier to remember who we're talking to:  /nick johndoe
[05:25] <alkisg> Is it there in cat /proc/cmdline ?
[05:25] <Toadisattva> just for kicks can you run echo $XDG_SESSION_TYPE in a terminal
[05:25] <Guest616> alkisg, ok.
[05:25] <alkisg> If it's there and it wasn't working, then you'll have to use xrandr or xorg.conf
[05:26] <alkisg> xrandr --addmode VGA-1 1280x1024; xrandr --output VGA-1 --mode 1280x1024
[05:26] <Guest616> 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] <alkisg> *or VGA-0, whatever xorg uses
[05:26] <alkisg> Guest616: that's wrong
[05:26] <alkisg> You have two ::
[05:26] <alkisg> Remove one : and try it again
[05:29] <topcat001> alkisg: if the edid fw load worked there is also a kernel message. I use custom edids for some setups.
[05:29] <alkisg> topcat001: no idea what nvidia does though, they may ignore the kernel edid completely and re-read it themselves
[05:31] <topcat001> right. However, they can at least verify if /sys/class/drm/*/edid is getting the right one
[05:43] <kotgc> test
[05:43] <Toadisattva> check
[05:44] <kotgc> 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] <Toadisattva> real quick just run echo $XDG_SESSION_TYPE and let me know what you get back
[05:45] <kotgc> Toadisattva, x11
[05:45] <Toadisattva> okay so you are on xorg
[05:45] <Toadisattva> just wanted to check
[05:46] <kotgc> Toadisattva, ok
[05:46] <Toadisattva> I noticed it didn't have a size for vga
[05:46] <kotgc> it?
[05:48] <Toadisattva> 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] <Toadisattva> you may have already tried that
[05:48] <Toadisattva> the xrandr readout didn't have a size for the vga*
[05:49] <alkisg> kotgc: xrandr --addmode VGA-0 1280x1024; xrandr --output VGA-0 --mode 1280x1024
[05:51] <kotgc> alkisg, https://dpaste.org/FXc0i
[05:52] <alkisg> kotgc: you mistyped, 0124
[05:52] <kotgc> alkisg, https://dpaste.org/Nx7N0
[05:53] <alkisg> kotgc: output of: xrandr | nc termbin.com 9999
[05:53] <kotgc> alkisg, https://termbin.com/f4px
[05:54] <alkisg> kotgc: and do you have an /etc/X11/xorg.conf file?
[05:54] <bblinky1> 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] <alkisg> (if so, pastebin it)
[05:55] <bblinky1> How do I upgrade them?
[05:55] <bblinky1> They seem to have some dependency loop keeping them from being upgradable
[05:56] <kotgc> No, only an empty directory /etc/X11/xorg.conf.d.
[05:56] <alkisg> OK, then we go to the last resort, let's see if nvidia will respect a xorg.conf, let me prepare one...
[05:57] <bblinky1> nvidia, respecting things?
[05:57] <bblinky1> :p
[05:59] <alkisg> kotgc: output of this please: xrandr --verbose | nc termbin.com 9999
[05:59] <alkisg> bblinky1: true, it's really not cooperative :) Can you pastebin the whole terminal output of a `sudo apt full-upgrade` ?
[05:59] <kotgc> alkisg, https://termbin.com/2dsq
[06:00] <bblinky1> alkisg: will you be ok with the output of nala in place of apt?
[06:00] <kotgc> bblinky1, https://www.youtube.com/watch?v=IVpOyKCNZYw&ab_channel=JimFeig  I'm starting to understand now.
[06:04] <bblinky1> alkisg: https://pastebin.pl/view/76472fb5
[06:06] <alkisg> kotgc: sudo wget https://termbin.com/bifq -O /etc/X11/xorg.conf
[06:06] <alkisg> kotgc: if it has problems booting, go to recovery console and: sudo rm /etc/X11/xorg.conf
[06:06] <Toadisattva> there it is
[06:07] <bblinky1> kotgc: indeed nvidia gives 0 shards about consumer linux drivers
[06:07] <alkisg> bblinky1: I think that's just phased updates you're seeing, https://wiki.ubuntu.com/PhasedUpdates
[06:08] <bblinky1> alkisg: ok... So I should basically just let it be?
[06:08] <alkisg> bblinky1: yes
[06:08] <bblinky1> Cool, thanks
[06:09] <bblinky1> Didn't even know about this "phased updates" feature of ubuntu
[06:09] <lotuspsychje> !phasedupdates | bblinky1
[06:09] <bblinky1> cool
[06:09] <bblinky1> I wonder how this makes sense on glib..
[06:10] <bblinky1> But I suppose it's some expanssion of the testing repo?
[06:12] <bblinky1> Ah, it's all in the link
[06:12] <bblinky1> Thanks
[06:16] <kotgc> test
[06:16] <kotgc> alkisg, I think I did it right, but same issue? https://dpaste.org/rRQdf
[06:17] <alkisg> jkotra: xrandr | nc termbin.com 9999
[06:22] <alkisg> Sorry, I meant kotgc ^
[06:23] <kotgc> alkisg, https://termbin.com/mxpl
[06:25] <alkisg> kotgc: well, we tried our best. Revert everything, then try to switch to nouveau :D
[06:26] <kotgc> alkisg, thank you.  I'll research what nouveau is.
[06:43] <lotuspsychje> !nouveau | kotgc
[06:46] <l88l> 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] <l88l> i know windows needs ntfs and another partion but will install windows first and then linux ubuntu after
[06:47] <guiverc> 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] <l88l> no uefi
[06:48] <guiverc> 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] <guiverc> 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] <l88l> ty
[08:43] <erle-> where does dkms or nvidia driver (packaged by Ubuntu) put the secure boot keys?
[08:43] <erle-> my bios forgot them
[08:44] <erle-> I want to reimport them
[08:44] <paul424> All I can ask is someone prepeare the libOIS in version 1.5.1 and put it into repository
[08:44] <paul424> 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] <paul424> The people using my snap will be upgraded to buggy, useless piece of software , great !
[08:50] <lotuspsychje> paul424: ravage already answered you about that issue yesterday?
[08:50] <paul424> partly
[08:51] <paul424> why someone cannot prepare a new version of libOIS and put it into repos ?
[09:14] <bblinky> Is there any integration for self encrypting nvme drives?
[09:24] <ravage> paul424, in a snap a lib outside snap will not help you anyway
[09:24] <ravage> the creator of that snap has to add that to the snap
[09:34] <dreamcat4> so how is the new 23.04 releaese like then?
[09:34] <dreamcat4> good / bad?
[09:35] <lotuspsychje> !discuss | dreamcat4
[09:35] <dreamcat4> ah sorry
[09:51] <ice9> how to remove bluetooth module, I tried with `modprop -r` but I get: modprobe: FATAL: Module bluetooth is in use
[09:53] <koffeinfriedhof> ice9: You have to stop the systemd bluetooth.service first
[09:53] <koffeinfriedhof> (and disable it if you do not want to autostart it)
[10:11] <paul424> ravage, I am the creator, I administer the opendungeons-plus as well develop it :D !!!!
[10:12] <ravage> then just compile the lib in your snap
[10:12] <ravage> as a part
[10:12] <ravage> you can find the staging libs required from the existing package
[10:13] <paul424> ravage, MAN , that's what I DO
[10:13] <paul424> but it doesn't work for some reason
[10:13] <paul424> after I moved to core 20 from core 18
[10:13] <ravage> why would you do that
[10:13] <paul424> ravage, https://pastebin.com/gR57Dp9v
[10:13] <ravage> i would better move to 22
[10:14] <paul424> ravage, hmm I needed the pybind11 which is availaible in core20 and core22
[10:14] <ravage> i can have a look at that snap adter lunch
[10:14] <paul424> ravage, oki that would be supper
[10:14] <paul424> ravage, naahh I hang around on many channel but not on #ubuntu and #snappy on regular basis
[10:15] <paul424> yeap autojoin to #ubuntu added :D
[10:56] <yes-ubuntu> 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] <yes-ubuntu> information either? Is this how stuff supposed to be under Linux?
[10:57] <ikonia> yes-ubuntu: what's the actual question, I'm not quite understanding
[11:00] <yes-ubuntu> 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] <yes-ubuntu> kill...
[11:05] <ikonia> yes-ubuntu: snap store is a snap that presents the interface to download naps
[11:05] <ikonia> snaps
[11:05] <ikonia> the next part is a command argument
[11:06] <ikonia> not sure why you want to kill it
[11:06] <ikonia> it will auto update when there is a newer version
[11:06] <ikonia> if you don't want the snap store, just stop it or remove the snap
[11:07] <yes-ubuntu> 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] <yes-ubuntu> 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] <ikonia> I'd imagine look at the man page of snap, or the snap documentation
[11:08] <ikonia> it's basically saying 'run this as an application'
[11:09] <ikonia> here is a useful post on how to terminate correctly the snap store to allow it to update
[11:09] <ikonia> https://discourse.ubuntu.com/t/how-to-close-the-snap-store-to-allow-snapd-to-update-it/30627/2
[11:10] <ikonia> looks like because it's launched as an app that it stays running even after the app is closed
[11:10] <ikonia> (I didn't know that)
[11:13] <yes-ubuntu> 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] <ikonia> it's an argument for gnome desktop integration
[11:21] <ikonia> it's not actually part of the snap
[11:56] <AMDavid> 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] <AMDavid> 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] <tarzeau> AMDavid: no logfiles? verbose mode? debug mode?
[11:59] <tarzeau> AMDavid: can you put your dumps and strace outputs online and refer url to it?
[11:59] <tarzeau> well yes not much appears to have happened since 2015: https://sourceforge.net/p/ptpd/code/HEAD/tree/
[12:01] <tarzeau> oh appears there's also: https://github.com/ptpd/ptpd
[12:02] <tarzeau> AMDavid: any reason you don't use NTP?
[12:03] <AMDavid> 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] <AMDavid> dumps and strace file: https://s3.amazonaws.com/dcc_stuff/ptpd_not_responding.tar
[12:11] <UBERMENSCH_57> hello
[12:12] <UBERMENSCH_57> greetings from Brazil
[12:13] <UBERMENSCH_57> hello mauro_melfi
[12:13] <mauro_melfi> Hello, good mornig
[12:13] <UBERMENSCH_57> good morning
[12:14] <UBERMENSCH_57> where are you from? I'm Brazilian
[12:14] <mauro_melfi> 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] <mauro_melfi> i'm from italy
[12:14] <tarzeau> mauro_melfi: pulseaudio -k didn't help (as user)?
[12:14] <UBERMENSCH_57> have you searched your computer audio Drive?
[12:15] <tarzeau> 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] <tarzeau> AMDavid: what hw exactly you run your arm64 stuff on?
[12:17] <mauro_melfi> pulseaudio -k didn't help :(
[12:17] <tarzeau> 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] <tarzeau> AMDavid: i was able to locate the problem, it's right in there:
[12:19] <tarzeau>         /* do the protocol engine */
[12:19] <tarzeau>         protocol(&rtOpts, ptpClock);
[12:19] <tarzeau>         /* forever loop.. */
[12:19] <tarzeau> ;)
[12:29] <AMDavid> 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] <AMDavid> is likely the norm. I'm wondering intermittent wifi network issues are triggering an issue with the ptpd code.
[12:32] <tarzeau> over wifi? and wifi is good?
[12:34] <tarzeau> 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] <tarzeau> unfortunately i never got my hands on the jetson from nvidia (they had that phase years ago to get a devel board)
[12:35] <AMDavid> 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] <AMDavid> I mean, PTPd on wifi works better than NTPd does on wifi - better granularity.
[12:36] <tarzeau> i got that, yes
[12:45] <ogra> AMDavid, please seek nvidia support, these images are highly hacked and modified by nvidia and not even remotely ubuntu ...
[12:46] <ogra> (note that there is work going on between nvidia and canonical to eventually support jetson orin and onwards sepcifically because nvidia noticed they can not support their own hacks)
[12:49] <tarzeau> ogra: details on that work? the orin fits where in this list? https://wiki.debian.org/InstallingDebianOn/NVIDIA/
[12:49] <tarzeau> ogra: where can i see details on their hacks?
[12:50] <ogra> tarzeau, no idea if they are documented at all, but nvidias L4T stuff falls in the same category as popos or linuxmint in this channel ... it is heavily modified and/or used a self breeded kernel with non-ubuntu config and missing (security) patches
[12:51] <ogra> s/used/uses
[12:51] <ogra> see the channel topic part about "unofficial derivatives" ....
[12:52] <tarzeau> will there ever be an update on https://ubuntu.com/desktop/statistics ?
[12:52] <ogra> if someone does such a research again, it will surely be published ...
[12:53] <tarzeau> ogra: ubuntu/canonical has plenty places they actively collect telemetry...
[12:54] <ogra> (not sure if in times of snaps where you get that data super detailed as a snap publisher, there will be seen a need for a broader research though)
[12:54] <BCB> I lost ssh connection during an update/upgrate and upon logging back in i'm getting "Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 49900 (apt-get)"  Any thoughts...  Thank you.
[12:55] <tarzeau> ogra: i have no idea what you're talking about when you say times of snaps. when i google images snaps, i can see a lot of schnaps (high alcoholic drinks)
[12:55] <tarzeau> BCB: pkill -9 dpkg; pkill -9 apt; apt upgrade, and it'll give you a command to copy paste
[12:55] <ogra> BCB, i'D wait and see if the process finishes ... if you have bad luck it might sit with some interactive prompt trying to talk to yur former session though
[12:55] <ogra> if it does not finish after a while, go with wht tarzeau suggested
[12:55] <ogra> *what
[12:56] <ogra> tarzeau, lol ...
[12:56] <tarzeau> ogra: remember that omgubuntu like webpages, first thing to do on ubuntu? here's mine: https://github.com/alexmyczko/autoexec.bat/blob/master/config.sys/ubuntu-remove-snap-firefox
[12:57] <ogra> tarzeau, when you publish a snap you get very detailed (anonymous) user data about where your users are, how many they are (even brken down by region), what distros they use etc etc
[12:57] <tarzeau> i get the same for publishing debs with popcon (from debian), and also from running an official mirror (visitor stats). and then there's hw-probe
[12:57] <ogra> tarzeau, well, up to the users indeed, but snaps are an integral part of ubuntu after existing for nearly a decade now ...
[12:58] <tarzeau> ogra: i've never seen a snap user, and i've been doing linux workstations since 1999
[12:58] <oerheks> here is a snap user..
[12:58] <oerheks> lolz
[12:58] <ogra> tnen you have not managed ubuntu systms for the last years ?
[12:58] <tarzeau> ogra: 350 machines for thousands of users, since 18 years
[12:59] <BCB> tarzeau I don't want to BREAK anyting...
[12:59] <BCB> ogra how can I monitor the process?
[12:59] <ogra> BCB, top or htop might help to see if it is still running and when it stops
[12:59] <tarzeau> you actually said the keyword: manage and management. snaps are not enterprise ready
[13:00] <BluesKaj> Hi all
[13:00] <ogra> tarzeau, LOL !!!!!
[13:00] <ogra> tarzeau, note that the majority of snap users are enterprises 🙂
[13:00] <ogra> at least in the commercial area
[13:00] <oerheks> snap haters should move to mint
[13:00] <tarzeau> ogra: certainly not in academic field, or in HPC area
[13:00] <tarzeau> oerheks: i'm not hating it, i'm just not using it, and i can't recommend it either
[13:01] <ogra> yeah, i wouldnt see tarzeau as a hater here ...
[13:01] <ogra> though i notice that we should probably move to #ubuntu-discuss with this
[13:01] <oerheks> oke, haters is a little too strong
[13:01] <BCB> tarzeau ogra connection dropped on one of the interactive screens??  Might still be "waiting" for my input??
[13:01] <ogra> we're getting slightly offtopic for the support channel
[13:02] <ogra> BCB, it could, yeah
[13:02] <ogra> BCB, but even if you kill it yu should always be able to recover
[13:03] <ogra> i'd just give it some ime in case it does not sit there and wait for input
[13:03] <ogra> *time
[13:03] <BCB> ogra FYI: "Be aware that removing the lock file is not a solution and may break your system."
[13:03] <ogra> yeah
[13:03] <ogra> lock files exist for a reason and are usually bound to a process doing something
[13:03] <oerheks> when locked, i would wait a minute or 2..
[13:03] <BCB> ok
[13:04] <BCB> or should I REBOOT?
[13:04] <oerheks> only when /var/run/reboot-required exists
[13:05] <tarzeau> BCB: i've written you the solution. i don't know why you have the impression it would BREAK anything?
[13:06] <AMDavid> ogra Thanks, that's interesting/useful feedback re: nvidia.  I had not previously thought of it as unoffical as it's using the Ubuntu offical repos, but as the kernel Nvidia want you to run is not offical Ubuntu then I get what you mean.
[13:08] <ogra> AMDavid, right, lmint and popos use the ubuntu repos too ... but come with a completely differently configured OS install, different kernel (popos) and even PPA overlays (also popos)
[13:08] <ogra> the same is true for the nvidia images ... they even use their own image creation tool that is incompatible with ubuntus
[13:24] <paul424> ravage: hello,helllo have you read the my snapcraft.yaml file already   ?
[13:26] <ravage> paul424, https://termbin.com/5nj3 that builds and runs
[13:26] <ravage> thros some log spam on the console
[13:26] <ravage> but im sure you can fix that
[13:27] <paul424> ravage: so what have you changed that it runs ?
[13:28] <ravage> basically i added the cmake prefix vars
[13:28] <ravage> the lib per default installs to /usr/local
[13:28] <ravage> and it could not be found there
[13:31] <ptblr-1236> hi
[13:33] <paul424> ravage: oki many many thanks , you are a genious! I cannot check it by now, because I don't have  the github key on that machine >_>
[13:33] <paul424> will try asap I go home
[13:39] <BCB> tarzeau: how do I find the process to kill?
[13:40] <BCB> tarzeau: https://paste.ubuntu.com/p/NRNFQJk7pB/plain/
[13:40] <tarzeau> BCB: you don't have to. just carefully read again what i wrote and follow it right
[13:40] <tarzeau> BCB: if you're unsure about commands. try man on it
[13:45] <BCB>  tarzeau got it!  i did not notice the multiple cmds you wrote.  Looked like it finished the up grade in the back ground then after killing the process it asked me to re run the interactive commands.  All good now.  Thank you!
[14:00] <meta-coder> Is Netplan a replacement for NetworkManager?
[14:02] <leftyfb> meta-coder: what is your issue exactly?
[14:04] <meta-coder> leftyfb: I think doesn't replace NM, but provides an abstraction layer over it?
[14:05] <leftyfb> meta-coder: netplan is the CLI renderer. But on Ubuntu desktop, it just refers to Network Manager for the configs. What exactly are you trying to accomplish?
[14:05] <meta-coder> Ok
[14:06] <leftyfb> meta-coder: did you need help with something or are you just trying to understand the netplan/nm relationship just for personal knowledge?
[14:06] <meta-coder> I am asking because, on 20.04 Netplan is installed, but I don't need to use it; Network Manager does the job for me.
[14:07] <leftyfb> meta-coder: you need to leave netplan there
[14:07] <leftyfb> meta-coder: do you have a reason why you think you need to remove it?
[14:08] <meta-coder> leftyfb: Ok. Thought it might conflict with Network Manager...
[14:08] <leftyfb> it doesn't
[14:08] <leftyfb> meta-coder: are you having network issues?
[14:09] <meta-coder> No
[14:10] <meta-coder> There is a bug in Network Manager though, but it is fixed in newer version.
[14:10] <leftyfb> meta-coder: which bug?
[14:11] <meta-coder> On IPv6, the default route disappears after some time.
[14:11] <leftyfb> meta-coder: it might be fixed in Ubuntu 22.04. You might consider upgrading to that.
[14:12] <meta-coder> Or, I was expecting to find newer Network Manager in backports, but it isn't there.
[14:13] <oerheks> That was an old bug, already patched in versions before 1.32
[14:13] <meta-coder> leftyfb: https://bugzilla.redhat.com/show_bug.cgi?id=2004212
[14:13] -ubottu:#ubuntu- bugzilla.redhat.com bug 2004212 in Red Hat Enterprise Linux 8 "IPv6 Default gateway deleted from routing table" [Urgent, Closed: Errata]
[14:13] <meta-coder> oerheks: you know about it?
[14:13] <leftyfb> oerheks: yeah, ubuntu 20.04 is still on nm 1.22
[14:14] <oerheks> it says in your redhat bugreport, and see the packages and changelogs on https://launchpad.net/ubuntu/+source/network-manager
[14:14] <oerheks> leftyfb, patched
[14:14] <leftyfb> are you sure?
[14:15] <leftyfb> oerheks: I only see "platform: workaround for preserving IPv6 address order" referring to ipv6
[14:17] <oerheks> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1967626
[14:17] -ubottu:#ubuntu- Launchpad bug 1967626 in network-manager (Ubuntu) "22.04 beta Network Manager still sets wrong IPv6 routing" [Low, Confirmed]
[14:17] <meta-coder> It is patched in NetworkManager 1.32.10. But Focal Fossa is on version 1.22.10-1ubuntu2.3 of Network Manager.
[14:18] <oerheks> affected package 1.22.10-1ubuntu2.2
[14:28] <Moosems> Could I get some help with installking Ubuntu 22.04? The guide is missing error messages and I can't find much online about my issue
[14:31] <Moosems> Right after pressing continue from installation type (I chose normal installation) it brings up an empty partition table that I'm struggling to format correctly
[14:32] <leftyfb> Moosems: can you take a picture of it and post to imgur.com?
[14:32] <Moosems> I can't access imgur on this wifi but can use imgbb.com, does that also work?
[14:32] <leftyfb> sure
[14:33] <Moosems> https://ibb.co/Y34fynD
[14:34] <leftyfb> Moosems: can I ask, what's wrong with just using the guided partition layout option?
[14:34] <Moosems> NOTE: it also requires an EIFI partition
[14:34] <Moosems> leftyfb: ?
[14:34] <leftyfb> hit back
[14:35] <leftyfb> then what options do you see?
[14:36] <Moosems> Back gives the following: https://ibb.co/X8BJqYt
[14:36] <akik> Moosems: there's nothing wrong in that picture you sent. you use the + sign to add partitions
[14:36] <leftyfb> akik: you shouldn't have to manually create partitions
[14:36] <oerheks> Mantic Minotaur
[14:36] <Moosems> akik: Which ones? Thats the issue, I have no idea what to add
[14:37] <leftyfb> oerheks: ?
[14:37] <akik> leftyfb: that's how it works
[14:37] <leftyfb> akik: incorrect. There's always been a guided mode which does it all for you
[14:38] <akik> leftyfb: there's nothing incorrect in what i said. the manual partitioning works like that
[14:38] <Moosems> akik: https://ubuntu.com/tutorials/install-ubuntu-desktop#6-type-of-installation
[14:39] <Moosems> That page never showed up
[14:39] <leftyfb> Moosems: right, you want the "Erase disk and install ubuntu"
[14:39] <Moosems> Yep. But how do I do that if it never comes up?
[14:40] <leftyfb> Moosems: wait, are you booted from that Sandisk 55AE?
[14:40] <leftyfb> Moosems: if so, it looks like it's not detecting the hard drive in your pc
[14:41] <Moosems> Yes
[14:41] <Moosems> I just took a video I'll make a link for
[14:41] <leftyfb> Moosems: what type of pc is this? desktop? laptop? other?
[14:41] <Moosems> 2013 Dell Inspiron Desktop
[14:41] <leftyfb> Moosems: we know the first problem to solve, it's not seeing your hard drive
[14:41] <leftyfb> Moosems: ok, go into the bios and look for RAID and disable it
[14:42] <Moosems> So reboot, and F2?
[14:42] <oerheks> and check for a bios update
[14:42] <leftyfb> set it to AHCI
[14:42] <leftyfb> Moosems: yes
[14:42] <tweak> hey~ having 2 keyboard issues on my hp laptop. first one, light does not work on audio mute key. second one, depite selecting numblock to be on in ssdm, it does not turn on autmatically
[14:42] <Moosems> BIOS is open
[14:43] <leftyfb> Moosems: you'll need to search around for the RAID setting
[14:43] <Moosems> leftyb: I'll look through all the settings and come back with what I find
[14:43] <MrBurns> Also make sure that the drive is detected in bios
[14:44] <oerheks> fastboot disabled ..
[14:44] <leftyfb> Moosems: d oyou have Windows installed on this drive?
[14:44] <Moosems> Are there any other names that might be used for RAID?
[14:45] <tweak> another issue i'm having, using refind bootloader, I cannot get it to access my vmlinux. I can get it to recognize grubx64.efi, but not the vmlinuz in /boot despite having the ext4 driver inside the drivers_x64 directory in /boot/efi/EFI/refind/drivers_x64/
[14:45] <tweak> secure boot on
[14:45] <Moosems> leftyb: I'm not sure what's on it. I assume theres nothing useful on here. It won't load anything when the computer is turned on, rather brings up reset or BIOS options
[14:45] <akik> Moosems: you didn'y say anything initially about a missing storage device..
[14:46] <leftyfb> Moosems: it's possible it's not detecting your hard drive
[14:46] <Moosems> SATA mode was AHCI, should it be ATA?
[14:46] <leftyfb> AHCI is fine
[14:46] <Moosems> It has a hard drive, just nothing on it
[14:46] <leftyfb> Moosems: do you see it detected in your BIOS?
[14:47] <Moosems> No.
[14:47] <leftyfb> Moosems: That is step #1 and unrelated to Ubuntu. You might seek support in #hardware
[14:48] <oerheks> i see you have a sandisk extreme 55ae ... from your 1st screenshot. probably fastboot disrupting
[14:48] <leftyfb> oerheks: that's a portable drive they're booting the live iso from
[14:48] <Moosems> Well now it notices the drive but says its 0 GB even though its 1 TB
[14:49] <leftyfb> Moosems: your BIOS might be too old. Look for an update
[14:49] <Moosems> #Hardware is where i'd find where to find the update??
[14:50] <leftyfb> Moosems: they might be able to help you get your pc to recognize the hard drive
[14:50] <Moosems> BIOS Revision: A05
[14:50] <Moosems> leftyb: I'll be loking both here and there then
[14:50] <leftyfb> Moosems: good luck
[14:51] <hsiktas[m]> does Ubuntu Pro do anything on a non-LTS release? I upgraded from 22.04 with Ubuntu Pro activated to 22.10 and now 23.04, and it seems like it is still listed as "Active machine" under my free personal token
[14:51] <leftyfb> hsiktas[m]: pretty sure pro doesn't work on non-LTS
[14:52] <oerheks> hsiktas[m], no, ESM and now PRO is LTS only?
[14:52] <leftyfb> ESM has only ever been LTS
[15:08] <hsiktas[m]> I just added Pro on an other machine and I got e.g. this update over ESM: https://packages.ubuntu.com/jammy/imagemagick-6-common On packages.ubuntu.com, can I somehow see which updates are subscripber-only?
[15:10] <oerheks> Previously Ubuntu did not provide security patches for "Universe" repo packages (instead relying on upstream patches to happen when they happen).
[15:10] <oerheks> from https://askubuntu.com/questions/1452299/im-getting-the-message-the-following-security-updates-require-ubuntu-pro-with
[15:11] <oerheks> so, universe packages under PRO are now under active maintaining
[15:39] <tweak> hi. issue i'm having, using refind bootloader, I cannot get it to access my vmlinux. I can get it to recognize grubx64.efi, but not the vmlinuz in /boot despite having the ext4 driver inside the drivers_x64 directory in /boot/efi/EFI/refind/drivers_x64/
[15:46] <bblinky> If I purge snap does it also remove all the snap packages ?
[15:48] <oerheks> See what happens if you try? i bet the ~/snap  folder remains in your HOME
[15:50] <paul424> ravage, yeah everything works fine with opendungeons-plus, I thank you once more
[15:50] <ravage> great :)
[15:50] <jhutchins> tweak: This is just a wild guess, but it couldn't hurt.  A lot of systems put a symlink to /boot/vmlinuz in /
[15:50] <bblinky> Removing snap firefox and revision 2356
[15:50] <bblinky> rm: cannot remove '/var/snap/firefox/common/host-hunspell/en_US.aff': Read-only
[15:50] <bblinky> file system
[15:50] <bblinky> rm: cannot remove '/var/snap/firefox/common/host-hunspell/en_US.dic': Read-only
[15:50] <bblinky> file system
[15:50] <bblinky> dpkg: error processing package snapd (--purge):
[15:50] <jhutchins> tweak: Ubuntu may already do that.
[15:52] <bblinky> Sry for spam
[15:53] <tweak> jhutchins: thank you, i will look up how to add a symlink ^^
[15:54] <bblinky> ln -s
[15:56] <tomreyn> bblinky: https://forum.snapcraft.io/t/unlinkat-var-snap-firefox-common-host-hunspell-en-us-aff-read-only-file-system/34022/5 (looks like a snapd bug to me.)
[15:57] <bblinky> lol
[15:58] <bblinky> Hmm, I guess I shall embrace the snappyness of canonical since i chose to install ubuntu
[15:58] <bblinky> for now
[16:00] <tweak> oh also, having 2 keyboard issues on my hp laptop. first one, light does not work on audio mute key. second one, depite selecting numblock to be on in keyboard settings, it does not turn on autmatically for ssdm time
[16:02] <tomreyn> äkubuntu is indeed the best place to ask kubuntu specific questions. that's it if you are running kubuntu, and a supported version of it.
[16:14] <jhutchins> tweak: On a BIOS system there's usually a numlock setting.  No idea about UEFI.
[16:18] <tweak> jhutchins: i'll check that thank you
[16:18] <jhutchins> tweak: That's one of those things that's sort of in the grey area between hardware and OS.
[17:04] <tweak> jhutchins: nope no luck ;p
[17:35] <jhutchins> tweak: Oh well.  Worth a shot.
[17:37] <hsiktas[m]> In Wayland on the Firefox Snap, shouldn't two finger swipes for back or forward work already? Apparently, this was added to Firefox last year.
[17:40] <jhutchins> hsiktas[m]: Does the LTS package have the same problem
[17:41] <hsiktas[m]> isn't the Snap the same on all Ubuntu releases?
[17:42] <jhutchins> hsiktas[m]: Since snaps aren't tied to releases I would expect that the current snap would be the same.  I don't know that's true though.
[17:43] <leftyfb> hsiktas[m]: it is
[17:54] <hsiktas[m]> it seems like Firefox supports this via Wayland, but the Snap hasn't enabled that yet
[17:54] <hsiktas[m]> https://bugzilla.mozilla.org/show_bug.cgi?id=1725245
[17:54] -ubottu:#ubuntu- Mozilla bug 1725245 in Testing "Add Ubuntu 22.04 as a test platform to run tests for MOZ_ENABLE_WAYLAND=1" [--, New]
[17:55] <hsiktas[m]> another missing feature due to snap :)
[18:01] <Macwinner> I'm having some weird mongodb crashes.  at almost the same exact time I'm seeing these messages in dmesg:  "[Fri Apr 28 08:58:34 2023] xfs filesystem being remounted at /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff)"
[18:02] <Macwinner> there are about 8 other messages like that for different mounts..
[18:02] <Macwinner> what could be causing the xfs filesystem to be remounted?
[18:34] <tomreyn> Macwinner: which ubuntu version (lsb_release -ds) is this? which kernel (cat /proc/version)? is some other service starting up or shutting down at the time the message you quoted is logged?
[18:35] <Macwinner> Ubuntu 22.04.2 LTS
[18:35] <Macwinner> Linux version 5.15.0-71-generic (buildd@lcy02-amd64-044) (gcc (Ubuntu 11.3.0-1ubuntu1~22.04.1) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #78-Ubuntu SMP Tue Apr 18 09:00:29 UTC 2023
[18:36] <Macwinner> tomreyn: I don't believe any other services is starting or shutting down..  i'm wondering if maybe this is red herring and systemd is remounting stuff after the mongod core dump?
[18:37] <tomreyn> possibly. all i have to work is one line of log without much contextual info.
[18:37] <tomreyn> *with
[18:38] <tomreyn> and other than that remount happening, this message is not really important for the next decade.
[18:39] <Macwinner> yeah.. just not sure why a remount would happen
[18:39] <Macwinner> it would seem bad to remount a fileysstem if mongodb needs constant access to it
[18:39] <Macwinner> would systemd-coredump remount xfs if it detected a coredump?
[18:42] <tomreyn> i wouldn't know, haven't used it
[18:42] <tomreyn> https://github.com/systemd/systemd/issues/21010 looks like it may have an answer to some of your questions
[18:42] -ubottu:#ubuntu- Issue 21010 in systemd/systemd "Systemd frequently remounts filesystem for some reason (???)" [Closed]
[18:44] <tomreyn> but more log context may show that this is actually an entirely different issue
[18:50] <Macwinner> tomreyn: let me see what else we got.. there isn't other context really before those lines
[18:53] <tomreyn> Macwinner: you're using the mongodb packages of ubuntu 22.04, right?
[18:55] <Macwinner> tomreyn: yeah.. from the mongodb official repo
[18:56] <Macwinner> or do you mean default ubuntu mongodb?   I don't think so since we are using mongodb 6.0.5
[18:56] <Macwinner> just reading through that ticket you mentioned..
[18:56] <tomreyn> oh, well then you should check with mongodb on their builds, since that's what's crashing.
[18:58] <Macwinner> yeah.. talking to them as well in parallel :)
[19:16] <jack1> I have to say: Ubuntu 22.04 is the icing on the cake. I loaded it on all 4 machines and zero problems.. fabulous job people.
[19:19] <jack1> Ubuntu/Mate
[19:20] <jack1> Last time that happened was 7.04
[19:22] <chonkin> Alright it is me again. I have another machine that is freezing on boot.
[19:22] <chonkin> Grub, e,  nomodeset_  is not working this time.  I'm locked at the command line.   How do I proceed with troubleshoot?
[19:26] <tomreyn> chonkin: is this before or after installation?
[19:26] <tomreyn> what's the hardware, how much ram, which ubuntu versin are you using?
[19:49] <chonkin> tomreyn   hardware is intel desktop.  GPU RTX 3090.  Ubuntu = 5.15.0-71-generic.  20.04.5 LTS.  KDE envrionment.   The computer was working fine for several days.   Just today I was installing matlab.  the nvidia-smi was working and showing the hardware.  When I rebooted this afternoon it was frozen.
[19:50] <tomreyn> chonkin: so you're saying it was frozen and that prompted you to reboot, or you rebooted and that triggered it to freeze?
[19:50] <chonkin> tomreyn : it is freezing during booting
[19:51] <chonkin> i rebooted on purpose to try to set an environment variable in profile.d
[19:51] <tomreyn> so it freezes on the grub command line, or does "freeze" just refer to the fact that you get to see the grub command line?
[19:54] <chonkin> I can see some output from the command line prior to freezing. The last thing that appears is,
[19:54] <chonkin> [   3.194506] proc_thermal_pci 0000:00:04.0: error: proc_thermal_add, will continue
[19:55] <chonkin> the cursor then blinks forever
[19:56] <tomreyn> is 0000:00:04.0 the nvidia card then?
[19:56] <tomreyn> you could tell when booting from a live / installer system and run lspci
[19:57] <tomreyn> are you using nvidia drivers provided by ubuntu?
[19:58] <chonkin> sorry.  I meant to say that that is the last line that appears on the screen.  There are likely more lines of output occurring in journalctl which I am examining now
[19:59] <tomreyn> based on what i read you should be using nvidia-driver-470 with this card.
[19:59] <ioria> chonkin, try to disable secure boot temporarily
[19:59] <chonkin> 0000:00:04.0 Signal processing controller: Intel Corporation Device 461d (rev 02)
[19:59] <tomreyn> (or newer)
[20:06] <chonkin> [3:59:40 pm] <tomreyn> based on what i read you should be using nvidia-driver-470 with this card.
[20:07] <chonkin> My usual reasoning is the driver number must match the kernel exactly.   So for 5.15.0-71-generic   the corresponding driver is nvidia-driver-515
[20:09] <tomreyn> the kernel message you quoted above indicates that the in-cpu temperature sensor driver failed to initialize, but it seems non-serious. according to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934741 the generic focal (20.04) kernel won't see a patch to support it. but chances are that 22.04 has it.
[20:09] -ubottu:#ubuntu- Launchpad bug 1934741 in linux (Ubuntu) "Add new PCI MMIO based thermal driver [8086:461d] for Intel Alder Lake" [High, In Progress]
[20:10] <tomreyn> i'm not aware of a relation between nvidia driver series and kernel versions, but i could be wrong.
[20:12] <oerheks> hmm, nvidia says 510 https://www.nvidia.com/download/driverResults.aspx/187162/en-us/
[20:12] <oerheks> for https://www.nvidia.com/download/driverResults.aspx/187162/en-us/
[20:12] <oerheks> err for RTX 3090 Ti
[20:14] <tomreyn> use that then, not i added "(or newer)" above
[20:14] <tomreyn> *notE
[20:14] <oehman>  I would go for 525
[20:16] <chonkin> http://paste.debian.net/1278811
[20:16] <oerheks> go wild, 530?
[20:18] <chonkin> oerheks , what if I wanted to go less wild?
[20:19] <oerheks> at least 510,,
[20:22] <chonkin> http://paste.debian.net/1278813
[20:26] <chonkin> im going to try 530.  Should I also install dkms-530?
[20:35] <jhutchins> I would note that the OEM nvidia drivers, which are the source for the Ubuntu drivers, each have a list of which specific cards they support.  Just installing the newest one does not guarantee that an older card will be supported.
[20:37] <tarzeau> jhutchins: i confirm.
[20:37] <tarzeau> jhutchins: modinfo nvidia.ko usually lists them pretty exactly, can match with lspci (-n) output
[20:56] <chonkin> ubuntu-drivers list-oem
[20:56] <chonkin> this returns nothing
[20:58] <chonkin> I believe the graphics card in this machine is not supported by ubuntu.  I am will to argue this point in open debate.
[20:58] <chonkin> No portion of this system can even "see" this card
[21:11] <chonkin> I have used Software & Updates  and attempted Apply Changes on a proprietery,tested   nvidia-driver-530-open,  this returned with an error,
[21:11] <chonkin> "Error while applying changes.  pk-client-error-quark : Error while installing package : installed nvidia-dkms-530-open package post installation script subprocess returned error exit status 10 (313)"
[21:15] <chonkin> I have never used "Software & Updates" before.    This is the first time I have used it today.   How do I revert any changes I just made?
[21:15] <chonkin> (i previously only ever used CLI)
[21:28] <ForeverNoob[m]> Hello, is this guide still relevant or does Ubuntu already ship with optimizations for SSD? https://www.howtogeek.com/62761/how-to-tweak-your-ssd-in-ubuntu-for-better-performance/
[21:34] <chonkin> Software&Updates is now frozen during an Apply Changes.   Any ideas?
[21:41] <tomreyn> ForeverNoob[m]: this technology has developed since 2011 (and so has ubuntu), and much if not most of this article is no longer relevant.
[21:42] <ForeverNoob[m]> That's good to hear, thanks.
[21:43] <tomreyn> chonkin: you can revert the "Software & Updates" application to undo the changes you just did using the "Software & Updates" application.
[21:44] <jhutchins> chonkin: Still frozen?
[21:44] <tomreyn> did you already disable secureboot (the first recommendation given to you regarding the 'freeze' issue?)
[21:45] <chonkin> jhutchins:   Yes.   ANd I have been leaving something out.   I have my gcc and g++  set to version 6.x
[21:46] <chonkin> Is there a possibility that this is causing driver installations to fail,  like for example  "Error! Bad return status for module build on kernel: 5.15.0-71-generic (x86_64)"
[21:46] <jhutchins> chonkin: Yes.
[21:46] <chonkin> Okay.  i can fix this very easily actually
[22:02] <chonkin> jhutchins  okay i'm getting this now  http://paste.debian.net/1278822
[22:05] <tomreyn> so apparently you have a "RTX 3070", not a "RTX 3070 Ti". does anything still not work now?
[22:07] <chonkin> tomreyn getting this  https://postimg.cc/bGs4kM0b
[22:07] <tomreyn> this does not look like an error message
[22:18] <bblinky> Can i mark a package to have been installed as a dependency??
[22:18] <rbox> apt-mark
[22:30] <chonkin> alright it looks like this computer is booting now
[22:30] <chonkin> thanks to everyone for listening
[23:40] <ricardol> Hi All! I was wondering if someone could help me with an issue. I am running ubuntu jammy, and i have my pc connected to wavlink usb docking station. I am trying to use the two HDMI ports from the docking station in an extended mode, however, ubuntu just mirrors them. Were should i look into to try and modify this?