%PDF- <> %âãÏÓ endobj 2 0 obj <> endobj 3 0 obj <>/ExtGState<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/Annots[ 28 0 R 29 0 R] /MediaBox[ 0 0 595.5 842.25] /Contents 4 0 R/Group<>/Tabs/S>> endobj ºaâÚÎΞ-ÌE1ÍØÄ÷{òò2ÿ ÛÖ^ÔÀá TÎ{¦?§®¥kuµùÕ5sLOšuY>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<> endobj 2 0 obj<>endobj 2 0 obj<>es 3 0 R>> endobj 2 0 obj<> ox[ 0.000000 0.000000 609.600000 935.600000]/Fi endobj 3 0 obj<> endobj 7 1 obj<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI]>>/Subtype/Form>> stream
#!/bin/sh REPORTBUG_VERSION=$(dpkg-query -f '${source:Version}' -W reportbug) # Depending on whether reportbug is new enough, we either write the output of # our various commands to a file and attach them to the report (this needs # reportbug ≥ 6.5.0) or just write them to the body of the bug report. if dpkg --compare-versions "$REPORTBUG_VERSION" ge "6.5.0"; then # We don’t clean up this directory because there is no way to know when # reportbug finished running, and reportbug needs the files around. # Given that those are just a couple of kilobytes in size and people # generally don’t file a lot of bugs, I don’t think it’s a big deal. DIR=$(mktemp -d) echo "-- BEGIN ATTACHMENTS --" >&3 udevadm info --export-db >$DIR/udev-database.txt echo "$DIR/udev-database.txt" >&3 echo "-- END ATTACHMENTS --" >&3 else _header() { echo "--------------" >&3 echo "$1:" >&3 echo "--------------" >&3 } _header "udev database" udevadm info --export-db >&3 fi