[plasmashell] [Bug 463428] Crash in TaskManager::WaylandStartupTasksModel::Private::loadConfig() after reloading wayland tasksmodel from config change
https://bugs.kde.org/show_bug.cgi?id=463428 --- Comment #5 from Mariusz Libera --- (In reply to Akseli Lahtinen from comment #4) > Has this crash occured anymore in Plasma 6? No. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487586] system settings crashed
https://bugs.kde.org/show_bug.cgi?id=487586 --- Comment #1 from Mariusz Libera --- Created attachment 169849 --> https://bugs.kde.org/attachment.cgi?id=169849=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487586] New: system settings crashed
https://bugs.kde.org/show_bug.cgi?id=487586 Bug ID: 487586 Summary: system settings crashed Classification: Applications Product: systemsettings Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: --- Application: systemsettings (6.0.90) Qt Version: 6.7.1 Frameworks Version: 6.2.0 Operating System: Linux 6.9.2-arch1-1-ml x86_64 Windowing System: Wayland Distribution: Arch Linux DrKonqi: 6.0.90 [CoredumpBackend] -- Information about the crash: system settings crashed while switching between different pages The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 operator() (__closure=0x56b4bcd40610) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:1915 #8 QtPrivate::QCallableObject, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x56b4bcd40600, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:555 #9 0x728b401a17b7 in QtPrivate::QSlotObjectBase::call (this=0x56b4bcd40600, r=0x56b4beb524a0, a=0x7ffc2f4278f0, this=, r=, a=) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobjectdefs_impl.h:469 #10 doActivate (sender=, signal_index=, argv=) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:4086 #11 0x728b4034a464 in QAbstractItemModel::modelReset (this=0x56b4bfeb16f0, _t1=...) at /usr/src/debug/qt6-base/build/src/corelib/Core_autogen/include/moc_qabstractitemmodel.cpp:1112 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486065] dolphin crashed while draggin a video file to another app
https://bugs.kde.org/show_bug.cgi?id=486065 --- Comment #1 from Mariusz Libera --- Created attachment 168862 --> https://bugs.kde.org/attachment.cgi?id=168862=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486065] New: dolphin crashed while draggin a video file to another app
https://bugs.kde.org/show_bug.cgi?id=486065 Bug ID: 486065 Summary: dolphin crashed while draggin a video file to another app Classification: Applications Product: dolphin Version: 24.02.2 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: mariusz.lib...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (24.02.2) Qt Version: 6.7.0 Frameworks Version: 6.1.0 Operating System: Linux 6.8.7-arch1-1-ml x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.0.4 [CoredumpBackend] -- Information about the crash: I tried to dragged a video file from dolphin into another app on a different screen and dolphin crashed. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 QScopedPointer >::get (this=0x8, this=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/tools/qscopedpointer.h:110 [...] #8 QObject::deleteLater (this=0x0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qobject.cpp:2456 #9 0x7d1e576f4cce in KDEPrivate::KUrlNavigatorButton::dragMoveEvent (this=0x5df16dfe5a10, event=) at /usr/src/debug/kio/kio-6.1.0/src/filewidgets/kurlnavigatorbutton.cpp:323 #10 0x7d1e561470d3 in QWidget::event (this=0x5df16dfe5a10, event=0x7ffd8fa61f10) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qwidget.cpp:9237 #11 0x7d1e560fbfcb in QApplicationPrivate::notify_helper (this=this@entry=0x5df16d5c8290, receiver=0x5df16dfe5a10, e=e@entry=0x7ffd8fa61f10) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qapplication.cpp:3287 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457928] flat acceleration profile not honored after mouse unplugged and plugged in again
https://bugs.kde.org/show_bug.cgi?id=457928 --- Comment #9 from Mariusz Libera --- (In reply to Nate Graham from comment #8) > Is anyone able to reproduce this issue in Plasma 5.27 or 6? It seems to work fine on Plasma 6 Wayland. I haven't tested on X11. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481577] ship a window rule to keep picture-in-picture windows above
https://bugs.kde.org/show_bug.cgi?id=481577 Mariusz Libera changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #6 from Mariusz Libera --- (In reply to Nate Graham from comment #5) > An exact title match for "Picture-in-Picture" might work in English, but > does this still work if the system is in another language? Good point, just checked, Firefox does indeed translate that. Wouldn't expect it. Well, this is pretty hopeless then. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481577] ship a window rule to keep picture-in-picture windows above
https://bugs.kde.org/show_bug.cgi?id=481577 --- Comment #4 from Mariusz Libera --- (In reply to Vlad Zahorodnii from comment #3) > > above=true > > aboverule=3 > > in plasma 6, I recommend to create a "layer" window rule instead to force > pip windows to be placed in the overlay layer. With that, pip windows will > be visible even if there's a fullscreen window. I wasn't aware of that, but it works even better. Description=Picture in picture for firefox layer=overlay layerrule=2 title=Picture-in-Picture titlematch=1 types=1 wmclass=firefox wmclassmatch=1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481577] ship a window rule to keep picture-in-picture windows above
https://bugs.kde.org/show_bug.cgi?id=481577 --- Comment #2 from Mariusz Libera --- (In reply to Nate Graham from comment #1) > I would be super in favor of this if it works properly. Does it work fine > with new PiP windows, not just the one you created it for? And are there > rules that work for all PiP windows for both Firefox and Chrome/Chromium? > Can you test those? This rule works fine for me, no issues whatsoever: Description=Picture in picture for firefox above=true aboverule=3 title=Picture-in-Picture titlematch=1 types=1 wmclass=firefox wmclassmatch=1 Chrome seems to work fine out of the box, if it's run in xwayland, native wayland version needs a rule: Description=Picture in picture for chrome above=true aboverule=3 title=Picture in picture titlematch=1 types=1 wmclass=chrome wmclassmatch=1 I would imagine that a regex would be needed to catch all chromium based browsers in 'wmclass'. By the way, it would be nice if there was a checkbox to enable/disable window rules instead of having to delete and recreate them to test. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481574] sending a window to another workspace leaves no windows focused on the current workspace
https://bugs.kde.org/show_bug.cgi?id=481574 --- Comment #3 from Mariusz Libera --- (In reply to Nate Graham from comment #1) > Are you saying you want it to move there, and also switch to that virtual > desktop as well? Because it can't focus the window when the window goes to > another virtual desktop without switching to that virtual desktop. No, at no point do I want to switch desktops. This is about focus. If you have 2 windows open and you close the one with focus, the other one now gains focus - this does not work, if instead of closing the focused window you send it to another desktop - the remaining window is not focused. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481577] New: ship a window rule to keep picture-in-picture windows above
https://bugs.kde.org/show_bug.cgi?id=481577 Bug ID: 481577 Summary: ship a window rule to keep picture-in-picture windows above Classification: Plasma Product: kwin Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: --- I understand that wayland protocol seems to be the long term solution, but how about a band aid in the meantime - a simple window rule enabled by default that forces picture-in-picture windows to be kept above. It seems to work fine. Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics Memory: 14.8 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82RE System Version: Legion 5 15ARH7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481576] New: redundant numbers next to virtual desktops in the window context menu
https://bugs.kde.org/show_bug.cgi?id=481576 Bug ID: 481576 Summary: redundant numbers next to virtual desktops in the window context menu Classification: Plasma Product: kwin Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: --- Created attachment 165953 --> https://bugs.kde.org/attachment.cgi?id=165953=edit screenshot OBSERVED RESULT right click the title bar and you have 'move to 1 desktop 1' EXPECTED RESULT 'move to desktop 1' or if the desktop has no name 'move to 1' Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics Memory: 14.8 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82RE System Version: Legion 5 15ARH7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481574] New: sending a window to another workspace leaves no windows focused on the current workspace
https://bugs.kde.org/show_bug.cgi?id=481574 Bug ID: 481574 Summary: sending a window to another workspace leaves no windows focused on the current workspace Classification: Plasma Product: kwin Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. have at least 2 virtual desktops 2. open 2 konsole windows on desktop 1 3. right click the title bar of the focused konsole window and select 'move to desktop 2' OBSERVED RESULT 4. the other konsole window is not focused EXPECTED RESULT 4. the other konsole window is focused SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics Memory: 14.8 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82RE System Version: Legion 5 15ARH7 ADDITIONAL INFORMATION It's the same, if I use the keyboard shortcut. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481297] New: walk through desktops shortcut missing
https://bugs.kde.org/show_bug.cgi?id=481297 Bug ID: 481297 Summary: walk through desktops shortcut missing Classification: Plasma Product: kwin Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: --- SUMMARY Can't find it in the shortcuts page of System Settings. There is 'walk through activities' and 'walk through windows', but 'walk through desktops' is nowhere to be found. I swear it was there before, was it renamed? Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.4-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-12500H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ASUS TUF Gaming F15 FX507ZC4_FX507ZC4 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 478667] New: dolphin crashed while using split view with kio-admin
https://bugs.kde.org/show_bug.cgi?id=478667
Bug ID: 478667
Summary: dolphin crashed while using split view with kio-admin
Classification: Applications
Product: dolphin
Version: 23.08.4
Platform: Arch Linux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: mariusz.lib...@gmail.com
CC: kfm-de...@kde.org
Target Milestone: ---
Application: dolphin (23.08.4)
Qt Version: 5.15.11
Frameworks Version: 5.113.0
Operating System: Linux 6.6.7-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.10 [KCrashBackend]
-- Information about the crash:
I opened a direcory with admin:/, then in the split view opened a different
directory - after a few seconds dolphin froze and then crashed.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 0x7f55c90d4d2a in QVector::realloc(int,
QFlags) (this=this@entry=0x7f555c01c900,
aalloc=, options=...) at /usr/include/qt/QtCore/qvector.h:706
#7 0x7f55c90d80f6 in QVector::append(KIO::Task&&) (t=...,
this=0x7f555c01c900) at /usr/include/qt/QtCore/qvector.h:806
#8 KIO::Connection::send(int, QByteArray const&) (data=,
cmd=, this=) at
/usr/src/debug/kio5/kio-5.113.0/src/core/connection.cpp:172
#9 KIO::Connection::send(int, QByteArray const&) (this=,
cmd=, data=) at
/usr/src/debug/kio5/kio-5.113.0/src/core/connection.cpp:166
#10 0x7f55c91124f1 in KIO::SlaveBase::send(int, QByteArray const&)
(this=0x7f555c01c8c0, cmd=, arr=) at
/usr/src/debug/kio5/kio-5.113.0/src/core/slavebase.cpp:1572
#11 0x7f55c910d2bc in KIO::SlaveBase::mimeType(QString const&)
(this=0x7f555c01c8c0, _type=...) at
/usr/src/debug/kio5/kio-5.113.0/src/core/slavebase.cpp:722
#12 0x7f55c74d1097 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7f558909f410, r=, this=0x7f555c015d60, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate(QObject*, int, void**) (sender=0x7f558909fa70,
signal_index=4, argv=0x7f558909f410) at kernel/qobject.cpp:3925
#14 0x7f55a814b421 in
OrgKdeKioAdminGetCommandInterface::mimeTypeFound(QString const&)
(_t1=, this=0x7f558909fa70) at
/usr/src/debug/kio-admin/build/src/interface_getcommand.moc:182
#15 OrgKdeKioAdminGetCommandInterface::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=_o@entry=0x7f558909fa70,
_c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=1,
_a=_a@entry=0x7f558909f550) at
/usr/src/debug/kio-admin/build/src/interface_getcommand.moc:97
#16 0x7f55a814b543 in
OrgKdeKioAdminGetCommandInterface::qt_metacall(QMetaObject::Call, int, void**)
(this=0x7f558909fa70, _c=QMetaObject::InvokeMetaMethod, _id=1,
_a=0x7f558909f550) at
/usr/src/debug/kio-admin/build/src/interface_getcommand.moc:161
#17 0x7f55c880776e in QDBusConnectionPrivate::deliverCall(QObject*, int,
QDBusMessage const&, QVector const&, int) (this=,
object=, msg=, metaTypes=,
slotIdx=) at
/usr/src/debug/qt5-base/qtbase/src/dbus/qdbusintegrator.cpp:1001
#18 0x7f55c74c3bd4 in QObject::event(QEvent*) (this=0x7f558909fa70,
e=0x7f55bc034e80) at kernel/qobject.cpp:1347
#19 0x7f55c81788ff in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x7f558909fa70, e=0x7f55bc034e80) at
kernel/qapplication.cpp:3640
#20 0x7f55c749c168 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x7f558909fa70, event=0x7f55bc034e80) at
kernel/qcoreapplication.cpp:1064
#21 0x7f55c74a10cb in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x562faf183ef0) at
kernel/qcoreapplication.cpp:1821
#22 0x7f55c74e7138 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x7f555c01c310) at kernel/qeventdispatcher_glib.cpp:277
#23 0x7f55c550df69 in g_main_dispatch (context=0x7f555c0089e0) at
../glib/glib/gmain.c:3476
#24 0x7f55c556c367 in g_main_context_dispatch_unlocked
(context=0x7f555c0089e0) at ../glib/glib/gmain.c:4284
#25 g_main_context_iterate_unlocked.isra.0
(context=context@entry=0x7f555c0089e0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4349
#26 0x7f55c550c162 in g_main_context_iteration (context=0x7f555c0089e0,
may_block=1) at ../glib/glib/gmain.c:4414
#27 0x7f55c74eaf9f in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f555c019e20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#28 0x7f55c749ae74 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f555c0086c0, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#29 0x7f55a8147057 in
AdminWorker::execLoopWithTerminatingIface(QEventLoop&,
[kwin] [Bug 466380] kwin_x11 crashes in KWin::X11Window::finishCompositing() when disabling compositing
https://bugs.kde.org/show_bug.cgi?id=466380 --- Comment #16 from Mariusz Libera --- (In reply to Nate Graham from comment #15) > Mariusz, are you still able to reproduce this issue? I haven't seen this issue since the initial report, but I also was not using my linux laptop all that much lately. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 468001] New: ksysguard crash on close
https://bugs.kde.org/show_bug.cgi?id=468001
Bug ID: 468001
Summary: ksysguard crash on close
Classification: Applications
Product: ksysguard
Version: 5.22.0
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: ksysguard-b...@kde.org
Reporter: mariusz.lib...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: ---
Application: ksysguard (5.22.0)
Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.2.8-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.3 [KCrashBackend]
-- Information about the crash:
I had a game running on one monitor and ksysguard on another with the game
process name entered in the quick search filter. A closed the game and then
ksysguard and saw a notification about the crash.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: System Monitor (ksysguard), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f7fe695f90d in operator==(QString const&, QString const&) (s1=...,
s2=...) at text/qstring.cpp:3432
#7 0x7f7fe78a41ba in QLabel::setText(QString const&) (this=0x55c1d7fe0360,
text=...) at widgets/qlabel.cpp:323
#8 0x55c1d64c1902 in ()
#9 0x7f7fe8549485 in KSGRD::SensorAgent::processAnswer(char const*, int)
(this=0x55c1d7e5f160, buf=, buflen=) at
/usr/src/debug/libksysguard/libksysguard-5.27.3/ksgrd/SensorAgent.cpp:282
#10 0x7f7fe854cc12 in KSGRD::SensorShellAgent::msgRcvd()
(this=0x55c1d7e5f160) at
/usr/src/debug/libksysguard/libksysguard-5.27.3/ksgrd/SensorShellAgent.cpp:73
#11 0x7f7fe6abea71 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fff2bb62c80, r=, this=0x55c1d7e5f340, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#12 doActivate(QObject*, int, void**) (sender=0x55c1d7e5f2a0,
signal_index=15, argv=0x7fff2bb62c80) at kernel/qobject.cpp:3923
#13 0x7f7fe6a187f2 in
QProcess::readyReadStandardOutput(QProcess::QPrivateSignal) (this=, _t1=...) at .moc/moc_qprocess.cpp:367
#14 0x7f7fe6a122b6 in
QProcessPrivate::tryReadFromChannel(QProcessPrivate::Channel*)
(this=0x55c1d7f785b0, channel=0x55c1d7f786c0) at io/qprocess.cpp:1073
#15 0x7f7fe6a18efd in QProcessPrivate::_q_canReadStandardError()
(this=) at io/qprocess.cpp:1092
#16 QProcess::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)
(_o=, _c=, _id=,
_a=0x7fff2bb62e30) at .moc/moc_qprocess.cpp:210
#17 0x7f7fe6abec20 in doActivate(QObject*, int, void**)
(sender=0x55c1d7ea36d0, signal_index=3, argv=0x7fff2bb62e30) at
kernel/qobject.cpp:3935
#18 0x7f7fe6ac0924 in QSocketNotifier::activated(QSocketDescriptor,
QSocketNotifier::Type, QSocketNotifier::QPrivateSignal)
(this=this@entry=0x55c1d7ea36d0, _t1=..., _t2=, _t3=...) at
.moc/moc_qsocketnotifier.cpp:178
#19 0x7f7fe6ac0a68 in QSocketNotifier::event(QEvent*) (this=0x55c1d7ea36d0,
e=) at kernel/qsocketnotifier.cpp:302
#20 0x7f7fe7778b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55c1d7ea36d0, e=0x7fff2bb62f50) at
kernel/qapplication.cpp:3640
#21 0x7f7fe6a8df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55c1d7ea36d0, event=0x7fff2bb62f50) at
kernel/qcoreapplication.cpp:1064
#22 0x7f7fe6ad7ac6 in socketNotifierSourceDispatch(GSource*, GSourceFunc,
gpointer) (source=0x55c1d7b48390) at kernel/qeventdispatcher_glib.cpp:107
#23 0x7f7fdcb0f53b in g_main_dispatch (context=0x7f7fc4000ee0) at
../glib/glib/gmain.c:3460
#24 g_main_context_dispatch (context=0x7f7fc4000ee0) at
../glib/glib/gmain.c:4200
#25 0x7f7fdcb6c219 in g_main_context_iterate.constprop.0
(context=0x7f7fc4000ee0, block=1, dispatch=1, self=) at
../glib/glib/gmain.c:4276
#26 0x7f7fdcb0e1a2 in g_main_context_iteration (context=0x7f7fc4000ee0,
may_block=1) at ../glib/glib/gmain.c:4343
#27 0x7f7fe6ad8c6c in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x55c1d7b4b340, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#28 0x7f7fe6a866ec in
QEventLoop::exec(QFlags) (this=0x7fff2bb631d0,
flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#29 0x7f7fe6a91219 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#30 0x55c1d646d8f5 in ()
#31 0x7f7fe623c790 in __libc_start_call_main
(main=main@entry=0x55c1d646d070, argc=argc@entry=1,
argv=argv@entry=0x7fff2bb63418) at ../sysdeps/nptl/libc_start_call_main.h:58
#32 0x7f7fe623c84a in __libc_start_main_impl (main=0x55c1d646d070, argc=1,
argv=0x7fff2bb63418, init=, fini=,
rtld_fini=, stack_end=0x7fff2bb63408) at ../csu/libc-start.c:360
#33 0x55c1d646d9de in ()
[Inferior 1 (process 163920) detached]
The reporter indicates this bug may be a
[frameworks-kconfig] [Bug 422529] Put config files inside a kde subdirectory in ~/.config, ~/.local/share, and ~/.cache
https://bugs.kde.org/show_bug.cgi?id=422529 Mariusz Libera changed: What|Removed |Added CC||mariusz.lib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466380] New: kwin_x11 crashed on disabling compositing
https://bugs.kde.org/show_bug.cgi?id=466380 Bug ID: 466380 Summary: kwin_x11 crashed on disabling compositing Classification: Plasma Product: kwin Version: 5.27.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: --- Created attachment 156695 --> https://bugs.kde.org/attachment.cgi?id=156695=edit backtrace I had Firefox running and it's window froze, I thought it might be a kwin compositing being broken again, so I pressed alt+shift+f12 and kwin crashed. Operating System: Arch Linux KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 19.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: LENOVO Product Name: 81BF System Version: Lenovo ideapad 520-15IKB -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458399] google chrome window stops updating
https://bugs.kde.org/show_bug.cgi?id=458399 Mariusz Libera changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Mariusz Libera --- I haven't seen that happen in quite a while, maybe it got fixed. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 465143] New: crash after logging in
https://bugs.kde.org/show_bug.cgi?id=465143
Bug ID: 465143
Summary: crash after logging in
Classification: Applications
Product: NeoChat
Version: unspecified
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: General
Assignee: fe...@posteo.de
Reporter: mariusz.lib...@gmail.com
CC: c...@carlschwan.eu
Target Milestone: ---
Application: neochat (23.01)
Qt Version: 5.15.8
Frameworks Version: 5.102.0
Operating System: Linux 6.1.8-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.26.90 [KCrashBackend]
-- Information about the crash:
neochat crashed after logging in
Operating System: Arch Linux
KDE Plasma Version: 5.26.90
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.8-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 19.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 81BF
System Version: Lenovo ideapad 520-15IKB
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: NeoChat (neochat), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f9081127b54 in Quotient::Room::id() const () from
/usr/lib/libQuotient.so.0.7
#7 0x5632eb6f3205 in
Controller::handleNotifications(QPointer)::{lambda()#1}::operator()()
const () at /usr/src/debug/neochat/neochat-23.01.0/src/controller.cpp:168
#8 0x7f907f6be931 in QtPrivate::QSlotObjectBase::call (a=,
r=, this=, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#9 doActivate (sender=0x5632edbff8c0, signal_index=10,
argv=0x7ffe75d45b00) at kernel/qobject.cpp:3923
#10 0x7f90810fd4e7 in Quotient::BaseJob::success(Quotient::BaseJob*) ()
from /usr/lib/libQuotient.so.0.7
#11 0x7f908117a6c5 in Quotient::BaseJob::finishJob() () from
/usr/lib/libQuotient.so.0.7
#12 0x7f907f6be931 in QtPrivate::QSlotObjectBase::call (a=,
r=, this=, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate (sender=0x5632ef030970, signal_index=10,
argv=0x7ffe75d45c60) at kernel/qobject.cpp:3923
#14 0x7f9080bbb6b8 in QNetworkReplyHttpImplPrivate::finished
(this=0x5632edc8ca20) at access/qnetworkreplyhttpimpl.cpp:2280
#15 0x7f907f6b1a70 in QObject::event (this=0x5632ef030970,
e=0x7f900c1a0420) at kernel/qobject.cpp:1347
#16 0x7f9080378b5c in QApplicationPrivate::notify_helper (this=, receiver=0x5632ef030970, e=0x7f900c1a0420) at
kernel/qapplication.cpp:3640
#17 0x7f907f68de08 in QCoreApplication::notifyInternal2
(receiver=0x5632ef030970, event=0x7f900c1a0420) at
kernel/qcoreapplication.cpp:1064
#18 0x7f907f68e913 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x5632ecef5ef0) at
kernel/qcoreapplication.cpp:1821
#19 0x7f907f6d4d48 in postEventSourceDispatch (s=0x5632ed0c6280) at
kernel/qeventdispatcher_glib.cpp:277
#20 0x7f907ebec82b in g_main_dispatch (context=0x7f9074005010) at
../glib/glib/gmain.c:3454
#21 g_main_context_dispatch (context=0x7f9074005010) at
../glib/glib/gmain.c:4172
#22 0x7f907ec43cc9 in g_main_context_iterate.constprop.0
(context=0x7f9074005010, block=1, dispatch=1, self=) at
../glib/glib/gmain.c:4248
#23 0x7f907ebeb0e2 in g_main_context_iteration (context=0x7f9074005010,
may_block=1) at ../glib/glib/gmain.c:4313
#24 0x7f907f6d8b2c in QEventDispatcherGlib::processEvents
(this=0x5632ed0c1d20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#25 0x7f907f6865ac in QEventLoop::exec (this=0x7ffe75d46170, flags=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#26 0x7f907f6910d9 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#27 0x7f907fb39fe2 in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1870
#28 0x7f9080376f2a in QApplication::exec () at kernel/qapplication.cpp:2832
#29 0x5632eb64ed75 in main (argc=, argv=) at
/usr/src/debug/neochat/neochat-23.01.0/src/main.cpp:332
[Inferior 1 (process 279620) detached]
The reporter indicates this bug may be a duplicate of or related to bug 460830.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 464955] right click context menus not always showing with compositing
https://bugs.kde.org/show_bug.cgi?id=464955 --- Comment #2 from Mariusz Libera --- I was able to reproduce it on a fresh profile after disabling fading popup effect. I don't have any scripts of custom effects. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464955] New: right click context menus not always showing with compositing
https://bugs.kde.org/show_bug.cgi?id=464955 Bug ID: 464955 Summary: right click context menus not always showing with compositing Classification: Plasma Product: kwin Version: 5.26.90 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: --- When I right click on the desktop or inside some apps like Chrome, the context menus don't show until I move the mouse cursor over them or show but with a noticable delay. Can't reproduce in all apps - Firefox and Dolphin always show them but with a slight delay. With composing disabled problem goes away - context menus show up immediately. Operating System: Arch Linux KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.8-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 19.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: LENOVO Product Name: 81BF System Version: Lenovo ideapad 520-15IKB mesa: 22.3.4 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 274102] Automatically backup new unnamed/unsaved notes/files
https://bugs.kde.org/show_bug.cgi?id=274102 Mariusz Libera changed: What|Removed |Added CC||mariusz.lib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463428] plasma crashed while saving a picture using xdg portal dialog in firefox
https://bugs.kde.org/show_bug.cgi?id=463428 --- Comment #1 from Mariusz Libera --- Created attachment 154800 --> https://bugs.kde.org/attachment.cgi?id=154800=edit backtrace Another crash while using xdg portal file picker to add an attachement to this bug report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463428] New: plasma crashed while saving a picture using xdg portal dialog in firefox
https://bugs.kde.org/show_bug.cgi?id=463428 Bug ID: 463428 Summary: plasma crashed while saving a picture using xdg portal dialog in firefox Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mariusz.lib...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 154799 --> https://bugs.kde.org/attachment.cgi?id=154799=edit backtrace Operating System: Arch Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.1.1-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 19.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: LENOVO Product Name: 81BF System Version: Lenovo ideapad 520-15IKB -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463332] New: plasma crashed while deleting a widget from the desktop
https://bugs.kde.org/show_bug.cgi?id=463332 Bug ID: 463332 Summary: plasma crashed while deleting a widget from the desktop Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mariusz.lib...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 154750 --> https://bugs.kde.org/attachment.cgi?id=154750=edit backtrace I had a weather widget on the desktop. Started edit mode and deleted the widget - plasma crashed. Operating System: Arch Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.1.1-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 19.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: LENOVO Product Name: 81BF System Version: Lenovo ideapad 520-15IKB -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463287] New: plasma crashed
https://bugs.kde.org/show_bug.cgi?id=463287 Bug ID: 463287 Summary: plasma crashed Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mariusz.lib...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 154719 --> https://bugs.kde.org/attachment.cgi?id=154719=edit backtrace I opened some app and then probably clicked on the taskbar to focus one of it's windows. Operating System: Arch Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.1.0-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 19.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: LENOVO Product Name: 81BF System Version: Lenovo ideapad 520-15IKB -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463276] New: plasma crashed
https://bugs.kde.org/show_bug.cgi?id=463276 Bug ID: 463276 Summary: plasma crashed Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mariusz.lib...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 154715 --> https://bugs.kde.org/attachment.cgi?id=154715=edit backtrace I don't think I was doing anything related to plasma. Operating System: Arch Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.1.0-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 19.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: LENOVO Product Name: 81BF System Version: Lenovo ideapad 520-15IKB -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462702] Reimplement Window Actions from KHotkeys for Wayland
https://bugs.kde.org/show_bug.cgi?id=462702 Mariusz Libera changed: What|Removed |Added CC||mariusz.lib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460036] UX regression for adding terminal command/script shortcuts in kcm_keys compared to kcm_khotkeys
https://bugs.kde.org/show_bug.cgi?id=460036 Mariusz Libera changed: What|Removed |Added CC||mariusz.lib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462570] can't rebind buttons on xp-pen drawing tablet
https://bugs.kde.org/show_bug.cgi?id=462570 --- Comment #5 from Mariusz Libera --- Created attachment 154254 --> https://bugs.kde.org/attachment.cgi?id=154254=edit screenshot of xp-pen driver pen -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462570] can't rebind buttons on xp-pen drawing tablet
https://bugs.kde.org/show_bug.cgi?id=462570 --- Comment #4 from Mariusz Libera --- Created attachment 154252 --> https://bugs.kde.org/attachment.cgi?id=154252=edit screenshot of xp-pen driver keys -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462570] can't rebind buttons on xp-pen drawing tablet
https://bugs.kde.org/show_bug.cgi?id=462570 --- Comment #3 from Mariusz Libera --- Created attachment 154251 --> https://bugs.kde.org/attachment.cgi?id=154251=edit screenshot of kcm tablet -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462570] can't rebind buttons on xp-pen drawing tablet
https://bugs.kde.org/show_bug.cgi?id=462570 --- Comment #2 from Mariusz Libera --- Created attachment 154250 --> https://bugs.kde.org/attachment.cgi?id=154250=edit pentablet-keyboard -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462570] can't rebind buttons on xp-pen drawing tablet
https://bugs.kde.org/show_bug.cgi?id=462570 --- Comment #1 from Mariusz Libera --- Created attachment 154249 --> https://bugs.kde.org/attachment.cgi?id=154249=edit pentablet-mouse -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462570] New: can't rebind buttons on xp-pen drawing tablet
https://bugs.kde.org/show_bug.cgi?id=462570 Bug ID: 462570 Summary: can't rebind buttons on xp-pen drawing tablet Classification: Applications Product: systemsettings Version: master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_tablet Assignee: plasma-b...@kde.org Reporter: mariusz.lib...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 154248 --> https://bugs.kde.org/attachment.cgi?id=154248=edit pentablet I have xp-pen deco mini7 tablet with 8 buttons and a pen with 2. The tablet page in system settings shows 3 buttons available to rebind. Of those three, the first one rebinds one of the buttons on the pen, the other 2 don't seem to have any effect. In evdev the tablet appears as 3 devices: 1. /dev/input/event7: UGTABLET 6 inch PenTablet Mouse 2. /dev/input/event8: UGTABLET 6 inch PenTablet Keyboard 3. /dev/input/event9: UGTABLET 6 inch PenTablet On the system settings page it appears as 'UGTABLET 6 inch PenTablet'. It's not a hardware issue, all of the buttons work out of the box with predefined bindings, and are detected by evdev-record and libinput debug-events. Buttons on the tablet come from /dev/input/event8 and the ones on the pen from /dev/input/event9, I think. I can rebind all of the buttons using the official xp-pen app/driver - but if I run that app the buttons only work in Krita and seem to become inactive elsewhere. The other drawback of using the official app is that mapping of screens becomes all messed up, because it seems to conflicts with kde (on wayland, on x11 it works fine). If I use the official xp-pen app/driver 3 additional devices are created: 1. /dev/input/event30: XP-PEN STYLUS 2. /dev/input/event31: XP-PEN MOUSE 3. /dev/input/event256:XP-PEN ERASER kde built using kdesrc-build evemu-describe outputs in attachments -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451270] Media hotkeys don't do anything
https://bugs.kde.org/show_bug.cgi?id=451270 Mariusz Libera changed: What|Removed |Added CC||mariusz.lib...@gmail.com --- Comment #9 from Mariusz Libera --- Just noticed that global media keys stopped working for me. Restarting plasma 'systemctl --user restart plasma-plasmashell.service' fixes it. Operating System: Arch Linux KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 6.0.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 19.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: LENOVO Product Name: 81BF System Version: Lenovo ideapad 520-15IKB -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449291] zoom effect has 2 mouse cursors visible
https://bugs.kde.org/show_bug.cgi?id=449291 Mariusz Libera changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #3 from Mariusz Libera --- I still had this issue with 5.26, but then I tested a fresh user account and couldn't reproduce. So I started looking at the config files and ~/.config/kwinrc had two sections related to zoom effect - after deleting those and rebooting this issue finally went away. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 432316] When splash screen is disabled, plasma takes long time before fully started
https://bugs.kde.org/show_bug.cgi?id=432316 --- Comment #3 from Mariusz Libera --- This issue is no longer there for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458340] dragged image gets stuck in front of other windows
https://bugs.kde.org/show_bug.cgi?id=458340 --- Comment #4 from Mariusz Libera --- (In reply to Nate Graham from comment #3) > Out of curiosity, how are you using the cursor to drag the image, while also > using the cursor to click the close button? Click with left mouse button and drag the image until you see a thumbnail appear and then let go left mouse button - the image thumbnail stays with the cursor. It actually is weird because the thumbnail stays within the nomacs window and can't be dropped that way on to other apps. Dragging works properly with left mouse + ctrl. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458340] dragged image gets stuck in front of other windows
https://bugs.kde.org/show_bug.cgi?id=458340 --- Comment #2 from Mariusz Libera --- (In reply to Nate Graham from comment #1) > Wayland or X11? > > How are you quitting it? Ctrl+Q with one hand while the other hand drags it > using a mouse/touchpad? X11, I didn't try it on wayland. Both clicking on the close button and alt+f4 have the same effect, but what I just noticed is that the nomacs process is still running in the background when this bug happens and if you terminate it the leftover thumbnail disappears - so I don't know whether it's kwin or nomacs bug, which of the two is responsible for ending drag and drop operation in this case. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458399] New: google chrome window stops updating
https://bugs.kde.org/show_bug.cgi?id=458399 Bug ID: 458399 Summary: google chrome window stops updating Product: kwin Version: 5.25.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: --- Created attachment 151643 --> https://bugs.kde.org/attachment.cgi?id=151643=edit about:gpu from chrome Sometimes Google Chrome window stops updating - I've noticed this a couple times while watching some youtube videos. This was in the log while it happened: sie 27 19:55:23 ideapad520 kwin_x11[771]: kwin_core: XCB error: 14 (BadIDChoice), sequence: 42990, resource id: 14830549, major code: 138 (XFIXES), minor code: 5 (CreateRegion) sie 27 19:55:23 ideapad520 kwin_x11[771]: kwin_core: XCB error: 140 (Unknown), sequence: 42991, resource id: 14830549, major code: 143 (DAMAGE), minor code: 3 (Subtract) sie 27 19:55:23 ideapad520 kwin_x11[771]: kwin_core: XCB error: 140 (BadRegion), sequence: 42992, resource id: 14830549, major code: 138 (XFIXES), minor code: 19 (FetchRegion) sie 27 19:55:23 ideapad520 kwin_x11[771]: kwin_core: XCB error: 140 (BadRegion), sequence: 42993, resource id: 14830549, major code: 138 (XFIXES), minor code: 10 (DestroyRegion) Stopping and starting compositing fixes it. sie 27 19:57:57 ideapad520 kwin_x11[771]: OpenGL vendor string: Intel sie 27 19:57:57 ideapad520 kwin_x11[771]: OpenGL renderer string: Mesa Intel(R) UHD Graphics 620 (KBL GT2) sie 27 19:57:57 ideapad520 kwin_x11[771]: OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.1.6 sie 27 19:57:57 ideapad520 kwin_x11[771]: OpenGL shading language version string: 4.60 sie 27 19:57:57 ideapad520 kwin_x11[771]: Driver: Intel sie 27 19:57:57 ideapad520 kwin_x11[771]: GPU class: Kaby Lake sie 27 19:57:57 ideapad520 kwin_x11[771]: OpenGL version: 4.6 sie 27 19:57:57 ideapad520 kwin_x11[771]: GLSL version: 4.60 sie 27 19:57:57 ideapad520 kwin_x11[771]: Mesa version: 22.1.6 sie 27 19:57:57 ideapad520 kwin_x11[771]: X server version: 1.21.1 sie 27 19:57:57 ideapad520 kwin_x11[771]: Linux kernel version: 5.19.3 sie 27 19:57:57 ideapad520 kwin_x11[771]: Requires strict binding: yes sie 27 19:57:57 ideapad520 kwin_x11[771]: GLSL shaders: yes sie 27 19:57:57 ideapad520 kwin_x11[771]: Texture NPOT support: yes sie 27 19:57:57 ideapad520 kwin_x11[771]: Virtual Machine: no sie 27 19:57:57 ideapad520 kwin_x11[771]: QObject::connect(KWin::InputMethod, KWin::EffectsHandlerImpl): invalid nullptr parameter sie 27 19:57:57 ideapad520 kwin_x11[771]: BlurConfig::instance called after the first use - ignoring sie 27 19:57:57 ideapad520 kwin_x11[771]: ZoomConfig::instance called after the first use - ignoring sie 27 19:57:57 ideapad520 kwin_x11[771]: WindowViewConfig::instance called after the first use - ignoring sie 27 19:57:57 ideapad520 kwin_x11[771]: SlidingPopupsConfig::instance called after the first use - ignoring sie 27 19:57:57 ideapad520 kwin_x11[771]: OverviewConfig::instance called after the first use - ignoring sie 27 19:57:57 ideapad520 kwin_x11[771]: MagicLampConfig::instance called after the first use - ignoring sie 27 19:57:57 ideapad520 kwin_x11[771]: KscreenConfig::instance called after the first use - ignoring sie 27 19:57:57 ideapad520 kwin_x11[771]: DesktopGridConfig::instance called after the first use - ignoring -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458340] New: dragged image gets stuck in front of other windows
https://bugs.kde.org/show_bug.cgi?id=458340 Bug ID: 458340 Summary: dragged image gets stuck in front of other windows Product: kwin Version: 5.25.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. open an image file in nomacs - https://nomacs.org/ 2. grab the image in nomacs' window to initiate drag and drop 3. close nomacs without dropping the image OBSERVED RESULT A thumbnail of the image gets stuck in front of all other windows and it can't be removed. EXPECTED RESULT thumbnail gets discarded when nomacs quits -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449291] zoom effect has 2 mouse cursors visible
https://bugs.kde.org/show_bug.cgi?id=449291 --- Comment #2 from Mariusz Libera --- Still an issue in plasma 5.25.4. Here is a screen recording for illustration: https://streamable.com/wko1bz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443076] item under mouse pointer is launched instead of the first search result
https://bugs.kde.org/show_bug.cgi?id=443076 Mariusz Libera changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Version|5.22.90 |5.25.4 --- Comment #6 from Mariusz Libera --- This is broken again. 5.25.4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457933] system settings crashed trying to open autostart page
https://bugs.kde.org/show_bug.cgi?id=457933 --- Comment #2 from Mariusz Libera --- (In reply to Nate Graham from comment #1) > Thank you for the bug report! Unfortunately the backtrace is incomplete and > missing debug symbols for the following lines that we need to figure out > exactly what's going wrong: > > > #28 0x7fe7802d534c in () at > > /usr/lib/qt/plugins/systemsettingsview/systemsettings_sidebar_mode.so > > #29 0x7fe7802d71ed in () at > > /usr/lib/qt/plugins/systemsettingsview/systemsettings_sidebar_mode.so > > #30 0x7fe7802d7e43 in () at > > /usr/lib/qt/plugins/systemsettingsview/systemsettings_sidebar_mode.so > > #31 0x7fe787676994 in () at /usr/lib/libQt5Qml.so.5 > > #32 0x7fe78757a96c in () at /usr/lib/libQt5Qml.so.5 > > Could you please install debug symbols, reproduce the crash, and attach a > new symbolicated backtrace? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports > > Thanks again! Sorry about that, I thought that the kde crash handling app downloads the symbols automatically now and didn't check the result. #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7fe7890a1543 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x7fe789051998 in __GI_raise (sig=6) at ../sysdeps/posix/raise.c:26 #3 0x7fe78aeae868 in KCrash::defaultCrashHandler(int) (sig=6) at /usr/src/debug/kcrash-5.97.0/src/kcrash.cpp:633 #4 0x7fe789051a40 in () at /usr/lib/libc.so.6 #5 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #6 0x7fe7890a1543 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #7 0x7fe789051998 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7fe78903b53d in __GI_abort () at abort.c:79 #9 0x7fe78909567e in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fe7891b41ea "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:155 #10 0x7fe7891305da in __GI___fortify_fail (msg=msg@entry=0x7fe7891b41d2 "stack smashing detected") at fortify_fail.c:26 #11 0x7fe7891305a6 in __stack_chk_fail () at stack_chk_fail.c:24 #12 0x7fe78757192b in loadProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData const&) (v4=0x7fe77c0076d0, object=, property=) at /usr/src/debug/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:207 #13 0x7fe787578e8b in QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) (object=0x7fe75c173648, engine=0x7fe77c0076d0, lookup=0x558f8193c510) at /usr/src/debug/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:883 #14 0x7fe78758dbea in QV4::Moth::VME::interpret(QV4::CppStackFrame*, QV4::ExecutionEngine*, char const*) (frame=0x7ffd5cfe2b10, engine=0x7fe77c0076d0, code=0x7fe74f1153fa "") at /usr/src/debug/qtdeclarative/src/qml/jsruntime/qv4vme_moth.cpp:641 #15 0x7fe787597e34 in QV4::Moth::VME::exec(QV4::CppStackFrame*, QV4::ExecutionEngine*) (frame=, engine=) at /usr/src/debug/qtdeclarative/src/qml/jsruntime/qv4vme_moth.cpp:466 #16 0x7fe78753b7f6 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) (this=, thisObject=, argv=, argc=, context=) at /usr/src/debug/qtdeclarative/src/qml/jsruntime/qv4function.cpp:69 #17 0x7fe78768fe6d in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) (this=0x558f81981260, callData=0x7fe75c173608, isUndefined=0x0) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmljavascriptexpression.cpp:212 #18 0x7fe787653121 in QQmlBoundSignalExpression::evaluate(void**) (this=, a=) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmlboundsignal.cpp:224 #19 0x7fe78765409c in QQmlBoundSignal_callback(QQmlNotifierEndpoint*, void**) (a=0x0, e=0x558f819842d0) at ../../include/QtQml/5.15.5/QtQml/private/../../../../../../qtdeclarative/src/qml/qml/qqmlboundsignalexpressionpointer_p.h:69 #20 QQmlBoundSignal_callback(QQmlNotifierEndpoint*, void**) (e=0x558f819842d0, a=0x0) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmlboundsignal.cpp:341 #21 0x7fe7876768cf in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) (endpoint=, a=0x0) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmlnotifier.cpp:104 #22 0x7fe7898bce6d in doActivate(QObject*, int, void**) (sender=0x558f81981bd0, signal_index=76, argv=0x0) at kernel/qobject.cpp:3778 #23 0x7fe787cf56d9 in QQuickItemViewPrivate::applyModelChanges(QQuickItemViewPrivate::ChangeResult*, QQuickItemViewPrivate::ChangeResult*) (totalRemovalResult=0x7ffd5cfe4840, totalInsertionResult=0x7ffd5cfe4870, this=0x558f81981c90) at /usr/src/debug/qtdeclarative/src/quick/items/qquickitemview.cpp:2130 #24 QQuickItemView
[systemsettings] [Bug 457933] New: system settings crashed trying to open autostart page
https://bugs.kde.org/show_bug.cgi?id=457933 Bug ID: 457933 Summary: system settings crashed trying to open autostart page Product: systemsettings Version: 5.25.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: --- Application: systemsettings (5.25.4) Qt Version: 5.15.5 Frameworks Version: 5.97.0 Operating System: Linux 5.19.1-arch2-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: 1. open system setttings 2. search for 'autostart' 3. click the 'autostart' search result 4. crash when I tried it again I couldn't reproduce the crash The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Settings (systemsettings), signal: Aborted [KCrash Handler] #4 0x7fe7890a14dc in () at /usr/lib/libc.so.6 #5 0x7fe789051998 in raise () at /usr/lib/libc.so.6 #6 0x7fe78903b53d in abort () at /usr/lib/libc.so.6 #7 0x7fe78909567e in () at /usr/lib/libc.so.6 #8 0x7fe7891305da in __fortify_fail () at /usr/lib/libc.so.6 #9 0x7fe7891305a6 in () at /usr/lib/libc.so.6 #10 0x7fe78757192b in () at /usr/lib/libQt5Qml.so.5 #11 0x7fe787578e8b in QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) () at /usr/lib/libQt5Qml.so.5 #12 0x7fe78758dbea in () at /usr/lib/libQt5Qml.so.5 #13 0x7fe787597e34 in () at /usr/lib/libQt5Qml.so.5 #14 0x7fe78753b7f6 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () at /usr/lib/libQt5Qml.so.5 #15 0x7fe78768fe6d in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () at /usr/lib/libQt5Qml.so.5 #16 0x7fe787653121 in QQmlBoundSignalExpression::evaluate(void**) () at /usr/lib/libQt5Qml.so.5 #17 0x7fe78765409c in () at /usr/lib/libQt5Qml.so.5 #18 0x7fe7876768cf in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /usr/lib/libQt5Qml.so.5 #19 0x7fe7898bce6d in () at /usr/lib/libQt5Core.so.5 #20 0x7fe787cf56d9 in () at /usr/lib/libQt5Quick.so.5 #21 0x7fe787cf6eb9 in QQuickItemView::setCurrentIndex(int) () at /usr/lib/libQt5Quick.so.5 #22 0x7fe78763c0c2 in () at /usr/lib/libQt5Qml.so.5 #23 0x7fe787691915 in () at /usr/lib/libQt5Qml.so.5 #24 0x7fe78769908e in () at /usr/lib/libQt5Qml.so.5 #25 0x7fe787698b73 in QQmlBinding::update(QFlags) () at /usr/lib/libQt5Qml.so.5 #26 0x7fe7876768cf in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /usr/lib/libQt5Qml.so.5 #27 0x7fe7898bce6d in () at /usr/lib/libQt5Core.so.5 #28 0x7fe7802d534c in () at /usr/lib/qt/plugins/systemsettingsview/systemsettings_sidebar_mode.so #29 0x7fe7802d71ed in () at /usr/lib/qt/plugins/systemsettingsview/systemsettings_sidebar_mode.so #30 0x7fe7802d7e43 in () at /usr/lib/qt/plugins/systemsettingsview/systemsettings_sidebar_mode.so #31 0x7fe787676994 in () at /usr/lib/libQt5Qml.so.5 #32 0x7fe78757a96c in () at /usr/lib/libQt5Qml.so.5 #33 0x7fe78757bf6d in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () at /usr/lib/libQt5Qml.so.5 #34 0x7fe78758e033 in () at /usr/lib/libQt5Qml.so.5 #35 0x7fe787597e34 in () at /usr/lib/libQt5Qml.so.5 #36 0x7fe78753b7f6 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () at /usr/lib/libQt5Qml.so.5 #37 0x7fe78768fe6d in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () at /usr/lib/libQt5Qml.so.5 #38 0x7fe787653121 in QQmlBoundSignalExpression::evaluate(void**) () at /usr/lib/libQt5Qml.so.5 #39 0x7fe78765409c in () at /usr/lib/libQt5Qml.so.5 #40 0x7fe7876768cf in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /usr/lib/libQt5Qml.so.5 #41 0x7fe7898bce6d in () at /usr/lib/libQt5Core.so.5 #42 0x7fe782fb8a5a in QQuickAbstractButtonPrivate::handleRelease(QPointF const&) () at /usr/lib/libQt5QuickTemplates2.so.5 #43 0x7fe782fd3ab9 in QQuickControl::mouseReleaseEvent(QMouseEvent*) () at /usr/lib/libQt5QuickTemplates2.so.5 #44 0x7fe787c3c1c9 in QQuickItem::event(QEvent*) () at /usr/lib/libQt5Quick.so.5 #45 0x7fe78a578b3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #46 0x7fe78988cad8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #47 0x7fe787c4cd93 in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () at /usr/lib/libQt5Quick.so.5 #48 0x7fe787c4d7f2 in QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () at /usr/lib/libQt5Quick.so.5 #49 0x7fe789d55b45 in
[systemsettings] [Bug 457928] New: flat acceleration profile not honored after mouse unplugged and plugged in again
https://bugs.kde.org/show_bug.cgi?id=457928 Bug ID: 457928 Summary: flat acceleration profile not honored after mouse unplugged and plugged in again Product: systemsettings Version: 5.25.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_mouse Assignee: plasma-b...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. plug in a mouse 1. set Acceleration profile to flat 2. xinput shows "libinput Accel Profile Enabled (353): 0, 1" 3. unplug the mouse 4. plug it in again OBSERVED RESULT System settings page still shows 'Flat' as selected option but xinput now shows "libinput Accel Profile Enabled (353): 1, 0" You have to set it to Adaptive , click apply and then set it to Flat again and click apply again. EXPECTED RESULT Mouse is set to the acceleration profile selected in the settings page. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443221] 'sleep' sometimes fails to put laptop to sleep
https://bugs.kde.org/show_bug.cgi?id=443221 --- Comment #6 from Mariusz Libera --- (In reply to Nate Graham from comment #5) > A lot has changed since then. Can anyone still reproduce this issue in > Plasma 5.25? Tried it 10 time and it worked every time. I'm on Plasma 5.25.2, don't know when it got fixed - I had this logout dialog disabled because of this bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449291] New: zoom effect has 2 mouse cursors visible
https://bugs.kde.org/show_bug.cgi?id=449291 Bug ID: 449291 Summary: zoom effect has 2 mouse cursors visible Product: kwin Version: 5.23.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: --- Activate 'Zoom' effect. There are 2 mouse cursors. The more you zoom in - the further appart they are. Operating System: Arch Linux KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.3-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 19.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448345] New: crash when unmounting external USB drive
https://bugs.kde.org/show_bug.cgi?id=448345 Bug ID: 448345 Summary: crash when unmounting external USB drive Product: plasmashell Version: 5.23.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: 1.0 Right clicked on my external USB drive in dolphin and 'Safely Remove'. Plasma crashed. sty 13 04:34:43 plasmashell[1177]: file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/DeviceItem.qml:158:5: Unable to assign [undefined] to QString sty 13 04:34:43 plasmashell[1177]: 25 -- exe=/usr/bin/plasmashell sty 13 04:34:43 plasmashell[1177]: 13 -- platform=xcb sty 13 04:34:43 plasmashell[1177]: 11 -- display=:0 sty 13 04:34:43 plasmashell[1177]: 20 -- appname=plasmashell sty 13 04:34:43 plasmashell[1177]: 17 -- apppath=/usr/bin sty 13 04:34:43 plasmashell[1177]: 10 -- signal=11 sty 13 04:34:43 plasmashell[1177]: 9 -- pid=1177 sty 13 04:34:43 plasmashell[1177]: 18 -- appversion=5.23.5 sty 13 04:34:43 plasmashell[1177]: 19 -- programname=Plasma sty 13 04:34:43 plasmashell[1177]: 31 -- bugaddress=sub...@bugs.kde.org sty 13 04:34:43 plasmashell[1177]: 12 -- startupid=0 sty 13 04:34:43 plasmashell[1177]: KCrash: crashing... crashRecursionCounter = 2 sty 13 04:34:43 plasmashell[1177]: KCrash: Application Name = plasmashell path = /usr/bin pid = 1177 sty 13 04:34:43 plasmashell[1177]: KCrash: Arguments: /usr/bin/plasmashell --no-respawn sty 13 04:34:43 plasmashell[1177]: XXX: resource creation failed sty 13 04:34:43 plasmashell[1177]: Unable to start Dr. Konqi sty 13 04:34:43 plasmashell[1177]: Re-raising signal for core dump handling. sty 13 04:34:43 kded5[1094]: Service "org.kde.StatusNotifierHost-1177" unregistered sty 13 04:34:43 kwin_x11[1095]: QMetaProperty::read: Unable to handle unregistered datatype 'KWin::SessionState' for property 'KWin::EffectsHandlerImplX11::sessionState' sty 13 04:34:43 kwin_x11[1095]: QMetaProperty::read: Unable to handle unregistered datatype 'KWin::SessionState' for property 'KWin::EffectsHandlerImplX11::sessionState' sty 13 04:34:43 kwin_x11[1095]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 53812, resource id: 23068759, major code: 15 (QueryTree), minor code: 0 sty 13 04:34:43 kwin_x11[1095]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 53914, resource id: 23068697, major code: 15 (QueryTree), minor code: 0 sty 13 04:34:43 kwin_x11[1095]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 54003, resource id: 23068703, major code: 15 (QueryTree), minor code: 0 sty 13 04:34:43 kwin_x11[1095]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 54091, resource id: 23068784, major code: 15 (QueryTree), minor code: 0 sty 13 04:34:43 kwin_x11[1095]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 54178, resource id: 23068735, major code: 15 (QueryTree), minor code: 0 sty 13 04:34:57 kwin_x11[1095]: kwin_core: Failed to focus 0x2c7 (error 8) sty 13 04:35:23 systemd[1051]: plasma-plasmashell.service: State 'stop-sigterm' timed out. Killing. sty 13 04:35:23 systemd[1051]: plasma-plasmashell.service: Killing process 1177 (plasmashell) with signal SIGKILL. sty 13 04:35:23 systemd[1051]: plasma-plasmashell.service: Killing process 1181 (QXcbEventQueue) with signal SIGKILL. sty 13 04:35:23 systemd[1051]: plasma-plasmashell.service: Killing process 1182 (QDBusConnection) with signal SIGKILL. sty 13 04:35:23 systemd[1051]: plasma-plasmashell.service: Killing process 1186 (n/a) with signal SIGKILL. sty 13 04:35:23 systemd[1051]: plasma-plasmashell.service: Killing process 1187 (plasmashel:sh0) with signal SIGKILL. sty 13 04:35:23 systemd[1051]: plasma-plasmashell.service: Killing process 1188 (plasmashel:sh1) with signal SIGKILL. sty 13 04:35:23 systemd[1051]: plasma-plasmashell.service: Killing process 1189 (plasmashel:sh2) with signal SIGKILL. sty 13 04:35:23 systemd[1051]: plasma-plasmashell.service: Killing process 1190 (plasmashel:sh3) with signal SIGKILL. sty 13 04:35:23 systemd[1051]: plasma-plasmashell.service: Killing process 1191 (plasmashel:sh4) with signal SIGKILL. sty 13 04:35:23 systemd[1051]: plasma-plasmashell.service: Killing process 1192 (plasmashel:sh5) with signal SIGKILL. sty 13 04:35:23 systemd[1051]: plasma-plasmashell.service: Killing process 1234 (n/a) with signal SIGKILL. sty 13 04:35:23 systemd[1051]: plasma-plasmashell.service: Killing process 1255 (n/a) with signal SIGKILL. sty 13 04:35:23 systemd[1051]: plasma-plasmashell.service: Killing process 1256 (n/a) with signal SIGKILL. sty 13 04:35:23 systemd[1051]: plasma-plasmashell.service: Killing process 1257 (n/a) with signal SIGKILL. sty 13 04:35:23 systemd[1051]: plasma-plasmashell.service: Killing process 1258 (n/a) with signal SIGKILL.
[systemsettings] [Bug 354109] Custom shortcuts: Window Data autodetect (conditions > new > active window) removes mouse button function
https://bugs.kde.org/show_bug.cgi?id=354109 Mariusz Libera changed: What|Removed |Added CC||mariusz.lib...@gmail.com --- Comment #9 from Mariusz Libera --- Still an issue in plasma 5.23.4. Detecting window properties works in "Window Rules" but is broken in "Custom Shortcuts". Maybe move the functionality of executing a custom command on window events to "Window Rules"? I was surprised to find it in the shortcut section of System Setting. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417146] compositing disabled on connecting/disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=417146 Mariusz Libera changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #19 from Mariusz Libera --- Kwin in plasma 5.23 definitely fixed this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443221] 'sleep' sometimes fails to put laptop to sleep
https://bugs.kde.org/show_bug.cgi?id=443221 Mariusz Libera changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443221] 'sleep' sometimes fails to put laptop to sleep
https://bugs.kde.org/show_bug.cgi?id=443221 --- Comment #2 from Mariusz Libera --- (In reply to David Edmundson from comment #1) > Please test with systemctl suspend As I wrote in the report 'systemctl suspend' works every time. Is there something else I can do to help debug this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443221] New: 'sleep' sometimes fails to put laptop to sleep
https://bugs.kde.org/show_bug.cgi?id=443221 Bug ID: 443221 Summary: 'sleep' sometimes fails to put laptop to sleep Product: plasmashell Version: 5.22.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mariusz.lib...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 STEPS TO REPRODUCE 1. Press the power button. 2. Select 'sleep' on the logout screen. OBSERVED RESULT Sometimes the logout screen disappears and nothing happens. EXPECTED RESULT Laptop goes to sleep. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.7-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 19.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION This started to happen with plasma 5.22 or one of its point releases and continues with the 5.23 beta. 'systemctl suspend' works each time. Logs when selecting 'sleep' failed 4 times in a row: paź 02 13:09:56 ideapad520 systemd-logind[402]: Power key pressed. paź 02 13:09:57 ideapad520 systemd[985]: Started dbus-:1.2-org.kde.LogoutPrompt@12.service. paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: :406:376: Could not add child element to parent element because the types are incorrect. paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: :407:130: Could not add child element to parent element because the types are incorrect. paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: :408:130: Could not add child element to parent element because the types are incorrect. paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: :408:393: Could not add child element to parent element because the types are incorrect. paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: :409:130: Could not add child element to parent element because the types are incorrect. paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: :410:129: Could not add child element to parent element because the types are incorrect. paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: :411:129: Could not add child element to parent element because the types are incorrect. paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: :412:129: Could not add child element to parent element because the types are incorrect. paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: :413:129: Could not add child element to parent element because the types are incorrect. paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: :413:379: Could not add child element to parent element because the types are incorrect. paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: :413:631: Could not add child element to parent element because the types are incorrect. paź 02 13:09:58 ideapad520 kwin_x11[1047]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 57557, resource id: 90177582, major code: 18 (ChangeProperty), minor code: 0 paź 02 13:09:58 ideapad520 systemd[985]: dbus-:1.2-org.kde.LogoutPrompt@12.service: Main process exited, code=exited, status=1/FAILURE paź 02 13:09:58 ideapad520 systemd[985]: dbus-:1.2-org.kde.LogoutPrompt@12.service: Failed with result 'exit-code'. paź 02 13:10:02 ideapad520 systemd-logind[402]: Power key pressed. paź 02 13:10:02 ideapad520 systemd[985]: Started dbus-:1.2-org.kde.LogoutPrompt@13.service. paź 02 13:10:04 ideapad520 kwin_x11[1047]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 58982, resource id: 90177582, major code: 18 (ChangeProperty), minor code: 0 paź 02 13:10:04 ideapad520 systemd[985]: dbus-:1.2-org.kde.LogoutPrompt@13.service: Main process exited, code=exited, status=1/FAILURE paź 02 13:10:04 ideapad520 systemd[985]: dbus-:1.2-org.kde.LogoutPrompt@13.service: Failed with result 'exit-code'. paź 02 13:10:45 ideapad520 kioslave5[258408]: Qt: Session management error: networkIdsList argument is NULL paź 02 13:10:47 ideapad520 kwin_x11[1047]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 65415, resource id: 50333889, major code: 3 (GetWindowAttributes), minor code: 0 paź 02 13:10:47 ideapad520 kwin_x11[1047]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 65416, resource id: 50333889, major code: 14 (GetGeometry), minor code: 0 paź 02 13:11:33 ideapad520 systemd-logind[402]: Power key pressed. paź 02 13:11:33 ideapad520 systemd[985]: Started dbus-:1.2-org.kde.LogoutPrompt@14.service. paź 02 13:11:34 ideapad520 kwin_x11[1047]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 8347, resource id: 98566190, major code: 18
[plasmashell] [Bug 443077] New: launcher can get maximized or tiled
https://bugs.kde.org/show_bug.cgi?id=443077 Bug ID: 443077 Summary: launcher can get maximized or tiled Product: plasmashell Version: 5.22.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: mariusz.lib...@gmail.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 STEPS TO REPRODUCE 1. Press [meta] to open the launcher. 2. Press key shortcut to maximize or tile a window. OBSERVED RESULT Launcher window is maximized/tiled. EXPECTED RESULT Launcher window is unaffected. ADDITIONAL INFORMATION Apparently you can also drag and resize it lika a normal window. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443076] New: item under mouse pointer is launched instead of the first search result
https://bugs.kde.org/show_bug.cgi?id=443076 Bug ID: 443076 Summary: item under mouse pointer is launched instead of the first search result Product: plasmashell Version: 5.22.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: mariusz.lib...@gmail.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 STEPS TO REPRODUCE 1. Position the mouse pointer where the launcher window will pop up. 2. Don't move the mouse. 3. Press [meta] to open the launcher. 4. Type something to search. 5. Press [enter] to launch the first result on the list. OBSERVED RESULT Item under the mouse pointer is highlighted and launched. EXPECTED RESULT First result of the search is highlighted and launched. ADDITIONAL INFORMATION This used to work correctly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417146] compositing disabled on connecting/disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=417146 --- Comment #18 from Mariusz Libera --- I can't reproduce it with 5.22.90, seems to be fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442615] New: shortcut 'window to next screen' doesn't work with maximized windows
https://bugs.kde.org/show_bug.cgi?id=442615 Bug ID: 442615 Summary: shortcut 'window to next screen' doesn't work with maximized windows Product: kwin Version: 5.22.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: --- I have a keyboard shortcut set for the action 'window to next screen', it moves non-maximized and fullscreen windows from one screen to the other, but does nothing when the focused window is maximized. It's a regresion - this functionality worked as expected in kwin 5.22. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439498] Plasma crashes when flash drive is unmounted and removed
https://bugs.kde.org/show_bug.cgi?id=439498 Mariusz Libera changed: What|Removed |Added CC||mariusz.lib...@gmail.com --- Comment #3 from Mariusz Libera --- Happens to me too. Unmounting external USB HDD either from Dolphin or the plasmoid crashes Plasma. It does not crash when unmounting a pendrive. Operating System: Arch Linux KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.6-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417146] compositing disabled on connecting/disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=417146 --- Comment #17 from Mariusz Libera --- (In reply to Vlad Zahorodnii from comment #15) > Created attachment 136150 [details] > patch > > Also, it will be great if somebody could apply this patch and check if kwin > successfully queries GL_MAX_VIEWPORT_DIMS. "Failed to query GL_MAX_VIEWPORT_DIMS" is not printed out, only "Suspending compositing because viewport limits are not met". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417146] compositing disabled on connecting/disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=417146 --- Comment #16 from Mariusz Libera --- (In reply to Vlad Zahorodnii from comment #14) > Created attachment 136147 [details] > potential fix > > I wonder if it's related to opengl context. Does the attached patch fix the > issue? No, it doesn't. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 432316] When splash screen is disabled, plasma takes long time before fully started
https://bugs.kde.org/show_bug.cgi?id=432316 Mariusz Libera changed: What|Removed |Added CC||mariusz.lib...@gmail.com --- Comment #1 from Mariusz Libera --- I did experience the same thing but only after enabling systemd startup: kwriteconfig5 --file startkderc --group General --key systemdBoot true additionaly powerdevil stopped intercepring power button events so pressing the power button just shut down my laptop instead of displaying the logout dialog. Enabling splash fixed the deylayed autostart but powerdevil still didn't work as expected so I had to go back to the non systemd startup: kwriteconfig5 --file startkderc --group General --key systemdBoot false Operating System: Arch Linux KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-arch1-1 OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 416353] Maximize button is miscolored when maximized
https://bugs.kde.org/show_bug.cgi?id=416353 --- Comment #9 from Mariusz Libera --- I'm no longer experiencing this bug. I think I fixed it at some point by deleting old config files ~/.config/gtk-3.0 so you may retry with a fresh user profile. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 432643] New: kdeconnect slowing down system shutdown
https://bugs.kde.org/show_bug.cgi?id=432643 Bug ID: 432643 Summary: kdeconnect slowing down system shutdown Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: mariusz.lib...@gmail.com Target Milestone: --- Created attachment 135506 --> https://bugs.kde.org/attachment.cgi?id=135506=edit journalctl -b -1 --user Shut down and restart in Plasma is slower by about 8-10 seconds if kdeconnect is running. Removing kdeconnect fixes the problem. Attached log indicates kdeconnect is timing out. SOFTWARE/OS VERSIONS kdeconnect 20.12.2 Operating System: Arch Linux KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.14-arch1-1 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417146] compositing disabled on connecting/disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=417146 --- Comment #12 from Mariusz Libera --- (In reply to Martin Sandsmark from comment #10) > Created attachment 135194 [details] > patch ish > > Can't get kwin to build (it apparently depends on -git versions of pretty > much everything), so I can't test this patch myself, but just to show what > I'm thinking This one works - can't reproduce the issue anymore. However it produces a small visual glitch - windows textures get stretched and then shrunk back when disconnecting the monitor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417146] compositing disabled on connecting/disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=417146 --- Comment #11 from Mariusz Libera --- (In reply to Martin Sandsmark from comment #9) > Created attachment 135193 [details] > Just testing > > Gave up trying to diff with kwinft, it's missing too many changes. > > But could you test this patch? It should show what the issue is at least. > > But looking at the stack traces it seems to fail when it is called directly, > and succeeds when going via a timer. So I assume there's some bug in some > driver that makes it necessary to delay the query for some arbitrary amount > of time (to fix it "properly"). I've tested this patch and at first it seemed to work - I couldn't reproduce the issue, but when I gave it another run with with QT_LOGGING_RULES="kwin_*.debug=true" - strangely, the issue returned. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417146] compositing disabled on connecting/disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=417146 Mariusz Libera changed: What|Removed |Added Version|5.17.90 |5.20.90 --- Comment #7 from Mariusz Libera --- I was hoping that reworked compositing in the upcoming kwin will fix this issue, so I gave kwin 5.20.90 a try - still the same, unfortunately. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417146] compositing disabled on connecting/disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=417146 --- Comment #5 from Mariusz Libera --- I can't reproduce this bug using kwinft/disman/kdisplay. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 418612] Gwenview opens randomly the thumbnail bar as a new window
https://bugs.kde.org/show_bug.cgi?id=418612 Mariusz Libera changed: What|Removed |Added CC||mariusz.lib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422678] New: battery indicator not showing up, widget shows no batteries attached
https://bugs.kde.org/show_bug.cgi?id=422678 Bug ID: 422678 Summary: battery indicator not showing up, widget shows no batteries attached Product: Powerdevil Version: 5.19.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: --- SUMMARY After update to plasma 5.19 battery indicator is not showing up. Widget added manually to the panel show no batteries - they are visible in KInfoCenter. Power management settings seem to work - at least brightness is adjusted if I unplug the power, the sound effect is plays, icon of the manually added widget changes. Process org_kde_powerdevil is running. Operating System: Arch Linux KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 5.7.1-arch1-1 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421213] Regression: Can no longer copy/move files into a symlinked folder
https://bugs.kde.org/show_bug.cgi?id=421213 Mariusz Libera changed: What|Removed |Added CC||mariusz.lib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 196998] Konsole should reflow the text when resizing
https://bugs.kde.org/show_bug.cgi?id=196998 Mariusz Libera changed: What|Removed |Added CC||mariusz.lib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420637] New: allow using apps other than kompare for diff functionality
https://bugs.kde.org/show_bug.cgi?id=420637 Bug ID: 420637 Summary: allow using apps other than kompare for diff functionality Product: dolphin Version: 20.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: mariusz.lib...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin has a diff toolbar button available but it works only with kompare. I prefer using Meld, some other people might prefer some other tools. Provide some selection mechanism, or fallback to a list of known comparison tools if kompare is not installed. Currently I'm using a dolphin with this patch: https://aur.archlinux.org/cgit/aur.git/tree/dolphin-meld.patch?h=dolphin-meld but a more general solution would probably be required. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417146] compositing disabled on connecting/disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=417146 --- Comment #3 from Mariusz Libera --- Created attachment 126331 --> https://bugs.kde.org/attachment.cgi?id=126331=edit backtrace when glGetIntegerv(GL_MAX_VIEWPORT_DIMS, limit) succeeds -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417146] compositing disabled on connecting/disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=417146 --- Comment #2 from Mariusz Libera --- Created attachment 126330 --> https://bugs.kde.org/attachment.cgi?id=126330=edit backtrace when glGetIntegerv(GL_MAX_VIEWPORT_DIMS, limit) fails -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417146] compositing disabled on connecting/disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=417146 --- Comment #1 from Mariusz Libera --- So I got curious and started debugging this. Adding those 2 lines: qCDebug(KWIN_OPENGL) << "viewport-limit-width:" << limit[0] << "\tviewport-limit-height:" << limit[1]; qCDebug(KWIN_OPENGL) << "size-width:" << size.width() << "\tsize-height:" << size.height(); in function SceneOpenGL::viewportLimitsMatched right after this call: glGetIntegerv(GL_MAX_VIEWPORT_DIMS, limit); somehow eliminated the race condition and I could no longer reproduce the issue. However the debug output sometimes showed expected values: kwin_scene_opengl: viewport-limit-width: 32768 viewport-limit-height: 32768 and other times something odd: kwin_scene_opengl: viewport-limit-width: 1023711040 viewport-limit-height: 21890 Anyway, it stopped triggering the if condition: if (limit[0] < size.width() || limit[1] < size.height()) When I moved those debug statements inside the if block, the problem returned. Here is the output of the debug statements: kwin_scene_opengl: viewport-limit-width: -40918160 viewport-limit-height: 22066 kwin_scene_opengl: size-width: 3840 size-height: 1080 So it seems that glGetIntegerv(GL_MAX_VIEWPORT_DIMS, limit) sometimes fails for some reason, leaving garbage values. I'm not an OpenGL expert so I have no idea why it would fail. Given that this viewport limit check is not executed at all in Wayland, is it really needed? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417146] New: compositing disabled on connecting/disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=417146 Bug ID: 417146 Summary: compositing disabled on connecting/disconnecting external monitor Product: kwin Version: 5.17.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: --- SUMMARY Connecting or disconnecting an external monitor very often disables compositing. It doesn't seem to happen 100% of the time, so it seems like some kind of a race condition. When it happens KWin displays a message: "Desktop effects have been suspended by another application. You can resume using the 'Alt+Shift+F12' shortcut.'". I thought that maybe it's Firefox, but no, it happens even when there are no applications open at all, just an empty desktop. STEPS TO REPRODUCE 1. Run KWin with compositing enabled. 2. Connect an external monitor. OBSERVED RESULT Compositing is disabled and KWin shows a notification as described above. EXPECTED RESULT Compositing continues to work. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 Kernel Version: 5.5.1-arch1-1 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 7.6 GiB of RAM ADDITIONAL INFORMATION This bug is not new to 5.17.90, it's the same in earlier versions, at least in 5.17. My external monitor is connected to HDMI port in my laptop via HDMI to VGA adapter if that matters. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 414113] Breeze GTK window close button doesn't match Breeze Qt version if you remove the circular background
https://bugs.kde.org/show_bug.cgi?id=414113 Mariusz Libera changed: What|Removed |Added CC||mariusz.lib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 416353] Maximize button is miscolored when maximized
https://bugs.kde.org/show_bug.cgi?id=416353 Mariusz Libera changed: What|Removed |Added CC||mariusz.lib...@gmail.com --- Comment #4 from Mariusz Libera --- Same here. Here is how it looks like in Eye of Gnome: https://imgur.com/dMjGFYa -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 413003] KInfoCenter eventually crashes when browsing through energy information
https://bugs.kde.org/show_bug.cgi?id=413003 Mariusz Libera changed: What|Removed |Added CC||mariusz.lib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 107302] Associate any virtual desktop with any screen
https://bugs.kde.org/show_bug.cgi?id=107302 Mariusz Libera changed: What|Removed |Added CC||mariusz.lib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 378523] KFontRequester: Fonts are saved with face name preventing bold/italic from working
https://bugs.kde.org/show_bug.cgi?id=378523 Mariusz Libera changed: What|Removed |Added CC||mariusz.lib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404176] kwin crash on game launch
https://bugs.kde.org/show_bug.cgi?id=404176 --- Comment #5 from Mariusz Libera --- I start Braid from a desktop icon (it's a GOG install), it then displays a launcher window and after I click the 'Launch!' button it starts and kwin crashes - sometimes, not every time - and Braid continues to run. >I set a kwin rule for it to block compositing. Actually scratch that, I was thinking of another game. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404176] kwin crash on game launch
https://bugs.kde.org/show_bug.cgi?id=404176 --- Comment #4 from Mariusz Libera --- Created attachment 117972 --> https://bugs.kde.org/attachment.cgi?id=117972=edit kwin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404176] kwin crash on game launch
https://bugs.kde.org/show_bug.cgi?id=404176 --- Comment #3 from Mariusz Libera --- Created attachment 117971 --> https://bugs.kde.org/attachment.cgi?id=117971=edit kwin backtrace Will that do? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404176] New: kwin crash on game launch
https://bugs.kde.org/show_bug.cgi?id=404176 Bug ID: 404176 Summary: kwin crash on game launch Product: kwin Version: 5.14.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: --- Application: kwin_x11 (5.14.4) Qt Version: 5.12.1 Frameworks Version: 5.54.0 Operating System: Linux 4.20.7-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I launched a game (Braid). I set a kwin rule for it to block compositing. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fda81c73840 (LWP 22973))] Thread 5 (Thread 0x7fda6a05e700 (LWP 23089)): #0 0x7fda88443afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fda88f4728c in () at /usr/lib/libQt5Script.so.5 #2 0x7fda88f472a9 in () at /usr/lib/libQt5Script.so.5 #3 0x7fda8843da9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fda8ab00b23 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fda6b060700 (LWP 23086)): #0 0x7fda88443afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fda6b5fcc84 in () at /usr/lib/dri/i965_dri.so #2 0x7fda6b5fc9a8 in () at /usr/lib/dri/i965_dri.so #3 0x7fda8843da9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fda8ab00b23 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fda7a0d9700 (LWP 23083)): #0 0x7fda8aaf5d16 in ppoll () at /usr/lib/libc.so.6 #1 0x7fda89683bab in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fda8968508b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fda89630b2c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fda89474569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fda87bfb969 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fda8947596c in () at /usr/lib/libQt5Core.so.5 #7 0x7fda8843da9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fda8ab00b23 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fda7bbd5700 (LWP 23037)): #0 0x7fda8aaf5d16 in ppoll () at /usr/lib/libc.so.6 #1 0x7fda89683bab in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fda8968508b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fda89630b2c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fda89474569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fda87660ba6 in () at /usr/lib/libQt5DBus.so.5 #6 0x7fda8947596c in () at /usr/lib/libQt5Core.so.5 #7 0x7fda8843da9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fda8ab00b23 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fda81c73840 (LWP 22973)): [KCrash Handler] #6 0x7fda8aa3cd7f in raise () at /usr/lib/libc.so.6 #7 0x7fda8aa27672 in abort () at /usr/lib/libc.so.6 #8 0x7fda8aa27548 in _nl_load_domain.cold.0 () at /usr/lib/libc.so.6 #9 0x7fda8aa35396 in () at /usr/lib/libc.so.6 #10 0x7fda882d7c30 in () at /usr/lib/libepoxy.so.0 #11 0x7fda883305a0 in () at /usr/lib/libepoxy.so.0 #12 0x7fda8831e4da in () at /usr/lib/libepoxy.so.0 #13 0x7fda883b75ad in KWin::GLTexturePrivate::~GLTexturePrivate() () at /usr/lib/libkwinglutils.so.11 #14 0x7fda883b9444 in () at /usr/lib/libkwinglutils.so.11 #15 0x7fda883b8aaa in KWin::GLTexture::~GLTexture() () at /usr/lib/libkwinglutils.so.11 #16 0x7fda78e80431 in () at /usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #17 0x7fda8965a7ab in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #18 0x7fda89663825 in QObject::~QObject() () at /usr/lib/libQt5Core.so.5 #19 0x7fda8a859b0f in KWin::Toplevel::~Toplevel() () at /usr/lib/libkwin.so.5 #20 0x7fda8a87283b in KWin::Deleted::~Deleted() () at /usr/lib/libkwin.so.5 #21 0x7fda8a872aa7 in KWin::Deleted::discard() () at /usr/lib/libkwin.so.5 #22 0x7fda8a858b4b in () at /usr/lib/libkwin.so.5 #23 0x7fda8a85907d in KWin::Compositor::suspend(KWin::Compositor::SuspendReason) () at /usr/lib/libkwin.so.5 #24 0x7fda8965d152 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #25 0x7fda89ffbe24 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #26 0x7fda8a0036e1 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #27 0x7fda89631e99 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #28
[kwin] [Bug 403588] New: kwin crash in present effect
https://bugs.kde.org/show_bug.cgi?id=403588 Bug ID: 403588 Summary: kwin crash in present effect Product: kwin Version: 5.14.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: --- Application: kwin_x11 (5.14.4) Qt Version: 5.12.0 Frameworks Version: 5.54.0 Operating System: Linux 4.20.3-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Initialized present effect by putting the mouse cursor in the hot corner. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3441b63840 (LWP 1131))] Thread 6 (Thread 0x7f342a65a700 (LWP 14894)): #0 0x7f344abdbd16 in ppoll () at /usr/lib/libc.so.6 #1 0x7f344976d46b in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f344976e94b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f344971a58c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f344955e5c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f344955f9cc in () at /usr/lib/libQt5Core.so.5 #6 0x7f344832aa9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f344abe6b23 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f3429e17700 (LWP 1286)): #0 0x7f3448330afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f344903128c in () at /usr/lib/libQt5Script.so.5 #2 0x7f34490312a9 in () at /usr/lib/libQt5Script.so.5 #3 0x7f344832aa9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f344abe6b23 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f342ae5b700 (LWP 1281)): #0 0x7f3448330afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f342b3f7c24 in () at /usr/lib/dri/i965_dri.so #2 0x7f342b3f2db0 in () at /usr/lib/dri/i965_dri.so #3 0x in () #4 0x in () #5 0x in () #6 0x in () #7 0x in () #8 0x in () #9 0x in () #10 0x in () #11 0x in () #12 0x in () #13 0x in () #14 0x in () #15 0x in () #16 0x in () #17 0x3a31785f6e69776b in () #18 0x30246b736964 in () #19 0x7ffce6ca1d2f in () #20 0xa60a2af0ef9dfc00 in () #21 0x in () Thread 3 (Thread 0x7f3439df6700 (LWP 1275)): #0 0x7f344abdbd16 in ppoll () at /usr/lib/libc.so.6 #1 0x7f344976d46b in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f344976e94b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f344971a58c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f344955e5c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f3447aeab89 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f344955f9cc in () at /usr/lib/libQt5Core.so.5 #7 0x7f344832aa9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f344abe6b23 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f343ba68700 (LWP 1221)): #0 0x7f344abdbd16 in ppoll () at /usr/lib/libc.so.6 #1 0x7f344976d46b in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f344976e94b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f344971a58c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f344955e5c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f3447552ba6 in () at /usr/lib/libQt5DBus.so.5 #6 0x7f344955f9cc in () at /usr/lib/libQt5Core.so.5 #7 0x7f344832aa9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f344abe6b23 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f3441b63840 (LWP 1131)): [KCrash Handler] #6 0x562357aa4a70 in () #7 0x7f344a8ec321 in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) () at /usr/lib/libkwin.so.5 #8 0x7f34497193bf in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) () at /usr/lib/libQt5Core.so.5 #9 0x7f3441475cc2 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () at /usr/lib/libQt5XcbQpa.so.5 #10 0x7f3441476a54 in QXcbConnection::processXcbEvents(QFlags) () at /usr/lib/libQt5XcbQpa.so.5 #11 0x7f34414a1d5e in () at /usr/lib/libQt5XcbQpa.so.5 #12 0x7f344971a58c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #13
[kdevelop] [Bug 403420] New: crash while trying to view a man page
https://bugs.kde.org/show_bug.cgi?id=403420 Bug ID: 403420 Summary: crash while trying to view a man page Product: kdevelop Version: 5.3.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: --- Application: kdevelop (5.3.1) Qt Version: 5.12.0 Frameworks Version: 5.54.0 Operating System: Linux 4.20.3-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: 1. Enabled man page documentation support 2. Clicked 'show documentation' inside a tooltip over a function 3. Side panel opened with a message saying there are multiple matches 4. I clicked the first one 5. kdevelop crashed -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe1ccc7bb40 (LWP 26699))] Thread 31 (Thread 0x7fe135ffb700 (LWP 27862)): #0 0x7fe1e0643afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe1db196379 in () at /usr/lib/libQt5WebEngineCore.so.5 #2 0x7fe1db197178 in () at /usr/lib/libQt5WebEngineCore.so.5 #3 0x7fe1db19720f in () at /usr/lib/libQt5WebEngineCore.so.5 #4 0x7fe1db156318 in () at /usr/lib/libQt5WebEngineCore.so.5 #5 0x7fe1db158806 in () at /usr/lib/libQt5WebEngineCore.so.5 #6 0x7fe1db158b44 in () at /usr/lib/libQt5WebEngineCore.so.5 #7 0x7fe1db199361 in () at /usr/lib/libQt5WebEngineCore.so.5 #8 0x7fe1e063da9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fe1e318fb23 in clone () at /usr/lib/libc.so.6 Thread 30 (Thread 0x7fe1367fc700 (LWP 27861)): #0 0x7fe1e31807a4 in read () at /usr/lib/libc.so.6 #1 0x7fe1ce3bb782 in pa_read () at /usr/lib/pulseaudio/libpulsecommon-12.2.so #2 0x7fe1d2e8055f in pa_mainloop_prepare () at /usr/lib/libpulse.so.0 #3 0x7fe1d2e80fd1 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7fe1d2e81091 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7fe1d2e8f5ae in () at /usr/lib/libpulse.so.0 #6 0x7fe1ce3eb9fc in () at /usr/lib/pulseaudio/libpulsecommon-12.2.so #7 0x7fe1e063da9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fe1e318fb23 in clone () at /usr/lib/libc.so.6 Thread 29 (Thread 0x7fe136ffd700 (LWP 27860)): #0 0x7fe1e0643ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe1db196447 in () at /usr/lib/libQt5WebEngineCore.so.5 #2 0x7fe1db19716a in () at /usr/lib/libQt5WebEngineCore.so.5 #3 0x7fe1db111950 in () at /usr/lib/libQt5WebEngineCore.so.5 #4 0x7fe1db13563b in () at /usr/lib/libQt5WebEngineCore.so.5 #5 0x7fe1db168608 in () at /usr/lib/libQt5WebEngineCore.so.5 #6 0x7fe1db199361 in () at /usr/lib/libQt5WebEngineCore.so.5 #7 0x7fe1e063da9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fe1e318fb23 in clone () at /usr/lib/libc.so.6 Thread 28 (Thread 0x7fe1377fe700 (LWP 27859)): #0 0x7fe1e0643afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe1db196379 in () at /usr/lib/libQt5WebEngineCore.so.5 #2 0x7fe1dba6eee8 in () at /usr/lib/libQt5WebEngineCore.so.5 #3 0x7fe1db1688cf in () at /usr/lib/libQt5WebEngineCore.so.5 #4 0x7fe1db199361 in () at /usr/lib/libQt5WebEngineCore.so.5 #5 0x7fe1e063da9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fe1e318fb23 in clone () at /usr/lib/libc.so.6 Thread 27 (Thread 0x7fe137fff700 (LWP 27858)): #0 0x7fe1e0643afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe1db196379 in () at /usr/lib/libQt5WebEngineCore.so.5 #2 0x7fe1db197178 in () at /usr/lib/libQt5WebEngineCore.so.5 #3 0x7fe1db19720f in () at /usr/lib/libQt5WebEngineCore.so.5 #4 0x7fe1db156318 in () at /usr/lib/libQt5WebEngineCore.so.5 #5 0x7fe1db158806 in () at /usr/lib/libQt5WebEngineCore.so.5 #6 0x7fe1db158b04 in () at /usr/lib/libQt5WebEngineCore.so.5 #7 0x7fe1db199361 in () at /usr/lib/libQt5WebEngineCore.so.5 #8 0x7fe1e063da9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fe1e318fb23 in clone () at /usr/lib/libc.so.6 Thread 26 (Thread 0x7fe13cc35700 (LWP 27857)): #0 0x7fe1e318fe57 in epoll_wait () at /usr/lib/libc.so.6 #1 0x7fe1d5644d4b in () at /usr/lib/libevent-2.1.so.6 #2 0x7fe1d563aac8 in event_base_loop () at /usr/lib/libevent-2.1.so.6 #3 0x7fe1db199f64 in () at /usr/lib/libQt5WebEngineCore.so.5 #4 0x7fe1db13563b in () at /usr/lib/libQt5WebEngineCore.so.5 #5 0x7fe1daae7ce4 in () at /usr/lib/libQt5WebEngineCore.so.5 #6 0x7fe1db1686d8 in () at
[plasmashell] [Bug 400626] New: plasma crashed while browsing apps in kicker
https://bugs.kde.org/show_bug.cgi?id=400626 Bug ID: 400626 Summary: plasma crashed while browsing apps in kicker Product: plasmashell Version: 5.14.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mariusz.lib...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.14.2) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.18.16-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Clicked on kicker and placed the mouse cursor on one of the categories, list of apps showed up, then moved the mouse cursor one category below - crash. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f987fde10c0 (LWP 2094))] Thread 25 (Thread 0x7f980d7fa700 (LWP 3000)): #0 0x7f98851eeafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f98862d171c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f98697ae469 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f98697b2339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f98697ad52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f98697b2392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f98697ad52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f98697b2392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f98697ad52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f98697b2392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f98697ad52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f98697b2392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f98697ad52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7f98697b2392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7f98697ad52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7f98697b2392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7f98697ad52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #17 0x7f98697b2392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #18 0x7f98697ad52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #19 0x7f98697b2392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #20 0x7f98697ad52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #21 0x7f98697b2392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #22 0x7f98697ad52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #23 0x7f98697b0389 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #24 0x7f98862d0f65 in () at /usr/lib/libQt5Core.so.5 #25 0x7f98851e8a9d in start_thread () at /usr/lib/libpthread.so.0 #26 0x7f9885fb5b23 in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7f980dffb700 (LWP 2999)): #0 0x7f98851eeafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f98862d171c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f98697ae469 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f98697b2339 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f98697ad52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f98697b2392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f98697ad52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f98697b2392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f98697ad52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f98697b2392 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f98697ad52d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f98697b2392 in
[plasmashell] [Bug 393871] New: plasma crash
https://bugs.kde.org/show_bug.cgi?id=393871 Bug ID: 393871 Summary: plasma crash Product: plasmashell Version: 5.12.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mariusz.lib...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.5) Qt Version: 5.10.1 Frameworks Version: 5.45.0 Operating System: Linux 4.16.5-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: just browsing the web in firefox, a few seconds after my laptop resumed from suspend -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f47e688a800 (LWP 21376))] Thread 25 (Thread 0x7f467bcff700 (LWP 8103)): #0 0x7f47dfddbcd9 in poll () at /usr/lib/libc.so.6 #1 0x7f47da65a523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f47da65a63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f47e072a254 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f47e06cc31b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f47e04db71e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f47e04e0abd in () at /usr/lib/libQt5Core.so.5 #7 0x7f47df6960bc in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f47dfde62ff in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7f4714815700 (LWP 8077)): #0 0x7f47dfddbcd9 in poll () at /usr/lib/libc.so.6 #1 0x7f47da65a523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f47da65a63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f47e072a254 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f47e06cc31b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f47e04db71e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f47e04e0abd in () at /usr/lib/libQt5Core.so.5 #7 0x7f47df6960bc in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f47dfde62ff in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7f46eb7ff700 (LWP 8076)): #0 0x7f47dfdd7734 in read () at /usr/lib/libc.so.6 #1 0x7f47da69fed1 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f47da659ff8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f47da65a4c6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f47da65a63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f47e072a254 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f47e06cc31b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f47e04db71e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f47e04e0abd in () at /usr/lib/libQt5Core.so.5 #9 0x7f47df6960bc in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f47dfde62ff in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7f4715c4a700 (LWP 8075)): #0 0x7f47dfddbcd9 in poll () at /usr/lib/libc.so.6 #1 0x7f47da65a523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f47da65a63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f47e072a254 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f47e06cc31b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f47e04db71e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f47e04e0abd in () at /usr/lib/libQt5Core.so.5 #7 0x7f47df6960bc in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f47dfde62ff in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7f46b5ffb700 (LWP 4556)): #0 0x7f47dfddbcd9 in poll () at /usr/lib/libc.so.6 #1 0x7f47d481b773 in () at /usr/lib/libpulse.so.0 #2 0x7f47d480cbd0 in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #3 0x7f47d480d271 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7f47d480d301 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7f47d481b6ae in () at /usr/lib/libpulse.so.0 #6 0x7f47d3f8c81c in () at /usr/lib/pulseaudio/libpulsecommon-11.1.so #7 0x7f47df6960bc in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f47dfde62ff in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7f46b67fc700 (LWP 31835)): #0 0x7f47df69c07c in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f47e04e1f9c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f471ee7752f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3
[plasmashell] [Bug 370975] device notifier pretends it cannot mount usb device while actually mounting it
https://bugs.kde.org/show_bug.cgi?id=370975 --- Comment #48 from Mariusz Libera <mariusz.lib...@gmail.com> --- I've tested it with a couple of pendrives and an external usb drive, everything functions properly - accessing devices from Device Notifier and from Dolphin works without errors. Awesome work, thanks for fixing it. :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370975] device notifier pretends it cannot mount usb device while actually mounting it
https://bugs.kde.org/show_bug.cgi?id=370975 --- Comment #40 from Mariusz Libera <mariusz.lib...@gmail.com> --- Created attachment 112348 --> https://bugs.kde.org/attachment.cgi?id=112348=edit device notifier workaround I've spend some time looking into this and found out that the issue is not with the Device Notifier itself but with Solid, or with how Solid interacts with Udisks. I don't really know what's the source of the bug but I've come up with a workaround that fixes Device Notifier (so far it's working as expected for me). If anyone wants to try it out, you have to rebuild plasma-workspace with the attached patch applied. It fixes only Device Notifier, mounting with Dolphin is still broken as it seems to be calling Solid in a different way. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392650] New: plasma crash
https://bugs.kde.org/show_bug.cgi?id=392650 Bug ID: 392650 Summary: plasma crash Product: plasmashell Version: 5.12.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mariusz.lib...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.4) Qt Version: 5.10.1 Frameworks Version: 5.44.0 Operating System: Linux 4.15.14-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I was searching for something in google image search using firefox, crash happened the moment I clicked on a picture - Unusual behavior I noticed: monitor gamma settings resetting - Custom settings of the application: i'm using redshift if that matters The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcbd6865800 (LWP 1184))] Thread 23 (Thread 0x7fca9e7fc700 (LWP 3071)): #0 0x7fcbcf6833bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcbd04c3fac in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fcb0ee7752f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fcb0ee7b719 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fcb0ee766fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fcb0ee7b772 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fcb0ee766fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fcb0ee7b772 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fcb0ee766fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7fcb0ee7b772 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7fcb0ee766fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7fcb0ee7b772 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7fcb0ee766fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7fcb0ee7b772 in () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7fcb0ee766fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7fcb0ee7b772 in () at /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7fcb0ee766fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #17 0x7fcb0ee7b772 in () at /usr/lib/libKF5ThreadWeaver.so.5 #18 0x7fcb0ee766fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #19 0x7fcb0ee7b772 in () at /usr/lib/libKF5ThreadWeaver.so.5 #20 0x7fcb0ee766fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #21 0x7fcb0ee79583 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #22 0x7fcbd04c2acd in () at /usr/lib/libQt5Core.so.5 #23 0x7fcbcf67d08c in start_thread () at /usr/lib/libpthread.so.0 #24 0x7fcbcfdcae7f in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7fca9effd700 (LWP 3070)): #0 0x7fcbcf6833bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcbd04c3fac in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fcb0ee7752f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fcb0ee7b719 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fcb0ee766fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fcb0ee7b772 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fcb0ee766fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fcb0ee7b772 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fcb0ee766fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7fcb0ee7b772 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7fcb0ee766fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7fcb0ee7b772 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7fcb0ee766fd in
[plasmashell] [Bug 370975] device notifier pretends it cannot mount usb device while actually mounting it
https://bugs.kde.org/show_bug.cgi?id=370975 Mariusz Libera <mariusz.lib...@gmail.com> changed: What|Removed |Added CC||mariusz.lib...@gmail.com --- Comment #23 from Mariusz Libera <mariusz.lib...@gmail.com> --- Same here, Archlinux. Plasma 5.12.3 frameworks 5.44.0 applications 17.12.3 Very annoying bug. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 319625] Bookmarks lost for renamed documents, allow to manually specify document path
https://bugs.kde.org/show_bug.cgi?id=319625 Mariusz Libera <mariusz.lib...@gmail.com> changed: What|Removed |Added CC||mariusz.lib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 336381] Directly save bookmarks to PDF
https://bugs.kde.org/show_bug.cgi?id=336381 Mariusz Libera <mariusz.lib...@gmail.com> changed: What|Removed |Added CC||mariusz.lib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387097] Need ability to read client.maximizeMode since it's currently not a property
https://bugs.kde.org/show_bug.cgi?id=387097 Mariusz Libera <mariusz.lib...@gmail.com> changed: What|Removed |Added CC||mariusz.lib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
