Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#12633 - [alltray] 0.70-1.1 x86_64 does not work

Attached to Project: Arch Linux
Opened by defrysk (defrysk) - Thursday, 01 January 2009, 14:22 GMT
Last edited by Eric Belanger (Snowman) - Saturday, 03 October 2009, 19:59 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Douglas Soares de Andrade (dsa)
Architecture x86_64
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: alltray 0.70-1.1 x86_64 does not work and bails out


Additional info:
* package version(s) alltray 0.70-1.1 x86_64
* config and/or log files etc.


Steps to reproduce: run it in xterm

alltray bails out with :
Gtk-Message: Failed to load module "pk-gtk-module": libpk-gtk-module.so: cannot open shared object file: No such file or directory

Alltray: To use Alltray under Gnome, Gconf support should not be disabled.
But it is.

I changed the PKGBUILD (see attachement) to fix it.

   PKGBUILD (0.6 KiB)
This task depends upon

Closed by  Eric Belanger (Snowman)
Saturday, 03 October 2009, 19:59 GMT
Reason for closing:  Fixed
Additional comments about closing:  alltray-0.70-1.2
Comment by Greg (dolby) - Thursday, 01 January 2009, 19:08 GMT
If disabling gconf isnt needed for x86_64 anymore, you can skip the Arch64 fix part. Simply like this:

cd $startdir/src/$pkgname-$pkgver

./configure --prefix=/usr
make || return 1
make DESTDIR=$startdir/pkg install
}
Comment by Petar Aleksich (Pobro) - Monday, 27 July 2009, 23:20 GMT
7 months and no patch for package in EXTRA? Would be funny if it was not so sad...
   PKGBUILD.patch (0.4 KiB)
Comment by Roman Kyrylych (Romashka) - Tuesday, 28 July 2009, 07:41 GMT
You don't seem to realize that we have limited "human resources".
The maintainer of the package was mostly inactive for a long time,
and the new maintainer took the package only recently.
Comment by Petar Aleksich (Pobro) - Tuesday, 28 July 2009, 14:19 GMT
Whatever the reason 7 months is unacceptable.
I don't mind taking care of it if you move it to AUR instead of leaving it sitting in EXTRA almost 7 months without maintainer.

Loading...