https://bugs.kde.org/show_bug.cgi?id=510487
Bug ID: 510487
Summary: KDE Itinerary from KDE F-droid repo hangs when doing a
route planning.
Classification: Applications
Product: KDE Itinerary
Version First 25.08.2
Reported In:
Platform: Android
OS: Android 13.x
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 185688
--> https://bugs.kde.org/attachment.cgi?id=185688&action=edit
Journey routing screen (start point, destination, time etc.)
SUMMARY
When I try to do a route planninng for "Budapest -> Ismaning" route, the
application first displays the results, but then slows down to the crawl as
more connections are found, and in the end hangs and needs to be restarted.
STEPS TO REPRODUCE
1. Install KDE Itinerary 25.08.02 from KDE's F-droid repo (Stable builds)
2. Open KDE Itinerary on the phone.
3. (enable all the public transport information sources and all optional
goodies in the settings).
4. Press the Trip planning button (middle one in the bottom drawer).
5. Start: (Hungary) BUDAPEST bus stop, Destination: Ismaning.
6. Departure or arrival time does not seem to influence the outcome, so
anything can be selected; mode of transportation: everything but the Aircraft.
7. Press the Search for journey button, the app loads and starts listing the
results.
8. After the results are listed, try scrolling the list to look for a specific
connection.
OBSERVED RESULT
App should be responsive, scrolling should be possible and in effect one of the
options should be selectable
EXPECTED RESULT
App hangs on the listing of possible connections.
SOFTWARE/OS VERSIONS
KDE Itinerary: 25.08.2
Android 13 (13.0)
KDE Frameworks: 6.18.0
Qt: 6.9.3 használatával, translated with: 6.9.2
Ismeretlen/Alapértelmezett
Build ABI: arm64-little_endian-lp64
Kernel: linux 5.10.233-android12-9-00001-g3f8134695cb5-ab13232202
ADDITIONAL INFORMATION
I don't know if the issue was present in the previous versions.
--
You are receiving this mail because:
You are watching all bug changes.
