|00:49||jinnjus has joined IRC (jinnjus!~user1@CPE788df72324c1-CM788df72324c0.cpe.net.cable.rogers.com)|
|03:40||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
|03:53||vagrantc_ has joined IRC (vagrantc_!~vagrant@unaffiliated/vagrantc)|
|03:55||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 260 seconds)|
|04:17||vagrantc_ is now known as vagrantc|
vagrantc: wheezy + your backports booted fine from a 16.04 server
I'll now test some really old graphics cards, to see if it makes a noticable difference there, and if it does, I'll publish that image as well
If you want to put them in wheezy-backports, they're fine...
wow, amazed that they even installed fine
or, were those ones i built specifically for wheezy?
(e.g. libc6 dependencies might change)
vagrantc: deb https://cascadia.debian.net/~vagrant/debian wheezy-backports-sloppy-UNRELEASED main
That's what I put in my sources
ltsp-client-core pulled some dependencies, but they installed fine
pulled some dependencies from where?
just additional packages available in wheezy?
ah, ok. no additional backports needed. good.
alkisg: if we actually put in wheezy-backports-sloppy, the rules for installing them via ltsp-build-client may need some tweaking ... or complex manual commandline
squeeze-LTS just ended.
Or they can just enable the backports after ltsp-build-client...
but it's a bit inelegant :)
but i guess we're not talking about an ideal system anyways ... we're already running a deprecated OS to support old hardware
...although I've yet to find a graphics card which has better performance there... tried trident, vanta, nothing, going on to s3virge...
Those are usually onboard, harder to find...
alkisg: I think the director is going to authorize at least 5 of those ASROCK SOC boards...
Cool, let's see how well they work with linux
his eyes lit up when I mentioned we could re-use the psu and case from those old p4 boxes that we had basically mothballed
it's the one you linked - was hoping that meant it worked well already o.O
In one case, the PSU didn't match; in another case, the amd board didn't work with 64bit ubuntu and needed 32bit
No, we've ordered it but haven't tested it yet
We've tested other similar solutions, but so far they were intel-based
oh! good thing it'll take forever for the funds to be ready
that video should be pretty easy to make work, not sure how ubuntu will react but I've never had issues with the ati stuff on arch
Now the last intel board we were proposing to schools is not available anymore, so we've switched to proposing that amd one instead
Yes it should be faster than intel if it works fine
That last intel board also had an IDE connector, and we were able to reuse the old hard disks as well
even more fun is that part of our business is a woodshop with a cnc wood carver/cloner so I could have it map one of the cases and build everyone wood cases :P
it's been bumped up as my priority again so we'll see how things go...
setting up a demo box for the environment I'd like them to use to have the boss and a select few employees test it out before we invest
i worked at a stained glass shop for a few years, and had intended to make a stained glass case, but never got around to it
frankly I'm tempted to buy the machien for myself just because I'm so impressed with them
heh I worked in float glass and had the same plan
never did it
I did however build a laminated cardboard one once
wife made me throw it away because it "was a fire hazard"
|05:48||fnurl has joined IRC (fnurl!3d3edc4a@gateway/web/cgi-irc/kiwiirc.com/ip.188.8.131.52)|
|05:51||ogra_ has left IRC (firstname.lastname@example.org, Ping timeout: 268 seconds)|
|05:55||ogra_ has joined IRC (email@example.com)|
|06:15||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
vagrantc: in all debian ltsp versions, the "Username:" field is too small and "Όνομα χρήστη:" doesn't fit there
Maybe a theme change is necessary...
Maybe right-alight the label instead of centering it?
alkisg: i'm open to patches ...
|07:09||* alkisg is against themes :P :D|
OK let's look at those "Operation failed: No such file or directory" issues under systemd...
It's because of: systemctl --quiet disable "$service"
alkisg: so, the patch you would propose is to remove all themes and just use raw X11 widgets? :)
vagrantc: no, to disable ldm theming support
To maintain only one theme instead of bothering with different distros etc
Widgets is a different things from themes
alkisg: so it's the theming that's breaking it?
I don't think e.g. gtk is implementing combo box by theming some x11 combo box
vagrantc: yes, I think it's the ldm theme that's breaking it
I get the same under ubuntu if I select the default ltsp theme instead of the ubuntu one
|07:32||mikkel has joined IRC (firstname.lastname@example.org)|
alkisg: honestly, themes are not my forte ...
Mine either... highvoltage, maybe you could have a look at it?
highvoltage: seems like we ought to fix the LDM themes to be able to display in other languages
I.e. the "Username:" label in debian's ldm theme is too narrow and translations like "Όνομα χρήστη:" don't fit
apparently, https://bugs.debian.org/615017 might be a theming issue
|07:34||kjackal has left IRC (kjackal!~kjackal@2a02:587:3110:5800:cca9:866f:3437:83c2, Ping timeout: 246 seconds)|
vagrantc: see, I even offered a patch at that bug report :D
When used with enable, disable, edit, (and related commands), make changes only temporarily, so that they are lost on the next reboot. This will have the effect that changes are not made in subdirectories of /etc but in /run, with identical immediate effects, however, since the latter is lost on reboot, the changes are lost too.
That sounds ideal
I'll modify 50-rm-system-services to use that one
hopefully it's available in all versions of systemd we're likely to target
available in jessie, at least
alkisg: keep it up! :)
|07:40||* vagrantc waves|
|07:40||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)|
|08:14||cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 248 seconds)|
|08:47||kjackal has joined IRC (email@example.com)|
Hello, we cannot get Audacity to record on Debian Jessie LTSP XFCE fat clients - actually it works sometimes, but most of the time it does not work. And sometimes it works at first, then stops working.
is there known problems with Audacity ?
sebd: no known problems with *ltsp* fat clients and audacity
But audacity might have any number of problems in debian jessie
You can test in a standalone, non-ltsp installation, to verify that it's not an ltsp issue
alkisg: you are right. By the way, do you know an alternative to Audacity to record children singing in classes ?
I haven't used anything else for that. There are many apps for that though, you could ask in #debian.
for simple recording, the command line tool arecord is probably sufficient -- if you want to edit the recording later on, you'll probably want to go for audacity
|10:09||lliurex-server has joined IRC (lliurex-server!c3391360@gateway/web/freenode/ip.184.108.40.206)|
|10:09||lbssousa has joined IRC (firstname.lastname@example.org)|
|10:26||adrianorg has left IRC (email@example.com, Ping timeout: 248 seconds)|
|10:28||adrianorg has joined IRC (firstname.lastname@example.org)|
|11:11||Anderson69s has joined IRC (Anderson69s!~Anderson6@mne69-3-82-224-54-195.fbx.proxad.net)|
|11:41||robb_nl has joined IRC (email@example.com)|
|11:54||Faith has joined IRC (Faith!~paty_@unaffiliated/faith)|
|12:14||F-GT has left IRC (F-GTfirstname.lastname@example.org, Read error: Connection reset by peer)|
|12:16||F-GT has joined IRC (F-GTemail@example.com)|
|12:20||FGXR6 has joined IRC (FGXR6firstname.lastname@example.org)|
|12:22||kjackal has left IRC (email@example.com, Ping timeout: 268 seconds)|
|12:23||F-GT has left IRC (F-GTfirstname.lastname@example.org, Ping timeout: 252 seconds)|
|12:26||FGXR6 has left IRC (FGXR6email@example.com, Ping timeout: 240 seconds)|
|12:27||F-GT has joined IRC (F-GTfirstname.lastname@example.org)|
|12:36||F-GT has left IRC (F-GTemail@example.com, Ping timeout: 244 seconds)|
|12:38||F-GT has joined IRC (F-GTfirstname.lastname@example.org)|
|12:47||F-GT has left IRC (F-GTemail@example.com, Ping timeout: 260 seconds)|
|12:56||kjackal has joined IRC (kjackal!~kjackal@2a02:587:3110:5800:40a4:65e7:9dce:63c3)|
|13:01||F-GT has joined IRC (F-GTfirstname.lastname@example.org)|
ok I found Traverso, I asked a user to see whether it fits the needs.
I tell them about arecord also, thank you fiesh
|13:43||robb_nl has left IRC (email@example.com, Ping timeout: 268 seconds)|
|14:56||ben_roose has joined IRC (firstname.lastname@example.org)|
|15:02||mikkel has left IRC (email@example.com, Quit: Leaving)|
|15:08||ogra_ has left IRC (firstname.lastname@example.org, Quit: Coyote finally caught me)|
|15:14||ogra_ has joined IRC (email@example.com)|
|15:23||lbssousa has left IRC (firstname.lastname@example.org, Quit: Konversation terminated!)|
|16:11||robb_nl has joined IRC (email@example.com)|
|16:17||ogra_ has left IRC (firstname.lastname@example.org, Quit: Coyote finally caught me)|
|16:20||ogra_ has joined IRC (email@example.com)|
|16:26||Anderson69s has left IRC (Anderson69s!~Anderson6@mne69-3-82-224-54-195.fbx.proxad.net, Quit: Time to EAT, SLEEP OR WHATEVER BYE!!!!!)|
|16:53||robb_nl has left IRC (firstname.lastname@example.org, Ping timeout: 248 seconds)|
|17:52||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|
|20:31||ogra_ has left IRC (email@example.com, Ping timeout: 250 seconds)|
|20:31||ogra_ has joined IRC (firstname.lastname@example.org)|
|21:16||Faith has left IRC (Faith!~paty_@unaffiliated/faith, Quit: Leaving)|
|21:53||ben_roose has left IRC (email@example.com, Remote host closed the connection)|
|22:43||robb_nl has joined IRC (firstname.lastname@example.org)|
|22:51||robb_nl has left IRC (email@example.com, Quit: I'm gone, bye bye)|
|23:31||kjackal has left IRC (kjackal!~kjackal@2a02:587:3110:5800:40a4:65e7:9dce:63c3, Ping timeout: 246 seconds)|
|23:32||kjackal has joined IRC (firstname.lastname@example.org)|
|23:46||kjackal has left IRC (email@example.com, Ping timeout: 248 seconds)|