Opened 12 years ago

Closed 8 years ago

#9278 closed bug (fixed)

print_addon_server crashes with LPR ports using hostnames

Reported by: jessicah Owned by: phoudoin
Priority: normal Milestone: R1
Component: Printing Version: R1/alpha4.1
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

When I submit a print job using a printer configured using LPR as the transport, if I use a hostname, print_addon_server crashes after the job has been printed/submitted 100% of the time. Does not occur when using an IP address.

Note that the print job does successfully print. This appears to be a problem in tearing down the add-on.

Backtrace:

[Current thread is 1 (team /boot/system/servers/print_addon_server (1523) thread print_addon_server (1523))]
#0  0x01cf4bdc in ?? ()
#1  0x002405e5 in __pthread_key_call_destructors () from /boot/system/lib/libroot.so
#2  0x0023f851 in __pthread_destroy_thread () from /boot/system/lib/libroot.so
#3  0x0023175c in _thread_do_exit_work () from /boot/system/lib/libroot.so
#4  0x00295330 in exit () from /boot/system/lib/libroot.so
#5  0x002030a8 in _start ()
#6  0x00106246 in runtime_loader () from /boot/system/runtime_loader
#7  0x7ffeefec in ?? ()

Change History (3)

comment:1 by vidrep, 8 years ago

I have tried to reproduce this issue using hrev50332 x86_gcc2 on a Epson XP-820 printer. The printer completed the print jobs without crashing. Can we assume this issue has been fixed? Jessicah, are you still able to reproduce the crash?

comment:2 by vidrep, 8 years ago

I have been sending print jobs to my Epson printers using hostname for the past 4 months without a single crash. This ticket is probably safe to close.

comment:3 by diver, 8 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.