[KDE Itinerary] [Bug 463452] interface text too small (Android)
https://bugs.kde.org/show_bug.cgi?id=463452 Yogesh changed: What|Removed |Added CC||yogesh-...@tuta.io --- Comment #1 from Yogesh --- (In reply to gumb from comment #0) > [..snip..] the text > size in the general interface is too small. It does not correspond to the > text in other apps and there doesn't appear to be any setting within the app > to change this. This affects me as well. @gumb, can you add a screenshot if possible? -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 415613] KLM Flight booking not imported from pdf ticket
https://bugs.kde.org/show_bug.cgi?id=415613 Yogesh changed: What|Removed |Added CC||yogesh-...@tuta.io --- Comment #3 from Yogesh --- This issue is affecting me too on the latest nightly version - 24.04.70 (f883f40). The PDF ticket is pretty barebones and does not have any QR code. I have mailed the PDF to you. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 486495] New: Importing Indian rail ticket PDF does not import departure time
https://bugs.kde.org/show_bug.cgi?id=486495 Bug ID: 486495 Summary: Importing Indian rail ticket PDF does not import departure time 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: yogesh-...@tuta.io Target Milestone: --- Created attachment 169128 --> https://bugs.kde.org/attachment.cgi?id=169128&action=edit Screenshot of itinerary on Android showing arrival time but no departure time SUMMARY Importing a rail ticket booked on IRCTC (the de-facto booking platform for Indian rail) fails to include the departure time for train trips. Arrival time is captured properly. SOFTWARE/OS VERSIONS Itinerary on Android : 24.07.70 (nightly - 5537e5a) Android - 12 Qt Version: 6.6.2 Engine Version: 6.1.40 PDF support: Poppler (23.09.0) Barcode decoder: ZXing (2.1.0) Extractors: 240 -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 473325] New: Display QR code for UK RSP-6 tickets as-is on itinerary
https://bugs.kde.org/show_bug.cgi?id=473325 Bug ID: 473325 Summary: Display QR code for UK RSP-6 tickets as-is on 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: yogesh-...@tuta.io Target Milestone: --- Created attachment 160928 --> https://bugs.kde.org/attachment.cgi?id=160928&action=edit Screenshot of QR decoder app showing contents of both Aztec codes SUMMARY The UK uses a custom rail ticket information encoding format RSP-6 which KDE itinerary correctly decodes into passenger and travel information. However KDE itinerary adds "aztec" in front of the ASCII contained in the Aztec 2D barcode before it recodes the ASCII into an Aztec 2D barcode displayed on the app. This makes ticket validations fail since the original QR code does not match with the KDE itinerary generated QR code. I used a qr code decoder app to compare the contents in both the original Aztec and the one generated by itinerary. Screencast attached. STEPS TO REPRODUCE 1. Scan a UK railway ticket from a booking app like "trainline". 2. Compare QR code from the app as well as KDE itinerary 3. Observe that they don't visually look the same and that their contents differ OBSERVED RESULT Contents of the original Aztec code and the one displayed on KDE itinerary are not identical. Contents in Aztec code displayed in KDE itinerary are prefixed with the string "aztec" EXPECTED RESULT Contents of the original Aztec code and the one displayed on KDE itinerary must be identical. ADDITIONAL INFORMATION Since the Contents of the Aztec code are actually a representation of cryptographically signed information, they have to be reproduced exactly. Screenshot attached -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 473325] Display QR code for UK RSP-6 tickets as-is on itinerary
https://bugs.kde.org/show_bug.cgi?id=473325 --- Comment #1 from Yogesh --- Mailed ticket samples privately. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 473326] New: Departure time is set wrong for QR scanned tickets
https://bugs.kde.org/show_bug.cgi?id=473326 Bug ID: 473326 Summary: Departure time is set wrong for QR scanned tickets 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: yogesh-...@tuta.io Target Milestone: --- SUMMARY When I scan a travel ticket into KDE itinerary, the time set as departure timeme is an hour later than the actual departure time. Tested with for UK RST-6 tickets. Not sure if this is related to processing daylight savings time quirks. STEPS TO REPRODUCE 1. Scan a UK train ticket into KDE itinerary 2. Compare departure times between original tickets and ones displayed in the app OBSERVED RESULT KDE itinerary sets departure time to one hour later than the actual departure time EXPECTED RESULT Departure times should be identical ADDITIONAL INFORMATION Samples emailed privately -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 473395] New: Itinerary on Android does not respect text size settings
https://bugs.kde.org/show_bug.cgi?id=473395 Bug ID: 473395 Summary: Itinerary on Android does not respect text size settings 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: yogesh-...@tuta.io Target Milestone: --- Created attachment 160969 --> https://bugs.kde.org/attachment.cgi?id=160969&action=edit itinerary appearance on Android SUMMARY Text sizes on KDE itinerary on Android are too small despite Android global text size settings being set for larger sizes. This is causing strain on the eyes. Making the font size even larger does not seem to have any effect on the app. There doesn't seem to be an app-specific setting to change the appearance so this problem cannot be circumvented currently, unfortunately. STEPS TO REPRODUCE 1. Open KDE itinerary on Android. Observe text size 2. Adjust font size in Android settings 3. Observe that text sizes on KDE itinerary do not change OBSERVED RESULT KDE itinerary font sizes are too small and fixed. No app specific appearance settings available to adjust font size EXPECTED RESULT Itinerary must respect Android system font size settings or implement app settings to adjust appearance including font sizes. ADDITIONAL INFORMATION Screenshots attacted -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 473395] Itinerary on Android does not respect text size settings
https://bugs.kde.org/show_bug.cgi?id=473395 --- Comment #1 from Yogesh --- Created attachment 160970 --> https://bugs.kde.org/attachment.cgi?id=160970&action=edit itinerary settings text size -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 473395] Itinerary on Android does not respect text size settings
https://bugs.kde.org/show_bug.cgi?id=473395 --- Comment #2 from Yogesh --- Created attachment 160971 --> https://bugs.kde.org/attachment.cgi?id=160971&action=edit Android font size settings -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 496050] New: Introduce a cancel button or modal close button for Account options
https://bugs.kde.org/show_bug.cgi?id=496050 Bug ID: 496050 Summary: Introduce a cancel button or modal close button for Account options Classification: Applications Product: Merkuro Version: 24.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: yogesh.giriku...@zoho.com CC: c...@carlschwan.eu Target Milestone: --- # SUMMARY In the settings under Accounts section, when clicking an account the user is presented with a modal with two options: Modify and Delete. There is no intuitive interaction that the user can do to exit the modal. Escape key works as does clicking outside the modal. But I think we should have a close button or a cancel button to make the behaviour clear. STEPS TO REPRODUCE 1. In Merkuro, open settings 2. Select Accounts section in the left pane 3. Click on an existing DAV (or other) account OBSERVED RESULT 1. User is presented with a Modify or Delete modal. EXPECTED RESULT One of three things should happen 1. There is a close modal button on the top right of the modal 2. ..or there should be a cancel button to cancel the action 3. ..or there should be text in the modal description stating "Esc key exits the modal" SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 467755] New: KDE Daemon crashed after windows starting and starting services.
https://bugs.kde.org/show_bug.cgi?id=467755 Bug ID: 467755 Summary: KDE Daemon crashed after windows starting and starting services. Classification: Applications Product: kdeconnect Version: 22.12.1 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: engg.yogeshku...@hotmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Application: kdeconnectd (22.12.1) (Compiled from sources) Qt Version: 5.15.3 Frameworks Version: 5.102.0 Operating System: Linux 5.14.0-289.el9.x86_64 x86_64 Windowing System: X11 Distribution: CentOS Stream 9 DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: KDE Daemon crashed after windows starting and starting services. The crash can be reproduced every time. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 0x7ff5fa2847e6 in KdeConnectConfig::deviceId() () from /lib64/libkdeconnectcore.so.22 #5 0x7ff5fa2892c7 in NetworkPacket::createIdentityPacket(NetworkPacket*) () from /lib64/libkdeconnectcore.so.22 #6 0x7ff5fa2754d0 in LanLinkProvider::broadcastToNetwork() () from /lib64/libkdeconnectcore.so.22 #7 0x7ff5f8adaf49 in QtPrivate::QSlotObjectBase::call (a=0x7ffd3e07fb40, r=, this=0x55589fe6d5e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #8 doActivate (sender=0x55589fd5c468, signal_index=3, argv=0x7ffd3e07fb40) at kernel/qobject.cpp:3886 #9 0x7ff5f8ad5ec7 in QMetaObject::activate (sender=, m=m@entry=0x7ff5f8d7e580 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd3e07fb40) at kernel/qobject.cpp:3946 #10 0x7ff5f8ade1ee in QTimer::timeout (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #11 0x7ff5f8ad1a2f in QObject::event (this=0x55589fd5c468, e=0x7ffd3e07fca0) at kernel/qobject.cpp:1336 #12 0x7ff5f97ae423 in QApplicationPrivate::notify_helper (this=, receiver=0x55589fd5c468, e=0x7ffd3e07fca0) at kernel/qapplication.cpp:3637 #13 0x7ff5f8aa7358 in QCoreApplication::notifyInternal2 (receiver=0x55589fd5c468, event=0x7ffd3e07fca0) at kernel/qcoreapplication.cpp:1064 #14 0x7ff5f8af7d43 in QTimerInfoList::activateTimers (this=0x55589fd3b150) at kernel/qtimerinfo_unix.cpp:643 #15 0x7ff5f8af863c in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:183 #16 0x7ff5f712fe2f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #17 0x7ff5f7184508 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #18 0x7ff5f712d5f3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #19 0x7ff5f8af8a48 in QEventDispatcherGlib::processEvents (this=0x55589fd3d000, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #20 0x7ff5f8aa5d62 in QEventLoop::exec (this=this@entry=0x7ffd3e07ff40, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #21 0x7ff5f8aae294 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #22 0x55589e04b0ae in main () [Inferior 1 (process 3522) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 467755] KDE Daemon crashed after windows starting and starting services.
https://bugs.kde.org/show_bug.cgi?id=467755 --- Comment #1 from yogesh kumar --- Created attachment 157548 --> https://bugs.kde.org/attachment.cgi?id=157548&action=edit KDE Daemon crashed after windows starting and starting services. kde connect application is used on cent os and installing from terminal .after installation this app is giving some error like "KDE Daemon crashed after windows starting and starting its services". Note: I am using this bag tracking system first time. but this bug tracking system is very hectic/irritating,just because of bug reporting is not in easy way .it's just like programming.and I thought everybody couldn't submitting bug this way or following set of instructions. It should be like that need mail account - application installed os version - saved bug report - simpal event discription . -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] [Wayland] KDE application don't remember maximization state after closing and re-opening
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #27 from Yogesh Marwaha --- It didn't work with Dolphin (Konsole too) for me also. Since other applications (which I use) seem to work fine, I tried some tricks. I manually resized application window and then closed it. Again started, maximised and closed. Afterwards it functioned as intended. PS: A bit unrelated, Firefox with custom title bar cannot determine that it's maximised. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420039] [XWayland]: Windows are often invisible and unusable
https://bugs.kde.org/show_bug.cgi?id=420039 Yogesh Marwaha changed: What|Removed |Added CC||yogeshm@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.
https://bugs.kde.org/show_bug.cgi?id=409919 Yogesh Marwaha changed: What|Removed |Added CC||yogeshm@gmail.com --- Comment #2 from Yogesh Marwaha --- Created attachment 121636 --> https://bugs.kde.org/attachment.cgi?id=121636&action=edit Screenshot 1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #4 from Yogesh Marwaha --- Created attachment 121638 --> https://bugs.kde.org/attachment.cgi?id=121638&action=edit Screenshot 3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #5 from Yogesh Marwaha --- I'll try to rephrase (or may be explain better) the problem being faced by OP and me. Prerequisite info: - Operating System: Arch Linux KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 Kernel Version: 4.19.57-1-lts OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 14.6 GiB Disclaimer: -- 1. Assuming that the OP wants to restore the application window (from maximized state) not minimize it; for me minimizing works fine. 2. This only seems to happen on KDE applications under wayland. Other non-KDE applications I use seem to work fine (e.g. Firefox, Gnu Cash, FileZilla, Chromium, Android Studio) Steps to reproduce: -- 1. Maximize a KDE application (Ref. screenshot 1) 2. Close it 3. Reopen the application (Note: Now the application seems to be opened with a size which would be if it was started maximized, but it does not actually start maximized, as is evident from titlebar buttons' state) (Ref. screenshot 2) 4. Try to maximize window by clicking on relevant button in titlebar. Window is resize in a weird way. (Ref. screenshot 3) If the window is resized (dragging from edges) before maximizing, it is maximized properly. Effects of behavior mentioned above: --- 1. Since the application window is started with a size of a maximized application (while not actually maximized as per KWin), it cannot be restored to a smaller size. 2. Since KWin thinks the window is not maximized, shown windows (i) have borders around them and (ii) are shown with a titlebar even if showing titlebars for maximized applications is disabled. Possible cause of problem: - Application indeed opens its window in maximized position but either KWin does not get the message or it forgets later that the window is maximized. I hope I'm clear enough. Regards. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #3 from Yogesh Marwaha --- Created attachment 121637 --> https://bugs.kde.org/attachment.cgi?id=121637&action=edit Screenshot 2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #7 from Yogesh Marwaha --- All right then. Since this bug affects multiple KDE applications (tested on dolphin, konsole, ksysguard, system settings, many KDE games) and needs to be worked on each one of them separately, does this bug needs to be reported separately for all those applications? If the answer is no, can you guide how can this be done. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410061] New: Dolphin fails to restore window state (on restart) to maximized when running on wayland
https://bugs.kde.org/show_bug.cgi?id=410061 Bug ID: 410061 Summary: Dolphin fails to restore window state (on restart) to maximized when running on wayland Product: dolphin Version: 19.04.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: yogeshm@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY Dolphin fails to restore window state (on restart) to maximized when running on wayland STEPS TO REPRODUCE 1. Maximize dophin window (Ref. screenshot 1) 2. Close it 3. Reopen dolphin (Note: Now the application seems to be opened with a size which would be if it was started maximized, but it does not actually start maximized, as is evident from titlebar buttons' state) (Ref. screenshot 2) 4. Try to maximize window by clicking on relevant button in titlebar. Window is resized in a weird way (Ref. screenshot 3). If the window is resized (dragging from edges) before maximizing, it is maximized properly. EFFECTS OF BEHAVIOR MENTIONED ABOVE 1. Since the application window is started with a size of a maximized application (while not actually maximized; evident from buttons on the titlebar), it cannot be restored to a smaller size. 2. Since, to the window manager, the window is not maximized, shown window (i) has border around it and (ii) is shown with a titlebar even if showing titlebar for maximized windows is disabled. SOFTWARE/OS/HARDWARE VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 Kernel Version: 4.19.57-1-lts OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 14.6 GiB ADDITIONAL INFORMATION This report originates from: https://bugs.kde.org/show_bug.cgi?id=409919 Another related bug report: https://bugs.kde.org/show_bug.cgi?id=391621 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410061] Dolphin fails to restore window state (on restart) to maximized when running on wayland
https://bugs.kde.org/show_bug.cgi?id=410061 --- Comment #2 from Yogesh Marwaha --- Created attachment 121657 --> https://bugs.kde.org/attachment.cgi?id=121657&action=edit Screenshot 2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410061] Dolphin fails to restore window state (on restart) to maximized when running on wayland
https://bugs.kde.org/show_bug.cgi?id=410061 --- Comment #1 from Yogesh Marwaha --- Created attachment 121656 --> https://bugs.kde.org/attachment.cgi?id=121656&action=edit Screenshot 1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410061] Dolphin fails to restore window state (on restart) to maximized when running on wayland
https://bugs.kde.org/show_bug.cgi?id=410061 --- Comment #3 from Yogesh Marwaha --- Created attachment 121658 --> https://bugs.kde.org/attachment.cgi?id=121658&action=edit Screenshot 3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #10 from Yogesh Marwaha --- I have filed a report against dolphin (https://bugs.kde.org/show_bug.cgi?id=410061). Can you have a look at screenshot 3 and confirm whether incorrect drawing along the right edge and bottom edge of the window is a fault of KWin or not? Judging from the mouse actions on that area, it is still part of the application window. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410061] Dolphin fails to restore window state (on restart) to maximized when running on wayland
https://bugs.kde.org/show_bug.cgi?id=410061 Yogesh Marwaha changed: What|Removed |Added Attachment #121657|0 |1 is obsolete|| --- Comment #5 from Yogesh Marwaha --- Created attachment 121662 --> https://bugs.kde.org/attachment.cgi?id=121662&action=edit Screenshot 2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410061] Dolphin fails to restore window state (on restart) to maximized when running on wayland
https://bugs.kde.org/show_bug.cgi?id=410061 Yogesh Marwaha changed: What|Removed |Added Attachment #121658|0 |1 is obsolete|| --- Comment #6 from Yogesh Marwaha --- Created attachment 121663 --> https://bugs.kde.org/attachment.cgi?id=121663&action=edit Screenshot 3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410061] Dolphin fails to restore window state (on restart) to maximized when running on wayland
https://bugs.kde.org/show_bug.cgi?id=410061 --- Comment #8 from Yogesh Marwaha --- This behavior is applicable for all KDE applications I have used/tried (dolphin, konsole, ksysguard, okular, gwenview, system settings, many KDE games (not tried all of them)) under wayland. Other non-KDE applications I use seem to work fine (e.g. Firefox, Gnu Cash, FileZilla, Chromium, Android Studio). -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 405558] New: Breeze dark theme shows dialog, tooltips etc. with light background
https://bugs.kde.org/show_bug.cgi?id=405558 Bug ID: 405558 Summary: Breeze dark theme shows dialog, tooltips etc. with light background Product: Breeze Version: 5.15.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: yogeshm@gmail.com Target Milestone: --- Created attachment 118856 --> https://bugs.kde.org/attachment.cgi?id=118856&action=edit Screenshot showing the problem SUMMARY Breeze dark theme shows dialog, tooltips etc. with light background. It was looking fine before I upgraded (in a nutshell... qt5 from 5.12.1 to 5.12.2 and plasma 5.15.2 to 5.15.3) STEPS TO REPRODUCE 1. Go to System Settings -> Workspace Theme -> Plasma Theme 2. Select Breeze Dark 3. Click on Apply 4. Open application launcher OR click on any applet which would open a dialog OR move mouse so as to show tooltip on any plasma icon/applet OBSERVED RESULT Even though dark theme was selected, background of dialog opened in Step 4 is light. EXPECTED RESULT Background should have been dark. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION I've tried clearing cache (~/.cache). I've tried other user account. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 405558] Breeze dark plasma theme shows dialog, tooltips etc. with light background
https://bugs.kde.org/show_bug.cgi?id=405558 Yogesh Marwaha changed: What|Removed |Added Summary|Breeze dark theme shows |Breeze dark plasma theme |dialog, tooltips etc. with |shows dialog, tooltips etc. |light background|with light background -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385880] Global Menu: does not work under wayland and causes a black screen when trying to enter its setting
https://bugs.kde.org/show_bug.cgi?id=385880 Yogesh Marwaha changed: What|Removed |Added CC||yogeshm@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 409919] [Wayland] KDE application don't remember maximization state after closing and re-opening
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #17 from Yogesh Marwaha --- Just updated my (Arch Linux) installation and the bug has disappeared (at least for all the KDE/non-KDE apps I use). A big thumbs-up for everyone involved! Operating System: Arch Linux KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 5.4.45-1-lts OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 409919] [Wayland] KDE application don't remember maximization state after closing and re-opening
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #20 from Yogesh Marwaha --- It seems to work for KDE apps(In reply to Nate Graham from comment #19) > Scratch that. It's only working for XWayland apps. Full Wayland apps are > still broken in the way described here. Is xeyes method valid to check whether an app is wayland native? If not, how can one verify that? PS: xeyes doesn't move on KDE apps and firefox (under wayland) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 409919] [Wayland] KDE application don't remember maximization state after closing and re-opening
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #15 from Yogesh Marwaha --- I tried to look for the problem and it looks like kxmlgui (or any part of KDE) is not to be blamed here. Following are the few observations (while on plasma-wayland session): - #1: Applications correctly save window size/maximized state on close, but they somehow cannot restore maximized window state #2: Vanilla Qt5 applications also fail to set maximized window state on open #3: For example, with 'qdbusviewer --platform xcb', window is maximized on open with 'qdbusviewer --platform wayland', window is not maximized on open (but still has proportions of maximized window) So, either Qt(wayland) is not setting the window state properly or there is a communication gap between KWin and Qt5 (wayland) clients. I've tried to look into the qtwayland source, but that's probably too much for me. Thanks for your time. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 397714] Glyph Characters cut off after most recent update - zsh themes
https://bugs.kde.org/show_bug.cgi?id=397714 Yogesh Kotadiya changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||yogeshkotadiya...@gmail.com --- Comment #2 from Yogesh Kotadiya --- Confirm! This is a really old bug, seems like the only KDE Terminal fails to render Double-Width glyph characters. The current solution is to use Mono fonts or add space after the glyphs in the rc file. https://imgur.com/GcEk1W7 With Mono Font https://imgur.com/tvNA5BU -- You are receiving this mail because: You are watching all bug changes.
[rekonq] [Bug 294129] Remove "rekonq" from main window of rekonq
https://bugs.kde.org/show_bug.cgi?id=294129 Yogesh Marwaha changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[rekonq] [Bug 294129] Remove "rekonq" from main window of rekonq
https://bugs.kde.org/show_bug.cgi?id=294129 --- Comment #5 from Yogesh Marwaha --- Since this feature request is irrelevant in today's context, I'm taking taking liberty to close this as "RESOLVED > WORKSFORME". Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 183458] Numpad (keypad) keys not mapped correctly when setting Global Shortcuts
https://bugs.kde.org/show_bug.cgi?id=183458 Yogesh Marwaha changed: What|Removed |Added CC||yogeshm@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kanagram] [Bug 377629] New: Unable to edit saved kvtml files since they are saved in different folder
https://bugs.kde.org/show_bug.cgi?id=377629
Bug ID: 377629
Summary: Unable to edit saved kvtml files since they are saved
in different folder
Product: kanagram
Version: 1.2
Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: general
Assignee: jpwhit...@kde.org
Reporter: yog...@karnatakaeducation.org.in
Target Milestone: ---
Creating and editing saved kvtml files through Kanagram configure menu was
possible in previous version of Kanagram that I had used in Ubuntu 14.04. Now
the current Kanagram version 1.2 in Ubuntu 16.04 doesn't allow you to do that.
Here's what I can see when I run kanagram from terminal and try to create own
vocabulary -
Checking path "/usr/share/apps/kvtml" for kvtml files
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
HSpellDict::HSpellDict: Init failed
No language dictionaries for the language: "en-GB"
org.kde.kanagram: Created game and engine helper
org.kde.kanagram: Set all context properties
org.kde.kanagram: Setup declarative engine
org.kde.kanagram: Set qml file location
Checking path "/usr/share/apps/kvtml" for kvtml files
"Cannot lock file /usr/share/apps/kvtml/en/hard.kvtml"
org.kde.kanagram: Saving file as
QUrl("file:///home/user/.local/share/kvtml/en/test.kvtml")
And after I close and re-open Kanagram again from terminal, I see this -
Checking path "/home/user/.local/share/apps/kvtml" for kvtml files
Checking path "/usr/share/apps/kvtml" for kvtml files
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
HSpellDict::HSpellDict: Init failed
Above suggests that Kanagram saves files .local/share/kvtml while it checks
path .local/share/apps/kvtml for kvtml files.
Vocabulary editor is one of the great feature of Kanagram and the current
documentation Kanagram also features this -
https://docs.kde.org/trunk5/en/kdeedu/kanagram/configuring.html#vocab-editor
--
You are receiving this mail because:
You are watching all bug changes.
