Package Details: vattery 0.7.5-3

Git Clone URL: https://aur.archlinux.org/vattery.git (read-only)
Package Base: vattery
Description: A GTK battery monitor for the sys-tray
Upstream URL: http://www.jezra.net/projects/vattery
Licenses: GPL
Submitter: timttmy
Maintainer: timttmy
Last Packager: timttmy
Votes: 30
Popularity: 0.000002
First Submitted: 2010-02-08 07:52
Last Updated: 2016-09-19 14:56

Latest Comments

psamim commented on 2016-09-18 07:49

==> ERROR: license should be an array

bidulock commented on 2016-03-06 13:47

license should be an array

timttmy commented on 2015-01-27 07:08

Unflagged out of date 0.7.5 is the latest version.
See https://launchpad.net/vattery/+download

Also updated PKGBUILD: added "package()" function to PKGBUILD.

timttmy commented on 2012-06-18 05:20

@donniezazen
A new release of vattery has been released. Hopefully it fixes the problem you were having.
Please see --> https://bugs.launchpad.net/vattery/+bug/1014119

donniezazen commented on 2012-05-21 20:13

@timttmy Yes, i will file the bug. According to thread https://bbs.archlinux.org/viewtopic.php?id=128453 battery information is stored in /sys/class/power_supply/BAT0. I have a Thinkpad t420i (4177-CTO).

timttmy commented on 2012-05-21 06:29

Looks like your battery info is stored elsewhere donniezazen

You should file a bug with Jezra https://bugs.launchpad.net/vattery/+bugs

Your laptop wouldn't be a toshiba would it? I used to have one as a server and I remember it stored it's battery stuff in a strange place.

timttmy commented on 2012-05-21 05:31

Looks like your battery info is stored elsewhere donniezazen

You should file a bug with Jezra https://bugs.launchpad.net/vattery/+bugs

Your laptop wouldn't be a toshiba would it? I used to have one as a server and I remember it stored it's battery stuff in a strange place.

donniezazen commented on 2012-05-20 22:05

Error opening directory '/proc/acpi/battery': No such file or directoryusing data type: None

timttmy commented on 2011-07-10 15:21

To quote from the vattery README
<quote>
-usage-
Run vattery when you need to keep track of a laptops
battery charge. Adding vattery to ~/.xinitrc might be
the most ideal way to use vattery.
</quote>

You are of course free to modify the PKGBUILD in any way to suit your needs. I don't wish to deviate the vattery install from which the programme author intended (and I did exchange emails with Jezra when creating the PKGBUILD).

Maybe you should file a bug/feature request upstream? https://bugs.launchpad.net/vattery

Regards
timttmy

dserban commented on 2011-07-10 14:20

Well, no.
Putting a .desktop file in /usr/share/applications doesn't make sense. I agree with that.
What I'm suggesting is to put a .desktop file in /etc/xdg/autostart, which has a different effect - it spares one the effort of manually editing the autostart file.
It's what several Arch packages do, polkit and wicd among them.

timttmy commented on 2011-07-10 14:10

I'm not sure if everyone would find a .desktop file useful, it maybe seen as clutter in a desktop menu.
As a Vattery user myself I just put an entry in my autostart file to start Vattery when I login.

I would add a .desktop file if enough people wanted it, but I think the autostart script is the correct way to start Vattery.
Regards
Marshall (timttmy)

dserban commented on 2011-07-10 09:46

I find it useful to create a freedesktop.org-compliant autostart entry for vattery, by appending the following snippet to the end of the PKGBUILD:

mkdir -p "${pkgdir}"/etc/xdg/autostart
DESKTOPFILE="${pkgdir}"/etc/xdg/autostart/${pkgname}.desktop
echo "[Desktop Entry]" > "${DESKTOPFILE}"
echo "Name=Vattery (battery monitor for the systray)" >> "${DESKTOPFILE}"
echo "Comment=Battery monitor for the systray" >> "${DESKTOPFILE}"
echo "Icon=battery" >> "${DESKTOPFILE}"
echo "Exec=vattery" >> "${DESKTOPFILE}"
echo "Terminal=false" >> "${DESKTOPFILE}"
echo "Type=Application" >> "${DESKTOPFILE}"
echo "Categories=GTK;Utility;Core;" >> "${DESKTOPFILE}"
echo "NotShowIn=KDE;" >> "${DESKTOPFILE}"

timttmy commented on 2011-06-17 14:38

Updated Vattery PKGBUILD to 0.7.4
Please Test :)

Cheers Jezra

Anonymous comment on 2011-06-16 19:07

The segfaulting is probably all my fault. Please submit bug reports at https://bugs.launchpad.net/vattery

Anonymous comment on 2011-06-16 07:22

Also segfaults for me after the last update:
(vattery:1648): GLib-CRITICAL **: g_regex_match_full: assertion `regex != NULL' failed

timttmy commented on 2011-06-15 20:14

It's working fine for me (eeepc 701)

ngoonee commented on 2011-06-15 00:40

Anybody getting segfaults on running this?