[kate] [Bug 415115] There is no settings for Kate visible by default
https://bugs.kde.org/show_bug.cgi?id=415115 Burkhard Lück changed: What|Removed |Added CC||lu...@hube-lueck.de --- Comment #1 from Burkhard Lück --- https://docs.kde.org/trunk5/en/applications/fundamentals/menus.html#menus-settings: Settings → Show Menubar (Ctrl+M) Toggle the Menubar display on and off. Once hidden it can be made visible using the shortcut Ctrl+M again. If the menubar is hidden, the context menu opened with a right mouse button click anywhere in the view area has an extra entry Show Menubar. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415122] New: Plasma crashes on startup
https://bugs.kde.org/show_bug.cgi?id=415122 Bug ID: 415122 Summary: Plasma crashes on startup Product: plasmashell Version: 5.17.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: logan2...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.4) Qt Version: 5.14.0 Frameworks Version: 5.64.0 Operating System: Linux 5.4.2-zen1-1-zen x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Starting Plasma desktop - Custom settings of the application: Simple Thermal Monitor widget in the taskbar, icon taskbar I am using the latest Arch Linux packages with Qt 5.14 The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa21a85ecc0 (LWP 2255))] Thread 35 (Thread 0x7fa1a6efd700 (LWP 2715)): #0 0x7fa21e3d1c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa21ef8ecc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fa21ef8eda2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fa220cfd18b in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa220cfd41b in () at /usr/lib/libQt5Quick.so.5 #5 0x7fa21ef88fd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7fa21e3cb4cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fa21ec0b2d3 in clone () at /usr/lib/libc.so.6 Thread 34 (Thread 0x7fa1a76fe700 (LWP 2714)): #0 0x7fa21e3d1c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa2116bf48c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa2116bf088 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa21e3cb4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa21ec0b2d3 in clone () at /usr/lib/libc.so.6 Thread 33 (Thread 0x7fa1bd477700 (LWP 2691)): #0 0x7fa21e3d1c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa21ef8ecc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fa21ef8eda2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fa220cfd18b in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa220cfd41b in () at /usr/lib/libQt5Quick.so.5 #5 0x7fa21ef88fd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7fa21e3cb4cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fa21ec0b2d3 in clone () at /usr/lib/libc.so.6 Thread 32 (Thread 0x7fa1bf202700 (LWP 2690)): #0 0x7fa21e3d1c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa2116bf48c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa2116bf088 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa21e3cb4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa21ec0b2d3 in clone () at /usr/lib/libc.so.6 Thread 31 (Thread 0x7fa1df7fe700 (LWP 2627)): #0 0x7fa21ec009ef in poll () at /usr/lib/libc.so.6 #1 0x7fa21d425120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fa21d4251f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fa21f1bbcdc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fa21f16239c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fa21ef87e62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fa220c37e9b in () at /usr/lib/libQt5Quick.so.5 #7 0x7fa21ef88fd6 in () at /usr/lib/libQt5Core.so.5 #8 0x7fa21e3cb4cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fa21ec0b2d3 in clone () at /usr/lib/libc.so.6 Thread 30 (Thread 0x7fa1d700 (LWP 2626)): #0 0x7fa21e3d1c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa21ef8ecc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fa21ef8eda2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fa220cfd18b in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa220cfd41b in () at /usr/lib/libQt5Quick.so.5 #5 0x7fa21ef88fd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7fa21e3cb4cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fa21ec0b2d3 in clone () at /usr/lib/libc.so.6 Thread 29 (Thread 0x7fa1e4e3e700 (LWP 2625)): #0 0x7fa21e3d1c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa2116bf48c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa2116bf088 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa21e3cb4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa21ec0b2d3 in clone () at
[kstars] [Bug 415121] New: Kstars Lite on Android 9 crashes during startup
https://bugs.kde.org/show_bug.cgi?id=415121 Bug ID: 415121 Summary: Kstars Lite on Android 9 crashes during startup Product: kstars Version: 3.3.7 Platform: Android OS: Android 9.x Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: ajreyno...@san.rr.com Target Milestone: --- SUMMARY During startup of Kstars Lite on my Samsung Galaxy S9+ running Android 9, the app closes while loading the NGC catalog. STEPS TO REPRODUCE 1. Start the program 2. During loading the NGC catalog, the app closes. SOFTWARE/OS VERSIONS Android 9 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 354542] Show proper CMYK colors embedded in files like Krita
https://bugs.kde.org/show_bug.cgi?id=354542 --- Comment #14 from Raghavendra kamath --- Apart from CMYK support , there seems to be lack of color management too. Incidentally "Showfoto" from digikam has color management (RGB Only) May be we can check how it works? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 415118] Not possible to update packages
https://bugs.kde.org/show_bug.cgi?id=415118 --- Comment #1 from maxisebajua...@gmail.com --- This was solved after rebooting my computer. Do you still think it's worth keeping it opened and investigating? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414621] I cannot press play to play the animation in krita to look it over. It will not play no matter how much I try.
https://bugs.kde.org/show_bug.cgi?id=414621 --- 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.
[Discover] [Bug 414078] Discover Checking For Updates Painfully Slow
https://bugs.kde.org/show_bug.cgi?id=414078 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 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 415120] New: Bug to return from Lock screen and enter Desktop on system startup when Wallpapers are in Slideshow
https://bugs.kde.org/show_bug.cgi?id=415120 Bug ID: 415120 Summary: Bug to return from Lock screen and enter Desktop on system startup when Wallpapers are in Slideshow Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: littlejhon...@gmail.com Target Milestone: --- Hello! A few days ago I noticed a bug that made my kde lock screen crash and only come back a few minutes later, usually 10 to 15 minutes. This occurs when the lock screen is in "slideshow" mode and the folder (or folders) configured with the images has too many images. A similar bug occurs if the desktop is set to "slideshow" and the folder has too many wallpapers. In this case, what happens is that the system takes a long time to leave the presentation screen and go to the desktop. I do not know what the limit of wallpapers seems reasonable to the system, but the absurd amount I have (over 30 thousand) makes the system have this problem. When I used debian and kde was 5.12 I never noticed any of them, so it's probably something in kde 5.17, because even in 5.16, which I remember using in Manjaro, there weren't any of these problems -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371455] Slide show wallpaper massively slows down login when many images are configured
https://bugs.kde.org/show_bug.cgi?id=371455 Little Jhonnes changed: What|Removed |Added CC||littlejhon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Plasma Workspace Wallpapers] [Bug 415119] New: Bug to return from Lock screen and enter Desktop on system startup when Wallpapers are in Slideshow Mode
https://bugs.kde.org/show_bug.cgi?id=415119 Bug ID: 415119 Summary: Bug to return from Lock screen and enter Desktop on system startup when Wallpapers are in Slideshow Mode Product: Plasma Workspace Wallpapers Version: 5.17.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: littlejhon...@gmail.com Target Milestone: --- Hello! A few days ago I noticed a bug that made my kde lock screen crash and only come back a few minutes later, usually 10 to 15 minutes. This occurs when the lock screen is in "slideshow" mode and the folder (or folders) configured with the images has too many images. A similar bug occurs if the desktop is set to "slideshow" and the folder has too many wallpapers. In this case, what happens is that the system takes a long time to leave the presentation screen and go to the desktop. I do not know what the limit of wallpapers seems reasonable to the system, but the absurd amount I have (over 30 thousand) makes the system have this problem. When I used debian and kde was 5.12 I never noticed any of them, so it's probably something in kde 5.17, because even in 5.16, which I remember using in Manjaro, there weren't any of these problems -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 415118] New: Not possible to update packages
https://bugs.kde.org/show_bug.cgi?id=415118 Bug ID: 415118 Summary: Not possible to update packages Product: Discover Version: 5.15.4 Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: maxisebajua...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 124456 --> https://bugs.kde.org/attachment.cgi?id=124456=edit Error screenshot SUMMARY: When I click on update all packages, after a few seconds I get this error message: Cannot obtain lock E: could not get lock /var/lib/dpkg/lock-frontend -open (11: resource temporarily unavailable) E: unable to acquire the dkpg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? STEPS TO REPRODUCE 1. Open discover 2. Click on updates 3. Click on update all OBSERVED RESULT The error I wrote on the summary EXPECTED RESULT The app should have downloaded and installed the updates SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) Lubuntu 19.04 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415117] New: Specific color selector don't update its value when using float value and color pick + UI size bug
https://bugs.kde.org/show_bug.cgi?id=415117 Bug ID: 415117 Summary: Specific color selector don't update its value when using float value and color pick + UI size bug Product: krita Version: 4.2.8 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: minor Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: qamp...@hotmail.com Target Milestone: --- SUMMARY While working with 16/32-bit float image and changing the Specific color selector to 16/32-bit float, the values got stuck (not updating) while trying to pick a color with color picker. However, the values from Tool Options are updating correctly. Also, it has no effect whether OCIO is on or off. Another bug is the profile selector drop-down menu on specific color selector is crushed horizontally to the point that I can't read/select the color profile correctly. Undocking/resizing the dock didn't fix it. (details on the linked video) STEPS TO REPRODUCE 1. Use color picker on 16/32-bit float image 2. Change the Depth of specific color selector to the 16/32-bit float 3. Observe the sliders and values OBSERVED RESULT The sliders are updating/moving, but the values are stuck. EXPECTED RESULT The values are updating properly. SOFTWARE/OS VERSIONS Windows: 10 Pro 1903 Qt Version: 5.12.5 ADDITIONAL INFORMATION Here's the video to further describing the problem: https://youtu.be/EycgE2ERfbk -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 415116] New: Empty repo https://cgit.kde.org/kexi-extras.git/
https://bugs.kde.org/show_bug.cgi?id=415116 Bug ID: 415116 Summary: Empty repo https://cgit.kde.org/kexi-extras.git/ Product: KEXI Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: kexi-b...@kde.org Reporter: aspotas...@gmail.com CC: a...@piggz.co.uk, in...@fables.co.za Target Milestone: --- SUMMARY The Git repo https://cgit.kde.org/kexi-extras.git/ is empty and makes me wonder if it's a mistake or someone forgot to push important source code. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 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.
[frameworks-syntax-highlighting] [Bug 414996] Python HL does not highlight octal numbers
https://bugs.kde.org/show_bug.cgi?id=414996 Nibaldo G. changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||5.66.0 Latest Commit||https://commits.kde.org/syn ||tax-highlighting/8ca7064781 ||a328b33b2cd79668e876719f1cc ||762 --- Comment #2 from Nibaldo G. --- Git commit 8ca7064781a328b33b2cd79668e876719f1cc762 by Nibaldo González. Committed on 13/12/2019 at 02:22. Pushed by ngonzalez into branch 'master'. Python: improve numbers, add octals, binaries and "breakpoint" keyword Summary: FIXED-IN: 5.66.0 **Changes:** * Improve number detection with underscores. Add binaries and octales. (I took the regular expressions from the TypeScript highlighting file and adapted them to Python). See: https://www.python.org/dev/peps/pep-0515/ * Add keyword "breakpoint" introduced in Python 3.7: https://www.python.org/dev/peps/pep-0553/ Reviewers: #framework_syntax_highlighting, dhaumann, cullmann Reviewed By: #framework_syntax_highlighting, dhaumann Subscribers: kwrite-devel, kde-frameworks-devel Tags: #kate, #frameworks Differential Revision: https://phabricator.kde.org/D25869 M +32 -0autotests/folding/test.py.fold M +36 -4autotests/html/test.py.html M +32 -0autotests/input/test.py M +36 -4autotests/reference/test.py.ref M +21 -16 data/syntax/python.xml https://commits.kde.org/syntax-highlighting/8ca7064781a328b33b2cd79668e876719f1cc762 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415086] A file won't "draw"
https://bugs.kde.org/show_bug.cgi?id=415086 Tymond changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Tymond --- @vanyossi: 1) The Select -> Deselect menu entry was greyed out. The only way to fix it that we've found for now was Select -> Select All and then Select -> Deselect. I believe there are other ways, but I haven't found them yet (and I've never personally got this issue either). 2) If the file that appeared broken was saved and later opened in new Krita instance, it would be working again. So no, while it can still be a user error, it's not such an obvious one. I believe it can be related to switching focus (Qt does have a problem with it) or multiple displays (likewise), probably with input. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415106] Popup palette colour history is not always updated
https://bugs.kde.org/show_bug.cgi?id=415106 Lynx3d changed: What|Removed |Added CC||l...@aspect-design.de --- Comment #1 from Lynx3d --- I'm not sure if this is really the issue you're seeing, but I found something that can cause colors to not be added to the history. The popup palette seems to be the home of several ugly hacks, one even relies on patches in ext_qt as I recently found out. If it only happens when you make a stroke quickly after closing the palette, you're probably seeing the effect of this commit: https://invent.kde.org/kde/krita/commit/591684144731c0e8516bfd065fa812ff3e5f9c00 I honestly can't follow which issue this is supposed to fix, but basically it blocks the update of recently used colors for 0.75s (plus event loop latency, I assume) after closing the popup palette. Given that it's almost 10 years old, chances are the causes have been refactored at least once and it needs reevaluation. -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 414219] Google Drive access not working
https://bugs.kde.org/show_bug.cgi?id=414219 Nikita Tihiy changed: What|Removed |Added CC||sharky.ti...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412870] Tags on splits are not shown in ledger view
https://bugs.kde.org/show_bug.cgi?id=412870 Ralf Habacker changed: What|Removed |Added Version Fixed In|4.8.5,5.0.8 |4.8.5 Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kmy ||money/ee1dd19a9af84a18cc5cf ||fd0891bfd62eae43d2d Status|REOPENED|RESOLVED --- Comment #4 from Ralf Habacker --- Git commit ee1dd19a9af84a18cc5cffd0891bfd62eae43d2d by Ralf Habacker. Committed on 13/12/2019 at 00:00. Pushed by habacker into branch '4.8'. Fix display of tags in ledger Tags in splits were not displayed in the ledger view. FIXED-IN:4.8.5 M +57 -21 kmymoney/widgets/transaction.cpp M +6-4kmymoney/widgets/transaction.h https://commits.kde.org/kmymoney/ee1dd19a9af84a18cc5cffd0891bfd62eae43d2d -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 406403] Tags within Split transaction not reporting correctly
https://bugs.kde.org/show_bug.cgi?id=406403 --- Comment #5 from Ralf Habacker --- Git commit 9bc5781d057b58a8a8dc465fda542d004927a513 by Ralf Habacker. Committed on 13/12/2019 at 00:00. Pushed by habacker into branch '4.8'. Add support for showing tags on splits in tag report M +21 -35 kmymoney/reports/querytable.cpp https://commits.kde.org/kmymoney/9bc5781d057b58a8a8dc465fda542d004927a513 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 406403] Tags within Split transaction not reporting correctly
https://bugs.kde.org/show_bug.cgi?id=406403 Ralf Habacker changed: What|Removed |Added Version Fixed In|5.0.8 |4.8.5,5.0.8 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 415115] New: There is no settings for Kate visible by default
https://bugs.kde.org/show_bug.cgi?id=415115 Bug ID: 415115 Summary: There is no settings for Kate visible by default Product: kate Version: 19.08.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: pr...@ww.ee Target Milestone: --- SUMMARY Usually there is some kind of menu bar for programs... or if it is hidden by default then clicking or holding down Alt key will reveal it. There is NONE for Kate :-( STEPS TO REPRODUCE 1. Look for menu bar for Kate... 1.1. fail to see one by default 2. press Alt 2.1. Observe nothing happening. OBSERVED RESULT No menu bar anywhere ever. EXPECTED RESULT Visible menu bar with File, Edit, View, Settings, Help, etc. somewhere. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE (available in About System) KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412870] Tags on splits are not shown in ledger view
https://bugs.kde.org/show_bug.cgi?id=412870 Ralf Habacker changed: What|Removed |Added Ever confirmed|0 |1 Resolution|DUPLICATE |--- Summary|Tags on splits are not |Tags on splits are not |shown in ledger and tag |shown in ledger view |view| Status|RESOLVED|REOPENED --- Comment #3 from Ralf Habacker --- tag view display has been fixed with bug 412429; this bug is for the remaining ledger view. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415114] New: Crash when selecting on desktop and wallpaper changes at the same time
https://bugs.kde.org/show_bug.cgi?id=415114 Bug ID: 415114 Summary: Crash when selecting on desktop and wallpaper changes at the same time Product: plasmashell Version: 5.17.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: qr...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.4) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 5.0.0-37-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: I dragged a selection rectangle on the desktop. While dragging the desktop wallpaper changed and the crash occured. Desktop Wallpaper settings are as follows: Layout: Folder View Wallpaper Type: Slideshow Order: Random -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6571acb800 (LWP ))] Thread 27 (Thread 0x7f64ce9bf700 (LWP 325)): #0 0x7f65688359f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b2469486c4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f65688359f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55b246948670, cond=0x55b246948698) at pthread_cond_wait.c:502 #2 0x7f65688359f3 in __pthread_cond_wait (cond=0x55b246948698, mutex=0x55b246948670) at pthread_cond_wait.c:655 #3 0x7f656b904aeb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x55b246948670) at thread/qwaitcondition_unix.cpp:146 #4 0x7f656b904aeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x55b246671230, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f656b904df9 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x55b246671238, mutex=mutex@entry=0x55b246671230, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7f656f928ec8 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x55b246671228) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 0x7f656f928ec8 in QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x55b2466711b0) at scenegraph/qsgthreadedrenderloop.cpp:710 #8 0x7f656f9292fa in QSGRenderThread::run() (this=0x55b2466711b0) at scenegraph/qsgthreadedrenderloop.cpp:739 #9 0x7f656b8fdb52 in QThreadPrivate::start(void*) (arg=0x55b2466711b0) at thread/qthread_unix.cpp:360 #10 0x7f656882f6db in start_thread (arg=0x7f64ce9bf700) at pthread_create.c:463 #11 0x7f656b1fa88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7f64dd717700 (LWP 324)): #0 0x7f65688359f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b2469f5458) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f65688359f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55b2469f5408, cond=0x55b2469f5430) at pthread_cond_wait.c:502 #2 0x7f65688359f3 in __pthread_cond_wait (cond=0x55b2469f5430, mutex=0x55b2469f5408) at pthread_cond_wait.c:655 #3 0x7f65470d32bb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f65470d2eb7 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f656882f6db in start_thread (arg=0x7f64dd717700) at pthread_create.c:463 #6 0x7f656b1fa88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f64de54d700 (LWP 309)): #0 0x7f65688359f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b24677c290) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f65688359f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55b24677c240, cond=0x55b24677c268) at pthread_cond_wait.c:502 #2 0x7f65688359f3 in __pthread_cond_wait (cond=0x55b24677c268, mutex=0x55b24677c240) at pthread_cond_wait.c:655 #3 0x7f656b904aeb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x55b24677c240) at thread/qwaitcondition_unix.cpp:146 #4 0x7f656b904aeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x55b2466a2700, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f656b904df9 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x55b2466a2708, mutex=mutex@entry=0x55b2466a2700, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7f656f928ec8 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x55b2466a26f8) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 0x7f656f928ec8 in QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x55b2466a2680) at scenegraph/qsgthreadedrenderloop.cpp:710 #8 0x7f656f9292fa in QSGRenderThread::run()
[krunner] [Bug 415113] New: KRunner appears on Win+Space when not configured.
https://bugs.kde.org/show_bug.cgi?id=415113 Bug ID: 415113 Summary: KRunner appears on Win+Space when not configured. Product: krunner Version: 5.17.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: barafu.albino.chee...@gmail.com Target Milestone: --- SUMMARY KRunner appears when Win+Space pressed, even when not configured. In fact, I have set all KRunner shortcuts to None, and it still appears on Win + Space. Win + Space is a frequently used shortcut to change language on multilanguage Windows machines (There are only three options to choose from). This behaviour of KRunner prevents using the shortcut to change languages and having consistent behaviour between Windows and KDE for people that switch often. STEPS TO REPRODUCE 1. Disable all shortcuts for KRunner 2. Press Win + Space OBSERVED RESULT KRunner appears EXPECTED RESULT Nothing should happen. If shortcut is assigned to ketyboard layout switching, it should happen. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch, latest updates (available in About System) KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 415112] Blank notification appears on lid up on Wayland
https://bugs.kde.org/show_bug.cgi?id=415112 aidanwillie0...@gmail.com changed: What|Removed |Added CC||aidanwillie0317@protonmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 415112] New: Blank notification appears on lid up on Wayland
https://bugs.kde.org/show_bug.cgi?id=415112 Bug ID: 415112 Summary: Blank notification appears on lid up on Wayland Product: kscreenlocker Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: aidanwillie0...@protonmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY When running a Wayland session, after I raise the lid on my laptop, the login screen appears, however, in the area of the screen where notifications are configured to appear, there is what appears to be a notification with no decorations, no text, and no close button. It fades eventually, but often another one appears. This only occurs on lid up, as manually locking the screen doesn't produce this effect. This bug doesn't occur on X11. STEPS TO REPRODUCE 1. Run a Wayland session of plasma 2. Close laptop lid 3. Open laptop lid 4. Wake screen if needed OBSERVED RESULT A notification without text, icons, or interactive elements of any kind appears on the area of the screen where notifications would normally appear, fading out after an amount of time. Afterwards, additional boxes similar to this may appear sometimes as well. EXPECTED RESULT This element shouldn't be present. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.0.0-37-generic KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION My laptop is a Thinkpad T430. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 415111] New: Yakuake calculates it's size based on the smallest monitor in multi monitor setup
https://bugs.kde.org/show_bug.cgi?id=415111 Bug ID: 415111 Summary: Yakuake calculates it's size based on the smallest monitor in multi monitor setup Product: yakuake Version: 3.0.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: yanp.b...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Conncet two displays with different resolution 2. Width and height of a window depend on smallest display 3. OBSERVED RESULT Small uncentered window drops down on the larger screen EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: arch / 5.17 (available in About System) KDE Plasma Version: 5.17 KDE Frameworks Version: Qt Version: 5.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 233628] self signed SSL Certificate is not remembered (remember forever function)
https://bugs.kde.org/show_bug.cgi?id=233628 Octavian Petre changed: What|Removed |Added CC|octav...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 368287] Dolphin crashed while moving files to directory on NTFS/FAT file system owned by another user [KIO::FileCopyJob::slotResult]
https://bugs.kde.org/show_bug.cgi?id=368287 sac changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #44 from sac --- Seems it was just a HW failure on my side (faulty DVD drive which caused irritations). While this lead to BSODs in Windows in some situations, I guess a few applications crashes in Kubuntu are OK in those situations, although I can no longer reproduce it because I destroyed the faulty drive. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378910] System Tray forgets Dropbox hidden state after logout+login
https://bugs.kde.org/show_bug.cgi?id=378910 --- Comment #11 from Konrad Materka --- Will it work correctly with xembedsniproxy? Dropbox is broken, there is another bug report for context menu - they are not following specification there to. I guess we can implement a workaround, but this should be limited to Dropbox only - by default Id is working well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415107] Kwin crashes when launching Rainlendar
https://bugs.kde.org/show_bug.cgi?id=415107 Vlad Zahorodnii changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Vlad Zahorodnii --- Update kwin to 5.14.1. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 415110] New: Latte Dock crash on open
https://bugs.kde.org/show_bug.cgi?id=415110 Bug ID: 415110 Summary: Latte Dock crash on open Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mikesh...@gmail.com Target Milestone: --- Application: latte-dock (0.9.3) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-24-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - Unusual behavior I noticed: The dock crashes immediately when trying to run, no GUI appears The crash can be reproduced every time. -- Backtrace: Application: Latte Dock (latte-dock), signal: Bus error Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0bbb7c7c80 (LWP 20029))] Thread 5 (Thread 0x7f0ba156a700 (LWP 20040)): #0 0x7f0bbe1a72c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x55f6075c38d4) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f0bbe1a72c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55f6075c3880, cond=0x55f6075c38a8) at pthread_cond_wait.c:508 #2 0x7f0bbe1a72c6 in __pthread_cond_wait (cond=0x55f6075c38a8, mutex=0x55f6075c3880) at pthread_cond_wait.c:638 #3 0x7f0bbf193def in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0bbf193ee1 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0bc0e987b9 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f0bc0e98a1a in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f0bbf18dcc2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0bbe1a0669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f0bbeca9323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f0bb246e700 (LWP 20036)): #0 0x7f0bbec9cc2f in __GI___poll (fds=0x7f0ba80025e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0bbd7c3a3e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0bbd7c3b73 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0bbf3ac6c3 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0bbf35363b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0bbf18ca75 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0bc0b3d319 in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f0bbf18dcc2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0bbe1a0669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f0bbeca9323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f0bb99e8700 (LWP 20031)): #0 0x7f0bbd80fc60 in g_mutex_unlock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0bbd7c2fb1 in g_main_context_prepare () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0bbd7c396b in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0bbd7c3b73 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0bbf3ac6c3 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0bbf35363b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0bbf18ca75 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0bbf684efa in () at /lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f0bbf18dcc2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f0bbe1a0669 in start_thread (arg=) at pthread_create.c:479 #10 0x7f0bbeca9323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f0bba92f700 (LWP 20030)): #0 0x7f0bbec9cc2f in __GI___poll (fds=0x7f0bba92eca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0bc12a7917 in () at /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f0bc12a953a in xcb_wait_for_event () at /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f0bbb112288 in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f0bbf18dcc2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0bbe1a0669 in start_thread (arg=) at pthread_create.c:479 #6 0x7f0bbeca9323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f0bbb7c7c80 (LWP 20029)): [KCrash Handler] #5 0x7f0bbed091b0 in __strncmp_sse42 () at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:199 #6 0x7f0bbfdef9b3 in () at /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #7 0x7f0bbfdec42b in KSharedDataCache::find(QString const&, QByteArray*) const () at /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #8 0x7f0bc123c154 in
[kio-gdrive] [Bug 415089] Dolphin Kio-gdrive authentication with Google account fails
https://bugs.kde.org/show_bug.cgi?id=415089 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 414219] Google Drive access not working
https://bugs.kde.org/show_bug.cgi?id=414219 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 415056] Kmail pretends to be done retrieving emails
https://bugs.kde.org/show_bug.cgi?id=415056 --- Comment #3 from Attila --- (In reply to Christophe Giboudeaux from comment #2) > which account type is it? pop3, imap... It is pop3 > Did you create filters? Yes I did -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 414564] Update of bank account data aborted
https://bugs.kde.org/show_bug.cgi?id=414564 Ralf Habacker changed: What|Removed |Added CC||ralf.habac...@freenet.de --- Comment #10 from Ralf Habacker --- (In reply to Stefan Hohrein from comment #9) > Hi, is there a plan to create a WIN10 version greater than 4.8.4? There are unstable version for windows at https://download.kde.org/unstable/kmymoney/ with latest kmymoney, gwenhywfar and aqbanking snapshots. See the folder with the latest date. > Currently kmymoney doesn't work and is of no use. That sounds pretty drastic. Does this statement refer to the whole program or just online banking ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402894] Display of original image
https://bugs.kde.org/show_bug.cgi?id=402894 Maik Qualmann changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/b90554b02110 ||58d499ce720b761d2d376ede041 ||7 Version Fixed In||7.0.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #14 from Maik Qualmann --- Git commit b90554b0211058d499ce720b761d2d376ede0417 by Maik Qualmann. Committed on 12/12/2019 at 20:55. Pushed by mqualmann into branch 'master'. the function to show / hide the original image already exists, draw the icon larger in the versioning view FIXED-IN: 7.0.0 M +2-1NEWS M +10 -9core/libs/properties/history/versionsoverlays.cpp https://invent.kde.org/kde/digikam/commit/b90554b0211058d499ce720b761d2d376ede0417 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 414195] Deselecting all fields on BibTeX Viewer hides the field sorting header
https://bugs.kde.org/show_bug.cgi?id=414195
Thomas Fischer changed:
What|Removed |Added
Latest Commit|c93ab89b16a5dc3588bd22e0d12 |9a6182af10b54e4f1150c7d7c16
|a1b6419cf431d |fe745f5fb9b04
--- Comment #5 from Thomas Fischer ---
(In reply to Thomas Fischer from comment #3)
> 2. Run as: bash run-kbibtex.sh
> https://anongit.kde.org/clones/kbibtex/thomasfischer/kbibtex.git
> bugs/kde123456
Sorry, there was a typo in above URL ("123456", should have been the bug
number).
So, please try to run this here:
bash run-kbibtex.sh
https://anongit.kde.org/clones/kbibtex/thomasfischer/kbibtex.git bugs/kde414195
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 414227] Dolphin crashes in KFileMetaData::UserMetaData::queryAttributes() when retrieving metadata from dangling symlink
https://bugs.kde.org/show_bug.cgi?id=414227 Nate Graham changed: What|Removed |Added Version Fixed In||5.66 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 414227] Dolphin crashes in KFileMetaData::UserMetaData::queryAttributes() when retrieving metadata from dangling symlink
https://bugs.kde.org/show_bug.cgi?id=414227 Ismael Asensio changed: What|Removed |Added Latest Commit||https://commits.kde.org/kfi ||lemetadata/4bb4195a6fc6841d ||d9ce1d3f564fc122b6032d86 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Ismael Asensio --- Git commit 4bb4195a6fc6841dd9ce1d3f564fc122b6032d86 by Ismael Asensio. Committed on 12/12/2019 at 20:50. Pushed by iasensio into branch 'master'. xattr: fix crash on dangling symlinks Summary: When requesting metadata on a dangling symlink, the framestack ends up calling `k_queryAttributes()` with the symlink path, where the `listxattr` syscall returns `size==-1` and `errno==ENOENT` (No such file or directory). This case was not covered before, and provoked a segfault on `QByteArray`. Full traceback on: https://bugs.kde.org/show_bug.cgi?id=414227 It might be also a good idea to always protect the function when `size==-1` Test Plan: - `bin/usermetadatawritertest` : added test - On dolphin, with panel information open, hover over a dangling symlink Reviewers: astippich, bruns Reviewed By: bruns Subscribers: bruns, kde-frameworks-devel, #baloo Tags: #frameworks, #baloo Differential Revision: https://phabricator.kde.org/D25414 M +11 -0autotests/usermetadatawritertest.cpp M +1-0autotests/usermetadatawritertest.h M +6-6src/xattr_p.h https://commits.kde.org/kfilemetadata/4bb4195a6fc6841dd9ce1d3f564fc122b6032d86 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406296] [Dolphin] Inconsistent sort order
https://bugs.kde.org/show_bug.cgi?id=406296 --- Comment #7 from Nate Graham --- Thank you very much! I'll take a look. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368430] Expose option to disable grouping in Icons-only Task Manager
https://bugs.kde.org/show_bug.cgi?id=368430
Nate Graham changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
Version Fixed In||5.18.0
Latest Commit||https://commits.kde.org/pla
||sma-desktop/5174aa9e1a29fa6
||cb82cd67b33e67827e9ba066e
--- Comment #11 from Nate Graham ---
Git commit 5174aa9e1a29fa6cb82cd67b33e67827e9ba066e by Nate Graham, on behalf
of Björn Feber.
Committed on 12/12/2019 at 20:48.
Pushed by ngraham into branch 'master'.
Add grouping and "Show Only Minimized" options to icons-only task manager
Summary:
FIXED-IN: 5.18.0
Being able to disable grouping for the icons-only task manager makes sense,
because it has enough space to hold plenty of application icons/launchers. The
"Show only tasks that are minimized" option is useful as well for the IOTM.
{F7258179}
Test Plan: Open the IOTM behavior settings page. Enable/disable grouping and
toggle the "Show only tasks that are minimized" option.
Reviewers: #plasma, #vdg, ngraham
Reviewed By: #vdg, ngraham
Subscribers: ngraham, hein, #vdg, plasma-devel, #plasma
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D23242
M +0-2applets/taskmanager/package/contents/ui/ConfigBehavior.qml
M +1-2applets/taskmanager/package/contents/ui/main.qml
https://commits.kde.org/plasma-desktop/5174aa9e1a29fa6cb82cd67b33e67827e9ba066e
--
You are receiving this mail because:
You are watching all bug changes.
[kde] [Bug 415109] Latte Dock crash when opening settings
https://bugs.kde.org/show_bug.cgi?id=415109 DarnedDev changed: What|Removed |Added CC||mikesh...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 415109] New: Latte Dock crash when opening settings
https://bugs.kde.org/show_bug.cgi?id=415109 Bug ID: 415109 Summary: Latte Dock crash when opening settings Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mikesh...@gmail.com Target Milestone: --- Application: latte-dock (0.9.3) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-24-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - Unusual behavior I noticed: The dock froze and crashed when displaying the settings panel. Relaunching the app is impossible without a restart, after one - the crash repeats The crash can be reproduced every time. -- Backtrace: Application: Latte Dock (latte-dock), signal: Bus error Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8291a83c80 (LWP 2055))] Thread 5 (Thread 0x7f8277815700 (LWP 2071)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x559923bb2c24) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x559923bb2bd0, cond=0x559923bb2bf8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x559923bb2bf8, mutex=0x559923bb2bd0) at pthread_cond_wait.c:638 #3 0x7f829544fdef in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f829544fee1 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f82971547b9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f8297154a1a in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f8295449cc2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f829445c669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f8294f65323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f8283fff700 (LWP 2066)): #0 0x7f8293a7c58d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f8293a7dbac in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8293a7eefb in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8293a7f96b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8293a7fb73 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f82956686c3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f829560f63b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f8295448a75 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f8296df9319 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f8295449cc2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f829445c669 in start_thread (arg=) at pthread_create.c:479 #11 0x7f8294f65323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f828bcbe700 (LWP 2059)): #0 __GI___libc_read (nbytes=16, buf=0x7f828bcbdb60, fd=7) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=7, buf=0x7f828bcbdb60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f8293ac763f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8293a7f58e in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8293a7f9e2 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f8293a7fb73 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f82956686c3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f829560f63b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f8295448a75 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f8295940efa in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7f8295449cc2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f829445c669 in start_thread (arg=) at pthread_create.c:479 #12 0x7f8294f65323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f8290beb700 (LWP 2057)): #0 0x7f8294f58c2f in __GI___poll (fds=0x7f8290beaca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f8297563917 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f829756553a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f82913d3288 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f8295449cc2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f829445c669 in start_thread (arg=) at pthread_create.c:479 #6 0x7f8294f65323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
[kmymoney] [Bug 414564] Update of bank account data aborted
https://bugs.kde.org/show_bug.cgi?id=414564 --- Comment #9 from Stefan Hohrein --- Hi, is there a plan to create a WIN10 version greater than 4.8.4? Currently kmymoney doesn't work and is of no use. Regards Stefan Hohrein -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415108] New: Plasma crash on initialization of Latte Dock
https://bugs.kde.org/show_bug.cgi?id=415108 Bug ID: 415108 Summary: Plasma crash on initialization of Latte Dock Product: plasmashell Version: 5.16.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mikesh...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.5) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-24-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: Trying to set up Latte Dock - Unusual behavior I noticed: When trying to switch to the taskbar system to Latte Dock, Plasma took way too long to restart - hanging at black screen for a bit over a minute - Custom settings of the application: Latte Dock from the official PPA -- Backtrace: Application: Plasma (plasmashell), signal: Bus error Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa2b5978880 (LWP 1619))] Thread 14 (Thread 0x7fa24ba3e700 (LWP 8239)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55e2c88d7780) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55e2c88d7730, cond=0x55e2c88d7758) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55e2c88d7758, mutex=0x55e2c88d7730) at pthread_cond_wait.c:638 #3 0x7fa2b9219def in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa2b9219ee1 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa2bb0327b9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fa2bb032a1a in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fa2b9213cc2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa2b8696669 in start_thread (arg=) at pthread_create.c:479 #9 0x7fa2b8e98323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7fa27d0fb700 (LWP 6999)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55e2c86bfdb4) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55e2c86bfd60, cond=0x55e2c86bfd88) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55e2c86bfd88, mutex=0x55e2c86bfd60) at pthread_cond_wait.c:638 #3 0x7fa2b9219def in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa2b9219ee1 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa2bb0327b9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fa2bb032a1a in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fa2b9213cc2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa2b8696669 in start_thread (arg=) at pthread_create.c:479 #9 0x7fa2b8e98323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7fa27d8fc700 (LWP 6998)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55e2c75c48e4) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55e2c75c4890, cond=0x55e2c75c48b8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55e2c75c48b8, mutex=0x55e2c75c4890) at pthread_cond_wait.c:638 #3 0x7fa2b9219def in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa2b9219ee1 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa2bb0327b9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fa2bb032a1a in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fa2b9213cc2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa2b8696669 in start_thread (arg=) at pthread_create.c:479 #9 0x7fa2b8e98323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7fa27eafd700 (LWP 5155)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55e2c7a6bee0) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55e2c7a6be90, cond=0x55e2c7a6beb8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55e2c7a6beb8, mutex=0x55e2c7a6be90) at pthread_cond_wait.c:638 #3 0x7fa2b9219def in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa2b9219ee1 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa2bb0327b9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6
[kscreenlocker] [Bug 413103] Slideshow on screenlocker shows same image on all monitors
https://bugs.kde.org/show_bug.cgi?id=413103 --- Comment #1 from Paul Lemmons --- Problem persists in: KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 413367] Columns width cannot be changed by users.
https://bugs.kde.org/show_bug.cgi?id=413367 Thomas Fischer changed: What|Removed |Added Latest Commit|6d1cda2ce8d3c16d929a7cde969 |7a228841e508a628c4bb8ee4623 |eb648e47a2c30 |1555c7d4bcb0d --- Comment #4 from Thomas Fischer --- (In reply to Thomas Fischer from comment #2) > Have you had the chance to test the proposed fix as explained in comment #1? > Please let me know if that fixed the problem for you. I have updated further this patch, addressing minor issues when moving columns and later resetting those move operations. https://commits.kde.org/clones/kbibtex/thomasfischer/kbibtex/7a228841e508a628c4bb8ee46231555c7d4bcb0d Please test and confirm whether this issue can be closed. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 387850] Have to enter password multiple times for screen to unlock
https://bugs.kde.org/show_bug.cgi?id=387850 Paul Lemmons changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Paul Lemmons --- I do not know when this got resolved but it is no longer a problem -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415094] sddm session combobox wrong colors
https://bugs.kde.org/show_bug.cgi?id=415094 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- I just added a manual test for PC3 combobox in p-f. Should make fixing this faster. (also we should address all issues from that test suite before going ahead porting stuff) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414849] Pager doesn't show windows of second screen anymore
https://bugs.kde.org/show_bug.cgi?id=414849 Paul Lemmons changed: What|Removed |Added CC||paul.lemm...@tmcaz.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415107] New: Kwin crashes when launching Rainlendar
https://bugs.kde.org/show_bug.cgi?id=415107 Bug ID: 415107 Summary: Kwin crashes when launching Rainlendar Product: kwin Version: 5.14.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: gijsb...@rondte.nl Target Milestone: --- Application: kwin_x11 (5.14.0) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.15.0-72-generic x86_64 Distribution: Ubuntu 16.04.6 LTS -- Information about the crash: - What I was doing when the application crashed: just launched Rainlendar2 (2.14.3 - beta) Apart from that various other applications were open: Firefox, Vivaldi, Deezer (on Nuvola app), Telegram Desktop, Thunderbird. Nothing else was done, but launching Rainlendar, which was just installed from .deb file. The same happened when launching Rainlendar 2.15 just after having installed it the other day. The crash can be reproduced every time. -- 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 0x7f279c0aa940 (LWP 2677))] Thread 6 (Thread 0x7f268d80b700 (LWP 10198)): #0 0x7f279bac1811 in __GI_ppoll (fds=fds@entry=0x7f27600201e8, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50 #1 0x7f2798e71b21 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f27600201e8) at kernel/qcore_unix.cpp:112 #3 qt_safe_poll (fds=0x7f27600201e8, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:133 #4 0x7f2798e731b2 in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7f2798e1d5ba in QEventLoop::exec (this=this@entry=0x7f268d80ac50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7f2798c525e4 in QThread::exec (this=this@entry=0x9436430) at thread/qthread.cpp:525 #7 0x7f27937a0195 in QQmlThreadPrivate::run (this=0x9436430) at qml/ftw/qqmlthread.cpp:148 #8 0x7f2798c5d727 in QThreadPrivate::start (arg=0x9436430) at thread/qthread_unix.cpp:367 #9 0x7f2794b036ba in start_thread (arg=0x7f268d80b700) at pthread_create.c:333 #10 0x7f279bacd41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f2767fff700 (LWP 3391)): #0 0x7f279bac1811 in __GI_ppoll (fds=fds@entry=0x7f26dc037608, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50 #1 0x7f2798e71b21 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f26dc037608) at kernel/qcore_unix.cpp:112 #3 qt_safe_poll (fds=0x7f26dc037608, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:133 #4 0x7f2798e731b2 in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7f2798e1d5ba in QEventLoop::exec (this=this@entry=0x7f2767ffec50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7f2798c525e4 in QThread::exec (this=this@entry=0x125f0b0) at thread/qthread.cpp:525 #7 0x7f27937a0195 in QQmlThreadPrivate::run (this=0x125f0b0) at qml/ftw/qqmlthread.cpp:148 #8 0x7f2798c5d727 in QThreadPrivate::start (arg=0x125f0b0) at thread/qthread_unix.cpp:367 #9 0x7f2794b036ba in start_thread (arg=0x7f2767fff700) at pthread_create.c:333 #10 0x7f279bacd41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f2771801700 (LWP 3177)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2797d9fde4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f2797d9fe29 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f2794b036ba in start_thread (arg=0x7f2771801700) at pthread_create.c:333 #4 0x7f279bacd41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f2772e1d700 (LWP 3146)): #0 0x7f279bac1811 in __GI_ppoll (fds=fds@entry=0x7f2768000ac8, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50 #1 0x7f2798e71b21 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f2768000ac8) at kernel/qcore_unix.cpp:112 #3 qt_safe_poll (fds=0x7f2768000ac8, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:133 #4 0x7f2798e731b2 in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7f2798e1d5ba in
[frameworks-kio] [Bug 412486] Dropdown menu in "Open File..." dialog in Vlc shows file that doesn't exist anymore
https://bugs.kde.org/show_bug.cgi?id=412486 mthw0 changed: What|Removed |Added Version|5.62.0 |5.64.0 CC||matejm98m...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 412853] Download/Upload speed is sorted upside down
https://bugs.kde.org/show_bug.cgi?id=412853 mthw0 changed: What|Removed |Added CC||matejm98m...@gmail.com Version|5.16.90 |5.17.4 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414630] shortcut bug in caption (tag)
https://bugs.kde.org/show_bug.cgi?id=414630 Maik Qualmann changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 413634] ARMv8.1 arithmetic instructions are not supported
https://bugs.kde.org/show_bug.cgi?id=413634 --- Comment #1 from ahashmi --- Created attachment 124454 --> https://bugs.kde.org/attachment.cgi?id=124454=edit Patch implements and tests ARM v8.1 SIMD instructions This patch adds support for AArch64 ARMv8.1 SIMD instructions: SQRDMLAH , , SQRDMLAH ., ., . SQRDMLAH , , .[] SQRDMLAH ., ., .[] SQRDMLSH , , SQRDMLSH ., ., . SQRDMLSH , , .[] SQRDMLSH ., ., .[] -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415103] "Preview on mouse-over" setting is not saved
https://bugs.kde.org/show_bug.cgi?id=415103 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 414902 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414902] After using the "healing clone" tool only preview is available from other tools
https://bugs.kde.org/show_bug.cgi?id=414902 Maik Qualmann changed: What|Removed |Added CC||antonio.angelo@protonmail.c ||om --- Comment #4 from Maik Qualmann --- *** Bug 415103 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415103] "Preview on mouse-over" setting is not saved
https://bugs.kde.org/show_bug.cgi?id=415103 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- It is not the Curves or Blure tool that deactivates the mouse over mode, but the Healing Clone tool. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415106] New: Popup palette colour history is not always updated
https://bugs.kde.org/show_bug.cgi?id=415106 Bug ID: 415106 Summary: Popup palette colour history is not always updated Product: krita Version: 4.2.8 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: ahab.greybe...@hotmail.co.uk Target Milestone: --- Created attachment 124453 --> https://bugs.kde.org/attachment.cgi?id=124453=edit Popup Palette colour history failure - example SUMMARY This has been seen on the 4.2.8 and 4.3.0 Dec 09 prealpha appimages and the 4.3.0 Dec 10 prealpha Windows portable zip. I've tried in on the 4.2.6 and 4.2.7.1 appimages and not seen it happen but it's intermittent. STEPS TO REPRODUCE 1. Start krita and create a new image. 2. Right click to bring up the popup palette. Note that the colour history ring is empty. 3. Choose a paint colour from the wheel then a shade from the triangle. 4. Paint a stroke with this colour. 5. Open the popup palette and note that the colour has been added to the history ring. 6. Repeat for different colours to populate the history ring. 7. Note that the colour is not always added to the history ring. OBSERVED RESULT See screenshot attached. Six different colours have been selected and used (using the mouse) but only four were added to the history ring. On one test, colours were often not added for several different sequential colours, then selecting a different brush preset from the palette and using it caused the colour to be added. Further selected colours were not added until I selected another different brush. This scenario only happened once as I was investigating the behaviour. It is intermittent. EXPECTED RESULT Each colour should be added to the history ring SOFTWARE/OS VERSIONS Krita Version: 4.2.8 Languages: en_GB, en Hidpi: true Qt Version (compiled): 5.12.5 Version (loaded): 5.12.5 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.19.0-6-amd64 Pretty Productname: Debian GNU/Linux 10 (buster) Product Type: debian Product Version: 10 OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "GeForce GTX 750 Ti/PCIe/SSE2" Version: "4.6.0 NVIDIA 418.74" Shading language: "4.60 NVIDIA" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 4.6, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Version: 4.6 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false Hardware Information GPU Acceleration: auto Memory: 16039 Mb Number of Cores: 8 Swap Location: /tmp Current Settings Current Swap Location: /tmp Undo Enabled: 1 Undo Stack Limit: 18 Use OpenGL: 1 Use OpenGL Texture Buffer: 1 Use AMD Vectorization Workaround: 0 Canvas State: OPENGL_SUCCESS Autosave Interval: 360 Use Backup Files: 1 Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Use Win8 Pointer Input: 0 Use RightMiddleTabletButton Workaround: 0 Levels of Detail Enabled: 0 Use Zip64: 0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415103] "Preview on mouse-over" setting is not saved
https://bugs.kde.org/show_bug.cgi?id=415103 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |ImageEditor -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415103] "Preview on mouse-over" setting is not saved
https://bugs.kde.org/show_bug.cgi?id=415103 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Setting "Preview on |"Preview on mouse-over" |mouse-over" is not |setting is not saved |mantained. | CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 415105] Discover crush on start
https://bugs.kde.org/show_bug.cgi?id=415105 c4rb0n_u...@protonmail.com changed: What|Removed |Added CC||c4rb0n_u...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381656] No "audio being played" indicator for many icon sizes
https://bugs.kde.org/show_bug.cgi?id=381656 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 415105] New: Discover crush on start
https://bugs.kde.org/show_bug.cgi?id=415105 Bug ID: 415105 Summary: Discover crush on start Product: Discover Version: 5.12.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: c4rb0n_u...@protonmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.12.8) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 5.0.0-37-generic x86_64 Distribution: Ubuntu 18.04.3 LTS -- Information about the crash: App just crashed on start, no window showed up even. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f226a1ab800 (LWP 8))] Thread 11 (Thread 0x7f9e0700 (LWP 22244)): #0 0x7f225ff6a515 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f225ff6ca63 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f225ff6d4fb in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f225ff6d6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f22660c499b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f22660699fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2265e8823a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2265e8d17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f226209b6db in start_thread (arg=0x7f9e0700) at pthread_create.c:463 #9 0x7f22657f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f22237fe700 (LWP 22243)): #0 0x7f22620a1ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f22237fdc40, expected=0, futex_word=0x7f221c0042f0) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f22620a1ed9 in __pthread_cond_wait_common (abstime=0x7f22237fdd00, mutex=0x7f221c0042a0, cond=0x7f221c0042c8) at pthread_cond_wait.c:533 #2 0x7f22620a1ed9 in __pthread_cond_timedwait (cond=0x7f221c0042c8, mutex=0x7f221c0042a0, abstime=0x7f22237fdd00) at pthread_cond_wait.c:667 #3 0x7f2265e8e468 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f2265e8a53d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2265e8d17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f226209b6db in start_thread (arg=0x7f22237fe700) at pthread_create.c:463 #7 0x7f22657f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f2223fff700 (LWP 22242)): #0 0x7f22620a19f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f221c023c70) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f22620a19f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f221c023c20, cond=0x7f221c023c48) at pthread_cond_wait.c:502 #2 0x7f22620a19f3 in __pthread_cond_wait (cond=0x7f221c023c48, mutex=0x7f221c023c20) at pthread_cond_wait.c:655 #3 0x7f2265e8e5ab in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f2265e86c1b in QSemaphore::acquire(int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f226609a958 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f22636fbdf2 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #7 0x7f22636fcd4c in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #8 0x7f226609a645 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f22636faeb2 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #10 0x7f226365c23f in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7f226365d6cc in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #12 0x7f226609a645 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f22636cfdd2 in QSslSocket::preSharedKeyAuthenticationRequired(QSslPreSharedKeyAuthenticator*) () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #14 0x7f22636f3cdc in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #15 0x7f22304fd156 in () at /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #16 0x7f22304fb2eb in () at /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #17 0x7f223050524e in () at /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #18 0x7f2230504147 in () at /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #19 0x7f22304f04c4 in SSL_do_handshake () at /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #20 0x7f22636f410d in () at
[klipper] [Bug 409366] Clearing clipboard history does not clear the clipboard
https://bugs.kde.org/show_bug.cgi?id=409366 popov895 changed: What|Removed |Added CC||popov...@ukr.net -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415104] New: System settings crashed when printing canceled
https://bugs.kde.org/show_bug.cgi?id=415104 Bug ID: 415104 Summary: System settings crashed when printing canceled Product: systemsettings Version: 5.17.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dukeallo...@yandex.ru Target Milestone: --- Application: systemsettings5 (5.17.4) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 5.4.2-arch1-1 x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I accidently clicked on button "Print" in Task planner tab after creating new task. When I canceled printing, System setting crashed. -- Backtrace: Application: Параметры системы (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3a265cb800 (LWP 1606))] Thread 9 (Thread 0x7f3a06d22700 (LWP 1627)): #0 0x7f3a2aaf342c in read () at /usr/lib/libc.so.6 #1 0x7f3a06394752 in pa_read () at /usr/lib/pulseaudio/libpulsecommon-13.0.so #2 0x7f3a063f8f8f in pa_mainloop_prepare () at /usr/lib/libpulse.so.0 #3 0x7f3a063f92f1 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7f3a063f93b1 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7f3a063e961e in () at /usr/lib/libpulse.so.0 #6 0x7f3a0636dd1c in () at /usr/lib/pulseaudio/libpulsecommon-13.0.so #7 0x7f3a296d04cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f3a2ab022d3 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f3a07523700 (LWP 1618)): #0 0x7f3a2aaf342c in read () at /usr/lib/libc.so.6 #1 0x7f3a28a869f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f3a28ad49e1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f3a28ad60c8 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f3a28ad70c3 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #5 0x7f3a07e4dbc8 in () at /usr/lib/libgio-2.0.so.0 #6 0x7f3a28ab2bb1 in () at /usr/lib/libglib-2.0.so.0 #7 0x7f3a296d04cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f3a2ab022d3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f3a07d24700 (LWP 1617)): #0 0x7f3a28a86479 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f3a28ad4147 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #2 0x7f3a28ad61b1 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f3a28ad61f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f3a28ad6242 in () at /usr/lib/libglib-2.0.so.0 #5 0x7f3a28ab2bb1 in () at /usr/lib/libglib-2.0.so.0 #6 0x7f3a296d04cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f3a2ab022d3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f3a0eb07700 (LWP 1613)): #0 0x7f3a28acd62f in g_source_ref () at /usr/lib/libglib-2.0.so.0 #1 0x7f3a28ad4662 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f3a28ad593b in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #3 0x7f3a28ad6046 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f3a28ad61f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f3a2b09cb2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f3a2b04383c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f3a2ae75305 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f3a2a17d449 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f3a2ae76530 in () at /usr/lib/libQt5Core.so.5 #10 0x7f3a296d04cf in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f3a2ab022d3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f3a1cbc3700 (LWP 1612)): #0 0x7f3a28ad47a2 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #1 0x7f3a28ad60c8 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f3a28ad61f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f3a2b09cb2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f3a2b04383c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f3a2ae75305 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f3a2a17d449 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f3a2ae76530 in () at /usr/lib/libQt5Core.so.5 #8 0x7f3a296d04cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f3a2ab022d3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f3a1d709700 (LWP 1610)): #0 0x7f3a296d6c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3a1ddba60c in () at /usr/lib/dri/i965_dri.so #2 0x7f3a1ddba208 in () at /usr/lib/dri/i965_dri.so #3 0x7f3a296d04cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f3a2ab022d3 in clone () at
[dolphin] [Bug 406296] [Dolphin] Inconsistent sort order
https://bugs.kde.org/show_bug.cgi?id=406296 gvgeo changed: What|Removed |Added CC||gv...@protonmail.com --- Comment #6 from gvgeo --- Made a patch D25741. Although I feel it could take an improvement. https://phabricator.kde.org/D25741 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 183429] open externally called folder in new tab
https://bugs.kde.org/show_bug.cgi?id=183429 --- Comment #33 from andydecle...@gmail.com --- Can we get this to work when no paths are provided to dolphin, such as when launching via a menu, dock, panel, krunner, or global shortcut? The implicit path is whatever dolphin's open-at-launch path is. I was looking forward to this feature but had no idea it was implemented, because its activation conditions overlap with my usage either very little or not at all. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381656] No "audio being played" indicator for many icon sizes
https://bugs.kde.org/show_bug.cgi?id=381656 gvgeo changed: What|Removed |Added CC||gv...@protonmail.com --- Comment #11 from gvgeo --- Made a patch D25925. Although not perfect, should be an improvement. https://phabricator.kde.org/D25925 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 267916] Dolphin User-Defined Tools/Services and configuration
https://bugs.kde.org/show_bug.cgi?id=267916 --- Comment #4 from andydecle...@gmail.com --- The patch is still working fine as of dolphin 19.12.0, if anyone's interested. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 410741] [Wayland] Plasma froze after I hover over entries of the task manager and icons in systray
https://bugs.kde.org/show_bug.cgi?id=410741 --- Comment #2 from Patrick Silva --- it happened again after upgrade to Qt 5.14 Operating System: Arch Linux KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.14.0 -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 233628] self signed SSL Certificate is not remembered (remember forever function)
https://bugs.kde.org/show_bug.cgi?id=233628 --- Comment #76 from Hans-Peter Jansen --- Created attachment 124452 --> https://bugs.kde.org/attachment.cgi?id=124452=edit 6 minutes after akonadi start without confirming these requests Needless to say, that these requests must *all* be answered for the same host. That issue exists since the beginning of time (I remember confirming piles of such dialogs in the past (in KDE4 times..). If you need more details or want me to do some tests, let me know. I'm ready and prepared to apply patches, if you can point me to some commits or diffs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414251] SDDM theme: keyboard layout does not respect locale during first login
https://bugs.kde.org/show_bug.cgi?id=414251 --- Comment #7 from severin.k...@gmail.com --- (In reply to David Edmundson from comment #6) > How are you setting the keyboard layout? I'm not sure if I understand what you mean with "how". I have beeetting it during the installation process, or if that didn't work with the GUI settings. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414251] SDDM theme: keyboard layout does not respect locale during first login
https://bugs.kde.org/show_bug.cgi?id=414251 David Edmundson changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO --- Comment #6 from David Edmundson --- How are you setting the keyboard layout? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414957] Unable to Open program
https://bugs.kde.org/show_bug.cgi?id=414957 --- Comment #9 from Asuna --- Created attachment 124451 --> https://bugs.kde.org/attachment.cgi?id=124451=edit %localappdata% These are the only files that show for krita under the %localappdata% file extention -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 414544] Icon does not respect the theme: black on black
https://bugs.kde.org/show_bug.cgi?id=414544 Kai Uwe Broulik changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Kai Uwe Broulik --- While you can provide a theme icon in the app for dark theme, you cannot then override it programmatically. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408125] Mouseover popups flicker with white version of breeze.
https://bugs.kde.org/show_bug.cgi?id=408125 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #4 from Nate Graham --- Not likely to be an issue with the Breeze theme itself. Can you reproduce this with Breeze Dark or when using a different Plasma theme? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356165] Theme misses any kinds of edges in non-compositting mode
https://bugs.kde.org/show_bug.cgi?id=356165 Nate Graham changed: What|Removed |Added Status|REOPENED|RESOLVED CC||n...@kde.org Resolution|--- |FIXED --- Comment #13 from Nate Graham --- Yup, fixed now. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 414993] Low contrast for selection with light gray text on Breeze dark at Network manager
https://bugs.kde.org/show_bug.cgi?id=414993 Nate Graham changed: What|Removed |Added Assignee|visual-des...@kde.org |jgrul...@redhat.com Target Milestone|1.0 |--- Status|REPORTED|CONFIRMED Product|plasmashell |plasma-nm Ever confirmed|0 |1 Component|Theme - Breeze |applet Keywords||usability --- Comment #1 from Nate Graham --- Really this is a bug in the network manager on two points: - It should not use super transparent text here - It should draw the hover highlight over the expanded area when expanded Let's fix it there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414251] SDDM theme: keyboard layout does not respect locale during first login
https://bugs.kde.org/show_bug.cgi?id=414251 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414957] Unable to Open program
https://bugs.kde.org/show_bug.cgi?id=414957 Asuna changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED Assignee|krita-bugs-n...@kde.org |riceri...@gmail.com --- Comment #8 from Asuna --- Created attachment 124450 --> https://bugs.kde.org/attachment.cgi?id=124450=edit Issue came back Issue back back again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 336457] Vertical alignment is off when some expanded indicator is not visible
https://bugs.kde.org/show_bug.cgi?id=336457 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED CC||n...@kde.org --- Comment #23 from Nate Graham --- This is no longer an issue today. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354644] Breeze dark seems to have white edges on a maximized panel
https://bugs.kde.org/show_bug.cgi?id=354644 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED CC||n...@kde.org Status|REOPENED|RESOLVED --- Comment #7 from Nate Graham --- No longer an issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381960] Icons of widgets placed in the panel change according panel height
https://bugs.kde.org/show_bug.cgi?id=381960 Nate Graham changed: What|Removed |Added Latest Commit||https://cgit.kde.org/plasma ||-framework.git/commit/?id=e ||44cab6ab55bb7ca832815305156 ||45ef46eef6a7 Status|CONFIRMED |RESOLVED Version Fixed In||5.66 Resolution|--- |FIXED --- Comment #13 from Nate Graham --- Fixed for Show Desktop and Minimize All by https://cgit.kde.org/plasma-framework.git/commit/?id=e44cab6ab55bb7ca83281530515645ef46eef6a7 recently! For any others, please file separate bugs against Plasmashell | Theme - Breeze. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 361419] Unaccepted Google calendar events not shown
https://bugs.kde.org/show_bug.cgi?id=361419 --- Comment #9 from Miikka --- Correction to my comment above: Looks like all meeting requests are missing (accepted, unaccepted) from my calendar. They are fetched OK because I'm able to see them from Akonadi Console but Korganizer isn't showing them but Kontact's Summary / front page is showing them. The only exception is Meeting requests created by myself: they're showing OK in Korganizer. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 413835] Application window flickers when focus is on a DATE field
https://bugs.kde.org/show_bug.cgi?id=413835 --- Comment #4 from schoenes-...@web.de --- I found two ways to circumvent the described behaviour. The screen will NOT flicker when FEDORA is being started with either the GNOME ON XORG or the XFCE SESSION desktop selection (see enclosed image of login options available). Consider my bug report as "works for me", however I think that KMyMoney with the GNOME environment should be inspected for the described phenomenon. -nothing follows- -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 413835] Application window flickers when focus is on a DATE field
https://bugs.kde.org/show_bug.cgi?id=413835 --- Comment #3 from schoenes-...@web.de --- Created attachment 124449 --> https://bugs.kde.org/attachment.cgi?id=124449=edit Screenshot of FEDORA Desktop login options details see comment -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 233628] self signed SSL Certificate is not remembered (remember forever function)
https://bugs.kde.org/show_bug.cgi?id=233628 --- Comment #75 from Hans-Peter Jansen --- Tumbleweed tends to be pretty current: kio: 5.64.0 kimap: 19.08.3 These are the related projects: https://build.opensuse.org/package/show/openSUSE:Factory/kio https://build.opensuse.org/package/show/openSUSE:Factory/kimap The build logs are available in the block. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 361764] Cannot add event to calendar with correct time: Add event window will not accept an "A.M." time
https://bugs.kde.org/show_bug.cgi?id=361764 --- Comment #26 from safe...@gmx.com --- Thankyou Filipus for replying. Here is what appears to be working. System Settings / Personalization Regional Settings --> Language = American English (Deleted Canadian English( Region Settings --> Formats --> Region = Canadian English (en_CA) Region Settings --> Formats --> Detailed Settings --> Time = Default --REBOOT-- Now, in following various internet results with the same / similar problem, I also copied a bunch of locale files, but can't remember from where to where, as it didn't seem to have any effect and I just continued trying things. It now appears likely that I will have to abandon my efforts to use KDE apps despite the apparent success of getting KOrganizer to work. Now KMail is failing to connect to a pop3 server, receiving the error that SSL needs be active and it is set to be active in KMail. Not trying to start a new topic, just adding a sigh that what looks like a great experience is going to be one I have to miss out. Thanks again for your note and best of the season to you. After reboot -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415103] New: Setting "Preview on mouse-over" is not mantained.
https://bugs.kde.org/show_bug.cgi?id=415103 Bug ID: 415103 Summary: Setting "Preview on mouse-over" is not mantained. Product: digikam Version: 6.4.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: antonio.ang...@protonmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Edit mode 2. Click the button "Preview on mouse-over" 3. Colour >curves (e.g.), change something 4. Cancel (it doesn't matter) 5. Enhance >Blur; change something 6. Preview on mouse-over is not set. OBSERVED RESULT Preview on mouse-over status previously set is not mantained. EXPECTED RESULT As in previous versions, I expect to find everytime the last set preview mode. SOFTWARE/OS VERSIONS Linux/KDE Ubuntu 18.0.4 (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.
[plasmashell] [Bug 400087] The tray icon of preferences-desktop-randr is a little bit wider than others.
https://bugs.kde.org/show_bug.cgi?id=400087
Nate Graham changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/pla
||sma-framework/5172b920f9e18
||2095d91d0e75944e3f3dae7fa49
Version Fixed In||5.66
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
--- Comment #2 from Nate Graham ---
Git commit 5172b920f9e182095d91d0e75944e3f3dae7fa49 by Nate Graham.
Committed on 12/12/2019 at 17:16.
Pushed by ngraham into branch 'master'.
[RFC] Fix Display Configuration icon margins
Summary:
The icon's old margins were too large, causing it to stick out.
FIXED-IN: 5.66
Test Plan:
{F7813886, size=full}
{F7813885, size=full}
Reviewers: #vdg, ndavis
Reviewed By: #vdg, ndavis
Subscribers: trickyricky26, kde-frameworks-devel
Tags: #frameworks
Differential Revision: https://phabricator.kde.org/D25296
M +69 -343 src/desktoptheme/breeze/icons/preferences.svg
https://commits.kde.org/plasma-framework/5172b920f9e182095d91d0e75944e3f3dae7fa49
--
You are receiving this mail because:
You are watching all bug changes.
[gcompris] [Bug 415102] missing-letter, voices broken on Android
https://bugs.kde.org/show_bug.cgi?id=415102 --- Comment #1 from anim...@gmail.com --- Note: bug was there already in GCompris 0.96 (I didn't check older versions), so at least it's not a new bug in 0.97. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 415102] missing-letter, voices broken on Android
https://bugs.kde.org/show_bug.cgi?id=415102 anim...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 415100] please support uploading large backtraces
https://bugs.kde.org/show_bug.cgi?id=415100 John Scott changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from John Scott --- *** This bug has been marked as a duplicate of bug 248807 *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 248807] Report with a long backtrace can't be sent (bugzilla 65k limit per comment)
https://bugs.kde.org/show_bug.cgi?id=248807 John Scott changed: What|Removed |Added CC||jsc...@posteo.net --- Comment #18 from John Scott --- *** Bug 415100 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 415102] New: missing-letter, voices broken on Android
https://bugs.kde.org/show_bug.cgi?id=415102 Bug ID: 415102 Summary: missing-letter, voices broken on Android Product: gcompris Version: git master Platform: Android OS: All Status: REPORTED Severity: major Priority: NOR Component: general Assignee: bruno.coud...@gcompris.net Reporter: anim...@gmail.com Target Milestone: --- SUMMARY Playing of voices is quite broken for missing-letter activity on Android: -it does play first word and first letter -voices for next words and letters are not played -Seems to happen only on Android (tested on Linux it works fine) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415101] New: Canvas only is unusable with incompatible HDR settings
https://bugs.kde.org/show_bug.cgi?id=415101 Bug ID: 415101 Summary: Canvas only is unusable with incompatible HDR settings Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: HDR Assignee: krita-bugs-n...@kde.org Reporter: til.schmit...@gmx.de Target Milestone: --- SUMMARY i encountered it on krita-nightly-x64-v4.3.0-prealpha-910-g818c841b0b and then updated to krita-nightly-x64-v4.3.0-prealpha-913-gcf3682662b, it still is like this. regular painting works fine windowed. STEPS TO REPRODUCE - select an incompatible HDR setting - go into canvas only mode. OBSERVED RESULT (i tried several times with different monitor configs, here are some results) - my wacom cintiq 13 pro gets a black screen - my secondary monitor (sony bravia 42 inch @1920x1080) goes into canvas only, but the contrast is lowered - getting image back on my cintiq only works by turning it off and on again outside of canvas only - dockers got defaulted - krita (g818...) crashed on me once, results are inconsistent - krita's window gets resized when i go back - krita's window options were switched out for the window options for the currently open project(i normally have them hidden/my krita is set up for true fullscreen) SOFTWARE/OS VERSIONS Windows: 10 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 383923] Start generating backtrace and searching for possible duplicates right after 'Report Bug' button was pressed in crash window
https://bugs.kde.org/show_bug.cgi?id=383923 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411166] Crash in QV4::QmlListWrapper::toVariant from Aurorae
https://bugs.kde.org/show_bug.cgi?id=411166 --- Comment #20 from David Kredba --- #33 0x7f29d0dab498 in QQmlBoundSignal_callback(QQmlNotifierEndpoint*, void**) (e=0x55db78b405b0, a=0x0) at ../../include/QtQml/5.13.2/QtQml/private/../../../../../src/qml/qml/qqmlboundsignalexpressionpointer_p.h:69 #34 0x7f29d0dedcb4 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) (endpoint=, a=a@entry=0x0) at qml/qqmlnotifier.cpp:104 #35 0x7f29d0d8a43d in QQmlData::signalEmitted(QAbstractDeclarativeData*, QObject*, int, void**) (object=0x55db77c0ff10, index=35, a=0x0) at qml/qqmlengine.cpp:887 #36 0x7f29d1d6545b in QMetaObject::activate(QObject*, int, int, void**) (sender=0x55db77c0ff10, signalOffset=, local_signal_index=, argv=argv@entry=0x0) at kernel/qobject.h:122 #37 0x7f29d0d84205 in QQmlVMEMetaObject::activate(QObject*, int, void**) (this=this@entry=0x55db78b81570, object=, index=, args=args@entry=0x0) at ../../include/QtQml/5.13.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertycache_p.h:864 #38 0x7f29d0d85e7a in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) (this=0x55db78b81570, o=, c=QMetaObject::WriteProperty, _id=, a=) at ../../include/QtQml/5.13.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertycache_p.h:854 #39 0x7f29d0d9f191 in QQmlPropertyData::writeProperty(QObject*, void*, QFlags) const (this=, target=, value=, flags=...) at ../../include/QtQml/5.13.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertycache_p.h:350 #40 0x7f29d0d9b41d in QQmlPropertyPrivate::write(QObject*, QQmlPropertyData const&, QVariant const&, QQmlContextData*, QFlags) (object=0x55db77c0ff10, property=..., value=..., context=, flags=...) at qml/qqmlproperty.cpp:1261 #41 0x7f29d0d9d412 in QQmlPropertyPrivate::writeValueProperty(QObject*, QQmlPropertyData const&, QQmlPropertyData const&, QVariant const&, QQmlContextData*, QFlags) (object=, core=..., valueTypeData=..., value=..., context=, flags=..., flags@entry=...) at qml/qqmlproperty.cpp:1191 #42 0x7f29d0e13304 in QQmlBinding::slowWrite(QQmlPropertyData const&, QQmlPropertyData const&, QV4::Value const&, bool, QFlags) (this=this@entry=0x55db78e4c4a0, core=..., valueTypeData=..., result=..., isUndefined=isUndefined@entry=false, flags=..., flags@entry=...) at ../../include/QtQml/5.13.2/QtQml/private/../../../../../src/qml/qml/ftw/qflagpointer_p.h:230 #43 0x7f29d0e14daf in GenericBinding<2>::write(QV4::Value const&, bool, QFlags) (this=0x55db78e4c4a0, result=..., isUndefined=, flags=...) at ../../include/QtQml/5.13.2/QtQml/private/../../../../../src/qml/jsruntime/qv4value_p.h:297 #44 0x7f29d0e1597b in QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&, QFlags, QV4::Scope&) (this=0x55db78e4c4a0, watcher=..., flags=..., scope=...) at ../../include/QtQml/5.13.2/QtQml/private/../../../../../src/qml/jsruntime/qv4scopedvalue_p.h:239 #45 0x7f29d0e11f64 in QQmlBinding::update(QFlags) (this=0x55db78e4c4a0, flags=...) at qml/qqmlbinding.cpp:185 #46 0x7f29d0da6f26 in QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) (this=, expression=0x55db78e4c4a0) at qml/qqmlcontext.cpp:705 -- You are receiving this mail because: You are watching all bug changes.
