gnarface | eyalroz: what do you get as a result for: dpkg -l |grep icon\-theme | 00:12 |
---|---|---|
eyalroz | gnarface: | 00:13 |
eyalroz | ii adwaita-icon-theme | 00:13 |
eyalroz | ii breeze-icon-theme | 00:13 |
eyalroz | ii deepsea-icon-theme | 00:13 |
eyalroz | ii gnome-icon-theme | 00:13 |
eyalroz | ii hicolor-icon-theme | 00:13 |
eyalroz | ii mate-icon-theme | 00:13 |
eyalroz | ii oxygen-icon-theme | 00:13 |
eyalroz | ii papirus-icon-theme | 00:13 |
eyalroz | ii tango-icon-theme | 00:13 |
gnarface | careful don't get flood kicked | 00:14 |
eyalroz | gnarface: Well, you asked... | 00:14 |
gnarface | looks like you have plenty | 00:14 |
gnarface | i'm not sure how to set one specifically in cinnamon | 00:14 |
Unit193 | But no elementary-xfce-icon-theme! | 00:25 |
systemdlete | more fun with apt updates. I've seen these messages before, but ignored them. Here is a sample, but it occurs for about a dozen packages: "dpkg: warning: files list file for package 'libmodule-runtime-perl' missing; assuming package has no files currently installed" | 00:27 |
systemdlete | The message seems to go away if I run apt update/apt upgrade again. Of course, that may not be a good test. However, if I run apt reinstall <pkgname> I will see the messages again. Apt does finish ok, though, it seems. | 00:28 |
eyalroz | Well, looks like locating an icon via in the menu item properties dialog - helps. | 00:29 |
rwp | eyalroz, The flood kicker is a global Libera.Chat mechanism and not specific to any one channel. Someone might ask for data but then expect a paste URL back. | 00:49 |
rwp | systemdlete, /var/lib/dpkg/info/libmodule-runtime-perl.list is missing on your system? How could that happen? | 00:50 |
YugiohMaster88 | hello im new to using devuan and i was just wondering how do i start and stop services on devuan through the terminal? | 05:08 |
GoatAvenger | YugiohMaster88, I'm no expert, but I think you want the command (/etc/init.d/serviceinquestion start|stop|restart|etc..) | 05:09 |
GoatAvenger | if you are using sysV, anyway | 05:10 |
GoatAvenger | which is the default, I believe | 05:10 |
YugiohMaster88 | ah ok thank you very much | 05:10 |
GoatAvenger | np | 05:10 |
rwp | GoatAvenger, FYI: service is /usr/sbin/service. So "sudo service fooname stop" and "service fooname restart" so forth. | 05:41 |
rwp | BTW... Has anyone ever mused that there is a stop and a start and a restart but no restop? :-) | 05:42 |
* GoatAvenger chuckles | 05:42 | |
GoatAvenger | rwp, /etc/init.d/yadada are the scripts themselves the init system uses, then..? | 05:42 |
GoatAvenger | think i answered my own question | 05:42 |
lts | Additional recommendation: sysv-rc-conf is nice for enabling services by using an interface | 05:51 |
lts | Doesn't start them but enables them to start during boot | 05:52 |
lts | ACtually, looks like it can start/stop them immediatelly with + and - keys. Nice. | 05:53 |
rwp | GoatAvenger, Yes. /etc/init.d/* are the scripts themselves. But if you run them directly then they inherit your command line environment. | 06:25 |
rwp | Your current working directory. Your environment variables. Your ssh-agent connection. All of that. Which is not desirable because it is not the boot time environment. | 06:26 |
GoatAvenger | rwp, therefore it's best to use, 'service serviceinquestion start|stop|run?' | 06:26 |
rwp | The "service" command cleans all of those things before calling the actual scripts. That's why it is the recommended way. But whether it is really needed or not depends upon the service script. | 06:27 |
GoatAvenger | good to know. I forget the conventions, I think, when the switch to systemd was made | 06:27 |
GoatAvenger | and then switching back | 06:27 |
rwp | If I am debugging things then I will call the /etc/init.d script directly with "sudo sh -x /etc/init.d/foo start" so as to trace things. But as a normal course of events I will use service to clean up my env first. | 06:29 |
onefang | When using the service command keep in mind this bit from it's man page - "The existence of a systemd unit of the same name as a script in /etc/init.d will cause the unit to take precedence over the init.d script." | 07:03 |
onefang | sysv-rc-conf FTW. | 07:04 |
funlw65 | /msg NickServ VERIFY REGISTER funlw65 6GcG3lJc8P3XtNGW | 07:23 |
funlw65 | /msg NickServ VERIFY REGISTER funlw65 6GcG3lJc8P3XtNGW | 07:24 |
onefang | Oops, you just told everyone what your password is. | 07:27 |
Unit193 | Nope, it's only a verification ID. | 07:27 |
funlw65 | The problem is, the veryfication ID can't be sent directly on the server, you have to be on a channel... | 08:24 |
funlw65 | Or I don't know, new to IRC. | 08:25 |
Unit193 | I mean, it's usually a good idea to have your client focused on the status window when doing that. | 08:26 |
onefang | Maybe no space in front? | 08:30 |
funlw65 | I've sent yesterday the verification ID only to come today with the message that the ID is not verified... Tried to do it from there but requested to join a channel first... | 08:34 |
funlw65 | After joining, instead of going back to status window, I've sent the message from here :P . Well, sent it again from the status window and it says (again) that the ID is now verified. Will see (I apologize, I hate to be off-topic). | 08:36 |
Unit193 | funlw65: You're now verified, congrats! | 08:39 |
limutoo | Hello Devuan tribe. | 09:34 |
systemdlete | rwp: beats me. I just ran apt upgrade and got those messages about the missing info files | 09:35 |
systemdlete | is there a way to re-establish them (aside from reinstalling the problem packages)? | 09:35 |
systemdlete | I mean, does apt have a fix-up mode that tests for and corrects inconsistencies? | 09:36 |
systemdlete | (rpm had an audit feature like that, iirc, or maybe yum, idr) | 09:36 |
systemdlete | beep makes no sound. "apulse /usr/bin/beep" makes no sound. "apulse -l 250 -f 300" makes no sound. | 10:53 |
systemdlete | BUT | 10:53 |
systemdlete | aplay /usr/share/sounds/alsa/Front_Center.wav works just fine | 10:53 |
systemdlete | beep broken? | 10:53 |
systemdlete | (no pulse here!) | 10:54 |
djph | systemdlete: 'beep' uses (is supposed to use) pcspkr. lotta distros disable it ... | 10:57 |
systemdlete | hmmm. Interesting. beep was installed by default in devuan, or by some other package via dependency. | 10:58 |
systemdlete | djph, any alternative that is simple? | 10:58 |
systemdlete | years ago, "beep" worked. Like a lot of stuff did. Then they improved the system. And now it does not work. | 10:59 |
djph | systemdlete: assuming your machine HAS a pcspkr (the little piezo on the motherboard), then it might be blacklisted or something | 11:03 |
systemdlete | it does have one, yes. | 11:03 |
systemdlete | and it works. | 11:03 |
systemdlete | but just not for "beep" | 11:04 |
djph | then 'beep' should work. unles your user doesn't have permissions to access the pcspkr | 11:04 |
joerg | >>[5 Aug 2022 08:24:16] <funlw65> The problem is, the veryfication ID can't be sent directly on the server, you have to be on a channel...<< depends entirely on your IRC client. I'd recommend to open a /QUERY NickServ which is equivalent to the sending a /msg NickServ but had the advantage that you can't fatfinger-typo stuff and cause disclosure of your credentials | 14:36 |
joerg | in expression: open a new tab or window or whatever the thing on your IRC client, by sending the command /query nickserv which should open a private channel to the nickserv bot for you. There you can go ahead and type plain text without and clumsy /msg bla intro. Try sending a simple %HELP | 14:40 |
joerg | very convenient and more resilient to typos etc | 14:42 |
joerg | sorry, my typo fatfingering, I meant to say >>Try sending a simple HELP<< | 14:43 |
joerg | screenshot of such query https://i.imgur.com/cRQ6wKV.png | 14:46 |
joerg | *sigh* hexchat - notorious for confusing the user by a very creative approach to what message text goes which tab | 14:53 |
joerg | (pc) beep is a very weird tricky thing, iirc an IOCTL call to the keyboard device | 15:06 |
joerg | it's completely unrelated to anything sound/audio/ALSA/pulse | 15:07 |
djph | joerg: yeah, thankfully I got out of using hexchat :) | 15:07 |
joerg | sorry, I got to correct myself: some mainboards support a real tiny speaker (not a piezo beeper) and those mainboards often offer a "beeper" audio channel in hw mixer | 15:15 |
djph | oh, that's fun | 15:16 |
joerg | e.g. see /usr/share/alsa/init/postinit/01beep.conf (not guaranteed to be same path and filename on your system) | 15:16 |
joerg | in a true console (not a virtual terminal under a window manager), a `echo -en "\007"` *should* trigger the PC beeper | 15:20 |
joerg | xterm and the like usually have a config where user can define what to do when a BELL (\007) gets "printed" | 15:23 |
joerg | ((re: got to correct myself)) likewise mainboards may offer a hw mixer control to mix the TTL squarewave piezo beeper output into the real audio stream to whatever is the "soundcard" on your system | 15:27 |
joerg | https://man7.org/linux/man-pages/man2/ioctl_console.2.html >> KDMKTONE Generate tone of specified length. The lower 16 bits of the unsigned long integer in argp specify the period in clock cycles, and the upper 16 bits give the duration in msec.<< | 15:32 |
joerg | I'm not sure if it's exactly to the point, but obviously sufficiently close to what I recall it to be | 15:34 |
joerg | regarding BEL aka ASCII \007 all the history and stuff in a nutshell, to understand why things are the way they are: https://en.wikipedia.org/wiki/Bell_character | 15:41 |
golinux | <joerg> *sigh* hexchat - notorious for confusing the user by a very creative approach to what message text goes which tab | 16:03 |
golinux | Is that why I found messages in a PM from a user that wasn't assigned to that window? | 16:04 |
golinux | While I've got your attention . . . is there a way to turn off the channel info clutter at the top of the window. That clutter is really annoying. | 16:06 |
golinux | It used to quicky scroll out of view . . . | 16:06 |
joerg | golinux: PM is not related to the hexchat "issue". Anybody opening a /query to any arbitrary user (not channel) will usually open a private tab on the addressee's IRC client, no matter if hexchat or any other client. That's the definition of what a /query does, aiui | 16:15 |
Helenah | Agreed | 16:16 |
golinux | But why would messages from unrelated users share one use's channel | 16:16 |
golinux | That NEVER happened on xchat. | 16:17 |
joerg | in contrary, a /msg <addressee> Some Message Text and similar type of responses and info messages is not defined in IRC specs where exactly it gets displayed to the user. This is where hexchat has very unique ideas where those get displayed | 16:20 |
joerg | regarding the >>channel info clutter<< I assume you refer to the /topic ? that depends on your IRC client | 16:21 |
Helenah | /msg is merely an alias to PRIVMSG, the server doesn't see /msg rather it sees PRIVMSG and the /msg alias in itself is coded to have differences depending on client. | 16:21 |
joerg | aah wait, there are also the server or chanserv generated ONJOIN or whatever they're called messages | 16:25 |
joerg | golinux: this? please check /msg chanserv help set entrymsg | 16:28 |
* joerg fails to find out how to check the current setting of chanserv entrymsg | 16:32 | |
Helenah | joerg: /quote ChanServ HELP or /raw ChanServ HELP | 16:41 |
Helenah | Look for SET in the list. | 16:41 |
joerg | /msg chanserv info #devuan ==>no "[Notice] -ChanServ- Entrymsg : <whatever message>" | 16:43 |
joerg | so I gather golinux referred to her hexchat displaying the chanel /topic and chanmode settings at /join | 16:44 |
joerg | this? https://i.imgur.com/zZNnFVg.png | 16:45 |
joerg | I have no idea who triggers this and if/how you could disable it | 16:46 |
Helenah | Disabling channel topics isn't a good idea, often channel rules and important stuff is specified in them. | 16:47 |
joerg | konversation IRC client shows the /topic persistently in a separate box on top of the channel tab | 16:48 |
joerg | so I could live without the chat window *** message text | 16:49 |
Helenah | There's /topic if you need the topic of a channel at any point, you don't need to keep scrolling up. | 16:50 |
golinux | joerg: Sorry . . . been in the kitchen | 16:51 |
joerg | and golinux specifically asked >>is there a way to turn off the channel info clutter at the top of the window. That clutter is really annoying. It used to quicky scroll out of view . . .<< which sounds like a sane rationale for wanting to get rid of it | 16:51 |
Helenah | Also be careful using /msg with services, for what you just used it for is fine but there is a risk of sensitive data ending up in the hands of someone masquerading as NickServ or ChanServ, they could get NickServ account credentials and channel passwords. | 16:51 |
golinux | I'm talking about the bar with channel into at the top of the message content. Would also be nice to get rid of the verbose join message that goes on and on. | 16:52 |
joerg | Helenah: I recommended using a /query instead | 16:52 |
golinux | Yes, joerg, you understand. | 16:52 |
Helenah | joerg: Why? That's if you want to open a PM window with someone. The vulnerability I spoke of is still there. | 16:53 |
golinux | Sadly I am in a rush atm so can't stick around. Will read and digest these notes later | 16:53 |
joerg | so please elaborate | 16:53 |
joerg | ^^^ Helenah | 16:54 |
Helenah | Every nick that is on this server could be used by anyone including services nicks unless Libera staff have made them unusable so just incase someone masquerades as NickServ or ChanServ, you should use /quote <ServiceName> or /raw <ServiceName> | 16:55 |
joerg | >><Helenah> Also be careful using /msg with services, ***for what you just used it***…<< what was it "I just used it for"? | 16:55 |
Helenah | You need to give me chance to type... | 16:55 |
joerg | Helenah: yes, nobody can use service nicks except the service bots, on libera | 16:56 |
Helenah | Yes but the habit should still be /quote or /raw is my point. | 16:56 |
Helenah | Just because Libera claim they've protected those nicks, doesn't mean every other IRC network has. | 16:56 |
joerg | sorry, I never heard of that and don't see the benefit | 16:56 |
Helenah | More the reason to listen to my security advice then. | 16:57 |
Helenah | Unless you want to gullibly dump passwords into the hands of people pretending to the services. | 16:57 |
joerg | security by obscurity? when I don't understand why something is needed, then I tend to not use it or - even worse - use it the wrong way and cause more trouble than without | 16:58 |
Helenah | I'm done supporting you because you're just being stubborn. | 16:59 |
joerg | on lebara network (and freenode, back when) the services nicks are protected and itS' been ages since anybody managed to pull a hack like that | 16:59 |
joerg | Helenah: you're welcome | 16:59 |
Helenah | Yes but you haven't been reading what I've been saying. | 17:00 |
Helenah | I said once that you've to make /raw and /quote habbit just incase an IRC network isn't protecting those nicks. | 17:00 |
joerg | I'm done arguing with you | 17:00 |
Helenah | Wow rude. | 17:00 |
joerg | HAH | 17:00 |
joerg | <Helenah> I'm done supporting you because you're just being stubborn. <joerg> I'm done arguing with you <Helenah> Wow rude. | 17:02 |
joerg | golden | 17:02 |
Helenah | Please stop! | 17:02 |
Helenah | This is a support channel. | 17:02 |
joerg | ORLY? | 17:03 |
joerg | I still miss the rationale how a /quote or /raw would provide any whatsoever increased protection against a rogue user squatting on a nick that is commonly associated to a service bot user account | 17:16 |
Helenah | joerg: Some IRCd's support aliases that can be pointed to a target (service). On Libera, the vhost "services." is reserved for services meaning nobody else can claim it. So while you're typing /msg NickServ, you're just messaging the NickServ with no checks of who is using that nick while the target of the alias is "NickServ!NickServ@services." instead. | 17:19 |
Helenah | You could also just: /msg NickServ@services. | 17:20 |
joerg | while a /query nickserv massively increases the chances you avoid leading space typos to disclose whole command parameter messages into an arbitrary public channel, and the https://i.imgur.com/WV6ds05.png "@services.libera.chat" hostmask is a good indication you don't chat to a rogue impersonator and chances you see that hostmask are much higher in a /query dedicated tab | 17:22 |
joerg | and any considerations about "other networks" is basically pointless since you have no way to guesss if that other network has any services at all, and how they're named there | 17:24 |
joerg | particuly we're on libera network here and users ask "libera related IRC questions" | 17:24 |
lts | Dear both, surely this is not a matter important enough to spend a fine Friday on. #devuan-offtopic if you really want to continue, please? | 17:26 |
Helenah | lts: Sure. | 17:26 |
joerg | lts: actually this should go to #libera, since it's libera's own emails and FAQs that recommend /msg nickserv VERIFY foobar etc. When I suggest to use a /query (*without* command/message parameter!) instead, I'm not willing to take bashing about this allegedly would introduce additional risks of impersonating services that apply on other networks only | 17:49 |
joerg | and maybe I'm dull but I still not seen why a /raw or /quote would help with this, and how | 17:53 |
joerg | so yes, take it to #libera please | 17:53 |
Helenah | joerg: You need to learn that not every mistake made in a situation is everyone elses but your own fault. We both went offtopic, I don't appreciate this blame game. | 18:06 |
joerg | please take it to #libera ! last warning. If you want to tell me what you think I to must learn, you're welconme to do so in a /query | 18:09 |
sabas3dgh | Hello | 23:43 |
sabas3dgh | How could I learn about how to run/stop/reload services in devuan? | 23:44 |
debdog | sabas3dgh: /etc/init.d/ contains the cripts. /etc/rcX.d/ contains the links for automatically calling the scripts depending on runlevel (the X in rcX.d) | 23:47 |
sabas3dgh | debdog, anymore information on devuan site (maybe). how to activate-deactivate? | 23:48 |
debdog | to just stop a service run e.g. "/etc/init.d/slim stop" as root | 23:48 |
debdog | same for start and restart | 23:49 |
sabas3dgh | what is the usage of rcX.d? | 23:50 |
joerg | they have the links that tell the init system what to start/stop during boot and shutdown | 23:51 |
joerg | the links defining runlevel 1 are in rc1.d/ etc | 23:51 |
joerg | aiui | 23:52 |
debdog | inside each of those dirs are READMEs with an explanation | 23:52 |
joerg | :-) | 23:52 |
joerg | there's this command, was it insserv? | 23:52 |
debdog | for startup the default runlevel is 2, so look at rc2.d | 23:52 |
sabas3dgh | is it the run service OpenRC? or something else special to devuan? | 23:54 |
debdog | the default is System V ini | 23:54 |
debdog | t | 23:54 |
debdog | openrc is availbe, too | 23:55 |
debdog | it's the one debian used by default in the past. so there still may be some docs on their wiki | 23:56 |
joerg | sabas3dgh: http://reisenweber.net/irclogs/libera/_devuan/_devuan.2022-08-05.log.html#t2022-08-05T05:41:29 ff related | 23:56 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!