[krunner] [Bug 486894] Windows runner does not prioritize exact matches for virtual desktops

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=486894

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #1 from Kishore Gopalakrishnan  ---
No longer reproducible with Plasma 6.1.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 481808] Clicking "Sleep" on the lockscreen makes it also display a failed login attempt

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=481808

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 489446] New: Shortcuts KCM does not allow to set human-friendly name for custom script shortcut

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=489446

Bug ID: 489446
   Summary: Shortcuts KCM does not allow to set human-friendly
name for custom script shortcut
Classification: Applications
   Product: systemsettings
   Version: 6.1.1
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_keys
  Assignee: plasma-b...@kde.org
  Reporter: kishor...@gmail.com
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY
When you create a Custom shortcut using the 'script or command' option, the
name of the item is just shown as the entire command. It would be better to
allow the user to select a more descriptive name.

STEPS TO REPRODUCE
1. System Settings > Keyboard > Shortcuts
2. Click on the 'add new shortcut' button > 'script or command'
3. Enter any command (e.g. `qdbus org.kde.krunner /App displaySingleRunner
krunner_appmenu`)
4. Click OK

OBSERVED RESULT
Name of the shortcut item in the sidebar is shown as just whatever command the
user entered

EXPECTED RESULT
Allow the user to specify a human-friendly name for the command. E.g., instead
of `qdbus org.kde.krunner /App displaySingleRunner krunner_appmenu`, I would
like to be able to display the name of the shortcut as `krunner-appmenu`

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.7-arch1-1 (64-bit)
Graphics Platform: X11

-- 
You are receiving this mail because:
You are watching all bug changes.

[kactivitymanagerd] [Bug 459961] Improve "move to activity" feature.

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=459961

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #7 from Kishore Gopalakrishnan  ---
With 
kwin 6.1.1.2
Plasma 6.1.1
I have the 'move to activity' option in the titlebar's right-click menu as
well.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 480628] Spectacle refuses to do vertical screen recording

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=480628

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 481985] Feature request: bring back "Walk through desktops" shortcut

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=481985

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 489442] New: Sidebar wrongly shows image files in an SFTP folder as having zero size

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=489442

Bug ID: 489442
   Summary: Sidebar wrongly shows image files in an SFTP folder as
having zero size
Classification: Applications
   Product: gwenview
   Version: 24.05.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: kishor...@gmail.com
  Target Milestone: ---

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
When viewing an image file in an SFTP folder using Gwenview, its size is
wrongly shown as '0B'.

STEPS TO REPRODUCE
1. Open an SFTP folder in Dolphin 
2. Select a PNG file in this folder and open it in Gwenview
3. Open the sidebar to see the file info (the tab with the 'i' symbol)

OBSERVED RESULT
File size is shown as 0B

EXPECTED RESULT
Either show actual size, or show 'unknown'

SOFTWARE/OS VERSIONS
gwenview 24.05.1
kio 6.3.0
kio-extras 24.05.1
libssh 0.10.6
openssh 9.7p1
Qt 6.7.2

ADDITIONAL INFORMATION
A. Dolphin's tooltip shows the file size correctly
B. Gwenview's sidebar shows the correct size for local files

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreensaver] [Bug 316348] kscreenlocker_greet constantly consumes around 20% CPU time

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=316348

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kactivitymanagerd] [Bug 482892] Switching activities also switches active virtual desktop

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=482892

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

--- Comment #5 from Kishore Gopalakrishnan  ---
I remember there being a GUI setting to configure this in the past, but can't
find it now (perhaps it got lost in the activities KCM redesign?).

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 487936] kde-plasma/plasma-workspace 5.27.11.1: ksmserver fails to save and later restore a session

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=487936

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com
 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #4 from Kishore Gopalakrishnan  ---


*** This bug has been marked as a duplicate of bug 487912 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 487912] plasma X11 session is not restored after logout/login

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=487912

--- Comment #13 from Kishore Gopalakrishnan  ---
*** Bug 487936 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 487912] plasma X11 session is not restored after logout/login

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=487912

--- Comment #7 from Kishore Gopalakrishnan  ---
I can at least confirm that my iceauth file (/run/user/1000/iceauth_XX ,
where XX is some apparently random string) is empty, so perhaps ksmserver
is indeed failing to write the 'magic cookie' (whatever that is) to that file.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 487912] plasma X11 session is not restored after logout/login

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=487912

--- Comment #6 from Kishore Gopalakrishnan  ---
In ksmserver/server.cpp, I see (around line 365)
```
if (IceWriteAuthFileEntry(fp, file_entry) != 0) {
qWarning("Failed to write ice auth file entry");
}
```
but the documentation for IceWriteAuthFileEntry (
https://www.x.org/releases/X11R7.7/doc/libICE/ICElib.html#IceWriteAuthFileEntry
) says "The function returns a nonzero status if the operation was successful.
"

I suppose this means the 'Failed to write ice auth file entry' messages in my
logs in comment 5 may be misleading.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 487912] plasma X11 session is not restored after logout/login

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=487912

--- Comment #5 from Kishore Gopalakrishnan  ---
After enabling 'full debug' output for ksmserver and rebooting, I get the
following messages in `journalctl -b -0 --user` (I have only reproduced a
segment that seems relevant)
```
Jun 02 14:59:53 kishorearchtestingVM systemd[499]: Started KDE Daemon 6.
Jun 02 14:59:53 kishorearchtestingVM ksmserver[588]: org.kde.kf6.ksmserver:
"/run/user/1000/KSMserver"
Jun 02 14:59:53 kishorearchtestingVM systemd[499]: Starting KDE Configuration
Module Initialization (Phase 1)...
Jun 02 14:59:53 kishorearchtestingVM ksmserver[588]: Failed to write ice auth
file entry
Jun 02 14:59:53 kishorearchtestingVM ksmserver[588]: Failed to write xsmp ice
auth file entry
Jun 02 14:59:53 kishorearchtestingVM ksmserver[588]: Failed to write ice auth
file entry
Jun 02 14:59:53 kishorearchtestingVM ksmserver[588]: Failed to write xsmp ice
auth file entry
Jun 02 14:59:53 kishorearchtestingVM ksmserver[588]: org.kde.kf6.ksmserver:
KSMServer::restoreSession  "saved at previous logout"
Jun 02 14:59:53 kishorearchtestingVM systemd[499]: Started KDE Session
Management Server.
Jun 02 14:59:53 kishorearchtestingVM systemd[499]: Starting KDE Plasma
Workspace...
Jun 02 14:59:53 kishorearchtestingVM kcminit_startup[550]: Initializing 
"/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_touchpad.so"
Jun 02 14:59:53 kishorearchtestingVM kcminit_startup[550]: kcm_touchpad: Using
X11 backend
Jun 02 14:59:53 kishorearchtestingVM kcminit_startup[550]: Initializing 
"/usr/lib/qt6/plugins/plasma/kcms/systemsettings_qwidgets/kcm_kgamma.so"
Jun 02 14:59:53 kishorearchtestingVM systemd[499]: Finished KDE Configuration
Module Initialization (Phase 1).
Jun 02 14:59:53 kishorearchtestingVM kded6[590]: org.kde.libkbolt: Failed to
connect to Bolt manager DBus interface:
Jun 02 14:59:53 kishorearchtestingVM kded6[590]: org.kde.bolt.kded: Couldn't
connect to Bolt DBus daemon
Jun 02 14:59:53 kishorearchtestingVM systemd[499]: Started KDE Window Manager.
Jun 02 14:59:53 kishorearchtestingVM kded6[590]:
org.kde.plasma.printmanager.kded: unable to register service to dbus
Jun 02 14:59:53 kishorearchtestingVM kded6[590]: QDBusObjectPath: invalid path
"/modules/plasma-session-shortcuts"
Jun 02 14:59:53 kishorearchtestingVM kded6[590]: kf.dbusaddons: The kded module
name "plasma-session-shortcuts" is invalid!
Jun 02 14:59:53 kishorearchtestingVM systemd[499]: Starting KActivityManager
Activity manager Service...
Jun 02 14:59:53 kishorearchtestingVM kded6[590]: QDBusObjectPath: invalid path
"/modules/kded_plasma-welcome"
Jun 02 14:59:53 kishorearchtestingVM kded6[590]: kf.dbusaddons: The kded module
name "kded_plasma-welcome" is invalid!
Jun 02 14:59:53 kishorearchtestingVM kded6[590]: kcm_touchpad: Using X11
backend
Jun 02 14:59:53 kishorearchtestingVM ksmserver[588]: org.kde.kf6.ksmserver:
KSMConnection::count 1
Jun 02 14:59:53 kishorearchtestingVM ksmserver[588]: org.kde.kf6.ksmserver: ICE
Connection rejected!
Jun 02 14:59:53 kishorearchtestingVM plasmashell[607]: Qt: Session management
error: None of the authentication protocols specified are supported
```

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 487912] plasma X11 session is not restored after logout/login

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=487912

--- Comment #4 from Kishore Gopalakrishnan  ---
Installing the xorg-iceauth package does not help for me.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 487912] plasma X11 session is not restored after logout/login

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=487912

--- Comment #3 from Kishore Gopalakrishnan  ---
(In reply to Kishore Gopalakrishnan from comment #2)
> ... Interestingly, applications are still opened correctly
> (preserving their previous state) when resuming an activity.

Scratch that. Activity supension/resumption also doesn't work for me.

When I suspend an activity, I can see using htop that those applications are
still running (and thus, they still appear if I resume the same activity
without rebooting). However, attempting to resume the activity after rebooting,
one is indeed presented with just an empty activity.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 487912] plasma X11 session is not restored after logout/login

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=487912

--- Comment #2 from Kishore Gopalakrishnan  ---
I also have this bug. Interestingly, applications are still opened correctly
(preserving their previous state) when resuming an activity.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 487912] plasma X11 session is not restored after logout/login

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=487912

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krunner] [Bug 469183] Krunner results order is unintuitive and often deprioritize the obvious choice

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=469183

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krunner] [Bug 485123] krunner deprioritizes (almost) exact matches

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=485123

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-knewstuff] [Bug 486913] New: i18n: interchanged context for two strings

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=486913

Bug ID: 486913
   Summary: i18n: interchanged context for two strings
Classification: Frameworks and Libraries
   Product: frameworks-knewstuff
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ad...@leinir.dk
  Reporter: kishor...@gmail.com
CC: alexander.loh...@gmx.de, kdelibs-b...@kde.org
  Target Milestone: ---

In src/qtquick/qml/UploadPage.qml, the context strings in lines 154 and 155
seem to be accidentally interchanged (the one which is supposed to be for a
generic provider mentions the KDE store, while the one which is supposed to be
KDE-specific does not mention KDE at all).

https://lxr.kde.org/source/frameworks/knewstuff/src/qtquick/qml/UploadPage.qml#0154
```
 ? i18ndc("knewstuff6", "A description of how to upload
content to a generic provider", "To upload new entries, or to add content to an
existing entry on the KDE Store, please open the website and log in. Once you
have done this, you will be able to find the My Products entry in the menu
which pops up when you click your user icon. Click on this entry to go to the
product management system, where you can work on your products .")
 : i18ndc("knewstuff6", "A description of how to upload
content to the KDE Store specifically", "To upload new entries, or to add
content to an existing entry, please open the provider's website and follow the
instructions there. You will likely need to create a user and log in to a
product management system, where you will need to follow the instructions for
how to add. Alternatively, you might be required to contact the managers of the
site directly to get new content added.")
0156 }
```

-- 
You are receiving this mail because:
You are watching all bug changes.

