fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (2024)

VocĆŖ pode obter um log do daemon --verbose fwupd quando estiver tentando fazer a atualizaĆ§Ć£o? NĆ£o consigo ver por que o dispositivo falhava ao abrir apĆ³s a mensagem de depuraĆ§Ć£o doing detach in idle . Obrigado.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (1) hughsie em 10 jul. 2017

Aqui estĆ” o registro detalhado do daemon:

Jul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0250 Fu Called Install(/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3,8)Jul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0250 Fu got option reasonJul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0250 Fu got option filenameJul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0250 Fu Emitting PropertyChanged('Status'='decompressing')Jul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0251 As found file 0 RQR24.05_B0029.hexJul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0251 As found file 1 com.logitech.Unifying.RQR24.metainfo.xmlJul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0252 As found file 2 RQR24.05_B0029.hex.ascJul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0252 Fu Using keyring at /var/lib/fwupd/gnupgJul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0255 Fu Adding public key /etc/pki/fwupd/GPG-KEY-Linux-Vendor-Firmware-ServiceJul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0258 Fu importing key 3FC6B804410ED0840D8F2F9748A6D80E4538BAC2 [0] SuccessJul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0258 Fu Adding public key /etc/pki/fwupd/GPG-KEY-Hughski-LimitedJul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0262 Fu importing key 7E5439F64986F7A9E973809BAD8A528FEC44881E [0] SuccessJul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0266 Fu returned signature fingerprint 3FC6B804410ED0840D8F2F9748A6D80E4538BAC2Jul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0266 Fu marking payload as trustedJul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0269 Fu requirement 0.8.2 ge 0.9.5 on org.freedesktop.fwupd passedJul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0269 Fu no requirement on firmware{(null)}Jul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0269 Fu requirement BOT03.0[0-1]_* regex BOT03.00_B0006 on bootloader passedJul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0269 Fu no requirement on firmware{vendor-id}Jul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0269 Fu performing update_prepare() on upowerJul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0269 Fu FuPending: trying to open database '/var/lib/fwupd/pending.db'Jul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0270 Fu FuPending: get resJul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0270 Unifying doing detach in idleJul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0270 Unifying detachingJul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0270 Unifying detaching deviceJul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0270 Unifying [HID] host->device:10 ff 80 f0 49 43 50Jul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0276 Unifying device /sys/devices/pci0000:00/0000:00:14.0/usb1/1-3 removedJul 10 07:39:00 zacapa fwupd[11447]: 13:39:00:0359 Fu emit removed from usb: usb:00:03Jul 10 07:39:02 zacapa fwupd[11447]: 13:39:02:0260 Unifying USB add usb:00:03Jul 10 07:39:02 zacapa fwupd[11447]: 13:39:02:0262 Unifying device /sys/devices/pci0000:00/0000:00:14.0/usb1/1-3 addedJul 10 07:39:02 zacapa fwupd[11447]: 13:39:02:0262 Unifying waiting for device to settle...Jul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0263 Unifying opening unifying device using USBJul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0263 Unifying claiming interface 0x00Jul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0264 Unifying host->device: 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Jul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0264 Unifying UDEV add /dev/hidraw1 = /sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:046D:AAAC.000C/hidraw/hidraw1Jul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0265 Unifying no HID_ID, skippingJul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0267 Unifying device->host: 80 00 00 06 04 00 6b ff 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Jul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0267 Unifying host->device: 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Jul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0268 Unifying device->host: 90 00 00 0e 42 4f 54 30 33 2e 30 30 5f 42 30 30 30 36 00 00 00 00 00 00 00 00 00 00 00 00 00 00Jul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0268 Unifying type: bootloader-texasJul 10 07:39:03 zacapa fwupd[11447]: flags: can-flash,active,is-open,requires-attachJul 10 07:39:03 zacapa fwupd[11447]: hidpp-version: 0.00Jul 10 07:39:03 zacapa fwupd[11447]: hidpp-id: 0xffJul 10 07:39:03 zacapa fwupd[11447]: usb-device: 0x15d1f40Jul 10 07:39:03 zacapa fwupd[11447]: platform-id: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-3Jul 10 07:39:03 zacapa fwupd[11447]: vendor: LogitechJul 10 07:39:03 zacapa fwupd[11447]: product: Unifying [bootloader-texas]Jul 10 07:39:03 zacapa fwupd[11447]: version-bootloader: BOT03.00_B0006Jul 10 07:39:03 zacapa fwupd[11447]: version-firmware: RQR24.xx_BxxxxJul 10 07:39:03 zacapa fwupd[11447]: guid: USB\VID_046D&PID_AAACJul 10 07:39:03 zacapa fwupd[11447]: flash-addr-high: 0x6bffJul 10 07:39:03 zacapa fwupd[11447]: flash-addr-low: 0x0400Jul 10 07:39:03 zacapa fwupd[11447]: flash-block-size: 0x0080Jul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0268 Unifying /sys/devices/pci0000:00/0000:00:14.0/usb1/1-3 is in replug, quitting loopJul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0268 Dfu device was not DFU capableJul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0268 As run FuPluginUsb:added{046d:aaac}Jul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0268 As run FuPluginUsb:get-string-descJul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0269 Fu using cc4cbfa9-bf9d-540b-b92b-172ce31013c1 for USB\VID_046D&PID_AAACJul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0269 Fu using 47292924-dfa1-58b1-bb45-c3b00c9c441c for USB\VID_046D&PID_AAAC&REV_0300Jul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0269 Fu waiting a small time for other pluginsJul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0269 As run FuPluginEbitdo:added{046d:aaac}Jul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0269 As run FuPluginAltos:added{046d:aaac}Jul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0269 Fu Emitting PropertyChanged('Status'='device-write')Jul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0271 Unifying host->device: d0 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Jul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0770 Fu emit added from usb: usb:00:03Jul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0770 Fu no requirement on id{org.freedesktop.fwupd}Jul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0771 Fu no requirement on firmware{(null)}Jul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0771 Fu no paramater given for firmware{bootloader}Jul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0771 Fu no requirement on firmware{vendor-id}Jul 10 07:39:03 zacapa fwupd[11447]: 13:39:03:0771 Fu ignoring usb:00:03 [USB BootLoader] as not updatable live or offline

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (2) byronclark em 10 jul. 2017

Obtendo o mesmo erro aqui com 0.9.5-1.fc26 no Fedora 26. Eu tenho um M510 e K350 conectado ao dongle Logitech.

atualizaĆ§Ć£o fwupdmgr
Baixando RQR12.07_B0029 para Unificando Receptor ...
Atualizando RQR12.07_B0029 no receptor de unificaĆ§Ć£o ...
Gravandoā€¦ falhou ao apagar fw @ 0x00 : falhou ao enviar dados: Dispositivo 046d: aaaa nĆ£o foi aberto

lsusb -d 0x046D:
Dispositivo 003 do barramento 003: ID 046d: aaaa Logitech, Inc.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (3) pkovacs em 19 jul. 2017

Eu recebo o dispositivo "046d: aaac" nĆ£o aberto, mas meu dispositivo estĆ” agudamente em "046d: c52b" de acordo com lsusb.

[ henning @ satellite ~] $ sudo fwupdmgr -v install ./.cache/gnome-software/3.24/firmware/4511b9b0d123bdbe8a2007233318ab215a59dfe6-Logitech-Unifying-RQR24.05_B0029.cab
(fwupdmgr: 13098): Fwupd-DEBUG: Emitting :: status-changed () [descompactando]
Descompactandoā€¦ (fwupdmgr: 13098): Fwupd-DEBUG: Emitting :: device-removed ((null))
(fwupdmgr: 13098): Fwupd-DEBUG: Emitting :: changed ()
(fwupdmgr: 13098): Fwupd-DEBUG: Emitting :: status-changed () [device-write]
Gravandoā€¦ falha ao apagar todas as pĆ”ginas: falha ao enviar dados: Dispositivo 046d: aaac nĆ£o foi aberto
[ henning @ satellite ~] $ lsusb -d 0x046D:
Dispositivo 024 do barramento 002: ID 046d: c52b Logitech, Inc. Receptor de unificaĆ§Ć£o
[ henning @ satƩlite ~] $

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (4) hkskoglund em 19 jul. 2017

Qualquer um de vocĆŖs pode obter um --verbose log de fwupd, por favor. Obrigado!

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (5) hughsie em 19 jul. 2017

