Menu
▾
▴
[TiLP-devel] [ tilp-Bugs-1575630 ] Using link causes errors from libraries
|
From: SourceForge.net <no...@so...> - 2008-02-29 17:00:46
|
Bugs item #1575630, was opened at 2006-10-12 02:49 Message generated for change (Settings changed) made by roms You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=118378&aid=1575630&group_id=18378 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Out of Date Priority: 5 Private: No Submitted By: Donald Straney (burntfuse) Assigned to: Romain Liévin (roms) Summary: Using link causes errors from libraries Initial Comment: When I set the device options in TiLP 2 (cable is a Blacklink on port #1, calc is an 83+) and pressed OK, I got two error messages, first "Msg: attempting to use a cable which has not been open before. Cause: Internal error.", then "Msg: illegal operation or argument. Cause: the program which uses this library is buggy. Fire-up the developer!" This happened whether I had the calculator connected or not, and trying the automatic scan in the device options didn't turn up anything. After that, whenever I tried to get a directory listing or send a file, two similar error messages appeared. For the record, TiLP worked fine on the same system. I was running TiLP 2 as root in Linux (Slackware, with a 2.4.29 kernel), with tilibs2 1.0, and this is the output: TiLP - Version 1.00, (C) 1999-2006 Romain Lievin THIS PROGRAM COMES WITH ABSOLUTELY NO WARRANTY PLEASE READ THE DOCUMENTATION FOR DETAILS built on Oct 10 2006 16:35:37 Unable to read file: Key file does not start with a group tilp-INFO: setlocale: <LC_CTYPE=en_US;LC_NUMERIC=en_US;LC_TIME=en_US;LC_COLL C;LC_MONETARY=en_US;LC_MESSAGES=en_US;LC_PAPER=en_US;LC_NAME=en_US;LC_ADDRES _US;LC_TELEPHONE=en_US;LC_MEASUREMENT=en_US;LC_IDENTIFICATION=en_US> tilp-INFO: bindtextdomain: <\locale> tilp-INFO: textdomain: <tilp2> ticables-INFO: ticables library version 1.0.0 ticables-INFO: setlocale: <LC_CTYPE=en_US;LC_NUMERIC=en_US;LC_TIME=en_US;LC_ ATE=C;LC_MONETARY=en_US;LC_MESSAGES=en_US;LC_PAPER=en_US;LC_NAME=en_US;LC_AD S=en_US;LC_TELEPHONE=en_US;LC_MEASUREMENT=en_US;LC_IDENTIFICATION=en_US> ticables-INFO: bindtextdomain: </usr/local/share/locale> ticables-INFO: textdomain: <libticables2> ticables-INFO: kernel: 2.4.29 tifiles-INFO: tifiles library version 1.0.0 tifiles-INFO: setlocale: <LC_CTYPE=en_US;LC_NUMERIC=en_US;LC_TIME=en_US;LC_C TE=C;LC_MONETARY=en_US;LC_MESSAGES=en_US;LC_PAPER=en_US;LC_NAME=en_US;LC_ADD =en_US;LC_TELEPHONE=en_US;LC_MEASUREMENT=en_US;LC_IDENTIFICATION=en_US> tifiles-INFO: bindtextdomain: </usr/local/share/locale> tifiles-INFO: textdomain: <libtifiles2> ticalcs-INFO: ticalcs library version 1.0.0 ticalcs-INFO: setlocale: <LC_CTYPE=en_US;LC_NUMERIC=en_US;LC_TIME=en_US;LC_C TE=C;LC_MONETARY=en_US;LC_MESSAGES=en_US;LC_PAPER=en_US;LC_NAME=en_US;LC_ADD =en_US;LC_TELEPHONE=en_US;LC_MEASUREMENT=en_US;LC_IDENTIFICATION=en_US> ticalcs-INFO: bindtextdomain: </usr/local/share/locale> ticalcs-INFO: textdomain: <libticalcs2> ticables-INFO: Check for lib-usb support: ticables-INFO: usb support: available. ticables-INFO: Check for lib-usb usability: ticables-INFO: usb filesystem (/proc|dev/bus/usb): not mounted ticables-INFO: => the usbfs must be supported by your kernel and you hav mount it ticables-INFO: => add a 'none /proc/bus/usb usbfs defaults 0 0' in your c/fstab'. ticables-INFO: => This line is enough for 'root' user. If you want to us as a single user, ticables-INFO: => take a look at the ticables2/README file. ticables-INFO: Check for tty usability: ticables-INFO: node /dev/ttyS0: exists ticables-INFO: permissions/user/group: -rwxrwxrw- root uucp ticables-INFO: is user can r/w on device: yes ticables-INFO: is useable: no tilp-INFO: tilp_device_err catched error 51 ticables-INFO: Check for tty usability: ticables-INFO: node /dev/ttyS0: exists ticables-INFO: permissions/user/group: -rwxrwxrw- root uucp ticables-INFO: is user can r/w on device: yes ticables-INFO: is useable: no tilp-INFO: tilp_device_err catched error 51 tilp-INFO: tilp_device_err catched error 51 tilp-INFO: tilp_device_err catched error 51 tilp-INFO: tilp_device_err catched error 51 ---------------------------------------------------------------------- Comment By: Romain Liévin (roms) Date: 2006-11-12 13:31 Message: Logged In: YES user_id=136160 Could you send to me a mail at roms_at_tilp_dot_info so that I can send to you a debug ticables2 library. Your problem is somewhat strange and I want to debug it... ---------------------------------------------------------------------- Comment By: Donald Straney (burntfuse) Date: 2006-11-11 16:32 Message: Logged In: YES user_id=1451589 I've got a Pentium III with an Intel 82801AA chipset, so I guess that's what handles the serial port. From my kernel's config: CONFIG_SERIAL=y CONFIG_SERIAL_CONSOLE=y CONFIG_SERIAL_EXTENDED=y CONFIG_SERIAL_MANY_PORTS=y CONFIG_SERIAL_SHARE_IRQ=y # CONFIG_SERIAL_DETECT_IRQ is not set CONFIG_SERIAL_MULTIPORT=y CONFIG_HUB6=y CONFIG_SERIAL_NONSTANDARD=y So the serial port support should be built in and working. It still could be a problem with my kernel though. In case it matters, I've got glibc 2.3.4. ---------------------------------------------------------------------- Comment By: Romain Liévin (roms) Date: 2006-11-11 11:00 Message: Logged In: YES user_id=136160 Which is your hardware? I never got this problem... Maybe your kernel is mis-configured? ---------------------------------------------------------------------- Comment By: Romain Liévin (roms) Date: 2006-11-11 10:58 Message: Logged In: YES user_id=136160 << ticables-INFO: Check for tty usability: ticables-INFO: node /dev/ttyS0: exists ticables-INFO: permissions/user/group: -rwxrwxrw- root uucp ticables-INFO: is user can r/w on device: yes ticables-INFO: is useable: no >> There is a problem with your serial device (not usable). Check for permission and hardware set-up correctly... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=118378&aid=1575630&group_id=18378 |
