[kdeconnect] [Bug 375644] Unable to pair kdeconnect when connecting via OpenVPN, even if specifying hostname or IP address
https://bugs.kde.org/show_bug.cgi?id=375644 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|NOT A BUG |WORKSFORME --- Comment #17 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.
[kdenlive] [Bug 382914] Rendering files as mp4, full hd, generates files much larger than before
https://bugs.kde.org/show_bug.cgi?id=382914 --- 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.
[plasmashell] [Bug 406096] Font size cannot be changed
https://bugs.kde.org/show_bug.cgi?id=406096 --- Comment #3 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.
[kdenlive] [Bug 384947] Kdenlive crashes after changing a profile in project if there was an item from library with different fps
https://bugs.kde.org/show_bug.cgi?id=384947 --- 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.
[kdenlive] [Bug 384780] notifications sounds arent affected by notification volume
https://bugs.kde.org/show_bug.cgi?id=384780 --- 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.
[amarok] [Bug 406753] New: If Else (Match all sequentially) when contained in And (Match all) fails in Dynamic Playlist
https://bugs.kde.org/show_bug.cgi?id=406753 Bug ID: 406753 Summary: If Else (Match all sequentially) when contained in And (Match all) fails in Dynamic Playlist Product: amarok Version: 2.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Playlists/Dynamic Playlists Assignee: amarok-bugs-d...@kde.org Reporter: garykennethkrue...@gmail.com CC: ralf-eng...@gmx.de Target Milestone: kf5 SUMMARY If Else (Match all sequentially) when contained in And (Match all) fails in Dynamic Playlist If any "If Else" element fails the And will always fail the If Else. STEPS TO REPRODUCE 1. Create an And with one or more succeeding biases. 2. Create an If Else (within the And) that succeeds for the first one or more biases, but fails on one or more subsequent biases. 3. Repopulate. OBSERVED RESULT Nothing from the If Else will appear in the playlist. EXPECTED RESULT There should be results that match in the playlist. Part of the problem is the traditional meaning of "If ... Else" does not match the traditional meaning of "Match all sequentially". But, Amarok is treating them as identical. "If ... Else" should return the first thing that matches, and if any one entry is successful, the overall result should be successful (a TRUE for the enclosing And). "Match all sequentially" should return everything that matches, until something doesn't match. But, the overall result should be successful if the first entry was successful (a TRUE for the enclosing And). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu Bionic Beaver 18.04.2 LTS. libqtcore4/bionic,now 4:4.8.7+dfsg-7ubuntu1 amd64 [installed,automatic] Qt 4 core module libqtgui4/bionic,now 4:4.8.7+dfsg-7ubuntu1 amd64 [installed,automatic] Qt 4 GUI module libqt5gui5/bionic-updates,now 5.9.5+dfsg-0ubuntu2 amd64 [installed,automatic] Qt 5 GUI module (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Connected to local mysql database. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406752] New: Menu for "New Tab" button shown in incorrect location for non-first triggering
https://bugs.kde.org/show_bug.cgi?id=406752 Bug ID: 406752 Summary: Menu for "New Tab" button shown in incorrect location for non-first triggering Product: konsole Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: arfrever@gmail.com Target Milestone: --- Problem reproduced with master branch. Problem introduced during last several weeks. 19.04.0 release supposedly unaffected. After starting new Konsole process, when pressing and holding "New Tab" button for some seconds for the first time, the menu with list of profiles appears in correct location. When pressing and holding this button again, this menu appears in incorrect location (moved to the left and below). It is necessary to start new Konsole process to notice this small difference. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 406751] Time relations become forgotten in Dynamic Playlist rules
https://bugs.kde.org/show_bug.cgi?id=406751 --- Comment #1 from Gary Kenneth Krueger --- By the way, it is running on Ubuntu Bionic Beaver 18.04.2 LTS. libqtcore4/bionic,now 4:4.8.7+dfsg-7ubuntu1 amd64 [installed,automatic] Qt 4 core module libqtgui4/bionic,now 4:4.8.7+dfsg-7ubuntu1 amd64 [installed,automatic] Qt 4 GUI module libqt5gui5/bionic-updates,now 5.9.5+dfsg-0ubuntu2 amd64 [installed,automatic] Qt 5 GUI module -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 406751] Time relations become forgotten in Dynamic Playlist rules
https://bugs.kde.org/show_bug.cgi?id=406751 Gary Kenneth Krueger changed: What|Removed |Added CC||garykennethkrue...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 406751] New: Time relations become forgotten in Dynamic Playlist rules
https://bugs.kde.org/show_bug.cgi?id=406751 Bug ID: 406751 Summary: Time relations become forgotten in Dynamic Playlist rules Product: amarok Version: 2.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Playlists/Dynamic Playlists Assignee: amarok-bugs-d...@kde.org Reporter: garykennethkrue...@gmail.com CC: ralf-eng...@gmx.de Target Milestone: kf5 SUMMARY Time relations become forgotten in Dynamic Playlist rules. STEPS TO REPRODUCE 1. Create a time related dynamic playlist rule (for example: Modified newer than 600 days) 2. Save the rule. 3. Try to go back in to edit the rule. By the way, if you don't go back in to edit the rule, the relation will be forgotten anyhow when you quit and restart Amarok. OBSERVED RESULT Observe that the playlist rule forgets "newer than", and now shows "on" as the relation. EXPECTED RESULT The playlist rule continues to show "newer than" (or the chosen relation) regardless of re-editing the rule or restarting Amarok. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Connected to local mysql database. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 406645] yaml diagnostics export
https://bugs.kde.org/show_bug.cgi?id=406645 --- Comment #4 from chg...@gmail.com --- And there is this script that goes hand in hand with -export-fixes=, this first run clang-tify in parrallel, then collect, then merge all replacement files, and finally call clang-apply-replacement if asked to. https://github.com/llvm-mirror/clang-tools-extra/blob/master/clang-tidy/tool/run-clang-tidy.py -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406746] XRender renders some things with too much transparency
https://bugs.kde.org/show_bug.cgi?id=406746 --- Comment #8 from Wyatt Childers --- (In reply to David Edmundson from comment #7) > Can you include some screenshots. > > It'll probably be a plasmashell cache issue. I'll update the issue with a screenshot of the broken state as soon as it occurs again. It's intermittent, and has been occurring for quite some time. I switched to an nvidia card, and then switched to XRender from OpenGL as a workaround for https://bugs.kde.org/show_bug.cgi?id=353983. This issue is cosmetic, but annoying lol. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406269] pdf document with empty signature field is claimed to be signed
https://bugs.kde.org/show_bug.cgi?id=406269 --- Comment #4 from Albert Astals Cid --- (In reply to Nate Graham from comment #3) > Not an expert on this stuff so let me ask some questions: > > - What exactly do you mean by "shitty broken signatures?" Lots of fields are missing. > - Are shitty broken signatures valid? Depends on what you mean by valid :D The existing contents are not wrong, they just miss lots of fields that make them quite shitty and not very useful. > Can they be legitimately used for any purpose? Most probably not. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 395497] Menubar - No text
https://bugs.kde.org/show_bug.cgi?id=395497 --- Comment #14 from Albert Astals Cid --- Can you send your .local/share/kxmlgui5/okular/part.rc file over? Do you remember doing any customization to your menus/toolbar/shortcuts? Can you confirm that removing your .local/share/kxmlgui5/okular/part.rc file (save it first somewhere else) fixes this? -- You are receiving this mail because: You are watching all bug changes.
[kdf] [Bug 406750] New: kdf desktop shortcut affects Task Manager
https://bugs.kde.org/show_bug.cgi?id=406750 Bug ID: 406750 Summary: kdf desktop shortcut affects Task Manager Product: kdf Version: 18.12 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jolug...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Create a desktop shortcut to the application 2. Launch the application 3. OBSERVED RESULT The task manager bar doesn't work until I close the application. If I launch it from the system menu everything works great. EXPECTED RESULT The task manager should work while the application is running SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro 18.0.4 KDE KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405831] Crash with audio clips in Kdenlive Win 19.04beta-git2019
https://bugs.kde.org/show_bug.cgi?id=405831 Vincent PINON changed: What|Removed |Added CC||vpi...@kde.org --- Comment #22 from Vincent PINON --- Hello, With today's code, it doesn't crash anymore, just showing message it can't load the clip... After program restart it does load the clips. Still to do some progress. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 358868] copy entire page to clipboard
https://bugs.kde.org/show_bug.cgi?id=358868 Albert Astals Cid changed: What|Removed |Added Latest Commit||https://commits.kde.org/oku ||lar/f788b5a384b5445bd08c775 ||e51e4041ca7045da2 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Albert Astals Cid --- Git commit f788b5a384b5445bd08c775e51e4041ca7045da2 by Albert Astals Cid, on behalf of Shubham Jangra. Committed on 21/04/2019 at 23:11. Pushed by aacid into branch 'master'. Add action in Edit menu to select the text on current page Test Plan: Click on "Select All Text on Current Page" entry in Edit menu to select the entire page. The selected text can then be copied via Edit menu item "Copy" Reviewers: aacid, #vdg, ngraham Reviewed By: #vdg, ngraham Subscribers: yurchor, michaelweghorn, kde-doc-english, davidhurka, abetts, loh.tar, alexde, ngraham, okular-devel Tags: #okular, #documentation Differential Revision: https://phabricator.kde.org/D18744 M +15 -0doc/index.docbook M +9-0part.cpp M +1-0part.h M +2-1part.rc M +15 -0ui/pageview.cpp M +2-0ui/pageview.h https://commits.kde.org/okular/f788b5a384b5445bd08c775e51e4041ca7045da2 -- You are receiving this mail because: You are watching all bug changes.
[kmines] [Bug 406749] New: Minesweeper Crashes
https://bugs.kde.org/show_bug.cgi?id=406749 Bug ID: 406749 Summary: Minesweeper Crashes Product: kmines Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dim...@gmail.com Reporter: jre...@yahoo.com CC: kde-games-b...@kde.org Target Milestone: --- Application: kmines (4.0 (29 Jan 2015)) Qt Version: 5.11.3 Frameworks Version: 5.55.0 Operating System: Linux 5.0.7-200.fc29.x86_64 x86_64 Distribution: "Fedora release 29 (Twenty Nine)" -- Information about the crash: - What I was doing when the application crashed:Just closed Firefox on Ferora 29 running in Gnome desktop as Plasma does not play well with my Nvida Card. The crash can be reproduced sometimes. -- Backtrace: Application: KMines (kmines), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdd3350d940 (LWP 8703))] Thread 5 (Thread 0x7fdd1f7fe700 (LWP 8709)): #0 0x7fdd36e7c3f1 in poll () at /lib64/libc.so.6 #1 0x7fdd33cbd3a6 in () at /lib64/libglib-2.0.so.0 #2 0x7fdd33cbd4d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fdd3752b5ab in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fdd374d9e0b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fdd37341e86 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fdd38df6f89 in () at /lib64/libQt5DBus.so.5 #7 0x7fdd3734b2fb in () at /lib64/libQt5Core.so.5 #8 0x7fdd3626f58e in start_thread () at /lib64/libpthread.so.0 #9 0x7fdd36e87683 in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fdd1700 (LWP 8708)): #0 0x7fdd36e7c3f1 in poll () at /lib64/libc.so.6 #1 0x7fdd33cbd3a6 in () at /lib64/libglib-2.0.so.0 #2 0x7fdd33cbd762 in g_main_loop_run () at /lib64/libglib-2.0.so.0 #3 0x7fdd24e9d10a in () at /lib64/libgio-2.0.so.0 #4 0x7fdd33ce62aa in () at /lib64/libglib-2.0.so.0 #5 0x7fdd3626f58e in start_thread () at /lib64/libpthread.so.0 #6 0x7fdd36e87683 in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fdd24a2e700 (LWP 8707)): #0 0x7fdd36e7c3f1 in poll () at /lib64/libc.so.6 #1 0x7fdd33cbd3a6 in () at /lib64/libglib-2.0.so.0 #2 0x7fdd33cbd4d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fdd33cbd521 in () at /lib64/libglib-2.0.so.0 #4 0x7fdd33ce62aa in () at /lib64/libglib-2.0.so.0 #5 0x7fdd3626f58e in start_thread () at /lib64/libpthread.so.0 #6 0x7fdd36e87683 in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fdd26249700 (LWP 8706)): #0 0x7fdd36e7c3f1 in poll () at /lib64/libc.so.6 #1 0x7fdd33c3839f in () at /lib64/libxcb.so.1 #2 0x7fdd33c3a01a in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7fdd263eabf9 in () at /lib64/libQt5XcbQpa.so.5 #4 0x7fdd3734b2fb in () at /lib64/libQt5Core.so.5 #5 0x7fdd3626f58e in start_thread () at /lib64/libpthread.so.0 #6 0x7fdd36e87683 in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fdd3350d940 (LWP 8703)): [KCrash Handler] #6 0x7fdd37a2d1e0 in () at /lib64/libQt5Gui.so.5 #7 0x7fdd37a38a32 in () at /lib64/libQt5Gui.so.5 #8 0x7fdd37a586d8 in () at /lib64/libQt5Gui.so.5 #9 0x7fdd37a64246 in QRasterPaintEngine::fill(QVectorPath const&, QBrush const&) () at /lib64/libQt5Gui.so.5 #10 0x7fdd37a4ba4d in QPaintEngineEx::draw(QVectorPath const&) () at /lib64/libQt5Gui.so.5 #11 0x7fdd37a4cc1b in QPaintEngineEx::drawRects(QRectF const*, int) () at /lib64/libQt5Gui.so.5 #12 0x7fdd37a64f65 in QRasterPaintEngine::drawRects(QRectF const*, int) () at /lib64/libQt5Gui.so.5 #13 0x7fdd37a728bc in QPainter::drawRects(QRectF const*, int) () at /lib64/libQt5Gui.so.5 #14 0x7fdd363f6829 in QSvgRect::draw(QPainter*, QSvgExtraStates&) () at /lib64/libQt5Svg.so.5 #15 0x7fdd36412323 in QSvgG::draw(QPainter*, QSvgExtraStates&) () at /lib64/libQt5Svg.so.5 #16 0x7fdd36418dcb in QSvgTinyDocument::draw(QPainter*, QString const&, QRectF const&) () at /lib64/libQt5Svg.so.5 #17 0x7fdd3927f6c8 in () at /lib64/libKF5KDEGames.so.7 #18 0x7fdd39280191 in () at /lib64/libKF5KDEGames.so.7 #19 0x7fdd392809ae in KGameRenderer::spritePixmap(QString const&, QSize const&, int, QHash const&) const () at /lib64/libKF5KDEGames.so.7 #20 0x557a958bf4d3 in () #21 0x557a958b1999 in () #22 0x557a958b2980 in () #23 0x557a958b121f in () #24 0x7fdd36dae413 in __libc_start_main () at /lib64/libc.so.6 #25 0x557a958b12be in _start () [Inferior 1 (process 8703) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 395520] Konsole KPart blur does not work/incorrect warning message
https://bugs.kde.org/show_bug.cgi?id=395520 Nick changed: What|Removed |Added CC||futurepi...@gmx.us -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405847] SFTP corrupts DNG files
https://bugs.kde.org/show_bug.cgi?id=405847 --- Comment #10 from Mau --- (In reply to Yuriy Vidineev from comment #7) > [...] > sshfs: 3.2 > > Probably it could be related to https://bugs.kde.org/show_bug.cgi?id=383069 > and -o writeback_cache=no > > I didn't see this issue with previous kdeconnect version Can this issue be related to sshfs if downgrading the Android app solves it? Downgraded app to v1.10.1, no issues at all as always. sshfs v2.10 here (Debian Buster), anyways. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406746] XRender renders some things with too much transparency
https://bugs.kde.org/show_bug.cgi?id=406746 --- Comment #7 from David Edmundson --- Can you include some screenshots. It'll probably be a plasmashell cache issue. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406738] Okular crashes when I try to open a specific epub file
https://bugs.kde.org/show_bug.cgi?id=406738
--- Comment #4 from Albert Astals Cid ---
For future people investigating, there's something weird going on in the
if(dom.setContent(htmlContent)) {
branch of Epub::Converter::convert
if you comment that whole branch out it works out fine :/
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 406746] XRender renders some things with too much transparency
https://bugs.kde.org/show_bug.cgi?id=406746 --- Comment #6 from Wyatt Childers --- (In reply to Vlad Zagorodniy from comment #4) > (In reply to David Edmundson from comment #3) > > That's true, but plasmashell does know when blur and contrast effect are > > running and switch to a different more opaque version. > Hmm, if compositing is turned off, it makes sense to draw opaque panels. > Though I don't think such thinking applies when using XRender rendering > backend. What if you actually want transparent panels? :) Well, compositing is enabled, through XRender. I think you're miss understanding a bit. So, I'm specifically talking about "panel pop-ups"/pop overs (things like clicking on the time to see the dates in the month, the part the pops up when you click the time). There are 3 cases: - Composition on working correctly: Month view is rendering correctly, with the correct opacity/transparency, just like they would on OpenGL, blurred, and simi transparent. - Compositing on but broken: Month view is being rendered wa too transparent, almost like a glass theme, rather than breeze. - Compositing off: Moth view is 100% opaque, no transparency. This issue is about the second case, where breeze is being rendered as if it were a glass theme sometimes under XRender, never happens under OpenGL. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 405313] kalarm freezes in gnome
https://bugs.kde.org/show_bug.cgi?id=405313 --- Comment #18 from David Jarvie --- It looks as if more Akonadi resources are running than there should be. To fix this: 1. In KAlarm, use the View -> Show Calendars menu option to display the alarm calendars in use. 2. Right click on each calendar shown and choose Show Details. Note the calendar type, contents and file shown there. In the drop-down selector, choose each of Active Alarms, Archived Alarms and Alarm Templates, and repeat for each. 3. You will now have a list of all the calendar files currently in use, which you can use to restore them in case of any resources disappear in the subsequent steps. 4. Run "akonadiconsole" and look in the displayed list for all resources identified by the KAlarm icon. 5. For each KAlarm resource, double click on it to display its configuration, and note the file name shown for it. 6. If two resources show the same file name, remove one of those resources (using the Remove button or menu option). It shouldn't matter which of the two resources you remove. Keep repeating this operation until each file name only shows up for one resource. 7. There should now be one resource in the list for each calendar file found in step 2. If any calendars are now missing from the list shown in KAlarm, you can restore them by going to the Calendars pane in KAlarm and clicking Add to reinstate them. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406746] XRender renders some things with too much transparency
https://bugs.kde.org/show_bug.cgi?id=406746 --- Comment #5 from Vlad Zagorodniy --- .. but I agree that such aspects have to be controlled by the desktop theme. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406746] XRender renders some things with too much transparency
https://bugs.kde.org/show_bug.cgi?id=406746 --- Comment #4 from Vlad Zagorodniy --- (In reply to David Edmundson from comment #3) > That's true, but plasmashell does know when blur and contrast effect are > running and switch to a different more opaque version. Hmm, if compositing is turned off, it makes sense to draw opaque panels. Though I don't think such thinking applies when using XRender rendering backend. What if you actually want transparent panels? :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406738] Okular crashes when I try to open a specific epub file
https://bugs.kde.org/show_bug.cgi?id=406738 Albert Astals Cid changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- --- Comment #3 from Albert Astals Cid --- yep -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 406748] New: Buttons are cut off while drkonqi generates a backtrace
https://bugs.kde.org/show_bug.cgi?id=406748 Bug ID: 406748 Summary: Buttons are cut off while drkonqi generates a backtrace Product: drkonqi Version: 5.15.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 119549 --> https://bugs.kde.org/attachment.cgi?id=119549=edit screenshot SUMMARY Observe the buttons highlighted in red in the attached screenshot. They are cut off. STEPS TO REPRODUCE 1. when a crash notification appears on your system, click its "Report bug" button to open drkonqi 2. click "Developer information" tab 3. observe the buttons immediately below the text box while the backtrace is generated EXPECTED RESULT The buttons are not cut off SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406746] XRender renders some things with too much transparency
https://bugs.kde.org/show_bug.cgi?id=406746 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #3 from David Edmundson --- >Panels look more opaque because of blur and background constrast effect, both >require OpenGL. That's true, but plasmashell does know when blur and contrast effect are running and switch to a different more opaque version. If OP has a transparent panel it means something along that path isn't working. Either from kwin, in plasma-framework or in the theme. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 406633] Cannot rate photos
https://bugs.kde.org/show_bug.cgi?id=406633 --- Comment #3 from Johannes Zarl-Zierl --- > I had the impression that it was not giving a rating, even when I pressed > keys 1-5, which I read about somewhere. But I did not confirm this for > certain. That should work in the image viewer, but not in the annotation dialog. If you press e.g. key 3 in the image viewer, do you get any visual feedback? If you then save the database and inspect the index.xml file, does the corresponding image tag contain a rating attribute? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406491] [wayland] neither primary selection neither copy paste working
https://bugs.kde.org/show_bug.cgi?id=406491 --- Comment #1 from Vlad Zagorodniy --- What version? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405609] System settings crashed when I opened "Application style"
https://bugs.kde.org/show_bug.cgi?id=405609 --- Comment #2 from Vlad Zagorodniy --- Cannot reproduce. What themes do you have installed? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406747] New: krita crashes immediately on first touch of tablet
https://bugs.kde.org/show_bug.cgi?id=406747 Bug ID: 406747 Summary: krita crashes immediately on first touch of tablet Product: krita Version: 4.1.7 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: jpriti...@pobox.com Target Milestone: --- SUMMARY I just upgraded to Ubuntu Disco. Krita worked great on Ubuntu Cosmic. STEPS TO REPRODUCE 1. Paint with tablet OBSERVED RESULT: Immediately crashes SOFTWARE/OS VERSIONS Krita Version: 4.1.7 (dpkg reports 2:4.1.7-1~cosmic) Qt Version (compiled): 5.11.1 Version (loaded): 5.12.2 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.0.0-13-generic Pretty Productname: Ubuntu 19.04 Product Type: ubuntu Product Version: 19.04 OpenGL Info **OpenGL not initialized** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406661] Display of tab icons no longer works
https://bugs.kde.org/show_bug.cgi?id=406661 --- Comment #3 from Kurt Hindenburg --- Actually it works here on 19.04; the big change in splitview broke it in master. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406746] XRender renders some things with too much transparency
https://bugs.kde.org/show_bug.cgi?id=406746 --- Comment #2 from Wyatt Childers --- (In reply to Vlad Zagorodniy from comment #1) > Panels look more opaque because of blur and background constrast effect, > both require OpenGL. I believe there's something else going on here. As an example, when I wrote this bug it was occurring, however, at the present time still using XRender my "panel pop-ups" (I really don't know what to call them haha), are the proper transparency. It's an intermittent issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406120] Animations cause whole screen to freeze for 10-30 seconds
https://bugs.kde.org/show_bug.cgi?id=406120 Vlad Zagorodniy changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #1 from Vlad Zagorodniy --- Could you please get backtrace of kwin when it's frozen? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406746] XRender renders some things with too much transparency
https://bugs.kde.org/show_bug.cgi?id=406746 Vlad Zagorodniy changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Vlad Zagorodniy --- Panels look more opaque because of blur and background constrast effect, both require OpenGL. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406746] New: XRender renders some things with too much transparency
https://bugs.kde.org/show_bug.cgi?id=406746 Bug ID: 406746 Summary: XRender renders some things with too much transparency Product: kwin Version: 5.15.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: dark...@nearce.com Target Milestone: --- SUMMARY For whatever reason XRender occasionally renders the start menu and other "panel pop-ups" as much more transparent than OpenGL. STEPS TO REPRODUCE I don't know exactly how to reproduce this consistently yet, aside from just running under XRender. OBSERVED RESULT The "panel pop-ups" are much much more transparent, almost completely so. EXPECTED RESULT The "panel pop-ups" should be the same darkness as rendering under OpenGL. ADDITIONAL INFORMATION Kernel version: 4.15.0-1024-oem NVidia binary driver: 415 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406319] Hangs/freezes when drag windows to top, right or left edges of the screen
https://bugs.kde.org/show_bug.cgi?id=406319 Vlad Zagorodniy changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #9 from Vlad Zagorodniy --- Both the outline and tabbox are qml based so I guess this is a dup of 406180. Is there any chance you could get a backtrace when kwin is frozen? (you would need two computers for this) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 397985] Round box drawing chars aren't nice
https://bugs.kde.org/show_bug.cgi?id=397985 --- Comment #6 from Bo Simonsen --- By the way, scaling is 1.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397850] kwin_x11 - triple buffer detection of compositing apparently broken with every driver; causing stuttering, lag or tearing
https://bugs.kde.org/show_bug.cgi?id=397850 --- Comment #4 from Vlad Zagorodniy --- (In reply to tempel.julian from comment #0) > First observation: > When KWIN_TRIPLE_BUFFER is set (both 1 and 0), the nasty initial > "calibration stuttering" when compositing turns on disappears. That stuttering occurs because KWin detects whether triple buffering is supported. > This easily noticeable when moving windows right after enabling compositing. > KWin is the only compositor I know which shows such a weird behavior. If you are aware of better way to detect triple buffering, please submit a new patch. :-) (In reply to tempel.julian from comment #1) > Well, if no one wants to fix it, perhaps set at least KWIN_TRIPLE_BUFFER=0 > by default? No, this is a terrible idea. (In reply to Steffen Coenen from comment #2) > This is probably a duplicate of https://bugs.kde.org/show_bug.cgi?id=344433 Yep, probably. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 397985] Round box drawing chars aren't nice
https://bugs.kde.org/show_bug.cgi?id=397985 --- Comment #5 from Bo Simonsen --- Created attachment 119548 --> https://bugs.kde.org/attachment.cgi?id=119548=edit screenshot of mc after antialiasing change -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 397985] Round box drawing chars aren't nice
https://bugs.kde.org/show_bug.cgi?id=397985 Bo Simonsen changed: What|Removed |Added Resolution|FIXED |--- CC||b...@geekworld.dk Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #4 from Bo Simonsen --- Using QPainter::Antialiasing made Konsole behave strange for scaled display, see attached screenshot for "mc". I am running openSUSE LEAP 15.1 where 18.12 has been patched with improvements in rendering of boxes. I tried commenting out paint.setRenderHint(QPainter::Antialiasing, _antialiasText); and that did make mc look normal. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 406745] code preview with syntax highlighting and dark theme not readable
https://bugs.kde.org/show_bug.cgi?id=406745 maxmustermann1...@web.de changed: What|Removed |Added CC||maxmustermann1...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 406745] New: code preview with syntax highlighting and dark theme not readable
https://bugs.kde.org/show_bug.cgi?id=406745 Bug ID: 406745 Summary: code preview with syntax highlighting and dark theme not readable Product: kio-extras Version: 19.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Thumbnails and previews Assignee: plasma-b...@kde.org Reporter: maxmustermann1...@web.de Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. change plasma look theme to breeze dark 2. open dolphin, enable text preview and go to a file with syntax highlighting OBSERVED RESULT https://i.imgur.com/Ng8mkuK.png syntax highlighting works fine and uses a dark colorscheme, but the file background is white and most file previews unreadable EXPECTED RESULT file preview using a dark file background, when using a dark theme SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Antergos Linux KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.2 Kernel Version: 5.0.8-arch1-1-ARCH ADDITIONAL INFORMATION kio-extras version: 19.04.0-1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 406744] New: Flatpak base images not updateable
https://bugs.kde.org/show_bug.cgi?id=406744 Bug ID: 406744 Summary: Flatpak base images not updateable Product: Discover Version: 5.15.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: lei...@leinir.dk Reporter: dark...@nearce.com CC: aleix...@kde.org, jgrul...@redhat.com Target Milestone: --- SUMMARY Flatpak runtimes count towards the number of things that need updated, but are not displayed in the UI, and will not enable the update button. This leads to the notifier displaying for instance "1 Update" but no updates displayed when you open Discover, and no way to make this notification go away, aside from going to the commandline and running `flatpak update`. STEPS TO REPRODUCE 1. Have a flatpak runtime (e.g. GNOME Application Platform version 3.32) that needs updated OBSERVED RESULT The update notifier says that an update is available. However, when opening Discover and there is no way to apply this update. EXPECTED RESULT The update notifier says that an update is available; when opening Discover the out of date runtimes are listed and are updateable with the update button. ADDITIONAL INFORMATION Flatpak Version: 1.3.1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406743] New: Default background color for HDR image is white
https://bugs.kde.org/show_bug.cgi?id=406743 Bug ID: 406743 Summary: Default background color for HDR image is white Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: tamtamy.tym...@gmail.com Target Milestone: --- SUMMARY Default background color is white, which is ok, but if someone wants to create a HDR image, it hurts their eyes because the first thing they see is a huge super bright white rectangle. It's like looking directly at a lightbulb. STEPS TO REPRODUCE 1. Get a HDR setup. 2. Clear up preferences. 3. Create a new image with Rec2020 linear color space. Don't touch "Content" tab. OBSERVED RESULT Big white rectangle burning your eyes. EXPECTED RESULT Dimmed light-grey rectangle, maybe? Or at least some kind of a warning... NOTES: Since user can set up their own default background color (it is remembered and suggested/used next time), it needs to be thought through: it wouldn't be great to overwrite user's choice. On the other hand, color selector used in Content tab don't support HDR... SOFTWARE/OS VERSIONS Version: 4.2.0-pre-alpha (git fb08951) Windows: 10 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 406587] Autodrop stops in freecell
https://bugs.kde.org/show_bug.cgi?id=406587 --- Comment #5 from Shlomi Fish --- Also see https://phabricator.kde.org/D20721 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406661] Display of tab icons no longer works
https://bugs.kde.org/show_bug.cgi?id=406661 --- Comment #2 from Kurt Hindenburg --- Yea, 32 does not work now in 19.04/master. change icon via \033]32;Icon\007 -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 406587] Autodrop stops in freecell
https://bugs.kde.org/show_bug.cgi?id=406587 --- Comment #4 from Shlomi Fish --- Hi! Thanks for the report and the testcase. Here is a proposed fix patch: https://phabricator.kde.org/D20720 There also seems to be an issue where loading the game is very slow now. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 406742] New: No column number, but editor Apperance configured to show cursor column number.
https://bugs.kde.org/show_bug.cgi?id=406742 Bug ID: 406742 Summary: No column number, but editor Apperance configured to show cursor column number. Product: lokalize Version: 18.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: sdepi...@gmail.com Reporter: bozid...@yahoo.com CC: sha...@ukr.net Target Milestone: --- No cursor column number STEPS TO REPRODUCE Configure lokalize to show LEDS and cursor column number 2. 3. OBSERVED RESULT There are no cursor column number. 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.
[dolphin] [Bug 332536] Show notification when the current open path does not exist anymore
https://bugs.kde.org/show_bug.cgi?id=332536 --- Comment #6 from Julian Schraner --- What do you mean by "more than just notifications"? In my opinion, simply closing the window is destructive and not very useful - the user might want to further use the window to navigate to a new path. An error is already displayed when you try to create a new file, which should be the expected behavior. So I personally think that if we had a notification box similar to the "permission denied" box that would pop up when the current path is deleted would fulfill this wish perfectly. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 406731] KDE file save dialog in Firefox ignores "html only" save mode
https://bugs.kde.org/show_bug.cgi?id=406731 Jan Grulich changed: What|Removed |Added Status|REPORTED|RESOLVED CC||jgrul...@redhat.com Resolution|--- |NOT A BUG --- Comment #1 from Jan Grulich --- Not a bug on our side, it's Firefox who does the saving. This is also reproducible with xdg-desktop-portal-gtk. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 332536] Show notification when the current open path does not exist anymore
https://bugs.kde.org/show_bug.cgi?id=332536 --- Comment #5 from Brock McNuggets --- (In reply to Julian Schraner from comment #4) > Changing title, as this isn't really a bug but more of a request for a > notification to inform the user that the current path doesn't exist anymore. It is more than just about notifications. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381414] [idea] Reduce opacity of grouped, expanded thumbnails to indicate group
https://bugs.kde.org/show_bug.cgi?id=381414 Julian Schraner changed: What|Removed |Added CC||m...@xyquadrat.ch Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 286373] DNG don't get filtered as raw (group of items relevant)
https://bugs.kde.org/show_bug.cgi?id=286373 Julian Schraner changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||m...@xyquadrat.ch Status|REPORTED|NEEDSINFO --- Comment #20 from Julian Schraner --- @AT: could you test this again (using the Digikam 6.0.0)? A lot of bugs were fixed since then, and it's easily possible that your problem was also resolved. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 338647] GROUP : assemble files by format shows two groups of RAW files instead of one
https://bugs.kde.org/show_bug.cgi?id=338647 Julian Schraner changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||m...@xyquadrat.ch Status|REPORTED|NEEDSINFO --- Comment #12 from Julian Schraner --- I cannot reproduce this issue with Digikam 6.0.0. @Alphazo, do you still experience this problem? SYSTEM INFO Operating System: KDE neon Testing Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 Kernel Version: 4.18.0-17-generic -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 175051] mount .iso option in context menu
https://bugs.kde.org/show_bug.cgi?id=175051 --- Comment #22 from Nate Graham --- That makes sense, especially because the fuse-kio system is being revitalized and worked on as a Google Summer of Code project. So showing FUSE volumes in Dolphin would be quite worthwhile in general IMO. But not just Dolphin; make sure they're visible to all users of the Solid framework so they show up in the file dialogs' Places Panel and Plasma's Device Notifier. Feel free to work on this and submit a patch! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 370705] Current Album is deselected when clearing search bar
https://bugs.kde.org/show_bug.cgi?id=370705 Julian Schraner changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||m...@xyquadrat.ch Resolution|--- |WAITINGFORINFO --- Comment #6 from Julian Schraner --- I cannot reproduce this behavior either with Digikam 6.0.0. @Frédéric, do you still experience this problem? SYSTEM INFO Operating System: KDE neon Testing Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 Kernel Version: 4.18.0-17-generic -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 390681] OFX import and unrecognized tag
https://bugs.kde.org/show_bug.cgi?id=390681 --- Comment #11 from bren...@coupeware.com --- I tested this and it works. This is not ideal as a global setting since I have to decide if I want to fix the one account that does not handle the FITID numbers correctly or deal with every other account that has previous imported transactions. First guess is that will require me to go throut hundreds of new duplicates and delete the ones that are already reconciled / cleared. Is there any chance that this will end up being an account based setting or is global the only way to do this? Brendan Coupe On Fri, Apr 19, 2019 at 2:11 AM Thomas Baumgart wrote: > > https://bugs.kde.org/show_bug.cgi?id=390681 > > --- Comment #10 from Thomas Baumgart --- > Git commit 9fca9e3661ce2d03e472ab1d520b59493ec110cb by Thomas Baumgart. > Committed on 19/04/2019 at 08:10. > Pushed by tbaumgart into branch '5.0'. > > Provide internal OFX id generation also for WebConnect > > The change provided in commit 65e3837697c93786 is not available when > importing an OFX statement file via WebConnect. For this case, a new > option has been added (no UI yet) to allow selection of the default for > the unique transaction id to be either the OFX FITID field or our > internal hash. The default is to use OFX FITID, so no change in prior > behavior. This default settings will also be used to preset the combo > box in the file selection dialog for OFX import and the account setting > for mapped accounts. > > If users set this option, they need to know that some duplicate > transactions may appear since the method to detect them changed. One way > to deal with that is to remove both transactions and redo the import. > > To set the method to the internal hash create a file named > > ~/.config/kmymoney/ofximporterrc > > with the following content: > > [General] > useOwnFITID=true > > Future versions of KMyMoney will provide a UI to change this setting. > > M +36 -11 kmymoney/plugins/ofx/import/ofximporter.cpp > > https://commits.kde.org/kmymoney/9fca9e3661ce2d03e472ab1d520b59493ec110cb > > -- > You are receiving this mail because: > You are the assignee for the bug. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 406645] yaml diagnostics export
https://bugs.kde.org/show_bug.cgi?id=406645 --- Comment #3 from Sergio Martins --- Thanks! This has been on my TODO list for some time now... Once this one works I think we should remove the old one from clazy, and only permit via "clazy-standalone -export-fixes", as the old one has many bugs when headers are being rewritten in parallel with "make -jN" -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 406645] yaml diagnostics export
https://bugs.kde.org/show_bug.cgi?id=406645 --- Comment #2 from Sergio Martins --- (Linking https://github.com/KDE/clazy/pull/32 here) -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 406645] yaml diagnostics export
https://bugs.kde.org/show_bug.cgi?id=406645 Sergio Martins changed: What|Removed |Added Assignee|unassigned-b...@kde.org |smart...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 403103] Remember last output save directory
https://bugs.kde.org/show_bug.cgi?id=403103 Kurt Hindenburg changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kon ||sole/61ed2c88a4e205eb5eef2d ||f6cdb13c7ddd6e2943 Version Fixed In||19.08.0 --- Comment #3 from Kurt Hindenburg --- Git commit 61ed2c88a4e205eb5eef2df6cdb13c7ddd6e2943 by Kurt Hindenburg. Committed on 21/04/2019 at 19:12. Pushed by hindenburg into branch 'master'. Remember last 'Save Output As' directory This will save current session's last 'Save Output As' directory as well as saving it so next Konsole startup will remember it. Original code by Tao Guo with additions by myself. FIXED-IN: 19.08.0 Differential Revision: https://phabricator.kde.org/D18352 M +24 -3src/SaveHistoryTask.cpp M +2-0src/SaveHistoryTask.h https://commits.kde.org/konsole/61ed2c88a4e205eb5eef2df6cdb13c7ddd6e2943 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406729] KWin closed unexpecedly; unable to reproduce :(
https://bugs.kde.org/show_bug.cgi?id=406729 --- Comment #4 from Vlad Zagorodniy --- This is most likely a Dim Inactive effect issue. Do you need help with repackaging kwin? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406738] Okular crashes when I try to open a specific epub file
https://bugs.kde.org/show_bug.cgi?id=406738 --- Comment #2 from Patrick Silva --- Created attachment 119547 --> https://bugs.kde.org/attachment.cgi?id=119547=edit epub file that makes okular to crash -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406738] Okular crashes when I try to open a specific epub file
https://bugs.kde.org/show_bug.cgi?id=406738 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- Can we have the file? -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 406672] Application startup delay with KDE runtime
https://bugs.kde.org/show_bug.cgi?id=406672 Jan Grulich changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/xdg ||-desktop-portal-kde/045302b ||5292cb62da5843906825c04898d ||6656d7 Status|REPORTED|RESOLVED --- Comment #3 from Jan Grulich --- Git commit 045302b5292cb62da5843906825c04898d6656d7 by Jan Grulich. Committed on 21/04/2019 at 18:52. Pushed by grulich into branch 'Plasma/5.15'. Settings portal: do not return QDBusVariant directly when calling Read() method It seems it's not possible to return an empty QDBusVariant, which makes our portal not to respond in time and delay application start. Instead of trying to return an empty QDBusVariant, we are supposed to return a DBus error. M +54 -20 src/settings.cpp M +4-2src/settings.h https://commits.kde.org/xdg-desktop-portal-kde/045302b5292cb62da5843906825c04898d6656d7 -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 406741] New: QFX Date Import
https://bugs.kde.org/show_bug.cgi?id=406741 Bug ID: 406741 Summary: QFX Date Import Product: skrooge Version: 2.19.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: abake...@gmail.com CC: steph...@mankowski.fr Target Milestone: --- Created attachment 119546 --> https://bugs.kde.org/attachment.cgi?id=119546=edit The dates in this file don't import into Skrooge correctly. SUMMARY When importing the attached QFX file, the dates all import as 12/31/69. I modified the Name fields and my account #, but the date fields are un-altered from when I downloaded from Chase. STEPS TO REPRODUCE 1. Import QFX file OBSERVED RESULT All transactions import with 12/31/69 as the date. EXPECTED RESULT Actual Transaction or Post date should be imported. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.44 Qt Version: 5.9.5 -- You are receiving this mail because: You are watching all bug changes.
[ksirk] [Bug 406437] ksirk crashes
https://bugs.kde.org/show_bug.cgi?id=406437 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Albert Astals Cid --- I made a few fixes that i think should fix this. The fix should be available for KDE Applications 19.0.4.1 I'm going to close it ad if you can, can you please try it once the next version is released and if it's still happening for you reopen this issue? -- You are receiving this mail because: You are watching all bug changes.
[kde-gtk-config] [Bug 406740] New: Blocks of “icon themes” and “behavior”
https://bugs.kde.org/show_bug.cgi?id=406740 Bug ID: 406740 Summary: Blocks of “icon themes” and “behavior” Product: kde-gtk-config Version: 5.15.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: manutort...@chakra-project.org Reporter: relikts2...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 119545 --> https://bugs.kde.org/attachment.cgi?id=119545=edit GTK Style menu SUMMARY Here’s what the GTK Style settings menu looks like in the resolution of 1366x768 (15.6 inch) - уou can see the problem in the attached video EXPECTED RESULT In this regard, I had a suggestion - to swap the blocks of “icon themes” and “behavior” to get rid of this ugly scroll bar SOFTWARE/OS VERSIONS Operating System: KDE neon 5.15 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.0 Kernel Version: 4.15.0-47-generic OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395725] Blur effect applied for aurorae decoration shadows
https://bugs.kde.org/show_bug.cgi?id=395725 sowren...@gmail.com changed: What|Removed |Added CC||sowren...@gmail.com --- Comment #18 from sowren...@gmail.com --- I am facing this issue with every other window decoration (only when blur is enabled) other than Breeze. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 398975] Muted designation is inconsistent
https://bugs.kde.org/show_bug.cgi?id=398975 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Latest Commit|https://commits.kde.org/bre |https://cgit.kde.org/plasma |eze-icons/b8d080c4e6a1aa857 |-framework.git/commit/?id=b |2e300240edaad807516c2f0 |d8264e92869428c0af84a6b8d2b ||19e518fa5ebe Status|REOPENED|RESOLVED Version Fixed In|5.54|5.58 --- Comment #10 from Nate Graham --- Yep this was fully fixed with https://cgit.kde.org/plasma-framework.git/commit/?id=bd8264e92869428c0af84a6b8d2b19e518fa5ebe! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401808] kde fails to actualize a desktop at startup
https://bugs.kde.org/show_bug.cgi?id=401808 --- Comment #18 from George R. Goffe --- Rex, I am interested in contributing to the rawhide releases. I don't know enough to do much debugging on my own though. For the most part, I work well with developers... forming a team of sorts. I am more than willing to work with developers to resolve these kinds of problems... WHEN they are willing. I have a rather long history of systems administration type work (about 50 years) and have been a developer in the past. I like working with developers... I learn with EVERY experience and I like to think that they learn too. Thanks for all your input! George... -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 406679] joystick icon looks a black ball
https://bugs.kde.org/show_bug.cgi?id=406679 --- Comment #2 from Nate Graham --- There are multiple problems here: - the Joystick KCM uses the icon `preferences-desktop-gaming` which is semantically incorrect (The KCM is about configuring the joystick input device, not gaming in general) - The preferences-desktop-gaming icon depicts the two-dimensional D-pad from a gaming controller, rather than a generic gaming-related icon like input-gaming - We have no icon that actually shows a joystick I think the solution is to: 1. Create a new icon `input-joystick` that actually looks like a joystick 2. Make a symlink called `preferences-desktop-joystick` that points to it 3. Have the joystick KCM use that icon, 4.Make `preferences-desktop-gaming` a symlink to `input-gaming`, and keep that in our back pocket for if we ever have generic gaming-related KCM. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 404794] Gwenview crashes when opening a very specific picture
https://bugs.kde.org/show_bug.cgi?id=404794 --- Comment #2 from Patrick Silva --- gwenview 19.04 is still crashing. Operating System: Arch Linux KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.2 Application: Gwenview (gwenview), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8456e708c0 (LWP 11857))] Thread 6 (Thread 0x7f84452e4700 (LWP 11890)): [KCrash Handler] #6 0x7f844d75d500 in () at /usr/lib/libtiff.so.5 #7 0x7f844d76ce22 in TIFFReadScanline () at /usr/lib/libtiff.so.5 #8 0x7f84543b5c17 in () at /usr/lib/qt/plugins/imageformats/libqtiff.so #9 0x7f845e61c016 in QImageReader::read(QImage*) (this=0x7f84452e3bc8, image=0x7f84500083d0) at image/qimagereader.cpp:1261 #10 0x7f845f94989f in () at /usr/lib/libgwenviewlib.so.5 #11 0x7f845f939f43 in () at /usr/lib/libgwenviewlib.so.5 #12 0x7f845de1aa11 in QThreadPoolThread::run() (this=0x5631f796dd20) at thread/qthreadpool.cpp:99 #13 0x7f845de1696c in QThreadPrivate::start(void*) (arg=0x5631f796dd20) at thread/qthread_unix.cpp:361 #14 0x7f845bebea92 in start_thread () at /usr/lib/libpthread.so.0 #15 0x7f845dafbcd3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f8445ae5700 (LWP 11873)): #0 0x7f845bec4bac in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f845de1cc4c in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x5631f6fd2b00) at thread/qwaitcondition_unix.cpp:146 #2 0x7f845de1cc4c in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x5631f6fb9d98, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f845de1cd3a in QWaitCondition::wait(QMutex*, unsigned long) (this=0x5631f6fb9da0, mutex=0x5631f6fb9d98, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7f845f9a49a4 in () at /usr/lib/libgwenviewlib.so.5 #5 0x7f845de1696c in QThreadPrivate::start(void*) (arg=0x5631f6fb9d30) at thread/qthread_unix.cpp:361 #6 0x7f845bebea92 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f845dafbcd3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f844d235700 (LWP 11860)): #0 0x7f845bec4fa6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f845de1cbc9 in QWaitConditionPrivate::wait_relative(QDeadlineTimer) (this=0x5631f73ef140, deadline=...) at thread/qwaitcondition_unix.cpp:136 #2 0x7f845de1cbc9 in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x5631f73ef140) at thread/qwaitcondition_unix.cpp:144 #3 0x7f845de1cbc9 in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x5631f7294360, deadline=...) at thread/qwaitcondition_unix.cpp:225 #4 0x7f845de1cd08 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x5631f73eef80, mutex=mutex@entry=0x5631f7294360, time=) at thread/qwaitcondition_unix.cpp:209 #5 0x7f845de1ac2b in QThreadPoolThread::run() (this=0x5631f73eef70) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:240 #6 0x7f845de1696c in QThreadPrivate::start(void*) (arg=0x5631f73eef70) at thread/qthread_unix.cpp:361 #7 0x7f845bebea92 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f845dafbcd3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f844700 (LWP 11859)): #0 0x7f845daecc54 in read () at /usr/lib/libc.so.6 #1 0x7f84599b5961 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f8459a05e40 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f8459a07636 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f8459a0777e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f845e028cb4 in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f8448000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f845dfd1a8c in QEventLoop::exec(QFlags) (this=this@entry=0x7f844fffecb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f845de15569 in QThread::exec() (this=this@entry=0x7f845d7c8080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f845d74cba6 in QDBusConnectionManager::run() (this=0x7f845d7c8080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #9 0x7f845de1696c in QThreadPrivate::start(void*) (arg=0x7f845d7c8080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #10 0x7f845bebea92 in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f845dafbcd3 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f8455e8b700 (LWP 11858)): #0 0x7f845daf10d1 in poll () at /usr/lib/libc.so.6 #1 0x7f845997c630 in () at /usr/lib/libxcb.so.1 #2 0x7f845997e2db in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f8456a22989 in QXcbEventQueue::run()
[kcalc] [Bug 406739] New: See previous calculation results
https://bugs.kde.org/show_bug.cgi?id=406739 Bug ID: 406739 Summary: See previous calculation results Product: kcalc Version: 19.04 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: ete...@alum.rit.edu Reporter: vytas.n...@gmail.com Target Milestone: --- SUMMARY It would be useful for users to be able to view all the previous calculation results that they did so far in the session. i.e. on subsequent calculations display the previous calculation and result with smaller font. Once pressed could be expanded to show all calculations that took place in the same session. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406738] New: Okular crashes when I try to open a specific epub file
https://bugs.kde.org/show_bug.cgi?id=406738 Bug ID: 406738 Summary: Okular crashes when I try to open a specific epub file Product: okular Version: 1.7.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: EPub backend Assignee: okular-de...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Operating System: Arch Linux KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.2 Application: Okular (okular), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f939816c800 (LWP 7007))] Thread 4 (Thread 0x7f9386836700 (LWP 7010)): #0 0x7f939b558bac in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9386c92254 in () at /usr/lib/dri/i965_dri.so #2 0x7f9386c91f78 in () at /usr/lib/dri/i965_dri.so #3 0x7f939b552a92 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f939c203cd3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f93950cd700 (LWP 7009)): #0 0x7f9398e5c414 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f9398eacd3a in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #2 0x7f9398eae636 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f9398eae77e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f939c732cb4 in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f9388000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f939c6dba8c in QEventLoop::exec(QFlags) (this=this@entry=0x7f93950ccd70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f939c51f569 in QThread::exec() (this=this@entry=0x7f939ca22080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f939c9a6ba6 in QDBusConnectionManager::run() (this=0x7f939ca22080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7f939c52096c in QThreadPrivate::start(void*) (arg=0x7f939ca22080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #9 0x7f939b552a92 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f939c203cd3 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f939714e700 (LWP 7008)): #0 0x7f939c1f90d1 in poll () at /usr/lib/libc.so.6 #1 0x7f939b7d7630 in () at /usr/lib/libxcb.so.1 #2 0x7f939b7d92db in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f9397d21989 in QXcbEventQueue::run() (this=0x5597904b5790) at qxcbeventqueue.cpp:228 #4 0x7f939c52096c in QThreadPrivate::start(void*) (arg=0x5597904b5790) at thread/qthread_unix.cpp:361 #5 0x7f939b552a92 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f939c203cd3 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f939816c800 (LWP 7007)): [KCrash Handler] #6 0x7f939465172f in std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_relaxed, this=0x41f289d0468d4412) at /usr/include/c++/8.3.0/bits/atomic_base.h:390 #7 0x7f939465172f in QAtomicOps::load(std::atomic const&) (_q_value=...) at /usr/include/qt/QtCore/qatomic_cxx11.h:227 #8 0x7f939465172f in QBasicAtomicInteger::load() const (this=0x41f289d0468d4412) at /usr/include/qt/QtCore/qbasicatomic.h:103 #9 0x7f939465172f in QtPrivate::RefCount::isShared() const (this=0x41f289d0468d4412) at /usr/include/qt/QtCore/qrefcount.h:101 #10 0x7f939465172f in QLinkedList::detach() (this=0x7f939c761768 ) at /usr/include/qt/QtCore/qlinkedlist.h:106 #11 0x7f939465172f in QLinkedList::append(Okular::ObjectRect* const&) (this=this@entry=0x7f939c761768 , t=@0x7ffe90feb5c0: 0x55979130e910) at /usr/include/qt/QtCore/qlinkedlist.h:394 #12 0x7f9394657c2a in Okular::TextDocumentGenerator::loadDocumentWithPassword(QString const&, QVector&, QString const&) (this=, fileName=..., pagesVector=..., password=...) at /usr/include/qt/QtCore/qrect.h:528 #13 0x7f939463139c in Okular::DocumentPrivate::openDocumentInternal(KPluginMetaData const&, bool, QString const&, QByteArray const&, QString const&) (this=0x5597905a7450, offer=..., isstdin=isstdin@entry=false, docFile=..., filedata=..., password=...) at /usr/src/debug/okular-19.04.0/core/document.cpp:875 #14 0x7f9394631a22 in Okular::Document::openDocument(QString const&, QUrl const&, QMimeType const&, QString const&) (this=this@entry=0x55979054b2a0, docFile=..., url=..., _mime=..., password=...) at /usr/src/debug/okular-19.04.0/core/document.cpp:2443 #15 0x7f93947b4815 in Okular::Part::doOpenFile(QMimeType const&, QString const&, bool*) (this=this@entry=0x559790533820, mimeA=..., fileNameToOpenA=..., isCompressedFile=isCompressedFile@entry=0x7ffe90feba37) at
[systemsettings] [Bug 406737] Added scripts cannot be later edited, as opposed to added programs
https://bugs.kde.org/show_bug.cgi?id=406737 vytas changed: What|Removed |Added Version|unspecified |5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 406737] New: Added scripts cannot be later edited, as opposed to added programs
https://bugs.kde.org/show_bug.cgi?id=406737 Bug ID: 406737 Summary: Added scripts cannot be later edited, as opposed to added programs Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_autostart Assignee: mon...@kde.org Reporter: vytas.n...@gmail.com Target Milestone: --- SUMMARY If a script (via add script) is added to the list, it later cannot be edited, as opposed to programs (via add program) which can be edited at any time. STEPS TO REPRODUCE 1. add any script from /usr/bin to the list 2. try to edit it once its added OBSERVED RESULT cannot be edited EXPECTED RESULT should be able to edit to have feature parity between add program and add script. SOFTWARE/OS VERSIONS Operating System: Fedora 29 KDE Plasma Version: 5.14.5 Qt Version: 5.11.3 KDE Frameworks Version: 5.55.0 Kernel Version: 5.0.7-200.fc29.x86_64 OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406735] Some shortcuts in Layers docker are broken or not the same as the Reference Manual
https://bugs.kde.org/show_bug.cgi?id=406735 --- Comment #3 from vanyossi --- Thanks! I was missing the other 2 shortcuts. :) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404698] Decryption Oracle based on replying to PGP or S/MIME encrypted emails
https://bugs.kde.org/show_bug.cgi?id=404698 David Faure changed: What|Removed |Added CC||fa...@kde.org --- Comment #11 from David Faure --- Interesting problem. Here's my feedback. - Preventing KMail from *sending* such messages would obviously be no help (one could just craft that message by hand or using another email client). - Preventing the user from replying to such a message would be very weird user experience (sorry, you are not allowed to reply to this message!) - So I guess the best solution is that when replying, we don't decrypt parts that were encrypted in the original message. I.e. if we are replying with a copy of those parts, and they were encrypted, they should be copied "as is". This would prevent any newly-added recipient from reading those, but that's fair enough I would say. I wouldn't really know how to implement this though. Might be tricky if the tree in memory only has the decrypted version. - Alternatively, KMail could say "for security reasons, these parts are going to be removed from your reply". But this also requires that we somehow know that these parts used to be encrypted in the original email. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406294] Mobile device displays two identical "Open with File Manager" items in Device Notifier
https://bugs.kde.org/show_bug.cgi?id=406294 Nate Graham changed: What|Removed |Added Latest Commit|https://commits.kde.org/kam |https://commits.kde.org/kio |era/c3a2dd14f88f9caa61ad867 |-extras/04a98bfd2a66dea494a |18f8bfaf3c385e17a |55c23c1e9b2538c0675a7 --- Comment #3 from Nate Graham --- Git commit 04a98bfd2a66dea494a55c23c1e9b2538c0675a7 by Nate Graham. Committed on 21/04/2019 at 17:05. Pushed by ngraham into branch 'master'. Give the Solid action a more descriptive name FIXED-IN: 19.08.0 M +1-1mtp/solid_mtp.desktop https://commits.kde.org/kio-extras/04a98bfd2a66dea494a55c23c1e9b2538c0675a7 -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 406587] Autodrop stops in freecell
https://bugs.kde.org/show_bug.cgi?id=406587 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org, ||shlo...@shlomifish.org --- Comment #3 from Albert Astals Cid --- Shlomi is this related to the changes you made to the solver? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406735] Some shortcuts in Layers docker are broken or not the same as the Reference Manual
https://bugs.kde.org/show_bug.cgi?id=406735 --- Comment #2 from Tyson Tan --- Sorry, I didn't know about that! Keep up the good work! :) -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 406736] New: Sidebar - toggle fixed width
https://bugs.kde.org/show_bug.cgi?id=406736 Bug ID: 406736 Summary: Sidebar - toggle fixed width Product: Falkon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: sgd.or...@gmail.com Target Milestone: --- SUMMARY Add option to toggle fixed width for sidebar. In opther words allow or forbid resize of the sidebar. User should be able to change this option on the fly. This would be helpful for function / plugins when sidebar is always visible. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406735] Some shortcuts in Layers docker are broken or not the same as the Reference Manual
https://bugs.kde.org/show_bug.cgi?id=406735 wolthera changed: What|Removed |Added Status|CONFIRMED |ASSIGNED Assignee|krita-bugs-n...@kde.org |ghe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406735] Some shortcuts in Layers docker are broken or not the same as the Reference Manual
https://bugs.kde.org/show_bug.cgi?id=406735 wolthera changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||griffinval...@gmail.com --- Comment #1 from wolthera --- Ivan's already been working on this for a few days now :) : https://invent.kde.org/kde/krita/merge_requests/5 I think it got lost when the layer docker was reworked. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 406732] Some digits of the clock are invisible on the screenlocker
https://bugs.kde.org/show_bug.cgi?id=406732 --- Comment #2 from Gicdillah --- (In reply to David Edmundson from comment #1) > nvidia after resume? No, it's Intel builtin video. Suspend and hibernate not used on that machine. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406735] New: Some shortcuts in Layers docker are broken or not the same as the Reference Manual
https://bugs.kde.org/show_bug.cgi?id=406735 Bug ID: 406735 Summary: Some shortcuts in Layers docker are broken or not the same as the Reference Manual Product: krita Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: tysont...@gmail.com Target Milestone: --- In the Reference Manual: #: ../../reference_manual/dockers/layers.rst:79 :kbd:`Shift + Ctrl` for selecting multiple layers. Should be :kbd:`Shift or Ctrl` for selecting multiple layers. #: ../../reference_manual/dockers/layers.rst:88 :kbd:`Alt` + |mouseleft| on the thumbnail for isolated view of a layer. is now actually :kbd:`Alt` + |mouseleft| on the LAYER NAME for isolated view of a layer. #: ../../reference_manual/dockers/layers.rst:89 :kbd:`Shift` + |mouseleft| on the eye-icon for hiding all but the current layer. This is not working. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 406732] Some digits of the clock are invisible on the screenlocker
https://bugs.kde.org/show_bug.cgi?id=406732 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||k...@davidedmundson.co.uk Status|REPORTED|NEEDSINFO --- Comment #1 from David Edmundson --- nvidia after resume? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398973] The window decorations configuration pop-up needs a Defaults icon
https://bugs.kde.org/show_bug.cgi?id=398973 --- Comment #9 from David Edmundson --- >Is your patch included in Qt 5.13 beta2 David? Yes, but we need the matching breeze side to set the icon. That's not merged as it's hard to merge a frameworks patch against non-released code in case it changes later. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 406734] New: "Acquire screenshot" feature does not work on Wayland
https://bugs.kde.org/show_bug.cgi?id=406734 Bug ID: 406734 Summary: "Acquire screenshot" feature does not work on Wayland Product: kolourpaint Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: bugsefor...@gmx.com Target Milestone: --- STEPS TO REPRODUCE 1. open kolourpaint on Wayland session 2. click "File" menu, select "Acquire screenshot" 3. click "Ok" button to take a screenshot OBSERVED RESULT kolourpaint does not take a screenshot EXPECTED RESULT kolourpaint takes a screenshot SOFTWARE/OS VERSIONS KolourPaint Version 19.07.70 Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave
https://bugs.kde.org/show_bug.cgi?id=406684 --- Comment #6 from avlas --- link to flatpak issue: https://github.com/flatpak/flatpak/issues/2846 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 Lukas Winkler changed: What|Removed |Added CC||k...@lw1.at -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406709] Screen Edge/Present WIndows Effect BLOCKS Auto-Lock of Desktop
https://bugs.kde.org/show_bug.cgi?id=406709 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from David Edmundson --- *** This bug has been marked as a duplicate of bug 234153 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 234153] Effects grabbing keyboard prevent screen locking
https://bugs.kde.org/show_bug.cgi?id=234153 David Edmundson changed: What|Removed |Added CC||rinkydink...@gmail.com --- Comment #17 from David Edmundson --- *** Bug 406709 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave
https://bugs.kde.org/show_bug.cgi?id=406684 --- Comment #5 from avlas --- I could make flatpak octave executable visible to flatpak cantor by doing: sudo flatpak override --filesystem=/var org.kde.cantor However it seems that this trick is not enough and communication between the two flatpak processes does not work as expected, i.e. any instruction makes cantor turn crazy waiting for a never reached octave's response, with a 100% CPU issue. I think I will open an issue in flatpak to see how this is expected to be done... In the meantime I would like to mention a usability issue in the context of point (1) above: I would recommend against filtering not configured backends at cantor startup (if not default backend is set). This is a matter of usability, mostly important for new users trying cantor: A new user may want to use e.g. Octave to make it default and configure its path (if not automatically detected). With current filtering this is not an option and gives the impression that such an option is not supported. So most final users will give up. Advanced users may realize that they can open any other available backend (if any) and go to settings to configure e.g. Octave's path. This is far from ideal. Ideally, all backends would be present without filtering. Then, if one selects a backend that is not properly configured, settings should be opened, so the user can set them right. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405847] SFTP corrupts DNG files
https://bugs.kde.org/show_bug.cgi?id=405847 Mark Fraser changed: What|Removed |Added CC||mfraz74+...@gmail.com --- Comment #9 from Mark Fraser --- I've started noticing problems with this today, doesn't happen with smaller files although I just tried opening a 70 kB xlsx file and that wouldn't work. Small jpgs and pdfs seem to be OK, but anything else breaks. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406725] Allow folders to be excluded for thumbnail generation
https://bugs.kde.org/show_bug.cgi?id=406725 Julian Schraner changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||m...@xyquadrat.ch --- Comment #1 from Julian Schraner --- Hello Isaak, if I understand your report correctly, this feature is actually already present in Dolphin. Go to the Settings->General->View and choose "Remember properties for each folder". Afterwards, the preview setting will work on a per-folder basis. Be aware that this also let's Dolphin remember other changes to the view properties, such as Details mode vs Icon mode or the icon size. Does that fulfill your needs or have I misunderstood your request? -- You are receiving this mail because: You are watching all bug changes.
