[kmymoney] [Bug 459881] edit loan wizard does not take empty value for principal and interest
https://bugs.kde.org/show_bug.cgi?id=459881 --- Comment #12 from Andriy Gapon --- The branch is at commit 581d3ef3940828479eb6a71cfd981760950b8839 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 459881] edit loan wizard does not take empty value for principal and interest
https://bugs.kde.org/show_bug.cgi?id=459881 --- Comment #11 from Andriy Gapon --- (In reply to Jack from comment #10) > Please specify exactly which version you are using to test, to be sure that > version does include the fix. This is branch 5.1 updated today in a Git repo cloned from https://invent.kde.org/office/kmymoney.git -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 459881] edit loan wizard does not take empty value for principal and interest
https://bugs.kde.org/show_bug.cgi?id=459881 --- Comment #9 from Andriy Gapon --- I am afraid that the change (as applied to 5.1 branch) has not fully fixed the issue for me. It does allow to leave the fields as empty and that fixes the original problem. But even if I leave one of the fields empty the wizard produces an error saying that I entered inconsistent values. Please see attached repro step 1 -6 images. It's possible that I am doing something wrong or that my earlier experiments created some sort of an edge case in the database (e.g., the current interest rate of zero). Could you please review this report? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 459881] edit loan wizard does not take empty value for principal and interest
https://bugs.kde.org/show_bug.cgi?id=459881 --- Comment #8 from Andriy Gapon --- Created attachment 160686 --> https://bugs.kde.org/attachment.cgi?id=160686=edit repro step 6 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 459881] edit loan wizard does not take empty value for principal and interest
https://bugs.kde.org/show_bug.cgi?id=459881 --- Comment #7 from Andriy Gapon --- Created attachment 160685 --> https://bugs.kde.org/attachment.cgi?id=160685=edit repro step 5 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 459881] edit loan wizard does not take empty value for principal and interest
https://bugs.kde.org/show_bug.cgi?id=459881 --- Comment #6 from Andriy Gapon --- Created attachment 160684 --> https://bugs.kde.org/attachment.cgi?id=160684=edit repro step 4 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 459881] edit loan wizard does not take empty value for principal and interest
https://bugs.kde.org/show_bug.cgi?id=459881 --- Comment #5 from Andriy Gapon --- Created attachment 160683 --> https://bugs.kde.org/attachment.cgi?id=160683=edit repro step 3 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 459881] edit loan wizard does not take empty value for principal and interest
https://bugs.kde.org/show_bug.cgi?id=459881 --- Comment #4 from Andriy Gapon --- Created attachment 160682 --> https://bugs.kde.org/attachment.cgi?id=160682=edit repro step 2 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 459881] edit loan wizard does not take empty value for principal and interest
https://bugs.kde.org/show_bug.cgi?id=459881 --- Comment #3 from Andriy Gapon --- Created attachment 160681 --> https://bugs.kde.org/attachment.cgi?id=160681=edit repro step 1 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424511] Loan will not calculate and does
https://bugs.kde.org/show_bug.cgi?id=424511 --- Comment #8 from Andriy Gapon --- (In reply to Jack from comment #7) > What should the subject of this bug actually be? The current one doesn't > really make sense. (It's worth fixing to assist future searching.) Perhaps, [some] fields cannot be left empty [for auto-calculation] in the loan wizard ? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424511] Loan will not calculate and does
https://bugs.kde.org/show_bug.cgi?id=424511 Andriy Gapon changed: What|Removed |Added CC||a...@uabsd.com --- Comment #6 from Andriy Gapon --- Bug 459881 seems to be related. Thomas, could you please take a look at it if / when you have time? Thank you. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 377246] count of new messages is shown incorrectly sometimes
https://bugs.kde.org/show_bug.cgi?id=377246 Andriy Gapon changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 269718] ksplashx crash in (unusual?) dual monitor setup
https://bugs.kde.org/show_bug.cgi?id=269718 --- Comment #5 from Andriy Gapon --- I haven't been using that kind of vertical monitor arrangement for many years. I think that the issue can be easily checked, but right now I do not have two monitors near me. -- You are receiving this mail because: You are watching all bug changes.
[kscd] [Bug 133834] No sound if CD-ROM drive has no audio cable
https://bugs.kde.org/show_bug.cgi?id=133834 --- Comment #14 from Andriy Gapon --- I no longer have that kind of *hardware* around. It's been 15 years after all. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 377246] count of new messages is shown incorrectly sometimes
https://bugs.kde.org/show_bug.cgi?id=377246 Andriy Gapon changed: What|Removed |Added Version|unspecified |1.7.0 Platform|Other |FreeBSD Ports -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 377246] count of new messages is shown incorrectly sometimes
https://bugs.kde.org/show_bug.cgi?id=377246 --- Comment #3 from Andriy Gapon --- Still seeing the problem with latest that I have installed: - choqok 1.7.0 - KDE Frameworks 5.99.0 - Qt 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 459881] edit loan wizard does not take empty value for principal and interest
https://bugs.kde.org/show_bug.cgi?id=459881 --- Comment #1 from Andriy Gapon --- Created attachment 152532 --> https://bugs.kde.org/attachment.cgi?id=152532=edit the error box -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 459881] New: edit loan wizard does not take empty value for principal and interest
https://bugs.kde.org/show_bug.cgi?id=459881 Bug ID: 459881 Summary: edit loan wizard does not take empty value for principal and interest Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Other OS: FreeBSD Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: a...@uabsd.com Target Milestone: --- Created attachment 152531 --> https://bugs.kde.org/attachment.cgi?id=152531=edit screenshot of the principal and interest step SUMMARY Trying to change interest rate on a load account and can't "leave empty" Principal and interest field at the corresponding step of the wizard. If I leave the field empty it magically becomes 0.00. When I enter the new interest rate at the next step I cannot go past it because the Wizard complain that the values do not match and I should leave one of them empty. STEPS TO REPRODUCE 1. Launch Edit loan wizard and select Modify the interest rate option 2. Select variable rate, etc 3. Try to leave Principal and interest value empty 4. Enter new interest value OBSERVED RESULT Wizard complains about mismatching values. EXPECTED RESULT Wizard should accept the new interest rate and calculate other parameters based on it. SOFTWARE/OS VERSIONS KDE Frameworks Version 5.98.0 Qt Version 5.15.5 (built against 5.15.5) The xcb windowing system ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447014] konsole window should be raised when dragging a tab over its taskbar entry
https://bugs.kde.org/show_bug.cgi?id=447014 Andriy Gapon changed: What|Removed |Added Platform|Other |FreeBSD Ports -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447014] New: konsole window should be raised when dragging a tab over its taskbar entry
https://bugs.kde.org/show_bug.cgi?id=447014 Bug ID: 447014 Summary: konsole window should be raised when dragging a tab over its taskbar entry Product: konsole Version: 21.08.3 Platform: Other OS: FreeBSD Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: a...@uabsd.com Target Milestone: --- Suppose I have two maximized konsole windows and I want to move a tab from one to the other. At present I have to unmaximize both windows and then drag the tab. It would be more convenient if I could start dragging in one (maximized) window, drag the tab over a taskbar entry of the other window, the window got raised / activated and I could finish dragging in the target window. Some applications already behave like that when something is being dragged onto their taskbar entry. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 443411] Regression: %w and %t placeholders not available in bell notifications
https://bugs.kde.org/show_bug.cgi?id=443411 Andriy Gapon changed: What|Removed |Added CC||a...@uabsd.com --- Comment #5 from Andriy Gapon --- I can confirm the same problem with, e.g., '%w' using Konsole 21.08.3. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 435309] 3b06b6f22 makes selection near invisible with some foreground/background color combinations
https://bugs.kde.org/show_bug.cgi?id=435309 Andriy Gapon changed: What|Removed |Added CC||a...@uabsd.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 434573] built-in calculator widget can extend beyond main window
https://bugs.kde.org/show_bug.cgi?id=434573 --- Comment #5 from Andriy Gapon --- Thank you very much! By the way, the calendar widget seems to have a similar issue. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 434573] built-in calculator widget can extend beyond main window
https://bugs.kde.org/show_bug.cgi?id=434573 --- Comment #3 from Andriy Gapon --- Comment on attachment 136811 --> https://bugs.kde.org/attachment.cgi?id=136811 screenshot when maximized on a left screen In the screenshot when kmymoney is maximized on the left screen we can see that a part of the calculator covers the panel at the bottom and a prt of the calculator is beyond the screenshot because it went over the screen edge to the right screen. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 434573] built-in calculator widget can extend beyond main window
https://bugs.kde.org/show_bug.cgi?id=434573 --- Comment #2 from Andriy Gapon --- Created attachment 136813 --> https://bugs.kde.org/attachment.cgi?id=136813=edit screenshot when maximized on the right screen (no problem) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 434573] built-in calculator widget can extend beyond main window
https://bugs.kde.org/show_bug.cgi?id=434573 --- Comment #1 from Andriy Gapon --- Created attachment 136812 --> https://bugs.kde.org/attachment.cgi?id=136812=edit screenshot of non-maximized window -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 434573] New: built-in calculator widget can extend beyond main window
https://bugs.kde.org/show_bug.cgi?id=434573 Bug ID: 434573 Summary: built-in calculator widget can extend beyond main window Product: kmymoney Version: 5.1.1 Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: a...@uabsd.com Target Milestone: --- Created attachment 136811 --> https://bugs.kde.org/attachment.cgi?id=136811=edit screenshot when maximized on a left screen The built-in calculator widget can extend beyond the main window. That can be inconvenient when kmymoney is maximized on a wrong screen in a multi-monitor configuration. I have a dual monitor setup with the monitors positioned left/right of each other. Attached screenshots show how the calculator is positioned when a main kmymoney window is not maximized, maximized on a left screen and maximized on a right screen. I hope that the screenshots demonstrate the problem. Especially, how a part of the calculator goes to the wrong screen. FreeBSD/KDE Plasma: KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 431492] New: kmymoney crash
https://bugs.kde.org/show_bug.cgi?id=431492 Bug ID: 431492 Summary: kmymoney crash Product: kde Version: unspecified Platform: unspecified OS: FreeBSD Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: a...@uabsd.com Target Milestone: --- Application: kmymoney (5.0.3) (Compiled from sources) Qt Version: 5.12.2 Frameworks Version: 5.59.0 Operating System: FreeBSD 12.0-CURRENT amd64 Distribution (Platform): FreeBSD Ports -- Information about the crash: All of a sudden started happening when trying to enter a particular scheduled transaction. Worked without any issues before. The crash can be reproduced every time. -- Backtrace: Application: KMyMoney (kmymoney), signal: Segmentation fault [KCrash Handler] #8 0x000805384a9f in MyMoneySplit::accountId() const () at /usr/local/lib/libkmm_mymoney.so.5 #9 0x005e2b03 in () #10 0x00515f34 in () #11 0x00510992 in () #12 0x00080a6b5eff in QMetaObject::activate(QObject*, int, int, void**) () at /usr/local/lib/qt5/libQt5Core.so.5 #13 0x0008081703a9 in QAction::activate(QAction::ActionEvent) () at /usr/local/lib/qt5/libQt5Widgets.so.5 #14 0x00080a6af021 in QObject::event(QEvent*) () at /usr/local/lib/qt5/libQt5Core.so.5 #15 0x000808179660 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/local/lib/qt5/libQt5Widgets.so.5 #16 0x00080817ac26 in QApplication::notify(QObject*, QEvent*) () at /usr/local/lib/qt5/libQt5Widgets.so.5 #17 0x00080a682d80 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/local/lib/qt5/libQt5Core.so.5 #18 0x00080a683dd2 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/local/lib/qt5/libQt5Core.so.5 #19 0x00080a6dc3e8 in () at /usr/local/lib/qt5/libQt5Core.so.5 #20 0x0008115d9796 in g_main_context_dispatch () at /usr/local/lib/libglib-2.0.so.0 #21 0x0008115d9b35 in () at /usr/local/lib/libglib-2.0.so.0 #22 0x0008115d9be4 in g_main_context_iteration () at /usr/local/lib/libglib-2.0.so.0 #23 0x00080a6dbdeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/local/lib/qt5/libQt5Core.so.5 #24 0x00080a67e76e in QEventLoop::exec(QFlags) () at /usr/local/lib/qt5/libQt5Core.so.5 #25 0x00080a68343e in QCoreApplication::exec() () at /usr/local/lib/qt5/libQt5Core.so.5 #26 0x00458170 in () #27 0x004560a8 in () #28 0x0045397f in () #29 0x000800a09000 in () #30 0x in () [Inferior 1 (process 64714) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412349] New: kwin crashed after VT switch from another X session
https://bugs.kde.org/show_bug.cgi?id=412349 Bug ID: 412349 Summary: kwin crashed after VT switch from another X session Product: kwin Version: 5.16.2 Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: a...@icyb.net.ua Target Milestone: --- Application: kwin_x11 (5.16.2) Qt Version: 5.12.2 Frameworks Version: 5.59.0 Operating System: FreeBSD 12.0-CURRENT amd64 Distribution (Platform): FreeBSD Ports -- Information about the crash: I switched to my X / KDE session from another session (using Ctrl+Alt+F9). The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #8 0x00080142979b in () at /usr/local/lib/libkwin4_effect_builtins.so.1 #9 0x00080142a30f in () at /usr/local/lib/libkwin4_effect_builtins.so.1 #10 0x00080142a151 in () at /usr/local/lib/libkwin4_effect_builtins.so.1 #11 0x000800dd7428 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/local/lib/libkwin.so.5 #12 0x00080138f6d5 in () at /usr/local/lib/libkwin4_effect_builtins.so.1 #13 0x000800dd7428 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/local/lib/libkwin.so.5 #14 0x000800dca98f in KWin::Scene::finalPaintWindow(KWin::EffectWindowImpl*, int, QRegion, KWin::WindowPaintData&) () at /usr/local/lib/libkwin.so.5 #15 0x000800dd7086 in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/local/lib/libkwin.so.5 #16 0x00080113ee7f in KWin::Effect::paintWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/local/lib/libkwineffects.so.12 #17 0x000800dd7045 in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/local/lib/libkwin.so.5 #18 0x00080113ee7f in KWin::Effect::paintWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/local/lib/libkwineffects.so.12 #19 0x000800dd7045 in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () at /usr/local/lib/libkwin.so.5 #20 0x000800dc9af2 in KWin::Scene::paintWindow(KWin::Scene::Window*, int, QRegion, KWin::WindowQuadList) () at /usr/local/lib/libkwin.so.5 #21 0x000800dc8b6b in KWin::Scene::paintSimpleScreen(int, QRegion) () at /usr/local/lib/libkwin.so.5 #22 0x000825cfab55 in () at /usr/local/lib/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #23 0x000800dc74c0 in KWin::Scene::finalPaintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/local/lib/libkwin.so.5 #24 0x000800dd6e25 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/local/lib/libkwin.so.5 #25 0x00080113edb4 in KWin::Effect::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/local/lib/libkwineffects.so.12 #26 0x000800dd6de7 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/local/lib/libkwin.so.5 #27 0x00080113edb4 in KWin::Effect::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/local/lib/libkwineffects.so.12 #28 0x000800dd6de7 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/local/lib/libkwin.so.5 #29 0x000800dc7225 in KWin::Scene::paintScreen(int*, QRegion const&, QRegion const&, QRegion*, QRegion*, QMatrix4x4 const&, QRect const&) () at /usr/local/lib/libkwin.so.5 #30 0x000825cf9039 in KWin::SceneOpenGL::paint(QRegion, QList) () at /usr/local/lib/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #31 0x000800dc0850 in KWin::Compositor::performCompositing() () at /usr/local/lib/libkwin.so.5 #32 0x00080b4aedd3 in QObject::event(QEvent*) () at /usr/local/lib/qt5/libQt5Core.so.5 #33 0x000809f79660 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/local/lib/qt5/libQt5Widgets.so.5 #34 0x000809f7ac26 in QApplication::notify(QObject*, QEvent*) () at /usr/local/lib/qt5/libQt5Widgets.so.5 #35 0x00080b482d80 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/local/lib/qt5/libQt5Core.so.5 #36 0x00080b4dae2f in QTimerInfoList::activateTimers() () at /usr/local/lib/qt5/libQt5Core.so.5 #37 0x00080b4d9285 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/local/lib/qt5/libQt5Core.so.5 #38 0x00081b8b2ef4 in () at /usr/local/lib/qt5/libQt5XcbQpa.so.5 #39 0x00080b47e76e in QEventLoop::exec(QFlags) () at /usr/local/lib/qt5/libQt5Core.so.5 #40 0x00080b48343e in QCoreApplication::exec() () at /usr/local/lib/qt5/libQt5Core.so.5 #41 0x00080082dbaf in kdemain () at
[kwin] [Bug 412008] New: kwin crashed after VT switch from another X session
https://bugs.kde.org/show_bug.cgi?id=412008 Bug ID: 412008 Summary: kwin crashed after VT switch from another X session Product: kwin Version: 5.16.2 Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: a...@icyb.net.ua Target Milestone: --- Application: kwin_x11 (5.16.2) Qt Version: 5.12.2 Frameworks Version: 5.59.0 Operating System: FreeBSD 12.0-CURRENT amd64 Distribution (Platform): FreeBSD Ports -- Information about the crash: - What I was doing when the application crashed: I switched to my X / KDE session from another session (using Ctrl+Alt+F9). The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #6 0x00080c359b5a in thr_kill () at thr_kill.S:3 #7 0x00080c359b24 in __raise (s=6) at /usr/src/lib/libc/gen/raise.c:52 #8 0x00080c359a99 in abort () at /usr/src/lib/libc/stdlib/abort.c:65 #9 0x00080b2a46e9 in QMessageLogger::fatal(char const*, ...) const () at /usr/local/lib/qt5/libQt5Core.so.5 #10 0x00081eb2f9d9 in () at /usr/local/lib/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so #11 0x00080b4b5eff in QMetaObject::activate(QObject*, int, int, void**) () at /usr/local/lib/qt5/libQt5Core.so.5 #12 0x00080b4be7c4 in QTimer::timerEvent(QTimerEvent*) () at /usr/local/lib/qt5/libQt5Core.so.5 #13 0x00080b4aedd3 in QObject::event(QEvent*) () at /usr/local/lib/qt5/libQt5Core.so.5 #14 0x000809f79660 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/local/lib/qt5/libQt5Widgets.so.5 #15 0x000809f7ac26 in QApplication::notify(QObject*, QEvent*) () at /usr/local/lib/qt5/libQt5Widgets.so.5 #16 0x00080b482d80 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/local/lib/qt5/libQt5Core.so.5 #17 0x00080b4dae2f in QTimerInfoList::activateTimers() () at /usr/local/lib/qt5/libQt5Core.so.5 #18 0x00080b4d9285 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/local/lib/qt5/libQt5Core.so.5 #19 0x00080b47e76e in QEventLoop::exec(QFlags) () at /usr/local/lib/qt5/libQt5Core.so.5 #20 0x00080b2abbb9 in QThread::exec() () at /usr/local/lib/qt5/libQt5Core.so.5 #21 0x00080b2acbb4 in () at /usr/local/lib/qt5/libQt5Core.so.5 #22 0x00080c05bc55 in thread_start (curthread=0x809d78900) at /usr/src/lib/libthr/thread/thr_create.c:289 #23 0x in () Thread 3 (LWP 102936 of process 45924): #1 0x00080c05ee0c in __thr_ppoll (pfd=0x819bf6018, nfds=1, timeout=0x0, newsigmask=0x0) at /usr/src/lib/libthr/thread/thr_syscalls.c:356 #2 0x00080b4d79ff in qt_safe_poll(pollfd*, unsigned int, timespec const*) () at /usr/local/lib/qt5/libQt5Core.so.5 #3 0x00080b4d918a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/local/lib/qt5/libQt5Core.so.5 #4 0x00080b47e76e in QEventLoop::exec(QFlags) () at /usr/local/lib/qt5/libQt5Core.so.5 #5 0x00080b2abbb9 in QThread::exec() () at /usr/local/lib/qt5/libQt5Core.so.5 #6 0x000803157179 in () at /usr/local/lib/qt5/libQt5Qml.so.5 #7 0x00080b2acbb4 in () at /usr/local/lib/qt5/libQt5Core.so.5 #8 0x00080c05bc55 in thread_start (curthread=0x809d3d000) at /usr/src/lib/libthr/thread/thr_create.c:289 #9 0x in () Thread 2 (LWP 102931 of process 45924): #1 0x00080c05ee0c in __thr_ppoll (pfd=0x800b83b18, nfds=1, timeout=0x0, newsigmask=0x0) at /usr/src/lib/libthr/thread/thr_syscalls.c:356 #2 0x00080b4d79ff in qt_safe_poll(pollfd*, unsigned int, timespec const*) () at /usr/local/lib/qt5/libQt5Core.so.5 #3 0x00080b4d918a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/local/lib/qt5/libQt5Core.so.5 #4 0x00080b47e76e in QEventLoop::exec(QFlags) () at /usr/local/lib/qt5/libQt5Core.so.5 #5 0x00080b2abbb9 in QThread::exec() () at /usr/local/lib/qt5/libQt5Core.so.5 #6 0x000808dab243 in () at /usr/local/lib/qt5/libQt5DBus.so.5 #7 0x00080b2acbb4 in () at /usr/local/lib/qt5/libQt5Core.so.5 #8 0x00080c05bc55 in thread_start (curthread=0x800719700) at /usr/src/lib/libthr/thread/thr_create.c:289 #9 0x in () Thread 1 (LWP 101889 of process 45924): #1 0x00080c05e64c in __thr_nanosleep (time_to_sleep=0x7fff9b50, time_remaining=0x7fff9b40) at /usr/src/lib/libthr/thread/thr_syscalls.c:287 #2 0x00080c2e889b in __sleep (seconds=1) at /usr/src/lib/libc/gen/sleep.c:62 #3 0x000809554bfa in () at /usr/local/lib/libKF5Crash.so.5 #4 0x00080955433a in KCrash::defaultCrashHandler(int) () at /usr/local/lib/libKF5Crash.so.5 #5 0x00080c0618c6 in handle_signal (actp=0x7fffd100, sig=11, info=0x7fffd4f0, ucp=0x7fffd180) at /usr/src/lib/libthr/thread/thr_sig.c:246 #6 0x00080c060f0f in thr_sighandler (sig=11,
[plasmashell] [Bug 409610] New: application launcher problem with focus stealing prevention high
https://bugs.kde.org/show_bug.cgi?id=409610 Bug ID: 409610 Summary: application launcher problem with focus stealing prevention high Product: plasmashell Version: 5.16.2 Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: a...@icyb.net.ua CC: plasma-b...@kde.org Target Milestone: 1.0 I set focus stealing prevention to high, so that, for example, when I click a web link in my email client my browser does not take over the focus. I want links to get opened in new tabs in background. But when I enable that setting, the application launcher that I have in a panel (configured as Always Visible = yes, Auto Hide = no, Windows Can Cover = no, Windows Go Below = no) becomes effectively useless. When I click the application launcher there is no application menu unless I minimize or close all windows. In other words, if there is a window in the place where the menu should appear, then the menu is below that window and it gets no focus. I think that the technical problem could be that the application launcher widget and the menu could be considered different applications and, thus, the focus stealing prevention does not allow the menu to grab the focus. But, in my opinion, they are the same "thing" logically and the menu must always be shown when the widget is clicked. This report is probably a duplicate of bug 377914, but that bug argued that the problem is a bug in kwin and that argument went nowhere. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #300 from Andriy Gapon <a...@icyb.net.ua> --- For nvidia users, maybe nvidiaXineramaInfoOrder can help to fix monitor IDs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #299 from Andriy Gapon <a...@icyb.net.ua> --- (In reply to Andriy Gapon from comment #298) Actually, it seems that the problem goes as deep as Qt as Xinerama. Qt (at least Qt 4.x for KDE 4.x) uses Xinerama to query monitor information. Now, compare what Xinerama reports on my system with 2 and 3 monitors: Xinerama screen count: 2 Screen #0 id 0 pos +1280+0 size1920x1080 Screen #1 id 1 pos +0+0 size1280x1024 Xinerama screen count: 3 Screen #0 id 0 pos +1280+0 size1920x1080 Screen #1 id 1 pos +3200+0 size1920x1080 Screen #2 id 2 pos +0+0 size1280x1024 See how monitor with 1280x1024 resolution got its ID switched from 1 to 2. And new monitor (the rightmost, at +3200+0) took 1. I am not sure how Xinerama works internally, if it assigns the IDs on a whim or if they come from graphics drivers. Maybe Qt should use XRandR instead of Xinerama for querying the monitor configuration. XRandR provides much richer information. In any case, I am not sure if KDE, being Qt based, can do much here. Well, I guess it could stop using QDesktopWidget or whatever Q-thing it uses and do its own thing, but that would be too radical. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Andriy Gapon <a...@icyb.net.ua> changed: What|Removed |Added CC||a...@icyb.net.ua --- Comment #298 from Andriy Gapon <a...@icyb.net.ua> --- My very wild guess is that the problem is caused by KDE using simple numbers in its "Containments" configuration. For example: [Containments][86] screen=1 But how KDE assigns those numbers could be unstable. It's possible that when a new monitor is added existing monitors get different numbers. And so, things get shuffled on the screen. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 386462] Yahoo Quote Updates quit working
https://bugs.kde.org/show_bug.cgi?id=386462 Andriy Gapon <a...@icyb.net.ua> changed: What|Removed |Added CC||a...@icyb.net.ua -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 386543] Provide ability to select online quote source for currency conversion
https://bugs.kde.org/show_bug.cgi?id=386543 Andriy Gapon <a...@icyb.net.ua> changed: What|Removed |Added CC||a...@icyb.net.ua --- Comment #1 from Andriy Gapon <a...@icyb.net.ua> --- This is important now that Yahoo stopped providing the hardcoded service. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 386436] choqok finds emojis where there are none
https://bugs.kde.org/show_bug.cgi?id=386436 --- Comment #2 from Andriy Gapon <a...@icyb.net.ua> --- (In reply to Andrea Scarpino from comment #1) > I know all url parsers need some rework, however could you please tell me > which microblog are you using? Andrea, this is with twitter. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 386436] New: choqok finds emojis where there are none
https://bugs.kde.org/show_bug.cgi?id=386436 Bug ID: 386436 Summary: choqok finds emojis where there are none Product: choqok Version: 1.6 Platform: Other OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mehrdad.mom...@gmail.com Reporter: a...@icyb.net.ua CC: scarp...@kde.org Target Milestone: --- Created attachment 108668 --> https://bugs.kde.org/attachment.cgi?id=108668=edit misdetected emoji Look at how choqok rendered "CONFIRMED: " in the attachment. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 323227] Changing the cursor using the terminal escape sequence clears the profile name
https://bugs.kde.org/show_bug.cgi?id=323227 Andriy Gapon <a...@icyb.net.ua> changed: What|Removed |Added CC||a...@icyb.net.ua --- Comment #5 from Andriy Gapon <a...@icyb.net.ua> --- Please see bug 347323 as well. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 347323] Add support for changing cursor shape with extended DECSCUSR escape sequences
https://bugs.kde.org/show_bug.cgi?id=347323 Andriy Gapon <a...@icyb.net.ua> changed: What|Removed |Added CC||a...@icyb.net.ua -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 326192] Choqok is intermittently extremely (unusably) slow, apparently due to size of archive
https://bugs.kde.org/show_bug.cgi?id=326192 --- Comment #9 from Andriy Gapon <a...@icyb.net.ua> --- The problem seems to be specifically caused by Twitter_Home_backuprc which full of deleted keys. If I correctly interpret what "[$d]" means. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 326192] Choqok is intermittently extremely (unusably) slow, apparently due to size of archive
https://bugs.kde.org/show_bug.cgi?id=326192 Andriy Gapon <a...@icyb.net.ua> changed: What|Removed |Added CC||a...@icyb.net.ua --- Comment #8 from Andriy Gapon <a...@icyb.net.ua> --- Seeing seemingly the same problem with 1.6. 0x8069189c7 QMapNodeBase::nextNode(void) const+0x17 0x806523188 KConfig::groupList(void) const+0x798 0x806527099 KConfig::deleteGroupImpl(QByteArray const&, QFlags)+0x39 0x80652a674 KConfigBase::deleteGroup(QString const&, QFlags)+0x34 0x8248705c1 TwitterApiMicroBlog::saveTimeline(Choqok::Account*, QString const&, QList<TwitterApiMicroBlog::saveTimeline::UI::PostWidget*> const&)+0x181 0x800a97b8f Choqok::UI::TimelineWidget::saveTimeline(void)+0x7f 0x806a902ab QMetaObject::activate(QObject*, int, int, void**)+0xbcb 0x806a902ab QMetaObject::activate(QObject*, int, int, void**)+0xbcb 0x806a88be6 QObject::event(QEvent*)+0x66 0x80536ff33 QApplicationPrivate::notify_helper(QObject*, QEvent*)+0x133 0x80537125c QApplication::notify(QObject*, QEvent*)+0x16c 0x806a60bd4 QCoreApplication::notifyInternal2(QObject*, QEvent*)+0x94 0x806aaf02a QTimerInfoList::activateTimers(void)+0x37a 0x806ab046d QEventDispatcherGlib::QEventDispatcherGlib(QEventDispatcherGlibPrivate&, QObject*)+0x42d 0x80d53b243 g_main_dispatch+0x1a3 0x80d53b090 g_main_context_dispatch+0x30 0x80d53b5de g_main_context_iterate+0x1be 0x80d53b653 g_main_context_iteration+0x53 0x806aafc58 QEventDispatcherGlib::processEvents(QFlags)+0x68 0x806a5cee0 QEventLoop::exec(QFlags)+0x190 0x806a61241 QCoreApplication::exec(void)+0x141 -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 377246] New: count of new messages is shown incorrectly sometimes
https://bugs.kde.org/show_bug.cgi?id=377246 Bug ID: 377246 Summary: count of new messages is shown incorrectly sometimes Product: choqok Version: unspecified Platform: Other OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mehrdad.mom...@gmail.com Reporter: a...@icyb.net.ua CC: scarp...@kde.org Target Milestone: --- Created attachment 104380 --> https://bugs.kde.org/attachment.cgi?id=104380=edit the screenshot The count of new messages is shown incorrectly sometimes in the folder panel. It would have a stale leading digit (typically "1"). Please see the attached screenshot. The correct count is three as shown in the title bar. -- You are receiving this mail because: You are watching all bug changes.