Description of problem: ----------------------- A pFranc USB Serial adapter type U232-P9 USB serial adapter is recognised and works correctly on a loop-back cable but causes Thunar to report kernel errors. This is unexpected behavior: a serial adapter cannot contain a filing system and so should either not be passed to Thunar or should be refused by Thunar without causing kernel errors. Version-Release number of selected component (if applicable): ------------------------------------------------------------- Thunar 1.6.15 How reproducible: ----------------- Happens every time the USB Serial adapter is attached Steps to Reproduce: ------------------- 1. Plug the USB Serial adapter into a vacant USB port Actual results: --------------- Jun 4 13:03:20 zappa kernel: usb 2-1: new full-speed USB device number 5 using xhci_hcd Jun 4 13:03:21 zappa kernel: usb 2-1: New USB device found, idVendor=0711, idProduct=0230 Jun 4 13:03:21 zappa kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jun 4 13:03:21 zappa kernel: usb 2-1: Manufacturer: USB-RS232 Interface Converter Jun 4 13:03:21 zappa kernel: usb 2-1: SerialNumber: 097465 Jun 4 13:03:21 zappa kernel: mct_u232 2-1:1.0: MCT U232 converter detected Jun 4 13:03:21 zappa kernel: usb 2-1: MCT U232 converter now attached to ttyUSB0 Jun 4 13:03:21 zappa mtp-probe[1955]: checking bus 2, device 5: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1" Jun 4 13:03:21 zappa mtp-probe[1955]: bus: 2, device: 5 was not an MTP device Jun 4 13:03:21 zappa org.xfce.FileManager[1135]: thunar-volman: Unsupported USB device type "usb". Jun 4 13:03:21 zappa org.xfce.FileManager[1135]: thunar-volman: Unsupported USB device type "mct_u232". Expected results: ----------------- Connecting the serial adaptor should not cause Thunar to raise kernel errors.
This is actually thunar-volman at fault. Would you be willing to file a bug on thunar-volman upstream? Or would you prefer I do so? Thanks for the report...
I talked to Kevin about re-filing bugs. He refiled this under thunar-volman and explained the ins and outs of the process.
If you have already filed an upstream bug, can you please post the bug number here?
I filed it: https://bugzilla.xfce.org/show_bug.cgi?id=14442
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Created attachment 1508987 [details] The relevant section of /var/log/messages
This problem is still present in Fedora 28. Attachment 1508987 [details], which preceeds this comment, was produced today by connecting the USB serial adapter to my Lenovo T440 laptop. It is running a copy of Fedora 28 that was last updated on 23Nov2018. Here is the version info: $ cat /proc/version Linux version 4.19.2-200.fc28.x86_64 (mockbuild.fedoraproject.org) (gcc version 8.2.1 20181105 (Red Hat 8.2.1-5) (GCC)) #1 SMP Wed Nov 14 20:58:35 UTC 2018 The log section shows that the kernel correctly recognised the USB serial adapter and registered it as ttyUSB0 and expected. Then its handed to thunar-volman, which fails to bind it because it doesn't support either a 'usb' or a 'mct_232' - scarcely surprising as USB serial converters don't support filing systems. At this point invoking thunar has failed, the USB serial adapter is disconnected, something (modemManager?) unbinds it and ModemManager also gives up and goes away. A similar thing happens with am AXE027 USBserial converter. The log of this failed connect session is in the following attachment. As adouble check just now I used this serial converter on a RaspberryPi (also fully patched on 23Nov2018). It runs Raspbian Linux, i.e. 32 bit Debian on an ARM chip). This test successfully uploaded and ran a binary on a PICAXE chip, displaying messages sent from the PICAXE in my Linux terminal session.
Created attachment 1509006 [details] log connection showing AXE027 USB serial adapter failure to initialise This is the second log showing what happened whe n I tried to use the AXE027 USB-serial adapted on my Lenovo T440 running fully patched (as of 23Nov18) Fedora 28.
This problem is partially fixed at present: My system was upgraded today. It is now: Linux version 4.20.5-100.fc28.x86_64 (mockbuild.fedoraproject.org) (gcc version 8.2.1 20181215 (Red Hat 8.2.1-6) (GCC)) #1 SMP Mon Jan 28 19:29:44 UTC 2019 My old pFranc serial adaptor is now working as expected and has communicated successfully with my airband transceiver with this adapter: Feb 1 20:14:35 zappa kernel: usb 2-2: new full-speed USB device number 20 using xhci_hcd Feb 1 20:14:36 zappa kernel: usb 2-2: New USB device found, idVendor=0711, idProduct=0230, bcdDevice= 1.03 Feb 1 20:14:36 zappa kernel: usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Feb 1 20:14:36 zappa kernel: usb 2-2: Manufacturer: USB-RS232 Interface Converter Feb 1 20:14:36 zappa kernel: usb 2-2: SerialNumber: 097465 Feb 1 20:14:36 zappa kernel: mct_u232 2-2:1.0: MCT U232 converter detected Feb 1 20:14:36 zappa kernel: usb 2-2: MCT U232 converter now attached to ttyUSB0 Feb 1 20:14:36 zappa mtp-probe[7106]: checking bus 2, device 20: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-2" Feb 1 20:14:36 zappa mtp-probe[7106]: bus: 2, device: 20 was not an MTP device Feb 1 20:14:36 zappa journal[1975]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0 Feb 1 20:14:36 zappa journal[1975]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2 The newer PICAXE AXE027 programming cable also appears to be usable but can't be further tested because : Feb 1 20:18:31 zappa kernel: usb 2-2: new full-speed USB device number 22 using xhci_hcd Feb 1 20:18:31 zappa kernel: usb 2-2: New USB device found, idVendor=0403, idProduct=bd90, bcdDevice= 6.00 Feb 1 20:18:31 zappa kernel: usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Feb 1 20:18:31 zappa kernel: usb 2-2: Product: AXE027 PICAXE USB Feb 1 20:18:31 zappa kernel: usb 2-2: Manufacturer: Revolution Feb 1 20:18:31 zappa kernel: ftdi_sio 2-2:1.0: FTDI USB Serial Device converter detected Feb 1 20:18:31 zappa kernel: usb 2-2: Detected FT232RL Feb 1 20:18:31 zappa kernel: usb 2-2: FTDI USB Serial Device converter now attached to ttyUSB0 Feb 1 20:18:31 zappa mtp-probe[7145]: checking bus 2, device 22: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-2" Feb 1 20:18:31 zappa mtp-probe[7145]: bus: 2, device: 22 was not an MTP device Feb 1 20:18:31 zappa journal[1975]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0 Feb 1 20:18:31 zappa journal[1975]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2 And, as you can see, above, there is no longer any attempt to hand the connection over to Thunar. Good job!
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.