[plasmashell] [Bug 447870] plasmashell crashes in HistoryItem::create() when selecting an item in plasma-pass
https://bugs.kde.org/show_bug.cgi?id=447870 --- Comment #3 from Isaac Salgueiro --- No worries, thanks for the update on this. I just installed plasma-pass 1.2.0-2 and it works for me. Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 6.5.0-21-generic (64-bit) Graphics Platform: X11 Processors: 12 × 13th Gen Intel® Core™ i7-1355U Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 467000] Can't load app.mavenlink.com/timesheets
https://bugs.kde.org/show_bug.cgi?id=467000 Isaac Salgueiro changed: What|Removed |Added Version|22.12.2 |22.12.3 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 467000] New: Can't load app.mavenlink.com/timesheets
https://bugs.kde.org/show_bug.cgi?id=467000 Bug ID: 467000 Summary: Can't load app.mavenlink.com/timesheets Classification: Applications Product: Falkon Version: 22.12.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: isalgue...@gmail.com Target Milestone: --- SUMMARY *** When you open app.mavenlink.com/timesheets webpage loads a spinner and never loads content. *** STEPS TO REPRODUCE 1. Open app.mavenlink.com/timesheets (registered account needed) OBSERVED RESULT Infinite spinner. Following errors in console: - Uncaught TypeError: u.at is not a function - Uncaught DOMException: Blocked a frame with origin "https://service.force.com; from accessing a cross-origin frame. EXPECTED RESULT Page loads SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447870] New: plasmashell crashes when selecting an item in plasma-pass
https://bugs.kde.org/show_bug.cgi?id=447870 Bug ID: 447870 Summary: plasmashell crashes when selecting an item in plasma-pass Product: plasmashell Version: 5.23.4 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: isalgue...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.23.4) Qt Version: 5.15.3 Frameworks Version: 5.89.0 Operating System: Linux 5.11.0-43-generic x86_64 Windowing System: X11 Distribution: KDE neon User - Plasma 25th Anniversary Edition DrKonqi: 5.23.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Select an item in plasma-pass - Unusual behavior I noticed: Plasma shell crashed and restarted itself. Nothing was copied to clipboard. `pass -c` command worked fine. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 1680] [New LWP 1701] [New LWP 1749] [New LWP 1750] [New LWP 1751] [New LWP 1752] [New LWP 1753] [New LWP 1754] [New LWP 1755] [New LWP 1778] [New LWP 1807] [New LWP 1808] [New LWP 1815] [New LWP 1816] [New LWP 1817] [New LWP 1828] [New LWP 1836] [New LWP 1837] [New LWP 1922] [New LWP 1923] [New LWP 2633] [New LWP 2634] [New LWP 2641] [New LWP 2642] [New LWP 2643] [New LWP 2644] [New LWP 2645] [New LWP 2646] [New LWP 2647] [New LWP 2648] [New LWP 2649] [New LWP 2650] [New LWP 2651] [New LWP 2652] [New LWP 2653] [New LWP 2654] [New LWP 2655] [New LWP 2656] [New LWP 2657] [New LWP 2658] [New LWP 3237] [New LWP 3238] [New LWP 3256] [New LWP 3257] [New LWP 3344] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f50f1bf9aff in poll () from /lib/x86_64-linux-gnu/libc.so.6 __preamble__ [Current thread is 1 (Thread 0x7f50edd3d9c0 (LWP 1672))] Thread 46 (Thread 0x7f50057fa700 (LWP 3344)): #0 0x7f50f0eca376 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f50e59549bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #2 0x7f50e595472b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #3 0x7f50f0ec3609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f50f1c06293 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 45 (Thread 0x7f4fe37fe700 (LWP 3257)): #0 0x7f50f0eca376 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f50f1f8e5cb in QWaitConditionPrivate::wait (deadline=..., this=0x563e3ebf81c0) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x563e3e438800, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f50f3bf8c24 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f50f3bf9099 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f50f1f8845c in QThreadPrivate::start (arg=0x563e3e438760) at thread/qthread_unix.cpp:329 #6 0x7f50f0ec3609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #7 0x7f50f1c06293 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 44 (Thread 0x7f4fe3fff700 (LWP 3256)): #0 0x7f50f0eca376 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f50e59549bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #2 0x7f50e595472b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #3 0x7f50f0ec3609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f50f1c06293 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 43 (Thread 0x7f4fedc99700 (LWP 3238)): #0 0x7f50f0eca376 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f50f1f8e5cb in QWaitConditionPrivate::wait (deadline=..., this=0x563e3e49f800) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x563e3e5473c0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f50f3bf8c24 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f50f3bf9099 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f50f1f8845c in QThreadPrivate::start (arg=0x563e3e547320) at thread/qthread_unix.cpp:329 #6 0x7f50f0ec3609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #7 0x7f50f1c06293 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 42 (Thread 0x7f4fee49a700 (LWP 3237)): #0 0x7f50f0eca376 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f50e59549bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #2 0x7f50e595472b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #3 0x7f50f0ec3609 in start_thread ()
[konsole] [Bug 431827] Konsole crashes if issuing CTLR+d if input is copied to other tabs
https://bugs.kde.org/show_bug.cgi?id=431827 Isaac Salgueiro changed: What|Removed |Added CC|isalgue...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411561] Konsole segfaults when sending `exit` to multiple tabs
https://bugs.kde.org/show_bug.cgi?id=411561 --- Comment #11 from Isaac Salgueiro --- Sorry, is Qt 5.15.2. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411561] Konsole segfaults when sending `exit` to multiple tabs
https://bugs.kde.org/show_bug.cgi?id=411561 Isaac Salgueiro changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #10 from Isaac Salgueiro --- Hi All This is fixed for me in konsole 21.04.0 and Qt 5.12.2 Regards, Isaac -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 379874] Crash opening a docx file
https://bugs.kde.org/show_bug.cgi?id=379874 --- Comment #7 from Isaac Salgueiro --- Hi Pierre Sorry, I don't remember with what document calligrawords crashed and rn I can't find a document that makes it crash. BR, Isaac -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 379874] Crash opening a docx file
https://bugs.kde.org/show_bug.cgi?id=379874 Isaac Salgueiro changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Isaac Salgueiro --- Sorry, forgot to update the status on my previous comment. -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 379874] Crash opening a docx file
https://bugs.kde.org/show_bug.cgi?id=379874 --- Comment #3 from Isaac Salgueiro --- Created attachment 134149 --> https://bugs.kde.org/attachment.cgi?id=134149=edit kcrash dump Well, I don't even remember with what document this segfaulted three years ago, but it just crashed on the second document I tried to open. calligrawords 1:3.2.0-0xneon+20.04+focal+build8 Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-58-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8665U CPU @ 1.90GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 420280] Can't add Google account: authentication stucks
https://bugs.kde.org/show_bug.cgi?id=420280 --- Comment #33 from Isaac Salgueiro --- (In reply to Nicolas Fella from comment #29) > @Isaac your issue is described in https://bugs.kde.org/show_bug.cgi?id=426034 > > It's fixed upstream but that fix hasn't arrived in Neon yet You're right Nicolas, thanks for the link, I already put my vote on the upstream issue. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 420280] Can't add Google account: authentication stucks
https://bugs.kde.org/show_bug.cgi?id=420280 Isaac Salgueiro changed: What|Removed |Added CC||isalgue...@gmail.com --- Comment #28 from Isaac Salgueiro --- I have a similar issue when trying to log in my google account. For me, clicking in 'Google' in the 'Add new account' dialog opens no window and it shows the following error message: "Message recipient disconnected from message bus without responding". I think these are the relevant logs: nov 25 09:59:17 myhostname signond[6067]: Cannot use KWindowSystem without a QGuiApplication nov 25 09:59:17 myhostname kernel: signond[6067]: segfault at 8 ip 7ff745b657ae sp 7ffca98bc090 error 4 in libQt5Core.so.5.15.1[7ff7459c6000+3080> Versions I'm running: kaccounts-providers/focal,now 4:20.08.3-0xneon+20.04+focal+build13 amd64 [installed,automatic] KDE providers for accounts sign-on Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 Kernel Version: 5.4.0-54-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8665U CPU @ 1.90GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Please, let me know if there's some other test or log that you may need to get your way around this. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 411493] kwrite memory usage when opening a rather big file
https://bugs.kde.org/show_bug.cgi?id=411493 --- Comment #5 from Isaac Salgueiro --- Just tried again (20.08.02) and this time CPU only spiked when scrolling through the file. IMO memory usage is still huge as you can see in the attached screenshot: that ~4GB step was the memory used by kwrite. Overall responsiveness is way better than when I opened this issue, but still system felt a bit laggy until I closed kwrite. I'm currently using: Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 Kernel Version: 5.4.0-52-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8665U CPU @ 1.90GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 411493] kwrite memory usage when opening a rather big file
https://bugs.kde.org/show_bug.cgi?id=411493 --- Comment #4 from Isaac Salgueiro --- Created attachment 132904 --> https://bugs.kde.org/attachment.cgi?id=132904=edit kwrite 20.08.2 CPU and memory usage -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 Isaac Salgueiro changed: What|Removed |Added CC||isalgue...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[korgac] [Bug 412498] New: KOrganizer crash
https://bugs.kde.org/show_bug.cgi?id=412498 Bug ID: 412498 Summary: KOrganizer crash Product: korgac Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: isalgue...@gmail.com Target Milestone: --- Application: korgac (5.12.1) Qt Version: 5.12.3 Frameworks Version: 5.62.0 Operating System: Linux 5.0.0-29-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: I was not using korganizer in the foreground. Kmail received some new mails, including a new event invite, and korganizer and the reminder daemon crashed. -- Backtrace: Application: KOrganizer Reminder Daemon (korgac), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc95702dd00 (LWP 2760))] Thread 5 (Thread 0x7fc92dfd5700 (LWP 2793)): #0 0x7fc950df90b4 in __GI___libc_read (fd=12, buf=0x7fc92dfd4b10, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fc947db22d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc947d6d0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc947d6d570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc947d6d6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc951958dcb in QEventDispatcherGlib::processEvents (this=0x7fc924000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fc9518fa03a in QEventLoop::exec (this=this@entry=0x7fc92dfd4d20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7fc9517214ca in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7fc951722c72 in QThreadPrivate::start (arg=0x55da2418c0f0) at thread/qthread_unix.cpp:361 #9 0x7fc949ae96db in start_thread (arg=0x7fc92dfd5700) at pthread_create.c:463 #10 0x7fc950e0a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fc92e7d6700 (LWP 2789)): #0 0x7fc950dfdbf9 in __GI___poll (fds=0x7fc9200049b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc947d6d5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc947d6d6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc951958dcb in QEventDispatcherGlib::processEvents (this=0x7fc92b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fc9518fa03a in QEventLoop::exec (this=this@entry=0x7fc92e7d5d20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fc9517214ca in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7fc951722c72 in QThreadPrivate::start (arg=0x55da241dbf30) at thread/qthread_unix.cpp:361 #7 0x7fc949ae96db in start_thread (arg=0x7fc92e7d6700) at pthread_create.c:463 #8 0x7fc950e0a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fc92fbf0700 (LWP 2786)): #0 0x7fc950dfdbf9 in __GI___poll (fds=0x7fc928018f90, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc947d6d5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc947d6d6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc951958dcb in QEventDispatcherGlib::processEvents (this=0x7fc928000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fc9518fa03a in QEventLoop::exec (this=this@entry=0x7fc92fbefcf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fc9517214ca in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7fc951dc7015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fc951722c72 in QThreadPrivate::start (arg=0x7fc95203ed80) at thread/qthread_unix.cpp:361 #8 0x7fc949ae96db in start_thread (arg=0x7fc92fbf0700) at pthread_create.c:463 #9 0x7fc950e0a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fc93689d700 (LWP 2781)): #0 0x7fc950dfdbf9 in __GI___poll (fds=0x7fc93689cc28, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc94a118747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fc94a11a36a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fc93947d578 in QXcbEventQueue::run (this=0x55da241059f0) at qxcbeventqueue.cpp:228 #4 0x7fc951722c72 in QThreadPrivate::start (arg=0x55da241059f0) at thread/qthread_unix.cpp:361 #5 0x7fc949ae96db in start_thread (arg=0x7fc93689d700) at pthread_create.c:463 #6 0x7fc950e0a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fc95702dd00 (LWP 2760)): [KCrash Handler] #6
[kmail2] [Bug 376156] Deleting messages in IMAP account with server side folders enabled isn't possible
https://bugs.kde.org/show_bug.cgi?id=376156 Isaac Salgueiro changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #7 from Isaac Salgueiro --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 412390] New: KOrganizer crash when hiding calendars
https://bugs.kde.org/show_bug.cgi?id=412390 Bug ID: 412390 Summary: KOrganizer crash when hiding calendars Product: korganizer Version: 5.12.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: isalgue...@gmail.com Target Milestone: --- Application: korganizer (5.12.1) Qt Version: 5.12.3 Frameworks Version: 5.62.0 Operating System: Linux 5.0.0-29-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: Application crashed after unchecking some of the calendars shown in the bottom-right corner in KOrganizer. This was on a Google account with about a dozen calendars. The crash does not seem to be reproducible. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4c0fc54880 (LWP 10998))] Thread 7 (Thread 0x7f4bd17af700 (LWP 11021)): #0 0x7f4c02df09f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f4bf7d18fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f4bf7d18f68, cond=0x7f4bf7d18f90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f4bf7d18f90, mutex=0x7f4bf7d18f68) at pthread_cond_wait.c:655 #3 0x7f4bf7a22844 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f4bf7a22889 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f4c02dea6db in start_thread (arg=0x7f4bd17af700) at pthread_create.c:463 #6 0x7f4c0b3b888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f4bd29c0700 (LWP 11019)): #0 0x7f4c02df09f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5590a7ebb368) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5590a7ebb318, cond=0x5590a7ebb340) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5590a7ebb340, mutex=0x5590a7ebb318) at pthread_cond_wait.c:655 #3 0x7f4bd32b584b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f4bd32b5447 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f4c02dea6db in start_thread (arg=0x7f4bd29c0700) at pthread_create.c:463 #6 0x7f4c0b3b888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f4be6dee700 (LWP 11007)): #0 0x7f4c0b3a70b4 in __GI___libc_read (fd=13, buf=0x7f4be6dedb10, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f4c00f622d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4c00f1d0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4c00f1d570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f4c00f1d6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f4c0bf06dcb in QEventDispatcherGlib::processEvents (this=0x7f4bd4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f4c0bea803a in QEventLoop::exec (this=this@entry=0x7f4be6dedd20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f4c0bccf4ca in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7f4c0bcd0c72 in QThreadPrivate::start (arg=0x5590a7b8c880) at thread/qthread_unix.cpp:361 #9 0x7f4c02dea6db in start_thread (arg=0x7f4be6dee700) at pthread_create.c:463 #10 0x7f4c0b3b888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f4be75ef700 (LWP 11004)): #0 0x7f4c00f1a4f9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f4c00f1cef2 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4c00f1d570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4c00f1d6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f4c0bf06dcb in QEventDispatcherGlib::processEvents (this=0x7f4bdc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f4c0bea803a in QEventLoop::exec (this=this@entry=0x7f4be75eed20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f4c0bccf4ca in QThread::exec (this=) at thread/qthread.cpp:531 #7 0x7f4c0bcd0c72 in QThreadPrivate::start (arg=0x5590a7b35c10) at thread/qthread_unix.cpp:361 #8 0x7f4c02dea6db in start_thread (arg=0x7f4be75ef700) at pthread_create.c:463 #9 0x7f4c0b3b888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f4becd24700 (LWP 11000)): #0 0x7f4c0b3abbf9 in __GI___poll (fds=0x7f4be0020bb0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4c00f1d5c9 in ?? () from
[konsole] [Bug 411561] Konsole segfaults when sending `exit` to multiple tabs
https://bugs.kde.org/show_bug.cgi?id=411561 --- Comment #8 from Isaac Salgueiro --- Created attachment 122819 --> https://bugs.kde.org/attachment.cgi?id=122819=edit New backtrace -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411561] Konsole segfaults when sending `exit` to multiple tabs
https://bugs.kde.org/show_bug.cgi?id=411561 --- Comment #7 from Isaac Salgueiro --- Don't know if this can help, but I had two konsole windows opened as background jobs and both got closed because of ssh idle timeout. Job 1 had 6 opened ssh tabs and segfaulted. Job 2 had 2 opened ssh tabs and exited normally. KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = konsole path = /usr/bin pid = 8118 KCrash: Arguments: /usr/bin/konsole --tabs-from-file /home/isalgueiro/Vaults/xxx/konsole_sessions/1.tabs KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 9 and type 'Read', disabling... [1]+ Stopped konsole --tabs-from-file ~/Vaults/xxx/konsole_sessions/1.tabs [2] Donekonsole --tabs-from-file ~/Vaults/xxx/konsole_sessions/2.tabs I'm attaching this new backtrace -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411561] Konsole segfaults when sending `exit` to multiple tabs
https://bugs.kde.org/show_bug.cgi?id=411561 --- Comment #3 from Isaac Salgueiro --- OK, so here's my complete workflow on this, just in case anything in how I'm launching Konsole is causing this segfault: 1. I have a "tabs file" in a vault with something like this: title: Server1;; command: sshpass -p supersecretpassword1 ssh user1@server1 title: Server2;; command: sshpass -p supersecretpassword2 ssh user2@server2 title: Server3;; command: sshpass -p supersecretpassword3 ssh user3@server3 title: Server4;; command: sshpass -p supersecretpassword4 ssh user4@server4 title: Server5;; command: sshpass -p supersecretpassword5 ssh user5@server5 title: Server6;; command: sshpass -p supersecretpassword6 ssh user6@server6 2. An alias to execute `konsole --tabs-from-file /path/to/that/tabs/file/from/1 &` 3. When I execute that alias, a new Konsole window opens up with 7 tabs, the 6 ssh sessions and a local shell (BTW no idea why it opens this extra local tab) 4. In this new window I do Edit / Copy input to / All tabs in current window 5. Everything works fine except when I run `exit`. Before hitting this bug (sorry, can't tell exactly in what Konsole version started this bug :( ) Konsole just closed normally. Now I'm getting segafults almost every time I `exit`. Hope this helps! Let me know if you want me to do any other test on this. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411561] Konsole segfaults when sending `exit` to multiple tabs
https://bugs.kde.org/show_bug.cgi?id=411561 --- Comment #2 from Isaac Salgueiro --- Maybe is because how I start konsole? I use the tabs-from-file flag to open konsole with SSH as start command. Sorry if the flag name is not exactly that, I'm not on my PC and writing this off the top of my head... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411561] New: Konsole segfaults when sending `exit` to multiple tabs
https://bugs.kde.org/show_bug.cgi?id=411561 Bug ID: 411561 Summary: Konsole segfaults when sending `exit` to multiple tabs Product: konsole Version: 19.08.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: isalgue...@gmail.com Target Milestone: --- Application: konsole (19.08.0) Qt Version: 5.12.3 Frameworks Version: 5.61.0 Operating System: Linux 5.0.0-27-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: I had a konsole window with 7 tabs oppened: 6 ssh sessions and a local shell. In one of the ssh sessions tab I selected Edit / Copy input to / All tabs in current window and executed `exit`. Konsole crashed with attached backtrace. The crash can be reproduced every time. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f46976495c0 (LWP 6934))] Thread 4 (Thread 0x7f46718bf700 (LWP 6937)): #0 0x7f468e4b99f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x559e9d856788) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x559e9d856738, cond=0x559e9d856760) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x559e9d856760, mutex=0x559e9d856738) at pthread_cond_wait.c:655 #3 0x7f46728a384b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f46728a3447 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f468e4b36db in start_thread (arg=0x7f46718bf700) at pthread_create.c:463 #6 0x7f4696f5088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f467a64b700 (LWP 6936)): #0 0x7f4696f43bf9 in __GI___poll (fds=0x7f4674004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f468c76c5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f468c76c6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4693608dcb in QEventDispatcherGlib::processEvents (this=0x7f4674000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f46935aa03a in QEventLoop::exec (this=this@entry=0x7f467a64ad70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f46933d14ca in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f4690e05015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f46933d2c72 in QThreadPrivate::start (arg=0x7f469107cd80) at thread/qthread_unix.cpp:361 #8 0x7f468e4b36db in start_thread (arg=0x7f467a64b700) at pthread_create.c:463 #9 0x7f4696f5088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f4681ff6700 (LWP 6935)): #0 0x7f4696f43bf9 in __GI___poll (fds=0x7f4681ff5ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f468eae2747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f468eae436a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f4684ddd578 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f46933d2c72 in QThreadPrivate::start (arg=0x559e9d5a0300) at thread/qthread_unix.cpp:361 #5 0x7f468e4b36db in start_thread (arg=0x7f4681ff6700) at pthread_create.c:463 #6 0x7f4696f5088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f46976495c0 (LWP 6934)): [KCrash Handler] #6 QWidget::testAttribute (attribute=, this=) at ../../include/QtWidgets/../../src/widgets/kernel/qwidget.h:868 #7 QWidget::isEnabled (this=0x0) at ../../include/QtWidgets/../../src/widgets/kernel/qwidget.h:767 #8 QWidget::setFocus (this=0x0, reason=Qt::OtherFocusReason) at kernel/qwidget.cpp:6515 #9 0x7f46935db98f in QtPrivate::QSlotObjectBase::call (a=0x7fff8e66b9c0, r=0x559e9d6c8600, this=0x559e9d6dff30) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #10 QMetaObject::activate (sender=sender@entry=0x559e9d6429a0, signalOffset=, local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7fff8e66b9c0) at kernel/qobject.cpp:3776 #11 0x7f46935dbf47 in QMetaObject::activate (sender=sender@entry=0x559e9d6429a0, m=m@entry=0x7f4696e26c40 , local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7fff8e66b9c0) at kernel/qobject.cpp:3648 #12 0x7f4696bd8d12 in Konsole::TabbedViewContainer::activeViewChanged (this=this@entry=0x559e9d6429a0, _t1=) at ./obj-x86_64-linux-gnu/src/konsoleprivate_autogen/EWIEGA46WW/moc_ViewContainer.cpp:272 #13 0x7f4696bc14a7 in Konsole::TabbedViewContainer::currentTabChanged (this=0x559e9d6429a0, index=3) at ./src/ViewContainer.cpp:514 #14 0x7f46935db98f in
[kate] [Bug 411493] kwrite memory usage when opening a rather big file
https://bugs.kde.org/show_bug.cgi?id=411493 --- Comment #2 from Isaac Salgueiro --- Yes, it has binary data and very long lines $ wc -L SoapUI-x64-5.5.0.sh 862 SoapUI-x64-5.5.0.sh $ file SoapUI-x64-5.5.0.sh SoapUI-x64-5.5.0.sh: POSIX shell script executable (binary data) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 411493] New: kwrite memory usage when opening a rather big file
https://bugs.kde.org/show_bug.cgi?id=411493 Bug ID: 411493 Summary: kwrite memory usage when opening a rather big file Product: kate Version: 19.08.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: isalgue...@gmail.com Target Milestone: --- SUMMARY After opening a 144MB file in kwrite and browsing its contents kwrite starts to consume 100% CPU and all the available memory. See #410129 STEPS TO REPRODUCE 1. Open a big file in kwrite 2. Press Ctrl End OBSERVED RESULT One of my CPU cores stays at 100% usage. Kwrite memory usage is very high, reaching ~8GB when I killed it. You can see KSysGuard attachements with this info in #410129 EXPECTED RESULT Browse file contents. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410129] System completly hang after opening a 144MB file with kwrite
https://bugs.kde.org/show_bug.cgi?id=410129 Isaac Salgueiro changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #12 from Isaac Salgueiro --- OK, I'm opening a new bug to kate component. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410129] System completly hang after opening a 144MB file with kwrite
https://bugs.kde.org/show_bug.cgi?id=410129 --- Comment #10 from Isaac Salgueiro --- Yep, but is not a bug this memory usage from kwrite? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410129] System completly hang after opening a 144MB file with kwrite
https://bugs.kde.org/show_bug.cgi?id=410129 --- Comment #8 from Isaac Salgueiro --- Created attachment 122442 --> https://bugs.kde.org/attachment.cgi?id=122442=edit Resources usage after killing kwrite -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410129] System completly hang after opening a 144MB file with kwrite
https://bugs.kde.org/show_bug.cgi?id=410129 --- Comment #7 from Isaac Salgueiro --- Created attachment 122441 --> https://bugs.kde.org/attachment.cgi?id=122441=edit Resources usage -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410129] System completly hang after opening a 144MB file with kwrite
https://bugs.kde.org/show_bug.cgi?id=410129 --- Comment #6 from Isaac Salgueiro --- Created attachment 122440 --> https://bugs.kde.org/attachment.cgi?id=122440=edit Resources usage -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410129] System completly hang after opening a 144MB file with kwrite
https://bugs.kde.org/show_bug.cgi?id=410129 --- Comment #5 from Isaac Salgueiro --- OK, after opening that 144MB file in kwrite and hitting 'Ctrl End' one of my CPU cores spiked to 100% usage and memory usage started to raise until I killed kwrite. I'm attaching some KSysGuard screenshots. This test was made in a fully updated Neon install with kwrite 19.08.0 Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.3 Kernel Version: 5.0.0-25-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i3-7100U CPU @ 2.40GHz Memory: 15,6 GiB -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410129] System completly hang after opening a 144MB file with kwrite
https://bugs.kde.org/show_bug.cgi?id=410129 --- Comment #3 from Isaac Salgueiro --- Don't think so, but I'll try to reproduce this while keeping an eye on free memory. Anyway, does that h0 param means that kwrite needs more than 2GB of memory for reading a 144MB file? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410129] New: System completly hang after opening a 144MB file with kwrite
https://bugs.kde.org/show_bug.cgi?id=410129 Bug ID: 410129 Summary: System completly hang after opening a 144MB file with kwrite Product: kwin Version: 5.16.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: isalgue...@gmail.com Target Milestone: --- Application: kwin_x11 (5.16.3) Qt Version: 5.12.3 Frameworks Version: 5.60.0 Operating System: Linux 4.18.0-25-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: I downloaded SoapUI installer from here https://www.soapui.org/downloads/soapui.html. It downloads a shell script, so I opened with kwrite to take a look (I tend to not execute random things from the internet without checking them first ¯\_(ツ)_/¯) without realising that ths script was so huge. Moved myself around that shell script with Av Pag and everything stoped responding, I couldn't even log in in a text mode terminal. After a restart, this kwin segfault report was here. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd5f36e8880 (LWP 2515))] Thread 5 (Thread 0x7fd5ba44d700 (LWP 2622)): #0 0x7fd5ebfb39f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fd5ef56cfb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fd5ef56cf68, cond=0x7fd5ef56cf90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fd5ef56cf90, mutex=0x7fd5ef56cf68) at pthread_cond_wait.c:655 #3 0x7fd5ef276844 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7fd5ef276889 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7fd5ebfad6db in start_thread (arg=0x7fd5ba44d700) at pthread_create.c:463 #6 0x7fd5f304888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fd5d150c700 (LWP 2617)): #0 0x7fd5f303bcf6 in __GI_ppoll (fds=fds@entry=0x7fd5c8000d28, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fd5f058fab1 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fd5c8000d28) at kernel/qcore_unix.cpp:132 #3 qt_safe_poll (fds=0x7fd5c8000d28, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:153 #4 0x7fd5f05911be in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7fd5f053503a in QEventLoop::exec (this=this@entry=0x7fd5d150bd00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7fd5f035c4ca in QThread::exec (this=) at thread/qthread.cpp:531 #7 0x7fd5ea9cb115 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fd5f035dc72 in QThreadPrivate::start (arg=0x555824097dd0) at thread/qthread_unix.cpp:361 #9 0x7fd5ebfad6db in start_thread (arg=0x7fd5d150c700) at pthread_create.c:463 #10 0x7fd5f304888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fd5d1f4e700 (LWP 2566)): [KCrash Handler] #6 QHashNode >::same_key (key0=..., h0=2494525897, this=0x50) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:158 #7 QHash >::findNode (this=this@entry=0x7fd5c4001828, akey=..., h=h@entry=2494525897) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:919 #8 0x7fd5ead6bbb2 in QHash >::findNode (ahp=, akey=..., this=0x7fd5c4001828) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:938 #9 QHash >::insert (avalue=..., akey=..., this=0x7fd5c4001828) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:774 #10 KPackage::PackageLoader::listPackages (this=0x7fd5c4001a70, packageFormat=..., packageRoot=...) at ./src/kpackage/packageloader.cpp:283 #11 0x7fd5f2b9ffdd in KWin::ScriptedEffectLoader::findAllEffects (this=) at ./effectloader.cpp:292 #12 0x7fd5f2ba7dd7 in QtConcurrent::StoredConstMemberFunctionPointerCall0, KWin::ScriptedEffectLoader>::runFunctor (this=0x5558243addc0) at /usr/include/x86_64-linux-gnu/qt5/QtConcurrent/qtconcurrentstoredfunctioncall.h:228 #13 QtConcurrent::RunFunctionTask >::run (this=0x5558243addc0) at /usr/include/x86_64-linux-gnu/qt5/QtConcurrent/qtconcurrentrunbase.h:108 #14 0x7fd5f03623e2 in QThreadPoolThread::run (this=0x5558240383b0) at thread/qthreadpool.cpp:99 #15 0x7fd5f035dc72 in QThreadPrivate::start (arg=0x5558240383b0) at thread/qthread_unix.cpp:361 #16 0x7fd5ebfad6db in start_thread (arg=0x7fd5d1f4e700) at pthread_create.c:463 #17 0x7fd5f304888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread
[calligrawords] [Bug 378424] Crash on comment on docx file
https://bugs.kde.org/show_bug.cgi?id=378424 --- Comment #8 from Isaac Salgueiro --- Created attachment 114434 --> https://bugs.kde.org/attachment.cgi?id=114434=edit Opening this document will cause calligrawords to segfault Please find test document attached. Opening this will cause calligrawords to segfault. -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 378424] Crash on comment on docx file
https://bugs.kde.org/show_bug.cgi?id=378424 --- Comment #7 from Isaac Salgueiro --- Created attachment 114431 --> https://bugs.kde.org/attachment.cgi?id=114431=edit New crash information added by DrKonqi calligrawords (3.1.0) using Qt 5.11.1 - What I was doing when the application crashed: Got this crash when trying to open a docx file. -- Backtrace (Reduced): #6 0x7fe0a63bdd38 in QTextLine::y() const () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x7fe0aa77fca4 in KoTextDocumentLayout::positionAnchorTextRanges(int, int, QTextDocument const*) () from /usr/lib/x86_64-linux-gnu/libkotextlayout.so.16 #8 0x7fe0aa761b61 in KoTextLayoutArea::layoutBlock(FrameIterator*) () from /usr/lib/x86_64-linux-gnu/libkotextlayout.so.16 #9 0x7fe0aa764d13 in KoTextLayoutArea::layout(FrameIterator*) () from /usr/lib/x86_64-linux-gnu/libkotextlayout.so.16 #10 0x7fe0aa775e06 in KoTextLayoutTableArea::layoutRow(TableIterator*, double, double) () from /usr/lib/x86_64-linux-gnu/libkotextlayout.so.16 -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 378424] Crash on comment on docx file
https://bugs.kde.org/show_bug.cgi?id=378424 Isaac Salgueiro changed: What|Removed |Added CC||isalgue...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 395341] Package 'plasma-browser-integration' is not in the repositories
https://bugs.kde.org/show_bug.cgi?id=395341 --- Comment #3 from Isaac Salgueiro --- Sorry if this is a dumb question, but I'm in 5.12 and can't find the `plasma-browser-integration` package. Is 5.12 not supported? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 395341] Package 'plasma-browser-integration' is not in the repositories
https://bugs.kde.org/show_bug.cgi?id=395341 Isaac Salgueiro changed: What|Removed |Added CC||isalgue...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 389552] New: Error opening mbox file with kmail
https://bugs.kde.org/show_bug.cgi?id=389552 Bug ID: 389552 Summary: Error opening mbox file with kmail Product: kmail2 Version: 5.6.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: isalgue...@gmail.com Target Milestone: --- Application: kmail (5.6.3) Qt Version: 5.7.1 Frameworks Version: 5.42.0 Operating System: Linux 4.13.0-16-generic x86_64 Distribution: KDE neon LTS User Edition 5.8 -- Information about the crash: - What I was doing when the application crashed: Click on mbox file in dolphin. Adding the mbox file in kmail settings didn't work either, it shows a red icon beside the mbox account without any other error message The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7268774a00 (LWP 11486))] Thread 24 (Thread 0x7f7151bd8700 (LWP 11543)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f7282fca5af in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7f7282fcabc9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7f7282fcad80 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f7282fc7747 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f728b5866ba in start_thread (arg=0x7f7151bd8700) at pthread_create.c:333 #6 0x7f729512741d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 23 (Thread 0x7f71d2f71700 (LWP 11542)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f727ec836f4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f727ec83739 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f728b5866ba in start_thread (arg=0x7f71d2f71700) at pthread_create.c:333 #4 0x7f729512741d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 22 (Thread 0x7f71d8f71700 (LWP 11530)): #0 0x7f728983da94 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f72897f923d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f72897f949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7295a3b75b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f72959e60ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7295815f64 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f729581ab48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f728b5866ba in start_thread (arg=0x7f71d8f71700) at pthread_create.c:333 #8 0x7f729512741d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 21 (Thread 0x7f71e7ffd700 (LWP 11519)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f7282fca5af in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7f7282fcabc9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7f7282fcad80 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f7282fc7747 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f728b5866ba in start_thread (arg=0x7f71e7ffd700) at pthread_create.c:333 #6 0x7f729512741d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 20 (Thread 0x7f7214ff9700 (LWP 11518)): #0 0x7f729511b74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f727a172861 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f727a163e11 in pa_mainloop_poll () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f727a1644ae in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f727a164560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f727a1727a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f7272954078 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #7 0x7f728b5866ba in start_thread (arg=0x7f7214ff9700) at pthread_create.c:333 #8 0x7f729512741d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 19 (Thread 0x7f72157fa700 (LWP 11517)): #0 __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x7f7295136b74 in ___fprintf_chk (fp=0x7f72953e6770 <_IO_stdfile_2_lock>, flag=1, format=0x7f7278dcb734 "[%s] %s\n") at fprintf_chk.c:30 #2 0x7f7278db345e in ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #3