13:45:49:0960 Fu FuMain: acquired name: org.freedesktop.fwupd13:45:54:0175 Unifying [HID] host->device:10 01 00 10 00 00 aa 13:45:55:0725 Unifying [HID] device->host:10 01 8f 00 10 01 00 13:45:55:0726 Unifying [HID] host->device:10 02 00 10 00 00 aa 13:45:56:0139 Unifying [HID] device->host:10 02 8f 00 10 01 00 13:45:56:0139 Unifying [HID] device->host:10 01 8f 00 10 01 00 13:45:56:0139 Unifying failed to probe /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2: invalid SubID13:45:59:0178 Unifying [HID] device->host:02 00 00 06 90 fd 00 00 13:45:59:0178 Unifying report 0x02 unknown length13:45:59:0178 Unifying [HID] host->device:10 01 00 10 00 00 aa 13:45:59:0227 Unifying [HID] device->host:02 00 00 00 e0 ff 00 00 13:45:59:0227 Unifying report 0x02 unknown length13:45:59:0227 Unifying ignoring message13:45:59:0233 Unifying [HID] device->host:10 01 8f 00 10 01 00 13:45:59:0233 Unifying [HID] device->host:01 01 00 00 00 00 00 00 13:45:59:0233 Unifying [HID] host->device:10 02 00 10 00 00 aa 13:45:59:0405 Unifying [HID] device->host:10 02 8f 00 10 01 00 13:45:59:0405 Unifying [HID] device->host:10 02 8f 00 10 01 00 13:45:59:0405 Unifying failed to probe /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2: invalid SubID13:46:04:0183 Unifying [HID] device->host:02 00 00 ff 4f ff 00 00 13:46:04:0183 Unifying report 0x02 unknown length13:46:04:0183 Unifying [HID] host->device:10 01 00 10 00 00 aa 13:46:04:0195 Unifying [HID] device->host:10 01 8f 00 10 01 00 13:46:04:0195 Unifying [HID] device->host:01 01 00 00 00 00 00 00 13:46:04:0195 Unifying [HID] host->device:10 02 00 10 00 00 aa 13:46:04:0623 Unifying [HID] device->host:10 02 8f 00 10 01 00 13:46:04:0623 Unifying [HID] device->host:20 02 01 01 00 00 00 00 00 00 00 00 00 00 00 13:46:04:0623 Unifying report 0x20 unknown length13:46:09:0189 Unifying [HID] host->device:10 01 00 10 00 00 aa 13:46:09:0273 Unifying [HID] device->host:10 01 8f 00 10 01 00 13:46:09:0275 Unifying [HID] host->device:10 02 00 10 00 00 aa 13:46:09:0607 Unifying [HID] device->host:10 02 8f 00 10 01 00 13:46:09:0607 Unifying [HID] device->host:20 02 01 03 00 00 00 00 00 00 00 00 00 00 00 13:46:09:0607 Unifying report 0x20 unknown length13:46:14:0194 Unifying [HID] host->device:10 01 00 10 00 00 aa 13:46:15:0487 Unifying [HID] device->host:10 01 8f 00 10 01 00 13:46:15:0488 Unifying [HID] host->device:10 02 00 10 00 00 aa 13:46:15:0837 Unifying [HID] device->host:10 02 8f 00 10 01 00 13:46:15:0837 Unifying [HID] device->host:20 02 01 03 11 00 00 00 00 00 00 00 00 00 00 13:46:15:0837 Unifying report 0x20 unknown length13:46:18:0557 Fu Called Install(*,7)13:46:18:0557 Fu got option reason13:46:18:0557 Fu got option filename13:46:18:0557 Fu Emitting PropertyChanged('Status'='decompressing')13:46:18:0558 Fu Emitting PropertyChanged('Status'='decompressing')13:46:18:0560 As found file 0 RQR24.05_B0029.hex13:46:18:0560 As found file 1 com.logitech.Unifying.RQR24.metainfo.xml13:46:18:0561 As found file 2 RQR24.05_B0029.hex.asc13:46:18:0586 Fu Using keyring at /var/lib/fwupd/gnupg13:46:18:0590 Fu Adding public key /etc/pki/fwupd/GPG-KEY-Hughski-Limited13:46:18:0601 Fu importing key 7E5439F64986F7A9E973809BAD8A528FEC44881E [0] Success13:46:18:0601 Fu Adding public key /etc/pki/fwupd/GPG-KEY-Linux-Vendor-Firmware-Service13:46:18:0609 Fu importing key 3FC6B804410ED0840D8F2F9748A6D80E4538BAC2 [0] Success13:46:18:0613 Fu returned signature fingerprint 3FC6B804410ED0840D8F2F9748A6D80E4538BAC213:46:18:0613 Fu marking payload as trusted13:46:18:0617 Fu requirement 0.8.2 ge 0.9.5 on org.freedesktop.fwupd passed13:46:18:0617 Fu no requirement on firmware{(null)}13:46:18:0617 Fu requirement BOT03.0[0-1]_* regex BOT03.01_B0008 on bootloader passed13:46:18:0617 Fu no requirement on firmware{vendor-id}13:46:18:0617 Fu performing update_prepare() on upower13:46:18:0617 Fu FuPending: trying to open database '/var/lib/fwupd/pending.db'13:46:18:0619 Fu FuPending: get res13:46:18:0619 Unifying doing detach in idle13:46:18:0619 Unifying detaching13:46:18:0619 Unifying detaching device13:46:18:0619 Unifying [HID] host->device:10 ff 80 f0 49 43 50 13:46:18:0632 Unifying device /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2 removed13:46:18:0664 Unifying device /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.2/0003:046D:C52B.0049/0003:046D:101B.004A/hidraw/hidraw25 removed13:46:18:0722 Unifying device /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.2/0003:046D:C52B.0049/0003:046D:2011.004B/hidraw/hidraw26 removed13:46:18:0725 Fu emit removed from usb: usb:00:0213:46:18:0726 Fu Device usb:00:02 was not found13:46:19:0194 Unifying not polling device as replug in process13:46:20:0053 Unifying USB add usb:00:0213:46:20:0057 Unifying device /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2 added13:46:20:0057 Unifying waiting for device to settle...13:46:21:0057 Unifying opening unifying device using USB13:46:21:0057 Unifying claiming interface 0x0013:46:21:0058 Unifying host->device: 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 13:46:21:0058 Unifying UDEV add /dev/hidraw0 = /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/0003:046D:AAAC.004C/hidraw/hidraw013:46:21:0059 Unifying no HID_ID, skipping13:46:21:0059 Unifying device->host: 80 00 00 06 04 00 6b ff 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 13:46:21:0059 Unifying host->device: 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 13:46:21:0061 Unifying device->host: 90 00 00 0e 42 4f 54 30 33 2e 30 31 5f 42 30 30 30 38 00 00 00 00 00 00 00 00 00 00 00 00 00 00 13:46:21:0061 Unifying type: bootloader-texasflags: can-flash,active,is-open,requires-attachhidpp-version: 0,00hidpp-id: 0xffusb-device: 0x7f69d4001440platform-id: /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2vendor: Logitechproduct: Unifying [bootloader-texas]version-bootloader: BOT03.01_B0008version-firmware: RQR24.xx_Bxxxxguid: USB\VID_046D&PID_AAACflash-addr-high: 0x6bffflash-addr-low: 0x0400flash-block-size: 0x008013:46:21:0062 Unifying /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2 is in replug, quitting loop13:46:21:0062 Dfu device was not DFU capable13:46:21:0062 As run FuPluginEbitdo:added{046d:aaac}13:46:21:0062 As run FuPluginUsb:added{046d:aaac}13:46:21:0062 As run FuPluginUsb:get-string-desc13:46:21:0063 Fu using cc4cbfa9-bf9d-540b-b92b-172ce31013c1 for USB\VID_046D&PID_AAAC13:46:21:0063 Fu using de81631f-2117-51f8-bcb1-4f874a293b29 for USB\VID_046D&PID_AAAC&REV_030113:46:21:0063 Fu waiting a small time for other plugins13:46:21:0064 As run FuPluginAltos:added{046d:aaac}13:46:21:0064 Fu Emitting PropertyChanged('Status'='device-write')13:46:21:0064 Fu Emitting PropertyChanged('Status'='device-write')13:46:21:0069 Unifying host->device: d0 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 13:46:21:0565 Fu emit added from usb: usb:00:0213:46:21:0565 Fu no requirement on id{org.freedesktop.fwupd}13:46:21:0565 Fu no requirement on firmware{(null)}13:46:21:0565 Fu no paramater given for firmware{bootloader}13:46:21:0565 Fu no requirement on firmware{vendor-id}13:46:21:0565 Fu ignoring usb:00:02 [USB BootLoader] as not updatable live or offline13:46:24:0534 Fu Called GetUpdates()13:46:24:0534 Fu no requirement on id{org.freedesktop.fwupd}13:46:24:0534 Fu no requirement on firmware{(null)}13:46:24:0534 Fu no requirement on firmware{bootloader}13:46:24:0534 Fu no requirement on firmware{vendor-id}13:46:24:0535 Fu no requirement on id{org.freedesktop.fwupd}13:46:24:0535 Fu no requirement on firmware{(null)}13:46:24:0535 Fu no paramater given for firmware{bootloader}13:46:24:0535 Fu no requirement on firmware{vendor-id}13:46:24:0535 Fu ignoring usb:00:02 [USB BootLoader] as not updatable live or offline13:46:24:0640 Fu Called GetUpdates()13:46:24:0640 Fu no requirement on id{org.freedesktop.fwupd}13:46:24:0640 Fu no requirement on firmware{(null)}13:46:24:0641 Fu no requirement on firmware{bootloader}13:46:24:0641 Fu no requirement on firmware{vendor-id}13:46:24:0641 Fu no requirement on id{org.freedesktop.fwupd}13:46:24:0641 Fu no requirement on firmware{(null)}13:46:24:0641 Fu no paramater given for firmware{bootloader}13:46:24:0641 Fu no requirement on firmware{vendor-id}13:46:24:0641 Fu ignoring usb:00:02 [USB BootLoader] as not updatable live or offline13:46:32:0678 Unifying device /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2 removed13:46:32:0678 Unifying closing device13:46:32:0678 Fu emit removed from usb: usb:00:0213:46:35:0536 Fu Called GetUpdates()13:46:35:0537 Fu no requirement on id{org.freedesktop.fwupd}13:46:35:0537 Fu no requirement on firmware{(null)}13:46:35:0537 Fu no requirement on firmware{bootloader}13:46:35:0537 Fu no requirement on firmware{vendor-id}13:46:35:0631 Fu Called GetUpdates()13:46:35:0631 Fu no requirement on id{org.freedesktop.fwupd}13:46:35:0631 Fu no requirement on firmware{(null)}13:46:35:0631 Fu no requirement on firmware{bootloader}13:46:35:0631 Fu no requirement on firmware{vendor-id}13:46:39:0090 Unifying USB add usb:00:0213:46:39:0090 Dfu device was not DFU capable13:46:39:0091 As run FuPluginEbitdo:added{046d:c52b}13:46:39:0091 As run FuPluginUsb:added{046d:c52b}13:46:39:0091 As run FuPluginUsb:get-string-desc13:46:39:0092 Fu using 77d843f7-682c-57e8-8e29-584f5b4f52a1 for USB\VID_046D&PID_C52B13:46:39:0092 Fu using 961d0fda-3bef-5eaa-ab4c-ce1dbfd492fe for USB\VID_046D&PID_C52B&REV_240113:46:39:0092 Fu waiting a small time for other plugins13:46:39:0092 As run FuPluginAltos:added{046d:c52b}13:46:39:0096 Unifying UDEV add /dev/hidraw0 = /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.2/0003:046D:C52B.004F/hidraw/hidraw013:46:39:0096 Unifying closing device13:46:39:0096 Unifying device /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2 added13:46:39:0096 Unifying waiting for device to settle...13:46:40:0097 Unifying opening unifying device using /dev/hidraw013:46:40:0097 Unifying [HID] host->device:10 ff 81 f1 01 00 00 13:46:40:0097 Unifying [HID] device->host:20 01 02 00 00 f6 5f 00 00 00 e9 00 00 00 00 13:46:40:0097 Unifying report 0x20 unknown length13:46:40:0098 Unifying ignoring message13:46:40:0099 Unifying [HID] device->host:10 ff 81 f1 01 24 01 13:46:40:0099 Unifying [HID] host->device:10 ff 81 f1 02 00 00 13:46:40:0101 Unifying [HID] device->host:10 ff 81 f1 02 00 23 13:46:40:0101 Unifying [HID] host->device:10 ff 81 f1 04 00 00 13:46:40:0103 Unifying [HID] device->host:10 ff 81 f1 04 01 08 13:46:40:0103 Unifying [HID] host->device:10 ff 80 00 00 05 00 13:46:40:0105 Unifying [HID] device->host:20 01 02 00 00 fb 2f 00 00 00 14 00 00 00 00 13:46:40:0105 Unifying report 0x20 unknown length13:46:40:0105 Unifying ignoring message13:46:40:0107 Unifying [HID] device->host:10 ff 80 00 00 00 00 13:46:40:0107 Unifying type: runtimeflags: can-flash,active,is-open,requires-detach,detach-will-replughidpp-version: 1,00hidpp-id: 0xffudev-device: 19platform-id: /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2vendor: Logitechproduct: Unifying Receiverversion-bootloader: BOT03.01_B0008version-firmware: RQR24.01_B0023guid: USB\VID_046D&PID_C52Bguid: USB\VID_046D&PID_AAAC13:46:40:0108 Unifying UDEV add /dev/hidraw2 = /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.2/0003:046D:C52B.004F/0003:046D:2011.0051/hidraw/hidraw213:46:40:0108 Unifying device /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.2/0003:046D:C52B.004F/0003:046D:2011.0051/hidraw/hidraw2 added13:46:40:0108 Unifying waiting for device to settle...13:46:41:0108 Unifying opening unifying device using /dev/hidraw213:46:41:0108 Unifying [HID] host->device:10 fe 00 10 00 00 aa 13:46:41:0111 Unifying [HID] device->host:10 02 8f 00 10 09 00 13:46:41:0112 Unifying closing device13:46:41:0112 Unifying could not open: device K520 is unreachable: resource error13:46:41:0112 Unifying [HID] device->host:20 01 02 00 00 f9 0f 00 00 00 36 00 00 00 00 13:46:41:0112 Unifying report 0x20 unknown length13:46:41:0112 Fu emit added from usb: usb:00:0213:46:41:0112 Unifying UDEV add /dev/hidraw1 = /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.2/0003:046D:C52B.004F/0003:046D:101B.0050/hidraw/hidraw113:46:41:0113 Unifying device /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.2/0003:046D:C52B.004F/0003:046D:101B.0050/hidraw/hidraw1 added13:46:41:0114 Unifying waiting for device to settle...13:46:42:0114 Unifying opening unifying device using /dev/hidraw113:46:42:0114 Unifying [HID] host->device:10 fe 00 10 00 00 aa 13:46:42:0159 Unifying [HID] device->host:10 01 8f 00 10 01 00 13:46:42:0159 Unifying [HID] host->device:10 fe 00 00 00 03 00 13:46:42:0259 Unifying [HID] device->host:10 01 8f 00 00 01 00 13:46:42:0259 Unifying failed to get idx for feature IFirmwareInfo [0x0003]: invalid SubID13:46:42:0259 Unifying [HID] host->device:10 fe 00 00 10 00 00 13:46:42:0361 Unifying [HID] device->host:10 01 8f 00 00 01 00 13:46:42:0361 Unifying failed to get idx for feature BatteryLevelStatus [0x1000]: invalid SubID13:46:42:0361 Unifying [HID] host->device:10 fe 00 00 00 c1 00 13:46:42:0463 Unifying [HID] device->host:10 01 8f 00 00 01 00 13:46:42:0464 Unifying failed to get idx for feature DfuControl [0x00c1]: invalid SubID13:46:42:0464 Unifying [HID] host->device:10 fe 00 00 00 c2 00 13:46:42:0565 Unifying [HID] device->host:10 01 8f 00 00 01 00 13:46:42:0565 Unifying failed to get idx for feature DfuControlSigned [0x00c2]: invalid SubID13:46:42:0566 Unifying [HID] host->device:10 fe 00 00 00 d0 00 13:46:42:0667 Unifying [HID] device->host:10 01 8f 00 00 01 00 13:46:42:0667 Unifying failed to get idx for feature Dfu [0x00d0]: invalid SubID13:46:42:0667 Unifying [HID] host->device:10 fe 81 0d 00 00 00 13:46:42:0767 Unifying [HID] device->host:10 01 81 0d 41 47 34 13:46:42:0767 Unifying HID++ ID now 0113:46:42:0767 Unifying type: peripheralflags: active,is-openhidpp-version: 1,00hidpp-id: 0x01udev-device: 21platform-id: /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.2/0003:046D:C52B.004F/0003:046D:101B.0050/hidraw/hidraw1vendor: Logitechproduct: M705guid: UFY\VID_046D&PID_101Bbattery-level: 65[henning<strong i="5">@satellite</strong> ~]$ sudo journalctl -f-- Logs begin at Thu 2016-03-17 15:19:48 CET. --juli 19 15:38:52 satellite fwupd[2450]: report 0x20 unknown lengthjuli 19 15:38:52 satellite fwupd[2450]: report 0x02 unknown lengthjuli 19 15:38:57 satellite fwupd[2450]: report 0x20 unknown lengthjuli 19 15:38:57 satellite fwupd[2450]: report 0x02 unknown lengthjuli 19 15:38:59 satellite sudo[13568]: henning : TTY=pts/4 ; PWD=/home/henning ; USER=root ; COMMAND=/bin/journalctl -fjuli 19 15:38:59 satellite audit[13568]: USER_CMD pid=13568 uid=1000 auid=1000 ses=3 msg='cwd="/home/henning" cmd=6A6F75726E616C63746C202D66 terminal=pts/4 res=success'juli 19 15:38:59 satellite audit[13568]: CRED_REFR pid=13568 uid=0 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'juli 19 15:38:59 satellite sudo[13568]: pam_systemd(sudo:session): Cannot create session: Already occupied by a sessionjuli 19 15:38:59 satellite audit[13568]: USER_START pid=13568 uid=0 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'juli 19 15:38:59 satellite sudo[13568]: pam_unix(sudo:session): session opened for user root by (uid=0)juli 19 15:39:02 satellite fwupd[2450]: report 0x20 unknown lengthjuli 19 15:39:02 satellite fwupd[2450]: report 0x02 unknown lengthjuli 19 15:39:07 satellite fwupd[2450]: report 0x20 unknown lengthjuli 19 15:39:12 satellite fwupd[2450]: report 0x20 unknown lengthjuli 19 15:39:12 satellite fwupd[2450]: report 0x02 unknown lengthjuli 19 15:39:13 satellite sudo[13570]: henning : TTY=pts/0 ; PWD=/home/henning ; USER=root ; COMMAND=/bin/fwupdmgr -v install ./.cache/gnome-software/3.24/firmware/4511b9b0d123bdbe8a2007233318ab215a59dfe6-Logitech-Unifying-RQR24.05_B0029.cabjuli 19 15:39:13 satellite audit[13570]: USER_CMD pid=13570 uid=1000 auid=1000 ses=3 msg='cwd="/home/henning" cmd=66777570646D6772202D7620696E7374616C6C202E2F2E63616368652F676E6F6D652D736F6674776172652F332E32342F6669726D776172652F343531316239623064313233626462653861323030373233333331386162323135613539646665362D4C6F6769746563682D556E696679696E672D52515232342E30355F42303032392E636162 terminal=pts/0 res=success'juli 19 15:39:13 satellite audit[13570]: CRED_REFR pid=13570 uid=0 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'juli 19 15:39:13 satellite sudo[13570]: pam_systemd(sudo:session): Cannot create session: Already occupied by a sessionjuli 19 15:39:13 satellite audit[13570]: USER_START pid=13570 uid=0 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'juli 19 15:39:13 satellite sudo[13570]: pam_unix(sudo:session): session opened for user root by (uid=0)juli 19 15:39:13 satellite kernel: usb 2-2: USB disconnect, device number 26juli 19 15:39:13 satellite gnome-shell[1785]: Could not release device 13,70: GDBus.Error:org.freedesktop.login1.DeviceNotTaken: Device not takenjuli 19 15:39:14 satellite kernel: usb 2-2: new full-speed USB device number 27 using xhci_hcdjuli 19 15:39:14 satellite kernel: usb 2-2: New USB device found, idVendor=046d, idProduct=aaacjuli 19 15:39:14 satellite kernel: usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0juli 19 15:39:14 satellite kernel: usb 2-2: Product: USB BootLoaderjuli 19 15:39:14 satellite kernel: usb 2-2: Manufacturer: Logitechjuli 19 15:39:14 satellite kernel: hid-generic 0003:046D:AAAC.0046: hiddev0,hidraw24: USB HID v1.11 Device [Logitech USB BootLoader] on usb-0000:00:14.0-2/input0juli 19 15:39:14 satellite mtp-probe[13601]: checking bus 2, device 27: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-2"juli 19 15:39:15 satellite mtp-probe[13601]: bus: 2, device: 27 was not an MTP devicejuli 19 15:39:16 satellite sudo[13570]: pam_unix(sudo:session): session closed for user rootjuli 19 15:39:16 satellite audit[13570]: USER_END pid=13570 uid=0 auid=1000 ses=3 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'juli 19 15:39:16 satellite audit[13570]: CRED_DISP pid=13570 uid=0 auid=1000 ses=3 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'juli 19 15:39:19 satellite PackageKit[1471]: get-updates transaction /2527_bcacbbdd from uid 1000 finished with success after 28msjuli 19 15:39:20 satellite kernel: usb 2-2: USB disconnect, device number 27juli 19 15:39:22 satellite kernel: usb 2-2: new full-speed USB device number 28 using xhci_hcdjuli 19 15:39:22 satellite kernel: usb 2-2: New USB device found, idVendor=046d, idProduct=c52bjuli 19 15:39:22 satellite kernel: usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0juli 19 15:39:22 satellite kernel: usb 2-2: Product: USB Receiverjuli 19 15:39:22 satellite kernel: usb 2-2: Manufacturer: Logitechjuli 19 15:39:22 satellite kernel: logitech-djreceiver 0003:046D:C52B.0049: hiddev0,hidraw24: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-2/input2juli 19 15:39:22 satellite mtp-probe[13621]: checking bus 2, device 28: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-2"juli 19 15:39:22 satellite mtp-probe[13621]: bus: 2, device: 28 was not an MTP devicejuli 19 15:39:22 satellite kernel: input: Logitech M705 as /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.2/0003:046D:C52B.0049/0003:046D:101B.004A/input/input47juli 19 15:39:22 satellite kernel: logitech-hidpp-device 0003:046D:101B.004A: input,hidraw25: USB HID v1.11 Mouse [Logitech M705] on usb-0000:00:14.0-2:1juli 19 15:39:22 satellite kernel: input: Logitech K520 as /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.2/0003:046D:C52B.0049/0003:046D:2011.004B/input/input48juli 19 15:39:22 satellite kernel: logitech-hidpp-device 0003:046D:2011.004B: input,hidraw26: USB HID v1.11 Keyboard [Logitech K520] on usb-0000:00:14.0-2:2juli 19 15:39:23 satellite fwupd[2450]: report 0x20 unknown lengthjuli 19 15:39:24 satellite fwupd[2450]: report 0x02 unknown lengthjuli 19 15:39:24 satellite PackageKit[1471]: get-updates transaction /2528_eadbbdbe from uid 1000 finished with success after 58msjuli 19 15:39:27 satellite fwupd[2450]: report 0x20 unknown lengthjuli 19 15:39:27 satellite fwupd[2450]: report 0x02 unknown length

(editado por @ superm1 para inserir no bloco de cĆ³digo)

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (6) hkskoglund em 19 jul. 2017

Anexar logs de fwupdmgr comandos e journalctl saĆ­da de terminal separado durante a execuĆ§Ć£o de fwupd no modo verbose.

fwupd, txt

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (7) pkovacs em 19 jul. 2017

TambĆ©m estou tendo problemas com a atualizaĆ§Ć£o do firmware de UnificaĆ§Ć£o, fwupd 0.9.5 no Arch Linux. No meu caso, a mensagem de erro diz:

failed to erase fw <strong i="6">@0x00</strong>: failed to send data: Device 046d:aaaa has not been opened

em seguida, o receptor para de funcionar e precisa ser reconectado manualmente. Isso ocorre em ambos os meus dois dongles receptores Unificadores. Ambos os IDs de dispositivo tambĆ©m sĆ£o 046d: c52b.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (8) intgr em 20 jul. 2017

O mesmo problema aqui no Fedora 26 com um mouse Logitech M325.