[krunner] [Bug 486894] New: Windows runner does not prioritize exact matches for virtual desktops

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=486894

Bug ID: 486894
   Summary: Windows runner does not prioritize exact matches for
virtual desktops
Classification: Plasma
   Product: krunner
   Version: 6.0.4
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: windows
  Assignee: plasma-b...@kde.org
  Reporter: kishor...@gmail.com
CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de
  Target Milestone: ---

SUMMARY
I have 16 virtual desktops. When I type 'desktop 1' in krunner, the windows
runner shows desktops 16 through 10 as the top results, resulting in desktop 1
not being offered as a result at all

STEPS TO REPRODUCE
1. Have 16 virtual desktops
2. type 'desktop 1' in krunner

OBSERVED RESULT
Top results are:
Desktop 16
Desktop 15
Desktop 14
Desktop 13
Desktop 12
Desktop 11
Desktop 10

with Desktop 1 not being shown at all

EXPECTED RESULT
The top result should be Desktop 1, which is an exact match


SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.6.30-1-lts (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 482098] Overlapping widgets with Activities widget on panel

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=482098

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=478556

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[lokalize] [Bug 486608] New: Lokalize crashed while saving file

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=486608

Bug ID: 486608
   Summary: Lokalize crashed while saving file
Classification: Applications
   Product: lokalize
   Version: 24.02.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: sdepi...@gmail.com
  Reporter: kishor...@gmail.com
CC: aa...@kde.org, sha...@ukr.net
  Target Milestone: ---

Application: lokalize (24.02.2)

Qt Version: 6.7.0
Frameworks Version: 6.1.0
Operating System: Linux 6.8.9-arch1-1 x86_64
Windowing System: X11
Distribution: Arch Linux
DrKonqi: 6.0.4 [KCrashBackend]

-- Information about the crash:
It crashed when I saved a file (by pressing Ctrl+S) after making some changes.
When I reopened the file, I found that all the changes had been saved. I am not
able to reproduce this consistently, but it has happened multiple times.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Lokalize (lokalize), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6  0x7e9f0fa6b4a5 in QSortFilterProxyModelPrivate::updateChildrenMapping
(this=0x5e25819af730, source_parent=..., parent_mapping=,
orient=, start=, end=358, delta_item_count=1,
remove=true) at itemmodels/qsortfilterproxymodel.cpp:1200
#7  0x7e9f0fa7f4ab in QSortFilterProxyModelPrivate::source_items_removed
(this=0x5e25819af730, source_parent=..., start=358, end=,
orient=Qt::Vertical) at itemmodels/qsortfilterproxymodel.cpp:1146
#8  0x7e9f0fa7c183 in QSortFilterProxyModelPrivate::source_items_removed
(orient=Qt::Vertical, end=, start=,
source_parent=..., this=0x5e25819af730) at
itemmodels/qsortfilterproxymodel.cpp:1106
#9  QSortFilterProxyModelPrivate::_q_sourceRowsRemoved (end=,
start=, source_parent=..., this=0x5e25819af730) at
itemmodels/qsortfilterproxymodel.cpp:1738
#10 QSortFilterProxyModel::qt_static_metacall (_o=,
_c=, _id=, _a=) at
.moc/moc_qsortfilterproxymodel.cpp:284
#11 0x7e9f0fac8b63 in doActivate (sender=0x5e2580cd19b0,
signal_index=15, argv=0x7ffdc8076600) at kernel/qobject.cpp:3937
#12 0x7e9f0fa4f4e3 in QAbstractItemModel::rowsRemoved
(this=this@entry=0x5e2580cd19b0, _t1=..., _t2=, _t3=, _t4=...) at .moc/moc_qabstractitemmodel.cpp:606
#13 0x7e9f0fa4f647 in QAbstractItemModel::endRemoveRows
(this=this@entry=0x5e2580cd19b0) at itemmodels/qabstractitemmodel.cpp:2837
#14 0x5e25800bf0c1 in ProjectModel::po_rowsInserted (this=0x5e2580cd19b0,
po_parent=, first=, last=) at
/usr/src/debug/lokalize/lokalize-24.02.2/src/project/projectmodel.cpp:272
#15 0x7e9f0fac89a7 in QtPrivate::QSlotObjectBase::call (a=0x7ffdc80768d0,
r=, this=0x5e2580c91390, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#16 doActivate (sender=0x5e2580cd19d8, signal_index=13,
argv=0x7ffdc80768d0) at kernel/qobject.cpp:3925
#17 0x7e9f0fa4f013 in QAbstractItemModel::rowsInserted
(this=this@entry=0x5e2580cd19d8, _t1=..., _t2=, _t3=, _t4=...) at .moc/moc_qabstractitemmodel.cpp:592
#18 0x7e9f0fa4f177 in QAbstractItemModel::endInsertRows
(this=0x5e2580cd19d8) at itemmodels/qabstractitemmodel.cpp:2782
#19 0x7e9f11690ea9 in KDirModelPrivate::_k_slotNewItems (this=, directoryUrl=, items=) at
/usr/src/debug/kio5/kio-5.115.0/src/widgets/kdirmodel.cpp:589
#20 0x7e9f0fac89a7 in QtPrivate::QSlotObjectBase::call (a=0x7ffdc8076ba0,
r=, this=0x5e2580ce1410, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#21 doActivate (sender=0x5e2580c73350, signal_index=16,
argv=0x7ffdc8076ba0) at kernel/qobject.cpp:3925
#22 0x7e9f1151824f in KCoreDirLister::itemsAdded (this=,
_t1=..., _t2=...) at
/usr/src/debug/kio5/build/src/core/KF5KIOCore_autogen/include/moc_kcoredirlister.cpp:565
#23 0x7e9f115189cd in KCoreDirListerPrivate::emitItems
(this=0x5e2580cd9520) at
/usr/src/debug/kio5/kio-5.115.0/src/core/kcoredirlister.cpp:2562
#24 0x7e9f1151fe3e in KCoreDirListerCache::slotUpdateResult
(this=, j=) at
/usr/include/c++/13.2.1/bits/unique_ptr.h:199
#25 0x7e9f0fac89a7 in QtPrivate::QSlotObjectBase::call (a=0x7ffdc8076e40,
r=, this=0x5e25831803f0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#26 doActivate (sender=0x5e2582f986d0, signal_index=6,
argv=0x7ffdc8076e40) at kernel/qobject.cpp:3925
#27 0x7e9f10d40a7a in KJob::result (this=this@entry=0x5e2582f986d0,
_t1=, _t1@entry=0x5e2582f986d0, _t2=...) at
/usr/src/debug/kcoreaddons5/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#28 0x7e9f10d46a5c in KJob::finishJob (this=0x5e2582f986d0,
emitResult=) at
/usr/src/debug/kcoreaddons5/kcoreaddons-5.115.0/src/lib/jobs/kjob.cpp:98
#29 0x7e9f0fac89a7 in QtPrivate::QSlotObjectBase::call (a=0x7ffdc8076f10,
r=, this=0x5e2582234410, this=, r=, a=) at

[kile] [Bug 445598] Dynamic word wrapping in Kile stopped working in Ubuntu 21.10

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=445598

