[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3
https://bugs.kde.org/show_bug.cgi?id=401088 Steve Vialle changed: What|Removed |Added CC||stev...@orcon.net.nz --- Comment #43 from Steve Vialle --- I have been seeing this for every filesystem (3 local filesystems on 2 RAID1 arrays , 5 NFS mounts), every login. Appears new(ish), as in I'm tracking current plasma releases and I've only seen it in the last couple of updates. The NFS mounts are indeed slow, as the network is firewalled until opensnitch's GUI loads (or could be down entirely) and mounts are retrying in the background (i.e. mounted with -o bg) but the messages regarding local arrays are entirely incorrect - as verified by dropping (or booting direct to) a VT. Those inaccessible NFS background mounts also completely prevent dolphin from launching (or hang it if it's already open and they go down), as well as freezing parts of plasmashell itself (including the panel and notifications). The result is an unusable desktop for a few seconds until the NFS mounts succeed, followed by a flurry of 8 "filesystem not responding" popups... which only appear once the filesystem is no longer "not responding", by which time they are completely pointless. If the network is actually down, the desktop remains unusable until the background mounts time out and fail - which could be 5 minutes, or it could be _forever_ if they are hard mounts. This is not an acceptable user experience by any stretch of the imagination, and I know of no other UI or file manager that locks up completely if a single non-essential mount is down. IOW, the behaviour of plasma/kio WRT inaccessible / unresponsive / slow filesystems is utterly broken, and has been for years. Adding popups is not addressing the root problem in the slightest, doubly so if they don't appear until _after_ the cause is resolved. -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 474820] New: kf6-kwayland: rpmlint error after build
https://bugs.kde.org/show_bug.cgi?id=474820
Bug ID: 474820
Summary: kf6-kwayland: rpmlint error after build
Classification: Plasma
Product: kwayland-integration
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: farch...@gmail.com
Target Milestone: ---
Good afternoon!
We're working on bringing kf6 packages into Fedora. For this package, we get
the following error:
kf6-kwayland-devel.x86_64: E: double-slash-in-pkgconfig-path
/usr/lib64/pkgconfig/KF6WaylandClient.pc libdir=${prefix}//usr/lib64
kf6-kwayland-devel.x86_64: E: double-slash-in-pkgconfig-path
/usr/lib64/pkgconfig/KF6WaylandClient.pc Libs: -L${prefix}//usr/lib64
-lKF6WaylandClient
Here's the error description:
double-slash-in-pkgconfig-path:
This pkg-config file contains a path with a double slash ('//') in it. This
will break debugedit when stripping debug symbols during package building if
these paths have been passed to gcc, and fail with the following error:
canonicalization unexpectedly shrank by one character.
This is after building commit 770e361d9b6521191e4464944e49b41b21ccdf2e (Latest
at the time of speaking):
https://invent.kde.org/frameworks/kwayland/-/commit/770e361d9b6521191e4464944e49b41b21ccdf2e
If you need any kind of information please do not hesitate to ask! Thanks!
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 467743] When opening .deb file, does not offer to update package, only to remove it
https://bugs.kde.org/show_bug.cgi?id=467743 Steve Zakulec changed: What|Removed |Added CC||spzaku...@gmail.com --- Comment #2 from Steve Zakulec --- Can confirm this is an issue- it regularly shows up with the Discord .deb files. I'm on KDE Neon. -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 473866] Merkuro displays wrong month/days
https://bugs.kde.org/show_bug.cgi?id=473866 Steve changed: What|Removed |Added Attachment #161779|merkuro off my months and |merkuro off by months and description|days|days -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474570] Keyboard binds for the Desktop Grid effect does not save/apply
https://bugs.kde.org/show_bug.cgi?id=474570 --- Comment #2 from Steve Cossette --- Created attachment 161732 --> https://bugs.kde.org/attachment.cgi?id=161732=edit Demonstration of behavior Hopefully this video demonstrates the problem! Thanks! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-bluez-qt] [Bug 474701] [KF6 build] rpmlint errors after compile: double-slash-in-pkgconfig-path
https://bugs.kde.org/show_bug.cgi?id=474701 Steve Cossette changed: What|Removed |Added Summary|rpmlint errors after|[KF6 build] rpmlint errors |compile:|after compile: |double-slash-in-pkgconfig-p |double-slash-in-pkgconfig-p |ath |ath --- Comment #1 from Steve Cossette --- Oh, forgot to mention. This is as-of commit fe828b861140534ed728142acf03bd64ca13821e dated September 1st. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-bluez-qt] [Bug 474701] New: rpmlint errors after compile: double-slash-in-pkgconfig-path
https://bugs.kde.org/show_bug.cgi?id=474701
Bug ID: 474701
Summary: rpmlint errors after compile:
double-slash-in-pkgconfig-path
Classification: Frameworks and Libraries
Product: frameworks-bluez-qt
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: now...@gmail.com
Reporter: farch...@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
***
Upon compiling the kf6 version of this framework, we get some rpm lint errors:
kf6-bluez-qt-devel.x86_64: E: double-slash-in-pkgconfig-path
/usr/lib64/pkgconfig/KF6BluezQt.pc libdir=${prefix}//usr/lib64
kf6-bluez-qt-devel.x86_64: E: double-slash-in-pkgconfig-path
/usr/lib64/pkgconfig/KF6BluezQt.pc Libs: -L${prefix}//usr/lib64 -lKF6BluezQt
This is the rpmlint explanation of the error:
double-slash-in-pkgconfig-path:
This pkg-config file contains a path with a double slash ('//') in it. This
will break debugedit when stripping debug symbols during package building if
these paths have been passed to gcc, and fail with the following error:
canonicalization unexpectedly shrank by one character.
Would it be possible to fix the double slash?
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 474570] New: Keyboard binds for the Desktop Grid effect does not save/apply
https://bugs.kde.org/show_bug.cgi?id=474570 Bug ID: 474570 Summary: Keyboard binds for the Desktop Grid effect does not save/apply Classification: Plasma Product: kwin Version: 5.27.7 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: farch...@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 *** If I go in Settings, Workspace -> Workspace Behavior and scroll down to the Desktop Grid effect under Window Management, and click on the Cog at the right (Effect Settings) and try to assign a keyboard shortcut to the effect, it'll look like it saved it. But if you go back into the effect's settings, the shortcut will be gone. STEPS TO REPRODUCE 1. Go to Settings, Workspace -> Workspace Behavior 2. Scroll down to Desktop Grid, and click on the Cog (Settings) 3. Try to assign a keyboard shortcut to the effect. OBSERVED RESULT The shortcut disappears/does not save after clicking OK EXPECTED RESULT The shortcut should have saved SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 38 KDE, 5.27.7 (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.9 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467074] When returning from screen energy saving, Plasma forgets that an external screen is connected and doesn't assign it a containment
https://bugs.kde.org/show_bug.cgi?id=467074 --- Comment #28 from Steve --- This is still an issue in 5.27.7. Although there seems to be new behavior - or at least I didn't notice there was a timeout dependency before. On my setup I can now cycle through my 3 other systems (via KVM Switch) and avoid the death of plasma shell if I do it quickly. It looks to be about 1 minute before it dies. I am happy to run some debugging for the developers if this is useful. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 474109] New: Add option to show valid moves
https://bugs.kde.org/show_bug.cgi?id=474109 Bug ID: 474109 Summary: Add option to show valid moves Classification: Applications Product: kpat Version: 23.08.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: co...@kde.org Reporter: sts33n...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- I request that a button be added, similar to the "Hint" button, that shows valid moves. It used to be that the "Hint" button did this, but recently kpat has been changed so that "Hint" only shows the move suggested by the solver. It would be nice if the user had a second button, say called "Show moves", that shows all legal moves. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 474106] spider solver sometimes shows solvable game as unsolvable
https://bugs.kde.org/show_bug.cgi?id=474106 --- Comment #1 from Steve Soule --- Created attachment 161377 --> https://bugs.kde.org/attachment.cgi?id=161377=edit Video showing bug -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 474106] New: spider solver sometimes shows solvable game as unsolvable
https://bugs.kde.org/show_bug.cgi?id=474106 Bug ID: 474106 Summary: spider solver sometimes shows solvable game as unsolvable Classification: Applications Product: kpat Version: 23.08.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: solver Assignee: co...@kde.org Reporter: sts33n...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- Created attachment 161376 --> https://bugs.kde.org/attachment.cgi?id=161376=edit kpat saved game SUMMARY Sometimes the solver in KPatience Spider shows "Solver: This game is no longer winnable" when the game can still be won. STEPS TO REPRODUCE 1. Load attached save game 2. Move red queen OBSERVED RESULT Message is "This game is no longer winnable" before the move. EXPECTED RESULT Message is "This game is winnable" or "Unable to determine if this game is winnable" before the move. SOFTWARE/OS VERSIONS Linux version: 6.4.11-1 distribution: openSUSE Tumbleweed 20230901 (x86_64) kwin5 version: 5.27.7-1.2.x86_64 plasma5-workspace version: 5.27.7-3.1.x86_64 libQt5Core5 version: 5.15.10+kde129-2.2.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472944] No option to use internal MYSQL (MariaDB) server
https://bugs.kde.org/show_bug.cgi?id=472944 --- Comment #2 from Steve Franks --- OK, thanks -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472944] New: No option to use internal MYSQL (MariaDB) server
https://bugs.kde.org/show_bug.cgi?id=472944 Bug ID: 472944 Summary: No option to use internal MYSQL (MariaDB) server Classification: Applications Product: digikam Version: 8.0.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Database-Engine Assignee: digikam-bugs-n...@kde.org Reporter: steve...@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 *** I am having issues with my old PC, running digikam under Ubuntu 22.04. It was running the 8.20 appimage, but kept hanging, so I installed the latest (8.0.0) version from the repository. It hasn't read the configuration file created by 8.2.0 and is using SQLite as its database engine. I want it to use MYSQL internal, because I have around 150k images. STEPS TO REPRODUCE 1. Remove 8.2.0 appimage 2. Install 8.0.0 using Ubuntu Software Updater. 3. Settings | Configure digikam | Database driopdown list only has Type of SQLite OBSERVED RESULT digikam stops responding, whilst finding new items. EXPECTED RESULT I should be able to use MYSQL Internal service SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 22.04 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.106.0 Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472256] New: Very difficult to align display edges in Display Configuration
https://bugs.kde.org/show_bug.cgi?id=472256 Bug ID: 472256 Summary: Very difficult to align display edges in Display Configuration Classification: Applications Product: systemsettings Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: sstein...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 160285 --> https://bugs.kde.org/attachment.cgi?id=160285=edit Software/OS Versions from "About this System" STEPS TO REPRODUCE 1. Attempt to drag second monitor around to align so that mouse moves smoothly between monitors. 2. 3. OBSERVED RESULT Second monitor "snaps" to useless locations (overlapping, kitty-corner, etc.). It is extremely difficult to get the common edges to line up at all, much less smoothly position the 2nd monitor's left edge along the right edge of the first in various vertical positions to test mouse movement. EXPECTED RESULT In previous versions, there was no "snapping", the monitors just smoothly positioned to wherever they were dragged. SOFTWARE/OS VERSIONS See attachment. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455326] Window crash after tiling twice to the screen edge
https://bugs.kde.org/show_bug.cgi?id=455326 --- Comment #9 from Steve Vialle --- (In reply to David Edmundson from comment #6) > Is this still reproducible against newer Plasma (5.27) Apologies for the late update, I am unable to reproduce this with 5.27.6. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467074] When returning from screen energy saving, Plasma forgets that an external screen is connected and doesn't assign it a containment
https://bugs.kde.org/show_bug.cgi?id=467074 --- Comment #27 from Steve --- I managed to find an installation image (.iso) from February 6th (2023). This version of Slackware64 has the following KDE5 versions: Core Desktop binaries: 5.26.5 Frameworks: 5.102.0 Applications: 22.12.2 I recently bought an external 1TB SSD and installed this version of the OS/Desktop Environment on my laptop. These versions do not exhibit the behavior when switching in/out the secondary desktop as it does in the more recent versions of Plasma X11. This should narrow down the code changes sufficiently in the plasma-desktop (and workspace) packages to a workable window for the bug-fixers. Happy bug-fixing to the KDE Team! I am confident your very capable developers can quickly resolve and fix the bug now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467074] When returning from screen energy saving, Plasma forgets that an external screen is connected and doesn't assign it a containment
https://bugs.kde.org/show_bug.cgi?id=467074 --- Comment #25 from Steve --- I can definitively state that in 5.27.5 this is only an issue with Plasma X11. Wayland and Full Wayland on my Slackware64 distro (Current tree) do not exhibit this behavior (bug) with Plasma shell - i.e. losing it's recollection of active monitors after a disconnection or sleep condition. See (my) comment #16 above for more detail on my setup. As I stated in my original bug report 470184 (now marked as duplicate of this bug), this is not an issue with XFCE4 or Windows on my system. This is only an issue on Plasma X11. The behavior we think started sometime after the 5.26.X? release. LabHamster was working on determining a more definitive release # of when Plasma Shell started to exhibit this behavior. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470444] when compresing operation finishes, dolphin window teleports to current virtual desktop
https://bugs.kde.org/show_bug.cgi?id=470444 Steve Vialle changed: What|Removed |Added CC||stev...@orcon.net.nz --- Comment #1 from Steve Vialle --- This happens when any external application (e.g. firefox download widget -> "show in folder") asks to open a directory, and that directory is open in dolphin on another desktop. The whole dolphin window (including any other open tabs) is pulled to the current desktop. Please provide a way to disable this (and focus/select after context-menu compression in general, and focus after move/copy operation as well), all these behaviours are related, relatively new, and _extremely_ annoying. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467074] When returning from screen energy saving, Plasma forgets that an external screen is connected and doesn't assign it a containment
https://bugs.kde.org/show_bug.cgi?id=467074 --- Comment #19 from Steve --- That would be great detective work LabHamster! I would venture that would be much appreciated by the Plasma team. That would help them immensely in tracking down what changed in Plasma. I can say definitively this is not an issue in Slackware 15.0 (5.23.5) but it is in Slackware current (5.27+). Mine are both x86_64 versions of the distro. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467074] When returning from screen energy saving, Plasma forgets that an external screen is connected and doesn't assign it a containment
https://bugs.kde.org/show_bug.cgi?id=467074 --- Comment #16 from Steve --- FWIW I am including my display configuration. My docking station has 1 display port and 1 HDMI port. It is the display port that goes to my 4-way HDMI switch (via a display-port to HDMI adapter) and ultimately monitor #3 (32-inch LG). The HDMI port feeds monitor #2 directly (DELL 32") and monitor #1 (internal laptop display) is disabled as I keep the laptop lid closed. It is when I temporarily switch out monitor #3 (and back in again) that I lose Plasma shell functionality on that desktop. I am using XFCE4 Desktop for this laptop until this bug is resolved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470184] Dual-monitor PC will not refresh secondary desktop after switching HDMI port in X11
https://bugs.kde.org/show_bug.cgi?id=470184 --- Comment #5 from Steve --- (In reply to Steve from comment #4) > I disagree this is a duplicate of bug 467074. The behavior might be similar > but it is triggered here by a completely different mechanism. That is a > (temporary) hardware disconnection of the secondary monitor - unlike > whatever the trigger is on 467074. After further inspection of bug 467074 I retract the above comment as it could very well be the same issue. My apologies Nate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470184] Dual-monitor PC will not refresh secondary desktop after switching HDMI port in X11
https://bugs.kde.org/show_bug.cgi?id=470184 --- Comment #4 from Steve --- I disagree this is a duplicate of bug 467074. The behavior might be similar but it is triggered here by a completely different mechanism. That is a (temporary) hardware disconnection of the secondary monitor - unlike whatever the trigger is on 467074. -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 470184] Dual-monitor PC will not refresh secondary desktop after switching HDMI port in X11
https://bugs.kde.org/show_bug.cgi?id=470184 --- Comment #2 from Steve --- There is more detail in a discussion on LQ here: https://www.linuxquestions.org/questions/showthread.php?p=6432534=1#post6432534 -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 470184] Dual-monitor PC will not refresh secondary desktop after switching HDMI port in X11
https://bugs.kde.org/show_bug.cgi?id=470184 --- Comment #1 from Steve --- There is a discussion with more detail on LQ here: https://www.linuxquestions.org/questions/showthread.php?p=6432534=1#post6432534 -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 470184] New: Dual-monitor PC will not refresh secondary desktop after switching HDMI port in X11
https://bugs.kde.org/show_bug.cgi?id=470184 Bug ID: 470184 Summary: Dual-monitor PC will not refresh secondary desktop after switching HDMI port in X11 Classification: Plasma Product: Active Window Control Version: unspecified Platform: Slackware OS: Linux Status: REPORTED Keywords: wayland Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: ste...@gmail.com CC: plasma-b...@kde.org 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. Switching secondary monitor out temporarily from a port-replicator switch while keeping primary desktop active. 2. Switch back in secondary monitor/desktop 3. OBSERVED RESULT Wallpaper and Desktop menu are disabled (inactive). Right-click on secondary desktop does not invoke menu. The wallpaper that was set will disappear and turn to a black background. EXPECTED RESULT Wallpaper and Desktop menu should become active after a second or two of refresh time. This errant behavior does not happen on other Desktops such as XFCE and Plasma Full Wayland mode - as well as Windows OS. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Slackware64 (Current)/23.04 & 5.105 (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9_20230412 ADDITIONAL INFORMATION As mentioned this is not an issue in Plasma5 full Wayland mode nor XFCE/X11. Secondary Desktop wallpaper and menu will resume/refresh after a second or two once monitor is reconnected through HDMI port replicator switch in those DE's. I have 4 computers that share the secondary monitor with a common mouse and keyboard. The brand of switch is xtremPro and is a model 4x1 USB HDMI KVM Switch 4K2K. If I use the xrandr binary in a script to temporarily switch the secondary monitor resolution I can get the secondary desktop to refresh. Below is the script: #!/bin/bash xrandr --output DP-2-2 --mode 1600x900 xrandr --output DP-2-2 --mode 1920x1080 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470108] New: Touchscreen zoom not working as expected
https://bugs.kde.org/show_bug.cgi?id=470108 Bug ID: 470108 Summary: Touchscreen zoom not working as expected Classification: Applications Product: okular Version: 23.04.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: cattysteve89...@163.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. On tablets with a touchscreen, use two finger to zoom in or zoom out. OBSERVED RESULT The zoom action also rolls the page. EXPECTED RESULT The zoom action should work as Ctrl + and Ctrl - do. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION None -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 469927] New: Please provide a way to rotate individual pages clockwise or counterclockwise
https://bugs.kde.org/show_bug.cgi?id=469927 Bug ID: 469927 Summary: Please provide a way to rotate individual pages clockwise or counterclockwise Classification: Applications Product: okular Version: 22.12.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: st...@kelem.net Target Milestone: --- SUMMARY Some PDF documents have a few pages oriented differently, e.g., a landscape page rotated so that it will print on a piece of paper in portrait mode. Sometimes pages are upside down. Please provide a way to display a page rotated. I would like to be able to rotate a single page CCW or CW multiple times, until the page is right-side up. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT The pages are displayed the way that they were set up when they were formatted. When printed, the page can be turned physically. However, the displayed image of a page can't be rotated, making it difficult to read. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 6.2.0-20-generic (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.
[KScreen] [Bug 463527] Multi monitor layout no longer save - it always reverts to the previously saved layout (Wayland)
https://bugs.kde.org/show_bug.cgi?id=463527 Steve Therrien changed: What|Removed |Added CC||kdeb...@stevetherrien.ca --- Comment #11 from Steve Therrien --- I had a similar problem with my settings not being saved. My `.local/share/kscreen` files weren't updating either. As a workaround, I created a new local user, configured my screens there, and copied that user's `.local/share/kscreen` files to my account (and fixed ownership of the files) as a workaround to make my laptop usable. I see you mentioned trying it on a fresh account without success though. By chance, today I noticed my `KScreen 2` background service wasn't running. I enabled it and changed my screen configuration, and my `.local/share/kscreen` files updated. Stopping the service stopped the files from being updated, so the two are connected. You'd mentioned disabling that service due to a different problem, but have you tried temporarily enabling it while saving your screen configuration settings? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469772] Keyboard shortcut "CTRL+S" works roughly 50% of the time
https://bugs.kde.org/show_bug.cgi?id=469772 Steve Cossette changed: What|Removed |Added Platform|Other |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469772] New: Keyboard shortcut "CTRL+S" works roughly 50% of the time
https://bugs.kde.org/show_bug.cgi?id=469772 Bug ID: 469772 Summary: Keyboard shortcut "CTRL+S" works roughly 50% of the time Classification: Applications Product: Spectacle Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: farch...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY *** After taking a screenshot, pressing CTRL+S on the keyboard will only work roughly 50% of the time. 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 https://www.youtube.com/watch?v=8p5m3Zq3CaQ (Made a video showing the full walkthrough of the issue) OBSERVED RESULT https://www.youtube.com/watch?v=8p5m3Zq3CaQ (Made a video showing the full walkthrough of the issue) EXPECTED RESULT https://www.youtube.com/watch?v=8p5m3Zq3CaQ (Made a video showing the full walkthrough of the issue) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 23.04.0 (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Distro: Fedora 38 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398458] Places tag hierarchy
https://bugs.kde.org/show_bug.cgi?id=398458 --- Comment #7 from Steve Franks --- (In reply to caulier.gilles from comment #6) > @Steve, > > digiKam 8.0.0 is out. This entry still valid with this release ? > > Best regards > > Gilles Caulier I haven't seen this error in any version since I reported it. Regards Steve -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438203] Progress bar stuck on 100%, Digikam won't allow further actions
https://bugs.kde.org/show_bug.cgi?id=438203 --- Comment #8 from Steve Franks --- (In reply to caulier.gilles from comment #7) > @steve > > digiKam 8.0.0 is out. This entry still valid with this release ? > > Best regards > > Gilles Caulier Another bug fixed. Regards Steve -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435902] Error message "insufficient privileges" on the database...
https://bugs.kde.org/show_bug.cgi?id=435902 --- Comment #13 from Steve Franks --- (In reply to caulier.gilles from comment #12) > @Steve > > digiKam 8.0.0 is out. This entry still valid with this release ? > > Best regards > > Gilles Caulier It is fine now, you may close the bug report. Kind Regards Steve -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468507] Immediate crash
https://bugs.kde.org/show_bug.cgi?id=468507 --- Comment #9 from Steve Cossette --- (In reply to Steve Cossette from comment #8) > Just a headsup, the brand new 1.0.1 version still behaves exactly the same For some reason, this crash doesn't occur on my second machine, so honestly I don't know what to think of this. -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468507] Immediate crash
https://bugs.kde.org/show_bug.cgi?id=468507 --- Comment #8 from Steve Cossette --- Just a headsup, the brand new 1.0.1 version still behaves exactly the same -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468507] Immediate crash
https://bugs.kde.org/show_bug.cgi?id=468507 Steve Cossette changed: What|Removed |Added CC||farch...@gmail.com --- Comment #7 from Steve Cossette --- I am working on building arianna for Fedora. Building the latest 1.0.0 tagged release works, but the latest git fails to start, and crashes with a segfault. Here'S the stack trace: Apr 22 09:01:38 fedora systemd-coredump[6194]: [] Process 6180 (arianna) of user 1000 dumped core. Module liblabsmodelsplugin.so from rpm qt5-qtdeclarative-5.15.9-1.fc38.x86_64 Module libmodelsplugin.so from rpm qt5-qtdeclarative-5.15.9-1.fc38.x86_64 Module libQuickCharts.so from rpm kf5-kquickcharts-5.104.0-1.fc38.x86_64 Module libdeclarative_webchannel.so from rpm qt5-qtwebchannel-5.15.9-1.fc38.x86_64 Module libqtgraphicaleffectsprivate.so from rpm qt5-qtgraphicaleffects-5.15.9-1.fc38.x86_64 Module libqtgraphicaleffectsplugin.so from rpm qt5-qtgraphicaleffects-5.15.9-1.fc38.x86_64 Module libqqc2desktopstyleplugin.so from rpm qqc2-desktop-style-5.104.0-1.fc38.x86_64 Module libwindowplugin.so from rpm qt5-qtdeclarative-5.15.9-1.fc38.x86_64 Module libqtquicktemplates2plugin.so from rpm qt5-qtquickcontrols2-5.15.9-1.fc38.x86_64 Module libqmlplugin.so from rpm qt5-qtdeclarative-5.15.9-1.fc38.x86_64 Module libcomponentsplugin.so from rpm kf5-kirigami2-addons-0.8.0-1.fc38.x86_64 Module libKirigamiPlugin.so from rpm kf5-kirigami2-5.104.0-1.fc38.x86_64 Module libqtlabsplatformplugin.so from rpm qt5-qtquickcontrols2-5.15.9-1.fc38.x86_64 Module libqquicklayoutsplugin.so from rpm qt5-qtdeclarative-5.15.9-1.fc38.x86_64 Module libqtquickcontrols2plugin.so from rpm qt5-qtquickcontrols2-5.15.9-1.fc38.x86_64 Module libQt5QmlWorkerScript.so.5 from rpm qt5-qtdeclarative-5.15.9-1.fc38.x86_64 Module libqtquick2plugin.so from rpm qt5-qtdeclarative-5.15.9-1.fc38.x86_64 Module libKF5Style.so.5 from rpm kf5-frameworkintegration-5.104.0-2.fc38.x86_64 Module libbreezecommon5.so.5 from rpm plasma-breeze-5.27.4-1.fc38.x86_64 Module libKF5Kirigami2.so.5 from rpm kf5-kirigami2-5.104.0-1.fc38.x86_64 Module breeze.so from rpm plasma-breeze-5.27.4-1.fc38.x86_64 Module libpciaccess.so.0 from rpm libpciaccess-0.16-8.fc38.x86_64 Module libtinfo.so.6 from rpm ncurses-6.4-3.20230114.fc38.x86_64 Module libedit.so.0 from rpm libedit-3.1-45.20221030cvs.fc38.x86_64 Module libdrm_intel.so.1 from rpm libdrm-2.4.114-2.fc38.x86_64 Module libdrm_nouveau.so.2 from rpm libdrm-2.4.114-2.fc38.x86_64 Module libdrm_amdgpu.so.1 from rpm libdrm-2.4.114-2.fc38.x86_64 Module libelf.so.1 from rpm elfutils-0.189-1.fc38.x86_64 Module libdrm_radeon.so.1 from rpm libdrm-2.4.114-2.fc38.x86_64 Module radeonsi_dri.so from rpm mesa-23.0.2-2.fc38.x86_64 Module libxshmfence.so.1 from rpm libxshmfence-1.3-12.fc38.x86_64 Module libxcb-sync.so.1 from rpm libxcb-1.13.1-11.fc38.x86_64 Module libxcb-present.so.0 from rpm libxcb-1.13.1-11.fc38.x86_64 Module libxcb-dri3.so.0 from rpm libxcb-1.13.1-11.fc38.x86_64 Module libwayland-server.so.0 from rpm wayland-1.22.0-1.fc38.x86_64 Module libdrm.so.2 from rpm libdrm-2.4.114-2.fc38.x86_64 Module libxcb-xfixes.so.0 from rpm libxcb-1.13.1-11
[digikam] [Bug 452441] After Cancelling Import digikam shows no albums
https://bugs.kde.org/show_bug.cgi?id=452441 --- Comment #15 from Steve Franks --- I will try to repeat the situation and let you know , Steve On Wed, 19 Apr 2023 at 06:58, wrote: > https://bugs.kde.org/show_bug.cgi?id=452441 > > --- Comment #14 from caulier.gil...@gmail.com --- > Hi Steve, > > Any feedback here ? > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468115] digikam 8.0.0-Beta1 hasn't imported tags
https://bugs.kde.org/show_bug.cgi?id=468115 --- Comment #12 from Steve Franks --- That's what I meant, sorry I've been busy and haven't looked at it for a while. I cloned that with SSH, but was denied access when I tried to upload it. I'll try again and let you know exactly what happens. Steve -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468115] digikam 8.0.0-Beta1 hasn't imported tags
https://bugs.kde.org/show_bug.cgi?id=468115 --- Comment #10 from Steve Franks --- Ok, I will download that. I realised that Beta 1 is the version that ‘lost’ exiftool. BTW I said that I would like to help with the manual. I checked it out from GitHub and made some minor changes, but GitHub won’t let me check it back in. I have obviously done something wrong, when I have time I will try again. Regards Steve On Fri, 7 Apr 2023 at 16:33, wrote: > https://bugs.kde.org/show_bug.cgi?id=468115 > > --- Comment #9 from caulier.gil...@gmail.com --- > Forget beta1. last build is available here: > > https://files.kde.org/digikam/ > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468115] digikam 8.0.0-Beta1 hasn't imported tags
https://bugs.kde.org/show_bug.cgi?id=468115 --- Comment #8 from Steve Franks --- Thank you, I’ll download beta1. Regards Steve -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468115] digikam 8.0.0-Beta1 hasn't imported tags
https://bugs.kde.org/show_bug.cgi?id=468115 --- Comment #5 from Steve Franks --- Yes. There’s still a question, why did Digikam ignore Exiftool? The location was correct. Regards Steve -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468115] digikam 8.0.0-Beta1 hasn't imported tags
https://bugs.kde.org/show_bug.cgi?id=468115 --- Comment #3 from Steve Franks --- (In reply to Maik Qualmann from comment #1) > No problem reading the tags here with the digiKam-8.0.0 from git/master. > Since Exiv2 reports an error in the Olympus IFD Makernote header, make sure > ExifTool is running in your version. > Also check the Advanced Metadata Settings for tags and reset the list to the > default settings if necessary. > You also write something from XMP files, also check the settings for > sidecars, whether reading is activated. > > Maik All settings appear to be correct. None have changed from 7.10. Changing location of Exiftool cured the problem and it continues to be OK when the location is changed back. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468115] digikam 8.0.0-Beta1 hasn't imported tags
https://bugs.kde.org/show_bug.cgi?id=468115 Steve Franks changed: What|Removed |Added CC||steve...@gmail.com --- Comment #2 from Steve Franks --- Created attachment 157865 --> https://bugs.kde.org/attachment.cgi?id=157865=edit Screenshot showing idle Exiftool Two instances of Exiftool, one using 0% CPU -- You are receiving this mail because: You are watching all bug changes.
[KXStitch] [Bug 453208] Manuel KXStitch en français
https://bugs.kde.org/show_bug.cgi?id=453208 Steve Allewell changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468115] New: digikam 8.0.0-Beta1 hasn't imported tags
https://bugs.kde.org/show_bug.cgi?id=468115 Bug ID: 468115 Summary: digikam 8.0.0-Beta1 hasn't imported tags Classification: Applications Product: digikam Version: 8.0.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Maintenance-Metadata Assignee: digikam-bugs-n...@kde.org Reporter: steve...@gmail.com Target Milestone: --- Created attachment 157814 --> https://bugs.kde.org/attachment.cgi?id=157814=edit Sample JPEG where tags are not shown SUMMARY *** I transferred images tagged in 7.10 to another PC where I'm exploring digikam 8.0.0. None of the JPEG images imported (Tools|Maintenance| Find New Files) have tags. My Linux PC running 8.0.0 shows the correct tags. *** STEPS TO REPRODUCE 1. Tag images. 2. Copy images and xmp files to new PC. 3. Read new files. OBSERVED RESULT digikam 7.10 shows 0 images without tags, 8.0 has 635 images without tags. EXPECTED RESULT Tags identical on both systems. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION XMP File contents:- http://www.w3.org/1999/02/22-rdf-syntax-ns#;> http://ns.adobe.com/exif/1.0/; xmlns:digiKam="http://www.digikam.org/ns/1.0/; xmlns:lr="http://ns.adobe.com/lightroom/1.0/; xmlns:tiff="http://ns.adobe.com/tiff/1.0/; xmlns:xmp="http://ns.adobe.com/xap/1.0/; xmlns:photoshop="http://ns.adobe.com/photoshop/1.0/; xmlns:dc="http://purl.org/dc/elements/1.1/; exif:ExifVersion="0231" exif:FlashpixVersion="0100" exif:ColorSpace="1" exif:ExposureTime="1/1000" exif:FNumber="110/10" exif:ExposureProgram="2" exif:ExposureBiasValue="0/10" exif:MaxApertureValue="1024/256" exif:MeteringMode="3" exif:LightSource="0" exif:FocalLength="150/1" exif:FileSource="3" exif:CFAPattern="2 0 2 0 0 1 1 2" exif:CustomRendered="0" exif:ExposureMode="0" exif:WhiteBalance="0" exif:DigitalZoomRatio="100/100" exif:SceneCaptureType="0" exif:GainControl="0" exif:Contrast="0" exif:Saturation="0" exif:Sharpness="0" tiff:ImageWidth="5240" tiff:ImageLength="3912" tiff:Compression="1" tiff:PhotometricInterpretation="1" tiff:Orientation="1" tiff:SamplesPerPixel="1" tiff:PlanarConfiguration="1" tiff:XResolution="300/1" tiff:YResolution="300/1" tiff:ResolutionUnit="2" tiff:Make="OLYMPUS CORPORATION" tiff:Model="E-M5MarkIII " tiff:Software="Version 1.7" xmp:ModifyDate="2023-03-24T14:09:26" xmp:CreateDate="2023-03-24T14:09:26" photoshop:DateCreated="2023-03-24T14:09:26"> 200 Places/Holidays/Malta Places Places/Holidays Places|Holidays|Malta Places Places|Holidays 16 Steve Franks 2022 Steve Franks -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467941] [Fedora Distupgrade using Discover] Update progress unavailable
https://bugs.kde.org/show_bug.cgi?id=467941 --- Comment #2 from Steve Cossette --- So, I've checked and it seems discover doesn'T really do update notification completion, so if anything, I can create a separate suggestion ticket about this. Though I think there should still be a "Downloading (5%)" in the progress bar or something to show the user how the update is progressing. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467941] [Fedora Distupgrade using Discover] Update progress unavailable
https://bugs.kde.org/show_bug.cgi?id=467941 --- Comment #1 from Steve Cossette --- Created attachment 157707 --> https://bugs.kde.org/attachment.cgi?id=157707=edit Update Progress -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467941] [Fedora Distupgrade using Discover] Update progress unavailable
https://bugs.kde.org/show_bug.cgi?id=467941 Steve Cossette changed: What|Removed |Added Summary|[Fedora Distupgrade using |[Fedora Distupgrade using |Discover] Minor UI issue|Discover] Update progress ||unavailable -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467941] New: [Fedora Distupgrade using Discover] Minor UI issue
https://bugs.kde.org/show_bug.cgi?id=467941 Bug ID: 467941 Summary: [Fedora Distupgrade using Discover] Minor UI issue Classification: Applications Product: Discover Version: 5.27.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updates (interactive) Assignee: plasma-b...@kde.org Reporter: farch...@gmail.com CC: aleix...@kde.org Target Milestone: --- Installed the new plasma that allows for updating using Discover from Fedora 37 to Fedora 38 (From here: https://copr.fedorainfracloud.org/coprs/aleasto/discover-distro-upgrade/packages/) Distro upgrade occurs in the background, but the discover UI seems to fail to show more information, or a decent estimation. The progress bar seems to be about accurate though. Shouldn't there be some kind of popup after it completed, to tell the user that it completed and a reboot is required to apply? The "More information" button is also greyed out and does nothing except make the update information smaller. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 316734] After waking the system, the desktop gets displayed for a moment before the lock screen appears
https://bugs.kde.org/show_bug.cgi?id=316734 Steve Vialle changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||stev...@orcon.net.nz --- Comment #73 from Steve Vialle --- This is still occuring as of plasma 5.27.3 Reopening this rather than creating yet another duplicate. If you want a new bug, I can do that too. This problem has been (re)appearing for 10 years now. Was/is this ever going to be fixed properly, and permanently *on X11*? As requested some time ago: > please check dmesg after a suspend cycle for messages related to drm? Dmesg snip from suspend -> resume cycle: https://bpa.st/O5ATM ^ | grep -i drm: [drm] PCIE GART of 512M enabled (table at 0x00800030). [drm] PSP is resuming... [drm] reserve 0xa0 from 0x82fd00 for PSP TMR [drm] DMUB hardware initialized: version=0x02020017 [drm] kiq ring mec 2 pipe 1 q 0 [drm] VCN decode and encode initialized successfully(under DPG Mode). [drm] JPEG decode initialized successfully. > try whether the issue also persist on a Wayland session. No. I do not have wayland or anything related to it installed, nor do I intend to. > I would like every affected user to report: > * Distribution and version > * Mesa version > * Hardware (which CPU and GPU) Gentoo current (2.13) Mesa 23.0.0 CPU: Intel I9-10900KF GPU: AMD Radeon RX 6700 XT Anything else you need? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467341] krunner shortcut as meta broken
https://bugs.kde.org/show_bug.cgi?id=467341 Steve Cossette changed: What|Removed |Added CC||farch...@gmail.com --- Comment #1 from Steve Cossette --- I get the same thing here, by following the same steps as @kinghat. Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.7-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62,7 GiB of RAM Graphics Processor: AMD Radeon RX 6900 XT -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 445652] /var/lib/PackageKit/offline-update-action file not deleted automatically, causing Discover to always suggest a reboot
https://bugs.kde.org/show_bug.cgi?id=445652 Steve Steiner changed: What|Removed |Added CC||sstein...@gmail.com --- Comment #10 from Steve Steiner --- This is flagged for Fedora RPMs, but this issue also occurs on: Operating System: Ubuntu 22.10 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-35-generic (64-bit) Discover 5.25.5 Deleted specified file, problem went away. This started when a kernel update was successfully applied, I rebooted as suggested, but the file, apparently, didn't get reset. Been driving me nuts... -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 422088] Can't type in Wayland
https://bugs.kde.org/show_bug.cgi?id=422088 Steve changed: What|Removed |Added Ever confirmed|1 |0 Status|CONFIRMED |REPORTED --- Comment #15 from Steve --- Applied todays 5 meg update, from Fedora Discovery still no joy on K-Touchif the name is double clicked it takes you to the program but allows no input. The only response is a flashing blue circle around the F Key.Fedora 37 SilverBlue Kinoite -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 422088] Can't type in Wayland
https://bugs.kde.org/show_bug.cgi?id=422088 Steve changed: What|Removed |Added Platform|Archlinux |Flatpak -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 422088] Can't type in Wayland
https://bugs.kde.org/show_bug.cgi?id=422088 Steve changed: What|Removed |Added CC||sbra...@gmail.com --- Comment #14 from Steve --- Same issue on Fedora 37 SilverBlue Kinoiteusing KTouch 22.12.3 Released 2023-03-02. The suggested fix is unclear so wasn't applied -- You are receiving this mail because: You are watching all bug changes.
[kde-inotify-survey] [Bug 466366] New: "Communication not allowed" on /usr/share/dbus-1/system.d/org.kde.kded.inotify.conf
https://bugs.kde.org/show_bug.cgi?id=466366 Bug ID: 466366 Summary: "Communication not allowed" on /usr/share/dbus-1/system.d/org.kde.kded.inotify.conf Classification: Plasma Product: kde-inotify-survey Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: farch...@gmail.com CC: sit...@kde.org Target Milestone: --- When using rpmlint on the built package, the following error is brought up: kde-inotify-survey.x86_64: E: communication not allowed /usr/share/dbus-1/system.d/org.kde.kded.inotify.conf I noticed that file is not in the sources, so I'm guessing it's generated along the way. That error is also ambiguous, so I opened an issue upstream for rpmlint: https://github.com/rpm-software-management/rpmlint/issues/1008#issuecomment-1443989082 If this could be fixed, that would be great! Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kde-inotify-survey] [Bug 466322] New: Translations are not wired in the build file
https://bugs.kde.org/show_bug.cgi?id=466322 Bug ID: 466322 Summary: Translations are not wired in the build file Classification: Plasma Product: kde-inotify-survey Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: farch...@gmail.com CC: sit...@kde.org Target Milestone: --- Building kde-inotify-survey doesn't seem to be building any translations. Does it maybe need to be wired in the build file? I'm using the release obtained directly through here: https://invent.kde.org/system/kde-inotify-survey/-/releases -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442901] GTK4 apps have double scaling on hidpi
https://bugs.kde.org/show_bug.cgi?id=442901 --- Comment #46 from Steve Vialle --- (In reply to Luca Bacci from comment #45) > We fixed the issue of unscaled XWayland apps for KDE > 5.27.1, but unfortunately I had to cut out the part which properly reads > Xft.DPI due to the imminence of the 5.27.1 release. So, IOW, "We hurriedly worked around the latest GTK crazy, at the expense of breaking both manual DPI settings in X11 and our own fonts control module."? :raisedeyebrow: GTK4+HiDPI really that special, huh? WIP, got it, cool, and thanks. Guess I'll just keep my xsettingsd.conf immutable and out of plasmas meddling paws while I look forward to the _real_ fix. If we need a new bug report to track this (as it's not really about GTK4 any more), cool. I'm not convinced this one deserves a "fixed" tag when the "fix" introduces additional regressions though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442901] GTK4 apps have double scaling on hidpi
https://bugs.kde.org/show_bug.cgi?id=442901 --- Comment #44 from Steve Vialle --- Additional quick tests: Setting Xft.dpi to 82 in /etc/X11/Xresources -> plasma/QT/GTK all 96DPI. Setting "DPI" "82x82" in /etc/X11/xorg.conf.d/foo.conf -> plasma runs at 96DPI. Setting "Force fonts DPI to 82 in fonts KCM -> plasma runs at 96DPI. _Please_ stop overriding my settings. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442901] GTK4 apps have double scaling on hidpi
https://bugs.kde.org/show_bug.cgi?id=442901 Steve Vialle changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #43 from Steve Vialle --- Not only is this still not fixed WRT DPI <96, the situation is now _worse_ than it was with 5.27.0. GTK3 and QT/KDE fonts are now the same DPI, so that's something... But that DPI is 96, and _everything_ is huge. It appears "force fonts DPI" is now being ignored altogether, and plasma is setting Xft.dpi to 96 unconditionally. xsettingsd.conf as of 5.27.1: Xft/DPI 98304 Gdk/UnscaledDPI 98304 Again, this is an _82_ DPI display, and that information is both readily available and manually provided in the fonts KCM. 5.27.0: ~ $ xdpyinfo | grep -B2 resolution screen #0: dimensions:1920x1080 pixels (594x334 millimeters) resolution:82x82 dots per inch ~ $ xrdb -query | grep dpi Xft.dpi:82 5.27.1: ~ $ xdpyinfo | grep -B2 resolution screen #0: dimensions:1920x1080 pixels (594x334 millimeters) resolution:82x82 dots per inch ~ $ xrdb -query | grep dpi Xft.dpi:96 No software or config changes on my end besides updating plasma. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466207] Crash right after start/login
https://bugs.kde.org/show_bug.cgi?id=466207 --- Comment #1 from Steve Cossette --- Clarification: This happens everytime the app is started. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466207] New: Crash right after start/login
https://bugs.kde.org/show_bug.cgi?id=466207
Bug ID: 466207
Summary: Crash right after start/login
Classification: Applications
Product: NeoChat
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: General
Assignee: fe...@posteo.de
Reporter: farch...@gmail.com
CC: c...@carlschwan.eu
Target Milestone: ---
Application: neochat (23.01)
Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.11-200.fc37.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora release 37 (Thirty Seven)"
DrKonqi: 5.27.0 [KCrashBackend]
-- Information about the crash:
Right after logging in/starting Neochat, maybe at most two minutes later, the
app crashes.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: NeoChat (neochat), signal: Segmentation fault
[KCrash Handler]
#4 0x7f54f12dce24 in Quotient::Connection::userId() const () from
/lib64/libQuotient.so.0.7
#5 0x55a58bacdd1d in
QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) ()
#6 0x7f54ef8d0e96 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#7 0x7f54f12d5db1 in Quotient::Connection::Private::completeSetup(QString
const&) () from /lib64/libQuotient.so.0.7
#8 0x7f54f12fa89b in
QtPrivate::QFunctorSlotObject(QString const&, std::nullopt_t const&, char const (&)
[1], QByteArray const&, QString const&, QString const&)::{lambda()#1}, 0,
QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) () from /lib64/libQuotient.so.0.7
#9 0x7f54ef8d0e96 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#10 0x7f54f12bf7d6 in Quotient::BaseJob::success(Quotient::BaseJob*) ()
from /lib64/libQuotient.so.0.7
#11 0x7f54f13546a1 in Quotient::BaseJob::finishJob() () from
/lib64/libQuotient.so.0.7
#12 0x7f54ef8d0e96 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#13 0x7f54f0e0a2d8 in QNetworkReplyHttpImplPrivate::finished() () from
/lib64/libQt5Network.so.5
#14 0x7f54ef8c8134 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#15 0x7f54f05aed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#16 0x7f54ef89d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#17 0x7f54ef8a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#18 0x7f54ef8eeb07 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#19 0x7f54ee916cbf in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#20 0x7f54ee96c598 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#21 0x7f54ee913f40 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#22 0x7f54ef8ee5fa in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#23 0x7f54ef89bf3a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#24 0x7f54ef8a4002 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#25 0x55a58b9897a5 in main ()
[Inferior 1 (process 102828) detached]
The reporter indicates this bug may be a duplicate of or related to bug 465143.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 442901] GTK4 apps have double scaling on hidpi
https://bugs.kde.org/show_bug.cgi?id=442901 Steve Vialle changed: What|Removed |Added CC||stev...@orcon.net.nz Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #32 from Steve Vialle --- As of plasma 5.27.0, this change breaks GTK font scaling on systems where display DPI <96. This is most notable in firefox. Inspecting generated ~.config/xsettingsd/xsettingsd.conf shows: Gdk/UnscaledDPI 98304 Where 98304/1024 = 96 That's 96DPI folks, I don't know where plasma is getting it but it's flat-out wrong on this system. This is an _82DPI_ display, as reported by: X11 / GPU driver / Monitor EDID: AMDGPU(0): DPI set to (82, 82) xdpyinfo: resolution:82x82 dots per inch xrdb: Xft.dpi:82 A frickin' ruler and a calculator. On top of that, "force fonts DPI" is set to 82 in the fonts KCM. Setting 'Gdk/UnscaledDPI 83968' in xsettingsd.conf (1024x82) and marking that file immutable so plasma can't screw with it restores correct font scaling in GTK3 applications. If plasma is going to pass this setting to xsettingsd, it should _at least_ respect the setting of "force fonts DPI" in the fonts KCM. Ideally that setting should be entirely unnecessary anyway, as there is a perfectly good autodetected value available from X11. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 465675] kompare version 22.12.2
https://bugs.kde.org/show_bug.cgi?id=465675 --- Comment #2 from Steve Riches --- OK I just opened compare.doc with Kwrite and can see tons of control characters - not exactly binary - but I hear you. You must get a lot of reports like mine. I would suggest modifying that terse message I received when running Kompare to say something like your own msg to me or comparing apples to oranges or something like that. Thanks for your response. Steve On Mon, Feb 13, 2023 at 1:28 PM Kevin Kofler wrote: > https://bugs.kde.org/show_bug.cgi?id=465675 > > Kevin Kofler changed: > >What|Removed |Added > > > Status|REPORTED|RESOLVED > Resolution|--- |NOT A BUG > > --- Comment #1 from Kevin Kofler --- > .doc files are binary files and cannot be compared with Kompare. The error > message is by design. > > .docx and .odt files are also binary files because they are compressed. > You can > try using a flat .odtf, which is uncompressed XML, but the diff between a > text > file and the ODT flat XML will also be mostly useless because all lines > will be > different. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 465675] New: kompare version 22.12.2
https://bugs.kde.org/show_bug.cgi?id=465675 Bug ID: 465675 Summary: kompare version 22.12.2 Classification: Applications Product: kompare Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kompare-de...@kde.org Reporter: sriche...@gmail.com Target Milestone: --- Created attachment 156195 --> https://bugs.kde.org/attachment.cgi?id=156195=edit two simple files: one is txt from kwrite and the other is .doc from libre 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. Run Kompare: compare.txt vs compare.doc 2. 3. OBSERVED RESULT Could not parse diff output EXPECTED RESULT I expected to be shown the way libre expresses quotations vs the way kwrite expresses quotations SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 37 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464851] New: Ejecting vs unmounting ISO image confusing
https://bugs.kde.org/show_bug.cgi?id=464851 Bug ID: 464851 Summary: Ejecting vs unmounting ISO image confusing Classification: Applications Product: dolphin Version: 22.12.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plugins: ISO mounting Assignee: kwon-young.c...@hotmail.fr Reporter: spzaku...@gmail.com CC: kfm-de...@kde.org 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. Right click an ISO in Dolphin and mount it 2. Right click on the now mounted ISO in the sidebar- choose Eject, Unmount, or click the eject symbol 3. Go back to the folder where you actually mounted the ISO from and right click, choosing "Unmount". OBSERVED RESULT The ISO is "ejected" in Step 2, but the icon still shows in the sidebar, with no way to remove it. Step 3 actually unmounts and clears the icon from the sidebar. EXPECTED RESULT In Step 2, the icon should be removed from the sidebar- especially if the text says "Unmount". SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION It's a bit confusing why ejecting/unmounting from the sidebar is different from right clicking the ISO and unmounting. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 462542] HTML Gallery behaves oddly
https://bugs.kde.org/show_bug.cgi?id=462542 --- Comment #16 from Steve Franks --- Created attachment 154431 --> https://bugs.kde.org/attachment.cgi?id=154431=edit dbgview log Windows 10 digikam 7.10.0 This is the debug view log captured whilst generating HTML Gallery 20110720 Varne. Windows 10 digikam 7.10.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 462542] HTML Gallery behaves oddly
https://bugs.kde.org/show_bug.cgi?id=462542 Steve Franks changed: What|Removed |Added Attachment #154302|0 |1 is obsolete|| --- Comment #15 from Steve Franks --- Created attachment 154429 --> https://bugs.kde.org/attachment.cgi?id=154429=edit Small HTML Gallery showing an album and a tag This is the HTML gallery from 7.10.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 462542] HTML Gallery behaves oddly
https://bugs.kde.org/show_bug.cgi?id=462542 --- Comment #14 from Steve Franks --- I downloaded 7.10.0 debug for Windows and have attached the DebugView output. The reason that there were no images for the galleries created for albums in my earlier po0sts, is that the tool doesn't include sub-folders. If a lowest level Album (sub-folder) is selected the the output contains a link for the Album and a Link for the Tag (see attached). Steve On Wed, 7 Dec 2022 at 11:36, Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=462542 > > --- Comment #13 from Maik Qualmann --- > Git commit c1a9acf506c95e093fd1ec328580d067ecb8b098 by Maik Qualmann. > Committed on 07/12/2022 at 11:36. > Pushed by mqualmann into branch 'master'. > > add test debug for Windows > > M +2-0 > core/dplugins/generic/tools/htmlgallery/generator/gallerygenerator.cpp > M +4-0core/libs/database/coredb/coredbnamefilter.cpp > > > https://invent.kde.org/graphics/digikam/commit/c1a9acf506c95e093fd1ec328580d067ecb8b098 > > -- > You are receiving this mail because: > You reported the bug. > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 462542] HTML Gallery behaves oddly
https://bugs.kde.org/show_bug.cgi?id=462542 --- Comment #12 from Steve Franks --- I couldn’t get either to work, as I expected, but the appimage did produce output for both the selected album and tag. Is it possible to capture all of the debugging output including that from the Create HTML Gallery tool? Steve On Wed, 7 Dec 2022 at 09:27, Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=462542 > > Maik Qualmann changed: > >What|Removed |Added > > > Status|RESOLVED|REOPENED > Resolution|FIXED |--- > > --- Comment #11 from Maik Qualmann --- > I tested it again here on Windows with digiKam-8.0.0 and albums and tags > don't > work. Since it works on Linux I suspect something path specific, I'll take > a > look. > > Maik > > -- > You are receiving this mail because: > You reported the bug. > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 462542] HTML Gallery behaves oddly
https://bugs.kde.org/show_bug.cgi?id=462542 --- Comment #10 from Steve Franks --- I agree that a gallery is created which shows all photos with the selected tag. Isn’t the output supposed to be just images in the selected album(s) that have that tag? If you run the gallery creation tool again it seems to be impossible to remove tags, or albums, which were used on previous occasions. I’m not able to capture the output displayed by the HTML Gallery tool and I don’t know how to capture all of the output from digikam in terminal. At most a few hundred lines can be copied after digikam closes. How does one save all output? Thanks Steve -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 462542] HTML Gallery behaves oddly
https://bugs.kde.org/show_bug.cgi?id=462542 --- Comment #9 from Steve Franks --- I discovered this running 7.8.0 under Windows 10, it is the same in 7.9.0 and I attached dbgView output to a previous email. My Linux PC is misbehaving, it frequently refuses to start, but if I can make it work I will send the debug output. Do you need jpeg output, or should I disable it to save space ( export QT_LOGGING_RULES="digikam*=true;jpeg=false"}? Steve On Sun, 4 Dec 2022 at 12:25, Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=462542 > > --- Comment #8 from Maik Qualmann --- > Tested here with the AppImage, no problems. Selecting a tag provides the > corresponding images in the gallery. > > Enable debug output in the terminal with: export > QT_LOGGING_RULES="digikam*=true" > > Post the output from the terminal of creating the HTML gallery. > > Maik > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 462542] HTML Gallery behaves oddly
https://bugs.kde.org/show_bug.cgi?id=462542 --- Comment #7 from Steve Franks --- digikam-7.9.0-20221202T144203-x86-64-debug.appimage running under MX Linux is similar. One or more albums must be selected before filtering by tags (Album 2012 which contains 2012-01-January to 2012-12-December. Tag Insects/Butterfly/Glanville Fritillary [/ indicates tag hierachy ]) The output shows all images that have the tag and the album page(s) are empty. See attached output from HTML Gallery creator when 20 Steve -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453937] Plasma duplicating desktop icons (files, folders, shortcuts)
https://bugs.kde.org/show_bug.cgi?id=453937 --- Comment #19 from steve --- (In reply to Nate Graham from comment #18) > This should be fixed in Plasma 5.27 (aka current git master) as of various > ports and fixes. Looking forward to February 2023 then. Recently it seems like it is creating more phantoms, could be subjective. I'm on 5.26.4. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 462542] HTML Gallery behaves oddly
https://bugs.kde.org/show_bug.cgi?id=462542 --- Comment #6 from Steve Franks --- I found the problem whilst using 7.8.0 on my Windows 10 PC. I downloaded and installed 7.9.0 and the problem persists. I’m not sure what a virtual album is. Each album on my system relates to a top-level folder on my hard drive. Steve On Fri, 2 Dec 2022 at 22:26, Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=462542 > > Maik Qualmann changed: > >What|Removed |Added > > > Status|CONFIRMED |RESOLVED > Resolution|--- |FIXED >Version Fixed In||8.0.0 > > --- Comment #5 from Maik Qualmann --- > Since the problem cannot be reproduced with the current digiKam-7.9.0 > AppImage, > I assume, based on the error messages from plugins, that you are using > digiKam-7.8.0. This partly uses libraries from digiKam-8.0.0 due to a > packing > error. The problem is fixed for digiKam-8.0.0. > > Maik > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 377399] kontact loses imap connections constantly
https://bugs.kde.org/show_bug.cgi?id=377399 --- Comment #4 from Steve --- I can't reproduce this with the current release. I needed help a long time ago. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 462542] HTML Gallery behaves oddly
https://bugs.kde.org/show_bug.cgi?id=462542 Steve Franks changed: What|Removed |Added CC||steve...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 462542] New: HTML Gallery behaves oddly
https://bugs.kde.org/show_bug.cgi?id=462542 Bug ID: 462542 Summary: HTML Gallery behaves oddly Classification: Applications Product: digikam Version: 7.9.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: steve...@gmail.com Target Milestone: --- Created attachment 154223 --> https://bugs.kde.org/attachment.cgi?id=154223=edit dbgview log file 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 *** HTML Gallery tool doesn't filter images correctly. The first Album selected is remembered for subsequence calls to the tool after it was deselected. When an Album is selected, if a Tag is also selected the tool processes images that are not in that album. STEPS TO REPRODUCE 1. Start Tools|Create HTML Gallery. Choose albums on the first dialog, select an album and go through all steps to create a gallery. Close, then restart the HTML Gallery Tool, Select Albums on the first screen. When you click Next any Albums selected previously are still selected. Deselect any previous albums and select a different one. 2. Select Tag(s) on the Tag Tab. Continue to select options as required. 3. On the final dialog click Next to create an HTML Gallery. OBSERVED RESULT When you finish the steps the display changes to show the process of the gallery generation. Notice that although only a single album was selected the display shows 2 albums are being processed. When you examine the output there are no images in the selected album and the tag section of the gallery shows images that have the tag, but are outside the selected album. EXPECTED RESULT 1) Previously selected albums are NOT processed. 2) Images within the selected album are filtered by the tag. i.e. Only images within that album, not all images in all albums which have been allocated that tag. In the example that I used, there are 24 images in 2022, with the tag "Red Admiral", but the output HTML Gallery has 58 HTML pages and 836 images. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 384546] Generated killer sudoku puzzle with multiple valid solutions (ksudoku 1.3)
https://bugs.kde.org/show_bug.cgi?id=384546 --- Comment #5 from Steve Soule --- You're right, of course. I don't know what I was thinking. I'm sorry for wasting your time. -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 384546] Generated killer sudoku puzzle with multiple valid solutions (ksudoku 1.3)
https://bugs.kde.org/show_bug.cgi?id=384546 Steve Soule changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Steve Soule --- Your demand that I reproduce the bug is not reasonable, since that would require a random number generator to produce precisely the same values as it did before. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 377982] Kontact sometimes fails to delete an email
https://bugs.kde.org/show_bug.cgi?id=377982 --- Comment #2 from Steve --- No, I can't reproduce it. I needed help many years ago. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 377979] akonadi_mailfilter_agent is filling up my syslog
https://bugs.kde.org/show_bug.cgi?id=377979 --- Comment #3 from Steve --- No, I can't reproduce it. I needed help many years ago. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 377590] kontact mail is unresponsive
https://bugs.kde.org/show_bug.cgi?id=377590 --- Comment #2 from Steve --- No, I can't reproduce it. I needed help many years ago. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 378172] akonadi keeps losing track of emails
https://bugs.kde.org/show_bug.cgi?id=378172 --- Comment #3 from Steve --- No, I can't reproduce it. I needed help many years ago. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461251] Can't install Skanlite after upgrade to 22.04
https://bugs.kde.org/show_bug.cgi?id=461251 --- Comment #1 from Steve Zakulec --- Think I figured out what was going on- libpoppler-glib8 was getting blocked by a small number of packages I had on my system from 20.04 (possibly Wine-related packages). Once I tried installing libpoppler-glib8 from a command prompt with "sudo pkcon install libpoppler-glib8", I was asked if it was okay if some packages were deleted in order for libpoppler-glib8 to install itself. Once I said yes, the package installed, and then skanlite had no problems installing. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461251] New: Can't install Skanlite after upgrade to 22.04
https://bugs.kde.org/show_bug.cgi?id=461251 Bug ID: 461251 Summary: Can't install Skanlite after upgrade to 22.04 Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: spzaku...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY After upgrading to Neon 22.04, Skanlite was removed, and can't be reinstalled due to missing dependencies. STEPS TO REPRODUCE 1. Search for Skanlite in Discover 2. Click install 3. Notice error messages going by OBSERVED RESULT Skanlite isn't installed due to missing dependencies EXPECTED RESULT*** Skanlite installs without issue, pulling in any missing dependencies automatically. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION I chose to remove all packages that could be auto-removed during the upgrade process. Here's the output from trying to install the package using apt: sudo apt install skanlite [sudo] password for steve: Reading package lists... Done Building dependency tree... Done Reading state information... Done Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) libsane1:amd64 < none -> 1.1.1-5 @un puN Ib > Broken libsane1:amd64 Depends on libpoppler-glib8:amd64 < none | 22.09.0-0xneon+22.04+jammy+release+build3 @un uH > (>= 0.18.0) Considering libpoppler-glib8:amd64 0 as a solution to libsane1:amd64 3 Considering libpoppler-glib8:amd64 0 as a solution to libsane1:amd64 3 Considering libpoppler-glib8:amd64 0 as a solution to libsane1:amd64 3 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libsane1 : Depends: libpoppler-glib8 (>= 0.18.0) but it is not going to be installed E: Unable to correct problems, you have held broken packages. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460941] Not finding new items in Album Folders
https://bugs.kde.org/show_bug.cgi?id=460941 --- Comment #3 from Steve Franks --- I did this on an old i7 Desktop, which only has 8gb RAM. digikam doesn't appear to run out of memory, so I don't know why it failed. The second run died at about 57%, so I changed the environment variable to activate debug; started dbugview; then restarted digikam. Of course this time it ran perfectly and finished importing new items. It's an annoying fault, which also occurs on my even older Lubuntu desktop. I will henceforth always run dbugview, with digikam, even though it slows everything down. At least if it happens again I can give you a debug log. Thanks Steve On Mon, 24 Oct 2022 at 18:02, Steve Franks wrote: > I tried several times. > > In the end I removed the album from the collection and restarted digikam > and added the folder again. That prompted a complete rescan, which is now > running. > > I will do as you suggested, if it happens again. > > Thanks > > Steve > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > Windows > > > > *From: *Maik Qualmann > *Sent: *24 October 2022 15:00 > *To: *steve...@gmail.com > *Subject: *[digikam] [Bug 460941] Not finding new items in Album Folders > > > > https://bugs.kde.org/show_bug.cgi?id=460941 > > > > Maik Qualmann changed: > > > >What|Removed |Added > > > > > CC||metzping...@gmail.com > > > > --- Comment #1 from Maik Qualmann --- > > The scanner for new elements works very reliably, if new ones are available > > they would be added. Check whether the rights of the folders and files are > > readable for digiKam. Otherwise we need a DebugView log. > > > > Maik > > > > -- > > You are receiving this mail because: > > You reported the bug. > > > -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460274] Windows don't display properly since Neon Plasma 5.26 Update
https://bugs.kde.org/show_bug.cgi?id=460274 Steve Allen changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460941] Not finding new items in Album Folders
https://bugs.kde.org/show_bug.cgi?id=460941 --- Comment #2 from Steve Franks --- I tried several times. In the end I removed the album from the collection and restarted digikam and added the folder again. That prompted a complete rescan, which is now running. I will do as you suggested, if it happens again. Thanks Steve Sent from Mail[1] for Windows *From: * Maik Qualmann[2] *Sent: *24 October 2022 15:00 *To: * steve...@gmail.com[3] *Subject: *[digikam] [Bug 460941] Not finding new items in Album Folders https://bugs.kde.org/show_bug.cgi?id=460941 Maik Qualmann changed: What |Removed |Added CC| |metzping...@gmail.com --- Comment #1 from Maik Qualmann --- The scanner for new elements works very reliably, if new ones are available they would be added. Check whether the rights of the folders and files are readable for digiKam. Otherwise we need a DebugView log. Maik -- You are receiving this mail because: You reported the bug. 1. https://go.microsoft.com/fwlink/?LinkId=550986 2. mailto:bugzilla_nore...@kde.org 3. mailto:steve...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460941] New: Not finding new items in Album Folders
https://bugs.kde.org/show_bug.cgi?id=460941 Bug ID: 460941 Summary: Not finding new items in Album Folders Classification: Applications Product: digikam Version: 7.8.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Albums-Engine Assignee: digikam-bugs-n...@kde.org Reporter: steve...@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 *** digikam isn't finding new items after being interrupted. STEPS TO REPRODUCE 1. Add new collection 2. Close digikam whilst automatic scanning of files is in progress 3. start digikam again OBSERVED RESULT The program restarts scanning for new items, but stops before completing the process. Running 'Maintenance Scan for New Items' does not complete the scan of all folders. I have folders for each year from 1999 to 2022, each contains folders for the months in that year. When I stopped digikam it was processing 2014. When restarted it processed more of 2014, but nothing after June 2014. The last time I ran it, it finished in a few minutes and does not appeared to have found more items. EXPECTED RESULT All relevant files in the Collection would be added to the collection and be visible in albums. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460274] Windows don't display properly since Neon Plasma 5.26 Update
https://bugs.kde.org/show_bug.cgi?id=460274 --- Comment #9 from Steve Allen --- That's really helpful, thanks. Moving the config worked a treat. Seems its regenerated and windows are appearing as normal. Will miss Bismuth tiling, hopefully the depends issue with the 20.04 base will get sorted next release, or the bismuth dev will find a fix Thanks for your help, is there anything I can provide (from my old kwinrc) that may be helpful? On Wed, 12 Oct 2022, 09:46 Vlad Zahorodnii, wrote: > https://bugs.kde.org/show_bug.cgi?id=460274 > > --- Comment #8 from Vlad Zahorodnii --- > (In reply to Steve Allen from comment #6) > > Actually output is `--no entries--` > > > > Is there a way to backup and clear my Kwin settings (e.g decoration etc) > > back to default? > > Yes, copy or move ~/.config/kwinrc somewhere > > -- > You are receiving this mail because: > You reported the bug. > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460274] Windows don't display properly since Neon Plasma 5.26 Update
https://bugs.kde.org/show_bug.cgi?id=460274 --- Comment #7 from Steve Allen --- If I create a new user, login with that user (to see if its my user setting causing issues) cycles the ssdm loginscreen -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460274] Windows don't display properly since Neon Plasma 5.26 Update
https://bugs.kde.org/show_bug.cgi?id=460274 --- Comment #6 from Steve Allen --- Actually output is `--no entries--` Is there a way to backup and clear my Kwin settings (e.g decoration etc) back to default? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460274] Windows don't display properly since Neon Plasma 5.26 Update
https://bugs.kde.org/show_bug.cgi?id=460274 --- Comment #5 from Steve Allen --- I will struggle to cut/pates logs. I only have my phone and the laptop (which I can only use the tty on) with me I won't be able to ssh in from my desktop until friday. Is there anything I should be looking for in the logs? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460274] Windows don't display properly since Neon Plasma 5.26 Update
https://bugs.kde.org/show_bug.cgi?id=460274 --- Comment #3 from Steve Allen --- Not a script, but I did use kwin-bismuth, but uninstalled that to rule it out. I wonder if the windows are trying to tile / kwin is trying to use bismuth decoration even though bismuth is not installed anymore? The first window I open flashes up very quickly (in a tiny square) then disappears. If I login to tty3 I get `error org.freedesktop.Dbus.Error.UnknownMethod` `No such method 'supportinformation' in any interface at object path 'KWin' (signature '')` I need to set up ssh access to the machine to help with cut/pasting commands and errors. There is more stuff I've tried here: https://www.reddit.com/r/kdeneon/comments/y1dei8/so_that_update_broke_erm_everything/irzhj2j?utm_medium=android_app_source=share=3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460274] Windows don't display properly since Neon Plasma 5.26 Update
https://bugs.kde.org/show_bug.cgi?id=460274 --- Comment #1 from Steve Allen --- I should note that it doesn't matter whether loginnis with x11 or wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460274] Windows don't display properly since Neon Plasma 5.26 Update
https://bugs.kde.org/show_bug.cgi?id=460274 Steve Allen changed: What|Removed |Added CC||stephenalle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460274] New: Windows don't display properly since Neon Plasma 5.26 Update
https://bugs.kde.org/show_bug.cgi?id=460274 Bug ID: 460274 Summary: Windows don't display properly since Neon Plasma 5.26 Update Classification: Plasma Product: kwin Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: stephenalle...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Login to KDE Neon 2. Launch "wallpaper settings" by right click on dektop 3. Launch any other application (Dolphin, Firefox, Emacs etc) OBSERVED RESULT When doing (2) the wallpaper settings window displays correctly, and is floating with a blue border When doing 3 no window, or a fullscreen black window, appears. EXPECTED RESULT Windows of applications to display. SOFTWARE/OS VERSIONS KDE Plasma: updated with the 11 10 22 update to plasma 5 26 -- You are receiving this mail because: You are watching all bug changes.
[KXStitch] [Bug 459868] Tools: Bug and Feature Requests
https://bugs.kde.org/show_bug.cgi?id=459868 --- Comment #1 from Steve Allewell --- Thank you for reporting these issues and suggestions, sometimes a quick question to the mailing list may have answered a number of these points. The Tools>Draw function will produce full cross stitches for lines unless the 'Configure KXStitch' setting Editor>Tools>'Tools Fractionals' is enabled, in which case it will produce a line using stitches that best fit the line and these are often quarter or half stitches. This is similar to the setting Import>'Use Fractionals' which, when enabled will use fractional stitches when importing images instead of just full stitches. I don't intend to change this behaviour as you suggested. The pasting functionality is by design as it may well be desirable to replicate the whitespace (background) into the pasted area. There is merge functionality built in by pressing and holding the shift key before releasing the mouse button or pressing [Enter] if using the keyboard to move the pattern being pasted. I have realised this is not documented, so my apologies for that and I will update accordingly, possibly even adding a tooltip or a setting that allows merge as a user default. Feature requests: - Select to do more : can you elaborate on what you would like to see here. - The current tools in the page setup allow you to create whatever page layout that you want and is fully documented. If there is something else that you would like to see, please provide more detail. - I can look at adding shading to overlapped cells. Regards -- You are receiving this mail because: You are watching all bug changes.
