brocashelm | is it safe to remove acpi packages if i have no need for them? | 01:14 |
---|---|---|
rwp | Safe? It all depends. If you truly are not using them then sure. But they often get used for the special function keys for example. | 01:22 |
rwp | On all of my machines for example ACPI is used for the power button for shutdown and suspend. | 01:22 |
buZz | 'acpi' package is just a frontend cli tool for reading the acpi information | 02:24 |
buZz | its not the tool for 'what happens on powerbutton press' | 02:24 |
buZz | -usually- thats your WM | 02:25 |
buZz | but there's other methods | 02:25 |
buZz | acpi/stable 1.7-1.1 amd64 | 02:25 |
buZz | displays information on ACPI devices | 02:25 |
buZz | if you're talking about that package, totally safe to remove | 02:25 |
buZz | brocashelm: ^ | 02:25 |
omen | is it easy to install systemd as dependency for some package? | 02:39 |
buZz | omen: all debian packages that depend on systemd have been either liberated of that dependancy , or arent present in devuan | 02:44 |
omen | what if i install package from 3rd party repo | 02:45 |
buZz | thats not a devuan package then | 02:46 |
buZz | you can mess up a linux install really good if you go installing .deb's from random sources :D | 02:46 |
buZz | better build whatever you want from source then | 02:46 |
buZz | what package are you looking at? | 02:46 |
omen | signal for example | 02:47 |
buZz | that doesnt depend on systemd afaik? | 02:47 |
omen | i hope so :D | 02:47 |
buZz | its not a system service | 02:47 |
buZz | so why would it? | 02:47 |
buZz | afaik the program is just a website wrapped in a browser wrapped in ... lxc? docker? no clue | 02:48 |
omen | yeah it would be weird | 02:48 |
buZz | maybe it helps to deal with issues you actually have | 02:48 |
buZz | instead of inventing unknowns :) | 02:48 |
omen | well atom for example has lot of packages named like gnome-* and isn't gnome pretty much only working on systemd | 02:49 |
buZz | whats 'atom' ? | 02:50 |
omen | i think it's categorized as text editor | 02:50 |
buZz | oh lol | 02:50 |
buZz | thats not a text editor | 02:50 |
omen | hackable texteditor | 02:50 |
buZz | that is just a website wrapped in a browser wrapped in some container | 02:50 |
omen | it's electron app | 02:50 |
buZz | are all your 'desired' programs just websites? :D | 02:50 |
buZz | why not just run a browser then | 02:51 |
omen | I just wanted to know if I get warned if I try to install systemd | 02:51 |
buZz | no you wont | 02:52 |
buZz | if you want to shoot yourself in the foot (like , by adding debian repos in sources.list) , the system will comply to -your- wishes | 02:52 |
buZz | and just do what you tell it to | 02:52 |
exorcist | hello, happy devuan user for some years here, here's a little problem: every time I close the lid of my laptop I get this message "None of the screen lock tools ran successfully, the screen will not be locked". I'm using latest release Chimaera. What's the best solution to this? | 08:50 |
exorcist | this fixed it ---> https://unix.stackexchange.com/questions/101806/why-doesnt-my-screen-lock-in-xfce | 09:18 |
exorcist | first install light-locker and switch login manager to lightdm, then run xfconf-query -c xfce4-session -p /general/LockCommand -s "light-locker-command -l" --create -t string | 09:18 |
exorcist | if this happens to other users it would be a good idea to post this solution somewhere on a devuan wiki of sorts, I don't know if you guys have such a thing | 09:19 |
onefang | We are testing a bunch of wiki's to see which one we like the best. Or at least some of the other devs are. | 09:20 |
exorcist | 👍 | 09:22 |
nat | since xfce 4.14/debian 10 locking screen has been really buggy for me | 10:10 |
nat | light locker should be set up by default in my opinion | 10:10 |
nat | I mean I have it set up and it works perfectly but I always have to mess a lot with it | 10:11 |
nat | I also have expresscard egpu and I have to modify logind settings to not suspend/lock screen while "docked" | 10:12 |
meridian | Hi all, | 10:49 |
meridian | I tried to register yesterday but my ip is banned. Can you please resolve the question? thanks! | 10:49 |
meridian | 109.190.13.28 | 10:49 |
meridian | ecrire@francois-delegue.fr | 10:49 |
meridian | (The message saying to not retry the registration should also be within the banned one…) | 10:49 |
meridian | ciao! | 10:49 |
onefang | Register on what? | 10:50 |
meridian | of course… dev1galaxy.org | 10:51 |
NetKBs | hi? | 18:36 |
jyri | the problem with Wikis are that after you have used Confluence you realise how much they suck | 19:47 |
jonadab | There are a lot of problems with wikis. The only really *good* thing about them, is that everyone and their dog is already familiar with Wikipedia. | 19:48 |
jonadab | At this point, MediaWiki markup is literally more widely known than XML. | 19:49 |
jonadab | So the barrier to entry for new users is just about as low as you can make it. | 19:50 |
nemo | ugh... how the heck does one run synaptic through ssh -Y these days | 22:02 |
nemo | polkit is soooo annoying | 22:02 |
nemo | $ synaptic-pkexec | 22:03 |
nemo | ==== AUTHENTICATING FOR com.ubuntu.pkexec.synaptic === | 22:03 |
nemo | polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie | 22:03 |
nemo | ... authenticating as... me... ☹ | 22:03 |
nemo | sudo synaptic doesn't work either | 22:03 |
nemo | xclock works fine | 22:04 |
nemo | siiiigh | 22:04 |
* nemo curses and installs vnc | 22:04 | |
rm | synaptic is arguably far from being an essential tool | 22:08 |
rm | iow why you even need it | 22:09 |
rwp | nemo, The man page for ssh -Y says "(Debian-specific: This option does nothing in the default configuration: ..." But I don't use it and know nothing more... | 22:19 |
nemo | rm: I guess I should familiarise myself with the debian commandline more | 22:20 |
rm | yeah the -Y part seemed unusual too | 22:20 |
rm | I just use -X | 22:20 |
nemo | rm: it should be equivalent most of the time | 22:20 |
nemo | I'm in habit of using -Y to work around situations where -X is not sufficient | 22:21 |
rm | I see | 22:21 |
nemo | but in any event, neither works here | 22:21 |
rm | I don't have synaptic installed to check | 22:23 |
redrick | rm: (Hello, fellow person with initials RM!) The ssh -Y option became necessary starting around 2008 with X.org's adoption of the "X11 SECURITY" extension. Please see https://www.x.org/wiki/Development/Documentation/Security/ . | 23:17 |
rm | redrick, thanks, I really meant I just use -X even today :) | 23:17 |
rm | and it works for me | 23:17 |
rm | admittedly I might not be using a recent Xorg | 23:17 |
redrick | It may if there's not cross-user authentication for the X client. Starting with X.org v. 7.2, though, the X client (such as /usr/bin/ssh, in this context) needs to jump through new hoops to qualify as a "trusted client". That's what -Y in place of -X does. | 23:20 |
redrick | I had to update my FAQ about remote X11 with root auth (http://linuxmafia.com/faq/Security/root-with-x11.html), when that change occurred. | 23:21 |
redrick | rm: I'm betting if you check ssh_config, you will fail to find a line saying "ForwardX11Trusted no". That config detail enables the 2009 security improvement to X11 implementation, to make the -X option more limited. But if your host lacks that, then -Y and -X both result in (dangerous) X11 client behaviour. | 23:49 |
rm | yeah I don't have that | 23:50 |
redrick | Some distros, notably Ubuntu Linux, made a policy decision to defer enabling the 2009 X11 SECURITY extension, by omitting that config. | 23:50 |
redrick | So, all X11 forwarding is assumed to involve friendly processes on both sides of the connection, that deserve the keys to the kingdom. | 23:51 |
redrick | With the option present, -X is subjected to the SECURITY extension, making it safer. -Y is then what you use to signal 'I trust all of this stuff completely. Let it do anything I could do locally.' | 23:53 |
redrick | Quoting the Ubuntu man page for ssh(1): "X11 forwarding is not subjected to X11 SECURITY extension restrictions by default, because too many programs currently crash in this mode. Set the ForwardX11Trusted option to “no” to restore the upstream behavior. This may change in future depending on client-side improvements.)" | 23:55 |
redrick | To be fair, that was in the 14.04 LTS man page, so they may have finally joined this century some time over the last five years. | 23:56 |
redrick | Anyway, reference was to /etc/ssh/ssh_config , on a typical system. | 23:56 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!