[kmail2] [Bug 414100] Text not visible when using dark theme
https://bugs.kde.org/show_bug.cgi?id=414100 --- Comment #12 from Raúl --- I have tried the suggestion from https://bugs.kde.org/show_bug.cgi?id=414100#c7 and I see it as a workaround. Thanks Christophe! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 380924] Use white background for the message windows whatever the selected plasma theme.
https://bugs.kde.org/show_bug.cgi?id=380924 Raúl changed: What|Removed |Added CC||rasas...@gmail.com --- Comment #2 from Raúl --- May this be related to https://bugs.kde.org/show_bug.cgi?id=414100 ? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 414100] Text not visible when using dark theme
https://bugs.kde.org/show_bug.cgi?id=414100 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471931] org.kde.plasma.battery widget does not work properly on task bar
https://bugs.kde.org/show_bug.cgi?id=471931 Raúl changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Raúl --- *** This bug has been marked as a duplicate of bug 464996 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464996] Resurrection of bug 422111 with upower 0.99.14 or later
https://bugs.kde.org/show_bug.cgi?id=464996 Raúl changed: What|Removed |Added CC||qtm...@gmail.com --- Comment #10 from Raúl --- *** Bug 471931 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471931] org.kde.plasma.battery widget does not work properly on task bar
https://bugs.kde.org/show_bug.cgi?id=471931 Raúl changed: What|Removed |Added CC||rasas...@gmail.com --- Comment #2 from Raúl --- This looks like a dupe of https://bugs.kde.org/show_bug.cgi?id=464996. By the way, I can confirm that restarting the plasma-plasmashell.service worked for me: `systemctl restart --user plasma-plasmashell.service` -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0
https://bugs.kde.org/show_bug.cgi?id=389829 --- Comment #19 from Raúl --- Hello: I think here we are talking about 2 different issues: * Issue reported which is that it is not possible to fetch a specific email from akonadi backend. I think this is related to database engine, database corruption or akonadiserver lack of sync with database. This is what your latest journalctl log (https://bugs.kde.org/attachment.cgi?id=144299) could be related to (or maybe not. I'm not sure) * A permanent deadlock in either the communication from akonadi with the database engine or a problem in the database handling. This is exposed when sending the `show engine innodb status;` sql statement to the database engine. This is also exposed with the error message ` Deadlock found when trying to get lock; try restarting transaction QMYSQL3: Unable to execute statement` I think this problem should be followed up in the proper bug report https://bugs.kde.org/show_bug.cgi?id=434706 This problems prevents going on in the kmail usage as akonadi cannot properly fetch or handle data from database. One workaround for my is killing the mariadb server and letting akonadi to restart it. Regards, -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0
https://bugs.kde.org/show_bug.cgi?id=389829 --- Comment #14 from Raúl --- Attila, sorry for the delay in answering. I'm not a KDE developer but I can explain you what I suspect about this bug and how it can be related (if not duped) to https://bugs.kde.org/show_bug.cgi?id=434706. kontact/akonadi is a user fronted which shows data that those get from akonadi which, in turn, is closely bounded to a database. The database is made up of tables and registers. You can take a look at those tables and registers using an external database browser or the database command line client. For instance, in my case akonadi relies on mariadb database engine and I can query the akonadi data externally like this: ``` $ mariadb -S/run/user/1001/akonadi/mysql.socket MariaDB [(none)]> use akonadi; MariaDB [akonadi]> show tables ; +--+ | Tables_in_akonadi| +--+ | collectionattributetable | | collectionmimetyperelation | | collectionpimitemrelation| | collectiontable | | flagtable| | mimetypetable| | parttable| | parttypetable| | pimitemflagrelation | | pimitemtable | | pimitemtagrelation | | relationtable| | relationtypetable| | resourcetable| | schemaversiontable | | tagattributetable| | tagremoteidresourcerelationtable | | tagtable | | tagtypetable | +--+ 19 rows in set (0.001 sec) ``` kontact/kmail sends database queries to feed akonadi database and also to retrieve data. I think either the query flow or the database engine has some kind of bug or limitation. Hence one of the database queries locks some database tables (like those listed above) and therefore most of the database operations are locked (they cannot be completed). https://bugs.kde.org/show_bug.cgi?id=434706 explains some similar behavior and that is why I asked you to check if both reports are about the same problem. You are right that https://bugs.kde.org/show_bug.cgi?id=434706 is too technical and this is where you could get lost. In order to check whether the problem is the same or not, here is the list of actions that you can perform to verify: * Wait for the problem to reproduce or reproduce it yourself (if possible) * Check `journalctl -xe` output and look for recent output like this: ``` kmail[1317]: org.kde.pim.akonadicore: Received response with a different tag! akonadi_maildispatcher_agent[1586]: void SendJob::setFrom(const QString &from) "m...@milianw.de" akonadi_maildispatcher_agent[1586]: d->m_returnPath "" akonadiserver[1305]: org.kde.pim.akonadiserver: QueryBuilder::exec(): database reported transaction deadlock, retrying transaction akonadiserver[1305]: org.kde.pim.akonadiserver: "Deadlock found when trying to get lock; try restarting transaction QMYSQL3: Unable to execute statement" akonadi_imap_resource[1583]: org.kde.pim.imapresource: "Connection to server lost." ``` * Additionally you can connect to the mariadb socket: `mariadb -S/run/user/1001/akonadi/mysql.socket` (1001 is your user code, maybe it's a different number) * Issue the following db engine query: `SHOW ENGINE INNODB STATUS` you should see that there is a deadlock detected: *LATEST DETECTED DEADLOCK* section in the https://bugs.kde.org/show_bug.cgi?id=434706 bug If you find out the same outcome, this and the other bug are quite possibly a duplicated. One additional comment is that I think the bug is not specifically about kmail, but about akonadi and its database engine usage. For getting a fix, we would need that someone with enough akonadi and DB knowledge to analyze and find out possible solutions. Unfortunately that is not by my hand. Regards, -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0
https://bugs.kde.org/show_bug.cgi?id=389829 --- Comment #11 from Raúl --- Could you please, confirm if this is a dupe of https://bugs.kde.org/show_bug.cgi?id=434706 In order to confirm, you would need to use mariadb/mysql client and check out the transaction status are described in there. Regards, -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 412257] kiod5 doesn't release usb device when it is not in use
https://bugs.kde.org/show_bug.cgi?id=412257 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 441067] Yakuake is no longer available in the task switcher list
https://bugs.kde.org/show_bug.cgi?id=441067 --- Comment #3 from Raúl --- Hello. I've tried Danail suggestion (patch) on yakuake 21.08 and it works. Thanks for this. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 441067] Yakuake is no longer available in the task switcher list
https://bugs.kde.org/show_bug.cgi?id=441067 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 401050] kmail mailto invokation fails if akonadi is loaded
https://bugs.kde.org/show_bug.cgi?id=401050 Raúl changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Raúl --- Hello: Thanks for the feedback. Reporting that I see it is working now here on: kontact 5.15.3 (20.08.3) KDE Frameworks 5.78.0 Qt 5.15.2 Closing consequently. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 401765] Accepting updated invitation caused Kontact crash.
https://bugs.kde.org/show_bug.cgi?id=401765 --- Comment #3 from Raúl --- I wonder if https://bugs.kde.org/show_bug.cgi?id=431885 is related. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 401765] Accepting updated invitation caused Kontact crash.
https://bugs.kde.org/show_bug.cgi?id=401765 Raúl changed: What|Removed |Added CC||rasas...@gmail.com --- Comment #2 from Raúl --- Maybe a more recent backtrace is useful: Kontact 5.13.3 KDE Frameworks 5.78.0 Qt 5.15.2 Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7f234d91f980 in KMime::Content::parent() const () at /lib/x86_64-linux-gnu/libKF5Mime.so.5abi1 #5 0x7f234d91f9ab in KMime::Content::topLevel() const () at /lib/x86_64-linux-gnu/libKF5Mime.so.5abi1 #6 0x7f22fdb31a49 in (anonymous namespace)::UrlHandler::findReceiver(KMime::Content*) (node=0x55d88b067300) at ./plugins/messageviewer/bodypartformatter/calendar/text_calendar.cpp:414 #7 0x7f22fdb35d7e in (anonymous namespace)::UrlHandler::handleInvitation(QString const&, KCalendarCore::Attendee::PartStat, MimeTreeParser::Interface::BodyPart*, MessageViewer::Viewer*) const (this=0x55d87e447880, iCal=..., status=KCalendarCore::Attendee::Accepted, part=0x7fffb7742f70, viewerInstance=0x55d87d20ac80) at ./plugins/messageviewer/bodypartformatter/calendar/text_calendar.cpp:875 #8 0x7f22fdb37dc6 in (anonymous namespace)::UrlHandler::handleClick(MessageViewer::Viewer*, MimeTreeParser::Interface::BodyPart*, QString const&) const (this=0x55d87e447880, viewerInstance=0x55d87d20ac80, part=0x7fffb7742f70, path=) at ./plugins/messageviewer/bodypartformatter/calendar/text_calendar.cpp:1217 #9 0x7f234bda6a19 in MessageViewer::BodyPartURLHandlerManager::handleClick(QUrl const&, MessageViewer::ViewerPrivate*) const () at /lib/x86_64-linux-gnu/libKF5MessageViewer.so.5abi1 #10 0x7f234bda51f8 in MessageViewer::URLHandlerManager::handleClick(QUrl const&, MessageViewer::ViewerPrivate*) const () at /lib/x86_64-linux-gnu/libKF5MessageViewer.so.5abi1 #11 0x7f234bd8cbd1 in MessageViewer::ViewerPrivate::slotUrlOpen(QUrl const&) () at /lib/x86_64-linux-gnu/libKF5MessageViewer.so.5abi1 #12 0x7f23ba135f91 in QObject::event(QEvent*) (this=0x55d87d3e1420, e=0x7f2368163e50) at kernel/qobject.cpp:1314 #13 0x7f23babcb15f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f23ba109f6a in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55d87d3e1420, event=0x7f2368163e50) at kernel/qcoreapplication.cpp:1063 #15 0x7f23ba10c9a1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x55d87ca118f0) at kernel/qcoreapplication.cpp:1817 #16 0x7f23ba161e33 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x55d87cb50cf0) at kernel/qeventdispatcher_glib.cpp:277 #17 0x7f23b0ee7e6b in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f23b0ee8118 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7f23b0ee81cf in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7f23ba1614bf in QEventDispatcherGlib::processEvents(QFlags) (this=0x55d87cb5cf30, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #21 0x7f23ba10892b in QEventLoop::exec(QFlags) (this=this@entry=0x7fffb77433f0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #22 0x7f23ba110ba0 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #23 0x55d87abe302b in () #24 0x7f23b9aeed0a in __libc_start_main (main=0x55d87abe2610, argc=3, argv=0x7fffb7743688, init=, fini=, rtld_fini=, stack_end=0x7fffb7743678) at ../csu/libc-start.c:308 #25 0x55d87abe354a in () [Inferior 1 (process 2111) detached] -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 434205] New: akonadiserver crashed handling DB(mariadb) deadlock
https://bugs.kde.org/show_bug.cgi?id=434205 Bug ID: 434205 Summary: akonadiserver crashed handling DB(mariadb) deadlock Product: Akonadi Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: rasas...@gmail.com Target Milestone: --- Application: akonadiserver (5.15.3 (20.08.3)) Qt Version: 5.15.2 Frameworks Version: 5.78.0 Operating System: Linux 5.10.0-4-amd64 x86_64 Windowing system: X11 Distribution: Debian GNU/Linux bullseye/sid -- Information about the crash: - What I was doing when the application crashed: kontact hd just retrieved some emails from my gmail pop3 account, then akonadiserver crashed. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x0) at /usr/include/c++/10/bits/atomic_base.h:420 #5 QAtomicOps::loadRelaxed (_q_value=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=0x0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:107 #7 QtPrivate::RefCount::ref (this=0x0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:55 #8 QByteArray::QByteArray (a=..., this=0x7f761a7fb510) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbytearray.h:525 #9 Akonadi::Protocol::PartMetaData::PartMetaData (this=0x7f761a7fb510) at ./obj-x86_64-linux-gnu/src/private/protocol_gen.h:170 #10 Akonadi::Protocol::StreamPayloadResponse::metaData (this=0x7f7604204180) at ./obj-x86_64-linux-gnu/src/private/protocol_gen.h:3688 #11 Akonadi::Server::PartStreamer::requestPartMetaData (this=0x7f761a7fb6d0, partName=...) at ./src/server/storage/partstreamer.cpp:60 #12 0x56351075a047 in Akonadi::Server::PartStreamer::streamPayload (this=0x7f761a7fb6d0, part=..., partName=...) at ./src/server/storage/partstreamer.cpp:65 #13 0x56351075a1e5 in Akonadi::Server::PartStreamer::stream (this=this@entry=0x7f761a7fb6d0, checkExists=checkExists@entry=true, partName=..., partSize=@0x7f761a7fb6a8: 0, changed=changed@entry=0x0) at ./src/server/storage/partstreamer.cpp:319 #14 0x56351069cb37 in Akonadi::Server::ItemModifyHandler::parseStream (this=0x7f760403ba10) at ./src/server/handler/itemmodifyhandler.cpp:280 #15 0x5635106706ce in Akonadi::Server::Connection::parseStream (this=0x563510e1d740, cmd=...) at ./src/server/connection.cpp:170 #16 0x563510672a37 in operator() (__closure=) at ./src/server/connection.cpp:261 #17 Akonadi::Server::DbDeadlockCatcher::callFunc&> (func=..., this=, func=..., recursionCounter=0) at ./src/server/storage/dbdeadlockcatcher.h:34 #18 Akonadi::Server::DbDeadlockCatcher::DbDeadlockCatcher > (func=..., this=) at ./src/server/storage/dbdeadlockcatcher.h:27 #19 Akonadi::Server::Connection::handleIncomingData (this=) at ./src/server/connection.cpp:261 #20 0x7f765052ff91 in QObject::event (this=0x563510e1d740, e=0x7f7604005780) at kernel/qobject.cpp:1314 #21 0x7f7650503f3f in doNotify (event=0x7f7604005780, receiver=0x563510e1d740) at kernel/qcoreapplication.cpp:1153 #22 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1139 #23 QCoreApplication::notifyInternal2 (receiver=0x563510e1d740, event=0x7f7604005780) at kernel/qcoreapplication.cpp:1063 #24 0x7f76505069a1 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x563510e1d4a0) at kernel/qcoreapplication.cpp:1817 #25 0x7f765055be33 in postEventSourceDispatch (s=0x7f7604004380) at kernel/qeventdispatcher_glib.cpp:277 #26 0x7f764ecc4e6b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f764ecc5118 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7f764ecc51cf in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f765055b4bf in QEventDispatcherGlib::processEvents (this=0x7f7604000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #30 0x7f765050292b in QEventLoop::exec (this=this@entry=0x7f761a7fbd60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #31 0x7f7650321a3e in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #32 0x7f7650322b81 in QThreadPrivate::start (arg=0x563510e1d8d0) at thread/qthread_unix.cpp:329 #33 0x7f764f628ea7 in start_thread (arg=) at pthread_create.c:477 #34 0x7f764ffa7def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7f761affd700 (LWP 2410) "0x563510e1cdf0-"): #1 0x7f764ecc50ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f764ecc51cf in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f765055b4db in QEventDispatcherGl
[kdevelop] [Bug 379669] KDevelop continues to hang on exit in itemrepository.h [Bucket::deleteItem]
https://bugs.kde.org/show_bug.cgi?id=379669 Raúl changed: What|Removed |Added Version|5.6.1 |5.6.2 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379669] KDevelop continues to hang on exit in itemrepository.h [Bucket::deleteItem]
https://bugs.kde.org/show_bug.cgi?id=379669 --- Comment #42 from Raúl --- Hello: Still happening on 5.6.2. Debian testing, KDE Frameworks 5.78.0, Qt 5.15.2 Thread 23 (Thread 0x7f8b60f90700 (LWP 3684) "KDevelop::Compl"): #0 0x7f8bf8da73ff in __GI___poll (fds=0x7f8b3809e7a0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f8bf5aa50ae in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8bf5aa51cf in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8bf934d4bf in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f8b384bbe70, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7f8bf92f492b in QEventLoop::exec(QFlags) (this=this@entry=0x7f8b60f8fbe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #5 0x7f8bf9113a3e in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f8bf9114b81 in QThreadPrivate::start(void*) (arg=0x55d9c4a66c20) at thread/qthread_unix.cpp:329 #7 0x7f8bf6439ea7 in start_thread (arg=) at pthread_create.c:477 #8 0x7f8bf8db1def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f8b63fff700 (LWP 3638) "Queue(0x55d9c2c"): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55d9c2f81374) at ../sysdeps/nptl/futex-internal.h:186 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55d9c2f81320, cond=0x55d9c2f81348) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55d9c2f81348, mutex=0x55d9c2f81320) at pthread_cond_wait.c:638 #3 0x7f8bf911aafb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., deadline=..., this=0x55d9c2f81320) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x55d9c30018c0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f8bf5a3d214 in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*) () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f8bf5a41d8e in () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f8bf5a3d0f2 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f8bf5a3f670 in ThreadWeaver::Thread::run() () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f8bf9114b81 in QThreadPrivate::start(void*) (arg=0x7f8b5c004e10) at thread/qthread_unix.cpp:329 #10 0x7f8bf6439ea7 in start_thread (arg=) at pthread_create.c:477 #11 0x7f8bf8db1def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f8b7d7fa700 (LWP 3636) "Queue(0x55d9c2c"): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55d9c2f81374) at ../sysdeps/nptl/futex-internal.h:186 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55d9c2f81320, cond=0x55d9c2f81348) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55d9c2f81348, mutex=0x55d9c2f81320) at pthread_cond_wait.c:638 #3 0x7f8bf911aafb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., deadline=..., this=0x55d9c2f81320) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x55d9c30018c0, deadline=...) at thread/qwaitcondition_unix.cpp:225 --Type for more, q to quit, c to continue without paging--c #5 0x7f8bf5a3d214 in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*) () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f8bf5a41d8e in () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f8bf5a3d0f2 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f8bf5a3f670 in ThreadWeaver::Thread::run() () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f8bf9114b81 in QThreadPrivate::start(void*) (arg=0x7f8b680051f0) at thread/qthread_unix.cpp:329 #10 0x7f8bf6439ea7 in start_thread (arg=) at pthread_create.c:477 #11 0x7f8bf8db1def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f8b7dffb700 (LWP 3635) "Queue(0x55d9c2c"): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55d9c2f81374) at ../sysdeps/nptl/futex-internal.h:186 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55d9c2f81320, cond=0x55d9c2f81348) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55d9c2f81348, mutex=0x55d9c2f81320) at pthread_cond_wait.c:638 #3 0x7f8bf911aafb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., deadline=..., this=0x55d9c2f81320) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x55d9c30018c0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f8bf5a3d214 in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*) () at /lib/
[telepathy] [Bug 356157] Configuration for groupwise protocol via haze not posible
https://bugs.kde.org/show_bug.cgi?id=356157 Raúl Osuna changed: What|Removed |Added CC||raulos...@gmail.com --- Comment #4 from Raúl Osuna --- To be honest, we don't use Groupwise any more for quite some years. I won't be able to test anything here. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 434031] Code parsing stalls (and hogs cpu) on clang_parseTranslationUnit2 error
https://bugs.kde.org/show_bug.cgi?id=434031 --- Comment #1 from Raúl --- Created attachment 136418 --> https://bugs.kde.org/attachment.cgi?id=136418&action=edit standalone clang invokation + backtrace I've mangled paths to avoid some non-relevant information disclosuring -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 434031] New: Code parsing stalls (and hogs cpu) on clang_parseTranslationUnit2 error
https://bugs.kde.org/show_bug.cgi?id=434031
Bug ID: 434031
Summary: Code parsing stalls (and hogs cpu) on
clang_parseTranslationUnit2 error
Product: kdevelop
Version: 5.6.2
Platform: Debian testing
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: rasas...@gmail.com
Target Milestone: ---
Created attachment 136415
--> https://bugs.kde.org/attachment.cgi?id=136415&action=edit
all threads backtrace after 99% parsing and ctrl-Q kdevelop
When kdevelope is parsing a somewhat big project, with includes properly
configured so all code dependencies are captured, clang parser shows an error,
the background parser never ends parsing (stalled at 99%). Moreover on kdevelop
quit (ctrl-Q) the background parser keeps on running hogging the CPU
STEPS TO REPRODUCE
1. Start with a recent zephyr project checkout:
https://docs.zephyrproject.org/latest/getting_started/index.html (up to west
init step)
2. Open zephyr rtos recent version as project (CMake based)
3. Add some important parsing paths in the project language parsing
configuration:
zephyrproject/modules/lib/mcumgr/mgmt/include
zephyrproject/modules/lib/mcumgr/smp/include
zephyrproject/modules/lib/tinycbor/include
zephyrproject/bootloader/mcuboot/boot/bootutil/include
zephyrproject/zephyr/include
zephyrproject/bootloader/mcuboot/boot/zephyr/include
4. Let kdevelop parse the code
OBSERVED RESULT
Background parsing stalls at 99% and exit kdevelop keeps background parser
running, even GUI has been shutdown. You'd need to kill kdevelop (again) for it
to exit.
EXPECTED RESULT
kdevelop properly parses code, tolerates parsing failures or at least stop
background parsing.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian testing
kdevelop 5.6.2
KDE Frameworks 5.78.0
Qt 5.15.2
ADDITIONAL INFORMATION
I'm attaching an all threads backtrace. See how there are 2 lengthy stacked
frames threads
console output:
libclang: crash detected during parsing: {
'source_filename' : 'zephyrproject/zephyr/drivers/dac/dac_dacx0508.c'
'command_line_args' : ['clang', '-ferror-limit=100', '-fspell-checking', '',
'-Wunused-parameter', '-Wunreachable-code', '-Wall', '-std=c99', '-nostdinc',
'-xc', '-isystemzephyrproject/modules/lib/mcumgr/mgmt/include',
'-isystemzephyrproject/modules/lib/mcumgr/smp/include',
'-isystemzephyrproject/modules/lib/tinycbor/include',
'-isystemzephyrproject/bootloader/mcuboot/boot/bootutil/include',
'-isystem/usr/lib/gcc/arm-none-eabi/8.3.1/include',
'-isystem/usr/lib/gcc/arm-none-eabi/8.3.1/include-fixed',
'-isystem/usr/include/newlib', '-Izephyrproject/zephyr/include',
'-Izephyrproject/bootloader/mcuboot/boot/zephyr/include', '-isystem',
'/usr/lib/llvm-11/lib/clang/11.0.1/include', '-imacros',
'/tmp/kdevelop.uxcuiC'],
'unsaved_files' : [],
'options' : 513,
}
kdevelop.plugins.clang: clang_parseTranslationUnit2 return with error code 2
kdevelop.plugins.clang: (start KDevelop with `KDEV_CLANG_DISPLAY_DIAGS=1
kdevelop` to see more diagnostics)
kdevelop.plugins.clang: Failed to parse translation unit:
"zephyrproject/zephyr/drivers/dac/dac_dacx0508.c"
libclang: crash detected during parsing: {
'source_filename' : 'zephyrproject/zephyr/subsys/usb/class/audio/audio.c'
'command_line_args' : ['clang', '-ferror-limit=100', '-fspell-checking', '',
'-Wunused-parameter', '-Wunreachable-code', '-Wall', '-std=c99', '-nostdinc',
'-xc', '-isystemzephyrproject/modules/lib/mcumgr/mgmt/include',
'-isystemzephyrproject/modules/lib/mcumgr/smp/include',
'-isystemzephyrproject/modules/lib/tinycbor/include',
'-isystemzephyrproject/bootloader/mcuboot/boot/bootutil/include',
'-isystem/usr/lib/gcc/arm-none-eabi/8.3.1/include',
'-isystem/usr/lib/gcc/arm-none-eabi/8.3.1/include-fixed',
'-isystem/usr/include/newlib', '-Izephyrproject/zephyr/include',
'-Izephyrproject/bootloader/mcuboot/boot/zephyr/include', '-isystem',
'/usr/lib/llvm-11/lib/clang/11.0.1/include', '-imacros',
'/tmp/kdevelop.hjUibn'],
'unsaved_files' : [],
'options' : 513,
}
kdevelop.plugins.clang: clang_parseTranslationUnit2 return with error code 2
kdevelop.plugins.clang: (start KDevelop with `KDEV_CLANG_DISPLAY_DIAGS=1
kdevelop` to see more diagnostics)
kdevelop.plugins.clang: Failed to parse translation unit:
"zephyrproject/zephyr/subsys/usb/class/audio/audio.c"
--
You are receiving this mail because:
You are watching all bug changes.
[konqueror] [Bug 432469] crahs when clicking "skip" on copying to smb
https://bugs.kde.org/show_bug.cgi?id=432469 Raúl changed: What|Removed |Added CC||rasas...@gmail.com --- Comment #1 from Raúl --- Same here on Debian testing with the same Qt and KF5 versions. Dolphin is 20.12.1 (-2) In my case I was moving (a lot of) files from a ext4 internal NVMe disk to an external magnetic USB connected hard drive. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 210648] Crash when cancel in dialog for restored gmail session.
https://bugs.kde.org/show_bug.cgi?id=210648 --- Comment #18 from Raúl --- Hello: On my current debian sid system with konqueror 20.12.0, Qt 5.12.4 and KF5 5.77.0 I cannot reproduce this exact problem (using KHTNL). I got to http://translate.reference.com/ but konqueror was taking 100% CPU usage without rendering the page and therefore I cannot provide further information and I would mark this as work for me. Regards, -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 169826] Konqueror crashes when toggling Caret Mode (F7) 2/3 times on some pages not completely loaded
https://bugs.kde.org/show_bug.cgi?id=169826 Raúl changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REOPENED --- Comment #16 from Raúl --- Valgrind log excerpt: ==34965== Conditional jump or move depends on uninitialised value(s) ==34965==at 0x1C2C3485: ??? ==34965==by 0xD4C7877: ??? ==34965== ==34965== Conditional jump or move depends on uninitialised value(s) ==34965==at 0x1C2C3485: ??? ==34965==by 0xD0EDCB7: ??? ==34965== ==34965== Invalid read of size 8 ==34965==at 0x1D97BF4F: setCaretInvisibleIfNeeded(KHTMLPart*) (khtml_part.cpp:2988) ==34965==by 0x686753F: void doActivate(QObject*, int, void**) (qobject.cpp:3898) ==34965==by 0x57BAB61: QAction::triggered(bool) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.15.2) ==34965==by 0x57BD3A0: QAction::activate(QAction::ActionEvent) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.15.2) ==34965==by 0x57BDF66: QAction::event(QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.15.2) ==34965==by 0x57C115E: QApplicationPrivate::notify_helper(QObject*, QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.15.2) ==34965==by 0x6830F29: QCoreApplication::notifyInternal2(QObject*, QEvent*) (qcoreapplication.cpp:1063) ==34965==by 0x602DC7A: QShortcutMap::dispatchEvent(QKeyEvent*) (qshortcutmap.cpp:675) ==34965==by 0x602E63A: QShortcutMap::tryShortcut(QKeyEvent*) (qshortcutmap.cpp:343) ==34965==by 0x5FD7CAD: QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int, QFlags, unsigned int, unsigned int, unsigned int, QString const&, bool, unsigned short) (qwindowsysteminterface.cpp:477) ==34965==by 0x5FFA49A: QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) (qguiapplication.cpp:2395) ==34965==by 0x5FD464B: QWindowSystemInterface::sendWindowSystemEvents(QFlags) (qwindowsysteminterface.cpp:1169) ==34965== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==34965== KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = konqueror path = /usr/bin pid = 34965 KCrash: Arguments: /usr/bin/konqueror www.lanacion.com.ar KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 169826] Konqueror crashes when toggling Caret Mode (F7) 2/3 times on some pages not completely loaded
https://bugs.kde.org/show_bug.cgi?id=169826 --- Comment #15 from Raúl --- Created attachment 134448 --> https://bugs.kde.org/attachment.cgi?id=134448&action=edit New crash information added by DrKonqi konqueror (20.12.0) using Qt 5.15.2 - What I was doing when the application crashed: What I did to reproduce is following what Darío already explained: " I can still reproduce the crash when loading the site: www.lanacion.com.ar and pressing F7 several times. " -- Backtrace (Reduced): #4 0x7fcf69a7ef4f in setCaretInvisibleIfNeeded(KHTMLPart*) (part=0x556d6f716a10) at ./src/khtml_part.cpp:2988 #5 0x7fd0169aa540 in doActivate(QObject*, int, void**) (sender=0x556d6ffdd480, signal_index=4, argv=0x7ffe984415d0) at kernel/qobject.cpp:3898 #6 0x7fd017606b62 in QAction::triggered(bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7fd0176093a1 in QAction::activate(QAction::ActionEvent) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7fd017609f67 in QAction::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 202457] "Next Difference/File" crashes when viewing a "move" diff
https://bugs.kde.org/show_bug.cgi?id=202457 Raúl changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #34 from Raúl --- Start browsing from a/Gemfile and press ctrl-PgUp until you get the crash. Valgrind report (excerpt): ==25494== Invalid read of size 8 ==25494==at 0x118793AC: UnknownInlinedFun (qlist.h:118) ==25494==by 0x118793AC: constBegin (qlist.h:341) ==25494==by 0x118793AC: KFileLVI::fillChangesList(QTreeWidget*, QHash*) (komparenavtreepart.cpp:627) ==25494==by 0x1187967C: KompareNavTreePart::setSelectedFile(Diff2::DiffModel const*) (komparenavtreepart.cpp:339) ==25494==by 0x11879A69: KompareNavTreePart::slotSetSelection(Diff2::DiffModel const*, Diff2::Difference const*) (komparenavtreepart.cpp:299) ==25494==by 0x624653F: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.2) ==25494==by 0x11848E0D: KomparePart::setSelection(Diff2::DiffModel const*, Diff2::Difference const*) (moc_kompare_part.cpp:400) ==25494==by 0x6246505: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.2) ==25494==by 0x489368D: Diff2::KompareModelList::setSelection(Diff2::DiffModel const*, Diff2::Difference const*) (in /usr/lib/x86_64-linux-gnu/libkomparediff2.so.5.2) ==25494==by 0x489A442: Diff2::KompareModelList::slotNextModel() (in /usr/lib/x86_64-linux-gnu/libkomparediff2.so.5.2) ==25494==by 0x6246505: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.2) ==25494==by 0x5372B61: QAction::triggered(bool) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.15.2) ==25494==by 0x53753A0: QAction::activate(QAction::ActionEvent) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.15.2) ==25494==by 0x5375F66: QAction::event(QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.15.2) ==25494== Address 0x40 is not stack'd, malloc'd or (recently) free'd ==25494== KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kompare path = /usr/bin pid = 25494 KCrash: Arguments: /usr/bin/kompare kompare_crash.diff KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 202457] "Next Difference/File" crashes when viewing a "move" diff
https://bugs.kde.org/show_bug.cgi?id=202457 --- Comment #33 from Raúl --- Created attachment 134446 --> https://bugs.kde.org/attachment.cgi?id=134446&action=edit New crash information added by DrKonqi kompare (4.1.20120) using Qt 5.15.2 - What I was doing when the application crashed: Debian sid. kompare 20.12.0, Qt 5.12.2 I reproduced like this: I used the most recent attached diff: * curl https://bugsfiles.kde.org/attachment.cgi?id=70359 |gunzip > kompare_crash.diff * kompare kompare_crash.diff * Go to first file in diff * Start browsing using ctrl-pgup, ctrl-pgdown -- Backtrace (Reduced): #4 QListData::begin (this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:118 #5 QList::constBegin (this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:341 #6 KFileLVI::fillChangesList (this=0x0, changesList=0x55c63834cdb0, diffToChangeItemDict=0x55c638324590) at ./komparenavtreepart/komparenavtreepart.cpp:627 #7 0x7fe7bcb1767d in KompareNavTreePart::setSelectedFile (this=0x55c638324560, model=0x55c638a5afd0) at ./komparenavtreepart/komparenavtreepart.cpp:339 #8 0x7fe7bcb17a6a in KompareNavTreePart::slotSetSelection (this=0x55c638324560, model=0x55c638a5afd0, diff=0x55c638a66170) at ./komparenavtreepart/komparenavtreepart.cpp:299 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 430441] Dolphin 20.12.0 segmentation faults when trying to drag mounted partition in Places panel
https://bugs.kde.org/show_bug.cgi?id=430441 Raúl changed: What|Removed |Added CC||rcbarb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 203846] Konqueror crashes when selecting text (khtml::CachedFontInstance::cachedCharWidth)
https://bugs.kde.org/show_bug.cgi?id=203846 --- Comment #10 from Raúl --- Hello: I'm not having either crash or 100% CPU usage with: Debian unstable Konqueror 20.08.03 KDE Frameworks 5.77.0 Qt 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 238600] Konqueror crash if this URL open: http://underverse.su/viewtopic.php?t=10420
https://bugs.kde.org/show_bug.cgi?id=238600 --- Comment #9 from Raúl --- Hi: I'm not seeing this crashing on konqueror 20.08.3 either using KHTML engine or webengine. Debian unstable KDE Frameworks 5.77.0 Qt 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 152561] konqueror crashes(SIGSEGV) when evaluating expression on the javascript debugger
https://bugs.kde.org/show_bug.cgi?id=152561 Raúl changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 from Raúl --- Hello: After so many years I tried to get something useful now from this bug report. Unfortunately I couldn't even get to the javascript debugger for KHTML. Therefore I'd close this bug. Thanks for caring. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-purpose] [Bug 419170] Dolphin 19.12.3 crach using TX with bluetooth
https://bugs.kde.org/show_bug.cgi?id=419170 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388869] continuing problem with duplicate and/or missing messages
https://bugs.kde.org/show_bug.cgi?id=388869 Raúl changed: What|Removed |Added CC||rasas...@gmail.com --- Comment #4 from Raúl --- May this be a dupe from https://bugs.kde.org/show_bug.cgi?id=389829 ? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0
https://bugs.kde.org/show_bug.cgi?id=389829 --- Comment #7 from Raúl --- Hello I'm on debian sid and I'm still seeing this bug with: Kontact/Kmail 5.14.1 (20.04.0) KDE Frameworks 5.70.0 Qt 5.14.2 POP3 email account. I've just attached a log from akonadi. The bad thing for me now is that this bug makes akonadiserver crash. This brings some inconveniences like it's not brought up again automatically and you cannot go on with the kmail usage. Some other times the mysql server (the backend I use) is bring up again, so there are 2 mysql sessions which leads to akonadiserver annoyance as it cannot handle the situation. You would need to stop akonadi server, kill all the mysql instances and start akonadiserver again. The problem is reproduced here quite often as the ghost email (wherever it is) is not being dealt. Let me know if I can provide more information. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0
https://bugs.kde.org/show_bug.cgi?id=389829 --- Comment #6 from Raúl --- Created attachment 131921 --> https://bugs.kde.org/attachment.cgi?id=131921&action=edit akonadiserver log (from .xsession-errors) -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 425872] Kontact crashes when accepting a delegated invitation
https://bugs.kde.org/show_bug.cgi?id=425872 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 419836] Events with empty UID are present in akonadi console but not showing up in the calendar
https://bugs.kde.org/show_bug.cgi?id=419836 Raúl changed: What|Removed |Added CC||rasas...@gmail.com --- Comment #8 from Raúl --- Bumped. Debian sid. Kontact 5.14.1 (20.04.0) KDE Frameworks 5.70.0 Qt 5.14.2 I can see the events on akonadiconsole but not on korganizer. I have copied the payload of a working and non-working event in some files which I can send privately to someone interested in debugging this issue. Regards, -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425456] Trackpoint Scrolling in Konsole broken since 20.07
https://bugs.kde.org/show_bug.cgi?id=425456 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 199415] blank screen during 'reloading the document...'
https://bugs.kde.org/show_bug.cgi?id=199415 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413176] keyboard input not detected properly
https://bugs.kde.org/show_bug.cgi?id=413176 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417604] Scrolling direction inverted in some Plasma scrollviews
https://bugs.kde.org/show_bug.cgi?id=417604 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422490] maildir resource gets stuck on synchronizing a folder with 72 messages
https://bugs.kde.org/show_bug.cgi?id=422490 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 402397] Okular crashes while trying to re-open already deleted document at startup
https://bugs.kde.org/show_bug.cgi?id=402397 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 389448] Width and height of the window doesn't set correctly on HiDPI screen after upgrade to plasma 5.12
https://bugs.kde.org/show_bug.cgi?id=389448 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 356914] Add an option to don't start playing media when call ends
https://bugs.kde.org/show_bug.cgi?id=356914 Raúl Arellano changed: What|Removed |Added CC||raul...@live.com.ar -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 419263] Right click on system tray icon brings wrong menu
https://bugs.kde.org/show_bug.cgi?id=419263 Raúl Arellano changed: What|Removed |Added CC||raul...@live.com.ar --- Comment #7 from Raúl Arellano --- *** Bug 419862 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 419862] Lattedock panel don't open context menu on SystemTray of gtk apps
https://bugs.kde.org/show_bug.cgi?id=419862 Raúl Arellano changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Raúl Arellano --- *** This bug has been marked as a duplicate of bug 419263 *** -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 419862] New: Lattedock panel don't open context menu on SystemTray of gtk apps
https://bugs.kde.org/show_bug.cgi?id=419862 Bug ID: 419862 Summary: Lattedock panel don't open context menu on SystemTray of gtk apps Product: lattedock Version: 0.9.10 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: raul...@live.com.ar Target Milestone: --- Created attachment 127398 --> https://bugs.kde.org/attachment.cgi?id=127398&action=edit Context menu shown on Right click of Microsoft Teams icon SUMMARY Using Microsoft Teams or Zoom (video conference software) add an icon to the system tray, when right click it STEPS TO REPRODUCE 1. Add system tray to latte panel 2. Open zoom/microsoft teams (etc) 3. Right click on zoom/microsoft teams icon in system tray OBSERVED RESULT Opens the system tray context menu instead of the app context menu EXPECTED RESULT See zoom/microsoft teams context menu SOFTWARE/OS VERSIONS Linux: 5.5.6 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 418660] New: Crash on floppy advanced button
https://bugs.kde.org/show_bug.cgi?id=418660 Bug ID: 418660 Summary: Crash on floppy advanced button Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rasas...@gmail.com Target Milestone: --- Application: aqemu () Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-8-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: - What I was doing when the application crashed: I have a virtual machine created (for freedos). I'm trying to add a floppy disk from a disk image file. After some tries I discovered that even a simple click on the advanced button leads to this crash. Regards The crash can be reproduced every time. -- Backtrace: Application: AQEMU (aqemu), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6a2fde5680 (LWP 19403))] Thread 3 (Thread 0x7f6a1ee52700 (LWP 19406)): #0 0x7f6a337a100c in futex_wait_cancelable (private=0, expected=0, futex_word=0x55568e795608) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f6a337a100c in __pthread_cond_wait_common (abstime=0x0, mutex=0x55568e7955b8, cond=0x55568e7955e0) at pthread_cond_wait.c:502 #2 0x7f6a337a100c in __pthread_cond_wait (cond=0x55568e7955e0, mutex=0x55568e7955b8) at pthread_cond_wait.c:655 #3 0x7f6a1f402e83 in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f6a1f402bd7 in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f6a3379afa3 in start_thread (arg=) at pthread_create.c:486 #6 0x7f6a338ad4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f6a26fbb700 (LWP 19405)): #0 0x7f6a338a2819 in __GI___poll (fds=0x7f6a2001a580, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f6a3282f136 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a3282f25c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a33f51743 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6a33eff15b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a33d4ee76 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6a2f61c545 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f6a33d58a67 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6a3379afa3 in start_thread (arg=) at pthread_create.c:486 #9 0x7f6a338ad4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f6a2fde5680 (LWP 19403)): [KCrash Handler] #6 0x55568d499a63 in Add_New_Device_Window::Set_Emulator_Devices(Available_Devices const&) () #7 0x55568d56bd2a in Properties_Window::on_TB_FD_Advanced_Settings_clicked() () #8 0x55568d604b11 in Properties_Window::qt_metacall(QMetaObject::Call, int, void**) () #9 0x7f6a33f298b7 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f6a34963602 in QAbstractButton::clicked(bool) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f6a3496381a in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f6a34964bdf in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f6a34964db5 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f6a348bb4d8 in QWidget::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f6a3487d4c1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f6a34884bb8 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f6a33f00489 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f6a34883ee9 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f6a348d5fd4 in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f6a348d8b5e in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f6a3487d4c1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f6a34884970 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f6a33f00489 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f6a342adff3 in QGuiApplicationPrivate::processMouseEvent(QW
[kdevelop] [Bug 379669] KDevelop continues to hang on exit in itemrepository.h [Bucket::deleteItem]
https://bugs.kde.org/show_bug.cgi?id=379669 Raúl changed: What|Removed |Added Version|unspecified |5.4.6 --- Comment #40 from Raúl --- Hi! This is just to remark that the bug is still hapenning on 5.4.6. See backtrace below, sorry for not providing a full one. When this happens kdevelop CPU usage rises to 100% and I had to kill it. Below the backtrace you can find a console output excerpt, in case it helps. #0 0x7f9d947a5f35 in KDevelop::Bucket::deleteItem >(unsigned short, unsigned int, KDevelop::ItemRepository&) (repository=..., hash=, index=62268, this=0x7f9d380051f0) at ./kdevplatform/serialization/itemrepository.h:972 #1 0x7f9d947a5f35 in KDevelop::Bucket::finalCleanup >(KDevelop::ItemRepository&) (repository=..., this=) at ./kdevplatform/serialization/itemrepository.h:696 #2 0x7f9d947a5f35 in KDevelop::ItemRepository::finalCleanup() (this=) at ./kdevplatform/serialization/itemrepository.h:2195 #3 0x7f9d942b6999 in KDevelop::ItemRepositoryRegistry::finalCleanup() (this=) at ./kdevplatform/serialization/itemrepositoryregistry.cpp:383 #4 0x7f9d946de41a in KDevelop::finalCleanup () at ./kdevplatform/language/duchain/duchain.cpp:1704 #5 0x7f9d946de41a in KDevelop::DUChain::shutdown() (this=) at ./kdevplatform/language/duchain/duchain.cpp:1742 #6 0x7f9d972ae646 in KDevelop::Core::cleanup() (this=0x55df81dbc9c0) at ./kdevplatform/shell/core.cpp:431 #7 0x7f9d972ae8dc in KDevelop::Core::shutdown() (this=0x55df81dbc9c0) at ./kdevplatform/shell/core.cpp:386 #8 0x7f9d9728da5d in KDevelop::MainWindow::~MainWindow() (this=this@entry=0x55df81eebbc0, __in_chrg=, __vtt_parm=) at ./kdevplatform/shell/mainwindow.cpp:150 #9 0x7f9d9728dab9 in KDevelop::MainWindow::~MainWindow() (this=0x55df81eebbc0, __in_chrg=, __vtt_parm=) at ./kdevplatform/shell/mainwindow.cpp:146 #10 0x7f9d95c9e100 in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f9d9681b96b in QWidget::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 --Type for more, q to quit, c to continue without paging-- #12 0x7f9d96921d64 in QMainWindow::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f9d93da717b in KMainWindow::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #14 0x7f9d93df1115 in KXmlGuiWindow::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #15 0x7f9d967dd4c1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f9d967e4970 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f9d95c744f9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f9d95c774db in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f9d95cc6173 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f9d9228ef2e in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7f9d9228f1c8 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f9d9228f25c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f9d95cc5797 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f9d88398401 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #25 0x7f9d95c731cb in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f9d95c7b1a2 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x55df81b253ac in main(int, char**) (argc=, argv=) at ./app/main.cpp:852 UdevQt: unhandled device action "unbind" UdevQt: unhandled device action "unbind" UdevQt: unhandled device action "bind" UdevQt: unhandled device action "bind" kdevplatform.language: item index out of bounds: 36 count: 19 kdevplatform.language: item index out of bounds: 35 count: 19 kdevplatform.language: item index out of bounds: 33 count: 19 kdevplatform.language: item index out of bounds: 32 count: 19 kdevplatform.language: item index out of bounds: 30 count: 19 kdevplatform.language: item index out of bounds: 29 count: 19 kdevplatform.language: item index out of bounds: 27 count: 19 kdevplatform.language: item index out of bounds: 26 count: 19 kdevplatform.language: item index out of bounds: 24 count: 19 kdevplatform.language: item index out of bounds: 23 count: 19 kdevplatform.language: item index out of bounds: 21 count: 19 kdevplatform.language: item index out of bounds: 20 count: 19 kdevplatform.language: item index out of bounds: 91 count: 0 kdevplatform.language: item index out of bounds: 90 count:
[KScreen] [Bug 371447] laptop screen disabled after resume from suspend to RAM
https://bugs.kde.org/show_bug.cgi?id=371447 Raúl changed: What|Removed |Added CC||rasas...@gmail.com --- Comment #9 from Raúl --- For the record. I came into this problem on (Debian) buster. Even I could go to a text console I couldn't switch on the embedded panel on the laptop (eDP). I tried kscreen-doctor and xrandr... till I read this answer: https://askubuntu.com/a/1120169 So the trick was chvt into X and then do xrandr in there. HTH, -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 411089] ews resource crashed on mail check
https://bugs.kde.org/show_bug.cgi?id=411089 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 229218] youtube html5 doesn't work with konqueror (most other html5 videos work)
https://bugs.kde.org/show_bug.cgi?id=229218 --- Comment #5 from Raúl --- I've tested this on a recent konqueror version: - konqueror 5.0.97 - KDE Frameworks 5.51.0 - Qt 5.11.2 youtube is working with html5 videos now. I see some glitches and support is surely improvable, but I would say this bug can be closed. Regards -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 283714] konq: right clicking anywhere in an "a tag" causes strange behavior
https://bugs.kde.org/show_bug.cgi?id=283714 --- Comment #5 from Raúl --- Hello: I've tested this on a recent konqueror version: - konqueror 5.0.97 - KDE Frameworks 5.51.0 - Qt 5.11.2 I would say that I'm either unable to reproduce or this is working as expected now. Recheck would be appreciated. Regards, -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 300940] KHTML fails to render correctly change.org
https://bugs.kde.org/show_bug.cgi?id=300940 Raúl changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Raúl --- I've tested this on a recent konqueror version: - konqueror 5.0.97 - KDE Frameworks 5.51.0 - Qt 5.11.2 I would say it's now working as much as kthml is able to. Therefore, I'm closing this. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 357711] konqueror crashed -- session autosave related [QPointer::operator->]
https://bugs.kde.org/show_bug.cgi?id=357711 Raúl changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Raúl --- I have done some tests with a recent konqueror/KHTML version: - konqueror 5.0.97 - KDE Frameworks 5.51.0 - Qt 5.11.2 My tests are not very complete but at first glance I would say that this is not reproducible. I will mark this accordingly and report again if I see any problem. Regrads, -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 199911] KJS fails to process the AJAX links on Twitter
https://bugs.kde.org/show_bug.cgi?id=199911 --- Comment #6 from Raúl --- Hello. I've just tried with: - konqueror 5.0.97 - KDE Frameworks 5.51.0 - Qt 5.11.2 For instance on https://twitter.com/DailyDilbert I can see text but no pictures or other "eye candy" -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 254955] konqueror freezes when using tinymce editor
https://bugs.kde.org/show_bug.cgi?id=254955 --- Comment #6 from Raúl --- I've tested this on a recent konqueror version: - konqueror 5.0.97 - KDE Frameworks 5.51.0 - Qt 5.11.2 Either basic[0] or full[1] tinymce version loads but fails to work. Konqueror does not crash and cpu load is more than acceptable (2% to 6%). This is all with khtml backend. When I say that it fails to work is that even that web page loads, the editor doesn't show any text and I can't either write anything on the edit frame. [0] https://www.tiny.cloud/docs/demo/basic-example/ [1] https://www.tiny.cloud/docs/demo/full-featured/ I also know that it doesn't work since webengine backend does show text and I can edit/write into the frame. Anyway, I'm not sure if this bug is useful as it is, probably developers would like one or several test cases in order to fix issues. HTH, regards, -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 389073] kmail doesnt start with mailto:
https://bugs.kde.org/show_bug.cgi?id=389073 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 140263] fluendo video java applet just show an static image.
https://bugs.kde.org/show_bug.cgi?id=140263 --- Comment #12 from Raúl --- Hello: I've tried to reproduce this today. I think the consensus nowadays is that using java applets on the browser is considered deprecated and unsafe. Please, correct me if I'm wrong. Therefore a recent version of firefox won't run java applets. Still when loading the link on firefox it knows that a java applet is required, event that firefox doesn't support it. I have the feeling that the web authors noticed about the java unsuitability and included alternatives as direct video download or using a vlc applet. On konqueror side, I had hard time to progress with the triage. I'm not sure if java applet support in the browser has been discontinued or alternatively how to configure it. HTH, -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 401050] New: kmail mailto invokation fails if akonadi is loaded
https://bugs.kde.org/show_bug.cgi?id=401050 Bug ID: 401050 Summary: kmail mailto invokation fails if akonadi is loaded Product: kmail2 Version: 5.9.1 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: rasas...@gmail.com Target Milestone: --- SUMMARY Invoking kmail mailto handler from the command line does nothing if akonadi is loaded. STEPS TO REPRODUCE 1. Make sure akonadi is not run it or stop it (akonadictl stop) 2. Invoke kmail from command line: kmail -qwindowtitle KMail mailto:847...@bugs.debian.org 3. See kmail compose window appears 4. Now akonadi should be running (check akonadictl status) 5. Repeat the previous kmail command: kmail -qwindowtitle KMail mailto:847...@bugs.debian.org OBSERVED RESULT kmail compose window does not appear. The only traces in console are: QIODevice::read (QLocalSocket): device not open (repeated several times) EXPECTED RESULT kmail compose window does appear. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian sid kmail 5.9.1 KDE Frameworks 5.51.0 Qt 5.11.2 (compilado con 5.11.2) ADDITIONAL INFORMATION I'm not running a full plasma desktop (temporarily). I run lxqt. Maybe related to https://bugs.kde.org/show_bug.cgi?id=389073 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 144172] uploading file from form to iframe fires no JS event
https://bugs.kde.org/show_bug.cgi?id=144172 --- Comment #5 from Raúl --- Nowadays konqueror/ktml is unable to load vaadin.com: Konqueror Versión 5.0.97 KDE Frameworks 5.49.0 Qt 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 272590] konq khtml unable to upload files in Transifex
https://bugs.kde.org/show_bug.cgi?id=272590 --- Comment #5 from Raúl --- Hello: I've tried loading transifex web on konqueror/khtml 5.0.97 on current debian sid stack: KDE Frameworks 5.49.0 Qt 5.11.2 The web is not loading properly and konqueror crashes before full render. I'd consider this not reproducible. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 400653] New: Plasma error creating a new Activity
https://bugs.kde.org/show_bug.cgi?id=400653 Bug ID: 400653 Summary: Plasma error creating a new Activity Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rcbarb...@gmail.com Target Milestone: --- Application: kcmshell5 (5.14.2) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.18.15-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: The module fail when I clic on the button for add an icon to a new Activity. The crash can be reproduced every time. -- Backtrace: Application: Módulo de preferencias del sistema (kcmshell5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbe45972840 (LWP 6747))] Thread 8 (Thread 0x7fbe24f91700 (LWP 6757)): #0 0x7fbe4b7bfd34 in read () from /lib64/libc.so.6 #1 0x7fbe477cb4b0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fbe47785a4b in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fbe47785ef0 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fbe4778606c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fbe4a556adb in QEventDispatcherGlib::processEvents (this=0x7fbe1c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fbe4a503adb in QEventLoop::exec (this=this@entry=0x7fbe24f90d40, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7fbe4a352de6 in QThread::exec (this=this@entry=0x5592f9dd3230) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7fbe499e7485 in QQmlThreadPrivate::run (this=0x5592f9dd3230) at /usr/src/debug/libqt5-qtdeclarative-5.11.2-1.1.x86_64/src/qml/qml/ftw/qqmlthread.cpp:148 #9 0x7fbe4a35c9b7 in QThreadPrivate::start (arg=0x5592f9dd3230) at thread/qthread_unix.cpp:367 #10 0x7fbe48f8f554 in start_thread () from /lib64/libpthread.so.0 #11 0x7fbe4b7ceccf in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7fbe261d2700 (LWP 6756)): #0 0x7fbe4b7bfd34 in read () from /lib64/libc.so.6 #1 0x7fbe477cb4b0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fbe47785a4b in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fbe47785ef0 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fbe4778606c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fbe4a556adb in QEventDispatcherGlib::processEvents (this=0x7fbe18000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fbe4a503adb in QEventLoop::exec (this=this@entry=0x7fbe261d1d40, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7fbe4a352de6 in QThread::exec (this=this@entry=0x5592f9567b00) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7fbe499e7485 in QQmlThreadPrivate::run (this=0x5592f9567b00) at /usr/src/debug/libqt5-qtdeclarative-5.11.2-1.1.x86_64/src/qml/qml/ftw/qqmlthread.cpp:148 #9 0x7fbe4a35c9b7 in QThreadPrivate::start (arg=0x5592f9567b00) at thread/qthread_unix.cpp:367 #10 0x7fbe48f8f554 in start_thread () from /lib64/libpthread.so.0 #11 0x7fbe4b7ceccf in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fbe27cd4700 (LWP 6755)): #0 0x7fbe48f954dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fbe4a35d16b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x5592f9623f70) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0x5592f9721e78, mutex=mutex@entry=0x5592f9721e70, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fbe49cf6249 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x5592f9721e68) at /usr/src/debug/libqt5-qtdeclarative-5.11.2-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:245 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x5592f9721df0) at /usr/src/debug/libqt5-qtdeclarative-5.11.2-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:709 #5 0x7fbe49cf64aa in QSGRenderThread::run (this=0x5592f9721df0) at /usr/src/debug/libqt5-qtdeclarative-5.11.2-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:738 #6 0x7fbe4a35c9b7 in QThreadPrivate::start (arg=0x5592f9721df0) at thread/qthread_unix.cpp:367 #7 0x7fbe48f8f554 in start_thread () from /lib64/libpthread.so.0 #8 0x7fbe4b7ceccf in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fbe32ce2700 (LWP 6753)): #0 0x7fbe4b7c42c9 in poll () from /lib64/libc.so.6 #1 0x7fbe47785f46 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fbe4778606c in g_main_context_iteration () from /usr
[kopete] [Bug 127809] Broken error message when retrieving the list of Jabber services fails
https://bugs.kde.org/show_bug.cgi?id=127809 Raúl changed: What|Removed |Added CC||rasas...@gmail.com --- Comment #5 from Raúl --- Hello: Have just tested on kopete 1.13.0 on KDE 4.14.38. When I proceed as per Stefan described, what I have is a single result which only includes the name of the introduced server and no other results, as oposed to a valid jabber server. I don't have any error message or dialog. Therefore I would say this report is no longer valid. Sidenote: I'm not sure if there's a more recent kopete version or if kopete has been ported to KF5 at all. HTH, -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 302089] Crash on tab close. Possibly phonon/gstreamer related.
https://bugs.kde.org/show_bug.cgi?id=302089 --- Comment #2 from Raúl --- Hello: Thanks for caring for this (way too) old bug. I don't think this report is useful anymore, last update was 7+ years ago and I'm not using konqueror anymore (unfortunately). Moreover, I went on using konqueror as web browser some years more after latest update therefore I think the bug is not reproducible or solved. HTH, -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 283271] Random crash KJS, pointers, tab close related
https://bugs.kde.org/show_bug.cgi?id=283271 --- Comment #2 from Raúl --- Hello: Thanks for caring for this (way too) old bug. I don't think this report is useful anymore, last update was 7+ years ago and I'm not using konqueror anymore (unfortunately). Moreover, I went on using konqueror as web browser some years more after latest update therefore I think the bug is not reproducible or solved. HTH, -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 251509] Crashing on massive tab reload [QList::detach_helper()]
https://bugs.kde.org/show_bug.cgi?id=251509 --- Comment #3 from Raúl --- Hello: Thanks for caring for this (way too) old bug. I don't think this report is useful anymore, last update was 7+ years ago and I'm not using konqueror anymore (unfortunately). Moreover, I went on using konqueror as web browser some years more after latest update therefore I think the bug is not reproducible or solved. HTH, -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379669] KDevelop continues to hang on exit in itemrepository.h [Bucket::deleteItem]
https://bugs.kde.org/show_bug.cgi?id=379669 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 389060] Heaptrack analysis keeps firing /usr/bin/plasmoidviewer
https://bugs.kde.org/show_bug.cgi?id=389060 Raúl changed: What|Removed |Added Version|5.2.1 |5.2.3 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 389060] Heaptrack analysis keeps firing /usr/bin/plasmoidviewer
https://bugs.kde.org/show_bug.cgi?id=389060 Raúl changed: What|Removed |Added CC||rasas...@gmail.com --- Comment #1 from Raúl --- Haven't had the time to go deeper into this, but I was trying to heaptrack my native C application and in the debugging of the heaptrack plugin crash what I found this code path: In Plugin::launchHeaptrack auto heaptrackJob = new Job(defaultLaunch); In Job::Job(KDevelop::ILaunchConfiguration* launchConfig) : m_pid(-1) m_analyzedExecutable = iface->executable(launchConfig, errorString).toLocalFile(); With GDB by single stepping into this latter iface->executable I got into the "QUrl ExecutePlasmoidPlugin::executable(ILaunchConfiguration* config, QString& /*error*/) const" function (in ./plugins/executeplasmoid/executeplasmoidplugin.cpp:58) I guess this was not the correct function to call this time, I would have rather expected to go into "QUrl ExecutePlugin::executable( ... )". Therefore the executable name was empty and the plugin somehow crashed in the Job destructor. Find below the relevant launch configuration: [Launch][Launch Configuration 0] Configured Launch Modes=execute Configured Launchers=nativeAppLauncher Name=cim Type=Native Application [Launch][Launch Configuration 0][Data] Arguments= Debugger Shell= Dependencies=@Variant(\x00\x00\x00\t\x00\x00\x00\x00\x01\x00\x00\x00\x0b\x00\x00\x00\x00\x03\x00\x00\x00"\x00C\x00I\x00V\x00I\x00A\x00_\x00R\x00S\x004\x008\x005\x00_\x00L\x00i\x00n\x00u\x00x\x00\x00\x00\x06\x00s\x00r\x00c\x00\x00\x00\x12\x00c\x00i\x00v\x00i\x00a\x00_\x00c\x00i\x00m) Dependency Action=Build Display Demangle Names=true Display Static Members=false EnvironmentGroup= Executable=file:///home/user/cim External Terminal=konsole --noclose --workdir %workdir -e %exe GDB Path= Project Target=cim,src,cim Remote GDB Config Script= Remote GDB Run Script= Remote GDB Shell Script= Start With=ApplicationOutput Use External Terminal=false Working Directory= isExecutable=false -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0
https://bugs.kde.org/show_bug.cgi?id=389829 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 255388] Kmail filters dont work in incoming mail
https://bugs.kde.org/show_bug.cgi?id=255388 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 343114] gets stuck on one request that times out, kmail and akonadiconsole do not display any mail payloads anymore, stuck waiting
https://bugs.kde.org/show_bug.cgi?id=343114 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 389659] Please wait while the message is transferred
https://bugs.kde.org/show_bug.cgi?id=389659 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 387876] Check mail stops working, must restart akonadi to fix
https://bugs.kde.org/show_bug.cgi?id=387876 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 380979] Kmail hangs on "Retrieving folder content"
https://bugs.kde.org/show_bug.cgi?id=380979 Raúl changed: What|Removed |Added CC||rasas...@gmail.com --- Comment #1 from Raúl --- Looking into similar issues, I came accross #377877. Could this be a duplicate of #377877? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377877] kmail stuck with retrieving folders 0%
https://bugs.kde.org/show_bug.cgi?id=377877 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 322477] Make sure Konsole plugin and kdev-python use the default environment variables configuration
https://bugs.kde.org/show_bug.cgi?id=322477 --- Comment #7 from Raúl --- Created attachment 111926 --> https://bugs.kde.org/attachment.cgi?id=111926&action=edit Patch attempt for fixing bug. Find attached a patch trying to fix the bug. I have tested and works as *I* expect but maybe it is not the correct solution. Feel free to comment on it or propose improvements. Note: I have found an artifact when launcher profile is the default profile. In this case no profile is written in the configuration file so profile name is found to be empty and a warning is issued. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 322477] Make sure Konsole plugin and kdev-python use the default environment variables configuration
https://bugs.kde.org/show_bug.cgi?id=322477 Raúl changed: What|Removed |Added CC||rasas...@gmail.com --- Comment #6 from Raúl --- Bumped on kdevelop 5.2.1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 391803] New: Baloo crashes copying from a smb shared folder
https://bugs.kde.org/show_bug.cgi?id=391803 Bug ID: 391803 Summary: Baloo crashes copying from a smb shared folder Product: frameworks-baloo Version: 5.43.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: rcbarb...@gmail.com Target Milestone: --- Application: baloo_file (5.43.0) Qt Version: 5.10.0 Frameworks Version: 5.43.0 Operating System: Linux 4.15.7-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was copying a file from a smb shared folder mounted with cifs. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa2a0dd3900 (LWP 3894))] Thread 3 (Thread 0x7fa2958af700 (LWP 4081)): [KCrash Handler] #6 0x7fa29e86238c in __memmove_avx_unaligned_erms () from /lib64/libc.so.6 #7 0x7fa29fb8f413 in memcpy (__len=2082, __src=, __dest=) at /usr/include/bits/string_fortified.h:34 #8 Baloo::PostingCodec::decode (this=this@entry=0x7fa2958ae987, arr=...) at /usr/src/debug/baloo5-5.43.0-1.1.x86_64/src/codecs/postingcodec.cpp:42 #9 0x7fa29fb80e94 in Baloo::PostingDB::get (this=this@entry=0x7fa2958aea70, term=...) at /usr/src/debug/baloo5-5.43.0-1.1.x86_64/src/engine/postingdb.cpp:100 #10 0x7fa29fb8cb00 in Baloo::WriteTransaction::commit (this=0x7f62880053b0) at /usr/src/debug/baloo5-5.43.0-1.1.x86_64/src/engine/writetransaction.cpp:259 #11 0x7fa29fb863e2 in Baloo::Transaction::commit (this=this@entry=0x7fa2958aeb80) at /usr/src/debug/baloo5-5.43.0-1.1.x86_64/src/engine/transaction.cpp:262 #12 0x555f634ca4fd in Baloo::NewFileIndexer::run (this=0x555f6547d9b0) at /usr/src/debug/baloo5-5.43.0-1.1.x86_64/src/file/newfileindexer.cpp:75 #13 0x7fa29f294e42 in QThreadPoolThread::run (this=0x555f6548d2e0) at thread/qthreadpool.cpp:101 #14 0x7fa29f297bf0 in QThreadPrivate::start (arg=0x555f6548d2e0) at thread/qthread_unix.cpp:376 #15 0x7fa29d84a59b in start_thread () from /lib64/libpthread.so.0 #16 0x7fa29e7fea1f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fa296434700 (LWP 3903)): #0 0x7fa29e7f4179 in poll () from /lib64/libc.so.6 #1 0x7fa29ac0d109 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fa29ac0d21c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fa29f4c4aab in QEventDispatcherGlib::processEvents (this=0x7fa29b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fa29f46b9da in QEventLoop::exec (this=this@entry=0x7fa296433c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fa29f292bfa in QThread::exec (this=) at thread/qthread.cpp:522 #6 0x7fa2a0684a35 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7fa29f297bf0 in QThreadPrivate::start (arg=0x7fa2a08f4d60) at thread/qthread_unix.cpp:376 #8 0x7fa29d84a59b in start_thread () from /lib64/libpthread.so.0 #9 0x7fa29e7fea1f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fa2a0dd3900 (LWP 3894)): #0 0x7fa29e7f4179 in poll () from /lib64/libc.so.6 #1 0x7fa29ac0d109 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fa29ac0d21c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fa29f4c4aab in QEventDispatcherGlib::processEvents (this=0x555f650e4df0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fa29f46b9da in QEventLoop::exec (this=this@entry=0x7ffe85c94270, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fa29f474514 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1332 #6 0x555f634c221c in main (argc=, argv=) at /usr/src/debug/baloo5-5.43.0-1.1.x86_64/src/file/main.cpp:104 Possible duplicates by query: bug 390610, bug 390363, bug 389455, bug 388296, bug 387637. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388790] SMTP does not support OAuth2
https://bugs.kde.org/show_bug.cgi?id=388790 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 369118] Multiple selection of "find in message" causes crash
https://bugs.kde.org/show_bug.cgi?id=369118 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 383856] New: Hang on opening odt file [infinite? loop in RunAroundHelper::fit] [testcase]
https://bugs.kde.org/show_bug.cgi?id=383856 Bug ID: 383856 Summary: Hang on opening odt file [infinite? loop in RunAroundHelper::fit] [testcase] Product: calligrawords Version: unspecified Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: opendocument Assignee: calligra-words-bugs-n...@kde.org Reporter: rasas...@gmail.com Target Milestone: --- Created attachment 107440 --> https://bugs.kde.org/attachment.cgi?id=107440&action=edit Test document that always reproduce the bug. I'm using the debian experimental 3.0.1 package rebuilt for stretch. When opening the attached file I get it looks like an infinite loop at RunAroundHelper::fit. #0 RunAroundHelper::fit (this=this@entry=0x7ffd79884a80, resetHorizontalPosition=resetHorizontalPosition@entry=false, isRightToLeft=, position=...) at ./libs/textlayout/RunAroundHelper.cpp:106 #1 0x7f64111318fc in KoTextLayoutArea::layoutBlock (this=this@entry=0x559f6942f300, cursor=cursor@entry=0x559f6941c4b0) at ./libs/textlayout/KoTextLayoutArea.cpp:1350 #2 0x7f6411134b53 in KoTextLayoutArea::layout (this=this@entry=0x559f6942f300, cursor=cursor@entry=0x559f6941c4b0) at ./libs/textlayout/KoTextLayoutArea.cpp:689 #3 0x7f641114bdbd in KoTextLayoutRootArea::layoutRoot (this=this@entry=0x559f6942f300, cursor=cursor@entry=0x559f6941c4b0) at ./libs/textlayout/KoTextLayoutRootArea.cpp:69 #4 0x7f641114ed8d in KoTextDocumentLayout::doLayout (this=this@entry=0x559f69404ad0) at ./libs/textlayout/KoTextDocumentLayout.cpp:819 #5 0x7f641114f618 in KoTextDocumentLayout::layout (this=0x559f69404ad0) at ./libs/textlayout/KoTextDocumentLayout.cpp:703 #6 0x7f6411cd3499 in QObject::event (this=0x559f69404ad0, e=) at kernel/qobject.cpp:1263 #7 0x7f6412050b8c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f6412058341 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f6412a8d3a7 in KoApplication::notify (this=, receiver=0x559f69404ad0, event=0x559f68ea3da0) at ./libs/main/KoApplication.cpp:657 #10 0x7f6411ca69e0 in QCoreApplication::notifyInternal2 (receiver=0x559f69404ad0, event=event@entry=0x559f68ea3da0) at kernel/qcoreapplication.cpp:988 #11 0x7f6411ca916d in QCoreApplication::sendEvent (event=0x559f68ea3da0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #12 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x559f68e2da00) at kernel/qcoreapplication.cpp:1649 #13 0x7f6411ca95d8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1503 #14 0x7f6411cfac43 in postEventSourceDispatch (s=0x559f68e80030) at kernel/qeventdispatcher_glib.cpp:276 #15 0x7f640b3b97f7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f640b3b9a60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f640b3b9b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f6411cfb04f in QEventDispatcherGlib::processEvents (this=0x559f68e958c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #19 0x7f640fe34cdb in KoProgressUpdater::update (this=) at ./libs/widgetutils/KoProgressUpdater.cpp:166 #20 0x7f6411cd25e9 in QMetaObject::activate (sender=0x559f6932b2a0, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3740 #21 0x7f6411cd25e9 in QMetaObject::activate (sender=sender@entry=0x559f693297e0, signalOffset=, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffd798854b0) at kernel/qobject.cpp:3740 #22 0x7f6411cd2f07 in QMetaObject::activate (sender=sender@entry=0x559f693297e0, m=m@entry=0x7f6410042be0 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffd798854b0) at kernel/qobject.cpp:3602 #23 0x7f640fe3edc1 in KoUpdater::sigProgress (this=this@entry=0x559f693297e0, _t1=, _t1@entry=100) at ./obj-x86_64-linux-gnu/libs/widgetutils/kowidgetutils_automoc.dir/moc_KoUpdater_S7VTS5GQ4NKEZV.cpp:158 #24 0x7f640fe36274 in KoUpdater::setProgress (this=0x559f693297e0, percent=percent@entry=100) at ./libs/widgetutils/KoUpdater.cpp:56 #25 0x7f6412a96d7c in KoDocument::openFile (this=0x559f68e8b100) at ./libs/main/KoDocument.cpp:1610 #26 0x7f6412a9e632 in KoDocument::Private::openFile (this=0x559f68f1a580) at ./libs/main/KoDocument.cpp:271 #27 KoDocument::Private::openLocalFile (this=0x559f68f1a580) at ./libs/main/KoDocument.cpp:293 #28 0x7f6412a9cd0d in KoDocument::openUrlInternal (this=this@entry=0x559f68e8b100, url=file:///home/raul/debs/calligra/testdocs/t5/t5d.odt) at ./libs/main/KoDocument.cpp:2675 #29 0x7f
[Breeze] [Bug 376620] breeze-dark: badly readable gray on gray text in plasma widgets
https://bugs.kde.org/show_bug.cgi?id=376620 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- 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 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360892] Plasma hangs when tooltip/popup is shown
https://bugs.kde.org/show_bug.cgi?id=360892 --- Comment #3 from Raúl Arellano --- Yes, I just build from that commit, running the system 1 hour and everything is working well. Even more smooth and faster than before. Thanks. I thin this can be closed now -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360892] Plasma hangs when tooltip/popup is shown
https://bugs.kde.org/show_bug.cgi?id=360892 Raúl Arellano changed: What|Removed |Added CC||raul...@live.com.ar --- Comment #1 from Raúl Arellano --- I think I'm having the same issue, just when updated plasma 5.6 on KaOSx When log-in, open kick-off, connect an external drive (popup appear), sometimes the system hangs for a couple of seconds. Graphics: Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller Display Server: X.Org 1.18.2 driver: intel Resolution: 1920x1080@60.00hz GLX Renderer: Mesa DRI Intel Sandybridge Mobile GLX Version: 3.0 Mesa 11.1.2 xf86-video-intel 2.99.917.4-1 Just comment to subscribe. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 349719] Crash while compiling cmake project [isChildItem, KDevelop::AbstractFileManagerPlugin::Private::removeFolder]
https://bugs.kde.org/show_bug.cgi?id=349719 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times
https://bugs.kde.org/show_bug.cgi?id=358171 --- Comment #21 from Raúl Arellano --- (In reply to AJslye from comment #20) > I'll need to test some more, but today's update in Arch to plasma-framework > 5.18.0-2 seems to have fixed this issue. I wonder what they patched or back > ported? Did they updated something? I've been up to 3 days without an issue -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times
https://bugs.kde.org/show_bug.cgi?id=358171 --- Comment #17 from Raúl Arellano --- Note that this is not happening in ALL intel graphics (i have a netbook with an intel atom / gma950 i think) @David Edmundson .. I think so, Now I realize that I always have that Xorg.0.log in /var/log even when it does not happens (i changed sddm theme a couple days ago and still have same error with todays date) In the test, i login with no error but nothings happens. here's the output raul ~ $ sddm-greeter --theme /usr/share/sddm/themes/breeze/ --test-mode [12:06:05.242] (II) GREETER: Reading from "/usr/share/xsessions/plasma.desktop" [12:06:05.243] (II) GREETER: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop" [12:06:05.243] (EE) GREETER: Socket error: "QLocalSocket::connectToServer: Invalid name" [12:06:06.134] (II) GREETER: Adding view for "VGA1" QRect(0,0 1920x1080) [12:06:06.391] (II) GREETER: Overwriting existing old cached entry due to collision. [12:06:08.459] (II) GREETER: Reading from "/usr/share/xsessions/plasma.desktop" [12:06:08.459] (WW) GREETER: QIODevice::write (QLocalSocket): device not open ^C raul ~ $ sudo sddm-greeter --theme /usr/share/sddm/themes/breeze/ --test-mode Contraseña: Put my password (i don't have more users), hit enter, login button and password textbox sets to gray, and nothing happens -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times
https://bugs.kde.org/show_bug.cgi?id=358171 Raúl Arellano changed: What|Removed |Added CC||raul...@live.com.ar --- Comment #11 from Raúl Arellano --- I'm also having this problem. I'm using KaOSx in a notebook with an intel b950. Every time it happens I see errors in Xorg log, if i login to plasma (wayland) everything works fine. Forum thread: http://kaosx.us/phpBB3/viewtopic.php?f=10&t=1299 Error in Xorg: http://kaosx.us/phpBB3/viewtopic.php?p=6809#p6809 (full log: https://paste.kde.org/p4uvc9wcd) -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 356157] Configuration for groupwise protocol via haze not posible
https://bugs.kde.org/show_bug.cgi?id=356157 Raúl Osuna changed: What|Removed |Added CC||ros...@suse.com --- Comment #2 from Raúl Osuna --- I can confirm this bug, and also that the proposed patch lets use Groupwise protocol again. Please consider including it. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 357711] konqueror crashed -- session autosave related [QPointer::operator->]
https://bugs.kde.org/show_bug.cgi?id=357711 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 357711] konqueror crashed -- session autosave related [QPointer::operator->]
https://bugs.kde.org/show_bug.cgi?id=357711 --- Comment #1 from Raúl --- Created attachment 96533 --> https://bugs.kde.org/attachment.cgi?id=96533&action=edit New crash information added by DrKonqi konqueror (4.14.13) on KDE Platform 4.14.14 using Qt 4.8.7 - What I was doing when the application crashed: I opnen konqueror again (same as above). This time I got to open a pair of new tabs. I browsed in one of then, closed and the konqueror crashed. -- Backtrace (Reduced): #6 0x7f9ab9042b2c in QPointer::operator-> (this=) at /usr/include/qt4/QtCore/qpointer.h:74 #7 KHTMLPart::saveState (this=0x54457d00, stream=...) at ../../khtml/khtml_part.cpp:5403 #8 0x7f9ab9042f93 in KHTMLPart::saveState (this=, stream=...) at ../../khtml/khtml_part.cpp:5467 #9 0x7f9ab9042f93 in KHTMLPart::saveState (this=, stream=...) at ../../khtml/khtml_part.cpp:5467 #10 0x7f9ab9042f93 in KHTMLPart::saveState (this=, stream=...) at ../../khtml/khtml_part.cpp:5467 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 357711] New: konqueror crashed -- session autosave related [QPointer::operator->]
https://bugs.kde.org/show_bug.cgi?id=357711 Bug ID: 357711 Summary: konqueror crashed -- session autosave related [QPointer::operator->] Product: konqueror Version: unspecified Platform: Debian unstable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: rasas...@gmail.com Application: konqueror (4.14.13) KDE Platform Version: 4.14.14 Qt Version: 4.8.7 Operating System: Linux 4.3.0-1-amd64 x86_64 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: - What I was doing when the application crashed: I opened konqueror from krunner. Iit restored a previously saved session. I always kill konqueror so session is saved. The session is quite big with a ~15 tabs window and another singled tab window. After the session was successfully restored konqueror "idled"* in the background for some minutes and it crashed. * I say idled but it actually takes some CPU as some opened webs require javascript running in background I have had some other similar crashed also related with autosave but unfortunately I'm unable to explain how they are reproduced. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f92a7262900 (LWP 7333))] Thread 6 (Thread 0x7f9285604700 (LWP 7735)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f928af18a4d in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7f928b9a3514 ) at /build/qtwebkit-B2cRei/qtwebkit-2.3.4.dfsg/Source/WTF/wtf/FastMalloc.cpp:2575 #2 0x7f928af18aa9 in WTF::TCMalloc_PageHeap::runScavengerThread (context=0x7f928b9a3514 ) at /build/qtwebkit-B2cRei/qtwebkit-2.3.4.dfsg/Source/WTF/wtf/FastMalloc.cpp:1771 #3 0x7f929fde6284 in start_thread (arg=0x7f9285604700) at pthread_create.c:333 #4 0x7f92a6b8774d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f9244602700 (LWP 7757)): #0 0x7f92a6b7e86d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f929f70c1cc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f929f70c2dc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f92a45b93a6 in QEventDispatcherGlib::processEvents (this=0x7f923c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #4 0x7f92a45872e1 in QEventLoop::processEvents (this=this@entry=0x7f9244601cd0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f92a4587655 in QEventLoop::exec (this=this@entry=0x7f9244601cd0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f92a4476559 in QThread::exec (this=) at thread/qthread.cpp:538 #7 0x7f92a4478e4c in QThreadPrivate::start (arg=0x1be0d70) at thread/qthread_unix.cpp:352 #8 0x7f929fde6284 in start_thread (arg=0x7f9244602700) at pthread_create.c:333 #9 0x7f92a6b8774d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f92430ac700 (LWP 7787)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7f92a4479394 in QWaitConditionPrivate::wait (time=3, this=0x1e77be0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=this@entry=0x1f04f00, mutex=mutex@entry=0x1e86848, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7f92a446bff7 in QThreadPoolThread::run (this=0x1f04ef0) at concurrent/qthreadpool.cpp:142 #4 0x7f92a4478e4c in QThreadPrivate::start (arg=0x1f04ef0) at thread/qthread_unix.cpp:352 #5 0x7f929fde6284 in start_thread (arg=0x7f92430ac700) at pthread_create.c:333 #6 0x7f92a6b8774d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f924246e700 (LWP 7801)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f928ac3c191 in JSC::BlockAllocator::blockFreeingThreadMain (this=0x7f9284d73398) at /build/qtwebkit-B2cRei/qtwebkit-2.3.4.dfsg/Source/JavaScriptCore/heap/BlockAllocator.cpp:128 #2 0x7f928af48fe6 in WTF::wtfThreadEntryPoint (param=0x1fa8be0) at /build/qtwebkit-B2cRei/qtwebkit-2.3.4.dfsg/Source/WTF/wtf/ThreadingPthreads.cpp:196 #3 0x7f929fde6284 in start_thread (arg=0x7f924246e700) at pthread_create.c:333 #4 0x7f92a6b8774d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f9241532700 (LWP 7826)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7f92a4479394 in QWaitConditionPrivate::wait (time=3, this=0x1e6d5d0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=this@entry=0x1e79430, mutex=mutex@entry=0x1e86848, time=3) a
[kdevelop] [Bug 357355] New: Crash on old session remove
https://bugs.kde.org/show_bug.cgi?id=357355 Bug ID: 357355 Summary: Crash on old session remove Product: kdevelop Version: 4.7.1 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: rasas...@gmail.com Application: kdevelop (4.7.1) KDE Platform Version: 4.14.14 Qt Version: 4.8.7 Operating System: Linux 4.3.0-1-amd64 x86_64 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: - What I was doing when the application crashed: I opened kdevelop after long time without using it. I have session holding only one old project. I started a new session, after the session was opened, I went back to the old session and remove it from the session menu. kdevelop crashed. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8d8ea6c940 (LWP 5650))] Thread 7 (Thread 0x7f8d70fed700 (LWP 5651)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f8d88d18d2a in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x7f8d88d18d59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x7f8d8762c284 in start_thread (arg=0x7f8d70fed700) at pthread_create.c:333 #4 0x7f8d8b15674d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f8cef258700 (LWP 5654)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7f8d8b808394 in QWaitConditionPrivate::wait (time=1000, this=0x307edc0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=this@entry=0x2e76468, mutex=mutex@entry=0x2e76470, time=time@entry=1000) at thread/qwaitcondition_unix.cpp:158 #3 0x7f8d8a115f16 in KDevelop::DUChainPrivate::CleanupThread::run (this=0x2e76450) at /build/kdevplatform-Y8NEm6/kdevplatform-1.7.1/language/duchain/duchain.cpp:283 #4 0x7f8d8b807e4c in QThreadPrivate::start (arg=0x2e76450) at thread/qthread_unix.cpp:352 #5 0x7f8d8762c284 in start_thread (arg=0x7f8cef258700) at pthread_create.c:333 #6 0x7f8d8b15674d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f8ce1d04700 (LWP 5655)): #0 0x7ffed2578caf in clock_gettime () #1 0x7f8d8b16357d in __GI___clock_gettime (clock_id=clock_id@entry=1, tp=tp@entry=0x7f8ce1d03a10) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f8d8b862795 in do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:127 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:144 #4 0x7f8d8b949215 in QTimerInfoList::updateCurrentTime (this=0x7f8cdc002ed0) at kernel/qeventdispatcher_unix.cpp:354 #5 QTimerInfoList::timerWait (this=0x7f8cdc002ed0, tm=...) at kernel/qeventdispatcher_unix.cpp:460 #6 0x7f8d8b947adc in timerSourcePrepareHelper (src=, timeout=0x7f8ce1d03ac4) at kernel/qeventdispatcher_glib.cpp:136 #7 0x7f8d84f9a75d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f8d84f9b0fb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f8d84f9b2dc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f8d8b9483a6 in QEventDispatcherGlib::processEvents (this=0x7f8cdc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #11 0x7f8d8b9162e1 in QEventLoop::processEvents (this=this@entry=0x7f8ce1d03c90, flags=...) at kernel/qeventloop.cpp:149 #12 0x7f8d8b916655 in QEventLoop::exec (this=this@entry=0x7f8ce1d03c90, flags=...) at kernel/qeventloop.cpp:204 #13 0x7f8d8b805559 in QThread::exec (this=) at thread/qthread.cpp:538 #14 0x7f8d8b807e4c in QThreadPrivate::start (arg=0x317e0e8) at thread/qthread_unix.cpp:352 #15 0x7f8d8762c284 in start_thread (arg=0x7f8ce1d04700) at pthread_create.c:333 #16 0x7f8d8b15674d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f8cbebc6700 (LWP 5676)): #0 0x7f8d84f9ab2c in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f8d84f9b170 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8d84f9b2dc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8d8b9483a6 in QEventDispatcherGlib::processEvents (this=0x7f8cb8003080, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #4 0x7f8d8b9162e1 in QEventLoop::processEvents (this=this@entry=0x7f8cbebc5c40, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f8d8b916655 in QEventLoop::exec (this=this@entry=0x7f8cbebc5c40, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f8d8b805559 in QThread::exec (this=this@entry=0x40ff2b0) at thread/qthread.cpp:538 #7 0x7f8d8b8f6343 in QInotify
[kdelibs] [Bug 333544] KWin crashes after running KAlgebra from git under valgrind and then pressing the Kickoff menu item.
https://bugs.kde.org/show_bug.cgi?id=333544 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 333475] plasma-desktop crashed
https://bugs.kde.org/show_bug.cgi?id=333475 Raúl changed: What|Removed |Added CC||rasas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