--- Comment #6 from Kishore Gopalakrishnan  ---
(In reply to Samuel Jimenez from comment #5)
> (In reply to Kishore Gopalakrishnan from comment #4)
> > (In reply to Samuel Jimenez from comment #3)
> > > This happens sporadically on 2.9.95
> > > Operating System: Arch Linux 
> > > KDE Plasma Version: 6.0.4
> > > KDE Frameworks Version: 6.1.0
> > > Qt Version: 6.7.0
> > > 
> > > If an entry for the file is created in kilerc, it remains persistent. 
> > > (This
> > > corresponds to View >Word Wrap > Dynamic Word Wrap)
> > > [View-Settings,View=0,URL=file://:@/path/to/file.tex]
> > > Dynamic Word Wrap=true
> > > 
> > > However, until this is saved per-file, the setting inherited from
> > > KTextEditor is not consistently respected.
> > > (Settings > Configure > Kile > Editor > Appearance > Dynamic Word Wrap)
> > > [KTextEditor View]
> > > Dynamic Word Wrap=true
> > 
> > Are you sure this is not a ktexteditor bug? I seem to be seeing similar
> > behaviour in Kate too.
> 
> In which version of Kate do you see this?
> I cannot reproduce in Kate version 24.02.2.
> 
> While I don't claim to be sure, I see it around 50% in Kile.

I also have kate 24.02.2, and dynamic word wrapping occasionally gets disabled
in some new windows (the same happens for me in Kile).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kile] [Bug 445598] Dynamic word wrapping in Kile stopped working in Ubuntu 21.10

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=445598

--- Comment #4 from Kishore Gopalakrishnan  ---
(In reply to Samuel Jimenez from comment #3)
> This happens sporadically on 2.9.95
> Operating System: Arch Linux 
> KDE Plasma Version: 6.0.4
> KDE Frameworks Version: 6.1.0
> Qt Version: 6.7.0
> 
> If an entry for the file is created in kilerc, it remains persistent. (This
> corresponds to View >Word Wrap > Dynamic Word Wrap)
> [View-Settings,View=0,URL=file://:@/path/to/file.tex]
> Dynamic Word Wrap=true
> 
> However, until this is saved per-file, the setting inherited from
> KTextEditor is not consistently respected.
> (Settings > Configure > Kile > Editor > Appearance > Dynamic Word Wrap)
> [KTextEditor View]
> Dynamic Word Wrap=true

Are you sure this is not a ktexteditor bug? I seem to be seeing similar
behaviour in Kate too.

-- 
You are receiving this mail because:
You are watching all bug changes.

[cantor] [Bug 485956] New: Cantor crashed while deleting cells

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=485956

Bug ID: 485956
   Summary: Cantor crashed while deleting cells
Classification: Applications
   Product: cantor
   Version: 24.02.2
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: cantor-b...@kde.org
  Reporter: kishor...@gmail.com
  Target Milestone: ---

Application: cantor (24.02.2)

Qt Version: 6.7.0
Frameworks Version: 6.1.0
Operating System: Linux 6.8.7-arch1-1 x86_64
Windowing System: X11
Distribution: Arch Linux
DrKonqi: 6.0.4 [KCrashBackend]

-- Information about the crash:
I had selected multiple cells by Ctrl-clicking on their right edges with the
mouse, right-clicking on the right edge of a selected cell, and choosing
'delete cells'. Cantor often (but not always) crashes when I do this.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Cantor (cantor), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7  0x7f92e86ab393 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8  0x7f92e865a6c8 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9  0x7f92e86424b8 in __GI_abort () at abort.c:79
#10 0x7f92e8643395 in __libc_message_impl (fmt=fmt@entry=0x7f92e87bb2ea
"%s\n") at ../sysdeps/posix/libc_fatal.c:132
#11 0x7f92e86b52a7 in malloc_printerr (str=str@entry=0x7f92e87be988
"malloc(): unaligned tcache chunk detected") at malloc.c:5772
#12 0x7f92e86b9a4c in tcache_get_n (ep=, tc_idx=) at malloc.c:3183
#13 tcache_get (tc_idx=) at malloc.c:3199
#14 __GI___libc_malloc (bytes=bytes@entry=24) at malloc.c:3320
#15 0x7f92e88b089d in operator new (sz=sz@entry=24) at
/usr/src/debug/gcc/gcc/libstdc++-v3/libsupc++/new_op.cc:50
#16 0x7f92e9b64298 in QWidgetRepaintManager::sendUpdateRequest
(this=0x5ad31daccd40, widget=0x5ad31d940870, updateTime=) at
kernel/qwidgetrepaintmanager.cpp:402
#17 0x7f92e9b65028 in QWidgetRepaintManager::sendUpdateRequest
(updateTime=QWidgetRepaintManager::UpdateLater, widget=,
this=0x5ad31daccd40) at kernel/qwidgetrepaintmanager.cpp:374
#18 QWidgetRepaintManager::markDirty (this=0x5ad31daccd40, r=...,
widget=, updateTime=QWidgetRepaintManager::UpdateLater,
bufferState=) at kernel/qwidgetrepaintmanager.cpp:291
#19 0x7f92e9b922df in QWidgetPrivate::update (this=, r=...) at kernel/qwidget.cpp:10886
#20 QWidget::update (this=, rgn=) at
kernel/qwidget.cpp:10863
#21 0x7f92e9e9febe in QGraphicsViewPrivate::processPendingUpdates
(this=0x5ad31df17560) at graphicsview/qgraphicsview.cpp:966
#22 0x7f92e9e90386 in QGraphicsScenePrivate::_q_processDirtyItems
(this=0x5ad31ddd1850) at graphicsview/qgraphicsscene.cpp:505
#23 QGraphicsScene::qt_static_metacall (_o=, _c=,
_id=, _a=) at .moc/moc_qgraphicsscene.cpp:197
#24 0x7f92e8ebb4da in QObject::event (this=0x5ad31df16b10,
e=0x5ad31dfea7a0) at kernel/qobject.cpp:1347
#25 0x7f92e9b578ff in QApplicationPrivate::notify_helper (this=, receiver=0x5ad31df16b10, e=0x5ad31dfea7a0) at
kernel/qapplication.cpp:3640
#26 0x7f92e8e93a68 in QCoreApplication::notifyInternal2
(receiver=0x5ad31df16b10, event=0x5ad31dfea7a0) at
kernel/qcoreapplication.cpp:1064
#27 0x7f92e8e989cb in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x5ad31d4bcf70) at
kernel/qcoreapplication.cpp:1821
#28 0x7f92e8edea48 in postEventSourceDispatch (s=0x5ad31d5fc290) at
kernel/qeventdispatcher_glib.cpp:277
#29 0x7f92e1d0d199 in g_main_dispatch (context=0x7f92cc000ed0) at
../glib/glib/gmain.c:3344
#30 0x7f92e1d6c3bf in g_main_context_dispatch_unlocked
(context=0x7f92cc000ed0) at ../glib/glib/gmain.c:4152
#31 g_main_context_iterate_unlocked.isra.0
(context=context@entry=0x7f92cc000ed0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4217
#32 0x7f92e1d0c712 in g_main_context_iteration (context=0x7f92cc000ed0,
may_block=1) at ../glib/glib/gmain.c:4282
#33 0x7f92e8ee288c in QEventDispatcherGlib::processEvents
(this=0x5ad31d5fab20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#34 0x7f92e8e92774 in QEventLoop::exec (this=this@entry=0x7ffd9613b270,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#35 0x7f92e8e93c13 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#36 0x7f92e932bef2 in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1870
#37 0x7f92e9b55cda in QApplication::exec () at kernel/qapplication.cpp:2832
#38 0x5ad31c9394d6 in main (argc=, argv=) at
/usr/src/debug/cantor/cantor-24.02.2/src/main.cpp:141
[Inferior 1 (process 146889) detached]

Reported using DrKonqi

-- 
You are receiving 

[lokalize] [Bug 485909] New: Lokalize crashed while jumping to next untranslated entry

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=485909

Bug ID: 485909
   Summary: Lokalize crashed while jumping to next untranslated
entry
Classification: Applications
   Product: lokalize
   Version: 24.02.2
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: sdepi...@gmail.com
  Reporter: kishor...@gmail.com
CC: aa...@kde.org, sha...@ukr.net
  Target Milestone: ---

Application: lokalize (24.02.2)

Qt Version: 6.7.0
Frameworks Version: 6.1.0
Operating System: Linux 6.8.7-arch1-1 x86_64
Windowing System: X11
Distribution: Arch Linux
DrKonqi: 6.0.4 [KCrashBackend]

-- Information about the crash:
Lokalize crashed when I pressed the Ctrl+Shift+Pgdn shortcut to jump to the
next untranslated entry. This happens only occasionally, so I am not sure
exactly what triggers the crash.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Lokalize (lokalize), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6  0x767efde7297a in QSortFilterProxyModel::parent (child=,
this=0x61ef53e6c200) at itemmodels/qsortfilterproxymodel.cpp:2219
#7  QSortFilterProxyModel::parent (this=0x61ef53e6c200, child=)
at itemmodels/qsortfilterproxymodel.cpp:2212
#8  0x61ef52054e10 in QModelIndex::parent (this=0x61ef550f6fd0) at
/usr/include/qt/QtCore/qabstractitemmodel.h:443
#9  TM::DBFilesModel::updateStats (this=0x61ef53e6c200, topLeft=...,
bottomRight=) at
/usr/src/debug/lokalize/lokalize-24.02.2/src/tm/dbfilesmodel.cpp:145
#10 0x767efdebb4da in QObject::event (this=0x61ef53e6c200,
e=0x767eb8001c60) at kernel/qobject.cpp:1347
#11 0x767efeb578ff in QApplicationPrivate::notify_helper (this=, receiver=0x61ef53e6c200, e=0x767eb8001c60) at
kernel/qapplication.cpp:3640
#12 0x767efde93a68 in QCoreApplication::notifyInternal2
(receiver=0x61ef53e6c200, event=0x767eb8001c60) at
kernel/qcoreapplication.cpp:1064
#13 0x767efde989cb in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x61ef52e80580) at
kernel/qcoreapplication.cpp:1821
#14 0x767efdedea48 in postEventSourceDispatch (s=0x61ef52f6a250) at
kernel/qeventdispatcher_glib.cpp:277
#15 0x767efc04d199 in g_main_dispatch (context=0x767ef4000ed0) at
../glib/glib/gmain.c:3344
#16 0x767efc0ac3bf in g_main_context_dispatch_unlocked
(context=0x767ef4000ed0) at ../glib/glib/gmain.c:4152
#17 g_main_context_iterate_unlocked.isra.0
(context=context@entry=0x767ef4000ed0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4217
#18 0x767efc04c712 in g_main_context_iteration (context=0x767ef4000ed0,
may_block=1) at ../glib/glib/gmain.c:4282
#19 0x767efdee288c in QEventDispatcherGlib::processEvents
(this=0x61ef52e9c7e0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#20 0x767efde92774 in QEventLoop::exec (this=this@entry=0x7ffd6befbcb0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#21 0x767efde93c13 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#22 0x767efe32bef2 in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1870
#23 0x767efeb55cda in QApplication::exec () at kernel/qapplication.cpp:2832
#24 0x61ef51fb0c91 in main (argc=, argv=) at
/usr/src/debug/lokalize/lokalize-24.02.2/src/main.cpp:135
[Inferior 1 (process 64680) detached]

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 485426] Google Groupware agent stops syncing after a while

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=485426

--- Comment #1 from Kishore Gopalakrishnan  ---
I also have this issue, and I get the following output in my system logs
(checked using `LANG=C journalctl -b -0 | grep akonadi_google_resource | less`:
```
Apr 15 17:10:21 kishore-thinkpad-e495 akonadi_google_resource[10265]:
qt.network.http2: connection error: GOAWAY invalid stream/error code
```

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 485426] Google Groupware agent stops syncing after a while

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=485426

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 483949] On recent update Kate overwrites settings

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=483949

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 402009] Advance an appointment is not displayed

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=402009

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #8 from Kishore Gopalakrishnan  ---
I think this bug is fixed now (I was able to reproduce it last year).

STEPS TO REPRODUCE
1. Create a recurring event on the Google calendar web interface (every week on
the same day)
2. Add Google Calendar to Korganizer (Settings > Configure Korganizer > General
> Calendars > Add > Google Groupware > Configure
3. check that the recurring event you created on Google Calendar web interface
is shown in Korganizer
4. Go to the Google Calendar web interface again, and change the time of a
single occurrence of the recurring event (it will allow you to select this
option while saving changes)
5. Check that the change is applied in the Google Calendar web interface
6. Now open Korganizer, right-click on the Google Calendar entry in the
sidebar, and click 'update folder'

OBSERVED RESULTS
The changed time of the single occurrence is correctly shown (earlier, it would
not be updated, just as this bug report mentions).

SOFTWARE VERSIONS
korganizer 6.0.0 (24.02.0)
Operating System: Arch Linux 
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-arch1-1 (64-bit)
Graphics Platform: X11

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 483823] New: New event button does not use currently selected date as default

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=483823

Bug ID: 483823
   Summary: New event button does not use currently selected date
as default
Classification: Applications
   Product: korganizer
   Version: 6.0.0
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: kishor...@gmail.com
  Target Milestone: ---

SUMMARY
When you create a new event from the toolbar button, it uses today's date by
default rather than the currently selected one.

STEPS TO REPRODUCE:
1. In the month-view date picker on the right (not the main view), click on a
date other than today's date
2. Click the 'new event' button in the toolbar
3. Cancel event creation
4. Right-click on a date other than today's date in the calendar, and click
'new event'

OBSERVED RESULTS
In step 2, the opened event creation dialog has today's date populated as the
default one, rather than the date the user had selected before clicking the
toolbar button.

On the other hand, step 4 behaves correctly, in that it sets the default event
date as the date the user had selected.

EXPECTED RESULTS
In step 2, the default date for the new event creation should be the date the
user had selected.

SOFTWARE/OS VERSIONS
korganizer 6.0.0 (24.02.0)
Operating System: Arch Linux 
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-arch1-1 (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
The current behaviour is frustrating for me, because I seem to have developed
the habit of selecting a date and pressing Ctrl+N, which always defaults to the
current date.

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 146564] [Wishlist] All Day area New Event function

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=146564

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[Merkuro] [Bug 450462] Feature Request: ability to copy events

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=450462

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 372835] Korganizer and Digital Clock/Calendar widget keep forgetting of selected Caldav resources

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=372835

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 481063] A reminder option to run a command would enable valuable use-cases

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=481063

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[krunner] [Bug 483815] New: Unit conversion runner does not detect KB as kilobytes

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=483815

Bug ID: 483815
   Summary: Unit conversion runner does not detect KB as kilobytes
Classification: Plasma
   Product: krunner
   Version: 6.0.2
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: converter
  Assignee: plasma-b...@kde.org
  Reporter: kishor...@gmail.com
CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de
  Target Milestone: ---

SUMMARY
The unit conversion runner thinks 'KB' (note the use of uppercase) stands for
kilobits, rather than kilobytes.


STEPS TO REPRODUCE
1. Type '1 KB' (without the quotes) in krunner

OBSERVED RESULT
0.125 kilobytes is shown as a unit conversion (i.e. the input is interpreted as
1 kilobit)

EXPECTED RESULT
KB should be kilobytes (just like GB=gigabytes)

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-arch1-1 (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
Typing 1 kB is interpreted as kilobyte.

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 183527] Use a name (better a new field i.e. "baptized" or so) for celebrating nameday (like birthday but based on names)

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=183527

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com
 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #1 from Kishore Gopalakrishnan  ---


*** This bug has been marked as a duplicate of bug 245993 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaddressbook] [Bug 245993] Wish for field 'name day' in KAddressbook

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=245993

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||m_gr...@yahoo.co.uk

