[dolphin] [Bug 493281] New: Columns in search view not remembered between sessions
https://bugs.kde.org/show_bug.cgi?id=493281 Bug ID: 493281 Summary: Columns in search view not remembered between sessions Classification: Applications Product: dolphin Version: 24.08.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: john@pelago.org.uk CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Customised columns in the search view are not used when a Dolphin session is restored. STEPS TO REPRODUCE 1. Run Dolphin 2. Go into Configure Dolphin window 3. Make sure "Show on startup: Folders, tabs, and window state from last time" is enabled 4. Press Ctrl+F 5. Search for something simple, e.g. "txt" 6. Right-click on the column headings and add a column, e.g. size 7. Observe that the size column has been added 8. Quit Dolphin 9. Run Dolphin again OBSERVED RESULT The search results appear as from last time, but the size column is no longer present. EXPECTED RESULT The search results appear as from last time, including the size column. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240916 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.10.9-1-default (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION Note that if you do a new search in the new Dolphin session, the additional size column will appear. So the custom columns are remembered in general, just not used in a search results tab that is initially opened in a restored session. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 491426] Some categories not working
https://bugs.kde.org/show_bug.cgi?id=491426 John Veness changed: What|Removed |Added Summary|Some cattegories not |Some categories not working |working | CC||john@pelago.org.uk -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 471548] Auto-Update for flatpaks, via Discover appears to be non-functional
https://bugs.kde.org/show_bug.cgi?id=471548 John changed: What|Removed |Added CC||johnmaveric...@mail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454339] tooltips shown when mouse outside of file name
https://bugs.kde.org/show_bug.cgi?id=454339 John Veness changed: What|Removed |Added Status|REPORTED|RESOLVED CC||john@pelago.org.uk Resolution|--- |DUPLICATE --- Comment #2 from John Veness --- *** This bug has been marked as a duplicate of bug 455645 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 455645] Tooltip frequently covers filenames when it appears
https://bugs.kde.org/show_bug.cgi?id=455645 --- Comment #15 from John Veness --- *** Bug 454339 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485824] Support expand-selected and expand-all single-level and recursive functions when navigating folders using Dolphin's detailed tree view
https://bugs.kde.org/show_bug.cgi?id=485824 John Veness changed: What|Removed |Added CC||john@pelago.org.uk --- Comment #2 from John Veness --- I think this would be useful too. For what it's worth, Windows (File) Explorer has had this for decades, using the "*" keyboard button. I still find myself hopefully pressing * sometimes in Dolphin! -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 492844] VP9 encoding is not GPU accelerated
https://bugs.kde.org/show_bug.cgi?id=492844 --- Comment #2 from Francis John Baldon --- After using libva-intel-driver for days, I'm not sure now if the bug is caused by Spectacle solely. As I've noticed, even chromium now doesn't do vp9 decoding, so this might be a driver issue. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 492844] New: VP9 encoding not working
https://bugs.kde.org/show_bug.cgi?id=492844 Bug ID: 492844 Summary: VP9 encoding not working Classification: Applications Product: Spectacle Version: 24.08.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: fjbal...@tuta.io CC: k...@david-redondo.de Target Milestone: --- Created attachment 173459 --> https://bugs.kde.org/attachment.cgi?id=173459&action=edit output from vainfo SUMMARY Attached is an output from vainfo. I'm having high cpu usage when I do webm/vp9 screen recording on spectacle. The default format is webm/vp9 and when I switch to mp4/h.264, cpu usage drastically decreases. I'm also seeing activity on the Video row when I'm using mp4/h.264 but nothing on webm/vp9. I have this line on my vainfo output so I assume I can encode vp9 on my igpu: "VAProfileVP9Profile0: VAEntrypointEncSlice" STEPS TO REPRODUCE 1. Screen record using Spectacle (Wayland) 2. Use System Monitor or intel_gpu_top to monitor cpu and gpu usage 3. Spectacle does not offload its encoding to the gpu, instead it uses only the cpu OBSERVED RESULT Spectacle does not use the gpu when encoding the video EXPECTED RESULT Spectacle uses the gpu when encoding the video SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Fedora Linux 40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ghostwriter] [Bug 492363] Ghostwriter crashes with a segment fault on very fresh installed neon after one character is typed.
https://bugs.kde.org/show_bug.cgi?id=492363 --- Comment #5 from John Kizer --- (In reply to Me from comment #4) > I added a new key to ~/.config/kde.org/ghostwriter.conf and it worked. > > ghostwriter.conf wasn't even on my computer when I first ran ghostwriter. I > manually added it after seeing a post elsewhere about it causing problems if > it was missing. > > I added this key to chostwriter.conf and it now works. > > ``` > [Preview] > lastUsedExporter=cmark-gfm > ``` Interesting - adding that file, with the key you mentioned, enabled me to start typing, but opening the File Open dialog caused a crash just as before. Getting closer, at least! -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 491942] I/O error on attempting to scan
https://bugs.kde.org/show_bug.cgi?id=491942 John Carrick Smith changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 492638] some apps making my pc slow
https://bugs.kde.org/show_bug.cgi?id=492638 john millar changed: What|Removed |Added URL||https://www.insuranceexplai ||ns.com/ -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 492638] New: some apps making my pc slow
https://bugs.kde.org/show_bug.cgi?id=492638 Bug ID: 492638 Summary: some apps making my pc slow Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: hm86...@jcbouchet.fr Target Milestone: --- I’m experiencing slow performance on my PC, and I suspect it’s due to certain applications. Could you please help identify which apps might be causing this slowdown and suggest ways to optimize or manage them? Your assistance in resolving this issue would be greatly appreciated. -- You are receiving this mail because: You are watching all bug changes.
[ghostwriter] [Bug 492363] Ghostwriter crashes with a segment fault on very fresh installed neon after one character is typed.
https://bugs.kde.org/show_bug.cgi?id=492363 John Kizer changed: What|Removed |Added CC||john.ki...@proton.me --- Comment #2 from John Kizer --- I'm experiencing the same issue having just installed ghostwriter for the first time today, using the RPM packaged version in Fedora Linux 40 (KDE Spin). At least based on that, it wouldn't seem to be unique to the packaging format or base system. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 492597] New: Print dialog has usability issues
https://bugs.kde.org/show_bug.cgi?id=492597 Bug ID: 492597 Summary: Print dialog has usability issues Classification: Applications Product: okular Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: jwork12...@yahoo.com Target Milestone: --- Created attachment 173275 --> https://bugs.kde.org/attachment.cgi?id=173275&action=edit The print dialog window I discussed in this bug report SUMMARY Print dialog has usability issues STEPS TO REPRODUCE I have a number of issues that I collect here. I encounter these issues when using the print dialog from Okular. I cannot find a generic print dialog, perhaps a kind developer could correct this bug report to point to the correct component if necessary. 0. I normally press C-p to print a document There is a surprisingly long waiting time of 3 seconds on my new desktop computer before the dialog window opens. I would expect opening of a small window to be instantaneous. As a result I suspect something is wrong with my (default) configuration. 1. To be able to adjust or even review the print settings I am forced to click open "Options." Why? I want to print something, I need the options and I have enough screen real estate. There is no need to emulate the terrible (IMHO) behavior of eg Chrome where you feed the user a new bit of the print dialog one click at a time. 2. After clicking open Options I see a tab Options. What? I just clicked open "Options" 3. To make things worse I see a third tab, this one called "PDF Options". Both effectively hide the options from sight, forcing me now to click through the whole print dialog tab collection. Unfortunately I did not find the desired option - see next point. 4. I need to print 2 pages per sheet. This most definitely is not a property of the printer itself, yet I have to find this option not under any of the 3 options collections mentioned before, but under the properties of the printer. At this stage I decided I encountered enough oddities to justify a redesign of this dialog window. I imagine that, since the print dialog is often used aspect of KDE, it taints a user's experience of the whole desktop environment. So perhaps there could be a revisit of this dialog, where it could be made to behave according to some sensible user interface guidelines. Thanks a lot! OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 492597] Print dialog has usability issues
https://bugs.kde.org/show_bug.cgi?id=492597 John van Spaandonk changed: What|Removed |Added Version|unspecified |24.08.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482706] Incorporate Desktop Folder Settings into System Settings to only have a single place of configurations
https://bugs.kde.org/show_bug.cgi?id=482706 --- Comment #3 from John --- Created attachment 173233 --> https://bugs.kde.org/attachment.cgi?id=173233&action=edit Screenshot of the Desktop Window options in question -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482706] Incorporate Desktop Folder Settings into System Settings to only have a single place of configurations
https://bugs.kde.org/show_bug.cgi?id=482706 John changed: What|Removed |Added CC||johnmaveric...@mail.com --- Comment #2 from John --- I was about to report this myself I Would be great to be able to configure Mouse Actions / folder Location / Icons / Filters on system settings ADDITIONAL INFORMATION Attaching a screenshot of the window in question (accessed from the desktop) Méven Car already mentioned this is "possibly" coming soon, at https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3395 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 471840] Discover does not update an icon theme installed from KDE Store
https://bugs.kde.org/show_bug.cgi?id=471840 John changed: What|Removed |Added CC||johnmaveric...@mail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 492455] Updateable KNS content not shown on Discover's updates page
https://bugs.kde.org/show_bug.cgi?id=492455 John changed: What|Removed |Added CC||johnmaveric...@mail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 484498] Widgets/Addons cannot be updated
https://bugs.kde.org/show_bug.cgi?id=484498 John changed: What|Removed |Added CC||johnmaveric...@mail.com --- Comment #2 from John --- Dupe of bug 484057 (now fixed!)??? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 492037] Alt + Tab and Alt + Tab + arrows key don't work very well.
https://bugs.kde.org/show_bug.cgi?id=492037 --- Comment #1 from John Shokri --- Created attachment 172853 --> https://bugs.kde.org/attachment.cgi?id=172853&action=edit info -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 492037] New: Alt + Tab and Alt + Tab + arrows key don't work very well.
https://bugs.kde.org/show_bug.cgi?id=492037 Bug ID: 492037 Summary: Alt + Tab and Alt + Tab + arrows key don't work very well. Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bluelksh...@gmail.com Target Milestone: --- Created attachment 172852 --> https://bugs.kde.org/attachment.cgi?id=172852&action=edit Alt + Tab and Alt + Tab + arrows key don't work very well. SUMMARY I've been using Alt + Tab to switch between windows, but the problem is that it adds a tab to the text, and I don't know how to fix it. I've checked the Obsidian shortcuts, but there is no Alt + Tab shortcut. Furthermore, I have added a video of the bug. The second problem is that when I use Alt + Tab along with the arrow keys, it changes the time slider in SM Player. Linux/KDE Plasma: KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445065] Dolphin freezes on "disk sleep" when browsing samba mount
https://bugs.kde.org/show_bug.cgi?id=445065 --- Comment #8 from John van Spaandonk --- And just today I had the problem again, needed to reboot the PC.I guess I solved the cases where the PC falls asleep, but not the case where the NAS sleeps / connection is gone. On Wednesday, August 21, 2024 at 12:17:49 PM GMT+2, John van Spaandonk wrote: https://bugs.kde.org/show_bug.cgi?id=445065 --- Comment #7 from John van Spaandonk --- It may be interesting to know that:1. I noticed also konsole gets stuck if I try to browse the affected samba mounts, pointing to a deeper system issue2. I worked around this problem by setting up the samba mounts with autofs instead of fixed entries in fstab.3. A consequence is that I now never get suggestions for files on the mounts by pressing the windows key and typing the first letters. Apparently that needs a file mounted as if it is a local file. On Tuesday, August 20, 2024 at 12:41:10 PM GMT+2, postix wrote: https://bugs.kde.org/show_bug.cgi?id=445065 postix changed: What |Removed |Added CC| |pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445065] Dolphin freezes on "disk sleep" when browsing samba mount
https://bugs.kde.org/show_bug.cgi?id=445065 --- Comment #7 from John van Spaandonk --- It may be interesting to know that:1. I noticed also konsole gets stuck if I try to browse the affected samba mounts, pointing to a deeper system issue2. I worked around this problem by setting up the samba mounts with autofs instead of fixed entries in fstab.3. A consequence is that I now never get suggestions for files on the mounts by pressing the windows key and typing the first letters. Apparently that needs a file mounted as if it is a local file. On Tuesday, August 20, 2024 at 12:41:10 PM GMT+2, postix wrote: https://bugs.kde.org/show_bug.cgi?id=445065 postix changed: What |Removed |Added CC| |pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 436928] Option to apply updates on shutdown, not startup
https://bugs.kde.org/show_bug.cgi?id=436928 --- Comment #19 from John --- (In reply to Nate Graham from comment #18) > Not quite; Bug 452820 is what's (half) implemented by that merge request. > This one technically is something different. Can you elaborate more on this? >From Thomas' reply I got the impression that whenever we got updates, even not doing any action about it, if we went on into kicker to shutdown the computer, the logout greeter would show users the option to install the updates and shutdown! Is that not the case? Can you please clarify (for dummies)? Tks -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 491942] I/O error on attempting to scan
https://bugs.kde.org/show_bug.cgi?id=491942 --- Comment #2 from John Carrick Smith --- Will do. About to upgrade to openSUSE 15.6. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 436928] Option to apply updates on shutdown, not startup
https://bugs.kde.org/show_bug.cgi?id=436928 --- Comment #17 from John --- Relevant merge (it fixes this): https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4596 -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 491942] New: I/O error on attempting to scan
https://bugs.kde.org/show_bug.cgi?id=491942 Bug ID: 491942 Summary: I/O error on attempting to scan Classification: Applications Product: Skanlite Version: 22.12.3 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: jcarricksm...@gmail.com Target Milestone: --- Application: skanlite (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 5.14.21-150500.55.73-default x86_64 Windowing System: X11 Distribution: "openSUSE Leap 15.5" DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: I attempted to scan a page on my epson SX215 PSC as it was printing. There was a delay before a message box appeared with the message "I/O error". This occured on all attempts until I closed Skanlite and restarted it. The crash can be reproduced every time. -- Backtrace: Application: Skanlite (skanlite), signal: Segmentation fault [KCrash Handler] #4 0x7f88c5118c5d in KSaneCore::DeviceInformation::~DeviceInformation() () from /usr/lib64/libKSaneCore.so.1 #5 0x7f88c510c129 in ?? () from /usr/lib64/libKSaneCore.so.1 #6 0x7f88c56af90c in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7f88c489d6ea in start_thread () from /lib64/libpthread.so.0 #8 0x7f88c52ae58f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f8877fff700 (LWP 8053) "threaded-ml"): #1 0x7f88b9d9e531 in pa_read () from /usr/lib64/pulseaudio/libpulsecommon-15.0.so #2 0x7f88bb0a6d9e in pa_mainloop_prepare () from /usr/lib64/libpulse.so.0 #3 0x7f88bb0a7810 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #4 0x7f88bb0a78d0 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #5 0x7f88bb0b5559 in ?? () from /usr/lib64/libpulse.so.0 #6 0x7f88b9dd3ef8 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-15.0.so #7 0x7f88c489d6ea in start_thread () from /lib64/libpthread.so.0 #8 0x7f88c52ae58f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f88a28cc700 (LWP 8044) "skanlite"): #1 0x7f88bee02ad3 in ?? () from /usr/lib64/libusbmuxd-2.0.so.6 #2 0x7f88bee03f33 in ?? () from /usr/lib64/libusbmuxd-2.0.so.6 #3 0x7f88c489d6ea in start_thread () from /lib64/libpthread.so.0 #4 0x7f88c52ae58f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f88badff700 (LWP 7986) "QDBusConnection"): #1 0x7f88c33f2b49 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f88c33f2c5c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f88c590b88b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f88c58a778a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f88c56ae3a7 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f88c6af82e5 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f88c56af90c in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f88c489d6ea in start_thread () from /lib64/libpthread.so.0 #9 0x7f88c52ae58f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f88c284da00 (LWP 7984) "skanlite"): #1 0x7f88c56b620b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib64/libQt5Core.so.5 #2 0x7f88c56af511 in QThread::wait(QDeadlineTimer) () from /usr/lib64/libQt5Core.so.5 #3 0x7f88c510bfd2 in ?? () from /usr/lib64/libKSaneCore.so.1 #4 0x7f88c510c089 in ?? () from /usr/lib64/libKSaneCore.so.1 #5 0x7f88c510fbae in KSaneCore::Interface::~Interface() () from /usr/lib64/libKSaneCore.so.1 #6 0x7f88c510fbe9 in KSaneCore::Interface::~Interface() () from /usr/lib64/libKSaneCore.so.1 #7 0x7f88c71cfd4f in KSaneIface::KSaneWidget::~KSaneWidget() () from /usr/lib64/libKF5Sane.so.5 #8 0x7f88c71cfd99 in KSaneIface::KSaneWidget::~KSaneWidget() () from /usr/lib64/libKF5Sane.so.5 #9 0x7f88c58d9a9b in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #10 0x7f88c6484836 in QWidget::~QWidget() () from /usr/lib64/libQt5Widgets.so.5 #11 0x55a8ec2a258c in ?? () #12 0x7f88c51cb24d in __libc_start_main () from /lib64/libc.so.6 #13 0x55a8ec2a26ca in ?? () [Inferior 1 (process 7984) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428320] Double-click window frame should horizontally or vertically maximize
https://bugs.kde.org/show_bug.cgi?id=428320 --- Comment #5 from John Veness --- It looks like this was added in Plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 491915] John Jerry' (Profile)
https://bugs.kde.org/show_bug.cgi?id=491915 John Jerry changed: What|Removed |Added Summary|Some apps are not working |John Jerry' (Profile) |in my PC| -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 491915] Some apps are not working in my PC
https://bugs.kde.org/show_bug.cgi?id=491915 John Jerry changed: What|Removed |Added URL||https://www.navicosoft.com/ -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 491915] New: Some apps are not working in my PC
https://bugs.kde.org/show_bug.cgi?id=491915 Bug ID: 491915 Summary: Some apps are not working in my PC Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: johnjerry5...@gmail.com Target Milestone: --- hosting and digital marketing agency. Best web hosting and digital marketing agency. I'm John Jerry and working at Navicosoft since 2018. Navicosoft offers a full range of digital services, including web design, development, SEO, and digital marketing. We specialize in creating tailored strategies for businesses, enhancing online presence and driving growth. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 442379] When using Natural Scrolling, scrolling direction to change volume is inverted
https://bugs.kde.org/show_bug.cgi?id=442379 John Veness changed: What|Removed |Added CC||john@pelago.org.uk --- Comment #15 from John Veness --- Is this really fixed? I'm still seeing this issue in: Operating System: openSUSE Tumbleweed 20240815 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.4-1-default (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 491756] Akregator crashes immediately on start after Fedora's 2024-08-15 updates
https://bugs.kde.org/show_bug.cgi?id=491756 --- Comment #2 from John Kizer --- I'm pretty sure this is: https://github.com/NVIDIA/egl-wayland/issues/127 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 491756] Akregator crashes immediately on start after Fedora's 2024-08-15 updates
https://bugs.kde.org/show_bug.cgi?id=491756
--- Comment #1 from John Kizer ---
Crash report info from the Crash Handler:
Application: Akregator (akregator), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[New LWP 6558]
[New LWP 6538]
[New LWP 6540]
[New LWP 6539]
[New LWP 6541]
[New LWP 6549]
[New LWP 6551]
[New LWP 6553]
[New LWP 6543]
[New LWP 6552]
[New LWP 6554]
[New LWP 6557]
[New LWP 6550]
[New LWP 6555]
[New LWP 6562]
[New LWP 6572]
[New LWP 6560]
[New LWP 6561]
[New LWP 6573]
[New LWP 6563]
[New LWP 6559]
[New LWP 6556]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/akregator'.
Program terminated with signal SIGABRT, Aborted.
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
[Current thread is 1 (Thread 0x7f9e3ea006c0 (LWP 6558))]
python sentry-sdk not installed :(
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7f9e3ea006c0 (LWP 6558))]
Thread 22 (Thread 0x7f9e3fe006c0 (LWP 6556)):
#0 0x7f9e8e2a2da9 in __futex_abstimed_wait_common64 (private=0,
futex_word=0x7f9e3fdfebf8, expected=0, op=393, abstime=0x0, cancel=true) at
futex-internal.c:57
#1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x7f9e3fdfebf8,
expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0,
private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2 0x7f9e8e2a2e2f in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x7f9e3fdfebf8, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
futex-internal.c:139
#3 0x7f9e8e2a57f9 in __pthread_cond_wait_common (cond=0x7f9e3fdfebd0,
mutex=, clockid=0, abstime=0x0) at pthread_cond_wait.c:503
#4 ___pthread_cond_wait (cond=0x7f9e3fdfebd0, mutex=) at
pthread_cond_wait.c:618
#5 0x7f9e87f9376e in base::ConditionVariable::Wait () at
./../../../../../src/3rdparty/chromium/base/synchronization/condition_variable_posix.cc:105
#6 0x7f9e87fb96a8 in base::WaitableEvent::TimedWaitImpl () at
./../../../../../src/3rdparty/chromium/base/synchronization/waitable_event_posix.cc:193
#7 0x7f9e87f3e710 in base::WaitableEvent::TimedWait () at
./../../../../../src/3rdparty/chromium/base/synchronization/waitable_event.cc:39
#8 0x7f9e87f79fe4 in base::internal::WorkerThread::RunWorker () at
./../../../../../src/3rdparty/chromium/base/task/thread_pool/worker_thread.cc:438
#9 0x7f9e87f7ab0d in base::internal::WorkerThread::RunPooledWorker () at
./../../../../../src/3rdparty/chromium/base/task/thread_pool/worker_thread.cc:359
#10 0x7f9e87f7ac98 in base::internal::WorkerThread::ThreadMain () at
./../../../../../src/3rdparty/chromium/base/task/thread_pool/worker_thread.cc:339
#11 0x7f9e87f9417a in ThreadFunc () at
./../../../../../src/3rdparty/chromium/base/threading/platform_thread_posix.cc:101
#12 0x7f9e8e2a66d7 in start_thread (arg=) at
pthread_create.c:447
#13 0x7f9e8e32a60c in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Thread 21 (Thread 0x7f9e3e0006c0 (LWP 6559)):
#0 0x7f9e8e32aa32 in epoll_wait (epfd=62,
events=events@entry=0x7f9e08001030, maxevents=32, timeout=timeout@entry=-1) at
../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1 0x7f9e8066b435 in epoll_dispatch (base=0x7f9e08000d70, tv=) at /usr/src/debug/libevent-2.1.12-12.fc40.x86_64/epoll.c:465
#2 0x7f9e80662f88 in event_base_loop (base=0x7f9e08000d70, flags=1) at
/usr/src/debug/libevent-2.1.12-12.fc40.x86_64/event.c:1992
#3 0x7f9e87fb69c0 in base::MessagePumpLibevent::Run () at
./../../../../../src/3rdparty/chromium/base/message_loop/message_pump_libevent.cc:353
#4 base::MessagePumpLibevent::Run () at
./../../../../../src/3rdparty/chromium/base/message_loop/message_pump_libevent.cc:273
#5 0x7f9e87f5bb87 in
base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run ()
at
./../../../../../src/3rdparty/chromium/base/task/sequence_manager/thread_controller_with_message_pump_impl.cc:645
#6 0x7f9e87f2277d in base::RunLoop::Run () at
./../../../../../src/3rdparty/chromium/base/run_loop.cc:134
#7 base::RunLoop::Run () at
./../../../../../src/3rdparty/chromium/base/run_loop.cc:106
#8 0x7f9e87f7f358 in base::Thread::Run () at
./../../../../../src/3rdparty/chromium/base/threading/thread.cc:337
#9 0x7f9e89ef4af5 in Run () at
./../../../../../src/3rdparty/chromium/content/child/child_process.cc:60
#10 0x7f9e87f7f858 in base::Thread::ThreadMain () at
./../../../../../src/3rdparty/chromium/base/threading/thread.cc:409
#11 0x7f9e87f9417a in ThreadFunc () at
./../../../../../src/3rdparty/chromium/base/threading/platform_thread_posix.cc:101
#12 0x7f9e8e2a66d7 in start_thread (arg=) at
pthread_create.c:447
#13 0x
[akregator] [Bug 491756] New: Akregator crashes immediately on start after Fedora's 2024-08-15 updates
https://bugs.kde.org/show_bug.cgi?id=491756 Bug ID: 491756 Summary: Akregator crashes immediately on start after Fedora's 2024-08-15 updates Classification: Applications Product: akregator Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: john.ki...@proton.me Target Milestone: --- SUMMARY After running system updates on 2024-08-15, Akregator crashes immediately on start (no window appears). STEPS TO REPRODUCE 1. Start Akregator from the Application Launcher OBSERVED RESULT Akregator crashes EXPECTED RESULT Akregator launches successfully SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 40 KDE Spin KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Below are the packages that upgraded between Akregator launching successfully and crashing on launch, if that is helpful: Packages Altered: Install kernel-6.10.4-200.fc40.x86_64 @updates Install kernel-core-6.10.4-200.fc40.x86_64 @updates Install kernel-devel-6.10.4-200.fc40.x86_64 @updates Install kernel-modules-6.10.4-200.fc40.x86_64 @updates Install kernel-modules-core-6.10.4-200.fc40.x86_64 @updates Install kernel-modules-extra-6.10.4-200.fc40.x86_64 @updates Upgrade Box2D-2.4.2-1.fc40.x86_64 @updates Upgrade btrfs-progs-6.10-1.fc40.x86_64 @updates Upgrade egl-wayland-1.1.15-1.fc40.x86_64 @updates Upgrade kernel-devel-matched-6.10.4-200.fc40.x86_64 @updates Upgrade libimagequant-4.0.3-5.fc40.x86_64 @updates Upgrade libldb-2.9.1-4.fc40.x86_64 @updates Upgrade openssl-1:3.2.2-3.fc40.x86_64 @updates Upgrade openssl-devel-1:3.2.2-3.fc40.x86_64 @updates Upgrade openssl-libs-1:3.2.2-3.fc40.i686 @updates Upgrade openssl-libs-1:3.2.2-3.fc40.x86_64 @updates Upgrade tigervnc-license-1.14.0-2.fc40.noarch @updates Upgrade tigervnc-server-minimal-1.14.0-2.fc40.x86_64 @updates Upgrade vim-data-2:9.1.672-1.fc40.noarch @updates Upgrade vim-minimal-2:9.1.672-1.fc40.x86_64 @updates Upgrade brave-browser-1.68.141-1.x86_64 @brave-browser Upgraded kernel-6.9.11-200.fc40.x86_64 @@System Upgraded kernel-core-6.9.11-200.fc40.x86_64 @@System Upgraded kernel-devel-6.9.11-200.fc40.x86_64 @@System Upgraded kernel-modules-6.9.11-200.fc40.x86_64 @@System Upgraded kernel-modules-core-6.9.11-200.fc40.x86_64 @@System Upgraded kernel-modules-extra-6.9.11-200.fc40.x86_64 @@System Removed kmod-nvidia-6.9.11-200.fc40.x86_64-3:555.58.02-1.fc40.x86_64 @@System Upgraded Box2D-2.4.1-14.fc40.x86_64 @@System Upgraded btrfs-progs-6.9.2-1.fc40.x86_64 @@System Upgraded egl-wayland-1.1.13-3.fc40.x86_64 @@System Upgraded kernel-devel-matched-6.10.3-200.fc40.x86_64 @@System Upgraded libimagequant-4.0.3-3.fc40.x86_64 @@System Upgraded libldb-2.9.1-1.fc40.x86_64 @@System Upgraded openssl-1:3.2.1-2.fc40.x86_64 @@System Upgraded openssl-devel-1:3.2.1-2.fc40.x86_64 @@System Upgraded openssl-libs-1:3.2.1-2.fc40.i686 @@System Upgraded openssl-libs-1:3.2.1-2.fc40.x86_64 @@System Upgraded tigervnc-license-1.13.1-14.fc40.noarch @@System Upgraded tigervnc-server-minimal-1.13.1-14.fc40.x86_64 @@System Upgraded vim-data-2:9.1.660-1.fc40.noarch @@System Upgraded vim-minimal-2:9.1.660-1.fc40.x86_64 @@System Upgraded brave-browser-1.68.137-1.x86_64 @@System -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 491684] New: Ampersands (&) in filename missing in "Actions for" button
https://bugs.kde.org/show_bug.cgi?id=491684 Bug ID: 491684 Summary: Ampersands (&) in filename missing in "Actions for" button Classification: Applications Product: dolphin Version: 24.05.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: john@pelago.org.uk CC: kfm-de...@kde.org Target Milestone: --- SUMMARY If you add the "Actions for" button to the toolbar, filenames that contain "&" will not appear correctly in that button. STEPS TO REPRODUCE 1. Run Dolphin 2. Configure Toolbars 3. Add the "Actions for..." button to the toolbar 4. Click on a file or folder with an ampersand in the name, e.g. "Night & Day" OBSERVED RESULT Button text says: Actions for "Night Day" EXPECTED RESULT Button text says: Actions for "Night & Day" SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240811 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.3-1-default (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
kde-bugs-dist@kde.org
https://bugs.kde.org/show_bug.cgi?id=491674
Bug ID: 491674
Summary: Dolphin Kleopatra actions display with "&&" rather
than "&"
Classification: Applications
Product: kleopatra
Version: 3.2.0.240502
Platform: openSUSE
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: aheine...@gnupg.org
Reporter: john@pelago.org.uk
CC: kdepim-b...@kde.org, m...@kde.org
Target Milestone: ---
Created attachment 172586
--> https://bugs.kde.org/attachment.cgi?id=172586&action=edit
Dolphin Kleopatra actions
SUMMARY
I'm unsure if this is a Kleopatra bug or a Dolphin one! In Dolphin, there are
right-click actions which come from Kleopatra and which contain double
ampersands ("&&") instead of single, which I assume was intended.
STEPS TO REPRODUCE
1. Ensure both Dolphin and Kleopatra are installed
2. Run Dolphin
3. Right-click on a folder
4. Go into the Actions submenu
OBSERVED RESULT
Entries "Archive && Encrypt Folder" and "Archive, Sign && Encrypt Folder".
EXPECTED RESULT
Entries "Archive & Encrypt Folder" and "Archive, Sign & Encrypt Folder".
SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240811
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.3-1-default (64-bit)
Graphics Platform: X11
ADDITIONAL INFORMATION
I assume the double-ampersands were intended to display as a single ampersand,
because of the Qt QAction feature described at
https://doc.qt.io/qt-6/qaction.html#text-prop , but something seems to be awry
here!
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 491550] Unmasked password should be masked as soon as confirming
https://bugs.kde.org/show_bug.cgi?id=491550 --- Comment #4 from John Veness --- Oh that's interesting. I'm using Breeze Dark, as supplied in openSUSE Tumbleweed. Note that I'm not talking about the SDDM login screen, which doesn't have an eye button, but the lock session screen (e.g. Meta+L). I've attached a couple of photos. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491550] Unmasked password should be masked as soon as confirming
https://bugs.kde.org/show_bug.cgi?id=491550 --- Comment #3 from John Veness --- Created attachment 172555 --> https://bugs.kde.org/attachment.cgi?id=172555&action=edit Unmasked password -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491550] Unmasked password should be masked as soon as confirming
https://bugs.kde.org/show_bug.cgi?id=491550 --- Comment #2 from John Veness --- Created attachment 172554 --> https://bugs.kde.org/attachment.cgi?id=172554&action=edit Masked password -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 491632] New: Battery Critical notification wording and countdown
https://bugs.kde.org/show_bug.cgi?id=491632 Bug ID: 491632 Summary: Battery Critical notification wording and countdown Classification: Plasma Product: Powerdevil Version: 6.1.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: john@pelago.org.uk CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 172548 --> https://bugs.kde.org/attachment.cgi?id=172548&action=edit Battery Critical notification SUMMARY I have a couple of suggestions for improving the current Battery Critical notification - see Expected Result. STEPS TO REPRODUCE 1. Use a battery-powered device 2. Allow your battery to deplete to 5% 3. Observe the Battery Critical notification OBSERVED RESULT Notification says: Battery Critical (5% Remaining). Battery level critical. Your computer will enter hibernation mode in 60 seconds. The notification will be static over those 60 seconds (unless you plug a power lead in, in which case it will disappear, as expected.) EXPECTED RESULT I suggest that the "60 seconds" part of the message be turned into a countdown that updates once per second, so the user can see exactly how long they've got to rush for a power lead. Also, "Your computer will enter hibernation mode" could be less jargon-y as "Your computer will hibernate", especially as the button below says "Hibernate Now" not "Enter Hibernation Mode Now". Possibly it shouldn't say "Your computer", maybe just "The computer" or "This computer" - I'm not sure if there's a HIG for this. Also also, you may not need the repetition of "Battery level critical" in the body, as it's already in the header, especially on a message you want to read quickly. As always, I suggest a usability expert should take a look at the wording for this rather than just taking my suggestions! SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240811 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.3-1-default (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 491630] New: User-facing use of word "module" considered jargon?
https://bugs.kde.org/show_bug.cgi?id=491630 Bug ID: 491630 Summary: User-facing use of word "module" considered jargon? Classification: Applications Product: systemsettings Version: 6.1.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: john@pelago.org.uk Target Milestone: --- Created attachment 172547 --> https://bugs.kde.org/attachment.cgi?id=172547&action=edit System Settings module mention SUMMARY If you change a setting in one KCM, and click to navigate to another without first Applying, an error message appears that refers to "the current module". This use of the word "module" here seems a bit jargon-y to me, especially as (as far as I can see) they are not generally referred to as modules in the UI. STEPS TO REPRODUCE 1. Open System Settings 2. Click on Mouse & Touchpad, Mouse 3. Change setting of Invert scroll direction 4. Don't click Apply 5. Click on Sound OBSERVED RESULT Error message appears saying "The settings of the current module have changed. Do you want to apply the changes or discard them?" EXPECTED RESULT Maybe "The settings on the current page have changed" or "The settings on this page have changed" would be better. But please let someone who is good at technical end-user writing take a look at this rather than just me! Also see the HIG https://develop.kde.org/hig/text_and_labels/ SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240811 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.3-1-default (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478443] Maximized state not remembered across launches
https://bugs.kde.org/show_bug.cgi?id=478443 John Veness changed: What|Removed |Added CC||nep...@pm.me --- Comment #10 from John Veness --- *** Bug 487197 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487197] Plasma systemsettings doesn't remember the window state
https://bugs.kde.org/show_bug.cgi?id=487197 John Veness changed: What|Removed |Added CC||john@pelago.org.uk Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from John Veness --- *** This bug has been marked as a duplicate of bug 478443 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438689] While a KCM is focused, Ctrl + F focuses the sidebar's search field typing doesn't input text
https://bugs.kde.org/show_bug.cgi?id=438689 John Veness changed: What|Removed |Added CC||john@pelago.org.uk -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447366] Screen locking should be referenced (linked or inserted) under power management
https://bugs.kde.org/show_bug.cgi?id=447366 John Veness changed: What|Removed |Added CC||john@pelago.org.uk -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 491624] Custom Duration oddities in Power Management settings
https://bugs.kde.org/show_bug.cgi?id=491624 John Veness changed: What|Removed |Added Component|general |kcm_powerdevil CC||k...@privat.broulik.de Product|Powerdevil |systemsettings -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 491624] New: Custom Duration oddities in Power Management settings
https://bugs.kde.org/show_bug.cgi?id=491624 Bug ID: 491624 Summary: Custom Duration oddities in Power Management settings Classification: Plasma Product: Powerdevil Version: 6.1.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: john@pelago.org.uk CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 172541 --> https://bugs.kde.org/attachment.cgi?id=172541&action=edit Custom Duration dialog SUMMARY The Custom Duration dialog box that pops up in System Settings, Power Management, seems to have confusing behaviour. STEPS TO REPRODUCE 1. Open System Settings 2. Go to Power Management page 3. Choose any power profile tab 4. Choose either of the timeout dropdowns (for Suspend Session, or Turn off screen) and choose Custom 5. Try to type numbers greater than OBSERVED RESULT Difficult to describe, but see video. You'll notice first off I type in 5000 which shows correctly as "5,000" but then I add another zero which shows incorrectly as "5," (should be "50,000"). When I press OK it changes to 5000 anyway. I enter custom again and change the 5000 to 5 and click OK, and it changes to 1. I enter custom again, type 5, then use the up arrow to increment. Instead of incrementing to 50001 it increments to 5001. If I type in then increment, it will allow numbers greater than , which I'm not sure is intentional. EXPECTED RESULT Custom duration should work more sanely! SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240811 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.3-1-default (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION Note that the similar Custom Duration dialog in System Settings, Screen Locking seems to act sanely. It seems to allow timeouts up to minutes, doesn't allow exceeding that, and doesn't display the same oddities described above as the one in Power Management. I wonder if it's some mismatch as to whether the textbox should allow maximum four digits or maximum five, where the intention was to limit it to four digits, but which sometimes accepts five digits. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486604] Can't use the "When locked, turn off screen" option when "Turn off screen" is set to Never in Power Management settings
https://bugs.kde.org/show_bug.cgi?id=486604
John Veness changed:
What|Removed |Added
Summary|Can't use the "When locked, |Can't use the "When locked,
|turn off screen" option |turn off screen" option
|when "Turn off screen" is |when "Turn off screen" is
|disabled in the Energy |set to Never in Power
|Saving settings |Management settings
CC| |john@pelago.org.uk
--- Comment #1 from John Veness ---
Came here to report the same thing. My use case is that I want to monitor a
long-running process by glancing at the screen, without the screen turning off.
But if I manually lock the session, I *would* like the screen to turn off after
a short while.
I am using Plasma 6.1.4 and the above instructions are now:
STEPS TO REPRODUCE
1. Go to System Settings -> Power Management
2. Go to any power profile
3. Set "Turn off screen" to Never
OBSERVED RESULT
"When locked" dropdown is disabled
EXPECTED RESULT
"When locked" dropdown should not be disabled
--
You are receiving this mail because:
You are watching all bug changes.
[kscreenlocker] [Bug 491550] Unmasked password should be masked as soon as confirming
https://bugs.kde.org/show_bug.cgi?id=491550 John Veness changed: What|Removed |Added Summary|Unmasked password should be |Unmasked password should be |made masked as soon as |masked as soon as |confirming |confirming -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 491550] New: Unmasked password should be made masked as soon as confirming
https://bugs.kde.org/show_bug.cgi?id=491550 Bug ID: 491550 Summary: Unmasked password should be made masked as soon as confirming Classification: Plasma Product: kscreenlocker Version: 6.1.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: john@pelago.org.uk Target Milestone: --- SUMMARY If you enter a password on the lock screen, then press the eye icon to make it visible, then press Return or click the arrow, the password should be immediately masked (i.e. turned into circles) before anything else. See Additional Info for why. STEPS TO REPRODUCE 1. Lock your screen 2. Type your password in 3. Press the eye button to make the password visible 4. Press Return OBSERVED RESULT The password is still visible for a short while (see Additional Info). EXPECTED RESULT The password is immediately masked. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240808 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.10.3-1-default (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION I have two use cases for this: 1, I was using an old laptop with not a lot of RAM, which spends a lot of time swapping (I realise this is not optimal, but anyway). I typed in my password, pressed the eye to check it (as I typed it wrong the first time), then pressed Return. Because of the low performance/high swapping of the machine, the correct password was left visible for three or four seconds while the PC was churning away, before the screen unlocked. 2, Even on a fast performance machine, if you unmask the password and still manage to type the password in incorrectly, the incorrect password is left visible for about three seconds before it disappears, even though it is greyed out immediately. As I say, in my opinion, in both these cases the password should be masked immediately you press Return/arrow (in the same way it's greyed out immediately), before any further processing as to whether the password is correct or not. Presumably there are other situations, not just slow machines, that may cause slow checking of passwords, such as when using LDAP on a slow network, where again you would not want the password to continue to be visible for so long. Thanks for reading! -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 491249] Typing in Application Dashboard with maliit-keyboard does not perform a search
https://bugs.kde.org/show_bug.cgi?id=491249 --- Comment #1 from John van Capel --- Possibly related to #421352: https://bugs.kde.org/show_bug.cgi?id=421352 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 491362] New: Capitalisation of "internet"
https://bugs.kde.org/show_bug.cgi?id=491362 Bug ID: 491362 Summary: Capitalisation of "internet" Classification: Plasma Product: plasma-nm Version: 6.1.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: john@pelago.org.uk Target Milestone: --- SUMMARY To match the HIG, "internet" should be capitalised in the message "This device appears to be connected to a network but is unable to reach the internet." STEPS TO REPRODUCE 1. Unplug your router from the Internet 2. Connect to your router OBSERVED RESULT See message "This device appears to be connected to a network but is unable to reach the internet." EXPECTED RESULT See message "This device appears to be connected to a network but is unable to reach the Internet." SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240805 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.10.2-1-default (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION https://develop.kde.org/hig/text_and_labels/#capitalization-and-punctuation -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 491249] Typing in Application Dashboard with maliit-keyboard does not perform a search
https://bugs.kde.org/show_bug.cgi?id=491249 John van Capel changed: What|Removed |Added CC||jvanca...@live.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491260] plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=491260 --- Comment #1 from John mcloskey --- Created attachment 172271 --> https://bugs.kde.org/attachment.cgi?id=172271&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491260] New: plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=491260 Bug ID: 491260 Summary: plasmashell crash Classification: Plasma Product: plasmashell Version: 6.1.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: johnmclos...@gmail.com Target Milestone: 1.0 Application: plasmashell (6.1.3) Qt Version: 6.7.2 Frameworks Version: 6.4.0 Operating System: Linux 6.10.2-202.fsync.fc40.x86_64 x86_64 Windowing System: Wayland Distribution: Nobara Linux 40 (KDE Plasma) DrKonqi: 6.1.3 [CoredumpBackend] -- Information about the crash: 1. boot fresh install using Nobara-40-Steam-HTPC-2024-07-26.iso from https://nobaraproject.org/download-nobara/ 2. login (plasma session) loads desktop environment without error 3. sudo dnf install gdb (to allow crash reporting) 4. sudo dnf update rpmfusion-nonfree-release rpmfusion-free-release fedora-repos nobara-repos --refresh && sudo dnf distro-sync --refresh && sudo dnf update --refresh 5. sudo reboot 6. login (plasma session) crashes everytime 7. neofetch (below) ⠀⠀⢀⣤⣴⣶⣶⣶⣦⣤⡀⠀⣀⣠⣤⣴⣤⣤⣀⡀ --- ⠀⣰⣿⣿⣿⣶⣤⡀ OS: Nobara Linux 40 (KDE Plasma) x86_64 ⠀⣿⣿⣿⣷⣄⠀⠀ Host: HX99G ⠀⣿⣷⣄ Kernel: 6.10.2-202.fsync.fc40.x86_64 ⠀⣿⣿⣿⣧⠀⠀⠀ Uptime: 30 mins ⠀⣿⣿⠟⠋⠉⠁⠀⠀⠉⠉⠛⠿⣧⠀⠀ Packages: 3121 (rpm) ⠀⠟⠁⠀⠀⠀⢀⣀⣀⡀⠀⠀⠀⠈⢻⣿⣿⣿⡇⠀ Shell: bash 5.2.26 ⠀⣿⣿⣿⡏⠀⠀⠀⢠⣾⣷⡄⠀⠀⠀⠻⠿⢿⣿⠀ Resolution: 3440x1440 ⠀⣿⣿⣿⠁⠀⠀⠀⣿⣿⣿⡇⠀⣀⣀⣬⣽⣿⣿⠀ DE: Plasma 6.1.3 ⠀⣿⣿⣿⠈⠻⢿⣿⣿⡿⠟⠁⠀⠀⠀⢸⣿⣿⣿⠀ WM: kwin ⠀⣿⣿⣿⣇⠀⠀⢸⣿⣿⣿⠀ Theme: Breeze-Dark [GTK2], Breeze [GTK3] ⠀⣷⣤⣤⣄⣀⡀⢸⣿⣿⣿⠀ Icons: breeze-dark [GTK2/3] ⠀⣿⣿⣷⣄⠀⠀⢸⣿⣿⣿⠀ Terminal: konsole ⠀⣇⠀⢸⣿⣿⣿⠀ CPU: AMD Ryzen 9 6900HX with Radeon Graphics (16) @ 4.935GHz ⠀⣿⣿⣿⡿⠟⠛⠉⠉⠛⠛⢿⣿⣿⠀⠸⣿⣿⡿⠀ GPU: AMD ATI Radeon RX 6650 XT / 6700S / 6800S ⠀⠘⢿⣿⣿⣿⡿⠋⠈⢿⠀⠀⠙⢿⣿⣿⣿⠟⠁⠀ Memory: 3448MiB / 64064MiB The crash can be reproduced every time. -- Backtrace (Reduced): #5 QQmlRefPointer::QQmlRefPointer (this=0x7f30a9ffe578, other=...) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/ftw/qqmlrefcount_p.h:184 #6 QQmlType::QQmlType (this=this@entry=0x7f30a9ffe578) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmltype.cpp:98 #7 0x7f30ec20f9d5 in QV4::ResolvedTypeReference::type (this=) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/jsruntime/qv4resolvedtypereference_p.h:46 #8 QQmlPropertyCacheCreator::propertyCacheForObject (this=this@entry=0x7f30a9ffe990, obj=obj@entry=0x7f3070299818, context=..., error=error@entry=0x7f30a9ffe660) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmlpropertycachecreator_p.h:365 #9 0x7f30ec21f109 in QQmlPropertyCacheCreator::buildMetaObjectRecursively (this=this@entry=0x7f30a9ffe990, objectIndex=1, context=..., isVMERequired=isVMERequired@entry=QQmlPropertyCacheCreator::VMEMetaObjectIsRequired::Maybe) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmlpropertycachecreator_p.h:279 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 491249] New: Typing in Application Dashboard with maliit-keyboard does not perform a search
https://bugs.kde.org/show_bug.cgi?id=491249 Bug ID: 491249 Summary: Typing in Application Dashboard with maliit-keyboard does not perform a search Classification: I don't know Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jvanca...@live.com Target Milestone: --- Created attachment 172265 --> https://bugs.kde.org/attachment.cgi?id=172265&action=edit Screenshot of observed result. SUMMARY When using a 2-in-1 device, I cannot search in the Application Dashboard with an on-screen keyboard by using the touchscreen. Instead, it simply inserts the text into "Type to search". STEPS TO REPRODUCE 1. Enable on-screen keyboard 2. Open Application Dashboard 3. Tap "Type to Search" to bring up virtual keyboard 4. Type text OBSERVED RESULT - Text gets inserted into "Type to search" dialogue. Backspace does nothing, and no search occurs. See attached screenshot. EXPECTED RESULT - A search occurs. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.12-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484871] Make it easier to revert to old default wallpaper after a Plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=484871 --- Comment #3 from John Veness --- Thanks Nate. Installing plasma6-workspace-wallpapers did indeed bring the old wallpapers back. It's good to know this is being done from the KDE side. I've opened https://bugzilla.opensuse.org/show_bug.cgi?id=1228603 to ask if openSUSE can install that package by default. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 464451] Arrows to go to Previous or Next Image Stop Working After Zoom Level is Changed
https://bugs.kde.org/show_bug.cgi?id=464451 John Veness changed: What|Removed |Added CC||john@pelago.org.uk --- Comment #3 from John Veness --- Similar to bug 453916. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 453916] Add default shortcuts for next/previous image (not arrows)
https://bugs.kde.org/show_bug.cgi?id=453916 John Veness changed: What|Removed |Added CC||john@pelago.org.uk -- You are receiving this mail because: You are watching all bug changes.
[KRdp] [Bug 488807] unable to connect using xfreerdp (X224_TPDU_CONNECTION_CONFIRM error)
https://bugs.kde.org/show_bug.cgi?id=488807 --- Comment #14 from John Kizer --- Created attachment 171594 --> https://bugs.kde.org/attachment.cgi?id=171594&action=edit Server-side logs for KRDP with an initially successful connection attempt from the Remmina Flatpak, then the connection freezing (client screen frozen, no input accepted) after a few minutes -- You are receiving this mail because: You are watching all bug changes.
[KRdp] [Bug 488807] unable to connect using xfreerdp (X224_TPDU_CONNECTION_CONFIRM error)
https://bugs.kde.org/show_bug.cgi?id=488807 --- Comment #13 from John Kizer --- Created attachment 171592 --> https://bugs.kde.org/attachment.cgi?id=171592&action=edit Server-side log from KRDC attempting to connect to KRDP on Fedora 40 Hope this is helpful, this is the server-side log from my attempt to use KRDC on a Fedora 40 device to connect to KRDP on another Fedora 40 device - mine appears to be a graphics issue though, and both are Nvidia devices using the RPMFusion-provided Nvidia drivers (555 series), so this may be a different issue? Should I log separately? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 452355] A notification asking to log-in to the network is displayed for every single network
https://bugs.kde.org/show_bug.cgi?id=452355 --- Comment #25 from John van Spaandonk --- (In reply to Nate Graham from comment #23) > Is this still reproducible in Plasma 6.1? I never had the problem anymore for at least one year. Suspect some relevant component updated. -- You are receiving this mail because: You are watching all bug changes.
[KRdp] [Bug 488807] unable to connect using xfreerdp (X224_TPDU_CONNECTION_CONFIRM error)
https://bugs.kde.org/show_bug.cgi?id=488807 John Kizer changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #7 from John Kizer --- Sorry if this is incorrect, I'm trying to set this to "Confirmed" so it's not auto-closed, since at least two folks have reported it? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 469144] Konsole zoom level (font size) should be remembered
https://bugs.kde.org/show_bug.cgi?id=469144 John Veness changed: What|Removed |Added Summary|Konsole zoom level should |Konsole zoom level (font |be remembered |size) should be remembered -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479246] systemsettings segmentation fault when applying change to GTK application theme
https://bugs.kde.org/show_bug.cgi?id=479246 --- Comment #1 from John Veness --- This seems to have been fixed recently (I'm currently running Plasma 6.1.2, but not sure exactly when it was fixed). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485378] Incorrect launch feedback for pinned apps in traditional Task Manager
https://bugs.kde.org/show_bug.cgi?id=485378 --- Comment #4 from John Veness --- This seems to have been fixed recently (I'm currently running Plasma 6.1.2, but not sure exactly when it was fixed). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 447245] Auto updates do not work
https://bugs.kde.org/show_bug.cgi?id=447245 --- Comment #17 from John --- BTW, i think the option to apply updates as soon as possible (e.g.: after 0min) is an important option! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 447245] Auto updates do not work
https://bugs.kde.org/show_bug.cgi?id=447245 --- Comment #16 from John --- I've been thinking about this... I think Plasma is misleading users if they set update settings to Apply System Updates: Immediately And it only does so "after 15 minutes of idle" (which may never occur!). When set to "Immediately" it should indeed apply them "Immediately" and not after XX Minutes of Idle. Having it "delayed" misleads the user. So either the idle time is removed or, ideally, a solution like Elias said: allowing user to set it manually (to, e.g.: 0min, 15min, 30 min) - where the 15min could be the default value... -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 489740] New: Krusader Handbook does not display content
https://bugs.kde.org/show_bug.cgi?id=489740 Bug ID: 489740 Summary: Krusader Handbook does not display content Classification: Applications Product: krusader Version: 2.8.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: usability Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: jkd...@zoho.com CC: krusader-bugs-n...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY The Menu 'Help' does not open the Krusader Help. It produces an error. The requested help file could not be parsed:/usr/share/doc/HTML/en//krusader/index.docbook STEPS TO REPRODUCE 1. Open Krusader 2. Click 'Help' menu. 3. Click on 'Krusader Handbook OBSERVED RESULT The requested help file could not be parsed:/usr/share/doc/HTML/en//krusader/index.docbook EXPECTED RESULT The Krusder Help (web or local file) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 (available in About System) KDE Plasma Version: 6.1 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 459277] use WPS (Wi-Fi Protected Setup) to easily connect to wifi connections
https://bugs.kde.org/show_bug.cgi?id=459277 John Veness changed: What|Removed |Added CC||john@pelago.org.uk -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481042] Directory with specific name can't be opened.
https://bugs.kde.org/show_bug.cgi?id=481042 John Veness changed: What|Removed |Added CC||john@pelago.org.uk --- Comment #3 from John Veness --- Likely a duplicate of 470031 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 489450] New: Add support for WIM files
https://bugs.kde.org/show_bug.cgi?id=489450 Bug ID: 489450 Summary: Add support for WIM files Classification: Applications Product: ark Version: 24.05.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plugins Assignee: elvis.angelac...@kde.org Reporter: john@pelago.org.uk CC: rthoms...@gmail.com Target Milestone: --- SUMMARY It would be great if Ark could open .wim files, as used for Windows installation images. STEPS TO REPRODUCE 1. Try to open a .wim archive in Ark OBSERVED RESULT Loading the archive ‘...boot.wim’ failed with the following error: No suitable plugin found. Ark does not seem to support this file type. EXPECTED RESULT The .wim file to be opened in Ark. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240628 KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.6-1-default (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION As I understand it, p7zip supports .wim files (indeed, "7z l boot.wim" shows a file listing). I have the 7z plugin activated in Ark. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488788] While in panel edit mode, opening Kickoff and closing it with the Esc key makes widget settings popup go below Panel Settings dialog
https://bugs.kde.org/show_bug.cgi?id=488788 John changed: What|Removed |Added CC||johnmaveric...@mail.com --- Comment #16 from John --- I'm on neon and i'm permanently facing the issue. by "permanently", i mean that i don't have to open kickoff everytime in edit mode to have this happening. The Pannel Setting always overlaps the widget options even after reboots. (i don't know if i ever opened kickoff while in edit mode, but it's possible that that i did it sometime) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 436928] Option to apply updates on shutdown, not startup
https://bugs.kde.org/show_bug.cgi?id=436928 --- Comment #16 from John --- I have opened a "dedicated" issue for this at: https://github.com/PackageKit/PackageKit/issues/770 Anyone aware if gnome has this working? (or if it's just for "regular" software - e.g.: just for non-critical software) this was brought up in the issue... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489179] New: Disabling logout confirmation screen doesn't work
https://bugs.kde.org/show_bug.cgi?id=489179 Bug ID: 489179 Summary: Disabling logout confirmation screen doesn't work Classification: Plasma Product: plasmashell Version: 6.1.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: jhtree...@gmail.com CC: natalie_clar...@yahoo.de Target Milestone: 1.0 SUMMARY Logging out from KDE/Plasma/Wayland using the desktop mouse right-click and selecting 'Leave...' or using ctrl-alt-del, always shows the logout confirmation screen (offering logout/cancel/shutdown etc options). I have unchecked the 'Logout Screen' option in the system settings. My '~/.config/ksmserverrc' file shows 'confirmLogout=false'. STEPS TO REPRODUCE 1. When logged in, right-click on the desktop background and select 'Leave...' 2. The logout confirmation window shows. 3. OBSERVED RESULT The logout confirmation window appears. Selecting logout from this does log out the user (as expected). EXPECTED RESULT No confirmation window should appear; the user should be logged straight out and returned to the SDDM login screen (I don't have auto-login upon logout enabled). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 40 (KDE/Plasma/Wayland) (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469706] Issues with actions for a non-mounted CD/DVD/BD in "Disks & Devices" applet (no eject, wrong icon, etc.)
https://bugs.kde.org/show_bug.cgi?id=469706 John Veness changed: What|Removed |Added Version|5.27.80 |6.1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469706] Issues with actions for a non-mounted CD/DVD/BD in "Disks & Devices" applet (no eject, wrong icon, etc.)
https://bugs.kde.org/show_bug.cgi?id=469706 John Veness changed: What|Removed |Added Summary|Cannot eject a non-mounted |Issues with actions for a |CD/DVD/BD via "Disks & |non-mounted CD/DVD/BD in |Devices" applet |"Disks & Devices" applet ||(no eject, wrong icon, ||etc.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469706] Cannot eject a non-mounted CD/DVD/BD via "Disks & Devices" applet
https://bugs.kde.org/show_bug.cgi?id=469706 John Veness changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469706] Cannot eject a non-mounted CD/DVD/BD via "Disks & Devices" applet
https://bugs.kde.org/show_bug.cgi?id=469706 John Veness changed: What|Removed |Added CC||john@pelago.org.uk --- Comment #2 from John Veness --- Created attachment 170959 --> https://bugs.kde.org/attachment.cgi?id=170959&action=edit Disks & Devices applet when audio CD is inserted, and action list expanded I've attached a screenshot showing the actions available for an (unmounted) audio CD, which shows: 1) No Eject action 2) Wrong icon (eject) used for "Open in File Manager" action 3) Almost-duplicate "Open with File Manager" action Operating System: openSUSE Tumbleweed 20240622 KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.5-1-default (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 489111] SkanPage doesn't always respect the default file format in which to save the files
https://bugs.kde.org/show_bug.cgi?id=489111 --- Comment #2 from John --- (In reply to Alexander Stippich from comment #1) > Git commit 661aa0c106bcee97f7164cc6394cbd56f5d1c44f by Alexander Stippich. > Committed on 24/06/2024 at 19:24. > Pushed by astippich into branch 'master'. > > fix configuration of default name filter Thank you! :) -- You are receiving this mail because: You are watching all bug changes.
[KRdp] [Bug 488807] unable to connect using xfreerdp (X224_TPDU_CONNECTION_CONFIRM error)
https://bugs.kde.org/show_bug.cgi?id=488807 --- Comment #3 from John Kizer --- If what I'm observing is with KRDC (mentioned by the original reporter as well) and Remmina as clients, should I create a new bug report since this one has been edited to be specific to xfreerdp? -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 489111] SkanPage doesn't always respect the default file format in which to save the files
https://bugs.kde.org/show_bug.cgi?id=489111 John changed: What|Removed |Added CC||johnmaveric...@mail.com -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 489111] New: SkanPage doesn't always respect the default file format in which to save the files
https://bugs.kde.org/show_bug.cgi?id=489111 Bug ID: 489111 Summary: SkanPage doesn't always respect the default file format in which to save the files Classification: Applications Product: Skanpage Version: 24.05.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: a.stipp...@gmx.net Reporter: johnmaveric...@mail.com Target Milestone: --- SUMMARY If the user changes the defaut file format in which skanpage should save files, it doesn't always respect the new default file format setting STEPS TO REPRODUCE 1. launch SkanPage 2. go to SkanPage Settings > Default File Format and set it to PNG 3. scan a page 4. go to "save all" and save the image 5. now hit the "delete all" button 6. scan the page again 7. go to "save all" again OBSERVED RESULT the file format pre-selected in not PNG anymore, but PDF!!! EXPECTED RESULT the file format should continue to be PNG SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 489108] Does not remember last window state
https://bugs.kde.org/show_bug.cgi?id=489108 John changed: What|Removed |Added CC||johnmaveric...@mail.com -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 489108] New: Does not remember last window state
https://bugs.kde.org/show_bug.cgi?id=489108 Bug ID: 489108 Summary: Does not remember last window state Classification: Applications Product: Skanpage Version: 24.05.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: a.stipp...@gmx.net Reporter: johnmaveric...@mail.com Target Milestone: --- SUMMARY Skanpage does not remember last used window state STEPS TO REPRODUCE 1. launch skanpage (it starts not-maximized!) 2. maximize the window 3. close skanpage 4. relaunch skanpage OBSERVED RESULT window is not maximized EXPECTED RESULT skanpage should remember last window state SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381326] recognize re-convergent fanout before complaining about Uninitialized
https://bugs.kde.org/show_bug.cgi?id=381326 --- Comment #11 from John Reiser --- This comment is to confirm that the bug still exists today 2024-06-24, 7 years after original filing. Actually there are two bugs: 1) In the True branch after a test for Equality (==) then the Defined bits propagate in both directions. Some bits which previously were Uninit may become dynamically Defined because they are equal to a Defined bit in the other operand. Thus dynamic Equality is NOT necessarily a Read-Only operation with respect to the Defined bits for each operand. (Of course if all input bits in both operands are Defined then there is no issue, and no accounting bits change.) 2) When control-flow paths converge at run time, then the Defined bits after the Join become equal to the AND of the corresponding Defined bits for each variable along any path that enters the Join. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488669] Notification window no longer automatically closes when 'No unread notifications'
https://bugs.kde.org/show_bug.cgi?id=488669 --- Comment #2 from John Horne --- Fedora 40 now has Plasma 6.1 packages available. Running an update, and reboot, the notifications window now closes when there are no unread notifications left. This bug report can be closed. Thanks for your help. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488719] Not able to screenshare, due to screensharing popup being blank
https://bugs.kde.org/show_bug.cgi?id=488719 John Schroeder changed: What|Removed |Added CC||jschr...@gmail.com --- Comment #35 from John Schroeder --- As a work around, downgrading xdg-desktop-portal from 1.14.4 to 1.14.3 made screen sharing work again for me. I was able to get the old 1.14.3 package from Ubuntu packages: https://packages.ubuntu.com/jammy/xdg-desktop-portal. -- You are receiving this mail because: You are watching all bug changes.
[KRdp] [Bug 488807] unable to connect
https://bugs.kde.org/show_bug.cgi?id=488807 John Kizer changed: What|Removed |Added CC||john.ki...@proton.me --- Comment #1 from John Kizer --- I'm also seeing the same thing, trying to connect from one Fedora 40 machine to another Fedora 40 installation, both on Plasma 6.1. The System Settings option didn't appear until I manually installed krdp, so I'm not sure if there might be some other package that needs installed still? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 204709] find: whole words only
https://bugs.kde.org/show_bug.cgi?id=204709 John Veness changed: What|Removed |Added Platform|openSUSE|unspecified CC||john@pelago.org.uk -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 488741] Share by E-mail not working
https://bugs.kde.org/show_bug.cgi?id=488741 John changed: What|Removed |Added CC||johnmaveric...@mail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 488741] New: Share by E-mail not working
https://bugs.kde.org/show_bug.cgi?id=488741 Bug ID: 488741 Summary: Share by E-mail not working Classification: Applications Product: okular Version: 23.08.1 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: johnmaveric...@mail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY On windows 10, with Thunderbird set as default e-mail software and after adding the "Share" button to the Okular toolbar If one tries to share the opened PDF document by E-mail - by pressing the share button - it won't open Thunderbird with the document attached on a new message, as expected STEPS TO REPRODUCE 1. Install Thunderbird and set it as default E-mail Client on Windows (and configure it as you see fit) 2. Go to Windows Store and install Okular 3. Add the Share button to the Okular toolbar 4. Open a PDF Document with Okular and press the Share button OBSERVED RESULT Nothing happens! EXPECTED RESULT it should automatically open and create a new e-mail message on Thunderbird, with the document attached, and ready to be filled with the sender's data SOFTWARE/OS VERSIONS Windows: 10 (latest update) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488669] New: Notification window no longer automatically closes when 'No unread notifications'
https://bugs.kde.org/show_bug.cgi?id=488669 Bug ID: 488669 Summary: Notification window no longer automatically closes when 'No unread notifications' Classification: Plasma Product: plasmashell Version: 6.0.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: jhtree...@gmail.com CC: k...@privat.broulik.de Target Milestone: 1.0 SUMMARY In Fedora 39/Plasma5 when all notifications had been read, the notification window from the panel automatically closed. Upgrading to Fedora 40/Plasma6 the notification window remains present and shows 'No unread notifications'. clicking on some other window (konsole, firefox etc) then causes the notification window to disappear. STEPS TO REPRODUCE 1. Run 'konsole', then I configured konsole (from the 'Settings' tab at the top of the konsole window) to show popup notifications for 'Bell in Focused Session'. 2. Use keyboard down-arrow key to go to bottom of konsole, and repeat a couple of times to get multiple popups. 3. On panel the Notifications icon should have appeared (indicating there are unread notifications. Close each notification using the 'Close' icon. After the last one is closed the Notification window remains saying 'No unread notifications' until the mouse is clicked elsewhere. OBSERVED RESULT See summary above. EXPECTED RESULT The notification window should automatically disappear as it did under Plasma 5. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 40 (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Looks like similar to closed bug report for Plasma 5 #435194 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 488612] Okular not launching
https://bugs.kde.org/show_bug.cgi?id=488612 --- Comment #2 from John Kagunda --- @K(In reply to Kevin Ottens from comment #1) > Tried to reproduce it but didn't manage to. I'm not sure how you could have > ended in a disconnected state like this. > > Running this should fix it though: > snap connect okular:kf6-core22 kf6-core22:kf6-core22-slot Yea it has fixed the issue thanks -- You are receiving this mail because: You are watching all bug changes.
[Books] [Bug 488612] New: Okular books not launching
https://bugs.kde.org/show_bug.cgi?id=488612 Bug ID: 488612 Summary: Okular books not launching Classification: Applications Product: Books Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Frameworks Cookbook Assignee: kde-doc-engl...@kde.org Reporter: rafaelj...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Okular Books is not working. >From June 16 2024 I have tried to launch several pdfs using okular books but its not working. I have tried to launch it from the terminal using ``` okular ./my.pdf ``` and I get this error ``` ERROR: not connected to the kf6-core22 content interface. ``` STEPS TO REPRODUCE 1. Try to open Okular OBSERVED RESULT Product does not launch EXPECTED RESULT Product should launch 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.
[valgrind] [Bug 487862] memcheck does not believe that bytes on new pages are Defined by brk() system call
https://bugs.kde.org/show_bug.cgi?id=487862
--- Comment #8 from John Reiser ---
(In reply to Mark Wielaard from comment #6)
> BTW it seems this whole discussion is duplicated in the comments of
> memcheck/mc_main.c mc_post_clo_init ()
>// - The current inaccuracy has caused maybe one complaint in seven
> years(?)
>// - Relying on the zeroed-ness of whole brk'd pages is pretty grotty... I
>// doubt most programmers know the above information.
>// So I'm not terribly unhappy with marking it as undefined. --njn.
>
> Which was written in 2009. So maybe times have changed since then. But I
> don't really remember any false positive report about this.
What has changed is very large apps such as qemu-user-* which depend on
dozens of "random" libraries, and the system
builders/maintainers/administrators
who tired of their own version of "dll hell" due to dependency tracking,
and the users (including "systematic" users with scripts) who got tired of
multi-second initialization of all those shared libraries; all gained new
appreciation
for -static builds of ET_EXEC (no shared libraries at all!) which initialize
in a flash
and have robust configuration (none!) for end users. Disk space is cheap for
many
such users; time is not. qemu-user has grown into a predictable evolution which
avoids nearly all "security" incidents which otherwise might argue for using
shared libraries.
But then "corner case" users of qemu-user-* (etc), the users who just might
find a bug or two,
discover that memcheck is much less useful. Gdb and debuginfo have no trouble
identifying malloc/free/sbrk+sys_brk etc., but memcheck does not recognize
them.
Re-building the app from source (and avoiding -static+ET_EXEC) takes hours of
time
and almost 10 GB of disk space, uses 4 different build systems (make, cmake,
meson, ninja)
and two runtime support systems (Go-lang and C-lang).
Being highly motivated for the particular case of qemu-mips*-static, I have
developed
binary patches that zero the new region of {_dl_early_allocate, malloc} +
{expanding sbrk/sys_brk}.
This is not as good as proper memcheck accounting, but it suits my purpose
of finding uninit local variables in what would otherwise be a blizzard of
Uninit complaints
caused by memcheck not recognizing when to mark bytes from sys_brk as Defined.
Without the patches, memcheck finds
==375110== ERROR SUMMARY: 9646 errors from 125 contexts (suppressed: 0 from
0)
before the process aborts with
==375110== Warning: ignored attempt to set SIGRT32 handler in sigaction();
==375110== the SIGRT32 signal is used internally by Valgrind
fatal error: sigaction failed [from Go-lang]
Memcheck should find some way to avoid relying on SIGRT32, perhaps using
pipefs.
The histogram of memcheck Uninit complaints (before patching) begins:
108 ==375110==at 0x64E006: _dl_early_allocate (in
/usr/bin/qemu-mipsel-static)
16 ==375110==at 0x63B5AB: brk (in /usr/bin/qemu-mipsel-static)
15 ==375110==at 0x5FDC36: __pthread_enable_asynccancel (in
/usr/bin/qemu-mipsel-static)
15 ==375110==at 0x5FDC2B: __pthread_enable_asynccancel (in
/usr/bin/qemu-mipsel-static)
14 ==375110==at 0x5FDCB9: __pthread_disable_asynccancel (in
/usr/bin/qemu-mipsel-static)
14 ==375110==at 0x5FDCB1: __pthread_disable_asynccancel (in
/usr/bin/qemu-mipsel-static)
14 ==375110==at 0x5FDC87: __pthread_disable_asynccancel (in
/usr/bin/qemu-mipsel-static)
10 ==375110==at 0x61BA21: __strcmp_avx2 (in
/usr/bin/qemu-mipsel-static)
5 ==375110==at 0x4E6CE6: mmap_unlock (mmap.c:39)
5 ==375110==at 0x4E6A7F: mmap_lock (mmap.c:32)
3 ==375110==at 0x606D85: _int_free (in /usr/bin/qemu-mipsel-static)
So far there is one uninit local:
==375110== Uninitialised value was created by a stack allocation
==375110==at 0x4808D0: process_string_cmd.constprop.0 (gdbstub.c:1368)
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 487862] memcheck does not believe that bytes on new pages are Defined by brk() system call
https://bugs.kde.org/show_bug.cgi?id=487862 --- Comment #5 from John Reiser --- (In reply to Mark Wielaard from comment #4) > So it seems reasonable for memcheck to assume the area exposed by brk() is > undefined. That assumption is incorrect for new pages on Linux, and there are applications that rely on the actual behavior, which is that on new pages all bytes are zero. For instance: qemu relies on this to hold data that tracks threads. > But if the pages already existed and brk() just gives them back those > aren't guaranteed to be all-zero but can contain whatever was there before. On Linux this is only partially true. If __cur_brk (the top of the sys_brk() region) varies within the same page, then the bytes retain their values. If __cur_brk decreases enough so that one or more whole pages are not contained in the allocated address space, then those pages are removed from the address space, and a subsequent sys_brk() which increases __cur_brk to include such addresses does assign new pages, and they are guaranteed to be zero. If an increasing sys_brk() would overlap with a different VMA (Linux-internal Virtual Memory Area) that already is assigned for some other purpose, then that sys_brk() fails and returns an error value. So for any successful sys_brk(), then new pages are guaranteed to be zero. Memcheck certainly knows which pages are new, and should mark then as Defined. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487862] memcheck does not believe that bytes on new pages are Defined by brk() system call
https://bugs.kde.org/show_bug.cgi?id=487862 --- Comment #2 from John Reiser --- (In reply to Paul Floyd from comment #1) > brk() is fairly old, removed from posix accordingly to the Linux manpage. > Increasingly I see it getting removed from platforms. In this case "old" means good, well-documented, well-debugged, reliable. Please name explicitly some platforms which are removing brk(), and their typical usage environments. The brk() system call has been present in most *nix-like systems since 1970, which is more than 50 years. brk() is present in Linux today, and Linux has a strong policy and implementation record for backwards compatibility of system calls; brk() will not disappear from Linux anytime soon. brk() is particularly useful during process startup when a call to malloc() might not yet be supported;. A programming language runtime can use brk() via an inline system call. See _dl_early_allocate() in glibc, for example. brk() and sbrk() enable an easy implementation of mark() and release() for Pascal run-time support. brk() is quite handy for use by other in-process emulators, which must deal with arbitrary mmap() anyway. For instance, qemu relies on brk() and sbrk(). brk() is multi-thread safe and async-signal safe without requiring any user-mode locks. It can be used safely in a signal handler. Thread managers may rely on brk() regardless of the implementation of malloc(). -- You are receiving this mail because: You are watching all bug changes.
