[ktimetracker] [Bug 484067] New: Crash after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=484067 Bug ID: 484067 Summary: Crash after unlocking screen Classification: Applications Product: ktimetracker Version: 5.0.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: aspotas...@gmail.com Reporter: g.trevi...@gmail.com Target Milestone: --- SUMMARY (On Kubuntu 22.04 fully updated) When I forget to stop the counters, lock the screen and go back after launch break, ktimetracker asks me if I want to keep counting or forget the break time (I don't remember the exact words). Whatever I select, the application crashes immediately after STEPS TO REPRODUCE 1. Start the the application select a task and start to count time 2. Wait some time then lock the screen 3. Wait a bit of time 4. Unlock the screen and click on the ktimetracker that appears OBSERVED RESULT The application crashes EXPECTED RESULT The application keeps running SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 348224] Akonadi hangs when viewing email with .ics attachment
https://bugs.kde.org/show_bug.cgi?id=348224 --- Comment #4 from Gianni --- I no longer use Akonadi, Kontact or KMail, so I'm unable to provide any new information. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 426652] Orientation option is set to 0 and causes error message in Status Message queue for CUPS
https://bugs.kde.org/show_bug.cgi?id=426652 Gianni changed: What|Removed |Added CC||a...@tiscali.it --- Comment #2 from Gianni --- Had same problem with Lexmark MC3224DWE Linux xxx-ThinkBook-15-G2-ITL 5.13.0-46-generic #51-Ubuntu SMP Sat May 21 01:39:51 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Linux version 5.13.0-46-generic (buildd@lcy02-amd64-094) (gcc (Ubuntu 11.2.0-7ubuntu2) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #51-Ubuntu SMP Sat May 21 01:39:51 UTC 2022 PRETTY_NAME="Ubuntu 21.10" NAME="Ubuntu" VERSION_ID="21.10" VERSION="21.10 (Impish Indri)" VERSION_CODENAME=impish ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=impish -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448053] New: Kwin Wayland crash (unknown reason)
https://bugs.kde.org/show_bug.cgi?id=448053 Bug ID: 448053 Summary: Kwin Wayland crash (unknown reason) Product: kwin Version: 5.23.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugs@frai.se Target Milestone: --- Created attachment 145184 --> https://bugs.kde.org/attachment.cgi?id=145184=edit coredumpctl dump SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** kwin_wayland crashes and restart after unknown reason. Coredump attached SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379506] Code coloring shifted with some characters
https://bugs.kde.org/show_bug.cgi?id=379506 --- Comment #4 from Gianni --- I've had the same issue with accents (portuguese strings). As shown in the attachments I've added, any time I have a string with ãçá I get the shift. If I substitute the ã for a the bug is gone. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379506] Code coloring shifted with some characters
https://bugs.kde.org/show_bug.cgi?id=379506 --- Comment #3 from Gianni --- Created attachment 143905 --> https://bugs.kde.org/attachment.cgi?id=143905=edit Color shift now gone if remove ã -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379506] Code coloring shifted with some characters
https://bugs.kde.org/show_bug.cgi?id=379506 --- Comment #2 from Gianni --- Created attachment 143904 --> https://bugs.kde.org/attachment.cgi?id=143904=edit Color shift due to ã -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379506] Code coloring shifted with some characters
https://bugs.kde.org/show_bug.cgi?id=379506 Gianni changed: What|Removed |Added CC||nasus.maxi...@gmail.com --- Comment #1 from Gianni --- Created attachment 143903 --> https://bugs.kde.org/attachment.cgi?id=143903=edit Color shift due to ãáç -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 391988] plasmashell crash while (apparently) writing on dolphin's console
https://bugs.kde.org/show_bug.cgi?id=391988 --- Comment #2 from Gianni --- (In reply to Nate Graham from comment #1) > Are you able to reproduce this in Plasma 5.17 or the upcoming 5.18? I am unable to reproduce this issue at all, I sent this bug via DrKonqi kind of unaware of how it worked back then. I think this bug can be safely closed, since I never experienced such crash ever again. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 404651] Text in login/lock screen gets clipped at the edges of some of the individual characters
https://bugs.kde.org/show_bug.cgi?id=404651 Gianni changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 404651] Text in login/lock screen gets clipped at the edges of some of the individual characters
https://bugs.kde.org/show_bug.cgi?id=404651 --- Comment #8 from Gianni --- Created attachment 121312 --> https://bugs.kde.org/attachment.cgi?id=121312=edit screenshot of lock screen featuring cropped outlined text in plasma 5.16 Missing outline is clearly visible at the rightmost digit '1', and slightly visible at the bottom of the letter 'g' of "luglio". It's also visible at the top of the name "Gianni". -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 404651] Text in login/lock screen gets clipped at the edges of some of the individual characters
https://bugs.kde.org/show_bug.cgi?id=404651 --- Comment #7 from Gianni --- Today I could update to plasma 5.16 on my machine and while the patch mostly fixes the issue sadly the problem is not completely gone, as the new appended image shows. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 408144] while the screen is locked user profile picture is displayed incorrectly when using software plasma renderer
https://bugs.kde.org/show_bug.cgi?id=408144 --- Comment #2 from Gianni --- (In reply to Nate Graham from comment #1) > So it works with "Auto" but not with "Software"? Exactly. Unfortunately I can't use "Auto" because that causes all sort of glitches and slowdowns (eg. https://bugs.kde.org/show_bug.cgi?id=347772) with my setup. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 408144] New: while the screen is locked user profile picture is displayed incorrectly when using software plasma renderer
https://bugs.kde.org/show_bug.cgi?id=408144 Bug ID: 408144 Summary: while the screen is locked user profile picture is displayed incorrectly when using software plasma renderer Product: kscreenlocker Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gianni_2...@hotmail.it CC: bhus...@gmail.com Target Milestone: --- Created attachment 120429 --> https://bugs.kde.org/attachment.cgi?id=120429=edit lockscreen behaviour with two user pictures using auto or software plasma renderer SUMMARY If I lock my session while Plasma Renderer is set to 'Software' the user picture is not correctly cut to fit the circle, overlapping existing decorations. I am appending an image that shows what happens using a "round" image on the first row and a "square" one on the second row; the first column shows what's displayed using Plasma Renderer set to 'Auto' while the second one shows the issue with Plasma Renderer set to 'Software'. STEPS TO REPRODUCE 1. Set Plasma Renderer to 'Software' 2. Restart the session to apply the change 3. Lock Screen OBSERVED RESULT User pictures are overlapping the existing round container and the white outline. EXPECTED RESULT User pictures should respect the page style and correctly fit inside the round container. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398317] Login and lock screen text have no shadows when using software rendering
https://bugs.kde.org/show_bug.cgi?id=398317 --- Comment #10 from Gianni --- As kindly suggested, I opened a new bug for the cropped outlined text, it's avaiable here: https://bugs.kde.org/show_bug.cgi?id=404651 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 404651] New: Outlined text in login/lock screen is oddly cropped when using software rendering
https://bugs.kde.org/show_bug.cgi?id=404651 Bug ID: 404651 Summary: Outlined text in login/lock screen is oddly cropped when using software rendering Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gianni_2...@hotmail.it CC: bhus...@gmail.com Target Milestone: --- Created attachment 118255 --> https://bugs.kde.org/attachment.cgi?id=118255=edit screenshot of lock screen featuring cropped outlined text SUMMARY This happens when using software rendering. The text seems to be cropped featuring an "incomplete outline". See attached image. STEPS TO REPRODUCE 1. Set plasma renderer to software (you may have to restart the session to make it effective) 2. Lock screen OBSERVED RESULT The text is oddly cropped. EXPECTED RESULT The text should feature a complete and clean outline. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux KDE Plasma Version: 5.15.0 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398317] Login and lock screen text have no shadows when using software rendering
https://bugs.kde.org/show_bug.cgi?id=398317 --- Comment #7 from Gianni --- Created attachment 118207 --> https://bugs.kde.org/attachment.cgi?id=118207=edit screenshot of lock screen featuring outlined text I confirm that the new patch works and provides now clearly visible outlined text. Nice job! For the sake of giving a complete feedback, I am noticing that the outline is somewhat "cropped" in certain places (eg. bottom part of "mercoledì 20 febbraio 2019"). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403314] screenlocker configuration module has poor performance if not started from system settings
https://bugs.kde.org/show_bug.cgi?id=403314 --- Comment #6 from Gianni --- I discovered something. When I resize the kcm modules from system settings (so the one that is currently redrawing the window with good responsiveness), there is a big memory leak. When I open System Settings and go to the "Workspace Theme" section (therefore I opened one of the problematic kcm modules), it occupies 47MB of ram. Then I start to resize the window continuously for 5 seconds: the systemsettings5 process now occupies 375MB of ram. It basically sky rockets the more I keep resizing. This fast leak happens on the kcm modules aforementioned. This does NOT happen when I open the kcm modules standalone (in that case it's the cpu going to 50% usage -> so 1 core to 100%, since I got 2). Although the leak I described above is by far the most aggressive, I noted that if I try to keep resizing other non affected kcm modules (both from system settings and standalone mode), or a newly opened system settings window, I still see a ram leak: a newly opened system settings window occupies around 28MB of ram, if I keep resizing it for 5 seconds it gets to 52MB of ram. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403314] screenlocker configuration module has poor performance if not started from system settings
https://bugs.kde.org/show_bug.cgi?id=403314 --- Comment #4 from Gianni --- (In reply to Nate Graham from comment #3) > 1. Is it just the screenlocker KCM that exhibits this problem, or other KCMs > too? > 2. Do you see the problem if you use Sidebar view instead of icons view for > the System Settings app itself? 1. Looking through other KCMs I can effectively confirm that at least "Look and Feel","Desktop Theme", "Cursor Theme", "Splash Screen" (all accessible from "Workspace Theme" inside system settings) and "Icons" are also affected by the same problem. 2. I do not see the problem using sidebar or tree view for the system settings. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403314] screenlocker configuration module has poor performance if not started from system settings
https://bugs.kde.org/show_bug.cgi?id=403314 --- Comment #2 from Gianni --- Forgot to add that I am using software plasma renderer. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403314] screenlocker configuration module has poor performance if not started from system settings
https://bugs.kde.org/show_bug.cgi?id=403314 Gianni changed: What|Removed |Added Summary|screenlocker configuration |screenlocker configuration |module performance issue if |module has poor performance |not started from system |if not started from system |settings|settings -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403314] screenlocker configuration module performance issue if not started from system settings
https://bugs.kde.org/show_bug.cgi?id=403314 --- Comment #1 from Gianni --- Created attachment 117513 --> https://bugs.kde.org/attachment.cgi?id=117513=edit qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403314] New: screenlocker configuration module performance issue if not started from system settings
https://bugs.kde.org/show_bug.cgi?id=403314 Bug ID: 403314 Summary: screenlocker configuration module performance issue if not started from system settings Product: systemsettings Version: 5.14.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcmshell Assignee: kdelibs-b...@kde.org Reporter: gianni_2...@hotmail.it Target Milestone: --- Created attachment 117512 --> https://bugs.kde.org/attachment.cgi?id=117512=edit Video showing difference between opening with systemsettings5 and standalone SUMMARY When I try to set a wallpaper for the lock-screen, if I access the screenlocker module from system settings I can choose an image normally, but if I start the screenlocker module "standalone" (eg. from the command line or from krunner) and select the "Aspect" tab when I try to resize it or scroll it, it shows severe ""redrawing"" problems. STEPS TO REPRODUCE 1. Open terminal and execute "kcmshell5 screenlocker" 2. Select "Aspect" tab 3. Try to resize the window or scroll through the images OBSERVED RESULT The screenlocker window doesn't redraw itself like it does when accessed from the system settings. EXPECTED RESULT The screenlocker module opened standalone should redraw itself as good as it does when opened from system settings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux KDE Plasma Version: Plasma 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION I am appending a video showing the described issue (note: the window gets updated eventually, it was just taking too long so I cut the video) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 400237] KDeveloped crash on startup
https://bugs.kde.org/show_bug.cgi?id=400237 --- Comment #1 from Gianni --- After clearing cache and reopening, KDevelop opned ok. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 400237] New: KDeveloped crash on startup
https://bugs.kde.org/show_bug.cgi?id=400237 Bug ID: 400237 Summary: KDeveloped crash on startup Product: kdevelop Version: 5.2.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: nasus.maxi...@gmail.com Target Milestone: --- Application: kdevelop (5.2.3) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.18.14-200.fc28.x86_64 x86_64 Distribution: "Fedora release 28 (Twenty Eight)" -- Information about the crash: - What I was doing when the application crashed: Just started KDevelop session and it automatically tried to open my last project, and it crashed. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f76ad4b8980 (LWP 29917))] Thread 15 (Thread 0x7f76527fc700 (LWP 29963)): #0 0x7f76c73163e9 in poll () at /lib64/libc.so.6 #1 0x7f76bd0ccbc6 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f76bd0cccf0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f76c81cb2ab in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f76c8179b7b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f76c7fe16b6 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f7661933d29 in QQuickXmlQueryEngine::run() () at /usr/lib64/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so #7 0x7f76c7feab4b in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f76c1820594 in start_thread () at /lib64/libpthread.so.0 #9 0x7f76c7320e6f in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f7652ffd700 (LWP 29954)): #0 0x7f76c182651c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f76c7feb183 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f76c4533730 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f76c453786c in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7f76c45327c1 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7f76c4535751 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7f76c7feab4b in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f76c1820594 in start_thread () at /lib64/libpthread.so.0 #8 0x7f76c7320e6f in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f76537fe700 (LWP 29953)): #0 0x7f76c182651c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f76c7feb183 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f76c4533730 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f76c453786c in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7f76c45327c1 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7f76c4535751 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7f76c7feab4b in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f76c1820594 in start_thread () at /lib64/libpthread.so.0 #8 0x7f76c7320e6f in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f7653fff700 (LWP 29952)): #0 0x7f76c182651c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f76c7feb183 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f76c4533730 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f76c453786c in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7f76c45327c1 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7f76c4535751 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7f76c7feab4b in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f76c1820594 in start_thread () at /lib64/libpthread.so.0 #8 0x7f76c7320e6f in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f7660d09700 (LWP 29951)): [KCrash Handler] #6 0x7f767302a594 in clang::Decl::setInvalidDecl(bool) () at /lib64/../lib64/libclangAST.so.6 #7 0x7f767302a5e0 in clang::Decl::setInvalidDecl(bool) () at
[akregator] [Bug 397866] akregator crashes when closing the rightmost tab
https://bugs.kde.org/show_bug.cgi?id=397866 --- Comment #5 from Gianni --- (In reply to tomas nackaerts from comment #4) > so a crash happens if you 1) close the rightmost tab and then 2) click on > the feed list. Yes, you are right. Now that I notice it, akregator crashes only when I'm clicking on a feed in the feed list (after I closed the rightmost tab). I confirm I am experiencing your same issue. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 398317] lock screen text has no shadows when using software plasma renderer
https://bugs.kde.org/show_bug.cgi?id=398317 Gianni changed: What|Removed |Added Resolution|WONTFIX |FIXED --- Comment #3 from Gianni --- (In reply to Kai Uwe Broulik from comment #2) > The shadow uses shader effects and this is not possible when using software. > This is just an emergency fallback option. In this case is it possible to provide a simpler alternative to make it readable? Maybe a border? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 398317] lock screen text has no shadows when using software plasma renderer
https://bugs.kde.org/show_bug.cgi?id=398317 --- Comment #1 from Gianni --- Created attachment 114808 --> https://bugs.kde.org/attachment.cgi?id=114808=edit Comparison of the lock screen when setting plasma renderer to opengl/automatic or software. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 398317] New: lock screen text has no shadows when using software plasma renderer
https://bugs.kde.org/show_bug.cgi?id=398317 Bug ID: 398317 Summary: lock screen text has no shadows when using software plasma renderer Product: kscreenlocker Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: breeze-theme Assignee: plasma-b...@kde.org Reporter: gianni_2...@hotmail.it CC: bhus...@gmail.com Target Milestone: --- Created attachment 114807 --> https://bugs.kde.org/attachment.cgi?id=114807=edit qdbus org.kde.KWin /KWin supportInformation If setting plasma renderer engine to "software" instead of opengl/automatic the date and time text on the lock screen page are missing the shadow. This harms the readability, especially with white-ish backgrounds. The issue happens every-time the lock screen appears when plasma renderer is set to software. sddm login page seems to never have shadows, independently from what setting is active on the "Plasma Renderer" menu. I am appending qdbus org.kde.KWin /KWin supportInformation and an image showing the automatic/opengl version and the software version of the lock screen affected portion. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 397866] akregator crashing when closing a tab
https://bugs.kde.org/show_bug.cgi?id=397866 --- Comment #2 from Gianni --- System info: KDE Plasma: 5.13.4 KDE Frameworks: 5.49.0 Qt version: 5.11.1 Akregator version: 5.9.0 The last (I hope) correction on the issue: akregator crashes every time I close the rightmost tab; akregator doesn't crash if I close any other tab that isn't the rightmost one (so it also crashes if I close the only open tab). -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 397866] akregator crashes when closing the rightmost tab
https://bugs.kde.org/show_bug.cgi?id=397866 Gianni changed: What|Removed |Added Summary|akregator crashing when |akregator crashes when |closing a tab |closing the rightmost tab -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 398030] KDevelop crashed while parsing C++17 structored binding
https://bugs.kde.org/show_bug.cgi?id=398030 Gianni changed: What|Removed |Added Summary|KDE crashed while parsing |KDevelop crashed while |C++17 structored binding|parsing C++17 structored ||binding --- Comment #1 from Gianni --- KDevelop does NOT crash with the same source code on my Gentoo machine. KDevelop 5.2.4 Frameworks 5.49.0 Qt 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 398030] KDE crashed while parsing C++17 structored binding
https://bugs.kde.org/show_bug.cgi?id=398030 Gianni changed: What|Removed |Added CC||nasus.maxi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 398030] New: KDE crashed while parsing C++17 structored binding
https://bugs.kde.org/show_bug.cgi?id=398030 Bug ID: 398030 Summary: KDE crashed while parsing C++17 structored binding Product: kdevelop Version: 5.2.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: nasus.maxi...@gmail.com Target Milestone: --- Application: kdevelop (5.2.3) Qt Version: 5.10.1 Frameworks Version: 5.48.0 Operating System: Linux 4.17.18-200.fc28.x86_64 x86_64 Distribution: "Fedora release 28 (Twenty Eight)" -- Information about the crash: - What I was doing when the application crashed: Simply opening a project that contains a header with: : auto [var1, var2] = std::make_tuple(1, "a"); - Custom settings of the application: Compiples and runs in GCC 8 with --std=c++17 The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc85b5bf940 (LWP 11443))] Thread 16 (Thread 0x7fc7f2ffd700 (LWP 11488)): #0 0x7fc8606cc918 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc866e8a736 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7fc866e87662 in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5 #3 0x7fc866e8a11d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #4 0x7fc8606c6594 in start_thread () at /lib64/libpthread.so.0 #5 0x7fc8661c70df in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7fc7f1ffb700 (LWP 11477)): [KCrash Handler] #6 0x7fc812ace634 in clang::Decl::setInvalidDecl(bool) () at /lib64/../lib64/libclangAST.so.6 #7 0x7fc812ace680 in clang::Decl::setInvalidDecl(bool) () at /lib64/../lib64/libclangAST.so.6 #8 0x7fc808095a53 in clang::ASTDeclReader::VisitDecl(clang::Decl*) () at /lib64/../lib64/../lib64/libclangSerialization.so.6 #9 0x7fc8080961b5 in clang::ASTDeclReader::VisitNamedDecl(clang::NamedDecl*) () at /lib64/../lib64/../lib64/libclangSerialization.so.6 #10 0x7fc808096685 in clang::ASTDeclReader::VisitValueDecl(clang::ValueDecl*) () at /lib64/../lib64/../lib64/libclangSerialization.so.6 #11 0x7fc8080966f9 in clang::ASTDeclReader::VisitDeclaratorDecl(clang::DeclaratorDecl*) () at /lib64/../lib64/../lib64/libclangSerialization.so.6 #12 0x7fc8080a41d0 in clang::ASTDeclReader::VisitVarDeclImpl(clang::VarDecl*) () at /lib64/../lib64/../lib64/libclangSerialization.so.6 #13 0x7fc8080a5087 in clang::ASTDeclReader::VisitDecompositionDecl(clang::DecompositionDecl*) () at /lib64/../lib64/../lib64/libclangSerialization.so.6 #14 0x7fc8080aac05 in clang::ASTDeclReader::Visit(clang::Decl*) () at /lib64/../lib64/../lib64/libclangSerialization.so.6 #15 0x7fc8080ab270 in clang::ASTReader::ReadDeclRecord(unsigned int) () at /lib64/../lib64/../lib64/libclangSerialization.so.6 #16 0x7fc80805e735 in clang::ASTReader::GetDecl(unsigned int) () at /lib64/../lib64/../lib64/libclangSerialization.so.6 #17 0x7fc8080ac941 in clang::ASTStmtReader::VisitDeclStmt(clang::DeclStmt*) () at /lib64/../lib64/../lib64/libclangSerialization.so.6 #18 0x7fc8080c043d in clang::ASTReader::ReadStmtFromStream(clang::serialization::ModuleFile&) () at /lib64/../lib64/../lib64/libclangSerialization.so.6 #19 0x7fc80802bece in clang::ASTReader::GetExternalDeclStmt(unsigned long) () at /lib64/../lib64/../lib64/libclangSerialization.so.6 #20 0x7fc812ac6533 in clang::FunctionDecl::getBody(clang::FunctionDecl const*&) const () at /lib64/../lib64/libclangAST.so.6 #21 0x7fc812ef302b in clang_getCursorDefinition () at /lib64/libclang.so.6 #22 0x7fc812ef337d in clang_isCursorDefinition () at /lib64/libclang.so.6 #23 0x7fc8131d7d46 in () at /lib64/libKDevClangPrivate.so.30 #24 0x7fc812ef42a4 in clang::cxcursor::CursorVisitor::Visit(CXCursor, bool) () at /lib64/libclang.so.6 #25 0x7fc812ef7e4d in clang::cxcursor::CursorVisitor::handleDeclForVisitation(clang::Decl const*) () at /lib64/libclang.so.6 #26 0x7fc812ef7ffb in clang::cxcursor::CursorVisitor::VisitDeclContext(clang::DeclContext*) () at /lib64/libclang.so.6 #27 0x7fc812ef40a3 in clang::cxcursor::CursorVisitor::VisitChildren(CXCursor) () at /lib64/libclang.so.6 #28 0x7fc812efd060 in clang_visitChildren () at /lib64/libclang.so.6 #29 0x7fc8131bde2c in Builder::visit(CXTranslationUnitImpl*, void*, QHash const&, bool) () at /lib64/libKDevClangPrivate.so.30 #30 0x7fc8131e4cad in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features, QHash&, ClangIndex*, std::function const&) () at /lib64/libKDevClangPrivate.so.30 #31 0x7fc8131e4510 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&,
[akregator] [Bug 397866] akregator crashing when closing a tab
https://bugs.kde.org/show_bug.cgi?id=397866 --- Comment #1 from Gianni --- I correct myself: now akregator seems to crash every time I close a tab. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 397866] akregator crashing when closing a tab
https://bugs.kde.org/show_bug.cgi?id=397866 Gianni changed: What|Removed |Added Summary|akregator crasher when |akregator crashing when |closing a tab |closing a tab -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 397866] New: akregator crasher when closing a tab
https://bugs.kde.org/show_bug.cgi?id=397866 Bug ID: 397866 Summary: akregator crasher when closing a tab Product: akregator Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: gianni_2...@hotmail.it Target Milestone: --- Created attachment 114598 --> https://bugs.kde.org/attachment.cgi?id=114598=edit gdb output with backtrace of akregator Recently I am experiencing an issue with akregator where often (1 out of 5 times, very very roughly) closing a tab causes the program to crash. By starting akregator from command line it prints a stacktrace when it crashes: Received signal 11 SEGV_ACCERR 011bdf80 #0 0x7f422eff134f #1 0x7f422da14d17 #2 0x7f422eff185e #3 0x7f423e3504b0 #4 0x011bdf80 r8: 7f41deffba40 r9: 7f41deffba50 r10: 7f41e02c838a r11: 7f41deffb930 r12: 7f41e003f5e0 r13: 7f41deffba40 r14: 019f9d60 r15: 7f41e0316a20 di: 019f9d60 si: 7f41deffba30 bp: 7f41deffbb50 bx: 7f41e0153d30 dx: 7f41e02f6c60 ax: 01794560 cx: 7f41deffba20 sp: 7f41deffb9c8 ip: 011bdf80 efl: 00010202 cgf: 002b0033 erf: 0015 trp: 000e msk: cr2: 011bdf80 [end of stack trace] Calling _exit(1). Core file will not be generated. I tried starting akregator with gdb and issuing the "bt" command when it supposedly crashed, I am appending the output as an attachment. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 378523] KFontRequester: Fonts are saved with face name preventing bold/italic to work
https://bugs.kde.org/show_bug.cgi?id=378523 Gianni changed: What|Removed |Added CC||gianni_2...@hotmail.it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388808] RubberBand has repeated large texture uploads
https://bugs.kde.org/show_bug.cgi?id=388808 --- Comment #5 from Gianni --- (In reply to David Edmundson from comment #3) > I don't want to have generic "it's sluggish" reports. As per that other > thread the hardware is struggling with GL QtQuick. I never meant to file a generic bug, but I couldn't produce a better description for what I saw. I entrusted the explanation of the problem to the appended video. I thought that if the "rubberband" was working on dolphin it ought to work the same way also on the bare desktop. I'm sorry if I caused confusion. > But in this case that hardware has highlighted a weak spot we should > optimise regardless. Glad to hear that. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 --- Comment #36 from Gianni --- (In reply to David Edmundson from comment #35) > Compositor settings affect only the window manager. GL clients will still use > GL. > This setting affects only the clients (plasmashell / systemsettings / > whatever) > There are reasons to mix and match those two. Thanks for explaining me. > In the meantime, you can export > QT_QUICK_BACKEND=software globally and confirm if that fixes it. I confirm that setting this env variable fixes the kscreenlocker_greet cpu issue for me! > >Unfortunately this setting breaks something because I can't see the themes > >preview anymore in system settings -> workspace themes. > > That was reported and fixed this week. Nice to hear! I hope to see this in the next bugfix update. In conclusion if I got this correctly the cpu issue was related to qt quick having bad performance issues (during screen lock) with outdated hardware not providing or providing an inefficient opengl backend. This is solved with setting the "plasma renderer" to "software", but this (until there's the patch you mentioned) doesnt comprehend kscreenlocker (or qtQuick?) so as a temporary workaround I also have to set QT_QUICK_BACKEND=software globally. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388808] interactions with the desktop area are sluggish
https://bugs.kde.org/show_bug.cgi?id=388808 --- Comment #2 from Gianni --- *Plasma version: 5.13.4 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 Gianni changed: What|Removed |Added Attachment #114379|0 |1 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 --- Comment #34 from Gianni --- Created attachment 114384 --> https://bugs.kde.org/attachment.cgi?id=114384=edit gdb backtrace output of kscreenlocker_greet on intel GMA950 using OpenGL 2 compositor gdb backtrace output of kscreenlocker_greet on intel GMA950 using OpenGL 2 compositor -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 Gianni changed: What|Removed |Added Attachment #114342|0 |1 is obsolete|| --- Comment #33 from Gianni --- Created attachment 114383 --> https://bugs.kde.org/attachment.cgi?id=114383=edit qdbus org.kde.KWin /KWin supportInformation on intel GMA950 with OpenGL 2 compositor qdbus org.kde.KWin /KWin supportInformation on intel GMA950 with OpenGL 2 compositor -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 --- Comment #32 from Gianni --- (In reply to David Edmundson from comment #31) > Another thing to try is typing "plasma renderer" into krunner > from there you can select "Rendering backend = software" > > Changes will apply after session restart. I would like to hear back on how > good the performance is. This is an interesting setting. The performance seems pretty good with better responsiveness and it also "solves" another bug I filed some time ago about sluggish desktop interaction #388808. Unfortunately this setting breaks something because I can't see the themes preview anymore in system settings -> workspace themes. Furthermore this doesn't solve the kscreenlocker_greet cpu issue. I don't know if this is the right place, but I'm interested in knowing what difference there is between setting XRender compositor and setting Rendering backend = software. (In reply to Christoph Feck from comment #30) > You can force OpenGL 2.1 for intel 915+ by enabling ARB_occlusion_query and > ARB_fragment_shader in drirc. Well, I didn't expect I could do that. Now I'm using OpenGL 2.1, so plasma provides more effects and seems more responsive, except for certain localized areas (like the workspace theme section, that apparently has become slower). Unfortunately, the kscreenlocker_greet issue is still present, but now that I have a capable opengl 2 graphic chip, I'm appending new qdbus and gdb debug info when using OpenGL 2 compositor. ps. These were really useful tips anyway, I apreciate that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388808] interactions with the desktop area are sluggish
https://bugs.kde.org/show_bug.cgi?id=388808 Gianni changed: What|Removed |Added Version|5.10.5 |5.13.3 Platform|Kubuntu Packages|Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388808] interactions with the desktop area are sluggish
https://bugs.kde.org/show_bug.cgi?id=388808 --- Comment #1 from Gianni --- Update: Bug is still present on Plasma version: 5.13.5 OS: KDE neon 5.13 Compositor used: XRedender/OpenGL 2.0 Graphics: Mesa DRI Intel(R) 945GM I discovered that the bug doesn't show itself if I type "plasma renderer" into krunner and select "Rendering backend = software". I'd like to add that it's not just the rectangle selection animation that is sluggish, but every interaction with the desktop, such as moving objects, selecting text in notes and so on. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388808] interactions with the desktop area are sluggish
https://bugs.kde.org/show_bug.cgi?id=388808 Gianni changed: What|Removed |Added Summary|cursor's rectangle |interactions with the |selection is sluggish on|desktop area are sluggish |the desktop area| -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 --- Comment #28 from Gianni --- Created attachment 114379 --> https://bugs.kde.org/attachment.cgi?id=114379=edit gdb backtrace output of kscreenlocker_greet on intel GMA950 I ran gdb after entering via ssh to the machine and gave the bt command. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 --- Comment #27 from Gianni --- > You are using xrender compositing. This could indicate that your OpenGL > drivers are broken. That would explain the high cpu usage. I am indeed using xrender compositing because my graphic chip (Intel GMA950) doesn't support opengl 2.x (only up to 1.4). Using xrender compositing gave me good enough performance while using plasma so far, and the bug wasn't there before 5.13 (I am unsure if the problem appeared at a certain version of 5.13, like 5.13.1 or so on). I take responsibility for not communicating sooner that the problem wasn't present in previous versions of Plasma on my machine. Since I'm not noticing abnormal performance issues other than the unreasonable cpu spikes during screen lock, I would like to encourage taking into account other possibilities. I'm currently learning how to use gdb in order to provide useful debug information as asked. I'll post the result as soon as I have had success with it. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 --- Comment #25 from Gianni --- Created attachment 114342 --> https://bugs.kde.org/attachment.cgi?id=114342=edit qdbus org.kde.KWin /KWin supportInformation macmini mid 2007 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 Gianni changed: What|Removed |Added CC||gianni_2...@hotmail.it --- Comment #24 from Gianni --- I am experiencing this bug on plasma 5.13.5 using intel integrated graphics. Whenever the screen locks kscreenlocker_greet starts eating cpu with consequent fan spin. This is very annoying and destroys the concept of energy saving. Since I'm not using nvidia graphics I doubt it's related to that specific driver, unless there is more than one bug (if someone thinks this is the case, I'll promptly file another bug). I'm appending output of "qdbus org.kde.KWin /KWin supportInformation" for my system (a mid 2007 macmini). -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 396698] New: Akregator crashes on start after plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=396698 Bug ID: 396698 Summary: Akregator crashes on start after plasma upgrade Product: akregator Version: 5.8.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: gianni_2...@hotmail.it Target Milestone: --- Application: akregator (5.8.2) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.15.15-041515-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: Akregator crashes immediately after starting it. This started happening after upgrading the system: KDE Plasma: 5.13.2 to 5.13.3 KDE Frameworks: 5.47 to 5.48.0 Qt: 5.11.0 to 5.11.1 Kernel used: 4.15.15-041515-generic The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4c46f45980 (LWP 30861))] Thread 2 (Thread 0x7f4c18907700 (LWP 30863)): #0 0x7f4c3b378c78 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f4c3b379330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4c3b37949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4c436ea0bb in QEventDispatcherGlib::processEvents (this=0x7f4c0c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f4c436915ba in QEventLoop::exec (this=this@entry=0x7f4c18906c00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f4c434c65e4 in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7f4c453b4f35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f4c434d1727 in QThreadPrivate::start (arg=0x7f4c4562dd60) at thread/qthread_unix.cpp:367 #8 0x7f4c3d2d26ba in start_thread (arg=0x7f4c18907700) at pthread_create.c:333 #9 0x7f4c42dd441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f4c46f45980 (LWP 30861)): [KCrash Handler] #6 0x7f4c43415438 in vtable for __cxxabiv1::__si_class_type_info () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #7 0x7f4c46a49d3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135 #8 0x00408327 in main (argc=1, argv=0x7fff28440798) at /workspace/build/src/main.cpp:106 The reporter indicates this bug may be a duplicate of or related to bug 392544. Possible duplicates by query: bug 396694, bug 394490, bug 392544, bug 389840, bug 386013. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391988] New: plasmashell crash while (apparently) writing on dolphin's console
https://bugs.kde.org/show_bug.cgi?id=391988 Bug ID: 391988 Summary: plasmashell crash while (apparently) writing on dolphin's console Product: plasmashell Version: 5.12.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: gianni_2...@hotmail.it CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.3) Qt Version: 5.10.0 Frameworks Version: 5.44.0 Operating System: Linux 4.13.0-37-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: Plasmashell crashed while I was writing a command on dolphin's console (I was just writing rm something, it crashed when I typed in the first letter). I dont know if it's really correlated, but I wasnt doing anything else. It's possible that I didn't have the focus on the console, in that case I would have typed the letter "r".. somewhere that plasma didn't like. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f63d36208c0 (LWP 2322))] Thread 9 (Thread 0x7f62f79b7700 (LWP 4254)): #0 0x7f63ccc9d74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f63c163f861 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f63c1630e11 in pa_mainloop_poll () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f63c16314ae in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f63c1631560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f63c163f7a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f63c08c7078 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #7 0x7f63cc2416ba in start_thread (arg=0x7f62f79b7700) at pthread_create.c:333 #8 0x7f63ccca941d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f62fce2b700 (LWP 4253)): #0 0x7ffd787d1b6d in clock_gettime () #1 0x7f63cccb7876 in __GI___clock_gettime (clock_id=clock_id@entry=1, tp=tp@entry=0x7f62fce2aa40) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f63cd5cfed1 in qt_clock_gettime (ts=0x7f62fce2aa40, clock=) at kernel/qelapsedtimer_unix.cpp:111 #3 do_gettime (frac=, sec=) at kernel/qelapsedtimer_unix.cpp:166 #4 qt_gettime () at kernel/qelapsedtimer_unix.cpp:175 #5 0x7f63cd5ce6c9 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f62f00030d0) at kernel/qtimerinfo_unix.cpp:91 #6 0x7f63cd5cec35 in QTimerInfoList::timerWait (this=0x7f62f00030d0, tm=...) at kernel/qtimerinfo_unix.cpp:388 #7 0x7f63cd5d033e in timerSourcePrepareHelper (timeout=0x7f62fce2ab14, src=) at kernel/qeventdispatcher_glib.cpp:132 #8 timerSourcePrepare (source=, timeout=0x7f62fce2ab14) at kernel/qeventdispatcher_glib.cpp:165 #9 0x7f63c78e691d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f63c78e72bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f63c78e749c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f63cd5d05cb in QEventDispatcherGlib::processEvents (this=0x7f62f8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #13 0x7f63cd57764a in QEventLoop::exec (this=this@entry=0x7f62fce2ace0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #14 0x7f63cd397554 in QThread::exec (this=this@entry=0x63dd920) at thread/qthread.cpp:522 #15 0x7f63d0508a35 in QQmlThreadPrivate::run (this=0x63dd920) at qml/ftw/qqmlthread.cpp:147 #16 0x7f63cd39c6eb in QThreadPrivate::start (arg=0x63dd920) at thread/qthread_unix.cpp:376 #17 0x7f63cc2416ba in start_thread (arg=0x7f62fce2b700) at pthread_create.c:333 #18 0x7f63ccca941d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f62fe6c7700 (LWP 4157)): #0 0x7ffd787d1b6d in clock_gettime () #1 0x7f63cccb7876 in __GI___clock_gettime (clock_id=clock_id@entry=1, tp=tp@entry=0x7f62fe6c6a40) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f63cd5cfed1 in qt_clock_gettime (ts=0x7f62fe6c6a40, clock=) at kernel/qelapsedtimer_unix.cpp:111 #3 do_gettime (frac=, sec=) at kernel/qelapsedtimer_unix.cpp:166 #4 qt_gettime () at kernel/qelapsedtimer_unix.cpp:175 #5 0x7f63cd5ce6c9 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f62f8002cd0) at kernel/qtimerinfo_unix.cpp:91 #6 0x7f63cd5cec35 in QTimerInfoList::timerWait (this=0x7f62f8002cd0, tm=...) at kernel/qtimerinfo_unix.cpp:388 #7 0x7f63cd5d033e in timerSourcePrepareHelper (timeout=0x7f62fe6c6b14, src=) at kernel/qeventdispatcher_glib.cpp:132 #8 timerSourcePrepare (source=, timeout=0x7f62fe6c6b14) at
[akregator] [Bug 389945] New: Akregator segmentation fault on startup
https://bugs.kde.org/show_bug.cgi?id=389945 Bug ID: 389945 Summary: Akregator segmentation fault on startup Product: akregator Version: 5.7.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: gianni_2...@hotmail.it Target Milestone: --- Application: akregator (5.7.1) Qt Version: 5.9.3 Frameworks Version: 5.42.0 Operating System: Linux 4.13.0-32-generic x86_64 Distribution: KDE neon User Edition 5.11 -- Information about the crash: I launched akregator using krunner but it crashed before showing anything. I was browsing with firefox when it happened. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa9ea918980 (LWP 20049))] Thread 22 (Thread 0x7fa965860700 (LWP 20113)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fa9d3750d04 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7fa9d3750d49 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7fa9e0b566ba in start_thread (arg=0x7fa965860700) at pthread_create.c:333 #4 0x7fa9e682f41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 21 (Thread 0x7fa975ffb700 (LWP 20108)): #0 0x7fa9e682374d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa9dede338c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa9dede349c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa9e714a6cb in QEventDispatcherGlib::processEvents (this=0x7fa994001bd0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fa9e70f2e2a in QEventLoop::exec (this=this@entry=0x7fa975ffac40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fa9e6f1b8f4 in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7fa9e6f20709 in QThreadPrivate::start (arg=0x1235b90) at thread/qthread_unix.cpp:368 #7 0x7fa9e0b566ba in start_thread (arg=0x7fa975ffb700) at pthread_create.c:333 #8 0x7fa9e682f41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 20 (Thread 0x7fa9767fc700 (LWP 20106)): #0 __memcpy_sse2 () at ../sysdeps/x86_64/multiarch/../memcpy.S:116 #1 0x7fa9e6757cb3 in __dcigettext (domainname=0x7fa9e68b4bc0 <_libc_intl_domainname> "libc", msgid1=0x7fa9e68b502c "Bad file descriptor", msgid2=msgid2@entry=0x0, plural=plural@entry=0, n=n@entry=0, category=category@entry=5) at dcigettext.c:553 #2 0x7fa9e675662f in __GI___dcgettext (domainname=, msgid=, category=category@entry=5) at dcgettext.c:47 #3 0x7fa9e67b35ec in __GI___strerror_r (errnum=errnum@entry=9, buf=buf@entry=0x0, buflen=buflen@entry=0) at _strerror.c:71 #4 0x7fa9e67b351f in strerror (errnum=9) at strerror.c:31 #5 0x7fa9cb228641 in event_warn () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #6 0x7fa9cb22cc38 in ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #7 0x7fa9cb216e2d in event_base_loop () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #8 0x7fa9d6fb68fe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fa9d6fb23b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fa9d6fceeea in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #11 0x7fa9d6fe6d86 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #12 0x7fa9d6fe2f2d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #13 0x7fa9e0b566ba in start_thread (arg=0x7fa9767fc700) at pthread_create.c:333 #14 0x7fa9e682f41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 19 (Thread 0x7fa976ffd700 (LWP 20105)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fa9d6fdb1e5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7fa9d6fdb294 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7fa9d6fb636d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fa9d6fb23b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fa9d6fceeea in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fa9d6fe6d86 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fa9d6fe2f2d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fa9e0b566ba in start_thread (arg=0x7fa976ffd700) at pthread_create.c:333 #9 0x7fa9e682f41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 18 (Thread 0x7fa9777fe700 (LWP 20104)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at
[plasmashell] [Bug 388808] New: cursor's rectangle selection is sluggish on the desktop area
https://bugs.kde.org/show_bug.cgi?id=388808 Bug ID: 388808 Summary: cursor's rectangle selection is sluggish on the desktop area Product: plasmashell Version: 5.10.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: gianni_2...@hotmail.it CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 109795 --> https://bugs.kde.org/attachment.cgi?id=109795=edit sluggish animation of rectangle selection on the desktop Plasma version: 5.10.5 OS: Kubuntu 17.10 Compositor used: XRender Graphics: Mesa DRI Intel(R) 945GM When I draw a selection rectangle on the desktop with the cursor, the draw animation is slow/sluggish, while it should be fluid. Drawing a selection rectangle on other places, such as a dolphin window, shows the correct behaviour and the animation is fluid. I'm attaching a video showing the animation first on the desktop and then on a dolphin window, so to highlight the difference. In the video it's less apparent than what it really is but it should still give an idea. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 380128] systemsettings5 window freezes when trying to open "Workspace Theme"
https://bugs.kde.org/show_bug.cgi?id=380128 Gianni <gianni_2...@hotmail.it> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Gianni <gianni_2...@hotmail.it> --- Issue doesn't show itself in KDE Neon LTS 5.8 with uname -a: Linux gianni-MacBook 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 382387] New: NetworkManager crashed when setting VPNs
https://bugs.kde.org/show_bug.cgi?id=382387 Bug ID: 382387 Summary: NetworkManager crashed when setting VPNs Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: nasus.maxi...@gmail.com Target Milestone: --- Application: kcmshell5 (5.10.1) Qt Version: 5.7.1 Frameworks Version: 5.35.0 Operating System: Linux 4.11.8-300.fc26.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I added a few (4-6) VPN by importing .ovpn files and not setting any config. -- Backtrace: Application: System Settings Module (kcmshell5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f12847888c0 (LWP 2382))] Thread 2 (Thread 0x7f1270deb700 (LWP 2384)): #0 0x7f1289413ab4 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #1 0x7f128941449b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f128941467c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f12905a1d0b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f1290551b8a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f12903a6efa in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f12930a0709 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x7f12903ab1ee in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f128db3a36d in start_thread () from /lib64/libpthread.so.0 #9 0x7f128f792b8f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f12847888c0 (LWP 2382)): [KCrash Handler] #6 0x5623b0378c00 in ?? () #7 0x7f12780b5f06 in NotifyByAudio::~NotifyByAudio() () from /lib64/libKF5Notifications.so.5 #8 0x7f12780b5fa9 in NotifyByAudio::~NotifyByAudio() () from /lib64/libKF5Notifications.so.5 #9 0x7f1290580a88 in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #10 0x7f1290581962 in QObject::~QObject() () from /lib64/libQt5Core.so.5 #11 0x7f1278090259 in (anonymous namespace)::Q_QGS_s_self::innerFunction()::Holder::~Holder() () from /lib64/libKF5Notifications.so.5 #12 0x7f128f6bcc38 in __run_exit_handlers () from /lib64/libc.so.6 #13 0x7f128f6bcc8a in exit () from /lib64/libc.so.6 #14 0x7f128f6a24e1 in __libc_start_main () from /lib64/libc.so.6 #15 0x5623ab2a88ca in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 382343] New: KDevelop crashes when trying to build a manually added dependency in run configuration.
https://bugs.kde.org/show_bug.cgi?id=382343 Bug ID: 382343 Summary: KDevelop crashes when trying to build a manually added dependency in run configuration. Product: kdevelop Version: 5.1.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: nasus.maxi...@gmail.com Target Milestone: --- Application: kdevelop (5.1.1) Qt Version: 5.7.1 Frameworks Version: 5.34.0 Operating System: Linux 4.11.8-200.fc25.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: - What I was doing when the application crashed: Started debug launch. Kdevelop show the message for building the dependency with "terminated" imediatly after. Trying to restart the process then causes the crash. The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb9e0fab640 (LWP 19542))] Thread 12 (Thread 0x7fb99d18f700 (LWP 19780)): #0 0x7fb9f3042460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb9fac4704a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7fb9f727b880 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7fb9f727fa38 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7fb9f727a9fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7fb9f727d8c9 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7fb9fac469ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7fb9f303c73a in start_thread () at /lib64/libpthread.so.0 #8 0x7fb9fa039e0f in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7fb99d990700 (LWP 19779)): #0 0x7fb9f3042460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb9fac4704a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7fb9f727b880 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7fb9f727fa38 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7fb9f727a9fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7fb9f727d8c9 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7fb9fac469ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7fb9f303c73a in start_thread () at /lib64/libpthread.so.0 #8 0x7fb9fa039e0f in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7fb99e191700 (LWP 19778)): #0 0x7fb9f3042460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb9fac4704a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7fb9f727b880 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7fb9f727fa38 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7fb9f727a9fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7fb9f727fa92 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7fb9f727a9fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #7 0x7fb9f727d8c9 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #8 0x7fb9fac469ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7fb9f303c73a in start_thread () at /lib64/libpthread.so.0 #10 0x7fb9fa039e0f in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fb99e992700 (LWP 19777)): #0 0x7fb9f3042460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb9fac4704a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7fb9f727b880 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7fb9f727fa38 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7fb9f727a9fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
[systemsettings] [Bug 380128] systemsettings5 window freezes when trying to open "Workspace Theme"
https://bugs.kde.org/show_bug.cgi?id=380128 --- Comment #1 from Gianni <gianni_2...@hotmail.it> --- I am using KDE Neon. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 380128] New: systemsettings5 window freezes when trying to open "Workspace Theme"
https://bugs.kde.org/show_bug.cgi?id=380128 Bug ID: 380128 Summary: systemsettings5 window freezes when trying to open "Workspace Theme" Product: systemsettings Version: 5.8.6 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gianni_2...@hotmail.it Target Milestone: --- When opening kde system settings and clicking on "Workspace Theme", the window somewhat freezes. "Freezes" is a bit inappropriate because it's more like it can't draw the content inside it (the content that should belong to the "Workspace Theme" section). Even if it can't draw that "Workspace Theme" part, it still gets mouse clicks and I am able to return to the main menu. This issue only shows with the xserver-xorg-video-intel video driver, while it doesn't show with the modesetting driver. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 376193] New: Konsole crashed when closing a Tab
https://bugs.kde.org/show_bug.cgi?id=376193 Bug ID: 376193 Summary: Konsole crashed when closing a Tab Product: konsole Version: 16.08.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: nasus.maxi...@gmail.com Target Milestone: --- Application: konsole (16.08.3) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.7.7-200.fc24.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: - What I was doing when the application crashed: I was closing a tab. - Also, I could not select a bug as duplicate of this one using "Crash Reporting Assistant" -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8001b62940 (LWP 5179))] Thread 3 (Thread 0x7f7ff5707700 (LWP 5313)): #0 0x7f800f17501d in poll () at /lib64/libc.so.6 #1 0x7f800863a156 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f800863a26c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f800ff7b73b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f800ff2c73a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f800fd895f3 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f801503d739 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7f800fd8d9da in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f800db406ca in start_thread () at /lib64/libpthread.so.0 #9 0x7f800f180f7f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f7ff7061700 (LWP 5306)): #0 0x7f800f17501d in poll () at /lib64/libc.so.6 #1 0x7f800cc25d10 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f800cc27aa9 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f7ffaed1d69 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f800fd8d9da in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f800db406ca in start_thread () at /lib64/libpthread.so.0 #6 0x7f800f180f7f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f8001b62940 (LWP 5179)): [KCrash Handler] #6 0x7f80109fcb8f in QActionPrivate::~QActionPrivate() () at /lib64/libQt5Widgets.so.5 #7 0x7f80109fcd39 in QActionPrivate::~QActionPrivate() () at /lib64/libQt5Widgets.so.5 #8 0x7f800ff5c3a7 in QObject::~QObject() () at /lib64/libQt5Core.so.5 #9 0x7f80109fb3f9 in QAction::~QAction() () at /lib64/libQt5Widgets.so.5 #10 0x7f80109fb429 in QAction::~QAction() () at /lib64/libQt5Widgets.so.5 #11 0x7f800ff5b25c in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #12 0x7f800ff5c35f in QObject::~QObject() () at /lib64/libQt5Core.so.5 #13 0x7f80140a3015 in KActionCollection::~KActionCollection() () at /lib64/libKF5XmlGui.so.5 #14 0x7f80140a3099 in KActionCollection::~KActionCollection() () at /lib64/libKF5XmlGui.so.5 #15 0x7f80140f2468 in KXMLGUIClient::~KXMLGUIClient() () at /lib64/libKF5XmlGui.so.5 #16 0x7f8014aa2ae1 in Konsole::SessionController::~SessionController() () at /lib64/libkonsoleprivate.so.16 #17 0x7f8014aa2b29 in Konsole::SessionController::~SessionController() () at /lib64/libkonsoleprivate.so.16 #18 0x7f800ff558b0 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #19 0x7f8010a01ecc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #20 0x7f8010a09671 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #21 0x7f800ff2d7aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #22 0x7f800ff2fe90 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #23 0x7f800ff7b6a3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #24 0x7f8008639e42 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #25 0x7f800863a1c0 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #26 0x7f800863a26c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #27 0x7f800ff7b71f in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #28 0x7f800ff2c73a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #29 0x7f800ff3423c in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #30 0x7f8014d54973 in kdemain () at /lib64/libkdeinit5_konsole.so #31 0x7f800f099401 in __libc_start_main () at /lib64/libc.so.6 #32 0x56432b198a8a in _start () Possible duplicates by query: bug 371624, bug 370971. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug
[kdevelop] [Bug 349877] CMake doesn't select proper generator after prune.
https://bugs.kde.org/show_bug.cgi?id=349877 --- Comment #4 from Gianni <nasus.maxi...@gmail.com> --- So. Almost 2 years. Any chance of merging this? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 360812] CMake fails to Locate poppler-qt4
https://bugs.kde.org/show_bug.cgi?id=360812 --- Comment #1 from Gianni <nasus.maxi...@gmail.com> --- Created attachment 98005 --> https://bugs.kde.org/attachment.cgi?id=98005=edit patch that fixes the syntax issue. -- You are receiving this mail because: You are watching all bug changes.
