[neon] [Bug 481288] Gdrive invalid protocol after create a Google account to access Google Drive
https://bugs.kde.org/show_bug.cgi?id=481288 Matias Barletta changed: What|Removed |Added CC||m...@lionix.com --- Comment #9 from Matias Barletta --- How can I provide more info? I have the same issue with a fresh KDE neon install. `Invalid field selection` error in dolphin. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483137] Screencast plugin fails if PipeWire is started after KWin
https://bugs.kde.org/show_bug.cgi?id=483137 Matias Barletta changed: What|Removed |Added CC||m...@lionix.com -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 466164] kmenueditor crashes after saving and reediting the item.
https://bugs.kde.org/show_bug.cgi?id=466164 --- Comment #3 from Matias Barletta --- Created attachment 157028 --> https://bugs.kde.org/attachment.cgi?id=157028=edit New crash information added by DrKonqi kmenuedit (5.27.2) using Qt 5.15.8 Editing Menu, selecting the offending menu item, then crash -- Backtrace (Reduced): #4 0x7f1d1c0c4324 in QWidgetLineControl::internalSetText(QString const&, int, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #9 0x7f1d1c268b32 in QTreeWidget::currentItemChanged(QTreeWidgetItem*, QTreeWidgetItem*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #11 0x7f1d1b2656c7 in QItemSelectionModel::currentChanged(QModelIndex const&, QModelIndex const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f1d1b26917d in QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f1d1c1eb14e in QAbstractItemView::mousePressEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 466164] kmenueditor crashes after saving and reediting the item.
https://bugs.kde.org/show_bug.cgi?id=466164 --- Comment #2 from Matias Barletta --- Created attachment 156933 --> https://bugs.kde.org/attachment.cgi?id=156933=edit New crash information added by DrKonqi kmenuedit (5.27.2) using Qt 5.15.8 Just editing a Favorite menu (dbeaver) causes the crash. -- Backtrace (Reduced): #4 0x7fe06e0c4324 in QWidgetLineControl::internalSetText(QString const&, int, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #9 0x7fe06e268b32 in QTreeWidget::currentItemChanged(QTreeWidgetItem*, QTreeWidgetItem*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #11 0x7fe06d2656c7 in QItemSelectionModel::currentChanged(QModelIndex const&, QModelIndex const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fe06d26917d in QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fe06e1eb14e in QAbstractItemView::mousePressEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 466164] kmenueditor crashes after saving and reediting the item.
https://bugs.kde.org/show_bug.cgi?id=466164 Matias Barletta changed: What|Removed |Added CC||m...@lionix.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413203] Some notifications don't disappear after timeout
https://bugs.kde.org/show_bug.cgi?id=413203 Matias Barletta changed: What|Removed |Added Version|5.17.0 |5.25.4 Platform|Archlinux Packages |Neon Packages CC||m...@lionix.com --- Comment #9 from Matias Barletta --- I have this issue in KDE Neon fully updated. Doing kdialog with --passivepopup holi 3 has the issue, as well as brave/chrome notifications. Restarting the system solves the issue till... till something happens and breaks. Sorry I can't give more details on the conditions for this to happen, I have this issue for more than a year, sometimes it disappears, then is back. It happens with Xorg using intel or nvidia (as default, not prime) Can I do something to shed more light on this @Kai Uwe Broulik ? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 441907] Yakuake always opens on the left screen in case of display scaling
https://bugs.kde.org/show_bug.cgi?id=441907 Matias Barletta changed: What|Removed |Added CC||m...@lionix.com --- Comment #3 from Matias Barletta --- Same thing here, using X11 and scaling 175 and 100 in the second monitor. -- You are receiving this mail because: You are watching all bug changes.
[kscreensaver] [Bug 316348] kscreenlocker_greet constantly consumes around 20% CPU time
https://bugs.kde.org/show_bug.cgi?id=316348 --- Comment #36 from Matias Barletta <m...@lionix.com> --- @david.sainty I have felt your pain, even with desktops effects working properly on opengl 3.1, kscreenlocker was eating my cpu ALL the time. I upgraded to the latest KDE Neon User Edition - problem is gone .. drastic measure, but works -- You are receiving this mail because: You are watching all bug changes.
[kscreensaver] [Bug 316348] kscreenlocker_greet constantly consumes around 20% CPU time
https://bugs.kde.org/show_bug.cgi?id=316348 --- Comment #31 from Matias Barletta <m...@lionix.com> --- This is a more complete bt Thread 9 (Thread 0x7f8678664700 (LWP 21290)): #0 0x7f8689b5e88d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f868984bbd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f868984d74f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f867a38a779 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f868a254a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f868520a6aa in start_thread (arg=0x7f8678664700) at pthread_create.c:333 #6 0x7f8689b69e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f8676ff5700 (LWP 21291)): #0 0x7f8689b5e88d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f86830ee1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f86830ee2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f868a48c4ef in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f868a43350a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f868a24fac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f868a254a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f868520a6aa in start_thread (arg=0x7f8676ff5700) at pthread_create.c:333 #8 0x7f8689b69e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f8674d11700 (LWP 21292)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f86761babf3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7f86761baa57 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7f868520a6aa in start_thread (arg=0x7f8674d11700) at pthread_create.c:333 #4 0x7f8689b69e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f866dc0e700 (LWP 21293)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f86761babf3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7f86761baa57 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7f868520a6aa in start_thread (arg=0x7f866dc0e700) at pthread_create.c:333 #4 0x7f8689b69e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f866d40d700 (LWP 21294)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f86761babf3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7f86761baa57 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7f868520a6aa in start_thread (arg=0x7f866d40d700) at pthread_create.c:333 #4 0x7f8689b69e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f866cc0c700 (LWP 21295)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f86761babf3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7f86761baa57 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ---Type to continue, or q to quit--- #3 0x7f868520a6aa in start_thread (arg=0x7f866cc0c700) at pthread_create.c:333 #4 0x7f8689b69e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f8667fff700 (LWP 21296)): #0 0x7f8689b5e88d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f86830ee1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f86830ee2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f868a48c4ef in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f868a43350a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f868a24fac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f868ba0ec35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f868a254a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f868520a6aa in start_thread (arg=0x7f8667fff700) at pthread_create.c:333 #9 0x7f8689b69e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f865700 (LWP 21299)): #0 0x7f8689b5e88d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f86830ee1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f86830ee2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f868a48c50b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f868a43350a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Cor
[kscreensaver] [Bug 316348] kscreenlocker_greet constantly consumes around 20% CPU time
https://bugs.kde.org/show_bug.cgi?id=316348 Matias Barletta <m...@lionix.com> changed: What|Removed |Added CC||m...@lionix.com --- Comment #25 from Matias Barletta <m...@lionix.com> --- (In reply to Martin Gräßlin from comment #23) > > Those experiencing the problem need to help us: please gdb into the process > and get a backtrace, so that we can see where it consumes the CPU. This id a gdb bt on kubuntu 15.10 (kernel 4.5) and plasma 4:5.5.4-0ubuntu1~ubuntu15.10~ppa1 #0 0x7f8689b5e88d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f86830ee1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f86830ee2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f868a48c4ef in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f868a43350a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f868a43b5ec in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x0040ae87 in main () -- You are receiving this mail because: You are watching all bug changes.
