Bug 515488 - APN setup doesn't work, says invalid password
Summary: APN setup doesn't work, says invalid password
Status: REPORTED
Alias: None
Product: plasma-mobile
Classification: Plasma
Component: Shell (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Mobile Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-02-04 10:02 UTC by Bart Ribbers
Modified: 2026-02-04 18:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bart Ribbers 2026-02-04 10:02:41 UTC
SUMMARY
On my device Plasma Mobile fails to connect to an APN. When I try to it just keeps saying the password is incorrect even though it's exactly what my provider says it should be.

This is basically the last bug that's blocking me from using my phone with this as a daily driver 😅

STEPS TO REPRODUCE
1. Put a SIM card in your phone running Plasma Mobile
2. Add an APN manually
3. Get settings from the provider, enter the password

OBSERVED RESULT
Plasma Mobile reports the password is invalid

EXPECTED RESULT
It should accept the password and connect

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: postmarketOS edge 
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.2
Comment 1 Bart Ribbers 2026-02-04 18:33:42 UTC
It seems the error reporting in the UI is just wrong. Going through the CLI together with Devin I found out that NetworkManager refuses to connect to my network because I'm roaming and that's now allowed for the connection.
I can enable roaming with `nmcli connection modify "KPN NL" gsm.home-only false` (where "KPN NL" is my provider's APN) and afterwards NetworkManager connects just fine. After that nmcli command I can even connect to the APN through the KCM.

So multiple things:
1. the KCM's error handling is faulty. The password isn't wrong, network manager just refuses to connect because roaming is disabled for the connection
2. roaming is not a global switch but has to be enabled per connection, and the KCM is not doing this
3. the "enable mobile data" switch in the KCM does absolutely nothing