Package Details: logger-pro-beta 1:

Git Clone URL: (read-only)
Package Base: logger-pro-beta
Description: Logger Pro for Linux Public Beta from Vernier Software
Upstream URL:
Licenses: unknown
Conflicts: logger-pro
Provides: logger-pro
Submitter: agias
Maintainer: tchebb
Last Packager: tchebb
Votes: 0
Popularity: 0.000000
First Submitted: 2011-11-20 21:21
Last Updated: 2016-02-01 12:40

Latest Comments

Morganamilo commented on 2018-06-08 02:55

This package is overriding the pkgver variable in each split package. It should not be doing this.

aouellette commented on 2016-09-07 00:13

I'm getting the same error as everyone else here. It looks like this might be something that is not fixable, see

baduhai commented on 2016-05-15 15:56

Came here to post that I have a problem, and it seems as though I'm not the first to encounter it. Unfortunately I have no Idea what to do about it. Here's what comes up when I run loggerpro or loggerpro_real:

main is linked to NGIO library version 01.96 .
main is linked to GoIO library version 02.53 .
loggerpro_real: symbol lookup error: loggerpro_real: undefined symbol: _ZN4Glib23spawn_command_line_syncERKSsPSsS2_Pi

Anonymous comment on 2016-02-27 17:10

From my searching around it appears that glibmm has changed. Seems that


is now


Unfortunately, I have no idea how to patch binaries (a simple replacement caused a seg-fault). Maybe this helps?

tchebb commented on 2016-02-01 20:05

It looks like something in glibmm or gcc changed, which resulted in spawn_command_line_sync() having a different mangled name. Since LoggerPro is only distributed in binary form, solving this would require either installing an old version of glibmm (if that's what changed) or somehow patching the binary to link to the new symbol name.

I'll try to spend a bit of time figuring out the second option, but if it doesn't work out, I'm just going to orphan this package and let someone else pick it up; I don't use the software anymore personally.

1001sd commented on 2016-02-01 18:46

I also get that error. Running "c++filt _ZN4Glib23spawn_command_line_syncERKSsPSsS2_Pi" gives "
Glib::spawn_command_line_sync(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> >*, std::basic_string<char, std::char_traits<char>, std::allocator<char> >*, int*)", which I don't know what means, but maybe someone does :P

MasterMax commented on 2016-02-01 09:22

getting the same error as @cabellicar123
any solution?

Anonymous comment on 2016-01-11 18:40

Getting an error:

$ loggerpro
main is linked to NGIO library version 01.96 .
main is linked to GoIO library version 02.53 .
/usr/bin/loggerpro_real: symbol lookup error: /usr/bin/loggerpro_real: undefined symbol: _ZN4Glib23spawn_command_line_syncERKSsPSsS2_Pi

tchebb commented on 2015-08-12 15:57

@helasraizam Should be fixed now.

As an aside, cower seems to have a bug that causes it to try to install the wrong files automatically, so if you use cower, you'll need to manually run pacman -U to install the built packages.

helasraizam commented on 2015-08-12 10:24

Hi tchebb, the same error of wanting to upgrade 1: -> 1:3846-1 has come up again.

rargh commented on 2014-11-07 08:00

@tchebb yeah, it's fixed, thanks!

tchebb commented on 2014-11-07 01:18

@rargh Is it better now? It looks like mkaurball doesn't properly detect the versions of split packages, so I just manually added the right fields to .AURINFO and re-uploaded.

rargh commented on 2014-11-06 09:36

The package keeps wanting to update to version 1:3846-1 from 1:, even after applying said update. I'm assuming these are equivalent, and possibly an easy fix on your end?

tchebb commented on 2014-10-27 03:20

Glad to help! I don't believe you need to do anything else. (I guess I was a bit hasty in my request for orphaning, though. Sorry for the somewhat-hostile takeover.)

agias commented on 2014-10-27 01:51

Looks like you've successfully taken ownership of this. Is there anything else I need to do?

Thanks for taking over, I no longer have use for this software and had basically forgotten about this package.

tchebb commented on 2014-10-21 08:46

Since it looks like you're not maintaining this package anymore, would you mind orphaning it? I've updated the PKGBUILD to the latest version and made a number of other changes including turning it into a split package (so the drivers and software are packaged separately), updating the dependency list, and adding a .install file to rebuild icon and MIME type cachesafter installtion.

I'd prefer to upload it as an update to this package rather than create a new package and cause confusion. I'm also happy to send the PKGBUILD to you if you want to continue to maintain this package.

Anonymous comment on 2012-09-12 19:41

but it's not really an issue after all

Anonymous comment on 2012-09-12 19:40

it just took a really long time to get passed that step, like 15+ minutes, which lead me to believe it had stopped working

agias commented on 2012-09-12 05:23

Did you fix the issue where it hung during the strip? I'm updating the PKGBUILD to include options=(!strip). I got the email from your comment, which I guess you deleted?

As for the library issue, as far as I'm aware the only two ways to fix it are to go into the program's source code (impossible, given they only release the binary) or to make a symbolic link as described here.

Unfortunately, even this doesn't work for me for some reason. For this reason, combined with the fact that it seems to be considered bad practices, I will not put the symlink in my PKGBUILD and I will flag it out-of-date.

Anonymous comment on 2012-09-12 04:13

i get this error when trying to run loggerpro on x86_64:

loggerpro: error while loading shared libraries: cannot open shared object file: No such file or directory

agias commented on 2011-11-20 21:21