--- Comment #6 from Kishore Gopalakrishnan  ---
*** Bug 183527 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[yakuake] [Bug 440128] Yakuake sticks on the activity it was started first

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=440128

--- Comment #8 from Kishore Gopalakrishnan  ---
(In reply to Christian Muehlhaeuser from comment #7)
> This sounds similar to 440281, which is apparently fixed. Can you still
> reproduce this with Plasma 6?

Yakuake now seems to have 'show on all activities' applied by default (without
the use needing to set any window rules), so I think this bug is fixed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 482152] When starting the LSP, Kate crashes.

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=482152

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 482329] On X11, Force Font DPI setting now affects more than just the font size

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=482329

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

--- Comment #4 from Kishore Gopalakrishnan  ---
I find that with the 'force fonts DPI' setting disabled and Display scaling set
to 150% on X11,

1. Qt5 applications are not scaled (checked with Cantor and Kile)
2. The titlebars of all windows are unscaled

Nevertheless, gtk3 applications (gedit) and Qt6 applications (System Settings
and Dolphin) have their content scaled correctly.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-systemmonitor] [Bug 482169] System Monitor in Plasma 6 crashes on clicking "Show Details Sidebar"

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=482169

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 482946] Kate crashed while editing

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=482946

--- Comment #1 from Kishore Gopalakrishnan  ---
It happened again; this time, I was using the split view. The backtrace looks
very different from https://bugs.kde.org/show_bug.cgi?id=481654, though, and
similar to the one I posted here.

I also see some stuff saying 'UTF8' in the backtrace. I am not sure if it is
relevant that I am using a non-Latin language (Tamil) as my system language
(nevertheless, during these crashes, I was editing files with only English
text).


Thread 1 (Thread 0x70d74332fe80 (LWP 89395)):
[KCrash Handler]
#4  0x70d748cab32c in ??? () at /usr/lib/libc.so.6
#5  0x70d748c5a6c8 in raise () at /usr/lib/libc.so.6
#6  0x70d748c424b8 in abort () at /usr/lib/libc.so.6
#7  0x70d748c423dc in ??? () at /usr/lib/libc.so.6
#8  0x70d748c52d46 in __assert_fail () at /usr/lib/libc.so.6
#9  0x70d738373bdc in rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator
>::operator[] >
(this=, name=) at
/usr/src/debug/kate/kate-24.02.0/addons/lspclient/rapidjson/include/rapidjson/document.h:1226
#10 rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator
>::operator[] >
(name=, this=) at
/usr/src/debug/kate/kate-24.02.0/addons/lspclient/rapidjson/include/rapidjson/document.h:1226
#11 rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator >::operator[] (name=, this=) at
/usr/src/debug/kate/kate-24.02.0/addons/lspclient/rapidjson/include/rapidjson/document.h:1211
#12 rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator >::operator[] (name=, this=) at
/usr/src/debug/kate/kate-24.02.0/addons/lspclient/rapidjson/include/rapidjson/document.h:1214
#13 parseLocationLink (loc=...) at
/usr/src/debug/kate/kate-24.02.0/addons/lspclient/lspclientserver.cpp:623
#14 parseDocumentLocation (result=) at
/usr/src/debug/kate/kate-24.02.0/addons/lspclient/lspclientserver.cpp:777
#15 0x70d738386d64 in std::__invoke_impl,
QList (*&)(rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator > const&),
rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator > const&>
(__f=) at /usr/include/c++/13.2.1/bits/invoke.h:60
#16 std::__invoke_r, QList
(*&)(rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator > const&),
rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator > const&>
(__fn=) at /usr/include/c++/13.2.1/bits/invoke.h:116
#17 std::_Function_handler
(rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator > const&),
QList (*)(rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator >
const&)>::_M_invoke(std::_Any_data const&,
rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator > const&)
(__functor=, __args#0=) at
/usr/include/c++/13.2.1/bits/std_function.h:291
#18 0x70d738388c41 in std::function
(rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator >
const&)>::operator()(rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator > const&) const
(__args#0=, this=0x5aff0feccb70) at
/usr/include/c++/13.2.1/bits/std_function.h:591
#19 operator() (m=, __closure=0x5aff0feccb40) at
/usr/src/debug/kate/kate-24.02.0/addons/lspclient/lspclientserver.cpp:2096
#20 std::__invoke_impl
>(ReplyHandler >&, const QObject*,
utils::identity(const
rapidjson::GenericValue >&)> >::type)::&, const rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator >&> (__f=...) at
/usr/include/c++/13.2.1/bits/invoke.h:61
#21 std::__invoke_r
>(ReplyHandler >&, const QObject*,
utils::identity(const
rapidjson::GenericValue >&)> >::type)::&, const rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator >&> (__fn=...) at
/usr/include/c++/13.2.1/bits/invoke.h:111
#22 std::_Function_handler,
rapidjson::MemoryPoolAllocator >&),
make_handler >(ReplyHandler >&,
const QObject*, utils::identity(const
rapidjson::GenericValue >&)> >::type):: >::_M_invoke(const std::_Any_data &, const
rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator > &)
(__functor=, __args#0=) at
/usr/include/c++/13.2.1/bits/std_function.h:290
#23 0x70d73837e9e8 in std::function::operator()(LSPApplyWorkspaceEditResponse const&) const
(__args#0=, this=0x7ffc164853c0) at
/usr/include/c++/13.2.1/bits/std_function.h:591
#24 LSPClientServer::LSPClientServerPrivate::readStandardOutput
(this=0x5aff0f23a9b0) at
/usr/src/debug/kate/kate-24.02.0/addons/lspclient/lspclientserver.cpp:1523
#25 0x70d749390ca9 in ??? () at /usr/lib/libQt6Core.so.6
#26 0x70d7494f642f in ??? () at /usr/lib/libQt6Core.so.6
#27 0x70d7494fdb35 in ??? () at /usr/lib/libQt6Core.so.6
#28 0x70d749390fab in ??? () at /usr/lib/libQt6Core.so.6
#29 0x70d749398530 in QSocketNotifier::event(QEvent*) () at
/usr/lib/libQt6Core.so.6
#30 0x70d74a2f438b in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt6Widgets.so.6
#31 0x70d749339818 in QCoreApplication::notifyInternal2(QObject*, Q

[kate] [Bug 482946] New: Kate crashed while editing

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=482946

Bug ID: 482946
   Summary: Kate crashed while editing
Classification: Applications
   Product: kate
   Version: 24.02.0
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: kishor...@gmail.com
  Target Milestone: ---

Application: kate (24.02.0)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.7.8-arch1-1 x86_64
Windowing System: X11
Distribution: Arch Linux
DrKonqi: 6.0.1 [CoredumpBackend]

-- Information about the crash:
I was editing a remote file over SFTP. I had just saved the file by pressing
Ctrl+S, and I started scrolling down. Kate then crashed.

I have been facing crashes also while editing local files (only after upgrading
to 24.02).

Since the crash seems to be related to the LSP, I will note that I was editing
a Python file when this crash happened (the LSP plugin was using pylsp). I have
also had crashes happen while editing Fortran files (in which case the fortls
LSP server is used), but I haven't obtained a backtrace with such a crash yet.

I have built Kate from source on my machine (along with debug symbols) using
the Arch PKGBUILD.

The crash can be reproduced sometimes.

-- Backtrace:
Application: கேட் (kate), signal: Aborted

[New LWP 7433]
[New LWP 7459]
[New LWP 7462]
[New LWP 7658]
[New LWP 87539]
[New LWP 7652]
[New LWP 87644]
[New LWP 87645]
[New LWP 7651]
[New LWP 7653]
[New LWP 87646]
[New LWP 87647]
[New LWP 7648]
[New LWP 7656]

This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/kate -session
1021b2181d61a17057267300037970296_1709818453_841'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7196fa2ab32c in ?? () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x7196f492fe80 (LWP 7433))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7196f492fe80 (LWP 7433))]

Thread 14 (Thread 0x7196e8e006c0 (LWP 7656)):
#0  0x7196fa2a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x7196fa2a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7196e9c8681c in ??? () at /usr/lib/dri/radeonsi_dri.so
#3  0x7196e9c9e7ec in ??? () at /usr/lib/dri/radeonsi_dri.so
#4  0x7196fa2a955a in ??? () at /usr/lib/libc.so.6
#5  0x7196fa326a3c in ??? () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7196f1e006c0 (LWP 7648)):
#0  0x7196fa2a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x7196fa2a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7196e9c8681c in ??? () at /usr/lib/dri/radeonsi_dri.so
#3  0x7196e9c9e7ec in ??? () at /usr/lib/dri/radeonsi_dri.so
#4  0x7196fa2a955a in ??? () at /usr/lib/libc.so.6
#5  0x7196fa326a3c in ??? () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7196d18006c0 (LWP 87647)):
#0  0x7196fa2a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x7196fa2a8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x7196faaa3ba4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x7196faaa64aa in ??? () at /usr/lib/libQt6Core.so.6
#4  0x7196faaa0bd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x7196fa2a955a in ??? () at /usr/lib/libc.so.6
#6  0x7196fa326a3c in ??? () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7196d38006c0 (LWP 87646)):
#0  0x7196fa2a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x7196fa2a8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x7196faaa3ba4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x7196faaa64aa in ??? () at /usr/lib/libQt6Core.so.6
#4  0x7196faaa0bd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x7196fa2a955a in ??? () at /usr/lib/libc.so.6
#6  0x7196fa326a3c in ??? () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7196e9a006c0 (LWP 7653)):
#0  0x7196fa2a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x7196fa2a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7196e9c8681c in ??? () at /usr/lib/dri/radeonsi_dri.so
#3  0x7196e9c9e7ec in ??? () at /usr/lib/dri/radeonsi_dri.so
#4  0x7196fa2a955a in ??? () at /usr/lib/libc.so.6
#5  0x7196fa326a3c in ??? () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7196f14006c0 (LWP 7651)):
#0  0x7196fa2a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x7196fa2a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7196e9c8681c in ??? () at /usr/lib/dri/radeonsi_dri.so
#3  0x7196e9c9e7ec in ??? () at 

[kate] [Bug 481654] Kate crashed when triggering quick open

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=481654

--- Comment #4 from Kishore Gopalakrishnan  ---
(In reply to Christoph Cullmann from comment #3)
> Could you retry this with the new 24.04 release?

Do you mean 24.02? I just updated to it; I will comment on this report if the
crash happens again (hasn't happened so far, but it wasn't that common even
earlier).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 481654] Kate crashed when triggering quick open

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=481654

--- Comment #2 from Kishore Gopalakrishnan  ---
(In reply to Waqar Ahmed from comment #1)
> This is crashing because of a stale pointer in view manager. This has been
> seen before but so far we have no idea why this happens
> 
> Some questions that might help:
> 
> - Did you use splits in the session that crashed?
> - Did you use tab drag and drop feature?
> - How do you normally close a tab/document?

I was using split view (two splits side-by-side).

I usually don't drag/drop tabs (at best, I occasionally right-click on a tab
and use the option to detach it from the window.

Usually I just close the entire window when I am done by middle-clicking on the
titlebar.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 481654] New: Kate crashed when triggering quick open

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=481654

Bug ID: 481654
   Summary: Kate crashed when triggering quick open
Classification: Applications
   Product: kate
   Version: 23.08.5
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: kishor...@gmail.com
  Target Milestone: ---

Application: kate (23.08.5)

Qt Version: 5.15.12
Frameworks Version: 5.115.0
Operating System: Linux 6.7.4-arch1-1 x86_64
Windowing System: X11
Distribution: Arch Linux
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
Kate crashed when I switched from another window using Alt+Tab, triggered Quick
Open using Ctrl+Alt+O, and started typing. I have not been able to reproduce
this crash again.

This was on X11, so it does not seem to be a duplicate of
https://bugs.kde.org/show_bug.cgi?id=471791

The crash does not seem to be reproducible.

-- Backtrace:
Application: கேட் (kate), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6  0x7a11de9c049a in KateQuickOpenModel::refresh (this=0x5f1e46832f50,
mainWindow=) at
/usr/src/debug/kate/kate-23.08.5/apps/lib/quickopen/katequickopenmodel.cpp:137
#7  0x7a11de9c0d2c in KateQuickOpen::updateState (this=0x7ffd79c095d0) at
/usr/src/debug/kate/kate-23.08.5/apps/lib/quickopen/katequickopen.cpp:379
#8  0x7a11de9e79f4 in KateQuickOpen::KateQuickOpen (mainWindow=, this=0x7ffd79c095d0) at
/usr/src/debug/kate/kate-23.08.5/apps/lib/quickopen/katequickopen.cpp:336
#9  KateMainWindow::slotQuickOpen (this=0x5f1e45854490) at
/usr/src/debug/kate/kate-23.08.5/apps/lib/katemainwindow.cpp:1489
#10 0x7a11dd4c8e27 in QtPrivate::QSlotObjectBase::call (a=0x7ffd79c09760,
r=, this=0x5f1e458f59a0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#11 doActivate (sender=0x5f1e44a2fdd0, signal_index=4,
argv=0x7ffd79c09760) at kernel/qobject.cpp:3925
#12 0x7a11de14abb7 in QAction::triggered (this=this@entry=0x5f1e44a2fdd0,
_t1=) at .moc/moc_qaction.cpp:376
#13 0x7a11de15060b in QAction::activate (this=0x5f1e44a2fdd0,
event=) at kernel/qaction.cpp:1161
#14 0x7a11de1506de in QAction::event (e=, this=) at kernel/qaction.cpp:1086
#15 QAction::event (this=, e=) at
kernel/qaction.cpp:1075
#16 0x7a11de1578ff in QApplicationPrivate::notify_helper (this=, receiver=0x5f1e44a2fdd0, e=0x7ffd79c098f0) at
kernel/qapplication.cpp:3640
#17 0x7a11dd493ef8 in QCoreApplication::notifyInternal2
(receiver=0x5f1e44a2fdd0, event=0x7ffd79c098f0) at
kernel/qcoreapplication.cpp:1064
#18 0x7a11dd493f63 in QCoreApplication::sendEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1462
#19 0x7a11dd967026 in QShortcutMap::dispatchEvent
(this=this@entry=0x5f1e4487ae58, e=e@entry=0x7ffd79c099b0) at
kernel/qshortcutmap.cpp:675
#20 0x7a11dd967415 in QShortcutMap::tryShortcut (this=0x5f1e4487ae58,
e=0x7ffd79c099b0) at kernel/qshortcutmap.cpp:343
#21 0x7a11dd91be08 in QWindowSystemInterface::handleShortcutEvent
(window=, timestamp=82160172, keyCode=79, modifiers=...,
nativeScanCode=32, nativeVirtualKey=111, nativeModifiers=12, text=...,
autorepeat=false, count=1) at kernel/qwindowsysteminterface.cpp:477
#22 0x7a11dd935522 in QGuiApplicationPrivate::processKeyEvent
(e=0x7ffd79c09b50) at kernel/qguiapplication.cpp:2398
#23 0x7a11d7a6e965 in QIBusPlatformInputContext::filterEventFinished
(this=, call=0x5f1e480b79b0) at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforminputcontexts/ibus/qibusplatforminputcontext.cpp:517
#24 0x7a11dd4c8e27 in QtPrivate::QSlotObjectBase::call (a=0x7ffd79c09ce0,
r=, this=0x5f1e48124e90, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#25 doActivate (sender=0x5f1e480b79b0, signal_index=3,
argv=0x7ffd79c09ce0) at kernel/qobject.cpp:3925
#26 0x7a11de7b1ad4 in QDBusPendingCallWatcher::finished (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:158
#27 0x7a11dd4bb964 in QObject::event (this=0x5f1e480b79b0,
e=0x5f1e477a1740) at kernel/qobject.cpp:1347
#28 0x7a11de1578ff in QApplicationPrivate::notify_helper (this=, receiver=0x5f1e480b79b0, e=0x5f1e477a1740) at
kernel/qapplication.cpp:3640
#29 0x7a11dd493ef8 in QCoreApplication::notifyInternal2
(receiver=0x5f1e480b79b0, event=0x5f1e477a1740) at
kernel/qcoreapplication.cpp:1064
#30 0x7a11dd498e5b in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x5f1e44859580) at
kernel/qcoreapplication.cpp:1821
#31 0x7a11dd4deec8 in postEventSourceDispatch (s=0x5f1e449cb2b0) at
kernel/qeventdispatcher_glib.cpp:277
#32 0x7a11dad0df69 in g_main_dispatch (context=0x7a11dec0) at
../glib/glib/gmain.c:3476
#33 0x7a11dad6c3a7 in g_main_context_dispatch_unlocked
(context=0x7a11dec0) at 

