[krita] [Bug 416716] Some dialogs are created off screen
https://bugs.kde.org/show_bug.cgi?id=416716 --- Comment #5 from eleanorh...@outlook.com --- (In reply to vanyossi from comment #4) > Do you happen to know the Qt version you have installed? Arch repos tend to > have recent versions of software. Since we have no control of where the > Windows will be placed, that is decided by the window manager, Im inclined > to think you have a Qt version >=5.13 which are known to be buggy. For krita > we stick with 5.12.4 for the moment. > > I will mark as not a bug. I mentioned this behavior occurs with the Krita Appimage, which is linked against Qt 5.12.5 $ ./krita-4.2.8-x86_64.appimage --appimage-extract $ strings squashfs-root/usr/lib/libQt5Core.so.5 | grep "QtCore library version" This is the QtCore library version Qt 5.12.5 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.5.0 20171010) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 417099] Discover froze and crashed a few seconds later
https://bugs.kde.org/show_bug.cgi?id=417099 annu...@yahoo.com changed: What|Removed |Added CC||annu...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 319386] Feature Request: Allow Syncing with TTRSS (Tiny Tiny RSS) / Liferea functionality
https://bugs.kde.org/show_bug.cgi?id=319386 an...@andwil.de changed: What|Removed |Added CC||an...@andwil.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415867] Face recognition -> after manual tagging -> no detection
https://bugs.kde.org/show_bug.cgi?id=415867 --- Comment #5 from Maik Qualmann --- Training database rebuilt in the maintenance tool? Maik -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417127] New: Search "also index content" option doesn't update baloofilerc config
https://bugs.kde.org/show_bug.cgi?id=417127 Bug ID: 417127 Summary: Search "also index content" option doesn't update baloofilerc config Product: systemsettings Version: 5.17.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tagwer...@innerjoin.org Target Milestone: --- SUMMARY: The System "Search" settings gives an option to index file content or not. This does not seem to have an effect STEPS TO REPRODUCE: 1. Open System Settings, scroll down to Workspace and click on Search, this gives options to "Enable File Search" and "Also index file content" (both these are checked) plus an option to avoid indexing particular folders. 2. Check the .config/baloofilerc file; this would contain something like: [Basic Settings] Indexing-Enabled=true [General] dbVersion=2 exclude filters=.pch,*.moc,*.fastq [etc, etc] exclude filters version=5 first run=false 3. Clear the "Also index file content" checkbox and apply. OBSERVED RESULTS: No change to the .config/baloofilerc file. If I log out and back in again the "Also index..." checkbox is checked again. Search in Dolphin still shows content matches EXPECTED RESULTS: A line: only basic indexing=true Should be added to the baloofilerc file and the baloo index rebuilt. SOFTWARE/OS VERSIONS: System Settings 5.17.90 from Neon Testing KDE Plasma 5.17.90 KDE Frameworks 5.67.0 Qt 5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415867] Face recognition -> after manual tagging -> no detection
https://bugs.kde.org/show_bug.cgi?id=415867 --- Comment #4 from r...@gmx.de --- digikam-7.0.0-beta3-20200130T131559-x86-64-debug.appimage USED Hello new feedback from me. In this version the problem still exists. r4c3 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 417126] New: Please implement a feature that subdivides a book
https://bugs.kde.org/show_bug.cgi?id=417126 Bug ID: 417126 Summary: Please implement a feature that subdivides a book Product: okular Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: sphaman...@gmail.com Target Milestone: --- SUMMARY What if we had the ability to subdivide an Ebook STEPS TO REPRODUCE 1. Open any Ebook 2. Read Ebook to somewhere like chapter 3 3. Realise that you've forgotten the content of chapter 1 OBSERVED RESULT You get frustrated that you have to reread the book from the first chapter and that the bookmark feature is doing no justice EXPECTED RESULT You have the ability to open the book in parts where each part is it's own book (subBook) and each subBook has it's own bookmarks, history and other stuff that comes standard with each book , only that it's a cut out of a bigger book. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 0.24.0 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 4.8.7 ADDITIONAL INFORMATION Okay , I admit that this is not a bug report at least not that of Okular , but rather that of my brain ... COMMAND_LINE : brain --wakeup --do_stuff VERSION : 1.3.8 OS : HumanAnatomy ARCH : prim_86e10n BUG : poor memory capacity First off let me point out that I'm having doubts that Okular ever had any bugs (sure I've been using it for about six months now , but still) it seems to work just fine. Here's the issue , I've been reading this ebook (Precalculus-OP_88kwxYo.pdf from Openstax) which is rather enormous (1156 pages) and somewhat interesting ,and for the third time now I keep rereading it from chapter one everytime I get to chapter three not because I want to but because I keep forgetting the contents of previous chapters , sure I could take notes but (besides saving the environment by not making use of paper [for writing]) I'd rather just read the original content or make use of the computer to take down notes but the switch from Okular to emacs is somewhat unsavoury especially having to do it every few seconds (one might as well rewrite the book) , in summary I'm not good at taking notes. So I came up with the idea of reading the book in parallel (as opposed to the way ebooks are read). Enter the Okular exclusive SubdivideBook (or whatever the developers choose to name it). Normal one opens an ebook and Okular conveniently takes them to the last page they've read , great so what's the problem ? After going back to the first chapter to look up a section of interest (from the third chapter) I normally would exit Okular there and then (given that the section of interest is in fact the entire chapter ), so when I reopen the book I have to whizz through hundreds of pages just to get to the third chapter and if I've forgotten the section I was in reread the entire chapter from the bottom. With the subBook feature I could open the book , choose a subBook that with chapter one read it (of course) and when I reopen the book , choose a subBook with chapter three , sure I could use the navigation options provided by Okular but then again reopening the book would force me to reread a chapter (or some subsection thereof) thus destroying the whole purpose. On the other hand each subBook has it's own last_page_read (or whatever it's called in the sources). A possible implementation would be a "Make SubBook mode" , in this mode there are (at least) four actions that can be performed, ADD_PAGE , REMOVE_PAGE , BUILD_SUBBOOK , CANCEL. The "Make SubBook" function could automatically add the current page (page being read on the call to make a subBook) and thus performing the ADD_PAGE function , on the call for the next page (which would now be the current page) ADD_PAGE could be performed again , the call for the previous page could result in REMOVE_PAGE being performed unless the the previous page is being requested from the first page of the subBook in which case the first page would be replaced by the current page on every previous page request. After the subBook has been completed BUILD_SUBBOOK could be performed. It's important to realise that a subBook is not a complete book in it's own right but rather a slice of a bigger book (or optionally another subBook [recursive subBooking]). Just in case it's not clear : ADD_PAGE --> Add a page to the subBook stack REMOVE_PAGE --> Removes a page from the top of the stack BUILD_SUBBOOK --> Creates a subBook from the subBook stack CANCEL--> Cancels the entire operation Please implement this feature if convenient , if inconvenient implement it all the same. -- You are receiving this mail because:
[plasmashell] [Bug 415917] The context menu when dropping a file to the desktop corner doesn't appear correctly
https://bugs.kde.org/show_bug.cgi?id=415917 tr...@yandex.com changed: What|Removed |Added Latest Commit|https://commits.kde.org/kio |https://commits.kde.org/pla |/fbb2be9aad196d92ca1a7adcc8 |sma-desktop/36e918b09780763 |afa8b63ba83659 |59c17c70c136bd27862db9d63 Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #9 from tr...@yandex.com --- Git commit 36e918b0978076359c17c70c136bd27862db9d63 by Tranter Madi. Committed on 04/02/2020 at 05:55. Pushed by trmdi into branch 'master'. Delay popup when dropping things into containments Summary: Depend: D26691 Test Plan: Drop files into desktop folder layout/folder widget, the menu is shown correctly in all cases. Reviewers: #plasma, davidedmundson, broulik, hein Reviewed By: #plasma, hein Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D26514 M +2-2containments/desktop/package/contents/ui/FolderView.qml M +3-2containments/desktop/plugins/folder/foldermodel.cpp M +1-1containments/desktop/plugins/folder/foldermodel.h https://commits.kde.org/plasma-desktop/36e918b0978076359c17c70c136bd27862db9d63 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415917] The context menu when dropping a file to the desktop corner doesn't appear correctly
https://bugs.kde.org/show_bug.cgi?id=415917 --- Comment #8 from tr...@yandex.com --- Git commit f8be3ea7102fbd584da1a39f5285ca72b5e69afa by Tranter Madi. Committed on 04/02/2020 at 05:54. Pushed by trmdi into branch 'master'. Optimize code when dropping files into the desktop Summary: Currently, when you have the desktop in the Desktop layout, if you drop 10 jpg files into the desktop, it creates 10 menus at the same position. When you have the desktop in the Folder layout, if you drop 10 jpg files into the desktop, it calls `KIO::setApplicationActions()` 10 times. What does this improve? - Do not create KIO::MimetypeJob for each file - Do not call `DropJob::setApplicationActions()` too many times/ create too many menus for each file. My idea is that, when you drop files into the desktop: - If they have the same `mimetype` -> we add actions support this `mimetype`. - If not -> we only show the action from `KIO::DropJob` and only actions support different `mimetypes` at the same time like `Add icon`... **Require:** D26484 Reviewers: #plasma, mart, broulik, #vdg, davidedmundson Reviewed By: #plasma, davidedmundson Subscribers: davidedmundson, anthonyfieroni, #plasma, kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D26691 M +95 -152 src/scriptengines/qml/plasmoid/containmentinterface.cpp M +2-4src/scriptengines/qml/plasmoid/containmentinterface.h A +110 -0src/scriptengines/qml/plasmoid/dropmenu.cpp [License: LGPL (v2+)] A +66 -0src/scriptengines/qml/plasmoid/dropmenu.h [License: LGPL (v2+)] https://commits.kde.org/plasma-framework/f8be3ea7102fbd584da1a39f5285ca72b5e69afa -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417121] Crash when switching to google maps in "Edit Geolocation" with v7.0.0-beta-2, beta 1 is ok
https://bugs.kde.org/show_bug.cgi?id=417121 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- ok, i will fix appimage bash script and rebuild the bundles Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417121] Crash when switching to google maps in "Edit Geolocation" with v7.0.0-beta-2, beta 1 is ok
https://bugs.kde.org/show_bug.cgi?id=417121 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Gilles, we may need to preload libnss3.so. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417125] New: Battery icon does not update on time
https://bugs.kde.org/show_bug.cgi?id=417125 Bug ID: 417125 Summary: Battery icon does not update on time Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Battery Monitor Assignee: k...@privat.broulik.de Reporter: andreyyash...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When battery runs low I get a notification about it, but it takes some time until battery icon becomes red. The same problem appears when I change the value of low battery level in settings on a level that is lower then current battarey charge. STEPS TO REPRODUCE 1. Charge you battery to a level higher then the value of low battery level in settings. 2. Set the value of low battery level in settings to be less than your current charge or wait until your battery charge drops. OBSERVED RESULT Battery icon is still white(At Least for some period of time). EXPECTED RESULT Battery icon becomes red immediately. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417040] No pressure at first stamp in floating dock mode
https://bugs.kde.org/show_bug.cgi?id=417040 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416498] Resume from suspend
https://bugs.kde.org/show_bug.cgi?id=416498 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376886] "insert 1 frame" and "remove 1 frame" should be available for layers
https://bugs.kde.org/show_bug.cgi?id=376886 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416447] system settings crashed when I clicked on "All settings"
https://bugs.kde.org/show_bug.cgi?id=416447 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 399225] OPENVPN does not connect to the network manager
https://bugs.kde.org/show_bug.cgi?id=399225 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 416408] Discover crashed after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=416408 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415899] Can't load a save file even with kde as saved file
https://bugs.kde.org/show_bug.cgi?id=415899 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 389559] Info Center crashes on clicking Energy Information
https://bugs.kde.org/show_bug.cgi?id=389559 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417124] New: Plasma crashes when selecting new global theme
https://bugs.kde.org/show_bug.cgi?id=417124 Bug ID: 417124 Summary: Plasma crashes when selecting new global theme Product: plasmashell Version: 5.17.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: rob...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.5) Qt Version: 5.14.1 Frameworks Version: 5.66.0 Operating System: Linux 5.5.0-1-MANJARO-ARM aarch64 Distribution: Manjaro ARM -- Information about the crash: - What I was doing when the application crashed: When I try to select another Global theme (in this instance, from Matcha to Breeze), Plasma crashes. When Plasma reloads, the global theme completes the switch. Package list: https://phabricator.kde.org/P537 Currently using the Panfrost driver: Compositing === Compositing is active Compositing Type: OpenGL ES 2.0 OpenGL vendor string: Panfrost OpenGL renderer string: Mali T860 (Panfrost) OpenGL version string: OpenGL ES 2.0 Mesa 20.0.0-devel (git-d3fa18a1fa) OpenGL platform interface: EGL OpenGL shading language version string: OpenGL ES GLSL ES 1.0.16 Driver: Unknown GPU class: Unknown OpenGL version: 2.0 GLSL version: 1.0.16 Mesa version: 20.0 X server version: 1.20.7 Linux kernel version: 5.5 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x8ae8cdd0 (LWP 1234))] Thread 8 (Thread 0x5895d090 (LWP 1725)): #0 0x8e6f21d4 in pthread_cond_wait@@GLIBC_2.17 () at /usr/lib/libpthread.so.0 #1 0x8f38b3a4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x8f38b558 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x913f1c54 in () at /usr/lib/libQt5Quick.so.5 #4 0x913f1f94 in () at /usr/lib/libQt5Quick.so.5 #5 0x8f3839b8 in () at /usr/lib/libQt5Core.so.5 #6 0x8e6eb938 in start_thread () at /usr/lib/libpthread.so.0 #7 0x8f015a1c in thread_start () at /usr/lib/libc.so.6 Thread 7 (Thread 0x5ad3d090 (LWP 1480)): #0 0x8e6f21d4 in pthread_cond_wait@@GLIBC_2.17 () at /usr/lib/libpthread.so.0 #1 0x8f38b3a4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x8f38b558 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x913f1c54 in () at /usr/lib/libQt5Quick.so.5 #4 0x913f1f94 in () at /usr/lib/libQt5Quick.so.5 #5 0x8f3839b8 in () at /usr/lib/libQt5Core.so.5 #6 0x8e6eb938 in start_thread () at /usr/lib/libpthread.so.0 #7 0x8f015a1c in thread_start () at /usr/lib/libc.so.6 Thread 6 (Thread 0x5bb99090 (LWP 1479)): #0 0x8e6f21d4 in pthread_cond_wait@@GLIBC_2.17 () at /usr/lib/libpthread.so.0 #1 0x8f38b3a4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x8f38b558 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x913f1c54 in () at /usr/lib/libQt5Quick.so.5 #4 0x913f1f94 in () at /usr/lib/libQt5Quick.so.5 #5 0x8f3839b8 in () at /usr/lib/libQt5Core.so.5 #6 0x8e6eb938 in start_thread () at /usr/lib/libpthread.so.0 #7 0x8f015a1c in thread_start () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7258c090 (LWP 1432)): #0 0x8e6f21d4 in pthread_cond_wait@@GLIBC_2.17 () at /usr/lib/libpthread.so.0 #1 0x8f38b3a4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x8f38b558 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x913f1c54 in () at /usr/lib/libQt5Quick.so.5 #4 0x913f1f94 in () at /usr/lib/libQt5Quick.so.5 #5 0x8f3839b8 in () at /usr/lib/libQt5Core.so.5 #6 0x8e6eb938 in start_thread () at /usr/lib/libpthread.so.0 #7 0x8f015a1c in thread_start () at /usr/lib/libc.so.6 Thread 4 (Thread 0x73643090 (LWP 1429)): #0 0x8d7bafb8 in () at /usr/lib/libglib-2.0.so.0 #1 0x8d7bcafc in () at /usr/lib/libglib-2.0.so.0 #2 0x8d7be354 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #3 0x8d7beee0 in () at /usr/lib/libglib-2.0.so.0 #4 0x8d7bf17c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x8f60d8ac in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x8f59efe4 in
[Powerdevil] [Bug 417083] Crash when unplugging second monitor in Wayland
https://bugs.kde.org/show_bug.cgi?id=417083 KaiMing changed: What|Removed |Added CC||ck_min...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416419] KWIN freezed
https://bugs.kde.org/show_bug.cgi?id=416419 Christoph Feck changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #3 from Christoph Feck --- Thanks for the update; changing status. The BadWindow error messages are long plaguing us, but since they aren't annotated with source line information, it is nearly impossible to understand the cause for them. They don't seem to be harmful, either. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416033] Kwin crash with kwin-tiling enabled when launching a VM
https://bugs.kde.org/show_bug.cgi?id=416033 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #7 from Christoph Feck --- Requested information was added with comment 5; changing status for inspection. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416989] Konqueror's terminal window does not start in current directory
https://bugs.kde.org/show_bug.cgi?id=416989 --- Comment #2 from phd --- https://phabricator.kde.org/D27148 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393403] Application launcher global shortcuts get assigned to random neighbours
https://bugs.kde.org/show_bug.cgi?id=393403 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Christoph Feck --- Requested information was added with comment 2; changing status for inspection. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415608] Frozen green screen when trying to wake up the system from sleep state. This problem is present on plasma 5 with linux kernel 5.x. Sleep works fine on linux kernel 4.x. Proc
https://bugs.kde.org/show_bug.cgi?id=415608 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |UPSTREAM Status|NEEDSINFO |RESOLVED --- Comment #6 from Christoph Feck --- If you cannot switch to the Linux VT, there is an issue with the kernel. I suggest to report it to the bug tracker of your distribution. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416386] Streched vertical line on Notifications
https://bugs.kde.org/show_bug.cgi?id=416386 Christoph Feck changed: What|Removed |Added CC||plasma-b...@kde.org Assignee|plasma-b...@kde.org |k...@privat.broulik.de Component|General |Notifications Target Milestone|--- |1.0 Product|kdeplasma-addons|plasmashell -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 416386] Streched vertical line on Notifications
https://bugs.kde.org/show_bug.cgi?id=416386 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #8 from Christoph Feck --- Requested information was added with comment 5; changing status for inspection. -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 416275] Activating Application Menu Bar Removes Windows Controls in Firefox
https://bugs.kde.org/show_bug.cgi?id=416275 --- Comment #6 from Mohan --- I am still having that on my test install. Maybe I haven't gotten the update yet. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416989] Konqueror's terminal window does not start in current directory
https://bugs.kde.org/show_bug.cgi?id=416989 phd changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Assignee|dolphin-bugs-n...@kde.org |p...@phd.re CC||p...@phd.re --- Comment #1 from phd --- Shouldn't this be fixed in KParts with ReadOnlyPart::setUrl() not only setting d->m_url but also updating d->m_file in a similar manner as the removed code did? -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 417123] New: info application crashed
https://bugs.kde.org/show_bug.cgi?id=417123 Bug ID: 417123 Summary: info application crashed Product: kinfocenter Version: 5.14.5 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: hubn...@gmail.com Reporter: k...@zipproth.de Target Milestone: --- Application: kinfocenter (5.14.5) Qt Version: 5.12.5 Frameworks Version: 5.62.0 Operating System: Linux 5.4.0-2-amd64 x86_64 Distribution: PureOS -- Information about the crash: - What I was doing when the application crashed: navigating between the various tabs of the info application - Unusual behavior I noticed: some of the tabs showed empty content, for example all my hard drives were simply displayed as "SSD" without any further information -- Backtrace: Application: Infozentrum (kinfocenter), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f96fd46c900 (LWP 16097))] Thread 8 (Thread 0x7f96d35ff700 (LWP 16271)): #0 0x7f97009b5db5 in futex_wait_cancelable (private=0, expected=0, futex_word=0x561107a18438) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f97009b5db5 in __pthread_cond_wait_common (abstime=0x0, mutex=0x561107a183e8, cond=0x561107a18410) at pthread_cond_wait.c:502 #2 0x7f97009b5db5 in __pthread_cond_wait (cond=0x561107a18410, mutex=0x561107a183e8) at pthread_cond_wait.c:655 #3 0x7f96e8f723eb in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f96e8f72007 in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f97009affb7 in start_thread (arg=) at pthread_create.c:486 #6 0x7f9701de32df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f96dadf9700 (LWP 16260)): #0 0x7f97009b5db5 in futex_wait_cancelable (private=0, expected=0, futex_word=0x561107a523d8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f97009b5db5 in __pthread_cond_wait_common (abstime=0x0, mutex=0x561107a52388, cond=0x561107a523b0) at pthread_cond_wait.c:502 #2 0x7f97009b5db5 in __pthread_cond_wait (cond=0x561107a523b0, mutex=0x561107a52388) at pthread_cond_wait.c:655 #3 0x7f96e8f723eb in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f96e8f72007 in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f97009affb7 in start_thread (arg=) at pthread_create.c:486 #6 0x7f9701de32df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f96e2e44700 (LWP 16210)): #0 0x7f97000811c4 in g_mutex_unlock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f970003602e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f970003622f in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f970235480b in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f97022fd71b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f970213e751 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f970164b845 in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f970213f8d2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f97009affb7 in start_thread (arg=) at pthread_create.c:486 #9 0x7f9701de32df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f96e3fff700 (LWP 16102)): #0 0x7f97009b5db5 in futex_wait_cancelable (private=0, expected=0, futex_word=0x561106937aec) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f97009b5db5 in __pthread_cond_wait_common (abstime=0x0, mutex=0x561106937a98, cond=0x561106937ac0) at pthread_cond_wait.c:502 #2 0x7f97009b5db5 in __pthread_cond_wait (cond=0x561106937ac0, mutex=0x561106937a98) at pthread_cond_wait.c:655 #3 0x7f96e8f723eb in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f96e8f72007 in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f97009affb7 in start_thread (arg=) at pthread_create.c:486 #6 0x7f9701de32df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f96f8fce700 (LWP 16101)): #0 0x7f9701dd8d1f in __GI___poll (fds=0x7f96e400f3c0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f970003610e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f970003622f in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f970235480b in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f97022fd71b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f970213e751 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f97011804e6 in () at /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7
[konsole] [Bug 416981] Colorful PS1 is somewhat broken
https://bugs.kde.org/show_bug.cgi?id=416981 --- Comment #2 from a.taha.b...@outlook.com --- (In reply to Ahmad Samir from comment #1) > What do you set PS1 to? It was: PS1='\e[1m[\e[35m\u\e[97m@\e[34m\h \W\e[97m]\$ \e[0m' I used tput instead of "\e[xxx" but it was not good either. Now, it is: PS1='[\u@\h \W]\$ ' -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 417118] Okular crashes on Print preview
https://bugs.kde.org/show_bug.cgi?id=417118 --- Comment #2 from Siddhartha Sahu --- Built from the latest master (commit on Feb 1): okular-git-r8658.c6d937ab0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 417118] Okular crashes on Print preview
https://bugs.kde.org/show_bug.cgi?id=417118 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Albert Astals Cid --- How recent is your "compiled from sources"? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398908] Dolphin uses up huge amounts of memory
https://bugs.kde.org/show_bug.cgi?id=398908 Ganton changed: What|Removed |Added CC||ku...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 315702] Re-add export function in kinfocenter
https://bugs.kde.org/show_bug.cgi?id=315702 --- Comment #14 from Christopher Yeleighton --- 1. The Export button should allow me to share information about the configuration, capabilities and important content on my computer with a computer-savvy pal who can give me some advice about what needs to be changed to improve it. 2. The Export button should allow me to archive information for future reference, to be able to answer the question what important configuration changes were made between point A and point B, in case anything stopped working in between. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416717] Option to apply settings to all touchpads, not just the current one
https://bugs.kde.org/show_bug.cgi?id=416717 Nate Graham changed: What|Removed |Added Summary|Feature request: give a |Option to apply settings to |global option to force |all touchpads, not just the |touchpad settings |current one Severity|normal |wishlist Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Nate Graham --- Thanks, Peter's explanation makes sense to me. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416717] Option to apply settings to all touchpads, not just the current one
https://bugs.kde.org/show_bug.cgi?id=416717 Nate Graham changed: What|Removed |Added Priority|NOR |LO -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416976] Regression: Screens should not be hidden in display configuration of systemsettings
https://bugs.kde.org/show_bug.cgi?id=416976 Nate Graham changed: What|Removed |Added Keywords||usability Status|REOPENED|CONFIRMED --- Comment #4 from Nate Graham --- Hey, I really like that idea! Showing the disabled screens in a separate area seems like quite an elegant solution to the issue, and would allow us to de-clutter the main UI by removing the combobox and the dots. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 253405] consider making shutdown dialog timeout shorter
https://bugs.kde.org/show_bug.cgi?id=253405 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |INTENTIONAL --- Comment #5 from Nate Graham --- It didn't go anywhere. :) Nobody was in favor, so I'm afraid I have to close this bug as RESOLVED INTENTIONAL. You can see the discussion in https://phabricator.kde.org/D27077 for details. If anyone can articulate a strong reason there why 10 seconds is better than 30, it might be possible to revisit the matter. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 350521] [RFE] [OpenVPN] kdeplasma-applets-plasma-nm does not support OTP Tokens for OpenVPN connections
https://bugs.kde.org/show_bug.cgi?id=350521 Vincent Scharf changed: What|Removed |Added CC||vinc...@scharf.eu.com --- Comment #13 from Vincent Scharf --- I can also confirm this behavior. In GNOME the challenge pops up just as expected, but on KDE there is only asked for the password and then the connection fails, since the OTP was not provided. Is there any work already done on this? -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 417122] New: Notification permission doesn't get stored
https://bugs.kde.org/show_bug.cgi?id=417122 Bug ID: 417122 Summary: Notification permission doesn't get stored Product: Falkon Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: k...@cyber-anlage.de Target Milestone: --- SUMMARY When I allow a website to send a notification (check the box to remember), close the browser and restart it. The site has to ask for permission again, it will be granted aromatic, but the website shouldn't have to ask again. If you enable desktop notifications on Youtube or Reddit this setting is disabled after you restart Falkon. STEPS TO REPRODUCE 1. go to https://www.bennish.net/web-notifications.html 2. click Authorize 3. select Remember 4. click Allow 5. restart Falkon 6. go to https://www.bennish.net/web-notifications.html 7. click the "Show"-button OBSERVED RESULT After restarting Falkon. Notifications will not show until I click on Authorize again. EXPECTED RESULT After restarting Falkon. Notifications should show when pressing the "Show"-button SOFTWARE/OS VERSIONS Linux/KDE Plasma: arch linux (available in About System) KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 Falkon: 3.1.0 and latest master -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416899] Offsets and ratio goes wrong when using Transform Tool
https://bugs.kde.org/show_bug.cgi?id=416899 --- Comment #5 from acc4commissi...@gmail.com --- (In reply to Ahab Greybeard from comment #4) > In the tool options docker for the transform tool, there is a small button > at the left near the top, called Transform around pivot point. Can you > toggle that to see if if makes a difference to the results you get? It still happens with the option pressed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415773] Krita 4.2.8 freezes when SHIFT-resizing brush
https://bugs.kde.org/show_bug.cgi?id=415773 --- Comment #16 from acc4commissi...@gmail.com --- I was wrong. Sorry. It seems to be a different problem and wasn't solved at all. I will write a separated bug report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415773] Krita 4.2.8 freezes when SHIFT-resizing brush
https://bugs.kde.org/show_bug.cgi?id=415773 --- Comment #15 from acc4commissi...@gmail.com --- (In reply to acc4commissions from comment #14) > It is certainly reduced drastically in the latest nightly, but I don't think > it's 'fixed' enough to call it so. It still happens when the size goes over > 750~850px. Although it's fairly usable as it is. For now I'm personally fine if you need to ignore this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415773] Krita 4.2.8 freezes when SHIFT-resizing brush
https://bugs.kde.org/show_bug.cgi?id=415773 acc4commissi...@gmail.com changed: What|Removed |Added CC||acc4commissi...@gmail.com --- Comment #14 from acc4commissi...@gmail.com --- It is certainly reduced drastically in the latest nightly, but I don't think it's 'fixed' enough to call it so. It still happens when the size goes over 750~850px. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417121] New: Crash when switching to google maps in "Edit Geolocation" with v7.0.0-beta-2, beta 1 is ok
https://bugs.kde.org/show_bug.cgi?id=417121 Bug ID: 417121 Summary: Crash when switching to google maps in "Edit Geolocation" with v7.0.0-beta-2, beta 1 is ok Product: digikam Version: 7.0.0 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Geolocation-Editor Assignee: digikam-bugs-n...@kde.org Reporter: ertl_mar...@gmx.de Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Select a picture 2. Item->Edit Geolocation 3. Select "Google Maps" OBSERVED RESULT App crashes EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian GNU/Linux 9 (available in About System) KDE Plasma Version: 5.8.6 KDE Frameworks Version: 5.28.0 Qt Version: 5.7.1 ADDITIONAL INFORMATION With digikam-7.0.0-beta1-x86-64.appimage this crash does not occur. Output on console: $ ./digikam-7.0.0-beta2-1-x86-64.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0 -- Preloading shared libs: QtAV 1.13.0(Jan 27 2020, 02:49:13) Multimedia framework base on Qt and FFmpeg. Distributed under the terms of LGPLv2.1 or later. Shanghai, China Copyright (C) 2012-2019 Wang Bin (aka. Lucas Wang) wbse...@gmail.com Donate: http://qtav.org/donate.html Source: https://github.com/wang-bin/QtAV Home page: http://qtav.org unknown: Unhandled container to remove : Digikam::DigikamApp [28149:28164:0203/221952.756673:ERROR:nss_util.cc(674)] Error initializing NSS with a persistent database (sql:/home/martin/.pki/nssdb): NSS error code: -8023 [28149:28164:0203/221952.756824:ERROR:nss_util.cc(154)] Error initializing NSS without a persistent database: NSS error code: -8023 [28149:28164:0203/221952.756836:FATAL:nss_util.cc(156)] nss_error=-8023, os_error=0 /tmp/.mount_digikaejjMEn/AppRun: Zeile 155: 28149 Trace/Breakpoint ausgelöst digikam $@ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417120] KWin closed unexpectedly when waking up laptop.
https://bugs.kde.org/show_bug.cgi?id=417120 --- Comment #3 from Milan Bartovic --- No KWin crash directly after reboot. But another crash after sleep. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417120] KWin closed unexpectedly when waking up laptop.
https://bugs.kde.org/show_bug.cgi?id=417120 --- Comment #2 from Milan Bartovic --- Next sleep produced again: KWin Closed Unexpectedly. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 381045] Logout greeter gets title bar and breaks background view
https://bugs.kde.org/show_bug.cgi?id=381045 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #13 from Nate Graham --- Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417120] KWin closed unexpectedly when waking up laptop.
https://bugs.kde.org/show_bug.cgi?id=417120 --- Comment #1 from Milan Bartovic --- After a next Sleep (Suspend to RAM): KWin Window Manager Desktop effects were restarted due to a graphics reset System is DELL E6420. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417120] New: KWin closed unexpectedly when waking up laptop.
https://bugs.kde.org/show_bug.cgi?id=417120 Bug ID: 417120 Summary: KWin closed unexpectedly when waking up laptop. Product: kwin Version: 5.16.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: bartovic.mi...@gmail.com Target Milestone: --- Application: kwin_x11 (5.16.5) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-29-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: I just woke up the laptop and logged in. Nothing more. It happened more times, already. I will try to reproduce. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa1c0057d00 (LWP 1831))] Thread 6 (Thread 0x7fa1af3fe700 (LWP 2200)): #0 0x7fa1c4d622c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x556e062dad90) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7fa1c4d622c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x556e062dad40, cond=0x556e062dad68) at pthread_cond_wait.c:508 #2 0x7fa1c4d622c6 in __pthread_cond_wait (cond=0x556e062dad68, mutex=0x556e062dad40) at pthread_cond_wait.c:638 #3 0x7fa1c57f3def in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa1c57f3ee1 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa1c48897b9 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fa1c4889a1a in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fa1c57edcc2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa1c4d5b669 in start_thread (arg=) at pthread_create.c:479 #9 0x7fa1c6f54323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fa1a76b2700 (LWP 1941)): #0 0x7fa1c4d622c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fa1c5370fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7fa1c4d622c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7fa1c5370f68, cond=0x7fa1c5370f90) at pthread_cond_wait.c:508 #2 0x7fa1c4d622c6 in __pthread_cond_wait (cond=0x7fa1c5370f90, mutex=0x7fa1c5370f68) at pthread_cond_wait.c:638 #3 0x7fa1c527a08a in () at /lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7fa1c527a0af in () at /lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7fa1c4d5b669 in start_thread (arg=) at pthread_create.c:479 #6 0x7fa1c6f54323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fa1a700 (LWP 1897)): #0 0x7fa1c5a09a24 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7fa1c59b363b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fa1c57eca75 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fa1c44fb319 in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #4 0x7fa1c57edcc2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa1c4d5b669 in start_thread (arg=) at pthread_create.c:479 #6 0x7fa1c6f54323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fa1be6fd700 (LWP 1883)): #0 0x7fa1c6f47d26 in __GI_ppoll (fds=0x7fa1b000b4e8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fa1c5a085f9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fa1c5a09b64 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fa1c59b363b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa1c57eca75 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa1c3f3aefa in () at /lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fa1c57edcc2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa1c4d5b669 in start_thread (arg=) at pthread_create.c:479 #8 0x7fa1c6f54323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fa1bf618700 (LWP 1859)): #0 0x7fa1c6f47c2f in __GI___poll (fds=0x7fa1bf617c28, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fa1c5711917 in () at /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fa1c571353a in xcb_wait_for_event () at /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fa1bf94f288 in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fa1c57edcc2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa1c4d5b669 in start_thread (arg=) at pthread_create.c:479 #6 0x7fa1c6f54323 in clone
[yakuake] [Bug 417119] New: Activities top bar covers the first row of the Yakuake dropdown window in multiple monitors
https://bugs.kde.org/show_bug.cgi?id=417119 Bug ID: 417119 Summary: Activities top bar covers the first row of the Yakuake dropdown window in multiple monitors Product: yakuake Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: gba...@msa.com.ar Target Milestone: --- Created attachment 125650 --> https://bugs.kde.org/attachment.cgi?id=125650=edit Dropdown yakuake covered by top bar SUMMARY STEPS TO REPRODUCE 1. Set 2 monitors (the main one and an extra too) 2. Call yakuake from hotkey being on the main monitor OBSERVED RESULT Activities top bar covers the first row of the Yakuake dropdown window EXPECTED RESULT Yakuake windows starts right after the Activities top bar SOFTWARE/OS VERSIONS Ubuntu 18.04 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 417118] New: Okular crashes on Print preview
https://bugs.kde.org/show_bug.cgi?id=417118 Bug ID: 417118 Summary: Okular crashes on Print preview Product: okular Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: sh.siddhar...@gmail.com Target Milestone: --- Application: okular (1.9.70) (Compiled from sources) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.1-arch1-1 x86_64 Windowing system: X11 Distribution: Arch Linux -- Information about the crash: OPening File -> Print Preview on any pdf file (tried on 3 different ones) crashes Okular. The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd296a50600 (LWP 59660))] Thread 7 (Thread 0x7fd28632f700 (LWP 59666)): #0 0x7fd299a94c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd287828dec in ?? () from /usr/lib/dri/i965_dri.so #2 0x7fd2878289e8 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7fd299a8e4cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fd29a5122d3 in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7fd286b30700 (LWP 59665)): #0 0x7fd299a94c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd287828dec in ?? () from /usr/lib/dri/i965_dri.so #2 0x7fd2878289e8 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7fd299a8e4cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fd29a5122d3 in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7fd27eb30700 (LWP 59664)): #0 0x7fd299a94c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd287828dec in ?? () from /usr/lib/dri/i965_dri.so #2 0x7fd2878289e8 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7fd299a8e4cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fd29a5122d3 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7fd287331700 (LWP 59663)): #0 0x7fd299a94c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd287828dec in ?? () from /usr/lib/dri/i965_dri.so #2 0x7fd2878289e8 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7fd299a8e4cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fd29a5122d3 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7fd28fdd3700 (LWP 59662)): #0 0x7fd29a5079ef in poll () from /usr/lib/libc.so.6 #1 0x7fd298f63120 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fd298f631f1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fd29aac403c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fd29aa6a4cc in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fd29a88ee52 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fd29ad14b28 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x7fd29a88ffc6 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fd299a8e4cf in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fd29a5122d3 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fd295c67700 (LWP 59661)): #0 0x7fd29a5079ef in poll () from /usr/lib/libc.so.6 #1 0x7fd299d0e630 in ?? () from /usr/lib/libxcb.so.1 #2 0x7fd299d102db in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7fd296634b81 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7fd29a88ffc6 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fd299a8e4cf in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fd29a5122d3 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7fd296a50600 (LWP 59660)): [KCrash Handler] #6 0x7fd29b59a6a5 in QAction::setEnabled(bool) () from /usr/lib/libQt5Widgets.so.5 #7 0x7fd28eb1261f in PageView::updateActionState (this=0x55f58f3d05c0, haspages=haspages@entry=false, documentChanged=documentChanged@entry=false, hasformwidgets=hasformwidgets@entry=false) at /usr/src/debug/okular/ui/pageview.cpp:1268 #8 0x7fd28eaa6e18 in Okular::Part::Part (this=this@entry=0x55f58f38abb0, parentWidget=parentWidget@entry=0x7fffe4dade50, parent=parent@entry=0x7fffe4dade50, args=..., __in_chrg=, __vtt_parm=) at /usr/include/c++/9.2.0/bits/atomic_base.h:413 #9 0x7fd28eab00d4 in KPluginFactory::createPartInstance (parentWidget=0x7fffe4dade50, parent=0x7fffe4dade50, args=...) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:536 #10 0x7fd29bb308a5 in KPluginFactory::create (this=0x55f58ebb0dc0, iface=0x7fd29c295a18 "KParts::ReadOnlyPart", parentWidget=0x7fffe4dade50, parent=0x7fffe4dade50, args=..., keyword=...) at /usr/src/debug/kcoreaddons/src/lib/plugin/kpluginfactory.cpp:145 #11 0x7fd28ead58db in KPluginFactory::create
[plasmashell] [Bug 417117] New: Plasma Crash to Black Screen After Sticky Note Creation
https://bugs.kde.org/show_bug.cgi?id=417117 Bug ID: 417117 Summary: Plasma Crash to Black Screen After Sticky Note Creation Product: plasmashell Version: 5.17.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: blakeg...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.5) Qt Version: 5.14.0 Frameworks Version: 5.66.0 Operating System: Linux 5.4.15-arch1-1 x86_64 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: Using VSCode, dragged a tab over to my desktop and created a sticky note. Clicked on VSCode again and desktop went black, but I could still see and interact with VSCode. - Unusual behavior I noticed: The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb6d35bccc0 (LWP 545))] Thread 18 (Thread 0x7fb66a1a6700 (LWP 81874)): #0 0x7fb6d708bc45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb6d7c4bcc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fb6d7c4bda2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fb6d99b918b in () at /usr/lib/libQt5Quick.so.5 #4 0x7fb6d99b941b in () at /usr/lib/libQt5Quick.so.5 #5 0x7fb6d7c45fd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7fb6d70854cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fb6d78c82d3 in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7fb66b7fe700 (LWP 73331)): #0 0x7fb6d708bc45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb6d7c4bcc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fb6d7c4bda2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fb6d99b918b in () at /usr/lib/libQt5Quick.so.5 #4 0x7fb6d99b941b in () at /usr/lib/libQt5Quick.so.5 #5 0x7fb6d7c45fd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7fb6d70854cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fb6d78c82d3 in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7fb66bfff700 (LWP 67874)): #0 0x7fb6d708bc45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb6d7c4bcc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fb6d7c4bda2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fb6d99b918b in () at /usr/lib/libQt5Quick.so.5 #4 0x7fb6d99b941b in () at /usr/lib/libQt5Quick.so.5 #5 0x7fb6d7c45fd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7fb6d70854cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fb6d78c82d3 in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7fb69ca6b700 (LWP 67873)): #0 0x7fb6d78bd9ef in poll () at /usr/lib/libc.so.6 #1 0x7fb6b069cc14 in () at /usr/lib/libpulse.so.0 #2 0x7fb6b06aa059 in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #3 0x7fb6b06b4301 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7fb6b06b43b1 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7fb6b06a461e in () at /usr/lib/libpulse.so.0 #6 0x7fb6b0622d1c in () at /usr/lib/pulseaudio/libpulsecommon-13.0.so #7 0x7fb6d70854cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fb6d78c82d3 in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7fb69e298700 (LWP 65327)): #0 0x7fb6d708bc45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb6d7c4bcc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fb6d7c4bda2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fb6d99b918b in () at /usr/lib/libQt5Quick.so.5 #4 0x7fb6d99b941b in () at /usr/lib/libQt5Quick.so.5 #5 0x7fb6d7c45fd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7fb6d70854cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fb6d78c82d3 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7fb69d9e9700 (LWP 62501)): #0 0x7fb6d708bc45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb6d7c4bcc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fb6d7c4bda2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fb6d99b918b in () at /usr/lib/libQt5Quick.so.5 #4 0x7fb6d99b941b in () at /usr/lib/libQt5Quick.so.5 #5 0x7fb6d7c45fd6 in () at /usr/lib/libQt5Core.so.5 #6
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 francisco_t changed: What|Removed |Added CC||leviat...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417114] Widget removed from desktop/panel is back after relogin if I do logout while "Undo" notification is visible
https://bugs.kde.org/show_bug.cgi?id=417114 Patrick Silva changed: What|Removed |Added Summary|Widget removed from desktop |Widget removed from |is back after relogin if I |desktop/panel is back after |do logout while "Undo" |relogin if I do logout |notification is visible |while "Undo" notification ||is visible --- Comment #1 from Patrick Silva --- The same happens with a widget removed from Plasma panel. Not reproducible if I close the "Undo" notification before logout. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416999] Task Manager never stops demanding attention in some cases when a window state is _NET_WM_STATE = _NET_WM_STATE_DEMANDS_ATTENTION
https://bugs.kde.org/show_bug.cgi?id=416999 andydecle...@gmail.com changed: What|Removed |Added Summary|Request: Option to obey |Task Manager never stops |visibility setting even |demanding attention in some |when an app window raises a |cases when a window state |bell/alert/_NET_WM_STATE = |is _NET_WM_STATE = |_NET_WM_STATE_DEMANDS_ATTEN |_NET_WM_STATE_DEMANDS_ATTEN |TION|TION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416999] Request: Option to obey visibility setting even when an app window raises a bell/alert/_NET_WM_STATE = _NET_WM_STATE_DEMANDS_ATTENTION
https://bugs.kde.org/show_bug.cgi?id=416999 --- Comment #20 from andydecle...@gmail.com --- (In reply to Michail Vourlakos from comment #19) > (In reply to andydecleyre from comment #18) > > So you had not been following the reproduction steps until now. Does latte > > tasks support ungrouped, text-based task items? > > > > I will change the product for this bug to Task Manager. Thank you for > > reproducing. > > OH I did but you never mentioned you are using a Plasma taskmanager, only by > using your layout file that was obvious... "with the Task Manager widget" -- original report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416999] Request: Option to obey visibility setting even when an app window raises a bell/alert/_NET_WM_STATE = _NET_WM_STATE_DEMANDS_ATTENTION
https://bugs.kde.org/show_bug.cgi?id=416999 andydecle...@gmail.com changed: What|Removed |Added CC||plasma-b...@kde.org Version|0.9.8.1 |5.17.5 Assignee|mvourla...@gmail.com|h...@kde.org Component|application |Task Manager Target Milestone|--- |1.0 Product|lattedock |plasmashell -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416999] Request: Option to obey visibility setting even when an app window raises a bell/alert/_NET_WM_STATE = _NET_WM_STATE_DEMANDS_ATTENTION
https://bugs.kde.org/show_bug.cgi?id=416999 --- Comment #19 from Michail Vourlakos --- (In reply to andydecleyre from comment #18) > So you had not been following the reproduction steps until now. Does latte > tasks support ungrouped, text-based task items? > > I will change the product for this bug to Task Manager. Thank you for > reproducing. OH I did but you never mentioned you are using a Plasma taskmanager, only by using your layout file that was obvious... -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416999] Request: Option to obey visibility setting even when an app window raises a bell/alert/_NET_WM_STATE = _NET_WM_STATE_DEMANDS_ATTENTION
https://bugs.kde.org/show_bug.cgi?id=416999 --- Comment #18 from andydecle...@gmail.com --- So you had not been following the reproduction steps until now. Does latte tasks support ungrouped, text-based task items? I will change the product for this bug to Task Manager. Thank you for reproducing. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 410767] Crash 5.4.0 appimage
https://bugs.kde.org/show_bug.cgi?id=410767 Wood changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #10 from Wood --- Crash stopped happening in 5.4.x > 5.4.0. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416999] Request: Option to obey visibility setting even when an app window raises a bell/alert/_NET_WM_STATE = _NET_WM_STATE_DEMANDS_ATTENTION
https://bugs.kde.org/show_bug.cgi?id=416999 andydecle...@gmail.com changed: What|Removed |Added Resolution|UPSTREAM|--- Status|RESOLVED|REPORTED --- Comment #17 from andydecle...@gmail.com --- I will try master now. But to be sure: you're trying with - panel mode - plasma Task Manager right? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416999] Request: Option to obey visibility setting even when an app window raises a bell/alert/_NET_WM_STATE = _NET_WM_STATE_DEMANDS_ATTENTION
https://bugs.kde.org/show_bug.cgi?id=416999 Michail Vourlakos changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #16 from Michail Vourlakos --- Ok, found it but this is NOT LATTE responsibility... Things work just fine with Latte Tasks plasmoid ! BUT you are using a Plasma Taskmanager. The Plasma Taskmanager sets its status to NEEDSATTENTION and in such case Latte responds to always SHOW the Latte dock/panel because it is AN APPLET requesting ATTENTION and in such case there could be no timer... Only solution for you is either to request from plasma devs that behavior with a timer or you need to switch to Latte Tasks, but I suppose this is not something you would prefer. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 417116] New: The search in "search and replace in files" is not so good as in "Find Text"
https://bugs.kde.org/show_bug.cgi?id=417116 Bug ID: 417116 Summary: The search in "search and replace in files" is not so good as in "Find Text" Product: lokalize Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sdepi...@gmail.com Reporter: elchev...@opensuse.org CC: sha...@ukr.net Target Milestone: --- Hi, I made a search in the "search and replace in files" with the folowing: Source: backtrace Target: estouro The problem is that the search only find this exact case sensitive match, it doesn't find the other possibilities like Backtrace/estouro, Backtrace/Estouro, backtrace/estouros, and so on. If I do a search using Ctrl+F inside a file and search for "estouro", I get the other possibilities like Estouro or estouros (the plural form). Is there a way to implement this? In the same tab for "mass replace" we have at least the option to use or not case sensitive Regards, Luiz -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416999] Request: Option to obey visibility setting even when an app window raises a bell/alert/_NET_WM_STATE = _NET_WM_STATE_DEMANDS_ATTENTION
https://bugs.kde.org/show_bug.cgi?id=416999 --- Comment #15 from Michail Vourlakos --- (In reply to andydecleyre from comment #11) > I honestly have a hard time believing that you have actually followed the > reproduction steps and still not reproduced the issue. believe it. I have set the dock to AutoHide to be even from obvious what is happenig. In my system, 1. Set a Latte dock to Auto hide 2. run your first command for a window 3. dock shows just fine for 8 secs and hides itself afterwards even though the window has not lost the needsattention flag 4. reexecuting [2] has no point because the window is still in NEEDSATTENTION 5. clearing its needs attention with your second command and reexecuting [2] behaves as normally from [3] Have you tried master version? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 417115] New: Kicker Run in terminal not working under wayland
https://bugs.kde.org/show_bug.cgi?id=417115 Bug ID: 417115 Summary: Kicker Run in terminal not working under wayland Product: frameworks-kwayland Version: 5.66.0 Platform: unspecified OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: johann.hoec...@gmail.com Target Milestone: --- SUMMARY When starting vim from Kicker under wayland, nothing happens. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT vim (and likely any other application with "Run in terminal" option set) opens within terminal application Linux/KDE Plasma: KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION Works in Plasma on X -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 381045] Logout greeter gets title bar and breaks background view
https://bugs.kde.org/show_bug.cgi?id=381045 --- Comment #12 from Szymon Łągiewka --- (In reply to Nate Graham from comment #11) > Is anyone still seeing this with Plasma 5.17 or the upcoming 5.18? Quick check (I don't use scaling anymore) on Plasma 5.17.5 and Qt 5.14.1 - everything works great with no artifacts as there were in 5.10. Feel free to resolve or wait for others to report. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416999] Request: Option to obey visibility setting even when an app window raises a bell/alert/_NET_WM_STATE = _NET_WM_STATE_DEMANDS_ATTENTION
https://bugs.kde.org/show_bug.cgi?id=416999 --- Comment #14 from andydecle...@gmail.com --- Created attachment 125649 --> https://bugs.kde.org/attachment.cgi?id=125649=edit nearly vanilla layout exhibiting the problem -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416999] Request: Option to obey visibility setting even when an app window raises a bell/alert/_NET_WM_STATE = _NET_WM_STATE_DEMANDS_ATTENTION
https://bugs.kde.org/show_bug.cgi?id=416999 --- Comment #13 from andydecle...@gmail.com --- Created attachment 125648 --> https://bugs.kde.org/attachment.cgi?id=125648=edit nearly vanilla lattedockrc exhibiting the problem -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 417076] Timeline time scale is not correctly modified when loading or creating project with non-default frame rate
https://bugs.kde.org/show_bug.cgi?id=417076 --- Comment #2 from alridd...@googlemail.com --- Fix confirmed. Thanks for the quick turnaround. :) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416999] Request: Option to obey visibility setting even when an app window raises a bell/alert/_NET_WM_STATE = _NET_WM_STATE_DEMANDS_ATTENTION
https://bugs.kde.org/show_bug.cgi?id=416999 --- Comment #12 from andydecle...@gmail.com --- Created attachment 125647 --> https://bugs.kde.org/attachment.cgi?id=125647=edit Screenshot of nearly vanilla setup exhibiting the problem -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416999] Request: Option to obey visibility setting even when an app window raises a bell/alert/_NET_WM_STATE = _NET_WM_STATE_DEMANDS_ATTENTION
https://bugs.kde.org/show_bug.cgi?id=416999 --- Comment #11 from andydecle...@gmail.com --- Alright, I created a fresh user, a fresh latte dock, and configured exactly as described in the original post: Task Manager widget and Dodge Active set, with no other items. Then I tested exactly as described in the original post, with xprop. I am attaching the lattedockrc, layout config, and a screenshot showing how the "needs attention window" (konsole) is obscured by latte. This never seems to end, at least with a few minutes of waiting. I honestly have a hard time believing that you have actually followed the reproduction steps and still not reproduced the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407793] Maximize vertically and horizontally do not work in wayland
https://bugs.kde.org/show_bug.cgi?id=407793 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417114] New: Widget removed from desktop is back after relogin if I do logout while "Undo" notification is visible
https://bugs.kde.org/show_bug.cgi?id=417114 Bug ID: 417114 Summary: Widget removed from desktop is back after relogin if I do logout while "Undo" notification is visible Product: plasmashell Version: 5.17.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 SUMMARY I can't reproduce this behavior on X11. STEPS TO REPRODUCE 1. start Wayland session 2. right click on desktop, click on "Add widgets..." 3. drag a widget and drop it on desktop (I used Analog Clock during my test) 4. close the widget explorer 5. right click on the widget added to desktop, click on "Remove " (plasma shows a notification with a button to undo removing) 6. while the notification is still visible, do logout 7 start Wayland session again OBSERVED RESULT widget removed in the steps above is present on your desktop again EXPECTED RESULT removed widget does not back after relogin SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416358] kcm_fonts: Cannot apply changes (button remains inactive)
https://bugs.kde.org/show_bug.cgi?id=416358 A. Wilcox (awilfox) changed: What|Removed |Added CC||awil...@adelielinux.org --- Comment #8 from A. Wilcox (awilfox) --- We're seeing this in Adélie Linux as well, on 5.17.90 with Qt 5.12.6. Additionally, the dropdowns for i.e. "Sub-pixel rendering" don't show any items other than the values currently chosen. Making the dropdowns active and then using the arrow keys, the values can be changed. (But the values cannot be saved, as previously described in this bug.) If this is a separate bug, I can file another. -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 417113] Add support for INSERT queries in the Query designer
https://bugs.kde.org/show_bug.cgi?id=417113 Jarosław Staniek changed: What|Removed |Added CC||stan...@kde.org Summary|SQL Insert INTO not |Add support for INSERT |correctly implemented |queries in the Query ||designer Severity|normal |wishlist --- Comment #3 from Jarosław Staniek --- Thanks, changes the title to "Add support for INSERT queries in the Query designer" because for now only SELECT queries are recongnised in the Designer. Wish #298149 is somehow alternate approach too. -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 417113] SQL Insert INTO not correctly implemented
https://bugs.kde.org/show_bug.cgi?id=417113 --- Comment #2 from mhanso...@gmail.com --- Created attachment 125646 --> https://bugs.kde.org/attachment.cgi?id=125646=edit Another image showing the error. -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 417113] SQL Insert INTO not correctly implemented
https://bugs.kde.org/show_bug.cgi?id=417113 --- Comment #1 from mhanso...@gmail.com --- Created attachment 125645 --> https://bugs.kde.org/attachment.cgi?id=125645=edit Image showing the issue. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 416957] Sort order menu doesn't work in compact/mobile view
https://bugs.kde.org/show_bug.cgi?id=416957 --- Comment #3 from Stefano Milani --- terminal output of bug (not crash, sorry for my error): file:///usr/lib/qt/qml/org/kde/kirigami.2/private/globaltoolbar/BreadcrumbControl.qml:43: TypeError: Cannot read property 'x' of undefined :7: TypeError: Cannot read property 'contentX' of null file:///usr/lib/qt/qml/org/kde/kirigami.2/private/ContextDrawerActionItem.qml:67: ReferenceError: mainFlickable is not defined file:///usr/lib/qt/qml/org/kde/kirigami.2/templates/OverlayDrawer.qml:209: TypeError: Cannot read property 'height' of null file:///usr/lib/qt/qml/org/kde/kirigami.2/templates/OverlayDrawer.qml:286: TypeError: Cannot read property 'height' of null -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 417113] New: SQL Insert INTO not correctly implemented
https://bugs.kde.org/show_bug.cgi?id=417113 Bug ID: 417113 Summary: SQL Insert INTO not correctly implemented Product: KEXI Version: 3.2.0 Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Queries Assignee: kexi-b...@kde.org Reporter: mhanso...@gmail.com CC: a...@piggz.co.uk, in...@fables.co.za Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Create a query using SQL view. 2. Include in that query INSERT INTO like you would to insert data into another table,(i.e. insert into table2 (a, b, c) select (d, e, f) from table 1;) 3. click "Check Query" OBSERVED RESULT "The query is incorrect "INSERT" is a reserved keyword." EXPECTED RESULT The query is correct SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417112] New: Icon Size Crash
https://bugs.kde.org/show_bug.cgi?id=417112 Bug ID: 417112 Summary: Icon Size Crash Product: systemsettings Version: 5.17.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mateusz.ko...@wp.pl Target Milestone: --- Application: systemsettings5 (5.17.5) Qt Version: 5.14.1 Frameworks Version: 5.66.0 Operating System: Linux 5.4.15-arch1-1 x86_64 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: When I click Change Icon Size in icons settings the system-settings app crashes every time. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5eb4684840 (LWP 4530))] Thread 10 (Thread 0x7f5e87fff700 (LWP 4542)): #0 0x7f5eb8d9042c in read () from /usr/lib/libc.so.6 #1 0x7f5eb6d1b9f0 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f5eb6d699e1 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7f5eb6d6b0c8 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7f5eb6d6b1f1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7f5eb934f03c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f5eb92f54cc in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7f5eb9119e52 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7f5eb83c1f89 in ?? () from /usr/lib/libQt5Qml.so.5 #9 0x7f5eb911afc6 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7f5eb797b4cf in start_thread () from /usr/lib/libpthread.so.0 #11 0x7f5eb8d9f2d3 in clone () from /usr/lib/libc.so.6 Thread 9 (Thread 0x7f5e8f367700 (LWP 4538)): #0 0x7f5eb8d9042c in read () from /usr/lib/libc.so.6 #1 0x7f5eb6d1b9f0 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f5eb6d699e1 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7f5eb6d6b0c8 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7f5eb6d6b1f1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7f5eb934f03c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f5eb92f54cc in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7f5eb9119e52 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7f5eb83c1f89 in ?? () from /usr/lib/libQt5Qml.so.5 #9 0x7f5eb911afc6 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7f5eb797b4cf in start_thread () from /usr/lib/libpthread.so.0 #11 0x7f5eb8d9f2d3 in clone () from /usr/lib/libc.so.6 Thread 8 (Thread 0x7f5ea9419700 (LWP 4537)): #0 0x7f5eb8d949ef in poll () from /usr/lib/libc.so.6 #1 0x7f5eb6d6b120 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f5eb6d6b1f1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f5eb934f03c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f5eb92f54cc in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f5eb9119e52 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f5eb83c1f89 in ?? () from /usr/lib/libQt5Qml.so.5 #7 0x7f5eb911afc6 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f5eb797b4cf in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f5eb8d9f2d3 in clone () from /usr/lib/libc.so.6 Thread 7 (Thread 0x7f5eaa32f700 (LWP 4536)): #0 0x7f5eb7981c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f5eab828dec in ?? () from /usr/lib/dri/i965_dri.so #2 0x7f5eab8289e8 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7f5eb797b4cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f5eb8d9f2d3 in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7f5eaab30700 (LWP 4535)): #0 0x7f5eb7981c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f5eab828dec in ?? () from /usr/lib/dri/i965_dri.so #2 0x7f5eab8289e8 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7f5eb797b4cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f5eb8d9f2d3 in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7f5eab331700 (LWP 4534)): #0 0x7f5eb7981c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f5eab828dec in ?? () from /usr/lib/dri/i965_dri.so #2 0x7f5eab8289e8 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7f5eb797b4cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f5eb8d9f2d3 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f5eb0933700 (LWP 4533)): #0 0x7f5eb7981c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f5eab828dec in ?? () from
[Discover] [Bug 416957] Sort order menu doesn't work in compact/mobile view
https://bugs.kde.org/show_bug.cgi?id=416957 --- Comment #2 from Stefano Milani --- terminal output of crash: file:///usr/lib/qt/qml/org/kde/kirigami.2/private/globaltoolbar/BreadcrumbControl.qml:43: TypeError: Cannot read property 'x' of undefined :7: TypeError: Cannot read property 'contentX' of null file:///usr/lib/qt/qml/org/kde/kirigami.2/private/ContextDrawerActionItem.qml:67: ReferenceError: mainFlickable is not defined file:///usr/lib/qt/qml/org/kde/kirigami.2/templates/OverlayDrawer.qml:209: TypeError: Cannot read property 'height' of null file:///usr/lib/qt/qml/org/kde/kirigami.2/templates/OverlayDrawer.qml:286: TypeError: Cannot read property 'height' of null -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 416951] kamoso crash after click record a video button
https://bugs.kde.org/show_bug.cgi?id=416951 --- Comment #4 from Stefano Milani --- terminal output at the moment of crash: $ kamoso No device found qrc:/qml/Mode.qml:5:28: Invalid property assignment: string expected - Assigning null to incompatible properties in QML is deprecated. This will become a compile error in future versions of Qt. file:///usr/lib/qt/qml/org/kde/kirigami.2/private/globaltoolbar/ToolBarPageHeader.qml:57:9: QML ActionToolBar: Binding loop detected for property "actions" file:///usr/lib/qt/qml/org/kde/kirigami.2/private/globaltoolbar/ToolBarPageHeader.qml:57:9: QML ActionToolBar: Binding loop detected for property "actions" file:///usr/lib/qt/qml/org/kde/kirigami.2/private/globaltoolbar/ToolBarPageHeader.qml:57:9: QML ActionToolBar: Binding loop detected for property "actions" file:///usr/lib/qt/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:126: TypeError: Cannot read property 'globalToolBarStyle' of null file:///usr/lib/qt/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:71:17: Unable to assign [undefined] to QQmlListProperty file:///usr/lib/qt/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:62:13: Unable to assign [undefined] to bool error debugMessage: Nessun nome di file specificato per la lettura. error on: "filesrc location=\"\" ! decodebin ! imagefreeze ! videoconvert ! identity name=last" "../gstreamer/plugins/elements/gstfilesrc.c(524): gst_file_src_start (): /GstPipeline:pipeline0/GstFileSrc:filesrc0" error debugMessage: Nessun nome di file specificato per la lettura. error on: "filesrc location=\"\" ! decodebin ! imagefreeze ! videoconvert ! bulge name=last" "../gstreamer/plugins/elements/gstfilesrc.c(524): gst_file_src_start (): /GstPipeline:pipeline1/GstFileSrc:filesrc1" (kamoso:2102): GLib-GObject-CRITICAL **: 18:59:53.143: g_object_set: assertion 'G_IS_OBJECT (object)' failed (kamoso:2102): GLib-GObject-CRITICAL **: 18:59:53.144: g_object_set: assertion 'G_IS_OBJECT (object)' failed (kamoso:2102): GLib-GObject-WARNING **: 18:59:53.144: invalid (NULL) pointer instance (kamoso:2102): GLib-GObject-CRITICAL **: 18:59:53.144: g_signal_emit_by_name: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (kamoso:2102): GLib-GObject-WARNING **: 18:59:58.311: invalid (NULL) pointer instance (kamoso:2102): GLib-GObject-CRITICAL **: 18:59:58.311: g_signal_emit_by_name: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kamoso path = /usr/bin pid = 2102 KCrash: Arguments: /usr/bin/kamoso KCrash: Attempting to start /usr/lib/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417082] Files on desktop can open multiple context menus at once on Wayland
https://bugs.kde.org/show_bug.cgi?id=417082 --- Comment #3 from Patrick Silva --- It also seems related/duplicate to/of bug 383904 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 416647] KBibTex unable to save files on a remote server via sftp
https://bugs.kde.org/show_bug.cgi?id=416647 --- Comment #3 from Joan --- (In reply to Thomas Fischer from comment #2) > I think I was able to fix this problem. Please have a look at the following > patch and report back if it fixed your problem: > https://commits.kde.org/clones/kbibtex/thomasfischer/kbibtex/ > 5040708c6486e075c7048ebd371ab6ccdd9262ed > > You can test this code without interfering with your default KBibTeX > installation by following the "quick start" instructions: > https://userbase.kde.org/KBibTeX/ > Development#Quick_Start_to_Run_KBibTeX_from_Git > > To test the Git version containing the fix for your bug, please run the > following command: > bash run-kbibtex.sh > https://anongit.kde.org/clones/kbibtex/thomasfischer/kbibtex.git > bugs/kde416647 Downloaded and compiled the new version as indicated. The patch did not work here, same behaviour as before. Let me add some additional information (tests): 1- To discard that I made something stupid with file permissions or sftp connection settings, I opened the remote (.bib) file with Kate and it worked as supposed, modifications were incorporated into the remote file after saving. 2- In kbibtex, the "save as" (new file) operation works well: I can succesfully save the modified contents into a new file in the remote directory. 3- After opening the remote file in kbibtex, I removed (externally, via cli) the remote file. After modifying the file (in kbibtex) and saving it, the OLD (unmodified) version 'reappeared' in the remote directory. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417082] Files on desktop can open multiple context menus at once on Wayland
https://bugs.kde.org/show_bug.cgi?id=417082 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #2 from Patrick Silva --- Is seems duplicate/related of/to bug 379635 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 345473] Double click on titlebar to maximize suddenly stops working
https://bugs.kde.org/show_bug.cgi?id=345473 lnx...@westlot.net changed: What|Removed |Added CC||lnx...@westlot.net --- Comment #62 from lnx...@westlot.net --- I can confirm this is still happening. The workaround from Patric Silva on running "kwin_x11 --replace" seems to work for now. Time will tell if it continues or reverts back to not working. Linux/KDE Plasma: KDE neon 5.17 with kernel 5.3.0-28-generic KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413179] Crash in QOpenGLTextureGlyphCache::resizeTextureData
https://bugs.kde.org/show_bug.cgi?id=413179 David Edmundson changed: What|Removed |Added Component|general |aurorae Summary|Crash in libnvidia-glcore |Crash in ||QOpenGLTextureGlyphCache::r ||esizeTextureData -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413179] Crash in QOpenGLTextureGlyphCache::resizeTextureData
https://bugs.kde.org/show_bug.cgi?id=413179 David Edmundson changed: What|Removed |Added CC||home.mat...@arcor.de --- Comment #7 from David Edmundson --- *** Bug 417111 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417111] Absturz nach Start des Chromium Browser
https://bugs.kde.org/show_bug.cgi?id=417111 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 413179 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417040] No pressure at first stamp in floating dock mode
https://bugs.kde.org/show_bug.cgi?id=417040 --- Comment #3 from Igor --- (In reply to Boudewijn Rempt from comment #1) > Could you please make a tablet log, too? I'm afraid that it'll turn out to > be a driver problem (because behaviour differs from tablet to tablet) and > that we cannot do much, but a tablet log would show whether we get tablet > events at all when the main window get focus. See > https://docs.krita.org/en/contributors_manual/user_support.html#gathering- > information Log: https://invent.kde.org/uploads/-/system/user/983/a32e3b1523e13b830a4442380bdc7fbc/tablet_log2 Screenshot with strokes during logging: https://invent.kde.org/uploads/-/system/user/983/8d55a8e2fa16a9c3d60cb2ffe15fd424/tablet_log2_strokes.jpg -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416652] Empty items in system tray area
https://bugs.kde.org/show_bug.cgi?id=416652 Konrad Materka changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||5.18.0 Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-workspace/31303ad3542b6 ||d05537b733e08857c43622ecc93 --- Comment #19 from Konrad Materka --- Git commit 31303ad3542b6d05537b733e08857c43622ecc93 by Konrad Materka. Committed on 03/02/2020 at 15:57. Pushed by kmaterka into branch 'Plasma/5.18'. [SNI] Fix race condition in item registration Summary: If StatusNotifierItem is registered and then immediately destroyed, it is possible that QDBusServiceWatcher will not emit the serviceUnregistered signal. Add an additional check to avoid such situations. FIXED-IN: 5.18.0 Test Plan: Telegram should not add empty items. Reviewers: #plasma_workspaces, #plasma, davidedmundson Reviewed By: #plasma_workspaces, #plasma, davidedmundson Subscribers: davidedmundson, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D27126 M +11 -7statusnotifierwatcher/statusnotifierwatcher.cpp https://commits.kde.org/plasma-workspace/31303ad3542b6d05537b733e08857c43622ecc93 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417111] Absturz nach Start des Chromium Browser
https://bugs.kde.org/show_bug.cgi?id=417111 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Component|general |aurorae -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417111] New: Absturz nach Start des Chromium Browser
https://bugs.kde.org/show_bug.cgi?id=417111 Bug ID: 417111 Summary: Absturz nach Start des Chromium Browser Product: kwin Version: 5.12.8 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: home.mat...@arcor.de Target Milestone: --- Application: kwin_x11 (5.12.8) Qt Version: 5.9.7 Frameworks Version: 5.55.0 Operating System: Linux 4.12.14-lp151.28.36-default x86_64 Distribution (Platform): openSUSE RPMs -- Information about the crash: Häufiger Absturz (nicht immer) nach dem Starten des Chromium Browser The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff534392940 (LWP 2037))] Thread 5 (Thread 0x7ff511299700 (LWP 3806)): #0 0x7ff53131db18 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #1 0x7ff5312c590a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #2 0x7ff5310e3daa in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #3 0x7ff52b8119f5 in () at /usr/lib64/libQt5Qml.so.5 #4 0x7ff5310e8ced in () at /usr/lib64/libQt5Core.so.5 #5 0x7ff52cd26569 in start_thread () at /lib64/libpthread.so.0 #6 0x7ff533d199ef in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7ff4f7fff700 (LWP 2285)): #0 0x7ff52cd2c8ad in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff52fff0574 in () at /usr/lib64/libQt5Script.so.5 #2 0x7ff52fff05b9 in () at /usr/lib64/libQt5Script.so.5 #3 0x7ff52cd26569 in start_thread () at /lib64/libpthread.so.0 #4 0x7ff533d199ef in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7ff5132d1700 (LWP 2152)): #0 0x7ff533d0f296 in ppoll () at /lib64/libc.so.6 #1 0x7ff53131c621 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7ff53131dd3e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7ff5312c590a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7ff5310e3daa in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7ff52b8119f5 in () at /usr/lib64/libQt5Qml.so.5 #6 0x7ff5310e8ced in () at /usr/lib64/libQt5Core.so.5 #7 0x7ff52cd26569 in start_thread () at /lib64/libpthread.so.0 #8 0x7ff533d199ef in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7ff518ca3700 (LWP 2058)): #0 0x7ff533d0f296 in ppoll () at /lib64/libc.so.6 #1 0x7ff53131c621 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7ff53131dd3e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7ff5312c590a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7ff5310e3daa in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7ff52a6b09e5 in () at /usr/lib64/libQt5DBus.so.5 #6 0x7ff5310e8ced in () at /usr/lib64/libQt5Core.so.5 #7 0x7ff52cd26569 in start_thread () at /lib64/libpthread.so.0 #8 0x7ff533d199ef in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7ff534392940 (LWP 2037)): [KCrash Handler] #6 0x41296a3b in () #7 0x7ff4ff2cee94 in () at /usr/lib64/libnvidia-glcore.so.440.44 #8 0x7ff4ff2d4268 in () at /usr/lib64/libnvidia-glcore.so.440.44 #9 0x7ff4fee58bbd in () at /usr/lib64/libnvidia-glcore.so.440.44 #10 0x7ff531be8945 in QOpenGLTextureGlyphCache::resizeTextureData(int, int) () at /usr/lib64/libQt5Gui.so.5 #11 0x7ff531b6d26a in QTextureGlyphCache::fillInPendingGlyphs() () at /usr/lib64/libQt5Gui.so.5 #12 0x7ff52bef7a76 in () at /usr/lib64/libQt5Quick.so.5 #13 0x7ff52bef4769 in () at /usr/lib64/libQt5Quick.so.5 #14 0x7ff52bfa3168 in QQuickTextNode::addGlyphs(QPointF const&, QGlyphRun const&, QColor const&, QQuickText::TextStyle, QColor const&, QSGNode*) () at /usr/lib64/libQt5Quick.so.5 #15 0x7ff52bfa8274 in () at /usr/lib64/libQt5Quick.so.5 #16 0x7ff52bfa40ca in QQuickTextNode::addTextLayout(QPointF const&, QTextLayout*, QColor const&, QQuickText::TextStyle, QColor const&, QColor const&, QColor const&, QColor const&, int, int, int, int) () at /usr/lib64/libQt5Quick.so.5 #17 0x7ff52bfa2d31 in QQuickText::updatePaintNode(QSGNode*, QQuickItem::UpdatePaintNodeData*) () at /usr/lib64/libQt5Quick.so.5 #18 0x7ff52bf5d918 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*) () at /usr/lib64/libQt5Quick.so.5 #19 0x7ff52bf5e193 in QQuickWindowPrivate::updateDirtyNodes() () at /usr/lib64/libQt5Quick.so.5 #20 0x7ff52bf5f412 in QQuickWindowPrivate::syncSceneGraph() () at /usr/lib64/libQt5Quick.so.5 #21 0x7ff52c018618 in QQuickRenderControl::grab() () at
[valgrind] [Bug 416436] Unrecognised instruction at address 0x1006037BD (__pthread_init.cold.2) macOS 10.15
https://bugs.kde.org/show_bug.cgi?id=416436 Louis Brunner changed: What|Removed |Added CC||louis.brunner...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416717] Feature request: give a global option to force touchpad settings
https://bugs.kde.org/show_bug.cgi?id=416717 --- Comment #4 from fli...@vongellhorn.ch --- I talked to Hutter https://gitlab.freedesktop.org/libinput/libinput/issues/419 and he said this should be added by KDE -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 417110] New: Audio thumbnails do not show waveform in left-hand clip after splitting when zoom level is 17+
https://bugs.kde.org/show_bug.cgi?id=417110 Bug ID: 417110 Summary: Audio thumbnails do not show waveform in left-hand clip after splitting when zoom level is 17+ Product: kdenlive Version: 19.12.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: pccs...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Load any video clip, and set to show video and audio separately on timeline. 2. Group video and audio and split. 3. Zoom to 17/21 OBSERVED RESULT Waveforms disappear from left hand portion. EXPECTED RESULT Waveform shown in both portions. SOFTWARE/OS VERSIONS Windows: 10 v1809 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
