[kwin] [Bug 450301] On KWin 5.24 X11 Nvidia, when reenabling compositing, windows begin flickering and flipping upside-down
https://bugs.kde.org/show_bug.cgi?id=450301 --- Comment #9 from Kott --- I think it's worth to mention that my Qt engine is Kvantum. I switch back to the Breeze and see no upside-down flipping for a while. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450301] On KWin 5.24 X11 Nvidia, when reenabling compositing, windows begin flickering and flipping upside-down
https://bugs.kde.org/show_bug.cgi?id=450301 Kott changed: What|Removed |Added CC||k...@kott.no-ip.biz --- Comment #7 from Kott --- Got the same with my config. Mostly when the mpv is playing. Kernel: 5.19.8-1-default arch: x86_64 bits: 64 Desktop: KDE Plasma v: 5.25.5 Distro: openSUSE Tumbleweed 20220915 Device-1: NVIDIA TU117 [GeForce GTX 1650] driver: nvidia v: 515.65.01 Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.3 driver: X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa failed: nv gpu: nvidia,nvidia-nvswitch resolution: 2560x1080~60Hz OpenGL: renderer: NVIDIA GeForce GTX 1650/PCIe/SSE2 v: 4.6.0 NVIDIA 515.65.01 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 439509] New: Konversation crash on autostart with Plasma.
https://bugs.kde.org/show_bug.cgi?id=439509 Bug ID: 439509 Summary: Konversation crash on autostart with Plasma. Product: konversation Version: 1.8.21042 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: k...@kott.no-ip.biz Target Milestone: --- Application: konversation (1.8.21042) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.12.13-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.22.2 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Login in KDE with SDDM, using Latte-Dock as panel. Konversation is autostarted. After connecting to the servers (rc.libera.chat) Konversation crashed. The crash can be reproduced every time. -- Backtrace: Application: Konversation (konversation), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f25e155e880 (LWP 2177))] [KCrash Handler] #6 0x7f25e3fb7f66 in operator== (s1=..., s2=...) at text/qstring.cpp:3432 #7 0x55de5edf78e9 in NickInfo::setAccount (this=0x0, name=...) at /usr/src/debug/konversation-21.04.2-2.1.x86_64/src/irc/nickinfo.cpp:250 #8 0x55de5ee04564 in InputFilter::parseClientCommand (this=0x55de613d2380, prefix=..., command=..., parameterList=..., messageTags=...) at /usr/include/qt5/QtCore/qshareddata.h:160 #9 0x55de5edbdd06 in InputFilter::parseLine (line=..., this=0x55de613d2380) at /usr/src/debug/konversation-21.04.2-2.1.x86_64/src/irc/inputfilter.cpp:123 #10 Server::processIncomingData (this=0x7ffd202a2c00) at /usr/src/debug/konversation-21.04.2-2.1.x86_64/src/irc/server.cpp:1366 #11 0x7f25e414ffb3 in QtPrivate::QSlotObjectBase::call (a=0x7ffd202a2e10, r=0x55de613d2260, this=0x55de6169bbd0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate (sender=0x55de613d22d0, signal_index=3, argv=0x7ffd202a2e10) at kernel/qobject.cpp:3886 #13 0x7f25e414947f in QMetaObject::activate (sender=, m=m@entry=0x7f25e43e9be0, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd202a2e10) at kernel/qobject.cpp:3946 #14 0x7f25e4153e6a in QTimer::timeout (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #15 0x7f25e4145e7f in QObject::event (this=0x55de613d22d0, e=0x7ffd202a2f90) at kernel/qobject.cpp:1336 #16 0x7f25e4cc2a7f in QApplicationPrivate::notify_helper (this=, receiver=0x55de613d22d0, e=0x7ffd202a2f90) at kernel/qapplication.cpp:3632 #17 0x7f25e411996a in QCoreApplication::notifyInternal2 (receiver=0x55de613d22d0, event=0x7ffd202a2f90) at kernel/qcoreapplication.cpp:1064 #18 0x7f25e41701eb in QTimerInfoList::activateTimers (this=0x55de6108d2b0) at kernel/qtimerinfo_unix.cpp:643 #19 0x7f25e4170acc in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:183 #20 idleTimerSourceDispatch (source=source@entry=0x55de6108e940) at kernel/qeventdispatcher_glib.cpp:230 #21 0x7f25e1ff080f in g_main_dispatch (context=0x7f25d8005000) at ../glib/gmain.c:3337 #22 g_main_context_dispatch (context=0x7f25d8005000) at ../glib/gmain.c:4055 #23 0x7f25e1ff0b98 in g_main_context_iterate (context=context@entry=0x7f25d8005000, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #24 0x7f25e1ff0c4f in g_main_context_iteration (context=0x7f25d8005000, may_block=1) at ../glib/gmain.c:4196 #25 0x7f25e4170e54 in QEventDispatcherGlib::processEvents (this=0x55de61091840, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #26 0x7f25e411836b in QEventLoop::exec (this=this@entry=0x7ffd202a31d0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #27 0x7f25e4120650 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #28 0x7f25e45641dc in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867 #29 0x7f25e4cc29f5 in QApplication::exec () at kernel/qapplication.cpp:2824 #30 0x55de5ed3ed66 in main (argc=, argv=0x7ffd202a32f0) at /usr/src/debug/konversation-21.04.2-2.1.x86_64/src/main.cpp:149 [Inferior 1 (process 2177) detached] Possible duplicates by query: bug 422092, bug 419229, bug 416379, bug 410586, bug 353672. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 415231] When code indexing is disabled, Kate's Project plugin has misleading error (points to kateproject, not config dialog)
https://bugs.kde.org/show_bug.cgi?id=415231 Kott changed: What|Removed |Added CC||k...@kott.no-ip.biz Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #4 from Kott --- Hi, Bug is still present. Kate Version 20.12.3 KDE Frameworks 5.80.0 Qt 5.15.2 (built against 5.15.2) The xcb windowing system openSUSE TW 20210319 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358930] moving the mouse over a different application icon immediately changes the window list
https://bugs.kde.org/show_bug.cgi?id=358930 --- Comment #26 from Kott --- (In reply to Nate Graham from comment #24) > Number of duplicates piling up; raising priority. Is it so hard to fix? I have to use latte-dock 9.11 which has the proper behavior, but it's more CPU hungry. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 431289] KDevelop crashes when creating Project from existing sources.
https://bugs.kde.org/show_bug.cgi?id=431289 --- Comment #2 from Kott --- Looks like it's not reproduces anymore. I'll check for a while and let You know. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 431289] New: KDevelop crashes when creating Project from existing sources.
https://bugs.kde.org/show_bug.cgi?id=431289 Bug ID: 431289 Summary: KDevelop crashes when creating Project from existing sources. Product: kdevelop Version: 5.6.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: k...@kott.no-ip.biz Target Milestone: --- Application: kdevelop (5.6.1) Qt Version: 5.15.2 Frameworks Version: 5.77.0 Operating System: Linux 5.10.4-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Make some code with Main.cpp includes/Header.h and Makefile Run KDevelop Open Main.cpp It looks for missed Header.h, select Solution 1 - Open Project Select Makefile, Create Project KDevelop crashes The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::operator++() (this=0x65007200620065) at /usr/include/c++/10/bits/atomic_base.h:325 #5 QAtomicOps::ref(std::atomic&) (_q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:283 #6 QBasicAtomicInteger::ref() (this=0x65007200620065) at /usr/include/qt5/QtCore/qbasicatomic.h:118 #7 QExplicitlySharedDataPointer::QExplicitlySharedDataPointer(QExplicitlySharedDataPointer const&) (o=..., this=0x7ffcaba5d2b0, this=, o=) at /usr/include/qt5/QtCore/qshareddata.h:187 #8 KDevelop::DUChainPointer::DUChainPointer(KDevelop::DUChainPointer const&) (rhs=..., this=0x7ffcaba5d2b0) at /usr/src/debug/kdevelop5-5.6.1-1.1.x86_64/kdevplatform/language/duchain/navigation/../duchainpointer.h:101 #9 KDevelop::AbstractNavigationContext::topContext() const (this=0x557d296176d0) at /usr/src/debug/kdevelop5-5.6.1-1.1.x86_64/kdevplatform/language/duchain/navigation/abstractnavigationcontext.cpp:73 #10 0x7fe4a0e6e5ed in KDevelop::ProblemNavigationContext::executeAction(int) (this=0x557d296176d0, index=) at /usr/src/debug/kdevelop5-5.6.1-1.1.x86_64/kdevplatform/language/duchain/navigation/problemnavigationcontext.cpp:259 #11 0x7fe4a0e6e801 in KDevelop::ProblemNavigationContext::executeKeyAction(QString const&) (this=0x557d296176d0, key=...) at /usr/src/debug/kdevelop5-5.6.1-1.1.x86_64/kdevplatform/language/duchain/navigation/problemnavigationcontext.cpp:243 #12 0x7fe4a0e793fc in KDevelop::AbstractNavigationContext::execute(KDevelop::NavigationAction const&) (this=this@entry=0x557d296176d0, action=...) at /usr/src/debug/kdevelop5-5.6.1-1.1.x86_64/kdevplatform/language/duchain/navigation/abstractnavigationcontext.cpp:183 #13 0x7fe4a0e7a45a in KDevelop::AbstractNavigationContext::acceptLink(QString const&) (this=this@entry=0x557d296176d0, link=...) at /usr/src/debug/kdevelop5-5.6.1-1.1.x86_64/kdevplatform/language/duchain/navigation/abstractnavigationcontext.cpp:487 #14 0x7fe4a0e7a5a1 in KDevelop::AbstractNavigationWidgetPrivate::anchorClicked(QUrl const&) (url=..., this=0x557d29609d50) at /usr/src/debug/kdevelop5-5.6.1-1.1.x86_64/kdevplatform/language/duchain/navigation/abstractnavigationwidget.cpp:285 #15 operator() (url=..., __closure=) at /usr/src/debug/kdevelop5-5.6.1-1.1.x86_64/kdevplatform/language/duchain/navigation/abstractnavigationwidget.cpp:121 #16 QtPrivate::FunctorCall, QtPrivate::List, void, KDevelop::AbstractNavigationWidget::initBrowser(int):: >::call (arg=, f=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #17 QtPrivate::Functor, 1>::call, void> (arg=, f=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #18 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl (which=, r=, ret=, a=, this_=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #19 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:436 #20 0x7fe4a240d8c6 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffcaba5d5e0, r=0x557d292af4f0, this=0x557d2a031ed0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #21 doActivate(QObject*, int, void**) (sender=0x557d29243930, signal_index=20, argv=argv@entry=0x7ffcaba5d5e0) at kernel/qobject.cpp:3886 #22 0x7fe4a2406c20 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x557d29243930, m=m@entry=0x7fe4a36765a0 , local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x7ffcaba5d5e0) at kernel/qobject.cpp:3946 #23 0x7fe4ab75 in QTextBrowser::anchorClicked(QUrl const&) (this=this@entry=0x557d29243930, _t1=...) at .moc/moc_qtextbrowser.cpp:347 #24 0x7fe4a3336ccb in QTextBrowserPrivate::_q_activateAnchor(QString const&) (this=0x557d29729020, href=...) at widgets/qtextbrowser.cpp:239 #25 0x7fe4a240d900
[Discover] [Bug 420259] Removing a Flatpak source crashes Discover.
https://bugs.kde.org/show_bug.cgi?id=420259 Kott changed: What|Removed |Added CC||k...@kott.no-ip.biz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #276 from Kott --- another 3d party solution: https://store.kde.org/p/1197828/ https://github.com/lehklu/Vallpaper -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389987] New: Please add delay to window preview when touching nearest icon in taskbar.
https://bugs.kde.org/show_bug.cgi?id=389987 Bug ID: 389987 Summary: Please add delay to window preview when touching nearest icon in taskbar. Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons-only Task Manager Assignee: h...@kde.org Reporter: k...@kott.no-ip.biz CC: plasma-b...@kde.org Target Milestone: 1.0 Hi. 1. Two or more application windows are grouped into one icon in taskbar. 2. When you hover over this icon - a series of thumbnails of the grouped windows appears. 3. If you move the cursor diagonally to window thumbnail, and even slightly (literally a pixel) touches the neighboring task-icon of another application , then the thumbnails of another application will pop out. So I have to move the cursor like chess knight (up then side) to select apps window from previews. This is not the same https://bugs.kde.org/show_bug.cgi?id=375671 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 389402] New: Drag'n'drop from apps-tab into devices-tab doesn't work
https://bugs.kde.org/show_bug.cgi?id=389402 Bug ID: 389402 Summary: Drag'n'drop from apps-tab into devices-tab doesn't work Product: plasma-pa Version: 5.11.95 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: k...@kott.no-ip.biz CC: plasma-b...@kde.org Target Milestone: --- Created attachment 110110 --> https://bugs.kde.org/attachment.cgi?id=110110=edit screenshot of plasma-pa dragging FF in devices tab With recent 5.11.95 update it's impossible to change output by dragging app's icon into devices tab. The target - devices-tab doesn't activates and apps-tab stills in front. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 389254] New: Display going to a wrong resolution
https://bugs.kde.org/show_bug.cgi?id=389254 Bug ID: 389254 Summary: Display going to a wrong resolution Product: kde Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jean.k...@free.fr Target Milestone: --- My computer is a Packard Bell AllInOne. Very often, the display on the screen is very unstable, trembling and wavering. The since the last session I started my machine, the window size is now greater than the screen size and I have to move the mouse to access the whole window. I've don't found the right command to fix it. Thanks for help -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 381173] Wrong countdown speed in timer plasmoid's window.
https://bugs.kde.org/show_bug.cgi?id=381173 Kott <k...@kott.no-ip.biz> changed: What|Removed |Added Summary|Wrong countdown speed in|Wrong countdown speed in |timer plasmoid. |timer plasmoid's window. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 381173] New: Wrong countdown speed in timer plasmoid.
https://bugs.kde.org/show_bug.cgi?id=381173 Bug ID: 381173 Summary: Wrong countdown speed in timer plasmoid. Product: kdeplasma-addons Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: timer Assignee: plasma-b...@kde.org Reporter: k...@kott.no-ip.biz Target Milestone: --- Steps: 1. Add the timer widget (desktop or panel). 2. Assign hotkey to the widget. 3. Select desired time. 4. Press hotkey, big window with digits appears. Result: Timer counting down at double speed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361985] Plasmashell crashes when MPRIS dbus app stops
https://bugs.kde.org/show_bug.cgi?id=361985 Kott <k...@kott.no-ip.biz> changed: What|Removed |Added CC||k...@kott.no-ip.biz --- Comment #7 from Kott <k...@kott.no-ip.biz> --- (In reply to Mike from comment #4) > Sort of. It's a proxy app that wraps the web service from JRiver > MediaCenter into a MPRIS "player" so that you can control JRiver MC with any > MPRIS applet. In addition, it provides an alternative GUI to simultaneously > manage playback on multiple JRiver MC servers on your net. Each JRiver > server can provide any number of playback zones (roughly related to > sound/video output devices), so it can get complex and MPRIS using the dbus > object-path per process creates a bit of a problem. > > It currently only works if JRiver is running somewhere on your net. Wow. Could you share your app? I'm (and not only one) looking for such tool. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus
https://bugs.kde.org/show_bug.cgi?id=363753 --- Comment #16 from Kott <k...@kott.no-ip.biz> --- > (The "bug" was added**). It's not a qtcurve bug, it's a QtDBus one and > should be fixed there. It just happens that in some configuration the QtDBus > is unloaded before QtCurve and after in other cases. The commit should only > be reverted if Well, "bug", my apologies:) What patches (Debian, Thiago's) are you talking about? And what version of Qt do use? thnx -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus
https://bugs.kde.org/show_bug.cgi?id=363753 --- Comment #11 from Kott <k...@kott.no-ip.biz> --- I think, the bug "added" in commit 3d8622c https://quickgit.kde.org/?p=qtcurve.git=commitdiff=3d8622c419a32033e36e940e8cb09b591ad93e29 Maybe it's not only cause. But version compiled before this commit - works without crash. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 363703] Popup Menu shadows not configurable
https://bugs.kde.org/show_bug.cgi?id=363703 Kott <k...@kott.no-ip.biz> changed: What|Removed |Added CC||k...@kott.no-ip.biz -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus
https://bugs.kde.org/show_bug.cgi?id=363753 Kott <k...@kott.no-ip.biz> changed: What|Removed |Added CC||k...@kott.no-ip.biz --- Comment #7 from Kott <k...@kott.no-ip.biz> --- I've just updated Qt 5.6.1 and crashes still presents. Application: kactivitymanagerd (kactivitymanagerd), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff44c8ec8c0 (LWP 30505))] Thread 2 (Thread 0x7ff43f9e1700 (LWP 30510)): #0 0x7ff44a109a1d in poll () at /lib64/libc.so.6 #1 0x7ff4498b7410 in () at /usr/lib64/libxcb.so.1 #2 0x7ff4498b91a9 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7ff4425c6579 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7ff44a80d2d8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7ff448cf1474 in start_thread () at /lib64/libpthread.so.0 #6 0x7ff44a1123ed in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7ff44c8ec8c0 (LWP 30505)): [KCrash Handler] #6 0x7ff44a804ff4 in QMutex::lock() () at /usr/lib64/libQt5Core.so.5 #7 0x7ff44b349c27 in () at /usr/lib64/libQt5DBus.so.5 #8 0x7ff44b34acec in QDBusConnection::sessionBus() () at /usr/lib64/libQt5DBus.so.5 #9 0x7ff432e96c4d in QtCurve::Style::disconnectDBus() () at /usr/lib64/qt5/plugins/styles/qtcurve.so #10 0x7ff432ed2e26 in QtCurve::StylePlugin::~StylePlugin() () at /usr/lib64/qt5/plugins/styles/qtcurve.so #11 0x7ff432ed2e59 in QtCurve::StylePlugin::~StylePlugin() () at /usr/lib64/qt5/plugins/styles/qtcurve.so #12 0x7ff44a9d98a9 in () at /usr/lib64/libQt5Core.so.5 #13 0x7ff44a9cf4f2 in () at /usr/lib64/libQt5Core.so.5 #14 0x7ff44a9cf629 in () at /usr/lib64/libQt5Core.so.5 #15 0x7ff44aa19927 in QObject::~QObject() () at /usr/lib64/libQt5Core.so.5 #16 0x7ff44a9ce6be in QFactoryLoader::~QFactoryLoader() () at /usr/lib64/libQt5Core.so.5 #17 0x7ff44b7944c9 in () at /usr/lib64/libQt5Widgets.so.5 #18 0x7ff44a061278 in __run_exit_handlers () at /lib64/libc.so.6 #19 0x7ff44a0612c5 in () at /lib64/libc.so.6 #20 0x00413fd9 in () #21 0x7ff44aa1224c in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #22 0x7ff44b3a2642 in QDBusServiceWatcher::serviceRegistered(QString const&) () at /usr/lib64/libQt5DBus.so.5 #23 0x7ff44b3a2dcf in () at /usr/lib64/libQt5DBus.so.5 #24 0x7ff44b3a31a0 in QDBusServiceWatcher::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib64/libQt5DBus.so.5 #25 0x7ff44b355028 in () at /usr/lib64/libQt5DBus.so.5 #26 0x7ff44aa12cf9 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #27 0x7ff44b725aec in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #28 0x7ff44b72af8f in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #29 0x7ff44a9e4a20 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #30 0x7ff44a9e699c in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #31 0x7ff44aa3a6c3 in () at /usr/lib64/libQt5Core.so.5 #32 0x7ff4487c6e57 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #33 0x7ff4487c70c0 in () at /usr/lib64/libglib-2.0.so.0 #34 0x7ff4487c716c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #35 0x7ff44aa3aacf in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #36 0x7ff44a9e276a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #37 0x7ff44a9eaf6c in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #38 0x00411b2b in main () -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360173] Plasma freeze sometime with notification & high load CPU and RAM
https://bugs.kde.org/show_bug.cgi?id=360173 --- Comment #12 from Kott <k...@kott.no-ip.biz> --- >>I also get every second the following error message in the journald log: >>>>plasma.engine.mpris2: Enabling stop action Do you have plasmoid PlayBar2 installed? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363488] plasmashell freezes unpredictable
https://bugs.kde.org/show_bug.cgi?id=363488 --- Comment #4 from Kott <k...@kott.no-ip.biz> --- >>Can you confirm it works correctly with Qt 5.6.1? Not with 5.6.1 But 5.6.0 in main distr repo has this patch: https://build.opensuse.org/package/view_file/openSUSE:Factory/libqt5-qtbase/Fix-QtDBus-deadlock-inside-kded-kiod.patch?expand=1 I'm not sure when this patched version came in my install, but freezes with heavy load seems gone. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363488] plasmashell freezes unpredictable
https://bugs.kde.org/show_bug.cgi?id=363488 --- Comment #2 from Kott <k...@kott.no-ip.biz> --- Hm, guess I found some relation. It freeze during heavy disk/cpu load, eg make -j8 I caught freezes when compiled clementine and qbs, both times. Maybe duplicates https://bugs.kde.org/show_bug.cgi?id=351897 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363488] plasmashell freezes unpredictable
https://bugs.kde.org/show_bug.cgi?id=363488 --- Comment #1 from Kott <k...@kott.no-ip.biz> --- Well. I tried to clean ~/.cache. I tried to run fresh clean profile. It freezes. What should I do else? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363488] New: plasmashell freezes unpredictable
https://bugs.kde.org/show_bug.cgi?id=363488 Bug ID: 363488 Summary: plasmashell freezes unpredictable Product: plasmashell Version: 5.6.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: k...@kott.no-ip.biz CC: bhus...@gmail.com, plasma-b...@kde.org I've changed my distro from OS 13.2 with Qt 5.6 and plasma-workspace 5.6.0 (from repos) to OS Tumbleweed mostly due often freezes in plasmashell. When there (on Tumblewwed) was Qt 5.5.x and even plasma 5.6.x there weren't any freezes. Now it has Qt 5.6 and plasma 5.6.4, freezes came back... I cannot realize the reasons or any what cause them, it simple freeze occasional in random time without any user action. Reproducible: Sometimes Steps to Reproduce: 1. Run plasma5-workspace. 2. Do something, or do nothing, just wait. Actual Results: 3. Plasma panel and desktop stops responding to mouse clicks. Expected Results: plasmashell should work NAME=openSUSE VERSION="Tumbleweed" VERSION_ID="20160520" PRETTY_NAME="openSUSE Tumbleweed (20160520) (x86_64)" Linux Kot 4.5.4-1-default #1 SMP PREEMPT Wed May 11 15:23:21 UTC 2016 (db90c25) x86_64 x86_64 x86_64 GNU/Linux NVIDIA Driver Version: 364.19 Name: libQt5Core5 Version : 5.6.0 Name: plasma5-workspace Version : 5.6.4 gdb trace: http://pastebin.com/kmuTyNeP -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 362907] kwin_x11 crashes in QtCurve::Style::disconnectDBus()
https://bugs.kde.org/show_bug.cgi?id=362907 Kott <k...@kott.no-ip.biz> changed: What|Removed |Added CC||k...@kott.no-ip.biz --- Comment #3 from Kott <k...@kott.no-ip.biz> --- I confirm next crashes: korgac, kactivitymanagerd - at startup dolphin - at logoff ktorrent5 - starting with argument (actually, didn't kill app, but crash-reports started) pasmashell - occasional Qt 5.6.0 OpenSuse Tumbleweed -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 361459] New: empty ktp-text-ui crashes
https://bugs.kde.org/show_bug.cgi?id=361459 Bug ID: 361459 Summary: empty ktp-text-ui crashes Product: telepathy Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: text-ui Assignee: kde-telepathy-b...@kde.org Reporter: k...@kott.no-ip.biz Application: ktp-text-ui (15.12.3) Qt Version: 5.6.0 Frameworks Version: 5.20.0 Operating System: Linux 3.16.7-35-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: Chat windows contains not text fields at all, only toolbar and menu. The next error displays in notification: "org.freedesktop.Telepathy.Error.NotAvailable: Handler no longer available" After clicking "history" it crashes. The crash can be reproduced every time. -- Backtrace: Application: Окно разговора (ktp-text-ui), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f87730a57c0 (LWP 29785))] Thread 2 (Thread 0x7f8758e37700 (LWP 29786)): #0 0x7f876d540cad in read () at /lib64/libc.so.6 #1 0x7f875e7e2073 in () at /usr/lib64/tls/libnvidia-tls.so.361.28 #2 0x7f8764e0c750 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8764dcb714 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8764dcbb7b in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f8764dcbcec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7f876dff041c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f876df9e16b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7f876ddd9caa in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7f876f41f095 in () at /usr/lib64/libQt5DBus.so.5 #10 0x7f876ddde749 in () at /usr/lib64/libQt5Core.so.5 #11 0x7f87655380a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7f876d54d00d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f87730a57c0 (LWP 29785)): [KCrash Handler] #5 0x7f8772ca9c60 in ChatWidget::account() const () at /usr/lib64/libktpchat.so #6 0x00429bf3 in ChatWindow::onOpenLogTriggered() () #7 0x004332ba in () #8 0x7f876dfc9cf1 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #9 0x7f876ecf3242 in QAction::triggered(bool) () at /usr/lib64/libQt5Widgets.so.5 #10 0x7f876ecf5ddd in QAction::activate(QAction::ActionEvent) () at /usr/lib64/libQt5Widgets.so.5 #11 0x7f876ee69c22 in () at /usr/lib64/libQt5Widgets.so.5 #12 0x7f876ee6ed50 in () at /usr/lib64/libQt5Widgets.so.5 #13 0x7f876ee7284b in QMenu::mouseReleaseEvent(QMouseEvent*) () at /usr/lib64/libQt5Widgets.so.5 #14 0x7f876ed3d53a in QWidget::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #15 0x7f876ee7318b in QMenu::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #16 0x7f876ecfc68c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #17 0x7f876ed014ff in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #18 0x7f876dfa0125 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #19 0x7f876ed00020 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at /usr/lib64/libQt5Widgets.so.5 #20 0x7f876ed55615 in () at /usr/lib64/libQt5Widgets.so.5 #21 0x7f876ed57922 in () at /usr/lib64/libQt5Widgets.so.5 #22 0x7f876ecfc68c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #23 0x7f876ed00aa2 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #24 0x7f876dfa0125 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #25 0x7f876e4f721b in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib64/libQt5Gui.so.5 #26 0x7f876e4f89b5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib64/libQt5Gui.so.5 #27 0x7f876e4da58b in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib64/libQt5Gui.so.5 #28 0x7f8758123e20 in () at /usr/lib64/libQt5XcbQpa.so.5 #29 0x7f8764dcba04 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #30 0x7f8764dcbc48 in () at /usr/lib64/libglib-2.0.so.0 #31 0x7f8764dcbcec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #32 0x7f876dff041c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #33 0x7f876df9e16b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #34 0x7f876dfa6076 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #35
[plasmashell] [Bug 361250] Plasma randomly freezes and eventually crashes and restarts
https://bugs.kde.org/show_bug.cgi?id=361250 Kott <k...@kott.no-ip.biz> changed: What|Removed |Added CC||k...@kott.no-ip.biz --- Comment #1 from Kott <k...@kott.no-ip.biz> --- The same, but crashes are very rare. And I don't know how to investigate this. I've tried to clean .cache https://forum.kde.org/viewtopic.php?f=289=124690=328672=plasmashell+freeze#p328672 I've tried to change plasma theme, thought there is bug in them https://bugs.kde.org/show_bug.cgi?id=360173 I've tried empty ~/ dir (I don't want to reinstall my system) I used minimal set of plasmoids: start menu, pager, icon-tasks, tray, clock. No luck. Yes I can connect to plasmashell via gdb or dbus, but for what? These freezes are Very annoying, much more than any other issues. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360173] Plasma freeze sometime with notification & high load CPU and RAM
https://bugs.kde.org/show_bug.cgi?id=360173 Kott <k...@kott.no-ip.biz> changed: What|Removed |Added CC||k...@kott.no-ip.biz --- Comment #10 from Kott <k...@kott.no-ip.biz> --- I still get freezes with Papirus plasma-theme. I use -git version, so sometimes (between pulls) all works normally, other times - freezes are very often. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 360050] Unable to type first symbol in upper-case.
https://bugs.kde.org/show_bug.cgi?id=360050 --- Comment #1 from Kott <k...@kott.no-ip.biz> --- The same result with screen keyboard, such as xvkbd. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 360050] Unable to type first symbol in upper-case.
https://bugs.kde.org/show_bug.cgi?id=360050 Kott <k...@kott.no-ip.biz> changed: What|Removed |Added Summary|First typed letter cannot |Unable to type first symbol |be capital |in upper-case. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 360050] New: First typed letter cannot be capital
https://bugs.kde.org/show_bug.cgi?id=360050 Bug ID: 360050 Summary: First typed letter cannot be capital Product: krunner Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@vhanda.in Reporter: k...@kott.no-ip.biz It's simple impossible to type first letter in capital in krunner window. Not with l-shift, r-shift or even caps-lock. Though paste-in works. Reproducible: Always Steps to Reproduce: 1. Open krunner (Alt-F2) 2. Start to type with shift pressed or caps-lock turned on. Actual Results: First letter will be lowercase. Expected Results: First letter should respect input case (shift, caps-lock) -- You are receiving this mail because: You are watching all bug changes.