[kwin] [Bug 465119] Option to hide mouse cursor after inactivity

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=465119

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 433284] Shortcut for switching input method (Windows + Space) does not work when using kimpanel-ibus-panel

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=433284

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[xdg-desktop-portal-kde] [Bug 476647] xdg-portal-desktop-kde start after xdg-portal-desktop, if it even starts

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=476647

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 442681] kded sometimes crashes in LayoutUnit::operator= when switching ibus keyboard layouts

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=442681

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Kishore Gopalakrishnan  ---
(In reply to Nate Graham from comment #1)
> Thank you for the bug report. Unfortunately we were not able to get to it
> yet. Can we ask you to please check if this is still an issue with Plasma
> 5.27, or--even better--the Plasma 6 beta?

On Plasma 5.27.10, I no longer get notifications about kded crashing, but the
behaviour I used to observe after a kded crash (arrow and pgup/pgdn keys
getting remapped) still occasionally crops up on days when I frequently switch
between ibus layouts. I don't see any easy way to figure out if the latter is
related to the earlier crashes (or even related to KDE), so I'll close this as
fixed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kile] [Bug 408287] Kile help (F1) points to wrong URL

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=408287

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #2 from Kishore Gopalakrishnan  ---
It looks like the online thing is only opened when the user does not have
khelpcenter installed. I can still reproduce the bug on current master (I used
the kile-git package from the Arch AUR).

Updated steps:
1. Make sure khelpcenter is not installed
2. Open Kile
3. Press F1

It still opens the same nonexistent URL with the wrong branch:
https://docs.kde.org/index.php?branch=stable5=ta_IN=kile=index.html

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 477146] On X11, the last opened window is not restored by session restore

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=477146

Kishore Gopalakrishnan  changed:

   What|Removed |Added

   Keywords||qt6

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 477146] New: On X11, the last opened window is not restored by session restore

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=477146

Bug ID: 477146
   Summary: On X11, the last opened window is not restored by
session restore
Classification: Plasma
   Product: plasmashell
   Version: 5.27.80
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Session Management
  Assignee: plasma-b...@kde.org
  Reporter: kishor...@gmail.com
  Target Milestone: 1.0

SUMMARY
In the Plasma 6 alpha, while using the X11 session, session restore does not
restore the last window that the user opened, but all other windows seem to be
restored correctly.

STEPS TO REPRODUCE
1. Log in to the X11 session
2. In System Settings > Session > Desktop Session, set 'on login launch apps
that were open:' to 'on last logout'
3. Close all open windows
4. Use krunner to open a Konsole window
5. Use krunner to open another Konsole window
6. Reboot by invoking krunner and typing 'restart'
7. Login to X11 session after reboot

OBSERVED RESULTS
The window opened in step 5 is not restored.

EXPECTED RESULTS
Windows of all applications that support session restore should be restored.

ADDITIONAL INFORMATION
A. If the window in step 5 is opened by using Konsole's Ctrl+Shift+N (new
window) shortcut in the existing Konsole window, session restore restores both
the Konsole windows (i.e. the bug does not occur).
B. The same bug is reproducible for other applications like Dolphin and System
Settings.
C. The bug also occurs if the window in step 5 was opened through the
application launcher menu (the one that is on the left side of the panel by
default).
D. Also reproducible in a fresh user account (ran `rm -rf .config .local .cache
.bash*` in a tty to clear all settings).

SOFTWARE VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.245.0
Qt Version: 6.6.0
Kernel Version: 6.1.62-1-lts (64-bit)
Graphics Platform: X11
Konsole 24.01.75
Dolphin 24.01.75

-- 
You are receiving this mail because:
You are watching all bug changes.

[kile] [Bug 445598] Dynamic word wrapping in Kile stopped working in Ubuntu 21.10

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=445598

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

--- Comment #2 from Kishore Gopalakrishnan  ---
Unable to reproduce on Arch Linux with the same version of Kile.

kile 2.9.93
Operating System: Arch Linux 
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11
Graphics Platform: X11

-- 
You are receiving this mail because:
You are watching all bug changes.

[kile] [Bug 471354] After commit a87b38362f945e6132de24c2f1c83ada1eb4447d terminal issues

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=471354

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 473897] Cannot add Google Groupware, "Configured account does not exist" then "Resource is not configured"

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=473897

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 468067] kwin sometimes crashes after Alt+Tab in KWin::isHighlightWindow()

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=468067

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #3 from Kishore Gopalakrishnan  ---
(In reply to David Edmundson from comment #2)
> Can you include the output of:
> 
> qdbus org.kde.KWin /KWin org.kde.KWin.supportInformation

Here: https://invent.kde.org/-/snippets/2735

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 467074] When returning from screen energy saving, Plasma forgets that an external screen is connected and doesn't assign it a containment

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=467074

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 470050] Dolphin does not restore folders when opened through session restore

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=470050

--- Comment #4 from Kishore Gopalakrishnan  ---
(In reply to Méven Car from comment #2)
> MR https://invent.kde.org/system/dolphin/-/merge_requests/550

That does not seem to fix the issue on my machine (tested situation A).

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 469656] Dolphin cannot remember previously opened tabs

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=469656

--- Comment #32 from Kishore Gopalakrishnan  ---
(In reply to Méven from comment #30)
> Git commit f91e691f26150b0c05c06897a8d85bf3a7fffc06 by Méven Car.
> Committed on 19/05/2023 at 15:41.
> Pushed by meven into branch 'release/23.04'.
> 
> global.cpp: Ensure qApp does not emit signal because of local QEventLoop
> (cherry picked from commit dec80fb0f940ff4e71032c2d3544f0d60a05c4ce)
> 
> M  +2-0src/global.cpp
> 
> https://invent.kde.org/system/dolphin/commit/
> f91e691f26150b0c05c06897a8d85bf3a7fffc06

I built dolphin from the release/23.04 branch (with this commit included), but
the earlier tabs are still not opened when Dolphin is opened as part of session
restore (reproduction steps are described in bug 470050).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 457847] kwin becomes unresponsive, need to restart session

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=457847

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||php4...@gmail.com

--- Comment #33 from Kishore Gopalakrishnan  ---
*** Bug 466317 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 466317] Entire windows randomly black

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=466317

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #7 from Kishore Gopalakrishnan  ---
Please change the status if this is still reproducible with mesa >= 22.3 (see
https://bugs.kde.org/show_bug.cgi?id=457847#c22)

*** This bug has been marked as a duplicate of bug 457847 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 3212] Option to hide backup files as well as dotfiles?

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=3212

