Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I Just bought a Bluetooth loudspeaker SACKit WOOFit S.
My Debian 11 sees the Bluetooth unit all right, and connects alright, but shortly after looses the connection.
Also, when connected, I cannot get any sound out from the unit - what to do ?
rln@rln:~$ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 17ef:1012 Lenovo Lenovo ThinkPad Dock
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 010: ID 046d:c312 Logitech, Inc. DeLuxe 250 Keyboard
Bus 003 Device 009: ID 17ef:1011 Lenovo
Bus 003 Device 008: ID 17ef:1012 Lenovo Lenovo ThinkPad Dock
Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 006: ID 5986:0397 Acer, Inc Integrated Camera
Bus 003 Device 004: ID 8087:07dc Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The SACKit was connected, according to Plasma, at the time of running the command ...
Unfortunately I only run Deb.11 Bullseye on both my pc's.
I just tried, though, to connect the device to my Android (10) phone.
I showed the same reaction: It does connect via bluetooth, but shortly after loses the connection.
Beginning of next week, I shall try to connect the device to an iPhone X, to see how this behaves.
I will be back.
PS: In a previous ticket, you showed med how to search the Internet for VENDORID:PRODUCTID (xxxx:xxxx).
Could you pls repeat, and also tell me which Linux file to edit the information into ?
I just tried, though, to connect the device to my Android (10) phone.
I showed the same reaction: It does connect via bluetooth, but shortly after loses the connection.
Seems to me like your bluetooth device has an issue with itself, not with Debian.
Any particular reason why you run hands-on testing when you're rather inexperienced with Linux?
I tend to agree: The error maybe lies within the device - i.e. the reason that I try to connect it to the iPhone, in order to exclude the Linux side - if the reaction is still the same.
I have one very old pc, which is too low spec to run Windoze10, but it runs Linux perfectly.
By word I was recommended to use Debian Linux.
I didn't appreciate, that Deb.11 is considered "development".
When I know of the iPhone's reaction, I shall return to this ticket and either close it or add info.
The way Debian works is there are three main branches:
1) Stable. Mainly for servers (and for the desktops of cautious people). Gets a complete upgrade every two years. Running updates are for security and bug fixes only.
2) Testing. Continuously updated from Unstable except for a brief freeze just before it becomes the next Stable release. There are separate updates for security but not for fixing bugs; they will get fixed in Unstable eventually.
3) Unstable. Continuously updated. Updates go through into Testing after a fixed time lag. If a bug is found, the clock stops until it is fixed.
Testing has fewer bugs than Unstable but it sometimes take longer for a fix to come through.
btw you might want to reconsider using your email address as a handle. There are roaming bots that skim email addresses from sites for spamming purposes.
THX for the hint on user name.
I don't seem to be able to change my login from my email to something else.
Do I then close this user and reopen a new one?
And how do I keep track of my current issue?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.