Arch Linux

AndyRTR

Developer

From: Magdeburg/Germany

Registered: 2005-10-07

Posts: 1,641

[PKGBUILD] GBrowser 0.4.0

http://gbrowser.sourceforge.net/index.php?page=home

# Contributor: AndyRTR <andreas.radke@freenet.de>
pkgname=gbrowser
pkgver=0.4.0
pkgrel=1
pkgdesc="GBrowser is a lightweight file browser, image viewer and terminal emulator written in C++ using GTK"
url="http://gbrowser.sourceforge.net/index.php"
license=""
depends=(libglade vte curl libexif fam)
makedepends=(scons)
conflicts=()
replaces=()
backup=()
install=
source=(http://dl.sourceforge.net/gbrowser/$pkgname-$pkgver.tar.gz)
md5sums=('2542c8b7077de1eb7a99f7e0c3150d65')

build() {
  cd $startdir/src/$pkgname-$pkgver
  scons prefix=$startdir/pkg/opt/gnome/
  scons prefix=$startdir/pkg/opt/gnome/ install  || return 1
  find $startdir/pkg/opt/gnome/bin -name .sconsign  -exec rm {} ; 
  find $startdir/pkg/opt/gnome/share/gbrowser -name .sconsign  -exec rm {} ; 
}

makepkg and install it. Here it soon crashes with some gtk errors:

(gbrowser:23318): Gtk-CRITICAL **: gtk_tree_store_iter_next: assertion `iter->user_data != NULL' failed

(gbrowser:23318): Gtk-CRITICAL **: gtk_tree_store_get_path: assertion `iter->user_data != NULL' failed

(gbrowser:23318): Gtk-CRITICAL **: gtk_tree_view_expand_to_path: assertion `path != NULL' failed

(gbrowser:23318): Gtk-CRITICAL **: gtk_tree_selection_select_path: assertion `path != NULL' failed

(gbrowser:23318): Gtk-CRITICAL **: gtk_tree_store_iter_next: assertion `iter->user_data != NULL' failed

(gbrowser:23318): Gtk-CRITICAL **: gtk_tree_store_get_path: assertion `iter->user_data != NULL' failed

(gbrowser:23318): Gtk-CRITICAL **: gtk_tree_view_expand_to_path: assertion `path != NULL' failed

(gbrowser:23318): Gtk-CRITICAL **: gtk_tree_selection_select_path: assertion `path != NULL' failed

Is this an upstream error?

Snowman

Developer/Forum Fellow

From: Montreal, Canada

Registered: 2004-08-20

Posts: 5,212

Re: [PKGBUILD] GBrowser 0.4.0

Is this an upstream error?

Looks so. Check their home page. Maybe there's already  a bug report for it or more info.