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#20287 - [xchat] Timer handler should only return 1 value. Print handler should only return 1 value.

Attached to Project: Arch Linux
Opened by punk (punkmexicano) - Tuesday, 27 July 2010, 07:03 GMT
Last edited by Ionut Biru (wonder) - Friday, 13 August 2010, 19:17 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Kevin Piche (kpiche)
Eric Belanger (Snowman)
Francois Charette (Firmicus)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
I get these errors
Timer handler should only return 1 value. Print handler should only return 1 value.
when i use 2 scripts (eventtoservertab-001.pl and textualdynambot-009.pl)in Xchat in arch linux, in the #xchat channel they say its a problem with perl in archlinux and that error doesnt appear in other linux distros




Steps to reproduce:
open xchat
start chatting with the plugins (scripts) loaded
and then appears the timer handler and print handler errors
This task depends upon

Closed by  Ionut Biru (wonder)
Friday, 13 August 2010, 19:17 GMT
Reason for closing:  Fixed
Additional comments about closing:  xchat 2.8.8-2
Comment by Gerardo Exequiel Pozzi (djgera) - Tuesday, 03 August 2010, 22:26 GMT
how works with newer perl-5.12.1-2? any sample testcase?

Next time please write package versions. Thanks.
Comment by punk (punkmexicano) - Wednesday, 04 August 2010, 01:25 GMT
i havent test it with newer perl 5.12.1-2.
right now i dont have arch installed on my laptop.....the perl scripts i used on xchat were dynambot and server tab scripts both made by lifeispain the package versions were the last ones...
Comment by Dirk (dsohler) - Wednesday, 04 August 2010, 22:27 GMT
I can confirm this bug with XChat script “improved nick completer 0.2”. I already contacted script author. He guesses that the error is in Perl or XChat, not in the script. This matched the bug’s description here and the position of #xchat.

XChat version: 2.8.8
Perl version: 5.12.1
improved nick completer version: 0.2 (2007/08/31)
Comment by Raphaël Bois (vdust) - Friday, 06 August 2010, 12:39 GMT
Hi. I also confirm this bug and managed to create a 3-lines test script that reproduces the "Print handler should only return 1 value" whenever you write a message:

%
Xchat::register("Test", "0.1", "Test");
Xchat::hook_print("Your Message", \&theTest);
sub theTest { return EAT_NONE; }
%

My guess is that the problem is either located in the perl bindings or perl 5.12.1 itself.

I tested with the following packages:
xchat 2.8.8-1
perl 5.12.1-2
Comment by Eric Belanger (Snowman) - Friday, 06 August 2010, 17:28 GMT
Try rebuilding xchat to see if it fix the problem.
Comment by Geoff (perseus) - Saturday, 07 August 2010, 08:26 GMT
This hit me last night on my first restart of Xchat for some time (Xchat 2.8.8 / Perl 5.12.1). lifeispain on the Xchat forum pointed me to this bug. Self-compiling Xchat using the defaults (apart from installation directory), cures it.
Comment by Dirk (dsohler) - Friday, 13 August 2010, 13:43 GMT
So the maintainer should simply rebuild it and push it to the repo?

Loading...