[plasmashell] [Bug 422755] Memory leak in plasmashell on opening activity manager sidebar repeatedly
https://bugs.kde.org/show_bug.cgi?id=422755 --- Comment #3 from Kishore Gopalakrishnan --- I can reproduce this in a Wayland session as well. In X11, setting `export QSG_RENDER_LOOP="basic"` in `~/.xprofile` (suggested on some other reports of memory leaks) does not help. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422816] New: Screen edges desktop effect no longer works
https://bugs.kde.org/show_bug.cgi?id=422816 Bug ID: 422816 Summary: Screen edges desktop effect no longer works Product: kwin Version: 5.19.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- SUMMARY After upgrading to Plasma 5.19, the 'Screen Edges' desktop effect (that highlights edges or corners which have actions bound to them when the mouse cursor approached them) no longer works. STEPS TO REPRODUCE 1. Bind some action to a screen corner (like 'present windows') 2. Check that the 'screen edge' effect is enabled 3. Move the cursor to the screen corner/edge which you had configured. OBSERVED RESULT The action works, but there is no blue glow when the mouse approaches the edge/corner like in previous Kwin versions. EXPECTED RESULT The effect should work if enabled, or it should be removed if this decision is intentional. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 5.6.15-arch1-1 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422758] The 'page number' toolbar item sometimes is too narrow to fit the complete page number
https://bugs.kde.org/show_bug.cgi?id=422758 --- Comment #1 from Kishore Gopalakrishnan --- Sorry, I couldn't attach the PDF to the report, but it can be downloaded from here: https://ui.adsabs.harvard.edu/link_gateway/1978A&A65..281R/ADS_PDF -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422758] New: The 'page number' toolbar item sometimes is too narrow to fit the complete page number
https://bugs.kde.org/show_bug.cgi?id=422758 Bug ID: 422758 Summary: The 'page number' toolbar item sometimes is too narrow to fit the complete page number Product: okular Version: 1.10.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Created attachment 129201 --> https://bugs.kde.org/attachment.cgi?id=129201&action=edit Screenshot showing the issue SUMMARY If we open a PDF that has page numbers from say 100 to 105, the 'page number' item shows something like `[101] 2 of 5.`. The 101 inside the box gets cut off since the box is only wide enough to fit a single digit (see attached screenshot). STEPS TO REPRODUCE 1. Open the attached PDF. OBSERVED RESULT The page number entry box in the 'page bar' is not wide enough to show the page number completely. EXPECTED RESULT The page number entry box should be wide enough to fit SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Okular version: 1.10.1 (from Help > About Okular) ADDITIONAL INFORMATION The width is set correctly on PDFs that legitimately have 3-digit numbers of pages, so it looks like Okular is setting the width of the box wrongly based on the number of pages in the PDF, and not the internal page numbers used by the file. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422755] New: Memory leak in plasmashell on opening activity manager sidebar repeatedly
https://bugs.kde.org/show_bug.cgi?id=422755 Bug ID: 422755 Summary: Memory leak in plasmashell on opening activity manager sidebar repeatedly Product: plasmashell Version: 5.19.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kishor...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY If we repeatedly open the activity manager sidebar (the one that shows a list of activities and allows you to suspend or resume them) Plasma's memory usage increases without bound. The consumed memory does not seem to be freed even 30 minutes later. This is also reproducible by repeatedly opening and closing popups in the system tray. STEPS TO REPRODUCE 1. Open a Konsole window (to run the script) and a Ksysguard window (to monitor Plasma's memory usage) 2. Note the initial memory usage of the plasmashell process. 3. Run the following script in bash: ``` while true do sleep 0.1 qdbus org.kde.plasmashell /PlasmaShell toggleActivityManager done ``` OBSERVED RESULT Note that the memory keeps on increasing without bound. After perhaps 10 minutes, the memory usage is a few 100 MB greater than the initial value (I have observed it easily crossing 500 MB). If you kill the script, wait, and look at Plasma's memory usage after some time, you will still see that it is >= the value it had when you killed the script. EXPECTED RESULT Memory usage should not increase without bound. Even if it increases, it should at least be freed after some time. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 5.6.15-arch1-1 Display server: X Compositor rendering backend: Opengl 2.0 Graphics driver: amdgpu HARDWARE INFORMATION OS Type: 64-bit Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx Memory: 13.6 GiB of RAM Graphics Processor: AMD RAVEN ADDITIONAL INFORMATION I often observe that after a week or so of uptime, plasmashell's memory usage can be close to a GB, which may be due to the same underlying cause. You can also reproduce this same issue by repeatedly clicking on system tray applets for many minutes, but I have reported for the activities manager as is was the first thing I was able to figure out how to activate from a script. I was also able to reproduce this in a different user account with the default theme, window decorations, etc. POSSIBLE DUPLICATES bug 412865 bug 393929 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360333] New system tray: icons do not scale with panel height, stay very small
https://bugs.kde.org/show_bug.cgi?id=360333 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375951] locally integrated menus
https://bugs.kde.org/show_bug.cgi?id=375951 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 395695] [Privacy] Private activity usage is displayed by KRunner in standard activities
https://bugs.kde.org/show_bug.cgi?id=395695 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com --- Comment #2 from Kishore Gopalakrishnan --- *** Bug 382583 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 382583] 'Private' option for activities is not respected by recent documents tracker
https://bugs.kde.org/show_bug.cgi?id=382583 Kishore Gopalakrishnan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Kishore Gopalakrishnan --- *** This bug has been marked as a duplicate of bug 395695 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403563] Memory leak in plasma desktop (plasmashell)
https://bugs.kde.org/show_bug.cgi?id=403563 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421950] Page Up/Down overlap does not work on pdf file
https://bugs.kde.org/show_bug.cgi?id=421950 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 400496] kmail sometimes consumes 100% CPU for hours (in Sonnet::Highlighter)
https://bugs.kde.org/show_bug.cgi?id=400496 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 301176] Kile doesn't use system settings for default browser
https://bugs.kde.org/show_bug.cgi?id=301176 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416776] Colourschemes window accepts input when I press krunner shortcut (alt + space)
https://bugs.kde.org/show_bug.cgi?id=416776 Kishore Gopalakrishnan changed: What|Removed |Added Summary|Colourschemes window|Colourschemes window |accepts input when I press |accepts input when I press |krunner shortcut|krunner shortcut (alt + ||space) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416776] New: Colourschemes window accepts input when I press krunner shortcut
https://bugs.kde.org/show_bug.cgi?id=416776 Bug ID: 416776 Summary: Colourschemes window accepts input when I press krunner shortcut Product: systemsettings Version: 5.17.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: kishor...@gmail.com CC: jpwhit...@kde.org, mwoehlke.fl...@gmail.com Target Milestone: --- SUMMARY If the focus is on the 'edit colour scheme' button, pressing alt+space to invoke krunner results in the button also being activated. STEPS TO REPRODUCE 1. Open the colour schemes selection screen (Appearance > Colours). 2. Press the edit button on a colour scheme. 3. Close the edit window which opens. 4. Now press Alt+Space to invoke krunner. OBSERVED RESULT Krunner opens, but immediately closes since the edit button also somehow detects the 'space' key and opens the edit window. EXPECTED RESULT Krunner should open, and nothing should happen in the system settings application. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION I'm not sure if this is a bug in the system settings application, in krunner or in whatever handle keyboard shortcuts, but I'm reporting it here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412626] Plasmoids sometimes get 'stuck' while moving
https://bugs.kde.org/show_bug.cgi?id=412626 Kishore Gopalakrishnan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Kishore Gopalakrishnan --- Can't reproduce in Plasma 5.17.90. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416417] New: Kwin crash when activating desktop grid via screen corner
https://bugs.kde.org/show_bug.cgi?id=416417 Bug ID: 416417 Summary: Kwin crash when activating desktop grid via screen corner Product: kwin Version: 5.17.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Application: kwin_x11 (5.17.90) Qt Version: 5.14.0 Frameworks Version: 5.66.0 Operating System: Linux 5.4.12-arch1-1 x86_64 Windowing system: X11 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I moved the mouse toward the screen corner to activate the desktop grid effect. However, kwin does not crash if I do it again. I had an external monitor connected to my laptop at the time. The crash does not seem to be reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe480384840 (LWP 1320))] Thread 15 (Thread 0x7fe3a485a700 (LWP 14683)): #0 0x7fe485b2ec45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe486968cc4 in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x5597fa19ec40) at thread/qwaitcondition_unix.cpp:158 #2 0x7fe486968cc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x5597fa8511b0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7fe486968da2 in QWaitCondition::wait(QReadWriteLock*, QDeadlineTimer) (this=0x5597fa19ec90, readWriteLock=0x80, deadline=...) at thread/qwaitcondition_unix.cpp:240 #4 0x in () Thread 14 (Thread 0x7fe3cbfff700 (LWP 14682)): #0 0x7fe4881f4ae6 in ppoll () at /usr/lib/libc.so.6 #1 0x7fe486b91cc3 in normalizedTimespec(timespec&) (t=...) at kernel/qcore_unix_p.h:116 #2 0x7fe486b91cc3 in operator-(timespec const&, timespec const&) (t1=..., t1=..., t2=..., t2=...) at kernel/qcore_unix_p.h:145 #3 0x7fe486b91cc3 in time_update (timeout=..., start=..., tv=0x7fe3cbffebc0) at kernel/qcore_unix.cpp:114 #4 0x7fe486b91cc3 in qt_safe_poll(pollfd*, unsigned long, timespec const*) (fds=0x7fe3a007d838, nfds=1, timeout_ts=0x0) at kernel/qcore_unix.cpp:169 #5 0x7fe486b932dd in QVector::detach() (this=0x7fe3a0021eb0) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:102 #6 0x7fe486b932dd in QVector::end() (this=0x7fe3a0021eb0) at ../../include/QtCore/../../src/corelib/tools/qvector.h:214 #7 0x7fe486b932dd in QVector::last() (this=0x7fe3a0021eb0) at ../../include/QtCore/../../src/corelib/tools/qvector.h:245 #8 0x7fe486b932dd in QVector::takeLast() (this=0x7fe3a0021eb0) at ../../include/QtCore/../../src/corelib/tools/qvector.h:156 #9 0x7fe486b932dd in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:507 #10 0x7fe486b3c39c in QStack::pop() (this=0x5597f66b0040) at ../../include/QtCore/../../src/corelib/tools/qstack.h:61 #11 0x7fe486b3c39c in QEventLoop::LoopReference::~LoopReference (this=, __in_chrg=) at kernel/qeventloop.cpp:201 #12 0x7fe486b3c39c in QEventLoop::exec(QFlags) (this=, flags=...) at kernel/qeventloop.cpp:208 #13 0x7fe486961e62 in QThread::exec() (this=) at thread/qmutex.h:247 #14 0x7fe485274479 in () at /usr/lib/libQt5Qml.so.5 #15 0x7fe486962fd6 in QThreadPrivate::start(void*) (arg=0x5597fb341a00) at thread/qthread_unix.cpp:363 #16 0x7fe485b284cf in start_thread () at /usr/lib/libpthread.so.0 #17 0x7fe4881ff2d3 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7fe451718700 (LWP 6599)): #0 0x7fe4881f4ae6 in ppoll () at /usr/lib/libc.so.6 #1 0x7fe486b91cc3 in normalizedTimespec(timespec&) (t=...) at kernel/qcore_unix_p.h:116 #2 0x7fe486b91cc3 in operator-(timespec const&, timespec const&) (t1=..., t1=..., t2=..., t2=...) at kernel/qcore_unix_p.h:145 #3 0x7fe486b91cc3 in time_update (timeout=..., start=..., tv=0x7fe451717bc0) at kernel/qcore_unix.cpp:114 #4 0x7fe486b91cc3 in qt_safe_poll(pollfd*, unsigned long, timespec const*) (fds=0x7fe3a8018218, nfds=1, timeout_ts=0x0) at kernel/qcore_unix.cpp:169 #5 0x7fe486b932dd in QVector::detach() (this=0x7fe3a8014a00) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:102 #6 0x7fe486b932dd in QVector::end() (this=0x7fe3a8014a00) at ../../include/QtCore/../../src/corelib/tools/qvector.h:214 #7 0x7fe486b932dd in QVector::last() (this=0x7fe3a8014a00) at ../../include/QtCore/../../src/corelib/tools/qvector.h:245 #8 0x7fe486b932dd in QVector::takeLast() (this=0x7fe3a8014a00) at ../../include/QtCore/../../src/corelib/tools/qvector.h:156 #9 0x7fe486b932dd in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at kernel/qeventdi
[kscreenlocker] [Bug 407767] It is possible to switch back and forth unlocked user sessions via TTY
https://bugs.kde.org/show_bug.cgi?id=407767 Kishore Gopalakrishnan changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Kishore Gopalakrishnan --- (In reply to Nate Graham from comment #1) > Can you reproduce this issue in Plasma 5.17? I cannot. I can reproduce this with Plasma 5.17.5, frameworks 5.65, and Qt 5.14. This is on Arch Linux. With two sessions open, switching via krunner locks the session switching was done from, but if I switch using Ctrl+Alt+F?, the session does not get locked -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413934] High CPU usage when switching wallpaper as slideshow
https://bugs.kde.org/show_bug.cgi?id=413934 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413591] New: Okular saves annotations with GMT instead of system time
https://bugs.kde.org/show_bug.cgi?id=413591 Bug ID: 413591 Summary: Okular saves annotations with GMT instead of system time Product: okular Version: 1.8.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- SUMMARY Okular saves timestamps in GMT in annotations, even though it displays time in the local timezone while initially creating the annotation. STEPS TO REPRODUCE 1. Set your timezone to something other than GMT. 2. Open a PDF and create a 'popup note' annotation. 3. Note that the time displayed on the top-right of the popup is the current time in the local timezone. 4. Type something and exit the box by pressing 'esc'. 5. Save the PDF and wait for Okular to reload it. 6. Double-click on the recently created annotation. 7. Note that the displayed time on the top-right of the popup now matches with GMT, and not with your current timezone. OBSERVED RESULT Annotation is saved with GMT timestamp. EXPECTED RESULT Annotation timestamp should contain local time. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION Output of `timedatectl`: ``` Local time: Tue 2019-10-29 16:16:14 IST Universal time: Tue 2019-10-29 10:46:14 UTC RTC time: Tue 2019-10-29 10:46:14 Time zone: Asia/Kolkata (IST, +0530) System clock synchronized: yes NTP service: active RTC in local TZ: no ``` My locale settings in 'Settings > Regional Settings > Formats' all correspond to 'India - English (en_IN)'. Possible duplicate of bug 400473, but I haven't changed my timezone in years. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 413505] New: Alt accelelerator does not work for 'OK' in the 'Set priority' window
https://bugs.kde.org/show_bug.cgi?id=413505 Bug ID: 413505 Summary: Alt accelelerator does not work for 'OK' in the 'Set priority' window Product: ksysguard Version: 5.17.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- SUMMARY In the window that allows you to set the niceness and IO priority for a process, the alt-accelerator does not work for 'OK', but it works for 'Cancel'. STEPS TO REPRODUCE 1. Open ksysguard. 2. Right-click on a process and select 'set priority'. 3. Press 'Alt'. 4. Note that 'O' is underlined in the 'OK' button, while 'C' is underlined in the 'Cancel' button. 5. Press 'Alt+O'. 6. Press 'Alt+C'. OBSERVED RESULT 'Alt+O' does not activate the 'OK' button, but 'Alt+C' activates the 'Cancel' button. EXPECTED RESULT Alt-accelerator should work for 'OK' as well. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413503] New: Applications list in the sidebar does not update properly when a search is performed
https://bugs.kde.org/show_bug.cgi?id=413503 Bug ID: 413503 Summary: Applications list in the sidebar does not update properly when a search is performed Product: plasmashell Version: 5.17.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: kishor...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 123509 --> https://bugs.kde.org/attachment.cgi?id=123509&action=edit Screenshot showing the issue. SUMMARY In the window that allows us to configure notifications per-application, typing a search query in the sidebar and then clearing it does not update the sidebar properly. STEPS TO REPRODUCE 1. Open the notification settings and go to 'configure applications' 2. Type a query in the searchbox which matches some item (eg. 'acc') 3. Clear the searchbox by clicking the 'clear' button 4. Note that some items in the 'system services' section have the same name as those in the 'applications' section. 5. Click one of the duplicated items in the 'system services' section. 6. Note that the main area shows the configuration for the system service which should've been in the location you were clicking, and not the erroneously duplicated label (see attached screenshot) 7. Typing a query that doesn't match anything (eg. 'asdf') in the searchbox and clearing seems to fix this till the next occurrence. OBSERVED RESULT Item names in the sidebar don't get updated properly when the query is cleared. EXPECTED RESULT Item names should get updated properly when the search query is cleared. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413500] New: Ampersands in category names are not shown in the 'desktop actions' application menu
https://bugs.kde.org/show_bug.cgi?id=413500 Bug ID: 413500 Summary: Ampersands in category names are not shown in the 'desktop actions' application menu Product: plasmashell Version: 5.17.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kishor...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 123508 --> https://bugs.kde.org/attachment.cgi?id=123508&action=edit Screenshot of the menu. SUMMARY In 'Configure Desktop > Mouse Actions', there is an option to bind an application menu to a mouse action on the desktop. The menu that appears when you do this does not display ampersands in category names (eg. `Science & Maths`, `Lost & Found`; see attached screenshot). STEPS TO REPRODUCE 1. Right click on Desktop > Configure Desktop > Mouse Actions. 2. Bind 'Application Launcher' to middle-click. 3. Middle-click on desktop. OBSERVED RESULT Category names are displayed stripping ampersands. EXPECTED RESULT Categroy names should be displayed with ampersands. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION I couldn't figure out any other place where this menu is used. The ampersands are displayed properly in the launcher plasmoids. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 413506] Kile crash while removing template
https://bugs.kde.org/show_bug.cgi?id=413506 --- Comment #1 from Kishore Gopalakrishnan --- Note: the crash happens on clicking 'OK' after selecting the template. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 413506] New: Kile crash while removing template
https://bugs.kde.org/show_bug.cgi?id=413506 Bug ID: 413506 Summary: Kile crash while removing template Product: kile Version: 2.9.93 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: michel.lud...@kdemail.net Reporter: kishor...@gmail.com Target Milestone: --- Application: kile (2.9.93) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.7-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I opened Kile, clicked 'File > Remove template', and selected a template I had previously created. The crash can be reproduced every time. -- Backtrace: Application: Kile (kile), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8bb30e8d00 (LWP 57545))] Thread 6 (Thread 0x7f8b9700 (LWP 57550)): #0 0x7f8bb8f85c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f8ba89b250c in ?? () from /usr/lib/dri/i965_dri.so #2 0x7f8ba89b2108 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7f8bb8f7f4cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f8bbbf932d3 in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7f8baadee700 (LWP 57549)): #0 0x7f8bb8f85c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f8bb920 in QWaitConditionPrivate::wait (deadline=..., this=0x55592a9a9270) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x55592a9d5e50, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f8bb9266752 in QWaitCondition::wait (this=this@entry=0x55592a9d5e58, mutex=mutex@entry=0x55592a9d5e50, time=time@entry=18446744073709551615) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7f8bbc30d049 in KileParser::ParserThread::run (this=0x55592a9d5e20) at /usr/src/debug/kile-2.9.93/src/parser/parserthread.cpp:169 #5 0x7f8bb92605b0 in QThreadPrivate::start (arg=0x55592a9d5e20) at thread/qthread_unix.cpp:360 #6 0x7f8bb8f7f4cf in start_thread () from /usr/lib/libpthread.so.0 #7 0x7f8bbbf932d3 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f8bab5ef700 (LWP 57548)): #0 0x7f8bb8f85c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f8bb920 in QWaitConditionPrivate::wait (deadline=..., this=0x55592aa356c0) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x55592aa32a60, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f8bb9266752 in QWaitCondition::wait (this=this@entry=0x55592aa32a68, mutex=mutex@entry=0x55592aa32a60, time=time@entry=18446744073709551615) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7f8bbc30d049 in KileParser::ParserThread::run (this=0x55592aa32a30) at /usr/src/debug/kile-2.9.93/src/parser/parserthread.cpp:169 #5 0x7f8bb92605b0 in QThreadPrivate::start (arg=0x55592aa32a30) at thread/qthread_unix.cpp:360 #6 0x7f8bb8f7f4cf in start_thread () from /usr/lib/libpthread.so.0 #7 0x7f8bbbf932d3 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f8bb10c1700 (LWP 57547)): #0 0x7f8bbbf889ef in poll () from /usr/lib/libc.so.6 #1 0x7f8bb5034170 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f8bb5034241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f8bb9486a1c in QEventDispatcherGlib::processEvents (this=0x7f8ba4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f8bb942d4ec in QEventLoop::exec (this=this@entry=0x7f8bb10c0d30, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f8bb925f385 in QThread::exec (this=this@entry=0x7f8bba3cb080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f8bba347b37 in QDBusConnectionManager::run (this=0x7f8bba3cb080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x7f8bb92605b0 in QThreadPrivate::start (arg=0x7f8bba3cb080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:360 #8 0x7f8bb8f7f4cf in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f8bbbf932d3 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f8bb233f700 (LWP 57546)): #0 0x7f8bbbf889ef in poll () from /usr/lib/libc.so.6 #1 0x7f8bb75de630 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f8bb75e02db in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f8bb2c6f101 in QXcbEventQueue::run (this=0x55592a6d2360) at qxcbeventqueue.cpp:228 #4 0x7f8bb92605b0 in QThreadPrivate::start (arg=0x55592a6d2360) at t
[plasmashell] [Bug 347770] notification number not alligned
https://bugs.kde.org/show_bug.cgi?id=347770 --- Comment #3 from Kishore Gopalakrishnan --- This bug is no longer valid (as of 5.17) since the number is not displayed in the system tray icon. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412952] Dolphin seems to add extra quotes when deleting trailing quote
https://bugs.kde.org/show_bug.cgi?id=412952 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413478] New: Dolphin should not try to enter invalid gzip archive.
https://bugs.kde.org/show_bug.cgi?id=413478 Bug ID: 413478 Summary: Dolphin should not try to enter invalid gzip archive. Product: dolphin Version: 19.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kishor...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 123494 --> https://bugs.kde.org/attachment.cgi?id=123494&action=edit Screenshot showing the issue SUMMARY If we try to browse an invalid gzip archive by opening it in Dolphin, Dolphin correctly complains about 'invalid protocol', but then it actually updates the location in the location bar to show that we are inside the archive (see attached screenshot), while still showing the contents of the parent folder. STEPS TO REPRODUCE 1. Create an invalid gzip archive (run the command `touch text.gzip`) 2. Open this archive by single/double-clicking it (depends on your settings) OBSERVED RESULT Note that while the location in the location bar tells us we are inside the archive (/home/kishore/Downloads/test.gz), the main pane just shows the contents of the parent folder (/home/kishore/Downloads). EXPECTED RESULT When we click on an invalid archive which is detected as such by Dolphin, Dolphin should not actually enter it. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63 Qt Version: 5.13.1 ADDITIONAL INFORMATION 'Back' and 'Up' items in the 'Go' menu also do not work properly once Dolphin enters such an archive. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413475] New: Dolphin detects wrong location for device if it is bind-mounted
https://bugs.kde.org/show_bug.cgi?id=413475 Bug ID: 413475 Summary: Dolphin detects wrong location for device if it is bind-mounted Product: dolphin Version: 19.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kishor...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I have a partition in which certain folders are bind-mounted to folders in my home directory. When I click this device in the dolphin sidebar, it opens one of the folders which have been bind-mounted, instead of the actual device. The directory structure is schematically as follows: /run/media/kishore/oldhome (mountpoint of the partition, which is named `Arch-home`) |- Documents |- some other directories `Documents` is bind-mounted to /home/kishore/Documents STEPS TO REPRODUCE: 1. Mount a partition (say 'Arch-home') which has multiple folders. 2. Bind-mount one of the folders (say 'Documents') to a folder in your home directory. 3. Click on the partition name in the 'devices' section of Dolphin's sidebar. OBSERVED RESULT When I click the item labelled 'Arch-home' in the dolphin sidebar (it appears under 'Devices'), I am taken to /home/kishore/Documents, instead of /run/media/kishore/oldhome (Note that the contents of these two locations are not the same, so it is not merely about displaying the right path in the addressbar.) EXPECTED RESULT Dolphin should correctly open the actual partition. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION Bug 330563 is a similar bug, but for krusader. Relevant portion of fstab: #Old home. UUID=9ae18791-bede-41a9-904f-dbea4d3993da /run/media/kishore/oldhome ext4 defaults,rw,relatime,nofail 0 0 #Bind mounts for ~ /run/media/kishore/oldhome/kishore/Downloads/home/kishore/Downloads none defaults,bind,uid=1000,gid=1000,nofail0 0 /run/media/kishore/oldhome/kishore/Documents/home/kishore/Documents none defaults,bind,uid=1000,gid=1000,nofail0 0 /run/media/kishore/oldhome/kishore/Pictures /home/kishore/Pictures none defaults,bind,uid=1000,gid=1000,nofail0 0 /run/media/kishore/oldhome/kishore/build/home/kishore/build none defaults,bind,uid=1000,gid=1000,nofail0 0 Output of `mount -t ext4` ``` /dev/sda2 on / type ext4 (rw,relatime) /dev/sda3 on /home type ext4 (rw,relatime,data=ordered) /dev/sdb14 on /run/media/kishore/oldhome type ext4 (rw,relatime) /dev/sdb14 on /home/kishore/Documents type ext4 (rw,relatime) /dev/sdb14 on /home/kishore/Downloads type ext4 (rw,relatime) /dev/sdb14 on /home/kishore/Pictures type ext4 (rw,relatime) /dev/sdb14 on /home/kishore/build type ext4 (rw,relatime) ``` Output of `lsblk` ``` NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 111.8G 0 disk ├─sda18:10 512M 0 part ├─sda28:2050G 0 part / ├─sda38:30 49.3G 0 part /home └─sda48:4012G 0 part [SWAP] sdb 8:16 0 931.5G 0 disk ├─sdb18:17 0 500M 0 part /boot ├─sdb28:18 040M 0 part ├─sdb38:19 0 128M 0 part ├─sdb48:20 0 750M 0 part ├─sdb58:21 070G 0 part ├─sdb78:23 0 734.7G 0 part /run/media/kishore/Files ├─sdb12 8:28 0 8.4G 0 part ├─sdb13 8:29 035G 0 part ├─sdb14 8:30 070G 0 part /run/media/kishore/oldhome └─sdb16 259:0012G 0 part [SWAP] ``` If I type the actual mountpoint into the addressbar, it shows me the correct location as expected. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 413473] New: Kile complains about failure and deletes file if one tries to overwrite an existing template.
https://bugs.kde.org/show_bug.cgi?id=413473 Bug ID: 413473 Summary: Kile complains about failure and deletes file if one tries to overwrite an existing template. Product: kile Version: 2.9.93 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: user interface Assignee: michel.lud...@kdemail.net Reporter: kishor...@gmail.com Target Milestone: --- Created attachment 123492 --> https://bugs.kde.org/attachment.cgi?id=123492&action=edit Screenshot of the error message. SUMMARY If we try to overwrite (through File > Create template from document) a previously created user template, Kile claims that creation failed and then deletes the file the user used to create the template. However, the template modification actually succeeds. STEPS TO REPRODUCE 1. Create a template. 2. Create a new .tex document using this template and make some changes in it. 3. File > Create template from document. 4. Choose to overwrite the existing template. OBSERVED RESULT Kile throws up an error saying 'failed to create template' (see attached screenshot). Once we dismiss the error, it then complains that the file has been deleted by another program. However, if we check the modified template by creating a new document, we find that the changes we made have actually been applied to the template, contrary to what the error message claimed. EXPECTED RESULT Kile should not falsely claim template creation failed. It should also not delete the document the user used to create the template. SOFTWARE/OS VERSIONS Linus distro: Arch Linux KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION If we try to create a new template (using a previously nonexistent template name), it succeeds and does not delete the document used, as expected. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413018] Plasma crashes in slideshow
https://bugs.kde.org/show_bug.cgi?id=413018 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 --- Comment #21 from Kishore Gopalakrishnan --- (In reply to Webcapcha from comment #18) > Created attachment 123229 [details] > Checkboxes are black > > Same for me. Almost every site has black checkboxes with Breeze Dark Plasma > Style Theme. > > Breeze Light looks like good The original bug occurs in Breeze light too. Yours sounds unrelated. You might find this useful: https://stackoverflow.com/questions/51684455/firefox-default-colour-scheme-for-inputs-forms -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412895] Attachment detector should not trigger while saving as draft
https://bugs.kde.org/show_bug.cgi?id=412895 Kishore Gopalakrishnan changed: What|Removed |Added Summary|Attachment detector should |Attachment detector should |trigger while saving as |not trigger while saving as |draft |draft -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412895] New: Attachment detector should trigger while saving as draft
https://bugs.kde.org/show_bug.cgi?id=412895 Bug ID: 412895 Summary: Attachment detector should trigger while saving as draft Product: kmail2 Version: 5.12.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- SUMMARY The attachment detector triggers even if one saves as draft, and one has to select the confusingly worded 'send as is' to actually save the draft without attaching a file. STEPS TO REPRODUCE 1. File > New > New Message 2. Type 'attachment' in the message body 3. You get a blue bar that reminds you to attach a file 4. Click Message > Save as Draft 5. You get a warning box with three options: 'attach file', 'send as is', or 'cancel'. 6. Clicking 'send as is' allows the draft to be saved without attaching a file. OBSERVED RESULT One has to click 'send as is' to save the draft, which is a bit confusing for the user. EXPECTED RESULT The attachment detector should only trigger while sending the message, but not while saving as draft. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 412868] New: Ksysguard crash on exit
https://bugs.kde.org/show_bug.cgi?id=412868 Bug ID: 412868 Summary: Ksysguard crash on exit Product: ksysguard Version: 5.16.90 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Application: ksysguard (5.16.90) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.3.1-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: Ksysguard crashed when I was clsoing it. I haven't been able to reproduce it consistently, but the crash happens a few times each day. The crash can be reproduced sometimes. -- Backtrace: Application: System Monitor (ksysguard), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f118a0beb00 (LWP 405359))] Thread 4 (Thread 0x7f1181699700 (LWP 405362)): #0 0x7f119ecd6667 in poll () from /usr/lib/libc.so.6 #1 0x7f1191f34130 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f1191f34201 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f119d3a5a1c in QEventDispatcherGlib::processEvents (this=0x7f1174000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f119d34c4ec in QEventLoop::exec (this=this@entry=0x7f1181698a70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f119d17e385 in QThread::exec (this=this@entry=0x7f119d708080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f119d684b37 in QDBusConnectionManager::run (this=0x7f119d708080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x7f119d17f5b0 in QThreadPrivate::start (arg=0x7f119d708080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:360 #8 0x7f119432557f in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f119ece10e3 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f11832d0700 (LWP 405361)): #0 0x7f119432b415 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f118357bf5c in ?? () from /usr/lib/dri/i965_dri.so #2 0x7f118357bb58 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7f119432557f in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f119ece10e3 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f1189327700 (LWP 405360)): #0 0x7f119ecd6667 in poll () from /usr/lib/libc.so.6 #1 0x7f119477d630 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f119477f2db in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f1189c41101 in QXcbEventQueue::run (this=0x5627ca9c7b70) at qxcbeventqueue.cpp:228 #4 0x7f119d17f5b0 in QThreadPrivate::start (arg=0x5627ca9c7b70) at thread/qthread_unix.cpp:360 #5 0x7f119432557f in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f119ece10e3 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f118a0beb00 (LWP 405359)): [KCrash Handler] #6 0x7f119df92f39 in QLabelPrivate::clearContents (this=this@entry=0x5627cae13d60) at widgets/qlabel.cpp:1302 #7 0x7f119df93a9c in QLabel::setText (this=0x5627cadd00d0, text=...) at widgets/qlabel.cpp:293 #8 0x7f119ee1dba4 in TopLevel::answerReceived (this=0x5627cadbbaf0, id=, answerList=...) at /home/kishore/build/build/ksysguard/src/ksysguard-5.16.90/gui/ksysguard.cpp:466 #9 0x7f119ea7e0d8 in KSGRD::SensorAgent::processAnswer (this=0x5627caea6450, buf=, buflen=) at /home/kishore/build/build/libksysguard/src/libksysguard-5.16.90/ksgrd/SensorAgent.cpp:91 #10 0x7f119ea857c0 in KSGRD::SensorShellAgent::msgRcvd (this=0x5627caea6450) at /usr/include/qt/QtCore/qarraydata.h:208 #11 0x7f119d379b70 in QtPrivate::QSlotObjectBase::call (a=0x7ffd4e065780, r=0x5627caea6450, this=0x5627cae0fc90) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #12 QMetaObject::activate (sender=0x5627caf1acd0, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3789 #13 0x7f119d2bff3b in QProcess::readyReadStandardOutput (this=this@entry=0x5627caf1acd0, _t1=...) at .moc/moc_qprocess.cpp:367 #14 0x7f119d2c6982 in QProcessPrivate::tryReadFromChannel (this=0x5627cae038c0, channel=0x5627cae039e8) at io/qprocess.cpp:1078 #15 0x7f119d2c6ce2 in QProcessPrivate::_q_canReadStandardError (this=) at io/qprocess.cpp:1097 #16 QProcess::qt_static_metacall (_o=, _c=, _id=, _a=0x7ffd4e065930) at .moc/moc_qprocess.cpp:210 #17 0x7f119d379a11 in QMetaObject::activate (sender=0x5627caf273f0, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3809 #18 0x7f119d386652 in QSocketNotifier::activated (this=this@entry=0x5627caf273f0, _t1=, _t2=...) at .moc/moc_qsocketnotifie
[krunner] [Bug 412627] New: Dsiplay properly rounded results instead of interval()
https://bugs.kde.org/show_bug.cgi?id=412627 Bug ID: 412627 Summary: Dsiplay properly rounded results instead of interval() Product: krunner Version: 5.16.90 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: calculator Assignee: k...@privat.broulik.de Reporter: kishor...@gmail.com Target Milestone: --- SUMMARY For some calculations, the calculator displays a bounding interval for the answer, like `interval(1.386294361119890, 1.386294361119891)`. This is difficult to read at a glance. Ideally, krunner would display a result rounded to the appropriate number of significant figures. STEPS TO REPRODUCE 1. Type `=log(4)` in krunner OBSERVED RESULT The output is `interval(1.386294361119890, 1.386294361119891)` with `Approximation` written beside it in greyed-out text. EXPECTED RESULT Since we have so many digits after the decimal point, there seems to be no harm in outputting something like `1.38629436111989`, while still noting that it is an approximation. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.62 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412626] New: Plasmoids sometimes get 'stuck' while moving
https://bugs.kde.org/show_bug.cgi?id=412626 Bug ID: 412626 Summary: Plasmoids sometimes get 'stuck' while moving Product: plasmashell Version: 5.16.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kishor...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 123025 --> https://bugs.kde.org/attachment.cgi?id=123025&action=edit Screenshot showing a plasmoid in the stuck state. SUMMARY When I move plasmoids with the mouse, they sometimes get stuck. To 'unstick' them, I have to release the mouse and try to trigger a move action again, after which it will slide slightly and come unstuck. STEPS TO REPRODUCE 1. Unlock desktop widgets. 2. Try to move a plasmoid by hovering on it and then dragging the bar that appears on its edge. OBSERVED RESULT The plasmoid sometimes gets stuck in the middle of a drag operation. It will not move further even if you continue dragging it with the mouse. In this state, it has a blue box surrounding it (see attached screenshot). To get it to come unstuck, one has to hover over it and trigger the move action again. EXPECTED RESULT Plasmoid should not get stuck while moving. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION I can reproduce this with the clock, folder view, and comic plasmoids. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 345134] Calculator plugin covers numbers I need to see
https://bugs.kde.org/show_bug.cgi?id=345134 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 353026] KRunner closes when focus is lost
https://bugs.kde.org/show_bug.cgi?id=353026 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 --- Comment #8 from Kishore Gopalakrishnan --- I ca nreproduce this bug if I use the Arch package (5.16.90), or if I build from the tar at `https://download.kde.org/unstable/plasma/`. However, I can't reproduce it if I build from the git repo (checked with 5.17 branch, 5.16 branch, 5.16.90 tag). Perhaps there is some issue with the tars? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 410801] 'Switch user' button is cut off
https://bugs.kde.org/show_bug.cgi?id=410801 --- Comment #1 from Kishore Gopalakrishnan --- I've submitted a patch here: https://phabricator.kde.org/D23786 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 384264] Make it possible to disable media controls on lock screen
https://bugs.kde.org/show_bug.cgi?id=384264 --- Comment #22 from Kishore Gopalakrishnan --- (In reply to ederag from comment #21) > > It's in the 'Appearance' tab of the 'Screen locking' settings. > > Definitely not there on my system described in comment #19. > Only "Wallpaper type" and "Positioning". > What's your system ? I have a checkbox titled 'show media controls' on top of 'wallpaper type'. I'm using Plasma 5.16.5 on Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 407259] Disconneting from automatically connected network and toggling wifi makes network disappear
https://bugs.kde.org/show_bug.cgi?id=407259 Kishore Gopalakrishnan changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED --- Comment #2 from Kishore Gopalakrishnan --- Cannot reproduce with plasma-nm 5.16.5. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 411756] New: Spurious 'error checking authorization' message when deleting network
https://bugs.kde.org/show_bug.cgi?id=411756 Bug ID: 411756 Summary: Spurious 'error checking authorization' message when deleting network Product: plasma-nm Version: 5.16.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: kishor...@gmail.com Target Milestone: --- Created attachment 122557 --> https://bugs.kde.org/attachment.cgi?id=122557&action=edit Screenshot showing the error SUMMARY When you delete a network, you get a message complaining that the connection could not be deleted. However, the connection actually gets deleted, so this error message is unnecessary. STEPS TO REPRODUCE 1. Open connections editor from the applet. 2. Select a connection and press the 'minus' sign at the bottom of the sidebar. 3. Click 'OK' on the confirmation window that appears. OBSERVED RESULT The connection gets deleted, but you also get an error notification (attached screenshot) EXPECTED RESULT There should be no error notification, since the connection actually gets successfully deleted. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION Reproducible on multiple user accounts. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 384264] Make it possible to disable media controls on lock screen
https://bugs.kde.org/show_bug.cgi?id=384264 Kishore Gopalakrishnan changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED CC||kishor...@gmail.com --- Comment #20 from Kishore Gopalakrishnan --- (In reply to ederag from comment #19) > Any privacy breaking setting should be off by default. > > The "setting" mentioned in comment #15 > is not visible on openSUSE Leap 15 (plasma 5.12.6) > After reading https://phabricator.kde.org/D9684, > Workspace>Desktop Behavior>Screen locking > seemed the place to look at. > Is it elsewhere ? It's in the 'Appearance' tab of the 'Screen locking' settings. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411707] Natural sorting doesn't handle numbers with decimal points
https://bugs.kde.org/show_bug.cgi?id=411707 Kishore Gopalakrishnan changed: What|Removed |Added Attachment #122532|0 |1 is obsolete|| --- Comment #2 from Kishore Gopalakrishnan --- Created attachment 122533 --> https://bugs.kde.org/attachment.cgi?id=122533&action=edit Screenshot showing the issue This screenshot shows the issue more clearly. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411707] Natural sorting doesn't handle numbers with decimal points
https://bugs.kde.org/show_bug.cgi?id=411707 --- Comment #1 from Kishore Gopalakrishnan --- Oh sorry, what I meant in the 'observed behaviour' part is that it seems to discard the leading zeroes after the decimal point and start the comparison anew. It is not comparing them digit by digit. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411707] New: Natural sorting doesn't handle numbers with decimal points
https://bugs.kde.org/show_bug.cgi?id=411707 Bug ID: 411707 Summary: Natural sorting doesn't handle numbers with decimal points Product: dolphin Version: 19.08.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Created attachment 122532 --> https://bugs.kde.org/attachment.cgi?id=122532&action=edit Screenshot showing Dolphin's wrong sorting order. SUMMARY Natural sorting does not sort numbers with decimal points as per their numerical value. STEPS TO REPRODUCE 1. Create files whose names have numbers with decimal points. 2. Enable natural sorting in Settings > Dolphin > General OBSERVED RESULT Digits after the decimal point are just compared digit-by digit for sorting purposes (Attached screenshot). EXPECTED RESULT Numbers with decimal points should also be sorted according to their numerical value if natural sorting is enabled. For example, the 'ls' program does this correctly. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION Also happens with folders. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #58 from Kishore Gopalakrishnan --- (In reply to Andras from comment #57) > What plain authentication you guys are talking about? It's only for outgoing > setup, incoming has to be configured in a way it's asked by Google anyway > and basically that's where this problem is happening at least for me. I have > a bunch, around 10 account setup in the right way in Kontact, I have 2 step > auth.. so there is no option to set less secure app in Google account but in > that case it won't be necessary in theory. It doesn't work for me either, > same message appears for all of my account so I just wait. You can do the same for incoming mail by going to the 'connection settings' section of the 'advanced' tab in the dialog that opens when you click 'modify' on an incoming account. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 327666] When dragging globe the Navigation item should ignore mouse events
https://bugs.kde.org/show_bug.cgi?id=327666 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com --- Comment #4 from Kishore Gopalakrishnan --- Bug is reproducible in Marble 2.2.20 (this is the version given in the help dialog. The KDE applications version is 19.04.3) Other infromation: KDE Frameworks 5.60.0 Qt 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #42 from Kishore Gopalakrishnan --- (In reply to Dirk Davidis from comment #41) > until this has not been fixed working with kde is a mess ... thunderbird or > evolution are no real alternative ... so is there any timeline when this > gets fixed? Are you not able to use the workaround mentioned in comment 2? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 410801] New: 'Switch user' button is cut off
https://bugs.kde.org/show_bug.cgi?id=410801 Bug ID: 410801 Summary: 'Switch user' button is cut off Product: kscreenlocker Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kishor...@gmail.com CC: bhus...@gmail.com Target Milestone: --- Created attachment 122056 --> https://bugs.kde.org/attachment.cgi?id=122056&action=edit Screenshot showing the issue SUMMARY The 'Switch users' button on the lock screen goes slightly out of the display area (see screenshot). STEPS TO REPRODUCE 1. Lock screen OBSERVED RESULT 'Swtich user' button is slightly out of the screen EXPECTED RESULT 'Switch user' button should fit completely within the screen SOFTWARE/OS VERSIONS Distro: Arch Linux KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION My screen resolution is 1366x768. I don't have access to a larger display to check if it is reproducible there too. Bug is reproducible regardless of whether the media controls are enabled / disabled. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 407767] It is possible to switch back and forth unlocked user sessions via TTY
https://bugs.kde.org/show_bug.cgi?id=407767 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 404387] Allow to set a maximum volume less than 100%
https://bugs.kde.org/show_bug.cgi?id=404387 --- Comment #1 from Kishore Gopalakrishnan --- I've submitted a patch here: https://phabricator.kde.org/D23082 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #30 from Kishore Gopalakrishnan --- (In reply to davidblunkett from comment #28) > Just ran into this bug - bloody hell it's annoying. It is working fine on a > parallel system (presumably the old token is still valid on that?). > > The bodge to disable kmail's "gmail" authentication by switching from > "imap.gmail.com" to and IP address and using PLAIN authentication has worked > for me but this is a poor fix. > > I can't find any way to switch to PLAIN without nobbling the address which > is really annoying but this should (at least) be an available option. Are you sure about the address thing? I have been able to use it by just switching the authentication to SSL/TLS, port 993, PLAIN (still using imap.gmail.com). -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 372288] krunner switch window focus
https://bugs.kde.org/show_bug.cgi?id=372288 --- Comment #6 from Kishore Gopalakrishnan --- My comment #1 on reproducibility was with a single display. However, I am no longer able to reproduce the bug with krunner version 5.16.4. I think the multimonitor issues might be a different bug. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409224] kmail with >=mariadb-10.4.6: not able to refresh email list: Unable to append status flags
https://bugs.kde.org/show_bug.cgi?id=409224 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 394181] Exporting to Imgur: i) catch and ii) store the ephemeral one-time Imgur deletion Url in a local logfile
https://bugs.kde.org/show_bug.cgi?id=394181 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 404275] Crash on startup
https://bugs.kde.org/show_bug.cgi?id=404275 --- Comment #17 from Kishore Gopalakrishnan --- (In reply to gesf02 from comment #15) > (In reply to Wolfgang Bauer from comment #10) > > (In reply to Christoph Feck from comment #9) > > > This is possibly fixed with > > > https://code.qt.io/cgit/qt/qtbase.git/commit/src/corelib/ > > > tools?id=82ad4be4a2e0c2bccb6cd8ea2440aefee4ec48ec in Qt 5.12.4. > > > > It seems that the crash is actually already fixed in Qt 5.12.3. > > At least I was able to reproduce it with 5.12.2 (by setting /etc/localtime > > to point to Asia/Tokyo), and korganizer starts fine now after I updated to > > Qt 5.12.3. > > How to update to Qt 5.12.3 without default repository? I'm using Fedora 30. Ask the fedora maintainers to update Qt or backport the fix. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377953] plasmashell uses full cpu core: "Track file transfers and other jobs"
https://bugs.kde.org/show_bug.cgi?id=377953 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408617] Dolphin doesn't remember icon size per folder with 'remember properties for each folder' configuration
https://bugs.kde.org/show_bug.cgi?id=408617 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kruler] [Bug 271937] RFC: KRuler belongs rather to "Utilities" than to "Graphics"
https://bugs.kde.org/show_bug.cgi?id=271937 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com --- Comment #2 from Kishore Gopalakrishnan --- (In reply to Christoph Feck from comment #1) > .desktop file still says 'Graphics' category. On openSUSE, it shows up in > 'Utilities' because they have a desktop file patch to override. I've submitted a patch here. https://phabricator.kde.org/D21831 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 408074] Arrow keys move 'priority' slider in wrong direction
https://bugs.kde.org/show_bug.cgi?id=408074 --- Comment #2 from Kishore Gopalakrishnan --- I've submitted a patch here: https://phabricator.kde.org/D21828 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407612] [Wayland] On Plasma 5.16 beta, with any Window Decoration theme other than Breeze, Kwin eats all the RAM in a few seconds and the session hangs
https://bugs.kde.org/show_bug.cgi?id=407612 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 408290] Placing focus in the searchbar makes Esc unable to dismiss the applet
https://bugs.kde.org/show_bug.cgi?id=408290
--- Comment #5 from Kishore Gopalakrishnan ---
(In reply to Nate Graham from comment #4)
> (In reply to Kishore Gopalakrishnan from comment #3)
> > (In reply to Kai Uwe Broulik from comment #2)
> > > Probably needs to be changed to:
> > >
> > > Keys.onEscapePressed: {
> > > if (searchToggleButton.checked) {
> > > searchToggleButton.checked = false;
> > > } else {
> > > event.accepted = false;
> > > }
> > > }
> >
> > This seems to work. Should I submit the patch?
> Yes please!
>
> > Note: I found another similar bug. If we click on some elements in the
> > networks list in a particular order, the searchbox refuses to accept text
> > that we type until we manually place the focus in the searchbox. I'll try to
> > see how that can be fixed.
> If you do, feel free to submit a patch for that, too.
I've submitted it here. https://phabricator.kde.org/D21620
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-nm] [Bug 408290] Placing focus in the searchbar makes Esc unable to dismiss the applet
https://bugs.kde.org/show_bug.cgi?id=408290
--- Comment #3 from Kishore Gopalakrishnan ---
(In reply to Kai Uwe Broulik from comment #2)
> Probably needs to be changed to:
>
> Keys.onEscapePressed: {
> if (searchToggleButton.checked) {
> searchToggleButton.checked = false;
> } else {
> event.accepted = false;
> }
> }
This seems to work. Should I submit the patch?
Note: I found another similar bug. If we click on some elements in the networks
list in a particular order, the searchbox refuses to accept text that we type
until we manually place the focus in the searchbox. I'll try to see how that
can be fixed.
--
You are receiving this mail because:
You are watching all bug changes.
[kile] [Bug 408294] New: Multiple items titled 'Go To' in 'Edit' Menu
https://bugs.kde.org/show_bug.cgi?id=408294 Bug ID: 408294 Summary: Multiple items titled 'Go To' in 'Edit' Menu Product: kile Version: 2.9.92 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: user interface Assignee: michel.lud...@kdemail.net Reporter: kishor...@gmail.com Target Milestone: --- Created attachment 120566 --> https://bugs.kde.org/attachment.cgi?id=120566&action=edit Screenshot of the menu SUMMARY The 'Edit' menu has multiple submenus titled 'Go To' (scrennshot attached). They should be merged. They both contain different items, so it is not a case of simple duplication. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 408290] New: Placing focus in the searchbar makes Esc unable to dismiss the applet
https://bugs.kde.org/show_bug.cgi?id=408290 Bug ID: 408290 Summary: Placing focus in the searchbar makes Esc unable to dismiss the applet Product: plasma-nm Version: 5.15.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: kishor...@gmail.com Target Milestone: --- SUMMARY Once we place focus in the searchbar, 'Esc' is unable to dismiss the applet no matter how many times we press it. The applet is able to be dismissed using 'Esc' after interacting with other elements in the applet. STEPS TO REPRODUCE 1. Open the Networks popup in the systray. 2. Click the search icon above the channels list. 3. Click in the search area to place focus there. 4. Press Esc. Searchbar disappears. 5. Press Esc again. Note that no matter how many times you press Esc, the popup does not close. 6. If you have an active wifi network, click on it. Click on the 'details tab'. 7. Now note that Esc works to close the popup. OBSERVED RESULT Esc doesn't allow the applet to be dismissed after step 5 without further manual interaction with the applet. EXPECTED RESULT Esc should allow the applet to be dismissed after step 5. I.e. first press of Esc should remove focus from the searchbar, and the second press should close the applet. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION It looks like the serachbar isn't giving up focus correctly when one presses Esc. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 408287] New: Kile help (F1) points to wrong URL
https://bugs.kde.org/show_bug.cgi?id=408287 Bug ID: 408287 Summary: Kile help (F1) points to wrong URL Product: kile Version: 2.9.92 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: michel.lud...@kdemail.net Reporter: kishor...@gmail.com Target Milestone: --- SUMMARY Kile help points to the URL 'https://docs.kde.org/index.php?branch=stable5&language=en_GB&application=kile&path=/', on opening which we get the error 'The branch stable5 is not available for the specified application/language', along with a link to actual location of the documentation. Instead, it should point to 'https://docs.kde.org/index.php?branch=trunk5&language=en_GB&application=kile&path=/' (branch 'stable5' is changed to 'trunk5'). STEPS TO REPRODUCE 1. Open Kile 2. Press F1 OBSERVED RESULT A page is opened which says that documentation doesn't exist, but contains a link to the right URL. EXPECTED RESULT It should open the correct documentation link. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408206] New: Notifications don't timeout (until the user moves the mouse) if they appear under cursor
https://bugs.kde.org/show_bug.cgi?id=408206 Bug ID: 408206 Summary: Notifications don't timeout (until the user moves the mouse) if they appear under cursor Product: plasmashell Version: 5.15.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: kishor...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY If a notification appears under the cursor, the timeout is not triggered properly. Expected behaviour is that that timeout should be suspended only if the user actively brings the cursor onto the notification. STEPS TO REPRODUCE 1. Place cursor at the position where notifications appear. 2. Run something like 'notify-send Test blah' in a terminal 3. Note that the notification just stays there. OBSERVED RESULT Notification timeout does not begin until the user moves the cursor out of the notification. EXPECTED RESULT The notification timeout should be suspended only in cases where the user actively moves the cursor onto the notification. Sometimes I'm typing with the cursor just sitting in a corner of my screen, and notifications which appear don't get dismissed, requiring me to move the mouse. One could either: 1. only suspend the timeout if the mouse is moved and the cursor is on the notification. 2. only suspend the timeout if the cursor was not initially on the notification and it was later brought onto the notification. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408075] New: Okular flips pages if history is exhausted while using the back / forward keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=408075 Bug ID: 408075 Summary: Okular flips pages if history is exhausted while using the back / forward keyboard shortcuts Product: okular Version: 1.7.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- SUMMARY Okular binds the alt+shift+left/right shortcuts to the 'back' and 'forward' items by default. If the history is exhausted (i.e. we navigate back/forward till there are no more locations left), okular starts moving to the next/previous page, acting as if we have pressed just the left/right arrow key. STEPS TO REPRODUCE 1. Open a PDF in Okular. 2. Add the back and forward buttons to the toolbar (this is just to illustrate the issue) 3. Note that the 'forward' button is greyed out. 4. Press Alt+Shift+Right (forward). 5. Note that Okular moves forward one page. 6. Now scroll up and down to populate the history. 7. Press Alt+Shift+Left until the history of previous locations is exhausted. At this point, the 'back' button will be greyed out and unclickable. 8. Press Alt+Shift+Left 8. Note that this causes Okular to move one page back (as if we had just pressed the left arrow key) OBSERVED RESULT Okular flips pages when there is nowhere to go to in the history. EXPECTED RESULT Okular should do nothing if history is exhausted (i.e. after steps 8 and 4). SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION This is reproducible only if the shortcut contains an arrow key. If we bind something like ctrl+9 to 'forward', Okular shows the expected behaviour. Prima facie, it looks like Okular doesn't correctly handle the keypresses corresponding to a shortcut if the shortcut corresponds to an action that cannot be performed (like going 'forward' when we are at the most recently veiwed location). -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 408074] New: Arrow keys move 'priority' slider in wrong direction
https://bugs.kde.org/show_bug.cgi?id=408074 Bug ID: 408074 Summary: Arrow keys move 'priority' slider in wrong direction Product: ksysguard Version: 5.15.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- SUMMARY Using the arrow keys to move the 'priority' slider in the 'Set Priority' window (that can be opened from the right-click menu of a process) results in the slider moving in the wrong direction. STEPS TO REPRODUCE 1. Open Ksysguard. 2. Go to the tab that lists processes. 3. Right click on a process and select 'Set Priority'. 4. Click on the slider that sets the CPU priority. 5. Press the left and right arrow keys on the keyboard. OBSERVED RESULT The slider moves in the direction opposite to that indicated by the arrow key pressed. EXPECTED RESULT Slider should move in the direction indicated by the arrow key pressed. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385522] Present Windows: Don't darken all windows and denote selection some other way than restoring original lightness
https://bugs.kde.org/show_bug.cgi?id=385522 --- Comment #36 from Kishore Gopalakrishnan --- (In reply to Saverio Brancaccio from comment #35) > Considering the number of votes (only 2 since 2017) on this issue, I suppose > it's not an interesting feature to fix. > Therefore, I reported a suggestion on a 3rd party site to have at least an > extension that performs the function in subject: > https://github.com/Zren/plasma-applet-presentwindows > The author is the same of the video I already reported here in a previous > message: > https://www.youtube.com/watch?v=QEHC43zMIMc > > Regards. As far as I understand, that extension doesn't do anything about the dimming. It just adds a button to trigger the 'Present Windows' shortcut. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 407910] Add keyboard shortcut to change font back to default size
https://bugs.kde.org/show_bug.cgi?id=407910 --- Comment #6 from Kishore Gopalakrishnan --- I've posted it here: https://phabricator.kde.org/D21412 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 407910] Add keyboard shortcut to change font back to default size
https://bugs.kde.org/show_bug.cgi?id=407910 --- Comment #3 from Kishore Gopalakrishnan --- (In reply to Nate Graham from comment #1) > Konsole now has this, added with > https://cgit.kde.org/konsole.git/commit/ > ?id=f6e432ab0c04226bd772019911b97298070d1264 > > Maybe you could work on a patch, copying how it was done for Konsole? I have a working patch now, in the sense that the action appears in the shortcuts manager and if one manually assigns a shortcut to it, one can reset the font sizes. However, I still haven't figured out how to get it to show in the 'Edit' menu, or how to correctly assign a default shortcut for it. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 407909] Tab navigation keyboard shortcuts don't work if cursor is placed in the 'sensor browser' sidebar
https://bugs.kde.org/show_bug.cgi?id=407909 Kishore Gopalakrishnan changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED Summary|Add tab navigation keyboard |Tab navigation keyboard |shortcuts |shortcuts don't work if ||cursor is placed in the ||'sensor browser' sidebar --- Comment #3 from Kishore Gopalakrishnan --- Ah sorry. STEPS TO REPRODUCE: 1. Open a custom tab in Ksysguard. 2. Click in the searchbar above the 'sensor browser' sidepane. 3. Press ctrl+tab or ctrl+shift+tab EXPECTED BEHAVIOUR: Ksysguard should switch to the next tab or the previous tab. OBSERVED BEHAVIOUR: Nothing happens. ADDITIONAL INFORMATION: One can get the tab navigation keyboard shortcuts to work again by clicking on one of the inactive tabs, or by pressing 'tab' until the focus is returned to the tabbar. Interestingly, Ksysguard doesn't seem to have the same problem with the default 'process viewer' tab. In this case, it can switch tabs no matter where the focus is. NOTE: Initially, I was under the impression that it wasn't implemented since there was no corresponding entry in the shortcuts manager. I usually keep the sidebar minimized (by setting the width to zero), so I didn't realise the focus was in the sidebar. Hence the inaccurate initial report. I've changed the title accordingly, but I don't know how to change the importance from wishlist to something else. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 407910] New: Add keyboard shortcut to change font back to default size
https://bugs.kde.org/show_bug.cgi?id=407910 Bug ID: 407910 Summary: Add keyboard shortcut to change font back to default size Product: kate Version: 19.04.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Currently, we only have 'enlarge font' and 'reduce font' options in 'Settings > Configure Shortcuts'. A keyboard shortcut to reset the default font size would be useful to quickly recover when one accidentally changes the font size (sometimes I accidentally press ctrl while scrolling). This could be bound by default to 'ctrl+0', since people are probably used to that from web browsers. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 407909] Add tab navigation keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=407909 --- Comment #1 from Kishore Gopalakrishnan --- Note that currently, ctrl+(shift)+tab seems to work no matter where the focus is in the default process viewer, but if you have a custom tab and the focus is in the sidebar that allows you to drag in new sensors, ctrl+(shift)+tab doesn't work and you have to bring the focus to the tabbar as mentioned earlier. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 407909] New: Add tab navigation keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=407909 Bug ID: 407909 Summary: Add tab navigation keyboard shortcuts Product: ksysguard Version: 5.15.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- It would be great to have 'next tab' and 'previous tab' items in Ksysguard's shortcut configuration (Settings > Configure Shortcuts). Currently, one has to press the 'tab' key until the tabbar is focussed, and then use ctrl+tab to navigate between tabs. In fact, ctrl+(shift)+tab would be a good default binding for these shortcuts, since they are now used as a standard tabbing shortcut in pretty much every application. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407908] New: Fade effect for partially cut off icons in folder view plasmoid
https://bugs.kde.org/show_bug.cgi?id=407908 Bug ID: 407908 Summary: Fade effect for partially cut off icons in folder view plasmoid Product: plasmashell Version: 5.15.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: kishor...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 120288 --> https://bugs.kde.org/attachment.cgi?id=120288&action=edit Screenshot illustrating current situation. In the attached screenshot, we see that the parts of icons that are partially out of the view are unceremoniously cut off before reaching the edge. This would look much better with some sort of fade effect for the cut off icons. The issue doesn't arise in applications like Dolphin because they have a well defined border around the area where files are displayed. This doesn't work for the folder view plasmoid, as the border is some invisible line. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 407859] Add option to follow system colour theme
https://bugs.kde.org/show_bug.cgi?id=407859 --- Comment #3 from Kishore Gopalakrishnan --- (In reply to Christoph Feck from comment #2) > The idea was to be able to set the colors of the document independent from > the colors of the UI. The colours of the text area can be set separately through the colour schemas in 'Settings > Configure Kate > Fonts and Colours'. This option just sets the colour theme of the toolbar, sidebar etc. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 407859] New: Add option to follow system colour theme
https://bugs.kde.org/show_bug.cgi?id=407859 Bug ID: 407859 Summary: Add option to follow system colour theme Product: kate Version: 19.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Kate allows one to choose a custom colour theme for the application alone through 'Settings > Colour Theme'. Currently it is missing a 'Default' option that tells Kate to follow the system colour scheme. This means that once one chooses a custom colour theme for the first time, one loses the ability to have Kate automatically match the system colour theme. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 407857] Options in right-click menu for 'Printers' plasmoid are confusingly named
https://bugs.kde.org/show_bug.cgi?id=407857 --- Comment #1 from Kishore Gopalakrishnan --- Similar bugs, but for other plasmoids: https://bugs.kde.org/show_bug.cgi?id=407561 https://bugs.kde.org/show_bug.cgi?id=407560 -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 407857] New: Options in right-click menu for 'Printers' plasmoid are confusingly named
https://bugs.kde.org/show_bug.cgi?id=407857 Bug ID: 407857 Summary: Options in right-click menu for 'Printers' plasmoid are confusingly named Product: print-manager Version: 19.04 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dantt...@gmail.com Reporter: kishor...@gmail.com Target Milestone: --- If we right-click on the 'Printers' systray item, we have two options which are both named 'Configure Printers'. One of them is for the plasmoid, and the other is for the systemwide KCM. They should be renamed, since the only way to currently distinguish between them is the icon. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407853] New: Extra ampersand in tooltip text on 'configure' button in Notifications plasmoid
https://bugs.kde.org/show_bug.cgi?id=407853 Bug ID: 407853 Summary: Extra ampersand in tooltip text on 'configure' button in Notifications plasmoid Product: plasmashell Version: 5.15.90 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: kishor...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 120261 --> https://bugs.kde.org/attachment.cgi?id=120261&action=edit Screenshot showing the issue STEPS TO REPRODUCE 1. Open Notifications Plasmoid from system tray. 2. Hover over the 'Configure' button to the right of the 'Do not disturb' text. 3. Note that the tooltip has an extra ampersand in the text (see screenshot). SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 407852] New: Ktexteditor overwrites closing bracket even if automatic brackets is not enabled
https://bugs.kde.org/show_bug.cgi?id=407852
Bug ID: 407852
Summary: Ktexteditor overwrites closing bracket even if
automatic brackets is not enabled
Product: frameworks-ktexteditor
Version: 5.58.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: kishor...@gmail.com
Target Milestone: ---
SUMMARY
Applications that use ktexteditor overwrite the closing bracket even when
auto-bracketing is not enabled.
STEPS TO REPRODUCE
1. Open Kile or Kate
2. Check that automatic brackets is disabled (In Kate, Settings > Editing >
uncheck 'Enable Automatic Brackets')
2. Type 'a()' (without quotes)
3. Place cursor inside the bracket
4. Type '()' (without quotes)
OBSERVED RESULT
It simply skips the outer bracket as if you're typing to get out of an
autocompleted bracket. The resulting entered text is 'a(()' (without quotes).
EXPECTED RESULT
It should enter 'a(())' (without quotes) as typed. Current behaviour is
disruptive and leads to unmatched brackets may be difficult to notice after the
fact.
SOFTWARE/OS VERSIONS
Linux distro: Arch Linux
KDE Plasma Version: 5.15.90
KDE Frameworks Version: 5.58.0
Qt Version: 5.13.0
ADDITIONAL INFORMATION
Downgrading ktexteditor to 5.57.0 fixes the issue (i.e. it shows the expected
behaviour).
The issue can be reproduced for '{}' and '[]' brackets too.
Possibly related to https://bugs.kde.org/show_bug.cgi?id=368580
Possible duplicate of https://bugs.kde.org/show_bug.cgi?id=318267 (Note that
that bug is from 2013, while the current bug is a regression in the current
frameworks release.)
--
You are receiving this mail because:
You are watching all bug changes.
[Powerdevil] [Bug 407710] Powerdevil doesn't handle button actions
https://bugs.kde.org/show_bug.cgi?id=407710 --- Comment #1 from Kishore Gopalakrishnan --- A git bisect shows this (https://phabricator.kde.org/D19162) as the first bad commit. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 347770] notification number not alligned
https://bugs.kde.org/show_bug.cgi?id=347770 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 383189] File Search kcm only lists the two first exclude locations from baloofilerc
https://bugs.kde.org/show_bug.cgi?id=383189 Kishore Gopalakrishnan changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 407710] New: Powerdevil doesn't handle button actions
https://bugs.kde.org/show_bug.cgi?id=407710 Bug ID: 407710 Summary: Powerdevil doesn't handle button actions Product: Powerdevil Version: 5.15.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- SUMMARY Button actions (suspend etc.) do not work in the latest 5.15.90 beta. Downgrading powerdevil to 5.15.5 fixes the issue STEPS TO REPRODUCE 1. Upgrade to powerdevil 5.15.90. 2. Configure laptop to sleep on power button press. 3. Press power button. OBSERVED RESULT Laptop does not sleep. EXPECTED RESULT Laptop should go to sleep. SOFTWARE/OS VERSIONS Linux distro: Arch Linux (kde-unstable repo) KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION Downgrading powerdevil to 5.15.5 fixes the issue. Output of `systemctl status systemd-logind` is as follows. With Powerdevil 5.15.90: ``` May 19 11:20:51 kishore-inspiron-3537 systemd-logind[740]: Power key pressed. ``` With Powerdevil 5.15.5: ``` May 19 11:21:18 kishore-inspiron-3537 systemd-logind[740]: Power key pressed. May 19 11:21:28 kishore-inspiron-3537 systemd-logind[740]: Operation 'sleep' finished. ``` Invoking suspend / hibernate via 'systemctl suspend' works perfectly. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 407709] New: List of excluded folders does not occupy all available space
https://bugs.kde.org/show_bug.cgi?id=407709 Bug ID: 407709 Summary: List of excluded folders does not occupy all available space Product: systemsettings Version: 5.15.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_baloo Assignee: baloo-bugs-n...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Created attachment 120179 --> https://bugs.kde.org/attachment.cgi?id=120179&action=edit Screenshot of KCM SUMMARY If we open the baloo KCM, it shows a list of excluded folders (attached screenshot). This list occupies only a small amount of the available space, and the rest of the window is left empty. Since there are not many other items in this particular KCM, it would be better to occupy the entire available vertical space instead of displaying it in a very small area which requires a lot of scrolling to view all the excluded folders. SOFTWARE/OS VERSIONS Linux distribution: Arch Linux KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 383189] File Search kcm only lists the two first exclude locations from baloofilerc
https://bugs.kde.org/show_bug.cgi?id=383189 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com --- Comment #1 from Kishore Gopalakrishnan --- I can't reproduce this now. Does this still occur on your machine? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 407561] New: [Usability] Configuration options in Network applet's right-click menu are confusingly named
https://bugs.kde.org/show_bug.cgi?id=407561 Bug ID: 407561 Summary: [Usability] Configuration options in Network applet's right-click menu are confusingly named Product: plasma-nm Version: 5.15.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: kishor...@gmail.com Target Milestone: --- SUMMARY If we right-click on the 'Networks' item in the system tray, we get two options. One of them opens the system settings panel to configure networks, while the other opens a configuration window for the plasmoid. Currently, it is difficult to distinguish which does what from the name alone. The option that opens the configuration for the plasmoid should be more clearly named as 'Configure Networks Plasmoid' or 'Configure this applet'. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.57.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION Simliar to bug 407560, but for this plasmoid. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407560] New: [Usability] Configuration options in Battery plasmoid's right-click menu are confusingly named
https://bugs.kde.org/show_bug.cgi?id=407560 Bug ID: 407560 Summary: [Usability] Configuration options in Battery plasmoid's right-click menu are confusingly named Product: plasmashell Version: 5.15.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Battery Monitor Assignee: k...@privat.broulik.de Reporter: kishor...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY If we right-click on the 'Battery and Brightness' item in the system tray, we get two options: 'Configure Power Saving', and 'Configure Battery and Brightness'. The former opens the system settings area, while the latter opens the configuration for the plasmoid. The option that opens the configuration window for the plasmoid should be named more clearly as 'Configure Battery and Brightness Plasmoid' or 'Configure this Plasmoid'. Currently, I find it confusing as to which option does what. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.57.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 398847] Kaddressbook not parsing gmail contacts
https://bugs.kde.org/show_bug.cgi?id=398847 Kishore Gopalakrishnan changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #32 from Kishore Gopalakrishnan --- (In reply to Boyd Stephen Smith Jr. from comment #31) > This is still affecting me in kaddresbook 18.08.3 from Debian. > > I have no idea how to convert from the 5.10.3 "fixed version" to the version > used by KDE application releases 18.08.3. From what I could glean, 5.10.3 > was released a year or so before 18.08.3, but the bug persists. Comment #26 says the fix is in 18.12.3. Please ask the Debain maintainer to backport the fix. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401479] Feature request: add animations that follow the fingers when performing touchpad gestures
https://bugs.kde.org/show_bug.cgi?id=401479 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 377217] Available connections are Shown as Active connections in Switch User Session
https://bugs.kde.org/show_bug.cgi?id=377217 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 407259] New: Disconneting from automatically connected network and toggling wifi makes network disappear
https://bugs.kde.org/show_bug.cgi?id=407259 Bug ID: 407259 Summary: Disconneting from automatically connected network and toggling wifi makes network disappear Product: plasma-nm Version: 5.15.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: kishor...@gmail.com Target Milestone: --- SUMMARY If I toggle wifi after manually disconnecting from a wifi network that is configured to automatically connect, the network is no longer shown in the list of networks in the applet. STEPS TO REPRODUCE 1. Connect to new wifi network 2. Open settings and select 'connect automatically' if it is not already selected. 3. Open network applet, press 'disconnect' beside the network name. 4. Toggle wifi (turn on and off using the checkbox next to the airplane mode checkbox). 5. Note that the earlier network is not shown. 6. The only way to get it to show seems to be to go to the settings and click 'remove selected connection'. The network will then be shown after we toggle wifi OBSERVED RESULT Network is no longer shown until we forget it and add again. EXPECTED RESULT The network should be shown as usual. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
