[00:03] <DarkenedGentlema> Does Ubuntu 22.04 not have ssh key support enabled by default?
[00:03] <DarkenedGentlema> does the ssh-server not have key auth enabled by default?
[00:03] <sarnold> can you rephrase your question?
[00:04] <DarkenedGentlema> thru my key into authorized_keys and it loosk like it's not using it.
[00:04] <tmus> it's enabled by default. check user, file permissions etc
[00:05] <DarkenedGentlema> Also this is in the sshd_config #PubkeyAuthentication yes
[00:05] <DarkenedGentlema> commendted out
[00:05] <sarnold> DarkenedGentlema: is it perchance an old ssh-rsa key? those are disabled by default now https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668
[00:05] <DarkenedGentlema> ya, it's a older key, ssh-rsa
[00:06] <tmus> DarkenedGentlema, commented out but enabled by default
[00:06] <murmel> yes, but it shows you the default
[00:08] <sarnold> DarkenedGentlema: aha, nice; you can either configure the system to accept old keys again or generate a shiny new key
[00:08] <DarkenedGentlema> So is it just not supporting rsa keys anymore, or does it have to do with the key length?
[00:09] <DarkenedGentlema> I'd rather now have to update hundreds of servers with a new key, anyway to "upgrade" my old key so that it works on old and new?
[00:11] <DarkenedGentlema> ssh-keygen still looks to default to an rsa key.  I'm a bit confused here as to what's going on.  Is it just key length?
[00:11] <sarnold> you can stuff a Host ... HostkeyAlgorithms +ssh-rsa  PubkeyAcceptedAlgorithms +ssh-rsa  match block into your client configuratoin to allow you to connect to servers that are too old
[00:13] <DarkenedGentlema> Must be key length because the rsa key i just generated worked fine.
[00:15] <sarnold> it might be, I thought it was the specific hash choice, heh
[00:17] <murmel> sarnold: release notes say that rsa is disabled :/
[00:19] <murmel> ahh reading the release notes of openssh, it talks about sha-1 being disabled
[00:19] <sarnold> > The available RSA signature variants are “ssh-rsa” (SHA1 signatures, not recommended), “rsa-sha2-256”, and “rsa-sha2-512” (the default).
[00:20] <sarnold> https://man.openbsd.org/ssh-keygen
[00:22] <linext> tomreyn, https://i.ibb.co/3SFhfBf/image.png
[00:24] <sarnold> linext: namei -l /home/jesse/Downloads/kisslicer_linux64_1.6.3_release/KISSlicer  might explain something
[00:25] <linext> https://i.ibb.co/bbffsng/image.png
[00:27] <sarnold> linext: note the permissions on /home/jessie would prevent a process executing as www-data from getting to the file
[00:28] <linext> can i grant access to www-data?
[00:28] <linext> chown ?
[00:30] <sarnold> you can either chmod the directory to allow the world read and execute access; you can use setfacl to add read and execute permissions specifically for www-data (or whatever process is executing); there's other choices but these are least likely to be disruptive
[00:35] <linext> hmmmm...
[00:36] <linext> i still get permission denied
[00:37] <sarnold> if you execute KISSlicer in the shell by hand, does it execute fine?
[00:37] <linext> yep, the command runs as my user
[00:39] <linext> does php on linux come with exec() and proc_open() turn on by default?
[00:39] <linext> this is the command
[00:39] <linext> https://ibb.co/p1d8XK3
[00:39] <linext> here's the code: https://ibb.co/vCNqHkq
[00:40] <sarnold> man these are fuzzy, I hope your view is way less fuzzy :)
[00:40] <linext> click the image to zoom in
[00:41] <sarnold> so, ahhh enable a bunch of JS and the it'll load a better version, thanks
[00:41] <linext> https://i.ibb.co/SDkyPBy/image.png
[00:41] <sarnold> MUCH BETTER
[00:41] <ladeda> I am running into a really strange issue on Ubuntu 20.04 I have a local repo I use with trusted=yes set yet when I run apt it errors "The following signatures couldn't be verified" but it should not be doing this step I have verified this repo doesn't exist any where else it's only in a single place and does have the trusted option set. I try the
[00:41] <ladeda> debug options i.e. Debug::Acquire::gpgv=true and Debug::pkgAcquire::Auth but I am not seeing any useful information. Anyone ever run into this issue before?
[00:42] <sarnold> so, I think there's a few possibilities -- first, that -o /home/jesse/.../3003.gcode sure looks like an output file. that means the /home/jesse/.../ directory needs to allow this user to WRITE to the directory
[00:42] <sarnold> or, better yet, store the output someplace that it can write to already
[00:43] <linext> like /var/www/html/
[00:44] <sarnold> the other thing that I wonder about -- the arguments to commands almost always need to be separated a bit more than these -- the '-o' should be a different array entry than the filename. quoted names usually screw up things to. maybe all that implode business means it's just building a string to hand to bash.. the 2>&1 sure suggests that's what's going on
[00:44] <linext> the php code is solid
[00:44] <linext> i'm already running it in Windows
[00:44] <murmel> arraybolt3[m]: man, sbuild-qemu doesn't work with ubuntu :/
[00:45] <linext> i'm trying to diagnose a bug in KISSlicer to tell if it's OS specific
[00:45] <arraybolt3[m]> murmel: Bummer.
[00:46] <murmel> arraybolt3[m]: still not sure why, as it can't find ifupdown (which is in universe, and I enabled this)
[00:46] <arraybolt3[m]> Sadly I only use just plain sbuild, so sbuild-qemu is foreign territory to me.
[00:46] <arraybolt3[m]> (And I use sbuild on Ubuntu, so sbuild on Debian is also foreign to me :( )
[00:47] <murmel> arraybolt3[m]: yeah, almost thinking about switching to ubuntu as the host OS, but I quite don't like it that I am being forced basically
[00:47] <arraybolt3[m]> murmel: Then don't do that. Install Lubuntu in a virt-manager VM and everything should just work.
[00:47] <kushal_kumaran> linext: why involve php in this? You could just run that command on the shell, if that's all you need.
[00:47] <murmel> would rather go ubuntu-server, will still think about it
[00:48] <arraybolt3[m]> murmel: Once you're running sbuild within the VM, you can use the Ubuntu version of sbuild while still having Debian on your hardware.
[00:48] <linext> kushal_kumaran, it's a web app
[00:48] <linext> the version 2 of 3dpartprice.com
[00:48] <linext> calculates time and material for printing STL files
[00:50] <sarnold> hmm, why does systemctl start-service mirror-rsync.service *hang* my shell when I run it? I thought the point of a service manager was to go off and do something useful rather than hang the shell. my service file: https://termbin.com/ehsg
[00:51] <kushal_kumaran> linext: thanks for the info. So are you specifically trying to debug the behavior when run through web? If so, then create a directory that is readable and writable by the www-data user and point your file paths to that directory. Also if you can, do show the error logs from the web server.
[00:51] <arraybolt3[m]> sarnold: For me, systemctl can always hang my shell, sometimes for a while. Maybe there's a systemctl switch to do it asynchronously or something.
[00:51]  * arraybolt3[m] looks
[00:52] <arraybolt3[m]> sarnold: https://askubuntu.com/questions/1004853/systemd-is-hanging-when-i-start-or-restart-a-service
[00:53] <arraybolt3[m]> sarnold: Use Type=simple rather than Type=OneShot.
[00:55] <sarnold> arraybolt3[m]: hmm now I wonder why I went with oneshot in the first place
[00:55] <kushal_kumaran> linext: I just looked back through your previous messages. Try switching to the www-data user in a shell and trying your command. You might need to set a shell for that user
[00:55] <sarnold> arraybolt3[m]: this isn't a persistent process, it should just execute for half an hour or something, then go away again for a few hours
[00:56] <arraybolt3[m]> sarnold: Then it will probably freeze your shell for half an hour. :)
[00:56] <murmel> sarnold: wouldn't a timer be more reasonable?
[00:56] <arraybolt3[m]> sarnold: If it's something that executes every few hours, perhaps you should shell script it with a timer like murmel suggests?
[00:56] <arraybolt3[m]> murmel: You beat me to it!
[00:57] <murmel> ha :) finally my newly acquired mechanical keyboard pays off
[00:57] <sarnold> arraybolt3[m], murmel, here's the timer that fires it https://termbin.com/ehe5
[00:58] <arraybolt3[m]> sarnold: Also using Type=simple will leave the service dead when it finishes, so if you're ok with that I don't see why Type=simple would be bad.
[00:58] <arraybolt3[m]> sarnold: Also why use systemd at all? Wouldn't a cron job be more suited for this?
[00:59] <sarnold> arraybolt3[m]: yes, a cronjob would have saved me about two hours of getting this thing set up :)
[00:59] <sarnold> arraybolt3[m]: but it's been working more or less for a few years, and saving all the logs in the journal, which is pretty handy
[00:59] <murmel> arraybolt3[m]: doesn't really matter :) and honestly I would rather have everything managed by systemd
[00:59] <sarnold> I think I'd rather it be managed by systemd, I just wish systemd weren't such crap
[00:59] <arraybolt3[m]> Eh, valid point.
[00:59] <kushal_kumaran> sarnold: --no-block
[01:00] <sarnold> kushal_kumaran: hey! I bet that'd do the trick
[01:00] <arraybolt3[m]> Oh. Welp, that should do it.
[01:01] <sarnold> kushal_kumaran: funny, I can't recall ever seeing that before, but there it is. once again: dear system, why is this seemingly-sane thing not the default and such a loooooong name? :)
[01:01] <sarnold> if this rsync ever finishes..
[01:01] <murmel> hm, I still believe that OneShot should be the correct Type
[01:01] <InPhase> sarnold: This sounds like a job for crontab.
[01:02] <arraybolt3[m]> murmel: Yeah, you're not wrong, but when the thing lasts that long...
[01:02] <murmel> sure
[01:02] <murmel> sarnold: how big is the mirror? at least for 22
[01:02] <murmel> 22.04
[01:02] <arraybolt3[m]> OK, so asking a systemd question will also cause an explosion of opinions. /me adds that to the list of One Hundred and One Ways to Explode an Ubuntu IRC Channel
[01:03] <sarnold> arraybolt3[m]: lol
[01:03] <InPhase> sarnold: It just so happens I have a job running every 4 hours, crontab entry like:  0 */4 * * * /path/to/the/script   It works fine.
[01:04] <InPhase> sarnold: Rather than a mystery spacing of 4 hours and unspecified time of run, I know exactly when it launches based on time of day.
[01:04] <murmel> sarnold: the more I read, simple _is_ the correct
[01:05] <murmel> I quite like that post https://trstringer.com/simple-vs-oneshot-systemd-service/
[01:05] <sarnold> murmel: I rsync the whole thing, not just one release; I'm apparently around 2TB at the moment:
[01:05] <sarnold> $ zfs list srv/mirror/ubuntu
[01:05] <sarnold> NAME                USED  AVAIL  REFER  MOUNTPOINT
[01:05] <sarnold> srv/mirror/ubuntu  2.01T  5.66T  1.63T  /srv/mirror/ubuntu
[01:05] <kushal_kumaran> Using crontab for long jobs is doable. Read the man page for flock though, and consider using it. The chronic utility is also useful, and you might want to investigate an external dead man switch type monitoring solution
[01:05] <arraybolt3[m]> sarnold: Yikes, are you running a whole Ubuntu mirror?
[01:06] <sarnold> kushal_kumaran: yeah, the whole need to use run_one or run-one or whatever, and deal with appending the output, and preventing cron from *actually* sending email, etc, was enough for me to think that I ought to try systemd timers
[01:06] <sarnold> arraybolt3[m]: yeah
[01:07] <murmel> sarnold: welp, somebody really wants _all_ the debs
[01:07] <InPhase> sarnold: Cron won't send emails if you just dump stdout and stderr to /dev/null or to a log file.
[01:07] <arraybolt3[m]> sarnold: Cool. Does that actually help the Ubuntu project? I thought about doing that at one point.
[01:08] <sarnold> murmel: heh, I've even asked the archive admins if it'd be possible to get a single "combined view", with ports.ubuntu.com and archive.ubuntu.com on *one* filesystem -- like it is on the internal archive -- but sadly the only thing publically exposed is split in two :(
[01:08] <murmel> arraybolt3[m]: it does, as long as it's public
[01:08] <murmel> :/
[01:08] <sarnold> arraybolt3[m]: I run full archive searches on mine, unpack all the sources to have all the source files in plocate, etc. it's a bit odd :)
[01:08] <murmel> sarnold: that's weird. why wouldn't they combine it :/
[01:09] <sarnold> murmel: because it's work to make it happen and I'm currently the only one nutter enough to want it :)
[01:09] <murmel> sarnold: saying nothing against it. would love to have a mirror always with me
[01:09] <sarnold> they've offered to punch me a hole through the firewall before but I don't want the VPN on that machine
[01:11] <murmel> arraybolt3[m]: maybe i should add, that it also helps when not public, as you would run a mirror when you have multiple systems -> less traffic for the project
[01:12] <sarnold> most people would probably be better served with a squid-deb-proxy on their network
[01:12] <arraybolt3[m]> murmel: Makes sense. I guess it depends on how many systems you're running - when the total bandwidth of a single upgrade operation approaches the size of just pulling the whole archive, it's time to think about running a personal mirror.
[01:13] <murmel> arraybolt3[m]: for example
[01:14] <InPhase> How much traffic would the rsync be transmitting every 4 hours just to check for updates on all 2TB of that?
[01:14] <murmel> InPhase: afaik not that much, as it's checking hashes
[01:14] <InPhase> Must be a lot of files though.
[01:15] <murmel> definitely
[01:15] <sarnold> here's a run from a few days ago https://termbin.com/1b7m
[01:15] <InPhase> If I learned it was 20GB, I wouldn't be too shocked.  :)
[01:15] <kushal_kumaran> In default configuration, rsync only compares file sizes and mtime AFAIK.
[01:16]  * arraybolt3[m] realizes I way overestimated when it would be time to set up a personal mirror - if you're running enough computers to download nearly 2 TB in a single update you're already WAY past the point of needing your own mirror
[01:16] <murmel> I always like the bytes/sec :S
[01:18] <InPhase> sarnold: Is that a full run there, showing about 1.5GB of traffic to do the check across 13 minutes?
[01:19] <InPhase> sarnold: Oh, I guess more than checking.  It shows changes there.  So the checking was some amount less.
[01:20] <sarnold> InPhase: yeah, that's both phases of a two-phase copy https://termbin.com/p8ht
[01:20] <sarnold> my machine has been off for the weekend (it's too stupid hot here these days) and it ran for 28m42s before giving me the prompt back :)
[01:20] <murmel> InPhase: you see with the second run is only a few hundred megs
[01:21] <InPhase> arraybolt3[m]: Well bandwidth is still cheap compared to disks, so it takes a lot of such updates before the mirror system pays for itself.
[01:22] <InPhase> murmel: Am I supposed to believe that 6 second interval is a full check?
[01:22] <InPhase> Is the mirroring software using a special rsync setup that pre-stores the info on the files or something that the rsync would need to know?
[01:23] <arraybolt3[m]> InPhase: Yeah but using bandwidth is still sapping money away from Canonical and their helpers, so using tons of bandwidth would be detrimental to the Ubuntu project. Reducing bandwidth = reducing cost = keep the project alive! And so much the better if you donate bandwidth, which is what I wanted to do.
[01:23] <murmel> InPhase: idk the second run is almost 4 mins
[01:23] <InPhase> murmel: Oh, 2 minutes 8 seconds.  Eyes and math failed me both at the same time.  :)
[01:26] <InPhase> arraybolt3[m]: Agreed on those points.  Different group calculation there, but important.
[02:10] <DarkenedGentlema> in netplan's routes, can i specify a dev rather than IP?
[02:20] <jhutchins> !netplan
[02:21] <jhutchins> DarkenedGentlema: Maybe work directly with the filters/tables?
[04:56] <Hash> If you have a btrfs @ and @home/subvolume, and if you need to reinstall, and then how does it know to only install over @ and leave @home alone?
[05:18] <alkisg> Morning all; which package displays this dialog on apt upgrades? I'd like to remove it:
[05:18] <alkisg> > Newer kernel available The currently running kernel version is 5.4.0-122-generic which is not the expected kernel  version 5.15.0-43-generic.  Restarting the system to load the new kernel will not be handled automatically, so you should consider rebooting.
[05:24] <alkisg> I think it's an apt hook that got installed when I installed something related to ubuntu-advantage, esm etc, but when I removed these, it wasn't removed...
[05:29] <alkisg> Comparing /etc with another server that doesn't show that dialog, I see no related differences...
[06:47] <geirha> if it's terminal dialog boxes, it's likely whiptail
[06:50] <geirha> Mh, nevermind, I didn't read the problem thoroughly
[06:51] <alkisg> It's indeed whiptail but I didn't manage to find out what triggers it in one server (making apt full-upgrade annoying) and not on all the other servers
[07:05] <fawan> i got a question about asterisk and odoo voip connection
[07:05] <fawan> https://serverfault.com/questions/1107543/my-asterisk-server-cant-read-extensions-conf
[07:52] <Ecko> Hi, I'm getting the following message: "Unattended upgrade result: Lock could not be acquired"
[07:53] <Ecko> Now I see that /var/lib/dpkg/lock exists, but read that the lock file is there to stay permanently. So now I'm kinda lost on where to look on getting this fixed
[07:53] <Ecko> Can anyone point me in the right direction?
[08:03] <elias_a> Ecko: Is your root partition out of space?
[08:03] <Ecko> No, 40% used
[08:04] <elias_a> alkisg: Σας εύχομαι καλή μέρα!
[08:05] <alkisg> Καλημέρα elias_a :)
[08:05] <elias_a> Ecko: Are you using GUI or CLI?
[08:06] <Ecko> cli
[08:07] <elias_a> Ecko: Could there be another update process that is locking the file? Perhaps a GUI window lurking among the dozens of other windows? :)
[08:11] <Ecko> Not sure. Atleast no GUI, since it's a server. Already checked logfiles to see which processes are running, but can't quite find it yet
[08:13] <elias_a> Ok. I'm not that fluent with all the possible processes that might lock the file. Let's wait for answers from other users.
[08:14] <Ecko> sure, thanks for the help so far :)
[08:22] <elias_a> NP :)
[08:41] <sr-> is there a page that shows if/which version of mesa the next HWE stack (20.04.5) will contain? and also, I saw mentions of an "early preview" for those hwe releases. how can I opt in to those?
[08:42] <fouga> Hello everyone,
[08:42] <fouga>  I would like to fix issue with my ubuntu using kerberos (client).
[08:42] <fouga> "klist: Credentials cache keyring persistant not found"
[08:42] <fouga> Can someone help me please?
[08:42] <fouga> I have to do kinit everytime.
[08:42] <fouga> Thanks
[09:17] <seecrets> spyware OS
[09:17] <pony> they all are
[09:18] <seecrets> "they"?
[09:19] <pony> all oses
[09:19] <seecrets> what os do you use pony
[10:12] <circuitbone> he uses pwnyos but its a secret
[11:10] <ferz> Hi, on Ubuntu 20.04.4 LTS with one of last upgrade I'm not able to disable touchpad anymore using xinput.
[11:11] <ferz> http://paste.scsys.co.uk/483
[11:12] <ferz> I've tested using id 9 and someother without success
[11:14] <ferz> Please have you hint to achieve to disable touchpad.  It's a mess typing on keyboard while the pointer moves the cursor of text.
[12:33] <BluesKaj> Hi all
[13:25] <seecrets> pony i didnt see ur reply if you sent it
[13:25] <seecrets> what os do you use
[13:25] <seecrets> templeos?
[13:28] <leftyfb> seecrets: can we help you with something?
[13:29] <seecrets> yes, tell me what ubuntu is doing contacting snapcraft during installation
[13:29] <seecrets> and why does it have to check for connectivity so frequently
[13:30] <leftyfb> same thing it does checking the ubuntu deb repositories
[13:31] <leftyfb> seecrets: you do know that ubuntu desktop uses snaps by default for some applications now right?
[13:31] <seecrets> yes
[13:32] <leftyfb> then what is your concern?
[13:32] <seecrets> ubuntu provides spyware applications by default
[13:33] <leftyfb> seecrets: false. Feel free to go to #ubuntu-offtopic to rant though. This is a support channel
[13:33] <seecrets> so a browser that provides google as the default search engine isnt spyware
[13:33] <seecrets> https://imgur.com/a/YDi3xUT
[13:33] <seecrets> mind debunking this too
[13:34] <seecrets> so from what i can tell
[13:35] <seecrets> im telling someone everytime i install ubuntu
[13:35] <BluesKaj> oh lord, another troll looking for an argument...sigh
[13:35] <seecrets> and im telling someone everytime im using my ubuntu machine
[13:35] <seecrets> for the duration im using it
[13:35] <seecrets> im not trolling
[13:35] <leftyfb> seecrets: this isn't the place for your rants. Again, this is a support channel. Go to #ubuntu-offtopic
[13:36] <seecrets> okay
[14:45] <Pruners> I'm in Ubuntu, is there a way I can save an internet URL, to a desktop alias?
[14:50] <wez> Pruners: There is
[14:50] <wez> Pruners: https://www.google.com/search?q=ubuntu+url+launcher&oq=ubuntu+url+launcher
[15:45] <arkanoid> Hello! I'm installing ubuntu desktop 22.04 and I'm puzzled by the dropdown menu "device for boot loader installation"
[15:45] <leftyfb> arkanoid: pick your hard drive
[15:46] <arkanoid> Context: UEFI system, EFI partition already exists as sdb1, I've created a partire for /boot in sdb2
[15:46] <arraybolt3[m]> arkanoid: The program your computer loads when it first boots up is the bootloader. The bootloader is what then starts Ubuntu. That bootloader has to be located somewhere, that option tells the Ubuntu installer where you want to put the bootloader. It should be put on whatever drive you want the system to boot from.
[15:46] <arraybolt3[m]> With that context, the bootloader should go in /dev/sdb1 I believe.
[15:47] <leftyfb> arkanoid: is there a reason why you're manually creating partitions, especially boot?
[15:48] <arkanoid> leftyfb:  yes, I'm doing some quite convoluted operation (after backup of course). I start from a dual boot windows + ubuntu, I want to remove windows and get ubuntu + ubuntu, but new ubuntu has LUKS working. I will remove old ubuntu after moving everything
[15:49] <arkanoid> So I am replacing windows partitions at the beginning of sdb with /boot and encrypted device as /
[15:50] <arraybolt3[m]> arkanoid: Your system does use EFI, right?
[15:51] <arraybolt3[m]> (Asking because I know Ubuntu will create an EFI partition even on a BIOS system, and so whether your system is EFI or BIOS will influence where you probably want to put the bootloader.)
[15:51] <arkanoid> Current situation is: sdb1 EFI, sdb2 /boot (new ubuntu), sdb3 / (encrypted new ubuntu), sdb4 / (old ubuntu without separate boot partition)
[15:52] <arkanoid> System is UEFI, yes. I've started the installer from UEFI and uefivars is mounted in installer
[15:52] <arraybolt3[m]> arkanoid: OK, then the bootloader goes on /dev/sdb1.
[15:52] <imbezol> is there a way to disable the firefox snap update warning? says 13 days left to close it. problem is i close it, do a refresh, and then the next day there's another update. so this popup has become a part of my life every 5 minutes.
[15:53] <imbezol> i think i've closed that popup a thousand times
[15:53] <leftyfb> imbezol: it's a known bug they are working on
[15:53] <arkanoid> arraybolt3[m]:  what sdb2 /boot used for, then?
[15:53] <imbezol> super super annoying. i hope they fix it soon.
[15:58] <arraybolt3[m]> arkanoid: OK, so the bootloader has two parts.
[15:58] <arraybolt3[m]> arkanoid: There's an "early bootloader" that goes in the EFI partition.
[15:58] <arraybolt3[m]> arkanoid: Then there's the "rest of the bootloader" that goes in /boot and has things like extra modules for certain uses, along with the configuration file for GRUB.
[15:58] <arraybolt3[m]> arkanoid: Also the /boot partition holds the kernel and initramfs.
[15:59] <arraybolt3[m]> arkanoid: The early bootloader goes wherever you select as the boot loader installation device.
[15:59] <arraybolt3[m]> arkanoid: So you want GRUB to go in the EFI partition, /dev/sdb1. The system will autopopulate /dev/sdb2 with all the necessary extras (the rest of the bootloader) as well as other files critical to the boot process.
[16:01] <jhutchins> https://opensource.com/article/17/2/linux-boot-and-startup
[16:02] <arraybolt3[m]> (A similar process is used on BIOS systems, but the early bootloader and rest of the bootloader are somewhat different, though the same concepts still exist.)
[16:02] <arkanoid> arraybolt3[m]: thanks, it makes sense now. I have question then. What is generally called "stage 2 bootloader" is what runs from EFI partition or what runs from /boot?
[16:05] <jhutchins> arkanoid: That's one of the stages for Grub (or possibly other bootloaders).
[16:08] <jhutchins> https://www.linuxquestions.org/questions/linux-newbie-8/what-is-grub-loading-stage2-745986/
[16:09] <jhutchins> arkanoid: A /boot partition is a mistake that will sooner or later run out of space and not allow you to upgrade your kernel.
[16:09] <jhutchins> There is no reason /boot should be a separate partition.
[16:10] <jhutchins> On archaic multi-user systems, /boot was mounted separately and unmounted at runtime so that malicious usrers could not tamper with the boot files.
[16:10] <arkanoid> jhutchins: I've been reading that separate /boot is required for booting when root is behind LUKS
[16:11] <jhutchins> https://www.techeblog.com/5mb-hard-drive-being-loaded-onto-a-plane-in-1956-and-35-more-cool-historical-photos/
[16:12] <jhutchins> arkanoid: There is a way to have /boot encrypted, I don't mess with such things.
[16:12] <jhutchins> arkanoid: It does provide additional entertainment when things go wrong.
[16:12] <arkanoid> I have (not yet) secure boot enabled (this will be my final target). So the boot process is currently efi in sdb1 >  grub in sdb2 > boots only with decryption password (this is working  now)
[16:15] <jhutchins> arkanoid: The purpose of "Secure Boot" is to prevent you from booting Linux install media and installing Linux.
[16:16] <arkanoid> jhutchins:  yeah, no. Please. I know what root of trust is
[16:17] <arkanoid> I can understand how firmware flashers deliver tpm with pre-flashed ms$ keys, but this doesn't mean what you say
[16:17] <leftyfb> lets try to stay on topic here
[16:17] <arkanoid> jhutchins:  also, my (very old) previous ubuntu installation with no separate boot partition has a /boot folder of 286MB
[16:18] <arraybolt3[m]> arkanoid: Keep in mind that is very very small for modern-day Ubuntu systems. 4 GB would be a safer /boot size IMO.
[16:19] <jhutchins> arkanoid: Yes, the boot folder is part of a standard Linux system.
[16:19] <arkanoid> I'm still in time for re-installing ubuntu with larger /boot partition or without it, but I want encrypted root and smooth daily sail like I've been experiencing so far without luks
[16:19] <arraybolt3[m]> (I saw someone in here with a /boot that was about that small. It was... not fun.)
[16:19] <jhutchins> It's convenient to have all of the required boot files in the same place, rather than breaking them out by version like the libraries and drivers.
[16:20] <jhutchins> There are a few distributions that do that, a seperate file tree for each kernel and a symlink in / that points to that tree.
[16:21] <jhutchins> That symlink also exists on some more standard systems for compatibility.
[16:21] <arkanoid> Rhel uses separate /boot
[16:21] <jhutchins> arkanoid: If you mean a separate partition, that's optional there as well.
[16:23] <arkanoid> jhutchins:  by default, you have separate boot partition
[16:24] <arkanoid> I'd like to get some confirmation about: is it really a risk having separate boot partition of 512MB size? Is it really a risk having boot embedded in root while keeping root encrypted with luks?
[16:25] <arraybolt3[m]> arkanoid: I would keep /boot separate since it's what Ubuntu does by default.
[16:25] <arraybolt3[m]> arkanoid: I would give at least 1GB to the /boot partition so that you have breathing room if things go haywire, maybe even 2 GB.
[16:26] <arkanoid> arraybolt3[m]: official docs says 256 - 1GB, I went 512, but I will reinstall now https://help.ubuntu.com/community/DiskSpace
[16:26] <arraybolt3[m]> arkanoid: It is not a risk to have boot embedded in root while root is encrypted, but it does require that things be configured in just the right way. Ubuntu doesn't do it that way by default, though Lubuntu and Ubuntu Studio do. So it's possible, but I don't know how to do that.
[16:26] <arraybolt3[m]> (On stock Ubuntu I mean.)
[16:27] <arraybolt3[m]> Also, the docs are generally a good source of info, but they're also miserably outdated in some instances, and I wouldn't be surprised if this is one of those instances.
[16:28] <arraybolt3[m]> Yeah, I'm seeing a mention of Ubuntu 10.04 (?!) in that Wiki article. I should edit that to reflect modern versions of Ubuntu.
[16:29] <arkanoid> arraybolt3[m]: I don't want to step too far away from defaults. Separate unencrypted boot seems not an higher risk for me. I mean, I would need an evil maid that tampers the boot/kernel. I just want to stay safe if laptop got lost/stolen
[16:32] <arkanoid> ubuntu core uses unencrypted boot while calling it Full Disk Encryption with chain of trust base don TPM2.0 enabled https://ubuntu.com/core/docs/uc20/full-disk-encryption
[16:33] <jhutchins> In spite of good intentions, the kernel and boot files do keep growing.
[16:33] <leftyfb> arkanoid: ubuntu core != ubuntu desktop/server. Feel free to discuss Ubuntu core in #snappy
[16:33] <jhutchins> It's been a long time since you could boot a system off of one floppy.
[16:34] <arkanoid> jhutchins: my other ubuntu installation went from 16.04 to 22.04 with daily usage, and /boot is 286MB
[16:34] <leftyfb> arkanoid: lets stay on topic with support questions you need help with
[16:34] <arraybolt3[m]> arkanoid: Then you should be fine with a separate unencrypted boot.
[16:35] <arkanoid> leftyfb: sure, but it's still an indicator that while encrypted /boot is possible, is not done even when secure boot is enabled by default
[16:35] <jhutchins> leftyfb: The question is how much space is adequate for /boot.
[16:35] <arraybolt3[m]> Were you to ever find your laptop again, you'd probably want to wipe and reinstall, restoring your data from a backup, but just LUKS'ing root and leaving boot unencrypted will work fine from a data security standpoint.
[16:36] <leftyfb> jhutchins: apparently in their case, they believe 286MB is adequate and don't seem interested in anyone elses opinion
[16:36] <arraybolt3[m]> leftyfb: They're just making a point trying to reason about wwhat is and isn't secure.
[16:36] <arraybolt3[m]> leftyfb: They said they were going to reinstall to make a bigger boot partition.
[16:37] <leftyfb> arraybolt3[m]: if the discussion were to continue to it's conclusion, throwing the PC into a fire is the most secure
[16:38] <arkanoid> I'm not saying it's adeguate, I actually said the opposite: I will reinstall now and use 2GB for /boot. What I just wanted to point out, is that a very old and frequently updated ubuntu installation still has a clean /boot folder of 286MB, and also the official docs says 256Mb to 1GB of size recommended.
[16:38] <arraybolt3[m]> leftyfb: I do a lot of security stuff and I can understand his concerns (since I've had those same concerns). And I'm still using a PC.
[16:39] <jhutchins> Actual use of the computer is discouraged as a security risk.
[16:39] <arraybolt3[m]> arkanoid: True. And it will stay that way if everything goes perfectly well (though it will grow a bit and then shrink again). But when something unexpected happens and kernels start piling up... (I've had that happen to me a few times.) So that's why you want a good buffer of breathing room.
[16:40] <arraybolt3[m]> jhutchins: C'mon. I get where he's coming from. I don't know what he said that has you and leftyfb doing this to him, but please stop. It's not appreciated, especially as someone who's in the same boat.
[16:40] <arkanoid> arraybolt3[m]: thanks. I'm now curious when the piling up happens. Never happened in my experience. What takes update to save copies and copies of kernel versions / initrd images?
[16:40] <jhutchins> arkanoid: It's an old joke.
[16:41] <jhutchins> arkanoid: With the realease of 22.04 we've seen people here run into space limits with /boot partitions, so it's a valid issue.
[16:41] <arraybolt3[m]> arkanoid: If something occurs that makes a kernel marked as manually installed, it will then stay there and not get autoremoved. That will cause there to be at least one extra kernel laying around.
[16:42] <jhutchins> ... plus config and initrd.
[16:43] <jhutchins> Does Ubuntu do the root symlink to the boot files?
[16:43] <arkanoid> k, reinstalling with 2GB now. If everything goes well like previous go, I will end up with two ubuntu installs like now. The only "obscure point" here to me yet is how grub "detects" other OSs
[16:44] <arraybolt3[m]> arkanoid: There's a special config file that gets built by grub-mkconfig that tells GRUB where the other operating systems are and how to boot them.
[16:44] <arraybolt3[m]> That tool will automatically run during install time.
[16:44] <arraybolt3[m]> (However do note that only one OS will be detected in Ubuntu 22.04 since os-prober was disabled, there's a way to re-enable that if that's undesirable, but in your instance it sounds like it's just fine.)
[16:45] <arkanoid> the tools is detecting deleted windows as still present then. I guess because there are some leftovers in EFI (sdb1) partition?
[16:45] <arraybolt3[m]> arkanoid: Quite possibly. If you're OK with potentially rendering all operating systems except the one you're installing now unbootable, you could (maybe even should) wipe the EFI partition and make a new one.
[16:46] <arkanoid> arraybolt3[m]: no, I'm interested in having old ubuntu still working as before. This until I end my experiments with luks/secure boot on new installation
[16:47] <arraybolt3[m]> arkanoid: OK. Actually, in that instance, what I'd do is go ahead and wipe the EFI partition, and then we'll just re-enable os-prober to pick up the original installation.
[16:47] <arraybolt3[m]> (I'll link to the instructions on re-enabling os-prober.)
[16:48] <arraybolt3[m]> https://askubuntu.com/questions/1410398/just-installed-ubuntu-22-04-on-a-dual-boot-setup-now-my-other-os-isnt-showing
[16:49] <arkanoid> arraybolt3[m]: I'm puzzled. If os-prober is disabled in 22.04, why I have grub showing 3 OSs (deleted windows, old ubuntu, new ubuntu with encrypted root) after the operation of deleting windows partitions to install new ubuntu?
[16:49] <arraybolt3[m]> arkanoid: Are you using Ubuntu 20.04?
[16:50] <arkanoid> no, 22.04
[16:50] <arkanoid> both old ubuntu installation and new ubuntu installation are ubuntu 22.04
[16:50] <arraybolt3[m]> Hmm... then you might be looking at your UEFI boot menu and not GRUB. Does the bootloader say "GNU GRUB" up at the top?
[16:51] <arkanoid> well, let me reboot to double check, but yeah I am quite sure. 1 minute
[16:52] <arraybolt3[m]> Maybe it's still picking up stuff from the EFI partition but not mounting things from other partitions then. I dunno.
[16:52] <arkanoid> I confirm GNU GRUB at boot with 3 OS options
[16:53] <arkanoid> Well whatever it is doing, it is making things work out of the box. Let's see what happens now that I'm going to reinstall new ubuntu ...
[16:54] <arkanoid> What should happen in EFI if I have more than one ubuntu installation on same system? Should I have one or two grub entries there?
[16:55] <arkanoid> I currently have EFI folder with Boot, Microsoft and ubuntu subfolders
[16:59] <arkanoid> The EFI/ubuntu/grub.cfg points to blkid of sdb2, so /boot of new ubuntu.
[16:59] <arkanoid> It means that os probe is working somehow on 22.04 as it detected all 3 OSs on installation
[17:00] <arkanoid> Let me double check in /boot/grub.cfg of newly installed Ubuntu if it matches the boot entries
[17:02] <arkanoid> Yep, I confirm /boot/grub/grub.cfg of newly installed Ubuntu contains entries for previously installed OSs, so probing is working
[17:04]  * ogra notes that there is no unencrypted /boot in Ubuntu Core systems that use secureboot with full disk encryption ... (and there is no way to have either/or, they only go together)
[17:10] <arg_> anyone using ubuntu on the HDMI TV sticks like the 1 from aliexpress, they say its ubuntu compatible, but it runs windows natively, just to hear how it runs, they have 2 and 4GB version.
[17:11] <arg_> sort of like the arm android tv sticks but its x86-64.
[17:11] <arg_> size of a usb stick.
[17:11] <leftyfb> arg_: https://ubuntu.com/certified
[17:11] <leftyfb> arg_: for anything else, you would just have to try it
[17:16] <arg_> leftyfb: yeah they are not branded things tho, i'm gonna hack 1 out to bring back a ubuntu phone competitor to the pine64. With a tiny hdmi touchscreen lol ;]
[17:16] <arraybolt3[m]> arkanoid: Hmm, not sure why it's picking them up then. I don't know if it's to be expected or not.
[17:16] <leftyfb> arg_: good luck
[17:18] <forgotmynick> i have rsyslog listening on a socket. how do i send test entries to that socket?
[17:19] <sarnold> forgotmynick: try logger
[17:21] <forgotmynick> sarnold: i love you
[17:22] <sarnold> forgotmynick: <3  :D
[17:27] <arkanoid> arraybolt3[m]:  I can confirm after reinstalling ubuntu plus deleting old EFI partition and recreating from scratch that the installer creates a grub config that permits loading old ubuntu install and all "advanced" sub options
[17:28] <arraybolt3[m]> Hmm. Maybe they changed something... though I'm not sure how that would make sense. Well, woot! Glad it's working, now I have one more thing confusing the sap out of my brain! 🤪
[17:44] <Hash> Hi
[17:44] <Hash> What is ~/.xtoolkit used by?
[17:47] <tomreyn> If i had to guess, i'd say the X Toolkit
[17:47] <leftyfb> I do not see that file mentioned anywhere having to do with ubuntu
[17:48] <leftyfb> the only thing I can find is a 3rd party tool not included in ubuntu called incubator-weex-cli
[17:50] <leftyfb> maybe week-tookit npm package
[17:50] <Hash> I thought that too, but it seems to have some node packages in there...
[17:50] <leftyfb> sorry, weex-toolkit
[17:50] <Hash> Isn't X toolkit just x libs and stuff? What what that have to do with node/npm
[17:51] <leftyfb> right, it's probably related to some npm package you installed
[17:51] <Hash> Unless it's like that intel cross platform mobnile app dev toolkit I might have instaleld once
[17:51] <Hash> \o/
[17:51] <leftyfb> ah right, Hash has me on ignore so didn't see any of this
[18:01] <sarnold> leftyfb: lol that's got to save a huge amount of time :)
[18:28] <skullone_> Is there a way in preseed to change the partman options to modify XFS filesystem format options? (ie. turn off reflinks, or other custom oddities)
[18:45] <tomreyn> skullone_: i don't know your answer, if the question refers to ubuntu desktop (it seems to). i also don't know your answer if the question would also extend to ubuntu server (which can be converted into a desktop installation), but assume you may have more options with subiquity + autoinstall (via curtin)
[19:40] <Beherit> BluesKaj: Hi !
[19:40] <arraybolt3[m]> Beherit: 👋
[19:41] <Beherit> hi array!
[19:41] <Beherit> first signs of life! hah!
[19:41] <arraybolt3[m]> Beherit: Anything we can help you with?
[19:41] <Beherit> been years since i actually used the MIRC , just logged in as an opportunity when i was sorting out thunderbird.
[19:42] <Beherit> no arraybolt, thanks. just saying hi.
[19:42] <arraybolt3[m]> Nice. If you ever run into anything that goes wrong with your Ubuntu system, feel free to ask for help here. Also, if you're interested in general conversation, we have #ubuntu-offtopic:libera.chat.
[19:43] <Beherit> ah Thank you!!
[20:08] <murmel> arraybolt3[m]: may I pm you?
[20:08] <arraybolt3[m]> murmel: Yeah, sure. Matrix preferred, IRC will work too but I might be slow.
[20:57] <murmel> is there a reason why ubuntu removes the rootless install script from docker.io?
[20:57] <murmel> can't find anything about it
[20:58] <de-facto> why is ctrl alt backspace not killing Xorg in Ubuntu?
[21:00] <leftyfb> de-facto: pretty sure that was removed years ago
[21:01] <de-facto> why would one remove such a useful thing?
[21:01] <de-facto> gnome shell freezes from time to time, so it would be useful to be able to kill it
[21:02] <leftyfb> de-facto: you should be focusing more on the freezes and less the workaround
[21:02] <murmel> yeah it's definitely not normal that gnome freezes
[21:03] <de-facto> it never was stable for me, so i got used to it freezing from time to time
[21:04] <de-facto> same with pulseaudio, it just corrupts from time to time, so killing it solves the issue with both
[21:05] <de-facto> was Ctrl Alt Backspace completely removed or just diabled?
[21:06] <leftyfb> de-facto: a quick google search shows it was "disabled" 13 years ago https://www.linuxjournal.com/content/tech-tip-restore-ctrl-alt-backspace-ubuntu
[21:07] <gordonjcp> yeah
[21:07] <gordonjcp> ctrl-alt-backspace to "zap" X hasn't been a thing for years
[21:08] <leftyfb> de-facto: are you running Ubuntu 20.04 or 22.04 and gnome is still freezing for you?
[21:08] <de-facto> 22.04
[21:09] <leftyfb> de-facto: is gnome freezing up on you?
[21:09] <de-facto> yeah its freezing from time to time
[21:09] <leftyfb> de-facto: is this a fresh install of ubuntu or have you been upgrading since 2009?
[21:10] <de-facto> fresh
[21:10] <leftyfb> de-facto: ok, maybe file a bug or ask someone here for help troubleshooting the issue
[21:10] <de-facto> i just assumed that gnome shell is not really stable yet
[21:10] <de-facto> yeah i just want ctrl alt backspace
[21:10] <de-facto> i dont want to dig into Xorg, thats too crazy
[21:11] <de-facto> they disabled it because users could "accidentally trigger it" lol
[21:11] <de-facto> aha, hmm
[21:11] <leftyfb> de-facto: you'll probably need to dig into "Xorg" (not the default unless you have Nvidia) in order to write the code back in to give you your workaround for a problem you aren't interested in getting resolved
[21:12] <leftyfb> btw, gnome shell was released 11 years ago
[21:13] <de-facto> yeah still not stable for me, sorry, but its how it is
[21:16] <leftyfb> de-facto: your issues could be related to bad memory, cpu, gpu, overheating, wrong drivers installed, faulty software installed or lack of resources. Since you don't know or are interested in resolving the issue, it's not yet valid to say gnome shell isn't stable
[21:20] <de-facto> all problems observed could be caused by such generic implied causes, to me gnome shell freezes from time to time, so thats an observation, hence it is not stable for me, what is the cause? i do not know, but i want to be able to kill it when it freezes
[21:20] <leftyfb> de-facto: wouldn't you prefer it not happen?
[21:21] <de-facto> yes i can buy a new pc, debug xorg on both my old and the new pc and compare, or i just could kill it and continue with what i do
[21:24] <de-facto> found it
[21:24] <de-facto> gsettings set org.gnome.desktop.input-sources xkb-options "['terminate:ctrl_alt_bksp']"
[21:36] <de-facto> nice it works, should be enabled by default in my opinion, very useful and widely known
[21:43] <ogra> given it has been disabled in most distros a decade and more ago, i wonder if it is actually still known at all by general users
[22:01] <Zenexer> I'm seeing that 22.04.1 was delayed until Aug 11.  However, all of my systems seem to already be on 22.04.1.  Anyone know what that's about?
[22:04] <leftyfb> Zenexer: only the 22.04.1 image releases have been delayed. You are running 22.04.1
[22:04] <Zenexer> Got it.  Does that have anything to do with apt dist-upgrade holding back python3-distupgrade and ubuntu-release-upgrader-core?
[22:05] <leftyfb> no
[22:05] <leftyfb> well, not sure about the last package
[22:05] <Zenexer> Hmm
[22:05] <leftyfb> well, maybe both
[22:06] <leftyfb> it's only a couple more days. Those shouldn't affect you though
[22:06] <Zenexer> I'm getting weird apt behavior.  The repos all seemed to be down for about 15 minutes, and now that they're back, apt list --upgradable shows both of those packages are ready to upgrade, but dist-upgrade doesn't want to go through with it unless I explicitly pass those two packages as args.
[22:06] <oerheks> the fix is to install ubuntu-release-upgrader-core, it pulls in the other 2 ?
[22:06] <Zenexer> Yeah, just making sure I'm not going to mess anything up by upgrading (or not upgrading)
[22:07] <leftyfb> you could just wait a couple days if you want to be safe
[22:07] <Zenexer> Seems like any systems that ran apt update shortly prior to the outage are affected, whereas any systems that waited until after are able to upgrade without issue.  I don't think I've ever seen that before.
[22:08] <oerheks> i had that issue too, the single package install fixed it
[22:09] <Zenexer> Yeah, it seems to be upgrading fine on other systems, so I just went ahead and upgraded.  Guess I'll just ignore it.
[22:09] <leftyfb> Zenexer: I just ran a full-upgrade, both of those packages installed just fine but snapd was held back. Which I'm ok with just leaving till it's not held back anymorw
[22:18] <oerheks> oh, it is something about phased updates .. i am not one of them
[22:18] <oerheks> https://askubuntu.com/questions/1420969/how-to-force-packages-that-have-been-kept-back-to-be-installed-as-automat/1421130#1421130
[22:35] <PReTeXTATo> Canonical has plans to launch Ubuntu for VisionFive Board V1 Model?
[22:42] <sarnold> heh, the release notes of the next release are mighty thin still https://discourse.ubuntu.com/t/kinetic-kudu-release-notes/27976
[22:47] <ogra> PReTeXTATo, https://discourse.ubuntu.com/t/ubuntu-on-the-visionfive-and-the-nezha-boards/29858
[22:52] <PReTeXTATo> THanKs.
[23:01] <junebug> I'm trying to get this crontab to run on reboot but no luck: reboot /home/myhome/bin/disable_touchscreen && echo "disabled touchscreen" >> /home/myhome/startup
[23:01] <junebug> using @reboot
[23:02] <sarnold> junebug: try: namei -l /home/myhome/bin/disable_touG
[23:03] <junebug> sarnold, you mean @reboot myname -l /my/command?
[23:03] <sarnold> junebug: no, run namei -l /home/myhome/bin/disable_touG   at a shell prompt right now -- my guess is that file, or a directory above it, has incorrect permissions
[23:03] <junebug> Oh ok
[23:04] <junebug> X for everyone
[23:05] <junebug> I'm on Ubuntu 20.04.4 LTS if that helps
[23:07] <sarnold> murmel: hey! I finally got around to reading that https://trstringer.com/simple-vs-oneshot-systemd-service/ article and it nails *exactly* why I picked oneshot rather than simple! the follow-up units wait until the oneshot finishes before they start
[23:07] <sarnold> junebug: and can the user in question also read the script?
[23:07] <junebug> yes
[23:08] <junebug> user writing the crontab -e is me
[23:08] <junebug> I have rx on all directories and rwx on the files
[23:08] <sarnold> junebug: okay.. the next usual problem with cronjobs is the PATH is quite a bit more restricted than usual -- take a look at the script and make sure that the shebang line is correct, make sure that every single executable that is used is in /bin or /usr/bin  or has an explicit path
[23:11] <junebug> sarnold, yes every executable in the script is in the /bin  or /usr/bin directory
[23:13] <sarnold> junebug: hmm, okay, a good challenge then :) check your mail? cron mails stderr output, maybe you've got a friendly error message saved in a spool file
[23:14] <junebug> sarnold, what is the command to check cron mail?
[23:14] <sarnold> junebug: it depends upon your system's email configuration
[23:15] <sarnold> junebug: /var/spool/mail/junebug maybe? or if you've got a working mail server on the system, maybe it goes somewhere else..
[23:15] <junebug> I don't use email...
[23:16] <junebug> I just saw this in the cron.d folder. I think it's an example:
[23:16] <junebug> SHELL=/bin/sh
[23:16] <junebug> PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
[23:16] <junebug> 8 0 * * *   root    test -x /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest --crond
[23:16] <junebug> Do I need to set the shell and the user?
[23:21] <junebug> nah that didn't work
[23:24] <sarnold> junebug: it depends upon the specific crontab -- the "system" crontabs often do require a user name
[23:25] <junebug> man cron reveals my system is using cron 8. I do a /reboot and don't find reboot anywhere in the manual
[23:26] <junebug> But I do see @reboot in man crontab which is crontab 5
[23:27] <sarnold> are you sure you're checking the right section? ± MANPAGER=cat man 5 crontab | grep reboot
[23:27] <sarnold>               @reboot        Run once, at startup.
[23:27] <junebug> Yeah I see it in crontab but not cron
[23:28] <junebug> So here's the thing
[23:28] <junebug> I know @reboot works
[23:28] <junebug> Because I can do @reboot echo "hello" >> /my/home/somefile
[23:28] <junebug> And it's there
[23:28] <junebug> It just doesn't like the script or how I'm calling the script
[23:29] <sarnold> can you run that script by hand fine?
[23:29] <junebug> Yes
[23:29] <junebug> I run it every time I start up my computer
[23:33] <sarnold> maybe instead of trying to find error output, try redirecting the output to a file? @reboot /home/myhome/bin/disable_touchscreen > /tmp/out 2>&1   ?
[23:33] <junebug> Smart
[23:33] <junebug> let me try that
[23:35] <joke> sarnold: hehe you are everywhere
[23:36] <sarnold> ayup :) heya joke
[23:38] <junebug> sarnold, I see this printed twice: Unable to connect to X server
[23:38] <sarnold> junebug: aha!
[23:39] <junebug> Should I add sleep 120?
[23:40] <sarnold> you'll also need to supply the XAUTHORITY and DISPLAY environment variables to it to connect to the running X. it'd probably be easier to just move the script to an X11 autostart service
[23:40] <sarnold> most desktop environments have an autostart thingy
[23:40] <junebug> ok let me google that
[23:40] <junebug> Thank you