[root@mobile-tek ~]# fwupdmgr --verbose updateDownloading RQR12.07_B0029 for Unifying [bootloader-nordic]...(fwupdmgr:6120): Fu-DEBUG: downloading https://secure-lvfs.rhcloud.com/downloads/938fec082652c603a1cdafde7cd25d76baadc70d-Logitech-Unifying-RQR12.07_B0029.cab to /root/.cache/fwupdmgr/938fec082652c603a1cdafde7cd25d76baadc70d-Logitech-Unifying-RQR12.07_B0029.cabFetching firmware https://secure-lvfs.rhcloud.com/downloads/938fec082652c603a1cdafde7cd25d76baadc70d-Logitech-Unifying-RQR12.07_B0029.cab(fwupdmgr:6120): Fu-DEBUG: ignoring status code 301 (MOVED PERMANENTLY)(fwupdmgr:6120): Fu-DEBUG: progress: 27%Downloadingā€¦ [********** ](fwupdmgr:6120): Fu-DEBUG: progress: 54%Downloadingā€¦ [********************* ](fwupdmgr:6120): Fu-DEBUG: progress: 56%Downloadingā€¦ [********************** ](fwupdmgr:6120): Fu-DEBUG: progress: 84%Downloadingā€¦ [********************************* ](fwupdmgr:6120): Fu-DEBUG: progress: 100%Downloadingā€¦ [****************************************]Updating RQR12.07_B0029 on Unifying [bootloader-nordic]...(fwupdmgr:6120): Fwupd-DEBUG: Emitting ::status-changed() [decompressing]Decompressingā€¦ (fwupdmgr:6120): Fwupd-DEBUG: Emitting ::status-changed() [device-write]Writingā€¦ failed to erase fw <strong i="6">@0x00</strong>: failed to send data: Device 046d:aaaa has not been opened

lsusb relata IDs de dispositivos diferentes:

Bus 002 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (9) dadreggors em 21 jul. 2017

Apenas por um palpite, algum de vocĆŖs estĆ” fazendo isso em computadores de 32 bits?

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (10) hughsie em 21 jul. 2017

NĆ£o eu, 64 bits aqui.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (11) dadreggors em 21 jul. 2017

x86_64 aqui

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (12) pkovacs em 21 jul. 2017

TambƩm em x86_64.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (13) byronclark em 21 jul. 2017

Eu tenho o mesmo problema no gnome wayland no arch, vocĆŖ quer meus dados tambĆ©m?
x86_64

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (14) Anoian em 21 jul. 2017

Puxei o dongle Logitech e, olhando para os cĆ³digos gravados em um lado do metal, li:

LZ304BS-DJ
M/N: C-U0007

AlĆ©m disso, percebi que o daemon estĆ” inundando os logs (no modo normal, nĆ£o detalhado) com esta mensagem:

Jul 21 19:49:53 athos fwupd[4466]: report 0x20 unknown length

Eu tenho fwupd mascarado por enquanto.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (15) pkovacs em 22 jul. 2017

Consegui fazer a atualizaĆ§Ć£o do firmware em um computador diferente - ambos executando exatamente a mesma configuraĆ§Ć£o, estaĆ§Ć£o de trabalho Fedora 26, e ambos executando a mesma revisĆ£o do fwupd (0.9.5-1.fc26). O comp mais recente em que a atualizaĆ§Ć£o foi bem-sucedida tambĆ©m Ć© o x86_64, mas Ć© um sistema Intel i7 mais recente e usa UEFI. O comp mais antigo, onde a atualizaĆ§Ć£o estava falhando, Ć© um Intel E6850 baseado em BIOS. Primeiro desconectei o dongle do sistema antigo e DESLIGUEi o teclado e o mouse. O sistema mais recente usa acessĆ³rios com fio. Em seguida, conectei o dongle a uma porta USB no novo sistema e executei a atualizaĆ§Ć£o sem problemas. Funcionou na primeira tentativa e RQR12.07_B0029 foi escrito sem erros. Mudei o dongle de volta para o comp antigo e ele estĆ” funcionando bem.

fwupdmgr -v update
Baixando RQR12.07_B0029 para Unificando Receptor ...
(fwupdmgr: 3186): Fu-DEBUG: download https://secure-lvfs.rhcloud.com/downloads/938fec082652c603a1cdafde7cd25d76baadc70d-Logitech-Unifying-RQR12.07_B0029.cab para /root/.cache/fwupdmgr/938fec082652c603a1cdafde7cd25d76baadc70d-Logitech-Unifying -RQR12.07_B0029.cab
Buscando firmware https://secure-lvfs.rhcloud.com/downloads/938fec082652c603a1cdafde7cd25d76baadc70d-Logitech-Unifying-RQR12.07_B0029.cab
(fwupdmgr: 3186): Fu-DEBUG: ignorando o cĆ³digo de status 301 (MOVIDO PERMANENTEMENTE)
(fwupdmgr: 3186): Fu-DEBUG: progresso: 27%
Baixandoā€¦ * * : Fu-DEBUG: progresso: 54%
Baixandoā€¦ * * * * * * : Fu-DEBUG: progresso: 56%
Baixandoā€¦ * * * * * * : Fu-DEBUG: progresso: 84%
Baixandoā€¦ * * * * * * * * * : Fu-DEBUG: progresso: 100%
Baixandoā€¦ [ * * * * * * * * * * * * ]
Atualizando RQR12.07_B0029 no receptor de unificaĆ§Ć£o ...
(fwupdmgr: 3186): Fwupd-DEBUG: Emitting :: status-changed () [descompactando]
Descompactandoā€¦ (fwupdmgr: 3186): Fwupd-DEBUG: Emitting :: device-removed ((null))
(fwupdmgr: 3186): Fwupd-DEBUG: Emitting :: changed ()
(fwupdmgr: 3186): Fwupd-DEBUG: Emitting :: status-changed () [device-write]
Escrevendoā€¦ * * * * * * * * * * * * * : Fwupd-DEBUG: Emitting :: status-changed () [reinicializaĆ§Ć£o do dispositivo]
Reiniciando o dispositivoā€¦ * * * * * * * * * * * ** : Fwupd-DEBUG: Emitting :: device-changed ((null))
(fwupdmgr: 3186): Fwupd-DEBUG: Emitting :: changed ()

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (16) pkovacs em 22 jul. 2017

Correndo o risco de adicionar um ... erm, eu tambƩm. Fedora 26, recentemente atualizado do 25 (4.11.10-300.fc26.x86_64 / fwupd-0.9.5-1.fc26.x86_64).

$ sudo fwupdmgr update --verboseDownloading RQR12.07_B0029 for Unifying Receiver...(fwupdmgr:12736): Fu-DEBUG: skpping download as file already existsUpdating RQR12.07_B0029 on Unifying Receiver...(fwupdmgr:12736): Fwupd-DEBUG: Emitting ::status-changed() [decompressing]Decompressingā€¦ (fwupdmgr:12736): Fwupd-DEBUG: Emitting ::status-changed() [device-write]Writingā€¦ failed to erase fw <strong i="8">@0x00</strong>: failed to send data: Device 046d:aaaa has not been opened

Se desejar logs daemon detalhados, vocĆŖ terĆ” que explicar como (!), Tudo o que recebo em _journalctl_ Ć© uma cĆ³pia do que @pkovacs estĆ” vendo: wads de ā€œ report 0x20 unknown length ā€ (e alguns 0x02 s e um ā€œ SubID 81 desconhecido ā€ que pode ter vindo de uma tentativa de atualizaĆ§Ć£o).

NĆ£o tenho certeza se seria relevante, mas os itens que tenho sĆ£o um teclado K800 e um mouse MX Master.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (17) fnxweb em 22 jul. 2017

Estou vendo isso hoje em um sistema Arch Linux atualizado (fwupd Ć© a versĆ£o 0.9.5-3).

$ fwupdmgr update -vDownloading RQR12.07_B0029 for Unifying [bootloader-nordic]...(fwupdmgr:1533): Fu-DEBUG: skpping download as file already existsUpdating RQR12.07_B0029 on Unifying [bootloader-nordic]...(fwupdmgr:1533): Fwupd-DEBUG: Emitting ::status-changed() [decompressing]Decompressingā€¦ (fwupdmgr:1533): Fwupd-DEBUG: Emitting ::status-changed() [device-write]Writingā€¦ failed to erase fw <strong i="6">@0x00</strong>: failed to send data: Device 046d:aaaa has not been opened

Esta Ć© a saĆ­da de fwupdmgr get-devices:

 Guid: 9d131a0c-a606-580f-8eda-80587250b8d6 DeviceID: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1 DisplayName: Unifying [bootloader-nordic] Description: <p>A Unifying receiver allows you to connect multiple compatible keyboards and mice to a laptop or desktop computer with a single USB receiver. Updating the firmware on your Unifying receiver improves performance, adds new features and fixes security issues.</p> Plugin: unifying Flags: allow-online|supported DeviceVendor: Logitech DeviceVendorId: USB:0x046D Version: RQR12.01_B0019 VersionBootloader: BOT01.02_B0014 Created: 2017-07-22 Guid: 7039436b-6acf-433b-86a1-368ec2ef7e1f DeviceID: UEFI-7039436b-6acf-433b-86a1-368ec2ef7e1f-dev0 DisplayName: MS-7885 Plugin: uefi Flags: internal|allow-offline|require-ac Version: 0.0.2550 VersionLowest: 0.0.2550 Created: 2017-07-22 Guid: eb7d0014-915d-548d-b014-23e153b3d6ee DeviceID: ro__sys_devices_pci0000_00_0000_00_03_0_0000_03_00_0 DisplayName: GM204 [GeForce GTX 980] Plugin: udev Flags: internal DeviceVendor: NVIDIA Corporation DeviceVendorId: PCI:0x10DE Created: 2017-07-22 Guid: 77d843f7-682c-57e8-8e29-584f5b4f52a1 Guid: 9f1820d3-8b97-5d02-8889-b47b2037247b DeviceID: usb:00:07 DisplayName: USB Receiver Plugin: usb Flags: none DeviceVendorId: USB:0x046D Version: 18.1 Created: 2017-07-22

Eu tambĆ©m tenho visto fwupd[1420]: report 0x20 unknown length spam no jornal a cada poucos segundos desde entĆ£o.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (18) jamsla em 22 jul. 2017

Algum de vocĆŖs pode tentar com git master? NĆ£o acho que haja algo especĆ­fico do Unifying no master que vĆ” consertar isso, mas estou me perguntando se a correĆ§Ć£o da tabela de hash do dispositivo Ć© a verdadeira correĆ§Ć£o para esse bug. Obrigado.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (19) hughsie em 22 jul. 2017

Para tentar isso rapidamente, eu apenas modifiquei o PKGBUILD do pacote Arch para baixar master.tar.gz em vez de $ {pkgver} .tar.gz, e construĆ­ e instalei ( updpkgsums / makepkg -s / pacman -U ). Depois de reiniciar, nĆ£o vejo nenhuma mudanƧa:

Downloading RQR12.07_B0029 for Unifying Receiver...(fwupdmgr:1663): Fu-DEBUG: skpping download as file already existsUpdating RQR12.07_B0029 on Unifying Receiver...(fwupdmgr:1663): Fwupd-DEBUG: Emitting ::status-changed() [decompressing]Decompressingā€¦ (fwupdmgr:1663): Fwupd-DEBUG: Emitting ::status-changed() [idle](fwupdmgr:1663): Fwupd-DEBUG: Emitting ::device-removed((null))(fwupdmgr:1663): Fwupd-DEBUG: Emitting ::changed()(fwupdmgr:1663): Fwupd-DEBUG: Emitting ::status-changed() [device-write]Writingā€¦ failed to erase fw <strong i="9">@0x00</strong>: failed to send data: Device 046d:aaaa has not been opened

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (20) jamsla em 22 jul. 2017

No comeƧo eu tive esse erro
failed to erase fw <strong i="6">@0x00</strong>: failed to send data: Device 046d:aaaa has not been opened
mas depois de tentar atualizar vƔrias vezes, mudou para
not found /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.3

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (21) ghost em 22 jul. 2017

EntĆ£o, passei algumas horas tentando depurar isso agora. Acho que o que estĆ” acontecendo Ć© que o GUsbDevice de baixo nĆ­vel estĆ” sendo fechado, em vez do LuDevice que o envolve. Basicamente, o LuDevice estĆ” ABERTO, mas o dispositivo subjacente estĆ” fechado. Acho que estĆ” sendo fechado por outro plugin. A depuraĆ§Ć£o continua ...

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (22) hughsie em 22 jul. 2017

Ok, isso pode ser complicado, muito bem se vocĆŖ conseguir fazer isso por mim ...

VocĆŖ pode construir e instalar:

  • libgusb, branch wip/hughsie/GUsbContextFlags
  • fwupd, branch wip/hughsie/GUsbContextFlags

VocĆŖ precisa ter certeza de que o Ćŗltimo realmente se relaciona com o primeiro. Se funcionar, grite e adicionarei mais algum texto de confirmaĆ§Ć£o, empurre-os para master e faƧa um novo tarball do anterior. Obrigado!

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (23) hughsie em 22 jul. 2017

Desculpem a espera - fico feliz em informar que os branches GUsbContextFlags parecem resolver o problema:

Downloading RQR12.07_B0029 for Unifying Receiver...(fwupdmgr:1631): Fu-DEBUG: skpping download as file already existsUpdating RQR12.07_B0029 on Unifying Receiver...(fwupdmgr:1631): Fwupd-DEBUG: Emitting ::status-changed() [decompressing]Decompressingā€¦ (fwupdmgr:1631): Fwupd-DEBUG: Emitting ::status-changed() [idle](fwupdmgr:1631): Fwupd-DEBUG: Emitting ::device-removed((null))(fwupdmgr:1631): Fwupd-DEBUG: Emitting ::changed()(fwupdmgr:1631): Fwupd-DEBUG: Emitting ::status-changed() [device-write]Writingā€¦ (fwupdmgr:1631): Fwupd-DEBUG: Emitting ::device-added((null))(fwupdmgr:1631): Fwupd-DEBUG: Emitting ::changed()Writingā€¦ [****************************************](fwupdmgr:1631): Fwupd-DEBUG: Emitting ::status-changed() [device-restart]Restarting deviceā€¦ [****************************************](fwupdmgr:1631): Fwupd-DEBUG: Emitting ::device-removed((null))(fwupdmgr:1631): Fwupd-DEBUG: Emitting ::changed()(fwupdmgr:1631): Fwupd-DEBUG: Emitting ::status-changed() [idle](fwupdmgr:1631): Fwupd-DEBUG: Emitting ::device-changed((null))(fwupdmgr:1631): Fwupd-DEBUG: Emitting ::changed()

Depois disso, nĆ£o tive problemas para usar o receptor. Quando estava falhando, tive que extrair e reinserir o receptor antes de continuar.

Aqui estĆ” o log do daemon, caso seja de interesse: fwupd.log.gz

Algumas notas:

  • Em primeiro lugar, no log daemon, o processo de gravaĆ§Ć£o sĆ³ vai atĆ© "Unificando 29568/49696 bytes [59,5%]". Presumo que seja normal e o espaƧo restante nĆ£o seja usado.
  • Em segundo lugar, ainda estou vendo um relatĆ³rio a cada cinco segundos no diĆ”rio, embora em vez de "relatĆ³rio 0x20 comprimento desconhecido" agora esteja no formato "dispositivo-> host: 20 01 02 00 00 df 0f 00 00 00 00 00 00 00 00 ". Eu imagino que este seja um assunto nĆ£o relacionado.

Muito obrigado por todo o seu esforƧo nisso!

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (24) jamsla em 23 jul. 2017

Estou confuso por que vocĆŖ estĆ” vendo o log de depuraĆ§Ć£o no diĆ”rio, que deveria ser Info / Warning etc.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (25) hughsie em 23 jul. 2017

Ohh, e tambƩm obrigado pelo teste rƔpido!

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (26) hughsie em 23 jul. 2017

NĆ£o se preocupe com o log de depuraĆ§Ć£o no diĆ”rio - usei "systemctl edit fwupd" para adicionar o sinalizador --verbose. Se eu reverter isso, as coisas ficam mais calmas :)

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (27) jamsla em 23 jul. 2017

@pkovacs - uma pergunta bastante estranha - o sistema de arquivos raiz Ʃ diferente entre as mƔquinas BIOS e UEFI, por acaso?

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (28) hughsie em 24 jul. 2017

Se vocĆŖ Ć© um usuĆ”rio do Fedora, carma apreciado pela atualizaĆ§Ć£o: https://bodhi.fedoraproject.org/updates/FEDORA-2017-06c7317f1f

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (29) hughsie em 24 jul. 2017

@hughsie Ambos os computadores estĆ£o usando volumes lĆ³gicos lvm2 para o sistema de arquivos raiz com ext4 como o sistema de arquivos real por baixo. O sistema UEFI Ć© baseado em ssd e eu tenho o bit noatime definido no sistema de arquivos. O sistema BIOS estĆ” usando uma unidade de disco comum. De qualquer forma, parece que vocĆŖ encerrou o problema.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (30) pkovacs em 24 jul. 2017

VocĆŖ pode lanƧar uma nova versĆ£o para que outras distros tambĆ©m possam atualizar? NĆ£o consigo construir libgusb e vinculĆ”-lo ao fwupd. Obrigada.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (31) SinBirb em 24 jul. 2017

