https://bugs.kde.org/show_bug.cgi?id=486368

Bas Roufs <basro...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|DOWNSTREAM                  |---
     Ever confirmed|0                           |1
             Status|RESOLVED                    |REOPENED

--- Comment #3 from Bas Roufs <basro...@gmail.com> ---
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.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to