--- Comment #71 from Kishore Gopalakrishnan  ---
(In reply to Méven from comment #70)
> Are people still interested in this feature ?
> 
> There a mimetype x-trash that seems to cover most extensions you are
> referring to.
> And this is editable using `keditfiletype5 application/x-trash`
> 
> It might only come with Dolphin with KF6 though.

It would be nice to be able to configure what mimetypes should be hidden (so
that I can then create a custom mimetype that matches the folders/files I want
to hide). For example, I would like to be able to hide all folders called
`__pycache__`. Mine may be a somewhat niche wish, though.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 469316] With multiple tabs, closing split view doesn't update tab name

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=469316

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 470050] New: Dolphin does not restore folders when opened through session restore

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=470050

Bug ID: 470050
   Summary: Dolphin does not restore folders when opened through
session restore
Classification: Applications
   Product: dolphin
   Version: 23.04.1
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: kishor...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
When Dolphin 23.04.1 is restored by resuming an activity or rebooting (with
session restoration enabled), it always shows the default directory (user's
home), instead of showing the folders that were open when the activity was
saved or the computer was shut down.

STEPS TO REPRODUCE
Situation A
1. In a fresh activity, open Dolphin and navigate to any directory other than
the default
2. Suspend the activity
3. Resume the activity

Situation B
1. In System Settings > Startup and Shutdown > Desktop Session, pick the option
to restore applications from last session
2. Open a Dolphin window and navigate to any directory other than the default
3. Reboot and log in

OBSERVED RESULT
A Dolphin window opens in the correct virtual desktop/activity, but it just
shows the default directory (user's home).

EXPECTED RESULT
Session restore should restore the folders that were open in the dolphin
windows.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 6.3.1-arch2-1 (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
Downgrading to 23.04.0 fixes the issue

Git bisect output:

d19800c69198b904ae47cb1e53dfe28f74618eb2 is the first bad commit
commit d19800c69198b904ae47cb1e53dfe28f74618eb2
Author: Méven Car 
Date:   Thu Apr 20 08:50:40 2023 +
Restrict attaching instances to those on the same activity or same virtual
desktop

CCBUG: 408919
(cherry picked from commit b99f6f50eef395a3ceb88fb3d4b7357cbbc13c85)

 src/dolphinmainwindow.cpp | 25 +
 src/dolphinmainwindow.h   |  3 +++
 src/global.cpp| 44 +---
 3 files changed, 61 insertions(+), 11 deletions(-)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 466317] Entire windows randomly black

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=466317

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

--- Comment #5 from Kishore Gopalakrishnan  ---
This seems related to https://bugs.kde.org/show_bug.cgi?id=457847#c8
Are any of you using mesa >= 22.3?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 468318] New: Kate command line options do not work

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=468318

Bug ID: 468318
   Summary: Kate command line options do not work
Classification: Applications
   Product: kate
   Version: 23.03.90
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: kishor...@gmail.com
  Target Milestone: ---

SUMMARY
When I type `kate --version` in a terminal, there is no output (process just
exits immediately). Similar for `kate --help` and `kate -h`

STEPS TO REPRODUCE
1. In a terminal, type `kate --version`

OBSERVED RESULT
No output

EXPECTED RESULT
Version number should be printed

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.10-arch1-1 (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
kwrite --version
and
dolphin --version
work, so it doesn't seem to affect other KDE applications.

Kate opens fine if I don't pass any options.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 468317] New: Duplicated 'show sidebar' action

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=468317

Bug ID: 468317
   Summary: Duplicated 'show sidebar' action
Classification: Applications
   Product: okular
   Version: 23.03.90
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: kishor...@gmail.com
  Target Milestone: ---

Created attachment 157971
  --> https://bugs.kde.org/attachment.cgi?id=157971=edit
Screenshot of the duplicated entries in the keyboard shortcuts dialog

SUMMARY
In 'Settings > Configure Keyboard Shortcuts', I see two items called 'show
sidebar', but only one of them works (the other one does not affect the sidebar
even when a keyboard shortcut is assigned to it).

Similarly, there are two 'show sidebar' actions in the list of available
toolbar buttons, only one of which works.

STEPS TO REPRODUCE
Part A (duplicated keyboard shortcut)
1. Settings > Configure Keyboard shortcuts
2. Search for 'sidebar'

Part B (duplicated toolbar entry)
1. Right-click on Okular toolbar > Configure toolbars
2. In 'main toolbar ', search for 'show sidebar'
3. In 'main toolbar ', search for 'show sidebar'
4. Place the 'show sidebar item in  onto the toolbar and save
changes
5. Try to find the new 'show sidebar' button on the toolbar

OBSERVED RESULT
Part A: Two items called 'show sidebar' (see attached screenshot), one of which
does nothing when a keyboard shortcut is assigned to it
Part B: Only the show sidebar item in okular_shell works, while the other one
shows no button even if placed on the toolbar.

EXPECTED RESULT
Only one 'show sidebar' item

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.10-arch1-1 (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
This is reproducible even in a fresh user account, so it does not seem to be an
issue of stale config files

Bug is reproducible on Arch Linux with Okular versions 23.08.80 and 23.08.90

Git bisect points to
2fbab13e1f439f0dd2c6758d51c80e86ee49392a is the first bad commit
commit 2fbab13e1f439f0dd2c6758d51c80e86ee49392a
Author: Eugene Popov 
Date:   Thu Dec 22 22:50:55 2022 +

Port sidebar to QDockWidget

With this MR, the sidebar can now be (if not locked):
* docked to the left or right side
* undocked and floated as an independent window
* closed with the close button in the header

BUG: 455013

 interfaces/viewerinterface.h |   7 ++
 part/part.cpp|   5 ++
 part/part.h  |   1 +
 part/sidebar.cpp |   5 ++
 part/sidebar.h   |   2 +
 shell/shell.cpp  | 162 ++-
 shell/shell.h|   6 +-
 shell/shell.rc   |   7 +-
 8 files changed, 192 insertions(+), 3 deletions(-)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 468067] New: kwin sometimes crashes after Alt+Tab

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=468067

Bug ID: 468067
   Summary: kwin sometimes crashes after Alt+Tab
Classification: Plasma
   Product: kwin
   Version: 5.27.3
  Platform: Archlinux
OS: Other
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: kishor...@gmail.com
  Target Milestone: ---

SUMMARY
kwin_x11 crashed when I pressed Alt+Tab to switch windows. I remember similar
crashes happening recently (this year), but most of the time Alt+Tab succeeds
without issues.

I have found reports of crashes on Wayland, but the backtrace looks different
in my case (and I am on X11), so I am reporting it separately.

STEPS TO REPRODUCE (not every time)
1. Alt+Tab

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.8-arch1-1 (64-bit)
Graphics Platform: X11
Graphics Processor: AMD Radeon Vega 8 Graphics

BACKTRACE
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/kwin_x11 --replace'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __GI___pthread_sigmask (how=1, newmask=, oldmask=0x0) at
pthread_sigmask.c:43
Downloading source file /usr/src/debug/glibc/glibc/nptl/pthread_sigmask.c...
43return (INTERNAL_SYSCALL_ERROR_P (result)
[Current thread is 1 (Thread 0x7fbee161a180 (LWP 3532))]

[Current thread is 13 (Thread 0x7fbec53ff6c0 (LWP 6454))]

Thread 16 (Thread 0x7fbeafbff6c0 (LWP 4789)):
#0  0x7fbee5a2b9df in __GI___poll (fds=0x7fbea40013b0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fbee456c17f in g_main_context_poll (priority=,
n_fds=1, fds=0x7fbea40013b0, timeout=, context=0x7fbea4000b90)
at ../glib/glib/gmain.c:4584
#2  g_main_context_iterate.constprop.0 (context=0x7fbea4000b90, block=1,
dispatch=1, self=) at ../glib/glib/gmain.c:4271
#3  0x7fbee450e1a2 in g_main_context_iteration (context=0x7fbea4000b90,
may_block=1) at ../glib/glib/gmain.c:4343
#4  0x7fbee6ad8c6c in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fbea4001040, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#5  0x7fbee6a866ec in
QEventLoop::exec(QFlags) (this=0x7fbeafbfeca0,
flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#6  0x7fbee68e725f in QThread::exec() (this=this@entry=0x55c6fa7db740) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#7  0x7fbee78c00e0 in QQmlThreadPrivate::run() (this=0x55c6fa7db740) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/ftw/qqmlthread.cpp:155
#8  0x7fbee68e432a in QThreadPrivate::start(void*) (arg=0x55c6fa7db740) at
thread/qthread_unix.cpp:330
#9  0x7fbee59b6bb5 in start_thread (arg=) at
pthread_create.c:444
#10 0x7fbee5a38d90 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 15 (Thread 0x7fbeaebfd6c0 (LWP 3701)):
#0  __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0,
op=393, expected=0, futex_word=0x55c6f95535d8) at futex-internal.c:57
#1  __futex_abstimed_wait_common (futex_word=futex_word@entry=0x55c6f95535d8,
expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0,
private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2  0x7fbee59b37cf in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x55c6f95535d8, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
futex-internal.c:139
#3  0x7fbee59b5f90 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x55c6f9553588, cond=0x55c6f95535b0) at pthread_cond_wait.c:503
#4  ___pthread_cond_wait (cond=0x55c6f95535b0, mutex=0x55c6f9553588) at
pthread_cond_wait.c:618
#5  0x7fbed92c284c in cnd_wait () at
../mesa-23.0.1/src/c11/impl/threads_posix.c:135
#6  util_queue_thread_func() () at ../mesa-23.0.1/src/util/u_queue.c:290
#7  0x7fbed930bc6c in impl_thrd_routine() () at
../mesa-23.0.1/src/c11/impl/threads_posix.c:67
#8  0x7fbee59b6bb5 in start_thread (arg=) at
pthread_create.c:444
#9  0x7fbee5a38d90 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 14 (Thread 0x7fbe7970f6c0 (LWP 6456)):
#0  __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0,
op=393, expected=0, futex_word=0x55c6fad71a60) at futex-internal.c:57
#1  __futex_abstimed_wait_common (futex_word=futex_word@entry=0x55c6fad71a60,
expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0,
private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2  0x7fbee59b37cf in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x55c6fad71a60, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, 

[KBibTeX] [Bug 467803] User preferences are no longer saved

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=467803

--- Comment #11 from Kishore Gopalakrishnan  ---
(In reply to Thomas Fischer from comment #10)
> Please check the new code. I force-pushed, so you may have to check out anew.
> First, I missed to reproduce the bug as I only tried to switch between
> various commands, but never tried the "No command" option. Then, while
> testing the preferences code, I noticed that free-text fields like "babel
> language" and "bibliography style" did not work correctly and incorrect
> assumed that was the bug you reported.

Thanks, it seems to be fixed now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 197726] Show annotations pop-up text in the reviews sidebar

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=197726

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||rafael.palma.l...@gmail.com

--- Comment #4 from Kishore Gopalakrishnan  ---
*** Bug 450748 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 450748] Show comments of the "Highlighter" and "Pop-up notes" in the sidebar

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=450748

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||kishor...@gmail.com
 Resolution|--- |DUPLICATE

--- Comment #2 from Kishore Gopalakrishnan  ---


*** This bug has been marked as a duplicate of bug 197726 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 197726] Show annotations pop-up text in the reviews sidebar

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=197726

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||toluterib...@gmail.com

