[00:03] <MonoL> Oh man I got it to run but I have no idea what I'm doing
[00:04] <MonoL> It's like I have to start conda environments and then install things and run from within them
[00:05] <MonoL> Dam it I wish I wasn't born dumb as a bag of hammers
[00:05] <Guest70> its working though, rite?
[00:05] <MonoL> yee
[00:06] <MonoL> but I don't want to ruin any programs that might depend on python
[00:08] <MonoL> I don't really know what I'm talking about but I think people setup walled environments in python to stop you from messing around with other programs that might depend on the python base install
[00:10] <Guest70> maybe join #python
[00:11] <MonoL> I could be pulling this info from thin air.. It's just what I've kinda gathered from my limited cognitive ability
[00:11] <MonoL> yeah
[00:12] <MonoL> If I wasn't so dumb I'd probably have joined #python first lel
[00:12] <MonoL> Sorry everyone
[03:15] <fabio_> hi
[04:33] <soreau> Hi, I'm on 22.04. How can I disable the notifications about snap upgrading firefox and chromium via cli?
[04:40] <Bashing-om> soreau: So far as I am aware - ^ -- a works in progress: https://ubuntu.com//blog/snaps-better-refresh-notifications
[04:42] <bougyman> soreau: uninstall snap.
[05:58] <lotuspsychje> bougyman: plz dont advice users to uninstall snap, its a part of ubuntu now
[07:49] <Chipzzz> quit
[07:52] <Chipzzz> quit
[08:30] <lux> hhi
[08:31] <lux> hi guys
[08:31] <murmel> hi lux
[08:31] <lux> hi
[08:31] <lux> how are you doing
[08:34] <murmel> !support | lux
[08:34] <murmel> eh
[08:34] <murmel> !offtopic | lux
[09:31] <ksy> !help
[09:31] <lotuspsychje> what can we do for you ksy
[09:34] <ksy> lotuspsychje: thank you. I just tried the help command to see what the bot can do
[10:04] <elwisp> pending update on discord snap, every day i get this notification several times, how do i get rid of it?
[10:04] <elwisp> it tells me to restart discord, and i have, i have even restarted the machine
[10:07] <ogra> elwisp, the notification is buggy (being fixed atm) and should tell you to stop the app and run "sudo snap refresh" ...
[10:08] <ogra> make sure to refresh the app manually while it is not running and the notification will go away
[10:19] <alkisg> Upgrading my 20.04 server to 22.04 removes the ldap-account-manager package. Upgrade logs: https://termbin.com/k00f
[10:19] <alkisg> I have a snapshot I can retry the upgrade if I can find a way to avoid it. Maybe installing php-json beforehand will help the apt resolver there?
[10:25] <elwisp> ogra: what does refreshing the app manually mean?
[10:25] <elwisp> because i have tried sudo snap refresh already
[10:25] <elwisp> i shall try again, perhaps i left it running that time
[10:26] <elwisp> I think that did it
[10:26] <elwisp> time iwll tell, thanks for the help ogra
[10:49] <alkisg> Indeed `apt install php-json` before `do-release-upgrade` worked around the issue
[11:53] <manwhowouldbekin> Hi all! I am wondering if someone can help me figure out what packages or settings I am missing here? I am trying to install dependencies for a Python project on Ubuntu 22.04. One package called uWGSI fails to install with the following stacktrace: https://pastebin.com/sm5eKqBu
[11:55] <brkcore> manwhowouldbekin, have you tried first sudo apt update && sudo apt-get upgrade --fix-missing -y
[11:55] <manwhowouldbekin> brkcore, I have not.
[11:56] <brkcore> manwhowouldbekin, also try apt-cache depends package_name
[11:57] <murmel> manwhowouldbekin: additionally, why are you trying to install a software which is probably not maintained anymore (as the copyright says 2016)
[11:57] <manwhowouldbekin> murmel, It is used by a project I am using as template. I do not know much about it (uWSGI)
[12:00] <manwhowouldbekin> brkcore, Those commands didn't help. What package name?
[12:01] <murmel> can you give the whole output of command + log?
[12:01] <manwhowouldbekin> murmel, Which command?
[12:02] <murmel> manwhowouldbekin: which you ran to get to this point
[12:02] <murmel> I assume that error didn't just appear out of nowhere ;)
[12:02] <manwhowouldbekin> murmel, The command was 'pipenv install --sequential
[12:03] <murmel> manwhowouldbekin: oh I just realized, it needs python2, which is not available on 22.04
[12:04] <murmel> holy moly, it's still in the repo :X
[12:04] <murmel> oh well
[12:04] <murmel> did you install python2?
[12:07] <manwhowouldbekin> murmel, This is the entire log of the command: https://pastebin.com/q1dZag9H
[12:08] <manwhowouldbekin> murmel, I have not installed Python2 on my system, AFAIK.
[12:09] <manwhowouldbekin> murmel, What is still in the repo?
[12:09] <murmel> python2
[12:12] <murmel> manwhowouldbekin: just a quick test in a vm, after installing all the python2 stuff, uwsgi is installable :S
[12:13] <manwhowouldbekin> murmel, I see! What is the best way to install it? I typically use Conda for my Python needs.
[12:13] <murmel> can you install python2 with conda? no idea on that part
[12:15] <manwhowouldbekin> murmel, I doubt it. Does this seem reasonable? `sudo apt install python2`
[12:15] <murmel> manwhowouldbekin: but honestly, I would isolate that stuff as much as possible in a vm or so. if you do, just follow the official instructions on how to install it
[12:16] <murmel> manwhowouldbekin: yes, but I would definitely not install it on a system you actively use
[12:16] <manwhowouldbekin> murmel, What stuff? The project? Or the Python 2?
[12:16] <murmel> both
[12:16] <murmel> python2 was deprecated like 12 years ago?
[12:16] <murmel> and out of support for like 3 or so
[12:16] <murmel> with uwsgi, at least their github repo still sees some work, but no idea how well it's maintained
[12:18] <manwhowouldbekin> murmel, Right. Seems outdated.
[12:19] <murmel> manwhowouldbekin: good luck ;) will be offline for a couple hours
[12:19] <manwhowouldbekin> murmel, Thanks!
[12:28] <BluesKaj> Hi all
[12:31] <poisone> hi
[12:31]  * poisone loading zm...
[12:36] <BCB> anyone familiar with composer in here?  My google fu is failing me.  I'm getting an unexpected 'use' syntax error and don't know why.  Thank you.
[12:37] <ravage> BCB try #php or the channel of the framework you use like #symfony
[13:03] <Guest60> any irc group for UT5 game engine?
[13:56] <Y05hito__> offtopic, if it's not open source, no.
[13:57] <Y05hito__> try ask on #libera or /list somewhere else
[14:01] <ravage> (the user left long ago)
[14:02] <Y05hito__> ok.
[14:18] <larslu> Every once in a while, gnome-screensaver and it's relatives mate-screensaver/xfce4-screensaver/cinnamon-screensaver have a bug to where it's easy to get around a locked session either by crashing it or some other way. How quickly does ubuntu backport and patch their distros in such an incident? Because it's getting me a bit paranoid if I can trust
[14:18] <larslu> any desktop environment at all to not be easy to circumvent. jwz is very proud of his xscreensaver and always reminds everyone how the rest suck.
[14:21] <ravage> larslu, if there is a security related problem it should be fixed pretty fast. also depends on i which repo your package is. https://help.ubuntu.com/community/Repositories
[14:22] <larslu> gnome-screensaver is under universe, which means its community supported. Can I trust the community will fix it within a very short amount of time?
[14:22] <ravage> no
[14:23] <larslu> If I was paying for ubuntu pro, would I be getting the security patch (even for universe) directly from canonical (and in a very short amount of time) rather than rely on the community?
[14:24] <ravage> for Ubuntu Pro related questions you would have to contact Canonical
[14:24] <ravage> Ubuntu Pro is not a community project
[14:24] <larslu> Okay. Thank you.
[14:27] <bancroft> can you enlarge a raid0 array with mdadm?
[14:29] <bancroft> raid0
[14:57] <mfoolb_> lame question of the day: don't know how messing around with AMD driver did it but I don't have 'terminal'
[14:57] <mfoolb_> listed in the gnome context menu
[14:57] <mfoolb_> how can I add it back to it?
[14:57] <mfoolb_> 22.04 LTS
[15:00] <murmel> yeah waiting ~1m helps to get support xD
[15:03] <jhutchins> murmel: Sometimes all you have to do is post the question to the internet and the answer becomes so obvious you're embarassed to stick around.
[15:05] <murmel> jhutchins: but not even 1 min? idk
[15:06] <Intelo> What do I need to use double shock usb 2 game controller on ubuntu in steam?
[15:07] <Intelo> and driers?
[15:07] <Intelo> and dri ers?
[15:07] <Intelo> and drivers?
[15:07] <murmel> are we talking about official dual shock 2 controllers?
[15:07] <respawn> did you check in steam settings
[15:09] <jfsimon1981_b> Hi seen this one :
[15:09] <jfsimon1981_b> https://www.makeuseof.com/tag/get-game-controllers-running-linux/
[15:17] <Intelo> murmel this one https://youtu.be/9QX1shkfPUM?t=114
[15:22] <murmel> Intelo: oh now it gets definitely way harder, as those third party controllers most of the time have very bad drivers (even on windows)
[15:24] <Intelo> murmel ok
[15:48] <fenrirjk> hi there
[15:48] <fenrirjk> I recently upgraded to Ubuntu 22.10 from 22.04
[15:48] <fenrirjk> I have trouble loading my signed modules: "modprobe: ERROR: could not insert 'vboxdrv': Key was rejected by service"
[15:48] <fenrirjk> My MOK key is enrolled, I can see it in dmesg or with `mokutil --list-enrolled`
[15:48] <fenrirjk> mokutil --sb-state returns `SecureBoot enabled`
[15:48] <fenrirjk> sudo mokutil --test-key MOK.der returns: `MOK.der is already enrolled`
[15:49] <fenrirjk> I have this behavior since I am using the kernel v5.19.x, I am currently using kernel v6.0.6
[15:49] <fenrirjk> With kernel v5.15.x I was able to load my signed modules without any problem
[15:49] <fenrirjk> Can someone help be debugging this issue ?
[15:51] <tomreyn> fenrirjk: hmm, there is no kernel v6.0.6 for 22.10, from what i can tell
[15:52] <tomreyn> are you building this yourself, or obtaining it from a third party, or using the unsupported test kernels?
[15:53] <fenrirjk> tomreyn: I installed it with mainline (Ubuntu Mainline Kernel Installer)
[15:53] <fenrirjk> But I have the same behavior with the 5.19.17 (installed during the release upgrade)
[15:53] <tomreyn> so it's an unsupported test kernel, i see
[15:54] <tomreyn> does it also happen with kinetics current default kernel, 5.19.0-23 ?
[15:55] <fenrirjk> How can I install this one ?
[15:55] <tomreyn> install any pending updates
[15:56] <tomreyn> !uptodate
[15:56] <fenrirjk> !uptodate
[15:56] <fenrirjk> ok
[15:56] <fenrirjk> my system is up to date (via `sudo apt update && sudo apt upgrade`
[15:57] <fenrirjk> doing `apt full-upgrade` right now
[15:58] <fenrirjk> there is indeed: `128 upgraded, 12 newly installed, 5 to remove and 0 not upgraded.` ... I hope that will fix my issue.
[16:00] <tomreyn> fenrirjk: you'd also need to boot into the default (5.19.0-23) kernel. such as by manually bringing up the grub menu and selecting this kernel from the "Advanced" submenu. Or by configuring grub to boot to this kernel by default. Or by removing any higher version kernels.
[16:02] <tomreyn> or by choosing the respective menu entry once (which is not easy), using grub-reboot
[16:02] <fenrirjk> Well I only have two kernels installed: ls /boot/vmlinuz* gives `/boot/vmlinuz  /boot/vmlinuz-5.15.0-52-generic  /boot/vmlinuz-5.19.17-051917-generic  /boot/vmlinuz-6.0.6-060006-generic  /boot/vmlinuz.old`
[16:03] <fenrirjk> (full-upgrade is completed)
[16:03] <tomreyn> this seems to list three kernel images
[16:04] <fenrirjk> ok, but how can I be sure if there is a v5.19.0-23 ?
[16:05] <tomreyn> hmm, i'm surprised that you have /boot/vmlinuz-5.15.0-52-generic but not /boot/vmlinuz-5.19.0-23-generic on kinetic (22.10)
[16:06] <tomreyn> apt policy linux-image linux-image-generic     says what?
[16:06] <tomreyn> !paste | fenrirjk
[16:07] <tomreyn> the easiest option to share this output is probably to run:    apt policy linux-image linux-image-generic |& nc termbin.com 9999
[16:08] <fenrirjk> https://dpaste.com/7UZ9TB9GR
[16:11] <fenrirjk> How can I check if a kernel is correctly signed for my secure boot ?
[16:11] <tomreyn> fenrirjk: oh, you just don't have linux-generic installed. you should have, though.
[16:11] <fenrirjk> Yes, i just installed it, thanks tomreyn.
[16:13] <tomreyn> so you now have the default Ubuntu 22.10 kernel image installed, and should boot into that (see above).
[16:14] <fenrirjk> Before I used to sign my kernels manually with my MOK keys, I can now skip this step ?
[16:14] <tomreyn> you should also test whether the out-of-tree vboxdrv kernel module can be built and it can be loaded.
[16:15] <tomreyn> i *think* that both the virtualbox packages probvided by oracle (which i would recommend using) as well as the ones provided by ubuntu in the (community maintained) "universe" repository build the kernel modules using DKMS
[16:15] <tomreyn> so it should happen automatically.
[16:16] <tomreyn> i assume that both are also secure boot compatible, but there i'm not really sure.
[16:16] <tomreyn> you may want to read up on https://wiki.ubuntu.com/UEFI/SecureBoot and https://wiki.ubuntu.com/UEFI/SecureBoot/DKMS
[16:16] <murmel> tomreyn: compatible yes, but they still need to be signed, otherwise sb will throw a fit
[16:17] <tomreyn> out of tree modules always need to be signed with your own MOK key, and this key needs to be imported to the uefi firmware managed key store.
[16:18] <murmel> yes i know. I just hope that rh will get to a point to finally upstream the kernel drivers :S vbox is such a pain to "support" because of sb
[16:18] <tomreyn> DKMS has provisions for signing those automatically, and there is also a mechanism to automatically generate and import a locally generated MOK during the Ubuntu installation process (and possibly later, not sure)
[16:18] <tomreyn> rh?
[16:19] <fenrirjk> afaik to sign modules automatically you just need to edit /etc/dkms/framework.conf to give your own keys.
[16:20]  * tomreyn would not know. good luck!
[16:21] <fenrirjk> ok rebooting now, I'll try this 5.19.0-23 kernel. brb.
[16:27] <jhutchins> I wonder if we're having a problem with less software testing because a greater proportion of users are using Linux systems to do work, rather than play with the software.
[16:39] <murmel> tomreyn: redhat works onto upstreaming the kernel modules
[16:42] <fenrirjk> tomreyn: With kernel v5.19.0-23 I managed to load vboxdrv and run virtualbox. Thank you very much.
[16:59] <Sven_vB> hi :) I'm using Ubuntu focal's apt to install winehq. is there an easy way to get a list of all the URLs apt had to download in order to install winehq?
[17:03] <Sven_vB> oh. I should have searched for URI, not URL. trying --print-uris.
[17:21] <x7upLime> I'm trying to build a snapd snap using snapcraft..
[17:22] <x7upLime> Just installed channel 4.x snapcraft and ran snapcraft on this https://github.com/snapcore/snapd/blob/master/build-aux/snap/snapcraft.yaml
[17:22] <x7upLime> The output:
[17:22] <x7upLime> launch failed: Unable to find an image matching "core". Please use `multipass find` for supported remotes and images.
[17:22] <x7upLime> An error occurred with the instance when trying to launch with 'multipass': returned exit code 2.
[17:22] <x7upLime> Ensure that 'multipass' is setup correctly and try again.
[17:24] <x7upLime> "multipass find" shows core and this works as well "multipass launch -n snapTest -m 2G -d 12G core". Also journalctl logs for snapd and snap.multipass are not useful..
[17:24] <x7upLime> am I missing something?
[17:25] <murmel> x7upLime: pretty sure #snappy is the better channel for such things, as ogra is definitely in that channel. but not sure if he is available on the weekends
[17:26] <x7upLime> thanks murmel, I
[17:26] <x7upLime> 'll try
[17:32] <memsworth> Hello folks
[17:34] <murmel> hi memsworth
[17:38] <memsworth> Glad to be hre :)
[18:05] <jhutchins> murmel: Just FYI (offtopic) since fairly early in the Red Hat project, certainly after they reorganized into RHEL and Fedora, they have provided proprietary drivers that are not true Open Source and are not shared with the community.  Only paying customers get access to those.
[18:05] <jhutchins> There's not a process where they "evolve" to open source and move upstream.
[18:09] <murmel> jhutchins: yeah I know. but thanks for pointing out. but as rh themselves said, they talked to oracle to get to a point where the modules are stable enough to get them upstreamed
[18:11] <tomreyn> fenrirjk: glad it worked out with the default kernel.
[18:12] <tomreyn> murmel: i see, i didn't know redhat cooperates with oracle on upstreaming vbox modules
[18:23] <Intelo> murmel did I missed your last message?
[18:25] <murmel> Intelo: idk? but did you look into the link somebody posted?
[18:26] <Intelo> ya its solved.
[18:26] <x7upLime> does multipass image snapcraft:core still exists? (core16)
[18:30] <tomreyn> x7upLime: you may want to ask this in #multipass or #ubuntu-cloud (preferrably during business hours)
[18:35] <x7upLime> thanks ':)
[19:04] <tommix> Hello there! My Ubuntu works so well that it is almost boring. No reasons to fix it, cos it ain't broken in any ways.
[19:05] <ravage> tommix, great. so stay around to help others or come back any time when you run into a problem. if you just want to chat about ubuntu there is #ubuntu-discuss
[19:05] <tommix> ah, ok. I will return if there is some reason.
[19:05] <raub> `When I set the qterminal colours, where does it pick them up? Would that be in /usr/share/qtermwidget5/color-schemes/?
[19:07] <ravage> raub, google says yes
[19:08] <raub> ravage: Are those colours GRB?
[19:08] <raub> er, RGB
[19:08] <raub> I can't see what I am typing right now, it is washed with a light blue background and white text
[19:09] <raub> hence m desire to change it. in LXterminal I can edit one thing but it seems qxterminal I have to create a new colorscheme file
[19:12] <ravage> Color=196,160,0 looks RGB
[19:14] <raub> ravage: thanks. I will run all the colours again in the colorscheme file to see if I can find the one that is annoying me
[19:39] <raub> Found it: it was Color4
[19:40] <Useer> hello
[19:43] <Useer> i love irc
[19:43] <Useer> so clean
[19:44] <Useer> no junk ad's
[19:56] <jpmh> I installed screen - when I try an run it I get a permission issue with /run/screen - it seems that the directory is being created as owned by root with rwx------ permissions.  I have truied changing it, and it does then work.  However, if I leave screen then the problem comes back when I next boot
[20:06] <tomreyn> jpmh: here, /run/screen is: drwxrwxrwt  2 root       utmp         40 Oct 19 22:44 screen
[20:07] <tomreyn> (of course, you may be running something completely different)
[20:07] <jpmh> tomreyn: I know that that is what it needs to be and if a change it to that then all works.  But next time it will be created incorrectly again
[20:08] <jpmh> as to what I am running - I am running what came from the repository
[20:08] <tomreyn> same here, som a specific ubuntu releases' "main" repository
[20:08] <jpmh> Screen version 4.08.00 (GNU) 05-Feb-20
[20:08] <tomreyn> s/som/from/
[20:09] <tomreyn> you could compare the permissions on your system to that of another of the same release
[20:11] <ravage> and /run ist temp anyway.
[20:11] <jpmh> tomreyn: that is sort of what I did.  /run is 755 and it makes /run/screen as 700 - I change it and all is OK tell...
[20:11] <ravage> https://p.haxxors.com/1pj0z8lm.txt
[20:12] <ravage> so even if mess up the rights it fixes itself after a reboot
[20:12] <jpmh> ravage: yes - I know and that is why screen is making /run/screen
[20:12] <ravage> this is a newer version of screen though. so i guess you maybe use 20.04?
[20:12] <jpmh> ravage: and infact it MESSES up after boot, making the /run/screen with the WRONG permissions
[20:13] <tomreyn> but, i suspect, only on your system
[20:14] <EriC^^> jpmh: what permissions does it create
[20:15] <tomreyn> and what is "it"
[20:15] <jpmh> tomreyn: I'm not sure that I understand what you are saying, but also sort of agree - on the HUNDREDS (literally) of other systems that I access there is no issue.  It is just on this NEW laptop
[20:15] <jpmh> EriC^^: it creates 0700
[20:15] <jpmh> EriC^^: owned by the root with group as root too
[20:15] <tomreyn> so is this a fresh installation from an ubuntu installation iso? which version?
[20:16] <EriC^^> jpmh: please type "sudo rm -r /run/screen && sudo apt-get install --reinstall screen"
[20:16] <jpmh> tomreyn: installed maybe two weeks ago 22.04 (minimal)  - And I will NEVER do minimal again - I have wasted so much time adding back things I lost
[20:17] <tomreyn> jpmh: great, that's the kind of basic information that's always good to provide when you have questions
[20:18] <ravage> but then the screen version is irritating
[20:18] <ravage> i have 4.09.00 (GNU) 30-Jan-22
[20:19] <kostkon> !info screen
[20:19] <ravage> !info screen jammy
[20:19] <tomreyn> "apt policy screen" may clear this up
[20:22] <ravage> his output is what you get on 20.04
[20:22] <ravage> just checked
[20:22] <tomreyn> jpmh's screen from a yet unknown package reports it is --version "Screen version 4.08.00 (GNU) 05-Feb-20". jammy's 4.9.0-1 package version would report that it is --version "Screen version 4.08.00 (GNU) 05-Feb-20"
[20:23] <Mentos> lol had to share this discovery in no mans sky -- https://prnt.sc/C0dRSG6F6fXM
[20:23] <tomreyn> jpmh: so what does    apt policy screen    say?
[20:24] <tomreyn> !ot | Mentos
[20:37] <jpmh> EriC^^: sorry for the delay I lost internet for a few - tried the remove and re-install - no change - even did a reboot
[20:38] <EriC^^> jpmh: ls -ld /run/screen gives what?
[20:39] <EriC^^> jpmh: which ubuntu version is this?
[20:40] <Useer> 22.10
 jpmh: so what does    apt policy screen    say?
[20:42] <Mentos> sorry tomreyn was meant for there
[20:42] <EriC^^> jpmh: what happens if you do 'sudo chown root:utmp /run/screen && sudo chmod 1777 /run/screen'
[20:43] <jpmh> EriC^^: as long as I manually FIX the permissions all works fine.  That's what is so annoying
[20:43] <EriC^^> jpmh: are you fixing it by running the command above?
[20:44] <jpmh> EriC^^: I am not doing the chown since it is already correct.  But I am setting the permissions
[20:45] <EriC^^> you're settingg 1777?
[20:47] <tomreyn> EriC^^: jpmh is saying that they are running a GNU screen which reports it is version "4.08.00 (GNU) 05-Feb-20", on a freshly (2 weeks ago) installed ubuntu 22.04. but 22.04 provides 4.9.0. something's not adding up.
[20:48] <EriC^^> ah tomreyn
[20:48] <jpmh> tomreyn: remember that I did need to install screen - which I did with apt install screen
[20:49] <tomreyn> jpmh: from where?
[20:49] <jpmh> and I did just reinstall
[20:49] <EriC^^> jpmh: run 'apt-cache policy screen | nc termbin.com 9999'
[20:49] <jpmh> tomreyn: no idea from where - wherever the system defaulted to
[20:50] <EriC^^> policy should clear it up i think
[20:50] <tomreyn> jpmh: it would have installed version 4.9.0 then
[20:50] <tomreyn> that's why i asked for the policy output 3 times. ;)
[20:51] <jpmh> tomreyn: and EriC^^ thanks to your input I removed screen - rebooted, installed screen and now have the right version and more to the point IT WORKS!  TY
[20:51] <jpmh> I really appreciate you guys and it is help like this that makes me love Ubuntu
[20:52] <tomreyn> good that it works now
[21:29] <morgan-u2> yes now that I can work it the ubuntu 22.04 copy all or part of the screen does work better than before, ease.....
[21:30] <jhutchins> raub: Yeah, it's a perpetual problem with vim, dark blue on black.
[21:30] <jhutchins> Ah yes, the scrollbuffer.
[21:54] <brkcore> is it possible to change the gnome screencast saving the videos in mp4 instead of webm?
[23:17] <olle> Any tips for text to speech apps? That's not the "standard" robot voice, but actually something better.
[23:17] <olle> Lots of paid websites with good voices, but
[23:19] <olle> Hm, some google results
[23:19] <ravage> festival sounds kind of ok https://www.cstr.ed.ac.uk/projects/festival/onlinedemo.html
[23:21] <ravage> the voices are all in extra packages
[23:26] <olle> ravage: yeah, found a link here https://askubuntu.com/questions/53896/natural-sounding-text-to-speech
[23:26] <olle> Just have to make it read pdf somehow
[23:27] <olle> Or copy-paste in some easy way
[23:28] <olle> Or read from the x window buffer :d
[23:30] <olle> bash can fetch the copy buffer with a tool. then pipe it to festival perhaps
[23:42] <olle> echo "(SayText \"$(xclip -selection clipboard -o)\")" | festival  '(voice_cmu_us_slt_arctic_hts)' --pipe
[23:42] <olle> That's the one
[23:42] <olle> :)
[23:42] <ravage> :)