[03:39] <PrinceRylan42> Hello!
[03:39] <PrinceRylan42> My second monitor is acting buggy. When I drag a program over to it the cursor is misaligned with the program. And sometimes the program doesn't want to leave my primary monitor. And with a program like VSCode, When I click on some of the functions. It doesn't respond.
[03:39] <PrinceRylan42> I'm using a 6-7 year old Toshiba television hooked up to HDMI. It works fine as my second monitor in Windows 11
[03:39] <PrinceRylan42> I'm running an oracle virtual machine. And I have two monitors I have 2 monitors selected in the display settings of oracle and I have the video memory turned up to max (128mg). I've tried switching the graphics controller from VMSVGA to VBoxVGA and VBoxSVGA but that doesn't help. How do I get my second monitor to function properly? Let me know if
[03:39] <PrinceRylan42> you need more information. Thank you.
[09:17] <xu-help27w> hi all
[09:18] <xu-help27w> lokking for xubuntu-18.04-core-i386.iso from https://unit193.net/xubuntu/core/
[09:18] <xu-help27w> can anybody help?
[09:21] <nicoz> xu-help27w https://unit193.net/xubuntu/core/pending/
[09:22] <nicoz> not have i386
[09:24] <gnrp> xu-help27w: Heh, Unit193 is afaik also in IRC
[09:25] <nicoz> I don’t think there is the 32 bit version...at least of the release 23.04
[09:25] <gnrp> I mean here on libera. So maybe you can contact him directly.
[09:25] <gnrp> nicoz: No, last one seems to be 18.04
[09:25] <nicoz> yes
[09:26] <nicoz> for 32bit should choose another distribution
[09:29] <gnrp> xu-help27w: You find a torrent link though on the release page. https://xubuntu.org/news/xubuntu-18-04-release/ - I don't see any traffic though when opening it quickly
[09:29] <gnrp> but probably contacting unit193 directly will prove the most successful way
[09:31] <nicoz> xu-help27w or you can try another distribution that still supports 32bit like debian
[09:31] <xu-help27w> gnrp yes, there no peers (
[10:14] <stamasd> FWIW I fixed the problem I had yesterday with installing Xubuntu 22.04.1 on a HP thin client. The problem was that the installer failed to install the openchrome xserver on this machine which needed it (it has a VIA Chrome GPU, and does not work with generic framebuffer xservers). Someone may want to look into that and fix it. What I did is boot
[10:14] <stamasd> from a live USB drive (happened to be a Gentoo opne which was laying nearby), chrooted into the installation and installed openchrome. I rebooted, and everything was working fine with full GUI and no more weird automatic switching between virtual consiles. Installed OpenSSH too while I was chrooted, so I can remotely login. All is well.
[21:03] <c_89> Hi, I have created notify_script.sh in the path "/etc/nut/" with permissions 775 (root:nut) and add it in the "/etc/nut/upsmon.conf", but when UPS switch on battery nothing happens.
[21:03] <c_89> for testing I have write also this line, but nothing: `NOTIFYCMD "/usr/bin/notify-send \"HELLO\""`
[21:15] <gnrp> c_89: This channel is specific to xubuntu, but upsmon is not really a xubuntu thing. I guess if you go to a broader (or more specific) channel, you might find more help
[21:15] <gnrp> anyway, you should always just upload your upsmon.conf to help debugging
[21:16] <c_89> gnrp I also posted in the specific channel but there are few people connected
[21:17] <gnrp> !paste
[21:18] <gnrp> c_89: Anyway, you should upload your upsmon.conf
[21:27] <c_89> gnrp https://bpa.st/raw/JVRBU
[21:35] <gnrp> c_89: Have you tried enabling exec for other events than just battery? Just to check
[21:35] <gnrp> and does it write to syslog?
[21:35] <gnrp> or wall, resp.
[21:36] <c_89> gnrp I can try with `NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC`
[21:37] <gnrp> c_89: I mean, in general, you should see the notifications on any open terminal and in syslog
[21:37] <gnrp> *any* notification, actually
[21:43] <c_89> gnrp nothing the only log I see is this: https://bpa.st/raw/FUPOC
[21:45] <gnrp> and you are sure an even toccurs, i.e., you pull the plug?
[21:45] <gnrp> have you tried upsc to check whether you actually properly connected?
[21:50] <c_89> gnrp Yes the values battery.voltage, battery.voltage.high ...etc are displayed correctly with upsc, it is strange that in addition to ignoring the EXEC directive nothing is displayed even with the SYSLOG+WALL directive...
[21:53] <gnrp> actually, could it be that ' fopen /run/nut/upsd.pid: No such file or directory' is causing a problem?
[21:53] <gnrp> c_89: Anyway, the problem seems not to be in the notification, but actually upsd receiving the messages
[21:54] <c_89> gnrp how can I fix upsd.pid?
[21:54]  * gnrp doesn't really know so much about upsd, sorry. Only used it rarely
[21:58] <gnrp> c_89: But so you already tried pulling the plug? Or disconnecting the UPS (its USB or how it is connected)?
[22:00] <c_89> gnrp yes I unplugged it and upsc shows: `ups.status: OB`
[22:03] <gnrp> and you left it longer than five seconds unplugged?
[22:03] <gnrp> ah, wait. You should enter the MONITOR variables, I'd say
[22:04] <gnrp> it says you have to enter at least one...
[22:08] <c_89> gnrp tried more than 5 seconds the log is still the same!
[22:09] <gnrp> c_89: Yeah, you have to define a MONITOR
[22:10] <c_89> gnrp where do you say?
[22:10] <gnrp> c_89: It is in the beginning, just after RUN_AS_USER
[22:15] <c_89> gnrp yes it is present https://bpa.st/raw/JVRBU I wrote it at the end of the file
[22:15] <gnrp> aah, ok. So the file is not parsed in a certain order?
[22:16] <c_89> gnrp `# RUN_AS_USER nut` should it be uncommented?
[22:34] <c_89> gnrp xubuntu 22.10 is still stuck at v2.7.4 package when instead the latest version is v2.8.0