--- Comment #3 from Kishore Gopalakrishnan  ---
*** Bug 467173 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 467173] Suggestion on how annotations are displayed in the sidebar

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=467173

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED
 CC||kishor...@gmail.com

--- Comment #1 from Kishore Gopalakrishnan  ---


*** This bug has been marked as a duplicate of bug 197726 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[KBibTeX] [Bug 467803] User preferences are no longer saved

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=467803

--- Comment #9 from Kishore Gopalakrishnan  ---
(In reply to Thomas Fischer from comment #6)
> Then, maybe I fixed a different bug. Can you please specify exactly for
> which setting you can reproduce the bug? In case of doubt, add a screenshot
> (in English, please).

It's the same setting I mentioned in the initial bug report ( Settings >
Configure Kbibtex >  Saving and Exporting > Command for 'Copy reference'). I've
added a video recording now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KBibTeX] [Bug 467803] User preferences are no longer saved

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=467803

--- Comment #8 from Kishore Gopalakrishnan  ---
(In reply to Thomas Fischer from comment #6)
> (In reply to Kishore Gopalakrishnan from comment #5)
> > I can still reproduce the bug after uninstalling kbibtex and building it
> > using the command you mentioned.
> You can test if you are actually running the bugfix version if you go to the
> Babel language combobox. Before, there was just English, Swedish, and
> German. Now there is a much longer list (taken from Babel's docs). Which
> list do you have?

I have the longer list.

> Then, maybe I fixed a different bug. Can you please specify exactly for
> which setting you can reproduce the bug? In case of doubt, add a screenshot
> (in English, please).
> Then, start KBibTeX from the command line and submit anything printed to
> this bug report.

This is what I get on running
$LANG=C bash --norc run-kbibtex.sh https://invent.kde.org/thomasfischer/kbibtex
bugs/kde467803
[cutting out some install/build output]

-- Installing: /tmp/kishore-kbibtex-usr/share/man/man1/kbibtex.1
kbuildsycoca5 running...
[warning] kbuildsycoca5 (unknown:0) - The desktop entry file
"/usr/share/applications/org.freedesktop.Xwayland.desktop" has Type=
"Application" but no Exec line
[warning] kbuildsycoca5 (unknown:0) - Invalid Service : 
"/usr/share/applications/org.freedesktop.Xwayland.desktop"
[warning] kbuildsycoca5 (unknown:0) - The desktop entry file
"/usr/share/applications/qemu.desktop" has Type= "Application" but no Exec line
[warning] kbuildsycoca5 (unknown:0) - Invalid Service : 
"/usr/share/applications/qemu.desktop"
[warning]  (unknown:0) - KLocalizedString: Using an empty domain, fix the code.
msgid: "BibTeX" msgid_plural: "" msgctxt: ""
[warning]  (unknown:0) - KLocalizedString: Using an empty domain, fix the code.
msgid: "BibLaTeX" msgid_plural: "" msgctxt: ""
[warning]  (unknown:0) - KLocalizedString: Using an empty domain, fix the code.
msgid: "No backups" msgid_plural: "" msgctxt: ""
[warning]  (unknown:0) - KLocalizedString: Using an empty domain, fix the code.
msgid: "Local files only" msgid_plural: "" msgctxt: ""
[warning]  (unknown:0) - KLocalizedString: Using an empty domain, fix the code.
msgid: "Both local and remote files" msgid_plural: "" msgctxt: ""
[warning]  (unknown:0) - KLocalizedString: Using an empty domain, fix the code.
msgid: "None" msgid_plural: "" msgctxt: "Comment Quoting"
[warning]  (unknown:0) - KLocalizedString: Using an empty domain, fix the code.
msgid: "@comment{\xE2\x80\xA6}" msgid_plural: "" msgctxt: "Comment Quoting"
[warning]  (unknown:0) - KLocalizedString: Using an empty domain, fix the code.
msgid: "% \xE2\x80\xA6" msgid_plural: "" msgctxt: "Comment Quoting"
[warning]  (unknown:0) - KLocalizedString: Using an empty domain, fix the code.
msgid: "lowercase" msgid_plural: "" msgctxt: "Casing of strings"
[warning]  (unknown:0) - KLocalizedString: Using an empty domain, fix the code.
msgid: "Initial capital" msgid_plural: "" msgctxt: "Casing of strings"
[warning]  (unknown:0) - KLocalizedString: Using an empty domain, fix the code.
msgid: "UpperCamelCase" msgid_plural: "" msgctxt: "Casing of strings"
[warning]  (unknown:0) - KLocalizedString: Using an empty domain, fix the code.
msgid: "lowerCamelCase" msgid_plural: "" msgctxt: "Casing of strings"
[warning]  (unknown:0) - KLocalizedString: Using an empty domain, fix the code.
msgid: "UPPERCASE" msgid_plural: "" msgctxt: "Casing of strings"
[warning]  (unknown:0) - KLocalizedString: Using an empty domain, fix the code.
msgid: "Open Editor" msgid_plural: "" msgctxt: "What to do if double-clicking
on a file view item"
[warning]  (unknown:0) - KLocalizedString: Using an empty domain, fix the code.
msgid: "View Document" msgid_plural: "" msgctxt: "What to do if double-clicking
on a file view item"
[warning]  (unknown:0) - KLocalizedString: Using an empty domain, fix the code.
msgid: "Important" msgid_plural: "" msgctxt: "Color Labels"
[warning]  (unknown:0) - KLocalizedString: Using an empty domain, fix the code.
msgid: "Unread" msgid_plural: "" msgctxt: "Color Labels"
[warning]  (unknown:0) - KLocalizedString: Using an empty domain, fix the code.
msgid: "Read" msgid_plural: "" msgctxt: "Color Labels"
[warning]  (unknown:0) - KLocalizedString: Using an empty domain, fix the code.
msgid: "Watch" msgid_plural:

[KBibTeX] [Bug 467803] User preferences are no longer saved

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=467803

--- Comment #7 from Kishore Gopalakrishnan  ---
Created attachment 157695
  --> https://bugs.kde.org/attachment.cgi?id=157695=edit
video showing bug reproduction

-- 
You are receiving this mail because:
You are watching all bug changes.

[KBibTeX] [Bug 467803] User preferences are no longer saved

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=467803

--- Comment #5 from Kishore Gopalakrishnan  ---
(In reply to Thomas Fischer from comment #4)
> > I can still reproduce this bug with the 'Settings > Configure Kbibtex > 
> > Saving and Exporting > Command for Copy reference' option. I think I
> > correctly built kbibtex from the branch you mentioned (kbibtex --versions
> > says `kbibtex 8261be23 (HEAD), near 0.10.0`).
> > Is there any debug output I can provide to help with this?
> KBibTeX is composed of a number of shared libraries and it may be possible
> that, despite you are running the kbibtex binary compiled from Git, the
> shared libraries installed from the ArchLinux package (with bug) are loaded.
> Try to uninstall the KBibTeX package to remove the libraries.
> 
> Then, I have a special Bash script prepared that simplifies the task of
> fetching the code from Git, compiling it, and setting some environment
> variables for execution:
> https://userbase.kde.org/KBibTeX/
> Development#Quick_Start_to_Run_KBibTeX_from_Git
> The invocation would be:
>   bash run-kbibtex.sh https://invent.kde.org/thomasfischer/kbibtex
> bugs/kde467803

I can still reproduce the bug after uninstalling kbibtex and building it using
the command you mentioned.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KBibTeX] [Bug 467803] User preferences are no longer saved

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=467803

--- Comment #3 from Kishore Gopalakrishnan  ---
(In reply to Thomas Fischer from comment #2)
> I think I fixed this bug. Please check branch 'bugs/kde467803' in my
> personal Git repository and confirm that it got indeed fixed:
> https://invent.kde.org/thomasfischer/kbibtex/-/tree/bugs/kde467803

I can still reproduce this bug with the 'Settings > Configure Kbibtex >  Saving
and Exporting > Command for Copy reference' option. I think I correctly built
kbibtex from the branch you mentioned (kbibtex --versions says `kbibtex
8261be23 (HEAD), near 0.10.0`).

Is there any debug output I can provide to help with this?

-- 
You are receiving this mail because:
You are watching all bug changes.

[KBibTeX] [Bug 467803] New: User preferences are no longer saved

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=467803

Bug ID: 467803
   Summary: User preferences are no longer saved
Classification: Applications
   Product: KBibTeX
   Version: 0.10
  Platform: Archlinux
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: fisc...@unix-ag.uni-kl.de
  Reporter: kishor...@gmail.com
  Target Milestone: ---

SUMMARY
Kbibtex 0.10.0 does not save user preferences (in Settings > Configure Kbibtex)
or read existing saved user preferences

STEPS TO REPRODUCE
1. In Settings > Configure Kbibtex >  Saving and Exporting > Command for 'Copy
reference', change to any of the non-default options
2. Click OK
3. Open the Settings window again and check the option that you changed

OBSERVED RESULT
The option has been reset to default

EXPECTED RESULT
User preferences should be saved.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.8-arch1-1 (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
downgrading to  0.9.3.2 fixes the issue.

Git bisect points to the following commit:
https://invent.kde.org/office/kbibtex/-/commit/19e5b7ec673032b6ab3ec2436c50316203644a6b

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 464639] When detaching a tab, toolbars are always shown in the new window

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=464639

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #4 from Kishore Gopalakrishnan  ---
No longer reproducible on kate 23.03.80

-- 
You are receiving this mail because:
You are watching all bug changes.

[lokalize] [Bug 467562] New: Lokalize crashed when closed

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=467562

Bug ID: 467562
   Summary: Lokalize crashed when closed
Classification: Applications
   Product: lokalize
   Version: 22.12.3
  Platform: Archlinux
OS: Other
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: sdepi...@gmail.com
  Reporter: kishor...@gmail.com
CC: sha...@ukr.net
  Target Milestone: ---

SUMMARY
Lokalize crashed when I closed its window. The crash is not reproducible.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.1.20-1-lts (64-bit)
Graphics Platform: X11

BACKTRACE

Program terminated with signal SIGSEGV, Segmentation fault.
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
Downloading source file /usr/src/debug/glibc/glibc/nptl/pthread_kill.c...
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
[Current thread is 1 (Thread 0x7f866894eac0 (LWP 27868))]

[Current thread is 1 (Thread 0x7f866894eac0 (LWP 27868))]

Thread 10 (Thread 0x7f8630fff6c0 (LWP 28623)):
#0  __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0,
op=393, expected=0, futex_word=0x5655123111b4) at futex-internal.c:57
#1  __futex_abstimed_wait_common (futex_word=futex_word@entry=0x5655123111b4,
expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0,
private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2  0x7f866cc9b7cf in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x5655123111b4, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
futex-internal.c:139
#3  0x7f866cc9df90 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x565512311160, cond=0x565512311188) at pthread_cond_wait.c:503
#4  ___pthread_cond_wait (cond=0x565512311188, mutex=0x565512311160) at
pthread_cond_wait.c:618
#5  0x7f866d2eb7c4 in QWaitConditionPrivate::wait (deadline=...,
this=0x565512311160) at thread/qwaitcondition_unix.cpp:146
#6  QWaitCondition::wait (this=, mutex=0x565511238e08,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#7  0x7f866d2e82f7 in QThreadPoolThread::run (this=0x56551233ac80) at
thread/qthreadpool.cpp:140
#8  0x7f866d2e432a in QThreadPrivate::start (arg=0x56551233ac80) at
thread/qthread_unix.cpp:330
#9  0x7f866cc9ebb5 in start_thread (arg=) at
pthread_create.c:444
#10 0x7f866cd20d90 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 9 (Thread 0x7f862affd6c0 (LWP 29070)):
#0  __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0,
op=393, expected=0, futex_word=0x565512f3b864) at futex-internal.c:57
#1  __futex_abstimed_wait_common (futex_word=futex_word@entry=0x565512f3b864,
expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0,
private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2  0x7f866cc9b7cf in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x565512f3b864, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
futex-internal.c:139
#3  0x7f866cc9df90 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x565512f3b810, cond=0x565512f3b838) at pthread_cond_wait.c:503
#4  ___pthread_cond_wait (cond=0x565512f3b838, mutex=0x565512f3b810) at
pthread_cond_wait.c:618
#5  0x7f866d2eb7c4 in QWaitConditionPrivate::wait (deadline=...,
this=0x565512f3b810) at thread/qwaitcondition_unix.cpp:146
#6  QWaitCondition::wait (this=, mutex=0x5655117f4cd8,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#7  0x7f866d2e82f7 in QThreadPoolThread::run (this=0x565512f3b770) at
thread/qthreadpool.cpp:140
#8  0x7f866d2e432a in QThreadPrivate::start (arg=0x565512f3b770) at
thread/qthread_unix.cpp:330
#9  0x7f866cc9ebb5 in start_thread (arg=) at
pthread_create.c:444
#10 0x7f866cd20d90 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 8 (Thread 0x7f865f6bd6c0 (LWP 28254)):
#0  __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0,
op=393, expected=0, futex_word=0x56551142ff74) at futex-internal.c:57
#1  __futex_abstimed_wait_common (futex_word=futex_word@entry=0x56551142ff74,
expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0,
private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2  0x7f866cc9b7cf in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x56551142ff74, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
futex-internal.c:139
#3  0x7f866cc9df90 in __pthread_cond_wait_common (abstime=0x0, clockid=0,

