[00:10] [telegram] It is safer to use your ~/.bashrc since that only belongs to your user. (re @Rodrigo: Hello, where does Lubuntu store the system-wide PATH variable? I read in a blog that "Ubuntu uses /etc/environment for the system-wide configuration and you find the default paths in this file." [00:10] [telegram] But in my Lubuntu there is only /etc/environment.d/ where I only find a single file (90qt-a11y.conf) [00:10] [telegram] I do have a ~/.bashrc file, but I am not sure if I will damage my system by changing it so I thought I'd ask first..) [10:04] hello [10:20] G'day steeeve127, if you have a Lubuntu support question, please just ask it (people will respond as they're able to). [10:21] what is this app [10:21] not lubuntu, quassel [10:22] Have you looked at the manual; eg. https://manual.lubuntu.me/stable/2/2.1/2.1.3/Quassel_IRC.html (stable=21.04, change 'stable' to 'lts' for the LTS manual in the url) [10:29] I'm on IRC (also ~33 rooms on libera, a few more on OFTC..) but this room is also linked to telegram, matrix.... (IRC/quassel is very resource light, esp. if compared to other choices...) [12:38] [telegram] great, thanks (re @kc2bez: It is safer to use your ~/.bashrc since that only belongs to your user.) [14:15] [telegram] I am running 18.04.5 on a Toshiba Satellite and trying to connect a Brother MFCJ5320DW printer. I have got step by step instructions from Brother [14:15] [telegram] The ip address is showing on printer as 0.0.0.0 and when I get to the gunzip linux-brprinter-installer-2.1.1-1.gz I get 'only root can perform this. [14:15] [telegram] After getting live support from Brother and repeating the message on screen says 'unable to find file or directory. [14:15] [telegram] Can anyone help? [14:15] [telegram] I know it is EOL but could do with getting the printer working. [14:15] [telegram] Thanks [14:25] T34P4RTY: i assume no one here will be willing to help you do anything but upgrade until you have upgraded to a supported release. [15:37] T34P4RTY is the printer itself shows IPv4 address 0.0.0.0 that suggests it tried to get a lease via DHCP4v and failed, which implies it cannot connect to the network's DHCPv4 server [15:38] wow drone, really? quieting our relay bot? >.> I'll have to discuss getting you fixed >.> [16:42] [telegram] Works on other devices though, surely none would work if that was so? (re @lubuntu_bot: (irc) T34P4RTY is the printer itself shows IPv4 address 0.0.0.0 that suggests it tried to get a lease via DHCP4v and failed, which implies it cannot connect to the network's DHCPv4 server) [16:47] T34P4RTY are those other devices using IPv4 or IPv6? many printers have adopted 'driverless' printing an advertise IPP (Internet Printing Protocol) using mDNS-services (Multicast DNS). It is possible that device is advertisting itself on IPv6 but not IPv4. Worth checking if only to know precisely how other PCs are talking to the printer [20:55] hai === ibra71 is now known as RyomenSukuna [22:16] [telegram] Other devices use both ipv4 and ipv6, I found this out when setting up broadband a while ago (re @lubuntu_bot: (irc) T34P4RTY are those other devices using IPv4 or IPv6? many printers have adopted 'driverless' printing an advertise IPP (Internet Printing Protocol) using mDNS-services (Multicast DNS). It is possible that device is advertisting itself on IPv6 but not IPv4. Worth checking if only to know precisely how other PCs are talk