Eu fiz um novo libgusb upstream hoje. Um novo fwupd demorarĆ” mais alguns dias.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (32) hughsie em 24 jul. 2017

Tentei o novo pacote libgusb e nĆ£o consigo instalar o firmware.

[ henning @ satellite ~] $ sudo dnf info libgusb
ƚltima verificaĆ§Ć£o de expiraĆ§Ć£o de metadados: 0:59:00 atrĆ”s em. 27. juli 2017 kl. 11,22 +0200.
Pakker som er installert
Nome: libgusb
Versjon: 0.2.11
VersĆ£o: 1.fc26
Arkitektur: x86_64
StĆørrelse: 108 k
Fonte: libgusb-0.2.11-1.fc26.src.rpm
Repo: @System
Do repo: updates-testing
Resumo: envoltĆ³rio GLib em torno de libusb1
URL: https://gitorious.org/gusb/
LicenƧa: LGPLv2 +
DescriĆ§Ć£o: GUsb Ć© um wrapper GObject para libusb1 que o torna fĆ”cil de fazer
: controle assĆ­ncrono, transferĆŖncias em massa e de interrupĆ§Ć£o com
: cancelamento e integraĆ§Ć£o em um mainloop.

EntĆ£o eu habilitei o ambiente de depuraĆ§Ć£o LIBUSB_DEBUG 4 no fwupd

sudo env LIBUSB_DEBUG = 4 / usr / libexec / fwupd / fwupd -v e executou fwupdmgr -v update

Vejo trĆŖs linhas logo apĆ³s a outra, parece que o libusb estĆ” fechando um dispositivo, provavelmente 0x46D: AAAC? e, em seguida, a gravaĆ§Ć£o do dispositivo falha.

10: 19: 14: 0652 Fu usando cc4cbfa9-bf9d-540b-b92b-172ce31013c1 para USB \ VID_046D & PID_AAAC
10: 19: 14: 0652 Fu usando de81631f-2117-51f8-bcb1-4f874a293b29 para USB \ VID_046D & PID_AAAC & REV_0301
[8.654633] [00005431] libusb: depurar [libusb_close]
...
10: 19: 14: 0655 Host-> dispositivo unificador: d0 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

10: 19: 09: 0534 Fu FuMain: nome adquirido: org.freedesktop.fwupd
10: 19: 12: 0149 Fu chamou GetUpdates ()
10: 19: 12: 0149 Fu nenhum requisito no id {org.freedesktop.fwupd}
10: 19: 12: 0149 Fu nenhum requisito no firmware {(nulo)}
10: 19: 12: 0149 Fu nenhum requisito no firmware {bootloader}
10: 19: 12: 0149 Fu nenhum requisito no firmware {id do fornecedor}
10: 19: 12: 0150 Fu chamou GetRemotes ()
10: 19: 12: 0152 InstalaĆ§Ć£o chamada Fu (/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1,7)
10: 19: 12: 0152 Fu tem o motivo da opĆ§Ć£o
10: 19: 12: 0152 Fu tem o nome do arquivo de opĆ§Ć£o
10: 19: 12: 0152 Fu Emitting PropertyChanged ('Status' = 'descompactando')
10: 19: 12: 0152 Fu Emitting PropertyChanged ('Status' = 'descompactando')
10: 19: 12: 0153 Arquivo encontrado 0 RQR24.05_B0029.hex
10: 19: 12: 0153 Conforme encontrado o arquivo 1 com.logitech.Unifying.RQR24.metainfo.xml
10: 19: 12: 0154 Arquivo 2 RQR24.05_B0029.hex.asc encontrado
10: 19: 12: 0167 Fu usando o chaveiro em / var / lib / fwupd / gnupg
10: 19: 12: 0170 Fu Adicionando chave pĆŗblica / etc / pki / fwupd / GPG-KEY-Hughski-Limited
10: 19: 12: 0175 Chave importando Fu 7E5439F64986F7A9E973809BAD8A528FEC44881E [0] Sucesso
10: 19: 12: 0175 Fu Adicionando chave pĆŗblica / etc / pki / fwupd / GPG-KEY-Linux-Vendor-Firmware-Service
10: 19: 12: 0183 Fu importando a chave 3FC6B804410ED0840D8F2F9748A6D80E4538BAC2 [0] Sucesso
10: 19: 12: 0201 Fu retornou a impressĆ£o digital de assinatura 3FC6B804410ED0840D8F2F9748A6D80E4538BAC2
10: 19: 12: 0201 Fu marcando a carga Ćŗtil como confiĆ”vel
10: 19: 12: 0203 Requisito de Fu 0.8.2 ge 0.9.5 em org.freedesktop.fwupd aprovado
10: 19: 12: 0203 Fu nenhum requisito no firmware {(nulo)}
10: 19: 12: 0203 Requisito de Fu BOT03.0 [0-1] _ * regex BOT03.01_B0008 no bootloader aprovado
10: 19: 12: 0203 Fu nenhum requisito no firmware {id do fornecedor}
10: 19: 12: 0203 Fu realizando update_prepare () na parte superior
10: 19: 12: 0203 Fu FuPending: tentando abrir o banco de dados '/var/lib/fwupd/pending.db'
10: 19: 12: 0203 Fu FuPendente: obter res
10: 19: 12: 0204 Unificando fazendo desanexar em inatividade
10: 19: 12: 0204 Destacamento unificador
10: 19: 12: 0204 Dispositivo de separaĆ§Ć£o unificador
10: 19: 12: 0204 Unificando [HID] host-> dispositivo: 10 ff 80 f0 49 43 50
10: 19: 12: 0210 Dispositivo de unificaĆ§Ć£o /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1 removido
10: 19: 12: 0234 Dispositivo de unificaĆ§Ć£o /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.2/0003:046D:C52B.002C/0003:046D:101B. 002D / hidraw / hidraw1 removido
10: 19: 12: 0290 Dispositivo de unificaĆ§Ć£o /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.2/0003:046D:C52B.002C/0003:046D:2011.002E / hidraw / hidraw2 removido
[6.293625] [00005433] libusb: debug [linux_get_device_address] obtendo endereƧo para o dispositivo: 2-1 desanexado: 1
[6.293644] [00005433] libusb: evento de hotplug de depuraĆ§Ć£o [udev_hotplug_event]. aĆ§Ć£o: remover.
[6.293664] [00005434] libusb: debug [handle_events] poll () retornou 1
[6.293676] [00005434] libusb: debug [handle_events] pegou um peixe no tubo de evento
[6.293679] [00005434] libusb: mensagem de hotplug de depuraĆ§Ć£o [handle_events] recebida
[6.293702] [00005434] libusb: debug [handle_events] poll () 2 fds com tempo limite em 0 ms
[6.293707] [00005434] libusb: debug [handle_events] poll () retornou 0
[6.293711] [00005434] libusb: debug [libusb_handle_events_timeout_completed] fazendo nosso prĆ³prio tratamento de eventos
[6.293713] [00005434] libusb: debug [handle_events] poll () 2 fds com tempo limite em 60000ms
10: 19: 12: 0292 EmissĆ£o de Fu removida do usb: usb: 00: 01
10: 19: 12: 0292 Dispositivo Fu usb: 00: 01 nĆ£o foi encontrado
[7.644288] [00005433] libusb: depurar [linux_get_device_address] obtendo endereƧo para o dispositivo: 2-1 desanexado: 0
[7.644306] [00005433] libusb: depuraĆ§Ć£o [linux_get_device_address] digitalizaĆ§Ć£o 2-1
[7.644356] [00005433] libusb: depurar [linux_get_device_address] bus = 2 dev = 19
[7.644361] [00005433] libusb: evento de hotplug de depuraĆ§Ć£o [udev_hotplug_event]. aĆ§Ć£o: adicionar.
[7.644364] [00005433] libusb: depurar [linux_enumerate_device] busnum 2 devaddr 19 session_id 531
[7.644377] [00005433] libusb: depurar [linux_enumerate_device] alocando novo dispositivo para 19/02 (sessĆ£o 531)
[7.644407] [00005433] libusb: debug [linux_get_parent_info] Dev 0x7f30b8001810 (2-1) tem pai 0x559ff80c1200 (usb2) porta 1
[7.644431] [00005434] libusb: debug [handle_events] poll () retornou 1
[7.644436] [00005434] libusb: debug [handle_events] pegou um peixe no tubo de evento
[7.644438] [00005434] libusb: mensagem de hotplug de depuraĆ§Ć£o [handle_events] recebida
[7.644467] [00005434] libusb: depurar [libusb_get_device_descriptor]
[7.644475] [00005434] libusb: depurar [libusb_get_device_descriptor]
[7.644490] [00005434] libusb: debug [handle_events] poll () 2 fds com tempo limite em 0 ms
[7.644494] [00005434] libusb: debug [lidar com eventos] poll () retornou 0
[7.644498] [00005434] libusb: debug [libusb_handle_events_timeout_completed] fazendo nosso prĆ³prio tratamento de eventos
[7.644501] [00005434] libusb: debug [handle_events] poll () 2 fds com tempo limite em 60000ms
10: 19: 13: 0642 UnificaĆ§Ć£o USB adicionar usb: 00: 01
10: 19: 13: 0645 Dispositivo de unificaĆ§Ć£o /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1 adicionado
10: 19: 13: 0645 Unificando esperando o dispositivo se estabelecer ...
10: 19: 14: 0645 Dispositivo unificador de abertura unificador usando USB
[8.647713] [00005431] libusb: depurar [libusb_open] abrir 2.19
[8.647786] [00005431] libusb: depurar [usbi_add_pollfd] adicionar eventos fd 22 4
[8.647841] [00005434] libusb: debug [handle_events] poll () retornou 1
[8.647857] [00005434] libusb: debug [handle_events] pegou um peixe no tubo de evento
[8.647901] [00005434] libusb: debug [handle_events] alguĆ©m atualizou o fds de votaĆ§Ć£o
[8.647919] [00005434] libusb: debug [libusb_handle_events_timeout_completed] fazendo nosso prĆ³prio tratamento de eventos
[8.647927] [00005434] libusb: debug [handle_events] poll fds modificado, realocando
[8.647940] [00005434] libusb: debug [handle_events] poll () 3 fds com tempo limite em 60000ms
10: 19: 14: 0646 Interface de reivindicaĆ§Ć£o de unificaĆ§Ć£o 0x00
[8.648022] [00005431] libusb: depurar interface [libusb_detach_kernel_driver] 0
[8.648646] [00005431] libusb: depurar interface [libusb_claim_interface] 0
10: 19: 14: 0647 Host-> dispositivo de unificaĆ§Ć£o: 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[8.648834] [00005431] libusb: depuraĆ§Ć£o [libusb_alloc_transfer] transferĆŖncia 0x559ff81cb5b0
[8.648868] [00005431] libusb: depuraĆ§Ć£o [libusb_submit_transfer] transferĆŖncia 0x559ff81cb5b0
[8.648884] [00005431] libusb: depurar [add_to_flying_list] armar timerfd para tempo limite em 2500ms (primeiro da linha)
10: 19: 14: 0647 Unificando UDEV add / dev / hidraw3 = /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/0003:046D:AAAC.002F/ hidraw / hidraw3
[8.649250] [00005434] libusb: debug [handle_events] poll () retornou 1
[8.649289] [00005434] libusb: depurar [reap_for_handle] tipo de urb = 2 status = 0 transferido = 32
[8.649311] [00005434] libusb: depuraĆ§Ć£o [handle_control_completion] manipulaĆ§Ć£o de status de conclusĆ£o 0
[8.649323] [00005434] libusb: depurar [disarm_timerfd]
[8.649336] [00005434] libusb: depuraĆ§Ć£o [usbi_handle_transfer_completion] transferĆŖncia 0x559ff81cb5b0 tem retorno de chamada 0x7f30de1d2b60
10: 19: 14: 0647 Unificando [8.649369] [00005434] libusb: debug [libusb_handle_events_timeout_completed] fazendo nosso prĆ³prio tratamento de eventos
sem HID_ID, pulando
[8.649380] [00005434] libusb: debug [handle_events] poll () 3 fds com tempo limite em 60000ms
10: 19: 14: 0647 Dispositivo de unificaĆ§Ć£o, nĆ£o sondagem, como reconfiguraĆ§Ć£o em processo
[8.649677] [00005431] libusb: depuraĆ§Ć£o [libusb_free_transfer] transferĆŖncia 0x559ff81cb5b0
[8.649710] [00005431] libusb: depuraĆ§Ć£o [libusb_alloc_transfer] transferĆŖncia 0x559ff81cb5b0
[8.649733] [00005431] libusb: depuraĆ§Ć£o [libusb_submit_transfer] transferĆŖncia 0x559ff81cb5b0
[8.649743] [00005431] libusb: depurar [add_to_flying_list] armar timerfd para tempo limite em 2500ms (primeiro da linha)
[8.649758] [00005431] libusb: debug [submit_bulk_transfer] precisa de 1 urbs para nova transferĆŖncia com comprimento de 32
[8.650946] [00005434] libusb: debug [lidar com eventos] poll () retornou 1
[8.650980] [00005434] libusb: depurar [reap_for_handle] tipo de urb = 1 status = 0 transferido = 32
[8.650990] [00005434] libusb: depuraĆ§Ć£o [handle_bulk_completion] status de conclusĆ£o de tratamento 0 de bulk urb 1/1
[8.651000] [00005434] libusb: depurar [handle_bulk_completion] Ćŗltimo URB na transferĆŖncia -> concluĆ­do!
[8.651010] [00005434] libusb: depurar [disarm_timerfd]
[8.651021] [00005434] libusb: depuraĆ§Ć£o [usbi_handle_transfer_completion] transferĆŖncia 0x559ff81cb5b0 tem retorno de chamada 0x7f30de1d2ae0
[8.651055] [00005434] libusb: debug [libusb_handle_events_timeout_completed] fazendo nosso prĆ³prio tratamento de eventos
[8.651065] [00005434] libusb: debug [handle_events] poll () 3 fds com tempo limite em 60000ms
[8.651147] [00005431] libusb: depuraĆ§Ć£o [libusb_free_transfer] transferĆŖncia 0x559ff81cb5b0
10: 19: 14: 0649 Dispositivo de unificaĆ§Ć£o -> host: 80 00 00 06 04 00 6b ff 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
10: 19: 14: 0649 Unificando host-> dispositivo: 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[8.651408] [00005431] libusb: depuraĆ§Ć£o [libusb_alloc_transfer] transferĆŖncia 0x559ff81cdf90
[8.651433] [00005431] libusb: depuraĆ§Ć£o [libusb_submit_transfer] transferĆŖncia 0x559ff81cdf90
[8.651447] [00005431] libusb: debug [add_to_flying_list] armar timerfd para tempo limite em 2500 ms (primeiro da linha)
[8.651797] [00005434] libusb: debug [handle_events] poll () retornou 1
[8.651828] [00005434] libusb: depurar [reap_for_handle] tipo de urb = 2 status = 0 transferido = 32
[8.651847] [00005434] libusb: depuraĆ§Ć£o [handle_control_completion] tratamento de status de conclusĆ£o 0
[8.651857] [00005434] libusb: depurar [disarm_timerfd]
[8.651868] [00005434] libusb: depuraĆ§Ć£o [usbi_handle_transfer_completion] transferĆŖncia 0x559ff81cdf90 tem retorno de chamada 0x7f30de1d2b60
[8.651905] [00005434] libusb: debug [libusb_handle_events_timeout_completed] fazendo nosso prĆ³prio tratamento de eventos
[8.651921] [00005434] libusb: debug [handle_events] poll () 3 fds com tempo limite em 60000ms
[8.651945] [00005431] libusb: depuraĆ§Ć£o [libusb_free_transfer] transferĆŖncia 0x559ff81cdf90
[8.651979] [00005431] libusb: depuraĆ§Ć£o [libusb_alloc_transfer] transferĆŖncia 0x559ff81cdf90
[8.652001] [00005431] libusb: depuraĆ§Ć£o [libusb_submit_transfer] transferĆŖncia 0x559ff81cdf90
[8.652013] [00005431] libusb: depurar [add_to_flying_list] armar timerfd para tempo limite em 2500 ms (primeiro da linha)
[8.652028] [00005431] libusb: debug [submit_bulk_transfer] precisa de 1 urbs para nova transferĆŖncia com comprimento de 32
[8.652940] [00005434] libusb: debug [handle_events] poll () retornou 1
[8.652974] [00005434] libusb: depurar [reap_for_handle] tipo de urb = 1 status = 0 transferido = 32
[8.652984] [00005434] libusb: depuraĆ§Ć£o [handle_bulk_completion] tratamento de status de conclusĆ£o 0 de bulk urb 1/1
[8.652994] [00005434] libusb: depurar [handle_bulk_completion] Ćŗltimo URB na transferĆŖncia -> concluĆ­do!
[8.653002] [00005434] libusb: depurar [disarm_timerfd]
[8.653013] [00005434] libusb: depuraĆ§Ć£o [usbi_handle_transfer_completion] transferĆŖncia 0x559ff81cdf90 tem retorno de chamada 0x7f30de1d2ae0
[8.653048] [00005434] libusb: debug [libusb_handle_events_timeout_completed] fazendo nosso prĆ³prio tratamento de eventos
[8.653058] [00005434] libusb: debug [handle_events] poll () 3 fds com tempo limite em 60000ms
[8.653101] [00005431] libusb: depuraĆ§Ć£o [libusb_free_transfer] transferĆŖncia 0x559ff81cdf90
10: 19: 14: 0651 Dispositivo de unificaĆ§Ć£o-> host: 90 00 00 0e 42 4f 54 30 33 2e 30 31 5f 42 30 30 30 38 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
10: 19: 14: 0651 Tipo de unificaĆ§Ć£o: bootloader-texas
sinalizadores: pode-flash, ativo, estĆ”-aberto, requer-anexar
versĆ£o hidpp: 0,00
hidpp-id: 0xff
dispositivo usb: 0x559ff817b0a0
id da plataforma: /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1
vendedor: Logitech
produto: Unificando [bootloader-texas]
version-bootloader: BOT03.01_B0008
versĆ£o-firmware: RQR24.xx_Bxxxx
guid: USB \ VID_046D & PID_AAAC
flash-addr-high: 0x6bff
flash-addr-low: 0x0400
tamanho do bloco flash: 0x0080

