- Arch-general - lists.archlinux.org

[arch-general] community/NUT replacing Network-UPS-Tools -- won't start.
by David C. Rankin 29 May '20

29 May '20

On upgrade I agreed to: :: Replace network-ups-tools with community/nut? [Y/n] network-ups-tools-2.7.4-5 [removal] nut-2.7.4-1 (both same version of package) However, after install, the nut-server.service would not start. Here are the logs for the last start before update and then the failure after the update: -- Reboot -- May 23 03:00:55 2pi systemd[1]: Starting Network UPS Tools - power devices information server... May 23 03:00:56 2pi upsd[474]: fopen /var/state/ups/upsd.pid: No such file or directory May 23 03:00:56 2pi upsd[474]: listening on 127.0.0.1 port 3493 May 23 03:00:56 2pi upsd[474]: listening on 127.0.0.1 port 3493 May 23 03:00:56 2pi upsd[474]: listening on ::1 port 3493 May 23 03:00:56 2pi upsd[474]: listening on ::1 port 3493 May 23 03:00:56 2pi upsd[474]: Connected to UPS [stp_ups]: usbhid-ups-stp_ups May 23 03:00:56 2pi upsd[474]: Connected to UPS [stp_ups]: usbhid-ups-stp_ups May 23 03:00:56 2pi upsd[475]: Startup successful May 23 03:00:56 2pi systemd[1]: Started Network UPS Tools - power devices information server. May 29 03:55:42 2pi upsd[475]: mainloop: Interrupted system call May 29 03:55:42 2pi upsd[475]: Signal 15: exiting May 29 03:55:42 2pi systemd[1]: Stopping Network UPS Tools - power devices information server... May 29 03:55:42 2pi systemd[1]: nut-server.service: Succeeded. May 29 03:55:42 2pi systemd[1]: Stopped Network UPS Tools - power devices information server. -- Reboot -- May 29 03:58:08 2pi systemd[1]: Starting Network UPS Tools - power devices information server... May 29 03:58:08 2pi upsd[480]: fopen /run/nut/upsd.pid: No such file or directory May 29 03:58:08 2pi upsd[480]: /etc/nut/upsd.conf is world readable May 29 03:58:08 2pi upsd[480]: /etc/nut/upsd.conf is world readable May 29 03:58:08 2pi upsd[480]: listening on 127.0.0.1 port 3493 May 29 03:58:08 2pi upsd[480]: listening on ::1 port 3493 May 29 03:58:08 2pi upsd[480]: listening on 127.0.0.1 port 3493 May 29 03:58:08 2pi upsd[480]: listening on ::1 port 3493 May 29 03:58:08 2pi upsd[480]: Warning: no UPS definitions in ups.conf May 29 03:58:08 2pi upsd[480]: Fatal error: at least one UPS must be defined in ups.conf May 29 03:58:08 2pi upsd[480]: Network UPS Tools upsd 2.7.4 May 29 03:58:08 2pi upsd[480]: Warning: no UPS definitions in ups.conf May 29 03:58:08 2pi upsd[480]: Fatal error: at least one UPS must be defined in ups.conf May 29 03:58:08 2pi systemd[1]: nut-server.service: Control process exited, code=exited, status=1/FAILURE May 29 03:58:08 2pi systemd[1]: nut-server.service: Failed with result 'exit-code'. May 29 03:58:08 2pi systemd[1]: Failed to start Network UPS Tools - power devices information server. May 29 04:09:14 2pi systemd[1]: Starting Network UPS Tools - power devices information server... May 29 04:09:14 2pi systemd[1]: nut-server.service: Control process exited, code=exited, status=1/FAILURE May 29 04:09:14 2pi systemd[1]: nut-server.service: Failed with result 'exit-code'. May 29 04:09:14 2pi systemd[1]: Failed to start Network UPS Tools - power devices information server. There is the very same definition of the ups in ups.conf, e,g, [stp_ups] driver = usbhid-ups port = auto desc = "stp CP825 UPS" Removing the community package and reinstalling the old package works fine, e,g, 04:16 2pi:~/.../pkg/x86_64/nut> sc restart nut-server 04:17 2pi:~/.../pkg/x86_64/nut> upsc stp_ups battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 3180 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 13.4 battery.voltage.nominal: 12 device.mfr: CPS device.model: UPS CP825 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.synchronous: no driver.version: 2.7.4 driver.version.data: CyberPower HID 0.4 driver.version.internal: 0.41 input.transfer.high: 140 input.transfer.low: 100 input.voltage: 122.0 input.voltage.nominal: 120 output.voltage: 122.0 ups.beeper.status: enabled ups.delay.shutdown: 20 ups.delay.start: 30 ups.load: 15 ups.mfr: CPS ups.model: UPS CP825 ups.productid: 0501 ups.realpower.nominal: 450 ups.status: OL ups.test.result: Done and passed ups.timer.shutdown: -60 ups.timer.start: 0 ups.vendorid: 0764 Why doesn't the new nut from community work? -- David C. Rankin, J.D.,P.E.