[kate] [Bug 464552] KWrite configure tab looks very strange in small windows and isn't usable

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=464552

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 452078] Make it easier to modify default LSP config

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=452078

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 464637] Kwin crash

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=464637

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|BACKTRACE   |WAITINGFORINFO

--- Comment #2 from Kishore Gopalakrishnan  ---
It hasn't happened again after rebuilding kwin with debug symbols, so I'll
close it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 464640] New: Typing in navigation bar dropdown then pressing enter does not select first item

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=464640

Bug ID: 464640
   Summary: Typing in navigation bar dropdown then pressing enter
does not select first item
Classification: Applications
   Product: kate
   Version: 22.12.1
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: kishor...@gmail.com
  Target Milestone: ---

SUMMARY
Clicking on an item in the breadcrumbs/navigation bar (the one under the tabbar
that shows the path to the current file as a set of clickable levels) shows a
dropdown in which we can type to filter. In this dropdown, typing and then just
pressing 'enter' does not select the first shown item in the dropdown.

STEPS TO REPRODUCE
1. Enable 'Settings > show navigation bar'
2. Click an item in the navigation bar
3. Type to filter
4. Press 'enter'

OBSERVED RESULT
The seach box disappears, but the list is still shown in its filtered state. To
select an item, you have to press the down arrow before pressing enter.

EXPECTED RESULT
The first item in the filtered list should've been opened after the user
pressed enter.

SOFTWARE/OS VERSIONS
kate 22.12.1
Operating System: Arch Linux 
KDE Plasma Version: 5.26.90
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.7-arch1-1 (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 464639] New: When detaching a tab, toolbars are always shown in the new window

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=464639

Bug ID: 464639
   Summary: When detaching a tab, toolbars are always shown in the
new window
Classification: Applications
   Product: kate
   Version: 22.12.1
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: kishor...@gmail.com
  Target Milestone: ---

SUMMARY
When a tab is detached from an existing Kate window using the right-click menu,
Kate's toolbar is always shown in the new window, regardless of whether the
user has previously chosen to hide the toolbars.

STEPS TO REPRODUCE
1. Go to 'Settings > toolbars shown' and hide both of Kate's toolbars
2. Relaunch Kate and check that the toolbars are not shown
3. Open multiple tabs in the same Kate window
4. Right-click on one of the tabs (in the tabbar) and click 'detach document'

OBSERVED RESULT
In the new window, Kate's toolbars are shown again

EXPECTED RESULT
Kate should always follow the user's toolbar configuration

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.26.90
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.7-arch1-1 (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
The toolbars are correctly hidden when opening a new window through krunner or
through ctrl+shift+N.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 464637] New: Kwin crash

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=464637

Bug ID: 464637
   Summary: Kwin crash
Classification: Plasma
   Product: kwin
   Version: 5.26.90
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: kishor...@gmail.com
  Target Milestone: ---

SUMMARY
While I was using my system, the windows flashed black for a moment, then I got
a crash notification for kwin. I don't remember exactly what I was doing at
that time, so I am unable to reproduce it.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.26.90
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.7-arch1-1 (64-bit)
Graphics Platform: X11
Graphics Processor: AMD Radeon Vega 8 Graphics

BACKTRACE
#0  __GI___pthread_sigmask (how=1, newmask=, oldmask=0x0) at
pthread_sigmask.c:43
#1  0x7f0aa0c51bdd in __GI___sigprocmask (how=,
set=, oset=)
at ../sysdeps/unix/sysv/linux/sigprocmask.c:25
#2  0x7f0aa3d121eb in KCrash::setCrashHandler(void (*)(int))
(handler=handler@entry=0x0) at
/usr/src/debug/kcrash/kcrash-5.102.0/src/kcrash.cpp:414
#3  0x7f0aa3d147e6 in KCrash::defaultCrashHandler(int) (sig=11) at
/usr/src/debug/kcrash/kcrash-5.102.0/src/kcrash.cpp:625
#4  0x7f0aa0c519e0 in  () at /usr/lib/libc.so.6
#5  0x0de1 in  ()
#6  0x55c7cb669460 in  ()
#7  0x55c7cb66a5b8 in  ()
#8  0x7f0aa3814cb7 in
KWin::EffectsHandlerImpl::highlightWindows(QVector const&)
() at /usr/lib/libkwin.so.5
#9  0x7f0aa3a8cbe2 in  () at /usr/lib/libkwin.so.5
#10 0x7f0aa3a9238c in  () at /usr/lib/libkwin.so.5
#11 0x7f0aa3a8bd47 in KWin::TabBox::TabBox::close(bool) () at
/usr/lib/libkwin.so.5
#12 0x7f0aa3a8c06b in KWin::TabBox::TabBox::accept(bool) () at
/usr/lib/libkwin.so.5
#13 0x7f0aa3a8c2f3 in KWin::TabBox::TabBox::modifiersReleased() () at
/usr/lib/libkwin.so.5
#14 0x7f0aa3a951fd in  () at /usr/lib/libkwin.so.5
#15 0x7f0aa385d6bf in
KWin::Application::dispatchEvent(xcb_generic_event_t*) () at
/usr/lib/libkwin.so.5
#16 0x7f0aa1e8470f in
QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*)
(this=, eventType=..., message=message@entry=0x7f0a8c069290,
result=result@entry=0x7ffc9d221620)
at kernel/qabstracteventdispatcher.cpp:495
#17 0x7f0a9c506f71 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
(this=this@entry=0x55c7ccd623c0, event=event@entry=0x7f0a8c069290)
at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbconnection.cpp:579
#18 0x7f0a9c50b550 in
QXcbConnection::processXcbEvents(QFlags)
(this=0x55c7ccd623c0, flags=...)
at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbconnection.cpp:1065
#19 0x7f0a9c52f9c8 in xcbSourceDispatch(GSource*, GSourceFunc, gpointer)
(source=)
at
/usr/src/debug/qt5-base/qtbase/src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:103
#20 0x7f0a9fc6d87b in g_main_dispatch (context=0x7f0a94005010) at
../glib/glib/gmain.c:3454
#21 g_main_context_dispatch (context=0x7f0a94005010) at
../glib/glib/gmain.c:4172
#22 0x7f0a9fcc4c89 in g_main_context_iterate.constprop.0
(context=0x7f0a94005010, block=1, dispatch=1, self=)
at ../glib/glib/gmain.c:4248
#23 0x7f0a9fc6c132 in g_main_context_iteration (context=0x7f0a94005010,
may_block=1) at ../glib/glib/gmain.c:4313
#24 0x7f0aa1ed8b2c in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x55c7cce59210, flags=...)
at kernel/qeventdispatcher_glib.cpp:423
#25 0x7f0aa1e865ac in
QEventLoop::exec(QFlags) (this=0x7ffc9d2219a0,
flags=...)
at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#26 0x7f0aa1e910d9 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#27 0x55c7cb62ec94 in  ()
#28 0x7f0aa0c3c290 in __libc_start_call_main
(main=main@entry=0x55c7cb62e880, argc=argc@entry=2,
argv=argv@entry=0x7ffc9d221c98) at ../sysdeps/nptl/libc_start_call_main.h:58
#29 0x7f0aa0c3c34a in __libc_start_main_impl (main=0x55c7cb62e880, argc=2,
argv=0x7ffc9d221c98, init=, fini=,
rtld_fini=, stack_end=0x7ffc9d221c88) at ../csu/libc-start.c:381
#30 0x55c7cb630205 in  ()

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 449840] Sometimes overview stops accepting keyboard input

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=449840

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 462277] When a window is closed, kwin does not free the memory for its icon

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=462277

--- Comment #3 from Kishore Gopalakrishnan  ---
(In reply to Fushan Wen from comment #2)
> Cannot reproduce

I can still reproduce this on 

Operating System: Arch Linux
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.8
Kernel Version: 5.15.86-1-lts (64-bit)
Graphics Platform: X11
mesa 22.3.2-3

I also noticed that the memory usage shown in ksysguard (for the kwin_x11
process) is much lower than that reported by heaptrack. Does this mean the
leaks found by heaptrack are false positives?

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 453811] Ability to define search engine search URL with no sanitization of queries

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=453811

--- Comment #2 from Kishore Gopalakrishnan  ---
(In reply to Alexander Lohnau from comment #1)
> Can you please give an example of such an engine?

The search engine I initially requested this for ( https://sci-hub.se ) now
seems to work even with the sanitized queries. Feel free to close this if it's
too niche a feature.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kile] [Bug 391923] Live Preview viewer should expose a 'trim margins' option

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=391923

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #4 from Kishore Gopalakrishnan  ---
Still present.

Kile 2.9.94 (built from git)
Operating System: Arch Linux
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Graphics Platform: X11

PS: how do I change the importance of this bug to 'wishlist'?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kile] [Bug 394398] Word count option does not work

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=394398

--- Comment #5 from Kishore Gopalakrishnan  ---
(In reply to Kishore Gopalakrishnan from comment #4)
> The relevant setting is now in Settings > configure Kile > editor > general.
> The workd count is still not shown in the status bar when this is enabled.

Kile 2.9.94 (built from git)
Operating System: Arch Linux
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Graphics Platform: X11

-- 
You are receiving this mail because:
You are watching all bug changes.

[kile] [Bug 394398] Word count option does not work

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=394398

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #4 from Kishore Gopalakrishnan  ---
The relevant setting is now in Settings > configure Kile > editor > general.
The workd count is still not shown in the status bar when this is enabled.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 457847] kwin becomes unresponsive, need to restart session

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=457847

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #31 from Kishore Gopalakrishnan  ---
Marking as an upstream bug as per
https://bugs.kde.org/show_bug.cgi?id=457847#c22

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=458085

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.