10: 19: 14: 0651 Unificando /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1 estĆ” em replug, encerrando o loop
[8.653410] [00005431] libusb: depurar [libusb_close]
[8.653431] [00005434] libusb: debug [handle_events] poll () retornou 1
[8.653442] [00005434] libusb: debug [handle_events] pegou um peixe no tubo de evento
[8.653448] [00005434] libusb: depurar [lidar com eventos] alguƩm estƔ fechando um dispositivo
[8.653459] [00005434] libusb: debug [libusb_try_lock_events] outra pessoa estĆ” fechando um dispositivo
[8.653465] [00005434] libusb: debug [libusb_event_handler_active] outra pessoa estĆ” fechando um dispositivo
[8.653473] [00005434] libusb: debug [libusb_handle_events_timeout_completed] outro thread estĆ” fazendo tratamento de eventos
[8.653483] [00005431] libusb: depurar [usbi_remove_pollfd] remover fd 22
[8.653518] [00005434] libusb: debug [libusb_handle_events_timeout_completed] fazendo nosso prĆ³prio tratamento de eventos
[8.653526] [00005434] libusb: debug [handle_events] poll fds modificado, realocando
[8.653533] [00005434] libusb: debug [handle_events] poll () 2 fds com tempo limite em 60000ms
10: 19: 14: 0651 O dispositivo Dfu nĆ£o era compatĆ­vel com DFU
10: 19: 14: 0651 Ao executar FuPluginEbitdo: adicionado {046d: aaac}
10: 19: 14: 0651 Conforme executado FuPluginUsb: adicionado {046d: aaac}
[8.653670] [00005431] libusb: depurar [libusb_open] abrir 2.19
[8.653697] [00005431] libusb: depurar [usbi_add_pollfd] adicionar eventos fd 22 4
[8.653713] [00005434] libusb: debug [handle_events] poll () retornou 1
[8.653723] [00005434] libusb: debug [handle_events] pegou um peixe no tubo de evento
10: 19: 14: 0652 [8.653729] [00005434] libusb: debug [handle_events] alguĆ©m atualizou o fds de votaĆ§Ć£o
Como [8.653740] [00005434] libusb: debug [libusb_handle_events_timeout_completed] fazendo nosso prĆ³prio tratamento de eventos
execute FuPluginUsb: get-string-desc
[8.653746] [00005434] libusb: debug [handle_events] poll fds modificado, realocando
[8.653754] [00005431] libusb: depuraĆ§Ć£o [libusb_alloc_transfer] transferĆŖncia 0x559ff81cdd10
[8.653764] [00005431] libusb: depuraĆ§Ć£o [libusb_submit_transfer] transferĆŖncia 0x559ff81cdd10
[8.653770] [00005431] libusb: depurar [add_to_flying_list] armar timerfd para tempo limite em 1000 ms (primeiro da linha)
[8.653756] [00005434] libusb: debug [handle_events] poll () 3 fds com tempo limite em 60000ms
[8.653792] [00005431] libusb: debug [libusb_handle_events_timeout_completed] outro encadeamento estĆ” fazendo tratamento de eventos
[8.653999] [00005434] libusb: debug [lidar com eventos] poll () retornou 1
[8.654012] [00005434] libusb: depurar [reap_for_handle] tipo de urb = 2 status = 0 transferido = 4
[8.654018] [00005434] libusb: depuraĆ§Ć£o [handle_control_completion] tratamento de status de conclusĆ£o 0
[8.654024] [00005434] libusb: depurar [disarm_timerfd]
[8.654031] [00005434] libusb: depuraĆ§Ć£o [usbi_handle_transfer_completion] transferĆŖncia 0x559ff81cdd10 tem retorno de chamada 0x7f30daf05c80
[8.654036] [00005434] libusb: depurar [sync_transfer_cb] comprimento_real = 4
[8.654047] [00005434] libusb: debug [libusb_handle_events_timeout_completed] fazendo nosso prĆ³prio tratamento de eventos
[8.654051] [00005431] libusb: depuraĆ§Ć£o [libusb_free_transfer] transferĆŖncia 0x559ff81cdd10
[8.654063] [00005431] libusb: depuraĆ§Ć£o [libusb_alloc_transfer] transferĆŖncia 0x559ff81cdd10
[8.654069] [00005431] libusb: depuraĆ§Ć£o [libusb_submit_transfer] transferĆŖncia 0x559ff81cdd10
[8.654073] [00005431] libusb: depurar [add_to_flying_list] armar timerfd para tempo limite em 1000 ms (primeiro da linha)
[8.654053] [00005434] libusb: debug [handle_events] poll () 3 fds com tempo limite em 60000ms
[8.654093] [00005431] libusb: debug [libusb_handle_events_timeout_completed] outro thread estĆ” fazendo tratamento de eventos
[8.654395] [00005434] libusb: debug [handle_events] poll () retornou 1
[8.654409] [00005434] libusb: depurar [reap_for_handle] tipo de urb = 2 status = 0 transferido = 30
[8.654414] [00005434] libusb: depuraĆ§Ć£o [handle_control_completion] tratamento de status de conclusĆ£o 0
[8.654418] [00005434] libusb: depurar [disarm_timerfd]
[8.654422] [00005434] libusb: depuraĆ§Ć£o [usbi_handle_transfer_completion] transferĆŖncia 0x559ff81cdd10 tem retorno de chamada 0x7f30daf05c80
[8.654429] [00005434] libusb: depurar [sync_transfer_cb] comprimento_real = 30
[8.654439] [00005434] libusb: debug [libusb_handle_events_timeout_completed] fazendo nosso prĆ³prio tratamento de eventos
[8.654445] [00005434] libusb: debug [handle_events] poll () 3 fds com tempo limite em 60000ms
[8.654443] [00005431] libusb: depuraĆ§Ć£o [libusb_free_transfer] transferĆŖncia 0x559ff81cdd10
10: 19: 14: 0652 Fu usando cc4cbfa9-bf9d-540b-b92b-172ce31013c1 para USB \ VID_046D & PID_AAAC
10: 19: 14: 0652 Fu usando de81631f-2117-51f8-bcb1-4f874a293b29 para USB \ VID_046D & PID_AAAC & REV_0301
[8.654633] [00005431] libusb: depurar [libusb_close]
[8.654645] [00005434] libusb: debug [handle_events] poll () retornou 1
[8.654648] [00005434] libusb: debug [handle_events] pegou um peixe no tubo de evento
[8.654657] [00005434] libusb: depurar [lidar com eventos] alguƩm estƔ fechando um dispositivo
[8.654661] [00005434] libusb: debug [libusb_try_lock_events] outra pessoa estĆ” fechando um dispositivo
[8.654664] [00005434] libusb: debug [libusb_event_handler_active] alguƩm estƔ fechando um dispositivo
[8.654667] [00005434] libusb: debug [libusb_handle_events_timeout_completed] outro encadeamento estĆ” fazendo tratamento de eventos
[8.654673] [00005431] libusb: depurar [usbi_remove_pollfd] remover fd 22
[8.654686] [00005434] libusb: debug [libusb_handle_events_timeout_completed] fazendo nosso prĆ³prio tratamento de eventos
[8.654689] [00005434] libusb: debug [handle_events] poll fds modificado, realocando
[8.654694] [00005434] libusb: debug [handle_events] poll () 2 fds com tempo limite em 60000ms
10: 19: 14: 0653 Fu esperando um pouco por outros plug-ins
10: 19: 14: 0653 Conforme executado FuPluginAltos: adicionado {046d: aaac}
10: 19: 14: 0653 Fu Emitting PropertyChanged ('Status' = 'device-write')
10: 19: 14: 0653 Fu Emitting PropertyChanged ('Status' = 'device-write')
10: 19: 14: 0655 Host-> dispositivo unificador: d0 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
10: 19: 15: 0154 EmissĆ£o de Fu adicionada de usb: usb: 00 : 01
10: 19: 15: 0154 Fu nenhum requisito no id {org.freedesktop.fwupd}
10: 19: 15: 0154 Fu nenhum requisito no firmware {(nulo)}
10: 19: 15: 0154 Fu nenhum parĆ¢metro fornecido para firmware {bootloader}
10: 19: 15: 0154 Fu nenhum requisito no firmware {id do fornecedor}
10: 19: 15: 0154 Fu ignorando usb: 00 : 01 [USB BootLoader] como nĆ£o atualizĆ”vel ao vivo ou offline
10: 19: 18: 0055 Fu chamou GetUpdates ()
10: 19: 18: 0055 Fu nenhum requisito no id {org.freedesktop.fwupd}
10: 19: 18: 0055 Fu nenhum requisito no firmware {(nulo)}
10: 19: 18: 0055 Fu nenhum requisito no firmware {bootloader}
10: 19: 18: 0055 Fu nenhum requisito no firmware {id do fornecedor}
10: 19: 18: 0056 Fu nenhum requisito no id {org.freedesktop.fwupd}
10: 19: 18: 0056 Fu nenhum requisito no firmware {(nulo)}
10: 19: 18: 0056 Fu nenhum parĆ¢metro fornecido para firmware {bootloader}
10: 19: 18: 0056 Fu nenhum requisito no firmware {id do fornecedor}
10: 19: 18: 0056 Fu ignorando usb: 00 : 01 [USB BootLoader] como nĆ£o atualizĆ”vel ao vivo ou offline
10: 19: 18: 0169 Fu chamou GetUpdates ()
10: 19: 18: 0169 Fu nenhum requisito no id {org.freedesktop.fwupd}
10: 19: 18: 0169 Fu nenhum requisito no firmware {(nulo)}
10: 19: 18: 0169 Fu nenhum requisito no firmware {bootloader}
10: 19: 18: 0169 Fu nenhum requisito no firmware {id do fornecedor}
10: 19: 18: 0169 Fu nenhum requisito no id {org.freedesktop.fwupd}
10: 19: 18: 0169 Fu nenhum requisito no firmware {(nulo)}
10: 19: 18: 0169 Fu nenhum parĆ¢metro fornecido para firmware {bootloader}
10: 19: 18: 0169 Fu nenhum requisito no firmware {id do fornecedor}
10: 19: 18: 0169 Fu ignorando usb: 00 : 01 [USB BootLoader] como nĆ£o atualizĆ”vel ao vivo ou offline

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (33) hkskoglund em 27 jul. 2017

@hkskoglund vocĆŖ compilou fwupd form master com a nova libgusb?

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (34) hughsie em 27 jul. 2017

NĆ£o, acabei de tentar a correĆ§Ć£o libgusb com o fwupd 0.9.5.1.fc26 mais recente. Vou apenas esperar pelo prĆ³ximo lanƧamento do fwupd antes de fazer mais testes.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (35) hkskoglund em 27 jul. 2017

OK, consegui construir o master do fwupd e funcionou!

[ henning @ satellite ~] $ sudo fwupdmgr atualizaĆ§Ć£o
Baixando RQR24.05_B0029 para Unificando Receptor ...
Atualizando RQR24.05_B0029 no receptor de unificaĆ§Ć£o ...
Descomprimindoā€¦
Reiniciando o dispositivoā€¦ [ * * * * * * * * * * * * ]

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (36) hkskoglund em 27 jul. 2017

Oi,

Sinto muito, mas instalei a versĆ£o mais recente de libgusb e fwupdmgr do Fedora updates-testing e ainda tenho o problema. Talvez eu tenha perdido algo, mas parece que estou usando as versƵes corretas:

libgusb-0.2.11.1.fc26
fwupd-0.9.5.1.fc26

Obrigado pela ajuda.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (37) thibautd em 2 ago. 2017

parece que estou usando as versƵes corretas
fwupd-0.9.5.1.fc26

Este precisa ser o 0.9.6 nĆ£o lanƧado ...

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (38) hughsie em 2 ago. 2017

Nova compilaĆ§Ć£o em https://bodhi.fedoraproject.org/updates/FEDORA-2017-148837efa0 - carma apreciado.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (39) hughsie em 3 ago. 2017

šŸ‘3

OlĆ”, a nova compilaĆ§Ć£o 0.9.6-1 fez o trabalho como um encanto no meu Fedora 26 WorkStation x86_64.

Bom trabalho ! Valeu

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (40) ZeSmoke em 3 ago. 2017

Tentei deixar este comentĆ”rio no Bodhi, mas nĆ£o consegui:

ApĆ³s essa atualizaĆ§Ć£o, o serviƧo fwupd nĆ£o inicia quando um joystick Logitech Extreme 3D Pro Ć© conectado. O dispositivo em questĆ£o Ć©:
Dispositivo 022 do barramento 003: ID 046d: c215 Logitech, Inc. Extreme 3D Pro

Com 0.9.5 o daemon inicia, mas ocasionalmente imprime a seguinte mensagem
fwupd [7002]: relatĆ³rio 0x02 comprimento desconhecido

Com a nova versĆ£o 0.9.6, o daemon inicia corretamente quando o joystick nĆ£o estĆ” conectado, mas imprime a saĆ­da abaixo quando estĆ” (as Ćŗltimas linhas se repetem para sempre).

No entanto, a nova versĆ£o atualiza com sucesso um receptor Logitech Unifying, que 0.9.5 nĆ£o (contanto que eu desconecte o joystick)

