[plasmashell] [Bug 407757] Notifications from kdeconnect all display in the centre of the screen on top of each other
https://bugs.kde.org/show_bug.cgi?id=407757 --- Comment #17 from Kai Uwe Broulik --- I just tried on a neon dev unstable ISO from yesterday and my patch fixes Latte dock there. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 407890] Setttings window is a blurry rectangle
https://bugs.kde.org/show_bug.cgi?id=407890 --- Comment #1 from Michail Vourlakos --- 1. Close Latte 2. Run from terminal: "latte-dock -d" 3. reproduce the issue 4. send the full output of the terminal -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407691] Hangs on Startup, with Album on Network share (on MacOS)
https://bugs.kde.org/show_bug.cgi?id=407691 --- Comment #19 from kde-bugtrac...@schmu.net --- Good news, Digikam (digiKam-6.2.0-git-20190524T080110-MacOS-x86-64.pkg) is starting now. It still stays on the "checking ICC Profiles" for a minute or to and is not responding in that phase, but after that it works as expected. Thanks for all your efforts! Thomas -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 407890] New: Setttings window is a blurry rectangle
https://bugs.kde.org/show_bug.cgi?id=407890 Bug ID: 407890 Summary: Setttings window is a blurry rectangle Product: lattedock Version: 0.8.8 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: s...@amshove.org Target Milestone: --- Created attachment 120281 --> https://bugs.kde.org/attachment.cgi?id=120281&action=edit Blurry settings window under the cursor Hello, I've freshly set up OpenSuSe Leap 15.1 and installed Latte 0.8.8 via Zypper from the official SuSe Repository. Latte is starting up correctly, however the settings window is "just a blurry rectancle", e.g. it doesn't show anything, nor does it allow me to configure anything. I've made sure that there are no settings under ~/.config/latte*, so it has a fresh start. STEPS TO REPRODUCE 1. Install Latte 2. Start Latte 3. Right click on dock, open settings OBSERVED RESULT Blurry window (see attached screenshot where the cursor is) EXPECTED RESULT Settings window SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Leap 15.1 with KDE Plasma (available in About System) KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.55.0 Qt Version: 5.9.7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407881] new notifications system does not work with Snap package of Discord
https://bugs.kde.org/show_bug.cgi?id=407881 --- Comment #3 from Kai Uwe Broulik --- The file is cut off at the top, you might want to redirect the output of dbus-monitor directly into a file. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 407887] i think it would be better to use sddm as lockscreen and both use the same theme
https://bugs.kde.org/show_bug.cgi?id=407887 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |NOT A BUG CC||k...@privat.broulik.de Status|REPORTED|RESOLVED --- Comment #1 from Kai Uwe Broulik --- You may think so but there's technical reasons not do so. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 365210] Unable to browse simple gzip/bzip files as an archive
https://bugs.kde.org/show_bug.cgi?id=365210 Nikita Melnichenko changed: What|Removed |Added CC||ver...@basealt.ru --- Comment #5 from Nikita Melnichenko --- *** Bug 403545 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 403545] Can't open file *.xz - protocol is not supported
https://bugs.kde.org/show_bug.cgi?id=403545 Nikita Melnichenko changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||nikita+...@melnichenko.name Resolution|--- |DUPLICATE --- Comment #2 from Nikita Melnichenko --- *** This bug has been marked as a duplicate of bug 365210 *** -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 392133] Huge memory consumption while doing nothing
https://bugs.kde.org/show_bug.cgi?id=392133 Nikita Melnichenko changed: What|Removed |Added Status|REOPENED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #25 from Nikita Melnichenko --- >From the report, the peak allocations happen in Qt5 and KF5 libs. I don't see any actual krusader code involved, just internal event handlers. Most heap peak is coming from libKF5Solid, which is a hardware tracker. Wild guess: if you have a faulty hardware that keeps disconnecting-reconnecting, it frequently triggers those event in Solid, which connect Qt objects and doing other stuff keeping track every such event. When you close Krusader, all the memory from this "hardware log" is freed and we see no leaks. It will be helpful if you get debug symbols for KF5 libs as well and rerun the tool, then it may give us a clue on what kind of event it is. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405010] Don't show a notification badge with a zero when there aren't any notifications
https://bugs.kde.org/show_bug.cgi?id=405010 --- Comment #4 from Jan Przybylak --- Yes -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 391038] Weird little widget that shows the desktop wallpaper shown over the mail window
https://bugs.kde.org/show_bug.cgi?id=391038 --- Comment #6 from Laurent Montel --- Git commit 21121ab09438360a06efca675f3670ed8c9c9b1c by Laurent Montel. Committed on 24/05/2019 at 05:53. Pushed by mlaurent into branch 'Applications/19.04'. It's not necessary to create a view. Perhaps it will fix this bug M +3-4templateparser/src/templateextracthtmlelementwebengineview.cpp M +2-2templateparser/src/templateextracthtmlelementwebengineview.h M +3-4templateparser/src/templatewebengineview.cpp M +2-2templateparser/src/templatewebengineview.h https://commits.kde.org/messagelib/21121ab09438360a06efca675f3670ed8c9c9b1c -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 400956] The date/time format of the LC_TIME locale is not regarded
https://bugs.kde.org/show_bug.cgi?id=400956 Nikita Melnichenko changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED CC||nikita+...@melnichenko.name --- Comment #7 from Nikita Melnichenko --- The ~/.kde/share/config/kdeglobals was not platform-independent. It was supported by custom logic in KDE4 libs (KLocale class), AFAIR. https://community.kde.org/KDE_Core/KLocale#Qt5_.2F_KDE5 > Using KLocale (and thus KConfig) is a major barrier to Qt-only apps adopting > our libraries so we should try remove the need for KLocale where-ever > possible. Much can be achieved by pushing KLocale features into QLocale and > ensuring QLocale fully supports all options common to all the platforms (some > options are still not supported, or are only properly supported on some > platforms). So we migrated to QLocale during KF5 migration. I agree that system setting should be respected in Qt (in case not explicitly overridden). Please open a bug in Qt bug tracker and reference it here. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 407475] Search dialog hides the KrViewer opened from it
https://bugs.kde.org/show_bug.cgi?id=407475 Nikita Melnichenko changed: What|Removed |Added CC||nikita+...@melnichenko.name --- Comment #1 from Nikita Melnichenko --- For the record, I can't repro with the following versions: KDE Frameworks Version: 5.54.1 Qt Version: 5.11.3 Can you try to build from source: v2.8.0-dev (master branch) or v2.7.2-dev (stable branch)? We have some bug fixes related to changed APIs. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 357171] Create new symlink dialog shows directories but not files
https://bugs.kde.org/show_bug.cgi?id=357171 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.59 Latest Commit||https://commits.kde.org/kio ||/95d0b44a3837a9e121ab90fdec ||8a239422d713fd Status|CONFIRMED |RESOLVED --- Comment #12 from Nate Graham --- Git commit 95d0b44a3837a9e121ab90fdec8a239422d713fd by Nate Graham, on behalf of Robert Hoffmann. Committed on 24/05/2019 at 05:18. Pushed by ngraham into branch 'master'. Fix desktop link to file or directory Summary: KUrlRequester: Show a popup to select between File and Directory before displaying the file dialog. Test Plan: Right click onto desktop, select 'Create new' and then 'Basic link to file or directory' or 'Link to Location (URL)'. Click the file selection icon. A popup is displayed. If 'File' is selected, a file dialog is displayed, showing files and directories, allowing the selection of a file. If 'Directory' is selected, a file dialog is displayed, showing only directories, allowing the selection of a directory. Without the patch, no popup is displayed, only directories are shown in the file dialog and only a directory can be selected. FIXED-IN: 5.59 Reviewers: #frameworks, ngraham, dfaure Reviewed By: ngraham, dfaure Subscribers: bruns, michaelweghorn, ngraham, kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D20197 M +73 -28 src/widgets/kurlrequester.cpp https://commits.kde.org/kio/95d0b44a3837a9e121ab90fdec8a239422d713fd -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 390718] KrViewer: Tab scrolling using arrows is not working when too many tabs are open
https://bugs.kde.org/show_bug.cgi?id=390718 --- Comment #7 from Nikita Melnichenko --- As I recall, we discussed this internally some time ago and we think it may be related to an upstream bug. So far we don't have any solution but patches are always welcome! As a workaround you may use Ctrl+Tab, Ctrl+Shift+Tab or Ctrl+], Ctrl+[ for tab switching. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 407102] Single instance not working in root mode
https://bugs.kde.org/show_bug.cgi?id=407102 Nikita Melnichenko changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #5 from Nikita Melnichenko --- Try $ su - $ krusader & $ krusader /home/ & Sudo is not the same as root. https://superuser.com/questions/771500/sudo-vs-root-any-actual-differences -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 391038] Weird little widget that shows the desktop wallpaper shown over the mail window
https://bugs.kde.org/show_bug.cgi?id=391038 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Laurent Montel --- I confirm it I will investigate it -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407878] Text Editing window is drawn behind floating dockers
https://bugs.kde.org/show_bug.cgi?id=407878 vanyossi changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||krita/commit/cd4d6453dac73d ||9d0851e7b2f63589bf0824fc82 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from vanyossi --- Git commit cd4d6453dac73d9d0851e7b2f63589bf0824fc82 by Ivan Yossi. Committed on 24/05/2019 at 04:42. Pushed by ivany into branch 'master'. Re-enable svgTextTool as a modal window It has to be this way to avoid being covered by tool windows, and before changing to nonModal as Tool window, a workaround for shortcuts must be made. As a Tool window the menu is not shown, making some edition options unavailable. BACKPORT:krita/4.2 M +1-1plugins/tools/svgtexttool/SvgTextTool.cpp https://invent.kde.org/kde/krita/commit/cd4d6453dac73d9d0851e7b2f63589bf0824fc82 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374748] Cursor dissapears when brush-size is 0px without pressure
https://bugs.kde.org/show_bug.cgi?id=374748 vanyossi changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/c5695b3dedf35f ||4bc530aa8012cd212dd3e2b667 --- Comment #4 from vanyossi --- Git commit c5695b3dedf35f4bc530aa8012cd212dd3e2b667 by Ivan Yossi. Committed on 24/05/2019 at 04:52. Pushed by ivany into branch 'master'. Set minimum brush size for slider same as shift-drag BACKPORT:krita/4.2 M +1-1libs/ui/kis_paintop_box.cc https://invent.kde.org/kde/krita/commit/c5695b3dedf35f4bc530aa8012cd212dd3e2b667 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407804] Clicking on the layer thumbnail in layers docker does not effect by choosing/selecting layer
https://bugs.kde.org/show_bug.cgi?id=407804 vanyossi changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/e775a0e8250163 ||3b5769e17263fa7ad5d036a29e Resolution|--- |FIXED --- Comment #3 from vanyossi --- Git commit e775a0e82501633b5769e17263fa7ad5d036a29e by Ivan Yossi. Committed on 24/05/2019 at 02:52. Pushed by ivany into branch 'master'. Click layer thumbnail with no modifier set layer selected BACKPORT:krita/4.2 M +1-0plugins/dockers/layerdocker/NodeDelegate.cpp https://invent.kde.org/kde/krita/commit/e775a0e82501633b5769e17263fa7ad5d036a29e -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376086] Shift + Clicking a layer eye icon does not hide other layers
https://bugs.kde.org/show_bug.cgi?id=376086 --- Comment #4 from vanyossi --- I made an implementation (currrently on merge request) But now Im doubtfull this feature make sense when "isolate layer" does something very similar. The shift + click on the patch hides all layers except the layers needed for the clicked layer to be visible (it will not hide their children also). A scon dclick restores the state as it was before. However because there are some other eyes present dmitry found it very confusing. I don't know how this feature is supposed to look, should we disable all eye icons except the one that was clicked? -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405010] Don't show a notification badge with a zero when there aren't any notifications
https://bugs.kde.org/show_bug.cgi?id=405010 --- Comment #3 from Laurent Montel --- Did you use plasma kde ? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407369] Okular crashes when opening a digitally signed pdf file.
https://bugs.kde.org/show_bug.cgi?id=407369 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404191] Ark can't open kra zip files
https://bugs.kde.org/show_bug.cgi?id=404191 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405107] Krita crashes once pointing canvas with graphics tablet
https://bugs.kde.org/show_bug.cgi?id=405107 --- Comment #10 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.
[kde] [Bug 407350] Problems loading desktop themes with plasma kde in debian stretch
https://bugs.kde.org/show_bug.cgi?id=407350 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407850] Open EXR 16-bit float images conflicts with gamma correction of 8-bit integer png images
https://bugs.kde.org/show_bug.cgi?id=407850 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 407227] Mint 19.1 on 64bit laptop .... kde-spectacle white-screens, requiring rebooting
https://bugs.kde.org/show_bug.cgi?id=407227 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377615] Sketch brush engine visual size change
https://bugs.kde.org/show_bug.cgi?id=377615 vanyossi changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from vanyossi --- This no longer happens in master. It seems dmitry implemented a force to make outline appear on max size. Now sketch engine uses a circular otuline as preview. I tested all Sketch engine brushes from different authors, and also made a couple in krita. Also checked, and the code to display the outline is there. It seems the relevant pieces are there since June 5 2018. I think we forgot to close this bug. @n-pigeon do you still get this bug? I'll mark as resolved for now -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367851] Folder View in Panel: deleting folders can break keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=367851 Alex changed: What|Removed |Added CC||amd...@yandex.com --- Comment #3 from Alex --- I can't reproduce this by following those steps, I tried a few times. But following the steps to reproduce bug 407889 I reliably get this issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407889] New: Shift-clicking in folder view with list view mode stops working properly after a restart
https://bugs.kde.org/show_bug.cgi?id=407889 Bug ID: 407889 Summary: Shift-clicking in folder view with list view mode stops working properly after a restart Product: plasmashell Version: 5.15.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: amd...@yandex.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 120280 --> https://bugs.kde.org/attachment.cgi?id=120280&action=edit Demonstration 1 SUMMARY When restarting plasmashell, logging out or rebooting the folder view widget in list view mode stops working properly and shift-clicking to select multiple items at once becomes unreliable. Doing this will also make keyboard navigation stop working as described in bug 367851. STEPS TO REPRODUCE 1. Add a Folder View widget with list view mode pointing to any directory containing some files. 2. Do any of the following: Restart plasmashell via terminal (kquitapp5 plasmashell and then kstart5 plasmashell), or log out and log back in, or reboot the computer. OBSERVED RESULT Shift-clicking no longer works reliably. EXPECTED RESULT Shift-clicking still works normally. SOFTWARE/OS VERSIONS KDE Neon Testing KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407877] Layer content not shown when file opened
https://bugs.kde.org/show_bug.cgi?id=407877 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com --- Comment #3 from vanyossi --- It happens for me on any .kra file .png, .psd, .jpg all show the contents on first load. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407878] Text Editing window is drawn behind floating dockers
https://bugs.kde.org/show_bug.cgi?id=407878 vanyossi changed: What|Removed |Added Ever confirmed|0 |1 CC||ghe...@gmail.com Status|REPORTED|CONFIRMED Assignee|krita-bugs-n...@kde.org |ghe...@gmail.com --- Comment #1 from vanyossi --- I made that change. The idea is to have the text tool open like modal window and edit the text more readily. I did try the text tool over all, but the problem was that if I made it a tool window it would loose the menu. Maybe I missed something to make it also go above the tool windows. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407888] New: Items remain with a different "strong" highlight color after drag-and-dropping them
https://bugs.kde.org/show_bug.cgi?id=407888 Bug ID: 407888 Summary: Items remain with a different "strong" highlight color after drag-and-dropping them Product: plasmashell Version: 5.15.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: amd...@yandex.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 120279 --> https://bugs.kde.org/attachment.cgi?id=120279&action=edit Demonstration 1 SUMMARY When you select any item inside a folder view and drag-and-drop it somewhere, it will remain with a different "stronger" highlight color unless you successfully move it to somewhere else. STEPS TO REPRODUCE 1. Add a Folder View widget pointing to any directory with some files. 2. Drag-and-drop any item to wherever you want, but don't move it (copying or simply canceling it works). OBSERVED RESULT The item returns to the folder view with a different, stronger highlight color when selected again. EXPECTED RESULT The item returns to the folder view with a regular highlight color when selected again. SOFTWARE/OS VERSIONS KDE Neon Testing KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION See attachment, it's very easy to see the difference in list view mode. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 407887] New: i think it would be better to use sddm as lockscreen and both use the same theme
https://bugs.kde.org/show_bug.cgi?id=407887 Bug ID: 407887 Summary: i think it would be better to use sddm as lockscreen and both use the same theme Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: driya...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY 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.
[plasmashell] [Bug 407886] New: Hovering over or selecting items inside a folder view in list view mode with the cursor is very unreliable
https://bugs.kde.org/show_bug.cgi?id=407886 Bug ID: 407886 Summary: Hovering over or selecting items inside a folder view in list view mode with the cursor is very unreliable Product: plasmashell Version: 5.15.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: amd...@yandex.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 120278 --> https://bugs.kde.org/attachment.cgi?id=120278&action=edit Demonstration 1 STEPS TO REPRODUCE 1. Add a Folder View widget pointing to any directory with a few files 2. Hover your cursor over any files and even try to select them by clicking, it's very unreliable OBSERVED RESULT Items don't reliably get highlighted when hovering the cursor over them, this also prevents them from being selected with a click. EXPECTED RESULT Hovering the cursor over items always highlights them properly. SOFTWARE/OS VERSIONS KDE Neon Testing KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION Moving the cursor slowly makes it very easy to reproduce, but it can also happen with normal speed and is easily noticeable during regular use. Most of the time this happens with the last item shown, but it can happen with any item for example if your cursor is coming from the right. Currently can't reproduce with icons view mode. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'
https://bugs.kde.org/show_bug.cgi?id=407778 --- Comment #17 from Robert --- Awesome, glad to hear. I look forward to trying out the next release :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407885] New: Unable to clear history in "Do Not Disturb" mode.
https://bugs.kde.org/show_bug.cgi?id=407885 Bug ID: 407885 Summary: Unable to clear history in "Do Not Disturb" mode. Product: plasmashell Version: 5.15.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: danielrios.flame...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The button to clear history is not showing when there is a notification in "Do Not Disturb" mode. STEPS TO REPRODUCE 1. Activate "Do Not Disturb" Mode. 2. Waits for two or more notifications or create them with "notify-send" command. It will not appear on the screen, since "Do Not Disturb" is active. 3. Open Notifications popup and you'll see that you have to close notification one by one, there is not "clear history" button. OBSERVED RESULT I think this happens because they are not expired notifications since they weren't shown on the screen. EXPECTED RESULT "Close history" button should clear all notification history, be expired or not. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon Unstable Edition (available in About System) KDE Plasma Version: 5.15.90 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385522] Present Windows: Don't darken all windows and denote selection some other way than restoring original lightness
https://bugs.kde.org/show_bug.cgi?id=385522 --- Comment #24 from leftcrane --- Why even have an option for dimming? All it does is make it harder to identify windows (virtually impossible in desktop grid) - why would anyone ever want this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407840] Left side vertical panels have a thinner clickable area than panels on other sides of the screen
https://bugs.kde.org/show_bug.cgi?id=407840 --- Comment #2 from Noah Davis --- This problem does not exist on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 401863] baloo creates multiple entries for files residing on multi-device btrfs file systems
https://bugs.kde.org/show_bug.cgi?id=401863 Johannes Tiemer changed: What|Removed |Added CC||jtie...@gmail.com --- Comment #2 from Johannes Tiemer --- I am experiencing the same behaviour. Baloo returns all results threefold regardless whether I search in the shell or via dolphin and ctrl+f. It does _not_ return triple results via krunner though. I have three partitions mounted to /home or parts of my home directory. Actually four, but the fourth is excluded from the search. The total number of partitions is seven. The file system on all partitions is ext4. - number of returned finds equals the number of partitions in the search path - the file system seems not to be involved SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (5.1.3.arch2-1) KDE Plasma Version: 5.15.5-1 KDE Frameworks Version: 5.58.0.1 Qt5 Version: 5.12.3-2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407691] Hangs on Startup, with Album on Network share (on MacOS)
https://bugs.kde.org/show_bug.cgi?id=407691 --- Comment #18 from kde-bugtrac...@schmu.net --- Ad if I unmount the network share, it stops showing pairs and going to start like before. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407691] Hangs on Startup, with Album on Network share (on MacOS)
https://bugs.kde.org/show_bug.cgi?id=407691 --- Comment #17 from kde-bugtrac...@schmu.net --- (In reply to Maik Qualmann from comment #14) > Ok, interesting. Do I understand it correctly that always an in-out pair is > displayed immediately, it takes only in between long? Not only one a lot of coming fast and then it gets slower and slower. Bye Thomas -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407884] New: Previous/Next Bookmark don’t work correctly if triggered from Contents side panel context menu
https://bugs.kde.org/show_bug.cgi?id=407884 Bug ID: 407884 Summary: Previous/Next Bookmark don’t work correctly if triggered from Contents side panel context menu Product: okular Version: 1.7.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: david.hu...@mailbox.org Target Milestone: --- SUMMARY Just discovered that the context menu in the Contents side panel offers the two actions “Previous Bookmark” and “Next Bookmark”. They are put in a section named "Page N", where N is the *number* of the page to which the current item in the Contents tree view points. Nevertheless, these two actions use the current viewport for determining the next/previous bookmark, not the page N like the section title suggests. STEPS TO REPRODUCE 1. Open a document with many pages and TOC 2. Create some bookmarks roughly at 1/3 and 2/3 of the document 3. Go to the middle of the document 4. Open the Contents panel 5. Open the context menu on the first item. 6. The section “Page 1” contains the action “Next Bookmark” OBSERVED RESULT Okular::Part::m_nextBookmark is triggered and brings me to the bookmark at 2/3 of the document. EXPECTED RESULT The next bookmark from page 1 is at 1/3 of the document, so it brings me there. I expect the action to respect the page number in the section title, because the other actions in the section (“Add Bookmark”) also do. SOFTWARE/OS VERSIONS KDE Neon 5.15.5 KDE Plasma 5.58.0 Qt 5.12.0 Okular 1.7.1 ADDITIONAL INFORMATION The context menu ist built in Okular::Part::slotShowTOCMenu(), which calls Okular::Part::showMenu(). This adds the actions “Add Bookmark” / “Remove Bookmark” and “Fit Width” to the context menu. These actions are custom made for page N. However, it also adds m_prevBookmark and m_nextBookmark, which don’t know anything about page N. When triggered, they just fetch the current viewport. ADDITONAL ADDITIONAL INFORMATION In the summary, I wrote: "Page N", where N is the *number* of the page. However, the Contents tree view items show the *name* of the page. This may be confusing, because the user might see two different numbers in the tree view item and the context menu. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 407838] Plasma-nm NetworkManager OpenConnect VPN login button is badly translated in italian
https://bugs.kde.org/show_bug.cgi?id=407838 --- Comment #4 from Vincenzo Reale --- (In reply to Renato from comment #0) > Created attachment 120256 [details] > Screenshot of openconnect window > > SUMMARY > > > STEPS TO REPRODUCE > 1. Select a openconnect VPN connection > 2. Login window is shown, enlarge it in order to show "connect" button (this > is due to https://bugs.kde.org/show_bug.cgi?id=403480) > 3. click connect button > 4. login form appears and "login" button is shown but the italian > translation is "Nome utente" which means "username" The issue has already been fixed a week ago (revision 1541748) Thank you for reporting. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407883] New: Previous/Next Bookmark actions not enabled/disabled correctly / do not cycle though bookmarks
https://bugs.kde.org/show_bug.cgi?id=407883 Bug ID: 407883 Summary: Previous/Next Bookmark actions not enabled/disabled correctly / do not cycle though bookmarks Product: okular Version: 1.7.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: david.hu...@mailbox.org Target Milestone: --- SUMMARY Just discovered that the context menu in the view area and the Bookmarks menu offer the two actions “Previous Bookmark” and “Next Bookmark”. These two are enabled as soon as there are Bookmarks in the current document. But they are enabled always, even if there is no previous or next bookmark. Clicking this action has no effect then. STEPS TO REPRODUCE 1. Open a document with many pages 2. Create some bookmarks somewhere in the middle 3. Go to the end of the document 4. Open the context menu in the view area or the Bookmarks menu OBSERVED RESULT Both actions “Previous Bookmark” and “Next Bookmark” are enabled. Clicking “Next Bookmark” has no effect. EXPECTED RESULT Only Previous Bookmark is enabled, because there is no next bookmark. Alternative: Previous/Next Bookmark cycle though bookmarks, so Next Bookmark goes to the first bookmark. SOFTWARE/OS VERSIONS KDE Neon 5.15.5 KDE Plasma 5.58.0 Qt 5.12.0 Okular 1.7.1 ADDITIONAL INFORMATION These actions are Okular::Part::m_prevBookmark and m_nextBookmark. They are updated in Okular::Part::rebuildBookmarkMenu(), which assumes cycling behaviour. To fix this, we need to decide whether these actions shall cycle though bookmarks or not. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406937] Cannot change icon theme in appimage
https://bugs.kde.org/show_bug.cgi?id=406937 --- Comment #2 from IWBR --- I just realized that the icon theme loads correctly when the Tree View Icon Size is set to 32, 48 or 64, but not 16 or 22. Maybe the icon theme does not have icon for the smallest sizes? -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 407882] New: After adding a new resource in KAlarm, it is not seen by KAlarm
https://bugs.kde.org/show_bug.cgi?id=407882 Bug ID: 407882 Summary: After adding a new resource in KAlarm, it is not seen by KAlarm Product: kalarm Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Akonadi Assignee: djar...@kde.org Reporter: djar...@kde.org Target Milestone: --- Add a new KAlarm calendar file resource. Its config file is created correctly, but it is not seen by KAlarm until Akonadi is restarted. Version 2.12.2, KDE Applications 19.04.1, on Neon. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 407544] KAlarm 19.04 doesn't work at all
https://bugs.kde.org/show_bug.cgi?id=407544 David Jarvie changed: What|Removed |Added Latest Commit||fe40ba8aa6e61beb9e3bf89742d ||f2b66091739ea Resolution|--- |FIXED Version Fixed In||19.04.2 Status|CONFIRMED |RESOLVED --- Comment #3 from David Jarvie --- This bug was caused by a mistake in porting the KAlarm resource to the config API (commit fe40ba8aa6e61beb9e3bf89742df2b66091739ea, 18 Aug 2018). Now fixed by kdepim-runtime commit fe40ba8aa6e61beb9e3bf89742df2b66091739ea. This will be in KAlarm version 2.12.3, which will be released as part of KDE Applications version 19.04.2. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407268] Adding keyframe to Postion and Zoom effect causes black screen in Project Monitor
https://bugs.kde.org/show_bug.cgi?id=407268 --- Comment #4 from khriss cortez --- Hi guys, I've just tested with several videos in both Arch/Plasma and Windows 10 (OSs fully updated) with Kdenlive 19.04.1 and the ISSUE PERSISTS, it has not been fixed yet. In Windows 10 at least the project screen is visible but in the final rendered video it only shows a white screen on the part the Position and Zoom effect has been applied. Please dig deeper on that, thanks in advance! PD. I troubleshooted by deleting the Kdenliverc and cache video configuration but it DIDN'T help at all. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 407780] Can't import with weboob 1.5: [err-5] La ligne de commandes suivante a échouée avec la code 1
https://bugs.kde.org/show_bug.cgi?id=407780 --- Comment #6 from chos...@laposte.net --- hi, rc=0 at the end. Le 22/05/2019 à 15:33, Stephane MANKOWSKI a écrit : > https://bugs.kde.org/show_bug.cgi?id=407780 > > --- Comment #5 from Stephane MANKOWSKI --- > Could you try this ? > PYTHONIOENCODING=utf_8 boobank ls -q -f csv -s id,label,balance; echo "rc="$? > > Do you have a 0 at the end? > If not, you must investigate why? > This is not due to Skrooge but to your weboob installation or configuration. > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407504] After changing the display resolution while a notification is showing does not change the position of the notification
https://bugs.kde.org/show_bug.cgi?id=407504 --- Comment #2 from Alex Nemeth --- I can confirm that this bug no longer happens with the latest build -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 384218] clear/^l shouldn't add empty lines to the scrollback buffer
https://bugs.kde.org/show_bug.cgi?id=384218 --- Comment #8 from Egmont Koblinger --- Good news: see update at https://bugzilla.gnome.org/show_bug.cgi?id=506438#c19. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407850] Open EXR 16-bit float images conflicts with gamma correction of 8-bit integer png images
https://bugs.kde.org/show_bug.cgi?id=407850 --- Comment #3 from iszotic --- The steps: 1) Open an OpenEXR image 2) It's pretty dark because it uses linear Gamma, then go to lut manager, use OpenColorIO, then color engine OCIO(enviroment), now set a standard gamma value of 2.2 3) Open a PNG file 4) PNG layer it's too white A workaround is to use the color adjustment curves on the PNG layers or set lut manager to a value of gamma 1.0 but then the OpenEXR layers get too dark and the PNG layers fine. PD: 4.17 doesn't have this issue. The OpenEXR layers are created in blender, with blender set with the default color manager instead of filmic and this used to show the same colors in blender and krita, now they don't, but I'm not concerned about using the lut manager but about PNG images that load with different lighting -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407881] new notifications system does not work with Snap package of Discord
https://bugs.kde.org/show_bug.cgi?id=407881 --- Comment #2 from Patrick Silva --- Created attachment 120277 --> https://bugs.kde.org/attachment.cgi?id=120277&action=edit output of dbus-monitor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395632] On RX Vega 64, KDE compositor does not run at 144Hz even though monitor refresh rate is set to 144Hz
https://bugs.kde.org/show_bug.cgi?id=395632 petrk changed: What|Removed |Added CC||pepk...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 407879] [KDE Konsole 19.04.1 - strange behaviour] "New Tab ->" shows a total listing of ... one entry, which must be selected
https://bugs.kde.org/show_bug.cgi?id=407879 --- Comment #1 from shevegen --- This image may help - easier to understand the problem I think: https://i.imgur.com/R3S9jjG.png -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 407000] "Defaults" button in "Global shortcuts" kcm sets all shortcuts of the task switcher to "None"
https://bugs.kde.org/show_bug.cgi?id=407000 petrk changed: What|Removed |Added CC||pepk...@gmail.com --- Comment #3 from petrk --- Confirming, I had to wipe my shortcuts manually. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407881] new notifications system does not work with Snap package of Discord
https://bugs.kde.org/show_bug.cgi?id=407881 --- Comment #1 from Kai Uwe Broulik --- Can you monitor notification dbus traffic and see what it does? dbus-monitor interface=org.freedesktop.Notifications Also, run plasma from console, enabling notification logging QT_LOGGING_RULES=org.kde.plasma.notifications=true plasmashell -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407881] new notifications system does not work with Snap package of Discord
https://bugs.kde.org/show_bug.cgi?id=407881 Patrick Silva changed: What|Removed |Added Summary|new noticiations system |new notifications system |does not work with Snap |does not work with Snap |package of Discord |package of Discord -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 407729] neon-settings package causes files in /sudoers.d to not be honored
https://bugs.kde.org/show_bug.cgi?id=407729 --- Comment #11 from Stuart K. Smith --- BTW, agreed on the security issue. I had narrowed it to just the specific PC and it's in a rather controlled environment. I had widened it (ALL ALL etc.) when trying to trouble shoot this issue. My laptop does not have this setup. I haven't ventured into polkit much, but worth a look. Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407881] New: new noticiations system does not work with Snap package of Discord
https://bugs.kde.org/show_bug.cgi?id=407881 Bug ID: 407881 Summary: new noticiations system does not work with Snap package of Discord Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: bugsefor...@gmx.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Notifications from Discord installed via Snap package stopped working after I install Plasma 5.16 beta on Arch Linux. I downgraded to Plasma 5.15.5 and now Plasma shows the notifications from Discord again. STEPS TO REPRODUCE 1. install Snap package of Discord https://snapcraft.io/discord 2. connect to Discord, chat to a friend and wait for a notification 3. OBSERVED RESULT Discord plays a notification sound but Plasma shows no notification EXPECTED RESULT Plasma shows notifications from Discord SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 Additional information Plasma does also not show notifications from Snap Discord on neon dev unstable -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407881] new noticiations system does not work with Snap package of Discord
https://bugs.kde.org/show_bug.cgi?id=407881 Patrick Silva changed: What|Removed |Added Version|master |5.15.90 Platform|Neon Packages |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 407729] neon-settings package causes files in /sudoers.d to not be honored
https://bugs.kde.org/show_bug.cgi?id=407729 --- Comment #10 from Stuart K. Smith --- Thank for the detailed info. Always good to be armed with the facts in my world. Funny you should make that recommendation about pkcon as I starting looking into it right after my last post here. My apt use was due to the burgeoning problems with early Discover in conjunction with Muon being without a dev. I just put apt into some aliases and made the suoders entry and went full CLI for updates and installations. That was about 5 years ago I think? pkcon looks good in the CLI and I'm looking at the GUIs also. Thanks again. Beverages on me if we ever meet in the real world :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 407271] KAboutData crashes when using git svn with KWallet
https://bugs.kde.org/show_bug.cgi?id=407271 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org --- Comment #3 from Antonio Rojas --- (In reply to Christoph Feck from comment #2) > I suggest to report this issue to the bug tracker of your distribution. This has gone throught downstream already. I have no idea what we are supposed to do about this TBH, this is reproducible in a plain Plasma session with unmodified KDE and svn packages. You just need a very specific setup to reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407880] New: Color swatch buttons do not return accurate values
https://bugs.kde.org/show_bug.cgi?id=407880 Bug ID: 407880 Summary: Color swatch buttons do not return accurate values Product: krita Version: 4.1.7 Platform: unspecified OS: macOS Status: REPORTED Severity: major Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: delgado@gmail.com Target Milestone: --- SUMMARY When selecting colors using color swatch buttons in Krita, OSX "Colors" dialogue (which Krita opens to select color) returns inaccurate color values to Krita. This dialogue is the only way to select color via a colorswatch button. STEPS TO REPRODUCE 1. Select any color swatch button to open the "Colors" dialogue (via color selector, palette editing pop-up, digital color mixer docker etc.) 2. Select specific color values and note RGB / hex values, click OK and save to palette 3. click newly made color swatch in palette and note RGB/hex values OBSERVED RESULT Values will not be the values originally selected. EXPECTED RESULT Values translated to Krita should reflect the chosen values in the OSX dialogue considering that for some dockers (digital color mixer) the only way to select colors for mixing is via color swatch buttons. SOFTWARE/OS VERSIONS Windows: macOS: YES Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION See forum post: https://forum.kde.org/viewtopic.php?f=139&t=160738 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 407650] Add an option to show all running pulseaudio applications instead of only playing applications
https://bugs.kde.org/show_bug.cgi?id=407650 --- Comment #6 from Ariel Rosenfeld --- (In reply to Nate Graham from comment #5) > I think I understand what you mean now. In fact I've found myself wanting > the same thing. > > > and vertical sliders > Not sure how that would be an improvement. the win7 mixer widget shows how to can look, its not very pretty as it copies the win7 style but it does try to maximize the information you can see and when you mouse over the icons you get even more information plus you can click them for menus with more options, reducing the clicks required to change volume or mute. it needs work to look more native but its clean and uses vertical widgets. the problem with horizontal sliders it grows up and you get less space to expand while vertical sliders expand to the side and have more space. kmix used to have an option to have an option select vertical or horizontal sliders but when pulseaudio was adopted kmix lost that option. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 406972] Falkon crashes randomly when typing in the address bar
https://bugs.kde.org/show_bug.cgi?id=406972 --- Comment #4 from magib...@hotmail.com --- I got it! This one was captured by KCrash, and is the same crash as in the first post (comment #3 might be a different bug). On this occasion, a blank tab was already opened, but I was on another one. I just switched to it and began typing in the address bar when falkon crashed. Here are the backtraces of the crashed and the main threads: Thread 27 (Thread 0x7f2b1184a700 (LWP 1085)): > [KCrash Handler] > #6 0x0035 in ?? () > #7 0x7f2b6d244709 in QCache::unlink (n=..., > this=0x7f2b6d3bb5c0 <(anonymous > namespace)::Q_QGS_qz_icon_provider::innerFunction()::holder+96>) at > /usr/include/qt/QtCore/qcache.h:187 > #8 QCache::trim (m=99, this=0x7f2b6d3bb5c0 <(anonymous > namespace)::Q_QGS_qz_icon_provider::innerFunction()::holder+96>) at > /usr/include/qt/QtCore/qcache.h:193 > #9 QCache::insert (this=0x7f2b6d3bb5c0 <(anonymous > namespace)::Q_QGS_qz_icon_provider::innerFunction()::holder+96>, akey=..., > aobject=0x7f2ae42eeda0, acost=1) at /usr/include/qt/QtCore/qcache.h:173 > #10 0x7f2b6d24270d in IconProvider::imageForUrl (url=..., > allowNull=) at > /usr/src/debug/falkon/src/lib/tools/iconprovider.cpp:211 > #11 0x7f2b6d126fa9 in LocationCompleterRefreshJob::runJob > (this=0x5593d6ddff50) at > /usr/src/debug/falkon/src/lib/navigation/completer/locationcompleterrefreshjob.cpp:109 > #12 0x7f2b6d127753 in non-virtual thunk to > QtConcurrent::RunFunctionTask::run() () at > /usr/include/qt/QtCore/qfutureinterface.h:293 > #13 0x7f2b6c482c91 in ?? () from /usr/lib/libQt5Core.so.5 > #14 0x7f2b6c47f63c in ?? () from /usr/lib/libQt5Core.so.5 > #15 0x7f2b64733a92 in start_thread () from /usr/lib/libpthread.so.0 > #16 0x7f2b6c166cd3 in clone () from /usr/lib/libc.so.6 > > Thread 1 (Thread 0x7f2b5a6ddb00 (LWP 912)): > #0 0x7f2b64739bac in pthread_cond_wait@@GLIBC_2.3.2 () from > /usr/lib/libpthread.so.0 > #1 0x7f2b6c48591c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () > from /usr/lib/libQt5Core.so.5 > #2 0x7f2b6c482108 in QThreadPoolPrivate::waitForDone(QDeadlineTimer > const&) () from /usr/lib/libQt5Core.so.5 > #3 0x7f2b6c482514 in QThreadPoolPrivate::waitForDone(int) () from > /usr/lib/libQt5Core.so.5 > #4 0x7f2b6c4825ad in QThreadPool::~QThreadPool() () from > /usr/lib/libQt5Core.so.5 > #5 0x7f2b6c4825ea in ?? () from /usr/lib/libQt5Core.so.5 > #6 0x7f2b6c0a5f2c in __run_exit_handlers () from /usr/lib/libc.so.6 > #7 0x7f2b6c0a605e in exit () from /usr/lib/libc.so.6 > #8 0x7f2b523c373f in ?? () from /usr/lib/dri/i965_dri.so > #9 0x7f2b53139dc3 in glPrimitiveBoundingBox () from > /usr/lib/libGLX_mesa.so.0 > #10 0x7f2b5a0bd6e9 in ?? () from > /usr/lib/qt/plugins/xcbglintegrations/libqxcb-glx-integration.so > #11 0x7f2b648a7f60 in QOpenGLContext::swapBuffers(QSurface*) () from > /usr/lib/libQt5Gui.so.5 > #12 0x7f2b64b57c08 in QPlatformBackingStore::composeAndFlush(QWindow*, > QRegion const&, QPoint const&, QPlatformTextureList*, bool) () from > /usr/lib/libQt5Gui.so.5 > #13 0x7f2b59f6a7a6 in ?? () from /usr/lib/libQt5XcbQpa.so.5 > #14 0x7f2b6ca58edd in ?? () from /usr/lib/libQt5Widgets.so.5 > #15 0x7f2b6ca5a995 in ?? () from /usr/lib/libQt5Widgets.so.5 > #16 0x7f2b6ca5c008 in ?? () from /usr/lib/libQt5Widgets.so.5 > #17 0x7f2b6ca5c379 in ?? () from /usr/lib/libQt5Widgets.so.5 > #18 0x7f2b6ca74337 in QWidgetPrivate::syncBackingStore() () from > /usr/lib/libQt5Widgets.so.5 > #19 0x7f2b6ca8cc39 in QWidget::event(QEvent*) () from > /usr/lib/libQt5Widgets.so.5 > #20 0x7f2b6cb9a405 in QMainWindow::event(QEvent*) () from > /usr/lib/libQt5Widgets.so.5 > #21 0x7f2b6d0a33af in BrowserWindow::event (this=0x5593cffc27e0, > event=0x5593d6ddf140) at > /usr/src/debug/falkon/src/lib/app/browserwindow.cpp:1252 > #22 0x7f2b6ca4bda4 in QApplicationPrivate::notify_helper(QObject*, > QEvent*) () from /usr/lib/libQt5Widgets.so.5 > #23 0x7f2b6ca533c1 in QApplication::notify(QObject*, QEvent*) () from > /usr/lib/libQt5Widgets.so.5 > #24 0x7f2b6c63a849 in QCoreApplication::notifyInternal2(QObject*, > QEvent*) () from /usr/lib/libQt5Core.so.5 > #25 0x7f2b6c63d928 in QCoreApplicationPrivate::sendPostedEvents(QObject*, > int, QThreadData*) () from /usr/lib/libQt5Core.so.5 > #26 0x7f2b6c690394 in ?? () from /usr/lib/libQt5Core.so.5 > #27 0x7f2b63d0590f in g_main_context_dispatch () from > /usr/lib/libglib-2.0.so.0 > #28 0x7f2b63d07869 in ?? () from /usr/lib/libglib-2.0.so.0 > #29 0x7f2b63d078ae in g_main_context_iteration () from > /usr/lib/libglib-2.0.so.0 > #30 0x7f2b6c68f969 in > QEventDispatcherGlib::processEvents(QFlags) () > from /usr/lib/libQt5Core.so.5 > #31 0x7f2b6c6394dc in > QEventLoop::exec(QFlags) () from > /usr/lib/libQt5Core.so.5 > #32 0x7f2b6c641596 in QCoreApplication::exec() () from > /usr/lib/libQt5Core.so.5 >
[konsole] [Bug 407879] New: [KDE Konsole 19.04.1 - strange behaviour] "New Tab ->" shows a total listing of ... one entry, which must be selected
https://bugs.kde.org/show_bug.cgi?id=407879 Bug ID: 407879 Summary: [KDE Konsole 19.04.1 - strange behaviour] "New Tab ->" shows a total listing of ... one entry, which must be selected Product: konsole Version: 19.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: sheve...@gmail.com Target Milestone: --- Linux OS here, KDE konsole compiled from source, version 19.04.1 All works sorta ok ... I have defined a custom profile for my preferred KDE konsole. Now the strange thing is - if I click on: File -> New Tab then the name of that single profile appears. I then have to select that profile with the mouse cursor/pointer, in order to open a new tab. What confuses me here is ... if the total selection is one (1), then what is the point of me having to select on that single entry? I mean if I already can not do any selection with the mouse, then why does KDE konsole show me that one selection that I then have to click? That makes no sense to me. Surely anyone thinking about this may come to the same conclusion - what is the exercise here for the user, shall the user train how to select a single entry in this dropdown-widget? It may be that something was buggy or so; I think I had more than one profile before, but since I only ever need a single profile, I always remove all but one profiles. (Might be that a default profile keeps on re-appearing but I personally really only want one profile and consider more than one profile confusing and an antifeature for me personally). Anyway. My suggestion is quite simple: - Only show a DROP DOWN when there are AT THE LEAST TWO possibilities to choose from. Personally I actually don't need this at all, since I only want a single profile; but a more elegant solution could be to mark this as an auto-pick solution or something, or some setting (but I would recommend no setting here, as this may keep it simpler; I am just providing alternatives to the current forced manual selection) Right now I only have a single entry to choose from, and it is a bit pointless to have to click on this single entry - I can not even click on anything else there, so why is that even appearing at all ... it means I have to make an additional step. I can not say whether this is new or not, largely because I actually dont even want to have any of this. ;) (Normally I open tabs via the keyboard anyway but sometimes I use to mouse to focus back on KDE konsole from my browser, so this is where I may then use the mouse instead.) I selected tabbar but I am not sure if this is the right name - I refer to the tab bar on the top menu widget e. g. where you can open a new tab. If someone considers this to be a feature, I would be curious about the explanation for when there is only a single entry (I understand it when there are more entries, but not when there is a single entry; although even when there are multiple entries, I actually think it is cumbersome to want to select another entry IF the user defaults to a specific variant already). IF a setting is considered then I would recommend to default to "ignore the case when there are fewer than two possibilities/entries". This might solve the issue altogether while still allowing for flexibility - not sure if anyone uses this option, but better be safe than sorry in the event that others may depend on it, even if I consider it overall to be not too terribly useful. Thanks for reading. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 407648] Remember the last-viewed tab, even after a reboot or after restarting plasmashell
https://bugs.kde.org/show_bug.cgi?id=407648 --- Comment #4 from Ariel Rosenfeld --- (In reply to Nate Graham from comment #3) > Ah, we found the real bug. :) I think fixing this makes sense. Not > everything needs to be configurable, especially when we can make the default > behavior more responsive to user expectations. Preserving state after reboot > almost always makes sense. I guess we will have to agree to disagree about what users expect from a mixer, people expect most mixers to look like the win7 volume mixer widget from the store or kmix. Many users expect more options to tweak in the Plasma/KDE shell. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407691] Hangs on Startup, with Album on Network share (on MacOS)
https://bugs.kde.org/show_bug.cgi?id=407691 --- Comment #16 from Maik Qualmann --- With the next packages for MacOS, we'll see if I'm right. One more note to the QFileSystemWatcher, this only works with local drives. Mounted network drives do not work (even on Linux) with the QFileSystemWatcher. Maik -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405010] Don't show a notification badge with a zero when there aren't any notifications
https://bugs.kde.org/show_bug.cgi?id=405010 Jan Przybylak changed: What|Removed |Added Version|unspecified |5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405010] Don't show a notification badge with a zero when there aren't any notifications
https://bugs.kde.org/show_bug.cgi?id=405010 --- Comment #2 from Jan Przybylak --- I use 5.11.1. This doesn't always happen, just sometimes. I have not been able to figure out what is causing it exactly, but I'm only using Kmail and Akregator, so it has to be one of them. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 Wolfgang Bauer changed: What|Removed |Added CC||jan.thomas.118+...@gmail.co ||m --- Comment #51 from Wolfgang Bauer --- *** Bug 407876 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 407876] Akregator crashes when closing tab in internal browser
https://bugs.kde.org/show_bug.cgi?id=407876 --- Comment #3 from Wolfgang Bauer --- Sorry, wrong bug number... I mean bug#371511 *** This bug has been marked as a duplicate of bug 371511 *** -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 407668] hidpi scaling problem
https://bugs.kde.org/show_bug.cgi?id=407668 --- Comment #6 from Nate Graham --- Update to a newer Ubuntu version or use a newer Snap- or Flatpak-provided version of Kolourpaint. If you need any further details, please ask in an Ubuntu-specific venue, as Ubuntu's release schedule and packaging decisions is something that KDE has no impact on. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 407668] hidpi scaling problem
https://bugs.kde.org/show_bug.cgi?id=407668 Nate Graham changed: What|Removed |Added Resolution|WORKSFORME |FIXED -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 407876] Akregator crashes when closing tab in internal browser
https://bugs.kde.org/show_bug.cgi?id=407876 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Wolfgang Bauer --- Probably the same as bug#394946, should be fixed in 19.04.2. *** This bug has been marked as a duplicate of bug 394946 *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 394946] Delete key no longer works in articles list after using search - keyboard focus stays in search field
https://bugs.kde.org/show_bug.cgi?id=394946 Wolfgang Bauer changed: What|Removed |Added CC||jan.thomas.118+...@gmail.co ||m --- Comment #2 from Wolfgang Bauer --- *** Bug 407876 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 407648] Remember the last-viewed tab, even after a reboot or after restarting plasmashell
https://bugs.kde.org/show_bug.cgi?id=407648 Nate Graham changed: What|Removed |Added Status|RESOLVED|REPORTED Summary|Add option to select|Remember the last-viewed |between the default tab |tab, even after a reboot or |opened when clicking on |after restarting |applet |plasmashell Resolution|NOT A BUG |--- --- Comment #3 from Nate Graham --- (In reply to Ariel Rosenfeld from comment #2) > Unfortunately it forgets the last viewed tab on reboot or logout which makes > it broken Ah, we found the real bug. :) I think fixing this makes sense. Not everything needs to be configurable, especially when we can make the default behavior more responsive to user expectations. Preserving state after reboot almost always makes sense. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 407648] Remember the last-viewed tab, even after a reboot or after restarting plasmashell
https://bugs.kde.org/show_bug.cgi?id=407648 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.
[digikam] [Bug 398921] digikam 5.9.0 slow to start on Mac but rapid on Ubuntu with same database
https://bugs.kde.org/show_bug.cgi?id=398921 --- Comment #21 from Maik Qualmann --- Git commit 8a2cbc6917d48bbc5d0b02b78d7bcda4176688cb by Maik Qualmann. Committed on 23/05/2019 at 19:10. Pushed by mqualmann into branch 'master'. QFileSystemWatcher can now be disabled. The setting is on the collection page. The default is off. Related: bug 407691, bug 406224, bug 403073 M +21 -13 core/libs/album/engine/albumwatch.cpp M +2-0core/libs/settings/applicationsettings.cpp M +3-0core/libs/settings/applicationsettings.h M +10 -0core/libs/settings/applicationsettings_albums.cpp M +3-0core/libs/settings/applicationsettings_p.cpp M +3-0core/libs/settings/applicationsettings_p.h M +16 -14 core/utilities/setup/collections/setupcollections.cpp https://invent.kde.org/kde/digikam/commit/8a2cbc6917d48bbc5d0b02b78d7bcda4176688cb -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406224] 'No space left on device' on startup
https://bugs.kde.org/show_bug.cgi?id=406224 --- Comment #7 from Maik Qualmann --- Git commit 8a2cbc6917d48bbc5d0b02b78d7bcda4176688cb by Maik Qualmann. Committed on 23/05/2019 at 19:10. Pushed by mqualmann into branch 'master'. QFileSystemWatcher can now be disabled. The setting is on the collection page. The default is off. Related: bug 407691, bug 403073, bug 398921 M +21 -13 core/libs/album/engine/albumwatch.cpp M +2-0core/libs/settings/applicationsettings.cpp M +3-0core/libs/settings/applicationsettings.h M +10 -0core/libs/settings/applicationsettings_albums.cpp M +3-0core/libs/settings/applicationsettings_p.cpp M +3-0core/libs/settings/applicationsettings_p.h M +16 -14 core/utilities/setup/collections/setupcollections.cpp https://invent.kde.org/kde/digikam/commit/8a2cbc6917d48bbc5d0b02b78d7bcda4176688cb -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403073] Can't remove a removable media when digikam run
https://bugs.kde.org/show_bug.cgi?id=403073 --- Comment #5 from Maik Qualmann --- Git commit 8a2cbc6917d48bbc5d0b02b78d7bcda4176688cb by Maik Qualmann. Committed on 23/05/2019 at 19:10. Pushed by mqualmann into branch 'master'. QFileSystemWatcher can now be disabled. The setting is on the collection page. The default is off. Related: bug 407691, bug 406224, bug 398921 M +21 -13 core/libs/album/engine/albumwatch.cpp M +2-0core/libs/settings/applicationsettings.cpp M +3-0core/libs/settings/applicationsettings.h M +10 -0core/libs/settings/applicationsettings_albums.cpp M +3-0core/libs/settings/applicationsettings_p.cpp M +3-0core/libs/settings/applicationsettings_p.h M +16 -14 core/utilities/setup/collections/setupcollections.cpp https://invent.kde.org/kde/digikam/commit/8a2cbc6917d48bbc5d0b02b78d7bcda4176688cb -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407691] Hangs on Startup, with Album on Network share (on MacOS)
https://bugs.kde.org/show_bug.cgi?id=407691 --- Comment #15 from Maik Qualmann --- Git commit 8a2cbc6917d48bbc5d0b02b78d7bcda4176688cb by Maik Qualmann. Committed on 23/05/2019 at 19:10. Pushed by mqualmann into branch 'master'. QFileSystemWatcher can now be disabled. The setting is on the collection page. The default is off. Related: bug 406224, bug 403073, bug 398921 M +21 -13 core/libs/album/engine/albumwatch.cpp M +2-0core/libs/settings/applicationsettings.cpp M +3-0core/libs/settings/applicationsettings.h M +10 -0core/libs/settings/applicationsettings_albums.cpp M +3-0core/libs/settings/applicationsettings_p.cpp M +3-0core/libs/settings/applicationsettings_p.h M +16 -14 core/utilities/setup/collections/setupcollections.cpp https://invent.kde.org/kde/digikam/commit/8a2cbc6917d48bbc5d0b02b78d7bcda4176688cb -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407878] New: Text Editing window is drawn behind floating dockers
https://bugs.kde.org/show_bug.cgi?id=407878 Bug ID: 407878 Summary: Text Editing window is drawn behind floating dockers Product: krita Version: nightly build (please specify the git hash!) Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: ahab.greybe...@hotmail.co.uk Target Milestone: --- SUMMARY This bug happens on all recent nightly appimages (during May as far as I can tell) but did not happen with version 4.1.7 or with the Feb 21st 4.2.0-pre-alpha. When editing text, the text editing window is drawn below/behind any floating dockers. This is inconvenient if you have lots of floating dockers on a second monitor. STEPS TO REPRODUCE As stated above OBSERVED RESULT As stated above EXPECTED RESULT It should be on top of floating docker, as it used to be. SOFTWARE/OS VERSIONS Krita Version: 4.2.0-beta (git 45bdec0) Languages: en_GB, en Hidpi: true Qt Version (compiled): 5.12.2 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: 4.9.0-9-amd64 Pretty Productname: Debian GNU/Linux 9 (stretch) Product Type: debian Product Version: 9 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407877] Layer content not shown when file opened
https://bugs.kde.org/show_bug.cgi?id=407877 Ahab Greybeard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407874] Interrupting kwin_x11 with ctrl+z freezes everything except hardware cursor
https://bugs.kde.org/show_bug.cgi?id=407874 --- Comment #2 from petrk --- Fair enough, freezing whole screen still seems a bit drastic, unless kwin can't do anything about it since it's interrupted from outside. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407877] Layer content not shown when file opened
https://bugs.kde.org/show_bug.cgi?id=407877 --- Comment #2 from M --- Sorry, wrong git hash. Correct is (git 45bdec0). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407873] Brightness OSD is not displayed when using hotkeys 5.15.90
https://bugs.kde.org/show_bug.cgi?id=407873 --- Comment #3 from petrk --- Yeah, about that. It seems to me that restoring default hotkeys from gui is unreliable. Nuking config files works best. Thanks for the fix. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407877] Layer content not shown when file opened
https://bugs.kde.org/show_bug.cgi?id=407877 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #1 from M --- Can confirm on my system (git ad31625). It happens with every document in LAB color space I tried so far. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 155490] some thoughts about icons and menu
https://bugs.kde.org/show_bug.cgi?id=155490 --- Comment #7 from David Hurka --- I think at least in the left sidebar, the icons could be improved. 1. Use the icon currently used by Layers for Contents, because Contents currently looks like linear text, not like a list. 2. Use a layer icon for Layers, because that’s what it means. Contents currently uses format-justify-left (format-justify-right for LTR layout), Layers currently uses format-list-unordered. Layers could use e. g. dialog-layers, like in Inkscape. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407877] New: Layer content not shown when file opened
https://bugs.kde.org/show_bug.cgi?id=407877 Bug ID: 407877 Summary: Layer content not shown when file opened Product: krita Version: nightly build (please specify the git hash!) Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: ahab.greybe...@hotmail.co.uk Target Milestone: --- SUMMARY The latest nightly build appimage krita-4.2.0-beta-45bdec0-x86_64.appimage does not display layer content when a file is opened. The presentation of this bug is slightly different for vector layer content compared to paint layer content but it seems to be influenced by the 'content bounding box' Turning the layers on then off clears the problem. STEPS TO REPRODUCE 1. Create an image with a paint layer over the standard background layer and paint a line in it. Save and Close. 2. Open the file and note that the canvas shows all transparency. 3. Turn off then on the background layer and the paint layer and everything displays fine after that. 4. Note that tuning off the paint layer first compared to turning off the background layer first shows slightly different things - a minor detail but naybe useful for diagnosis. 5. Note that using a vector layer (e.g with text) shows a different initial bug characteristic but again related to the content bounding box. OBSERVED RESULT As above. EXPECTED RESULT This should not happen. SOFTWARE/OS VERSIONS Krita Version: 4.2.0-beta (git 45bdec0) Languages: en_GB, en Hidpi: true Qt Version (compiled): 5.12.2 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: 4.9.0-9-amd64 Pretty Productname: Debian GNU/Linux 9 (stretch) Product Type: debian Product Version: 9 ADDITIONAL INFORMATION This does not happen in recent previous nightly appimages. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 180443] Provide icons for entries in the View menu
https://bugs.kde.org/show_bug.cgi?id=180443 --- Comment #2 from David Hurka --- Update: Trim Margins got an icon, and a new icon was created for Trim to Selection. Close this bug? -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 407876] Akregator crashes when closing tab in internal browser
https://bugs.kde.org/show_bug.cgi?id=407876 Christoph Feck changed: What|Removed |Added Version|unspecified |5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 407876] Akregator crashes when closing tab in internal browser
https://bugs.kde.org/show_bug.cgi?id=407876 Jan Thomas changed: What|Removed |Added CC||jan.thomas.118+...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 407876] Akregator crashes when closing tab in internal browser
https://bugs.kde.org/show_bug.cgi?id=407876 --- Comment #1 from Jan Thomas --- I forgot the Akregator version, and the Bug report doesnt let me specify this version. Pacman reports "19.04.1-1" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407873] Brightness OSD is not displayed when using hotkeys 5.15.90
https://bugs.kde.org/show_bug.cgi?id=407873 David Edmundson changed: What|Removed |Added Version Fixed In||5.16.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407620] Standalone KWin KCM window accessed from window decoration context menu is too small
https://bugs.kde.org/show_bug.cgi?id=407620 --- Comment #2 from Nate Graham --- Created attachment 120276 --> https://bugs.kde.org/attachment.cgi?id=120276&action=edit Looks like this. Not fixed with that commit, sorry. It looks like this. ^^ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407873] Brightness OSD is not displayed when using hotkeys 5.15.90
https://bugs.kde.org/show_bug.cgi?id=407873 David Edmundson changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from David Edmundson --- Fixed in master. You might need to wipe your globalshorcuts config if you had the beta installed -- You are receiving this mail because: You are watching all bug changes.
