[KDE Itinerary] [Bug 485559] New: Add train stop locations and directions on indoor maps for easier train changes
https://bugs.kde.org/show_bug.cgi?id=485559 Bug ID: 485559 Summary: Add train stop locations and directions on indoor maps for easier train changes Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Android OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: chris.seife...@onenetbeyond.org Target Milestone: --- As a frequent traveler, I often find myself rushing to change trains, especially when connection times are short. To make the process smoother and less stressful, I propose adding the following features to KDE Itinerary: 1. Display train stop locations on indoor maps: - When my itinerary includes a train journey, show the estimated stopping location of the train on the indoor map of the train station. - Indicate the direction of the train's movement (e.g., with an arrow) to help me understand where to go on the train when it's still moving that I can go to a door which will be close to the stairs or elevators to change trains faster. 2. Highlight stairs and elevators near the train stop: - Identify and highlight the nearest stairs and elevators to the estimated train stop location on the indoor map. - This will help me quickly locate the most convenient route to reach my connecting train or exit the station. 3. (Provide guidance to the estimated stairs/elevator location: - Based on the location of the train stop and the nearest stairs/elevator, guide me towards the estimated location of the stairs/elevator on the platform. - Display this information on the indoor map, allowing me to walk towards the stairs/elevator in advance. - This feature will be particularly useful when I have limited time to change trains, as it can help me board the connecting train more quickly and efficiently.) Benefits: - Reduces my stress and anxiety during train changes, especially when connection times are short. - Helps me navigate train stations more easily, especially in large or unfamiliar stations. - Saves time by guiding me to the most convenient stairs or elevators near my train stop. - Enhances my overall user experience by providing valuable information and guidance during my journey. Implementation: - Utilize the existing indoor map data of train stations provided by the app. - Obtain information on train stop locations. - (Develop algorithms to estimate the position of the nearest stairs/elevator based on the train stop location.) I appreciate your consideration of this feature request and look forward to any feedback or discussion. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 484310] platform (updating) issue
https://bugs.kde.org/show_bug.cgi?id=484310 reportthebug changed: What|Removed |Added Attachment #167651|This is the right platform, |This is the right platform description|I mixed up the picture | |description in the initial | |bug report, the wrong one | |was platform 3 | -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 484310] platform (updating) issue
https://bugs.kde.org/show_bug.cgi?id=484310 reportthebug changed: What|Removed |Added Attachment #167650|right platform |Wrong platform description|| -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 484310] platform (updating) issue
https://bugs.kde.org/show_bug.cgi?id=484310 reportthebug changed: What|Removed |Added Attachment #167651|wrong platform |This is the right platform, description||I mixed up the picture ||description in the initial ||bug report, the wrong one ||was platform 3 --- Comment #2 from reportthebug --- Comment on attachment 167651 --> https://bugs.kde.org/attachment.cgi?id=167651 This is the right platform, I mixed up the picture description in the initial bug report, the wrong one was platform 3 The right platform is 10 to Kassel, the wrong one is 3 to Fulda, so also the trains destination was wrong, but not the station I had to leave the train. Both trains left at the same time, maybe that's why it didn't update or got it wrong? I actually arrived 2 hours later because of the bug. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 484310] platform (updating) issue
https://bugs.kde.org/show_bug.cgi?id=484310 --- Comment #1 from reportthebug --- Created attachment 167651 --> https://bugs.kde.org/attachment.cgi?id=167651=edit wrong platform -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 484310] New: platform (updating) issue
https://bugs.kde.org/show_bug.cgi?id=484310 Bug ID: 484310 Summary: platform (updating) issue Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Android OS: Android 13.x Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: chris.seife...@onenetbeyond.org Target Milestone: --- Created attachment 167650 --> https://bugs.kde.org/attachment.cgi?id=167650=edit right platform Description: When using the KDE Itinerary application to plan a train journey, the initial saved connection information sometimes does not reflect the correct train platform. This can result in the user being 2 hours late for their train if they rely on the incorrect platform information. Reproduction Steps: 1. Search for a train connection using KDE Itinerary 2. The application provides the train platform information 3. Save the connection details 4. Search for the same connection again 5. The application now shows the correct train platform, but the initially saved connection still has the wrong platform information Expected Behavior: When the user searches for a train connection and saves the details, the platform information should be accurately reflected in the saved connection. If the platform information changes, the saved connection should be automatically updated to show the correct platform. Actual Behavior: The saved connection information does not always match the latest platform information shown by the application, even after performing a new search for the same connection. This can lead to the user arriving at the wrong platform and missing their train. Environment: - KDE Itinerary version: 24.04.70 -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 476388] New: Door to Door Navigation in KDE Itinerary
https://bugs.kde.org/show_bug.cgi?id=476388 Bug ID: 476388 Summary: Door to Door Navigation in KDE Itinerary Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: chris.seife...@onenetbeyond.org Target Milestone: --- Dear KDE Itinerary developers, I am writing to request a new feature for KDE Itinerary - door to door navigation. As an avid user of public transportation, I often find myself relying on GPS navigation to get around. However, I have to switch between different apps to navigate from my current location to my destination, and then from my destination to the nearest public transportation hub. This can be quite inconvenient, especially when I'm in a rush. Possible solutions Here are some possible solutions for implementing door-to-door navigation in KDE Itinerary: Integrate with external mapping services: KDE Itinerary could use external mapping services like OpenStreetMap to provide door-to-door directions. This would require developing a plugin or integration with these services, but it would provide the most accurate and up-to-date information. I believe that adding door to door navigation to KDE Itinerary would make it a more comprehensive travel planner. This feature would allow users to input their departure and arrival locations, and then receive step-by-step instructions on how to travel from one point to another. This would include information on the best routes, transportation options, and estimated travel times. Thank you for considering my request. I believe that door to door navigation would be a valuable addition to KDE Itinerary, and I would be happy to provide further feedback or assistance during the development process. Best regards -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 476356] New: Cancelled trains not indicated as such in itinerary view
https://bugs.kde.org/show_bug.cgi?id=476356 Bug ID: 476356 Summary: Cancelled trains not indicated as such in itinerary view Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Android OS: Android 13.x Status: REPORTED Severity: major Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: chris.seife...@onenetbeyond.org Target Milestone: --- Description: In KDE Itinerary, when viewing an itinerary, cancelled trains are not indicated as such. The only way to know if a train has been cancelled is by clicking on the connection and looking for the text that the train is cancelled. This can be inconvenient and time-consuming, especially when planning a trip with multiple trains and connections. Steps to reproduce: - Open KDE Itinerary and create a new itinerary or open an existing one. - Add a train connection to the itinerary that has been cancelled. - View the itinerary in the main window. - Observe that the cancelled train is not indicated as such in the itinerary view. - Click on the connection (or "connection view") to view the details of the train. - Observe that the train is marked as cancelled Expected behavior: - Cancelled trains should be indicated as such in the itinerary view, using a clear and visible marker such as a red "X" or strikethrough text. - The marker should be displayed next to the train connection in the itinerary view, so that it's easily visible without having to click on the connection. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 475191] New: Bus connection not displayed in itinerary when selecting alternative trip
https://bugs.kde.org/show_bug.cgi?id=475191 Bug ID: 475191 Summary: Bus connection not displayed in itinerary when selecting alternative trip Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Android OS: Android 7.x Status: REPORTED Severity: major Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: chris.seife...@onenetbeyond.org Target Milestone: --- I encountered an issue when using KDE itinerary to plan a trip. I had selected a trip by train and then clicked on an alternative that included a bus. However, when I selected the trip with the bus, the bus connection was not displayed in the itinerary. Normally, when I select a connection with a bus, it is accepted without any errors and displayed in the itinerary overview. Steps to reproduce: Open KDE itinerary. Search for a trip by train. Click on an alternative that includes a bus. Observe that the bus connection is not displayed in the itinerary. Expected behavior: The bus connection should be displayed in the itinerary, just like it is when selecting a connection with a bus normally. KDE Itinerary Version: 23.11.70 -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 474599] New: Issue with Importing Train Tickets into Connections in KDE Itinerary
https://bugs.kde.org/show_bug.cgi?id=474599 Bug ID: 474599 Summary: Issue with Importing Train Tickets into Connections in KDE Itinerary Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Android OS: Android 12.x Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: chris.seife...@onenetbeyond.org Target Milestone: --- When importing a train ticket via a QR code or manual input and then searching for and selecting a connection, the ticket is not automatically linked to the connection. This issue persists even when selecting a connection and then importing the ticket. Additionally, if the itinerary has multiple changes or trains, the imported ticket is located under each connection, requiring users to scroll down to locate and manage the ticket. Steps to Reproduce: Open KDE Itinerary. Import a train ticket using a QR code, manual input, or by selecting a ticket from the list. Search for and select a connection related to the imported ticket. Observe that the ticket is not automatically linked to the connection. Note that the ticket is located under each connection with multiple changes or trains, necessitating scrolling to find and manage the ticket. Expected Behavior: The train ticket should be automatically linked to the selected connection, ensuring proper organization and management of travel itineraries. It would be nice if you could fix this issue to automatically link imported tickets to their corresponding connections, improving the user experience and overall functionality of KDE Itinerary. Fixing this issue will make it easier to seamlessly organise and manage itineraries with multiple connections or trains. Thank you very much for your effort in the app :) -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 474197] Unable to Import Regional Train Tickets in France via QR Code and SNCF Online Tickets into KDE Itinerary
https://bugs.kde.org/show_bug.cgi?id=474197 --- Comment #2 from reportthebug --- (In reply to Volker Krause from comment #1) > Which region did you try? I know at least Normandie doesn't work as it's > using a QR code format we cannot decode yet and for which we have no > documentation. it's the Alsace (and Vosges) region -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 474197] New: Unable to Import Regional Train Tickets in France via QR Code and SNCF Online Tickets into KDE Itinerary
https://bugs.kde.org/show_bug.cgi?id=474197 Bug ID: 474197 Summary: Unable to Import Regional Train Tickets in France via QR Code and SNCF Online Tickets into KDE Itinerary Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Other OS: Android 7.x Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: chris.seife...@onenetbeyond.org Target Milestone: --- The KDE integration with regional train ticketing in France is not allowing users to import their SNCF online tickets or regional train tickets via QR code into the KDE itinerary. Steps to Reproduce: 1. Purchase a regional train ticket in France with SNCF. 2. Attempt to import the ticket into the KDE itinerary. 3. Observe that the ticket is not imported successfully (all SNCF Online Tickets are effected, using the QR code only regional train tickets are effected). Expected Behavior: The regional train tickets in France, both SNCF online tickets and those via QR code, should be importable into the KDE itinerary for seamless travel organization. KDE Itinerary version: 23.11.70 -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 474097] New: Departure platform not displayed for French trains in KDE Itinerary
https://bugs.kde.org/show_bug.cgi?id=474097 Bug ID: 474097 Summary: Departure platform not displayed for French trains in KDE Itinerary Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: chris.seife...@onenetbeyond.org Target Milestone: --- In KDE Itinerary, the departure platform for trains in France is not displayed, even though it is usually available shortly before departure. Is it possible to integrate this information into KDE Itinerary? Steps to reproduce: 1. Open KDE Itinerary and search for a train journey in France. 2. Click on a specific train to view its details. 3. Wait until the departure time is within aournd 30 minutes. 4. Note that the departure platform for the train is still not displayed. Expected behavior: The departure platform should be displayed for French trains in KDE Itinerary, similar to other train-related information such as schedule, fare, and availability. Notes: - This issue may be related to the data source used by KDE Itinerary, which might not provide departure platform information for French trains. - Integrating this feature may require modifications to the underlying code and data structures of KDE Itinerary. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 474096] New: Final Destination Not Displayed for Buses and Trains in KDE Itinerary
https://bugs.kde.org/show_bug.cgi?id=474096 Bug ID: 474096 Summary: Final Destination Not Displayed for Buses and Trains in KDE Itinerary Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: chris.seife...@onenetbeyond.org Target Milestone: --- Description: In KDE Itinerary, the final destination of a bus or train is not always displayed, making it difficult for users to determine which train or bus to take, especially when there are multiple options available. This issue has been reported by several users and can lead to confusion and inconvenience while planning a trip. Steps to Reproduce: 1. Open KDE Itinerary and search for a route between two cities that have multiple bus or train options. 2. Observe the list of results and notice that some buses or trains do not display their final destination. 3. Try selecting one of the buses or trains without a displayed final destination and observe that the details page also does not show the final destination. 4. Compare the behavior with other similar apps or websites that provide public transportation information to see how they handle this scenario. Expected Behavior: The final destination of each bus or train should be displayed clearly and consistently throughout the app, including on the initial search results page and on the details page for each route. Actual Behavior: The final destination of some buses or trains is not displayed, leaving users uncertain about which train or bus to take. Notes: - This issue may be related to data quality or availability, as different sources may provide incomplete or inconsistent information. - The issue may also be specific to certain regions or transit agencies, so testing with different locations and routes may help identify the scope of the problem. - Providing accurate and complete information about public transportation routes is essential for users who rely on these services, so resolving this issue would greatly improve the user experience. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 473321] New: Implementation of a "Now" button in the travel plan search
https://bugs.kde.org/show_bug.cgi?id=473321 Bug ID: 473321 Summary: Implementation of a "Now" button in the travel plan search Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: chris.seife...@onenetbeyond.org Target Milestone: --- Summary: Add a button to the KDE Itinerary application that allows users to search for currently available transport connections, similar to the functionality provided by e.g. long-pressing the selected time in the Transportr application. Background: If I want to search for a connection at the current time, the time and date of the last search destination is currently displayed in the search field. It would be helpful to add a feature that allows users to quickly search for connections that are available at the current time. This would provide a more seamless experience, especially for users who need to make last-minute changes to their plans or want to take advantage of immediate transport options. Proposed feature: 1. Implement a "Now" button within the KDE Itinerary search interface. This button should be clearly visible and easily accessible, preferably in the main search bar or results page. 2. When the user clicks the button, the application should automatically use the current time as the departure/arrival time for the search. The users should have the option to override the current time if they wish. 3. The search results should display the available connections departing or arriving within a short time frame (e.g. the next hour) and highlight the earliest options. Users can then select a connection and proceed to get more information if needed. Benefits: - Provides a quick and easy way for users to find immediate transport connections, reducing the need to manually adjust departure times. - Improves user experience by providing a more dynamic and flexible search option. - Allows users to take advantage of last minute transport opportunities or make spontaneous changes to their plans. By implementing this feature, KDE Itinerary can further establish itself as a versatile and user-friendly transport planning tool. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 473172] Enhancement Request: Switchable Connection Search Fields and Recently Searched Connections Feature
https://bugs.kde.org/show_bug.cgi?id=473172 --- Comment #2 from reportthebug --- (In reply to Volker Krause from comment #1) > This makes sense in general, but also lets me suspect that the existing > features to avoid the need for any of that aren't working. The search form > is supposed to be pre-filled with the location and date of the current > timeline position. So the idea is that you usually would only need to adjust > the time and destination. > > If that's not happening we need to fix it. If however your usage pattern or > usecase isn't covered by that it would be interesting to learn more about > how you use this feature to better understand how to support that best. My use case would be to search for the same direction several times after searching for another connection. When I search for a connection from point A to B, for example in the Öffi app, this is saved in a kind of history at the bottom of the search field, where I can then simply click on a last search route. See the picture: https://my.adminforge.de/apps/files_sharing/publicpreview/MgnaBNMSFxqMoSD?file=/=1576156=1366=768=true=f96025a514e7938066b8003724eabbcc -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 473176] New: Interactive map feature for viewing and selecting destinations
https://bugs.kde.org/show_bug.cgi?id=473176 Bug ID: 473176 Summary: Interactive map feature for viewing and selecting destinations Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: chris.seife...@onenetbeyond.org Target Milestone: --- I would like to propose the implementation of an interactive map showing the connections found by KDE Itinerary. This map could be similar to the one found in Öffi, which visualises the connections and even allows users to select their preferred destination. The addition of an interactive map could bring several benefits to KDE Itinerary users: 1. Visualise connections: An interactive map would allow users to visually understand the route and connections, making it easier to identify potential problems or alternative options, especially on a laptop, as the Deutsche Bahn, for example, has dropped its map view feature. 2. Destination selection: Users could select their destination directly on the map, providing a more intuitive way to select their desired location. 3. Improved user experience: Integrating a map into KDE Itinerary would make the application more user-friendly, especially for those unfamiliar with the public transport system in a particular area. 4. Users could better plan transfer locations. To implement this feature, I suggest considering the following: - Integration with OpenStreetMap. - Displaying the route and connections with clear markers and labels. - Allow users to interact with the map, such as zooming, panning and selecting destinations directly on the map. - The ability to toggle between the map view and the current list view of connections, allowing users to choose the view that best suits their needs. Thank you for taking this into consideration. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 472851] SSL Handshake Failed in KDE Itinerary - Indoor Train Station Map Issue
https://bugs.kde.org/show_bug.cgi?id=472851 --- Comment #11 from reportthebug --- (In reply to Volker Krause from comment #10) > Ok, that is likely the cause of this problem then. And this is not limited > to the indoor map, but would affect any API use on a server using Let's > Encrypt certificates. > > There are three possible options I can think of: > (1) You manually install the ISRG X1 certificate from > https://letsencrypt.org/certificates/, assuming that is possible on Android > at all. I installed the Self- and Cross-signed variant of ISRG Root X1 and also OCSP X1, but the error still occurs. > (2) We bundle an updated CA certificate set with all our network-using apps > (which is presumably what your browser does). That isn't hard technically, > but it's substantial compliance work to ensure we don't make things worse by > shipping a not trustworthy certificate. This does sound like the best option. Also, the error still occurs on my older phone, it works fine on my newer one. But it may be happening to other users who have phone configurations like my older phone, so a fix would be helpful. > (3) We add an option to ignore the error. That opens the door for > accidentally compromising security even for people with correct CA > certificates though. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 473123] Inclusive Transport Icon
https://bugs.kde.org/show_bug.cgi?id=473123 --- Comment #2 from reportthebug --- (In reply to Volker Krause from comment #1) > There's a train icon in the same series/style, but that's already in use by > KTrip: > https://invent.kde.org/utilities/ktrip/-/blob/master/src/org.kde.ktrip.svg That's a good point, if there is already a train icon in the same series/style used by KTrip, it might be better to choose a different icon to avoid confusion. Perhaps a possible solution could be to use a combination of transport icons, such as trains, buses and trams, to represent a wider range of sustainable travel options and also better reflect the diversity of public transport available to users. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 473172] New: Enhancement Request: Switchable Connection Search Fields and Recently Searched Connections Feature
https://bugs.kde.org/show_bug.cgi?id=473172 Bug ID: 473172 Summary: Enhancement Request: Switchable Connection Search Fields and Recently Searched Connections Feature Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: chris.seife...@onenetbeyond.org Target Milestone: --- I would like to submit a feature request to improve the user experience when searching for connections in the KDE Itinerary application. I would like to request the addition of two features: 1. Switchable connection search fields: It would be helpful if the application offered a switchable option to swap the "From" and "To" fields in the connection search fields. This would allow users to quickly enter their origin and destination without having to manually rearrange the fields, saving time and effort. 2. Recently searched connections feature: It is already possible to view a list of recently searched (train) stations. However, a quicker addition would be to implement a feature that displays a list of recently searched connections. This would allow users to easily access and reference their previous search results with one click, reducing the need to re-enter the same information. What do you think? -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 473123] New: Inclusive Transport Icon
https://bugs.kde.org/show_bug.cgi?id=473123 Bug ID: 473123 Summary: Inclusive Transport Icon Classification: Applications Product: KDE Itinerary Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: chris.seife...@onenetbeyond.org Target Milestone: --- SUMMARY *** The KDE Itinerary application currently displays an aeroplane icon as its app logo, representing the travel planning feature of the application. I propose that the icon be updated to better reflect other modes of transport, such as trains, which reflect the sustainability values of the KDE community. *** Rationale: In times of impending climate disaster, it is important to reflect environmental values. A more inclusive transport icon demonstrates sustainable travel options and encourages users to consider environmentally friendly alternatives to flying. Proposed solution: - Replace the current aeroplane icon with a more generic transport icon representing a combination of public transport vehicles such as trains, buses and trams. This change would make the app icon more inclusive and highlight the different sustainable travel options available to users. - Alternatively, if a more specific icon is desired, consider using an icon that represents a train, as trains are often a more sustainable alternative to air travel for long distance travel. Benefits: - Aligns with the promotion of sustainability and environmentally friendly practices. - Encourages users to consider green travel options when planning their trips. - Reinforces KDE's identity as a sustainability-conscious community. I'm not a designer, but I could try to help create an icon that would help promote and reflect an environmentally conscious attitude among users :) -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 472851] SSL Handshake Failed in KDE Itinerary - Indoor Train Station Map Issue
https://bugs.kde.org/show_bug.cgi?id=472851 --- Comment #9 from reportthebug --- (In reply to Volker Krause from comment #8) > Hm, that sounds like the device CA certificate chain is incomplete, and for > Android <= 7 and Let's Encrypt certificates that isn't even entirely > implausible. > > Can you check if your device has the "Internet Security Research Group > (ISRG) X1" certificate installed? Here this is under Settings > Security & > privacy > Encryption & credentials > Trusted credentials, but this can of > course vary from one Android version to the next. The mentioned certificate is not installed. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 472851] SSL Handshake Failed in KDE Itinerary - Indoor Train Station Map Issue
https://bugs.kde.org/show_bug.cgi?id=472851 --- Comment #7 from reportthebug --- (In reply to Volker Krause from comment #5) > Does opening https://maps.kde.org in the browser work without SSL errors? This is opening without SSL errors > As you seem to be using the nightly build, within the next 24h there should > be an update that should show additional details as part of that error > message. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 472851] SSL Handshake Failed in KDE Itinerary - Indoor Train Station Map Issue
https://bugs.kde.org/show_bug.cgi?id=472851 --- Comment #6 from reportthebug --- (In reply to Volker Krause from comment #4) > Git commit c51060a1a4c3fcdfdb5eb5f67693ba3faca3a4dd by Volker Krause. > Committed on 03/08/2023 at 17:25. > Pushed by vkrause into branch 'master'. > > Improve diagnostics for SSL errors > > M +11 -1src/map/loader/tilecache.cpp > > https://invent.kde.org/libraries/kosmindoormap/-/commit/ > c51060a1a4c3fcdfdb5eb5f67693ba3faca3a4dd Now the error is: "SSL handshake failed (The issuer certificate of a locally looked up certificate could not be found)" -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 472851] SSL Handshake Failed in KDE Itinerary - Indoor Train Station Map Issue
https://bugs.kde.org/show_bug.cgi?id=472851 --- Comment #3 from reportthebug --- (In reply to reportthebug from comment #2) > yes, any other network operations are working the same error occurs as well in the KDE OSM Indoor Map - app: also "SSL handshake failed." and no display of the map -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 472851] SSL Handshake Failed in KDE Itinerary - Indoor Train Station Map Issue
https://bugs.kde.org/show_bug.cgi?id=472851 --- Comment #2 from reportthebug --- yes, any other network operations are working -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 472851] New: SSL Handshake Failed in KDE Itinerary - Indoor Train Station Map Issue
https://bugs.kde.org/show_bug.cgi?id=472851 Bug ID: 472851 Summary: SSL Handshake Failed in KDE Itinerary - Indoor Train Station Map Issue Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Android OS: Android 7.x Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: chris.seife...@onenetbeyond.org Target Milestone: --- SUMMARY *** The KDE Itinerary application does not display the indoor map of train stations due to an SSL handshake failure *** STEPS TO REPRODUCE 1. Open KDE Itinerary. 2. Search for a train station with indoor mapping available. 3. Attempt to access the indoor map. OBSERVED RESULT An SSL handshake failure occurs, preventing the indoor map from loading. The error message displayed is as follows: "SSL handshake failed." EXPECTED RESULT The indoor map of the train station should be displayed without any issues. SOFTWARE/OS VERSIONS KDE_Itinerary Version: 23.11.70 ADDITIONAL INFORMATION Please note that this issue only occurs when trying to access the indoor train station map and does not affect other features of the KDE Itinerary application. I kindly request that this issue be addressed in a future update to ensure a seamless user experience when accessing indoor maps within the application. Thank you for your attention to this matter, and I look forward to the resolution of this bug. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 472809] New: Improve Train Accessibility Filtering in KDE Itinerary
https://bugs.kde.org/show_bug.cgi?id=472809 Bug ID: 472809 Summary: Improve Train Accessibility Filtering in KDE Itinerary Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Android OS: Android 12.x Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: chris.seife...@onenetbeyond.org Target Milestone: --- As a user of KDE Itinerary, I would like to request the following feature to improve the accessibility filtering for trains: Feature Request: - Add a new filter option for "Accessibility" in the search bar, allowing users to select specific types of accessibility features they require, such as wheelchair accessibility or bike storage. - Provide a clear and concise description of the accessibility features available at each train station, including information on the availability of elevators, ramps, and accessible restrooms. - Provide a map view of the train station and the surrounding area, highlighting the location of accessible entrances, exits, and amenities. Benefits: This feature would greatly improve the accessibility and usability of KDE Itinerary for users with disabilities, allowing them to easily find and book trains that meet their needs. It would also help to reduce frustration and anxiety associated with traveling with a disability, and increase the overall user experience as well as help travelers with a bike. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 472808] New: Support Arrival Time Search for Trains
https://bugs.kde.org/show_bug.cgi?id=472808 Bug ID: 472808 Summary: Support Arrival Time Search for Trains Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Android OS: Android 12.x Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: chris.seife...@onenetbeyond.org Target Milestone: --- Dear KDE Itinerary Team, I am writing to request a new feature in KDE Itinerary that would allow users to search for trains based on their arrival time. This feature would be useful for users who need to plan their schedules around the arrival times of trains. Currently, the application only allows users to search for trains based on their departure times, which can be limiting for some users. With the ability to search for trains based on arrival times, users would be able to more easily plan their trips and make the most of their time. Here are some specific details about the feature that I would like to suggest: - Search by arrival time: Users should be able to enter the arrival time of their destination station, and the application should return a list of trains that arrive at that time. - Search by time range: Users should be able to select a time range (e.g. "morning," "afternoon," "evening") to search for trains that arrive within that range. - Display arrival time in the search results: When searching for trains, the application should display the estimated arrival time for each train in the search results, so that users can quickly see which trains fit their schedule. - Sort search results by arrival time: Users should be able to sort the search results by arrival time, so that they can easily see which trains arrive first. I believe that this feature would enhance the user experience of KDE Itinerary Thank you for considering my request! Best regards, Chris -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 471197] New: Option to select Specific Transport Type in KDE Itinerary
https://bugs.kde.org/show_bug.cgi?id=471197 Bug ID: 471197 Summary: Option to select Specific Transport Type in KDE Itinerary Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: chris.seife...@onenetbeyond.org Target Milestone: --- SUMMARY *** [FEATURE REQUEST] Option to select Specific Transport Type in KDE Itinerary *** NOTE: This is a feature request, not a crash report. STEPS TO REPRODUCE 1. Open KDE Itinerary 2. Navigate to the trip planning feature 3. Enter the desired start and end locations OBSERVED RESULT There is no option to select a specific transport type (bus, regional traffic, long-distance traffic, etc.) EXPECTED RESULT A feature that allows users to specify the type of transport they prefer for their journey. SOFTWARE/OS VERSIONS KDE Itinerary 23.07.70 ADDITIONAL INFORMATION This feature can be beneficial for users who prefer certain types of transport or need to plan their journeys based on specific modes of transport due to personal preferences, accessibility needs, or other reasons. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469805] New: No Subfolders in Albums from External Drives During Face Recognition, and Inefficient Rescan Process
https://bugs.kde.org/show_bug.cgi?id=469805 Bug ID: 469805 Summary: No Subfolders in Albums from External Drives During Face Recognition, and Inefficient Rescan Process Classification: Applications Product: digikam Version: 8.0.0 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: chris.seife...@onenetbeyond.org Target Milestone: --- SUMMARY *** In digiKam, when using the face recognition feature from within the Album view, it appears that subfolders contained in albums from external drives are not being scanned. The software only scans the main folder, omitting any images that might be present in the subfolders. Additionally, when attempting to perform face recognition on large collections, if the process is interrupted and then restarted, it seems to start from the beginning each time. This makes scanning large collections impractical, especially if interruptions are necessary due to the size of the collection. *** STEPS TO REPRODUCE 1.Connect an external drive with an album that contains subfolders. 2.Open digiKam and navigate to the People view. 3.There is no subfolders for albums on external hard drives 4.Notice that only the main folder of the album is scanned, and the subfolders are ignored. Also if I scan for faces from within the Album-view, where the subfolders are actually shown the following happens 1. Connect an external drive with an album that contains subfolders. 2. Open digiKam and navigate to the Album view. 3. Initiate the face recognition process. 4. Subfolders are scanned. 5. Interrupt the face recognition process and close digiKam. 6. Reopen digiKam and resume the face recognition process. 7. Notice that the face-detection process restarts from the beginning, rather than picking up where it left off. OBSERVED RESULT 1. There is no subfolders for albums on external hard drives in People view 2. When the face recognition process is initiated from the Album view, only the main folder of the album is scanned. Subfolders within the album are ignored. 3. If the face recognition process is interrupted and then restarted, it starts over from the beginning, rather than resuming from where it left off. EXPECTED RESULT 1. When initiating the face recognition process from within people view, the software should scan not only the main album folders but also any subfolders, ensuring all images are processed. 2. The face recognition process should remember its progress between sessions or give an option in Album view, allowing for it to be paused and resumed without starting from the beginning each time. SOFTWARE/OS VERSIONS Linux Debian: 11.7.0 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.15.9 ADDITIONAL INFORMATION digiKam installed through flatpak -- You are receiving this mail because: You are watching all bug changes.
