Arch Linux

cryptearth

Member

Registered: 2024-02-03

Posts: 2,374

kde bug tracker limited access?

in reference to https://bbs.archlinux.org/viewtopic.php?id=315167
tried to open linked bug from my phone via mobile, android, chrome, no extensions: 403
tried via wget from my home pc: works
asked google: seems the kde bug tracker is quite restrictive - but also blocking regular mobile internet? anyone knows anything?

kokoko3k

Member

Registered: 2008-11-14

Posts: 2,479

Re: kde bug tracker limited access?

Worked with firefox mobile, but not from lightning (an android webview based browser), 403.

Faced that since long time.

Last edited by kokoko3k (2026-10-13 17:04:32)

---

Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !

5hridhyan

Member

Registered: 2025-12-25

Posts: 1,097

Re: kde bug tracker limited access?

Yeah, same on LOS 22 w/ Brave Nightly; I get a 403.

in termux I normally get a 200:

~ $ curl -sS -o /dev/null -w 'HTTP %{http_code}\n' 
  https://bugs.kde.org/
HTTP 200

But setting a browser User-Agent makes it return 403. Even a desktop Firefox UA gets a 403 through curl. IG it's evaluating more than just UAs, lol.

kokoko3k

Member

Registered: 2008-11-14

Posts: 2,479

Re: kde bug tracker limited access?

Maybe an extreme antispam measure...

---

Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,373

Re: kde bug tracker limited access?

Same here, vivialdi w/ chromium UA
Works w/ wget.

Should be a new development, I'm pretty sure I saw a KDE bug last month.
I guess that's another way to be bug free - they could also just make the account creation more cumbersome…

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

WorMzy

Administrator

From: Scotland

Registered: 2010-06-16

Posts: 13,682

Website

Re: kde bug tracker limited access?

Worked for Arch.

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

rubberycar

Member

Registered: 2026-10-16

Posts: 1

Website

Re: kde bug tracker limited access?

A 403 usually means the server is refusing access, but it doesn't necessarily mean the tracker is blocking mobile users specifically. Since it works from your home PC, I'd try comparing the same URL on mobile data and Wi-Fi, and checking whether a VPN or DNS filter changes the result. It could also be a restriction related to the site's security rules or the way the request is being handled. If others can reproduce it on different mobile networks, that would help narrow down the cause.

cryptearth

Member

Registered: 2024-02-03

Posts: 2,374

Re: kde bug tracker limited access?

have to give it a shot over the weekend

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,373

Re: kde bug tracker limited access?

It's certainly not a mobile thing.

wget works for me, vivaldi doesn't, nor does a dated FF 141.0.3
Using the wget UA in vivaldi also doesn't work - there's probably some profiling that hits if anything shows up that could submit a bug…

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

5hridhyan

Member

Registered: 2025-12-25

Posts: 1,097

Re: kde bug tracker limited access?

The situation might be different atm... It opens normally in Brave for me now.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,373

Re: kde bug tracker limited access?

Nope. Still 403 (but not tested brave)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

5hridhyan

Member

Registered: 2025-12-25

Posts: 1,097

Re: kde bug tracker limited access?

Maybe they've whitelisted cats only now. Perhaps, have you tried having a cat as your background?
Guess you guys have to wait if the secret credential didn't work

Jokes aside, it might just be a flaky server-side anti-bot measure acting aggressively and blocking legit users, which could also be time- and region-dependent

Last edited by 5hridhyan (2026-10-16 15:00:35)