[00:38] <regedit> hello
[00:38] <regedit> is there a command to virtually "unplug/replug" an external hard drive so i dont have to do it manually?
[00:40] <LambdaComplex> regedit: eject
[00:40] <LambdaComplex> either that or umount
[00:40] <regedit> and then? how to un-eject right afterwards
[00:40] <LambdaComplex> eject might actually make you have to physically unplug/replug it
[00:40] <regedit> right...
[00:41] <regedit> what is this "unmount", and can i "mount" again afterwards as wasy as unplugging/replugging?
[00:41] <regedit> *easy
[00:59] <croran_44[m]> jerome-: yeah you can set a second IP address for your network interface
[01:09] <jerome-> croran_44[m] but could I use traceroute -s 192.168.1.100 google.com to choose one router or the other?
[01:09] <jerome-> I tried http://pastebin.fr/107876
[01:09] <jerome-> but it doesn't work
[02:04] <bobdobbs> Hi all. I'm trying to get a (new) second monitor working. My system has dual boot. If I boot into windows, then windows picks up the monitor just fine. If I boot into Ubuntu 22.04... no such luck
[02:05] <arraybolt3[m]> bobdobbs: What graphics hardware are you using? Or, better yet, pop open a terminal, run "lspci | nc termbin.com 9999" and send the link it spits out, that will tell me your graphics hardware for sure.
[02:05] <bobdobbs> I'm running an nvidia card. So I opened nvidia-settings from terminal. The program opens, and doesn't give me an option to configure displays. In the terminal itself, I see this: https://www.toptal.com/developers/hastebin/renegirute.less
[02:05] <bobdobbs> arraybolt3[m]: I'm running an RTX 3070ti. I'll your command in a sec...
[02:06] <arraybolt3[m]> regedit: You use the "mount" and "unmount" commands - they are used to give you access to the filesystem on a drive.
[02:07] <arraybolt3[m]> regedit: You can figure out what drives are in your system by running "lsblk" in a terminal. You should be able to recognize your drive based on its size - if not, unplug it, run lsblk, plug it in, run lsblk again, and whatever drives shows up new the second time is most likely your external drive (unless you're suffering a hardware fault).
[02:07] <bobdobbs> arraybolt3[m]: https://termbin.com/o7qb
[02:07] <arraybolt3[m]> bobdobbs: Do you have the proprietary nVidia drivers installed?
[02:08] <arraybolt3[m]> bobdobbs: If you're not sure, run "apt list --installed | grep nvidia | nc termbin.com 9999" and I'll be able to tell from that.
[02:09] <bobdobbs> arraybolt3[m]: I'm afraid I don't know. I remember trying to install the proprietary drivers
[02:09] <bobdobbs> arraybolt3[m]: https://termbin.com/zark
[02:09] <bobdobbs>  
[02:10] <arraybolt3[m]> bobdobbs: Yep, proprietary drivers are installed. Check your monitor configuration - you might just have not enabled the second monitor.
[02:11] <bobdobbs> arraybolt3[m]: what do you mean by 'enabled'?
[02:12] <arraybolt3[m]> bobdobbs: I mean, Linux can choose to use only one monitor, or only the other monitor, or mirror the two, or extend your display across all of them (that's probably what you want to happen). If you open your monitor configuration, you might find that the monitor is detected, but Linux simply isn't using it and you just need to switch it on in your monitor configuration.
[02:14] <bobdobbs> arraybolt3[m]: ah, ok. So usually to configure my monitor set-up, I use the application 'nvidia-settings'. However, when I open it I notice two things: currently it doesn't give me an option to configure monitors. In addition, when I run 'nvidia-settings' from terminal, I see this: https://www.toptal.com/developers/hastebin/renegirute.less
[02:15] <bobdobbs> arraybolt3[m]: sooooo... I suspect that the driver is installed but not enabled.
[02:15] <arraybolt3[m]> Looks like nVidia can't find the X Server, which is to be expected if you're on Ubuntu 22.04, since Ubuntu 22.04 uses Wayland.
[02:15] <jdmark> stock ubuntu 22.04 is quite polished
[02:15] <arraybolt3[m]> Isn't there a monitor configuration tool included within Ubuntu?
[02:15] <arraybolt3[m]> Try using that rather than the nVidia utility.
[02:16] <bobdobbs> I have no idea. I'll google...
[02:16] <arraybolt3[m]> bobdobbs: Try just opening your Application Menu, type "monitor", and click whatever looks like "monitor configuration" or something, that isn't the nVidia utility.
[02:17] <bobdobbs> arraybolt3[m]: ok. If I do that, then I find a sub-panel within the 'settings' panel
[02:18] <arraybolt3[m]> bobdobbs: That sounds about right.
[02:18] <bobdobbs> arraybolt3[m]: In the displays section of the settings panel I can see a options for the monitor that is getting signal. I see no settings options for a second monitory
[02:19] <arraybolt3[m]> bobdobbs: Uh... ok, that's wrong.
[02:19] <arraybolt3[m]> bobdobbs: As in, something has indeed gone glitchy.
[02:19] <bobdobbs> yeeeup
[02:20] <arraybolt3[m]> OK, hold on, I have to go away from keyboard for a sec, I'll be right back.
[02:20] <bobdobbs> sure thing :)
[02:22] <arraybolt3[m]> OK, back.
[02:22] <arraybolt3[m]> Looking for why this might be happening...
[02:23] <arraybolt3[m]> You're on Ubuntu 22.04, right?
[02:23] <bobdobbs> yup
[02:23] <arraybolt3[m]> Or are you still on 20.04?
[02:23] <arraybolt3[m]> OK.
[02:23] <bobdobbs> I'm wondering if I might have some luck if I re-install the proprietary drivers?
[02:23] <arraybolt3[m]> I would NOT do that.
[02:23] <arraybolt3[m]> I have seen at least one guy, maybe more, nuke their system trying that.
[02:24] <bobdobbs> when you say 'nuke'... do you mean actual damage of some kind?
[02:24] <arraybolt3[m]> As in, OS goes totally glitchy, UI disappears, user is left with no recourse but to reinstall Ubuntu entirely (or at least no recourse any of us could figure out).
[02:24] <bobdobbs> oh crap. no way do I want that.
[02:25] <bobdobbs> what about replacing the proprietary driver with the open-source alternative? And maybe then switching back over?
[02:25] <arraybolt3[m]> I've successfully done that, but you won't like the graphics performance very much.
[02:26] <arraybolt3[m]> Nouveau only gives 2D acceleration in most instances, which is kind of a waste of a 3070 Ti.
[02:26] <bobdobbs> ah, ok
[02:26] <arraybolt3[m]> I'mma try to figure out why the driver isn't working right and see if there's a solution.
[02:27] <enigma9o7[m]> I bet it'll all work fine if you login to an X session.
[02:27] <arraybolt3[m]> bobdobbs: OK, this is kind of a messy solution, but someone figured it out here: https://forums.developer.nvidia.com/t/external-monitor-issue-on-ubuntu-22-04-jammy-using-nvidia-510-and-470-proprietary-drivers/214152
[02:27] <bobdobbs> k, checking it out...
[02:29] <arraybolt3[m]> enigma9o7: You may be right. nVidia and Wayland have historically been grumpy when you put them together, but they supposedly fixed that in 22.04. Guess it's still not quite fixed yet.
[02:29] <enigma9o7[m]> Hmmm I thought the opposite, I thought wayland was disabled by default for nvidia.
[02:30] <bobdobbs> Last time I checked I wasn't using wayland
[02:30] <enigma9o7[m]> But I thought it was related to sleep issues, not multiple displays.
[02:30] <arraybolt3[m]> enigma9o7: Used to be, but just recently something changed (I don't know if nVidia's drivers got better or Wayland got better), and now Ubuntu uses Wayland even with nVIdia.
[02:30] <enigma9o7[m]> Okay, then that means you should be able to use xrandr for some command line troublehsooting at least.
[02:31] <enigma9o7[m]> see if the display is even detected, and able to enable it
[02:31] <arraybolt3[m]> enigma9o7: He just did that.
[02:31] <enigma9o7[m]> run `xrandr` and share output on pastebin
[02:31] <enigma9o7[m]> oh ok
[02:31] <bobdobbs> Also, I'd like to avoid wayland for the moment. I use synergy as a software kvm. It doesn't work with wayland.
[02:31] <bobdobbs> Now, I could switch to wayland if I really had to. But I'd rather try to avoid switching.
[02:31] <arraybolt3[m]> bobdobbs: That's fine. Try the solution from nVidia's website just in case, if that still doesn't work, we'll dive into X troubleshooting.
[02:32] <arraybolt3[m]> bobdobbs: (Funny thing is, nVidia and X are supposed to work OK together. They're working just fine on my system AFAIK, though I should find out if I'm using X or not, I think I am.)
[02:32] <bobdobbs> arraybolt3[m]: the last post in that thread is the guy saying that the proposed solution didn't work for him.
[02:32] <arraybolt3[m]> Yep, my system is on X.
[02:33] <arraybolt3[m]> bobdobbs: Yes, but he also says he got it to work by fiddling with his monitor resolution.
[02:33] <enigma9o7[m]> Yeah sure `xrandr` output, it should list every display port and if it sees anything hooked up, etc
[02:33] <arraybolt3[m]> Working solution: So if I set the resolution to the exact same on all 3 monitors, the external ones begin to properly display: (1920x1080 which is also my native laptop monitor resolution). From there I can readjust the monitors to their respective native resolutions. The settings will also remain persistent after a reboot but you need to replug the hub back into the USBC port after you login in order to get the external screens to
[02:33] <arraybolt3[m]> reappear.
[02:33] <arraybolt3[m]> +1 for xrandr output
[02:34] <bobdobbs> How is he setting resolutions on monitors that his system isn't registering?
[02:34] <arraybolt3[m]> bobdobbs: He ran "sudo prime-select nvidia" and that got the system to register the monitors. They still didn't display until he did the resolution tweaking, though.
[02:35] <bobdobbs> hmmmm
[02:35] <bobdobbs> When I do that I get "Error: no integrated GPU detected"
[02:36] <arraybolt3[m]> bobdobbs: Crud.
[02:36] <bobdobbs> maybe the prime-select tool relies on the nvidia driver loading? Which it probably isnt?
[02:37] <arraybolt3[m]> bobdobbs: Does this help? https://askubuntu.com/questions/1407450/second-monitor-is-not-working-after-freshubuntu-22-04-installation
[02:37] <jhutchins> 2
[02:37] <arraybolt3[m]> To everyone: Anyone know that magic command that shows whether the nVidia drivers are loaded or not? I remember it exists, but can't remember what it is.
[02:39] <jhutchins> arraybolt3[m]: irc is always "To everyone"
[02:39] <jhutchins> arraybolt3[m]: nvidia-smi
[02:39] <jhutchins> arraybolt3[m]: https://linuxconfig.org/how-to-check-nvidia-driver-version-on-your-linux-system
[02:40] <arraybolt3[m]> bobdobbs: Try running "nvidia-smi".
[02:40] <arraybolt3[m]> jhutchins: Thank you!
[02:41] <bobdobbs> arraybolt3[m]: the monitor that is not being fed signal uses HDMI. The card only has one HDMI port. So I can't change the physical port that it is using.
[02:41] <bobdobbs> huh. interesting: https://www.toptal.com/developers/hastebin/eloyenutoy.sql
[02:42] <arraybolt3[m]> Well that might just be the problem.
[02:42] <arraybolt3[m]> Now the question is how to get the nVidia driver to load...
[02:42] <tomreyn> regedit: unmount is actually about file systems, not disks. should be done first for any file systems that have journalling / require umounting to not loose data. "mount" does the reverse. this is more of a preparatory step to ejecting a disk.
[02:43] <tomreyn> regedit: you can also do an scsi bus rescan (this might help with 'undoing' an eject, i havent tried)
[02:44] <bobdobbs> arraybolt3[m]: is a GPU driver a kernel module?
[02:44] <arraybolt3[m]> bobdobbs: Yes.
[02:45] <jhutchins> Eject dumps the buffers first.
[02:45] <bobdobbs> arraybolt3[m]: I'm aware of somethign called 'blacklisting' that prevents kernel modules from being loaded. It is worth trying to eliminate the possibility that I'm blacklisting the module?
[02:46] <arraybolt3[m]> bobdobbs: Yeah, that might be a good idea.
[02:46] <jhutchins> At least one of the logs will say why it's not loading.
[02:46] <tomreyn> jhutchins: as in 'sync'? that's good, but doesn't help with file systems marked unclean, requiring fsck.
[02:48] <arraybolt3[m]> bobdobbs: Can you do "journalctl -n 1000 | nc termbin.com 9999"? That will show us a solid chunk of your log data and potentially help us troubleshoot why your monitor isn't working.
[02:48] <bobdobbs> sure thing...
[02:49] <bobdobbs> https://termbin.com/xi4i
[02:49] <arraybolt3[m]> modprobe: FATAL: Module nvidia not found in directory /lib/modules/5.15.0-39-generic - Boom. That's almost certainly the problem.
[02:50] <arraybolt3[m]> bobdobbs: Can you do "sudo apt update && sudo apt full-upgrade", then reboot and see if that clears up the problem?
[02:50] <bobdobbs> this sounds promising
[02:50] <bobdobbs> ok!
[02:50] <enigma9o7[m]> If that doesnt help, check `ubuntu-drivers list` and see if it thinks its installed, or if it thinks you need to do something
[02:50] <arraybolt3[m]> +1 ^^
[02:52] <bobdobbs> ok. 'full-upgrade' is doing it's thing now. Once that is done (assuming no errors - which I'm sure will be the case) I'll reboot
[02:52] <enigma9o7[m]> The way I've always checked for nvidia driver (didnt know that smi stuff0 was with `glxinfo|grep "version string"`
[02:53] <arraybolt3[m]> enigma9o7: Handy trick to know, I'll try to remember that, since I've got nVidia too. It's not bitten me bad yet, but considering how frequently there's problems with it, it probably will one day.
[02:59] <bobdobbs> arraybolt3[m]: ok - apt had completed. There are no errors. I'm gonna reboot. See you shortly. Please cross your fingers for me.
[02:59] <bobdobbs> If you don't see in a few minutes, tell my descendants that I fought til the end
[03:03] <bobdobbs> arraybolt3[m]: back!
[03:03] <arraybolt3[m]> And? Any progress?
[03:03] <arraybolt3[m]> (We've got more tricks in mind if it's not fixed yet.)
[03:03] <bobdobbs> arraybolt3[m]: actually, I'm just gonna make a cup of hot  tea. It's very cold here. I'll be back properly in 5 mins.
[03:03] <arraybolt3[m]> 👍️
[03:06] <arthuryunzesssss> Hi,anyone here? My PC all usb device is don't work now, I just have to connect it use ssh at another PC. I installed realsense camera sdk before, it may changed some udev rules,then i delete /usr/local/lib/libusb*, then all usb device don't work after a reboot. How can i check and fix it ?
[03:06] <arraybolt3[m]> arthuryunzesssss: There's plenty of us here, but I'm not sure how to fix that. Someone else might have an idea.
[03:07] <enigma9o7[m]> reinstall libusb packages
[03:07] <enigma9o7[m]> sudo apt install --reinstall libusb*
[03:07] <enigma9o7[m]> but replace libusb* with whatever
[03:07] <arraybolt3[m]> arthuryunzesssss: As a rule of thumb, mass-deleting software like that instead of using the package manager is a bad idea. enigma9o7 has good ideas.
[03:07] <enigma9o7[m]> to know what packages you had installed there is a log too, just grep it for libusb or whatever you thought you deleted
[03:08] <enigma9o7[m]> and yeah next time, if you're just doing an experiement, move the f iles somewhere else instead of deleting them.... and ifyou really want to re move them, use package manager to remove package.
[03:09] <arthuryunzesssss> I knew that. But i compare it to a new PC. new PC ubuntu file system don't have any libusb* files at /usr/local/lib path.....
[03:09] <arthuryunzesssss> so i just del it.
[03:09] <bobdobbs> arraybolt3[m]: back. And... no, the OS still isn't picking up the second monitor. Starting nvidia-settings gives me the same message as before: 'ERROR: NVIDIA driver is not loaded'
[03:10] <enigma9o7[m]> yeah but apt thinks they'r einstalled
[03:10] <enigma9o7[m]> so dependencies are missing for something, etc, it can't handle it.
[03:10] <bobdobbs> 'nvidia-smi' returns the same message as before. It can't see a loaded driver
[03:10] <arraybolt3[m]> arthuryunzesssss: The problem with that is that installing software that messes with libraries may be able to override other stuff, so if you still have the problematic software installed but deleted the replacement libraries it installed, there may be a problem.
[03:10] <enigma9o7[m]> bob: `unbuntu-drivers list`
[03:11] <arraybolt3[m]> bobdobbs: OK, check "ubuntu-drivers" list and see if it thinks the driver is properly installed.
[03:11] <arraybolt3[m]> Er, "ubuntu-drivers list".
[03:11] <enigma9o7[m]> it takes a min, be patient
[03:11] <bobdobbs> arraybolt3[m]: https://www.toptal.com/developers/hastebin/tisaruruxe.apache
[03:12] <arraybolt3[m]> bobdobbs: Odd, some nVidia stuff was installed earlier, but to me it looks like it's not installed correctly. Hold on one moment...
[03:12] <enigma9o7[m]> If it were me, I'd remove all of those packages.  Then reboot.  Then `sudo ubuntu-drivers install` to let it pick the right ones.
[03:13] <arraybolt3[m]> WAIT, DON'T DO THAT.
[03:13] <enigma9o7[m]> but do what array says
[03:13] <arraybolt3[m]> enigma9o7: I watched someone kill their system doing that.
[03:13] <bobdobbs> :\
[03:13] <enigma9o7[m]> There is no system killing.
[03:13] <arraybolt3[m]> enigma9o7: If there's some way to avoid having to do that, it would be preferable to something that could go horribly wrong.
[03:13] <enigma9o7[m]> Worst case you have to use tty.  But what should happen is nouveau, unless he blacklisted it.
[03:13] <arraybolt3[m]> (Not trying to override you, just scared.)
[03:13] <enigma9o7[m]> nah no worries
[03:14] <enigma9o7[m]> I did preface it with 'if it were me'
[03:14] <arraybolt3[m]> bobdobbs: Can you check the "Software and Updates" app on your system?
[03:14] <arraybolt3[m]> bobdobbs: There should be a GUI there that lets you properly install nVIdia drivers.
[03:15] <bobdobbs> oh yes!
[03:16] <bobdobbs> this looks promising. under 'software and updates' -> 'additional drivers' I'm seeing options for drivers to install. Including the proprietary driver
[03:17] <bobdobbs> The list has a radio box. The box currently has a proprietary driver selected already. As we know, a driver is indeed installed. But there is in updated one available
[03:17] <bobdobbs> So it might make sense for me to select the updated version and reboot
[03:17] <arraybolt3[m]> bobdobbs: That sounds promising. Let me check just to make sure, but the updated one should be safe.
[03:18] <bobdobbs> Hopefully the updated driver will install... and actually load
[03:18] <bobdobbs> Also, hot instant soup is great in cold weather
[03:19] <arraybolt3[m]> bobdobbs: Looks like that driver should be good. +1 on the hot soup, I love that stuff. (Though over here in the central US it's been getting into the 100+ degrees range.)
[03:19] <arraybolt3[m]> (So my house at least is NOT suffering from cold LOL)
[03:19] <bobdobbs> arraybolt3[m]: where in the states are you? I'm reading a book about politics in Nebraska at the moment
[03:20] <arraybolt3[m]> bobdobbs: I'm in Missouri. I can sum it up in four words. Bipolar. Weather. Gone. Nuts.
[03:20] <bobdobbs> lol
[03:21] <arraybolt3[m]> It can never decide whether it wants to be burning hot or freezing cold. We've had to turn on the heater in the summer, and then blast the AC just a few days later.
[03:21] <bobdobbs> damn
[03:21] <bobdobbs> k, what are our thoughts on updating the driver via the updates gui ?
[03:25] <arraybolt3[m]> bobdobbs: Looks like the newer driver should be OK.
[03:26] <xrandr> Does anyone know of a good linux alternative to OneNote?
[03:26] <bobdobbs> arraybolt3[m]: k, I'm gonna do it. Back shortly
[03:27] <enigma9o7[m]> What is it?
[03:27] <xrandr> What is OneNote?
[03:28] <arraybolt3[m]> enigma9o7: He's installing a newer version of the nVidia driver.
[03:28] <arraybolt3[m]> xrandr: XJournal++ I believe.
[03:28] <enigma9o7[m]> Thats what I wondered, yeah.
[03:28] <arraybolt3[m]> It's actually Xournal++.
[03:29] <arraybolt3[m]> enigma9o7: Think what would happen if LibreOffice lost its concept of a page size and let you type anywhere on the screen. Add some handwriting capabilities, and that's OneNote.
[03:29] <arraybolt3[m]> (OneNote is a Microsoft product, though.)
[03:30] <InPhase> xrandr: cherrytree is an option I recently encountered.  It is in the repository, and seems to have some recent advances that are useful since the last stable ubuntu release, such as adding in LaTeX equation support.
[03:31] <xrandr> Nice thanks!
[03:31] <InPhase> xrandr: Ultimately it's try a bunch and find a workflow that fits your brain.  :)
[03:31] <bobdobbs> arraybolt3[m]: bad news I'm afraid. Monitor not being activated. Still getting the same error from nvidia-settings
[03:32] <bobdobbs> nvidia-smi still saying it can't communicate with the nvidia driver
[03:32] <arraybolt3[m]> bobdobbs: That's downright confusing. I'm afraid you'll need to wait for someone more knowledgable than I to help then, 'cause I'm pretty much out of ideas.
[03:32] <bobdobbs> arraybolt3[m]: thanks for helping out
[03:33] <xrandr> InPhase: Thanks. I'm gonna try those two
[03:33] <bobdobbs> arraybolt3[m]: this stuff is way beyond me
[03:34] <arraybolt3[m]> bobdobbs: nVidia is usually way beyond everyone, experts included. When it works it works well, but when it doesn't, good luck.
[03:34] <arraybolt3[m]> (At least it works well for me.)
[03:36] <arraybolt3[m]> bobdobbs: If all else fails, you might try installing Ubuntu to a USB drive. Like, boot from a live USB, insert a second USB with enough room, then install Ubuntu to the second USB. Then try installing the nVidia drivers from the Software and Updates GUI, and see if that works. Still, someone else might have a better idea.
[03:37] <bobdobbs> arraybolt3[m]: that sounds like PITA, to be honest
[03:38] <bobdobbs> I believe I have an ubuntu 22.02 usb stick close at hand though
[03:42] <InPhase> bobdobbs: You can do that with one USB stick if you use qemu, which will allow you to boost directly to an Ubuntu installer without even rebooting, and then you pass it access to the usb system and it can install directly to the inserted usb.  Since it's a graphical issue, you will of course wnat to do a full proper reboot into it as arraybolt3[m] says for the final test of the alternate setup.
[03:43] <InPhase> s/boost directly/boot directly/
[03:45] <InPhase> bobdobbs: That's a slight bit more to setup but I found it super handy to start making USB boot systems this way.  Once you get used to qemu you can also boot directly from them in the VM and set them up without even rebooting (for purposes other than graphical), so it's a good generalized toolset to have available.
[03:45] <bobdobbs> hmmmm
[03:46] <InPhase> bobdobbs: If you're brand new to Linux, ignore everything I said and do it the straightforward way...  But this is a better way if you're comfortable with the system.  :)
[03:49] <bobdobbs> maybe I should just try and switch to the nouveau driver/
[03:49] <arthuryunzesssss> enigma9o7[m]  I just apt reinstalled  libusb* ,but it still don't work. and i just check /var/log/syslog after i insert a USB Keyborad, is these log useful?
[03:49] <arthuryunzesssss> repeat my question: My PC all usb device is don't work now, I just have to connect it use ssh at another PC. I installed realsense camera sdk before, it may changed some udev rules, then i delete /usr/local/lib/libusb* files, then all usb devices don't work after a reboot.
[03:49] <arthuryunzesssss> Jul  4 11:44:28 sy kernel: [  864.988449] usb 1-8: new low-speed USB device number 6 using xhci_hcd
[03:49] <arthuryunzesssss> Jul  4 11:44:29 sy kernel: [  865.144435] usb 1-8: New USB device found, idVendor=09da, idProduct=2268, bcdDevice= 1.02
[03:49] <arthuryunzesssss> Jul  4 11:44:29 sy kernel: [  865.144441] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[03:49] <arthuryunzesssss> Jul  4 11:44:29 sy kernel: [  865.144445] usb 1-8: Product: USB Keyboard
[03:49] <arthuryunzesssss> Jul  4 11:44:29 sy kernel: [  865.144447] usb 1-8: Manufacturer: SONiX
[03:49] <arthuryunzesssss> Jul  4 11:44:29 sy kernel: [  865.151181] input: SONiX USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.0/0003:09DA:2268.0007/input/input34
[03:57] <arthuryunzesssss> I just apt reinstalled  libusb* ,but it still don't work. and i just check /var/log/syslog after i insert a USB Keyborad, is these log useful? https://pastebin.ubuntu.com/p/vnrkrPdWMz/
[03:57] <arthuryunzesssss> repeat my question: My PC all usb device is don't work now, I just have to connect it use ssh at another PC. I installed realsense camera sdk before, it may changed some udev rules, then i delete /usr/local/lib/libusb* files, then all usb devices don't work after a reboot.
[05:03] <bobdobbs> who was helping me out with monitor issues not so long ago?
[05:12] <arthuryunzesssss> bobdobbs  seems like arraybolt3[m]
[05:12] <bobdobbs> ah yes. thanks.
[05:12] <bobdobbs> arraybolt3[m]: I got it working!
[05:13] <bobdobbs> arraybolt3[m]: I took a shot in the dark. After switching between drivers in the 'software and updates' tool didn't work, I remembered that I have a download of the nvidia installer sitting around.
[05:13] <bobdobbs> arraybolt3[m]: So I ran that installer and rebooted. After that, I have both monitors running.
[07:22] <Bizona> Hello fellows,
[07:22] <Bizona> I have one query and I hope you can give me any insights on it.
[07:22] <Bizona> https://help.ubuntu.com/community/Full_Disk_Encryption_Howto_2019
[07:22] <Bizona> I have followed these instructions for FDE, so the user can log in with just one credential(instead of setting up encryption from the installation process which will require passphrase to decrypt and user password afterwards)
[07:22] <Bizona> All of the steps we successful and were performed on a completely wiped disk with brand new partitions.
[07:22] <Bizona> However when rebooted and tried to test the encryption. At first I got the following BIOS message when trying to boot:
[07:29] <Bizona> Hello Fellas,
[07:29] <Bizona> I have one pickle that I have to solve it is regarding:
[07:29] <Bizona> https://help.ubuntu.com/community/Full_Disk_Encryption_Howto_2019
[07:29] <Bizona> I have followed these instructions for FDE, so the user can log in with just one credential(instead of setting up encryption from the installation process which will require passphrase to decrypt and user password afterwards)
[07:29] <Bizona> All of the steps we successful and were performed on a completely wiped disk with brand new partitions.
[07:29] <Bizona> However when rebooted and tried to test the encryption. At first I got the following BIOS message when trying to boot:
[07:30] <arraybolt3[m]> Bizona: Sadly, I'm missing everything you're saying after "At first I got the following BIOS message when trying to boot:". It looks like you typed the message outside of IRC and then pasted it in - sadly, this may have triggered our flooding protection, which means you may have been muted for 60 seconds. Whenever you're able to talk again, please start over from there. Sorry about this, it's a defense to keep people from being able to
[07:30] <arraybolt3[m]> harm the channel.
[07:31] <arraybolt3[m]> We are happy to help you and will try to assist as soon as the bot unmutes you.
[07:32] <bobdobbs> arraybolt3[m]: hiya. Did you see my last message on this channel to you? I got my display issue sorted.
[07:32] <arraybolt3[m]> bobdobbs: Nice! I saw it was with a downloaded nVidia driver, that was the .run file, wasn't it?
[07:32] <bobdobbs> yup!
[07:33] <bobdobbs> I remembered that I had it sitting in a downloads directory. I just figured it was worth a shot. And it worked.
[07:33] <arraybolt3[m]> bobdobbs: I ask because, if it was the .run file, you may have to reinstall it after every kernel upgrade. So if you reboot your system and are like "ack! Where'd my fancy display setup go?", try reinstalling the driver.
[07:33] <bobdobbs> ah, that's good to know !
[07:33] <arraybolt3[m]> (The Ubuntu package is supposed to avoid that, but it wasn't working in this instance, so whatever works.)
[07:35] <bobdobbs> arraybolt3[m]: the only issue was that it switched me from x11 to wayland. Currently no software kvm seems to support wayland. But I guess I can't win 'em all.
[07:36] <bobdobbs> I've been using a software kvm - synergy - for years, so I can control my mac. But I'm considering returing the mac anyway. It's too crashy and not critical for my work.
[07:36] <arraybolt3[m]> bobdobbs: Is your software kvm doing something like letting you use multiple computers as monitors for your main system? Or letting you use multiple systems with the same keyboard and mouse?
[07:36] <bobdobbs> arraybolt3[m]: it lets me use a single k/m across two, sometimes three computers
[07:37] <arraybolt3[m]> bobdobbs: You might be able to control your Mac using something like VNC or SSH. I personally use SSH to remote control my desktop from my Chromebook ("ssh -X -C user@computer" and BOOM I can access GUI apps over the network). It's not perfect, but it's really handy.
[07:37] <bobdobbs> huh.
[07:38] <arraybolt3[m]> SSH will only give you individual apps, though. VNC will give you a full remote desktop session. So it won't be exactly the same as a KVM, but it'll be something.
[07:38] <bobdobbs> yeah, I'll consider that... but my mac just crashed again now. So my thoughts of retiring it are... increasing
[07:38] <alkisg> It's also possible to run vnc over ssh and get the whole desktop
[07:38] <arraybolt3[m]> (Also not sure how well SSH with X forwarding will work with macOS, I dunno if a Mac has an X server.)
[07:39] <bobdobbs> I mostly use it for a media center. Watching movies while I work.
[07:39] <bobdobbs> So now I'm thinking... maybe I could wire a third monitor to my ubuntu machine instead
[07:39] <arraybolt3[m]> Man, glad to know Macs are crashy, I just about forked out almost a grand for one some months ago.
[07:40] <bobdobbs> arraybolt3[m]: I think it just might by my mac. It's a good machine, but I've put more ram in it... and it's not Special Mac Ram.
[07:40] <arraybolt3[m]> bobdobbs: If all you need is a media center, you might consider getting some cheap Linux mini PC. A Raspberry Pi might work (though I've experienced a bit of screen tearing with it). They're dirt-cheap and mine's been reliable so far.
[07:40] <bobdobbs> It's only been crashy since I increased the RAM from 8G to 32G
[07:41] <bobdobbs> hmmmm
[07:41] <arraybolt3[m]> Ah. I've heard Apple devices are particularly finicky when it comes to hardware. Reports of things like "I added a screen protector and now Face ID doesn't work" or insane stuff like that.
[07:42] <bobdobbs> arraybolt3[m]: the media center has to be able to run either mac or windows. Basically, I'm streaming movies from Amazon Prime to a country where Prime is limited. So I'm using getflix (I got a lifetime account) to fool Amazon Prime into thinking that I'm in the USA
[07:42] <bobdobbs> getflix has a client app for windows and mac
[07:42] <arraybolt3[m]> bobdobbs: You could just use a VPN service and do the same thing.
[07:43] <arraybolt3[m]> (ProtonVPN is one I've looked into a bit.)
[07:43] <nikolam> Since recently (And I have seen is most obviously today), my system seems very slow and sometimes unresponsive. I tried to get back to system state from July 1s (from BTFS snapshot) and it behaves the same..
[07:43] <bobdobbs> Last few times I shopped around, nothing beat getflix
[07:43] <bobdobbs> Also... because I've got a lifetime account with getflix, I don't have to pay a sub
[07:44] <nikolam> But I think it is CPU time issue , evert command freexes for a few seconds before continuing.
[07:44] <bobdobbs> Also... I'd like my media center to be able to run a good screen. The mac is fairly high-res. Definitely higher than 1080p
[07:44] <arraybolt3[m]> bobdobbs: ProtonVPN is free, but whatever works for you. They sell dirt-cheap Windows PCs on EBay where I'm at.
[07:44] <nikolam> OS is on SSD (SATA) , it is HP 600G1 TWR with i5 4570, using intel graphics at the moment
[07:45] <bobdobbs> k, looking at proton...
[07:45] <arraybolt3[m]> nikolam: Possibly a kernel issue, try booting into an older kernel. During early boot, hit Esc just when the screen changes or goes totally black, then select "Advanced Options for Ubuntu", and select an older kernel in the list (don't select one of the recovery mode options).
[07:46] <nikolam> arraybolt3[m], I tried booting in state from Joly 1st and recently deleted older Btrfs snapshots. Will try booting older kernel in current newest state and report.
[07:46] <arraybolt3[m]> nikolam: If no amount of trying gets Esc to work for you, try using Shift instead.
[07:46] <nikolam> arraybolt3[m], thanks
[07:46] <arraybolt3[m]> No problem.
[07:47] <arraybolt3[m]> If an older kernel works, try not to reboot until the next kernel update if you can avoid it. Then when a kernel update comes through, boot into it and see if the problem's been resolved. If it's persistent, you may want to open a bug report on Launchpad.net.
[07:56] <arthuryunzesssss> finally i fixed it by `sudo apt-get install xserver-xorg-input-all`. thank you all!!
[07:56] <arthuryunzesssss> repeat my question: My PC all USB device is don't work now, I just have to connect it use SSH on another PC. I installed realsense camera sdk before, it  may changed some udev rules, then I delete /usr/local/lib/libusb*,then all USB devices didn't work after a reboot.
[08:11] <alkisg> dpkg -V => (partially) checks for modified system files
[08:11] <alkisg> *with sudo
[08:40] <nikolam> arraybolt3[m], I think issue here were hardware related. I removed power form all the hard drives and SSD and disconnected Sata to 2X sata power extender and connected all 3 drives directly to power supply. And maybe because of power disconnecting/connecting it now works fine.
[08:41] <nikolam> Misbihaving SATA devices also are known for causing weird troubles on other OSes too.
[08:41] <nikolam> When I saw some kind of issue on ZFS mirror pool, I knew it were about SAAT drive.
[08:41] <nikolam> After re-connecting everyting back to normal.
[08:41] <arraybolt3[m]> nikolam: Makes sense. Sometimes just taking stuff out and putting it back in fixes it. You should have seen the screen on my Windows XP box the day a STRAND OF HAIR got stuck in one of my RAM sockets (with a RAM stick in it, mind you!).
[08:41] <arraybolt3[m]> (Still not sure how that happened.)
[08:42] <nikolam> So, power extenders can cause power issues to the drives and some old drives "love" to be disconnected and re-connected to power and continue working fine.
[08:42] <nikolam> I also have external power supply for drives, so it also may be grounding issue too.
[08:42] <arraybolt3[m]> Power extender, like the SATA equivalent of an extension cord?
[08:43] <nikolam> like power splitters , from one SATA power plug for hard drive, to 2 power for SATA
[08:43] <nikolam> male to 2 females
[08:44] <arraybolt3[m]> Yeah, that sounds like a problem to me.
[08:44] <arraybolt3[m]> Power splitters at least used to cause crazy problems with HDDs, sounds like they still do today.
[08:45] <arraybolt3[m]> Glad to hear you got it working!
[08:45] <nikolam> arraybolt3[m], yes, thanks :P
[10:13] <pitiless> i had a boyfriend named "Ubuntu" once
[10:13] <pitiless> ...
[10:14] <pitiless> nobody knows the rest?
[10:14] <pitiless> sheesh getting anything out of you guys is like pulling teeth
[10:14] <EriC^^> something like blabla kicked pitiless blabla
[10:14] <pitiless> wrong
[10:14] <KBar> pitiless: Do you have Ubuntu-related questions?
[10:14] <arraybolt3[m]> pitiless: Sorry, but this is the Ubuntu live chat support channel. You might have better luck on #ubuntu-offtopic.
[10:14] <pitiless> yes
[10:15] <pitiless> where is the usa back door you guys told me about at Mesa
[10:15] <arraybolt3[m]> (If you'd said, "Hey guys I just accidentally deleted an important file, how do I get it back?", you'd probably have a small army come out of the woodwork to help you fix the problem.)
[10:15] <pitiless> Ubuntu has an nsa back door
[10:15] <pitiless> wrong, arraybolt3[m]
[10:16] <pitiless> that's a lie
[10:16] <arraybolt3[m]> pitiless: This is not an Ubuntu support question. Please, if you want to discuss this, take it to #ubuntu-offtopic (or, if you think the back door is a high-quality discussion point, maybe try #ubuntu-discuss.)
[10:16] <pitiless> what's the best Linux distro for child porn?
[10:17] <pitiless> that doesn't have a usa back door
[10:17] <arraybolt3[m]> !ops | kick pitiless now
[10:17] <pitiless> emergency
[10:17] <arraybolt3[m]> pitiless: That is illegal, and highly unacceptable. If there's an operator around, you will be banned.
[10:17] <pitiless> what a great excuse to do whatever the fuck you want
[10:18] <arraybolt3[m]> pitiless: Yeah, stop polluting our minds and wreaking havoc. You know better.
[10:18] <pitiless> i guess I'll just have to notify the credit agencies and put the usa on an mkultra payment plan
[10:18] <pitiless> 30 year mortgage... s&p can't be trusted to rate credit
[10:19] <pitiless> after that 2009 mbs heist
[10:19] <pitiless> give me something better to do then
[10:20] <pitiless> it's my responsibility on behalf of the other children and my sister the CIA tortured from birth
[10:20] <pitiless> trauma based mind control research
[10:20] <oerheks> pitiless, please leave this channel, thanks.
[10:20] <Maik> pitiless: that's enough for now
[10:20] <pitiless> naw fuck you
[10:21] <Maik> !ops | pitiless is misbehaving
[10:21] <pitiless> can't you use the skull chip to make me pass out? just do that
[10:21] <pitiless> i can't sleep
[10:22] <pitiless> what you don't pay me will cost 100x in havoc
[10:22] <pitiless> don't be stupid. pay for mkultra
[10:22] <arraybolt3[m]> Wow, glad that's over.
[10:24] <Maik> next time it's best not to feed such people too much
[10:25] <arraybolt3[m]> Probably a good idea. They like wreaking havoc, so getting mad is what they want...
[10:25] <Maik> exactly
[11:56] <dvorkindmitry> Ubuntu 22. I need to build extrnal module for the default kernel. installed kernel-headers, but was not able to build. Then I installed linux-source, unpacked, copyed current .config and build the module. But VERMAGIC is different and no sign. How to do it correctly?
[12:00] <ravage> the best way is to use dkms
[12:01] <ravage> and why would you need the .config file for that?
[12:06] <dvorkindmitry> ravage, I will use dkms a bit later. now need to just understand what is wrong
[12:06] <arraybolt3[m]> dvorkindmitry: Does your system have Secure Boot enabled?
[12:07] <dvorkindmitry> ravage, I need .config case linux-source does not have it
[12:08] <dvorkindmitry> arraybolt3[m], you mean EFI? no. I'm using ubuntu in VirtualBox. No need any security. I just need to undersand how to build module correctly, what kernel source whould I use and why vermagic is different
[12:09] <arraybolt3[m]> Ah, OK. I don't know about vermagic and whatnot, but I saw you mention signing and thought, "Oy, he's gonna run into a heap of complexity trying to do kernel module stuff if Secure Boot is enabled." But you don't have Secure Boot in your environment, in which case that's a hurdle you don't have to jump.
[12:12] <ravage> modinfo module.ko
[12:12] <ravage> will show you the kernel it was built for
[12:12] <ravage> compare with uname -r
[12:14] <dvorkindmitry> arraybolt3[m], oh, no. My default kernel in Ubuntu is currently signed. So To load the module I need to have same VERMAGIC and sign the module too.
[12:15] <dvorkindmitry> ravage, I already did it! That's why I know the problem. Is there any good guide how to correctly build external kernel module for default kernel?
[12:15] <ravage> you really just have to build agains the same headers
[12:17] <ravage> thats /usr/src/linux-headers-$(uname -r)
[12:35] <Jeremy31> dvorkindmitry: If you have made that source before, you might need to make clean
[12:55] <dvorkindmitry> ravage, I try. But got security headers error - some of them does not exist in the headers tree!
[12:56] <dvorkindmitry> Jeremy31, no, I took it as-is! apt install linux-source, unpack, copy the .config to this dir, then "make oldconfig && make scripts && make modules_prepare". Like it should be done!
[12:59] <Jeremy31> Try>  make -C /lib/modules/$(uname -r)/build M=$(pwd) clean && make -C /lib/modules/$(uname -r)/build M=$(pwd) modules
[13:54] <squid_game> I am using ubuntu 22.04. I can't install python3.8 by apt install python3. Does anyone know how to install it?
[14:03] <mickey> what would be a good way to force all dns traffic through a specific DoH server on a laptop, so it doesn't use arbitrary DNS servers provided by dhcp servers everywhere? dnscrypt-proxy?
[14:18] <sweb> inside kvm machine, should i disable completly systemd-timesyncd ?
[14:18] <sweb> if on KVM host chrony is installed
[14:18] <sweb> ubuntu 20.04
[14:40] <Psil0Cybin> Hey squid gamer
[14:41] <Psil0Cybin> Question folks so trying to backup data for reformat rsync best way?
[14:41] <Psil0Cybin> My home directly just configurations for apps mainly
[14:42] <arraybolt3[m]> Psil0Cybin: Depends on what you're trying to do. RSync will probably do the trick, though, it can clone an entire Linux system from one drive to another and have things working right - I did it once.
[14:43] <arraybolt3[m]> Psil0Cybin: One thing you'll want to be sure of is that the filesystem on your external drive matches the one on your internal drive. If you try to rsync from ext4 to FAT32, you are going to be so sad when you lose all your file permissions. Preferably, make the filesystems identical. If you're using ext4 on your internal drive, use ext4 on your external drive.
[14:44] <rob0> well, a full Unix filesystem. You should have no troubles going from ext4 to xfs, for example. FAT filesystems do not work for Unix file attributes.
[15:07] <kzootech> hello world! the other day i was having problems with ubuntu both 20.04 and 22.04 not turning on my screens unless i used nomodeset or video=... at boot, if i used video=... then when it comes times for X to start i get the same no signal type problem, the xorg logs make it appear as everything went fine
[15:09] <kzootech> its a radeon pro wx4100 card that should be supported by amdgpu (its detected, it does edid stuff in xorg, etc)
[15:09] <arraybolt3[m]> kzootech: What video hardware are you using? Integrated graphics? AMD Radeon? nVidia?
[15:09] <kzootech> arraybolt3[m]: radeon pro wx4100
[15:09] <arraybolt3[m]> Wow, wouldn't have expected an AMD to go wonky. Maybe silly, but can you double-check your monitor connections to the video card? Sometimes just unplugging stuff and plugging it back in can fix stuff.
[15:09] <kzootech> (ive had this same issue in two versions of ubunut, fedora, and debian)
[15:10] <kzootech> arraybolt3[m]: ive tried that, ive tried unplugging them after X starts, power cycling, etc
[15:10] <kzootech> ive had issues with display port cables before, but these are certified ones
[15:10] <kzootech> and it all works fine in non-linux land
[15:11] <kzootech> https://bbs.archlinux.org/viewtopic.php?id=245260 this person seems to have a very similar issues that they seemed to have solved with displayport to dvi adapaters, which i dont have
[15:11] <arraybolt3[m]> kzootech: Shoot. And this has been happening since day one, right?
[15:12] <kzootech> well no idea realy, i had this machine as a linux machine for a long time, switched away, bought a new gpu, so this is the first time ive really tried this gpu in linux
[15:12] <kzootech> i bought it with the idea its probably pretty compatible
[15:13] <kzootech> it seems like an issue with modesetting to me
[15:13] <kzootech> i just dont know how to approach the issue at this point
[15:13] <arraybolt3[m]> Looking at stuff that might help.
[15:13] <mickey> also, is there a working way to get wireguard settings in the network management of gnome on ubuntu 22.04, or cli is really the only way now?
[15:14] <kzootech> arraybolt3[m]: i think ive tried everything i can think of, disabling/enabling xwayland, using 20.04 and going back to kernel 5.4 to manually install amdgpu drivers from amd, etc
[15:15] <arraybolt3[m]> kzootech: I'm looking up stuff about PRIME, that Arch thread you linked to said something about it.
[15:16] <kzootech> arraybolt3[m]: i think that has to do with multiple gpus? this computer does have integrated graphics, but i disabled that in the bios to eliminate that as a possible issue
[15:17] <arraybolt3[m]> I'm not sure what to do then. You might give the proprietary drivers a shot, other than that, I'm stumped. Sorry, someone else might know the answer.
[15:18] <kzootech> it seems like some sort of weird driver issue
[15:46] <jhutchins> https://forums.developer.nvidia.com/t/enabling-switchable-graphics-on-amd-and-nvidia-hybrid-gpu-in-asus-tuf-series-laptops-on-linux/118585
[16:05] <ioria> kzootech, i don't know that card, but might be a resolution issue ; boot with 'nomodeset' and change the resolution in Settings -> Displays  and reboot
[16:53] <p9> Are /mnt/* mountpoints available to snaps? From what I've read they should be but I'm still getting Permission denied on access
[16:54] <arraybolt3[m]> p9: I believe they are available, but you need to connect a specific interface or something like that. I'll see if I can dig up the docs...
[16:54] <p9> arraybolt3[m]: yeah the :removable-media I have it connected and I can access udisks-mounted volumes in /media
[16:55] <p9> but not /mnt ones from fstab
[16:56] <arraybolt3[m]> p9: Hmm, :removable-media ought to have done it from what I'm seeing. Maybe you can create a custom folder in /media and use that instead?
[16:56] <oerheks> snaps are mounted in /var/lib/snapd/snaps/
[16:56] <arraybolt3[m]> (Snaps are remarkably restricted when it comes to what paths they can access - the list of allowed paths is literally hardcoded into the Snap code AFAIK.)
[16:56] <oerheks> and user settings in ~/snap/
[16:57] <jhutchins> p9: That suggests that the settings in fstab may be the problem.
[16:58] <p9> arraybolt3[m]: I know but the ones under /mnt were supposed to be available: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1643706/comments/49
[16:58] <oerheks> some snaps give a setting in settings > applications
[16:59] <arraybolt3[m]> Well, looking at the source code, I don't see /mnt in the list of allowed directories, but I do see /media in there.
[16:59] <jhutchins> I thought that violated the whole idea of snap isolation.
[16:59] <oerheks> the old way to override was install snap with --classic option, .. depreciated
[17:00] <arraybolt3[m]> Snippet of code right out of the Snap source: https://pastebin.com/AwsUw1iC Contains the list of allowed mountpoints. Not sure if there's other places where other mountpoints are listed, but FWIW, there it is.
[17:01] <p9> arraybolt3[m]: this is from current version?
[17:01] <arraybolt3[m]> p9: If you're willing to trust the Snap with your life (or at least with your computer's security), you can install it with --devmode, that may let you bypass the restrictions you're running into (and defeat half the purpose of Snaps, but Snaps are so often rough around the edges I don't think anyone cares).
[17:01] <arraybolt3[m]> p9: Yep, most recent source.
[17:02] <arraybolt3[m]> Oh wait, I was wrong, hold on...
[17:02] <arraybolt3[m]> (GitHub threw me for a loop, sorry, making new pastebin, strangely I see /mnt in the actual latest sources)
[17:02] <p9> jhutchins: /mnt would make since that's where people are supposed to mount their network drives, etc.
[17:02] <jhutchins> If the security is controlled from within the snap then the snap has no inherent security.
[17:03] <jhutchins> There's nothing that prevents it from trashing the root system.
[17:03] <arraybolt3[m]> https://pastebin.com/nSey72LE
[17:03] <p9> I don't see a reason for why only removable media is allowed
[17:04] <arraybolt3[m]> p9: How exactly did you connect :removable-media?
[17:04] <jhutchins> p9: The illusion of protecting the host system.
[17:05] <p9> arraybolt3[m]: wait a second it's not connected, damn it
[17:05] <p9> or is it?
[17:05] <p9> removable-media           losslesscut:removable-media  -
[17:06] <p9> slot is shown as "-" so that means snapd?
[17:06] <arraybolt3[m]> p9: Try running "snap connections <appname>" and that will tell you if it's connected I believe.
[17:07] <arraybolt3[m]> The empty slot appears to mean that the snap does not have access to the interface.
[17:07] <oerheks> losslesscut gives an entry in systemsettings > applications >  losslesscut
[17:07] <oerheks> really..
[17:08] <p9> jhutchins: /mnt is not system it's data. besides snap is not docker it's not meant to be isolated
[17:08] <oerheks> p9 yes it is by design
[17:09] <arraybolt3[m]> p9: Can you try "sudo snap connect losslesscut:removable-media :removable-media" and see if that gets it to work?
[17:09] <arraybolt3[m]> (I think your app is called losslesscut, if not, replace the bit about losslesscut.)
[17:09] <p9> removable-media           losslesscut:removable-media  :removable-media                 manual
[17:09] <arraybolt3[m]> p9: So no, the interface is NOT connected, and the command above should connect it.
[17:09] <p9> yay
[17:09] <arraybolt3[m]> p9: That looks more like it.
[17:10] <oerheks> next time, look into settings :-)
[17:10] <p9> I remember connecting it before must have disconnected during upgrade (?)
[17:10] <p9> it works now!!
[17:11] <arraybolt3[m]> oerheks: Hey, I like the command line, leave us to it! (read: 🤦‍♂️ how did I not think of that...)
[17:12] <p9> arraybolt3[m]: thanks I would probably spent the rest of the day on it
[17:14] <arraybolt3[m]> p9: No problem. Glad to help, even if my solution was more difficult than it needed to be.
[17:24] <Gloomweaver> I seem to have messed up certificates on my 18.04.6 system
[17:24] <Gloomweaver> I'm not 100% sure how to fully diagnose the issues, let alone fix them lol
[17:26] <Gloomweaver> I did 'apt update', 'apt upgrade', 'dpkg-reconfigure ca-certificates' and 'apt install -y ca-certificates'
[17:29] <oerheks> Gloomweaver, really? did it install ca-certificates again?
[17:29] <genii> Gloomweaver: You might want to try something like: sudo apt install --reinstall ca-certificates  ...which would overwrite any messed up config files
[17:29] <Gloomweaver> https://pastebin.mozilla.org/Dyck2fGO
[17:29] <genii> oerheks: Ya but without --reinstall will just re-use existing conf stuff
[17:30] <oerheks> so, what is messep ?
[17:30] <oerheks> c/messed up ?
[17:31] <Gloomweaver> genii: used --reinstall flag and tried again, same error trying to connect to google
[17:31] <genii> oerheks: "<Gloomweaver> I seem to have messed up certificates on my 18.04.6 system" "<Gloomweaver> I'm not 100% sure how to fully diagnose the issues, let alone fix them lol"
[17:31] <genii> Gloomweaver: It may require a logoff/logon cycle
[17:31] <oerheks> i get the same output, nothing wrong with your paste
[17:33] <Gloomweaver> hmm
[17:33] <oerheks> oh wait..  indeed different https://pastebin.mozilla.org/T3vasNw2
[17:34] <Gloomweaver> genii: it's ubuntu server and I was hoping to avoid rebooting or login cycling... any way to work around it?
[17:35] <oerheks> reboot that server, there is nothing else you can do? even your current running services might be having troubles too.
[17:37] <Gloomweaver> but muh uptime
[17:37] <oerheks> interesting..
[17:38] <arraybolt3[m]> Gloomweaver: Can you get away with restarting one non-critical service and see if it suddenly starts working again? That might tell you if the reboot is worth it.
[17:38] <genii> Gloomweaver: Issuing sudo update-ca-certificates  ...might work
[17:38] <genii> Since that should do all the hooks required to properly restart it
[17:41] <Gloomweaver> arraybolt3[m]: well... so I have an IRCd running, which I want to avoid restarting for obvious reasons, and a ZNC, those are the main ones. IRCd is working fine, but znc keeps having issues connecting to libera WRT TruskPKI never working correctly. so down the rabbithole from #znc and some googleing and it seems my root certificates are all messed up
[17:42] <Gloomweaver> I could restart my znc and see if it works now
[17:44] <Gloomweaver> when I reinstall ca-certificates, it says "Updating certificates in /etc/ssl/certs..." "0 added, 0 removed; done."
[17:44] <Gloomweaver> seems there should be some though?
[17:45] <patanga> my chromium refuses to go to new sites (base urls). it works fine, as long as i stay on a certain site , say, ammazon.com, i see all subsites. But as soon as i want to change to abc.com or even chromium://extensions , either by link or by inserting the url, it refuses to do it. enough ram and cpu there. any idea?
[17:46] <BadAtom> are you sure the sites you can go to aren't cached?
[17:46] <BadAtom> and can you resolve DNS for the ones that don't work?
[17:47] <oerheks> patanga, why crossposting ?
[17:47] <patanga> BadAtom: i can reach the other sites with w3m ..., so no DNS problem. no the sites are not cached
[17:47] <patanga> oerheks: sorry
[17:50] <XoloX> https://ibb.co/0DHWgsp
[17:50] <oerheks> oh we need to click that, XoloX ?
[17:50] <XoloX> How do I add the unallocated space to SDA10?
[17:50] <XoloX> Yes It's a screenshot. I really don't know what to do?
[17:51] <XoloX> I need to make the partition I'm using bigger.
[17:52] <oerheks> clcik sda10, in the menu: resize, and it will grow taking space from unallocated
[17:53] <arraybolt3[m]> XoloX: You'll need to unmount SDA10 before you can move and grow it, so you may have to boot from a live USB. Make sure you have full backups of all your data before doing this.
[17:53] <oerheks> partitions can grow, without unmounting AFAIK, not shrink
[17:55] <XoloX> It's a laptop. I got it for free because the screen was busted. A few years ago I managed to wipe it, took of the screen. Back than I had a youtube video showing how to boot from USB. Managed to put linux on it. For the hell of it I cannot find the video back. So booting from a USB is a problem.
[17:56] <arraybolt3[m]> XoloX: There's a ton of people here who can walk you through that process.
[17:56] <arraybolt3[m]> XoloX: Do you have a blank USB drive on hand?
[17:57] <XoloX> That would be great!
[17:57] <XoloX> Yes I have it has the latest Ubuntu.
[17:57] <XoloX> But I can not boot off it!
[17:58] <arraybolt3[m]> XoloX: Fantastic. So what you do is, you power down your computer, then plug in the USB drive and turn it back on. While it's booting up, hammer the Esc key like crazy (your system might require a different key here). When you get to something that gives you an option like "Boot Menu", select that option, then pick the USB drive.
[17:58] <arraybolt3[m]> XoloX: HP laptops should respond to the Esc key, but other common keys are F2, F10, and F12 - your screen may tell you what button to press during very early bootup.
[17:58] <XoloX> Yes but there is no monitor. That's the problem.
[17:59] <arraybolt3[m]> XoloX: OK, what's the exact make and model of your laptop? Something like "Dell Inspiron 7000" is what I'm looking for.
[17:59] <oerheks> no monitor ..
[17:59] <arraybolt3[m]> (That should be enough for us to figure out the right settings.)
[17:59] <arraybolt3[m]> oerheks: Probably no built-in monitor, the BIOS may insist on trying to display to a nonexistent laptop screen.
[18:00] <arraybolt3[m]> He's almost certainly using an external monitor.
[18:01] <EriC^^> XoloX: hp uses f9
[18:01] <XoloX> I have an external monitor. But that doesn't show the BIOS. I tried a magnet around the border of the bottom part, no luck. Maybe in the hinges? But it took them off years and many houses ago. If I look in the terminal it says "lid open"
[18:01] <XoloX> It's a asus s400c
[18:02] <arraybolt3[m]> XoloX: OK, that may help me figure out how you can do this blind.
[18:02] <XoloX> That would be awesome!
[18:02] <XoloX> How do you know?
[18:03] <arraybolt3[m]> XoloX: Manufacturers frequently give specific directions for how to enter BIOS setup and the boot menu. No need for a screen as long as the keyboard works, though you may have to hunt and peck until you find the USB drive in the boot menu.
[18:04] <arraybolt3[m]> XoloX: OK, this may be a bit tricky, I may be a bit while I gather instructions that are as close to perfect as I can get.
[18:04] <XoloX> Awesome dude/dudette!
[18:05] <arraybolt3[m]> XoloX: OK, can you continue chat even if you power off the system? Or do I need to give you all the instructions at once?
[18:07] <XoloX> I'm on a different PC, no worries. Do we need to change the settings in the BIOS? Or is there an option like in my new laptop. "press f9 to select boot media"? If we need to go into the BIOS settings I like to have so that it boots from USB when I put a stick in.
[18:08] <arraybolt3[m]> XoloX: So here's the first thing to try. Power off the laptop entirely. Then hold the F2 key and power the laptop on, holding down F2. After a bit, release the F2 key, then press F8. Next, down arrow, then Enter key. That may boot you into the live USB immediately. If not, come back and we'll try option 2.
[18:08] <arraybolt3[m]> XoloX: It's sorta like the "press f9 to select boot media" but a bit trickier, the instructions above *may* work, if they don't your system may require a different set of keypresses.
[18:08] <XoloX> After a bit, | how many seconds is a bit?
[18:09] <arraybolt3[m]> XoloX: I'd do 7 seconds. You have to just take a wild guess here since you don't have a screen, but 5 seconds is about right for many of my systems, so I'd try 7 to give it enough time.
[18:10] <arraybolt3[m]> XoloX: In the event this doesn't just work, power the computer down all the way so we can try the other method.
[18:12] <XoloX> press F8. Next, down arrow | next is right arrow?
[18:12] <arraybolt3[m]> Down arrow, then Enter.
[18:13] <arraybolt3[m]> Not right arrow.
[18:13] <arraybolt3[m]> XoloX: Again, if this doesn't work, don't start pressing other keys, just shut the system all the way down so we can try the other method.
[18:13] <XoloX> No luck
[18:14] <arraybolt3[m]> XoloX: OK. Hold the power button until the system turns off.
[18:15] <arraybolt3[m]> XoloX: The other method is even more arcane. Hold the F2 key and press the Power button, keep holding F2 for 7 seconds, then release it. Then press the Right Arrow key exactly 4 times. Then press Down Arrow exactly 6 times, then press Enter.
[18:15] <XoloX> I turned it off and on it's still booting
[18:15] <XoloX> oke give me sec
[18:17] <XoloX> Sorry, no luck
[18:18] <arraybolt3[m]> Ugh. Crud. OK, let's try this.
[18:18] <XoloX> After i did the last thing it booted into the normal os (linux mint). Did I select that drive?
[18:18] <arraybolt3[m]> Hold F2, press power, release power, hold f2 for 7 seconds.
[18:19] <arraybolt3[m]> XoloX: Very possibly! Try hitting the Down Arrow key 7 times in the last step then.
[18:19] <arraybolt3[m]> (Forget about the "OK let's try this part", it sounds like we're near success.)
[18:19] <XoloX> gonna try. Godspeed!
[18:19] <oerheks> and broken screen .. and running mint..
[18:19] <XoloX> ?
[18:20] <arraybolt3[m]> XoloX: We usually don't offer support for systems other than Ubuntu, but we're so close at this point.
[18:21] <arraybolt3[m]> oerheks: We only don't support Mint because of potential software differences AFAIK. This is a hardware problem, and it's one we've almost solved.
[18:21] <XoloX> I figured it's based on Ubuntu?
[18:22] <XoloX> No luck on 7 down. It goes back into Mint.
[18:22] <arraybolt3[m]> XoloX: Well, the thing is, Ubuntu derivatives can ship software configuration that we aren't prepared to deal with, so we stick to officially supported Ubuntu flavours so we know what to expect.
[18:22] <arraybolt3[m]> XoloX: Then try 5 down.
[18:22] <arraybolt3[m]> (Maybe the USB drive is located above the hard drive, not below it.
[18:23] <oerheks> weird hardware issue, he has no screen .. so how would he use that laptop?
[18:23] <arraybolt3[m]> oerheks: Laptops with no screen work with an external monitor plugged in.
[18:23] <arraybolt3[m]> Just use it as a desktop.
[18:25] <enigma9o7[m]> You could also ssh/vnc into it.
[18:25] <enigma9o7[m]> Use it as a media player for your tv.
[18:26] <XoloX> No luck and not booting.
[18:27] <XoloX> I have a desktop. Broken laptop is hooked up to TV indeed. SSH would be possible to do it? The desktop is win10.
[18:28] <XoloX> But in SSH it would need to run. So I can not unmount the partition. No?
[18:29] <arraybolt3[m]> XoloX: Crud. I'm not sure how to make it work then. And there's no way to get the old screen back on for just long enough to stumble through the BIOS menu?
[18:30] <XoloX> No it was really broken. And I lost sight of it years ago.
[18:30] <XoloX> Did you see the picture I posted?
[18:31] <arraybolt3[m]> XoloX: Blah. Yeah, the problem is SDA10 is your root partition, there's no way to get it to move while its mounted.
[18:32] <XoloX> It's not possible flat out?
[18:32] <XoloX> It's frustrating. I managed to put mint on it a few years ago.
[18:32] <arraybolt3[m]> XoloX: If the partition is mounted, there's no way to move it, flat out. If you can figure out the key sequence that will get you to the USB drive, you should be good. Here's the page I was referring to: https://www.asus.com/us/support/FAQ/1013017/#A1
[18:33] <XoloX> The youtube video I used was in legacy mode
[18:34] <XoloX> The blue / grey interface
[18:34] <arraybolt3[m]> XoloX: Yeah. That's where I was getting my "press the arrow keys X number of times" from, looking at the sample screens in that link.
[18:38] <XoloX> Ow cool.
[18:38] <XoloX> Do you know how to google what part of the laptop scans for "lid closed"?
[18:39] <arraybolt3[m]> No clue sadly.
[18:40] <XoloX> Can i save this chat?
[18:40] <oerheks> !logs
[18:40] <oerheks> no need to
[18:40] <XoloX> I want to.
[18:41] <arraybolt3[m]> XoloX: You can download the .txt files of #ubuntu from the website Ubottu linked to. That will let you save the chat.
[18:42] <XoloX> https://irclogs.ubuntu.com/2022/07/04/
[18:42] <XoloX> ?
[18:43] <arraybolt3[m]> XoloX: FInd the file named "#ubuntu.txt" in there. You might want to wait 15 or 30 minutes before downloading it so that all the data has a chance to get properly logged, there's a bit of a lag between when a message is sent and when it shows up in the IRC logs.
[18:43] <arraybolt3[m]> XoloX: The file you want: https://irclogs.ubuntu.com/2022/07/04/%23ubuntu.txt
[18:44] <arraybolt3[m]> Again, wait a bit before saving it so it gets all the data.
[18:45] <XoloX> Thanks! I wait a bit.
[18:47] <XoloX> Is there a newer file? This one stops at 18:00
[18:47] <XoloX> (it's 20:48 where I am)
[18:47] <arraybolt3[m]> XoloX: No, the file gets updated after a while. It may take some time, but it'll get there eventually.
[18:48] <XoloX> Cool.
[18:48] <arraybolt3[m]> (And, the file will stay there for the rest of forever (unless Canonical decides to get rid of it, which is highly unlikely), so even if you don't get it today, you can get it tomorrow.)
[21:42] <ahoypaloy> h-hi everyone
[21:44] <jhutchins> ahoypaloy: Got a question about Ubuntu?
[21:45] <ahoypaloy> anyone experiencing display closure after latest updates?
[21:45] <ahoypaloy> whenever I wake up my PC from a suspension/lock, the monitors will close automatically after
[21:45] <ahoypaloy> 5-10 seconds and restore again after clicking the mouse/keyboard
[21:45] <ahoypaloy> Linux workstation 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
[21:49] <jhutchins> ahoypaloy: Wayland or X?  Hardware?  What desktop (gnome is the default)?
[21:49] <ahoypaloy> Distributor ID:	Ubuntu
[21:49] <ahoypaloy> Description:	Ubuntu 22.04 LTS
[21:49] <ahoypaloy> Release:	22.04
[21:49] <ahoypaloy> Codename:	jammy
[21:50] <SuperLag> Are there unneeded services I can turn off on an Ubuntu Server install that's only ever going to be my instance of IRC?
[21:51] <mumixam> more than likely yes
[21:51] <mumixam> we dont know what options you did during install so its hard to say
[21:52] <carnophage2> Superlag, what are you thinking?
[21:52] <SuperLag> log in with OpenSSH, add keys from github. I didn't add anything aside from that.
[21:52] <mumixam> unless your system has low ram and slow cpu its likely not worth the effort
[21:53] <SuperLag> I had it at 2GB, then descreased it to 1GB
[21:53] <SuperLag> only one vCPU
[21:55] <jhutchins> SuperLag: Should be plenty, irc is a text app.  640K ought to be enough.
[21:55] <SuperLag> :D
[21:55] <jhutchins> Throw sysstat on it, see what's using what resources, tune from there.
[21:56] <SuperLag> actually, I think I'm barking up the wrong tree, looking at htop
[21:57] <SuperLag> load avg is nothing... it's another VM that's making the fan squeal. Got to figure out which one.
[22:01] <SuperLag> jhutchins: oh yeah, imagine that... cockpit-tls was the culprit. Restart cockpit systemd, and the CPU went silent again.
[22:18] <ayeye> hello!
[22:20] <jhutchins> ahoypaloy: Looks like everybody's out drinking beer and blowing things up.
[22:21] <jhutchins> ahoypaloy: Try switching to X (assuming you defaulted to Wayland).
[22:36] <kodachi> hello
[22:37] <Bashing-om> Welcome kodachi - Your support question ?
[22:50] <somerandomnick> I don't have the exact version, but somewhere between linux-image-5.4.0-104-generic and linux-image-5.4.0-107-generic, boot on Xen/ARM64 was broken.
[22:51] <somerandomnick> (I want to say it was broken with linux-image-5.4.0-105-generic, but I lost the note)
[22:55] <jhutchins> somerandomnick: Does your system preserve the older kernels?
[22:56] <jhutchins> (Also, if boot was broken, how did you update the kernels?)
[22:59] <somerandomnick> jhutchins: To some extent, I'm lot letting it remove linux-image-5.4.0-104-generic since that one is able to boot.
[22:59] <somerandomnick> ^lot^not
[23:11] <somerandomnick> Huh, "Focal update: v5.4.168 upstream stable release (LP: #1957991)"; "xen/console: harden hvc_xen against event channel storms" appears to be about the right time-frame.
[23:16] <oerheks> how about arm64+hwe ?
[23:16] <oerheks> !hwe
[23:16] <oerheks> it would bring 5.15?
[23:19] <physikoi> Hi #ubuntu. I'm lost in a proverbial forrest. I had setup my mac successfully to dual boot macos and windows. Recently, I decided to add another two partitions for ubuntu and swap. This worked too. However, when I tried to restart the computer, I could no longer boot windows. So, I followed some instructions about fixing a hybrid GPT/MBR into a 'protected mbr'. After doing that, the computer won't boot
[23:19] <physikoi> from anything: not refind, not macos, not windows, and not ubuntu. ATM, I do have the computer booted into Ubuntu trial mode from a usb stick. My question is this: is it possible to fix the partion tables so that the aforementioned are all bootable again without losing data? thanks
[23:24] <oerheks> i believe osprober, the tool to detect other os versions, is disabled
[23:24] <oerheks> for UEFI security reasons
[23:24] <oerheks> https://www.omgubuntu.co.uk/2021/12/grub-doesnt-detect-windows-linux-distros-fix
[23:25] <oerheks> jutst to make you aware, anoying imho
[23:26] <physikoi> oerheks: checking that out now. ty
[23:29] <physikoi> oerheks: not sure if related, but i just tried `fdisk -l` and it omits the "device" with windows,
[23:30] <physikoi> WRT that article, I can't actually boot unto the ubuntu partion either. I'm booted from an ubuntu usb in test mode
[23:30] <physikoi> I can confirm I'm working with release 22.04
[23:32] <oerheks> maybe an uefi issue too, windows not in uefi, ubuntu in uefi..
[23:32] <oerheks> !uefi
[23:36] <physikoi> Is this to say that I can't use ubuntu usb drive to fix my boot woes? The article does mention something called `boot-repair`, which I've started downloading
[23:43] <somerandomnick> For all the problems with ACPI one should admit it does generally work and is mostly OS-independent; this is rather superior to device-trees for which the working cases are rather more notable than the non-working cases.