Created attachment 169050 [details] Focus at the same thing down right under. SUMMARY So far, I do not manage to get WIFI enabled by the useful steps at a fresh install of Kubuntu 24.04 LTS, at this laptop: Lenovo Thinkpad X230 i5, along with 4 GB RAM, 250 GB SSD. A quick internet search clarifies me that I am not the only one who deals with this problem. I do work now with wired internet. However, this wired connection does not help me to get the WIFI enabled. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
*** Bug 486369 has been marked as a duplicate of this bug. ***
> bas@Camino:~$ rfkill list > 0: tpacpi_bluetooth_sw: Bluetooth > Soft blocked: yes > Hard blocked: yes > 1: phy0: Wireless LAN > Soft blocked: no > Hard blocked: yes If it is hardblocked, it cannot be enabled in software. E.g., see https://askubuntu.com/questions/98702/how-to-unblock-something-listed-in-rfkill Unfortunately this seems like a downstream configuration issue and I would suggest asking for help on the distribution forums.
ADDITIONAL INFORMATION - UPDATE THURSDAY 2 MAY 2024. ==================================================== Bug 486369, https://bugs.kde.org/show_bug.cgi?id=486369, has been remarked as a duplicate of this one. However, the text of that «duplicate» bug is much more complete then this one before me submitting this update. Anyway, it was not my intention to submit two bugs about the same issue. But because of some mistake at my side, I unintentionally submitted two bug reports. Here below, I share an edited and updated version of the bug report that is complete in my opinion, hower a «duplicate». SUMMARY ====== So far, I do not manage to get WIFI enabled by the useful steps at a fresh install of Kubuntu 24.04 LTS, at this laptop: Lenovo Thinkpad X230 i5, along with 4 GB RAM, 250 GB SSD. A quick internet search clarifies me that I am not the only one who deals with this problem. I do work now with wired internet. However, this wired connection does not help me to get the WIFI enabled. Ticking the box for enabling WIFI is not possible. You can see it at the screenshot I send with this report. That's why, I have looked for methods to get WIFI enabled via the command line. No result. At this output report, you can see why: bas@Camino:~$ iw dev phy#0 Interface wlp3s0 ifindex 3 wdev 0x1 addr 9c:4e:36:aa:5c:d0 type managed txpower 0.00 dBm multicast TXQ: qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets 0 0 0 0 0 0 0 0 0 bas@Camino:~$ sudo ip link set wlp3s0 up RTNETLINK answers: Operation not possible due to RF-kill bas@Camino:~$ bas@Camino:~$ nmcli radio wifi disabled bas@Camino:~$ nmcli radi wifi on bas@Camino:~$ sudo nmcli radio wifi on bas@Camino:~$ sudo ip link set wlp3s0 up RTNETLINK answers: Operation not possible due to RF-kill bas@Camino:~$ bas@Camino:~$ rfkill list 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: yes 1: phy0: Wireless LAN Soft blocked: no Hard blocked: yes bas@Camino:~$ See also, amongst other pages: https://www.baeldung.com/linux/connect-network-cli https://www.baeldung.com/linux/disable-wireless-network STEPS TO REPRODUCE ================= 1. The graphical check down under - trying to tick the box to enable WIFI. See also attached screenshot. 2. Command line checks summarised here - see here above. See also the two links for more info. OBSERVED RESULT ============== Both checks did NOT end up in enabling WIFI. EXPECTED RESULT ============== Enabling WIFI should need to be possible via either command line or the graphical approach. SOFTWARE/OS VERSIONS ==================== Linux/KDE Plasma: (available in About System) System info 1 May 2024. ++++++++++++++++++++ Operating System: Kubuntu 24.04 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.8.0-31-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 3,5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4000 Manufacturer: LENOVO Product Name: 2325AZ8 System Version: ThinkPad X230 Yesterday, Wednesday 1 May 2024, a comment came in about this passage in my report: > bas@Camino:~$ rfkill list > 0: tpacpi_bluetooth_sw: Bluetooth > Soft blocked: yes > Hard blocked: yes > 1: phy0: Wireless LAN > Soft blocked: no > Hard blocked: yes This is the comment I point at: «(...) If it is hardblocked, it cannot be enabled in software. E.g., see https://askubuntu.com/questions/98702/how-to-unblock-something-listed-in-rfkill Unfortunately this seems like a downstream configuration issue and I would suggest asking for help on the distribution forums. (...)» I get this point. It needs to be resolved «downstream», at Kubuntu related forums in my case. However, I still consider this bug as unresolved. That's why, I reopen it. I gonna ask for advise at two of such Kubuntu forums. I'll point at both of them at this bug report. If some useful advise comes in, I'll share it also here. Yours. Bas Roufs, Mook, near Nijmegen, NL.
I understand that your issue is still ongoing, but marking this bug report as resolved-downstream just means that there is nothing we could do about this issue on KDE's side, and this seems like an issue downstream. So please don't reopen this unless there is further evidence that this indicates a bug in KDE software.
(In reply to fanzhuyifan from comment #4) > I understand that your issue is still ongoing, but marking this bug report > as resolved-downstream just means that there is nothing we could do about > this issue on KDE's side, and this seems like an issue downstream. So please > don't reopen this unless there is further evidence that this indicates a bug > in KDE software. I understand and respect this opinion. However, please clarify me: what means, in my situation, «downstream»? Kubuntu? If something(In reply to fanzhuyifan from comment #4) > I understand that your issue is still ongoing, but marking this bug report > as resolved-downstream just means that there is nothing we could do about > this issue on KDE's side, and this seems like an issue downstream. So please > don't reopen this unless there is further evidence that this indicates a bug > in KDE software. I understand and respect this opinion. However, clarify what means «downstream» in this situation - Kubuntu, the system where I stumbled on this bug? If some useful info will come in from there, I'll share it here. May be, also other Kubuntu users will subscribe to this bug - I am not the only one who experiences this problem.
(In reply to Bas Roufs from comment #5) > I understand and respect this opinion. However, clarify what means > «downstream» in this situation - Kubuntu, the system where I stumbled on > this bug? If some useful info will come in from there, I'll share it here. > May be, also other Kubuntu users will subscribe to this bug - I am not the > only one who experiences this problem. IMO this might be a hardware issue (there is something physically wrong with the card/the connection), or this might be a driver issue (driver bug or wrong driver). Anyways I would suggest asking for help on the distribution forums.
Yet another possibility is that your laptop has a physical button to enable/disable the wifi, and you need to press that (https://askubuntu.com/questions/98702/how-to-unblock-something-listed-in-rfkill).
(In reply to fanzhuyifan from comment #6) > (In reply to Bas Roufs from comment #5) > > I understand and respect this opinion. However, clarify what means > > «downstream» in this situation - Kubuntu, the system where I stumbled on > > this bug? If some useful info will come in from there, I'll share it here. > > May be, also other Kubuntu users will subscribe to this bug - I am not the > > only one who experiences this problem. > > IMO this might be a hardware issue (there is something physically wrong with > the card/the connection), or this might be a driver issue (driver bug or > wrong driver). Anyways I would suggest asking for help on the distribution > forums. Of course, I'll check all such options at such forums. However, when I worked with Kubuntu 22.04.4 LTS at exactly the same device, I WAS able to work with WIFI - then, it was no problem to enable it.
(In reply to fanzhuyifan from comment #7) > Yet another possibility is that your laptop has a physical button to > enable/disable the wifi, and you need to press that > (https://askubuntu.com/questions/98702/how-to-unblock-something-listed-in- > rfkill). The button combination FN -F5 is seemlingly aimed at toggling WIFI. However, nothing happens. When alternating this button combination with the terminal command connmanctl enable wifi, I keep getting this feedback: wifi is not available. bas@Camino:~$ connmanctl enable wifi wifi is not available Weird detail: at Kubuntu 22.04.4 LTS, I did not have such an issue. WIFI worked simply.
Created attachment 169142 [details] 1. Mouse at WIFI connection corner right down under.
Created attachment 169143 [details] 1a. Focus at mouse pointer at WIFI connection corner right down under.png
Created attachment 169144 [details] Enabling WIFI not possible
Created attachment 169145 [details] 2a. Detail - Enabling WIFI not possible.png
Created attachment 169146 [details] 3. Bluetooth disbabled.png
Created attachment 169147 [details] 3a. Impossible to get Bluetooth enabled.
As I said, if the wifi is hard blocked, there is nothing kde software could do about it. Please don't reopen this.
(In reply to fanzhuyifan from comment #16) > As I said, if the wifi is hard blocked, there is nothing kde software could > do about it. Please don't reopen this. @ the KDE experts who have dealt with this bug report: https://bugs.kde.org/show_bug.cgi?id=486368 (In reply to fanzhuyifan from comment #16) > As I said, if the wifi is hard blocked, there is nothing kde software could > do about it. Please don't reopen this. A few words about the status of this bug..... I do respect your wish to NOT «reopen» it. However, the qualification «resolved» is simply not right - the bug is far from resolved. That's why, I have changed the status of the bug to «reported» instead of «resolved». However, as you suggest, I am sharing now this bug «downstream». It is not possible, according to you, to solve the issue at the level of KDE. «Downstream» means in my case: experts and experienced users of Kubuntu - especially those who deal with WIFI and Bluetooth. I have already started a conversation with a few amongst them about this issue. However, before sharing this report more widely amongst Kubuntu experts and users, I need to make this report more complete. That's why, I have added some extra screeenshots as well as this 3 May update. I need to add here two things more. First of all, it has become clear to me that at my system, there is a similar problem with Bluetooth. That's why, I deal with it in more detail in this update. Finally - terminal reports indeed do point at «hard blocks» for both WIFI and Bluetooth. Also a few Kubuntu expert users I spoke with so far, think in the same direction, which I understand. On the other hand - Only a few weeks ago, I have been working with Kubuntu 22.04.4 LTS at exactly the same laptop with the same hardware and the same BIOS settings. Then, WIFI worked out of the box and Bluetooth with some hiccups. I am really not sure whether «hard blocks» are the core issue. More about this here below in this paragraph..... «(...) WHAT IS THE CORE ISSUE? HARD BLOCKS AND/OR SOMETHING ELSE? (..)» @ Kubuntu expert users..... After checking the settings related to WIFI (and Bluetooth), I ended up filing a bug report at KDE: https://bugs.kde.org/show_bug.cgi?id=486368 According to the feedback I got from KDE experts after doing so, the problem is real. However, those experts say it cannot be solved at the side of KDE. It needs to be solved «downstream», so at the side of Kubuntu in our case. My question in this context: how and where exactly can I file a bug report in such a way, that it will be read and dealt with by Kubuntu expert users who deal with WIFI and Bluetooth? A complete update I'll publish here in a few hours.
Cannot enable WIFI at Kubuntu 24.04 LTS. Same problem for Bluetooth. Update from the bug reporter, Bas Roufs, Friday 3 May 2024 for this bug report: https://bugs.kde.org/show_bug.cgi?id=486368 Mook, near Nijmegen, The Netherlands: For: Expert users and developers of Kubuntu who know about WIFI and Bluetooth. Cc.: KDE Experts. INTRODUCTION. ============ @ the KDE experts who have dealt with this bug report: https://bugs.kde.org/show_bug.cgi?id=486368 (In reply to fanzhuyifan from comment #16) > As I said, if the wifi is hard blocked, there is nothing kde software could > do about it. Please don't reopen this. A few words about the status of this bug..... I do respect your wish to NOT «reopen» it. However, the qualification «resolved» is simply not right - the bug is far from resolved. That's why, I have changed the status of the bug to «reported» instead of «resolved». However, as you suggest, I am sharing now this bug «downstream». It is not possible, according to you, to solve the issue at the level of KDE. «Downstream» means in my case: experts and experienced users of Kubuntu - especially those who deal with WIFI and Bluetooth. I have already started a conversation with a few amongst them about this issue. However, before sharing this report more widely amongst Kubuntu experts and users, I need to make this report more complete. That's why, I have added some extra screeenshots as well as this 3 May update. I need to add here two things more. First of all, it has become clear to me that at my system, there is a similar problem with Bluetooth. That's why, I deal with it in more detail in this update. Finally - terminal reports indeed do point at «hard blocks» for both WIFI and Bluetooth. Also a few Kubuntu expert users I spoke with so far, think in the same direction, which I understand. On the other hand - Only a few weeks ago, I have been working with Kubuntu 22.04.4 LTS at exactly the same laptop with the same hardware and the same BIOS settings. Then, WIFI worked out of the box and Bluetooth with some hiccups. I am really not sure whether «hard blocks» are the core issue. More about this here below in this paragraph..... «(...) WHAT IS THE CORE ISSUE? HARD BLOCKS AND/OR SOMETHING ELSE? (..)» @ Kubuntu expert users..... After checking the settings related to WIFI (and Bluetooth), I ended up filing a bug report at KDE: https://bugs.kde.org/show_bug.cgi?id=486368 According to the feedback I got from KDE experts after doing so, the problem is real. However, those experts say it cannot be solved at the side of KDE. It needs to be solved «downstream», so at the side of Kubuntu in our case. My question in this context: how and where exactly can I file a bug report in such a way, that it will be read and dealt with by Kubuntu expert users who deal with WIFI and Bluetooth? A complete update I'll publish here in a few hours. THE PROBLEM IN BRIEF. ==================== So far, I do not manage to get WIFI enabled by the useful steps at a fresh install of Kubuntu 24.04 LTS, at this laptop: Lenovo Thinkpad X230 i5, along with 4 GB RAM, 250 GB SSD. A quick internet search clarifies me that I am not the only one who deals with this problem. I do work now with wired internet. However, this wired connection does not help me to get the WIFI enabled. Ticking the box for enabling WIFI is not possible. The same applies for Bluetooth. You can see it at the screenshots I have sent along with this bug report: https://bugs.kde.org/show_bug.cgi?id=486368 That's why, I have looked for methods to get both WIFI and Bluetooth enabled via the command line. I do get useful info like that. However, so far, I do not manage to get WIFI and Bluetooth enabled. Here below, I share with you a command line output report. COMMAND LINE bas@Camino:~$ iw dev phy#0 Interface wlp3s0 ifindex 3 wdev 0x1 addr 9c:4e:36:aa:5c:d0 type managed txpower 0.00 dBm multicast TXQ: qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets 0 0 0 0 0 0 0 0 0 bas@Camino:~$ sudo ip link set wlp3s0 up RTNETLINK answers: Operation not possible due to RF-kill bas@Camino:~$ bas@Camino:~$ nmcli radio wifi disabled bas@Camino:~$ nmcli radi wifi on bas@Camino:~$ sudo nmcli radio wifi on bas@Camino:~$ sudo ip link set wlp3s0 up RTNETLINK answers: Operation not possible due to RF-kill bas@Camino:~$ bas@Camino:~$ rfkill list 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: yes 1: phy0: Wireless LAN Soft blocked: no Hard blocked: yes bas@Camino:~$ See also, amongst other pages: https://www.baeldung.com/linux/connect-network-cli https://www.baeldung.com/linux/disable-wireless-network STEPS TO REPRODUCE ================= 1. Check my screeenshots attached to the bug report at KDE. It's about the graphical check down under - fruitlessly trying to tick the box to enable WIFI or the one to enable Bluetooth. At each screenshot, you can see a red arrow pointing at a WIFI or Bluetooth check box that cannot be ticked. 2. Command line checks summarised here - see here above. See also the two links for more info. OBSERVED RESULT ============== Both checks did NOT end up in enabling WIFI. EXPECTED RESULT ============== Enabling WIFI should need to be possible via either command line, the graphical approach or both of them. SOFTWARE/OS VERSIONS ==================== Linux/KDE Plasma: (available in About System) System info 3 May 2024. ++++++++++++++++++++ Operating System: Kubuntu 24.04 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.8.0-31-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 3,5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4000 Manufacturer: LENOVO Product Name: 2325AZ8 System Version: ThinkPad X230 WHAT IS THE CORE ISSUE? HARD BLOCKS AND/OR SOMETHING ELSE? +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ On Wednesday 1 May 2024, a comment came in about this passage in my report: > bas@Camino:~$ rfkill list > 0: tpacpi_bluetooth_sw: Bluetooth > Soft blocked: yes > Hard blocked: yes > 1: phy0: Wireless LAN > Soft blocked: no > Hard blocked: yes This is the comment I point at: «(...) If it is hardblocked, it cannot be enabled in software. E.g., see https://askubuntu.com/questions/98702/how-to-unblock-something-listed-in-rfkill Unfortunately this seems like a downstream configuration issue and I would suggest asking for help on the distribution forums. (...)» I get this point. I gonna ask for advise at two Kubuntu forum. I'll point there at this bug report. If some useful advise comes in, I'll share it also here. More about Bluetooth. --------------------- Here below, I carry out some checks recommended in this article: https://community.spiceworks.com/t/how-to-verify-bluetooth-using-linux-command/961891 bas@Camino:~$ bluetoothctl -v bluetoothctl: 5.72 bas@Camino:~$ No error report so far - there is SOME bluetooth in the system. Now, I check whether bluetooth is running or not..... bas@Camino:~$ systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Active: active (running) since Fri 2024-05-03 14:49:51 CEST; 5h 40min ago Docs: man:bluetoothd(8) Main PID: 1931 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4220) Memory: 552.0K (peak: 2.9M swap: 412.0K swap peak: 412.0K) CPU: 98ms CGroup: /system.slice/bluetooth.service └─1931 /usr/libexec/bluetooth/bluetoothd mei 03 14:49:51 Camino bluetoothd[1931]: Starting SDP server mei 03 14:49:51 Camino bluetoothd[1931]: src/plugin.c:plugin_init() System does not support csip plugin mei 03 14:49:51 Camino bluetoothd[1931]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled mei 03 14:49:51 Camino bluetoothd[1931]: src/plugin.c:plugin_init() System does not support micp plugin mei 03 14:49:51 Camino bluetoothd[1931]: src/plugin.c:plugin_init() System does not support vcp plugin mei 03 14:49:51 Camino bluetoothd[1931]: src/plugin.c:plugin_init() System does not support mcp plugin mei 03 14:49:51 Camino bluetoothd[1931]: src/plugin.c:plugin_init() System does not support bass plugin mei 03 14:49:51 Camino bluetoothd[1931]: src/plugin.c:plugin_init() System does not support bap plugin mei 03 14:49:51 Camino bluetoothd[1931]: Bluetooth management interface 1.22 initialized mei 03 14:49:51 Camino bluetoothd[1931]: src/profile.c:register_profile() :1.53 tried to register 0000111e-00> lines 1-22/22 (END) Apparently, it is running, however, with some complications. How to fix them? Can anybody help with this? Now, I try this..... bas@Camino:~$ sudo systemctl start bluetooth [sudo] password for bas: bas@Camino:~$ No error report here. Now, I try again this command: systemctl status bluetooth The result I get is exactly as above. Now, I gonna check whether or not all required packages have been installed: sudo apt list --installed | grep blue bas@Camino:~$ sudo apt list --installed | grep blue [sudo] password for bas: WARNING: apt does not have a stable CLI interface. Use with caution in scripts. bluedevil/noble,now 4:5.27.11-0ubuntu2 amd64 [installed,automatic] bluez-cups/noble,now 5.72-0ubuntu5 amd64 [installed,automatic] bluez-obexd/noble,now 5.72-0ubuntu5 amd64 [installed,automatic] bluez/noble,now 5.72-0ubuntu5 amd64 [installed,automatic] libbluetooth3/noble,now 5.72-0ubuntu5 amd64 [installed,automatic] libkf5bluezqt-data/noble,noble,now 5.115.0-0ubuntu6 all [installed,automatic] libkf5bluezqt6/noble,now 5.115.0-0ubuntu6 amd64 [installed,automatic] libspa-0.2-bluetooth/noble,now 1.0.5-1 amd64 [installed,automatic] qml-module-org-kde-bluezqt/noble,now 5.115.0-0ubuntu6 amd64 [installed,automatic] Apparently, everything needed has been installed. Now, I look at the «bluetooth adapter» and connectivity issues. sudo hciconfig hci0 reset bas@Camino:~$ sudo hciconfig hci0 reset Can't get device info: No such device This is weird....This points at some hardare issue? On the other hand... at exactly the same laptop with the same specs, I DID work with Bluetooth. However, it was not reliable. There were hiccups. By toggling FN + F5, I tried to get Bluetooth and or WIFI working.... But the test «sudo hciconfig hci0 reset» delivers the same non-result. Any conflicting Bluetooth related services running? I try this command.... sudo systemctl list-units | grep -i bluetooth bas@Camino:~$ sudo systemctl list-units | grep -i bluetooth bluetooth.service loaded active running Bluetooth service bas@Camino:~$ Apparently, there is one process running. But I still cannot «enable» Bluetooth. No clue what to do next to get Bluetooth running. Can anybody help me with this? HARDWARE ISSUES OR SOMETHING ELSE? +++++++++++++++++++++++++++++++++ For both WIFI and Bluetooth, command output reports seemingly point at hardware issues, hard blocs, etc.On the other hand, at exactly the same laptop, I WAS able to with with those techniques - WIFI out of the box, BLuetooth with some hiccups. I hope to get together more answers from now on.
I just submitted an adapted version of this bug report here: Cannot enable WIFI & Bluethooth at fresh install of Kubuntu 24.04 LTS. «Hard blocks» or something else?. https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2065074
despues de una actualizacion ya no me detecta la tarjeta Wifi, mi equipo es un sony vaio VPCSB