[kmail] [Bug 209938] Long threads push messages off the view in threaded view because of indent accumulation
https://bugs.kde.org/show_bug.cgi?id=209938 --- Comment #6 from Kishore Gopalakrishnan --- Should I change the status of the bug since it is confirmed that it applies to Kmail2? Or perhaps file a new bug with the kmail2 product? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405435] In Open Recent menu, underscores in filenames become accelerators
https://bugs.kde.org/show_bug.cgi?id=405435 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 405775] New: 'Impossible to send email' notification is too intrusive
https://bugs.kde.org/show_bug.cgi?id=405775 Bug ID: 405775 Summary: 'Impossible to send email' notification is too intrusive Product: kmail2 Version: 5.10.3 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Created attachment 118982 --> https://bugs.kde.org/attachment.cgi?id=118982=edit Screenshot showing error dialog The error dialog that Kmail shows when it get disconnected from the network (see attachment) is too intrusive. In my case, it keeps on popping up whenever my wifi connection is dropped. It does not get automatically dismissed, and sometimes I get multiple instances of this dialog popping up in short succession. Since this appears even when Kmail runs in the background (grabbing focus and interrupting my work), it would be better to have this as a notification which uses the normal desktop notification system. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 405669] New: Feature request: ability to download only recent message bodies
https://bugs.kde.org/show_bug.cgi?id=405669 Bug ID: 405669 Summary: Feature request: ability to download only recent message bodies Product: kmail2 Version: 5.10.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- If we right-click on an IMAP folder and go to 'folder properties > retrieval', one can choose to either retrieve full messages, or retrieve on demand. It would be useful to be able to retrieve full messages for recent mails, and retrieve on demand for older ones. For people with large mail inboxes, retrieving everything just to have access to perhaps the last 30 days of mail offline seems like a waste. Ideally, there would be a third option which would retrieve full messages only for mails in the last X days (where X could be user-configurable). Apologies if this already exists as an option somewhere. I couldn't find it. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 404679] Korganizer crashes on startup
https://bugs.kde.org/show_bug.cgi?id=404679 --- Comment #1 from Kishore Gopalakrishnan --- With debug symbols for qt5 -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7ba6b77200 (LWP 31206))] Thread 5 (Thread 0x7f7b9edee700 (LWP 31220)): #0 0x7f7bae84c7a4 in read () from /usr/lib/libc.so.6 #1 0x7f7baa409971 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f7baa45a0b0 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7f7baa45b4e6 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7f7baa45b62e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7f7baed9fd04 in QEventDispatcherGlib::processEvents (this=0x7f7b8c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f7baed48b2c in QEventLoop::exec (this=this@entry=0x7f7b9ededd60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f7baeb8c569 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f7baeb8d96c in QThreadPrivate::start (arg=0x558b3fc35710) at thread/qthread_unix.cpp:361 #9 0x7f7baca57a9d in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f7bae85bb23 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f7b9f5ef700 (LWP 31213)): #0 0x7f7bae850c21 in poll () from /usr/lib/libc.so.6 #1 0x7f7baa45b540 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f7baa45b62e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f7baed9fd04 in QEventDispatcherGlib::processEvents (this=0x7f7b94000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f7baed48b2c in QEventLoop::exec (this=this@entry=0x7f7b9f5eed60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f7baeb8c569 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f7baeb8d96c in QThreadPrivate::start (arg=0x558b3fbb4d20) at thread/qthread_unix.cpp:361 #7 0x7f7baca57a9d in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f7bae85bb23 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f7ba4995700 (LWP 31208)): #0 0x7f7bae84c7a4 in read () from /usr/lib/libc.so.6 #1 0x7f7baa409971 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f7baa45a0b0 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7f7baa45b4e6 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7f7baa45b62e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7f7baed9fd04 in QEventDispatcherGlib::processEvents (this=0x7f7b98000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f7baed48b2c in QEventLoop::exec (this=this@entry=0x7f7ba4994d30, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f7baeb8c569 in QThread::exec (this=this@entry=0x7f7bae541080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f7bae4c5ba6 in QDBusConnectionManager::run (this=0x7f7bae541080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #9 0x7f7baeb8d96c in QThreadPrivate::start (arg=0x7f7bae541080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #10 0x7f7baca57a9d in start_thread () from /usr/lib/libpthread.so.0 #11 0x7f7bae85bb23 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f7ba5b5c700 (LWP 31207)): #0 0x7f7bae850c21 in poll () from /usr/lib/libc.so.6 #1 0x7f7baa3d0630 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f7baa3d22db in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f7ba6711949 in QXcbEventQueue::run (this=0x558b3fae4a60) at qxcbeventqueue.cpp:228 #4 0x7f7baeb8d96c in QThreadPrivate::start (arg=0x558b3fae4a60) at thread/qthread_unix.cpp:361 #5 0x7f7baca57a9d in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f7bae85bb23 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f7ba6b77200 (LWP 31206)): [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x51) at /usr/include/c++/8.2.1/bits/atomic_base.h:390 #7 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x51) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103 #9 QtPrivate::RefCount::ref (this=0x51) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:55 #10 QString::QString (other=..., this=0x7fffd9d9ce90) at ../../include/QtCore/../../src/corelib/tools/qstring.h:958 #11 QTimeZonePrivate::Data::Data (this=0x7fffd9d9ce90) at tools/qtimezoneprivate_p.h:81 #12 QTzTimeZonePrivate::previousTransition (this=0x558b3fc4ad90, beforeMSecsS
[korganizer] [Bug 404679] New: Korganizer crashes on startup
https://bugs.kde.org/show_bug.cgi?id=404679 Bug ID: 404679 Summary: Korganizer crashes on startup Product: korganizer Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Application: korganizer (5.10.2) Qt Version: 5.12.1 Frameworks Version: 5.55.0 Operating System: Linux 4.20.10-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Launched korganizer. If I launch it from the terminal, it shows the following output: KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = korganizer path = /usr/bin pid = 16859 KCrash: Arguments: /usr/bin/korganizer KCrash: Attempting to start /usr/lib/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 Job 1, 'korganizer' has stopped and opens the crash reporting thing. Please let me know if you want me to compile the qt packages with debug symbols as well. The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0ed5ec5840 (LWP 16859))] Thread 5 (Thread 0x7f0ece2bc700 (LWP 16874)): #0 0x7f0eddb9a7a4 in read () from /usr/lib/libc.so.6 #1 0x7f0edb147971 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f0edb1980b0 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7f0edb1994e6 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7f0edb19962e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7f0ede0ebd04 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f0ede094b2c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7f0edded8569 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7f0edded996c in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f0edbda3a9d in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f0eddba9b23 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f0ecead5700 (LWP 16866)): #0 0x7f0edb1473b9 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0 #1 0x7f0edb198e17 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #2 0x7f0edb199466 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f0edb19962e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f0ede0ebd04 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f0ede094b2c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f0edded8569 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7f0edded996c in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f0edbda3a9d in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f0eddba9b23 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f0ecfce6700 (LWP 16861)): #0 0x7f0eddb9a7a4 in read () from /usr/lib/libc.so.6 #1 0x7f0edb147971 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f0edb1980b0 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7f0edb1994e6 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7f0edb19962e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7f0ede0ebd04 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f0ede094b2c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7f0edded8569 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7f0edd812ba6 in ?? () from /usr/lib/libQt5DBus.so.5 #9 0x7f0edded996c in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7f0edbda3a9d in start_thread () from /usr/lib/libpthread.so.0 #11 0x7f0eddba9b23 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f0ed4ead700 (LWP 16860)): #0 0x7f0eddb9ec21 in poll () from /usr/lib/libc.so.6 #1 0x7f0edb10e630 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f0edb1102db in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f0ed5a62949 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7f0edded996c in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f0edbda3a9d in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f0eddba9b23 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f0ed5ec5840 (LWP 16859)): [KCrash Handler] #6 0x7f0eddf7d0da in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f0eddf769f9 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f0eddf1f29f in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f0eddf1f71d in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7f0eddf1fcb4 in QDateTime::QDateTime(QDate const&, QTime const&, QTimeZone const&) () from
[kmail2] [Bug 397968] Arrow symbols to expand and contract recipient lists are interchanged
https://bugs.kde.org/show_bug.cgi?id=397968 Kishore Gopalakrishnan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Kishore Gopalakrishnan --- Seems to be fixed in version 5.10.2. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 404387] New: Allow to set a maximum volume less than 100%
https://bugs.kde.org/show_bug.cgi?id=404387 Bug ID: 404387 Summary: Allow to set a maximum volume less than 100% Product: plasma-pa Version: 5.15.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: kishor...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- If we right click on the volume plasmoid and select 'Configure Audio Volume', the 'General' tab has a box that allows us to set a maximum volume higher than 100%. It would be nice to have the ability to set the value to something lower than 100% as well. This is useful for people with sensitive (not sure if that's the right word) earphones. I currently use my earphones at around 15%, and it would be nice to have the ability to set a maximum value lower than 100% so I don't accidentally blow my ears out while adjusting the volume with the scroll wheel. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 196998] Konsole should reflow the text when resizing
https://bugs.kde.org/show_bug.cgi?id=196998 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 76082] smooth scrolling in all apps
https://bugs.kde.org/show_bug.cgi?id=76082 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 402882] Pointing Devices KCM
https://bugs.kde.org/show_bug.cgi?id=402882 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- 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 CC||martin.tlus...@gmail.com --- Comment #12 from Kishore Gopalakrishnan --- *** Bug 400415 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 400415] google email adress shown in //schemas.google.com/g/2005#home:email.adr...@gmail.com Format
https://bugs.kde.org/show_bug.cgi?id=400415 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Kishore Gopalakrishnan --- *** This bug has been marked as a duplicate of bug 398847 *** -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 400623] New: While editing clipboard items, one cannot use alt accelerator to select 'OK' button
https://bugs.kde.org/show_bug.cgi?id=400623 Bug ID: 400623 Summary: While editing clipboard items, one cannot use alt accelerator to select 'OK' button Product: klipper Version: 5.14.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasma-widget Assignee: plasma-b...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Copy some text to the clipboard. 2. Open the clipboard widget and press the button to edit the text. 3. A window appears with the copy text editable. It has two buttons, OK and 'Cancel'. 4. Press 'alt'. Observe that 'O' in 'OK' and 'C' in cancel are underlined. 5. Press 'alt+O'. 6. Press 'alt+C'. OBSERVED RESULT When we press 'alt+O', the letter 'o' is just input into the text field. However, pressing 'alt+C' activates the 'cancel' button and closes the edit window. EXPECTED RESULT 'alt+O' should activate the 'OK' button. SOFTWARE VERSIONS KDE Plasma Version: 5.14.2 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION The value of the 'AutoCheckAccelerators' setting in .config/kdeglobals doesn't affect the reproducibility of this bug. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400511] Crash when trying to highlight/underline a text
https://bugs.kde.org/show_bug.cgi?id=400511 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400189] File > Properties window's initial size is too small for .djvu files
https://bugs.kde.org/show_bug.cgi?id=400189 Kishore Gopalakrishnan changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 from Kishore Gopalakrishnan --- I'm really sorry for the noise. It seems I'd set a kwin window rule for okular that disobeys the requested minimum size. I've marked the bug as resolved. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400189] File > Properties window's initial size is too small for .djvu files
https://bugs.kde.org/show_bug.cgi?id=400189 --- Comment #6 from Kishore Gopalakrishnan --- Created attachment 115864 --> https://bugs.kde.org/attachment.cgi?id=115864=edit Window for PDF after resizing -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400189] File > Properties window's initial size is too small for .djvu files
https://bugs.kde.org/show_bug.cgi?id=400189 --- Comment #5 from Kishore Gopalakrishnan --- Created attachment 115863 --> https://bugs.kde.org/attachment.cgi?id=115863=edit Window for PDF as it initially opens -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400189] File > Properties window's initial size is too small for .djvu files
https://bugs.kde.org/show_bug.cgi?id=400189 --- Comment #4 from Kishore Gopalakrishnan --- Created attachment 115862 --> https://bugs.kde.org/attachment.cgi?id=115862=edit Window for djvu after resizing (filename blanked out by me) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400189] File > Properties window's initial size is too small for .djvu files
https://bugs.kde.org/show_bug.cgi?id=400189 --- Comment #3 from Kishore Gopalakrishnan --- Created attachment 115861 --> https://bugs.kde.org/attachment.cgi?id=115861=edit Window as it initially opens for djvu -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 400191] New: Kile crashes when right-clicking tab
https://bugs.kde.org/show_bug.cgi?id=400191 Bug ID: 400191 Summary: Kile crashes when right-clicking tab Product: kile Version: 2.9.92 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.92) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.18.14-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: Steps to reproduce: 1. Open a .tex file in Kile 2. Right click on the tab Observed result: Kile crashes. We can tell it hasn't closed cleanly because it doesn't clean the temporary files even if configured to do so on exit. This happens even if multiple tabs are open. 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 0x7fcd917de880 (LWP 26039))] Thread 7 (Thread 0x7fcd739e1700 (LWP 29450)): #0 0x7fcd9dcfd7a4 in read () from /usr/lib/libc.so.6 #1 0x7fcd93c01782 in pa_read () from /usr/lib/pulseaudio/libpulsecommon-12.2.so #2 0x7fcd97d4455f in pa_mainloop_prepare () from /usr/lib/libpulse.so.0 #3 0x7fcd97d44fd1 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0 #4 0x7fcd97d45091 in pa_mainloop_run () from /usr/lib/libpulse.so.0 #5 0x7fcd97d535ae in ?? () from /usr/lib/libpulse.so.0 #6 0x7fcd93c319fc in ?? () from /usr/lib/pulseaudio/libpulsecommon-12.2.so #7 0x7fcd9ae75a9d in start_thread () from /usr/lib/libpthread.so.0 #8 0x7fcd9dd0cb23 in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7fcd85675700 (LWP 26045)): #0 0x7fcd9ae7bafc in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fcd85c0f1ac in ?? () from /usr/lib/dri/i965_dri.so #2 0x7fcd85c0eee8 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7fcd9ae75a9d in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fcd9dd0cb23 in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7fcd877fe700 (LWP 26043)): #0 0x7fcd9ae7bafc in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fcd9b0fc71c in QWaitCondition::wait (this=0x5617ecb07a24, readWriteLock=0x80, time=0) at thread/qwaitcondition_unix.cpp:223 #2 0x7fcd74003a00 in ?? () #3 0x7fcd877fdd00 in ?? () #4 0x5617f22572d0 in ?? () #5 0xad5e467e4daf0200 in ?? () #6 0x5617f22572d0 in ?? () #7 0x5617ecb0f130 in ?? () #8 0x5617f22572d0 in ?? () #9 0x5617ecb0f160 in ?? () #10 0x7fcd877fdcf0 in ?? () #11 0x7fcd74003a00 in ?? () #12 0x7fcd877fdd00 in ?? () #13 0x7fcd9e0465a1 in KileParser::ParserThread::run (this=0x0) at /usr/src/debug/kile-2.9.92/src/parser/parserthread.cpp:169 #14 0x7fcd9b0fbf65 in QThreadPrivate::start (arg=0x5617ecb0f130) at thread/qthread_unix.cpp:388 #15 0x7fcd9ae75a9d in start_thread () from /usr/lib/libpthread.so.0 #16 0x7fcd9dd0cb23 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7fcd87fff700 (LWP 26042)): #0 0x7fcd9ae7bafc in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fcd9b0fc71c in QWaitCondition::wait (this=0x5617ecb17490, readWriteLock=0x80, time=0) at thread/qwaitcondition_unix.cpp:223 #2 0x7fcd7c01bf50 in ?? () #3 0x7fcd87ffed00 in ?? () #4 0x in ?? () Thread 3 (Thread 0x7fcd8e7bd700 (LWP 26041)): #0 0x7fcd9dcfd7a4 in read () from /usr/lib/libc.so.6 #1 0x7fcd98850781 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fcd988a0a50 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7fcd988a1e86 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7fcd988a1fce in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7fcd9b2fcfe4 in QEventDispatcherGlib::processEvents (this=0x7fcd8b20, flags=...) at kernel/qeventdispatcher_glib.cpp:428 #6 0x7fcd9b2a88cc in std::__atomic_base::load (__m=, this=) at ../../include/QtCore/../../src/corelib/tools/qstack.h:61 #7 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103 #9 QtPrivate::RefCount::isShared (this=) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:101 #10 QVector::isDetached (this=) at ../../include/QtCore/../../src/corelib/tools/qvector.h:106 #11 QVector::detach (this=) at ../../include/QtCore/../../src/corelib/tools/qvector.h:383 #12 QVector::data (this=) at ../../include/QtCore/../../src/corelib/tools/qvector.h:127 #13 QStack::pop (this=0x34) at ../../include/QtCore/../../src/corelib/tools/qstack.h:62 #14 QEventLoop::LoopReference::~LoopReference (this=,
[kmail] [Bug 209938] Long threads push messages off the view in threaded view because of indent accumulation
https://bugs.kde.org/show_bug.cgi?id=209938 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com --- Comment #5 from Kishore Gopalakrishnan --- This still occurs in kmail2. SOFTWARE VERSIONS KDE Plasma Version: 5.14.1 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 Kmail version 5.9.2 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400189] File > Properties window's initial size is too small for .djvu files
https://bugs.kde.org/show_bug.cgi?id=400189 Kishore Gopalakrishnan changed: What|Removed |Added Summary|File > Properties window's |File > Properties window's |inital size is too small|initial size is too small |for .djvu files |for .djvu files -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400189] New: File > Properties window's inital size is too small for .djvu files
https://bugs.kde.org/show_bug.cgi?id=400189 Bug ID: 400189 Summary: File > Properties window's inital size is too small for .djvu files Product: okular Version: 1.5.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 If we open the File > Properties window while viewing a djvu file, the window opens with the wrong size, i.e. so small that none of the text is displayed properly. STEPS TO REPRODUCE 1. Open a djvu file in okular 2. Go to File > Properties OBSERVED RESULT The opened window is so small that the text is not displayed properly. Lines of text are cut off vertically, i.e. only a certain fraction of the top of each line is displayed. In the extreme case, one simply sees what appear to be a bunch of dashed lines (the top edges of letters in each line). However, one can resize the window and view the text. EXPECTED RESULT The File>properties window should open with a size which allows the text to be displayed properly SOFTWARE VERSIONS KDE Plasma Version: 5.14.1 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION The same does not happen with PDF files, i.e. the File>properties window opens with the correct size. However, one can resize the window until it is small enough to get the same effect of text not being displayed properly. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 162211] Copying to an external causes lots of missing files
https://bugs.kde.org/show_bug.cgi?id=162211 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 400188] New: Unable to resize sidebar when 'add shape' panel is minimized
https://bugs.kde.org/show_bug.cgi?id=400188 Bug ID: 400188 Summary: Unable to resize sidebar when 'add shape' panel is minimized Product: calligrawords Version: 3.1.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: calligra-words-bugs-n...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- SUMMARY If the 'add shape' panel in the sidebar is minimized (using the arrow to the left of the panel name), no resize handle appears when we hover over left edge of the sidebar. STEPS TO REPRODUCE 1. Hover mouse over the left edge of the sidebar and try to resize it. 2. Observe that resizing is allowed. 3. Now click the arrow to the left of the name of the 'add shapes' panel in the sidebar. 4. Hover mouse over left edge of sidebar. 5. Note that no resize handle appears. 6. Try dragging. 7. Window gets moved instead of resizing the sidebar. 8. Unminimise the 'add shapes' panel by clicking the arrow again. 9. We are now able to resize the sidebar as before. OBSERVED RESULT We cannot resize the sidebar when the 'add shape' panel is minimised. EXPECTED RESULT State of the 'add shape' panel should have no effect on whether we are able to resize the sidebar. SOFTWARE VERSIONS KDE Plasma Version: 5.14.1 KDE Frameworks Version: 5.51 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 341545] Timezone offset from current timezone seems to be applied twice
https://bugs.kde.org/show_bug.cgi?id=341545 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- 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 CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 398606] Okular 'Help > What's this' doesn't work on toolbar items
https://bugs.kde.org/show_bug.cgi?id=398606 --- Comment #3 from Kishore Gopalakrishnan --- Oh. I didn't realise it was intentional. Perhaps the 'what's this' menu item should be removed, then, if the application has no help text for any of the buttons? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 383389] Krunner crash
https://bugs.kde.org/show_bug.cgi?id=383389 --- Comment #6 from Kishore Gopalakrishnan --- I haven't been able to reproduce this, at least for the last few months. I think that whatever it was has been fixed. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 398605] Closing the 'find' toolbar should clear search field
https://bugs.kde.org/show_bug.cgi?id=398605 --- Comment #4 from Kishore Gopalakrishnan --- (In reply to Albert Astals Cid from comment #3) > (In reply to Kishore Gopalakrishnan from comment #2) > > I'm not sure if I'm missing something, but there is currently no simple way > > to dismiss both the bar and the search term highlights once I find what I'm > > searching for. > > Press Esc twice. > > This is a wishlist and honestly i'm very close to marking it WONTFIX. This > is the behaviour Okular has had for more than a decade, unless you can find > hordes of people agreeing with you, it means people like the current > behaviour. Oh okay. That makes sense. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 398605] Closing the 'find' toolbar should clear search field
https://bugs.kde.org/show_bug.cgi?id=398605 --- Comment #2 from Kishore Gopalakrishnan --- Personally, I feel that it is more in line with the user's expectations to not highlight search terms once the search bar is closed (this is the case in browser 'find' toolbars, for instance). Perhaps there should be a 'minimize' button if the user wants to hide the bar without clearing the field. I'm not sure if I'm missing something, but there is currently no simple way to dismiss both the bar and the search term highlights once I find what I'm searching for. I frequently find myself searching for something, finding what I want, closing the toolbar, and then having to open it again after noticing that the search terms are still highlighted. Even if I were to somehow break this habit, I would still have to manually clear the search field before closing the search bar each time. One way to accomodate both our usecases would be to keep the search term as it is in the search field even after it is closed, but somehow make sure that the terms in the document aren't highlighted when the bar is closed. However, I'm not sure if this would be easy or difficult to implement. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 398601] Kile does not remove already typed letters while tab-completing reference
https://bugs.kde.org/show_bug.cgi?id=398601 --- Comment #3 from Kishore Gopalakrishnan --- (In reply to Christoph Feck from comment #2) > Does the same happen in Kate? There is also a setting 'Remove tail on > complete' in Editor settings, which might affect this behaviour. I can reproduce this with the autocomplete options in 'Editor > Editing > Autocompletion' completely disabled, and only 'Kile > Complete > Auto completion for LaTeX markup' enabled. I can't reproduce this in Kate. If I disable the 'autocompletion for LaTeX markup' option leaving the other autocomplete stuff enabled, I still get suggestions (I assume Kile picks them up from words previously used in the document) and tab-completing with them works as expected. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 398601] Kile does not remove already typed letters while tab-completing reference
https://bugs.kde.org/show_bug.cgi?id=398601 --- Comment #1 from Kishore Gopalakrishnan --- This only happens if you press tab before the 'suggestion box' appears for completion. If you wait for the suggestion box to appear, and then press tab, the expected behaviour occurs. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 398606] New: 'Help > What's this' doesn't work on toolbar items
https://bugs.kde.org/show_bug.cgi?id=398606 Bug ID: 398606 Summary: 'Help > What's this' doesn't work on toolbar items Product: okular Version: 1.5.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- If go to 'help > What's this', and try to use it on any of the toolbar buttons, we simply get a red crossed circle on the cursor, indicating that the item is not clickable. I couldn't find any item that was clickable (I tried the sidebar and the page bar as well). In Kate, for example, the analogous help item works on toolbar buttons etc., so this seems to be some issue with Okular. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 398605] New: Closing the 'find' toolbar should clear search field
https://bugs.kde.org/show_bug.cgi?id=398605 Bug ID: 398605 Summary: Closing the 'find' toolbar should clear search field Product: okular Version: 1.5.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Steps to reproduce: 1. Open a PDF file. 2. Search for a word it contains (using the toolbar that appears when you press 'CTRL+F'). 3. The result is highlighted in the PDF. 4. Now close the search toolbar. Observed result: Note that the search result is still highlighted. Removing this highlight requires one to manually clear the search toolbar before closing it. On pressing 'CTRL+F' again, one sees that the earlier search result is still in the search field. Clearing this clears the highlight. Expected result: The search field text should be cleared on closing the toolbar, so that the search highlight is not shown when the toolbar is not visible. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 398604] New: In .okular files, inline note wraps per character
https://bugs.kde.org/show_bug.cgi?id=398604 Bug ID: 398604 Summary: In .okular files, inline note wraps per character Product: okular Version: 1.5.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Steps to reproduce: 1. Open a djvu file. 2. Make an inline note. 3. Save as .okular file. 4. Open resulting .okular file. 5. Resize inline note such that the text is wrapped. Observed result: Text is wrapped per-character, i.e., the wrapping breaks words across lines. This impairs the readability of the text in the note. Expected result: The wrapping should not break words, as is the case in inline notes in PDF files. I'm not sure if this is a bug in the djvu backend or something else, so I am putting it under 'general'. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 398601] Kile does not remove already typed letters while tab-completing reference
https://bugs.kde.org/show_bug.cgi?id=398601 Kishore Gopalakrishnan changed: What|Removed |Added Summary|Does not remove already |Kile does not remove |typed letters while |already typed letters while |tab-completing reference|tab-completing reference -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 398601] New: Does not remove already typed letters while tab-completing reference
https://bugs.kde.org/show_bug.cgi?id=398601
Bug ID: 398601
Summary: Does not remove already typed letters while
tab-completing reference
Product: kile
Version: 2.9.92
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: editor
Assignee: michel.lud...@kdemail.net
Reporter: kishor...@gmail.com
Target Milestone: ---
Steps to reproduce:
1. In a .tex file, define a label with '\label{eq: Faraday}'.
2. Save the document.
3. Type '\ref{eq: F' and press 'tab'
Observed result:
The reference is completed as '\ref{eq: Feq: Faraday'.
Expected result:
Kile should take into account the already typed letters while tab-completing.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 398474] New: Kwin sometimes freezes, consuming 100% of one CPU core
https://bugs.kde.org/show_bug.cgi?id=398474 Bug ID: 398474 Summary: Kwin sometimes freezes, consuming 100% of one CPU core Product: kwin Version: 5.13.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Sometimes kwin freezes, and does not respond to mouse movement, keyboard shortcuts etc. It usually happens when I am triggering the 'desktop grid' effect via a screen corner, and the animation just stops halfway. However, I cannot reporduce this consistently, and I am not sure if this is actually the trigger. If I switch to a tty during such a freeze and open htop, I find that kwin_x11 is taking 100% of a CPU core. It does not respond to SIGTERM, so I usually have to send SIGKILL and then start kwin again. I tried to capture to output of kwin during one such run (by starting kwin using something like 'nohup kwin_x11 --replace > kwin_log_20180911-0915.txt &', and it is below: OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile OpenGL version string: 4.5 (Core Profile) Mesa 18.1.8 OpenGL shading language version string: 4.50 Driver: Intel GPU class: Haswell OpenGL version: 4.5 GLSL version: 4.50 Mesa version: 18.1.8 X server version: 1.20.1 Linux kernel version: 4.18.6 Requires strict binding:yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no kwin_x11: ../libepoxy/src/dispatch_common.c:858: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed. After the last line, there is some stuff about raising a crash handler, which I assume happens when I kill the process. I am runnning Arch Linux, and using the 'xf86-video-intel' driver. I am not sure what other information would be relevant here. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397968] New: Arrow symbols to expand and contract recipient lists are interchanged
https://bugs.kde.org/show_bug.cgi?id=397968 Bug ID: 397968 Summary: Arrow symbols to expand and contract recipient lists are interchanged Product: kmail2 Version: 5.9.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- When we view an email with lots of recipients in the 'message preview' pane, or the dedicated 'read message' window, the list of addresses in the 'To:' field is contracted. Currently, a 'left-pointing double arrow' is displayed when the list is contracted, and a 'down-pointing double arrow' is displayed when the list is expanded. I feel that the display should actually be inverted, i.e. the symbol diplayed should indicate what the button will do, rather than indicating the current state. This makes sense since this is a clickable element that performs an action (similar logic is used for play/pause buttons in music players, for instance). -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 397966] New: Tab character shown in clipboard preview is too messy
https://bugs.kde.org/show_bug.cgi?id=397966 Bug ID: 397966 Summary: Tab character shown in clipboard preview is too messy Product: klipper Version: 5.13.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: plasma-widget Assignee: plasma-b...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Created attachment 114646 --> https://bugs.kde.org/attachment.cgi?id=114646=edit Screenshot showing the issue The symbol shown for the 'tab' character in the clipboard preview looks very messy due to the small font size used in the preview. This makes it difficult to tell at a glance what is actually there. Perhaps a different symbol for the tab character would be a good idea. For example, a single horizontal arrow pointing right (would this have to point left for right-to-left languages?) would convey the intended message, while being much more readable. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 186531] [JJ] Trim Margin doesn't work if paper color was set
https://bugs.kde.org/show_bug.cgi?id=186531 --- Comment #23 from Kishore Gopalakrishnan --- Is this bug still reproducible? As of version 1.5.0, 'trim margins' works for me with 'accessibility > change light and dark colours' enabled, and the paper colour set to dark grey. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 397843] New: 'Position' is mispelled in balooctl indexSize output
https://bugs.kde.org/show_bug.cgi?id=397843 Bug ID: 397843 Summary: 'Position' is mispelled in balooctl indexSize output Product: frameworks-baloo Version: 5.47.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: balooctl Assignee: baloo-bugs-n...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- If we type 'balooctl indexSize', we get ``` Actual Size: 77.68 MiB Expected Size: 49.20 MiB PostingDB: 10.02 MiB20.364 % PosistionDB: 11.73 MiB23.841 % ... ``` 'Position' is mispelled above. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 397842] New: Option to 'unload all tabs' on a per-window basis.
https://bugs.kde.org/show_bug.cgi?id=397842 Bug ID: 397842 Summary: Option to 'unload all tabs' on a per-window basis. Product: Falkon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: now...@gmail.com Reporter: kishor...@gmail.com Target Milestone: --- It would be useful to have an 'unload all tabs' option that works on a per-window basis, instead of having to individually unload each tab. While the option to 'unload' tree is available if one uses the 'tree mode' of the vertical tabs extension, it is not accessible if one uses the 'tab list' mode, the 'tab manager' sidebar, or just the tab bar. Ideally, it would appear in the menu that is shown when you right-click on the tab bar, along with 'reload all tabs' and 'bookmark all tabs'. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 397841] New: Scrolling to set time is unusable on touchpads
https://bugs.kde.org/show_bug.cgi?id=397841 Bug ID: 397841 Summary: Scrolling to set time is unusable on touchpads Product: kdeplasma-addons Version: 5.13.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: timer Assignee: plasma-b...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- If one tries to set the duration in the timer widget by scrolling on a touchpad, one finds that the scroll is too sensitive. Unlike a mouse wheel, it is very difficult to scroll only by one 'unit' with a touchpad. For laptop users, it would be nice to have a 'set custom duration' option in the right click menu, which would allow one to use the keyboard to enter the desired digits. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394747] Tabs should not be hidden when we scroll
https://bugs.kde.org/show_bug.cgi?id=394747 --- Comment #14 from Kishore Gopalakrishnan --- In Settings > Window Management > Window Rules, the windows that open when we click 'new rule' and 'modify rule' are also too big, and should have scrollbars. This particular window doesn't seem to be mentioned in the Phabricator page linked for the KCM redesign. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394747] Tabs should not be hidden when we scroll
https://bugs.kde.org/show_bug.cgi?id=394747 --- Comment #12 from Kishore Gopalakrishnan --- (In reply to Nate Graham from comment #11) > The best we can do is enforce a maximum > height for KCMs that use tabs such that when opened in kcmshell, no vertical > scrollbar will ever be needed to fit the whole thing. Is there some technical issue that prevents putting the scrollbars inside the tabs like in the touchpad KCM, or is that what you mean by enforcing a maximum height? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394747] Tabs should not be hidden when we scroll
https://bugs.kde.org/show_bug.cgi?id=394747 --- Comment #10 from Kishore Gopalakrishnan --- Even Window Management > Window behaviour (specifically the 'focus' tab) wouldn't have fit on the screen without a scrollbar if I'd had a large panel and a titlebar. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394747] Tabs should not be hidden when we scroll
https://bugs.kde.org/show_bug.cgi?id=394747 --- Comment #9 from Kishore Gopalakrishnan --- Created attachment 114330 --> https://bugs.kde.org/attachment.cgi?id=114330=edit Touchpad KCM, which shows the ideal behaviour While looking through the various KCMs, I noticed that input devices > touchpad (image attached) has what I would consider the ideal behaviour (there is a scroll area inside each tab). The following KCMs did not fit without a scrollbar on a 768 px tall screen, of which maybe 20 pixels were taken up by the panel. The available height would probably be even smaller for people who don't hide titlebars and borders for maximised windows. Desktop behaviour > virtual desktops (I have 16 virtual desktops, so that might be the reason. I think the default is 9, which would *just* fit there) Display and monitor > displays (There are no tabs here, so there is no problem) Multimedia > audio volume (Not on my setup, but it could become too tall if there are 4–5 applications playing audio. I'm not sure what would happen then) Power management > Energy saving Input devices > touchpad (this behaves properly, as seen in the attached image) I'm not sure about the 'printers' KCM, since I don't have any print service installed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394747] Tabs should not be hidden when we scroll
https://bugs.kde.org/show_bug.cgi?id=394747 --- Comment #7 from Kishore Gopalakrishnan --- Created attachment 114315 --> https://bugs.kde.org/attachment.cgi?id=114315=edit Screenshot showing the issue @Nate As you can see in the attached screenshot, the tabs get cut off even when we scroll vertically. Ideally, the scrollbar would only scroll the stuff below the tab bar, leaving the tab bar always on top. I don't think this should be marked as a duplicate of bug 389585. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 397039] When a PDF file is saved using file > save as, the file path in file > properties is not updated
https://bugs.kde.org/show_bug.cgi?id=397039 Kishore Gopalakrishnan changed: What|Removed |Added Summary|When a PDF file is saved|When a PDF file is saved |using file> save as, the|using file > save as, the |file path in file > |file path in file > |proerties is not updated|properties is not updated -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 397039] New: When a PDF file is saved using file> save as, the file path in file > proerties is not updated
https://bugs.kde.org/show_bug.cgi?id=397039 Bug ID: 397039 Summary: When a PDF file is saved using file> save as, the file path in file > proerties is not updated Product: okular Version: 1.4.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Steps to reproduce: 1. Settings > configure okular 2. Uncheck 'display document title...' if it is checked. 3. Select 'display full file path' when not displaying document title. 4. Open a PDF file. 5. File > Save as; save it somewhere else under a different name in a different location 6. Note that the window title changes, indicating that okular is showing the file in the new location. 7. Go to File > Properties. 8. Look at the value of 'file path'. Observed results: The file path shown in the properties dialogue is the old path, but the new path is shown in the window title. Reloading the file by pressing 'F5' updates the path in File > Properties to the new location. Expected results: The new path and filename should be shown both in the window title and the Properties dialogue. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 397005] When spectacle is launched, the focus should be on the 'save' button
https://bugs.kde.org/show_bug.cgi?id=397005 --- Comment #2 from Kishore Gopalakrishnan --- Ah. I didn't realise Ctrl+S would work here. Then the current setup makes more sense, I guess. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397006] New: Keyboard indicator systray item does not handle multiple lock keys properly.
https://bugs.kde.org/show_bug.cgi?id=397006 Bug ID: 397006 Summary: Keyboard indicator systray item does not handle multiple lock keys properly. Product: plasmashell Version: 5.13.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: kishor...@gmail.com Target Milestone: 1.0 This is about the system tray item that indicates when Caps Lock or Num Lock are pressed. If we press both Caps and Num Lock (in any order), it simply shows the icon for Caps Lock. Ideally, it would either show a separate icon in the system tray for each key, or there would be some other way to show that multiple locks are active. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 397005] New: When spectacle is launched, the focus should be on the 'save' button
https://bugs.kde.org/show_bug.cgi?id=397005 Bug ID: 397005 Summary: When spectacle is launched, the focus should be on the 'save' button Product: Spectacle Version: 18.04.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: kishor...@gmail.com Target Milestone: --- When I launch Spectacle, it takes a screenshot and a window opens showing various options to take a new screenshot, change type of screenshot etc. Currently, the keyboard focus is initially on the Capture mode> Area drop-down list. I think it would be better to initially have the focus on the 'save' button, so that the user can just press space and be done if there are no changes to be made. In case there are changes, a typical user would have to tab / use the mouse anyway to select various options no matter where the inital focus is. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 396535] New: Balooctl seems to assume folders with hyphens in name are subfolders
https://bugs.kde.org/show_bug.cgi?id=396535 Bug ID: 396535 Summary: Balooctl seems to assume folders with hyphens in name are subfolders Product: frameworks-baloo Version: 5.47.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: balooctl Assignee: baloo-bugs-n...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Steps to reproduce: 1. Create folders '~/test1', '~/test2' and '~/test1-test' 2. Run 'balooctl config add excludeFolders ~/test1' 3. Run 'balooctl config add excludeFolders ~/test2' 4. Run 'balooctl config add excludeFolders ~/test1-test' Observed results: Commands in step 2 and 3 succeed, but command in step 4 fails with output 'Parent folder /home/user/test1 is already in the list of exclude folders' Expected results: All three commands should be able to add the respective folders to the list of excluded folders. Baloo seems to detect folders with hyphens in name as subfolders. This should not happen. Quoting the filename and giving the full path does not seem to affect this behaviour. However, adding via the graphical settings (System settings > search > file search) works for such folders. Sorry for the title, but I couldn't think of a proper way to describe this in that space in a more specific way. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 186531] [JJ] Trim Margin doesn't work if paper color was set
https://bugs.kde.org/show_bug.cgi?id=186531 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 375467] Cantor hangs at "Initializing Session" when choosing Sage backend (Sage version 7.6)
https://bugs.kde.org/show_bug.cgi?id=375467 --- Comment #20 from Kishore Gopalakrishnan --- (In reply to Nikita Sirgienko from comment #19) > Now, on master branch, Cantor have patch for sage login for versions 8.1 and > 8.2 (I think the patch also can work with future 8.3 version) > I will want to add this patch in 18.04.3 release, but it will be usefull, if > this patch will be tested before release not only by developers. > Could anybody with Sage 8.1 or 8.2 builds Cantor from source code and > confirm, that login starts work correctly? Cantor built from source works on Arch with sagemath version 8.2. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 390266] Krunner window width should be adjustible
https://bugs.kde.org/show_bug.cgi?id=390266 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 395593] New: There should be an option to hide the tab bar only when the vertical tabs sidebar is shown
https://bugs.kde.org/show_bug.cgi?id=395593 Bug ID: 395593 Summary: There should be an option to hide the tab bar only when the vertical tabs sidebar is shown Product: Falkon Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: kishor...@gmail.com Target Milestone: --- Currently, the settings of the 'vertical tabs' extension only allow to permanently hide the tab bar (using the 'use as replacement for main tab bar' option). It would be nice to have an option to automatically hide the tab bar only when the vertical tabs sidebar is shown. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395432] In sidebar view, clicking a search result should show the result with the relevant subcategories displayed as well
https://bugs.kde.org/show_bug.cgi?id=395432 --- Comment #1 from Kishore Gopalakrishnan --- Created attachment 113351 --> https://bugs.kde.org/attachment.cgi?id=113351=edit Display when we navigate to the 'mouse' KCM by clicking the subcategories What I meant to say in the previous comment is that the second sidebar visible in the above screenshot should have also been visible when we directly search for 'mouse' in the system settings search bar and click on the result. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395432] New: In sidebar view, clicking a search result should show the result with the relevant subcategories displayed as well
https://bugs.kde.org/show_bug.cgi?id=395432 Bug ID: 395432 Summary: In sidebar view, clicking a search result should show the result with the relevant subcategories displayed as well Product: systemsettings Version: 5.13.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: sidebarview Assignee: notm...@gmail.com Reporter: kishor...@gmail.com Target Milestone: --- Created attachment 113350 --> https://bugs.kde.org/attachment.cgi?id=113350=edit Display when we navigate to the 'mouse' KCM through search If I search for an item in the search bar in the 'system settings' application, I can click on one of the results to go to the relevant KCM. However, doing this does not show the 'complete' sidebar view (i.e. the information on which category the KCM belongs to is missing), which is a bit disorienting. Ideally, the sidebar would be completely expanded even if we have navigated to the KCM by using the search bar. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 394398] Word count option does not work
https://bugs.kde.org/show_bug.cgi?id=394398 --- Comment #1 from Kishore Gopalakrishnan --- Recently, there was a change in Kate to make word count a global preference. The corresponding option shows up in settings > configure Kile > editor > appearance > advanced. However, enabling the option doesn't show the word count on the status bar, as reported earlier. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 395073] New: Make krunner show an option to open a dolphin window with the same search carried out, as the last result of file search
https://bugs.kde.org/show_bug.cgi?id=395073 Bug ID: 395073 Summary: Make krunner show an option to open a dolphin window with the same search carried out, as the last result of file search Product: krunner Version: 5.12.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: filesearch Assignee: baloo-bugs-n...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- If I search a term which matches a lot of files, krunner shows only a small numebr of results. It would be nice if krunner would show an entry at the end, titled 'perform search in dolphin', 'view more results', or something similar, in case the user wishes to view results that are not displayed. This entry would open dolphin, with a search for files matching the term everywhere. Currently, the user has to open a dolphin window, press ctrl+f, type the search query again, and click 'everywhere' to view all the results. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394729] Plasmashell reproducibly crashes when changing Dropbox system tray entry's hidden status
https://bugs.kde.org/show_bug.cgi?id=394729 Kishore Gopalakrishnan <kishor...@gmail.com> changed: What|Removed |Added CC||kishor...@gmail.com --- Comment #1 from Kishore Gopalakrishnan <kishor...@gmail.com> --- Cannot reproduce on Arch Linux with Plasma 5.12.90 and Dropbox 50.4.71. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394550] Plasmashell crashes when right clicking task bar icons
https://bugs.kde.org/show_bug.cgi?id=394550 Kishore Gopalakrishnan <kishor...@gmail.com> changed: What|Removed |Added CC||kishor...@gmail.com --- Comment #1 from Kishore Gopalakrishnan <kishor...@gmail.com> --- Can you try reproducing this with a new user to see if it's a problem with your configuration or something else? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 394513] KDEConnect on Android connecting even on mobile network
https://bugs.kde.org/show_bug.cgi?id=394513 Kishore Gopalakrishnan <kishor...@gmail.com> changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394747] New: Tabs should not be hidden when we scroll
https://bugs.kde.org/show_bug.cgi?id=394747 Bug ID: 394747 Summary: Tabs should not be hidden when we scroll Product: systemsettings Version: 5.12.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- In any KCM where the options available cannot fit in the available window size, scrollbars appear, and we can scroll to access other options. In KCMs with multiple tabs, the tab bar too gets hidden when we scroll (examples of KCMs with multple tabs are 'Input devices > mouse' and 'power management > energy saving'). This behaviour is present when we access the KCM by browsing through the 'system settings' application, and also when we launch the KCM alone from krunner. It would be better to have the tab area stay visible no matter where we scroll, and scroll only the area containing the options presented by the currently active tab. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 394746] [Feature request] Button to open downloads directory in 'download complete' notification
https://bugs.kde.org/show_bug.cgi?id=394746 Kishore Gopalakrishnan <kishor...@gmail.com> changed: What|Removed |Added Summary|Button to open downloads|[Feature request] Button to |directory in 'download |open downloads directory in |complete' notification |'download complete' ||notification -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 394746] New: Button to open downloads directory in 'download complete' notification
https://bugs.kde.org/show_bug.cgi?id=394746 Bug ID: 394746 Summary: Button to open downloads directory in 'download complete' notification Product: Falkon Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: kishor...@gmail.com Target Milestone: --- It would be nice to have a set of buttons in the 'download complete' notification to open the folder containing the downloaded file, or open the downloaded file. I'm not sure how easy this would be to implement in a way that works for all desktop environments. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 394744] Dolphin cannot browse archives that are not named with the appropriate extension
https://bugs.kde.org/show_bug.cgi?id=394744 --- Comment #1 from Kishore Gopalakrishnan <kishor...@gmail.com> --- I forgot to mention this: the 'extract' option also does not appear in the right-click context menu for archives which don't have an extension. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 394744] New: Dolphin cannot browse archives that are not named with the appropriate extension
https://bugs.kde.org/show_bug.cgi?id=394744 Bug ID: 394744 Summary: Dolphin cannot browse archives that are not named with the appropriate extension Product: dolphin Version: 18.04.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kishor...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- If we have a zip or tar.gz archive, we can usually browse it like a folder. However, if the archive is named without an extension, we get the message 'invalid protocol' when we try to do this. However, the 'information' panel in Dolphin shows that it is correctly detected as having the relevant mime type. Steps to reproduce: 1. Create a folder. 2. Create two text files inside it. 3. Compress the folder as zip, naming it folder.zip, or something similar. 4. Observe that you can enter the archive like a folder and view the text files inside. 5. Now, rename the archive from 'folder.zip' to 'folder' (remove the extension). 6. Now, if you try to browse the archive in Dolphin Observed results: For zip archives without extension, it seems to enter the folder, but does not show the contents. For tar.gz archives without extension, it does not enter the archive, and gives the error 'invalid protocol'. Expected results: Archives which are detected as archives by mimetype should be handled in the same way, regardless of whether they have the appropriate extension. Possibly related: https://bugs.kde.org/show_bug.cgi?id=188989 , but this is about zip archives having a different extension, instead of having no extension. I'm not sure if this is a bug in Dolphin or kio, so I'm filing it under Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 394398] New: Word count option does not work
https://bugs.kde.org/show_bug.cgi?id=394398 Bug ID: 394398 Summary: Word count option does not work Product: kile Version: 2.9.92 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: editor Assignee: michel.lud...@kdemail.net Reporter: kishor...@gmail.com Target Milestone: --- If I enable 'view > show word count', no word count is shown in the status bar. However, word count works in Kate, so it does not seem to be an editor bug per se. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 393952] New: 'Find my phone' does not play any ringtone until the user selects one in the plugin settings
https://bugs.kde.org/show_bug.cgi?id=393952 Bug ID: 393952 Summary: 'Find my phone' does not play any ringtone until the user selects one in the plugin settings Product: kdeconnect Version: 1.8 Platform: Android OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: kishor...@gmail.com Target Milestone: --- I remember this used to work some time ago, so I'm not sure which version the change was introduced in. In the latest version, I noticed that the 'find my phone' plugin had no ringtone selected. I.e., the phone screen would just light up and display the button to stop the 'ringing', but no sound would be played. I had to go the plugin settings > select ringtone on my phone, and select a ringtone to get it to work. Ideally, the app would have the default ringtone pre-selected if the user has not changed the setting. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393948] New: When opening history sidebar, cursor should be in the history search text box
https://bugs.kde.org/show_bug.cgi?id=393948 Bug ID: 393948 Summary: When opening history sidebar, cursor should be in the history search text box Product: Falkon Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: kishor...@gmail.com Target Milestone: --- I often find myself pressing ctrl+h to open history, then start typing to filter history entries, only to realise I have to click on the text box on top of the history sidebar, in order to put the cursor there first. I think you should consider making the cursor focus be there when the sidebar is newly opened. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 375467] Cantor hangs at "Initializing Session" when choosing Sage backend (Sage version 7.6)
https://bugs.kde.org/show_bug.cgi?id=375467 --- Comment #9 from Kishore Gopalakrishnan <kishor...@gmail.com> --- (In reply to Alexander Semke from comment #7) > (In reply to Kishore Gopalakrishnan from comment #6) > > (In reply to Antonio Rojas from comment #5) > > > > With Cantor 17.08.3 and sage 8.0 on Arch linux, if I run 'cantor -b sage' > > from a terminal, there is no terminal output, and Cantor opens, but keeps on > > showing the 'initialising Session' dialog box. > The communication with Sage was made more stable in 18.04. Can you please > check the current release? Do you still have problems with Sage? With Cantor 18.04 and sage version 8.1 on Arch Linux, it now indefinitely has 'calculating...' displayed in the status bar after I enter any sage command in a cell and press shift+enter. No results are displayed, even if I do simple stuff like '2+3 <shift+enter>'. I.e., the sage backend is still completely unusable, although it now seems to start up without any obvious error dialog displayed. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 393274] Android app crashes when multimedia player plugin is enabled
https://bugs.kde.org/show_bug.cgi?id=393274 --- Comment #7 from Kishore Gopalakrishnan <kishor...@gmail.com> --- Created attachment 112335 --> https://bugs.kde.org/attachment.cgi?id=112335=edit Output of 'abd logcat' during such a crash (In reply to Matthijs Tijink from comment #6) > I looked into it and couldn't find a definite answer. Maybe you could test > my suggested change? > > You can download an Android apk at https://phabricator.kde.org/D12618 > Can you try to install this and see if the app still crashes? You might get > prompted to first remove the currently installed KDE Connect app. > > In case it doesn't work, it would be great if you could upload a log > (connect your phone by usb and run "adb logcat" on the command line, then > wait for the app to crash). The new apk you linked at that Phabricator page works. I have also attached the output of 'adb logcat' during a crash, while using the version in the Play Store. I paired the devices with kdeconnect, enabled USB debugging, opened kdeconnect, and then started the command. I immediately went to my music player on my computer and played a music file with album art. After that, I got a message that kdeconnect crashed (on my phone), and I ended the 'adb logcat' command. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 393274] Android app crashes when multimedia player plugin is enabled
https://bugs.kde.org/show_bug.cgi?id=393274 --- Comment #5 from Kishore Gopalakrishnan <kishor...@gmail.com> --- I've been able to reproduce it again. It seems to crash only if the song I'm playing has album art associated with it. This is with Clementine. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 393274] Android app crashes when multimedia player plugin is enabled
https://bugs.kde.org/show_bug.cgi?id=393274 --- Comment #4 from Kishore Gopalakrishnan <kishor...@gmail.com> --- Okay, this is really weird. I can't reproduce it any more. Tested with Clementine and Rhythmbox. I haven't changed the versions of kdeconnect (on my phone and laptop) or Clementine. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 393274] Android app crashes when multimedia player plugin is enabled
https://bugs.kde.org/show_bug.cgi?id=393274 --- Comment #3 from Kishore Gopalakrishnan <kishor...@gmail.com> --- (In reply to Albert Vaca from comment #2) > What media player are you using? I'm using the qt5 branch of Clementine (https://aur.archlinux.org/packages/clementine-qt5-git/). I'll try to reproduce it with some other player, soon. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 393636] New: When an image is copied to clipboard, the preview in the Klipper popup is scaled to fit the width of the popup
https://bugs.kde.org/show_bug.cgi?id=393636 Bug ID: 393636 Summary: When an image is copied to clipboard, the preview in the Klipper popup is scaled to fit the width of the popup Product: klipper Version: 5.12.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: plasma-widget Assignee: mgraess...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- If I copy an image (eg. in Okular, open a PDF, right-click drag, and select to copy as an image to clipboard) that is much taller than it is wide, the preview shown in the popup (the one that appears when you left-click the clipboard system tray item) is scaled to fit width. This means I have to scroll very far to reach the next item. Perhaps you could consider making sure this image preview is scaled in such a way that it does not go out of the popup, and thus one does not need to scroll too far to reach the next item. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393629] New: Vertical tabs does not remember shown or hidden status
https://bugs.kde.org/show_bug.cgi?id=393629 Bug ID: 393629 Summary: Vertical tabs does not remember shown or hidden status Product: Falkon Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: kishor...@gmail.com Target Milestone: --- If I have the 'vertical tabs' extension enabled, it does not remember whether I currently have the 'vertical tabs' sidebar shown or hidden. Instead, it is always shown when I open a new window. My use case is that I would like to use it only when I have a lot of tabs open, but hide it when I only have a few tabs. Currently, I have to either use the 'tab manager' sidebar (which is frankly a bit of an overkill if I'm just using it for tab switching) or go into the settings and enable the 'vertical tabs' extension only when I want to use it. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 393616] New: Kate cuts off lower part of letters on last line
https://bugs.kde.org/show_bug.cgi?id=393616 Bug ID: 393616 Summary: Kate cuts off lower part of letters on last line Product: kate Version: 18.04.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Created attachment 112299 --> https://bugs.kde.org/attachment.cgi?id=112299=edit Screenshot showing the issue Kate cuts off the lower parts of letters like 'g' and 'j' that are on the last line of a text file (see attached screenshot). -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 386513] Krunner memory leak
https://bugs.kde.org/show_bug.cgi?id=386513 --- Comment #5 from Kishore Gopalakrishnan <kishor...@gmail.com> --- Sorry for the double comment. I double clicked the 'save changes' button, and I got some error about detecting a 'mid air collision', and I pressed the 'submit my new comment' button, assuming it would send only the new comment. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 386513] Krunner memory leak
https://bugs.kde.org/show_bug.cgi?id=386513 --- Comment #4 from Kishore Gopalakrishnan <kishor...@gmail.com> --- So I ran some tests on this. The leak does not happen (or is very slow) when no runners are enabled. However, I am able to trigger it with either the 'applications' (launch applications) runner, or the 'windows' (find open windows) runner alone enabled. I noticed that the speed of the memory usage increase seemes to increase with the number of results returned by krunner. For example, if I had lots of windows open, and I typed a query that would result in a large number of results being returned (like typing 'kons' with 20 or so Konsole windows open), the memory usage would jump by roughly or more 5 MB each time. This is with krunner 5.12.4, and Qt 5.10.1. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 386513] Krunner memory leak
https://bugs.kde.org/show_bug.cgi?id=386513 --- Comment #3 from Kishore Gopalakrishnan <kishor...@gmail.com> --- So I ran some tests on this. The leak does not happen (or is very slow) when no runners are enabled. However, I am able to trigger it with either the 'applications' (launch applications) runner, or the 'windows' (find open windows) runner alone enabled. I noticed that the speed of the memory usage increase seemes to increase with the number of results returned by krunner. For example, if I had lots of windows open, and I typed a query that would result in a large number of results being returned (like typing 'kons' with 20 or so Konsole windows open), the memory usage would jump by roughly or more 5 MB each time. This is with krunner 5.12.4, and Qt 5.10.1. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 387454] MTP doesn't work in KDE with Linux 4.14
https://bugs.kde.org/show_bug.cgi?id=387454 Kishore Gopalakrishnan <kishor...@gmail.com> changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 392913] NTFS mountpoints appears as hidden after mount
https://bugs.kde.org/show_bug.cgi?id=392913 Kishore Gopalakrishnan <kishor...@gmail.com> changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 393274] Android app crashes when multimedia player plugin is enabled
https://bugs.kde.org/show_bug.cgi?id=393274 --- Comment #1 from Kishore Gopalakrishnan <kishor...@gmail.com> --- I forgot to mention in my previous comment that, as far as I can tell, there are no issues when I disable the 'multimedia control' plugin. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 393274] New: Android app crashes when multimedia player plugin is enabled
https://bugs.kde.org/show_bug.cgi?id=393274 Bug ID: 393274 Summary: Android app crashes when multimedia player plugin is enabled Product: kdeconnect Version: 1.8 Platform: Android OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: kishor...@gmail.com Target Milestone: --- The android application crashes regularly if the 'multimedia player' plugin is enabled. When this happens, I get an option to 'send feedback' (I tried this once), but I don't know how to access those crash logs directly. On my Android device, I am using the latest version on the Play Store (1.8.2); my laptop's version of kdeconnect is 1.3 After kdeconnect crashes, the persistent notification it sends gets stuck in the notification area. This is on a Moto G4 running Android 7.0. I couldn't find any errrors in the logs on my laptop too. I'm not sure what other information might be relevant, so feel free to ask for more. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393162] Certificate error dialog should be allowed to be ignored on pages
https://bugs.kde.org/show_bug.cgi?id=393162 --- Comment #2 from Kishore Gopalakrishnan <kishor...@gmail.com> --- But sometimes I might not want to accept the certificate, since, for example, it's from a news website I don't particularly trust, and it doesn't seem to be necessary to view the content of the webpage. I still think that to deal with cases such as the one mentioned in the first comment, there should either be an option to 'reject and close tab', or 'ignore requests' in the aforementioned dialog. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 393224] New: Kbibtex does not detect lyx pipe created by Kile
https://bugs.kde.org/show_bug.cgi?id=393224 Bug ID: 393224 Summary: Kbibtex does not detect lyx pipe created by Kile Product: KBibTeX Version: 0.7 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: fisc...@unix-ag.uni-kl.de Reporter: kishor...@gmail.com Target Milestone: --- Kile (I'm using version 2.9.91 of Kile) creates its lyx pipe in /tmp. Kbibtex does not seem to be able to detect it automatically (the 'send to LyX/Kile' feature does not work). However, if I manually specify the location of the pipe in 'settings > configure kbibtex > saving and exporting > Manually specified LyX pipe', I am able to use the aforementioned feature properly. Kbibtex should also search in /tmp for a Lyx pipe. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 393224] Kbibtex does not automatically detect lyx pipe created by Kile
https://bugs.kde.org/show_bug.cgi?id=393224 Kishore Gopalakrishnan <kishor...@gmail.com> changed: What|Removed |Added Summary|Kbibtex does not detect lyx |Kbibtex does not |pipe created by Kile|automatically detect lyx ||pipe created by Kile -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393162] New: Certificate error dialog should be allowed to be ignored on pages
https://bugs.kde.org/show_bug.cgi?id=393162 Bug ID: 393162 Summary: Certificate error dialog should be allowed to be ignored on pages Product: Falkon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: kishor...@gmail.com Target Milestone: --- Recently I visited a news website, on which for some reason, I kept on getting spammed with error dialogs regarding unrecognised certificates. I couldn't close the page or the browser, since the dialog kept on popping up as soon as I clicked 'no'. I ended up having to use the system monitor to kill by browser. There should be some way to automatically reject certificate requests from a particular site, in order to prevent such issues and allow the browser to remain usable. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362844] Drag and Drop in Present windows
https://bugs.kde.org/show_bug.cgi?id=362844 Kishore Gopalakrishnan <kishor...@gmail.com> changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392799] Window contents also scroll while using alt + scroll wheel to change opacity
https://bugs.kde.org/show_bug.cgi?id=392799 --- Comment #6 from Kishore Gopalakrishnan <kishor...@gmail.com> --- (In reply to Martin Flöser from comment #5) > Please test a gtk-3 application instead of Gimp. If you cannot reproduce > there it should be reported to Qt. I cannot reproduce this with gedit. Is it alright if I just report the bug to Qt as 'Qt applications accept mouse events although another application has a mouse grab', or is there some other relevant information I would need to give them for this bug? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392799] Window contents also scroll while using alt + scroll wheel to change opacity
https://bugs.kde.org/show_bug.cgi?id=392799 --- Comment #4 from Kishore Gopalakrishnan <kishor...@gmail.com> --- (In reply to Martin Flöser from comment #3) > To a certain degree this is also an application bug as they > accept mouse events although another application has a mouse grab. This seems to happen in all QT5 applications. However it doesn't seem to happen in GTK applications (I tested with GIMP). Should I report a QT bug? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392799] Window contents also scroll while using alt + scroll wheel to change opacity
https://bugs.kde.org/show_bug.cgi?id=392799 --- Comment #2 from Kishore Gopalakrishnan <kishor...@gmail.com> --- (In reply to Martin Flöser from comment #1) > Is this on X11 or Wayland? This is on X11. I haven't tested on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392799] New: Window contents also scroll while using alt + scroll wheel to change opacity
https://bugs.kde.org/show_bug.cgi?id=392799 Bug ID: 392799 Summary: Window contents also scroll while using alt + scroll wheel to change opacity Product: kwin Version: 5.12.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- If we press 'alt' and scroll with the mouse wheel, kwin changes the opacity of the window under the mouse. However, scroll events are also passed to the window, and thus the window contents also scroll. Steps to reproduce: 1. Open a window in which scrolling is possible (for eg. a long text file in kate or a webpage in a browser). 2. Press alt and scroll down with the mouse wheel. Observed result: The opacity decreases, and the window contents scroll down. Expected result: The opacity should change, but the window contents should not scroll. This bug seems possibly related to bug 368827, but I am reporting it separately since it involves mouse events. -- You are receiving this mail because: You are watching all bug changes.
