[krita] [Bug 410830] New: play/pause button behaves like a play/stop button
https://bugs.kde.org/show_bug.cgi?id=410830 Bug ID: 410830 Summary: play/pause button behaves like a play/stop button Product: krita Version: 4.2.5 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: nicole.sim...@gmail.com Target Milestone: --- SUMMARY the timing header starts from the beginning of the timeline when hitting play/pause. when pausing an animation by clicking on the play/stop button, it starts at the beginning instead of pausing on the currnt frame. EXPECTED RESULT when clicking the play/stop button, the timing header should stop on the currnt frame. please fix this. it's been reported back in 2017-02-24 11:25:54 UTC and hasn't been fixed and updated since. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 140676] Command line option --pause incorrectly acts just like --play-pause
https://bugs.kde.org/show_bug.cgi?id=140676 Nicole changed: What|Removed |Added CC||nicole.sim...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365222] Custom buttons disappear from toolbar after restarting Krita
https://bugs.kde.org/show_bug.cgi?id=365222 Nicole changed: What|Removed |Added CC||nicolebro...@alumni.nd.edu --- Comment #15 from Nicole --- I'm on 4.0.0 and Windows 10 and this is still happening. Are there any plans to iron out this bug? It's rather frustrating to have to re-configure the window every time I restart the program. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393025] New: files won't save
https://bugs.kde.org/show_bug.cgi?id=393025 Bug ID: 393025 Summary: files won't save Product: krita Version: unspecified Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: sillydwarven...@aol.com Target Milestone: --- when I went to save my work, i tried using both the "save" and "save as" features, but both gave me an error message saying "file not found" when I tried to save them. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 380486] New: Brushs Greyed out and not selectable
https://bugs.kde.org/show_bug.cgi?id=380486 Bug ID: 380486 Summary: Brushs Greyed out and not selectable Product: krita Version: 3.1.4 Platform: MS Windows OS: unspecified Status: UNCONFIRMED Severity: normal Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: n.rate...@gmail.com Target Milestone: --- Created attachment 105856 --> https://bugs.kde.org/attachment.cgi?id=105856&action=edit Krita brush bug I don't have a tablet (yet) so all I use is a mouse. I have not downloaded nor created any brushes as of yet, so I am using the default brushes. So now the real problem. Every time I right click so that I can select a different brush, all the brushes are grey and are not selectable. I am stuck using only a single brush. I have uninstalled and reinstalled Krita and it has not fixed the problem. I will provide a screenshot of the problem. -- You are receiving this mail because: You are watching all bug changes.
Öko-Test: die Testsieger zur Absicherung Ihrer Arbeitskraft
Liebe Leserinnen und Leser, das Risiko einer Berufsunfähigkeit darf nicht unterschätzt werden. Jeder vierte Deutsche wird im Laufe seines Arbeitslebens berufsunfähig. Durch die finanzielle Veränderung stürzen viele Betroffene in ein tiefes finanzielles Loch. Jetzt können Sie das Risiko einer drohenden Berufsunfähigkeit schon ab 4,69 € monatlich versichern: http://bu-preiswert.net/track/?id=D8BAE25C55&e=3D912A705C&u=33570AC826 Wir haben in unserem Test 70 Angebote untersucht. Mehr als die Hälfte der Tarife haben dabei die Bestnote bekommen. Wir haben eine Übersicht der besten Tarife zusammengestellt: - HanseMerkur Tarif SBU Profi Care - Europa Premium Vorsorge 1 - R+V Tarif BZ Vorteile einer Berufsunfähigkeit sind: - schon ab 4,69 € monatlich Risiko versichern - Schutz vor dem finanziellen Ruin - wenige Gesundheitsfragen Ihr Team von Öko-Test Nicole Unger Redaktion – Verbraucher Knesebeckstraße 53 52525 Waldfeucht Keine weiteren Benachrichtigungen empfangen: http://bu-preiswert.net/unsubscribe/?id=D8BAE25C55&u=33570AC826&p=26AB869CEC&m=QzxRCa0TudJVd4LfSX7DvGnuNJ5QKEBrjw0bMDsufFVNOA8KNa1IjE4QqprFcnJw
[kscreenlocker] [Bug 489118] New: X11 Screen locker, if "cancelled" right after locking, will permanently freeze
https://bugs.kde.org/show_bug.cgi?id=489118 Bug ID: 489118 Summary: X11 Screen locker, if "cancelled" right after locking, will permanently freeze Classification: Plasma Product: kscreenlocker Version: 6.1.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nrfocon...@gmail.com Target Milestone: --- Created attachment 170919 --> https://bugs.kde.org/attachment.cgi?id=170919&action=edit emerge --info SUMMARY The screen locker kicked in while I was reading something in my browser, and I instinctively bumped the mouse to prevent the screen from locking in its entirety. In Plasma 5.x, this would automatically unlock my screen (an additional few seconds would require a password), and I could continue. In Plasma 6.1, this results in the locker process freezing. `loginctl unlock-session` was unsuccessful, I required `loginctl terminate-session` (fortunately, most of my programs are capable of some degree of crash recovery). STEPS TO REPRODUCE 1. Let screen time out. 2. Bump the mouse right as you notice the screen change. OBSERVED RESULT Frozen, undismissable lock screen. EXPECTED RESULT Lock screen either: * goes away * prompts for password SOFTWARE/OS VERSIONS Kernel: 6.9.5-gentoo-x86_64 (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION I've also attached the output of `emerge --ignore-default-opts --info kscreenlocker`, which will provide some extra information about how exactly the package was built and what kind of environment my system is. Not sure how helpful or needed it will actually be, but I didn't want to finish this empty handed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483163] On X11 with compositing turned on, blank screen on lock screen when using Breeze Plasma style
https://bugs.kde.org/show_bug.cgi?id=483163 --- Comment #33 from Nicole Schoebel --- I just made an interesting observation. A couple of days ago I added a second monitor to my system. Since then the bug had disappeared. I would always see the lock screen as intended. Today I checked what happens when I remove the second monitor again. I unplugged the second monitor from the computer, changed “/etc/X11/xorg.conf.d/10-monitor.conf” back to what it was before, and rebooted. The bug was back. I would see a black lock screen with the exception of a visible mouse cursor. I then plugged the (second) monitor cable back into the computer, but did NOT connect the other end to the monitor yet. Bug still there. I then connected the other end of the cable to the monitor, and - without having to reboot (!) - the lock screen would then work as intended. The monitor was connected to power, but in standby at that point. When I turned it completely on nothing was visible, it wasn’t even getting a signal. “xrandr -q” was showing the monitor as connected though. I then unplugged the monitor cable from the computer again. The lock screen would still work as intended. So, to sum it up: As long as I connect a second monitor at any time after a reboot, the lock screen will work as intended until the next reboot. The monitor does NOT have to stay connected. It just had to be there at some point. For information: My primary monitor is connected via DisplayPort. The second one is connected via HDMI. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style
https://bugs.kde.org/show_bug.cgi?id=483163 --- Comment #25 from Nicole Schoebel --- Earlier today I went into "System Settings / Display & Monitor" and DISabled "Compositing / Enable on startup". I then rebooted. After I logged back into KDE, I could then activate the lock screen and it would show properly. I tested this multiple times, and it worked fine every time. I then re-enabled the compositor, and then the lock screen would show up black again except for the mouse cursor. So the bug only seems to appear when the compositor is enabled, which makes me wonder if the compositor is getting confused about which window should be displayed on top? If I understand the design of the lock screen correctly (as described in the sources in kscreenlocker/DESIGN), then a fullscreen (empty - all black) window is put on top of all other windows, and then the actual lock screen is put on top of that. If the compositor for some reason would think that that fullscreen window belongs on top of the lock screen... we would see exactly this bug. So, could this actually be a compositor bug? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style
https://bugs.kde.org/show_bug.cgi?id=483163 Nicole Schoebel changed: What|Removed |Added CC||schoebel220...@nschoebel.de --- Comment #7 from Nicole Schoebel --- I still see this on 6.0.2. Just installed it on Arch Linux, rebooted and then tested it. I have a weird observation to add though. While most times the lock-screen is not visible (but the mouse cursor is), sometimes I did actually see the lock-screen. I keep my computer on overnight, but the session is locked and the monitor is turned off. On most occasions in the morning the lock-screen was visible. I also had that happen once during the day. It only seems to happen when a couple of hours have passed. And what may be a factor here (though I'm not sure) is that a lot of disk activity happened while the session was locked or just before it was locked. My computer does automatic backup overnight. And the one time when it worked during the day, I had copied a couple of gigabytes to a USB disk just before locking the session. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 455367] Vertical unreadable `% Complete` progress bars
https://bugs.kde.org/show_bug.cgi?id=455367 Nicole Schoebel changed: What|Removed |Added CC||schoebel220...@nschoebel.de --- Comment #7 from Nicole Schoebel --- I see the same problem with the vertical progress bar in LibreOffice when saving a big document. For a split second a progress bar appears at the bottom of the window, and with Breeze it is vertical, but it should be horizontal. When I change the application style to Fusion the bug disappears both in KTorrent and LibreOffice. Switch back to Breeze, and the bug appears again. This is on Arch Linux. So it looks to me as if the bug is actually in Breeze. Looking at the recent commits, there is one from a few weeks ago (https://invent.kde.org/plasma/breeze/-/commit/2bf9fc4c7be280e2b77f7c150855e0fca0b80d9a) that made changes to the progress bar implementation in Breeze. I'm not familiar with the KDE codebase, not even familiar with C++, so I'm not sure if that is actually the cause. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 432955] New: enabling WYTIWYG comments
https://bugs.kde.org/show_bug.cgi?id=432955
Bug ID: 432955
Summary: enabling WYTIWYG comments
Product: kate
Version: 20.12.2
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: nicolesharp...@gmail.com
Target Milestone: ---
SUMMARY
There needs to be a WYTIWYG ("what you type is what you get") mode for KATE.
Currently it is very difficult to always disable automatic indentations for
certain filetypes. A strict WYTIWYG mode would mean that KATE will never
insert any characters (including spaces or indents) that were not typed by the
user, regardless of the filetype.
STEPS TO REPRODUCE
1. For file "style.css", type "/*" and hit enter.
2. " * " is automatically inserted by KATE.
3. No option in settings to disable automatic indentation for all filetypes.
SOFTWARE/OS VERSIONS
KATE 20.12.2 for 64-bit Microsoft Windows 10 Education
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 462013] New: Preferences on application of changes not saved
https://bugs.kde.org/show_bug.cgi?id=462013 Bug ID: 462013 Summary: Preferences on application of changes not saved Classification: Applications Product: digikam Version: 7.8.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Tags-Pick Assignee: digikam-bugs-n...@kde.org Reporter: mcdow...@yahoo.com Target Milestone: --- SUMMARY When application opens and you are applying tags it asks you if you want to not see the warning about applying tags each time. When you shut down and restart the application it asks again. Preference is only saved for the session. *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Apply tags and say that you want to not see the warning each time. 2. Close the App 3. Open the app and apply tags again. You will see that the warning is back under this new session OBSERVED RESULT Preference is only saved for the current session EXPECTED RESULT Preference should be saved between sessions. SOFTWARE/OS VERSIONS Windows: Device nameWin10PC-Nikki Processor Intel(R) Core(TM) i5-8600 CPU @ 3.10GHz 3.10 GHz Installed RAM 16.0 GB (15.8 GB usable) Device ID FEA4214E-D94A-4A95-B6FD-D9337F882F40 Product ID 00330-52650-31352-AAOEM System type 64-bit operating system, x64-based processor Pen and touch No pen or touch input is available for this display 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.
[digikam] [Bug 462013] Preferences on application of changes not saved
https://bugs.kde.org/show_bug.cgi?id=462013 --- Comment #3 from Nicole McDowell --- Good to know. Thank you! On Saturday, November 19, 2022 at 12:57:04 AM CST, Maik Qualmann wrote: https://bugs.kde.org/show_bug.cgi?id=462013 Maik Qualmann changed: What |Removed |Added CC| |metzping...@gmail.com Resolution|--- |INTENTIONAL Status|REPORTED |RESOLVED Version Fixed In| |7.9.0 --- Comment #2 from Maik Qualmann --- The query that the action affects many tags and that writing the metadata can take a long time is intentionally saved only for the current session. This is absolutely intentional. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433468] New: DigiKam Create HTML Gallery lockup
https://bugs.kde.org/show_bug.cgi?id=433468 Bug ID: 433468 Summary: DigiKam Create HTML Gallery lockup Product: digikam Version: 7.1.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Plugin-Generic-HTMLGallery Assignee: digikam-bugs-n...@kde.org Reporter: nicolesharp...@gmail.com Target Milestone: --- SUMMARY 64-bit DigiKam 7.1.0 for 64-bit Microsoft Windows 10 locks up when attempting to Create HTML Gallery using Simple/Natural template. Not sure if it is just my system, but this appears to be a consistent bug since upgrading from DigiKam 7.0.0 to DigiKam 7.1.0. I was able to successfully create galleries with DigiKam 7.0.0, but have not been able to since upgrading to DigiKam 7.1.0 using the same/identical settings and images. What happens is that it gets to "create directories" ... "copying theme" ... "generate images and XML files" ... "create directories" ... "create directories" ... "generating files" and then stops. Progress bar says "0%" and remains there regardless of how much time is waited for. Clicking "Back" and then "Cancel" and then closing DigiKam does not stop the process though and DigiKam must instead be manually terminated from the Windows Task Manager. In DigiKam 6, HTML gallery generation using the exact settings might take anywhere from a few seconds for small albums to under an hour for very large albums. STEPS TO REPRODUCE 1. Create HTML Gallery 2. choose image selection method: albums 3. Simple Theme 4. Natural Style 5. save image format: JPEG 6. save image quality: 100% 7. save image max size: 1024 px 8. include full-size original images for download: yes 9. thumbnail format: JPEG 10. thumbnail quality: 100% 11. thumbnail size: 128 px 12. open in browser: no OBSERVED RESULT Application gets stuck at 0%. Closing application does not end stuck/locked-up process, and digikam.exe must be manually terminated from Windows Task Manager. EXPECTED RESULT HTML gallery creation. SOFTWARE/OS VERSIONS 64-bit DigiKam 7.1.0 64-bit Microsoft Windows 10 ADDITIONAL INFORMATION As part of additional testing, I uninstalled DigiKam 7.1.0 and then installed DigiKam 7.0.0. HTML Gallery creation now works correctly, with medium-sized galleries containing hundreds of images created within just a minute or so (using identical settings and images from DigiKam 7.1.0). So downgrading to DigiKam 7.0.0 is a practical workaround and the issue is specific to just DigiKam 7.1.0. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 364043] Intuos Pro cannot generate settings profiles, cannot configure buttons.
https://bugs.kde.org/show_bug.cgi?id=364043 Nicole Erskine changed: What|Removed |Added CC||erskinenic...@rocketmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483163] Sometimes on X11 with compositing turned on, black lock screen when using Breeze Plasma style, but controls are all there and remain interactive
https://bugs.kde.org/show_bug.cgi?id=483163 --- Comment #99 from Nicole Schoebel --- Count me in as another one for whom 6.2.5 does NOT fix this bug. I vote to reopen this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483163] Sometimes on X11 with compositing turned on, black lock screen when using Breeze Plasma style, but controls are all there and remain interactive
https://bugs.kde.org/show_bug.cgi?id=483163 --- Comment #127 from Nicole Schoebel --- For me the bug was gone in 6.3.0 and remains fixed in 6.3.1. This is on Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
