[Bug 1297326] Re: gutenprint52+usb crashed with SIGSEGV in __GI___pthread_mutex_lock()

2014-03-27 Thread Solomon Peachy
There is an upstream fix for the crash; it will be in the next gutenprint release. Alternatively you can get the patch here if you don't want to wait for upstream to spit out a new release: http://gimp-print.cvs.sourceforge.net/viewvc/gimp- print/print/src/cups/backend_common.c?r1=1.31&r2=1.32&v

[Bug 1297326] Re: gutenprint52+usb crashed with SIGSEGV in __GI___pthread_mutex_lock()

2014-03-25 Thread Solomon Peachy
At first glance it appears that the crash is in the bowels of libusb's enumeration code and has nothing to do with the backend itself. Please log into the non-graphical console, and run three things for me on the command line: lsusb /usr/lib/cups/backend/usb /usr/lib/cups/backend/gutenprint52+usb

[Bug 1297326] Re: gutenprint52+usb crashed with SIGSEGV in __GI___pthread_mutex_lock()

2014-03-25 Thread Solomon Peachy
In particular, I suspect that VMWare's "Printer feaure" is responsible, but I have no idea how it's exposed within the VM. The gutenprint backend uses similar enumeration logic as the CUPS USB backend, so I'm particularly interested if the latter works when the former does not. -- You received

[Bug 1297326] Re: gutenprint52+usb crashed with SIGSEGV in __GI___pthread_mutex_lock()

2014-03-26 Thread Solomon Peachy
Can you run those commands as root? The fact that 'lsusb' is failing shows taht something more serious than a failing backend is going wrong. Please uninstall the VMWare tools too, at least as an experiment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1297326] Re: gutenprint52+usb crashed with SIGSEGV in __GI___pthread_mutex_lock()

2014-03-26 Thread Solomon Peachy
The gutenprint backend crash is due to not catching the failure of libusb_init(). Why libusb_init is failing is another matter entirely... Oh, one more thing; can you run 'ls -l /usr/lib/cups/backend/' for me? -- You received this bug notification because you are a member of Ubuntu Bugs, which