[neon] [Bug 487085] Krusader fails to open embedded konsole terminal
https://bugs.kde.org/show_bug.cgi?id=487085 --- Comment #2 from Bob Borges --- Also an issue after the latest Manjaro/kde update. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 487085] Krusader fails to open embedded konsole terminal
https://bugs.kde.org/show_bug.cgi?id=487085 Bob Borges changed: What|Removed |Added CC||robert.d.bor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485622] Discover's context menu entry "update" does nothing.
https://bugs.kde.org/show_bug.cgi?id=485622 --- Comment #4 from Bob Miller --- Ditto for Discover. Type "sudo plasma-discover" in a terminal window, enter password, and Discover will run as before. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485622] Discover's context menu entry "update" does nothing.
https://bugs.kde.org/show_bug.cgi?id=485622 --- Comment #3 from Bob Miller --- One more item. If I click on the systemsettings button the normal icons appear, but again anything requiring authentication does not work. If i type: sudo systemsettings from a terminal, then all additions/changes/deletions can be effected. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485622] Discover's context menu entry "update" does nothing.
https://bugs.kde.org/show_bug.cgi?id=485622 Bob Miller changed: What|Removed |Added CC||rmiller...@gmail.com --- Comment #2 from Bob Miller --- This is a HUGE problem that needs to be fixed. I don't know if the problem is Ubuntu or KDE but the admin setting in a user's profile is no longer working. If have 3 systems running 22.04 LTS. In all of them, the request for authentication while running as an admin user has disappeared. Example: Discover The program retrieves the Updates Hit Update button Nothing happens It used to be that the authentication window would appear, type in password, and proceed This lack of asking for authentication is also in making changes to users, network address -- anything that used to trigger an authentication request. The bug has been present for months. I'm sure it's been logged somewhere else. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 485213] Rollovers appear black on black background
https://bugs.kde.org/show_bug.cgi?id=485213 Bob Leslie changed: What|Removed |Added CC||k...@bobleslie.com.au -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 485213] New: Rollovers appear black on black background
https://bugs.kde.org/show_bug.cgi?id=485213 Bug ID: 485213 Summary: Rollovers appear black on black background Classification: Applications Product: kate Version: 21.12.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: k...@bobleslie.com.au Target Milestone: --- Created attachment 168271 --> https://bugs.kde.org/attachment.cgi?id=168271=edit Screenshot 08-04-2024 *** 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 STEPS TO REPRODUCE 1. Installed Kate after new install of Ubuntu 22.04 Mate 2. Run Kate and bring up Search and Replace 3. All rollovers in Search and Replace area come up black on black OBSERVED RESULT Text not visible EXPECTED RESULT Text visible 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.
[kdenlive] [Bug 483777] Enabling Proxies Corrupts Timeline
https://bugs.kde.org/show_bug.cgi?id=483777 --- Comment #8 from Bob Wetzelheimer --- To double check, I re-installed 24.02.0 and it doesn't crash on startup -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 483777] Enabling Proxies Corrupts Timeline
https://bugs.kde.org/show_bug.cgi?id=483777 --- Comment #7 from Bob Wetzelheimer --- However (and if you want me to open a new bug, let me know), I'm getting a crash every time I try and open any project file from Explorer. If I open them via File -> Open, they load fine. I uploaded a new video showing the issue to that folder I linked "opening_bug.mkv" -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 483777] Enabling Proxies Corrupts Timeline
https://bugs.kde.org/show_bug.cgi?id=483777 --- Comment #6 from Bob Wetzelheimer --- Thanks for the quick fix! I messed around with it for a bit and couldn't reproduce the issue with build 7748 / 2024-03-25 01:21 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 483777] Enabling Proxies Corrupts Timeline
https://bugs.kde.org/show_bug.cgi?id=483777 --- Comment #1 from Bob Wetzelheimer --- I've been playing around with it and I can't reproduce it in 23.08.5 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 483777] Enabling Proxies Corrupts Timeline
https://bugs.kde.org/show_bug.cgi?id=483777 Bob Wetzelheimer changed: What|Removed |Added Component|Effects & Transitions |Video Display & Export -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 483777] New: Enabling Proxies Corrupts Timeline
https://bugs.kde.org/show_bug.cgi?id=483777 Bug ID: 483777 Summary: Enabling Proxies Corrupts Timeline Classification: Applications Product: kdenlive Version: 24.02.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: here_you_go_...@outlook.com Target Milestone: --- SUMMARY When enabling proxies and saving again, the timing of edits I've made is lost, audio and video is desynchronized. It seems like it restarts subsequent cuts from the beginning sometimes. I can reproduce this using `big_buck_bunny_1080p_h264.mov`. STEPS TO REPRODUCE 1. Add a clip to project 2. Cut it up using the razor and adjust the in and out timing by grabbing the edges of the clip 2. Save and exit 3. Open again. Loads correctly 4. Enable proxies for video clips 5. Save 6. Open. Timeline has been messed up, edits are lost, audio and video are de-synchronized Sometimes after enabling proxies and before saving I have to make further changes to the project to get the corruption to occur. OBSERVED RESULT Edits to project are corrupted and lost EXPECTED RESULT Saving and opening a file should not change edits and timings FILES https://drive.google.com/drive/folders/1pWx7BG11qbjqFyKGocLsohcr7WYtrEcc?usp=sharing - Screen recording reproducing issue - Screenshots of timeline before/after (https://imgur.com/a/pMiR1L4) - Project files before/after SOFTWARE/OS VERSIONS Edition Windows 10 Pro Version 22H2 Installed on11/2/2020 OS build19045.4170 Experience Windows Feature Experience Pack 1000.19054.1000.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443721] Keyboard repeat speed is ignored under wayland
https://bugs.kde.org/show_bug.cgi?id=443721 Bob Igo changed: What|Removed |Added CC||b...@igo.name -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 480220] KDE Connect Daemon Crashes whenever phone screen is turned on
https://bugs.kde.org/show_bug.cgi?id=480220 Mr. Bob changed: What|Removed |Added CC||robertbrooks...@email.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473083] Appimage has no title-bar under Wayland: add Qt plugin wayland-decoration-client.
https://bugs.kde.org/show_bug.cgi?id=473083 --- Comment #10 from Bob --- Inconclusive, that one doesn't even want to start on Ubuntu (23.10) I'm afraid: ``` ./digikam-master-381-linux-gcc-x86_64.AppImage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. -- Detected host Linux ubuntu-64-23.10 -- AppImage mounted directory: /tmp/.mount_digikaHnSI0k Check library libudev.so.0 Check library libxcb-dri3.so.0 Check library libcrypto.so.1.1 Check library libssl.so.1.1 Check library libnss3.so Check library libnssutil3.so Check library libsmime3.so Check library libpango-1.0.so.0 Check library libpangocairo-1.0.so.0 Check library libgmodule-2.0.so.0 -- Preloading shared libs: :/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/libnss3.so:/usr/lib/x86_64-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux-gnu/libsmime3.so:/usr/lib/x86_64-linux-gnu/libpango-1.0.so.0:/usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0:/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 digikam: symbol lookup error: /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0: undefined symbol: g_string_free_and_steal Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. QSocketNotifier: Can only be used with threads started with QThread /tmp/.mount_digikaHnSI0k/AppRun.wrapped: symbol lookup error: /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_proxy_marshal_flags ``` -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473083] Appimage has no title-bar under Wayland: add Qt plugin wayland-decoration-client.
https://bugs.kde.org/show_bug.cgi?id=473083 --- Comment #8 from Bob --- I've just tried the linked 8.2 appimage, it still launches without a titlebar I'm afraid. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 388935] Unable to import investment account transaction with .csv
https://bugs.kde.org/show_bug.cgi?id=388935 b...@mroczka.com changed: What|Removed |Added CC||b...@mroczka.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474714] Folder panel arrows missing and cannot be expanded on some, not all folders containing sub-folders
https://bugs.kde.org/show_bug.cgi?id=474714 --- Comment #7 from Bob English --- (In reply to Tobias Fella from comment #6) > > *** This bug has been marked as a duplicate of bug 474713 *** Antonio Rojas said it was a duplicate of Bug 47413: Document structure listview needs RMB I clicked on the link to find it. Now you changed it to a duplicate of my own original report: Bug 474713: Folder panel arrows missing and cannot be expanded on some, not all folders containing sub-folders So just delete this one that is literally just a single digit higher (from 474713 to 474714), and all of the duplicate stuff altogether: Both of you and this system are just confuse things! So my original bug report is valid then? Because If I filed it twice, then theres something wrong with this system -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474714] Folder panel arrows missing and cannot be expanded on some, not all folders containing sub-folders
https://bugs.kde.org/show_bug.cgi?id=474714 Bob English changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #5 from Bob English --- I filed this Bug 47414: "Folder panel arrows missing and cannot be expanded on some, not all folders containing sub-folders" Reported: 2023-09-20 02:14 UTC by Bob English Product: Dolphin Component: panels: folders Version: 23.08.01 bug 417413 is not me at all! It's marked: "Document structure listview needs RMB" Reported: 2002-09-04 10:03 UTC by Andrey Cherepanov Product: Kword Component: general Version: unspecified I filed yesterday because the problem just showed up in the last two weeks, Andrey a whole year ago! If the info in the header isn't different enough, which they are, then the description of the problem sure is! They are completely different problems, in completely different programs; A document editor vs a file manager! I don't even use Kword, and never have. Please read the whole thing! I think you need a vacation Antonio! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474714] Folder panel arrows missing and cannot be expanded on some, not all folders containing sub-folders
https://bugs.kde.org/show_bug.cgi?id=474714 Bob English changed: What|Removed |Added Resolution|DUPLICATE |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #3 from Bob English --- This is completely unrelated to bug 474713! This is about Dolphin's folder panel, not Kwrites document structure! -- You are receiving this mail because: You are watching all bug changes.
[kword] [Bug 47413] Document structure listview needs RMB
https://bugs.kde.org/show_bug.cgi?id=47413 --- Comment #7 from Bob English --- (In reply to Antonio Rojas from comment #6) > *** Bug 474714 has been marked as a duplicate of this bug. *** This cannot be true! The bug I filed yesterday is with DOLPHIN's folder panel, not Kwrite's doccument structure! Please read it again, or actually read the whole thing! You marked my completely different bug as duplicate of this one: They are not at all related! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474714] New: Folder panel arrows missing and cannot be expanded on some, not all folders containing sub-folders
https://bugs.kde.org/show_bug.cgi?id=474714 Bug ID: 474714 Summary: Folder panel arrows missing and cannot be expanded on some, not all folders containing sub-folders Classification: Applications Product: dolphin Version: 23.08.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: bobofengl...@zoho.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** In the folder Panel (Folders), some folders that do contain sub-ofolders do not have a visible arrow, nor does clicking on where it should be expand the folder, and then show the sub folders as it did until very recently (~ A week or two). *** Example: my home folder (no others investigated yet), whether hidden or shown. 48 folders in total, 23hidden (with Dot), and 25 not hidden. View = hidden on or off, mode: Icons, "Limit to home directory" = deselected; some of the ones without arrows have only symlinks to other folders in them, some are mixed, and some (most) do not. No hidden files with sub folders are missing the arrow, and the fist one missing the arrow is # 33 but stands alone, then they are OK again, and then from #43 on up they all have no arrows. STEPS TO REPRODUCE 1. open Dolphin and look. OBSERVED RESULT Some working folder expansion arrows are missing. EXPECTED RESULT All folders with sub-folders should have visible and functioning tree expansion arrows., SOFTWARE/OS VERSIONS: Arch Linux/KDE Plasma. KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION I am dead tired now, but will investigate commonalities/differences... anything I can notice that may be the culprit. Sorry, I can't help on the programming end, as it's beyond me. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474713] New: Folder panel arrows missing and cannot be expanded on some, not all folders containing sub-folders
https://bugs.kde.org/show_bug.cgi?id=474713 Bug ID: 474713 Summary: Folder panel arrows missing and cannot be expanded on some, not all folders containing sub-folders Classification: Applications Product: dolphin Version: 23.08.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: bobofengl...@zoho.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** In the folder Panel (Folders) some folders that do contain sub0folders do not have a visible arrow, nor does clicking on where it should be expand the folder, and then show the sub folders as it did until very recently (~ A week or two). *** Example: my home folder (no others investigated yet), hidden shown, 48 folders in total, 23hidden (with Dot), and 25 not hidden. View = hidden on or off, mode: Icons, "Limit to home directory" = deselected; some of the ones without arrows have only symlinks to other folders in them, some are mixed, and some (most) do not. No hidden files with sub folders are missing the arrow, and the fist one missing the arrow is # 33 but stands alone, then they are OK again, and then from #43 on up they all have no arrows. STEPS TO REPRODUCE 1. open Dolphin and look. OBSERVED RESULT Some folder expansion arrows are missing. EXPECTED RESULT Folders with sub-folders should have visible and functioning tree expansion arrows., SOFTWARE/OS VERSIONS: Arch Linux/KDE Plasma. KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION I am dead tired now, but will investigate commonalities/differences... anything I can notice that may be the culprit. Sorry, I can't help on the programming end, as it's beyond me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465937] Split does not reset to its original value once "adjacent quick-tiled windows" configuration ceases to exist
https://bugs.kde.org/show_bug.cgi?id=465937 Bob Borges changed: What|Removed |Added CC||robert.d.bor...@gmail.com --- Comment #24 from Bob Borges --- +1 for the general complaints. Please implement possibility to: - disable automatic resize of two adjacent quick-tiled windows - disable automatic resize of quick tiled windows on all virtual desktops I'm a recent KDE user, and generally love it, but this behavior alone has me considering changing DE/WM again after just a couple months. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473083] Appimage has no title-bar under Wayland: add Qt plugin wayland-decoration-client.
https://bugs.kde.org/show_bug.cgi?id=473083 --- Comment #6 from Bob --- Yes I'm using Gnome on Wayland. That does sound like it might be the issue. I was aware there are some differences in the way Window decorations are handled under Wayland but didn't know the details, thanks for the explanation. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473083] Appimage has no titlebar under Wayland
https://bugs.kde.org/show_bug.cgi?id=473083 --- Comment #4 from Bob --- It's a good thought and the same occurred to me, but having tried all the shortcut combinations I could think of and resetting the Digikam config files, I haven't been able to find any setting that's hiding the titlebar. I installed KDE system settings to see if there was anything there, but the dialogue is all but empty as I have no KDE components installed. Also, I have since concluded that it couldn't be this: 1. I've never had KDE/Plasma installed on this system. 2. The app has a titlebar when launched with QT_QPA_PLATFORM=xcb I think (2) strongly suggests that this isn't a misconfiguration on my system. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 348104] Remove all tags from selected image(s)
https://bugs.kde.org/show_bug.cgi?id=348104 --- Comment #7 from Bob --- Nevermind, I hadn't checked the code thoroughly enough, found it! Thanks :-) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 348104] Remove all tags from selected image(s)
https://bugs.kde.org/show_bug.cgi?id=348104 Bob changed: What|Removed |Added CC||arkon...@yahoo.com --- Comment #6 from Bob --- Is there any way to call this new function in the app? I am running the 8.1.0 appimage but haven't been able to find one yet. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473083] Appimage has no titlebar under Wayland
https://bugs.kde.org/show_bug.cgi?id=473083 --- Comment #2 from Bob --- Thanks for the response. I am running a Wayland session. I am running other appimages without issue: BambuStudio_ubuntu-v01.07.02.51-20230804223010.AppImage kdenlive-23.04.3-x86_64.AppImage UltiMaker-Cura-5.4.0-linux-modern.AppImage Bob -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473083] New: Appimage has no titlebar under Wayland
https://bugs.kde.org/show_bug.cgi?id=473083 Bug ID: 473083 Summary: Appimage has no titlebar under Wayland Classification: Applications Product: digikam Version: 8.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Portability-Interroperability Assignee: digikam-bugs-n...@kde.org Reporter: arkon...@yahoo.com Target Milestone: --- SUMMARY *** The 8.1.0 appimage has no titlebar under Wayland. *** STEPS TO REPRODUCE 1. I tried launching with: QT_QPA_PLATFORM=wayland ./Applications/digiKam-8.1.0-x86-64.appimage In the log output I see the messages 'unknown: EGL not available' and 'unknown: Unhandled container to remove : Digikam::DigikamApp' 2. I then tried launching with: QT_QPA_PLATFORM=wayland-egl ./Applications/digiKam-8.1.0-x86-64.appimage Digikam failed to launch. 3. I then tried: QT_QPA_PLATFORM=xcb ./Applications/digiKam-8.1.0-x86-64.appimage Digikam launched normally, with a titlebar. OBSERVED RESULT When run without amendment the appimage creates a window without a titlebar. EXPECTED RESULT The appimage should run without modification under Wayland and create a window with a titlebar. SOFTWARE/OS VERSIONS Ubuntu 23.04 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468639] Compiling 8.0.0 stop on 'make install'.
https://bugs.kde.org/show_bug.cgi?id=468639 --- Comment #6 from Bob Billson --- (In reply to caulier.gilles from comment #5) > In fact it breaks in unit-test rules. I don't know why. You don't needs > unit-test in your build. Just disable it to append this configure option > with cmake: > > -DBUILD_TESTING=OFF > > recompile all after configure and try make install. After a clean recompile, make install work without any errors. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 468969] New: Implement STOP Command in Plate Solve when Camera is Busy
https://bugs.kde.org/show_bug.cgi?id=468969 Bug ID: 468969 Summary: Implement STOP Command in Plate Solve when Camera is Busy Classification: Applications Product: kstars Version: 3.6.4 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: rmiller...@gmail.com Target Milestone: --- SUMMARY *** 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. 2. 3. OBSERVED RESULT When a Plate Solve is initiated, and the system detects the camera as busy, the Plate Solve routine goes into a series of waits at 10 sec, 20 sec, 40 sec, etc etc waiting for the camera to become unbusy. Often times (more like usually) the camera is not busy. The system thinks the camera is busy, but there is no apparent indication to the user. The problem is that, when the Plate Solver starts these delays as the user searches for why the system thinks the camera is busy, the STOP button is grayed out! Sometimes the only solution is to quit the session, then restart. The simple solution would seem to be to let the user STOP the process as soon as the Plate Solve routine says the camera is busy so the user can find where the system thinks the camera is busy before the Ekos embarks on a long wait sequence. One example of where the system thinks the camera is busy when it is not is the Focus module. If the camera is doing loop capture and the STOP button is hit in the Focus module, the Plate Solve module will always say the camera is busy. After hitting STOP when doing Focus looping, run the camera once in a Single Shot mode. That usually clears the conflict. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447593] segfault when moving large number of photos between albums
https://bugs.kde.org/show_bug.cgi?id=447593 --- Comment #5 from Bob Billson --- (In reply to caulier.gilles from comment #4) > @Bob > > digiKam 8.0.0 is out. Problem still reproducible ? > > Best regards > Gilles Caulier No the problem cannot be reproduced on 8.0.0. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468639] Compiling 8.0.0 stop on 'make install'.
https://bugs.kde.org/show_bug.cgi?id=468639 --- Comment #4 from Bob Billson --- (In reply to caulier.gilles from comment #3) > I just tried here with current code from git master (next 8.1.0), and > problem is not reproducible. "sudo make install" work as expected, i'm use > Kubuntu 22.04. > > Tip : clean your "build" directory, recompile all and try again. > > Gilles Caulier I cleaned my "build" directory and recompiled. Same error with "sudo make install". -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468639] Compiling 8.0.0 stop on 'make install'.
https://bugs.kde.org/show_bug.cgi?id=468639 --- Comment #2 from Bob Billson --- (In reply to caulier.gilles from comment #1) > her i use "make install/fast" and it works... "make install/fast" also worked for me -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468639] New: compiling 8.0.0 crashes on 'make install'
https://bugs.kde.org/show_bug.cgi?id=468639 Bug ID: 468639 Summary: compiling 8.0.0 crashes on 'make install' Classification: Applications Product: digikam Version: 8.0.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: r...@nodot.org Target Milestone: --- SUMMARY *** Compiling 8.0.0 from source doing 'sudo make install' crashes with error complaining test-data directory already exists and is not empty. *** STEPS TO REPRODUCE 1. cmake -DCMAKE_BUILD_TYPE=release -DCMAKE_INSTALL_PREFIX=/usr/local . 2. make -j`nproc` 3. sudo make install OBSERVED RESULT reb@grue:~/src/digikam/digikam-8.0.0$ sudo make install [sudo] password for reb: [ 0%] Generating mo... [ 0%] Built target pofiles-651a6d3373c8feb286ebdb52b95b3370 [ 0%] Generating ts... [ 0%] Built target tsfiles-651a6d3373c8feb286ebdb52b95b3370 make[2]: Circular CMakeFiles/test-data <- test-data dependency dropped. make[2]: Circular test-data <- test-data dependency dropped. [ 0%] Checkout unit-test data repository. Please wait... fatal: destination path '/home/reb/src/digikam/digikam-8.0.0/test-data' already exists and is not an empty directory. make[2]: *** [CMakeFiles/test-data.dir/build.make:73: test-data] Error 128 make[1]: *** [CMakeFiles/Makefile2:7123: CMakeFiles/test-data.dir/all] Error 2 make: *** [Makefile:146: all] Error 2 SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.11-grue (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-6500U CPU @ 2.50GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: Purism Product Name: Librem 15 v3 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468264] feature request: resource bundle deletion and user feedback
https://bugs.kde.org/show_bug.cgi?id=468264 --- Comment #1 from Bob Ross --- > 2. I don't find a button to delete a complete bundle. It could be handy, > after selecting a bundle using the 'local resources' combobox, to have a > button 'delete complete bundle' to remove it completely. Maybe it's better to add a 'delete bundle' button in the 'manage resource libraries' window, next to the activate/deactivate button. In this way activating and deleting bundles is all in the same place -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468310] New: open resources folder button not working
https://bugs.kde.org/show_bug.cgi?id=468310 Bug ID: 468310 Summary: open resources folder button not working Classification: Applications Product: krita Version: 5.1.5 Platform: Android OS: Android 12.x Status: REPORTED Severity: normal Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: bobrosspaint...@protonmail.com Target Milestone: --- SUMMARY The 'open resources folder' button is not working. STEPS TO REPRODUCE 1. Go to 'settings' - 'manage resources' 2. The 'open resources folder' button is not working OBSERVED RESULT open resources folder button not working EXPECTED RESULT open resources folder button should work Remember: there are no bugs, only happy little accidents! Bob Ross The joy of painting -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468297] workspace isn't overwritten when using same name
https://bugs.kde.org/show_bug.cgi?id=468297 Bob Ross changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Bob Ross --- This bug can be closed, because I did something wrong. It's working fine. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468297] New: workspace isn't overwritten when using same name
https://bugs.kde.org/show_bug.cgi?id=468297 Bug ID: 468297 Summary: workspace isn't overwritten when using same name Classification: Applications Product: krita Version: 5.1.5 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: bobrosspaint...@protonmail.com Target Milestone: --- Hello friends, SUMMARY When saving a workspace using the same name as a previously created workspace, Krita asks if you want to overwrite the workspace, but this doesn't seem to happen. After loading the overwritten workspace, it's still the old one. STEPS TO REPRODUCE 1. Create a workspace, give it a name "test" 2. Change the workspace, overwrite it using same name "test" 3. Load the workspace and see nothing has changed (it's not overwritten) OBSERVED RESULT The workspace is not overwritten when using the same name EXPECTED RESULT The workspace should be overwritten when using the same name Remember: we don't make bugs, only happy little accidents! Bob Ross The joy of painting -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468264] New: feature request: resource bundle deletion and user feedback
https://bugs.kde.org/show_bug.cgi?id=468264 Bug ID: 468264 Summary: feature request: resource bundle deletion and user feedback Classification: Applications Product: krita Version: 5.1.5 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: bobrosspaint...@protonmail.com Target Milestone: --- Hello friends SUMMARY In 'settings' - 'manage resources': there is a button 'import resources' to install a bundle. I like to request 2 things to make this window better for the user. 1. When a bundle is installed by using the 'import resources' button , there is no feedback to the user the installation is finished (also no progress bar of the installation process in the UI). I would like to request a message box saying 'installation finished successfully' and/or a progress bar during installation (big bundle can take some time). 2. I don't find a button to delete a complete bundle. It could be handy, after selecting a bundle using the 'local resources' combobox, to have a button 'delete complete bundle' to remove it completely. Remember: there are no bugs, only happy little accidents! Bob Ross The joy of painting -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468263] New: bundle brushes not all loaded after installing
https://bugs.kde.org/show_bug.cgi?id=468263 Bug ID: 468263 Summary: bundle brushes not all loaded after installing Classification: Applications Product: krita Version: 5.1.5 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: bobrosspaint...@protonmail.com Target Milestone: --- Hello friends SUMMARY After installing this brush bundle in krita 5.1.5 https://github.com/Rakurri/rakurri-brush-set-for-krita/releases/tag/V2.1 Only 4 brushes where shown in krita. I had to close and open krita again to make them all appear in the docker. I think something is not refreshed after installing a bundle. STEPS TO REPRODUCE 1. Install https://github.com/Rakurri/rakurri-brush-set-for-krita/releases/tag/V2.1 2. See only 4 brushes are in the docker 3. Close and restart krita to see them all appear OBSERVED RESULT Not all brushes are shown EXPECTED RESULT All brushes should be shown without restarting krita Remember: there are no bugs, only happy little accidents! Bob Ross The joy of painting -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 467943] Unable to see full account name in selection dropdown for QIF export
https://bugs.kde.org/show_bug.cgi?id=467943 Bob Swift changed: What|Removed |Added CC||bsw...@rsds.ca -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 443566] Make it easier for user to re-use existing security when adding to new investment account
https://bugs.kde.org/show_bug.cgi?id=443566 Bob Swift changed: What|Removed |Added CC||bsw...@rsds.ca -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 467943] New: Unable to see full account name in selection dropdown for QIF export
https://bugs.kde.org/show_bug.cgi?id=467943 Bug ID: 467943 Summary: Unable to see full account name in selection dropdown for QIF export Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: ux-ui Assignee: kmymoney-de...@kde.org Reporter: bsw...@rsds.ca Target Milestone: --- Created attachment 157708 --> https://bugs.kde.org/attachment.cgi?id=157708=edit Export dialog at default and expanded widths SUMMARY When you open the dialog box to export an account to a QIF file, the account selection dropdown is a fixed width that does not display the full name of the accounts in the list. Resizing the dialog box (increasing the width) extends the width of the "QIF Profile" selection but the width of the "Account to export" selection remains fixed. Hovering the mouse pointer over an item in the list does not display a tooltip with the full name of the item. STEPS TO REPRODUCE 1. Open the "QIF Export" dialog by selecting "File" > "Export" > "QIF..." from the menu bar on the main screen. 2. Increase the width of the "QIF Export" dialog by dragging the left or right edge of the dialog box. 3. OBSERVED RESULT The width of the "Account to export" selection remains fixed. The width of the "QIF Profile" selection expands to fill the width of the dialog box. EXPECTED RESULT The width of the "Account to export" and "QIF Profile" selections expand proportionally to the width of the dialog box. SOFTWARE/OS VERSIONS Windows: 7 and 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I am attaching screen images of the dialog box at different widths to illustrate that the width of the "Account to export" selection remains fixed. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467024] Make Text in Properties Selectable for Copy
https://bugs.kde.org/show_bug.cgi?id=467024 --- Comment #2 from Bob D --- Selecting/copying individual values would be ample. I'd like to be able to select full file path, e.g. Q:\folder1\folder2\filename.tif, instead of Q:\folder1\folder2\ and filename.tif separately.(In reply to Maik Qualmann from comment #1) > We can make individual values selectable and copyable relatively easily. Is > that enough, or are all values actually required as a block? > > Maik Selecting/copying individual values would be ample for me. I'd like to be able to select full file path, e.g. "Q:\folder1\folder2\filename.tif", instead of "Q:\folder1\folder2" and "filename.tif" separately. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467024] New: Make Text in Properties Selectable for Copy
https://bugs.kde.org/show_bug.cgi?id=467024 Bug ID: 467024 Summary: Make Text in Properties Selectable for Copy Classification: Applications Product: digikam Version: 7.9.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Usability-Clipboard Assignee: digikam-bugs-n...@kde.org Reporter: plowmail2...@gmail.com Target Milestone: --- SUMMARY *** 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. Select a thumbnail 2. Select Properties (menu a the right edge of the window) 3. OBSERVED RESULT Displayed text cannot be selected/copied EXPECTED RESULT Desired result: Select text with mouse, and copy to the clipboard. Maybe add a button to the Properties display to copy all of its text to the clipboard. Also, add a choice somewhere so that Copy on a selected image will copy the image file's path as a string to the clipboard. 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.
[kio-extras] [Bug 411489] USB (MTP) connection to Android fails if Dolphin was running before plugging in
https://bugs.kde.org/show_bug.cgi?id=411489 Bob Igo changed: What|Removed |Added Version|21.08.0 |22.08.2 CC||b...@igo.name --- Comment #17 from Bob Igo --- Bug remains in kio-extras 22.08.2, Kubuntu 22.10, Plasma 5.25.5 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 439554] Visual bug on some PDF previews
https://bugs.kde.org/show_bug.cgi?id=439554 Bob Igo changed: What|Removed |Added Version|21.04.2 |22.08.2 --- Comment #8 from Bob Igo --- FYI, I still see this in Kubuntu 22.10, Plasma 5.25.5 with kio-extras 22.08.2. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464996] Resurrection of bug 422111
https://bugs.kde.org/show_bug.cgi?id=464996 --- Comment #6 from Bob --- As an addon to my last comment, that line: file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:61:17: Unable to assign [undefined] to int Also gets emitted periodically from plasmashell while the battery applet is bugged, probably due to periodic battery discharge updates in the backend somewhere. Seems like battery information is being sent to the applet, but once its in the bugged state it will not update otherwise. The only thing that clears it is a restart of plasmashell so the applet reloads to get the proper data. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464996] Resurrection of bug 422111
https://bugs.kde.org/show_bug.cgi?id=464996 --- Comment #5 from Bob --- In regular use I have a non-systemd system and plasmashell and powerdevil get started via their /etc/kde/xdg/autostart/ scripts. They are not always started in the same order on my system. Sometimes they are closer together, sometimes further apart, sometimes in reverse order. It would seem that on some of these occasions there is a timing that hits this bug. With that in mind, I managed to reproduce this bug from a running plasma session by opening konsole and running the following as my test user: # /usr/lib64/libexec/org_kde_powerdevil --replace & /usr/bin/plasmashell --replace Most of the time the two will restart as normal. However on rare occasion it will start with the bugged batterymonitor applet where it fails to report about my laptop's battery. Racing the two programs this way seems to trigger it as well, although only on rare occasion. The plasmashell console spew after the --replace command was is same everytime when the battery applet is working normally. When the applet gets bugged, the only difference is that plasmashell console will output the following: file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:61:17: Unable to assign [undefined] to int This line gets emitted when clicking on the icon in the system tray when the battery icon that should be there is bugged and replaced with the display brightness icon instead. I am not a kde/plasma expert so its hard to know what to look into next here. Any insight on what to try next from a dev would be appreciated. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 --- Comment #27 from Bob Treat --- Fedora has a patch. I tested it and it works for me. Should hit the repos soon. Details in the other bug referenced above. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 Bob Treat changed: What|Removed |Added CC||rptr...@gmail.com --- Comment #25 from Bob Treat --- (In reply to Matt Keith from comment #24) > Also to add, I am running fedora 37 kde spin with the 5.27 release of kde > plasma under wayland Running Nobara 37 (Fedora based) and switching to X11 gets my monitors to behave correctly. So my end, it's a Wayland thing. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #140 from Bob English --- (In reply to brian from comment #139) > Well it was nice while it lasted. As I reported two days ago, my system was > working after the 5.27.0 upgrade for the first time since Christmas. It > worked for a couple days including power offs, reboots. But I never let the > system sleep -- until today. Once the screens slept, the second screen > would not return on wake up. And now even reboots and cold-boots will not > let me re-activate that second screen again. Its back to square one. > > And there were no system changes applied during this time. > > My system details: > Operating System: Fedora Linux 37 > KDE Plasma Version: 5.27.0 > KDE Frameworks Version: 5.103.0 > Qt Version: 5.15.8 > Kernel Version: 6.1.11-200.fc37.x86_64 (64-bit) > Graphics Platform: X11 > Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz > Memory: 31.3 GiB of RAM > Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 > Manufacturer: Gigabyte Technology Co., Ltd. If you read this entire thread you would have found out there is a way to get the monitor back. At least manually until this is fixed: If you delete any files with monitor layouts that are named like this: c2cda156c1e54840478e5af385672567 from: $ /home/USER/.local/share/kscreen/ and $ /home/USER/.local/share/kscreen/outputs and logging off/ back in (not sure) or as I did: reboot, so new versions of the files will be regenerated as detected: Viola', 2 Monitors again. I did have to change their orientation in the settings though. Theres another workaround in this thread too. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 466052] New: Define global configurable default formatting settings for such things as dates, thousands and decimal separators, etc.
https://bugs.kde.org/show_bug.cgi?id=466052 Bug ID: 466052 Summary: Define global configurable default formatting settings for such things as dates, thousands and decimal separators, etc. Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: ux-ui Assignee: kmymoney-de...@kde.org Reporter: kmymoney@dfgh.net Target Milestone: --- SUMMARY *** It is annoying to always get an error when creating new import profile when the typical US date format of M-D-Y in CSV files is at odds with the program default Y-M-D Can the format settings that are typically region dependent be added to the Settings/Configure KMM dialog someplace? Keeping the ability to override the default is fine, but it would be much friendlier to have a programmable default. *** 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.
[kmymoney] [Bug 466051] New: focus lost when typing in Indicator boxes when creating import profile
https://bugs.kde.org/show_bug.cgi?id=466051 Bug ID: 466051 Summary: focus lost when typing in Indicator boxes when creating import profile Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: ux-ui Assignee: kmymoney-de...@kde.org Reporter: kmymoney@dfgh.net Target Milestone: --- Created attachment 156475 --> https://bugs.kde.org/attachment.cgi?id=156475=edit screenshot of issue SUMMARY *** When configuring a new CSV Profile, Focus is lost when typing in the 'Indicator for Credit/Debit' boxes after typing each character. Cursor moves to the top left field of the input file and typed characters replace that content. *** STEPS TO REPRODUCE 1. create a new input profile for a CSV file 2. start typing a new keyword in the 'Indicator for Credit' or 'Indicator for Debit' entry boxes (noticed in the Amount tab) OBSERVED RESULT notice that the first character is correctly displayed and further characters appear in the row 1 column 1 input file EXPECTED RESULT all characters typed show up in the box in which they are typed SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464996] Resurrection of bug 422111
https://bugs.kde.org/show_bug.cgi?id=464996 --- Comment #4 from Bob --- I updated to the latest plasma release and can still trigger this battery applet bug after enough login/logout cycles. Here's the "About" copy paste, for the record: Operating System: Slackware Live 15.0 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: Dell Inc. Product Name: XPS 13 9350 The bug is the same: A random chance that upon login, the battery applet thinks there's no battery and only shows the icon and controls for screen brightness/keyboard brightness instead. The tooltip over the "battery applet" in this state reports "No Batteries Available". This would seem that batterymonitor thinks there's no batteries, even though UPower reports 'IsPresent' as true, along with solid-hardware5 reporting "Battery.present = true (bool)" when looking at the details of my battery. Somehow there is a very small chance the applet gets the wrong information at session startup and stays that way until plasmashell is restarted. Seems like a timing issue but I dont understand enough about how the applet gets its data to make a proper guess. If there's anything else I can supply please let me know. Everything seems to report a present and functional battery except the applet. Upower and soild reports arn't anything to look at because they report a present battery and charge status as normal. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 465695] Incomplete transaction type list for Mutual Funds
https://bugs.kde.org/show_bug.cgi?id=465695 --- Comment #2 from Bob --- (In reply to Jack from comment #1) > You can use different categories for long and short term cap gains (and I > even have another set for tax deferred accounts.) I think the transactions > don't need different inherent types - you get a dividend of some sort and > you either get the cash or use it to buy additional shares. The dividend > could be interest, dividends, long or short term capital gains > distributions. Using different Categories is sufficient to allow you to > prepare the reports you need to prepare your taxes. > Separately, it is known that Investments needs a major overhaul, but that is > not high on the current priority list. Right now the basics of capital > gains are not really handled by KMM. I'm actually working on accumulating > all the various things that need to be dealt with, which are now not really > addressed. I'll add all this to the list, but nothing is likely to happen > in the near future. Thanks for the feedback on the submission and roadmap expectations. While I agree that a high level category of distributions can include dividends, special dividends, stocks/company spin outs and the various capital gains would obviously be preferred. As a brand new user, I guess I am highlighting the obvious. As I get deeper into it, I certainly agree that Investments needs to be better, I have some other feedback as I struggle getting my data into the program, should I write those up as individual bug/wishlist items - what is preferred? Some are usability, others are feature support - futures and options categories, etc. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 465698] New: Better handling of transaction type naming in imports
https://bugs.kde.org/show_bug.cgi?id=465698 Bug ID: 465698 Summary: Better handling of transaction type naming in imports Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: kmymoney@dfgh.net Target Milestone: --- SUMMARY *** It's annoying that apparently the phrasing of transactions must be matched exactly when manually importing a CSV file. 'Dividend Reinvestment' is not the same as 'Reinvest Dividend' and thus import fails requiring a manual editing of every transaction in the import file. It would be great if a popup could be implemented that would allow the user to specify/select what the transaction type is from the KMM display list and then remember that for the duration of the import or perhaps longer. Given the decision not to support cash in an investment account which is contrary to almost all investment accounts I have, intelligent importing of mixed transactions from those accounts would be very nice to support. Since the program knows of the association of investment and brokerage accounts from when they were created, give the importer the ability to direct a line item to either the investment or brokerage account. *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT import fails EXPECTED RESULT user can map the import file transaction types to what the program has defined, greatly decreasing user frustration with the import process SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464996] Resurrection of bug 422111
https://bugs.kde.org/show_bug.cgi?id=464996 --- Comment #3 from Bob --- I'm seeing the same thing on my system so I thought I would try to add my findings here... SUMMARY I am also seeing the missing battery applet bug described here and in 422111 on the latest version of plasmashell (5.26.5). The bug is very sporadic/random in nature but can be recurrently triggered with enough attempts. STEPS TO REPRODUCE Start a desktop session from a tty (i.e. with the startplasma-x11 xinit script). If the battery applet shows up normally, log out back to tty and launch the x11 session again until it occurs. The bug also shows up when starting the session from a display manager like sddm. I just used the tty method because it was quicker to repeatedly launch sessions. Note: The bug only triggers on new session startups. Simply restarting plasmashell in an already running session will not cause it. Note that it is highly random to trigger. I have observed up to 24 attempts until it triggers the bug. Other times it takes less attempts. OBSERVED RESULT Battery icon is missing from the system tray. It is replaced by the brightness icon and the tool tip reports "No Batteries Available". This is shown in the screenshots. EXPECTED RESULT The battery level should always be reported since this is a battery powered laptop. SOFTWARE/OS VERSIONS Operating System: Slackware Live 15.0 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.11 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: Dell Inc. Product Name: XPS 13 9350 ADDITIONAL INFORMATION UPower and solid-hardware5 both report the battery is present in any case. It is just the icon in plasmashell that is incorrect. When the battery icon is missing, running 'org_kde_powerdevil --replace' has no effect. When powerdevil restarts, the icon disappears and reappears as the brightness icon and still reports batteries are not available. Only restarting plasmashell returns it to normal. This bug seems related to UPower. Slackware is still packaging UPower 0.99.13 and the bug is not present with the combination of UPower 0.99.13 and Plasma 5.26.5. I've tested newer UPower versions (0.99.14 up to 0.99.20) and the bug can be triggered on all newer versions with enough login attempts. I'm not sure what happened between 0.99.13 to 0.99.14 that might cause this to trigger but it seemed related and worth mentioning. I hope this information is helpful. I can try to provide more debug output if needed but I am not experienced with the inner workings of upower, powerdevil, and plasmashell. - Bob -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464996] Resurrection of bug 422111
https://bugs.kde.org/show_bug.cgi?id=464996 --- Comment #2 from Bob --- Created attachment 156216 --> https://bugs.kde.org/attachment.cgi?id=156216=edit Screenshot of the failed condition This one has the tooltip -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464996] Resurrection of bug 422111
https://bugs.kde.org/show_bug.cgi?id=464996 Bob changed: What|Removed |Added CC||bobfun...@gmail.com --- Comment #1 from Bob --- Created attachment 156215 --> https://bugs.kde.org/attachment.cgi?id=156215=edit Screenshot of the failed condition This is when the bug has occurred. The brightness icon is here instead of the battery, and the tool tip reports batteries are unavailable. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 465695] New: Incomplete transaction type list for Mutual Funds
https://bugs.kde.org/show_bug.cgi?id=465695 Bug ID: 465695 Summary: Incomplete transaction type list for Mutual Funds Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: kmymoney@dfgh.net Target Milestone: --- SUMMARY *** Mutual Funds commonly have Long Term (LT) Capital Gains and Short Term (ST) Capital Gains distributions and offer the possibilities of Reinvesting those moneys. Currently only Dividends and Reinvest Dividends are listed as choices of Fund disbursements. These transactions are important to differentiate as their tax handling is different. *** STEPS TO REPRODUCE 1. Characterize the transaction type for mutual funds 2. 3. OBSERVED RESULT transaction type list missing: -Long Term (LT) Capital Gains -Short Term (ST) Capital Gains -Reinvest Long Term (LT) Capital Gains -Reinvest Short Term (ST) Capital Gains EXPECTED RESULT transaction type list includes the missing 4 types 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.
[kmymoney] [Bug 465693] New: New File Setup dialog wording wrong
https://bugs.kde.org/show_bug.cgi?id=465693 Bug ID: 465693 Summary: New File Setup dialog wording wrong Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: ux-ui Assignee: kmymoney-de...@kde.org Reporter: kmymoney@dfgh.net Target Milestone: --- Created attachment 156214 --> https://bugs.kde.org/attachment.cgi?id=156214=edit picture of dialog box SUMMARY *** The New File Setup dialog wording states 'click Next' but there is no 'Next' button to push. *** STEPS TO REPRODUCE 1. launch a new install of KMyMoney 2. Go thru configuration 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 456216] KReminder crashes randomly
https://bugs.kde.org/show_bug.cgi?id=456216 --- Comment #4 from Bob Mattes --- (In reply to Claudio Cambra from comment #3) > Hi, sorry to hear that Bob. We will be closing the issue due to lack of > info, but if you try Kalendar again and encounter this issue please feel > free to post to this bug report or open a new one Thanks. Will do. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 456216] KReminder crashes randomly
https://bugs.kde.org/show_bug.cgi?id=456216 --- Comment #2 from Bob Mattes --- (In reply to Carl Schwan from comment #1) > Hi, > > It seems this bug report is missing some important backtrace information. > Could you please install the missing debug symbols package, reproduce the > bug, and generate a new backtrace? > (https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports) > > Thanks for reporting bugs. > Cheers, > Carl Hi Carl, Thank you for looking into this. I moved on from KDE and Kontact months ago and so cannot regenerate the issue. Sorry. Cheers, Bob -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 464468] New: Menu Help Online Handbook goes to KDE Documentation, digikam unknown
https://bugs.kde.org/show_bug.cgi?id=464468 Bug ID: 464468 Summary: Menu Help Online Handbook goes to KDE Documentation, digikam unknown Classification: Applications Product: digikam Version: 7.9.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Documentation Assignee: digikam-bugs-n...@kde.org Reporter: plowmail2...@gmail.com Target Milestone: --- SUMMARY *** Menu Help Online Handbook goes to KDE Documentation. That page lacks entry for "digikam". *** STEPS TO REPRODUCE 1. Click on Menu Help Online Handbook OBSERVED RESULT Land on web page https://docs.kde.org/?application=digikam=trunk5 That page lacks entry for "digikam" EXPECTED RESULT Land on the Online Handbook SOFTWARE/OS VERSIONS Windows: 7 Home Premium 64-bit 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 464389] New: Bad link to documentation
https://bugs.kde.org/show_bug.cgi?id=464389 Bug ID: 464389 Summary: Bad link to documentation Classification: Applications Product: digikam Version: unspecified Platform: unspecified OS: Unspecified Status: REPORTED Severity: normal Priority: NOR Component: Documentation Assignee: digikam-bugs-n...@kde.org Reporter: plowmail2...@gmail.com Target Milestone: --- SUMMARY *** STEPS TO REPRODUCE 1. Install version 7.9 2. Read release notes (C:/Program Files/digiKam/releasenotes.html) 3. click on "as PDF" in "The complete handbook is available online as HTML or as PDF." OBSERVED RESULT At https://docs.kde.org/?application=digikam=trunk5=digikam.pdf get this: "The application digikam could not be found" EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 462558] Wish: I wish for smaller configurable vertical line spacing in Kate
https://bugs.kde.org/show_bug.cgi?id=462558 --- Comment #3 from Bob --- (In reply to Waqar Ahmed from comment #2) > This is a won't fix. 1.0 is the default value that the underlying font gives > us. If you want less, then you should change the font to behave that way. If > the editor provides a way to do this, it will just wreck the UI. Understood. Thanks for looking into this, Waqar. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 441324] Ease the process of closing an investment brokerage account.
https://bugs.kde.org/show_bug.cgi?id=441324 b...@mroczka.com changed: What|Removed |Added CC||b...@mroczka.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462833] New: For database tables created with generated SQL, database storage layer doesn't correctly save and retrieve base currency
https://bugs.kde.org/show_bug.cgi?id=462833
Bug ID: 462833
Summary: For database tables created with generated SQL,
database storage layer doesn't correctly save and
retrieve base currency
Classification: Applications
Product: kmymoney
Version: 5.1.2
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: database
Assignee: kmymoney-de...@kde.org
Reporter: bpes...@pcdialogs.com
Target Milestone: ---
SUMMARY
When working with database tables created by manually issuing the generated
SQL, as opposed to letting kmymoney itself create the tables, the database
storage layer doesn't correctly save and retrieve base currency, so that
whenever such an SQL-based kmymoney file is opened, the user is prompted to
re-choose the base currency.
STEPS TO REPRODUCE
1. Start kmymoney with the -n option
2. Choose Tools->Generate Database SQL
3. Save the generated SQL into a file
4. Creating a new database or using an existing one, run the commands in the
generated SQL file
5. In kmymoney, open the database
6. In the Currencies dialog that appears, add a currency and select it as the
base currency
7. Save the kmymoney data to the database
8. Re-open the database by either closing and restarting kmymoney or choosing
File->Open database
OBSERVED RESULT
kmymoney again prompts for selecting the base currency.
There is no row in the kmmKeyValuePairs table with kvpType='STORAGE',
kvpKey='kmm-baseCurrency' and kvpData=
The baseCurrency column in the single row in the kmmFileInfo table is empty
EXPECTED RESULT
File should open without prompt for base currency.
A row should be present in the kmmKeyValuePairs table with kvpType='STORAGE',
kvpKey='kmm-baseCurrency' and kvpData=
The baseCurrency column in the single row in the kmmFileInfo table should have
the 3 character base currency id
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
Reading the MyMoneyStorageSqlPrivate::readFileInfo method indicates that while
there is a column called baseCurrency in the kmmFileInfo table, that's not
where the base currency is retrieved from. Instead, it is retrieved from the
kmmKeyValuePairs table, from a row with kvpType='STORAGE' and kvpId=''. If you
manually issue the command 'insert into kmmkeyvaluepairs
values('STORAGE','','kmm-baseCurrency','USD');' (or some other currency id),
the problem goes away.
However, in the scenario described above,
MyMoneyStorageSqlPrivate::writeFileInfo doesn't write such a record after
choosing a base currency and saving to the database in the GUI. There is a call
to writeKeyValuePairs("STORAGE", kvpList, pairs); around line 683 of
kmymoney/plugins/sql/mymoneystoragesql_p.h, but at that point the pairs
parameter has no entry with the key "kmm-baseCurrency". I haven't been able to
determine why.
I'm running kmymoney on Fedora 35 (close to EOL) and I have seen that Qt
library updates do break some things, including kmymoney. I know nothing about
Qt, but I am wondering if this is a Qt problem.
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 462558] Wish: I wish for smaller configurable vertical line spacing in Kate
https://bugs.kde.org/show_bug.cgi?id=462558 Bob changed: What|Removed |Added Attachment #154238|0 |1 is obsolete|| --- Comment #1 from Bob --- Created attachment 154239 --> https://bugs.kde.org/attachment.cgi?id=154239=edit Comparison of vertical line spacing of Kate vs Textpad -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 462558] New: Wish: I wish for smaller configurable vertical line spacing in Kate
https://bugs.kde.org/show_bug.cgi?id=462558 Bug ID: 462558 Summary: Wish: I wish for smaller configurable vertical line spacing in Kate Classification: Applications Product: kate Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: bob872...@hotmail.com Target Milestone: --- Created attachment 154238 --> https://bugs.kde.org/attachment.cgi?id=154238=edit Comparison of vertical line spacing of Kate vs Textpad SUMMARY For me, there is too much vertical whitespace between lines for the same TTF font Courier New (as a simple comparison font) I would like the option to set a vertical whitespace less than the current minimum value of "1.0" in Configure Kate I have shown the differences in attached image: KateNeon_vs_TextpadWin7.png Background context: This might be more general for linux font rendering which always seems to prefer lots of whitespace which I am not pleased about. This could be Konsole, text editors, Konquerer or KDE titlebars and tool bars. KDE and Linux always seems to have a lot of vertical whitespace used for: title bar area, application menu, application toolbar, statusbar etc. Again, this is so apparent in my attachment as the "title bar area, application menu, application toolbar" vertical size for Kate vs Textpad is about double for Kate. In an era when non-casual users are desktop/laptop users with 16:10 or 16:9 aspect screens, it's annoying. I get that you want to support touch control on mobile, but I don't want a mobile OS for use on my desktop. I have a mouse, a keyboard, a high DPI screen and I would prefer to use all of that precious vertical space to the maximum effect when programming, reading documentation etc. STEPS TO REPRODUCE 1. Navigate to Kate -> Settings Menu -> Configure Kate -> Appearance Tab -> Line Height Multiplier 2. Click the down arrow as much as possible for "Line Height Multiplier" setting 3. You cannot go below a multiplier of 1.0 OBSERVED RESULT "1.0" is the arbitrary minimum value EXPECTED RESULT I want to go lower than 1.0. I would experiment and check results, but I want to get rid of most of the vertical whitespace area in between lines in the editor regardless of font choice. For this, I would suggest a minimum of zero? SOFTWARE/OS VERSIONS Windows: 7 Professional SP1 Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.26.80 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 5.15.0-53-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-2500K CPU @ 3.30GHz Memory: 7.8 GiB of RAM Graphics Processor: SVGA3D; build: RELEASE; LLVM; Manufacturer: innotek GmbH Product Name: VirtualBox System Version: 1.2 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 462251] New: kdesrc-build kde-pim throws DBUS error inside kdepim-docker instance
https://bugs.kde.org/show_bug.cgi?id=462251 Bug ID: 462251 Summary: kdesrc-build kde-pim throws DBUS error inside kdepim-docker instance Classification: Developer tools Product: kdesrc-build Version: Git Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mp...@kde.org Reporter: kdebugs.20.gordo...@spamgourmet.com Target Milestone: --- SUMMARY kdesrc-build kde-pim throws DBUS error inside kdepim-docker instance STEPS TO REPRODUCE 1. Download kubuntu latest iso and install into a new VirtualBox VM instance 2. Follow steps from https://community.kde.org/KDE_PIM/Docker 3. Finally execute most critical step (from section "Running the Docker container"): run.sh $HOME/kdepim-dev OBSERVED RESULT bob029345@bob029345-VirtualBox:~/kdepim-docker$ ./run.sh $HOME/kdepim-dev dbus at unix:abstract=/tmp/dbus-gXoBJ4oY8w,guid=282d241d1cd3b89b30ee8ac66381124a dbus at 27 dbus killed, starting again started dbus neon@367a8b8badc3:~$ sudo apt update Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease Get:5 http://archive.neon.kde.org/unstable jammy InRelease [173 kB] Hit:6 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease Fetched 173 kB in 1s (127 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. W: http://archive.neon.kde.org/unstable/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. neon@367a8b8badc3:~$ sudo apt full-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. neon@367a8b8badc3:~$ kdesrc-build kde-pim ~/kdesrc-build ~ The signatures feature is experimental at /home/neon/kdesrc-build/modules/ksb/Util/LoggedSubprocess.pm line 139. The signatures feature is experimental at /home/neon/kdesrc-build/modules/ksb/Util/LoggedSubprocess.pm line 165. The signatures feature is experimental at /home/neon/kdesrc-build/modules/ksb/Util/LoggedSubprocess.pm line 189. The signatures feature is experimental at /home/neon/kdesrc-build/modules/ksb/Util/LoggedSubprocess.pm line 200. The signatures feature is experimental at /home/neon/kdesrc-build/modules/ksb/Util/LoggedSubprocess.pm line 217. The global configuration file is stored in the old location. It will still be processed correctly, however, it's recommended to move it to the new location. Please move ~/.kdesrc-buildrc to ~/kdepim/home/config/kdesrc-buildrc The global data file is stored in the old location. It will still be processed correctly, however, it's recommended to move it to the new location. Please move ~/.kdesrc-build-data to ~/.local/state/kdesrc-build-data Cloning sysadmin-repo-metadata Encountered an error in the execution of the script. --> org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory Please submit a bug against kdesrc-build on https://bugs.kde.org/ Your logs are saved in file:///home/neon/kdepim/logs/2022-11-25-01 ~ neon@367a8b8badc3:~$ EXPECTED RESULT The kde run.sh script should execute without any issue as this is done in a Docker container SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.10 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-23-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-2500K CPU @ 3.30GHz Memory: 7.8 GiB of RAM Graphics Processor: llvmpipe Manufacturer: innotek GmbH Product Name: VirtualBox System Version: 1.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #55 from Bob English --- (In reply to bertil.bonus from comment #54) > My problem returned with the upgrade to 22.04. DP monitor disappeared. > HDMI/DVI monitor remained. > > Solved it by removing all files under > > $ /home/USER/.local/share/kscreen/ > and > $ /home/USER/.local/share/kscreen/outputs > > and logging off/ back in. Solved? No, the problem still persists, as if you let your system suspend it will lose that monitor again. Deleting those files is just a band aid, not a final solution. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #49 from Bob English --- I found a way to get both monitors back; Well until the system goes back to sleep. It's from the EndeavourOS Forum: If you delete any files with monitor layouts that are named like this: c2cda156c1e54840478e5af385672567 from: $ /home/USER/.local/share/kscreen/ and $ /home/USER/.local/share/kscreen/outputs and logging off/ back in (not sure) or as I did: reboot, so new files will be regenerated as detected. You can experiment with deleting one or more of the files to see if this fixes your issue. If you want to play it safe, you can archive the existing files and restore them in case of disaster, and then also have them for later comparisons with the new ones. I deleted them all (so 4), and rebooted: Viola', 2 Monitors again. I did have to change their orientation in the settings though. Hopefully this can assist the dev's who still haven't arrived on the scene (or if, are hiding :>), to find the source of the bug. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #44 from Bob English --- (In reply to Bob English from comment #43) > Just Updated everything: No change! > > Operating System: EndeavourOS > KDE Plasma Version: 5.26.2 > KDE Frameworks Version: 5.99.0 > Qt Version: 5.15.7 > Kernel Version: 6.0.7-arch1-1 (64-bit) > Graphics Platform: X11 > Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor > Memory: 62.7 GiB of RAM > Graphics Processor: NVIDIA GeForce GTX 1050/PCIe/SSE2 Had this When first reporting: KDE Plasma Version: 5.26.0 (NOW: 5.26.2) KDE Frameworks Version: 5.99.0(NO CHANGE) Qt Version: 5.15.6 (Now: 5.15.7) Kernel Version: 6.0.2-arch1-1 (64-bit)(Now:6.0.7-arch1-1) Problem Still persists. Cannot change in settings (same behavior). bertil.bo...@gmail.com's issue, may have been unrelated to begin with, as the mere claim "I have the same problem" came with no usable info to establish it, and their new claim: "It seems to have gotten better for me!" is also void of any usable info. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #43 from Bob English --- Just Updated everything: No change! Operating System: EndeavourOS KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel Version: 6.0.7-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #40 from Bob English --- (In reply to John from comment #39) > As a work around I am using autorandr. I saved a working profile and have > it reload when the computer wakes from sleep. I don't want a workaround, and that one requires installing and learning the program and it's quirks... I have been on Linux for over a decade and never even heard of 'autorandr' until now. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461291] New: Keyboard shortcuts definitions using the Numeric Keypad keys are not possible
https://bugs.kde.org/show_bug.cgi?id=461291 Bug ID: 461291 Summary: Keyboard shortcuts definitions using the Numeric Keypad keys are not possible Classification: I don't know Product: kde Version: unspecified Platform: OpenSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: grim.der.rea...@gmail.com Target Milestone: --- I would like to bind single keys from the numpad as shortcuts, which was possible with opensuse15.1 (and not anymore since 15.2) STEPS TO REPRODUCE: Example with Dolphin version 22.08.2 – set a keyboard shortcut to duplicate a file (or any other action): Duplicate file set to «NumPad + 7» doesn't work. Duplicate file set to «Shift + NumPad + 7» doesn't work. Duplicate file set to «Crtl + NumPad + 7» doesn't work. Duplicate file set to «Crtl + Shift + NumPad + 7» doesn't work. Duplicate file set to «Crtl + Ü» does work. Duplicate file set to «Crtl + 7» does work – (Keyboard “7” – not NumPad “7”). OBSERVED RESULT Currently, KDE Plasma will not allow shortcuts definitions using the Numeric Keypad keys. EXPECTED RESULT Use a shortcut with a single key from the numeric keypad without adding a 'Crtl +' or 'Shift +' SOFTWARE/OS VERSIONS NAME="openSUSE Tumbleweed" # VERSION="20221030" -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #37 from Bob English --- (In reply to Nate Graham from comment #36) > Hopefully someone who's familiar with the inner workings of KScreen and KWin > can help with that. Unfortunately that person is not me; I'm just bug > triaging. Thanks Triage guy! Will Wait for the surgeons. :>) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #35 from Bob English --- Just logged out, and got a login screen on both monitors. Logged in to my maintenance account, both monitors working. Logged out from it, and once again Login screen on both monitors, logged in to this, my main account, KDE splash screen on both monitors, but as soon as the desktop showed up, back to only one monitor. :>( -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #34 from Bob English --- Any other files to attach that may help? Is there some file we can look into and change some setting manually, or even a file to delete that will make Plasma detect the monitors on reboot, hopefully without losing a whole bunch of other settings, so not the entire plasma setup...? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #32 from Bob English --- I will try just switching users too. Also: This silence from the developers isn't encouraging. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #29 from Bob English --- (In reply to Rainer Klier from comment #26) > (In reply to Rainer Klier from comment #24) > > i have a second user account on my computer, to be able to test issues, if > > they also occur on other accounts. > > and today i found out, that the external monitor is enabled automtaically/by > > default on this second user account. > > i was wrong. > it doesn't have anything to do with the account. > today i first tried the test-account after switching on the computer, and > here the behaviour was the same: external monitor was disabled. > then i logged of from the test-account and logged in to my account, and > guess what, the second monitor was enabled by default. This morning I logged onto my maintenance account instead, and no change at all, so not what you were describing, that account still has two monitors, and this one still has my primary one off and it cannot be turned back on. So you may have left out something, like : Did you let the monitors suspend while in your "Test" account? or What all did you do that would call for Plasma to save whatever changes? Any which way, I cannot at all see how making changes in one account can change anything in another (Separate /home/USER folders with separate settings files) unless it happened system wide in the first place which this did not as shown by the evidence. I sure hope you didn't just make it all up, or else you may be sending those trying to fix it on a wild and useless goose chase, and hindering the investigation, not helping it. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #27 from Bob English --- (In reply to Rainer Klier from comment #26) > (In reply to Rainer Klier from comment #24) > > i have a second user account on my computer, to be able to test issues, if > > they also occur on other accounts. > > and today i found out, that the external monitor is enabled automtaically/by > > default on this second user account. > > i was wrong. > it doesn't have anything to do with the account. > today i first tried the test-account after switching on the computer, and > here the behaviour was the same: external monitor was disabled. > then i logged of from the test-account and logged in to my account, and > guess what, the second monitor was enabled by default. So it's flippant between accounts, that doesn't mean the account has nothing to do with it, but that it does! It means that display settings for each account are saved per account, and whatever mechanism is saving them is screwing up. I also have what I call a "Maintenance account" and I too logged into it to see if the problem was with it too, and it worked fine. So just maybe if I log back into it, it too is missing a monitor, and when I go back to this one I will have two monitors again. If so then the developers may get a better idea where to look, as something about the login process may have something to do with it, or effect whatever the issue is. I will try tomorrow: Dead tired now. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #25 from Bob English --- (In reply to Rainer Klier from comment #24) > i have a second user account on my computer, to be able to test issues, if > they also occur on other accounts. > and today i found out, that the external monitor is enabled automtaically/by > default on this second user account. > i can't explain why, and before the update to 5.26 it was of course also > working with my main account. > i just wanted to tell you this fact. There are other duplicate bug reports, as listed above, but to read them you have to follow the links as their text isn't carried over to here which would be a good thing for clarity. My original bug report had some important details, including that the problem is isolated to one account. Heres what I wrote: "After the system went into standby, when I unlocked the screen one of 2 monitors (the primary one at 4K) is black, no mouse pointer, nothing! Reboot doesn't help. In display settings the monitor is present, but not activated. I find and select it from the drop down list, and can change the resolution, but the refresh rate cannot be selected, and it reads 30Hz with an i (for Info) next to it, I click the i and get "30 Hz is the only resolution this monitor can display" (it can do 60Hz for sure). I log off and log on to a different user account and all is well, both monitors work, and as usual. Conclusion: Something wrong with Plasma settings of that one user account only. Now, for the last week or so (I run updates daily) Plasma has not remembered any window sizes or positions, nor Icon locations after moving on the desktop between reboots. They seem to be stuck in time from when I used them one week ago. Since only one user account is affected it must be related to one or more user specific Plasma display settings related files, and Plasma is not making changes to it/them, but now somehow did, but in a very bad way! Maybe it's a module it uses to record changes, but I cannot tell yet until I logon to the other user account open a few apps resize their windows, move a few Icons around... reboot and see if the changes took, but I don't want it to break too!" Now I add this: Before I shut down, I always close all open windows on all desktops, but now after rebooting some (not all) open again, as if I didn't close them. Although all of these problems may not be related, they all have one thing in common: Plasma is not recording the desktop and displays configurations after suspending monitors, or reboots. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #23 from Bob English --- FWIW: My graphics card (1 x Display port, 1 x HDMI) supports and runs both monitors, and on mine it is the one using a Display port that doesn't work, and the one on the HDMI is the one that works. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 439554] Visual bug on some PDF previews
https://bugs.kde.org/show_bug.cgi?id=439554 --- Comment #7 from Bob Igo --- Occurs for me on KDE 5.24 on Kubuntu 22.04. As with the original report, even from the same vendor, the behavior varies, and reading the PDF never shows a leading blank page. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 439554] Visual bug on some PDF previews
https://bugs.kde.org/show_bug.cgi?id=439554 Bob Igo changed: What|Removed |Added CC||b...@igo.name -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #19 from Bob English --- Everything is normal, up to and including the KDE splash screen, then only one monitor comes on line. In the settings it is set as primary; I had it as secondary. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #18 from Bob English --- Created attachment 153040 --> https://bugs.kde.org/attachment.cgi?id=153040=edit Bob English's kscreen-console bug -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #12 from Bob English --- (In reply to Bryan D. Stine from comment #11) > (In reply to Bob English from comment #10) > > Updated the system and there was one for Plasma Display. Rebooted >> No > > change. Went into settings enabled the display, set as primary, still > > misreporting the refresh rate with 30Hz listed as the only rate the monitor > > can run at, which is false, it can do 60Hz. When I hit apply, all that > > happens is that all of the open apps shift to the left, 1/2 on and 1/2 off > > screen, the dialog with the "Keep" and "revert" buttons does nothing on > > clicking (Cursor positioning incorrect?) and it reverts. Reboot doesn't > > change anything. > > > > So I cannot accept this as Fixed, as the problem still remains. > > I’m inclined to agree. The commit cited is in wayland code, and I built kain > on the Plasma/5.26 branch last night and still experience loss of the > primary screen on resume from suspend on X11. Exactly! I too am on X11, not Wayland, so I cannot see how it applies to us. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 Bob English changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #10 from Bob English --- Updated the system and there was one for Plasma Display. Rebooted >> No change. Went into settings enabled the display, set as primary, still misreporting the refresh rate with 30Hz listed as the only rate the monitor can run at, which is false, it can do 60Hz. When I hit apply, all that happens is that all of the open apps shift to the left, 1/2 on and 1/2 off screen, the dialog with the "Keep" and "revert" buttons does nothing on clicking (Cursor positioning incorrect?) and it reverts. Reboot doesn't change anything. So I cannot accept this as Fixed, as the problem still remains. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #9 from Bob English --- (In reply to Nate Graham from comment #2) > Vixed by Vlad Zahorodnii with > https://invent.kde.org/plasma/kwin/commit/ > ff28dd06936d733ac6d65f41669b1331fa28d1cc in Plasma 5.26.1! By "Vixed" do you mean Fixed? and if so, how do I apply the fix, as your link points to some page used by the programmers, I'm just a user, and it tells me nothing. I will run an update now and see if this "Commit" was added to an update. Please stand by -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460623] Lost one of two displays for one user only
https://bugs.kde.org/show_bug.cgi?id=460623 Bob English changed: What|Removed |Added Platform|Other |Archlinux -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460623] New: Lost one of two displays for one user only
https://bugs.kde.org/show_bug.cgi?id=460623 Bug ID: 460623 Summary: Lost one of two displays for one user only Classification: Plasma Product: plasmashell Version: 5.26.0 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bobofengl...@zoho.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY *** After the system went into standby, when I unlocked the screen one of 2 monitors (the primary one at 4K) is black, no mouse pointer, nothing! Reboot doesn't help. In display settings the monitor is present, but not activated. I find and select it from the drop down list, and can change the resolution, but the refresh rate cannot be selected, and it reads 30Hz with an i next to it, I click the i and get "30 Hz is the only resolution this monitor can display" (it can do 60Hz for sure). I log off and log on to a different user account and all is well, both monitors work, and as usual. Conclusion: Something wrong with Plasma settings of that one user account only. Now, for the last week or so (I run updates daily) Plasma has not remembered any window sizes or positions, nor Icon locations after moving on the desktop between reboots. They seem to be stuck in time from when I used them one week ago. Since only one user account is affected it must be related to one or more user specific Plasma display settings related files, and Plasma is not making changes to it/them, but now somehow did, but in a very bad way! Maybe it's a module it uses to record changes, but I cannot tell yet until I logon to the other user account open a few apps resize their windows, move a few Icons around... reboot and see if the changes took, but I don't want it to break too! Any Ideas? *** STEPS TO REPRODUCE 1. Let session go into standby 2. Move mouse and see if displays work 3. OBSERVED RESULT One of two displays doesn't work EXPECTED RESULT Both displays work SOFTWARE/OS VERSIONS Operating System: Arch Linux EndeavourOS KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.2-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 459471] Satellites Not Shown
https://bugs.kde.org/show_bug.cgi?id=459471 Bob Miller changed: What|Removed |Added CC||rmiller...@gmail.com --- Comment #1 from Bob Miller --- Make that a multitude of TLE files in /home/bob/.local/share/kstars -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 459471] New: Satellites Not Shown
https://bugs.kde.org/show_bug.cgi?id=459471 Bug ID: 459471 Summary: Satellites Not Shown Classification: Applications Product: kstars Version: 3.6.0 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: rmiller...@gmail.com Target Milestone: --- Kstars is not processing satellites. There are a multitude of TLE files in /home/bob/.local/kstars. These files used to contain the two line element (TLE) representations of the satellites. Now those files all say something like Document Moved Object MovedThis document may be found http://celestrak.org/NORAD/elements/geodetic.txt;>here and that's it. No data. If one goes to http://celestrak.org/NORAD/elements/geodetic.txt you will find all the geodetic satellite TLEs. However, updating the satellite data via Kstars loads the same empty files. A workaround is to go to the NORAD site and download the data into the appropriate .tle file. Kstars will read that data, plot the satellites, find a satellite in the Pointing menu, etc. However, after downloading and saving a .tle file, make sure to change the r/w permissions to read only; otherwise the next satellite update will overwrite with an essentially blank file. Running kstars-bleeding STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: kubuntu (ubuntu 20 LTS) All software (INDI, kstars, etc) is up to date KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
