Description of problem: system-config-printer hangs after new clicked Version-Release number of selected component (if applicable): system-config-printer-0.6.116-1 How reproducible: Always Steps to Reproduce: 1. click new 2. 3. Actual results: Expected results: Additional info:
[root@localhost util]# system-config-printer-gui *** glibc detected *** malloc(): memory corruption: 0x08064fa0 *** sh: line 1: 27741 Aborted perl -e 'ioctl(STDIN,0x84005001,$result);print $result' 2>/dev/null </dev/usb/lp0 Traceback (most recent call last): File "/usr/share/printconf/util/queueTree.py", line 580, in new_button_clicked self.addQueue.addQueueDruid () File "/usr/share/printconf/util/addQueue.py", line 248, in addQueueDruid self.populate_device_view () File "/usr/share/printconf/util/addQueue.py", line 468, in populate_device_view self.local_devs = self.parent.conf.scan_local_printer_devices (force) File "/usr/share/printconf/util/printconf_conf.py", line 1265, in scan_local_printer_devices local_printer_devices.device_dict[dev].update(autodetect_usb_printer(dev, i)) File "/usr/share/printconf/util/printconf_conf.py", line 1392, in autodetect_usb_printer return { "auto" : auto } UnboundLocalError: local variable 'auto' referenced before assignment
Here is a similar report from fedora-list: https://www.redhat.com/archives/fedora-list/2004-December/msg05889.html Could you please try running this as root?: perl -e 'ioctl(STDIN,0x84005001,$result);print $result' </dev/usb/lp0 Does that do the same thing?
[root@localhost ~]# perl -e 'ioctl(STDIN,0x84005001,$result);print $result' </dev/usb/lp0 *** glibc detected *** malloc(): memory corruption: 0x08064f78 *** Aborted Apparently so.
This is going wrong in the perl program then. Chip, any idea what's up?
I just noticed that when I run this program at home it does not hang. I have a notebook that i use in a docking station at work, where the program hangs. The docking station has a usb parallel printer port emulator. Perhaps something is going on with that that is causing the problem? Is there a workaround.. I don't care about using the parallel port?
*** Bug 153929 has been marked as a duplicate of this bug. ***
*** Bug 155007 has been marked as a duplicate of this bug. ***
Is this the same issue as Bug #144536?
Yes, and that bug has a stack trace. *** This bug has been marked as a duplicate of 144536 ***