Package Details: kalu 4.1.0-1

Git Clone URL: (read-only)
Package Base: kalu
Description: Upgrade notifier w/ AUR support, watched (AUR) packages, news
Upstream URL:
Licenses: GPL3+
Submitter: jjacky
Maintainer: jjacky
Last Packager: jjacky
Votes: 164
Popularity: 2.258688
First Submitted: 2012-02-14 18:03
Last Updated: 2016-05-12 18:14

Latest Comments

T0t0 commented on 2017-08-14 00:26

Pour les francophones: Editez le pkgbuild en rajoutant " --with-news-rss-url=" sans les " " après ...prefix=/usr pour avoir les nouvelles en français :)

adam777 commented on 2016-02-29 12:00

Yep, working now, thanks :)

jjacky commented on 2016-02-29 11:08

Are you using the latest PKGBUILD (4.0.2-2) ? It should have a proper URL for the new AUR version.

adam777 commented on 2016-02-29 08:41

AUR search doesn't work.
I suppose you need to change the RPC search code, if that is what you are using.
Had to do the same with my custom AUR downloader script.

jjacky commented on 2016-02-23 17:05

1) all you need about icons support should be found in the man page
2) No need for sudo, no. kalu's updater does auth via policykit, so you'll likely need to have a polkit authentication agent running for things to work however.

blackhole commented on 2016-02-23 12:23

I have two problems:
1) I cannot change the tray icon
2) Authentication is failing. Maybe kalu is using sudo? How can I change that?

WoefulDerelict commented on 2016-02-04 17:26

I was having the same issue as adam777 with the 4.0.1 update. After building branch next and installing it I can verify the fix works and notifications are no longer empty.

jjacky commented on 2016-02-04 08:25

hmm... I guess that's what happens when you're tired. Stupid mistake on my part, just pushed a fix on branch next. Sorry about that.

Will have to release 4.0.2 very soon....

adam777 commented on 2016-02-04 05:29

I'm getting empty notifications with 4.0.1 for some reason.
Worked fine in 4.0.0

* EDIT *
Weird, it's working now after a few reinstalls.

N3mesis98 commented on 2016-02-01 20:14

Am I the only one getting this error when trying to launch the latest version of kalu (4.0.0-1) ?

(kalu:12930): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
Segmentation fault (core dumped)

jghodd commented on 2016-02-01 18:23

This is no longer building. Even when the 'pacman<4.3' dependency is removed from the PKGBUILD file, it's running into an issue with the latest pacman changes (

- alpm_siglevel_t - removed members ALPM_SIG_PACKAGE_SET, ALPM_SIG_PACKAGE_TRUST_SET

- alpm_event_pacorig_created_t
- alpm_event_t.pacorig_created

It's interesting that kalu-kde does build with the 'pacman<4.3' dependency removed, but kalu does not.

[Edit: the other comments weren't here when I started this post. I've used the pacman-5 branch to rebuild kalu and kalu-kde and both appear to be working fine.]

Pinerto commented on 2016-02-01 14:36

Works. >> ""pacman-5" instead of "next"
Only this
"warning: directory permissions differ on /usr/share/polkit-1/rules.d/
filesystem: 750 package: 700"


jjacky commented on 2016-02-01 14:24

You can't build this package because it requires a new upstream version, which doesn't exist yet; This is to be expected.

Again, you can simply use the PKGBUILD from kalu-git but using branch "pacman-5" instead of "next" to build a pacman 5-compatible kalu, while waiting for the new version.

Pinerto commented on 2016-02-01 14:20

Pls update at least your PKGBUILD.
Pacaur and aura are unable to build, because of the PKGBUILD.

jjacky commented on 2016-02-01 14:13

Not sure what you did, there's no actual error message here, but no: building from branch pacman-5 works fine with pacman 5.0
Obviously you need to build from git, so again using kalu-git's PKGBUILD but editing it to use the right branch (plus tweak dependencies).

I have to admit I was expecting pacman-5 to stay in testing a little bit longer, and I'm not ready just yet... but a new release of kalu will come soon. Meanwhile, you can build kalu from branch pacman-5 on github for a compatible version.