2 2

[arch-general] Viability of Go libraries in the repositories
by George Rawlinson 18 May '20

18 May '20

Hi all, It was good to read the changes to Go packaging in the arch-dev-public mailing list. I'd like to bring up the viability of having Golang libraries in the official repositories. Considering the fact that multiple[0][1] versions of the same Go libraries can co-exist in the same Go codebase ... is there really a need for the libraries to exist in the official repositories? There may well be a situation in the future where some Go binary requires multiple versions of the same library, but only the latest version exists in the repositories. [0]:https://blog.golang.org/v2-go-modules [1]:https://research.swtch.com/vgo-import

1 0

[arch-general] Kaffeine failure
by pete 17 May '20

17 May '20

Afternoon all Having issues recently with a couple of things one i can sort of live with the other i cant the unimportant one mouse needs double click to open a file otr start a program PITA but i can if essential live with it the other try to start kaffeine i get kaffeine 15-05-20 16:55:33.535 [Warning ] QCommandLineParser: already having an option named "h" 15-05-20 16:55:33.535 [Warning ] QCommandLineParser: already having an option named "help-all" 15-05-20 16:55:33.535 [Warning ] QCommandLineParser: already having an option named "v" 15-05-20 16:55:34.453 [Info ] kaffeine.dvb: Using built-in dvb device manager 15-05-20 16:55:34.660 [Info ] kaffeine.dev: Found dvb device P14f1880200709002: Conexant CX22702 DVB-T KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kaffeine path = /usr/bin pid = 5892 KCrash: Arguments: /usr/bin/kaffeine KCrash: Attempting to start /usr/lib/drkonqi 15-05-20 16:55:34.794 [Warning ] QSocketNotifier: Invalid socket 13 and type 'Read', disabling... 15-05-20 16:55:34.795 [Warning ] QSocketNotifier: Invalid socket 28 and type 'Read', disabling... 15-05-20 16:55:34.795 [Warning ] QSocketNotifier: Invalid socket 29 and type 'Read', disabling... qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 491, resource id: 0, major code: 20 (GetProperty), minor code: 0 I also have an icon issue all was fine up until a few days ago restarted the computer after a few days in hospital with a cancer problem ran "pacman -Syu" since then it has been a pain i ould like it working correctly again as it seems i will be spending more time not doing too much i have tried backing out all i can find that was updated to no avail Thanks Pete

3 6

[arch-general] usbguard
by Frank 16 May '20

16 May '20

