Comment 11 for bug 1025381

This device's information in the submission.xml file seems to be confusing c3:

P: /devices/pci0000:00/0000:00:1a.7/usb1/1-1
  N: bus/usb/001/002
  E: BUSNUM=001
  E: DEVNAME=/dev/bus/usb/001/002
  E: DEVNUM=002
  E: DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb1/1-1
  E: DEVTYPE=usb_device
  E: DRIVER=usb
  E: ID_BUS=usb
  E: ID_MODEL=USB_Flash_Drive
  E: ID_MODEL_ENC=USB\x20Flash\x20Drive
  E: ID_MODEL_ID=1167
  E: ID_REVISION=0100
  E: ID_SERIAL=USB_2.0_USB_Flash_Drive_000000005538679C
  E: ID_SERIAL_SHORT=000000005538679C
  E: ID_USB_INTERFACES=:080650:
  E: ID_VENDOR=USB_2.0
  E: ID_VENDOR_ENC=USB\x202.0
  E: ID_VENDOR_ID=048d
  E: MAJOR=189
  E: MINOR=1
  E: PRODUCT=48d/1167/100
  E: SUBSYSTEM=usb
  E: TYPE=0/0/0
  E: UDEV_LOG=3
  E: USEC_INITIALIZED=203699593

Particularly, the ID_VENDOR_ENC value is what's making c3 choke. If this is changed to USB\\x202.0 (note the double backslash from USB\x202.0), the submission goes through.

This is just an observation though, the actual fix will involve ensuring data is correctly-formatted when passing it to Postgres, which is the one saying this:

DataError: invalid input syntax for type bytea

this would be much easier to figure out if I could see the entire query as sent to the DBMS. Still, I'll go and read up on postgres bytea syntax, see what I can learn.