Pinerto commented on 2016-02-01 12:53

"simply build from that branch (e.g. using kalu-git from the AUR only changing the branch name in the PKGBUILD) "

Even with these changes, the build stop at:

Makefile:1118: recipe for target 'src/kalu-dbus/kalu_dbus-kalu-dbus.o' failed
make[2]: *** [src/kalu-dbus/kalu_dbus-kalu-dbus.o] Error 1
make[2]: Leaving directory '/home/archie/Downloads/kalu/src/kalu-3.0.0'
Makefile:1380: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/archie/Downloads/kalu/src/kalu-3.0.0'
Makefile:615: recipe for target 'all' failed
make: *** [all] Error 2
==> ERROR: A failure occurred in build().

It is the same for kalu and kalu-git too.

adam777 commented on 2016-02-01 07:21

I'll have a look, thanks.

jjacky commented on 2016-01-30 14:29

Branch pacman-5 was just pushed on github, so to use kalu alongside pacman 5.0 simply build from that branch (e.g. using kalu-git from the AUR only changing the branch name in the PKGBUILD)

adam777 commented on 2016-01-30 06:46

Please update for pacman 5.0.0 :-)

jjacky commented on 2016-01-26 17:07

Does it actually list those packages? Did you change your pacman.conf? Sounds like you removed a repo or something, so now all packages from there are seen as foreign, and therefore looked for, and reported missing from, the AUR.

oboedad55 commented on 2016-01-25 23:44

Odd problem started today. I have about 15 AUR packages installed. However, kalu says I have 1011 installed that are no longer in the AUR. Anyone have any ideas?

jjacky commented on 2016-01-25 21:29

There's a configure option (--with-news-rss-url) to set the URL of the RSS feed to use.

lenardcamilleri commented on 2016-01-25 20:52

Can anyone tell me if I can edit the source where kalu gets the news. To change it from arch's to something else

jjacky commented on 2015-10-14 13:04

hmm.. I can't reproduce this. Sounds like this might be coming from your theme maybe, especially if this happens with other applications (e.g. pkgclip).

I tried a couple themes but no crash here. Maybe try with a different theme, or start e.g. `GTK_THEME=Raleigh pkgclip` from a terminal and see if it works or not. If so that means it's an issue with your current theme.

martynjy commented on 2015-10-13 19:18

Crashes when 'Preferences' is invoked:

Program received signal SIGSEGV, Segmentation fault.
0xb787a8ea in ?? () from /usr/lib/

GTK3 was upgraded today:
upgraded gtk3 (3.18.1-1 -> 3.18.2-1)

Update. The exact same segfault happens with pkgclip.

SOLVED: Problem traced (thank you jjacky) to xfce-dusk-gtk3 theme.

jjacky commented on 2015-03-29 14:50

Note sure what "doesn't work" mean, but if it was a compilation error re: LC_MESSAGES it should be fixed now, try again please.

remussatala commented on 2015-03-29 01:42

Something like that for kalu-git PKGBUILD?

options=('!strip' 'debug')"

I tried that and it does not work.

jjacky commented on 2015-03-28 16:59

Just use kalu-git from the AUR, but adding the options to the PKGBUILD before running makepkg. Then install it (via pacman) as usual, and it will replace kalu.

remussatala commented on 2015-03-28 04:22

So, what command should I install Kalu?

jjacky commented on 2015-03-27 17:03

Right, I meant if you could recompile kalu with:
options=('!strip' 'debug')
in the PKGBUILD so it has debug symbols. In fact, if you could do that using the PKGBUILD for kalu-git instead, it'd be even better.

Then run `gdb kalu` from a terminal, type 'r' to run kalu from gdb, and when it crashes type 'bt full' to get a backtrace; That backtrace might be helpful figuring out what's causing the crash.

remussatala commented on 2015-03-27 04:14

remussatala commented on 2015-03-27 03:52

I have not edited file PKGBUILD. "Segmentation fault (core dumped)" That is all I have.

