Package Details: logger-pro-drivers-beta 1:1.5.1.1-2

Git Clone URL: https://aur.archlinux.org/logger-pro-beta.git (read-only)
Package Base: logger-pro-beta
Description: Logger Pro for Linux Public Beta from Vernier Software (drivers)
Upstream URL: http://www.vernier.com/downloads/logger-pro-linux/
Licenses: unknown
Conflicts: logger-pro-drivers
Provides: logger-pro-drivers
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

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 http://www.vernier.com/til/3628/.

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

_ZN4Glib23spawn_command_line_syncERKSsPSsS2_Pi

is now

_ZN4Glib23spawn_command_line_syncERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPS5_S8_Pi

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:3.8.4.6-1 -> 1:3846-1 has come up again.

rargh commented on 2014-11-07 08:00

@tchebb yeah, it's fixed, thanks!

All comments