$ sudo / usr / libexec / fwupd / fwupd --verbose
21: 25: 17: 0638 DepuraĆ§Ć£o detalhada Fu ativada (no console 1)
21: 25: 17: 0639 Fu carregando valores de configuraĆ§Ć£o de /etc/fwupd.conf
21: 25: 17: 0639 Fu usando o caminho de configuraĆ§Ć£o de / etc / fwupd
21: 25: 17: 0639 Fu carregando de /etc/fwupd/remotes.d/fwupd.conf
21: 25: 17: 0639 Fu carregando de /etc/fwupd/remotes.d/lvfs-testing.conf
21: 25: 17: 0640 Fu carregando de /etc/fwupd/remotes.d/lvfs.conf
21: 25: 17: 0640 Fu carregando de /etc/fwupd/remotes.d/vendor.conf
21: 25: 17: 0640 Fu ordenando lvfs-testing = lvfs + 1
21: 25: 17: 0640 Fu ordenando lvfs = fwupd + 1
21: 25: 17: 0640 Fu ordenando lvfs-testing = lvfs + 1
21: 25: 17: 0640 Teste de lvfs remoto Fu nĆ£o habilitado, portanto, pulando
21: 25: 17: 0640 Ao executar
21: 25: 17: 0642 Conforme executado AsStore: store-from-root
21: 25: 17: 0642 Como usando o caminho do Ć­cone /var/lib/fwupd/remotes.d/lvfs/icons
21: 25: 17: 0642 Conforme executado AsStore: match-addons
21: 25: 17: 0642 As Emitting :: changed () [from-root]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Ao executar AsStore: store-from-file {/usr/share/fwupd/remotes.d/fwupd/metadata.xml}
21: 25: 17: 0643 Conforme executado AsStore: store-from-root
21: 25: 17: 0643 Como usar o caminho do Ć­cone /usr/share/fwupd/remotes.d/fwupd/icons
21: 25: 17: 0643 Conforme executado AsStore: match-addons
21: 25: 17: 0643 As Emitting :: changed () [from-root]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Como Emitting :: changed () [add-app]
21: 25: 17: 0643 Fornecedor remoto Fu nĆ£o habilitado, portanto, pulando
21: 25: 17: 0643 Dispositivos Fu agora na loja:
21: 25: 17: 0643 Fu 1 com.dell.uefi5b7ab884.firmware AtualizaĆ§Ć£o do sistema Precision E7X10
21: 25: 17: 0643 Fu 2 com.8bitdo.fc30.firmware FC30
21: 25: 17: 0643 Fu 3 com.dell.uefi9cb573d5.firmware AtualizaĆ§Ć£o do sistema Latitude 3480
21: 25: 17: 0643 Fu 4 com.dell.uefi6180aaaa.firmware AtualizaĆ§Ć£o do sistema Latitude E5X60
21: 25: 17: 0643 Fu 5 com.dell.uefia5d83d78.firmware AtualizaĆ§Ć£o do sistema AIO do Precision 5720
21: 25: 17: 0643 Fu 6 com.8bitdo.fc30arcade.firmware FC30 Joystick
21: 25: 17: 0643 Fu 7 com.dell.uefi3c20b9e1.firmware AtualizaĆ§Ć£o do sistema AIO OptiPlex 7450
21: 25: 17: 0643 Fu 8 com.dell.uefi1610b70e.firmware Inspiron 14 7000 Gaming / Inspiron 15 7000 AtualizaĆ§Ć£o do sistema de jogos
21: 25: 17: 0643 AtualizaĆ§Ć£o do sistema Fu 9 com.dell.uefiaee2604a.firmware Embedded Box PC 3000
21: 25: 17: 0643 Fu 10 com.dell.uefi4fed6c9d.firmware AtualizaĆ§Ć£o do sistema OptiPlex 7050
21: 25: 17: 0643 Fu 11 com.dell.uefi169d9146.firmware Vostro 14-3468 AtualizaĆ§Ć£o do sistema
21: 25: 17: 0643 Fu 12 com.dell.uefib950d63c.firmware AtualizaĆ§Ć£o do sistema OptiPlex 7040
21: 25: 17: 0643 Fu 13 com.dell.uefi48af7d21.firmware XPS 13 9360 AtualizaĆ§Ć£o do sistema
21: 25: 17: 0643 Fu 14 com.dell.uefi8661c04a.firmware AtualizaĆ§Ć£o do sistema Latitude 3470
21: 25: 17: 0643 Fu 15 com.dell.uefif952fe9e.firmware AtualizaĆ§Ć£o do sistema Latitude 3380
21: 25: 17: 0643 Fu 16 com.8bitdo.snes30.firmware SNES30
21: 25: 17: 0643 Fu 17 com.hughski.ColorHug.firmware ColorHug
21: 25: 17: 0643 Fu 18 com.dell.uefid69fed57.firmware AtualizaĆ§Ć£o do sistema AIO OptiPlex 3050
21: 25: 17: 0643 Fu 19 com.dell.uefi10c40550.firmware AtualizaĆ§Ć£o do sistema OptiPlex 7050
21: 25: 17: 0643 Fu 20 com.dell.uefi1367a91a.firmware AtualizaĆ§Ć£o do sistema OptiPlex 5050
21: 25: 17: 0643 Fu 21 com.dell.uefi33773727.firmware XPS 13 9350 AtualizaĆ§Ć£o do sistema
21: 25: 17: 0643 Fu 22 com.dell.uefi21f94926.firmware Edge Gateway 3000/3001/3002/3003 AtualizaĆ§Ć£o do sistema
21: 25: 17: 0643 Fu 23 com.8bitdo.fc30pro.firmware FC30 Pro
21: 25: 17: 0643 Fu 24 com.8bitdo.nes30pro.firmware NES30 Pro
21: 25: 17: 0643 Fu 25 com.dell.uefi8ae34f14.firmware AtualizaĆ§Ć£o do sistema AIO OptiPlex 7450
21: 25: 17: 0643 Fu 26 com.dell.uefib566a9b1.firmware AtualizaĆ§Ć£o do sistema AIO OptiPlex 5250
21: 25: 17: 0643 Fu 27 com.dell.uefie0f614ed.firmware Edge Gateway 5000/5100 AtualizaĆ§Ć£o do sistema
21: 25: 17: 0643 Fu 28 com.dell.uefi416d1c90.firmware AtualizaĆ§Ć£o do sistema AIO OptiPlex 5250
21: 25: 17: 0643 Fu 29 com.dell.uefi124c207d.firmware XPS 15 9550 / AtualizaĆ§Ć£o do sistema Precision 5510
21: 25: 17: 0643 Fu 30 com.dell.uefi51d41d4e.firmware AtualizaĆ§Ć£o do sistema Latitude 7370
21: 25: 17: 0643 Fu 31 com.dell.uefi5034bac4.firmware AtualizaĆ§Ć£o TPM 1.2
21: 25: 17: 0643 Fu 32 com.dell.uefi22d63f4.firmware AtualizaĆ§Ć£o TPM 2.0
21: 25: 17: 0643 Fu 33 com.dell.uefi53f51f56.firmware AtualizaĆ§Ć£o do sistema Latitude 7X80
21: 25: 17: 0643 Fu 34 com.logitech.MPK01.firmware Teclado sem fio para vƔrios dispositivos Logitech K780
21: 25: 17: 0643 Fu 35 com.dell.uefi49e03513.firmware Latitude 5X80 System Update
21: 25: 17: 0643 Fu 36 com.dell.uefi212026ee.firmware AtualizaĆ§Ć£o do sistema Latitude E7X70
21: 25: 17: 0643 Fu 37 com.dell.uefi8b7b32a7.firmware AtualizaĆ§Ć£o do sistema Latitude 5X80
21: 25: 17: 0643 Fu 38 com.8bitdo.nes30.firmware NES30
21: 25: 17: 0643 Fu 39 com.dell.uefi78db8ddd.firmware AtualizaĆ§Ć£o do sistema AIO OptiPlex 3050
21: 25: 17: 0644 Fu 40 com.dell.uefi5ffdbc0d.firmware XPS 13 9360 AtualizaĆ§Ć£o do sistema
21: 25: 17: 0644 Fu 41 com.logitech.Unifying.RQR24.firmware Logitech Unifying Receiver
21: 25: 17: 0644 Fu 42 com.dell.uefid63450d6.firmware AtualizaĆ§Ć£o do sistema OptiPlex 3046
21: 25: 17: 0644 Fu 43 com.hughski.ColorHug2.firmware ColorHug2
21: 25: 17: 0644 Fu 44 com.dell.uefi293af847.firmware AtualizaĆ§Ć£o do sistema OptiPlex 3050
21: 25: 17: 0644 Fu 45 com.dell.uefi1d4362ca.firmware Inspiron 14-3467 AtualizaĆ§Ć£o do sistema
21: 25: 17: 0644 Fu 46 com.dell.uefi8080d214.firmware AtualizaĆ§Ć£o do sistema OptiPlex 5050
21: 25: 17: 0644 Fu 47 com.dell.uefi45e3439b.firmware AtualizaĆ§Ć£o do sistema ChengMing 3967
21: 25: 17: 0644 Fu 48 com.hughski.ColorHugALS.firmware ColorHugALS
21: 25: 17: 0644 Fu 49 com.dell.uefia0a3aa54.firmware Embedded Box PC 5000 AtualizaĆ§Ć£o do sistema
21: 25: 17: 0644 Fu 50 com.logitech.Unifying.RQR12.firmware Logitech Unifying Receiver
21: 25: 17: 0644 Fu 51 com.dell.uefia81a55fe.firmware AtualizaĆ§Ć£o do sistema AIO OptiPlex 3240
21: 25: 17: 0644 Fu 52 com.dell.uefi34578c72.firmware XPS 15 9560 / AtualizaĆ§Ć£o do sistema Precision 5520
21: 25: 17: 0644 Fu 53 com.8bitdo.sfc30.firmware SFC30
21: 25: 17: 0644 Fu 54 com.dell.uefi43ca3264.firmware AtualizaĆ§Ć£o do sistema AIO OptiPlex 7440
21: 25: 17: 0644 Fu 55 UEFI-dummy-dev0 AtualizaƧƵes UEFI
21: 25: 17: 0644 Fu 56 com.via.VL811.firmware Firmware VL811
21: 25: 17: 0644 Fu 57 com.via.VL811 + .firmware VL811 + Firmware
21: 25: 17: 0644 Fu 58 com.via.VL812.firmware Firmware VL812
21: 25: 17: 0644 Fu 59 com.via.VL812_B2.firmware VL812 B2 Firmware
21: 25: 17: 0647 Fu smbios property / sys / class / dmi / id / sys_vendor = Gigabyte Technology Co., Ltd.
21: 25: 17: 0647 Fu smbios property / sys / class / dmi / id / chassis_type = 3
21: 25: 17: 0647 Fu no / sys / class / dmi / id / product_family, portanto, ignorando
21: 25: 17: 0647 Fu smbios property / sys / class / dmi / id / product_name = Z97X-UD3H-BK
21: 25: 17: 0647 Fu no / sys / class / dmi / id / product_sku, portanto, ignorando
21: 25: 17: 0647 Fu smbios property / sys / class / dmi / id / bios_vendor = American Megatrends Inc.
21: 25: 17: 0647 Fu smbios property / sys / class / dmi / id / bios_version = F8
21: 25: 17: 0647 Fu no / sys / class / dmi / id / bios_major_release entĆ£o ignorando
21: 25: 17: 0647 Fu no / sys / class / dmi / id / bios_minor_release, portanto, ignorando
21: 25: 17: 0647 Fu smbios property / sys / class / dmi / id / board_vendor = Gigabyte Technology Co., Ltd.
21: 25: 17: 0647 Fu smbios property / sys / class / dmi / id / board_name = Z97X-UD3H-BK-CF
21: 25: 17: 0647 Fu HardwareID-0 nĆ£o estĆ” disponĆ­vel, nĆ£o disponĆ­vel como 'FamĆ­lia' desconhecido
21: 25: 17: 0647 Fu HardwareID-1 nĆ£o estĆ” disponĆ­vel, nĆ£o disponĆ­vel como 'FamĆ­lia' desconhecido
21: 25: 17: 0647 Fu HardwareID-2 nĆ£o estĆ” disponĆ­vel, nĆ£o disponĆ­vel como 'BiosMajorRelease' desconhecido
21: 25: 17: 0647 Fu HardwareID-3 nĆ£o estĆ” disponĆ­vel, nĆ£o disponĆ­vel como 'FamĆ­lia' desconhecido
21: 25: 17: 0647 Fu HardwareID-4 nĆ£o estĆ” disponĆ­vel, nĆ£o disponĆ­vel como 'FamĆ­lia' desconhecido
21: 25: 17: 0647 Fu HardwareID-5 nĆ£o estĆ” disponĆ­vel, nĆ£o disponĆ­vel como 'FamĆ­lia' desconhecido
21: 25: 17: 0647 Fu HardwareID-6 nĆ£o estĆ” disponĆ­vel, nĆ£o disponĆ­vel como 'ProductSku' desconhecido
21: 25: 17: 0647 Fu HardwareID-7 nĆ£o estĆ” disponĆ­vel, nĆ£o disponĆ­vel como 'ProductSku' desconhecido
21: 25: 17: 0647 Fu {bcbfb817-5da5-5fe6-b1ac-8781109aacd7} <- Gigabyte Technology Co., Ltd. & Z97X-UD3H-BK e Gigabyte Technology Co., Ltd. & Z97X-UD3H-BK-CF
21: 25: 17: 0647 Fu {e4253799-0751-5332-b849-a244c491997d} <- Gigabyte Technology Co., Ltd. & Z97X-UD3H-BK
21: 25: 17: 0647 Fu HardwareID-10 nĆ£o estĆ” disponĆ­vel, nĆ£o disponĆ­vel como 'FamĆ­lia' desconhecido
21: 25: 17: 0647 Fu HardwareID-11 nĆ£o estĆ” disponĆ­vel, nĆ£o disponĆ­vel como 'FamĆ­lia' desconhecido
21: 25: 17: 0647 Fu {76ae82f3-6e64-5e37-865e-aa31a2f10d8b} <- Gigabyte Technology Co., Ltd. & 3
21: 25: 17: 0647 Fu {da56712d-5221-526c-a5b2-78a6480f102f} <- Gigabyte Technology Co., Ltd. & Gigabyte Technology Co., Ltd. & Z97X-UD3H-BK-CF
21: 25: 17: 0647 Fu {7fbc5de5-d280-5d62-8741-11013abaeab2} <- Gigabyte Technology Co., Ltd.
21: 25: 17: 0647 Fu adicionando plugin /usr/lib64/fwupd-plugins-2/libfu_plugin_upower.so
21: 25: 17: 0647 Fu realizando init () em /usr/lib64/fwupd-plugins-2/libfu_plugin_upower.so
21: 25: 17: 0647 Fu adicionando plugin /usr/lib64/fwupd-plugins-2/libfu_plugin_steelseries.so
21: 25: 17: 0647 Fu adicionando plugin /usr/lib64/fwupd-plugins-2/libfu_plugin_amt.so
21: 25: 17: 0647 Fu adicionando plugin /usr/lib64/fwupd-plugins-2/libfu_plugin_altos.so
21: 25: 17: 0648 Fu adicionando plugin /usr/lib64/fwupd-plugins-2/libfu_plugin_dell.so
21: 25: 17: 0649 Fu realizando init () em /usr/lib64/fwupd-plugins-2/libfu_plugin_dell.so
21: 25: 17: 0666 Fu adicionando o plugin /usr/lib64/fwupd-plugins-2/libfu_plugin_synapticsmst.so
21: 25: 17: 0667 Fu adicionando o plugin /usr/lib64/fwupd-plugins-2/libfu_plugin_unifying.so
21: 25: 17: 0667 Fu realizando init () em /usr/lib64/fwupd-plugins-2/libfu_plugin_unifying.so
21: 25: 17: 0667 Fu adicionando o plugin /usr/lib64/fwupd-plugins-2/libfu_plugin_usb.so
21: 25: 17: 0667 Fu adicionando o plugin /usr/lib64/fwupd-plugins-2/libfu_plugin_uefi.so
21: 25: 17: 0667 Fu adicionando plugin /usr/lib64/fwupd-plugins-2/libfu_plugin_dfu.so
21: 25: 17: 0667 Fu realizando init () em /usr/lib64/fwupd-plugins-2/libfu_plugin_dfu.so
21: 25: 17: 0667 Fu adicionando plugin /usr/lib64/fwupd-plugins-2/libfu_plugin_test.so
21: 25: 17: 0667 Fu realizando init () em /usr/lib64/fwupd-plugins-2/libfu_plugin_test.so
21: 25: 17: 0667 Inicial de teste
21: 25: 17: 0667 Fu adicionando plugin /usr/lib64/fwupd-plugins-2/libfu_plugin_raspberrypi.so
21: 25: 17: 0668 Fu realizando init () em /usr/lib64/fwupd-plugins-2/libfu_plugin_raspberrypi.so
21: 25: 17: 0668 Fu adicionando plugin /usr/lib64/fwupd-plugins-2/libfu_plugin_colorhug.so
21: 25: 17: 0668 Fu realizando init () em /usr/lib64/fwupd-plugins-2/libfu_plugin_colorhug.so
21: 25: 17: 0668 Fu adicionando plugin /usr/lib64/fwupd-plugins-2/libfu_plugin_ebitdo.so
21: 25: 17: 0668 Fu adicionando plugin /usr/lib64/fwupd-plugins-2/libfu_plugin_udev.so
21: 25: 17: 0669 Fu realizando init () em /usr/lib64/fwupd-plugins-2/libfu_plugin_udev.so
21: 25: 17: 0669 Ao executar FuMain: setup
21: 25: 17: 0669 Conforme executado FuMain: setup {altos}
21: 25: 17: 0669 Fu realizando inicializaĆ§Ć£o () em altos
21: 25: 17: 0669 Conforme executado FuMain: setup {amt}
21: 25: 17: 0669 Fu realizando inicializaĆ§Ć£o () no amt
21: 25: 17: 0669 Fu desativando o plugin porque: falhou ao inicializar amt: ME recusou a conexĆ£o
21: 25: 17: 0669 Conforme executado FuMain: setup {colorhug}
21: 25: 17: 0669 Fu realizando inicializaĆ§Ć£o () no colorhug
21: 25: 17: 0669 Conforme executado FuMain: setup {dell}
21: 25: 17: 0669 Fu realizando inicializaĆ§Ć£o () no Dell
21: 25: 17: 0669 Fu desativando o plugin porque: falhou ao inicializar dell: atualizaĆ§Ć£o de firmware nĆ£o suportada
21: 25: 17: 0669 Ao executar FuMain: setup {dfu}
21: 25: 17: 0669 Fu realizando inicializaĆ§Ć£o () em dfu
21: 25: 17: 0669 Conforme executado FuMain: setup {ebitdo}
21: 25: 17: 0669 Fu realizando inicializaĆ§Ć£o () no ebitdo
21: 25: 17: 0669 Conforme executado FuMain: setup {raspberrypi}
21: 25: 17: 0669 Conforme executado FuMain: setup {steelseries}
21: 25: 17: 0669 Fu realizando inicializaĆ§Ć£o () na sĆ©rie de aƧo
21: 25: 17: 0669 Ao executar FuMain: setup {synapticsmst}
21: 25: 17: 0669 Fu realizando inicializaĆ§Ć£o () no synapticsmst
21: 25: 17: 0669 Ao executar FuMain: setup {test}
21: 25: 17: 0669 Fu realizando inicializaĆ§Ć£o () no teste
21: 25: 17: 0669 Fu desativando o plug-in porque: falhou no teste de inicializaĆ§Ć£o: o plug-in de teste Ć© usado apenas para integraĆ§Ć£o contĆ­nua
21: 25: 17: 0669 Conforme executado FuMain: setup {udev}
21: 25: 17: 0669 Conforme executado FuMain: setup {uefi}
21: 25: 17: 0669 Conforme executado FuMain: setup {unifying}
21: 25: 17: 0669 Fu realizando inicializaĆ§Ć£o () na unificaĆ§Ć£o
21: 25: 17: 0669 Unificando UDEV add / dev / hidraw0 = /sys/devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5:1.0/0003:046D:C215.0011/ hidraw / hidraw0
21: 25: 17: 0669 Dispositivo de unificaĆ§Ć£o /sys/devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5:1.0/0003:046D:C215.0011/hidraw/hidraw0 adicionado
21: 25: 17: 0669 Dispositivo de unificaĆ§Ć£o de abertura de unificaĆ§Ć£o usando / dev / hidraw0
21: 25: 17: 0669 Unificando [HID] host-> dispositivo: 10 fe 00 10 00 00 aa
21: 25: 17: 0675 Dispositivo de unificaĆ§Ć£o [HID] -> host: 00 f2 87 80 00 00 00
21: 25: 17: 0675 O relatĆ³rio de unificaĆ§Ć£o HID ++ 1.0 0x00 tem comprimento desconhecido, ignorando
21: 25: 17: 0683 Dispositivo de unificaĆ§Ć£o [HID] -> host: 00 f2 87 80 00 00 00
21: 25: 17: 0683 O relatĆ³rio de unificaĆ§Ć£o HID ++ 1.0 0x00 tem comprimento desconhecido, ignorando
21: 25: 17: 0691 Dispositivo de unificaĆ§Ć£o [HID] -> host: 00 f2 87 80 00 00 00
21: 25: 17: 0691 O relatĆ³rio de unificaĆ§Ć£o HID ++ 1.0 0x00 tem comprimento desconhecido, ignorando
21: 25: 17: 0699 Dispositivo de unificaĆ§Ć£o [HID] -> host: 00 f2 87 80 00 00 00
21: 25: 17: 0699 O relatĆ³rio de unificaĆ§Ć£o HID ++ 1.0 0x00 tem comprimento desconhecido, ignorando
21: 25: 17: 0707 Dispositivo de unificaĆ§Ć£o [HID] -> host: 00 f2 87 80 00 00 00
21: 25: 17: 0707 O relatĆ³rio de unificaĆ§Ć£o HID ++ 1.0 0x00 tem comprimento desconhecido, ignorando
21: 25: 17: 0715 Dispositivo de unificaĆ§Ć£o [HID] -> host: 00 f2 87 80 00 00 00
21: 25: 17: 0715 O relatĆ³rio de unificaĆ§Ć£o HID ++ 1.0 0x00 tem comprimento desconhecido, ignorando
21: 25: 17: 0723 Dispositivo de unificaĆ§Ć£o [HID] -> host: 00 f2 87 80 00 00 00
21: 25: 17: 0723 O relatĆ³rio de unificaĆ§Ć£o HID ++ 1.0 0x00 tem comprimento desconhecido, ignorando
21: 25: 17: 0731 Dispositivo de unificaĆ§Ć£o [HID] -> host: 00 f2 87 80 00 00 00
21: 25: 17: 0731 O relatĆ³rio de unificaĆ§Ć£o HID ++ 1.0 0x00 tem comprimento desconhecido, ignorando
21: 25: 17: 0739 Dispositivo de unificaĆ§Ć£o [HID] -> host: 00 f2 87 80 00 00 00
21: 25: 17: 0739 O relatĆ³rio de unificaĆ§Ć£o HID ++ 1.0 0x00 tem comprimento desconhecido, ignorando
21: 25: 17: 0747 Dispositivo de unificaĆ§Ć£o [HID] -> host: 00 f2 87 80 00 00 00
21: 25: 17: 0747 O relatĆ³rio de unificaĆ§Ć£o HID ++ 1.0 0x00 tem comprimento desconhecido, ignorando
21: 25: 17: 0755 Dispositivo de unificaĆ§Ć£o [HID] -> host: 00 f2 87 80 00 00 00
21: 25: 17: 0755 O relatĆ³rio de unificaĆ§Ć£o HID ++ 1.0 0x00 tem comprimento desconhecido, ignorando
21: 25: 17: 0763 Dispositivo de unificaĆ§Ć£o [HID] -> host: 00 f2 87 80 00 00 00
21: 25: 17: 0763 O relatĆ³rio de unificaĆ§Ć£o HID ++ 1.0 0x00 tem comprimento desconhecido, ignorando
21: 25: 17: 0771 Dispositivo de unificaĆ§Ć£o [HID] -> host: 00 f2 87 80 00 00 00
21: 25: 17: 0771 O relatĆ³rio de unificaĆ§Ć£o HID ++ 1.0 0x00 tem comprimento desconhecido, ignorando
21: 25: 17: 0779 Dispositivo de unificaĆ§Ć£o [HID] -> host: 00 f2 87 80 00 00 00
21: 25: 17: 0779 O relatĆ³rio de unificaĆ§Ć£o HID ++ 1.0 0x00 tem comprimento desconhecido, ignorando
21: 25: 17: 0787 Dispositivo de unificaĆ§Ć£o [HID] -> host: 00 f2 87 80 00 00 00
21: 25: 17: 0787 O relatĆ³rio de unificaĆ§Ć£o HID ++ 1.0 0x00 tem comprimento desconhecido, ignorando

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (41) roshanshariff em 3 ago. 2017