jjacky commented on 2015-03-24 12:34

remussatala: I'm afraid I'll need more info. If you could e.g. compile kalu with options=('!strip' 'debug') (in PKGBUILD) and send me a backtrace of the crash, that might help figuring out what's happening.

remussatala commented on 2015-03-23 22:46

Segmentation fault (core dumped)
if when pressing "About" in xfce.

hectorsales commented on 2014-12-29 09:07

@jjacky, thanks your PKGBUILD works fine, Now pacman 4.2 is in 'core' repo.

jjacky commented on 2014-12-28 13:18

Yes, I'll update this PKGBUILD once pacman-4.2 hits core; Meanwhile if you're already using it you can either use kalu-git or e.g. this PKGBUILD[1] to install kalu 3.0.0


hectorsales commented on 2014-12-28 08:04

Hi,@jjacky, i have seen that there is a new version of kalu (git) supporting pacman=> 4.2.x, a simple question, when pacman 4.2 update, now in testing, you will update this kalu (non git)?


jjacky commented on 2014-11-12 09:26

Yes it's a known issue with GTK+ 3.14, you can either apply the workaround[1] manually, or simply switch to kalu-git to use the latest dev version, where this has been fixed already.


Ennoia commented on 2014-11-12 07:54

I've got huge icons in the drop-down menu (about 44 px). Should probably be half the size (seeing the blank between each line).
I've tried several gtk2/3 theme or icon theme: nothing change.

Aerion commented on 2014-09-26 15:24

Bug report link

Aerion commented on 2014-09-26 14:44

Of course, I should have thought of that, as knotify4 or indeed kdebase-runtime, is not listed as one of the packages providing notification-daemon.

I'll open a bug report for it.


jjacky commented on 2014-09-26 12:06

kalu uses libnotify, and a notification daemon is required for notifications to actually be shown, etc This is why in the PKGBUILD you find a dependency on notification-daemon -- Now usually when you install another one (other than package notification-daemon), e.g. xfce4-notifyd, it will provide notification-daemon, to handle such dependencies.

So I'd say it seems that this might be a packaging issue on kdebase-runtime, which should have such a provide; you might try and report that. Meanwhile, you could e.g. ignore the dependency on install, install an empty package depending on kdebase-runtime and providing notification-daemon (that should "fix" your dependency issue), or simply remove that dependency from kalu's PKGBUILD, and it should work fine.

Aerion commented on 2014-09-26 11:52

This is by far the best upgrade notifier for Arch Linux, thanks!

It works beautifully on a number of MATE desktops, but on all my KDE machines the installer want to install a notification daemon, even though knotify4 is installed as part of kdebase-runtime.

Can kalu not communicate directly with knotify4?

gabx commented on 2014-05-17 12:20

I am not satisfied with my kalu setup within i3. Do you have any pointer for a working config of kalu inside i3 ?
TY in advance

jjacky commented on 2014-05-13 12:08

Well, it's not really a choice but more that I haven't looked into using systemd to manager user sessions yet (and I believe this is still a work in progress at this point). It might eventually happen...

gabx commented on 2014-05-13 10:47

TY for you very good and simple app. I am wondering why there is no systemd service unit. Is it a deliberated choice ?

mask2011 commented on 2014-03-29 09:19

I use kalu for about 6 or more months. Sinced I posted here I haven't had any issues. If it happpens again I'll try to provide further info.

jjacky commented on 2014-03-15 12:26

Yeah, any info would help. Did you use kalu before 2.4.0 and if so, if this new with this version? If you can start kalu using `kalu -dd` and send me the output of the crash it might help.

Also, if you could send have a backtrace that'd be great. If you hve gdb, you might be able to do `systemd-coredump gdb kalu` to load the latest coredump into gdb, then do `bt full` and send me the output.

Feel free to email me said outputs, or if you have questions.

mask2011 commented on 2014-03-14 21:41

I get random crashes when trying to update. It even goes away from the tray.

I haven't noticed doing something specific before hand. If there is a way to provide further info please tell me.

