Package Details: kalu-kde 4.5.2-2

Git Clone URL: https://aur.archlinux.org/kalu-kde.git (read-only, click to copy)
Package Base: kalu-kde
Description: Upgrade notifier w/ AUR support, watched (AUR) packages, news; supports autohide in KDE Plasma's panel
Upstream URL: https://github.com/Thulinma/kalu
Licenses: GPL3+
Conflicts: kalu
Provides: kalu
Submitter: Rhinoceros
Maintainer: Rhinoceros (Thulinma, jghodd)
Last Packager: Rhinoceros
Votes: 14
Popularity: 0.000004
First Submitted: 2014-12-30 12:30 (UTC)
Last Updated: 2024-09-14 14:24 (UTC)

Latest Comments

1 2 3 4 5 6 .. 14 Next › Last »

BluePyTheDeer251 commented on 2024-10-05 16:32 (UTC) (edited on 2024-10-05 16:43 (UTC) by BluePyTheDeer251)

Sorry to ask, but what does MIA mean? (idk most terminology here)

nvm it apparently means "missing in action"

Rhinoceros commented on 2024-10-05 06:01 (UTC)

Thanks @Aerion. FWIW I've submitted an orphan request for statusnotifier since jjacky is MIA. I have no plans for long-term maintenance, but I can at least apply the fix from the comments.

BluePyTheDeer251 commented on 2024-10-01 17:19 (UTC) (edited on 2024-10-05 16:52 (UTC) by BluePyTheDeer251)

Thanks, will use once I get home

Edit: Used it like 2 days ago (the "proper" way), and it just works™.

Aerion commented on 2024-10-01 15:44 (UTC) (edited on 2024-10-01 15:45 (UTC) by Aerion)

@BluePyTheDeer251 The solution is mentioned in the comments for statusnotifier. It can be solved as follows:

The 'quick and dirty' way:

sudo pacman -S --asdeps gobject-introspection

Then install statusnotifier as normal.

The 'proper' way:

  • manually install statusnotifier, i.e. using git clone instead of via an AUR helper
  • edit the PKGBUILD and add the following line after the 'depends=' line

makedepends=('gobject-introspection')

  • save the PKGBUILD
  • makepkg -si --asdeps
  • install kalu-kde as normal

BluePyTheDeer251 commented on 2024-09-22 23:01 (UTC)

Tried to install, couldn't because of statusnotifier failing to build.

Rhinoceros commented on 2024-09-14 14:25 (UTC)

I just bumped the pkgrel, since this package will need to be rebuilt for pacman 7. Just uninstall kalu-kde, do the pacman update, then reinstall kalu-kde. Everything seems to work fine for me with pacman 7.

Thulinma commented on 2024-04-01 22:11 (UTC)

There was a second occurrance of the same bug I fixed the other day... which I fixed earlier today. There should be no more crashes at all with 4.5.2! Please let me know if anyone still experiences any 😭

jghodd commented on 2024-04-01 21:37 (UTC)

@Rhinoceros - i get what you're saying. i'll take another look at the syntax and see if i can use sed to strip out the optimization and source-fortification.

Rhinoceros commented on 2024-03-31 23:33 (UTC)

Thanks @jghodd that looks good. I had another thought, and I'm not sure if my original idea was a bit faulty.

What if users had their CFLAGS as -O3, say? It's probably more robust to explicitly append -O0 instead of assuming users have -O2.

I couldn't find much documentation on -Wp,-D_FORTIFY_SOURCE=2 though, so I'm not sure what the default replacement is.

jghodd commented on 2024-03-31 17:46 (UTC)

@Rhinoceros - I don't disagree with your point about hard-coding CFLAGS. it could bite you later on down the line.

How about this:


build() {
  export CFLAGS="${CFLAGS/" -O2"/""}"
  export CFLAGS="${CFLAGS/" -Wp,-D_FORTIFY_SOURCE=2"/""}"

  cd "${_pkgname}-${pkgver}"
  ./autogen.sh
  ./configure --prefix=/usr --enable-status-notifier
  make
}

This works, btw.

1 2 3 4 5 6 .. 14 Next › Last »