[Akonadi] [Bug 410179] PIM events in Plasma calendar causes OOM killer
https://bugs.kde.org/show_bug.cgi?id=410179 Martin Ottmar changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 447740] Crash in QAccessible::queryAccessibleInterface
https://bugs.kde.org/show_bug.cgi?id=447740 --- Comment #10 from Martin Ottmar --- Still keeps crashing "randomly". Few minutes ago just after pressing Alt+TAB to get into KDevelop followed by pressing key "Key_Down" (immediatelly) in order to see lower lines in the current editor tab with some python code. It is possible that the Ctrl key has been pressed too at the same time (HP laptop with some bios troubles in linux - it generates Ctrl key press randomly, especially under heavy load - not spotted in MS Windows when analysed by our technicians). It has been the first crash in QAccessibleEvent related to a key press. Usually, it crashes just after LMB on an editor tab or inside the editor window, but I think, always just after applications switch. Updated Archlinux (5.98.0, 22.08.1), KDevelop with VI mode and with the kdev-python plugin from AUR. Normal X-server configuration with plasma, no any wayland. Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7f169e715f90 in QAccessibleObject::object() const () at /usr/lib/libQt5Gui.so.5 #5 0x7f169f1c00de in QAccessibleWidget::isValid() const () at /usr/lib/libQt5Widgets.so.5 #6 0x7f169e71f0fd in QAccessibleEvent::accessibleInterface() const () at /usr/lib/libQt5Gui.so.5 #7 0x7f169e71acb5 in QAccessible::updateAccessibility(QAccessibleEvent*) () at /usr/lib/libQt5Gui.so.5 #8 0x7f169bde0614 in KateViewInternal::cursorMoved() () at /usr/lib/libKF5TextEditor.so.5 #9 0x7f169bdd6bff in KateViewInternal::updateCursor(KTextEditor::Cursor, bool, bool, bool) () at /usr/lib/libKF5TextEditor.so.5 #10 0x7f169be50cdd in KateVi::NormalViMode::handleKeypress(QKeyEvent const*) () at /usr/lib/libKF5TextEditor.so.5 #11 0x7f169be6169c in KateVi::InputModeManager::handleKeypress(QKeyEvent const*) () at /usr/lib/libKF5TextEditor.so.5 #12 0x7f169be3e88a in KateViInputMode::keyPress(QKeyEvent*) () at /usr/lib/libKF5TextEditor.so.5 #13 0x7f169be3b8f7 in KateViInputMode::stealKey(QKeyEvent*) () at /usr/lib/libKF5TextEditor.so.5 #14 0x7f169bde2875 in KateViewInternal::eventFilter(QObject*, QEvent*) () at /usr/lib/libKF5TextEditor.so.5 #15 0x7f169e28c7f2 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #16 0x7f169ef78b0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #17 0x7f169ef7ddf8 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #18 0x7f169e28cb88 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #19 0x7f169efcf18b in () at /usr/lib/libQt5Widgets.so.5 #20 0x7f169ef78b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #21 0x7f169e28cb88 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #22 0x7f169e73fb50 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () at /usr/lib/libQt5Gui.so.5 #23 0x7f169e720dfe in bool QWindowSystemInterfacePrivate::handleWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/libQt5Gui.so.5 #24 0x7f169e72a0e6 in QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int, QFlags, unsigned int, unsigned int, unsigned int, QString const&, bool, unsigned short) () at /usr/lib/libQt5Gui.so.5 #25 0x7f169e73faf2 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () at /usr/lib/libQt5Gui.so.5 #26 0x7f169e728985 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5 #27 0x7f167ff2f6c0 in () at /usr/lib/libQt5XcbQpa.so.5 #28 0x7f169a1e281b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #29 0x7f169a238ec9 in () at /usr/lib/libglib-2.0.so.0 #30 0x7f169a1e10d2 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #31 0x7f169e2d750c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #32 0x7f169e28532c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #33 0x7f169e28fe59 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #34 0x558bfb28cba9 in () #35 0x7f169da3c290 in () at /usr/lib/libc.so.6 #36 0x7f169da3c34a in __libc_start_main () at /usr/lib/libc.so.6 #37 0x558bfb28d715 in () [Inferior 1 (process 3769) detached] -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 396573] Akonadi is utterly broken for an IMAP account since 5.8.2
https://bugs.kde.org/show_bug.cgi?id=396573 Martin Ottmar changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #10 from Martin Ottmar --- I'm sorry. This has been probably fixed yet in 2019, but I've forgotten to close this. Reading IMAP accounts works fine now (still last versions with archlinux), maybe exept the unpleasant long pause after network re-connection (manual refresh doesn't work too until some timeout - expected automatic pull immediately after network re-connection). -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 410179] PIM events in Plasma calendar causes OOM killer
https://bugs.kde.org/show_bug.cgi?id=410179 --- Comment #9 from Martin Ottmar --- Oh, I'm sorry. I've tried to enable the digital clock PIM plugin few weeks ago, and it didn't crash. PIM started immediately, with working kalendar and containing valid PIM informations. There is not any CPU or (noticeable) memory impact on plasmashell. There is nice new feature like dots as events by each day. At least dots by the first visible day (of each month page) have invalid color, but damn it! Digital clock caPIM events work again within daily using! But I don't know, when it was fixed. The last unsuccessful try before, it was probably last year. I think, this ticket should be closed. Plasma: 5.25.5 Frameworks: 5.98.0 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 451041] New: Kdevelop crash just after a LMB in editor on a source line
https://bugs.kde.org/show_bug.cgi?id=451041 Bug ID: 451041 Summary: Kdevelop crash just after a LMB in editor on a source line Product: kdevelop Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: mirovsk...@gmail.com Target Milestone: --- Application: kdevelop (5.7.211202 (21.12.2)) Qt Version: 5.15.2 Frameworks Version: 5.91.0 Operating System: Linux 5.16.11-arch1-1 x86_64 Windowing System: X11 Distribution: Arch Linux DrKonqi: 5.24.2 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Yet within a spontaneous recovery (full re-indexing) from the previous crash (OOM-killer's work), LMB on any line of a permanently opened python source code file, in order to get editing focus into this source tab, it leads into kdevelop crash. Just after the crash, I removed /tmp/kdevelop-* and /tmp/preamble-* and run kdevelop again. After next full automatic re-indexing was finished, I pressed the LMB on another source line (first action from kdevelop start) of the same python source code again, and another (this one) crash occured again. This problem occurs from time to time for years. System is fully updated archlinux with added kdevelop-python-git 5.6.1.r32.g405b5009-1 AUR package compiled against python 3.9 (actual python-3.10 is not supported yet) The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7f1e5d504fe0 in QAccessibleObject::object() const () at /usr/lib/libQt5Gui.so.5 #5 0x7f1e5def7dae in QAccessibleWidget::isValid() const () at /usr/lib/libQt5Widgets.so.5 #6 0x7f1e5d50e115 in QAccessibleEvent::accessibleInterface() const () at /usr/lib/libQt5Gui.so.5 #7 0x7f1e5d509c15 in QAccessible::updateAccessibility(QAccessibleEvent*) () at /usr/lib/libQt5Gui.so.5 #8 0x7f1e5b47b40b in KateViewInternal::cursorMoved() () at /usr/lib/libKF5TextEditor.so.5 #9 0x7f1e5b47c7c4 in KateViewInternal::updateCursor(KTextEditor::Cursor, bool, bool, bool) () at /usr/lib/libKF5TextEditor.so.5 #10 0x7f1e5b47d0f3 in KateViewInternal::placeCursor(QPoint const&, bool, bool) () at /usr/lib/libKF5TextEditor.so.5 #11 0x7f1e5b47faf2 in KateViewInternal::mousePressEvent(QMouseEvent*) () at /usr/lib/libKF5TextEditor.so.5 #12 0x7f1e5dce7916 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #13 0x7f1e5dcb11a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #14 0x7f1e5dcb5fd7 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #15 0x7f1e5d068b9a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #16 0x7f1e5dcb499f in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /usr/lib/libQt5Widgets.so.5 #17 0x7f1e5dd057d7 in () at /usr/lib/libQt5Widgets.so.5 #18 0x7f1e5dd0737c in () at /usr/lib/libQt5Widgets.so.5 #19 0x7f1e5dcb11a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #20 0x7f1e5d068b9a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #21 0x7f1e5d52c130 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/libQt5Gui.so.5 #22 0x7f1e5d517695 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5 #23 0x7f1e3f76af80 in () at /usr/lib/libQt5XcbQpa.so.5 #24 0x7f1e597b3f13 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #25 0x7f1e5980a0d9 in () at /usr/lib/libglib-2.0.so.0 #26 0x7f1e597b1485 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #27 0x7f1e5d0b4ada in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #28 0x7f1e5d060e6b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #29 0x7f1e5d06c5c7 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #30 0x555b80ebfda1 in () #31 0x7f1e5c9d7310 in __libc_start_call_main () at /usr/lib/libc.so.6 #32 0x7f1e5c9d73c1 in __libc_start_main_impl () at /usr/lib/libc.so.6 #33 0x555b80ec0c4e in () [Inferior 1 (process 57844) detached] Possible duplicates by query: bug 449294, bug 448885, bug 446487, bug 423425, bug 399032. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 440412] New: Broken python file syntax after the r'\\' expression
https://bugs.kde.org/show_bug.cgi?id=440412
Bug ID: 440412
Summary: Broken python file syntax after the r'\\' expression
Product: frameworks-syntax-highlighting
Version: 5.84.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: syntax
Assignee: kwrite-bugs-n...@kde.org
Reporter: mirovsk...@gmail.com
CC: walter.von.entfer...@posteo.net
Target Milestone: ---
SUMMARY
Python file syntax highlighting (in KDevelop) is definitely broken after the
line containing the r'\\' expression. It was probably broken in the last
framework release.
STEPS TO REPRODUCE
1. Open KDevelop
2. Create a new file containing:
class Any:
def AnyMethod(self):
pat = r'\\text'
print ('still correct here')
pat = r'\\'
print ('broken here')
2. Select Python syntax for this file
3. Observe the result
OBSERVED RESULT
File syntax highlight is broken after the pattern r'\\' until the end of the
python file
EXPECTED RESULT
Pattern r'\\' (or possibly r"\\") shall not break the syntax highlighting
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-systemmonitor] [Bug 439615] ksystemstats keeps crashing on every login
https://bugs.kde.org/show_bug.cgi?id=439615 --- Comment #13 from Martin Ottmar --- Thanks for the explanation! No, thanks for that offer very much, but I'm just the reporter here, you're the programmer! I want to have this problem fixed and I will help You as much as I can do... But no any commits from my side! :-D -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439615] ksystemstats keeps crashing on every login
https://bugs.kde.org/show_bug.cgi?id=439615 --- Comment #11 from Martin Ottmar --- Is this enough, or do You know a better way? # sensors -u iwlwifi_1-virtual-0 Adapter: Virtual device temp1: temp1_input: 51.000 fam15h_power-pci-00c4 Adapter: PCI adapter power1: power1_average: 0.000 power1_crit: 14.961 power1_average_interval: 0.010 BAT0-acpi-0 Adapter: ACPI interface in0: in0_input: 16.398 amdgpu-pci-0100 Adapter: PCI adapter vddgfx: in0_input: 0.806 edge: temp1_input: 56.000 temp1_crit: 104000.000 temp1_crit_hyst: -273.150 power1: power1_average: 2774.162 power1_cap: 35.000 k10temp-pci-00c3 Adapter: PCI adapter temp1: temp1_input: 58.000 temp1_max: 70.000 temp1_crit: 95.000 temp1_crit_hyst: 90.000 radeon-pci-0008 Adapter: PCI adapter temp1: temp1_input: 58.000 temp1_crit: 120.000 temp1_crit_hyst: 90.000 acpitz-acpi-0 Adapter: ACPI interface temp1: temp1_input: 58.000 temp1_crit: 255.000 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439615] ksystemstats keeps crashing on every login
https://bugs.kde.org/show_bug.cgi?id=439615 --- Comment #10 from Martin Ottmar --- I don't understand, what is the meaning of the "submit a merge request". I'm sorry, I'm not a KDE programmer nor a community programmer. And I'm fighting with the English language too! :-o -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439615] ksystemstats keeps crashing on every login
https://bugs.kde.org/show_bug.cgi?id=439615 --- Comment #9 from Martin Ottmar --- As You can see above, the valueFeature is NULL on the next line after sensors_get_subfeature(). And I can't see anything what would fill it later. But to be sure: (gdb) br 121 Breakpoint 3 at 0x72a01c41: file /usr/src/debug/ksystemstats-5.22.3/plugins/lmsensors/SensorsFeatureSensor.cpp, line 121. (gdb) c Continuing. Thread 1 "ksystemstats" hit Breakpoint 2, makeSensorsFeatureSensor (chipName=0x555a7e90, feature=0x555b0300, parent=0x556809a0) at /usr/src/debug/ksystemstats-5.22.3/plugins/lmsensors/SensorsFeatureSensor.cpp:121 121 in /usr/src/debug/ksystemstats-5.22.3/plugins/lmsensors/SensorsFeatureSensor.cpp (gdb) p valueFeature $4 = (const sensors_subfeature *) 0x0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439615] ksystemstats keeps crashing on every login
https://bugs.kde.org/show_bug.cgi?id=439615
--- Comment #7 from Martin Ottmar ---
(Damned procrastination!)
(gdb) p *this->m_chipName
$3 = {prefix = 0x561ebee811a0 "fam15h_power", bus = {type = 2, nr = 0}, addr =
196, path = 0x561ebee811c0 "/sys/class/hwmon/hwmon4"}
...
Thread 1 "ksystemstats" hit Breakpoint 1, makeSensorsFeatureSensor
(chipName=0x555a7e90, feature=0x555b0300, parent=0x556809a0) at
/usr/src/debug/ksystemstats-5.22.3/plugins/lmsensors/SensorsFeatureSensor.cpp:100
(gdb) p valueFeature
$1 = (const sensors_subfeature *) 0x0
(gdb) p *chipName
$2 = {prefix = 0x555a81a0 "fam15h_power", bus = {type = 2, nr = 0}, addr =
196, path = 0x555a81c0 "/sys/class/hwmon/hwmon4"}
(gdb) p *feature
$3 = {name = 0x555b0320 "power1", number = 0, type = SENSORS_FEATURE_POWER,
first_subfeature = 0, padding1 = 0}
lm_sensors-3.6.0.r41.g31d1f125-1 (without debug symbols, of course :-/ )
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-systemmonitor] [Bug 439615] ksystemstats keeps crashing on every login
https://bugs.kde.org/show_bug.cgi?id=439615 --- Comment #6 from Martin Ottmar --- You're welcome! -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439615] ksystemstats keeps crashing on every login
https://bugs.kde.org/show_bug.cgi?id=439615 --- Comment #4 from Martin Ottmar --- FYI: (gdb) frame 0 #0 SensorsFeatureSensor::update (this=0x561ebef6e9c0) at /usr/src/debug/ksystemstats-5.22.3/plugins/lmsensors/SensorsFeatureSensor.cpp:142 142 in /usr/src/debug/ksystemstats-5.22.3/plugins/lmsensors/SensorsFeatureSensor.cpp (gdb) p m_valueFeature $1 = (const sensors_subfeature *) 0x0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439615] ksystemstats keeps crashing on every login
https://bugs.kde.org/show_bug.cgi?id=439615 --- Comment #3 from Martin Ottmar --- Hello. Yes, it is easy in archlinux. I can provide binaries. And the full coredump too, if you tell me, how to get it from systemd... :-) -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439615] ksystemstats keeps crashing on every login
https://bugs.kde.org/show_bug.cgi?id=439615 --- Comment #2 from Martin Ottmar --- Created attachment 139948 --> https://bugs.kde.org/attachment.cgi?id=139948=edit coredump dump -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439615] New: ksystemstats keeps crashing on every login
https://bugs.kde.org/show_bug.cgi?id=439615 Bug ID: 439615 Summary: ksystemstats keeps crashing on every login Product: plasma-systemmonitor Version: 5.22.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: mirovsk...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 139928 --> https://bugs.kde.org/attachment.cgi?id=139928=edit dump from journalctl SUMMARY ksystemstats keeps crashing on every login or when starting manually via: systemctl --user start plasma-ksystemstats.service STEPS TO REPRODUCE Just login to a new plasma session from sddm OBSERVED RESULT Ksystemstats coredumps few times (after some retries) and system monitor sensors are not available. EXPECTED RESULT Ksystemstats should start SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I'm sorry. I'm unable to distinguish since when, because of the Arch package ksystemstats was unistalled since its introduction for high cpu consumption... -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 421325] Broken settings agains the context menu after update to last KDE frameworks
https://bugs.kde.org/show_bug.cgi?id=421325 --- Comment #3 from Martin Ottmar --- I'm sorry. I've forgotten to fill status update. I saw few crashes of KDevelop last days (introduced maybe in KDevelop-5.5.0?). I didn't try to reproduce such crash yet, but it seems that it is related to LMB probably with a mouse dragging (maybe after switching applications?). I noticed that probably each of these crashes leads to partial loss of KDevelop configuration. All opened files and projects, but even enabled module settings is forgotten after this crash. I spotted the last crash just yesterday. After re-configuration, I noticed that the behaviour mentioned in this bugreport is gone. What is interesting, I didn't need to change the other settings, only the modules setting was forgotten, it seems. And since the last crash, the VI mode works correctly, and vertical slider minimap is turned off, both as it is set in my KDevelop settings. So it is possible, that this problem can be solved simply by deleting old configuration files. So, maybe this bug should be closed. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 421325] Broken settings agains the context menu after update to last KDE frameworks
https://bugs.kde.org/show_bug.cgi?id=421325 --- Comment #1 from Martin Ottmar --- Huh. Looking to the file /var/log/pacman.log: [2020-05-08T01:33:57+0200] [ALPM] upgraded kdevelop (5.5.0-2 -> 5.5.1-1) I'm sorry, I have missed the last KDevelop update. So, it is possible that the problem mentioned above may be related to the KDevelop update, not to the following KDE frameworks update. My laptop and KDevelop was not (probably) restarted (at least) since thursday until today. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 421325] New: Broken settings agains the context menu after update to last KDE frameworks
https://bugs.kde.org/show_bug.cgi?id=421325
Bug ID: 421325
Summary: Broken settings agains the context menu after update
to last KDE frameworks
Product: kdevelop
Version: 5.5.1
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: UI: general
Assignee: kdevelop-bugs-n...@kde.org
Reporter: mirovsk...@gmail.com
Target Milestone: ---
SUMMARY
I would like to ask You, if is it possible that a KDevelop package needs a
rebuild after updating to last KDE frameworks? Since the system update last
night I have the following problem:
At least the VI mode and slider minimap KDevelop settings is broken and
changing it in the setup is without any effect. I want to have the VI mode
always enabled and the slider minimap always disabled, and I have this
set in the KDevelop settings. But this setting is completely ignored and only
the KDevelop context menu setting is taken in the account. Which is
unfortunately the other behaviour in default (minimap enabled and VI mode
disabled).
The similar settings in KWrite works fine.
STEPS TO REPRODUCE
1. Open KDevelop setting and ensure that the VI mode is still enabled and the
slider minimap is disabled
2. Try in the editor, if the VI mode is really enabled
3. Observe, if the slider minimap is really turned off
OBSERVED RESULT
Settings of the VI mode is turned off, because of it is turned of in the
context menu by default.
Settings of the slider minimap is turned on because of it is turned on in the
context menu by default
EXPECTED RESULT
VI mode shall be turned on and set as the default in the KDevelop context menu
The slider minimap shall be turned off and set as the default in the context
menu
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 20.04
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70
Qt Version: 5.14.2
ADDITIONAL INFORMATION
journal -xe contains strange errors:
kvě 11 12:26:42 iccmonb kdevelop[10065]: Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kvě 11 12:26:42 iccmonb kdevelop[10065]: kdevplatform.shell: Can't load plugin
"kdevastyle" because a factory to load the plugin could not be obtained:
"Knihovnu /usr/lib/qt/plugins/kdevplatform/33/kdevastyle.so nelze nahrát:
(libastyle.so.3: sdílený objektový soubor ne>
kvě 11 12:26:46 iccmonb kdevelop[10065]: kdevplatform.language: Cannot load a
top-context from file
"~/.cache/kdevduchain/kdevelop-{4f7ef71a-d47c-4a93-9c5e-aad486893516}/topcontexts/1979"
- the required language-support for handling ID 100 is probably not load>
kvě 11 12:26:46 iccmonb kdevelop[10065]: kdevplatform.language: Cannot load a
top-context from file
"~/.cache/kdevduchain/kdevelop-{4f7ef71a-d47c-4a93-9c5e-aad486893516}/topcontexts/1979"
- the required language-support for handling ID 100 is probably not load>
kvě 11 12:26:46 iccmonb kdevelop[10065]: kdevplatform.language: Cannot load a
top-context from file
"~/.cache/kdevduchain/kdevelop-{4f7ef71a-d47c-4a93-9c5e-aad486893516}/topcontexts/1979"
- the required language-support for handling ID 100 is probably not load>
kvě 11 12:26:50 iccmonb kdevelop[10065]: kdevplatform.language: Cannot load a
top-context from file
"~/.cache/kdevduchain/kdevelop-{4f7ef71a-d47c-4a93-9c5e-aad486893516}/topcontexts/1979"
- the required language-support for handling ID 100 is probably not load>
kvě 11 12:26:52 iccmonb kwin_x11[673]: qt.qpa.xcb: QXcbConnection: XCB error: 3
(BadWindow), sequence: 58082, resource id: 117440523, major code: 18
(ChangeProperty), minor code: 0
kvě 11 12:26:52 iccmonb kdevelop[10065]: qrc:/qml/Develop.qml:139:21: QML
Heading: Binding loop detected for property "font.pointSize"
kvě 11 12:26:52 iccmonb kdevelop[10065]: qrc:/qml/area_code.qml:87:9: QML
Heading: Binding loop detected for property "font.pointSize"
kvě 11 12:26:52 iccmonb kdevelop[10065]: qrc:/qml/area_code.qml:63:9: QML
Heading: Binding loop detected for property "font.pointSize"
kvě 11 12:26:55 iccmonb kdevelop[10065]: kdevelop.plugins.welcomepage: "Last
fetch of news feed was on po kvě 11 09:01:03 2020 GMT+0200"
kvě 11 12:27:03 iccmonb kdevelop[10065]: kdevelop.plugins.python.duchain:
Custom python interpreter "/usr/local/bin/python3.6dm" configured for project
"IDP-pyqt" is invalid, using default
kvě 11 12:27:12 iccmonb kdevelop[10065]: kdevplatform.shell: formatter plugin
"kdevcustomscript" supports unknown mimetype entry "text/x-objc++src"
kvě 11 12:27:12 iccmonb kdevelop[10065]: kdevplatform.shell: formatter plugin
"kdevcustomscript" supports unknown mimetype entry "text/x-objchdr"
kvě 11 12:27:12 iccmonb kdevelop[10065]: kdevplatform.shell: formatter plugin
"kdevcustomscript" supports unknown mimetype entry "text/x-objc++src"
kvě 11 12:27:12 iccmonb kdevelop[10065]: kdevplatform.shell: formatter plugin
"kdevcustomscript" supports unknown
[plasmashell] [Bug 410179] Plasma shell killed by OOM killer after few seconds of running
https://bugs.kde.org/show_bug.cgi?id=410179 --- Comment #4 from Martin Ottmar --- It seems that the problem won't appear until I enable "PIM events plugin" in settings of digital clock applet. When I enable "PIM events plugin" option, there are missing calendars to choose at all in the side "tab", but at the moment, akonadiserver, mysql and akonadi_imap_resource_3(?!) start to exhaust CPU for a lot of minutes. And RAM allocated for plasmashell starts to grow slowly (cca 200kB per second?). And then, let's say, after cca 10minutes (probably just when akonadi_indexing_agent starts) the consumed memory skyrokets up to 2GB... If there is enough of free memory and OOM killer leaves plasmashell running, then CALDAV calendar events finally appear in the digital clock calendar, and akonadi stops draining CPU. This akonadi behaviour is new too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 410179] Plasma shell killed by OOM killer after few seconds of running
https://bugs.kde.org/show_bug.cgi?id=410179 --- Comment #3 from Martin Ottmar --- (With the current configuration): Running with the software renderer doesn't make any difference. Even with compositing completely turned off. After the "configuration reset", plasmashell starts immediately with the "usual" size in memory, but... Today I've noticed that just after boot, the plasmashell was running with the "usual" portion of memory. But, it was killed by OOM killer after 22 minutes of uptime. If I remember well, the progress was the same yesterday in the morning. The first killing occurred after some amount of time, but each (working) day, I'm using my system exactly the same way. So, I'm going to try to configure plasma again, as it was before the configuration reset and to watch its behaviour carefully. For now, thanks for Your interest and I'm sorry for my bad English. BTW: what does the "Tokenizer Warning: 8Bit character" message mean? I mean, how to distinguish, from where it comes from? I've noticed it before within restarting akonadi (when I was fighting with akonadi problems). I'm using UTF-8 within the whole system -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 410179] Plasma shell killed by OOM killer after few seconds of running
https://bugs.kde.org/show_bug.cgi?id=410179 --- Comment #2 from Martin Ottmar --- Created attachment 121737 --> https://bugs.kde.org/attachment.cgi?id=121737=edit plasmashell console output -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 410179] New: Plasma shell killed by OOM killer after few seconds of running
https://bugs.kde.org/show_bug.cgi?id=410179 Bug ID: 410179 Summary: Plasma shell killed by OOM killer after few seconds of running Product: plasmashell Version: 5.16.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mirovsk...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Since plasma 5.16.3 there is a problem with plasmashell memory consumption. It takes about 2.1GB of RAM just after start. Remember me, was it less than 200MB before? :-o I have nothing special. Two panels. The basic (hiding) panel contains few icons, temperature monitor (CPU and GPU temperature monitoring), standard weather widget and kdeconnect. The additional hiding pannel contains network monitor only. There are not any other widgets or icons on the destop (just black background), I don't use features like activities or semantic desktop (or anyhow else you call it). KWIN compositing is turned on, but only few. I'm using this same configuration for years. The interesting is that if I don't start my usual applications and the OOM killer keeps the plasmashell running, the memory consumption gets back to normal (about 150MB) after some while (about 10 minutes). It is not preceded by any special CPU activity I have laptop with 8GB of memory but 3GB are preserved for tmpfs (ramdisks in order to spare writting cycles for SSD). The swap memory is completely turned off. Private memory 2011600 KB [heap] 5320 KB /memfd:JSGCHeap:/usr/lib/libQt5Qml.so.5 (deleted) 4396 KB /usr/lib/libLLVM-8.so 2112 KB /usr/lib/libtelepathy-qt5.so.0.0.9.7 1768 KB ~/.cache/plasma_theme_oxygen_v5.60.0.kcache Shared memory 33644 KB /usr/lib/libLLVM-8.so 6128 KB /usr/lib/dri/radeonsi_dri.so 5144 KB /usr/lib/libQt5Gui.so.5.13.0 4316 KB /usr/lib/libQt5Core.so.5.13.0 3884 KB /usr/lib/libQt5Qml.so.5.13.0 Totals Pixmap 34604 KB(Might be stored in the graphics card's memory) Private 2056140 KB (= 25624 KB clean + 2030516 KB dirty) Shared 133268 KB (= 133176 KB clean + 92 KB dirty) Rss 2189408 KB (= Private + Shared) Pss 2081083 KB (= Private + Shared/Number of Processes) Swap0 KB STEPS TO REPRODUCE 1. Just start KDE and wait until plasma shell is fully loaded OBSERVED RESULT Plasmashell is killed by OOM killer when running my applications as usual. If not, the memory consumption gets back to normal after cca 10 minutes of running EXPECTED RESULT Plasmashell starts and keeps running consuming much less memory (cca. 150MB of RAM) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 396573] Akonadi is utterly broken for an IMAP account since 5.8.2
https://bugs.kde.org/show_bug.cgi?id=396573 --- Comment #9 from Martin Ottmar --- Just sixt months (from the first report) without my favorite email account on my desktop. Currently there is akonadi 18.12.1/5.10.1 installed. All problems reported within this ticket are still here. I don't see much progress even in other reported bugs. Is akonadi dead? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 396573] Akonadi is utterly broken for an IMAP account since 5.8.2
https://bugs.kde.org/show_bug.cgi?id=396573
--- Comment #5 from Martin Ottmar ---
I'm pretty sure, I've tried all three interesting methods ("Čistý text",
"PLAIN" and "LOGIN") for all encryption methods (None, SSL/TLS and STARTTLS).
And the PLAIN method was the preferred one. No any combination is working now,
with the new akonadi 18.08/5.9.0 (Good news everyone, the google account is
broken now! :-D ). I looks like any combination I choose is ignored completely,
and it uses the same default with the same result.
BTW: What is the difference between methods "Čistý text" and "PLAIN", if any?
If I try to set STARTTLS/PLAIN (None/PLAIN / STARTTLS/PLAIN) and then I drop
the mentioned iptables output rule, and to renew the incoming manually, the
follow mouse policy method makes the desktop unusable, and the network traffic
skyrockets immediately. Sometimes, within this hell, I'm able to see the
strange window mentioned above for a moment, but it disappears immediately.
The following is from the akonadi console:
Job ID Created Wait Time Job DurationJob Type
State Info
akonadi_imap_resource_1
19538 15:20:25 CEST.935 00:00:00.014
Custom-startConnect Running
19541 15:20:25 CEST.964 00:00:00.007
Custom-startConnect Running
19544 15:20:25 CEST.987 00:00:00.009
Custom-startConnect Running
19547 15:20:26 CEST.009 00:00:00.008
Custom-startConnect Running
19550 15:20:26 CEST.031 00:00:00.010
Custom-startConnect Running
19553 15:20:26 CEST.054 00:00:00.009
Custom-startConnect Running
19556 15:20:26 CEST.076 00:00:00.011
Custom-startConnect Running
19559 15:20:26 CEST.100 00:00:00.011
Custom-startConnect Running
19562 15:20:26 CEST.123 00:00:00.009
Custom-startConnect Running
19565 15:20:26 CEST.144 00:00:00.014
Custom-startConnect Running
19568 15:20:26 CEST.172 00:00:00.009
Custom-startConnect Running
19571 15:20:26 CEST.197 00:00:00.012
Custom-startConnect Running
19574 15:20:26 CEST.222 00:00:00.009
Custom-startConnect Running
19577 15:20:26 CEST.244 00:00:00.010
Custom-startConnect Running
19580 15:20:26 CEST.267 00:00:00.011
Custom-startConnect Running
19583 15:20:26 CEST.291 00:00:00.012
Custom-startConnect Running
19586 15:20:26 CEST.316 00:00:00.009
Custom-startConnect Running
19589 15:20:26 CEST.338 00:00:00.010
Custom-startConnect Running
19592 15:20:26 CEST.364 00:00:00.011
Custom-startConnect Running
19595 15:20:26 CEST.389 00:00:00.009
Custom-startConnect Running
19598 15:20:26 CEST.411 00:00:00.009
Custom-startConnect Running
19601 15:20:26 CEST.432 00:00:00.009
Custom-startConnect Running
19604 15:20:26 CEST.454 00:00:00.012
Custom-startConnect Running
19607 15:20:26 CEST.479 00:00:00.012
Custom-startConnect Running
19610 15:20:26 CEST.505 00:00:00.010
Custom-startConnect Running
19613 15:20:26 CEST.528 00:00:00.011
Custom-startConnect Running
19616 15:20:26 CEST.558 00:00:00.012
Custom-startConnect Running
19619 15:20:26 CEST.590 00:00:00.012
Custom-startConnect Running
19622 15:20:26 CEST.620 00:00:00.009
Custom-startConnect Running
19625 15:20:26 CEST.646 00:00:00.010
Custom-startConnect Running
19628 15:20:26 CEST.673 00:00:00.009
Custom-startConnect Running
19631 15:20:26 CEST.695 00:00:00.012
Custom-startConnect Running
19634 15:20:26 CEST.725 00:00:00.012
Custom-startConnect Running
19637 15:20:26 CEST.751 00:00:00.014
Custom-startConnect Running
19640 15:20:26 CEST.778 00:00:00.009
Custom-startConnect Running
19643 15:20:26 CEST.801 00:00:00.009
Custom-startConnect Running
19646 15:20:26 CEST.822 00:00:00.009
Custom-startConnect Running
19649 15:20:26 CEST.844 00:00:00.011
Custom-startConnect Running
19652 15:20:26 CEST.870 00:00:00.011
Custom-startConnect Running
19655 15:20:26 CEST.893 00:00
[Akonadi] [Bug 396573] Akonadi is utterly broken for an IMAP account since 5.8.2
https://bugs.kde.org/show_bug.cgi?id=396573 --- Comment #3 from Martin Ottmar --- Almost two months without my favorite IMAP account. :-O Akonadi has been "fixed" by adding iptables permanent DROP rule for OUTPUT packets to the broken IMAP server. It "fixes" everything strange meant above, except the IMAP account itself, of course, which behaves as disconnected now. So, akonadi and the KDE workspace are usable together again. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 396573] Akonadi is utterly broken for an IMAP account since 5.8.2
https://bugs.kde.org/show_bug.cgi?id=396573 --- Comment #2 from Martin Ottmar --- I'm unable to find anything about this broken IMAP resource logged in akonadi console logs. There are plenty of messages from other IMAP resources and from CALDAV resource. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 396573] Akonadi is utterly broken for an IMAP account since 5.8.2
https://bugs.kde.org/show_bug.cgi?id=396573 --- Comment #1 from Martin Ottmar --- Created attachment 113969 --> https://bugs.kde.org/attachment.cgi?id=113969=edit network traffic generated when akonadi is running -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 396573] New: Akonadi is utterly broken for an IMAP account since 5.8.2
https://bugs.kde.org/show_bug.cgi?id=396573 Bug ID: 396573 Summary: Akonadi is utterly broken for an IMAP account since 5.8.2 Product: Akonadi Version: 5.8.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: IMAP resource Assignee: kdepim-b...@kde.org Reporter: mirovsk...@gmail.com Target Milestone: --- Created attachment 113968 --> https://bugs.kde.org/attachment.cgi?id=113968=edit annoying windows I have a problem since the akonadi 18.04/5.8.2 (installed on friday 9th of June (archlinux)). One of my IMAP accounts (volny.cz) stopped working in kmail just after the update. The original settings was STARTTLS/143. But as I verified later from server support, the server volny.cz doesn't support STARTTLS for IMAP at all. So, it seems that for many years I was connected insecure from k9-mail and from kmail (Is it possible to notify the user about this fallback?). :-/ Actually, there is another annoying behaviour of akonadi, which leads into state, when I'm blocked on the server for next one day as a spammer (Because I'm unable to logging from my phone via the k9-mail anymore within this time period - without changing anything there). There is a strange window (Please excuse my free translation fom Czech language and my poor English): Unable to verify - Volny.cz type E-mail IMAP server Server for account "Volny.cz" refused given username and password. Authentication method failed, server answered: A02 NO Bad username or password [ AUTHENTICATIONFAILED ] I keep getting these windows. Sometimes I have more than 30 instances of these windows appeared at the same time, sometimes, a previous instance get immediately closed automatically. But they are steeling mouse focus (focus follow mouse settings) for more than three seconds with terrible window blinking. Sometimes I'm even unable to turn akonadi off from KDE at all. This comes together with permanent network traffic (about 170kbps). And even if the account gets blocked in akonadi after some while with strange message (which is not true anyway): "Unable to read password: User refused access to wallet", I'm probably still keep getting these windows even they are not visible (periodically loosing focus until I stop akonadi completely). I have next three IMAP accounts with TLS configured in akonadi. And it seems that they work correctly. Fix of the KDE bug #395249 doesn't have any possitive effect. It is still broken the same way with akonadi 5.8.3. Maybe it is worst, because akonadi won't disable the account automatically anymore, I think. I'm unable to disable checking of this broken account without deleting it from akonadi. When I press LMB on an Inbox folder of any other account, this hell will start again immediately, even if the volny.cz account is not visible in kmail and removed from manual or automatic email checking. The problem is, that explicit change to other configurations (insecure connection or SSL/993) doesn't change anything, too. The only found "solution" is to turn akonadi off. :-/ -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 395249] Akonadi 5.8.2 breaks existing IMAP/STARTTLS account
https://bugs.kde.org/show_bug.cgi?id=395249 Martin Ottmar changed: What|Removed |Added CC||mirovsk...@gmail.com --- Comment #7 from Martin Ottmar --- I have probably the same problem since the last update to akonadi 18.04/5.8.2 on friday 9th (archlinux). One of my IMAP accounts (volny.cz) stopped working in kmail just after the update. The original settings was STARTTLS/143. But as I verified later, the server volny.cz doesn't support STARTTLS for IMAP at all. So, it seems that for many years I was connected insecure from k9-mail and from kmail. :-/ But in my case, changing to other configurations (insecure connection or SSL/993) doesn't work too. Actually, there is another annoying behaviour of akonadi, which leads into state, when I'm most probably blocked on the server as a spammer (Because I'm unable to logging from my phone via the k9-mail anymore - without changing anything there). There is a strange window (Please excuse my free translation fom Czech language and my poor English): Unable to verify - Volny.cz type E-mail IMAP server Server for account "Volny.cz" refused given username and password. Authentication method failed, server answered: A02 NO Bad username or password [ AUTHENTICATIONFAILED ] I keep getting these windows. Sometimes I have more than 30 instances of these windows appeared at the same time, sometimes, a previous instance get immediately closed automatically. But they are steeling mouse focus for more than one second with terrible window blinking. And even if the account gets blocked in akonadi after a while with strange message (which is not true anyway): "Unable to read password: User refused access to wallet", I'm probably still keep getting these windows even they are not visible (periodically loosing focus until I stop akonadi completely). In akonadi, I have next three IMAP accounts with TLS configured and it seems that they work correctly. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 372835] New: Korganizer and Digital Clock/Calendar widget keep forgetting of selected Caldav resources
https://bugs.kde.org/show_bug.cgi?id=372835 Bug ID: 372835 Summary: Korganizer and Digital Clock/Calendar widget keep forgetting of selected Caldav resources Product: Akonadi Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: DAV Resource Assignee: kdepim-b...@kde.org Reporter: mirovsk...@gmail.com Target Milestone: --- Our company CalDav calendar resource contains two calendars called "Personal Callendar" and "Staff". I'm not using the personal calendar, so I have it permanently disabled. But, when I enable the "Staff" calendar, by checking a certain CheckBox in Korganizer calendar viewer, or in the panel->Digital Clock Settings->PIM Events Plugin, akonadi (usually) forgets this setting after next plasma session login. Setting this resource as default in the korganizer doesn't have any effect. This behaviour has been confirmed on (archlinux) machine of my colleague. This behaviour (in korganizer) is there since KDE-3.5 or before. This behaviour is new in KF5 for the new style Digital Clock/Calendar plasma widget. Best regards. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 337953] Broken message with windows cp1250 encoding
https://bugs.kde.org/show_bug.cgi?id=337953 Martin Ottmar <mirovsk...@gmail.com> changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #4 from Martin Ottmar <mirovsk...@gmail.com> --- I'm sorry. I've forgotten to close it (Do I have permissions to do it?). It works again (on all my platforms) since I've migrated my desktop to plasma5. So it should be closed. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 367999] New: It would be a "killer-app" with akonadi/kadressbook integration and full SMS chat support
https://bugs.kde.org/show_bug.cgi?id=367999 Bug ID: 367999 Summary: It would be a "killer-app" with akonadi/kadressbook integration and full SMS chat support Product: kdeconnect Version: unspecified Platform: unspecified OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: mirovsk...@gmail.com It would be a "killer-app" with akonadi/kadressbook integration and full SMS chat support I believe KDE connect could help to KDE pim support. I would like to have full PC/phone contacts synchronization with possibility of intelligent contacts merging (e.g. automatical searching for duplicate numbers and contacts graphical merging in kdiff3-like style - but this would be request for kaddressbook team). Also having a possibility to answer a SMS is very fine, but: When the notification popup disappears, there is not another possibility how to do that (maybe the message is in the kdeconnect widget history, but the possibility to answer is missing). Besides, there is a known bug, when the "Reply" button is missing even in the popup notification window (if the popup notification window is enabled even for general notifications). So my wish is to implement full PC chat support in phone-like style. I mean new tabbed window which contains contact(s) line (not editable when entering via "Reply" button), history groupbox, , message editbox (possibly with SMS message breaking support), and "Send"/"Close" buttons. Having a smileys support there would be a nice bonus ;-) I don't want to disturb my colleagues in our office. I have headphones in my working laptop, the phone sound is muted. I don't want to touch my phone when a new SMS is received (I mean to unlock the phone and to start a fight with small phone keyboard), I'm working with my laptop and writing a SMS via normal keyboard is much easier and faster for me. All I want is a notification popup (with current possibility to reply) and visual notification in systray. And only the last unread message (for each contact) keep staying in the notification history with formatting like: []: LMB on the "Reply" button should open a new tab in the chat window or to move focus to the existing one. But I want a "Send SMS" button too. For contact without history. This button could open a new tab in the chat window with contact full search support (with an advice popup like in kmail), but there could be a possibility to choose a contact in kaddressbook too. So, this is my dream and I believe it is not only my. I'm sorry for my bad English Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
