[gwenview] [Bug 465688] "Fit" on scaled wayland display doesn't fit
https://bugs.kde.org/show_bug.cgi?id=465688 Jorge changed: What|Removed |Added CC||jorge_barroso...@hotmail.co ||m --- Comment #1 from Jorge --- I have been able to reproduce this when using a display scale different from 100% and a screenshot (ensuring the same size as the display) The problem seems to come from DocumentView::toggleZoomToFit and DocumentView::toggleZoomToFill calling "d->setZoom(1., d->cursorPosition());" with "1." zoom, which should probably be a different value (i.e. 1.25 for 125% scale), but I'm unsure as to what's the best way to get the current display scale and apply it to the zoom level instead of a hardcoded "1." -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 465688] "Fit" on scaled wayland display doesn't fit
https://bugs.kde.org/show_bug.cgi?id=465688 --- Comment #4 from Jorge --- Using "devicePixelRatio" methods returns "2" in my case, which may be due to using KF5/Qt5 under Wayland. I've tried building with Qt6 but with no luck :-/ -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 441221] New: Latte does not start with the system
https://bugs.kde.org/show_bug.cgi?id=441221 Bug ID: 441221 Summary: Latte does not start with the system Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jone...@gmail.com Target Milestone: --- Application: latte-dock (0.10.0) Qt Version: 5.15.3 Frameworks Version: 5.85.0 Operating System: Linux 5.11.0-27-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed:When starting the system, Latte dock does not load and has to be loaded manually and continues without any further errors. The crash can be reproduced sometimes. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [New LWP 1413] [New LWP 1438] [New LWP 1439] [New LWP 1440] [New LWP 1441] [New LWP 1444] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f7a64dd6aff in __GI___poll (fds=0x7ffdd3f83f38, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f7a6133d9c0 (LWP 1382))] Thread 7 (Thread 0x7f7a51647700 (LWP 1444)): #0 __GI___libc_read (nbytes=16, buf=0x7f7a516469a0, fd=10) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=10, buf=0x7f7a516469a0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f7a6382cb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7a637e3ebe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f7a637e4312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f7a637e44a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f7a654f4fcb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f7a6549925b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f7a652b2c22 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f7a65756f4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7f7a652b3dbc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f7a645d3609 in start_thread (arg=) at pthread_create.c:477 #12 0x7f7a64de3293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f7a52048700 (LWP 1441)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f7a58005788) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f7a58005738, cond=0x7f7a58005760) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f7a58005760, mutex=0x7f7a58005738) at pthread_cond_wait.c:647 #3 0x7f7a5d49ee7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #4 0x7f7a5d49ea7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #5 0x7f7a645d3609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f7a64de3293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f7a52849700 (LWP 1440)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f7a58005788) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f7a58005738, cond=0x7f7a58005760) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f7a58005760, mutex=0x7f7a58005738) at pthread_cond_wait.c:647 #3 0x7f7a5d49ee7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #4 0x7f7a5d49ea7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #5 0x7f7a645d3609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f7a64de3293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f7a5c8e8700 (LWP 1439)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f7a58005788) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f7a58005738, cond=0x7f7a58005760) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f7a58005760, mutex=0x7f7a58005738) at pthread_cond_wait.c:647 #3 0x7f7a5d49ee7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #4 0x7f7a5d49ea7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #5 0x7f7a645d3609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f7a64de3293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f7a5d0e9700 (LWP 1438)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f7a58005788) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f7a58005738, cond=0x7f7a58005760) at pthread_cond_wait.c:508 #2
[Akonadi] [Bug 473897] Cannot add Google Groupware, "Configured account does not exist" then "Resource is not configured"
https://bugs.kde.org/show_bug.cgi?id=473897 Jorge changed: What|Removed |Added CC||jorge...@hotmail.es -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454600] PWA on wayland don't get their own window icon in the taskbar
https://bugs.kde.org/show_bug.cgi?id=454600 Jorge changed: What|Removed |Added CC||jorge_barroso...@hotmail.co ||m --- Comment #8 from Jorge --- (In reply to sebastien.leon from comment #5) > (In reply to tnizametdinov from comment #4) > > I'm on Plasma 5.25.5, but the issue is still there. > > Have you try to set chrome://flags/#ozone-platform-hint to "wayland" ? This fixed it for me, quite similar in brave: setting brave://flags/#ozone-platform-hint to "Auto" or "Wayland". It comes configured with "Default" which at this point in time equals "X11" -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 464358] New: Kalendar crash when changing completition status of task
https://bugs.kde.org/show_bug.cgi?id=464358 Bug ID: 464358 Summary: Kalendar crash when changing completition status of task Classification: Applications Product: kalendar Version: 22.12.1 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: jorgem...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: kalendar (22.12.1) Qt Version: 5.15.8 Frameworks Version: 5.101.0 Operating System: Linux 5.15.0-58-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.26 DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: When clicking on a task, you get a pop-up inside the main Kalendar window. where you can set the completition status with a slider. Kalendar immediatly crash when you try to edit this slider. By double-clicking the task, you get a pop-up window where you can also change the completition status. Kalendar crashes when saving the changes if you modified the completition status. However, the completition status does get saved. I observed this behaviour both with tasks from my google calendar and whith tasks from my local Personal Calendar. The crash can be reproduced sometimes. -- Backtrace: Application: Kalendar (kalendar), signal: Segmentation fault [KCrash Handler] #4 0x55bdbf8cbdec in ?? () #5 0x7f5cd328e0d4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5cd31eeb59 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f5cd322b5a1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f5cd328e108 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f5cd31eeb59 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f5cd322b5a1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f5cd328e108 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f5cd31eeb59 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f5cd322b5a1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f5cd328e108 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f5cd31eeb59 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f5cd51f8d2a in ?? () from /lib/x86_64-linux-gnu/libKF5ItemModels.so.5 #17 0x7f5cd328e0d4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f5cd31eeb59 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f5cd55628d4 in ?? () from /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5 #20 0x7f5cd556cdb9 in ?? () from /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5 #21 0x7f5cd328e108 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f5cd54b417b in Akonadi::Monitor::itemChanged(Akonadi::Item const&, QSet const&) () from /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5 #23 0x7f5cd54c5692 in Akonadi::MonitorPrivate::emitItemsNotification(Akonadi::Protocol::ItemChangeNotification const&, QVector const&, Akonadi::Collection const&, Akonadi::Collection const&) () from /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5 #24 0x7f5cd54c6809 in Akonadi::MonitorPrivate::emitNotification(QSharedPointer const&) () from /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5 #25 0x7f5cd54c3dba in Akonadi::MonitorPrivate::flushPipeline() () from /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5 #26 0x7f5cd54c421d in Akonadi::MonitorPrivate::dataAvailable() () from /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5 #27 0x7f5cd328e0d4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f5cd328e108 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f5cd35f2e90 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #30 0x7f5cd35f87cb in KJob::finishJob(bool) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #31 0x7f5cd3283ade in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7f5cd3eea793 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x7f5cd325607a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7f5cd3259167 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x7f5cd32b0487 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x7f5cd0c6ed3
[lattedock] [Bug 464586] New: lattedock crash at sistem iniciaty
https://bugs.kde.org/show_bug.cgi?id=464586 Bug ID: 464586 Summary: lattedock crash at sistem iniciaty Classification: Plasma Product: lattedock Version: 0.10.8 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: jone...@gmail.com Target Milestone: --- Application: latte-dock (0.10.8) Qt Version: 5.15.8 Frameworks Version: 5.102.0 Operating System: Linux 5.15.0-58-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.26 DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: No inicia automáticamente y hay que hacerlo manualmente. Ocurre en varios inicios. No siempre The crash can be reproduced sometimes. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x7ff254c28716 in ?? () from /lib/x86_64-linux-gnu/libKF5ActivitiesStats.so.1 #5 0x7ff2707862b3 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #6 0x7ff27042fb43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #7 0x7ff2704c1a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 5 (Thread 0x7ff246ef6640 (LWP 1655) "latte-dock"): #1 __pselect (nfds=5, readfds=0x7ff246eeda40, writefds=0x0, exceptfds=0x0, timeout=, sigmask=) at ../sysdeps/unix/sysv/linux/pselect.c:56 #2 0x7ff26c4aa03d in ?? () from /lib/x86_64-linux-gnu/libusbmuxd-2.0.so.6 #3 0x7ff26c4aad88 in ?? () from /lib/x86_64-linux-gnu/libusbmuxd-2.0.so.6 #4 0x7ff27042fb43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #5 0x7ff2704c1a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 4 (Thread 0x7ff2561c2640 (LWP 1562) "QQmlThread"): #1 0x7ff26ef6f666 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff26ef183e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff270bebb4e in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff270b9099b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff2709a34e2 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff2727a5b09 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7ff2709a4703 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff27042fb43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #9 0x7ff2704c1a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 3 (Thread 0x7ff261fff640 (LWP 1548) "QQmlThread"): #1 __GI___libc_read (fd=21, buf=0x7ff261ffe970, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7ff26ef1b134 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff26ef6f60d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff26ef183e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff270bebb4e in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff270b9099b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7ff2709a34e2 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff2727a5b09 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7ff2709a4703 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7ff27042fb43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #11 0x7ff2704c1a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 2 (Thread 0x7ff26bb8a640 (LWP 1435) "QDBusConnection"): #1 0x7ff26ef6f666 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff26ef183e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff270bebad8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff270b9099b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff2709a34e2 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff270e52f1b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7ff2709a4703 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff27042fb43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #9 0x7ff2704c1a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 1 (Thread 0x7ff26c3609c0 (LWP 1398) "latte-dock"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x56076821c960) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x56076821c960, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x00
[kmail2] [Bug 346135] Kmail support for DarkThemes and HTML-Mails
https://bugs.kde.org/show_bug.cgi?id=346135 Jorge changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 CC||tarma...@gmail.com Resolution|WORKSFORME |--- --- Comment #8 from Jorge --- Is there any news, improvements about this? I don't think it should be that hard to be able to set the background color white, or select white teme for that application. It just makes KDE unusable with dark themes at all, just setting an option to change background color would make it and it shouldn't be that hard to do -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 346135] Kmail support for DarkThemes and HTML-Mails
https://bugs.kde.org/show_bug.cgi?id=346135 Jorge changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REOPENED|RESOLVED --- Comment #10 from Jorge --- Thanks for the info, right now I use KMail for debian on sid, version 18.08.1-1. Can't wait until they release the fix! *** This bug has been marked as a duplicate of bug 317803 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 317803] Kmail2 renders colors based on the user system colors rather than the default colors browsers use.
https://bugs.kde.org/show_bug.cgi?id=317803 Jorge changed: What|Removed |Added CC||s.sut...@gmx.de --- Comment #25 from Jorge --- *** Bug 346135 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392102] New: kmail close when resend an email
https://bugs.kde.org/show_bug.cgi?id=392102 Bug ID: 392102 Summary: kmail close when resend an email Product: kmail2 Version: unspecified Platform: Chakra OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: japv7...@gmail.com Target Milestone: --- When I want to resend an email the application is closed If the mail is new, there is no problem. Version Plasma 5.9.5 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392102] kmail close when resend an email
https://bugs.kde.org/show_bug.cgi?id=392102 --- Comment #2 from Jorge --- Version 5.7.3 Sometimes it is fixed by restarting the computer 2018-03-20 9:34 GMT-06:00 Laurent Montel : > https://bugs.kde.org/show_bug.cgi?id=392102 > > Laurent Montel changed: > >What|Removed |Added > > > CC||mon...@kde.org > > --- Comment #1 from Laurent Montel --- > Backtrace please > kmail version please > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #3 from José JORGE --- (In reply to knossos456 from comment #2) > Have you same problem with VLC (because newest Kaffeine is based on VLC > core) ? > For me and ATI 5450, all is OK (VLC and Kaffeine) for VDPAU and ubuntu 16.04 > ( under 3% cpu usage > Please post your graphical card model It is an ATI HD3200 (R600 GPU integrated in the motherbord). I have no problems when using directly VLC. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #8 from José JORGE --- (In reply to knossos456 from comment #7) > If you dont use virtual adapters, please notice also that kaffeine 2.0x use > vlc as dvb core, and perhaps your version of Vlc is not correct, version > > 2.22 is requested. > This is explained on VLC forum, VDPAU did not work on old VLC versions. I use vlc 2.2.4. It is important to understand that the 100% CPU does not stop if I stop the player. I have to close it. So it seems a Kaffeine interface bug, not a vlc one. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #12 from José JORGE --- (In reply to Mauro Carvalho Chehab from comment #11) > option is accepted there. You could try those: > --no-video-title-show -V xcb_glx > or: > --no-video-title-show -V xcb_xv > > and re-start Kaffeine. > > Please test if changing to one of the above will affect the CPU usage. None of those affect the CPU usage. The bug still triggers after watching one channel, either by clicking on stop, or by clicking on another channel. Is there a way to debug the libvlc usage by kaffeine? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453857] malloc() aborts during save
https://bugs.kde.org/show_bug.cgi?id=453857 --- Comment #12 from Vicente Jorge --- Solved, updating gnutls 3.7.5-1 to 3.7.5-2 on Arch -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 464119] Systemd/logind sleep inhibitions inhibit both sleep and screen locking.
https://bugs.kde.org/show_bug.cgi?id=464119 Jorge Nerín changed: What|Removed |Added CC||jne...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 394608] Drag and Drop does not work with Chrome on multiple-monitors
https://bugs.kde.org/show_bug.cgi?id=394608 Jorge Nerín changed: What|Removed |Added CC||jne...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 486185] New: Partition Manager fails at detecting partition, while GParted and Gnome Disks show the proper partition.
https://bugs.kde.org/show_bug.cgi?id=486185 Bug ID: 486185 Summary: Partition Manager fails at detecting partition, while GParted and Gnome Disks show the proper partition. Classification: Applications Product: partitionmanager Version: 24.02.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: jorgebla...@mac.com Target Milestone: --- Created attachment 168938 --> https://bugs.kde.org/attachment.cgi?id=168938&action=edit Screenshot of partition managers and konsole. SUMMARY KDE Partition Manager displays /dev/sdb as unknown filesystem, 28.82 GiB capacity, inactive. GParted, Gnome disks and fdisk -l show /dev/sdb as File system: fat32, the used capacity, remaining capacity, total size 28.82 GiB, the blank label, the UUID, the mount point, the path and the sectors, first: 0, last: 60437491 and total: 60437492 STEPS TO REPRODUCE 1. Open KDE Partition Manager, be informed you are missing tools to handle ext4 filesystems and nvme drives because linux-utils and e2fsprogs are not installed. 2. Look for connected USB drive. 3. USB drive has unknown, unassigned filesystem. 4. Compare to GParted, Gnome Disks and fdisk -l OBSERVED RESULT FAT32 partition is not detected. EXPECTED RESULT FAT32 partition to be detected. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20240418 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1 Qt Version: 6.7.0 ADDITIONAL INFORMATION Kernel 6.8.6-1 Wayland session -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 486185] Partition Manager fails at detecting partition, while GParted and Gnome Disks and fdisk show the actual partition.
https://bugs.kde.org/show_bug.cgi?id=486185 Jorge Blasio changed: What|Removed |Added Summary|Partition Manager fails at |Partition Manager fails at |detecting partition, while |detecting partition, while |GParted and Gnome Disks |GParted and Gnome Disks and |show the proper partition. |fdisk show the actual ||partition. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 486185] Partition Manager fails at detecting partition, while GParted, Gnome Disks and fdisk show the actual partition.
https://bugs.kde.org/show_bug.cgi?id=486185 Jorge Blasio changed: What|Removed |Added Summary|Partition Manager fails at |Partition Manager fails at |detecting partition, while |detecting partition, while |GParted and Gnome Disks and |GParted, Gnome Disks and |fdisk show the actual |fdisk show the actual |partition. |partition. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 454134] New: The program closes without saving the new entries. When you save, error.
https://bugs.kde.org/show_bug.cgi?id=454134 Bug ID: 454134 Summary: The program closes without saving the new entries. When you save, error. Product: kmymoney Version: 5.1.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: vicentejorges...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. New seat 2. Save 3. Error OBSERVED RESULT I don't save EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456235] New: System Settings estoura ao configurar o display
https://bugs.kde.org/show_bug.cgi?id=456235 Bug ID: 456235 Summary: System Settings estoura ao configurar o display Product: systemsettings Version: 5.25.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jor...@tecit.pt Target Milestone: --- Application: systemsettings (5.25.1) Qt Version: 5.15.5 Frameworks Version: 5.95.0 Operating System: Linux 5.18.6-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.1 [KCrashBackend] -- Information about the crash: Sempre que tento configurar o ecran o programa fecha. Abre a janela do "display and monitor" mas não chega a apresentar o desenho do ecrãn The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Floating point exception [KCrash Handler] #4 0x7f22981c2048 in OutputModel::resolutionsStrings (output=..., this=) at /usr/src/debug/kscreen5-5.25.1-1.1.x86_64/kcm/output_model.cpp:579 #5 OutputModel::data (this=, index=..., role=) at /usr/src/debug/kscreen5-5.25.1-1.1.x86_64/kcm/output_model.cpp:72 #6 0x7f22a4226a30 in QModelIndex::data (arole=268, this=0x7fff86a63230) at /usr/include/qt5/QtCore/qabstractitemmodel.h:460 #7 QQmlDMAbstractItemModelData::value (role=268, this=0x55df1657f180) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.1.x86_64/src/qmlmodels/qqmladaptormodel.cpp:414 #8 QQmlDMCachedModelData::metaCall (this=0x55df1657f180, call=, id=, arguments=0x7fff86a632e0) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.1.x86_64/src/qmlmodels/qqmladaptormodel.cpp:282 #9 0x7f22a50c26f6 in QQmlPropertyData::readProperty (property=0x7fff86a632c0, target=0x55df1657f180, this=0x55df164add08) at ../../include/QtQml/5.15.5/QtQml/private/../../../../../../src/qml/qml/qqmlpropertydata_p.h:357 #10 loadProperty (v4=0x55df1469c3b0, object=0x55df1657f180, property=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:176 #11 0x7f22a50e2ac6 in QV4::Moth::VME::interpret (frame=0x7fff86a63180, engine=0x55df1469c3b0, code=0x7f227e76cc1a ":(\030\a\006\064\a\030\006\002") at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.1.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:641 #12 0x7f22a50e732f in QV4::Moth::VME::exec (frame=frame@entry=0x7fff86a634e0, engine=engine@entry=0x55df1469c3b0) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.1.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:466 #13 0x7f22a507a2ce in QV4::Function::call (this=this@entry=0x55df14cb79a0, thisObject=, argv=argv@entry=0x7f227f07d5d0, argc=, context=) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.1.x86_64/src/qml/jsruntime/qv4function.cpp:69 #14 0x7f22a52023fd in QQmlJavaScriptExpression::evaluate (this=this@entry=0x55df167873c0, callData=0x7f227f07d5a0, isUndefined=isUndefined@entry=0x7fff86a636af) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.1.x86_64/src/qml/qml/qqmljavascriptexpression.cpp:212 #15 0x7f22a52085a4 in QQmlBinding::evaluate (this=this@entry=0x55df167873c0, isUndefined=isUndefined@entry=0x7fff86a636af) at ../../include/QtQml/5.15.5/QtQml/private/../../../../../../src/qml/jsruntime/qv4jscall_p.h:95 #16 0x7f22a520c6c3 in QQmlNonbindingBinding::doUpdate (this=0x55df167873c0, watcher=..., flags=..., scope=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.1.x86_64/src/qml/qml/qqmlbinding.cpp:254 #17 0x7f22a520a244 in QQmlBinding::update (this=0x55df167873c0, flags=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.1.x86_64/src/qml/qml/qqmlbinding.cpp:194 #18 0x7f22a50c2a5b in QQmlData::flushPendingBinding (propertyIndex=..., o=0x55df16786630) at ../../include/QtQml/5.15.5/QtQml/private/../../../../../../src/qml/qml/qqmldata_p.h:421 #19 QV4::QObjectWrapper::getProperty (engine=0x55df1469c3b0, object=0x55df16786630, property=0x7f2270119e08) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:236 #20 0x7f22a50e2ac6 in QV4::Moth::VME::interpret (frame=0x7fff86a63180, engine=0x55df1469c3b0, code=0x7f227e76ccba ":,\030\v\260-\003\t\030\006\002") at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.1.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:641 #21 0x7f22a50e732f in QV4::Moth::VME::exec (frame=frame@entry=0x7fff86a639e0, engine=engine@entry=0x55df1469c3b0) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.1.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:466 #22 0x7f22a507a2ce in QV4::Function::call (this=this@entry=0x55df14cb7820, thisObject=, argv=argv@entry=0x7f227f07d508, argc=, context=) at /usr/src/debug/libqt5-qtdeclarative-5.15.5+kde19-1.1.x86_64/src/qml/jsruntime/qv4function.cpp:69 #23 0x7f22a52023fd in QQmlJavaScriptExpression::evaluate (this=this@
[plasmashell] [Bug 439604] Plasma-5.18.7.1, screen lock: textbox/loginbox not activated by keyboard
https://bugs.kde.org/show_bug.cgi?id=439604 Jorge Nerín changed: What|Removed |Added CC||jne...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456235] System Settings crashes in OutputModel::resolutionsStrings()
https://bugs.kde.org/show_bug.cgi?id=456235 --- Comment #3 from Jorge Goncalves --- kscreen-doctor -o Output: 70 Virtual1 enabled connected primary Unknown Modes: 79:3840x2400@60 80:3840x2160@60 81:2880x1800@60 82:2560x1600@60 83:2560x1440@60 84:1920x1440@60 85:1856x1392@60 86:1792x1344@60 87:1920x1200@60 88:1920x1080@60 89:1600x1200@60 90:1680x1050@60 91:1400x1050@60 92:1280x1024@60 93:1440x900@60 94:1280x960@60 95:1360x768@60 96:1280x800@60 97:1152x864@75 98:1280x768@60 99:1280x720@60 100:1024x768@60 101:800x600@60 102:640x480@60 1354:1280x1024@60*! Geometry: 0,0 1280x1024 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown primary Output: 71 Virtual2 disabled connected Unknown Modes: 79:3840x2400@60 80:3840x2160@60 81:2880x1800@60 82:2560x1600@60 83:2560x1440@60 84:1920x1440@60 85:1856x1392@60 86:1792x1344@60 87:1920x1200@60 88:1920x1080@60 89:1600x1200@60 90:1680x1050@60 91:1400x1050@60 92:1280x1024@60 93:1440x900@60 94:1280x960@60 95:1360x768@60 96:1280x800@60 97:1152x864@75 98:1280x768@60 99:1280x720@60 100:1024x768@60 101:800x600@60 102:640x480@60 1351:0x0@60! Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 72 Virtual3 disabled disconnected Unknown Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 73 Virtual4 disabled disconnected Unknown Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 74 Virtual5 disabled disconnected Unknown Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 75 Virtual6 disabled disconnected Unknown Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 76 Virtual7 disabled disconnected Unknown Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 77 Virtual8 disabled disconnected Unknown Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 427360] New: Discover crashes
https://bugs.kde.org/show_bug.cgi?id=427360 Bug ID: 427360 Summary: Discover crashes Product: Discover Version: 5.19.5 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: jmoncayo...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.19.5) Qt Version: 5.15.0 Frameworks Version: 5.74.0 Operating System: Linux 5.4.0-47-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: Al iniciar Discover y acceder a Settings la aplicación se cierra automáticamente. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7f5e6f079617 in QQmlData::wasDeleted (object=0x555b09554ff0) at ../../include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/qml/qqmldata_p.h:338 #5 QV4::QObjectWrapper::wrap (object=0x555b09554ff0, engine=0x555b07bd2be0) at jsruntime/qv4qobjectwrapper_p.h:213 #6 loadProperty (v4=0x555b07bd2be0, object=0x555b09cb2f30, property=...) at jsruntime/qv4qobjectwrapper.cpp:139 #7 0x7f5e6f07a6b2 in QV4::QObjectWrapper::getQmlProperty (engine=engine@entry=0x555b07bd2be0, qmlContext=qmlContext@entry=0x555b09557900, object=0x555b09cb2f30, name=0x7f5e61d1d628, revisionMode=revisionMode@entry=QV4::QObjectWrapper::IgnoreRevision, hasProperty=hasProperty@entry=0x0, property=0x0) at jsruntime/qv4qobjectwrapper.cpp:388 #8 0x7f5e6f1eb1e3 in QV4::QQmlTypeWrapper::virtualGet (m=0x7f5e61d1d618, id=..., receiver=0x7f5e61d1d618, hasProperty=0x0) at ../../include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/common/qv4staticvalue_p.h:325 #9 0x7f5e6effe18c in QV4::Object::get (receiver=0x7f5e61d1d618, hasProperty=0x0, name=0x7f5e61d1d620, this=0x7f5e61d1d618) at ../../include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/jsruntime/qv4string_p.h:167 #10 QV4::Lookup::getterFallback (l=, engine=0x555b07bd2be0, object=...) at jsruntime/qv4lookup.cpp:201 #11 0x7f5e6f09bc87 in QV4::Moth::VME::interpret (frame=0x7fff3e799eb0, engine=0x555b07bd2be0, code=0x7f5e580176d4 ":*\030\006\002") at jsruntime/qv4vme_moth.cpp:638 #12 0x7f5e6f0a11af in QV4::Moth::VME::exec (frame=frame@entry=0x7fff3e799eb0, engine=engine@entry=0x555b07bd2be0) at jsruntime/qv4vme_moth.cpp:463 #13 0x7f5e6f02ddfd in QV4::Function::call (this=this@entry=0x555b082e4050, thisObject=, argv=argv@entry=0x7f5e61d1d5b0, argc=, context=) at jsruntime/qv4function.cpp:69 #14 0x7f5e6f1d4607 in QQmlJavaScriptExpression::evaluate (this=this@entry=0x555b0950cf80, callData=callData@entry=0x7f5e61d1d580, isUndefined=isUndefined@entry=0x7fff3e79a0af) at ../../include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/jsruntime/qv4value_p.h:343 #15 0x7f5e6f1da463 in QQmlBinding::evaluate (this=this@entry=0x555b0950cf80, isUndefined=isUndefined@entry=0x7fff3e79a0af) at ../../include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/jsruntime/qv4jscall_p.h:95 #16 0x7f5e6f1de99d in QQmlNonbindingBinding::doUpdate (this=0x555b0950cf80, watcher=..., flags=..., scope=...) at qml/qqmlbinding.cpp:254 #17 0x7f5e6f1db762 in QQmlBinding::update (this=0x555b0950cf80, flags=...) at qml/qqmlbinding.cpp:194 #18 0x7f5e6f079e45 in QQmlData::flushPendingBinding (propertyIndex=..., o=0x555b09557b40) at ../../include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/qml/qqmldata_p.h:421 #19 QV4::QObjectWrapper::getProperty (engine=0x555b07bd2be0, object=0x555b09557b40, property=0x7f5e54143e68) at jsruntime/qv4qobjectwrapper.cpp:236 #21 QV4::QQmlContextWrapper::lookupScopeObjectProperty (l=0x555b08422080, engine=0x555b07bd2be0, base=0x0) at jsruntime/qv4qmlcontext.cpp:569 #22 0x7f5e6f09b9fc in QV4::Moth::VME::interpret (frame=0x7fff3e79a3e0, engine=0x555b07bd2be0, code=0x7f5e58017630 ":\":#:$p\030\006\002") at jsruntime/qv4vme_moth.cpp:585 #23 0x7f5e6f0a11af in QV4::Moth::VME::exec (frame=frame@entry=0x7fff3e79a3e0, engine=engine@entry=0x555b07bd2be0) at jsruntime/qv4vme_moth.cpp:463 #24 0x7f5e6f02ddfd in QV4::Function::call (this=this@entry=0x555b082e3fb0, thisObject=, argv=argv@entry=0x7f5e61d1d500, argc=, context=) at jsruntime/qv4function.cpp:69 #25 0x7f5e6f1d4607 in QQmlJavaScriptExpression::evaluate (this=this@entry=0x555b0950d0a0, callData=callData@entry=0x7f5e61d1d4d0, isUndefined=isUndefined@entry=0x7fff3e79a5df) at ../../include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/jsruntime/qv4value_p.h:343 #26 0x7f5e6f1da463 in QQmlBinding::evaluate (this=this@entry=0x555b0950d0a0, isUndefined=isUndefined@entry=0x7fff3e79a5df) at ../../include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/jsruntime/qv4jscall_p.h:95 #27 0x7f5e6f1de99d in QQmlNonbindingBinding::doUpdate (
[valgrind] [Bug 441843] New: Memcheck fails on unhandled instruction in libipp
https://bugs.kde.org/show_bug.cgi?id=441843 Bug ID: 441843 Summary: Memcheck fails on unhandled instruction in libipp Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: julien.jo...@stuff-o-matic.com Target Milestone: --- When running my program with Valgrind & memcheck, it fails with an unhandled instruction message: vex amd64->IR: unhandled instruction bytes: 0x48 0xF 0xFC 0xD 0x7 0xBF 0x3E 0x0 0xF 0x70 vex amd64->IR: REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==2678158== valgrind: Unrecognised instruction at address 0xd000b1. ==2678158==at 0xD000B1: ??? ==2678158==by 0xD0AF05: y8_ippiFilterDeblockingLuma_VerEdge_H264_8u_C1IR It occurs with Valgrind 3.17 built from source on Centos 7.4. My program uses ipp 8.1.1. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 441843] Memcheck fails on unhandled instruction in libipp
https://bugs.kde.org/show_bug.cgi?id=441843 Julien Jorge changed: What|Removed |Added CC||julien.jorge@stuff-o-matic. ||com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423766] systemsettings5 crash
https://bugs.kde.org/show_bug.cgi?id=423766 --- Comment #4 from Jorge Girardi --- I fixed the problem by removing kde /home//.conf configuration file and rebooting to generate a clean one. It works well. El miércoles, 22 de julio de 2020 05:07:22 p. m. GMT-3, Christoph Feck escribió: https://bugs.kde.org/show_bug.cgi?id=423766 --- Comment #2 from Christoph Feck --- Every thread has an event loop, that's not a problem. Using a nested QEventLoop would be problematic, but that is not visible from the backtrace. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 475402] New: vex amd64->IR: unhandled instruction bytes: 0xC5 0x79 0xD6 0xC0 0x4C 0x8D 0x9C 0x24 0xA0 0x2
https://bugs.kde.org/show_bug.cgi?id=475402 Bug ID: 475402 Summary: vex amd64->IR: unhandled instruction bytes: 0xC5 0x79 0xD6 0xC0 0x4C 0x8D 0x9C 0x24 0xA0 0x2 Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: julien.jo...@gmx.fr Target Milestone: --- When running my program with Valgrind & memcheck, it fails with an unhandled instruction message: vex amd64->IR: unhandled instruction bytes: 0xC5 0x79 0xD6 0xC0 0x4C 0x8D 0x9C 0x24 0xA0 0x2 vex amd64->IR: REX=0 REX.W=0 REX.R=1 REX.X=0 REX.B=0 vex amd64->IR: VEX=1 VEX.L=0 VEX.n=0x0 ESC=0F vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0 ==137781== valgrind: Unrecognised instruction at address 0x4cf081. ==137781==at 0x4CF081: _mm_set_epi64x (emmintrin.h:595) ==137781==by 0x4CF081: _mm_set_epi64 (emmintrin.h:601) ==137781==by 0x4CF081: _mm_loadl_epi64 (emmintrin.h:712) It occurs with Valgrind 3.22 built from source (commit 97508f5561756a43f054c1d8e06c3e318124c9c3) but also with 3.19 from Ubuntu repositories. The program is compiled using GCC 13.1.0, and executed on the same machine. Passing -v shows: Arch and hwcaps: AMD64, LittleEndian, amd64-cx16-lzcnt-rdtscp-sse3-ssse3-avx-avx2-bmi-f16c-rdrand-rdseed. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 475483] New: System Update stops at 17% (since more than 24 hours ago, no change)
https://bugs.kde.org/show_bug.cgi?id=475483 Bug ID: 475483 Summary: System Update stops at 17% (since more than 24 hours ago, no change) Classification: Applications Product: Discover Version: 5.24.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: jrm.m...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 162230 --> https://bugs.kde.org/attachment.cgi?id=162230&action=edit screen capture Updating System on Discover, as usual, the task goes to 17% and stops. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 475483] System Update stops at 17% (since more than 24 hours ago, no change)
https://bugs.kde.org/show_bug.cgi?id=475483 Jorge Medina changed: What|Removed |Added CC||jrm.m...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 419274] Saving settings aren't respected
https://bugs.kde.org/show_bug.cgi?id=419274 Jorge Nerín changed: What|Removed |Added CC||jne...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423766] New: systemsettings5 crash
https://bugs.kde.org/show_bug.cgi?id=423766 Bug ID: 423766 Summary: systemsettings5 crash Product: systemsettings Version: 5.18.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jorgegira...@yahoo.com.ar Target Milestone: --- Application: systemsettings5 (5.18.5) Qt Version: 5.12.7 Frameworks Version: 5.71.0 Operating System: Linux 5.3.18-lp152.14-default x86_64 Windowing system: X11 Distribution: openSUSE Leap 15.2 -- Information about the crash: - What I was doing when the application crashed: I was downloading global theme opensuse dark when systemsettings5 crash The crash can be reproduced every time. -- Backtrace: Application: Preferencias del sistema (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f01c455d900 (LWP 9593))] Thread 10 (Thread 0x7f019135e700 (LWP 9612)): #0 0x7f01b8f05ab9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f01b8eb9b67 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f01b8eba6ab in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f01b8eba88c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f01c037b19b in QEventDispatcherGlib::processEvents (this=0x55da658f0d80, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f01c031c32a in QEventLoop::exec (this=this@entry=0x7f019135dc40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f01c014210a in QThread::exec (this=) at thread/qthread.cpp:531 #7 0x7f01be129146 in ?? () from /usr/lib64/libQt5Quick.so.5 #8 0x7f01c01438b2 in QThreadPrivate::start (arg=0x55da65909400) at thread/qthread_unix.cpp:361 #9 0x7f01bb6484f9 in start_thread () from /lib64/libpthread.so.0 #10 0x7f01bf9e3f2f in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7f0191b5f700 (LWP 9611)): #0 0x7f01bf9d5220 in read () from /lib64/libc.so.6 #1 0x7f01b8f019a0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f01b8eba298 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f01b8eba720 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f01b8eba88c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f01c037b19b in QEventDispatcherGlib::processEvents (this=0x55da6574d6b0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f01c031c32a in QEventLoop::exec (this=this@entry=0x7f0191b5ecb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f01c014210a in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7f01c01438b2 in QThreadPrivate::start (arg=0x55da6574d620) at thread/qthread_unix.cpp:361 #9 0x7f01bb6484f9 in start_thread () from /lib64/libpthread.so.0 #10 0x7f01bf9e3f2f in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f0195c9e700 (LWP 9603)): #0 0x7f01bf9de7a9 in syscall () from /lib64/libc.so.6 #1 0x7f01c0145f94 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0, val=, op=0, addr=) at thread/qfutex_p.h:92 #2 QtLinuxFutex::futexWait > (expectedValue=, futex=...) at thread/qfutex_p.h:107 #3 futexSemaphoreTryAcquire_loop (timeout=-1, nn=8589934593, curValue=, u=...) at thread/qsemaphore.cpp:219 #4 futexSemaphoreTryAcquire (timeout=-1, n=, u=...) at thread/qsemaphore.cpp:262 #5 QSemaphore::acquire (this=0x7f01bcfa1460, n=) at thread/qsemaphore.cpp:326 #6 0x7f01bcce3044 in ?? () from /usr/lib64/libQt5Network.so.5 #7 0x7f01c01438b2 in QThreadPrivate::start (arg=0x7f01bcfa1440) at thread/qthread_unix.cpp:361 #8 0x7f01bb6484f9 in start_thread () from /lib64/libpthread.so.0 #9 0x7f01bf9e3f2f in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f019649f700 (LWP 9602)): #0 0x7f01bf9d96db in poll () from /lib64/libc.so.6 #1 0x7f01b8eba779 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f01b8eba88c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f01c037b19b in QEventDispatcherGlib::processEvents (this=0x55da64d6f070, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f01c031c32a in QEventLoop::exec (this=this@entry=0x7f019649ecb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f01c014210a in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f01c01438b2 in QThreadPrivate::start (arg=0x55da64f3e650) at thread/qthread_unix.cpp:361 #7 0x7f01bb6484f9 in start_thread () from /lib64/libpthread.so.0 #8 0x7f01bf9e3f2f in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f01979bf700 (LWP 9601)): #0 0x7f01bf9daac7 in ioctl () from /lib64/libc.so.6 #1 0x7f01a5c219fc in ?? () from /usr/lib64/libnvidia-glcore.so.440.82 #2 0x7f01a5c229e7 in ?? () from /usr/lib64/libnvidia-glcore.so.440.8
[kalarm] [Bug 424204] New: Feature request: Send sound output to device other than default
https://bugs.kde.org/show_bug.cgi?id=424204 Bug ID: 424204 Summary: Feature request: Send sound output to device other than default Product: kalarm Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: djar...@kde.org Reporter: jorge.delg...@gmail.com Target Milestone: --- SUMMARY Nowadays, my USB headphones I use for VoIP calls (work and personal) are plugged into my desktop computer 100% of the time. It would be GREAT for some apps like KAlarm to be able to select the output device in the case I'm away from my computer I can still hear the notification. KAlarm does not show under the Applications list in the general sound configuration. Not even while playing a sound. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 424204] Feature request: Send sound output to device other than default
https://bugs.kde.org/show_bug.cgi?id=424204 --- Comment #1 from Jorge Delgado --- I think this applies to a lot of people not only with the "pandemic" but also now there are more and more people using softphones/voip. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392961] Layout shortcut makes all other shortcuts starting with that combination unavailable
https://bugs.kde.org/show_bug.cgi?id=392961 Jorge Nerín changed: What|Removed |Added CC||jne...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 430238] New: Object focus after scan goes unnecesarily to ABOUT button. Lowers efficiency.
https://bugs.kde.org/show_bug.cgi?id=430238 Bug ID: 430238 Summary: Object focus after scan goes unnecesarily to ABOUT button. Lowers efficiency. Product: Skanlite Version: 2.2.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: jorge.delg...@gmail.com Target Milestone: --- SUMMARY Default object focus after scan is the ABOUT button. In a multiple page scan job it would be great if, after clicking SCAN on the first page and saving the output, the focus would remain in the SCAN button. Then a simple ENTER or SPACE on the keyb will start a new page scan. Leaving the mouse to do the click while standing (because the scanner is not right next to the mouse/computer) is prone for some failed click as it may move. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 434526] New: okular snap not run
https://bugs.kde.org/show_bug.cgi?id=434526 Bug ID: 434526 Summary: okular snap not run Product: okular Version: 20.12.3 Platform: Snap OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: jlainezboni...@gmail.com Target Milestone: --- SUMMARY I installed okular : sudo snap install okular But when I wanted to run : snap run okular I get the following error: /snap/okular/108/kf5-launch: line 226: exec: okular: not found STEPS TO REPRODUCE 1. sudo snap install okular 2. snap run okular OBSERVED RESULT /snap/okular/108/kf5-launch: line 226: exec: okular: not found EXPECTED RESULT Open okular pdf view document SOFTWARE/OS VERSIONS Linux: Ubuntu KDE Frameworks Version: 5.47.0 snap Qt Version: ADDITIONAL INFORMATION I had installed the snap okular application months ago and it was working perfectly, suddenly it disappeared from my application menu, I uninstalled and reinstalled it but it no longer opened the app. The kf5-launch file referred to in the error is not inside the 108/ directory, but outside of it. But I could not move them, since they only have read permissions. All the other snap applications I have installed (vlc, odio) are working fine, only okular stopped working. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 434526] okular snap not run
https://bugs.kde.org/show_bug.cgi?id=434526 Jorge Lainez changed: What|Removed |Added CC||jlainezboni...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 434526] okular snap not run
https://bugs.kde.org/show_bug.cgi?id=434526 --- Comment #4 from Jorge Lainez --- thanks for fixed it -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 402019] Accents not send to device
https://bugs.kde.org/show_bug.cgi?id=402019 Jorge Araújo changed: What|Removed |Added Version|1.10|23.08.5 CC||labo...@pm.me --- Comment #7 from Jorge Araújo --- I confirm this bug still exists. When I type a character with accent it shows in the remote keyboard field on the desktop instead of showing on the device. I am using Debian testing, KDE 5.27.11, Keyboard language PT -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 492294] New: Dolphin shows some garbled filenames of a mounted directory with UTF-8 characters in the path
https://bugs.kde.org/show_bug.cgi?id=492294 Bug ID: 492294 Summary: Dolphin shows some garbled filenames of a mounted directory with UTF-8 characters in the path Classification: Applications Product: dolphin Version: 24.08.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: jorgebla...@mac.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 173019 --> https://bugs.kde.org/attachment.cgi?id=173019&action=edit Screen capture of a Nautilus file info window vs the same in Dolphin showing the same file SUMMARY Dolphin fails to display all filenames of an SMB mounted path that includes UTF-8 japanese characters. STEPS TO REPRODUCE 1. Mount SMB share 2. Go to directory with UTF-8 characters 3. some filenames are garbled OBSERVED RESULT Garbled filenames (some) EXPECTED RESULT Full filenames SOFTWARE/OS VERSIONS Linux/KDE Plasma: yes KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Gnome FIles / Nautilus shows filenames normally -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491720] New: plasmashell crash when right click on a task manager's application to show the popup menu
https://bugs.kde.org/show_bug.cgi?id=491720 Bug ID: 491720 Summary: plasmashell crash when right click on a task manager's application to show the popup menu Classification: Plasma Product: plasmashell Version: 5.24.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: jne...@gmail.com CC: qydwhotm...@gmail.com Target Milestone: 1.0 SUMMARY I opened a new google chrome guest window, and I right clicked on the task manager's entry to show the popup menu to send it to another virtual desktop, plasmashell crashed and restarted, trying again succeded then. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Application: plasmashell (5.24.7) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 6.8.0-40-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.4 LTS DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x742c1e9d087e in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x742c1e9b73dc in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x742c1e9bc965 in QSGBatchRenderer::Renderer::renderBatches() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x742c1e9bd352 in QSGBatchRenderer::Renderer::render() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x742c1e9a4924 in QSGRenderer::renderScene(QSGBindable const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x742c1e9a4df3 in QSGRenderer::renderScene(unsigned int) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x742c1ea0aa47 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x742c1ea7a5f9 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x742c1ea1945d in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x742c1ea19e07 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x742c1ca1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x742c1c494ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #16 0x742c1c526850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 21 (Thread 0x742bce000640 (LWP 2021) "plasmash:gdrv0"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x5b2f664d1fe8) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x5b2f664d1fe8, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x742c1c493a41 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5b2f664d1f98, cond=0x5b2f664d1fc0) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x5b2f664d1fc0, mutex=0x5b2f664d1f98) at ./nptl/pthread_cond_wait.c:627 #5 0x742c1491952d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #6 0x742c148c98bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #7 0x742c1491945b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #8 0x742c1c494ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #9 0x742c1c526850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 20 (Thread 0x742bcea00640 (LWP 2020) "plasma:traceq0"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x5b2f664c48b0) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x5b2f664c48b0, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x742c1c493a41 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5b2f664c4860, cond=0x5b2f664c4888) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x5b2f664c4888, mutex=0x5b2f664c4860) at ./nptl/pthread_cond_wait.c:627 #5 0x742c1491952d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #6 0x742c148c98bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #7 0x742c1491945b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #8 0x742c1c494ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #9 0x742c1c526850 in c
[kturtle] [Bug 270031] Kturtle crashes sometimes when lauching a script
https://bugs.kde.org/show_bug.cgi?id=270031 José JORGE changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 --- Comment #7 from José JORGE --- Still reproductible :open in khotnewstuff 2 scripts, it always crash with "Hole or summit" opened in second place. -- You are receiving this mail because: You are watching all bug changes.
[kturtle] [Bug 196558] KTurtle Crash when opening new sample while other sample was running
https://bugs.kde.org/show_bug.cgi?id=196558 José JORGE changed: What|Removed |Added CC||lists.jjo...@free.fr --- Comment #3 from José JORGE --- Was this code reworked? Or maybe this is related to bug 270031? -- You are receiving this mail because: You are watching all bug changes.
[kblocks] [Bug 406272] kblocks does not play the theme sounds
https://bugs.kde.org/show_bug.cgi?id=406272 --- Comment #2 from José JORGE --- (In reply to Albert Astals Cid from comment #1) > Yeah by looking at the existing themes it seems like at some point the sound > files where customizable (or at least that was the plan), but looking at the > code it isn't, it just plays the three hardcoded files in the code. Thanks for the bootstrap : I did that crazy thing which is trying to contribute my first code to KDE, while I use it since 1998 ;-) D21472 and D21477 in Phabricator waiting to be reviewed. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 407116] New: Identity : Username is required to reset password
https://bugs.kde.org/show_bug.cgi?id=407116 Bug ID: 407116 Summary: Identity : Username is required to reset password Product: www.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: lists.jjo...@free.fr Target Milestone: --- This is a bug about the website https://identity.kde.org/index.php?r=registration/index I have created a user account years ago. Now I come back, and do not remember the username or the password. Only the email. It should be possible to reset password only with the email. Thanks -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 407116] Identity : Username is required to reset password
https://bugs.kde.org/show_bug.cgi?id=407116 José JORGE changed: What|Removed |Added CC||lists.jjo...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 412359] New: Baloo file extractor
https://bugs.kde.org/show_bug.cgi?id=412359 Bug ID: 412359 Summary: Baloo file extractor Product: frameworks-baloo Version: 5.62.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: the.maggot.nameless@gmail.com Target Milestone: --- Application: baloo_file (5.62.0) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.3.1-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: When my system starts. - Unusual behavior I noticed: The application stops and notice every time about this. - Custom settings of the application: Default settings. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f46497aaf40 (LWP 763))] Thread 3 (Thread 0x7f0643fff700 (LWP 890)): [KCrash Handler] #6 0x7f464d656755 in raise () from /usr/lib/libc.so.6 #7 0x7f464d641851 in abort () from /usr/lib/libc.so.6 #8 0x7f464c62c753 in ?? () from /usr/lib/liblmdb.so #9 0x7f464c621435 in ?? () from /usr/lib/liblmdb.so #10 0x7f464c622676 in ?? () from /usr/lib/liblmdb.so #11 0x7f464c6228b3 in ?? () from /usr/lib/liblmdb.so #12 0x7f464c6244ec in ?? () from /usr/lib/liblmdb.so #13 0x7f464c627619 in mdb_cursor_put () from /usr/lib/liblmdb.so #14 0x7f464c62a4ab in mdb_put () from /usr/lib/liblmdb.so #15 0x7f464e130c8a in Baloo::DocumentTimeDB::put(unsigned long long, Baloo::DocumentTimeDB::TimeInfo const&) () from /usr/lib/libKF5BalooEngine.so.5 #16 0x7f464e157cd5 in Baloo::WriteTransaction::replaceDocument(Baloo::Document const&, QFlags) () from /usr/lib/libKF5BalooEngine.so.5 #17 0x7f464e14a925 in Baloo::Transaction::replaceDocument(Baloo::Document const&, QFlags) () from /usr/lib/libKF5BalooEngine.so.5 #18 0x55e4c11ee7b6 in ?? () #19 0x7f464dbd29a2 in ?? () from /usr/lib/libQt5Core.so.5 #20 0x7f464dbcf5b0 in ?? () from /usr/lib/libQt5Core.so.5 #21 0x7f464c68757f in start_thread () from /usr/lib/libpthread.so.0 #22 0x7f464d7180e3 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f464924a700 (LWP 791)): #0 0x7f464d70d667 in poll () from /usr/lib/libc.so.6 #1 0x7f464bc75130 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f464bc75201 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f464ddf5a1c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f464dd9c4ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f464dbce385 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f464e17cb37 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x7f464dbcf5b0 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f464c68757f in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f464d7180e3 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f46497aaf40 (LWP 763)): #0 0x7f464d6e097b in __getdents64 () from /usr/lib/libc.so.6 #1 0x7f464d6e0a45 in readdir64 () from /usr/lib/libc.so.6 #2 0x7f464dd3966e in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f464dcc7ffc in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f464dcc885e in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f464dcc8cfe in QDirIterator::QDirIterator(QString const&, QFlags, QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x55e4c11f6bcd in ?? () #7 0x55e4c120860e in ?? () #8 0x55e4c120694c in ?? () #9 0x7f464ddca44a in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #10 0x7f464dd9d9a0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #11 0x7f464dda0739 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #12 0x7f464ddf6404 in ?? () from /usr/lib/libQt5Core.so.5 #13 0x7f464bc733ae in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #14 0x7f464bc751c1 in ?? () from /usr/lib/libglib-2.0.so.0 #15 0x7f464bc75201 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #16 0x7f464ddf5a03 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #17 0x7f464dd9c4ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #18 0x7f464dda4326 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #19 0x55e4c11dc402 in ?? () #20 0x7f464d642ee3 in __libc_start_main () from /usr/lib/libc.so.6 #21 0x55e4c11dc5be in ?? () [Inferior 1 (process 763) detached] Possible duplicates by query: bug 410403, bug 408293, bug 406173. Reported using DrKonqi --
[Powerdevil] [Bug 405508] New: powerdevil is not clever when the battery is very big
https://bugs.kde.org/show_bug.cgi?id=405508 Bug ID: 405508 Summary: powerdevil is not clever when the battery is very big Product: Powerdevil Version: 5.15.1 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lists.jjo...@free.fr Target Milestone: --- SUMMARY I have a laptop with a secondary big battery : it gives me more than 50 hours usable time. As I can only configure critical level to 0%, it happens when I still have 2 hours of battery remaining. Maybe powerdevil could ignore the percentage as long as upower indicates more than 15 minutes remaining? ADDITIONAL INFORMATION Here is my upower with the big battery empty, and the internal one almost full. Note the percentage lower than 5% while I still have 3,6 hours. [jose@burro tc]$ upower -d Device: /org/freedesktop/UPower/devices/line_power_AC native-path: AC power supply: yes updated: sáb 16 mar 2019 07:15:54 CET (391 seconds ago) has history: no has statistics: no line-power warning-level: none online: no icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Hewlett-Packard model:Primary serial: 02908 2010/10/14 power supply: yes updated: sáb 16 mar 2019 07:22:03 CET (22 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging warning-level: none energy: 44,1891 Wh energy-empty:0 Wh energy-full: 44,8884 Wh energy-full-design: 44,3889 Wh energy-rate: 12,2433 W voltage: 12,432 V time to empty: 3,6 hours percentage: 98% capacity:100% technology: lithium-ion icon-name: 'battery-full-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT1 native-path: BAT1 vendor: Hewlett-Packard model:Travel serial: 09255 2010/05/23 power supply: yes updated: sáb 16 mar 2019 07:22:01 CET (24 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging warning-level: action energy: 0 Wh energy-empty:0 Wh energy-full: 964,161 Wh energy-full-design: 0,0148 Wh energy-rate: 0 W voltage: 13,289 V percentage: 0% capacity:100% technology: lithium-ion icon-name: 'battery-caution-symbolic' History (charge): 1552717237 0,000 discharging History (rate): 1552717237 0,000 discharging Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: sáb 16 mar 2019 07:20:37 CET (108 seconds ago) has history: no has statistics: no battery present: yes state: discharging warning-level: low energy: 44,1891 Wh energy-full: 1009,05 Wh energy-rate: 12,2433 W time to empty: 3,6 hours percentage: 4,37928% icon-name: 'battery-caution-symbolic' Daemon: daemon-version: 0.99.9 on-battery: yes lid-is-closed: no lid-is-present: yes critical-action: HybridSleep -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 405508] powerdevil is not clever when the battery is very big
https://bugs.kde.org/show_bug.cgi?id=405508 --- Comment #3 from José JORGE --- (In reply to Nate Graham from comment #2) > Not sure that would be very user-friendly, at least not for the common case. > Most people don't think of their battery's remaining charge in watt-hours. Yes, it is not user friendly. And I have an old Asus EeePC 901 which only reports it's charge in percentage steps, nothing else appears in upower. Another idea could be the way percentage are rounded : for me, it is fine to keep current way, but the 0% battery level should not happen when we have 0.9%, but a real 0%? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 405508] powerdevil is not clever when the battery is very big
https://bugs.kde.org/show_bug.cgi?id=405508 --- Comment #5 from José JORGE --- (In reply to Kai Uwe Broulik from comment #4) > So, percent doesn't work for large batteries, Watt-hours is "unfriendly", > remaining time is unreliable and constantly changing... Maybe a solution would be to allow to write manually a smaller number : - keep the scroll with mouse for 1% steps - allow to write manually a 0.1% value? -- You are receiving this mail because: You are watching all bug changes.
[kblocks] [Bug 406272] New: kblocks does not play the theme sounds
https://bugs.kde.org/show_bug.cgi?id=406272 Bug ID: 406272 Summary: kblocks does not play the theme sounds Product: kblocks Version: unspecified Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: squall.leonhart@gmail.com Reporter: lists.jjo...@free.fr CC: kde-games-b...@kde.org Target Milestone: --- I have created an Europe theme for kblocks, and added it to opendesktop.org so that it can be installed from kblocks theme configuration. Unfortunately, the modified sounds are not played, it still plays the defaults sounds. HOW TO REPRODUCE - open kblocks - config -> theme -> get more theme - install europe theme - select it - play, listen the sounds Compare to the sound you hear with : vlc ~/.local/share/kblocks/themes/europe/*ogg -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 420177] New: keyboard is qwerty
https://bugs.kde.org/show_bug.cgi?id=420177 Bug ID: 420177 Summary: keyboard is qwerty Product: krdc Version: 19.04 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: VNC Assignee: uwol...@kde.org Reporter: lists.jjo...@free.fr Target Milestone: --- SUMMARY When I connect to a system running Krfb, the keyboard is qwerty, while both systems are azerty. STEPS TO REPRODUCE 1. Configure 2 systems with french keyboard. 2. Launch Krfb in the first one 3. Launch Krdc in the second one and connect OBSERVED RESULT Typing 'a' gives 'q'. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 420177] keyboard is qwerty
https://bugs.kde.org/show_bug.cgi?id=420177 José JORGE changed: What|Removed |Added Platform|Other |Mageia RPMs CC||lists.jjo...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 414036] ksgrd_network_helper uses a lot of CPU on high network load
https://bugs.kde.org/show_bug.cgi?id=414036 --- Comment #3 from José JORGE --- (In reply to Jan Przybylak from comment #2) > After some testing it seems to me that this is caused by having the columns > "Upload" and/or "Download" activated in the list of all processes. I removed > these columns and ksgrd_network_helper disappered entirely. YEs, this bug is against the new helper for this two columns. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403791] Replace all passivenotification messages with InlineMessages
https://bugs.kde.org/show_bug.cgi?id=403791 Jorge Chaves changed: What|Removed |Added CC||jlcarv.cha...@gmail.com --- Comment #4 from Jorge Chaves --- Não consigo atualizar o Discover, nem instalar programas com ele pois exibe a mensagem que não há conexão. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 414036] ksgrd_network_helper uses a lot of CPU on high network load
https://bugs.kde.org/show_bug.cgi?id=414036 --- Comment #14 from José JORGE --- (In reply to iamashwin99 from comment #12) > Can someone find out if this works for them? This can't be the solution : the CPU load happens when a lot of small packets are travelling in the network, and ksysguard looks inside them to know which program is using them. The fact that chromium network service generates more packets when running is only a side effect. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 285544] Per-application network monitoring similar to IO Read/Write columns
https://bugs.kde.org/show_bug.cgi?id=285544 José JORGE changed: What|Removed |Added CC||lists.jjo...@free.fr Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from José JORGE --- This was implemented with ksysguard 5.17.2, thanks to Jan Kusanagi -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 414036] New: ksgrd_network_helper uses a lot of CPU on high network load
https://bugs.kde.org/show_bug.cgi?id=414036 Bug ID: 414036 Summary: ksgrd_network_helper uses a lot of CPU on high network load Product: ksysguard Version: 5.17.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: lists.jjo...@free.fr Target Milestone: --- Created attachment 123844 --> https://bugs.kde.org/attachment.cgi?id=123844&action=edit helper launched with --stats show more than 500 packets per second New helper for ksysguard shows very high CPU usage when it processes a lot of packets STEPS TO REPRODUCE 1. launch ksysguard in the first tab 2. wget http://ftp.free.fr/mirrors/mageia.org/iso/7.1/Mageia-7.1-i586/Mageia-7.1-i586.iso 3. watch CPU usage OBSERVED RESULT Very high usage EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[katomic] [Bug 401318] New: Shift-Tab segfaults
https://bugs.kde.org/show_bug.cgi?id=401318 Bug ID: 401318 Summary: Shift-Tab segfaults Product: katomic Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dim...@gmail.com Reporter: lists.jjo...@free.fr CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY Shift-Tab segfaults STEPS TO REPRODUCE 1. Launch 2. Press Shift +Tab 3. Erreur de segmentation (core dumped) Mageia 6 KDE Frameworks 5.42.0 Qt 5.9.4 (construit sur 5.9.3) Le système de fenêtres xcb EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[katomic] [Bug 401318] Shift-Tab segfaults
https://bugs.kde.org/show_bug.cgi?id=401318 José JORGE changed: What|Removed |Added Version|unspecified |3.0 Platform|Other |Mageia RPMs -- You are receiving this mail because: You are watching all bug changes.
[katomic] [Bug 401318] Shift-Tab segfaults
https://bugs.kde.org/show_bug.cgi?id=401318 --- Comment #1 from José JORGE --- It shows version 4.0, which is not in the version list here. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 389483] VLC leaks playing video details to lock screen
https://bugs.kde.org/show_bug.cgi?id=389483 Jorge Nerín changed: What|Removed |Added CC||jne...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391147] New: Location Bar crashes Dolphin when dragging contents from folder panel into desired location
https://bugs.kde.org/show_bug.cgi?id=391147 Bug ID: 391147 Summary: Location Bar crashes Dolphin when dragging contents from folder panel into desired location Product: dolphin Version: 16.08.3 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: gmpin...@gmail.com Target Milestone: --- Intermittently, when dragging items from the folder panel into the location bar immediately above, where the directory hierarchy is displayed in a drop-down list, Dolphin crashes. This also happens in tabbed windows. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378190] Xdebug support for PHP debugging (port from kdelibs/Qt4 -> KF5/Qt5)
https://bugs.kde.org/show_bug.cgi?id=378190 José JORGE changed: What|Removed |Added CC||lists.jjo...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378190] Xdebug support for PHP debugging (port from kdelibs/Qt4 -> KF5/Qt5)
https://bugs.kde.org/show_bug.cgi?id=378190 --- Comment #2 from José JORGE --- It is a pity no one with C++ skills needs this one... I just discovered upgrading from Mageia 5 to 6 that I have lost Kdevelop PHP debug... -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 368833] Incomplete and incorrect animation icons
https://bugs.kde.org/show_bug.cgi?id=368833 --- Comment #2 from Jorge Villaseñor --- An animated one should be located on icons/breeze/animations, it would be good to have it on multiple sizes too. I'm interested on the 16x16 one. And if a static version of it is wanted, it should be available on icons/breeze/status/16 As reference, I noticed the Oxygen theme has those icons. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 392507] New: no reconoce el celular para cargar las fotos a la computadora
https://bugs.kde.org/show_bug.cgi?id=392507 Bug ID: 392507 Summary: no reconoce el celular para cargar las fotos a la computadora Product: dolphin Version: 17.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jssor...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Created attachment 111729 --> https://bugs.kde.org/attachment.cgi?id=111729&action=edit PANTALLA QUE MUESTRA Al conectar mi celular MOTOROLA G4 a la computadora, no puede acceder a la memoria, indica un error desconocido 150 No puedo abrir para ver las fotos del celular y descargarlo a mi computadora, mi sistema es MANJARO LINUX AÑADO UN ARCHIVO PARA QUE SE VEA LA FALLA AGRADECERIA QUE ME ORIENTEN PARA SOLUCIONAR ESTE PROBLEMA GRACIAS. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 378832] use of vaapi in transcoding and rendering
https://bugs.kde.org/show_bug.cgi?id=378832 José JORGE changed: What|Removed |Added CC||lists.jjo...@free.fr --- Comment #5 from José JORGE --- (In reply to Anton Gubarkov from comment #4) > I was able to patch manually. I confirm this is working for me. Thanks a lot! Can you please paste the proxy clip line you are using. I got no success with adding "-vaapi_device /dev/dri/renderD128 -hwaccel vaapi -hwaccel_output_format vaapi -i" before the existing parameters in default MPEG2 proxy clips. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 392703] New: crash importing directly from firefox, no crash importing from file menu
https://bugs.kde.org/show_bug.cgi?id=392703 Bug ID: 392703 Summary: crash importing directly from firefox, no crash importing from file menu Product: kmymoney Version: 5.0.1 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: lists.jjo...@free.fr Target Milestone: --- I have associated kmymoney with ofx files in firefox. With version 4.x I had no problem with this. Now with kmymoney 5.0.1, it crashes at the end of the import, after the resume screen saying import was done with success. If instead I open the ofx file from the menu import ofx, I get no crash. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 392703] crash importing directly from firefox, no crash importing from file menu
https://bugs.kde.org/show_bug.cgi?id=392703 --- Comment #2 from José JORGE --- (In reply to Thomas Baumgart from comment #1) > Can you provide a sample file (without personal data) that causes the crash > to happen? Also, can you provide a backtrace of the crash? I think the file is not the problem, as I have no segfault if I open it from the file import menu... Well, it did not segfault when I tried to xdg-open the ofxfile under gdb the first 2 tries, but the third segfaulted : (gdb) backtrace #0 0x719002f4 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #1 0x718040b1 in QIODevice::channelReadyRead(int) () from /lib64/libQt5Core.so.5 #2 0x71c8525c in QAbstractSocketPrivate::canReadNotification() () from /lib64/libQt5Network.so.5 #3 0x71c94fc1 in QReadNotifier::event(QEvent*) () from /lib64/libQt5Network.so.5 #4 0x723b951c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #5 0x723c09c7 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #6 0x718d5c68 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #7 0x719293cd in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #8 0x7fffe7867ac7 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #9 0x7fffe7867cf8 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #10 0x7fffe7867d9c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #11 0x71928776 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #12 0x718d3e0a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #13 0x718dc9c8 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #14 0x00471182 in runKMyMoney(QApplication&, std::unique_ptr >, QUrl const&, bool) () #15 0x0046fc5e in main () Is this enough? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 378832] use of vaapi in transcoding and rendering
https://bugs.kde.org/show_bug.cgi?id=378832 --- Comment #7 from José JORGE --- (In reply to Anton Gubarkov from comment #6) > I use the following line for decode&rescale with subsequent encode to DNxHD > Thanks, I was able to get fast proxy file with this setting. Now I have another problem : the proxy clip is used when reading directly the clip, but is not used anymore when the clip is in the timeline. I think I will open a bug report about that. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384764] Proxy clips on time line play slower than original clips
https://bugs.kde.org/show_bug.cgi?id=384764 José JORGE changed: What|Removed |Added CC||lists.jjo...@free.fr --- Comment #9 from José JORGE --- (In reply to mikko.rapeli from comment #8) > And that's why proxy clips are slower to play than originals, though the > different code does impact too. h264 original is tougher to decode than > mpeg2video proxy. I've just upgraded my Kdenlive from 16.x to 17.12.2 and I can see the same bug : the proxy clip is used when playing the single clip, but not used anymore when the clip is in the timeline. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 392703] crash importing directly from firefox, no crash importing from file menu
https://bugs.kde.org/show_bug.cgi?id=392703 --- Comment #4 from José JORGE --- Created attachment 111840 --> https://bugs.kde.org/attachment.cgi?id=111840&action=edit anonymised ofx file that triggers the bug I can trigger the bug opening this file with xdg-open -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 371909] No image or sound on TNT
https://bugs.kde.org/show_bug.cgi?id=371909 José JORGE changed: What|Removed |Added CC||lists.jjo...@free.fr --- Comment #6 from José JORGE --- Looks like this bug could be closed. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 392703] crash importing directly from firefox, no crash importing from file menu
https://bugs.kde.org/show_bug.cgi?id=392703 José JORGE changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #7 from José JORGE --- (In reply to Thomas Baumgart from comment #6) > Does this still happen with newer versions of the project? You might want to > try a recent AppImage file if your distro does not have a newer version > available. Fixed with 5.0.2 version in my Mageia distro, thanks. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 403760] New: Don't suspend system on button event if the screen is in DPMS mode
https://bugs.kde.org/show_bug.cgi?id=403760 Bug ID: 403760 Summary: Don't suspend system on button event if the screen is in DPMS mode Product: Powerdevil Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lists.jjo...@free.fr Target Milestone: --- If a user configures the power button to suspend the system, it works as expected. But there is a use case where it should not : when the screen is black. An average user press the power button when the screen is black to poweron the system. In this case it suspends the system. Windows systems only awake the screen in this case, which seems more ergonomic. STEPS TO REPRODUCE 1. Configure suspend to RAM when power button is used. 2. Put the screen in energy save (ex. "xset dpms force off") 3. Press the power button OBSERVED RESULT The system awakes the monitor and suspends. EXPECTED RESULT The system only awakes the monitor. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 394752] New: Discovery crash while viewing application
https://bugs.kde.org/show_bug.cgi?id=394752 Bug ID: 394752 Summary: Discovery crash while viewing application Product: Discover Version: 5.12.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: jorgea...@gmail.com Target Milestone: --- Application: plasma-discover (5.12.5) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-22-generic x86_64 Distribution: Ubuntu 18.04 LTS -- Information about the crash: - What I was doing when the application crashed: Selected wireshark gtk option to get more information in Discovery app -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f658e59c800 (LWP 2874))] Thread 10 (Thread 0x7f65425a2700 (LWP 2920)): #0 0x7f6589b5dbf9 in __GI___poll (fds=0x7f6534002960, nfds=1, timeout=91402) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f658434f439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f658434f54c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f658a4ab90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f658a4509ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f658a26f22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f658a27416d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f658647c6db in start_thread (arg=0x7f65425a2700) at pthread_create.c:463 #8 0x7f6589b6a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f65529e1700 (LWP 2917)): #0 0x7f6584394cd9 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f658434f538 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f658a4ab90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f658a4509ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f658a26f22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f658a27416d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f658647c6db in start_thread (arg=0x7f65529e1700) at pthread_create.c:463 #7 0x7f6589b6a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f65439dc700 (LWP 2886)): #0 0x7f6589b5dbf9 in __GI___poll (fds=0x7f653c00d340, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f658434f439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f658434f54c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f658a4ab90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f658a4509ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f658a26f22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f658a27416d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f658647c6db in start_thread (arg=0x7f65439dc700) at pthread_create.c:463 #8 0x7f6589b6a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f6553fff700 (LWP 2882)): #0 0x7f6584394cd9 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f658434f3fe in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f658434f54c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f658a4ab90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f658a4509ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f658a26f22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f658a27416d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f658647c6db in start_thread (arg=0x7f6553fff700) at pthread_create.c:463 #8 0x7f6589b6a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f6559731700 (LWP 2881)): #0 0x7f6589b5dbf9 in __GI___poll (fds=0x7f6554004e10, nfds=1, timeout=9402) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f658434f439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f658434f54c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f658a4ab90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f658a4509ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/lib
[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #19 from José JORGE --- (In reply to Mauro Carvalho Chehab from comment #18) > Bug #371579 was fixed upstream. Could you please test if this solved the > issue for you? Thanks, but I suppose I have to checkout form git? Or can I try a tarball? -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #21 from José JORGE --- (In reply to Mauro Carvalho Chehab from comment #18) > Bug #371579 was fixed upstream. Could you please test if this solved the > issue for you? Issue not solved as of today's GIT. I could get one time kaffeine to only use ~25% CPU after lots of play/stop on DVB. But 99% of the time, CPU is at 125% (dual-core system) when playing, and at 100% when playback is stopped. Any hint on how to dump tasks load welcome... -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #17 from José JORGE --- (In reply to Mauro Carvalho Chehab from comment #16) > If any of this task happens as often as the scheduler is called, it will > show 100% CPU usage. It is hard to discover what task is taking more time > without profiling it. One could run a profiler to check what task is > consuming more time, in order to identify the culprit. Any hint on how to profile? Thanks. > > Maybe this could be a reflex of EPG parsing, as reported on this bug: >https://bugs.kde.org/show_bug.cgi?id=371579 I don't think so, as the 100% CPU sometimes stops only by clicking on stop, then play again. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379345] New: Addons repository not load
https://bugs.kde.org/show_bug.cgi?id=379345 Bug ID: 379345 Summary: Addons repository not load Product: Discover Version: 5.9.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Apt Back-end Assignee: aleix...@kde.org Reporter: lukasrochaara...@gmail.com Target Milestone: --- QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' no packages for "UEFI Updates" no packages for "VL811 Firmware" no packages for "VL811+ Firmware" no packages for "VL812 Firmware" no packages for "VL812 B2 Firmware" The file "/home/lucas/.local/share/knewstuff3/kdenlive_projectprofiles.knsregistry" could not be opened. invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not found! Check your KNS3 installation." The file "/home/lucas/.local/share/knewstuff3/comic.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/kfontinst.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/messageviewer_header_themes.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/ksieve_script.knsregistry" could not be opened. invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not found! Check your KNS3 installation." The file "/home/lucas/.local/share/knewstuff3/wallpaper.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/k3btheme.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/kwinswitcher.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/kdenlive_renderprofiles.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/sddmtheme.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/knotes_printing_theme.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/cgcicon.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/emoticons.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/discover_ktexteditor_codesnippets_core.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/cgctheme.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/plasmoids.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/kdenlive_wipes.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/lookandfeel.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/kaddressbook_themes.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/kdenlive_titles.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/kwinscripts.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/korganizer.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/plasma-themes.knsregistry" could not be opened. The file "/home/lucas/.local/share/knewstuff3/cgcgtk3.knsregistry" could not be opened. Discarding invalid backend "ksysguard.knsrc" Discarding invalid backend "servicemenu.knsrc" QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' klauncher not running... launching kdeinit QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher' kdeinit5: Launched KLauncher, pid = 4399, result = 0 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' kdeinit5: opened connection to :0 kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/p
[Discover] [Bug 379345] Addons repository not load
https://bugs.kde.org/show_bug.cgi?id=379345 --- Comment #3 from Jorge Lucas --- (In reply to Aleix Pol from comment #2) > It says there's a network error. Can you see if it's properly connected? Yes... The machine is connected! Brownsers, download of apps work's normally! -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 358045] Kdialog display nothing with --progressbar
https://bugs.kde.org/show_bug.cgi?id=358045 José JORGE changed: What|Removed |Added CC||lists.jjo...@free.fr --- Comment #3 from José JORGE --- I can confirm this is a recent bug, as for Plasma 5.8.0 it did work. I observe it with Mageia Cauldron for at most one month. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #46 from José JORGE --- Yes a big thanks for all, it was beyond my abilities... For an end user, is there an idea when an official release will bring this fix? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 494780] New: Performance Degradation on Nvidia (Hibrid) HDMI Output with Triple Buffering Disabled (Fedora 40, KDE Plasma)
https://bugs.kde.org/show_bug.cgi?id=494780 Bug ID: 494780 Summary: Performance Degradation on Nvidia (Hibrid) HDMI Output with Triple Buffering Disabled (Fedora 40, KDE Plasma) Classification: Plasma Product: kwin Version: 6.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: j...@hotmail.es Target Milestone: --- Created attachment 174824 --> https://bugs.kde.org/attachment.cgi?id=174824&action=edit Example of moving a screen creating jerky movement and high usage on Nvidia GPU Summary: There is noticeable performance degradation when using an external monitor connected via the Nvidia HDMI output on hibrid configuration AMD + Nvidia laptops . The GPU usage spikes to 100% when moving windows on the external monitor and moving windows around. This issue did not occur before upgrading to KDE Plasma 6.2. Steps to Reproduce: Connect an external monitor to the Nvidia HDMI output. Move windows around on the external monitor. Observe GPU usage and performance when moving windows. Expected Results: Smooth performance without excessive GPU usage. Actual Results: GPU usage reaches 100% (as observed via Btop++) when moving windows, causing sluggish performance and jerky movement. The issue is specific to the Nvidia HDMI output. When using the AMD integrated graphics to connect the monitor, performance is smooth and the GPU use remains minimum. This performance degradation did not occur prior to KDE Plasma 6.2. System Info: Operating System: Fedora Linux 40 KDE Plasma Version: 6.2.0 KDE Frameworks Version: 6.7.0 Qt Version: 6.7.2 Kernel Version: 6.11.3-350.vanilla.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840HS w/ Radeon 780M Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon 780M + Nvidia HDMI Output Laptop Model: Victus by HP Gaming Laptop Could be related to the issue #494407 as affects the same system configuration. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 494407] After upgrade to Plasma 6.2, external monitor affected by graphical artifacts
https://bugs.kde.org/show_bug.cgi?id=494407 --- Comment #13 from Jorge Durán --- (In reply to Nate Graham from comment #12) Thank you, Nate! I’ve created the report on #494780 to track the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 494407] After upgrade to Plasma 6.2 External monitor affected by artifacts and low performance
https://bugs.kde.org/show_bug.cgi?id=494407 Jorge Durán changed: What|Removed |Added CC||j...@hotmail.es Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #11 from Jorge Durán --- (In reply to Evert Vorster from comment #10) > Update on this issue. > > Just disabling triple buffering solves the graphical artifacts, however the > performance issues remains. > > To be clear, I set: > KWIN_DRM_DISABLE_TRIPLE_BUFFERING=1 > > In my environment, and with no other changes the display artifacts are now > gone. However, dragging a window around on the external monitor is really > jerky, and the longer it is dragged around the more jerky it gets. > > So, that "Fixed" might be a little premature. At best it only is "Half > fixed", as the bug report clearly states artifacts AND low performance. I can confirm this is happening on my system as well. Disabling triple buffering removes the graphical artifacts, but the performance issues persist on the Nvidia HDMI output. GPU shows 100% on Btop++ when moving windows on the external Nvidia output. But if I connect the monitor though the AMD integrated graphics it is all good. Operating System: Fedora Linux 40 KDE Plasma Version: 6.2.0 KDE Frameworks Version: 6.7.0 Qt Version: 6.7.2 Kernel Version: 6.11.3-350.vanilla.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840HS w/ Radeon 780M Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon 780M Manufacturer: HP Product Name: Victus by HP Gaming Laptop System Version: Type1ProductConfigId -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 494780] Performance Degradation on Nvidia (Hibrid) HDMI Output with Triple Buffering Disabled (Fedora 40, KDE Plasma)
https://bugs.kde.org/show_bug.cgi?id=494780 Jorge Durán changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Jorge Durán --- Seems to be fixed on the 6.2.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 494780] Performance Degradation on Nvidia (Hibrid) HDMI Output with Triple Buffering Disabled (Fedora 40, KDE Plasma)
https://bugs.kde.org/show_bug.cgi?id=494780 Jorge Durán changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 494407] After upgrade to Plasma 6.2, external monitor affected by graphical artifacts
https://bugs.kde.org/show_bug.cgi?id=494407 --- Comment #15 from Jorge Durán --- (In reply to Luis Mayo from comment #14) > Hi! > > This did indeed get fixed for me in 6.2.1 but it has come back in 6.2.2. Is > it just me? I can canfirm, that 6.2.3 works fine. Not sure about KDE 6.2.2. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 460882] Wishlist: KFileMetadata extractor for .eml files
https://bugs.kde.org/show_bug.cgi?id=460882 Jorge Nerín changed: What|Removed |Added CC||jne...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500930] plasmashell keeps crashing right after loggin in and subsequently.
https://bugs.kde.org/show_bug.cgi?id=500930
--- Comment #2 from Jorge Blasio ---
gamescope consistently keeps crashing plasmashell and restarting it:
mar 02 09:06:48 klaasje plasmashell[45866]: qt.dbus.integration: Could not
connect "org.cups.cupsd.Notifier" to PrinterFinishingsChanged(QString, QString,
QString, uint, QString, bool) :
mar 02 09:06:49 klaasje plasmashell[45866]: org.kde.applets.brightness: D-Bus
action "KeyboardBrightnessControl" is not available at service
"org.kde.Solid.PowerManagement"
mar 02 09:06:49 klaasje plasmashell[45866]: QFont::setPointSizeF: Point size <=
0 (0.00), must be greater than 0
mar 02 09:06:49 klaasje plasmashell[45866]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/CompactRepresentation.qml:40:
TypeError: Cannot read property 'height' of null
mar 02 09:06:49 klaasje plasmashell[45866]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/DashboardRepresentation.qml:771:29:
Unable to assign ActionMenu_QMLTYPE_267 to QQuickItem
mar 02 09:06:50 klaasje plasmashell[45866]: Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
mar 02 09:06:50 klaasje plasmashell[45866]: QFont::setPointSizeF: Point size <=
0 (0.00), must be greater than 0
mar 02 09:06:53 klaasje tailscaled[1965]: open-conn-track: timeout opening (TCP
100.96.180.78:45194 => 195.135.223.50:80); no associated peer node
mar 02 09:06:59 klaasje tailscaled[1965]: open-conn-track: timeout opening (TCP
100.96.180.78:45194 => 195.135.223.50:80); no associated peer node
mar 02 09:07:05 klaasje tailscaled[1965]: open-conn-track: timeout opening (TCP
100.96.180.78:45194 => 195.135.223.50:80); no associated peer node
mar 02 09:07:06 klaasje plasmashell[45866]: error marshalling arguments for
get_icon: dup failed: Demasiados ficheros abiertos
mar 02 09:07:06 klaasje plasmashell[45866]: Error marshalling request:
Demasiados ficheros abiertos
mar 02 09:07:07 klaasje plasmashell[45866]: org.kde.plasma.libtaskmanager: time
out polling for icon of window "{789fb34f-a62c-4161-a5f6-b0c41c1639fb}"
mar 02 09:07:07 klaasje plasmashell[45866]: org.kde.plasma.libtaskmanager: time
out polling for icon of window "{789fb34f-a62c-4161-a5f6-b0c41c1639fb}"
mar 02 09:07:07 klaasje plasmashell[45866]: org.kde.plasma.libtaskmanager: time
out polling for icon of window "{789fb34f-a62c-4161-a5f6-b0c41c1639fb}"
mar 02 09:07:07 klaasje plasmashell[45866]: org.kde.plasma.libtaskmanager: time
out polling for icon of window "{789fb34f-a62c-4161-a5f6-b0c41c1639fb}"
mar 02 09:07:07 klaasje plasmashell[45866]: org.kde.plasma.libtaskmanager: time
out polling for icon of window "{789fb34f-a62c-4161-a5f6-b0c41c1639fb}"
mar 02 09:07:07 klaasje plasmashell[45866]: org.kde.plasma.libtaskmanager: time
out polling for icon of window "{789fb34f-a62c-4161-a5f6-b0c41c1639fb}"
mar 02 09:07:07 klaasje plasmashell[45866]: org.kde.plasma.libtaskmanager: time
out polling for icon of window "{789fb34f-a62c-4161-a5f6-b0c41c1639fb}"
mar 02 09:07:07 klaasje plasmashell[45866]: org.kde.plasma.libtaskmanager: time
out polling for icon of window "{789fb34f-a62c-4161-a5f6-b0c41c1639fb}"
mar 02 09:07:08 klaasje plasmashell[45866]: org.kde.plasma.libtaskmanager: time
out polling for icon of window "{789fb34f-a62c-4161-a5f6-b0c41c1639fb}"
mar 02 09:07:08 klaasje plasmashell[45866]: org.kde.plasma.libtaskmanager: time
out polling for icon of window "{789fb34f-a62c-4161-a5f6-b0c41c1639fb}"
mar 02 09:07:08 klaasje plasmashell[45866]: org.kde.plasma.libtaskmanager: time
out polling for icon of window "{789fb34f-a62c-4161-a5f6-b0c41c1639fb}"
mar 02 09:07:08 klaasje plasmashell[45866]: org.kde.plasma.libtaskmanager: time
out polling for icon of window "{789fb34f-a62c-4161-a5f6-b0c41c1639fb}"
mar 02 09:07:12 klaasje firefox[6435]: [Parent 6435, Main Thread] WARNING:
gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
'GDK_IS_WAYLAND_WINDOW (window)' failed: 'glib warning', file
/home/abuild/rpmbuild/BUILD/MozillaFirefox-135.0-build/firefox-135.0/toolkit/xre/nsSigHandlers.cpp:201
mar 02 09:07:12 klaasje firefox[6435]:
gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
'GDK_IS_WAYLAND_WINDOW (window)' failed
mar 02 09:07:13 klaasje tailscaled[1965]: open-conn-track: timeout opening (TCP
100.96.180.78:45194 => 195.135.223.50:80); no associated peer node
mar 02 09:07:14 klaasje kwin_wayland[5809]: kwin_scene_opengl: 0x2:
GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
mar 02 09:07:14 klaasje kwin_wayland[5809]: kwin_scene_opengl: 0x2:
GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
mar 02 09:07:14 klaasje kwin_wayland[5809]: kwin_scene_opengl: 0x2:
GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEF
[plasmashell] [Bug 500930] plasmashell keeps crashing right after loggin in and subsequently.
https://bugs.kde.org/show_bug.cgi?id=500930 Jorge Blasio changed: What|Removed |Added Summary|plasmashell keeps crashing |plasmashell keeps crashing |right after loggin in an|right after loggin in and |onwards.|subsequently. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500930] New: plasmashell keeps crashing right after loggin in an onwards.
https://bugs.kde.org/show_bug.cgi?id=500930 Bug ID: 500930 Summary: plasmashell keeps crashing right after loggin in an onwards. Classification: Plasma Product: plasmashell Version: 6.3.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: jorgebla...@mac.com Target Milestone: 1.0 Created attachment 179027 --> https://bugs.kde.org/attachment.cgi?id=179027&action=edit Crash log SUMMARY Right after loading the session, plasmashell crashe but the panels remain. Next crash takes everything down. STEPS TO REPRODUCE 1. log in OBSERVED RESULT Dr. Konqi complains of plasmachell crashing, but panels remain until it crashes again. EXPECTED RESULT Stable desktop session. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.13.4-1 KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11 Qt Version: 6.8.2 ADDITIONAL INFORMATION Wayland session, Mesa 25.0.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500930] plasmashell keeps crashing right after loggin in and subsequently.
https://bugs.kde.org/show_bug.cgi?id=500930 --- Comment #1 from Jorge Blasio --- caught crash: systemd-coredump[6814]: [🡕] Process 6776 (plasmashell) of user 1000 dumped core. Stack trace of thread 6776: #0 0x7fc0bb09a13c __pthread_kill_implementation (libc.so.6 + 0x9a13c) #1 0x7fc0bb041436 raise (libc.so.6 + 0x41436) #2 0x7fc0be7a087f _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x687f) #3 0x7fc0bb041500 __restore_rt (libc.so.6 + 0x41500) #4 0x7fc0bc175714 n/a (libQt6Gui.so.6 + 0x175714) #5 0x7fc0bc22a7ab _ZN12QInputDeviceD1Ev (libQt6Gui.so.6 + 0x22a7ab) #6 0x7fc0b71486a7 n/a (libQt6XcbQpa.so.6 + 0x6a6a7) #7 0x7fc0bb9f4e9e _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x1f4e9e) #8 0x7fc0bdddee35 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x1dee35) #9 0x7fc0bb9ada30 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x1ada30) #10 0x7fc0bb9b3a20 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x1b3a20) #11 0x7fc0bbc6beb4 n/a (libQt6Core.so.6 + 0x46beb4) #12 0x7fc0bbb1f0b5 n/a (libQt6Core.so.6 + 0x31f0b5) #13 0x7fc0bb0438e1 __cxa_finalize (libc.so.6 + 0x438e1) #14 0x7fc0bb92e9e7 n/a (libQt6Core.so.6 + 0x12e9e7) #15 0x7fc0beb98102 _dl_call_fini (ld-linux-x86-64.so.2 + 0x1102) #16 0x7fc0beb9b4ce _dl_fini (ld-linux-x86-64.so.2 + 0x44ce) #17 0x7fc0bb043eb1 __run_exit_handlers (libc.so.6 + 0x43eb1) #18 0x7fc0bb043f80 exit (libc.so.6 + 0x43f80) #19 0x7fc0bbb38c2b _ZN18QCommandLineParser11showVersionEv (libQt6Core.so.6 + 0x338c2b) #20 0x7fc0bbb3a20e _ZN18QCommandLineParser7processERK5QListI7QStringE (libQt6Core.so.6 + 0x33a20e) #21 0x7fc0bbb3a2c1 _ZN18QCommandLineParser7processERK16QCoreApplication (libQt6Core.so.6 + 0x33a2c1) #22 0x55c02594dc16 n/a (n/a + 0x0) #23 0x55c0384a55e0 n/a (n/a + 0x0) ELF object binary architecture: AMD x86-64 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 470373] New: Add shortcuts to change the current terminal size. Similar to what Terminator does
https://bugs.kde.org/show_bug.cgi?id=470373 Bug ID: 470373 Summary: Add shortcuts to change the current terminal size. Similar to what Terminator does Classification: Applications Product: konsole Version: 23.04.1 Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: keyboard Assignee: konsole-de...@kde.org Reporter: jfsanchez.em...@gmail.com Target Milestone: --- Created attachment 159298 --> https://bugs.kde.org/attachment.cgi?id=159298&action=edit using mouse to adjust terminal size SUMMARY Same way we can change the focus from one terminal to another using shortcuts, it would be great if we can also resize the current terminal using some keyboard shortcuts. This is the only feature Terminator offers that I miss in Konsole. I opened the same issue in GitLab originally -> https://invent.kde.org/utilities/konsole/-/issues/39#note_688207 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 470373] Add shortcuts to change the current terminal size. Similar to what Terminator does
https://bugs.kde.org/show_bug.cgi?id=470373 --- Comment #2 from Jorge F. Sánchez --- (In reply to tcanabrava from comment #1) > Created attachment 159301 [details] > attachment-3421079-0.html > > Jorge, > > This is a nice issue and it's something that could help konsole. > This is, at the same time, something easy to implement, I wonder if you > would like to give it a try - and if so I'm quite happy to help you get > started. > If not, I'll also implement this, since it makes sense. > > Best, > Tomaz > > > On Sun, May 28, 2023 at 6:38 PM Jorge F. Sánchez > wrote: > > > https://bugs.kde.org/show_bug.cgi?id=470373 > > > > Bug ID: 470373 > >Summary: Add shortcuts to change the current terminal size. > > Similar to what Terminator does > > Classification: Applications > >Product: konsole > >Version: 23.04.1 > > Platform: Neon > > OS: Linux > > Status: REPORTED > > Severity: wishlist > > Priority: NOR > > Component: keyboard > > Assignee: konsole-de...@kde.org > > Reporter: jfsanchez.em...@gmail.com > > Target Milestone: --- > > > > Created attachment 159298 [details] > > --> https://bugs.kde.org/attachment.cgi?id=159298&action=edit > > using mouse to adjust terminal size > > > > SUMMARY > > Same way we can change the focus from one terminal to another using > > shortcuts, > > it would be great if we can also resize the current terminal using some > > keyboard shortcuts. > > This is the only feature Terminator offers that I miss in Konsole. > > > > I opened the same issue in GitLab originally -> > > https://invent.kde.org/utilities/konsole/-/issues/39#note_688207 > > > > -- > > You are receiving this mail because: > > You are the assignee for the bug. I would love to implement it myself, but I have no idea where to start :) . I was checking the source code.. and there are a lot components. I found in the ViewManager you declare most of the Actions & shortcuts, but from there, it is hard (for me) to understand what could be the component that should be resized once the action is triggered. -- You are receiving this mail because: You are watching all bug changes.
