libera/#devuan/ Thursday, 2023-02-09

gnarface[NoClan]GoAway: i think the primary benefit of kvm is performance, if you have hardware that supports it02:47
gnarfaceif caronte comes back, someone clarify for them that the list of supported hardware i386 and amd64 hardware is the same as debian's02:48
gnarface[NoClan]GoAway: and if you do an upgrade, it shouldn't clobber any config files you've customized02:49
gnarface(but you should always make a backup first, just in case)02:49
xisopgreetings. when i use the tty console (not sure if that's the correct term for it..) sometimes the blinking cursor disappears. by tty i mean hitting ctrl+alt+f1-605:25
xisopis there a way to reset it to get the cursor back? i noticed it seems to happen if i spin up vim05:25
rrqyou mean the text input cursor or the one that gpm brings?05:28
xisopthe text cursor that usually shows up at login and continues to show up throughout the session05:29
debdogcould be silent mode which happens when one accidently hits ctrl-s05:29
xisophmm. maybe i should check that my bash/vim are using the correct term type05:29
debdogquit it with ctrl-q05:29
xisopdoes that usually block input though?05:30
debdogthe input is silent05:34
debdognot blocked05:34
rrqtry 'tput cnorm' to get back the cursor05:44
rrq(man 5 terminfo)05:47
rwpxisop, What TERM are you using?  AFAIK it should be TERM=linux on the Linux vt consoles.06:00
ltsxisop: there is literally the command "reset" to reset a tty06:02
xisopsorry, i was away. the good news is that i haven't experienced it this boot06:04
xisopi will likely write an alias in my .bashrc that has tput cnorm and possibly 'reset' as well06:04
gnarfaceuh, i'm pretty sure ctrl+s will actually lock the terminal06:35
onefangPause, not lock.06:35
gnarfacewell, inputs and outputs will queue up until you hit ctrl+q but i'm pretty sure nothing input-wise takes effect until then06:36
onefangExcept the ctrl-q obviously.  B-)06:36
gnarfacebackground tasks will still run in some cases, but some stuff will actually stall waiting for terminal output to be acknowledged, i'm not super clear on the details06:36
debdoghmm, good point06:37
gnarfacenow that i'm thinking about it though, i can't recall if that'll stop the cursor blink too or not06:37
gnarfaceanyway, it's a good theory, the only other thing that comes to mind is maybe a framebuffer driver issue just making the cursor invisible06:39
gnarfacebut if it's just some state corruption based on bad binary character outputs leaking out somewhere, typing "reset" (then hitting enter) should indeed still work to clear it, even if you can't see the "reset" text output, or (usually) even if it comes out as garbled characters06:40
gnarfacei would try both in order (ctrl+q then the "reset" command) and if neither worked look into trying a different driver for the console06:43
gnarfacethe current trend is to default to kms/modesetting for everything, but in some cases that's still not the best choice for all hardware06:43
debdoghit ctrl-s then "date" enter. then went boiling water for tea when I came back ctrl-q. it definitely shows the time of input and not ctrl-q.06:45
gnarfacehmm, interesting06:46
debdoginterstingly the clock on my screen-statusbar also stopped updating06:46
gnarfaceso then if that's the case, reset might work invisibly first, then the fix would show up after ctrl+q06:47
debdogprobably yes06:48
onefangAh screen-statusbar.  I have often had to reset when running tmux, usually when an ssh to somewhere fell over coz the connectien died, and the ssh was displaying some TUI thing that had left the terminal in afunny state when it fell over.07:15
gnarfacedebdog: now this is interesting though, when i ctrl+s then type date then ctrl+q, the output date is definitely the time of ctrl+q not the initial typing of the date command07:23
gnarfacethat's IN x though07:23
gnarfaceer, in X i mean07:23
gnarfaceso maybe it's different if you tested that at the system virtual terminal?07:23
gnarfaceor maybe it's a terminal, shell, or even window manager difference?07:24
gnarfacethis rings a bell, like we've been over this before07:27
debdoggnarface: xterm plus screen07:28
debdogecho $SHELL07:29
debdog/bin/bash07:29
debdogwindowmanager: fluxbox07:29
gnarfaceinteresting07:29
gnarfacei'm using urxvt, bash, and enlightenment07:30
gnarfaceno screen07:30
gnarfacecould it be something to do with screen?07:30
debdogtesting without...07:30
gnarfaceit's gotta be something, because it had always been my understanding that pending inputs would fire after unlocking the terminal07:31
gnarfacebut pending outputs, whether they actually ran their jobs or not instead of waiting for the terminal would depend on how they were coded07:31
debdogI remember it differently. s stands for silent hence to shell works but there is no output visible07:32
debdogohh, without screen it displays the ctrl-q time07:33
debdogwell...07:33
onefangxisop mentioned tty console, so no window manager.07:35
debdogyes, and the solution was a different one07:37
gnarfacewait, but was there a solution actually mentioned? i thought we were still waiting for the issue to happen again07:42
debdogI thought so <xisop> i will likely write an alias in my .bashrc that has tput cnorm and possibly 'reset' as well07:42
gnarfaceoh, so maybe07:43
gnarfacehmmm...07:44
onefangMore a workaround than a solution.07:46
gnarfacewell the real curiosity is what's doing it?07:47
gnarfacei'm interested in the low-level cause07:48
Avadid u tried  this prize draw https://t.co/bWI707eqmZ is it work or not ?11:58
Ava???11:59
RhineDevilI'm trying to use pipewire on devuan testing, the setup works by running this script on boot: https://paste.debian.net/hidden/ed0ab46f/13:06
RhineDevilWorked before but on last update plasma doesn't recognize pipewire13:06
u-amarsh04confused by this (my report): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=103093415:20
RhineDevilXDG_RUN_DIR in my environment is empty, how do I fix?15:57
gnarfaceyou mean XDG_RUNTIME_DIR?15:58
mcrI guess I gotta stop relying/using apt-cacher(-ng). It used to work so well :-(15:58
RhineDevilgnarface: yes exactly15:58
gnarfacei think if it's not set and something is complaining it's a bug in your window manager15:59
gnarfacebut i have had the same problem before, hang on i'll get you a script15:59
RhineDevilgnarface: would be nice if the problem was addressed officially since the value in debian is set in libpam-systemd16:00
gnarfacehmm16:00
gnarfacei'm not sure there's not an official way16:01
RhineDevilgnarface: if you can make it present to higher-ups, in the meantime pass me a script or something16:03
gnarfaceyea16:04
RhineDevilgnarface: what do you think about export XDG_RUNTIME_DIR="${XDG_RUNTIME_DIR:-/run/user/$(id -ru)}" as a temporary fix?16:07
RhineDevilin /etc/bash.bashrc16:07
RhineDevilin this way it provides an harmless default easily overrided16:09
gnarfacehttps://paste.debian.net/1270148/16:09
gnarfacetry this16:09
gnarfacei'd put it in your user's profile but up to you16:10
gnarfacei had put it in my ~/.bash_profile, but if you have a ~/.profile instead already, i'd put it there16:10
gnarfacenot sure why but it seems to be the convention to define this type of stuff in the bash profile rather than the bashrc16:10
gnarfacethere's a global one too but if this is your only user and nobody else uses the system i'm not sure there's any sense in making it global16:11
gnarfacehttps://paste.debian.net/1270149/16:11
gnarfaceif for some reason the first one doesn't work, try this one instead!16:11
gnarfacei mean ^16:11
gnarfaceRhineDevil:16:12
RhineDevilgnarface: I think I'll stick to my solution, after all /var/run/user/$(id -ru) still gets created on session login16:12
RhineDeviland it's chmoded for the current user16:12
gnarfacewell whatever works16:13
RhineDevilso no reason for creating a tmp runtime dir in /tmp/ in my opinion...16:13
RhineDevilyeah16:13
gnarfacewell just that everything else does it and that's what /tmp is for16:13
gnarfacebut neither place is actually where this directory is s'16:14
gnarface... is "supposed" to go, i don't think16:14
gnarfacei think when it is working it goes somewhere in your home directory but i'm not sure16:14
RhineDevilgnarface: didn't work, I guess the cause is plasma starting before profile or bashrc are run16:28
gnarfaceRhineDevil: if you have a graphical login, it has to be set in its environment16:29
gnarfaceRhineDevil: oh, plasma might just not be actually running your bash profile at all, too16:29
RhineDevilAs I thought, after forcing a restart of plasma it worked16:29
RhineDevilgnarface: it runs it, just way later16:30
gnarfacedoes it run the global one earlier?16:30
RhineDevilbut I can't restart plasma just cause I want to have sound16:30
RhineDevilgnarface: yeah the global one16:30
RhineDevilok uhm where the f should I put user variables even before plasma starts?16:32
RhineDevilthis things wacky af16:33
gnarfacehmm, try ~/.xsession16:34
gnarfaceor maybe ~/.xsessionrc16:35
gnarfaceactually, try putting this in ~/.xsessionrc:16:36
gnarface. $HOME/.profile16:36
gnarfacethen you can just add the XDG variable to your .profile as normal16:37
RhineDevilgnarface: since I want global stuff, added the line in /etc/X11/Xsession.d/40x11-common_xsessionrc16:39
RhineDevilsee you in less than 1 min probably16:39
RhineDevilgnarface: worked as expected16:42
gnarfacethe reason to prefer the user one over the global one is then if it gets changed during an upgrade you don't have to worry about it getting clobbered or having to be manually merged16:43
RhineDevilgnarface: I know, but packages offer you to keep global files, and most times it makes sense to do that16:46
dan9er[m]The APT source onion service is down17:15
dan9er[m]Keep getting Host Unreachable in aptitude, and when try to visit via Tor Browser it says the onion url is not on the hash chain17:17
[NoClan]GoAwaygnarface: thanks for the info.18:13
carontehey all22:28
debdogoy22:33
caronteSince I am a Devuan wannabe,  I have anyway a question if somebody has still Ubuntu machines22:44
caronteHope it doesn´t sound trollish, but lately I found Ubuntu WAY less stable than I was used to.22:44
dan9er[m]caronte: Please don't ask to ask, just ask, you'll get an answer faster22:45
carontewell, I did :D22:46
dan9er[m]Ubuntu is getting more unstable? So how does this relate to Devuan22:46
carontedan9er[m]: I am wondering if it is related to the use of systemd and snap packages.22:48
dan9er[m]uuuh idk, I think one will need to do a deep dive to get a definitive answer22:49
dan9er[m]someone more knowledgeable here can tell you some of systemd's flaws that make it unstable / harder to write stable software for22:51
fsmithredbetter to have that conversation on #devuan-offtopic22:51
fsmithredand save this space for support22:52
dan9er[m]yeah22:52
carontedan9er[m], dan9er[m] thank you22:53

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!