Description of problem: "could not open port" error has not handled. Version-Release number of selected component: esptool-3.2-2.fc36 Additional info: reporter: libreport-2.17.1 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-a8be372b-bc99-4c60-ae91-3a3ccca15680.scope cmdline: /usr/bin/python3 -s /usr/bin/esptool --chip esp32c3 --port /dev/ttyUSB0 --baud 921600 flash_id crash_function: open exception_type: FileNotFoundError executable: /usr/bin/esptool interpreter: python3-3.10.4-1.fc36.x86_64 kernel: 5.17.11-300.fc36.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: serialposix.py:268:open:serial.serialutil.SerialException: [Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0' Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/serial/serialposix.py", line 265, in open self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK) FileNotFoundError: [Errno 2] No such file or directory: '/dev/ttyUSB0' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/esptool", line 5143, in <module> _main() File "/usr/bin/esptool", line 5136, in _main main() File "/usr/bin/esptool", line 4541, in main esp = esp or get_default_connected_device(ser_list, port=args.port, connect_attempts=args.connect_attempts, File "/usr/bin/esptool", line 125, in get_default_connected_device _esp = chip_class(each_port, initial_baud, trace) File "/usr/bin/esptool", line 329, in __init__ self._port = serial.serial_for_url(port) File "/usr/lib/python3.10/site-packages/serial/__init__.py", line 88, in serial_for_url instance.open() File "/usr/lib/python3.10/site-packages/serial/serialposix.py", line 268, in open raise SerialException(msg.errno, "could not open port {}: {}".format(self._port, msg)) serial.serialutil.SerialException: [Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0' Local variables in innermost frame: self: Serial<id=0x7f8bb7f0d4b0, open=False>(port='/dev/ttyUSB0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=None, xonxoff=False, rtscts=False, dsrdtr=False) Potential duplicate: bug 1925968
Created attachment 1886103 [details] File: backtrace
Created attachment 1886104 [details] File: cpuinfo
Created attachment 1886105 [details] File: environ
Created attachment 1886106 [details] File: mountinfo
Created attachment 1886107 [details] File: namespaces
Created attachment 1886108 [details] File: open_fds
Does /dev/ttyUSB0 exist on your system?
no ttyUSB0 in there. maybe you can put a try-except block in esptool? to avoid triggering abrt.
Thank you for the report. I wasn't aware this problem triggers abrt. See upstream PR: https://github.com/espressif/esptool/pull/751. We will backport it to esptool in Fedora 36.
Pull requests with update were open to all Fedoras: F37: https://src.fedoraproject.org/rpms/esptool/pull-request/9 F36: https://src.fedoraproject.org/rpms/esptool/pull-request/10 F35: https://src.fedoraproject.org/rpms/esptool/pull-request/11
FEDORA-2022-16e68a849a has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-16e68a849a
FEDORA-2022-16e68a849a has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-6e23de3038 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-6e23de3038
FEDORA-2022-4c59060b08 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-4c59060b08
FEDORA-2022-6e23de3038 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-6e23de3038` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-6e23de3038 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-4c59060b08 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-4c59060b08` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-4c59060b08 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-4c59060b08 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-6e23de3038 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.