O joystick parece estar enviando spam para o daemon com "00 f2 87 80 00 00 00" - tentarei resolver isso no fim de semana.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (42) hughsie em 4 ago. 2017

Corrigido o problema para mim tambĆ©m, adicionado um Karma +1. Obrigado pela soluĆ§Ć£o rĆ”pida!

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (43) thibautd em 5 ago. 2017

NĆ£o sei se isso Ć© uma regressĆ£o ou apenas um erro semelhante, mas no Ubuntu 19.10 estou recebendo esse erro exato.

falha ao obter dispositivo apĆ³s desanexar: falha ao esperar por desanexar novamente: o dispositivo 3414db784a57169c10b1f4ec7253baa6a637e80d nĆ£o voltou

O dispositivo Ć© desativado ao tentar instalar a atualizaĆ§Ć£o. Tenho que desconectar e reconectar manualmente para que o meu teclado comece a trabalhar novamente.

Talvez nĆ£o relacionado, mas encontrei este post em uma pesquisa.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (44) Goddard em 7 dez. 2019

VocĆŖ precisa reconectar o receptor durante a atualizaĆ§Ć£o.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (45) FFY00 em 7 dez. 2019

JĆ” tentei, mas sempre que reconecto o aparelho ele sĆ³ dĆ” um nĆ£o suportado.

Buscando metadados https://cdn.fwupd.org/downloads/firmware-testing.xml.gz
Baixandoā€¦ [ * * * * * * * * * * * * ** ]
Buscando assinatura https://cdn.fwupd.org/downloads/firmware-testing.xml.gz.asc

Buscando metadados https://cdn.fwupd.org/downloads/firmware.xml.gz
Baixandoā€¦ [ * * * * * * * * * * * * ** ]
Buscando assinatura https://cdn.fwupd.org/downloads/firmware.xml.gz.asc

Sem atualizaƧƵes para o receptor de unificaĆ§Ć£o, atual Ć© RQR12.10_B0032: RQR12.05_B0028 = mais antigo, RQR12.10_B0032 = mesmo, RQR12.08_B0030 = mais antigo, RQR12.07_B0029 = mais antigo
Baixando RQR12.10_B0032 para Unificar Receptor ...
Descomprimindoā€¦ [ * * * * * * * * * * * * ]
Autenticandoā€¦ [ * * * * * * * * * * * ]
Atualizando receptor de unificaĆ§Ć£o ...
Inativoā€¦ [ * * * * * * * * * * * * ]
nĆ£o suportado

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (46) Goddard em 7 dez. 2019

mĆŗltiplas maneiras diferentes

Buscando metadados https://cdn.fwupd.org/downloads/firmware-testing.xml.gz
Baixandoā€¦ [ * * * * * * * * * * * * ** ]
Buscando assinatura https://cdn.fwupd.org/downloads/firmware-testing.xml.gz.asc

Buscando metadados https://cdn.fwupd.org/downloads/firmware.xml.gz
Baixandoā€¦ [ * * * * * * * * * * * * ** ]
Buscando assinatura https://cdn.fwupd.org/downloads/firmware.xml.gz.asc

ignorando o Unifying Receiver [71413822e87deae707da948bd4b7e537af463c19] como nĆ£o atualizĆ”vel

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (47) Goddard em 7 dez. 2019

Buscando metadados https://cdn.fwupd.org/downloads/firmware-testing.xml.gz
Baixandoā€¦ [ * * * * * * * * * * * * ** ]
Buscando assinatura https://cdn.fwupd.org/downloads/firmware-testing.xml.gz.asc

Buscando metadados https://cdn.fwupd.org/downloads/firmware.xml.gz
Baixandoā€¦ [ * * * * * * * * * * * * ** ]
Buscando assinatura https://cdn.fwupd.org/downloads/firmware.xml.gz.asc