LithiumPT commented on 2014-02-17 00:06

Thanks jjacky! I did not have the whole base-devel group installed, all fine now :)

LithiumPT commented on 2014-02-17 00:06

Thanks jjacky! that was it :)

jjacky commented on 2014-02-14 12:52

Any chance you don't have pkg-config installed (it is required, and expected to be installed as it is part of base-devel) ?

LithiumPT commented on 2014-02-14 11:43

I keep getting this error when running 'makepkg -s':

configure: error: libnotify is required
==> ERROR: A failure occurred in build().

$pacman -Q libnotify
libnotify 0.7.6-1

$pacman -Q notification-daemon
notification-daemon 0.7.6-2

what's happening? (I've got all the other listed dependencies too...)

sgtpep commented on 2013-10-18 11:53

Build fails with error: "configure: error: libnotify is required", but package libnotify is installed and directory /usr/include/libnotify exists.

sgtpep commented on 2013-10-18 11:52

Build fails with error: "configure: error: libnotify

justin8 commented on 2013-07-16 06:21

Can you please add arch='armv7h' as well? Tested on a samsung chromebook and it is working perfectly.

sir_sure commented on 2013-06-04 21:03

I see, seems like I haven't grasped Kalu's philosophy until now. What I would like to have is an icon show up in the systray and a libnotify notification pop up at every session start (i.e. after fresh boot), but only if there are actually updates available (given that we are Arch users this happens fairly frequently ;-) ). The reason for this is that I usually only do system upgrades immediately after booting, so I wouldn't rely on Kalu being there for me all the time :-)

But, as I already mentioned, it seems like I wasn't aware of Kalu's purpose yet. Given the wealth of its features, maybe it is a bit too much of an overkill for my purpose. A simple script will probably suffice.

Anyways, thank you very much for your neat work and efforts! The comprehensive yet very concise man pages deserve a special mention at this point.

jjacky commented on 2013-06-03 13:40

Seems you're trying to use kalu only "on demand" to do a sysupgrade, but that's not really what it was designed for. Meaning, it is first an upgrade notifier, that does indeed sit in your systray all day long, checking for upgrades and notifying when there are any every once in a while.
That's the idea, so quitting after a check or after running a sysupgrade wouldn't really be useful then.

If you wanna use kalu for a one-shot operation, you could run `kalu -a` though that is CLI-only. I'm not sure doing a GUI equivalent would be worth it, because kalu needs to stay alive as long as the notifications are (so it can handle the clicks on action-buttons), and again, having it quit right after feels somewhat "odd" and against the idea to me...

sir_sure commented on 2013-06-03 12:56

Cool app! It would be great if there was an option which would allow automatically quiting kalu once a system update is done. Of course you could also do that by running a script after an update (which is already possible), but a solution not involving kill would be cleaner.

Also, an option preventing Kalu from starting if there are no updates available would be cool so that after auto-starting Kalu on session login it would not start and linger in the notification area.

Anyways, thank you for writing Kalu!

moonman commented on 2013-06-02 09:37

Thank you

jjacky commented on 2013-06-01 17:20

Yeah, sounds like a good idea. I'll see to do that, thanks.

moonman commented on 2013-06-01 06:24

I agree,
but you could probably change the group of "wheel" to let's say "kalu", include the file and just document that users would need to add themselves to group "kalu" in order to get rid of passwod-asking. Seems a little easier than messing with these polkit policies. Not trying to force anything on you though, just a friendly suggestion. I appreciate the great application you've created.

jjacky commented on 2013-05-31 16:31

This is a nice tip, thanks. I know some people might be interested in this, so I'll add it to the man page or something; but I'm not sure I wanna add the file as part of the package.

I mean, a sysupgrade remains an important and possibly critical operation in how it can affect one's system, so I think by default it should require user authentication.

moonman commented on 2013-05-31 11:23

would it be possible to add /etc/polkit-1/rules.d/20-kalu.rules
with this in it:

