[kile] [Bug 488410] New: Conflicting options on Build Tools menu
https://bugs.kde.org/show_bug.cgi?id=488410 Bug ID: 488410 Summary: Conflicting options on Build Tools menu Classification: Applications Product: kile Version: 2.9.93 Platform: Kubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: user interface Assignee: michel.lud...@gmail.com Reporter: matiaslapo...@gmail.com Target Milestone: --- SUMMARY Hello, I am having several problems trying to define custom build tools. It's not entirely clear when/how the different settings are being stored, sometimes there aren't even any changes at all. In particular, I was trying to move all the temporary files derived from a compilation into a subdirectory to avoid cluttering the root folder. This has proven to be a complication with the BibTex tool, which I couldn't make it work for this particular case. Here are some of the problems I have found. STEPS TO REPRODUCE / OBSERVED RESULT * One of the bugs is that whenever a setting has been defined (e.g., those in Advanced -> "Source extension", "Target extension", "Target file", "Relative dir"), they cannot be emptied once again. If one erases the option, presses "OK", and goes back to the Configuration menu, the pre-erasure settings appear once again. This proves to be a problem when creating a configuration for an already-existing tool: as the configuration is cloned from the currently active one, some fields already have some pre-stored values and thus cannot be cleared. * Adding a "Relative dir" does not work, kile still tries to search for the .aux file in the root folder. I have to manually add the folder as an option to the command. * When a "Source extension" is defined it overrides the other options. i.e., if I try to set "aux" as the source, then the relative directory I added in the previous step stops working. * Changing a Tool's Configuration Advanced->Type (e.g., to execute from Konsole, as I wanted to debug what wasn't working) didn't work neither when modifying an existing configuration (or modifying one just created from an existing tool, which copies the options from the currently active configuration). * The tool is not added to the build menu until one access the "Menu" tab. I understand if this is a choice, i.e., do not create the tool until the user (inadvertently) requests for it, but then I don't understand why it wouldn't be possible to remove the tool from the menu. Furthermore, changing the tool's icon does not take effect until restarting the application. EXPECTED RESULT In the end, the only way I could achieve my intended use was to create a new duplicated tool of a "custom" class (so as to not grab any bibtex defaults), making sure I did not accidently set any of the conflicting fields, i.e., immediately creating a configuration without "source extension", that opens in Konsole, and has the relative dir set as an option of the tool. But this also means that in order to have the full pipeline (i.e., compiling a main.tex, then compiling the bibliography, recompiling the main.tex and then having the preview of the PDF) working with an output dir, I would need to create duplicated tools for each step (ViewPDF, e.g.: "relative dir" does not work, it already has a "source extension", and there's no way to manually set a relative dir). I think the current functionality doesn't reflect what one would expect from the current interface. I didn't notice if this happened with other tools (i.e., I didn't notice this problem happening with pdflatex because I used the `-output-dir=folder` option for the command, so I didn't notice that "Relative dir" wouldn't be actually working, and there was no "Source extension" overriding the other options neither). I know this report is a bit all over the place and I am happy to provide any additional details, but I am not sure how to debug this further, i.e. I wasn't able to find any verbose mode nor logs for Kile, and I couldn't access the documentation linked on the project's page (https://docs.kde.org/trunk5/en/kile/kile/index.html), therefore being more restricted on my description was difficult (i.e., I can only report "end-user" stuff directly). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 23.10 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481288] Gdrive invalid protocol after create a Google account to access Google Drive
https://bugs.kde.org/show_bug.cgi?id=481288 Matias Barletta changed: What|Removed |Added CC||m...@lionix.com --- Comment #9 from Matias Barletta --- How can I provide more info? I have the same issue with a fresh KDE neon install. `Invalid field selection` error in dolphin. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483137] Screencast plugin fails if PipeWire is started after KWin
https://bugs.kde.org/show_bug.cgi?id=483137 Matias Barletta changed: What|Removed |Added CC||m...@lionix.com -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 466164] kmenueditor crashes after saving and reediting the item.
https://bugs.kde.org/show_bug.cgi?id=466164 --- Comment #3 from Matias Barletta --- Created attachment 157028 --> https://bugs.kde.org/attachment.cgi?id=157028=edit New crash information added by DrKonqi kmenuedit (5.27.2) using Qt 5.15.8 Editing Menu, selecting the offending menu item, then crash -- Backtrace (Reduced): #4 0x7f1d1c0c4324 in QWidgetLineControl::internalSetText(QString const&, int, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #9 0x7f1d1c268b32 in QTreeWidget::currentItemChanged(QTreeWidgetItem*, QTreeWidgetItem*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #11 0x7f1d1b2656c7 in QItemSelectionModel::currentChanged(QModelIndex const&, QModelIndex const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f1d1b26917d in QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f1d1c1eb14e in QAbstractItemView::mousePressEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 466164] kmenueditor crashes after saving and reediting the item.
https://bugs.kde.org/show_bug.cgi?id=466164 --- Comment #2 from Matias Barletta --- Created attachment 156933 --> https://bugs.kde.org/attachment.cgi?id=156933=edit New crash information added by DrKonqi kmenuedit (5.27.2) using Qt 5.15.8 Just editing a Favorite menu (dbeaver) causes the crash. -- Backtrace (Reduced): #4 0x7fe06e0c4324 in QWidgetLineControl::internalSetText(QString const&, int, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #9 0x7fe06e268b32 in QTreeWidget::currentItemChanged(QTreeWidgetItem*, QTreeWidgetItem*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #11 0x7fe06d2656c7 in QItemSelectionModel::currentChanged(QModelIndex const&, QModelIndex const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fe06d26917d in QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fe06e1eb14e in QAbstractItemView::mousePressEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 466164] kmenueditor crashes after saving and reediting the item.
https://bugs.kde.org/show_bug.cgi?id=466164 Matias Barletta changed: What|Removed |Added CC||m...@lionix.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413203] Some notifications don't disappear after timeout
https://bugs.kde.org/show_bug.cgi?id=413203 Matias Barletta changed: What|Removed |Added Version|5.17.0 |5.25.4 Platform|Archlinux Packages |Neon Packages CC||m...@lionix.com --- Comment #9 from Matias Barletta --- I have this issue in KDE Neon fully updated. Doing kdialog with --passivepopup holi 3 has the issue, as well as brave/chrome notifications. Restarting the system solves the issue till... till something happens and breaks. Sorry I can't give more details on the conditions for this to happen, I have this issue for more than a year, sometimes it disappears, then is back. It happens with Xorg using intel or nvidia (as default, not prime) Can I do something to shed more light on this @Kai Uwe Broulik ? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 441907] Yakuake always opens on the left screen in case of display scaling
https://bugs.kde.org/show_bug.cgi?id=441907 Matias Barletta changed: What|Removed |Added CC||m...@lionix.com --- Comment #3 from Matias Barletta --- Same thing here, using X11 and scaling 175 and 100 in the second monitor. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 449552] New: CUPS and DBus crashes
https://bugs.kde.org/show_bug.cgi?id=449552 Bug ID: 449552 Summary: CUPS and DBus crashes Product: okular Version: 21.08.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: matiaslapo...@gmail.com Target Milestone: --- Application: okular (21.08.1) Qt Version: 5.15.2 Frameworks Version: 5.86.0 Operating System: Linux 5.13.0-27-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: Ubuntu 21.10 -- Information about the crash: - What I was doing when the application crashed: I am having problems with the printers on my computer, where it crashes when trying to do something related with them. e.g.: * libreoffice crashes on startup, I have to disable cups previously every time * when trying to open the "Print" dialog on Okular, I also get a crash. * `lpstat -p -d` crashes with the following error: "dbus[794440]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file ../../../dbus/dbus-message.c line 2760. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace [1]794440 IOT instruction (core dumped) lpstat -p -d" This is the same type of crash info that I get from okular and libreoffice. The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139952731393600) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139952731393600) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=139952731393600, signo=signo@entry=6) at pthread_kill.c:91 #7 0x7f494caaa476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f494ca907b7 in __GI_abort () at abort.c:79 #9 0x7f494bf52ed6 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #10 0x7f494bf79620 in _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #11 0x7f494bf688af in dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #12 0x7f494bf69d86 in dbus_message_append_args_valist () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #13 0x7f494bf69fdd in dbus_message_append_args () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #14 0x7f493c08c23a in avahi_record_browser_new () from /lib/x86_64-linux-gnu/libavahi-client.so.3 #15 0x7f4930452d41 in ?? () from /lib/x86_64-linux-gnu/libcups.so.2 #16 0x7f4930402591 in cupsGetDests2 () from /lib/x86_64-linux-gnu/libcups.so.2 #17 0x7f493c37e235 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/printsupport/libcupsprintersupport.so #18 0x7f493c37e3d2 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/printsupport/libcupsprintersupport.so #19 0x7f494c3478e7 in QPrinterInfo::defaultPrinter() () from /lib/x86_64-linux-gnu/libQt5PrintSupport.so.5 #20 0x7f494c342b1d in QPrinterPrivate::findValidPrinter(QPrinterInfo const&) () from /lib/x86_64-linux-gnu/libQt5PrintSupport.so.5 #21 0x7f494c344c16 in QPrinterPrivate::initEngines(QPrinter::OutputFormat, QPrinterInfo const&) () from /lib/x86_64-linux-gnu/libQt5PrintSupport.so.5 #22 0x7f494c345042 in QPrinter::QPrinter(QPrinter::PrinterMode) () from /lib/x86_64-linux-gnu/libQt5PrintSupport.so.5 #23 0x7f4945622e67 in Okular::Part::slotPrint() () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #24 0x7f494d16958b in QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f494d16e456 in QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x55bba36a2492 in ?? () #27 0x7f494d195a88 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f494dcd7b86 in QAction::triggered(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x7f494dcda89c in QAction::activate(QAction::ActionEvent) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7f494dcdb487 in QAction::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7f494dcde6b3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x7f494d15e16a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from
[kwin] [Bug 350645] Huge icons in Task Switcher
https://bugs.kde.org/show_bug.cgi?id=350645 Matias L changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #9 from Matias L --- To the best of my knowledge, it doesn't happen anymore :) (honestly, I have migrated from that setup long ago). -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 423970] Urgency options for notifications (do not disturb mode)
https://bugs.kde.org/show_bug.cgi?id=423970 --- Comment #2 from Matias L --- (In reply to Nicolas Fella from comment #1) > Just curious: Any particular reason you are using kdialog for this at all > instead of just notify-send? Not really, in fact because of this I am actually using notify-send. KDialog seems more complete, and already comes preinstalled, whilst I had to install notify-send. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 423970] New: Urgency options for notifications (do not disturb mode)
https://bugs.kde.org/show_bug.cgi?id=423970 Bug ID: 423970 Summary: Urgency options for notifications (do not disturb mode) Product: kdialog Version: 20.04 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: br...@frogmouth.net Reporter: matiaslapo...@gmail.com Target Milestone: --- SUMMARY With the new "Do not disturb" mode, passive popups made by knotify have no way to bypass it. The notify-send tool, of the libnotify-bin package, provides a "Urgency" parameter that, set to critical, makes the passive notification appear even when in do not disturb mode. I though it would be useful to have this functionality also for kdialog. STEPS TO REPRODUCE 1. Set KDE's Notifications to "Do not disturb" 2. Send a passive popup OBSERVED RESULT No notification appears. EXPECTED RESULT Shown notification provided it is labeled as critical urgency. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KUbuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68 Qt Version: 5.12.8 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372340] Tagged face areas on portait (vertical) oriented images are mispositioned
https://bugs.kde.org/show_bug.cgi?id=372340 Matias changed: What|Removed |Added CC||k...@matiascuenca.com.ar --- Comment #10 from Matias --- I just want to report that this problem still exists (5.9.0 win) and how to get around it. The problem seem to be that Picasa always writes the faces areas with respect to the physical orientation without accounting for the EXIF orientation tag. What I did in order to import my Picasa collection into DigiKam was 1- Configure DigiKam to read face tags and do not rotate based on EXIF orientation 2- Added the Picasa tagged directories to the DB (all the face metadata was already embedded on the XMP tags and not on the picasa.ini) 3- Create a couple of searches in DigiKam to filter landscape pictures that had a rotated left or rotated right EXIF tag. 4- On those pictures I did a "Adjust EXIF orientation tag to NORMAL" 5- I manual rotated the picture (in batch). The key to this solution is this last step where DigiKam not only rotates the image but it also rotates the areas for the faces. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 373854] New: My solution: umbrello there was a problem saving, in Ubuntu 16.04
https://bugs.kde.org/show_bug.cgi?id=373854 Bug ID: 373854 Summary: My solution: umbrello there was a problem saving, in Ubuntu 16.04 Product: umbrello Version: 2.18.3 (KDE Applications 15.12.3) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: matiaswv...@gmail.com Target Milestone: --- I solved it this way. sudo apt-get install kinit sudo apt-get install kio and the error disappeared. Bye. Matias W. Vera -- You are receiving this mail because: You are watching all bug changes.
[kscreensaver] [Bug 316348] kscreenlocker_greet constantly consumes around 20% CPU time
https://bugs.kde.org/show_bug.cgi?id=316348 --- Comment #36 from Matias Barletta <m...@lionix.com> --- @david.sainty I have felt your pain, even with desktops effects working properly on opengl 3.1, kscreenlocker was eating my cpu ALL the time. I upgraded to the latest KDE Neon User Edition - problem is gone .. drastic measure, but works -- You are receiving this mail because: You are watching all bug changes.
[kscreensaver] [Bug 316348] kscreenlocker_greet constantly consumes around 20% CPU time
https://bugs.kde.org/show_bug.cgi?id=316348 --- Comment #31 from Matias Barletta <m...@lionix.com> --- This is a more complete bt Thread 9 (Thread 0x7f8678664700 (LWP 21290)): #0 0x7f8689b5e88d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f868984bbd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f868984d74f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f867a38a779 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f868a254a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f868520a6aa in start_thread (arg=0x7f8678664700) at pthread_create.c:333 #6 0x7f8689b69e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f8676ff5700 (LWP 21291)): #0 0x7f8689b5e88d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f86830ee1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f86830ee2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f868a48c4ef in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f868a43350a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f868a24fac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f868a254a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f868520a6aa in start_thread (arg=0x7f8676ff5700) at pthread_create.c:333 #8 0x7f8689b69e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f8674d11700 (LWP 21292)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f86761babf3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7f86761baa57 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7f868520a6aa in start_thread (arg=0x7f8674d11700) at pthread_create.c:333 #4 0x7f8689b69e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f866dc0e700 (LWP 21293)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f86761babf3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7f86761baa57 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7f868520a6aa in start_thread (arg=0x7f866dc0e700) at pthread_create.c:333 #4 0x7f8689b69e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f866d40d700 (LWP 21294)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f86761babf3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7f86761baa57 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7f868520a6aa in start_thread (arg=0x7f866d40d700) at pthread_create.c:333 #4 0x7f8689b69e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f866cc0c700 (LWP 21295)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f86761babf3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7f86761baa57 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ---Type to continue, or q to quit--- #3 0x7f868520a6aa in start_thread (arg=0x7f866cc0c700) at pthread_create.c:333 #4 0x7f8689b69e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f8667fff700 (LWP 21296)): #0 0x7f8689b5e88d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f86830ee1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f86830ee2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f868a48c4ef in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f868a43350a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f868a24fac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f868ba0ec35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f868a254a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f868520a6aa in start_thread (arg=0x7f8667fff700) at pthread_create.c:333 #9 0x7f8689b69e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f865700 (LWP 21299)): #0 0x7f8689b5e88d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f86830ee1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f86830ee2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f868a48c50b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f868a43350a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Cor
[kscreensaver] [Bug 316348] kscreenlocker_greet constantly consumes around 20% CPU time
https://bugs.kde.org/show_bug.cgi?id=316348 Matias Barletta <m...@lionix.com> changed: What|Removed |Added CC||m...@lionix.com --- Comment #25 from Matias Barletta <m...@lionix.com> --- (In reply to Martin Gräßlin from comment #23) > > Those experiencing the problem need to help us: please gdb into the process > and get a backtrace, so that we can see where it consumes the CPU. This id a gdb bt on kubuntu 15.10 (kernel 4.5) and plasma 4:5.5.4-0ubuntu1~ubuntu15.10~ppa1 #0 0x7f8689b5e88d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f86830ee1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f86830ee2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f868a48c4ef in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f868a43350a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f868a43b5ec in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x0040ae87 in main () -- You are receiving this mail because: You are watching all bug changes.
