[yakuake] [Bug 415762] Exiting the session in a Yakuake tab sometimes crash Yakuake
https://bugs.kde.org/show_bug.cgi?id=415762 --- Comment #12 from Siddhartha Sahu --- Created attachment 128112 --> https://bugs.kde.org/attachment.cgi?id=128112=edit New crash information added by DrKonqi yakuake (3.0.5+) using Qt 5.14.2 - What I was doing when the application crashed: Same as the other reports, yakuake crashes sometimes when a shell is closed using ctrl+d. -- Backtrace (Reduced): #6 0x7ff40ca2916f in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/libQt5Core.so.5 #7 0x7ff40e1b731e in KActionCollection::removeAssociatedWidget(QWidget*) () from /usr/lib/libKF5XmlGui.so.5 #8 0x7ff40e1ffebc in KXMLGUIClient::prepareXMLUnplug(QWidget*) () from /usr/lib/libKF5XmlGui.so.5 #9 0x7ff40e207440 in KXMLGUIFactory::removeClient(KXMLGUIClient*) () from /usr/lib/libKF5XmlGui.so.5 #10 0x7ff3fc506053 in Konsole::SessionController::~SessionController() () from /usr/lib/libkonsoleprivate.so.20 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 415762] Exiting the session in a Yakuake tab sometimes crash Yakuake
https://bugs.kde.org/show_bug.cgi?id=415762 Siddhartha Sahu changed: What|Removed |Added CC||sh.siddhar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 417118] Okular crashes on Print preview
https://bugs.kde.org/show_bug.cgi?id=417118 --- Comment #2 from Siddhartha Sahu --- Built from the latest master (commit on Feb 1): okular-git-r8658.c6d937ab0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 417118] New: Okular crashes on Print preview
https://bugs.kde.org/show_bug.cgi?id=417118 Bug ID: 417118 Summary: Okular crashes on Print preview Product: okular Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: sh.siddhar...@gmail.com Target Milestone: --- Application: okular (1.9.70) (Compiled from sources) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.1-arch1-1 x86_64 Windowing system: X11 Distribution: Arch Linux -- Information about the crash: OPening File -> Print Preview on any pdf file (tried on 3 different ones) crashes Okular. The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd296a50600 (LWP 59660))] Thread 7 (Thread 0x7fd28632f700 (LWP 59666)): #0 0x7fd299a94c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd287828dec in ?? () from /usr/lib/dri/i965_dri.so #2 0x7fd2878289e8 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7fd299a8e4cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fd29a5122d3 in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7fd286b30700 (LWP 59665)): #0 0x7fd299a94c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd287828dec in ?? () from /usr/lib/dri/i965_dri.so #2 0x7fd2878289e8 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7fd299a8e4cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fd29a5122d3 in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7fd27eb30700 (LWP 59664)): #0 0x7fd299a94c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd287828dec in ?? () from /usr/lib/dri/i965_dri.so #2 0x7fd2878289e8 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7fd299a8e4cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fd29a5122d3 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7fd287331700 (LWP 59663)): #0 0x7fd299a94c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd287828dec in ?? () from /usr/lib/dri/i965_dri.so #2 0x7fd2878289e8 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7fd299a8e4cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fd29a5122d3 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7fd28fdd3700 (LWP 59662)): #0 0x7fd29a5079ef in poll () from /usr/lib/libc.so.6 #1 0x7fd298f63120 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fd298f631f1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fd29aac403c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fd29aa6a4cc in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fd29a88ee52 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fd29ad14b28 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x7fd29a88ffc6 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fd299a8e4cf in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fd29a5122d3 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fd295c67700 (LWP 59661)): #0 0x7fd29a5079ef in poll () from /usr/lib/libc.so.6 #1 0x7fd299d0e630 in ?? () from /usr/lib/libxcb.so.1 #2 0x7fd299d102db in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7fd296634b81 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7fd29a88ffc6 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fd299a8e4cf in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fd29a5122d3 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7fd296a50600 (LWP 59660)): [KCrash Handler] #6 0x7fd29b59a6a5 in QAction::setEnabled(bool) () from /usr/lib/libQt5Widgets.so.5 #7 0x7fd28eb1261f in PageView::updateActionState (this=0x55f58f3d05c0, haspages=haspages@entry=false, documentChanged=documentChanged@entry=false, hasformwidgets=hasformwidgets@entry=false) at /usr/src/debug/okular/ui/pageview.cpp:1268 #8 0x7fd28eaa6e18 in Okular::Part::Part (this=this@entry=0x55f58f38abb0, parentWidget=parentWidget@entry=0x7fffe4dade50, parent=parent@entry=0x7fffe4dade50, args=..., __in_chrg=, __vtt_parm=) at /usr/include/c++/9.2.0/bits/atomic_base.h:413 #9 0x7fd28eab00d4 in KPluginFactory::createPartInstance (parentWidget=0x7fffe4dade50, parent=0x7fffe4dade50, args=...) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:536 #10 0x7fd29bb308a5 in KPluginFactory::create (this=0x55f58ebb0dc0, iface=0x7fd29c295a18 "KParts::ReadOnlyPart", parentWidget=0x7fffe4dade50, parent=0x7fffe4dade50, args=..., keyword=...) at /usr/src/debug/kcoreaddons/src/lib/plugin/kpluginfactory.cpp:145 #11 0x7fd28ead58db in KPluginFactory::create
[frameworks-plasma] [Bug 397336] Tooltip timeout is too short and unalterable
https://bugs.kde.org/show_bug.cgi?id=397336 Siddhartha Sahu changed: What|Removed |Added CC||sh.siddhar...@gmail.com --- Comment #5 from Siddhartha Sahu --- This issue remains in plasma git master. I'd prefer tooltips to stay as long as the mouse is over the widgets. I have a bunch to timezones configured in the digital clock widget and face the short timeout issue when the tooltip showing the current time in different timezones closes while I'm still trying to lookup/process it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387901] Task manager loses windows with multi monitor
https://bugs.kde.org/show_bug.cgi?id=387901 Siddhartha Sahu changed: What|Removed |Added CC||sh.siddhar...@gmail.com --- Comment #6 from Siddhartha Sahu --- I am seeing the same issue on git master with the icon-only task manager configured to only show applications in current screen. Disconnecting my external screens does not reset the task manager state and I have to restart plasmashell as a workaround. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 409285] New: Dolphin crash when copying files to pen drive
https://bugs.kde.org/show_bug.cgi?id=409285 Bug ID: 409285 Summary: Dolphin crash when copying files to pen drive Product: dolphin Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sh.siddhar...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (19.07.70) (Compiled from sources) Qt Version: 5.12.4 Frameworks Version: 5.60.0 Operating System: Linux 5.1.15-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Dragged and dropped a file to the flash drive entry in the dolphin pane and selected "copy file" -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8e461bbc80 (LWP 1680))] Thread 5 (Thread 0x7f8e37fff700 (LWP 1685)): #0 0x7f8e4e1d4667 in poll () from /usr/lib/libc.so.6 #1 0x7f8e496937c0 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f8e496938ae in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f8e4c16327c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f8e4c10a3ac in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f8e4bf459c5 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f8e4bf46bf0 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f8e4a5f457f in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f8e4e1df0e3 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f8e3dcb4700 (LWP 1684)): #0 0x7f8e4a5fa415 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f8e3e169f7c in ?? () from /usr/lib/dri/i965_dri.so #2 0x7f8e3e169b78 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7f8e4a5f457f in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f8e4e1df0e3 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f8e3700 (LWP 1683)): #0 0x7f8e4e1d018c in read () from /usr/lib/libc.so.6 #1 0x7f8e49641961 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f8e49691f70 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7f8e49693766 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7f8e496938ae in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7f8e4c16327c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f8e4c10a3ac in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7f8e4bf459c5 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7f8e4c3dfb37 in ?? () from /usr/lib/libQt5DBus.so.5 #9 0x7f8e4bf46bf0 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7f8e4a5f457f in start_thread () from /usr/lib/libpthread.so.0 #11 0x7f8e4e1df0e3 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f8e4518f700 (LWP 1682)): #0 0x7f8e4e1d4667 in poll () from /usr/lib/libc.so.6 #1 0x7f8e4a81d630 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f8e4a81f2db in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f8e45d80079 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7f8e4bf46bf0 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f8e4a5f457f in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f8e4e1df0e3 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f8e461bbc80 (LWP 1680)): [KCrash Handler] #6 QSharedDataPointer::~QSharedDataPointer (this=0x555a9f40f6e0, __in_chrg=) at /usr/include/c++/9.1.0/bits/atomic_base.h:326 #7 KFileItem::~KFileItem (this=0x555a9f40f6e0, __in_chrg=) at /usr/src/debug/kio/src/core/kfileitem.h:47 #8 0x7f8e4db43433 in QList::node_destruct (this=0x555a9f0cde30, n=0x555a9f40f6e0) at /usr/include/qt/QtCore/qlist.h:452 #9 QList::erase (it=..., this=0x555a9f0cde30) at /usr/include/qt/QtCore/qlist.h:539 #10 KCoreDirListerCache::reinsert (oldUrl=..., item=..., this=0x7f8e4dbb2500 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>) at /usr/src/debug/kio/src/core/kcoredirlister_p.h:309 #11 KCoreDirListerCache::processPendingUpdates (this=0x7f8e4dbb2500 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>) at /usr/src/debug/kio/src/core/kcoredirlister.cpp:2014 #12 0x7f8e4c137460 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #13 0x7f8e4c1443f8 in QTimer::timeout(QTimer::QPrivateSignal) () from /usr/lib/libQt5Core.so.5 #14 0x7f8e4c137cd5 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #15 0x7f8e4cbdd485 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #16 0x7f8e4cbe69b1 in
[kdeconnect] [Bug 408399] Add pointer feature to slideshow remote plugin
https://bugs.kde.org/show_bug.cgi?id=408399 Siddhartha Sahu changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Siddhartha Sahu --- Found this was already reported. *** This bug has been marked as a duplicate of bug 403500 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 403500] Add a "laser pointer" in presentation mode
https://bugs.kde.org/show_bug.cgi?id=403500 Siddhartha Sahu changed: What|Removed |Added CC||sh.siddhar...@gmail.com --- Comment #1 from Siddhartha Sahu --- *** Bug 408399 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 408399] New: Add pointer feature to slideshow remote plugin
https://bugs.kde.org/show_bug.cgi?id=408399 Bug ID: 408399 Summary: Add pointer feature to slideshow remote plugin Product: kdeconnect Version: unspecified Platform: Android OS: Android 9.x Status: REPORTED Severity: wishlist Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: sh.siddhar...@gmail.com Target Milestone: --- I loved the slideshow remote feature after discovering it recently. I can see this being a quick replacement for my hardware presenter, except for one missing feature: a pointer. It'd be great if the cursor control from the "remote input" plugin could be combined with "slideshow remote". * I don't know how hard this is, but on activating "slideshow remote", the mouse pointer on the laptop screen should change to a visible red dot similar to what google slides allows and how the laser in a hardware pointer works. Bonus if the color can be configured. * I tried navigating the normal mouse pointer using the "remote input" plugin, but the speed/acceleration of the pointer was that great. The combined plugin should allow easy navigation through the entire presentation screen area easily enough. (Using version 1.12.7 on Android currently) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 408398] New: Inhibit screensaver plugin should take into account critical battery level settings
https://bugs.kde.org/show_bug.cgi?id=408398 Bug ID: 408398 Summary: Inhibit screensaver plugin should take into account critical battery level settings Product: kdeconnect Version: 1.3.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: sh.siddhar...@gmail.com Target Milestone: --- SUMMARY Currently, I like to use the inhibit screensaver plugin to disable screen locking when kdeconnect is active. However, this also disables the laptop suspend, even in battery mode. What I ideally want is to enable this feature, but if battery reaches a critical level, the power management settings should take over and the laptop should get suspended. STEPS TO REPRODUCE 1. Enable "Inhibit screensaver" plugin and connect phone to laptop. 2. Laptop lock screen is disabled 3. Turn off AC power for laptop until "critical level" as defined in power management settings is reached. OBSERVED RESULT Laptop does not suspend, as configured in settings and keeps running until it runs out of battery and forcefully shuts down. EXPECTED RESULT At critical level, power management settings should override kdeconnect and configured action (suspend in my case) should be performed. SOFTWARE/OS VERSIONS Linux/KDE Plasma KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION I'm not 100% sure that this is due to the kdeconnect config, but I think the above is the current behavior. I do see the message "kdeconnect is currently inhibiting power management". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407473] Modify lock screen timeout behaviour for wrong passwords
https://bugs.kde.org/show_bug.cgi?id=407473 --- Comment #3 from Siddhartha Sahu --- I figured out one way to do this, and opened a RR at https://phabricator.kde.org/D21192. Please take a look and see if this makes sense. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407473] Modify lock screen timeout behaviour for wrong passwords
https://bugs.kde.org/show_bug.cgi?id=407473
--- Comment #2 from Siddhartha Sahu ---
Thanks Nate! So I did this and the text input doesn't get blocked anymore.
```
diff --git a/lookandfeel/contents/lockscreen/MainBlock.qml
b/lookandfeel/contents/lockscreen/MainBlock.qml
index 97e7e943..529ccea3 100644
--- a/lookandfeel/contents/lockscreen/MainBlock.qml
+++ b/lookandfeel/contents/lockscreen/MainBlock.qml
@@ -59,7 +59,6 @@ SessionManagementScreen {
focus: true
echoMode: TextInput.Password
inputMethodHints: Qt.ImhHiddenText | Qt.ImhSensitiveData |
Qt.ImhNoAutoUppercase | Qt.ImhNoPredictiveText
-enabled: !authenticator.graceLocked
revealPasswordButtonShown: true
onAccepted: {
@@ -93,6 +92,7 @@ SessionManagementScreen {
PlasmaComponents.Button {
id: loginButton
Layout.fillWidth: true
+enabled: !authenticator.graceLocked
text: i18nd("plasma_lookandfeel_org.kde.lookandfeel", "Unlock")
onClicked: startLogin()
```
I'm not sure what to change on line 88 that you linked. I guess another event
should replace "onClearPassword", maybe loginButton.onsubmit but I couldn't get
it to work yet.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 407473] New: Modify lock screen timeout behaviour for wrong passwords
https://bugs.kde.org/show_bug.cgi?id=407473 Bug ID: 407473 Summary: Modify lock screen timeout behaviour for wrong passwords Product: plasmashell Version: 5.15.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Lock/logout applet Assignee: plasma-b...@kde.org Reporter: sh.siddhar...@gmail.com Target Milestone: 1.0 Currently, the password input in the login/lock screen gets disabled for a timeout period after entering a wrong password. This is all good, but the behaviour can be slightly improved I think. Instead of disabling both the input field and the login button/action, just disable the login action, so that the user can continue to edit/retype the password while waiting for the timeout to expire. This way the user can save on some of the waiting time. Especially, by the time the user is done retyping, the timeout would have expired and the user can proceed to the login action. Apologies if there is already a way to do this easily or already been reported. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404789] New: Refresh user application desktop files
https://bugs.kde.org/show_bug.cgi?id=404789 Bug ID: 404789 Summary: Refresh user application desktop files Product: plasmashell Version: 5.15.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: sh.siddhar...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY On ArchLinux, changes to system desktop files are automatically rebuilt after each update by pacman. However, it is a little more difficult to change user desktop files. STEPS TO REPRODUCE 1. Make changes to user desktop files in ~/.local/share/applications OBSERVED RESULT Changes are not reflected in Kicker EXPECTED RESULT There should be a user visible way to refresh the entries. I know about kbuildsycoca5 after a web search, but I think from a usability perspective, there should be a graphical way to refresh the desktop files, maybe in the context menu or in the Menu editor. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.15.1 KDE Frameworks Version: 5.55 Qt Version: 5.12.1 -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 404110] Cannot auto-scroll the PDF preview anymore
https://bugs.kde.org/show_bug.cgi?id=404110 Siddhartha Sahu changed: What|Removed |Added CC||sh.siddhar...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Siddhartha Sahu --- It seems from the screenshot that "Live preview" is disabled, which is needed for auto-scroll and compile on save. Enable live preview, either using the button on the bottom of the window below the editor pane (below Next Latex Badbox in your screenshot) or from Build -> Live Preview menu, and try again. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379865] Unable to type in Konsole using Tamil language input
https://bugs.kde.org/show_bug.cgi?id=379865 Siddhartha Sahu changed: What|Removed |Added CC||sh.siddhar...@gmail.com --- Comment #1 from Siddhartha Sahu --- I just tried typing in tamil on konsole 18.08.2 and it works. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 346144] akonadi_launcher_agent crashes repeatedly
https://bugs.kde.org/show_bug.cgi?id=346144 Siddhartha Sahu <sh.siddhar...@gmail.com> changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INVALID -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393413] Dolphin crash when previewing mp4
https://bugs.kde.org/show_bug.cgi?id=393413 Siddhartha Sahu <sh.siddhar...@gmail.com> changed: What|Removed |Added CC||sh.siddhar...@gmail.com --- Comment #1 from Siddhartha Sahu <sh.siddhar...@gmail.com> --- Do you get this crash consistently? Can you update your packages and check? I cannot reproduce this on Arch Linux (Dolphin 18.04.0 and Qt 5.10.1). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393352] New: Slow plasma startup
https://bugs.kde.org/show_bug.cgi?id=393352 Bug ID: 393352 Summary: Slow plasma startup Product: plasmashell Version: 5.12.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sh.siddhar...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 112144 --> https://bugs.kde.org/attachment.cgi?id=112144=edit Bootchart showing plasma startup sequence Please find attached a bootchart showing my plasma startup. Steps: 1) Reboot and login to tty1. 2) Start systemd-bootchart: `/usr/lib/systemd/systemd-bootchart -o /tmp -r -n 1500 > /dev/null 2>&1 &` 3) `startx` (which is just `exec startkde`) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 346144] akonadi_launcher_agent crashes repeatedly
https://bugs.kde.org/show_bug.cgi?id=346144 --- Comment #3 from Siddhartha Sahu <sh.siddhar...@gmail.com> --- Hi Denis, You can close this bug report. I'm not using KMail at the moment. Thanks, Sid -- You are receiving this mail because: You are watching all bug changes.
