| gnarface | Soltis: i wonder if something in userspace is changing the keymap unexpectedly | 00:01 |
|---|---|---|
| gnarface | like at some point after this | 00:01 |
| Soltis | gnarface: I can't say no for sure, but this is a _fresh_ install as of around 15 minutes before I first started asking on here. | 00:05 |
| gnarface | the culprit is probably a malfunctioning desktop keymap setting tool | 00:07 |
| gnarface | that's my guess anyway | 00:07 |
| Soltis | gnarface: Not sure, but I got wireless working finally (some version mismatches from having to manually install packages) and so far it SEEMS to be working correctly now as well. | 02:10 |
| Soltis | gnarface: Also you're right - both are using the i915 driver. | 05:00 |
| gnarface | the backports kernel may have fixed it, but resume from hibernate and suspend is widely known to be glitchy across the board | 05:12 |
| gnarface | and the common culprits are the video drivers | 05:12 |
| gnarface | nvidia has issues with it too | 05:12 |
| gnarface | i haven't even bothered testing amd | 05:13 |
| gnarface | i think some people have suggested the lid switch activation to be a particular complication but i don't know for sure if it's related | 05:14 |
| gnarface | one thing to test would be if you can run the pm-suspend script directly and get it to resume correctly from that without closing the lid | 05:15 |
| gnarface | if you're using a graphical login manager, i think i've even heard that some of them excite this bug while others don't | 05:16 |
| Soltis | gnarface: I'm just using the defaults from the live CD installer. | 08:51 |
| gnarface | Soltis: ah, it's not the same thing as the regular installer, though i'm not sure it matters in this case but it could affect package selection | 08:56 |
| Kitty | there's a console tool for selecting runlevels of a init script | 14:32 |
| Kitty | I can never remember what it's called | 14:32 |
| Kitty | it's got a curses interface | 14:32 |
| rrq | sysv-rc-conf? | 14:33 |
| Kitty | that's the one | 14:43 |
| Kitty | I can never rememebr sysv-rc-conf for init.d update | 14:43 |
| Kitty | that's so I can find it when I grep the logs | 14:43 |
| Kitty | why is there a /etc/systemd directory in Devuan ? | 17:49 |
| fsmithred | vestigial appendage from debian. It does nothing in devuan. It's there for packages to drop the files that systemd needs. | 17:51 |
| fsmithred | more to the point, the only way to get rid of it would be to fork all the packages that expect to drop files there. | 17:52 |
| fsmithred | That would be a lot of wasted work. | 17:53 |
| Kitty | aah | 17:53 |
| fsmithred | and removing service files just to remove service files is the equivalent of removing sysvinit scripts. | 17:55 |
| Kitty | is there a tool for converting a systemd.service file into an sysvinit file ? | 17:55 |
| fsmithred | yeah, it's a script in the sysvinit-utils package | 17:55 |
| Kitty | I'm not seeing it | 17:57 |
| fsmithred | yeah, it's not what I thought. /lib/init/init-d-script makes a skeleton init script | 17:58 |
| fsmithred | I'm pretty sure a conversion script exists, written by the current sysvinit maintainer. | 17:58 |
| fsmithred | Here's one, and my browser tells me I've been here before: https://github.com/akhilvij/systemd-to-sysvinit-converter | 18:01 |
| fsmithred | I'm sure I did not try it. | 18:01 |
| Kitty | I'll look tomorrow, just realised it's home time | 18:09 |
| Kitty | thanks for your help | 18:09 |
| sadoon[m] | I'm getting a corrupted files error on the torrent versions of the isos for chimaera amd64 | 19:27 |
| sadoon[m] | I've tried the desktop and netinstaller so far | 19:27 |
| sadoon[m] | I'm also getting it on the latest netinstall from the mirrors | 19:32 |
| sadoon[m] | This is weird. Even the old beta release iso is giving me errors. Could be the SSD I'm using? | 19:34 |
| sadoon[m] | I'll try to reinitialize it | 19:35 |
| fsmithred | sadoon[m], what is giving the error message? | 19:36 |
| sadoon[m] | debootstrap says bash deb is corrupted | 19:36 |
| fsmithred | io errors when you try to run a command? | 19:37 |
| sadoon[m] | No the installer is trying to debootstrap but having this error | 19:37 |
| fsmithred | check sha256sum on the iso | 19:38 |
| sadoon[m] | The iso is fine I just found out | 19:38 |
| sadoon[m] | It was the MBR | 19:38 |
| sadoon[m] | I reinitialized it and now it's fine | 19:38 |
| sadoon[m] | 4 isos can't all be corrupted xD | 19:38 |
| fsmithred | yeah, good point | 19:39 |
| sadoon[m] | Thanks btw | 19:39 |
| sadoon[m] | Installing devuan for my work desktop | 19:39 |
| fsmithred | nice | 19:39 |
| sadoon[m] | Had these issues while I was at work so I decided to take the SSD back home and hotplug it and install devuan using qemu, the best way | 19:39 |
| crhylove | Good Morning from Hawaii! What's the best way to hook up bluetooth in Daedelus? | 20:32 |
| rwp | crhylove, Make sure you have bluetooth, bluez, and blueman installed. Use blueman for graphical management. | 22:01 |
| crhylove | @rwp, Perfect! Thanks! | 22:36 |
| eyalroz | Hello Devuaners :-) | 23:31 |
| eyalroz | I want to run a mosh server on my machine. I was expecting an /etc/init.d/mosh or /etc/init.d/mosh-server , but that's not available. How come? | 23:32 |
| rwp | AFAIK there is no such thing as a mosh server. It simply uses ssh. I use mosh all of the time. I am using it now. | 23:32 |
| rwp | Make sure to open UDP ports 60001:60009 or so on your server side. | 23:33 |
| eyalroz | rwp: So, what is /usr/bin/mosh-server then? | 23:34 |
| eyalroz | (I haven't used mosh before) | 23:34 |
| rwp | The mosh-server is used by mosh when it connects to the remote end over ssh. And then subsequently mosh-client and mosh-server communicate. | 23:35 |
| rwp | But one *starts* it up by simply calling mosh and connecting to the remote server. | 23:35 |
| rwp | For example: "mosh myserver.example.com" | 23:35 |
| eyalroz | In that case - doesn't it open ports 60001:60009 on its own? | 23:35 |
| rwp | Mosh does open those ports. But firewalls override anything that any program does. | 23:35 |
| rwp | If a firewall blocks those ports incoming then those ports are blocked. | 23:36 |
| eyalroz | Ok, thanks, rwp. | 23:36 |
| rwp | mosh starts the mosh-server on the remote end by using ssh there to get it going. Then it chooses the next available port from the range starting at 60001. | 23:37 |
| rwp | After the initial ssh call using TCP to get the mosh-server running then mosh-client and mosh-server converse using UDP from them forward. | 23:38 |
| rwp | After you get this going for yourself at least once ping me and I will pass along why I always use it with screen or tmux. | 23:38 |
| eyalroz | How about tunneling, though? | 23:41 |
| eyalroz | Is there some UDP tunneling server I could use on an intermediate machine? | 23:42 |
| eyalroz | (that's not a Devuan-related question obviously) | 23:42 |
| rwp | Right. Probably a better question for the #mosh channel. | 23:43 |
| rwp | Before going there let me point out good general stuff at https://mosh.org/ with an FAQ and other info. Scroll down it for good stuff. | 23:44 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!