[Bug 1830930] Re: USB 3 devices are not detected on thunderbolt 3
I guess it worth updating your BIOS to the latest version. According to the details above you have Ver. 02.06.03, while in HP site I can find Ver 02.07.00 The release notes there mention several fixes for the handling of USB-C ports. (I hope there is an easy way to do so on Linux. Hopefully it's available from fwupd :) ) https://support.hp.com/us-en/drivers/selfservice/hp-elitedesk-800-65w-g4 -desktop-mini-pc/21353734 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830930 Title: USB 3 devices are not detected on thunderbolt 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830930] Re: USB 3 devices are not detected on thunderbolt 3
From https://www.samsung.com/semiconductor/minisite/ssd/product/portable/t5/ I learn this is a USB 3.1 Gen2 device, not a Thunderbolt device, so authorization isn't relevant (and thunderbolt-tools isn't the relevant package). Still, the fact that you had to force power the controller even when a device is connected (and especially as it works when it's connected on boot) suggests there is some sort of issue between the BIOS / port controller / cable / maybe other parts in the system that take part in the HW detection. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830930 Title: USB 3 devices are not detected on thunderbolt 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1830930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 150252] Re: [master] tasksel removes all Ubuntu-desktop dependencies without confirmation dialog
Still happens on Ubuntu 18.10. I removed openssh-server and noticed a lot of dependencies of ubuntu-desktop removed. Running "apt install ubuntu-desktop" after it installed 270 packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/150252 Title: [master] tasksel removes all Ubuntu-desktop dependencies without confirmation dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tasksel/+bug/150252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748157] Re: [MIR] thunderbolt-tools
Thanks for the review! I'd like to get a bit more details about some of the comments to understand what steps I can take to improve it. Please let me know if you prefer to take this discussion to another medium. > - udev rules -- appear to be configured for works-by-default behaviour, > some examples on how to configure for authorization-required would be > nice I'm not sure I understand what examples and what configuration this comment refers to. > - No tests, a bit unfortunate This is about the package or the upstream project? Upstream we have some tests (using umockdev). See here for CI: https://travis-ci.org/intel/thunderbolt-software-user-space > - File IO done via RAII-C++ classes, not exactly obvious when it happens Any specific question that I can answer (or maybe even document in the code)? > - No PolicyKit My assumption (and is mentioned here and there in the code) is that eventually the tool will be better if it does start using PolicyKit for the privileged actions. It'd be nice to here what do you think about it or if there are guidelines from the distro on where, when and how to use it. > It uses std::random_device for security uses -- I believe this is safe but > direct use of getrandom(2) would not have questions about underlying C++ > library implementation choices. Noted. flags=0 is good enough, yes? (I will may have to make sure first that all the relevant distros include this syscall already.) Thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748157 Title: [MIR] thunderbolt-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1748157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761757] Re: use correct path for tbtacl in udev rules
I'm not sure I understand what's going on here, so I'll take the risk that I'm describing the obvious: @UDEV_BIN_DIR@ is a cmake parameter that is replaced by cmake with the path it reads from pkgconfig. See here: https://github.com/intel/thunderbolt-software-user-space/blob/master/CMakeLists.txt#L10 If this is the wrong location: 1. UDEV_BIN_DIR can be set manually while running cmake (or using ccmake/cmake-gui). 2. If there is a better way to detect the distro-specific correct location for udev dirs, I'd like to fix it upstream. Anyway, copy of the original .rules.in files instead of using the resulted .rules file seems strange to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761757 Title: use correct path for tbtacl in udev rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1761757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748157] Re: [MIR] thunderbolt-tools
Seth, It was disabled as the project is now handled at freedesktop's GitLab. I opened an issue there: https://github.com/intel/thunderbolt-software-user-space/issues/60 ** Bug watch added: github.com/intel/thunderbolt-software-user-space/issues #60 https://github.com/intel/thunderbolt-software-user-space/issues/60 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748157 Title: [MIR] thunderbolt-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1748157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748157] Re: [MIR] thunderbolt-tools
(Sorry, I meant: https://gitlab.freedesktop.org/bolt/bolt/issues/78) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748157 Title: [MIR] thunderbolt-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1748157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748157] Re: [MIR] thunderbolt-tools
My 2 cents: I think bolt and thunderbolt-tools must agree on the ACL (device whitelist for auto-approve on next connection) location and format and then I assume they can co-exist happily without stepping on each other's toes. Even if both try to authorize the same device on connection, it shouldn't matter much as the final result is that the device is authorized and ready to use. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748157 Title: [MIR] thunderbolt-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1748157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697395] Re: Thunderbolt devices don't work if connected during boot
FYI, the patches that Mario mentioned above landed Linus' tree for v4.14-rc1 and hopefully will be backported to 4.13. See details here: https://github.com/01org/thunderbolt-software-user-space/issues/24#issuecomment-328011428 ** Bug watch added: github.com/01org/thunderbolt-software-user-space/issues #24 https://github.com/01org/thunderbolt-software-user-space/issues/24 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697395 Title: Thunderbolt devices don't work if connected during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