Good evening, I'm trying to make usbgard work. I created the initial rules set with usbguard generate-policy > /etc/usbguard/rules.conf and started the usbguard.service. Now I testing it with a USB flash drive but am failing to make it work. The drive is plugged and usbguard list-devices gives the following output: 19: block id 058f:6387 serial "50624E36" name "Mass Storage" hash "icy/i6K1xnkICYPmiNNwJ18cmu5GqfsHSjCGuC5WIXg=" parent-hash "oDU77vx1EsfYlDoXkU7iWjsvmBNCDNTcCHp/V0hIFXc=" via-port "2-1.2" with-interface 08:06:50 with-connect-type "hotplug" However usbguard allow-device 058f:6387 throws the following error message: IPC ERROR: request id=1: Device lookup: device id: id doesn't exist lsbusb shows the device with the same id: Bus 002 Device 004: ID 058f:6387 Alcor Micro Corp. Flash Drive So what am I doing wrong here? Thanks Frank

3 3

[arch-general] PAM CAllback
by Andy Pieters 15 May '20

15 May '20

Hi I am looking to have PAM call a script after a successful 2F authentication. My impression is that it is not going to be possible. I even have got a question open on StackExchange about it [1] Any ideas? [1] https://unix.stackexchange.com/questions/586243/callback-when-logged-on-via…

2 4

[arch-general] Irritating bug in outdated version of gnome-flashback
by Roope Salmi 14 May '20

14 May '20

The current version of gnome-flashback in the repositories has a bug with taking screenshots to the clipboard using the keyboard shortcut. After using it a couple times, pasting the resulting image no longer works and crashes some targets. At the same time gnome-flashback locks up. More details in the upstream bug report: https://gitlab.gnome.org/GNOME/gnome-flashback/-/issues/50 It was fixed in 3.37.1. This is a feature I use daily, and I can imagine many others do too. gnome-flasback has been flagged outdated for a while now, and it seems the maintainer, Balló György has been inactive for some time. Can we get an update for this package? - Roope Salmi

1 0

Re: [arch-general] foldingathome-beta setup
by Jude DaShiell 14 May '20

14 May '20

I gave up on foldingathome-beta and installed the foldingathome package. A little more information was in that package for setup. The client was able to find an nvidia GEFORCe gpu on the machine so I enabled the foldingathome-nvidia service and afterwards ran systemctl status foldingathome and no errors this time and the system was given 500,000 steps and had completed 25,000 of them by the end of the status information. If this doesn't break I may be able to put it on a second computer and double my meeger contribution to this effort. --

1 0

[arch-general] foldingathome-beta setup
by Jude DaShiell 14 May '20

14 May '20

Is foldingathome-beta looking for the gpu on the motherboard or video card in my computer? When I searched this machine I got an intel with a 9 series number after it along with nvidia nouveau and radeon graphics if memory serves. The radeon graphics would have come up since the video monitor is a radeon 3 series if memory serves. If I can figure out which one to use my guess is delete all other incorrect lines in /opt/fah/GPUs.txt and maybe I get past this gpu error. I'm running foldingathome-beta on command line and was running foldingathome-noroot earlier until that package got replaced by this beta package. --

1 0

[arch-general] r8169: transmit queue 0 timed out - dying hardware?
by Bjoern Franke 12 May '20

12 May '20

Hi, a box running Arch on AsRock QC5000-ITXPH has some issues with it's ethernet chipset since several days: https://dpaste.org/hVfk Network is stuck then and it somehow resumes after 1 hour or so. I stumbled upon https://bugzilla.kernel.org/show_bug.cgi?id=199549, but changing the powermanagement did not help. The issue appears with 5.6.x and also 5.4.x LTS, now even the DHCP request failed after rebooting with 5.6.11. As it appears with both kernel branches, I hardly believe it's a kernel issue. But dying ethernet chipsets on a board? Regards Bjoern

4 6

[arch-general] cgal package out of date
by 王少东 12 May '20

12 May '20

Hello, cgal 5.0 has been released for a while https://www.cgal.org/releases.html But the cgal package is still 4.14.2 https://www.archlinux.org/packages/community/x86_64/cgal/ It's flagged out-of-date on 2019-12-05, please update the package. Thanks.

1 0