polkit.addRule(function(action, subject) {
if (( == "org.jjk.kalu.sysupgrade") &&
subject.isInGroup("wheel")) {
return polkit.Result.YES;

so the users of group wheel wouldn't be prompted for the password. Thank you

adam777 commented on 2013-04-05 05:32

And now that pacman 4.1 is out on [stable], please update Kalu to support it.

bayi commented on 2013-04-01 23:52

nevermind i found the PKGBUILD on your site.... my brain was in write only mode again

bayi commented on 2013-04-01 23:51

Hi i saw on your site that there is already an updated version for pacman 4.1 +
Can you please update the PKGBUILD or, upload a new package that works with the new pacman ? I miss kalu since i updated today ( yes im on testing ... )

michaudg commented on 2013-04-01 21:27

Wonderful tool! Just what i was looking for. Works great with GNOME 3.6! Thanks for your work.

oboedad55 commented on 2013-03-22 15:41

Hmmm... Nothing shows up in the news box under Cinnamon.

jjacky commented on 2013-03-22 10:48

When the notification for unread news shows up, click the "Show News" button; Then from that window you can select which news to mark (by default they're all selected) and just click "Mark Read"

oboedad55 commented on 2013-03-22 02:43

@jjacky, how do I clear the news? Thanks!

jjacky commented on 2013-03-20 18:15

Well, the original icon is a 48x48 PNG so it can look better at that size, I meant to say it is supposed to be smaller (i.e. it's natural size when kalu "attaches" it to the notification is smaller, by design).

I just realized, though, that I forgot to say: you can change it. If you want a bigger icon on notification, change it on Preferences. You can even just use kalu's logo (/usr/share/pixmaps/kalu.png), when loading it from a file that way it'll be kept at its natural size, here 48x48. (Of course, you can also use any other logo of any size you want.)

aricart commented on 2013-03-20 17:39

Maybe if it were a larger scalable icon it wouldn't be as problematic? (SVG?) This could also help for panels that display icons of varying sizes.

adam777 commented on 2013-02-09 18:51

Thanks for the quick reply.
Indeed, the notifications pile up, if I'm away from the system.
Anyway, I see this is all on KDE.
Thanks again for the great work and the ongoing support

jjacky commented on 2013-02-09 11:51

- the icon does look ugly, and I think that's because it's not supposed to be that large; It should be the same as in the systray. Nothing's changed about this in kalu though, so I'd guess this comes from your notification daemon.

- I'm not sure what you mean by "added" -- yes, after each check if there are updates kalu triggers a new notification, that's indeed how it works, has been the case from day one.
What I would guess is, if you have changed/updated your notification daemon, maybe it didn't used to keep old/past notifications around, and now keeps them in a list or something. Is that what you mean by added?
Again, this would be something from your notification daemon, not kalu.

adam777 commented on 2013-02-09 00:19

2 small issues with KDE 4.10.
- The update notification look a bit weird (icon seems to be of low quality).
- When an update is available, with each check, another notification is added.
In previous versions of KDE, only one notification was displayed.

Both issues are of low priority, of course.

adam777 commented on 2013-01-30 15:45

Just a heads up.
Latest oxygen-gtk seems to solve the graphic glitches I've had since gtk updated back in november.

adam777 commented on 2012-12-05 21:45

Oh, I suppose the "update system" button should have triggered an alarm.
Guess I judged too soon. Thanks.

jjacky commented on 2012-12-05 17:05

Yes, this is normal. Computing the list of packages with upgrades for notifications is a no-user-interaction process, so in cases of conflict such as this one (where user input is required to know what to do), you get such a message on the notification.

However, you can still use kalu's updater to do the sysupgrade, in which case you'll then be asked the same question(s) you would with pacman, only in a GUI ;)

adam777 commented on 2012-12-05 16:59

Latest dbus update caused the following message to appear:

Unable to compile list of packages
Failed to prepare transaction:
conflicting dependencies
- dbus and dbus-core are in conflict

Manually using pacman -Syu yields the following:
:: Replace dbus-core with core/dbus? [Y/n]

I accepted and update continued as expected.

jjacky commented on 2012-11-09 09:17

I don't think there's anything I can do, no. You could try another using theme, if it still happens then it might be an issue with gtk3 & KDE, else it'd be coming from oxygen-gtk.

I don't use KDE nor that theme, but I haven't had any issue with the latest gtk3.

adam777 commented on 2012-11-09 08:48

Not sure it's even up to you, but latest gtk3 messes up kalu under KDE using the oxygen-gtk theme.

jjacky commented on 2012-10-27 18:41

Yes, thanks, I saw that too. It was due to a bug parsing JSON from the AUR, which always assumed valid JSON. Version 1.3.0 is out now, fixing this (amongst other things).

adam777 commented on 2012-10-27 17:14

There seem to be some bug with AUR checking.
During the recent AUR downtime, whenever Kalu checked for updates, it crashed (tray icon disappeared, process not running).
As nothing changed comparing to current situation except the AUR being back up (now update checking works as usual), and the crashed was 100% reproducible, I think the blame lies there.
Sadly I do not know the exect response Kalu received during that period, so I'm not sure how you can address it.

jjacky commented on 2012-10-21 19:24

Yes, little bug due to the switch of the main site to https-only (kalu used http and didn't follow redirections).

Fixed in v1.2.1, now available.

adam777 commented on 2012-10-21 18:23

I'm having problems with news checking.

Unable to check the news
Error on line 9 char 8: Element 'body' was closed, but the currently open element is 'hr'.

News hasn't changed on front page, perhaps something changed in the page code.

gabx commented on 2012-10-06 17:26

I use polkit 0.107-2, which support systemd.
I didn't have a running agent ! Installing polkit-gnome solved my issue. I have now the UI window.

gabx commented on 2012-10-06 17:26

I use polkit 0.107-2, which support systemd.
I didn't have a running agent ! Installing polkit-gnome solved my issue. I have now the UI window.

gabx commented on 2012-10-06 15:56

I use polkit 0.107-2, which support systemd.
I didn't have a running agent ! Installing polkit-gnome solved my issue. I have now the UI window.

jjacky commented on 2012-10-06 12:07

Since you said you don't use consolekit, did you make sure to compile polkit using --with-systemd, so that it can work with systemd's logind ? I believe you need to do so for polkit to actually see your active session (else it relies on consolekit).
Just did a quick test in a VM, and it should work as expected (your polkit agent asking for your password) in a "pure" systemd system w/out consolekit. BTW you do have a running polkit agent, right? Otherwise that might be why the polkit auth failed: because there's no running agent (e.g. polkit-gnome) to ask for your password.

gabx commented on 2012-10-06 11:13

$ loginctl show-session 1

I guess my session is seen as active.
I will wait for next upgrade then.

jjacky commented on 2012-10-02 10:52

The polkit policy used requires your session to be properly seen as active by polkit, so you either need to make sure it is, or you could also edit the policy to remove said requirement.

The latter requires to edit a file that will be replaced on upgrade, but in fact next version will not require an active session anymore:

gabx commented on 2012-10-02 08:54

When I want to upgrade. Failed to initialize. Authorization from Policykit failed.
Need to # kalu to be able to upgrade.
What shall I do to solve this issue? (I do not use consolekit for my XFCE session).
TY for your work.

gabx commented on 2012-10-02 08:54

When I want to upgrade. Failed to initialize. Authorization from Policykit failed.
What shall I do to solve this issue? (I do not use consolekit for my XFCE session).
TY for your work.

gabx commented on 2012-10-02 08:53

When I want to upgrade. Failed to initilize. Authorization from Policykit failed.
What shall I do to solve this issue? (I do not use consolekit for my XFCE session).
TY for your work.

mrbit commented on 2012-09-15 12:04


PhotonX commented on 2012-07-21 11:44

Problem has been solved by itself. It might be because I didn't have my glibc updated and some modules were still in /lib rather then in /usr/lib. Now after the update of glibc the package builds and works fine. :)

jjacky commented on 2012-07-21 11:13

Afraid not. I assume you have pacman 4.0 correctly installed; you could try `gcc -print-search-dirs` and make sure that /usr/lib is on the libraries list. You could also try adding it, e.g. running `export LIBRARY_PATH=/usr/lib:$LIBRARY_PATH` before you ran configure/makepkg...

PhotonX commented on 2012-07-21 07:35

I see. Have you any hints about how to find the cause of the problem?


jjacky commented on 2012-07-20 20:29

Not sure why you get that, but it seems like some error/problem on your side though; libalpm is a dep, since it is provided by pacman.

PhotonX commented on 2012-07-20 19:53

Seems like libalpm is missing as dep, at least I get

checking for alpm_db_get_pkg in -lalpm... no
configure: error: libalpm is required
==> ERROR: An error occured in build().
Aborting ...
==> ERROR: Makepkg was unable to build kalu.
==> Restart building kalu ? [y/N]

Installed packages that might be interesting:

$ yaourt alpm
1 extra/pyalpm 0.5.3-1 [installed]
Libalpm bindings for Python 3
2 archlinuxfr/package-query 1.0.1-1 [installed]
Query ALPM and AUR
8 aur/package-query 1.0.1-1 [installed] (1623)

jjacky commented on 2012-05-20 17:19

@denoyse: right, your policy file got overwritten during the update. I believe this could be avoided by putting the file in the backup array of the PKGBUILD, however i don't really see it as a configuration file, so I won't do that.
Of course, you can add it yourself before making the package.

denoyse commented on 2012-05-20 14:01

After the update to 1.0 - of course - the system asks for the password again. would it be possible to add an option to maybe 1.1 where you can set up permissions to allow a passwordless update?


chadberg commented on 2012-05-11 22:59

Had to ln -s pod2man into /usr/bin for it to compile (I think lightdm is screwing up my path), but it's in, and I love it! Was using yapan, but kalu just shot to the top of my list....

denoyse commented on 2012-05-06 11:13

Yep, i got that (yaourt -Syua)

I allready wondered why i was asked for a password, as i tryed to allow everything via sudo. I will try the policy file, thx for the tip!
EDIT: Works perfectly, thanks!

denoyse commented on 2012-05-05 11:44

Yep, i got that (yaourt -Syua)

I allready wondered why i was asked for a password, as i tryed to allow everything via sudo. I will try the policy file, thx for the tip!

jjacky commented on 2012-05-05 10:16

kalu-dbus is started automatically w/ root privileges already, that's not the issue. If you really want to allow sysupgrade w/out password check, I think you'll need to change the policy (in /usr/share/polkit-1/actions/org.jjk.kalu.policy) and replace auth_admin with yes

As for AUR upgrade, that's not gonna happen. kalu's updater simply provides a little GUI for libalpm's sysupgrade, nothing more. But you can have a button (on AUR notifications) to start an (AUR) helper of your choice to take care of it.

denoyse commented on 2012-05-05 07:30

I'll give it a shot, seems to be nice...
Is is possible (and if: how) to avoid entering the password? Can i add an rc script that starts kalu-dbus with root-privileges or something like that?
As feature request: Would be nice to add an AUR upgrade, but i am surely not the first to mention ;-)

denoyse commented on 2012-05-05 07:30

I'll give it a shot, seems to be nice...
Is is possible (and if: how) to avoid entering the password? Kann i add an rc script that starts kalu-dbus with root-privileges or something like that?
As feature request: Would be nice to add an AUR upgrade, but i am surely not the first to mention ;-)

jjacky commented on 2012-04-19 11:33

oh right, little mixup there between SyncDbsInTooltip & SaneSortOrder... Thanks, both this and the typo will be fixed in, coming up later today.

Anonymous comment on 2012-04-18 21:30

Hello, first of all thanks for your app, it's awesome!
I'm experiencing a small issue: in the misc tab unchecking "Show if databases can by (be?) synchronized in tooltip" doesn't work ... SyncDbsInTooltip in kalu.conf is always set to "1"

gobonja commented on 2012-03-27 13:01

Kalu is on it's way to become default update manager for Nosonja.