Baixando RQR12.10_B0032 para Unificar Receptor ...
(fwupdmgr: 40236): FuCommon-DEBUG: 12: 05: 40.698: criando caminho /root/.cache/fwupd
(fwupdmgr: 40236): FuMain-DEBUG: 12: 05: 40.699: pular o download porque o arquivo jĆ” existe
(fwupdmgr: 40236): Fwupd-DEBUG: 12: 05: 40.699: Emitting :: status-changed () [descompactando]
Descomprimindoā€¦ - : Fwupd-DEBUG: 12: 05: 40.700: Emitting :: status-changed () [idle]
Descomprimindoā€¦ [ * * * * * * * * * * * * ]
(fwupdmgr: 40236): Fwupd-DEBUG: 12: 05: 40.733: Emitting :: status-changed () [esperando por autenticaĆ§Ć£o]
Autenticandoā€¦ - : Fwupd-DEBUG: 12: 05: 40.735: Emitting :: status-changed () [idle]
Autenticandoā€¦ [ * * * * * * * * * * * ]
Atualizando receptor de unificaĆ§Ć£o ...
Inativoā€¦ [ * * * * * * * * * * * ]
(fwupdmgr: 40236): Fwupd-DEBUG: 12: 05: 42.192: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
(fwupdmgr: 40236): Fwupd-DEBUG: 12: 05: 42.194: Emitting :: status-changed () [apagar dispositivo]
Apagandoā€¦ - : Fwupd-DEBUG: 12: 05: 42.195: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Apagandoā€¦ / : Fwupd-DEBUG: 12: 05: 43.392: Emitting :: status-changed () [device-write]
Gravandoā€¦ / : Fwupd-DEBUG: 12: 05: 43.393: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escritaā€¦ : Fwupd-DEBUG: 12: 05: 43.413: Emitting :: dispositivo alterado (71413822e87deae707da948bd4b7e537af463c19)
Escritaā€¦ : Fwupd-DEBUG: 12: 05: 43.445: Emitting :: dispositivo alterado (71413822e87deae707da948bd4b7e537af463c19)
Escritaā€¦ : Fwupd-DEBUG: 12: 05: 43.477: Emitting :: dispositivo alterado (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * : Fwupd-DEBUG: 12: 05: 43.513: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * : Fwupd-DEBUG: 12: 05: 43.545: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * : Fwupd-DEBUG: 12: 05: 43.577: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Gravandoā€¦ * : Fwupd-DEBUG: 12: 05: 43.613: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Gravandoā€¦ * : Fwupd-DEBUG: 12: 05: 43.645: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escritaā€¦ : Fwupd-DEBUG: 12: 05: 43.677: Emitting :: dispositivo alterado (71413822e87deae707da948bd4b7e537af463c19)
Escritaā€¦ : Fwupd-DEBUG: 12: 05: 43.709: Emitting :: dispositivo alterado (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * : Fwupd-DEBUG: 12: 05: 43.745: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * : Fwupd-DEBUG: 12: 05: 43.777: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * : Fwupd-DEBUG: 12: 05: 43.809: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦: Fwupd-DEBUG: 12: 05: 43.845: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦: Fwupd-DEBUG: 12: 05: 43.877: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * : Fwupd-DEBUG: 12: 05: 43.909: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦: Fwupd-DEBUG: 12: 05: 43.941: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Gravandoā€¦ * : Fwupd-DEBUG: 12: 05: 43.977: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * : Fwupd-DEBUG: 12: 05: 44.009: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * : Fwupd-DEBUG: 12: 05: 44.041: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * : Fwupd-DEBUG: 12: 05: 44.077: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Gravandoā€¦ * : Fwupd-DEBUG: 12: 05: 44.109: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * : Fwupd-DEBUG: 12: 05: 44.141: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * : Fwupd-DEBUG: 12: 05: 44.173: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Gravandoā€¦ * : Fwupd-DEBUG: 12: 05: 44.209: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * : Fwupd-DEBUG: 12: 05: 44.241: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Gravandoā€¦ * * : Fwupd-DEBUG: 12: 05: 44.273: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * : Fwupd-DEBUG: 12: 05: 44.309: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Gravandoā€¦ * * : Fwupd-DEBUG: 12: 05: 44.341: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * : Fwupd-DEBUG: 12: 05: 44.373: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * : Fwupd-DEBUG: 12: 05: 44.405: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * : Fwupd-DEBUG: 12: 05: 44.441: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * : Fwupd-DEBUG: 12: 05: 44.473: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * : Fwupd-DEBUG: 12: 05: 44.505: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * : Fwupd-DEBUG: 12: 05: 44.541: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * : Fwupd-DEBUG: 12: 05: 44.573: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * : Fwupd-DEBUG: 12: 05: 44.605: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * : Fwupd-DEBUG: 12: 05: 44.641: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * : Fwupd-DEBUG: 12: 05: 44.673: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * : Fwupd-DEBUG: 12: 05: 44.705: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * : Fwupd-DEBUG: 12: 05: 44.737: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * : Fwupd-DEBUG: 12: 05: 44.773: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * : Fwupd-DEBUG: 12: 05: 44.805: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * : Fwupd-DEBUG: 12: 05: 44.837: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * : Fwupd-DEBUG: 12: 05: 44.873: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * : Fwupd-DEBUG: 12: 05: 44.905: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * : Fwupd-DEBUG: 12: 05: 44.937: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * : Fwupd-DEBUG: 12: 05: 44.969: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * : Fwupd-DEBUG: 12: 05: 45.005: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Gravandoā€¦ * * * * * : Fwupd-DEBUG: 12: 05: 45.037: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Gravandoā€¦ * * * * * : Fwupd-DEBUG: 12: 05: 45.069: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Gravandoā€¦ * * * * * : Fwupd-DEBUG: 12: 05: 45.105: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Gravandoā€¦ * * * * * : Fwupd-DEBUG: 12: 05: 45.138: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Gravandoā€¦ * * * * * : Fwupd-DEBUG: 12: 05: 45.170: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Gravandoā€¦ * * * * * : Fwupd-DEBUG: 12: 05: 45.202: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Gravandoā€¦ * * * * * : Fwupd-DEBUG: 12: 05: 45.238: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Gravandoā€¦ * * * * * * : Fwupd-DEBUG: 12: 05: 45.270: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * : Fwupd-DEBUG: 12: 05: 45.302: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * : Fwupd-DEBUG: 12: 05: 45.338: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Gravandoā€¦ * * * * * * : Fwupd-DEBUG: 12: 05: 45.370: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * : Fwupd-DEBUG: 12: 05: 45.402: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * : Fwupd-DEBUG: 12: 05: 45.434: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Gravandoā€¦ * * * * * * : Fwupd-DEBUG: 12: 05: 45.470: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * : Fwupd-DEBUG: 12: 05: 45.502: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * : Fwupd-DEBUG: 12: 05: 45.534: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * : Fwupd-DEBUG: 12: 05: 45.570: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * : Fwupd-DEBUG: 12: 05: 45.602: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Gravandoā€¦ * * * * * * * : Fwupd-DEBUG: 12: 05: 45.634: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * : Fwupd-DEBUG: 12: 05: 45.670: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * : Fwupd-DEBUG: 12: 05: 45.702: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * : Fwupd-DEBUG: 12: 05: 45.734: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * : Fwupd-DEBUG: 12: 05: 45.766: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * : Fwupd-DEBUG: 12: 05: 45.802: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * : Fwupd-DEBUG: 12: 05: 45.834: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * : Fwupd-DEBUG: 12: 05: 45.866: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * : Fwupd-DEBUG: 12: 05: 45.902: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * : Fwupd-DEBUG: 12: 05: 45.934: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * : Fwupd-DEBUG: 12: 05: 45.966: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * : Fwupd-DEBUG: 12: 05: 45.998: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.034: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.066: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.098: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.134: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.166: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.198: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.230: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.266: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.298: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.330: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.366: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.398: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.430: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.462: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.498: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.530: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.562: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.599: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.631: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * * * * : Fwupd-DEBUG: 12: 05: 46.663: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Escrevendoā€¦ * * * * * * * * * * * * : Fwupd-DEBUG: 12: 05: 47.071: Emitting :: device-changed (71413822e87deae707da948bd4b7e537af463c19)
Atualizando receptor de unificaĆ§Ć£o ...
Gravandoā€¦ * * * * * * * * * * * * : Fwupd-DEBUG: 12: 05: 49.402: Emitting :: device-changed (3414db784a57169c10b1f4ec7253baa6a637e80d)
(fwupdmgr: 40236): Fwupd-DEBUG: 12: 05: 49.402: Emitting :: status-changed () [idle]
Escrevendoā€¦ [ * * * * * * * * * * * * * ]
(fwupdmgr: 40236): Fwupd-DEBUG: 12: 05: 49.403: Emitindo :: alterado ()
Sem atualizaƧƵes para o receptor de unificaĆ§Ć£o, atual Ć© RQR12.10_B0032: RQR12.05_B0028 = mais antigo, RQR12.10_B0032 = mesmo, RQR12.08_B0030 = mais antigo, RQR12.07_B0029 = mais antigo

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (48) Goddard em 7 dez. 2019

VocĆŖ pode executar o daemon no modo detalhado e fornecer a saĆ­da do daemon durante esta tentativa?

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (49) superm1 em 7 dez. 2019

Eu ficaria feliz. Como? AlƩm disso

atualizaĆ§Ć£o de sudo fwupdmgr && atualizaĆ§Ć£o de sudo fwupdmgr -vvv

NĆ£o tenho ideia de como fazer mais nada com o seu software.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (50) Goddard em 7 dez. 2019

@Goddard Como mentioend em https://github.com/fwupd/fwupd/wiki/Getting-involved, vocĆŖ pode usar:

# fwupdmgr modify-config VerboseDomains '*'

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (51) superm1 em 9 dez. 2019

E entĆ£o o diĆ”rio do sistema para o daemon ( fwupd.service para nĆ£o snap e snap.fwupd.fwupd.service para snap)

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (52) superm1 em 9 dez. 2019

Este problema foi marcado automaticamente como obsoleto porque nĆ£o teve atividades recentes. Ele serĆ” fechado se nenhuma outra atividade ocorrer. Obrigado por suas contribuiƧƵes.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (53) stale[bot] em 11 jan. 2020

Aqui estĆ” o log do mesmo erro relatado por @Goddard.

failed to get device after detach: failed to wait for detach replug: device 75f2cedf3387d4d43fc6cd30d11c6e53f47d1a7 did not come back

saĆ­da do journalctl:

fwupd[11437]: 18:06:29:0494 FuMain Called GetRemotes()fwupd[11437]: 18:06:29:0500 FuMain Called Install(e75f2cedf3387d4d43fc6cd30d11c6e53f47d1a7,7)fwupd[11437]: 18:06:29:0500 FuMain got option reasonfwupd[11437]: 18:06:29:0500 FuMain got option filenamefwupd[11437]: 18:06:29:0500 FuEngine Emitting PropertyChanged('Status'='decompressing')fwupd[11437]: 18:06:29:0500 FuMain Emitting PropertyChanged('Status'='decompressing')fwupd[11437]: 18:06:29:0502 FuCabinet processing folder: 1/1fwupd[11437]: 18:06:29:0502 FuCabinet failed to verify com.logitech.Unifying.RQR24.metainfo.xml: no JcatItemfwupd[11437]: 18:06:29:0502 FuCabinet processing file: com.logitech.Unifying.RQR24.metainfo.xmlfwupd[11437]: 18:06:29:0502 XbSilo compiling 463b210def7303f7d40e5a0be9aaefd651f453ed:prefix=componentsā€¦fwupd[11437]: 18:06:29:0502 XbSilo 0,28ms compile 463b210def7303f7d40e5a0be9aaefd651f453ed:prefix=componentsfwupd[11437]: 18:06:29:0502 FuCabinet invalid container checksum (null), fixing up to dcb67c5c079971ee5fc1662c42dea4bee8e1165dfwupd[11437]: 18:06:29:0502 XbSilo 0,47ms get size nodetabfwupd[11437]: 18:06:29:0503 XbSilo 0,04ms adding strtab elementfwupd[11437]: 18:06:29:0503 XbSilo 0,02ms adding strtab attr namefwupd[11437]: 18:06:29:0503 XbSilo 0,03ms adding strtab attr valuefwupd[11437]: 18:06:29:0503 XbSilo 0,05ms adding strtab textfwupd[11437]: 18:06:29:0503 XbSilo 0,02ms writing nodetabfwupd[11437]: 18:06:29:0503 XbSilo 0,02ms fixing ->parent and ->nextfwupd[11437]: 18:06:29:0503 XbSilo 0,00ms appending strtabfwupd[11437]: 18:06:29:0503 XbSilo 0,02ms parse blobfwupd[11437]: 18:06:29:0503 XbSilo 0,02ms query on / with `components/component` limit=0 -> 1 resultsfwupd[11437]: 18:06:29:0503 XbSilo 0,01ms query on component with `releases/release` limit=0 -> 1 resultsfwupd[11437]: 18:06:29:0503 FuCabinet processing release: RQR24.11_B0036fwupd[11437]: 18:06:29:0503 XbSilo 0,06ms query on release with `checksum[@target='content']` limit=1 -> 1 resultsfwupd[11437]: 18:06:29:0518 Jcat returned signature fingerprint 3FC6B804410ED0840D8F2F9748A6D80E4538BAC2fwupd[11437]: 18:06:29:0518 FuCabinet verified payload RQR24.11_B0036.shex using detachedfwupd[11437]: 18:06:29:0518 FuEngine Emitting PropertyChanged('Status'='idle')fwupd[11437]: 18:06:29:0518 FuMain Emitting PropertyChanged('Status'='idle')fwupd[11437]: 18:06:29:0518 XbSilo 0,03ms query on / with `components/component` limit=0 -> 1 resultsfwupd[11437]: 18:06:29:0518 XbSilo 0,06ms query on component with `provides/firmware[@type='flashed']` limit=0 -> 4 resultsfwupd[11437]: 18:06:29:0518 XbSilo 0,04ms query on component with `custom/value[@key='LVFS::UpdateProtocol']` limit=1 -> 1 resultsfwupd[11437]: 18:06:29:0518 XbSilo 0,00ms query on component with `releases/release` limit=1 -> 1 resultsfwupd[11437]: 18:06:29:0518 XbSilo 0,01ms query on component with `requires/*` limit=0 -> 7 resultsfwupd[11437]: 18:06:29:0518 FuEngine requirement 1.3.1 ge 1.4.0 on org.freedesktop.fwupd passedfwupd[11437]: 18:06:29:0518 XbSilo 0,02ms query on component with `provides/firmware[@type='flashed']` limit=0 -> 4 resultsfwupd[11437]: 18:06:29:0518 XbSilo 0,01ms query on component with `custom/value[@key='LVFS::UpdateProtocol']` limit=1 -> 1 resultsfwupd[11437]: 18:06:29:0518 XbSilo 0,00ms query on component with `releases/release` limit=1 -> 1 resultsfwupd[11437]: 18:06:29:0518 XbSilo 0,01ms query on component with `custom/value[@key='LVFS::VersionFormat']` limit=0 -> 0 resultsfwupd[11437]: 18:06:29:0519 XbSilo 0,00ms query on component with `requires/*` limit=0 -> 7 resultsfwupd[11437]: 18:06:29:0519 FuEngine requirement 1.3.1 ge 1.4.0 on org.freedesktop.fwupd passedfwupd[11437]: 18:06:29:0519 XbSilo 0,02ms query on component with `custom/value[@key='LVFS::UpdateMessage']` limit=1 -> 0 resultsfwupd[11437]: 18:06:29:0519 FuMain Emitting PropertyChanged('Status'='waiting-for-auth')fwupd[11437]: 18:06:29:0525 FuMain Emitting PropertyChanged('Status'='idle')fwupd[11437]: 18:06:29:0525 FuIdle inhibiting: performing updatefwupd[11437]: 18:06:29:0526 FuPlugin performing composite_prepare() on dell_dockfwupd[11437]: 18:06:29:0526 XbSilo 0,02ms query on component with `releases/release` limit=1 -> 1 resultsfwupd[11437]: 18:06:29:0526 Fwupd looking for os-release at /etc/os-releasefwupd[11437]: 18:06:29:0526 XbSilo 0,08ms query on component with `releases/release/checksum[@target='container']` limit=1 -> 1 resultsfwupd[11437]: 18:06:29:0526 FuHistory remove device Unifying Receiver [e75f2cedf3387d4d43fc6cd30d11c6e53f47d1a7]fwupd[11437]: 18:06:29:0534 FuHistory add device Unifying Receiver [e75f2cedf3387d4d43fc6cd30d11c6e53f47d1a7]fwupd[11437]: 18:06:29:0540 FuEngine performing prepare on FuLogitechHidPpRuntime:fwupd[11437]: Unifying Receiverfwupd[11437]: DeviceId: e75f2cedf3387d4d43fc6cd30d11c6e53f47d1a7fwupd[11437]: Guid: cc4cbfa9-bf9d-540b-b92b-172ce31013c1fwupd[11437]: Guid: fcf55bf5-767b-51ce-9c17-f6f538c4ee9f <- HIDRAW\VEN_046D&DEV_C52B&REV_00fwupd[11437]: Guid: 279ed287-3607-549e-bacc-f873bb9838c4 <- HIDRAW\VEN_046D&DEV_C52Bfwupd[11437]: Summary: A miniaturised USB wireless receiverfwupd[11437]: Plugin: logitech_hidppfwupd[11437]: Protocol: com.logitech.unifyingsignedfwupd[11437]: Flags: updatable|supported|registeredfwupd[11437]: VendorId: USB:0x046Dfwupd[11437]: Version: RQR24.09_B0033fwupd[11437]: VersionBootloader: BOT03.02_B0009fwupd[11437]: VersionFormat: plainfwupd[11437]: Icon: preferences-desktop-keyboardfwupd[11437]: InstallDuration: 30fwupd[11437]: Created: 2020-04-21fwupd[11437]: Modified: 2020-04-21fwupd[11437]: UpdateState: failedfwupd[11437]: PhysicalId: DEVPATH=/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/usb2/2-2/2-2:1.2fwupd[11437]: SignedFirmware: truefwupd[11437]: 18:06:29:0540 FuPlugin performing update_prepare() on logindfwupd[11437]: 18:06:29:0544 FuPluginLogind opened logind fd 28fwupd[11437]: 18:06:29:0544 FuPlugin performing update_prepare() on upowerfwupd[11437]: 18:06:29:0545 FuEngine performing detach on FuLogitechHidPpRuntime:fwupd[11437]: Unifying Receiverfwupd[11437]: DeviceId: e75f2cedf3387d4d43fc6cd30d11c6e53f47d1a7fwupd[11437]: Guid: cc4cbfa9-bf9d-540b-b92b-172ce31013c1fwupd[11437]: Guid: fcf55bf5-767b-51ce-9c17-f6f538c4ee9f <- HIDRAW\VEN_046D&DEV_C52B&REV_00fwupd[11437]: Guid: 279ed287-3607-549e-bacc-f873bb9838c4 <- HIDRAW\VEN_046D&DEV_C52Bfwupd[11437]: Summary: A miniaturised USB wireless receiverfwupd[11437]: Plugin: logitech_hidppfwupd[11437]: Protocol: com.logitech.unifyingsignedfwupd[11437]: Flags: updatable|supported|registeredfwupd[11437]: VendorId: USB:0x046Dfwupd[11437]: Version: RQR24.09_B0033fwupd[11437]: VersionBootloader: BOT03.02_B0009fwupd[11437]: VersionFormat: plainfwupd[11437]: Icon: preferences-desktop-keyboardfwupd[11437]: InstallDuration: 30fwupd[11437]: Created: 2020-04-21fwupd[11437]: Modified: 2020-04-21fwupd[11437]: UpdateState: failedfwupd[11437]: PhysicalId: DEVPATH=/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/usb2/2-2/2-2:1.2fwupd[11437]: SignedFirmware: truefwupd[11437]: 18:06:29:0545 FuPlugin running superclassed update_detach() on logitech_hidppfwupd[11437]: 18:06:29:0549 FuPluginLogitechHidPp failed to detach to bootloader: failed to send: failed to write 7 bytes to 29: Protokollfehlerfwupd[11437]: 18:06:29:0550 FuDeviceList waiting 10000ms for replugfwupd[11437]: 18:06:29:0555 FuEngine auto-removing GUdevDevicefwupd[11437]: 18:06:29:0555 FuDeviceList waiting 10000ms for Unifying Receiver device removalfwupd[11437]: 18:06:30:0993 FuDevice using 279ed287-3607-549e-bacc-f873bb9838c4 for HIDRAW\VEN_046D&DEV_C52Bfwupd[11437]: 18:06:30:0995 FuDevice using c37b55ca16f25918f5b14cb9431b0db277201f11 for HID_PHYS=usb-0000:03:00.0-2/input0fwupd[11437]: 18:06:31:0054 FuEngine failed to add udev device /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/usb2/2-2/2-2:1.0/0003:046D:AAE5.0096/hidraw/hidraw6: no HID++ IDfwupd[11437]: 18:06:39:0554 FuDeviceList device did not replugfwupd[11437]: 18:06:39:0554 FuHistory modifying device Unifying Receiver [e75f2cedf3387d4d43fc6cd30d11c6e53f47d1a7]fwupd[11437]: 18:06:39:0563 FuPlugin performing composite_cleanup() on dell_dockfwupd[11437]: 18:06:39:0563 FuIdle uninhibiting: performing updatefwupd[11437]: 18:06:39:0564 FuDeviceList doing delayed removalfwupd[11437]: 18:06:39:0564 FuDeviceList ::removed e75f2cedf3387d4d43fc6cd30d11c6e53f47d1a7fwupd[11437]: 18:06:39:0564 FuPlugin performing device_removed() on dell_dock

Replug nĆ£o funcionou e apenas relatou not supported .

  • fwupd 1.4.0
  • libgusb 0.3.4

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (54) a-andre em 21 abr. 2020

@Goddard, vocĆŖ pode abrir uma nova ediĆ§Ć£o com todas as suas circunstĆ¢ncias e registros? A causa raiz deste estĆ” definitivamente corrigida, mas hĆ”

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (55) superm1 em 21 abr. 2020

Em que estado o dispositivo estava realmente depois disso? Seu perifƩrico estava funcionando?

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (56) superm1 em 21 abr. 2020

Antes: Bus 002 Device 043: ID 046d:c52b Logitech, Inc. Unifying Receiver
Depois de: Bus 002 Device 044: ID 046d:aae5 Logitech, Inc. USB BootLoader

O dispositivo parou de funcionar. Tive que reconectar o receptor para o dispositivo funcionar novamente.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (57) a-andre em 21 abr. 2020

Este problema foi marcado automaticamente como obsoleto porque nĆ£o teve atividades recentes. Ele serĆ” fechado se nenhuma outra atividade ocorrer. Obrigado por suas contribuiƧƵes.

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (58) stale[bot] em 22 mai. 2020

Esta pĆ”gina foi Ćŗtil?

0 / 5 - 0 avaliaƧƵes

fwupd šŸš€ - O receptor de unificaĆ§Ć£o falha ao atualizar | bleepcoder.com (2024)
Top Articles
Latest Posts
Article information

Author: Aron Pacocha

Last Updated:

Views: 5995

Rating: 4.8 / 5 (48 voted)

Reviews: 95% of readers found this page helpful

Author information

Name: Aron Pacocha

Birthday: 1999-08-12

Address: 3808 Moen Corner, Gorczanyport, FL 67364-2074

Phone: +393457723392

Job: Retail Consultant

Hobby: Jewelry making, Cooking, Gaming, Reading, Juggling, Cabaret, Origami

Introduction: My name is Aron Pacocha, I am a happy, tasty, innocent, proud, talented, courageous, magnificent person who loves writing and wants to share my knowledge and understanding with you.