[kate] [Bug 474285] New: Kate crashes on SQL reconnect
https://bugs.kde.org/show_bug.cgi?id=474285 Bug ID: 474285 Summary: Kate crashes on SQL reconnect Classification: Applications Product: kate Version: 22.12.3 Platform: Debian unstable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: vas...@zoho.eu Target Milestone: --- Application: kate (22.12.3) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 6.4.0-3-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux trixie/sid DrKonqi: 5.27.7 [KCrashBackend] -- Information about the crash: Sometimes when I hit the reconnect button to renew my database connection the plugin crashes and it takes Kate with it. It does not happen everytime. I will test one or two things I have in my mind but for the bug to manifest the connection must have been expired. This rate limits my testing at one test per day. The crash can be reproduced sometimes. -- Backtrace: Application: Kate (kate), signal: Segmentation fault [KCrash Handler] #4 0x7f13b49b08ea in QSqlQuery::clear() () from /lib/x86_64-linux-gnu/libQt5Sql.so.5 #5 0x7f13b49c2c88 in QSqlQueryModel::clear() () from /lib/x86_64-linux-gnu/libQt5Sql.so.5 #6 0x7f13b4c9fd01 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katesqlplugin.so #7 0x7f13b4ca1a67 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katesqlplugin.so #8 0x7f13ccafba32 in QtPrivate::QSlotObjectBase::call (a=0x7ffed8521150, r=0x55926df63be0, this=0x55926e00a250) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #9 doActivate (sender=0x55926df638e0, signal_index=5, argv=0x7ffed8521150) at kernel/qobject.cpp:3925 #10 0x7f13b4c94075 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katesqlplugin.so #11 0x7f13b4c9c226 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katesqlplugin.so #12 0x7f13b4c960f4 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katesqlplugin.so #13 0x7f13ccafba32 in QtPrivate::QSlotObjectBase::call (a=0x7ffed85212c0, r=0x55926df63be0, this=0x55926dffb4e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #14 doActivate (sender=0x55926dffb200, signal_index=4, argv=0x7ffed85212c0) at kernel/qobject.cpp:3925 #15 0x7f13cd95c4d2 in QAction::triggered(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f13cd95f12f in QAction::activate(QAction::ActionEvent) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f13cda5661a in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f13cda56767 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f13cdb4f28a in QToolButton::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f13cd9a4e18 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f13cd962d2e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f13cd96b1cd in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f13ccac30d8 in QCoreApplication::notifyInternal2 (receiver=0x55926e002a50, event=0x7ffed8521850) at kernel/qcoreapplication.cpp:1064 #24 0x7f13cd9694be in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f13cd9bd96d in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f13cd9c0cbf in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7f13cd962d2e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7f13ccac30d8 in QCoreApplication::notifyInternal2 (receiver=0x55926e186cc0, event=0x7ffed8521b00) at kernel/qcoreapplication.cpp:1064 #29 0x7f13cd13ea6b in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #30 0x7f13cd112d5c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #31 0x7f13c6cfb8ba in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #32 0x7f13ca9155b4 in g_main_dispatch (context=context@entry=0x7f13cec0) at ../../../glib/gmain.c:3476 #33 0x7f13ca918607 in g_main_context_dispatch_unlocked (context=0x7f13cec0) at ../../../glib/gmain.c:4284 #34 g_main_context_iterate_unlocked (context=context@entry=0x7f13cec0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4349 #35 0x7f13ca918bfc in g_main_context_iteration (context=0x7f13cec0, may_block=1) at ../../../glib/gmain.c:4414 #3
[kwin] [Bug 461052] kwin crashed in KWin::Window::isOnOutput()
https://bugs.kde.org/show_bug.cgi?id=461052 --- Comment #9 from Vassilis Virvilis --- (In reply to Vlad Zahorodnii from comment #8) > Can you attach the screenshot of that effect? I don't think so. It is transient during virtual desktop switching. I would need probably to record it in video. > I can't reproduce the crash, kwin doesn't crash if I remove and reconnect an > output while the overview effect is active and switch between virtual > desktops. Ok I have 2 different monitors with the same resolution. When I came in the morning sometimes I have to switch the monitors (for some non related reason). When I get back in my chair everything is normal. When I try to switch to another virtual screen I get the crash. Hope that helps -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461052] kwin crashed in KWin::Window::isOnOutput()
https://bugs.kde.org/show_bug.cgi?id=461052 --- Comment #7 from Vassilis Virvilis --- (In reply to Vlad Zahorodnii from comment #6) > > -try to change virtual desktops - kwin crashes and the report-bug is popped > > up. > Is overview/present windows/desktop grid active when you change virtual > desktop? Do you mean the thumbnails of virtual desktops selector? (sorry I don't know the proper name). In that case yes - I would say. It is always shown when I change virtual desktops. So it should be shown also when the bug is triggered (after monitor change). Now I can't remember if it is actually shown or crashes trying to show it and I am not at work so I cannot reproduce it. However in a recent update kwin started to restart itself after the crash and the mitigates the severity of this error. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 461627] Crash when trying to delete non-printing hung job same as #430737
https://bugs.kde.org/show_bug.cgi?id=461627 --- Comment #1 from Vassilis Virvilis --- Well crashed again. Same crash. I am not reposting the crash information. I think I can reproduce it. My CUPS installation does have for sure a problem and doesn't print. When I try to delete the hunged non printing job it crashes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461052] kwin crashed in KWin::Window::isOnOutput()
https://bugs.kde.org/show_bug.cgi?id=461052 --- Comment #5 from Vassilis Virvilis --- This crash is consistent for me now. The way to reproduce is: -Start Plasma session (login) -Remove old monitor -Attach new monitor (same resolution - don't know what happens if you reconnect the old monitor. Hm?) -kwin seems working -try to change virtual desktops - kwin crashes and the report-bug is popped up. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))
https://bugs.kde.org/show_bug.cgi?id=461316 --- Comment #55 from Vassilis Virvilis --- Out of curiosity, I have no experience with opengl/mesa so the question may be invalid. The main culprit that is being reversed is a patch that was adjusting reference counting of ... something (opengl context? not sure). The question is: Are we sure that the patch being reversed is buggy? We know for sure that it caused a regression and kwin crashes. However, isn't it possible that this is a failure of Qt/KDE/Plasma/kwin to handle the new "correct" behavior that the patch introduced? Don't get me wrong I am thrilled and grateful that you guys found it and have the mesa guys reverting it but I am just curious... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kjobwidgets] [Bug 461318] Kate crash when hung plasmashell is killed
https://bugs.kde.org/show_bug.cgi?id=461318 --- Comment #1 from Vassilis Virvilis --- This is time the backtrace is somewhat different. That's why I am posting again... Application: Kate (kate), signal: Segmentation fault [KCrash Handler] #4 0x7fab83ee484f in QObject::property (this=this@entry=0x564e91ce5570, name=name@entry=0x7fab86200155 "desktopFileName") at kernel/qobject.cpp:4119 #5 0x7fab861f9091 in KUiServerV2JobTracker::registerJob (this=0x564e91a02110, job=) at ./src/kuiserverv2jobtracker.cpp:186 #6 0x7fab861f7fe6 in operator() (__closure=0x564e91890740) at ./src/kuiserverv2jobtracker.cpp:227 #7 QtPrivate::FunctorCall, QtPrivate::List<>, void, KUiServerV2JobTracker::registerJob(KJob*):: >::call (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146 #8 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256 #9 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x564e91890730, r=, a=, ret=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443 #10 0x7fab83ee8caf in QtPrivate::QSlotObjectBase::call (a=0x7ffedb40a550, r=0x564e91a02110, this=0x564e91890730) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #11 doActivate (sender=0x7fab862080c0 <(anonymous namespace)::Q_QGS_serverProxy::innerFunction()::holder>, signal_index=3, argv=0x7ffedb40a550) at kernel/qobject.cpp:3919 #12 0x7fab83ee8caf in QtPrivate::QSlotObjectBase::call (a=0x7ffedb40a660, r=0x7fab862080c0 <(anonymous namespace)::Q_QGS_serverProxy::innerFunction()::holder>, this=0x564e916af5e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate (sender=0x7fab600245e0, signal_index=5, argv=0x7ffedb40a660) at kernel/qobject.cpp:3919 #14 0x7fab83ee1f4f in QMetaObject::activate (sender=sender@entry=0x7fab600245e0, m=m@entry=0x7fab8531e6c0 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffedb40a660) at kernel/qobject.cpp:3979 #15 0x7fab85300d6f in QDBusServiceWatcher::serviceOwnerChanged (this=this@entry=0x7fab600245e0, _t1=..., _t2=..., _t3=...) at .moc/moc_qdbusservicewatcher.cpp:242 #16 0x7fab8530168a in QDBusServiceWatcherPrivate::_q_serviceOwnerChanged (newOwner=..., oldOwner=..., service=..., this=) at ./src/dbus/qdbusservicewatcher.cpp:76 #17 QDBusServiceWatcher::qt_static_metacall (_o=_o@entry=0x7fab600245e0, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=3, _a=_a@entry=0x7ffedb40a7e0) at .moc/moc_qdbusservicewatcher.cpp:116 #18 0x7fab85301b33 in QDBusServiceWatcher::qt_metacall (this=0x7fab600245e0, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x7ffedb40a7e0) at .moc/moc_qdbusservicewatcher.cpp:197 #19 0x7fab852b361b in QDBusConnectionPrivate::deliverCall (this=, object=, msg=..., metaTypes=..., slotIdx=) at ../../include/QtCore/../../src/corelib/tools/qvarlengtharray.h:190 #20 0x7fab83edd450 in QObject::event (this=0x7fab600245e0, e=0x7fab600151f0) at kernel/qobject.cpp:1347 #21 0x7fab84b62f5e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7fab83eb1718 in QCoreApplication::notifyInternal2 (receiver=0x7fab600245e0, event=0x7fab600151f0) at kernel/qcoreapplication.cpp:1064 #23 0x7fab83eb46b1 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x564e8f525ec0) at kernel/qcoreapplication.cpp:1821 #24 0x7fab83f09dd3 in postEventSourceDispatch (s=0x564e8f611500) at kernel/qeventdispatcher_glib.cpp:277 #25 0x7fab822667a9 in g_main_dispatch (context=0x7fab78005010) at ../../../glib/gmain.c:3444 #26 g_main_context_dispatch (context=context@entry=0x7fab78005010) at ../../../glib/gmain.c:4162 #27 0x7fab82266a38 in g_main_context_iterate (context=context@entry=0x7fab78005010, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4238 #28 0x7fab82266acc in g_main_context_iteration (context=0x7fab78005010, may_block=1) at ../../../glib/gmain.c:4303 #29 0x7fab83f094b6 in QEventDispatcherGlib::processEvents (this=0x564e8f612910, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #30 0x7fab83eb019b in QEventLoop::exec (this=this@entry=0x7ffedb40ac20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #31 0x7fab83eb8306 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #32 0x564e8f418511 in ?? () #33 0x7fab83a4618a in __libc_start_call_main (main=main@entry=0x564e8f416220, argc=argc@entry=4, argv=argv@entry=0x7ffedb40b198) at ../sysdeps/nptl/libc_start_call_main.h:58 #34 0x7fab83a46245 in __libc_start_main_impl (main=0x564e8f416220, argc=4, argv=0x7ffedb40b198, init=, fini=, rtld_fini=, stack_end=0x7ffedb40b188) at ../csu/libc-star
[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))
https://bugs.kde.org/show_bug.cgi?id=461316 --- Comment #30 from Vassilis Virvilis --- (In reply to Oleg Solovyov from comment #27) > Older version would spam notifications so hard it could have killed any > version of Mesa But but... a client shouldn't be able to crash a library... My world shutters... Seriously though. If I try to open thousands or million of files I wouldn't expect a crash in libc or in the kernel. I would expect an error "out of resources" but then I guess my program would crash because I wouldn't have been checking for errors. Is something like that goes on here? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))
https://bugs.kde.org/show_bug.cgi?id=461316 --- Comment #29 from Vassilis Virvilis --- (In reply to xxmlud from comment #28) > Hello, Vassilis Virvilis, I am in the same situation as you. But I don't > know how to provide some logs that can help with this problem. > One question, do you have two monitors? No. I have one monitor per machine. But I have work and home computer. Some times I use xpra to access the work machine. Sometimes I got a local crash. Sometimes I got a remote crash. Sometimes I have keyboard other I have mouse. Sometimes the keyboard input is borked like a modifier (like Ctrl or Alt) is pressed. The borked modifier is probably a remote thing only but I am not 100% sure. It's all over the place really. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))
https://bugs.kde.org/show_bug.cgi?id=461316 --- Comment #26 from Vassilis Virvilis --- Thanks for looking so hard at this. Much appreciated. Yesterday I had another instance of this (or another bug). This time kwin wasn't killed (windows have their titles) but kwin was unresponsive. However I had keyboard and I was able to run 'kwin --replace' and then everything got ok. I don't remember how I got to the terminal though. Either I was already there (konsole had focus) or Alt-Tab worked which strikes me as somewhat weird. Unfortunately no logs for this new one. I am not sure I am helping anyone with these awfully incomplete reports. I will try my best to run the reproducer. Maybe I would be able to report something more useful. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))
https://bugs.kde.org/show_bug.cgi?id=461316 --- Comment #22 from Vassilis Virvilis --- This is probably another bug. I looked around but can't anything. Probable bad keywords. (no keyboard input) This time my desktop hanged. (Not sure if I had mouse pointer). Certainly not keyboard. Windows decorations were there. I switch to console and back to X. Now I have mouse pointer but no click. No keyboard. Now I can't Ctrl-Alt-F2. I ssh and do sudo chvt 2 I restart kwin from console (DISPLAY=:0 kwin --replace) Now I have mouse pointer + click but still no keyboard. I restarted plasmashell. Kate crashed as per: https://bugs.kde.org/show_bug.cgi?id=461318 Still no keyboard input. *** Do you happen to know what process I need to restart to gain keyboard again?. I had to reboot. and I lost a lot of state. In the meantime as I promised I straced both kwin and plasmashell. Everything looks ok. They are waiting for input: kwin: futex(0x56164c8eaec4, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, FUTEX_BITSET_MATCH_ANY plasmashell: futex(0x55796b5c3f14, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, FUTEX_BITSET_MATCH_ANY This bug is more severe and more difficult / rare to trigger. If somebody has a pointer for this bug I will post there. Otherwise I will open a new bug later today. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))
https://bugs.kde.org/show_bug.cgi?id=461316 --- Comment #21 from Vassilis Virvilis --- Aa a reproducer. Thanks for that. I will try it at home and report back. I hope that you are onto something. If memory serves a lot of the crashes are related with virtual dekstop switches - not sure if that is a Knotification though... We 'll see. Much appreciated anyway... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))
https://bugs.kde.org/show_bug.cgi?id=461316 --- Comment #11 from Vassilis Virvilis --- This one? https://gitlab.freedesktop.org/mesa/mesa/-/commit/768238fdc06eed3dce36da3baf811cb70db42b5c -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))
https://bugs.kde.org/show_bug.cgi?id=461316 --- Comment #9 from Vassilis Virvilis --- In my home. I upgraded to 5.26.3 (debian unstable) and was hit again by this . Not sure which error code though, because it was the first kwin instance and not one that I run from terminal so I didn't have stderr output. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 461627] New: Crash when trying to delete non-printing hung job same as #430737
https://bugs.kde.org/show_bug.cgi?id=461627 Bug ID: 461627 Summary: Crash when trying to delete non-printing hung job same as #430737 Classification: Frameworks and Libraries Product: print-manager Version: 22.04.2 Platform: Debian unstable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dantt...@gmail.com Reporter: vas...@zoho.eu Target Milestone: --- Application: kde-print-queue (22.04.2) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 6.0.0-3-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux bookworm/sid DrKonqi: 5.26.3 [KCrashBackend] -- Information about the crash: Hey the backtrace looks different from https://bugs.kde.org/show_bug.cgi?id=430737 but the title is the same: crashed after deleting job because of unrecognized location of the printer Really sorry if it is a duplicate. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Print Queue (kde-print-queue), signal: Segmentation fault [KCrash Handler] #4 QStandardItem::text (this=0x0) at /usr/include/x86_64-linux-gnu/qt5/QtGui/qstandarditemmodel.h:75 #5 PrintQueueUi::modifyJob (this=0x55eb6f062280, action=action@entry=0, destName=...) at ./printqueue/PrintQueueUi.cpp:475 #6 0x55eb6d752007 in PrintQueueUi::cancelJob (this=) at ./printqueue/PrintQueueUi.cpp:528 #7 0x7f14ae2e8caf in QtPrivate::QSlotObjectBase::call (a=0x7ffeb5565340, r=0x55eb6f062280, this=0x55eb6f276f90) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #8 doActivate (sender=0x55eb6f25ef20, signal_index=3, argv=0x7ffeb5565340) at kernel/qobject.cpp:3919 #9 0x7f14ae2e1f4f in QMetaObject::activate (sender=, m=m@entry=0x7f14af478dc0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3979 #10 0x7f14aef87270 in QShortcut::activated (this=) at .moc/moc_qshortcut.cpp:202 #11 0x7f14aef883a3 in QShortcut::event (this=0x55eb6f25ef20, e=0x7ffeb55654d0) at kernel/qshortcut.cpp:743 #12 0x7f14aef62f5e in QApplicationPrivate::notify_helper (this=, receiver=0x55eb6f25ef20, e=0x7ffeb55654d0) at kernel/qapplication.cpp:3637 #13 0x7f14ae2b1718 in QCoreApplication::notifyInternal2 (receiver=0x55eb6f25ef20, event=0x7ffeb55654d0) at kernel/qcoreapplication.cpp:1064 #14 0x7f14ae76c9db in QShortcutMap::dispatchEvent (this=, e=) at kernel/qshortcutmap.cpp:675 #15 0x7f14ae76d32b in QShortcutMap::tryShortcut (this=this@entry=0x55eb6ee87f78, e=e@entry=0x7ffeb5565590) at kernel/qshortcutmap.cpp:343 #16 0x7f14ae7154e6 in QWindowSystemInterface::handleShortcutEvent (window=, timestamp=1821273, keyCode=16777223, modifiers=..., nativeScanCode=91, nativeVirtualKey=65439, nativeModifiers=0, text=..., autorepeat=false, count=1) at kernel/qwindowsysteminterface.cpp:477 #17 0x7f14ae73939d in QGuiApplicationPrivate::processKeyEvent (e=0x55eb6f615ed0) at kernel/qguiapplication.cpp:2398 #18 0x7f14ae711e1c in QWindowSystemInterface::sendWindowSystemEvents (flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169 #19 0x7f14a8cfc0fa in xcbSourceDispatch (source=) at ./src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:105 #20 0x7f14aca687a9 in g_main_dispatch (context=0x7f14a4005010) at ../../../glib/gmain.c:3444 #21 g_main_context_dispatch (context=context@entry=0x7f14a4005010) at ../../../glib/gmain.c:4162 #22 0x7f14aca68a38 in g_main_context_iterate (context=context@entry=0x7f14a4005010, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4238 #23 0x7f14aca68acc in g_main_context_iteration (context=0x7f14a4005010, may_block=1) at ../../../glib/gmain.c:4303 #24 0x7f14ae3094b6 in QEventDispatcherGlib::processEvents (this=0x55eb6ef58d40, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #25 0x7f14ae2b019b in QEventLoop::exec (this=this@entry=0x55eb6f250d48, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #26 0x7f14afb1f30b in KCupsRequest::waitTillFinished (this=this@entry=0x55eb6f250d30) at ./libkcups/KCupsRequest.cpp:615 #27 0x55eb6d751b7c in PrintQueueUi::modifyJob (this=0x55eb6f062280, action=action@entry=0, destName=...) at ./printqueue/PrintQueueUi.cpp:472 #28 0x55eb6d752007 in PrintQueueUi::cancelJob (this=) at ./printqueue/PrintQueueUi.cpp:528 #29 0x7f14ae2e8caf in QtPrivate::QSlotObjectBase::call (a=0x7ffeb5565a30, r=0x55eb6f062280, this=0x55eb6f276f90) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #30 doActivate (sender=0x55eb6f25ef20, signal_index=3, argv=0x7ffeb5565a30) at kernel/qobject.cpp:3919 #31 0x7f14ae2e1f4f in QMetaObject::activate (sender=, m=m@entry=0x7f14af478dc0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject
[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))
https://bugs.kde.org/show_bug.cgi?id=461316 --- Comment #8 from Vassilis Virvilis --- I also got the 'error 2: No such file or directory' error: The X11 connection broke: I/O error (code 1) XIO: fatal IO error 2 (No such file or directory) on X server ":0" after 5589828 requests (5589828 known processed) with 0 events remaining. kwin killed so no strace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))
https://bugs.kde.org/show_bug.cgi?id=461316 --- Comment #6 from Vassilis Virvilis --- So far the X errors are: 1. Local: The X11 connection broke: I/O error (code 1) X connection to :0 broken (explicit kill or server shutdown). --> kwin killed 2. Local: The X11 connection broke: I/O error (code 1) XIO: fatal IO error 0 (Success) on X server ":0" --> kwin killed 3. Remote: The X11 connection broke: I/O error (code 1) XIO: fatal IO error 22 (Invalid argument) on X server ":0" after 6963214 requests (6963214 known processed) with 0 events remaining. --> kwin killed I will keep updating the list. Note: It looks like the hung case is much rarer. Maybe it happens when the plasmashell is busted and it is actually a different bug. When kwin dies user input are dying too so I can't be really sure that plasmashell is actually alive before I restart kwin. Maybe all 3 above are different bugs. I certainly hope that this isn't the case though because it looks terribly difficult to diagnose this without a backtrace let alone 3 of them. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))
https://bugs.kde.org/show_bug.cgi?id=461316
--- Comment #5 from Vassilis Virvilis ---
It did it a again this on (remote with xpra) unlock time with error code 22.
I am posting only a few lines of intermixed output (plasmashell & kwin) just in
case somebody may spot something.
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 16004, resource
id: 60817412, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 16008, resource
id: 60817421, major code: 18 (ChangeProperty), minor code: 0
QFont::setPointSizeF: Point size <= 0 (0.00), must be greater than 0
Could not find the Plasmoid for Plasma::FrameSvgItem(0x563937d58010)
QQmlContext(0x563934b35570)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Could not find the Plasmoid for Plasma::FrameSvgItem(0x563937d58010)
QQmlContext(0x563934b35570)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:248:21:
QML SelectableLabel: Binding loop detected for property "implicitWidth"
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:248:21:
QML SelectableLabel: Binding loop detected for property "implicitWidth"
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:248:21:
QML SelectableLabel: Binding loop detected for property "implicitHeight"
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/SelectableLabel.qml:40:5:
QML TextArea: Binding loop detected for property "implicitHeight"
The X11 connection broke: I/O error (code 1)
XIO: fatal IO error 22 (Invalid argument) on X server ":0"
after 6963214 requests (6963214 known processed) with 0 events remaining.
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 32106, resource
id: 0, major code: 53 (CreatePixmap), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 32107,
resource id: 29364601, major code: 55 (CreateGC), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 32108,
resource id: 29364601, major code: 72 (PutImage), minor code: 0
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 461419] New: Kate plugin-sql: Export/Copy of output table fails to retain order
https://bugs.kde.org/show_bug.cgi?id=461419 Bug ID: 461419 Summary: Kate plugin-sql: Export/Copy of output table fails to retain order Classification: Applications Product: kate Version: 22.04.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: vas...@zoho.eu Target Milestone: --- Consider the following simple SQL that generates two rows. SELECT 1 row, 11 col1, 12 col2, 13 col3 UNION ALL SELECT 2, 21,22, 23; The output is: rowcol1 col2 col3 111 12 13 221 22 23 but when I export or copy I get: col1 row col3 col2 21 223 22 11 1 13 12 It has mixed both rows and columns. My system: Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-2-amd64 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 31.3 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4000 Manufacturer: Gigabyte Technology Co., Ltd. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))
https://bugs.kde.org/show_bug.cgi?id=461316 --- Comment #3 from Vassilis Virvilis --- ok it did it again. Same error but different message. kwin got killed so no backtrace. The X11 connection broke: I/O error (code 1) XIO: fatal IO error 0 (Success) on X server ":0" Here is the combined output in the console from kwin and plasmashell. I don't want to spam this bug so I won't post any more of these outputs unless somebody finds them useful. caching records from 6725 to 6925 Export in 0 msecs kwin_core: XCB error: 152 (BadDamage), sequence: 48054, resource id: 69786721, major code: 143 (DAMAGE), minor code: 3 (Subtract) kwin_core: XCB error: 152 (BadDamage), sequence: 50025, resource id: 69786857, major code: 143 (DAMAGE), minor code: 3 (Subtract) qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 60404, resource id: 69787609, major code: 3 (GetWindowAttributes), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 60405, resource id: 69787609, major code: 14 (GetGeometry), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 60408, resource id: 69787609, major code: 3 (GetWindowAttributes), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 60409, resource id: 69787609, major code: 14 (GetGeometry), minor code: 0 kwin_core: XCB error: 152 (BadDamage), sequence: 1323, resource id: 69788124, major code: 143 (DAMAGE), minor code: 3 (Subtract) libkcups: Renew-Subscription last error: 0 successful-ok qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 10656, resource id: 94371894, major code: 18 (ChangeProperty), minor code: 0 kwin_core: XCB error: 3 (BadWindow), sequence: 13117, resource id: 69781020, major code: 129 (SHAPE), minor code: 6 (Input) qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 13118, resource id: 69781020, major code: 2 (ChangeWindowAttributes), minor code: 0 QFont::setPointSizeF: Point size <= 0 (0.00), must be greater than 0 kwin_core: XCB error: 3 (BadWindow), sequence: 27544, resource id: 69789767, major code: 129 (SHAPE), minor code: 6 (Input) qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 27545, resource id: 69789767, major code: 2 (ChangeWindowAttributes), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 29605, resource id: 29362200, major code: 18 (ChangeProperty), minor code: 0 kwin_core: XCB error: 3 (BadWindow), sequence: 31735, resource id: 69791250, major code: 129 (SHAPE), minor code: 6 (Input) qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31736, resource id: 69791250, major code: 2 (ChangeWindowAttributes), minor code: 0 kwin_core: XCB error: 3 (BadWindow), sequence: 36739, resource id: 69791729, major code: 129 (SHAPE), minor code: 6 (Input) qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 36740, resource id: 69791729, major code: 2 (ChangeWindowAttributes), minor code: 0 kwin_core: XCB error: 3 (BadWindow), sequence: 28091, resource id: 69792410, major code: 129 (SHAPE), minor code: 6 (Input) qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 28092, resource id: 69792410, major code: 2 (ChangeWindowAttributes), minor code: 0 kwin_core: XCB error: 152 (BadDamage), sequence: 46384, resource id: 69816448, major code: 143 (DAMAGE), minor code: 3 (Subtract) kwin_core: XCB error: 152 (BadDamage), sequence: 6396, resource id: 69819312, major code: 143 (DAMAGE), minor code: 3 (Subtract) qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7456, resource id: 71303652, major code: 19 (DeleteProperty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7467, resource id: 71303652, major code: 19 (DeleteProperty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7468, resource id: 71303652, major code: 18 (ChangeProperty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7469, resource id: 71303652, major code: 19 (DeleteProperty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7470, resource id: 71303652, major code: 19 (DeleteProperty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7471, resource id: 71303652, major code: 19 (DeleteProperty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7472, resource id: 71303652, major code: 7 (ReparentWindow), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7473, resource id: 71303652, major code: 6 (ChangeSaveSet), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7474, resource id: 71303652, major code: 2 (ChangeWindowAttributes), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 7475, resource id: 71303652, major code: 10 (UnmapWindow), minor code: 0 kwin_core: XCB error: 3 (BadWindow), sequence: 8525, resource id: 71303784,
[kate] [Bug 461318] New: Kate crash when hung plasmashell is killed
https://bugs.kde.org/show_bug.cgi?id=461318 Bug ID: 461318 Summary: Kate crash when hung plasmashell is killed Classification: Applications Product: kate Version: 22.04.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: vas...@zoho.eu Target Milestone: --- When the kwin hangs as in https://bugs.kde.org/show_bug.cgi?id=461316 I got a 50% percent chance that the plasmashell got hang and I have to kiil it and restart it. When that happens the Kate crashes (again a 50% chances) with the following backtrace. Hope this helps. Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-2-amd64 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 31.3 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4000 Manufacturer: Gigabyte Technology Co., Ltd. -- Application: Kate (kate), signal: Segmentation fault [KCrash Handler] #4 0x7fec1ea5e654 in KJob::isSuspended() const () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #5 0x7fec1f81a0dc in KUiServerV2JobTracker::registerJob (this=0x559dfb9ddd40, job=) at ./src/kuiserverv2jobtracker.cpp:236 #6 0x7fec1f818fe6 in operator() (__closure=0x559dfbe0a4a0) at ./src/kuiserverv2jobtracker.cpp:227 #7 QtPrivate::FunctorCall, QtPrivate::List<>, void, KUiServerV2JobTracker::registerJob(KJob*):: >::call (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146 #8 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256 #9 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x559dfbe0a490, r=, a=, ret=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443 #10 0x7fec1d6e8caf in QtPrivate::QSlotObjectBase::call (a=0x7ffcf054e070, r=0x559dfb9ddd40, this=0x559dfbe0a490) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #11 doActivate (sender=0x7fec1f8290c0 <(anonymous namespace)::Q_QGS_serverProxy::innerFunction()::holder>, signal_index=3, argv=0x7ffcf054e070) at kernel/qobject.cpp:3919 #12 0x7fec1d6e8caf in QtPrivate::QSlotObjectBase::call (a=0x7ffcf054e180, r=0x7fec1f8290c0 <(anonymous namespace)::Q_QGS_serverProxy::innerFunction()::holder>, this=0x559dfb9ddd70) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate (sender=0x559dfbad27f0, signal_index=5, argv=0x7ffcf054e180) at kernel/qobject.cpp:3919 #14 0x7fec1d6e1f4f in QMetaObject::activate (sender=sender@entry=0x559dfbad27f0, m=m@entry=0x7fec1e9546c0 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffcf054e180) at kernel/qobject.cpp:3979 #15 0x7fec1e936d6f in QDBusServiceWatcher::serviceOwnerChanged (this=this@entry=0x559dfbad27f0, _t1=..., _t2=..., _t3=...) at .moc/moc_qdbusservicewatcher.cpp:242 #16 0x7fec1e93768a in QDBusServiceWatcherPrivate::_q_serviceOwnerChanged (newOwner=..., oldOwner=..., service=..., this=) at ./src/dbus/qdbusservicewatcher.cpp:76 #17 QDBusServiceWatcher::qt_static_metacall (_o=_o@entry=0x559dfbad27f0, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=3, _a=_a@entry=0x7ffcf054e300) at .moc/moc_qdbusservicewatcher.cpp:116 #18 0x7fec1e937b33 in QDBusServiceWatcher::qt_metacall (this=0x559dfbad27f0, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x7ffcf054e300) at .moc/moc_qdbusservicewatcher.cpp:197 #19 0x7fec1e8e961b in QDBusConnectionPrivate::deliverCall (this=, object=, msg=..., metaTypes=..., slotIdx=) at ../../include/QtCore/../../src/corelib/tools/qvarlengtharray.h:190 #20 0x7fec1d6dd450 in QObject::event (this=0x559dfbad27f0, e=0x7febf803ae90) at kernel/qobject.cpp:1347 #21 0x7fec1e362f5e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7fec1d6b1718 in QCoreApplication::notifyInternal2 (receiver=0x559dfbad27f0, event=0x7febf803ae90) at kernel/qcoreapplication.cpp:1064 #23 0x7fec1d6b46b1 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x559df97d0ec0) at kernel/qcoreapplication.cpp:1821 #24 0x7fec1d709dd3 in postEventSourceDispatch (s=0x559df98babe0) at kernel/qeventdispatcher_glib.cpp:277 #25 0x7fec1b868799 in g_main_dispatch (context=0x7fec10005010) at ../../../glib/gmain.c:3444 #26 g_main_context_dispatch (context=context@entry=0x7fec10005010) at ../../../glib/gmain.c:4162 #27 0x7fec1b868a28 in g_main_context_iterate (context=context@entry=0x7fec10005010, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4238 #28 0x7fec1b868abc in g_main_context_iteration (context=0x7fec10005
[kwin] [Bug 461316] Kwin killed by X (The X11 connection broke: I/O error (code 1))
https://bugs.kde.org/show_bug.cgi?id=461316 --- Comment #1 from Vassilis Virvilis --- Now I saw the about system: Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-2-amd64 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 31.3 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4000 Manufacturer: Gigabyte Technology Co., Ltd. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461316] New: Kwin killed by X (The X11 connection broke: I/O error (code 1))
https://bugs.kde.org/show_bug.cgi?id=461316 Bug ID: 461316 Summary: Kwin killed by X (The X11 connection broke: I/O error (code 1)) Classification: Plasma Product: kwin Version: 5.26.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: vas...@zoho.eu Target Milestone: --- Really really sorry for this but no backtrace. Kwin is getting killed by X with (2 last lines) The X11 connection broke: I/O error (code 1) X connection to :0 broken (explicit kill or server shutdown). I trust that I dind't kill my kwin on purpose. Can any keyboard combination do this? This time it took 2-3 days to be killed like this. Here are all the messages that it spits in these 3 days. I really hope that you will be able to find something valuable. I mentioned this bug in https://bugs.kde.org/show_bug.cgi?id=461052 (which is another bug) After the kwin crash I have a 50% change for a plasmashell crash. This is of course is another bug but it is entirely possible that the plasmashell crash comes first and lead to the kwin death mentioned here. I can't tell because when kwin is killed the desktop is unresponsive. One other observation. Some times kwin is killed (cannot be found with ps - no titlebars in the windows) and sometimes it hangs (unresponsive desktop, titlebars in windows and can be found by ps). Next time (in 2 - 3 days) I will try to attach a strace. bill@beyonder:~$ kwin --replace & [1] 1185549 bill@beyonder:~$ kwin_xkbcommon: XKB: inet:334:58: unrecognized keysym "XF86EmojiPicker" bill@beyonder:~$ OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) HD Graphics 4000 (IVB GT2) OpenGL version string: 4.2 (Compatibility Profile) Mesa 22.2.2 OpenGL shading language version string: 4.20 Driver: Intel GPU class: IvyBridge OpenGL version: 4.2 GLSL version: 4.20 Mesa version: 22.2.2 X server version: 1.21.1 Linux kernel version: 6.0 Requires strict binding:yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no bill@beyonder:~$ bill@beyonder:~$ bill@beyonder:~$ bill@beyonder:~$ jobs [1]+ Running kwin --replace & bill@beyonder:~$ disown bill@beyonder:~$ jobs bill@beyonder:~$ bill@beyonder:~$ bill@beyonder:~$ qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5075, resource id: 69206021, major code: 18 (ChangeProperty), minor code: 0 bill@beyonder:~$ kwin_core: XCB error: 152 (BadDamage), sequence: 39, resource id: 29365899, major code: 143 (DAMAGE), minor code: 3 (Subtract) kwin_core: XCB error: 152 (BadDamage), sequence: 7894, resource id: 29366594, major code: 143 (DAMAGE), minor code: 3 (Subtract) qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 10273, resource id: 29366843, major code: 3 (GetWindowAttributes), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 10274, resource id: 29366843, major code: 14 (GetGeometry), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 10277, resource id: 29366843, major code: 3 (GetWindowAttributes), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 10278, resource id: 29366843, major code: 14 (GetGeometry), minor code: 0 kwin_core: XCB error: 152 (BadDamage), sequence: 11036, resource id: 29366874, major code: 143 (DAMAGE), minor code: 3 (Subtract) kwin_core: XCB error: 152 (BadDamage), sequence: 13608, resource id: 29367088, major code: 143 (DAMAGE), minor code: 3 (Subtract) kwin_core: XCB error: 152 (BadDamage), sequence: 18108, resource id: 29367428, major code: 143 (DAMAGE), minor code: 3 (Subtract) qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 23835, resource id: 29367950, major code: 3 (GetWindowAttributes), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 23836, resource id: 29367950, major code: 14 (GetGeometry), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 23839, resource id: 29367950, major code: 3 (GetWindowAttributes), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 23840, resource id: 29367950, major code: 14 (GetGeometry), minor code: 0 kwin_core: XCB error: 152 (BadDamage), sequence: 24681, resource id: 29367983, major code: 143 (DAMAGE), minor code: 3 (Subtract) kwin_core: XCB error: 152 (BadDamage), sequence: 37748, resource id: 29368993, major code: 143 (DAMAGE), minor code: 3 (Subtract) kwin_core: XCB error: 152 (BadDamage), sequence: 39963
[kwin] [Bug 461052] kwin crash
https://bugs.kde.org/show_bug.cgi?id=461052 --- Comment #1 from Vassilis Virvilis --- Just remembered something that may be important. My monitor broke down (don't ask) and I had to connect a new one (same resolution though). Then I got the KCrash dialog in the new monitor. Hope that helps. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461052] New: kwin crash
https://bugs.kde.org/show_bug.cgi?id=461052 Bug ID: 461052 Summary: kwin crash Classification: Plasma Product: kwin Version: 5.26.0 Platform: Debian unstable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: vas...@zoho.eu Target Milestone: --- Application: kwin_x11 (5.26.0) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 6.0.0-1-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux bookworm/sid DrKonqi: 5.26.0 [KCrashBackend] -- Information about the crash: Hi, I got a lot a crashes from kwin probably after 5.24 (not so sure). It happens every 3 days - sometimes sooner with a X error 22 bad request. Previously I had kwin running for months. Usually kwin cannot restart itself after that. This time it managed to restart and offered me the KCrash dialog so this is probably a different bug and I thought to sent it over in case anybody can see it through... I have some 3D effects enabled not sure if that plays any role. The crash does not seem to be reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #4 KWin::OutputMode::size() const (this=0x1) at ./src/core/output.cpp:50 #5 0x7fb0ea3cc01e in KWin::Output::modeSize() const (this=this@entry=0x557e6db30f80) at ./src/core/output.cpp:184 #6 0x7fb0ea3cc22d in KWin::Output::pixelSize() const (this=this@entry=0x557e6db30f80) at ./src/core/output.cpp:189 #7 0x7fb0ea3cc27b in KWin::Output::geometry() const (this=0x557e6db30f80) at ./src/core/output.cpp:169 #8 0x7fb0ea4fe1c0 in KWin::Window::isOnOutput(KWin::Output*) const (this=this@entry=0x557e6de536c0, output=) at ./src/window.cpp:439 #9 0x7fb0ea4973fc in KWin::DesktopBackgroundItem::updateWindow() (this=this@entry=0x557e6ee4ea30) at ./src/scripting/desktopbackgrounditem.cpp:112 #10 0x7fb0ea4979ba in KWin::DesktopBackgroundItem::setDesktop(KWin::VirtualDesktop*) (desktop=, this=0x557e6ee4ea30) at ./src/scripting/desktopbackgrounditem.cpp:66 #11 KWin::DesktopBackgroundItem::setDesktop(KWin::VirtualDesktop*) (desktop=, this=0x557e6ee4ea30) at ./src/scripting/desktopbackgrounditem.cpp:62 #12 KWin::DesktopBackgroundItem::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x557e6ee4ea30, _c=, _id=, _a=) at ./obj-x86_64-linux-gnu/src/kwin_autogen/include/moc_desktopbackgrounditem.cpp:148 #13 0x7fb0ea497d53 in KWin::DesktopBackgroundItem::qt_metacall(QMetaObject::Call, int, void**) (this=0x557e6ee4ea30, _c=QMetaObject::WriteProperty, _id=3, _a=0x7ffd1e0e71f0) at ./obj-x86_64-linux-gnu/src/kwin_autogen/include/moc_desktopbackgrounditem.cpp:197 #14 0x7fb0e98e9e4e in QQmlPropertyData::writeProperty(QObject*, void*, QFlags) const (flags=..., value=, target=, this=) at ../../include/QtQml/5.15.6/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:393 #15 QObjectPointerBinding::write(QV4::Value const&, bool, QFlags) (this=, result=..., isUndefined=, flags=...) at qml/qqmlbinding.cpp:714 #16 0x7fb0e98eb89e in QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&, QFlags, QV4::Scope&) (this=0x557e6eaa55c0, watcher=..., flags=..., scope=) at qml/qqmlbinding.cpp:258 #17 0x7fb0e98e92b4 in QQmlBinding::update(QFlags) (this=0x557e6eaa55c0, flags=...) at qml/qqmlbinding.cpp:194 #18 0x7fb0e98c66df in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) (endpoint=, a=0x0) at qml/qqmlnotifier.cpp:104 #19 0x7fb0e86e87ed in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fb0e86e8caf in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fb0ea382708 in KWin::VirtualDesktopManager::currentChanged(unsigned int, unsigned int) (this=this@entry=0x557e6dd18c60, _t1=, _t1@entry=2, _t2=) at ./obj-x86_64-linux-gnu/src/kwin_autogen/EWIEGA46WW/moc_virtualdesktops.cpp:622 #22 0x7fb0ea4ea7e4 in KWin::VirtualDesktopManager::setCurrent(KWin::VirtualDesktop*) (this=0x557e6dd18c60, newDesktop=0x557e6e047510) at ./src/virtualdesktops.h:63 #23 0x7fb0e91e7ec9 in NETRootInfo::event(xcb_generic_event_t*, QFlags*, QFlags*) () at /lib/x86_64-linux-gnu/libKF5WindowSystem.so.5 #24 0x7fb0ea47d084 in KWin::RootInfoFilter::event(xcb_generic_event_t*) (this=, event=) at ./src/rootinfo_filter.cpp:26 #25 0x7fb0ea45c497 in KWin::Application::dispatchEvent(xcb_generic_event_t*) (this=, event=0x7fb0dc026b90) at ./src/main.cpp:447 #26 0x7fb0e86aec9f in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7fb0e24d43cf in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #28 0x7fb0e24d5956 in QXcbConnection::processXcbEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #29 0x7fb0e
[telepathy] [Bug 397369] [Neon Bionic] Chat window does not show messages - version 4:17.12.3-0ubuntu1
https://bugs.kde.org/show_bug.cgi?id=397369 --- Comment #6 from Vassilis Virvilis --- I don't know. I asked the same thing in a debian bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906098 Vassilis -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 397369] [Neon Bionic] Chat window does not show messages - version 4:17.12.3-0ubuntu1
https://bugs.kde.org/show_bug.cgi?id=397369 --- Comment #4 from Vassilis Virvilis --- Thanks for looking into this I am in debian unstable. Current versions are: ii libqt5webkit5:amd64 5.212.0~alpha2-17+b1 amd64Web content engine library for Qt ii libqt5core5a:amd64 5.11.2+dfsg-7amd64Qt 5 core module and telepathy ii kde-telepathy-text-ui 17.08.3-2amd64Telepathy text chat UI for the KDE Plasma Desktop I will try to check when 18.04 is supposed to be released in the unstable -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 397369] [Neon Bionic] Chat window does not show messages - version 4:17.12.3-0ubuntu1
https://bugs.kde.org/show_bug.cgi?id=397369 Vassilis Virvilis changed: What|Removed |Added CC||vas...@zoho.eu --- Comment #2 from Vassilis Virvilis --- Me too. I have this problem in Debian unstable with salut. telepathy version is 17.08.3 Any ideas how to debug or better workaround around this? Is the bug really in in the text-ui package? -- You are receiving this mail because: You are watching all bug changes.
