[kwin] [Bug 489444] New: Overview doesn't work on NVIDIA 555; key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
https://bugs.kde.org/show_bug.cgi?id=489444 Bug ID: 489444 Summary: Overview doesn't work on NVIDIA 555; key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Classification: Plasma Product: kwin Version: 6.1.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: ja...@jamesnorth.net Target Milestone: --- SUMMARY I just updated both my NVIDIA drivers to 555 and KDE Plasma to 6.1.1. When I press SUPER+W to trigger the Overview, nothing happens. If I spam SUPER+W, the Overview will appear eventually. STEPS TO REPRODUCE 1. Try to open Overview with SUPER+W OBSERVED RESULT Nothing happens. In journalctl -r, I get this logspam: ``` Jun 30 02:15:13 archalpha kwin_wayland_wrapper[1161]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Jun 30 02:15:13 archalpha kwin_wayland_wrapper[1161]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Jun 30 02:15:13 archalpha kwin_wayland_wrapper[1161]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Jun 30 02:15:13 archalpha kwin_wayland_wrapper[1161]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Jun 30 02:15:13 archalpha kwin_wayland_wrapper[1161]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Jun 30 02:15:12 archalpha kwin_wayland_wrapper[1161]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Jun 30 02:15:12 archalpha kwin_wayland_wrapper[1161]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Jun 30 02:15:12 archalpha kwin_wayland_wrapper[1161]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Jun 30 02:15:12 archalpha kwin_wayland_wrapper[1161]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Jun 30 02:15:12 archalpha kwin_wayland_wrapper[1161]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Jun 30 02:15:10 archalpha kwin_wayland[1048]: qt.svg: :1:14112: Could not resolve property: #linearGradient10962 Jun 30 02:15:09 archalpha kwin_wayland_wrapper[1161]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Jun 30 02:15:09 archalpha kwin_wayland_wrapper[1161]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Jun 30 02:15:09 archalpha kwin_wayland_wrapper[1161]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! ``` EXPECTED RESULT The overview appears. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.9.7-arch1-1 (64-bit)/6.1.1 (available in About System) KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489306] Turning off Virtual Desktop switching animations does not affect Overview
https://bugs.kde.org/show_bug.cgi?id=489306 James North changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from James North --- Fair enough. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489306] New: Turning off Virtual Desktop switching animations does not affect Overview
https://bugs.kde.org/show_bug.cgi?id=489306 Bug ID: 489306 Summary: Turning off Virtual Desktop switching animations does not affect Overview Classification: Plasma Product: kwin Version: 6.1.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: ja...@jamesnorth.net Target Milestone: --- SUMMARY When I turn off "Show animation when switching" in the Virtual Desktop settings, I can now instantly switch desktops. But when I hit SUPER+W to bring up the overview effect and switch desktops, it still slides. I like most animations in KDE but this transition is jarring whether it's slide or fade, so I only turn this animation off. It would be nice if switching desktops was instantaneous in the Overview effect too. * For "Fade Desktop, see macOS Mission Control with Reduce Motion on for prior art. * For it being disabled, see GNOME's Overview with Reduce Animations for prior art. STEPS TO REPRODUCE 1. Go to Virtual Desktops and turn off Show animation when switching 2. Use the Overview effect and switch desktops OBSERVED RESULT The sliding animation still occurs. EXPECTED RESULT The switch should be instantaneous SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.9.6 (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION It'd be good if the Fade Desktop effect also reflected in the Overview for people who use that :) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 489276] Compressor/Expander: MLT: "[filter avfilter.compand ] Cannot set sink channel counts"
https://bugs.kde.org/show_bug.cgi?id=489276 --- Comment #2 from James North --- Downgraded to 1cb1ee7399bfe45491b57fc56df5999a2e1f93ba9fea76c664b87116d821f0c6 flatpak commit for now, which does not exhibit this bug. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 489276] Compressor/Expander: MLT: "[filter avfilter.compand ] Cannot set sink channel counts"
https://bugs.kde.org/show_bug.cgi?id=489276 --- Comment #1 from James North --- Happens on the Flatpak too. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 489276] New: Compressor/Expander: MLT: "[filter avfilter.compand ] Cannot set sink channel counts"
https://bugs.kde.org/show_bug.cgi?id=489276 Bug ID: 489276 Summary: Compressor/Expander: MLT: "[filter avfilter.compand ] Cannot set sink channel counts" Classification: Applications Product: kdenlive Version: 24.05.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: ja...@jamesnorth.net Target Milestone: --- SUMMARY When I add the Compressor/Expander effect to a clip and try to play it, it tells me: qml: Add effect: avfilter.compand XML parsing of "avfilter.compand" . found 5 parameters QLocale: Default value is QVariant(double, 0) parsed: "0" QLocale: Default value is QVariant(double, 0.8) parsed: "0.8" QLocale: Default value is QVariant(double, 0.01) parsed: "0.01" QLocale: Default value is QVariant(double, 0) parsed: "0" QLocale: Default value is QVariant(double, 0) parsed: "0" END parsing of "avfilter.compand" . Number of found parameters 5 // GOT CLIP STACK DATA CHANGE: QList(308) // GOT CLIP STACK DATA CHANGE DONE: QModelIndex(1,0,0x19,TimelineItemModel(0x57141e96f320)) = QList(308) MUTEX LOCK loadEffects COUNT: 2 MUTEX UNLOCK loadEffects deleting collapsibleeffectview MLT: "[filter avfilter.compand ] Cannot set sink channel counts" MLT: "[filter avfilter.compand ] Cannot set sink channel counts" STEPS TO REPRODUCE 1. Add Compressor/Expander effect to a clip 2. Try to play the clip OBSERVED RESULT The effect has no effect. EXPECTED RESULT The effect works. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.9.6-arch1-1 (64-bit)/Wayland (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Using: * mlt 7.24.0-3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489227] Focus moves to window on another screen when desktop is empty
https://bugs.kde.org/show_bug.cgi?id=489227 --- Comment #4 from James North --- It also happens with the Focus Follows Mouse option for me (what I was using before this bug started happening). It even happens with Click to Focus despite the window in the other monitor not being focused when opening the terminal on the wrong monitor. To reproduce this, here's what I'm doing: * I am on Virtual Desktop 1. * Firefox is pinned on Monitor 2. There is another Firefox window on Monitor 1, VD 1. * I switch to VD 3, which has no windows on monitor 1 but the pinned window on Monitor 2. * I hit CTRL+ALT+T to bring up my Alacritty terminal, and it appears on Monitor 2 despite the window on Monitor 2 not being visually focused (i.e. the window decorations are grey and faded). The weird thing is, the window on Monitor 2 *is* visually focused (no grey window decorations) when I perform the same procedure with any Window activation policy but while Separate screen focus is disabled. If it's enabled, the visual focus goes away, but that doesn't seem to mean anything. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489227] Focus moves to window on another screen when desktop is empty
https://bugs.kde.org/show_bug.cgi?id=489227 --- Comment #2 from James North --- Nope. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489227] New: Focus moves to window on another screen when desktop is empty
https://bugs.kde.org/show_bug.cgi?id=489227 Bug ID: 489227 Summary: Focus moves to window on another screen when desktop is empty Classification: Plasma Product: kwin Version: 6.1.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: ja...@jamesnorth.net Target Milestone: --- SUMMARY I have three monitors. Ever since 6.1, whenever I try to open an application on an empty desktop, it opens on the wrong monitor. I have Focus Follows Mouse (mouse precedence) set. Despite my cursor being on monitor 1, the application opens on monitor 2. STEPS TO REPRODUCE 1. Switch to an empty virtual desktop on your primary monitor, or close an application on the current desktop so that it's completely empty, but make sure there's a window on your second monitor. The window may need to be Pinned to all desktops. 2. Open an application with a keyboard shortcut (e.g. your terminal with CTRL+ALT+T) OBSERVED RESULT The focus moves to the window on the other monitor once on an empty desktop on monitor 1, and the window opens on the wrong monitor. EXPECTED RESULT The window opens on the monitor under my cursor, which *should* be focused. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch/6.1.0/Wayland (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489215] New: Overview effect doesn't show desktops if there are two rows
https://bugs.kde.org/show_bug.cgi?id=489215 Bug ID: 489215 Summary: Overview effect doesn't show desktops if there are two rows Classification: Plasma Product: kwin Version: 6.1.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: ja...@jamesnorth.net Target Milestone: --- SUMMARY If I add two rows of virtual desktops, when I bring up the Overview effect, it doesn't show my desktops at the top. It only shows if I have one row of desktops. STEPS TO REPRODUCE 1. Use two rows of virtual desktops 2. Use the overview effect OBSERVED RESULT I can't see my desktops in the top row. EXPECTED RESULT I should be able to see my desktops in one row. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475721] KDE session doesn't start when attempting to login (applying kscreen config failed!)
https://bugs.kde.org/show_bug.cgi?id=475721 --- Comment #2 from James North --- Hi, If I get around to testing this particular machine again, it's not going to be for quite a long time. What I can say is that I've been running the last versions of the KDE 5.x series and now the 6.x series since October on Arch Linux with the same hardware, and I have never experienced this issue. Several years ago, I used to get this same issue on Arch Linux when I used KDE, but not when I went back to KDE the past few months. Sorry, I guess it would be better to close this issue, and if I use Fedora and face it again, I'll re-open it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457636] Feature to map pen buttons to keys / sequence of keys or commands
https://bugs.kde.org/show_bug.cgi?id=457636 James North changed: What|Removed |Added CC||ja...@jamesnorth.net --- Comment #12 from James North --- Created attachment 168122 --> https://bugs.kde.org/attachment.cgi?id=168122=edit Plasma Wayland 6.0.3 Drawing Tablet KCM I'm a little confused on the status of this. I have a Cintiq so I don't have any Tablet Buttons, only the buttons on my stylus. I can't evaluate whether that has been done, but comments from 2022 suggest they have been. When I look at the Drawing Tablet KCM in Plasma 6.0.3, I see three "Tool Buttons". This seems pretty similar to the X KCM screenshot Nicolas Fella provided. However, there is no image of the Stylus on the Wayland KCM. The image is really useful, because it clearly displays where on the stylus the Buttons are located. I need to guess on Wayland. Additionally, I can't seem to find a way to bind the Tool Buttons to mouse presses like Middle Mouse button or Left Mouse button as shown in Nicolas Fella's X screenshot: https://bugs.kde.org/attachment.cgi?id=151209 So: * Need a graphic of the pen with button numbers labelled * Need to be able to map mouse presses to stylus I think that's it? I've uploaded an attachment of what the current settings look like in 6.0.3. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458949] [Desktop grid] effect cannot be activated until Slide effect's animation ends
https://bugs.kde.org/show_bug.cgi?id=458949 James North changed: What|Removed |Added CC||ja...@jamesnorth.net Version|5.25.5 |6.0.3 --- Comment #3 from James North --- I've been experiencing this bug on Plasma 6.0.3. It's quite annoying, as the animation seems to last an extra second after the desktop has finished sliding, making it seem like the shortcut for the overview effect just doesn't work reliably. Experienced on Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475653] Primary monitor is switched when coming back from suspend/rebooting
https://bugs.kde.org/show_bug.cgi?id=475653 --- Comment #12 from James North --- Alright, I tried with the 29th October build of KDE Neon, and finally got it working. Had to workaround it to get the installer working, but nonetheless. After launching Wayland, plasmashell immediately crashed. System settings also wouldn't launch, so I can't set my display configuration up and setup display scaling. Running `systemsettings` from Konsole gets me: > systemsettings: error while loading shared libraries: libKF6Kirigami2.so.6: > cannot open shared object file: No such file or directory On the plus side, it detected my primary monitor correctly the first time. I suspended, and when I came back, the primary monitor was still detected correctly. So, issue fixed maybe? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475653] Primary monitor is switched when coming back from suspend/rebooting
https://bugs.kde.org/show_bug.cgi?id=475653 --- Comment #11 from James North --- The installer failed after about 20 seconds, which is probably not a good sign. The ISO I downloaded was from a week ago, so maybe it's fixed now. I'll see if I can download the latest KDE Neon Unstable ISO and try that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475653] Primary monitor is switched when coming back from suspend/rebooting
https://bugs.kde.org/show_bug.cgi?id=475653 --- Comment #10 from James North --- Sorry for the late response. Awful week. I *tried* to run the Live ISO for KDE Neon Unstable, but it defaults to X11 in the live session and won't let me choose Wayland. For some reason, the graphics processor in About this System is detected as NV166 despite being a NVIDIA RTX 2060S. I'll see if I can find a secondary drive somewhere to install it on. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475653] Primary monitor is switched when coming back from suspend/rebooting
https://bugs.kde.org/show_bug.cgi?id=475653 --- Comment #9 from James North --- Thanks for the info, Nate. I'll give Unstable a try in a live session soon. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475653] Primary monitor is switched when coming back from suspend/rebooting
https://bugs.kde.org/show_bug.cgi?id=475653 --- Comment #6 from James North --- Checking ~/.local/share/kscreen, I see my three sets of config files for my displays. First, in a file in the root directory (DP-2 and HDMI-A-1), then in the outputs directory (HDMI-1 and DP-3), and then in the control/configs directory (HDMI-1 and DP-3). I can't see any configuration files here though: ~/config/plasma-org.kde.plasma.desktop-appletsrc ~/config/plasmashellrc As for trying Plasma 6...this might be beyond me. There doesn't appear to be an existing AUR package, so I'll probably need to compile it from source. The basic warnings seem simple enough but the actual instructions seem to be here: https://invent.kde.org/sdk/kdesrc-build/-/tree/master#quick-howto And those aren't too bad either, although I think they leave out the final step of actually running Plasma 6... Maybe it'd be best to try KDE Neon on an external SSD: https://neon.kde.org/download Is the Testing Edition Plasma 6? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475653] Primary monitor is switched when coming back from suspend/rebooting
https://bugs.kde.org/show_bug.cgi?id=475653 --- Comment #2 from James North --- I am able to reliably reproduce this display shuffling bug whenever resuming from suspend. (In reply to Michael Butash from comment #1) > Every time my displays change, KDE chooses random ID's for them (DP-1, DP-3, > DP-5), and it wreaks havoc on things. I suspect yours might be similar. > Until someone makes wayland far more deterministic around display ID's, I > suspect kde will remain a basketcase for multi-monitor. Where are you seeing these IDs? I couldn't find anything in plasmashellrc. > After a while, I find KDE builds like 50 different display configs for them > each time it changes randomly, which seems to just confuse the hell out of > things. Per Nate Graham, clearing them fixed things, but they start building > up with the shuffling again over time, and each time clearing them makes my > life better since learning this, which I've done periodically over a bit > since figuring this out. You probably should as well with hot plugging your > second display probably causes similar. Where do I find these display configs to clear out? By "hot plugging", do you mean unplugging the monitor while the system is running? Because these monitors are permanently plugged in. For some reason, my graphics tablet is usually detected as the main monitor by Linux-based systems by default (I don't know about other operating systems). The Arch Linux install media reliably detected my graphics tablet as the main monitor and formatted the console as 1920x1080, leaving a very large space on my 4K monitor completely black. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475662] Failed to put system to sleep. System resumed again
https://bugs.kde.org/show_bug.cgi?id=475662 --- Comment #3 from James North --- Another piece of information that may prove important: I don't have any normal swap on this machine. I'm using zram managed by zram-generator: https://wiki.archlinux.org/title/Zram#Using_zram-generator I just noticed this note: > Hibernating to swap on zram is not supported, even when zram is configured > with a backing device on permanent storage. logind will protect against > trying to hibernate to a swap space on zram. Now, I'm not trying to hibernate. I'm trying to suspend/sleep. And it works currently. This seemed important to mention however. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475721] New: KDE session doesn't start when attempting to login (applying kscreen config failed!)
https://bugs.kde.org/show_bug.cgi?id=475721 Bug ID: 475721 Summary: KDE session doesn't start when attempting to login (applying kscreen config failed!) Classification: Plasma Product: kwin Version: 5.27.8 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: ja...@jamesnorth.net Target Milestone: --- SUMMARY This issue relates to the two weeks I spent on Fedora 38 KDE. Every time I rebooted my computer, I couldn’t login to KDE, even after waiting 2 hours. Usually, it’s just a black screen for 2-3 minutes, but the last time, I couldn’t login at all. I can’t show you the full logs as I couldn't get to a desktop on this machine, but journalctl -r spams: kwin_core: Applying Kscreen config failed! I also saw: kwin_wayland_drm: Failed to create gamma blob! Invalid argument I have a NVIDIA RTX 2060S card and I was attempting to log in to KDE Wayland. I just updated via Discover before rebooting, which performed an offline update. STEPS TO REPRODUCE 1. Reboot the computer. 2. Ty to login. OBSERVED RESULT I see a black screen for over 2 hours with nothing happening, and the KDE session never starts. EXPECTED RESULT I can login and the session starts. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 38 (Oct 15th) (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.111.0 Qt Version: 5.15 ADDITIONAL INFORMATION Sorry for not being able to provide specific versions. I uninstalled Fedora because of this recurrent issue, but I thought I should report it as it is quite a severe error. As such, I'm not available to troubleshoot it because this doesn't occur on Arch Linux. I ran into several other bugs related to KDE/KDE programs that aren't present on Arch and documented them but unsure whether I should report them because I'm no longer using the system... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475662] Failed to put system to sleep. System resumed again
https://bugs.kde.org/show_bug.cgi?id=475662 --- Comment #2 from James North --- In the four times I've suspended/rebooted my computer since filing this bug, I have not been able to reproduce it yet. A reboot is what allowed me to suspend again initially. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475662] Failed to put system to sleep. System resumed again
https://bugs.kde.org/show_bug.cgi?id=475662 --- Comment #1 from James North --- Additionally, when it comes back from suspend, the primary monitors are switched as I reported here: https://bugs.kde.org/show_bug.cgi?id=475653 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475662] New: Failed to put system to sleep. System resumed again
https://bugs.kde.org/show_bug.cgi?id=475662
Bug ID: 475662
Summary: Failed to put system to sleep. System resumed again
Classification: Plasma
Product: kwin
Version: 5.27.8
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: core
Assignee: kwin-bugs-n...@kde.org
Reporter: ja...@jamesnorth.net
Target Milestone: ---
SUMMARY
I'm attempting to put my KDE Wayland session on NVIDIA to sleep. I've tried
three times, but it just keeps waking up! I've tried clicking sleep from the
menu, and I've tried sudo systemctl suspend. No dice.
Here is some of journalctl -r:
Oct 16 00:23:31 archalpha kmix[4738]: org.kde.kmix: No such icon
"audio-card-pci"
Oct 16 00:23:31 archalpha kmix[4738]: org.kde.kmix: No such icon
"audio-card-pci"
Oct 16 00:23:31 archalpha plasmashell[4546]: org.kde.plasma.pulseaudio: No
object for name "alsa_output.pci-_2d_00.1.hdmi-stereo.monitor"
Oct 16 00:23:31 archalpha plasmashell[4546]: org.kde.plasma.pulseaudio: No
object for name "alsa_output.pci-_2f_00.4.iec958-stereo.monitor"
Oct 16 00:23:31 archalpha rtkit-daemon[732]: Recovering from system lockup, not
allowing further RT threads.
Oct 16 00:23:31 archalpha rtkit-daemon[732]: Supervising 0 threads of 0
processes of 0 users.
Oct 16 00:23:31 archalpha rtkit-daemon[732]: Recovering from system lockup, not
allowing further RT threads.
Oct 16 00:23:31 archalpha rtkit-daemon[732]: Supervising 0 threads of 0
processes of 0 users.
Oct 16 00:23:31 archalpha rtkit-daemon[732]: Recovering from system lockup, not
allowing further RT threads.
Oct 16 00:23:31 archalpha rtkit-daemon[732]: Supervising 0 threads of 0
processes of 0 users.
Oct 16 00:23:31 archalpha rtkit-daemon[732]: Recovering from system lockup, not
allowing further RT threads.
Oct 16 00:23:31 archalpha rtkit-daemon[732]: Supervising 0 threads of 0
processes of 0 users.
Oct 16 00:23:31 archalpha rtkit-daemon[732]: Recovering from system lockup, not
allowing further RT threads.
Oct 16 00:23:31 archalpha rtkit-daemon[732]: Supervising 0 threads of 0
processes of 0 users.
Oct 16 00:23:31 archalpha wireplumber[928]: PipeWire's BlueZ SPA missing or
broken. Bluetooth not supported.
Oct 16 00:23:31 archalpha wireplumber[928]: SPA handle 'api.bluez5.enum.dbus'
could not be loaded; is it installed?
Oct 16 00:23:31 archalpha systemd[1]: systemd-suspend.service: Failed with
result 'exit-code'.
Oct 16 00:23:31 archalpha systemd[1]: systemd-suspend.service: Main process
exited, code=exited, status=1/FAILURE
Oct 16 00:23:31 archalpha kwin_wayland[4426]: kwin_core: Applying KScreen
config failed!
Oct 16 00:23:31 archalpha kwin_wayland[4426]: kwin_core: Applying KScreen
config failed!
Oct 16 00:23:31 archalpha kwin_wayland[4426]: kwin_core: Applying KScreen
config failed!
Oct 16 00:23:31 archalpha kwin_wayland[4426]: kwin_core: Applying KScreen
config failed!
Oct 16 00:23:31 archalpha kwin_wayland[4426]: kwin_core: Applying KScreen
config failed!
Oct 16 00:23:31 archalpha kwin_wayland[4426]: kwin_core: Applying KScreen
config failed!
Oct 16 00:23:31 archalpha kwin_wayland[4426]: kwin_core: Applying KScreen
config failed!
Oct 16 00:23:31 archalpha kwin_wayland[4426]: kwin_core: Could not find window
with uuid "{cf203a26-beed-47b2-bbcb-04248de21b0b}"
Oct 16 00:23:31 archalpha kwin_wayland[4426]: kwin_core: Could not find window
with uuid "{cf203a26-beed-47b2-bbcb-04248de21b0b}"
Oct 16 00:23:31 archalpha kwin_wayland[4426]: kwin_core: Could not find window
with uuid "{cf203a26-beed-47b2-bbcb-04248de21b0b}"
Oct 16 00:23:31 archalpha kwin_wayland[4426]: kwin_core: Applying KScreen
config failed!
Oct 16 00:23:31 archalpha kwin_wayland[4426]: kwin_core: Applying KScreen
config failed!
Oct 16 00:23:31 archalpha kwin_wayland[4426]: kwin_core: Applying KScreen
config failed!
Oct 16 00:23:31 archalpha kwin_wayland[4426]: kwin_core: Applying KScreen
config failed!
Oct 16 00:23:31 archalpha kscreenlocker_greet[16354]: qt.qpa.wayland: Wayland
does not support QWindow::requestActivate()
Oct 16 00:23:31 archalpha kscreenlocker_greet[16354]: qt.qpa.wayland: Wayland
does not support QWindow::requestActivate()
Oct 16 00:23:31 archalpha kwin_wayland[4426]: kwin_core: Applying KScreen
config failed!
Oct 16 00:23:31 archalpha kwin_wayland[4426]: kwin_core: Applying KScreen
config failed!
Oct 16 00:23:31 archalpha kwin_wayland[4426]: kwin_wayland_drm: Atomic modeset
commit failed! Permission denied
Oct 16 00:23:29 archalpha rtkit-daemon[732]: Demoted 0 threads.
Oct 16 00:23:29 archalpha rtkit-daemon[732]: Demoting known real-time threads.
Oct 16 00:23:29 archalpha systemd-sleep[16464]: Failed to put system to sleep.
System resumed again: Device or resource busy
Oct 16 00:23:29 archalpha rtkit-daemon[732]: The canary thread is apparently
starving. Taking action.
Oct 16 00:23:29 archalpha kernel: PM: suspend exit
Oct 16 00:23:29 archalpha kernel:
[kwin] [Bug 475653] New: Primary monitor is switched when coming back from suspend/rebooting
https://bugs.kde.org/show_bug.cgi?id=475653 Bug ID: 475653 Summary: Primary monitor is switched when coming back from suspend/rebooting Classification: Plasma Product: kwin Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: ja...@jamesnorth.net Target Milestone: --- SUMMARY I have two monitors. I set one of the monitors as the primary display, but when the computer wakes up again, the monitor is switched (often, I'm not sure if this is always the case). I then need to set the other monitor back to primary and the taskbar will move back. I experienced this issue on Fedora, but recently moved to Arch Linux and am still facing this issue. I have a NVIDIA card, and am running Wayland. My second monitor uses a HDMI port but is converted to DisplayPort before being plugged into my GPU. My monitor uses HDMI. There is nothing in my ~/.config/plasmashellrc related to Screen Connectors. This command produces no output: grep -A4 tors ~/.config/plasmashellrc Output of inxi -GSxxz --vs: inxi 3.3.30-00 (2023-09-25) System: Kernel: 6.5.7-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 13.2.1 Desktop: KDE Plasma v: 5.27.8 tk: Qt v: 5.15.11 wm: kwin_wayland dm: SDDM Distro: Arch Linux Graphics: Device-1: NVIDIA TU106 [GeForce RTX 2060 SUPER] vendor: Gigabyte driver: nvidia v: 535.113.01 arch: Turing pcie: speed: 8 GT/s lanes: 16 ports: active: none off: DP-2,HDMI-A-1 empty: DP-1,DP-3 bus-ID: 2d:00.0 chip-ID: 10de:1f06 Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.2.1 compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting alternate: fbdev,nouveau,nv,vesa gpu: nvidia d-rect: 2880x1620 display-ID: 0 Monitor-1: DP-2 pos: bottom-r res: 960x540 size: N/A Monitor-2: HDMI-A-1 pos: primary,top-left res: 1920x1080 size: N/A API: EGL v: 1.5 platforms: gbm: drv: nvidia API: OpenGL v: 4.6.0 vendor: nvidia v: 535.113.01 glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 display-ID: :1.0 API: Vulkan v: 1.3.264 surfaces: xcb,xlib,wayland device: 0 type: discrete-gpu driver: nvidia device-ID: 10de:1f06 STEPS TO REPRODUCE 1. Set a display as the primary monitor 2. Suspend or reboot the computer 3. Watch as the other display is selected as the primary monitor and the taskbar moves to the other monitor. OBSERVED RESULT My primary monitor changes. EXPECTED RESULT My primary monitor remains my primary monitor in perpetuity. SOFTWARE/OS VERSIONS Linux: 6.5.7-arch1-1 Kernel (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION I'm using Wayland with my NVIDIA GPU. The second monitor is a Wacom Cintiq graphics tablet. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426627] Ability re-arrange existing virtual desktops
https://bugs.kde.org/show_bug.cgi?id=426627 Alan North changed: What|Removed |Added CC||alanscode...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469898] New: Regional settings issue - defaults to American English
https://bugs.kde.org/show_bug.cgi?id=469898 Bug ID: 469898 Summary: Regional settings issue - defaults to American English Classification: Applications Product: systemsettings Version: 5.24.7 Platform: Kubuntu OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_users Assignee: plasma-b...@kde.org Reporter: len.no...@outlook.com.au CC: uhh...@gmail.com Target Milestone: --- Created attachment 159035 --> https://bugs.kde.org/attachment.cgi?id=159035=edit System Information Screenshot 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 *** My Location is Western Australia UCT+8hrs. My time is correct but an update has changed all Regional Language settings to UCT -8hrs STEPS TO REPRODUCE 1. AstroPhotos show date taken as tomorrow, 8 hours ahead of actual capture time 2. I cannot reset regional language settings as all choices default to UCT -8hrs 3. Wish it would work on horse racing... OBSERVED RESULT I cannot correct it, Regional language just defaults to -8 hrs. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 22.04 (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.
[kdenlive] [Bug 469029] Cant Drag and Drop ANY Clips to Timeline
https://bugs.kde.org/show_bug.cgi?id=469029 --- Comment #5 from James North --- Had another computer to test this on—GNOME 44 running Wayland. Drag-and-drop works on this one. All computers running Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 469029] Cant Drag and Drop ANY Clips to Timeline
https://bugs.kde.org/show_bug.cgi?id=469029 James North changed: What|Removed |Added CC||ja...@jamesnorth.net --- Comment #4 from James North --- Another user with the same issue. See this thread on KDE Discuss for users with the same issue; all using GNOME: https://discuss.kde.org/t/cannot-drag-and-drop-any-clip-from-project-bin-to-timeline/1113/10 In turn, this forum points back to GNOME's bugtracker: https://gitlab.gnome.org/GNOME/mutter/-/issues/2715 I can reproduce it on my GNOME 44 X11 desktop, but not Sway. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 259917] the simulate option cannot be selected and the 'remove image' option is greyed out
https://bugs.kde.org/show_bug.cgi?id=259917 North changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #11 from North --- Reported, reported, reported. I no longer have a cd reader. Go away. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 466286] Ekos does not return my saved Indi Preferences at next startup
https://bugs.kde.org/show_bug.cgi?id=466286 --- Comment #1 from Len North --- MY Location is always correct, except when it places all targets below the horizon. This was fixed by Jasem at my request years ago The QSI does not remember my camera temperature, cooling ramps, This occurred when cooling ramps were introduced. WCS degrees Rotation and observer name always show empty. Solver is never enabled, I often re-enable it 5 or 6 times during startup - then it's good til I do a meridian flip and we start again. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 466286] New: Ekos does not return my saved Indi Preferences at next startup
https://bugs.kde.org/show_bug.cgi?id=466286 Bug ID: 466286 Summary: Ekos does not return my saved Indi Preferences at next startup Classification: Applications Product: kstars Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: astroga...@westnet.com.au Target Milestone: --- Created attachment 156630 --> https://bugs.kde.org/attachment.cgi?id=156630=edit Starting with Astrometry, Default configuration loaded last. It's not what I Saved. 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 appear to be getting default configurations overwriting my saved preferences in the Indi Control Panel as shown by the attached text. This problem has been better defined for me by the help of Forum members, especially Frederick Ruegsegger on #90756 "For my part, this has been fiddly from time to time - particularly during configuration of a new or revised profile." Fred has defined this well, and since I commenced doing Bug reporting on Nightly Builds I have have reloaded the Linux PC with 3 new OS and now run an exclusive Kubuntu SSD drive only - each time I blame my system as my KStars Ver 3.5.7 has none of the Fatal issues I am now finding with a new build. STEPS TO REPRODUCE 1. An Mature KStars is annoying sometimes, but not with fatal crashes. 2. A new build is difficult to configure each night for imaging, hours are lost in the setup. 3. The logs show the configuration information, but the text entered below the Indi Control Panels indicate that My Saved Configurations may be being overwritten by system default configurations. OBSERVED RESULT New Builds of any KStars on a new OS are not stable. They stabilize over time. EXPECTED RESULT Without a 'Portable and Editable Configuration File Backup' confirming my preferances, then I'm just getting a factory default setting in my preferances SOFTWARE/OS VERSIONS: Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-60-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 31.3 GiB of RAM Graphics Processor: llvmpipe ADDITIONAL INFORMATION Would you please consider a USB drive backup / restore file system where we could just reload all our details, equipment, optial trains and preferances? Thanks -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 259917] the simulate option cannot be selected and the 'remove image' option is greyed out
https://bugs.kde.org/show_bug.cgi?id=259917 North changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 259917] the simulate option cannot be selected and the 'remove image' option is greyed out
https://bugs.kde.org/show_bug.cgi?id=259917 --- Comment #8 from North --- Reported -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465605] Solver, Guiding and Exposure timeout on KStars Ver 3.6.4 Beta
https://bugs.kde.org/show_bug.cgi?id=465605 --- Comment #4 from Len North --- I have just downloaded a log file and the file on my computer has a column of ... barcode like information, but the check file I looked at does not. My question, are you receiving the complete file, am I doing something wrong? Len -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465605] Solver, Guiding and Exposure timeout on KStars Ver 3.6.4 Beta
https://bugs.kde.org/show_bug.cgi?id=465605 --- Comment #3 from Len North --- No further logs available, sorry Len -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465605] Solver, Guiding and Exposure timeout on KStars Ver 3.6.4 Beta
https://bugs.kde.org/show_bug.cgi?id=465605 --- Comment #2 from Len North --- Created attachment 156165 --> https://bugs.kde.org/attachment.cgi?id=156165=edit Guiding_Issues-Lost_track_of_the_guide_Star -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465605] Solver, Guiding and Exposure timeout on KStars Ver 3.6.4 Beta
https://bugs.kde.org/show_bug.cgi?id=465605 --- Comment #1 from Len North --- Created attachment 156164 --> https://bugs.kde.org/attachment.cgi?id=156164=edit Solver issues 0052 hrs event -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465605] New: Solver, Guiding and Exposure timeout on KStars Ver 3.6.4 Beta
https://bugs.kde.org/show_bug.cgi?id=465605 Bug ID: 465605 Summary: Solver, Guiding and Exposure timeout on KStars Ver 3.6.4 Beta Classification: Applications Product: kstars Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: astroga...@westnet.com.au Target Milestone: --- Created attachment 156163 --> https://bugs.kde.org/attachment.cgi?id=156163=edit Description and screenshots 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 *** Solver, Guiding and Exposure timeout on KStars Ver 3.6.4 Beta As per summary with screenshots and log files STEPS TO REPRODUCE 1. Installed a clean Kubuntu OS 2. Downloaded Nightly build - it was only a few hours old 3. Only using StellarMate OS: v1.7.5 Stable, Model SM-110, on an Rpi 4B-4GB from previous nights OBSERVED RESULT One hour of excellence, then solver, guiding and Exposure timeout issues EXPECTED RESULT KStars ver 3.6.4 beta worked better for me SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-60-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 680/PCIe/SSE2 ADDITIONAL INFORMATION Major fault - good night but no pics - and it was a great learning opportunity -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465549] I cannot complete an alignment on NGC 2070 - Solver fails to resolve and keeps trying
https://bugs.kde.org/show_bug.cgi?id=465549 --- Comment #1 from Len North --- Urgent update, and Apologies Jasem, Just looking at Line 13429 and I realized that I have left my Gemini 2 mini on the mount. It is running the new Losmandy level 6 beta version (for about a week). I apologize that I was not running my Gemini 2 tallboy controller which is my controller for bug testing your KStars. The connection problems I had tonight have all happened before except the alignment retrying which is new of mid Jan to early Feb and predates my G2 mini upgrade -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465549] New: I cannot complete an alignment on NGC 2070 - Solver fails to resolve and keeps trying
https://bugs.kde.org/show_bug.cgi?id=465549 Bug ID: 465549 Summary: I cannot complete an alignment on NGC 2070 - Solver fails to resolve and keeps trying Classification: Applications Product: kstars Version: 3.6.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: astroga...@westnet.com.au Target Milestone: --- Created attachment 156130 --> https://bugs.kde.org/attachment.cgi?id=156130=edit New log - something about QSocketNotifier - Invalid Sockets 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 *** KStars 3.6.3 Stable Build: 2023-02-07T07:46:30Z Had a really good run on this same build last night, but tonight I have spent 3 hours restarting and trying to get the INDI Control Panel - KStars to hold its settings. STEPS TO REPRODUCE 1. Don't know, I have changed all USB cables and the ZWO Camera, but most significantly I have had to rewrite into an empty Primary and Secondary Train selection box. To assist I called one new set of entries Imaging and Guiding, but the old names came back next time 2. Every start has seemed OK, but then going back to the Web Manager causes the system to crash and shutdown - This is a new issue 3. The final issue (I gave up) I decided to send some logs for this evenings events and all my log preference settings were back to default... No files and no verbosity. 3a. I went back and reset it again and produced this small log of my latest crash. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-58-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 680/PCIe/SSE2 ADDITIONAL INFORMATION Thank you Len -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465324] KStars 3.6.4 Beta, Focus module - total crash repeatable 4 times
https://bugs.kde.org/show_bug.cgi?id=465324 Len North changed: What|Removed |Added Assignee|mutla...@ikarustech.com |astroga...@westnet.com.au --- Comment #4 from Len North --- Created attachment 156007 --> https://bugs.kde.org/attachment.cgi?id=156007=edit This log file has more info on the crash This bug is in KStars Ver 3.6.3 Stable Build: 2023-01-31T10:34:48Z and while running Stellarmate v 1.7.5 Upgraded today. It is as described previously... BUT it is not occuring when I only run Stellarmate V 1.7.5 locally on the RPi 4B-4GB. This raises questions about my Ubuntu / Kubuntu / PC. For Balance, I need to refer to the StellarMate needing me to reload all my indi information again (a version of indi is already running, do you wish to close it - and I said Yes.) Do you want me to get a comprehensive log for Stellarmate? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465324] KStars 3.6.4 Beta, Focus module - total crash repeatable 4 times
https://bugs.kde.org/show_bug.cgi?id=465324 --- Comment #3 from Len North --- Created attachment 155968 --> https://bugs.kde.org/attachment.cgi?id=155968=edit Focuser Page with description I use the capture button so I can manually select a guide star at the required exposure, rather than start automatic capturing. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465324] KStars 3.6.4 Beta, Focus module - total crash repeatable 4 times
https://bugs.kde.org/show_bug.cgi?id=465324 --- Comment #2 from Len North --- Created attachment 155967 --> https://bugs.kde.org/attachment.cgi?id=155967=edit Log report of Focuser crash -3 This is a new problem I have not seen before and it is not happening on KStars ver 3.6.3 Stable Len -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465324] KStars 3.6.4 Beta, Focus module - total crash repeatable 4 times
https://bugs.kde.org/show_bug.cgi?id=465324 --- Comment #1 from Len North --- Created attachment 155966 --> https://bugs.kde.org/attachment.cgi?id=155966=edit Log report of Focuser crash -2 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465324] New: KStars 3.6.4 Beta, Focus module - total crash repeatable 4 times
https://bugs.kde.org/show_bug.cgi?id=465324 Bug ID: 465324 Summary: KStars 3.6.4 Beta, Focus module - total crash repeatable 4 times Classification: Applications Product: kstars Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: astroga...@westnet.com.au Target Milestone: --- Created attachment 155965 --> https://bugs.kde.org/attachment.cgi?id=155965=edit Log report of Focuser crash 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. Take an image using the small square "Capture button" in focuser 2. Change the exposure setting in Camera and Filter Wheel 3. Retake a "capture" image OBSERVED RESULT Everything crashes completely EXPECTED RESULT Normally I would see stars in the picture window, but I was trying to reproduce an issue which I think a notice said "No Stars Detected". So I tried to reproduce it today... and I did ... 4 times SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-58-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 680/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465174] Crash during startup.
https://bugs.kde.org/show_bug.cgi?id=465174 --- Comment #9 from Len North --- Created attachment 155929 --> https://bugs.kde.org/attachment.cgi?id=155929=edit Part 2 of ver 3.6.4 Log file -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465174] Crash during startup.
https://bugs.kde.org/show_bug.cgi?id=465174 --- Comment #8 from Len North --- Created attachment 155928 --> https://bugs.kde.org/attachment.cgi?id=155928=edit Part 1of2 ver 3.6.4 log Part one of 3.6.4 log for comparison -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465174] Crash during startup.
https://bugs.kde.org/show_bug.cgi?id=465174 --- Comment #7 from Len North --- Created attachment 155927 --> https://bugs.kde.org/attachment.cgi?id=155927=edit SNR displays vary Thanks heaps. Len -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465174] Crash during startup.
https://bugs.kde.org/show_bug.cgi?id=465174 --- Comment #6 from Len North --- Created attachment 155926 --> https://bugs.kde.org/attachment.cgi?id=155926=edit Solver issues, where an aligned telescope suddenly stopped functioning. After the crash, the system was restarted (cold start) but solver issues were the main problem, everything else was OK. After the next start, poor guiding and variations in SNR displays was a minor issue. p.s. I loaded your new version 3.6.4 soon after it was uploaded and it is amazing, just like the old days. connection was fine, guiding was precise and flexible. Guess I can now go back to 30min exposures. Thanks -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 259917] the simulate option cannot be selected and the 'remove image' option is greyed out
https://bugs.kde.org/show_bug.cgi?id=259917 --- Comment #6 from North --- I no longer have a cd reader. Stop bugging me please. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465174] Crash during startup.
https://bugs.kde.org/show_bug.cgi?id=465174 --- Comment #4 from Len North --- Hello Jasem Kstars 3.6.4 is MAGIC. How do I apologize for annoying reporting, but connection and guiding is now the best I have seen. Congratulations & Kind Regards Len -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465174] Crash during startup.
https://bugs.kde.org/show_bug.cgi?id=465174 --- Comment #3 from Len North --- Created attachment 155886 --> https://bugs.kde.org/attachment.cgi?id=155886=edit 3rd log file -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465174] Crash during startup.
https://bugs.kde.org/show_bug.cgi?id=465174 --- Comment #2 from Len North --- Created attachment 155885 --> https://bugs.kde.org/attachment.cgi?id=155885=edit 2nd log file -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465174] Crash during startup.
https://bugs.kde.org/show_bug.cgi?id=465174 --- Comment #1 from Len North --- Created attachment 155884 --> https://bugs.kde.org/attachment.cgi?id=155884=edit 1st Log file -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465174] New: Crash during startup.
https://bugs.kde.org/show_bug.cgi?id=465174 Bug ID: 465174 Summary: Crash during startup. Classification: Applications Product: kstars Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: astroga...@westnet.com.au Target Milestone: --- Created attachment 155883 --> https://bugs.kde.org/attachment.cgi?id=155883=edit Initial startup crash report 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 started Ekos and indi then pressed connect. The first 3 profiles showed up. then it crashed I did not set or reset all parameters in all profiles, but these items allowed me to progress. STEPS TO REPRODUCE 1. crash recovery > reactivate StellarMate Web Manager. 2. 30 iterations of solver did not resolve, even though sirius was centred in Image viewer > enable solver in Indi / Astrometry panel and reset "ZWO CCD" as it was now blank.. All now OK for Solver as it was immediately within 2 arc seconds and green. 3. Anomoly on graphs:- SNR Guiding vs SNR Analyse vs SNR setup Page graph. I will compile a 1 page summary and send it In summary. SNR shows initially in the graph, but doesn't keep showing in the Analyse page. SNR Is good in Setup Page Guide Window, but in Guide Window it was as if I had the exposure delay enabled. It was not. OBSERVED RESULT Currently running nicely EXPECTED RESULT I hoped for a simpler startup SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-58-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 680/PCIe/SSE2 ADDITIONAL INFORMATION I have some small log files -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465059] sudden huge deviations in guiding
https://bugs.kde.org/show_bug.cgi?id=465059 --- Comment #3 from Len North --- Created attachment 155806 --> https://bugs.kde.org/attachment.cgi?id=155806=edit Earlier I had some issues with alignment where there were 6 tries but it was no closer to resolution. Capture and solve has been the best part of following the Kstars development. It is fast and I don't want to go back to sitting outside driving PHD-2 from a laptop. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465059] sudden huge deviations in guiding
https://bugs.kde.org/show_bug.cgi?id=465059 --- Comment #2 from Len North --- Created attachment 155805 --> https://bugs.kde.org/attachment.cgi?id=155805=edit Guiding history with an RMS of 62.1 was outstanding then... -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465059] sudden huge deviations in guiding
https://bugs.kde.org/show_bug.cgi?id=465059 --- Comment #1 from Len North --- Created attachment 155804 --> https://bugs.kde.org/attachment.cgi?id=155804=edit This is what I love about what the KStars team does - perfect Sorry that I cannot even write a report properly (2 more attachments to come) -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465059] New: sudden huge deviations in guiding
https://bugs.kde.org/show_bug.cgi?id=465059 Bug ID: 465059 Summary: sudden huge deviations in guiding Classification: Applications Product: kstars Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: astroga...@westnet.com.au Target Milestone: --- Created attachment 155803 --> https://bugs.kde.org/attachment.cgi?id=155803=edit The charts have been assembled to show my view of the events. SUMMARY *** Kstars Version 3.6.3 Beta Build: 2023-01-30T13:18:19Z *** Guiding and capture was stable - attachment 1 Guiding jumped by about 175 arc seconds in 30 seconds - attachment 2 Earlier I had alignment issues so had turned on Alignment Logging, but that log didn't help the other issue - attachment 3 STEPS TO REPRODUCE 1. Changing viewing screens between Guiding, CCD and setup have often caused guiding instability sometimes just a bump.. or a crash. 2. The mount and outside equipment are on a capable battery with filtered AC charging and earth bonding. Data is 30 metres via ethernet. 3. Remote 64 bit Indi has seen RPi 4B-4G replace the RPi3B and now run Kubuntu inside. OBSERVED RESULT No Change observed, still have setup and operational issues EXPECTED RESULT The issues are not passive as when the guide stars are lost, there is extreme motion involved. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-58-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 680/PCIe/SSE2 ADDITIONAL INFORMATION I have compared a Unihedron SQM graph of the night and although it closely follows your sky quality reading. this time it didn't. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 464922] KStars 3.6.3beta: ZWO multiple camera issues for 1 camera
https://bugs.kde.org/show_bug.cgi?id=464922 --- Comment #5 from Len North --- Thank you Jasem, Camera driver issues resolved. My startup issues have been resolved with all cameras playing nicely together on one driver. Setup time last night was about 25 minutes compared to a usual 2 to 3 hours. Information only. Last night I got to observe our dark skies with binoculars while capturing with Ekos. I also saw the brightening of the sky in a Unihedron SQM graph as the milky way went over. My aligned mount with motors is in a fixed position in my backyard where I setup and strip the scope and electronics for each session. Controlling is done by an Ethernet cable from the house. Other projects are all portable. I went into our winter cloud period last May and nearly gave up astronomy over guiding camera connection issues. You have been very helpful. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 464922] KStars 3.6.3beta: ZWO multiple camera issues for 1 camera
https://bugs.kde.org/show_bug.cgi?id=464922 --- Comment #2 from Len North --- Another issue is that I cannot find a backup procedure for my settings (Backup does not return any results in a search of the manual) as I have spent hours entering my settings for every new version and often when I reopen the program. Although I press save in each of the Indi Control Panels, the next time it starts I have to re-enter my settings e.g. Observer name and optical train details etc Please note: My location is always showing correctly. Would you like a list of those I regularly reset? And I just love the reworking of the Optical Train format. It suits the smaller screens. Thanks for all you do, I'm in Australia and have been with KStars since 2017. I now have a tripple boot PC with your beta version on Kubuntu, and your stable version on Ubuntu. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 464922] KStars 3.6.3beta: ZWO multiple camera issues for 1 camera
https://bugs.kde.org/show_bug.cgi?id=464922 --- Comment #1 from Len North --- Created attachment 155714 --> https://bugs.kde.org/attachment.cgi?id=155714=edit Shows 2x ZWO120MM_S Cameras -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 464922] New: KStars 3.6.3beta: ZWO multiple camera issues for 1 camera
https://bugs.kde.org/show_bug.cgi?id=464922 Bug ID: 464922 Summary: KStars 3.6.3beta: ZWO multiple camera issues for 1 camera Classification: Applications Product: kstars Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: astroga...@westnet.com.au Target Milestone: --- Created attachment 155713 --> https://bugs.kde.org/attachment.cgi?id=155713=edit Log file from Ekos 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 *** As I have 3 ZWO ASI Cameras, I refer to my ASI1600MC-S as a ZWO CCD, my ASI120MM-S as ZWO 2 and my ASI120MC-SS as ZWO 3. I only use one of the ASI120's for guiding at any time, and that may be with a QSI 683 CCD or the ASI 1600MC-S as imaging cameras. The problem is that I get multiple ASI 120's showing up as selected cameras, 1 as an ZWO CCD 120xxx and the other as ZWO 120xxx STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 463147] I am seeing huge guiding errors on Ubuntu / StellarMate, but works perfectly on iMac / Stellarmate
https://bugs.kde.org/show_bug.cgi?id=463147 --- Comment #6 from Len North --- Created attachment 154673 --> https://bugs.kde.org/attachment.cgi?id=154673=edit Screen Shot 2022-12-19 at 00.35.56.png --- Comment #7 from Len North --- Created attachment 154674 --> https://bugs.kde.org/attachment.cgi?id=154674=edit Screen Shot 2022-12-18 at 01.22.43.png --- Comment #8 from Len North --- Created attachment 154675 --> https://bugs.kde.org/attachment.cgi?id=154675=edit Screenshot from 2022-12-17 20-26-35.png -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 463147] I am seeing huge guiding errors on Ubuntu / StellarMate, but works perfectly on iMac / Stellarmate
https://bugs.kde.org/show_bug.cgi?id=463147 --- Comment #5 from Len North --- > On 18 Dec 2022, at 14:45, Jasem Mutlaq wrote: > > https://bugs.kde.org/show_bug.cgi?id=463147 > > --- Comment #1 from Jasem Mutlaq --- > What's your guiding RMS in both setups? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 463147] I am seeing huge guiding errors on Ubuntu / StellarMate, but works perfectly on iMac / Stellarmate
https://bugs.kde.org/show_bug.cgi?id=463147 --- Comment #4 from Len North --- (In reply to Jasem Mutlaq from comment #1) > What's your guiding RMS in both setups? Mac OS +Ver 3.5.7 is guiding at under 0.60 RMS Linux ver 3.6.2 is guiding above 4.00 RMS Please see the two new attachments. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 463147] I am seeing huge guiding errors on Ubuntu / StellarMate, but works perfectly on iMac / Stellarmate
https://bugs.kde.org/show_bug.cgi?id=463147 --- Comment #3 from Len North --- Created attachment 154671 --> https://bugs.kde.org/attachment.cgi?id=154671=edit Mac OS Guiding Guiding screenshot No2 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 463147] I am seeing huge guiding errors on Ubuntu / StellarMate, but works perfectly on iMac / Stellarmate
https://bugs.kde.org/show_bug.cgi?id=463147 --- Comment #2 from Len North --- Created attachment 154670 --> https://bugs.kde.org/attachment.cgi?id=154670=edit Screenshots of Linux OS guiding v3.6.2 Screenshots while guiding -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 463147] New: I am seeing huge guiding errors on Ubuntu / StellarMate, but works perfectly on iMac / Stellarmate
https://bugs.kde.org/show_bug.cgi?id=463147 Bug ID: 463147 Summary: I am seeing huge guiding errors on Ubuntu / StellarMate, but works perfectly on iMac / Stellarmate Classification: Applications Product: kstars Version: 3.6.2 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: astroga...@westnet.com.au Target Milestone: --- Created attachment 154643 --> https://bugs.kde.org/attachment.cgi?id=154643=edit 4 frames supposedly taken with a 14 arcsecong guiding error I am seeing guiding errors on Ubuntu 22.4.1 / kstars 3.6.2 / StellarMate, but works on mid 2011 iMac High Sierra / kstars 3.5.7 /Stellarmate *** I have been using KStars since 2017, but a new issue has emerged as I have changed from using my remote StellarMate with RPi 4b-4G controller to using a dualBoot PC on Linux for my controller The latest KStars is giving me grief as my guiding is showing plus 6 to minus 6 arcseconds guide error, but it is not apparent in my photo. with the same server and mount config, I switch to my iMac running KStars version 3.5.7 as a controller, and all runs well. Can I access a linux copy of 3.5.7 for ubuntu until I can resolve other local issues that are not related to KStars as we have 4 clear nights ahead? These are for info only: e.g. I can't dual boot with Kubuntu, as it says I have system naming issues e.g. I take 3-4 hours per setup as my configuration all resets to default with any error while using 3.6.2 on linux, but it works perfectly on iMac using 3.5.7 Please help me if I can get an earlier Linux version Thanks Len STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 460674] Connecting 2x ZWO CMOS cameras and one camera always fails.
https://bugs.kde.org/show_bug.cgi?id=460674 --- Comment #3 from Len North --- Hello Jasem, Progress has been made, but there is still one problem for me, the Index File Download is disabled with a directory permission issue.. Pic 1 A previous issue was that the Optical Train setup issues meant that my ZWO Guide camera issues were invisible to me on your layout… Pic 2, 3 and 4. Where the Words ZWO…, ZWO Camera 2 and ZWO ASI120MM-S are all different but not visible, but only the last one works. as you can see by Pic 5… MY INITIAL ISSUE WAS CAUSED BY MY REMOTE RPI INDI SERVER which has been replaced due to it needing 5 updates but still had the same StarBlock issues.. see log_03-34-57.txt and others Thank you for the functionality that I have had for the last 4 or 5 years. Although I find it annoying to have to enter my name for the fits file every time I restart the program, there is nothing like KStars / EKOS that comes close to consideration. One day I will ask the forum how I can turn off all automatic updates, even on Ubuntu Mate as they ruin many hours of possible capture. I’m sorry that our (southern hemisphere) imaging is different to the northern hemisphere, but my issues were due to me losing a windows 7 pc power supply and my QSI 683 is having needed maintenance. Kind regards Len North > On 19 Oct 2022, at 16:07, Jasem Mutlaq wrote: > > https://bugs.kde.org/show_bug.cgi?id=460674 > > --- Comment #2 from Jasem Mutlaq --- > Please update to KStars v3.6.1 > > -- > You are receiving this mail because: > You reported the bug. Pic 1 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 460674] Connecting 2x ZWO CMOS cameras and one camera always fails.
https://bugs.kde.org/show_bug.cgi?id=460674 --- Comment #1 from Len North --- Created attachment 153009 --> https://bugs.kde.org/attachment.cgi?id=153009=edit Log file from iMac for KStars crash I have added some log files -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 460674] New: Connecting 2x ZWO CMOS cameras and one camera always fails.
https://bugs.kde.org/show_bug.cgi?id=460674 Bug ID: 460674 Summary: Connecting 2x ZWO CMOS cameras and one camera always fails. Classification: Applications Product: kstars Version: 3.6.1 Platform: Kubuntu OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: astroga...@westnet.com.au Target Milestone: --- Created attachment 153008 --> https://bugs.kde.org/attachment.cgi?id=153008=edit I have seen both cameras connected, but not together 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. Running RPi3B with Stellarmate at the Mount Imaging Camera is an old version of ZWO ASI 1600-MC-S - Not cooled Guide Cameras - Tried an ZWO ASI 120MC-S and a ASI 120MM-S Put new USB 2B leads and no change 2. Recently converted PC running Kabuntu has upgraded itself to KStars 3.6.1 3. Also tried iMac 10.13.6 with KStars 3.3.4 through to KStars 3.5.9 OBSERVED RESULT The iMac just crashed out The Kubuntu EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: 10.13.6 Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version 5.15.0-50-generic (64bit) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 458352] New: KStars Update failed to fetch due to unsigned...
https://bugs.kde.org/show_bug.cgi?id=458352 Bug ID: 458352 Summary: KStars Update failed to fetch due to unsigned... Product: kstars Version: 3.6.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: astroga...@westnet.com.au Target Milestone: --- Created attachment 151620 --> https://bugs.kde.org/attachment.cgi?id=151620=edit My original message of this was blocked as spam SUMMARY *** *** STEPS TO REPRODUCE 1. I Updated Ubuntu Mate - it went OK 2. I attempting to update KStars and got error messages OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Raspberry Pi running Ubuntu Mate Release 20.04.4 LTS (Focal Fossa) 64-bit Kernel Linux 5.4.0-1069-raspi aarch64 MATE 1.24.0 ADDITIONAL INFORMATION Thanks Len -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428112] Changing XDG folder locations in the KCM does not update items in the Places Model that point to the old location
https://bugs.kde.org/show_bug.cgi?id=428112 Alan North changed: What|Removed |Added CC||alanscode...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 451255] kstars starts Sky image, but it needs operator intervention before I open EKOS
https://bugs.kde.org/show_bug.cgi?id=451255 --- Comment #2 from Len North --- Hello Jasem, Please accept this email as one subject. Each night before I start, I have to manually enter a lot of basic information that the program should remember - now I have to align the Sky Image Map on KStars front page before I proceed to EKOS. KStars 3.5.7 Stable is fine on Win10 and Mac OS 10.13. 6. as of tonight, but I am having this issue on a RPI 4B 4G Ubuntu 20.04.4 LTS (Focal Fossa) 64-bit Kernel Linux 5.4.0-1053-raspi aarch64 + Mate 1.24.0 and I have 16.6GB of available disk space. My remote server is a Stellar Mate RPi3B. ## My ISP has just reported a maintenance shutdown for internet issues. I use the internet for NTP Time.## Prior to recent update EKOS would always sync with My DISPLAYED time date and location (as shown in writing on the Sky Image - the first screen of kstars) so my orientation and sky tracking was good. The planetarium may have not always have been really accurate, but was never a serious issue as it corrected itself with the first plate solve. Now it appears that in indi My written time, date and location is being replaced with whatever the planetarium sky image shows my location and therefore sky view to be, even if it shows the wrong hemisphere. THIS DOESN’T HELP - Setting the TIME>to NOW does’nt help THIS ALWAYS FIXES IT - But in Pointing, just pressing >Zenith always helps. If the Sky Image is still upside down then pressing >South, then >Zenith completely syncs indi to the correct orientation before opening EKOS. It doesn’t stop kstars from being much better than many expensive programs, but it just adds my location as another item to the long list of preset parameters that it forgets and needs attention when setting up. Most of these should be “written in stone items” and don’t change. Such as:- my ownership name “Len North”on the camera fits header files - This is not currently saved but has to be entered manually and nightly on the Indi Control Panel-KStars > CCD General Info screen > Fits Header> OBSERVER my QSI preset temp is always -20 deg C, but it is never remembered, The field on the Indi Control Panel-KStars > CCD > Temperature just shows ambient temp on startup and them randomly shows a meaningless temperature. my QSI rotation usually has 2 rotation changes twice per year, but needs me to manually reset the WCS setting each night ( Bouquets-it often remembers during restarts throughout the evening) my guide camera always asks for camera rotation even though I always set WCS disabled. my 45,000 max steps on the Pegasus focuser often / randomly reverts to 100,000 steps - the default Rather than an editable and saveable config library for fixed presets or Backups, the program appears to on rely on multiple locations with the fluid versions of the same data and worse, the new info is now editable easily but not recorded in the master config. Further to the Fits Header File. All I see now is “Generated By indi" but surely a version and build number is a start. I have included a fits header from 2018 using The Sky X Pro, but all my files since 2012 are traceable to me and my location along with whatever equipment I was using… my photos are embedded as my photos. Kind regards Len North > On 8 Mar 2022, at 15:41, Jasem Mutlaq wrote: > > https://bugs.kde.org/show_bug.cgi?id=451255 > > --- Comment #1 from Jasem Mutlaq --- > Thank you for the report. I'm still not exactly sure what the problem is. You > open KStars and you need to orient it to look at a specific direction? like > south? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 451255] kstars starts Sky image, but it needs operator intervention before I open EKOS
https://bugs.kde.org/show_bug.cgi?id=451255 --- Comment #3 from Len North --- Created attachment 147378 --> https://bugs.kde.org/attachment.cgi?id=147378=edit Screen Shot 2022-03-09 at 01.38.12.png --- Comment #4 from Len North --- Created attachment 147379 --> https://bugs.kde.org/attachment.cgi?id=147379=edit Screen Shot 2022-03-09 at 01.33.59.png -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 451255] New: kstars starts Sky image, but it needs operator intervention before I open EKOS
https://bugs.kde.org/show_bug.cgi?id=451255 Bug ID: 451255 Summary: kstars starts Sky image, but it needs operator intervention before I open EKOS Product: kstars Version: 3.5.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: astroga...@westnet.com.au Target Milestone: --- Created attachment 147352 --> https://bugs.kde.org/attachment.cgi?id=147352=edit This screen grab does not reflect my sky at the shown time date and location. SUMMARY *** Before I start.. I love what you people achieve with kstars -big fan. *** I am using an RPi 4B 4G Linux (aarch64) release 5.4.0-1052-raspi and a Stellar Mate remote server, but the problem occurs before I start EKOS an even if I don't have the Stellar Mate connected STEPS TO REPRODUCE 1. Start kstars and confirm location, dates, times, the meridian line and Sky Image orientation - I live in the Southern Hemisphere so appreciate that this information is normally remembered 2. Last night the first go-to was not correct so I shut it down for a restart and it parked my Gemini 2 Telescope facing the ground. This has not ever happened before. 3. I restarted and checked Step 1 where I got a sky image with only part of the meridian visible. Setting time to NOW made no difference so I went to POINTING and chose SOUTH then ZENITH. This returned the meridian and sky view to correct orientation and I had a good night of imaging. Tonight it did the same, the sky image did not initially show my sky 4 An apology, KStars has made me lazy and I have always used the Sky Image as my reference but now I have to check KStars 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.
[kstars] [Bug 445064] New: In camera and filters screen I have chosen Enforce Temperature before Capture, yet frames are captured and no alarm or alert is issued.
https://bugs.kde.org/show_bug.cgi?id=445064 Bug ID: 445064 Summary: In camera and filters screen I have chosen Enforce Temperature before Capture, yet frames are captured and no alarm or alert is issued. Product: kstars Version: 3.5.5 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: astroga...@westnet.com.au Target Milestone: --- SUMMARY KStars 3.5.5 Stable is no longer reliable. Benchmark settings cannot be trusted. There is a disconnect between what you ask and what you get. For example, My QSI ambient air temperature and preset cooling temperature differences cannot exceed 47deg C so -20deg is a good setting for nightime capture, but during the daytime -20deg setting on a 30deg day will bring up 100% Cooling, therefore the temperature rises above the critical setting of -20deg C STEPS TO REPRODUCE 1. To eliminate operating system fault I am using Stellar Mate SD Cards on 2 RPi's. As a server and as a controller. 2. Select "Enforce Temperature before Capture" 3. Select an unreachable temperature, say -30deg C, OBSERVED RESULT as the cooling demand passes 100% and just take lots of frames... Please note 1) that the Temperature tick is still green and the camera ignores the enforce command. 2) No alerts or alarms are issued EXPECTED RESULT I Expect Ekos to use my input settings, Control and modify the outputs Raise alarms and alerts when it cannot comply SOFTWARE/OS VERSIONS Stellar Mate SD cards in 2 Raspberry Pi's Also on my macOS: ADDITIONAL INFORMATION This is one of a number of issues where input settings are lost or ignored rather than being saved, so this is a formal "Stake in the sand" for me to document how KStars ver 3.5.5 has become unreliable. Others are Pegasus Focuser settings, QSICamera sensor settings, QSI Camera rotation settings, Guide camera settings... Until ver 3.5.5 stable I had fun doing astronomy, but it has become unworkable as a simple guiding crash will make an SD Card unusable. Thanks for what you do.. just having a bad day here. (No captures all last night) Len -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439131] Detached brush editor does not respect brush changes done via the Python API
https://bugs.kde.org/show_bug.cgi?id=439131 --- Comment #2 from Alan North --- Seeing that other bug report, it looks more like the bug is the brush editor was never designed to "listen" to external changes since it didn't need to be, although strange the sliders do affect it. Did not think to test this at the time, but any changes that can be made via the popup palette brush hud are also a problem. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439127] Crash when switching to smudge brush engine with rgba tip in lightness map mode
https://bugs.kde.org/show_bug.cgi?id=439127 Alan North changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Alan North --- This had been a bug that I'd been asked to file when an MR regarding default rgba tip settings was being tested. In the end I think changes to the MR were made and this was fixed or no longer relevant. I just checked to be sure, but it's no longer a problem. I've closed it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440311] Creating nameless brush tip from clipboard does not save tip correctly and can make krita crash.
https://bugs.kde.org/show_bug.cgi?id=440311 --- Comment #9 from Alan North --- I might have spoken too soon. Forgot to test the crash *facepalm*. That's still happening when there's a preset whose brush tip doesn't exist. I was also getting crashes suddenly when just saving any preset, but when I deleted my database and removed the brushes that had missing tips, they stopped. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440311] Creating nameless brush tip from clipboard does not save tip correctly and can make krita crash.
https://bugs.kde.org/show_bug.cgi?id=440311 --- Comment #8 from Alan North --- Just tested, tips no longer disappear and they save fine with an extension and everything, so it was the colon causing problems on windows. I haven't tried other resources, but if anything else saves like that, it might have the same problem. BUT... still getting a crash (crash log 2) when saving any brush tips with the same name (blank or named). Feels like a separate bug though now that I've pinned it down more, I've filed a new issue: https://bugs.kde.org/show_bug.cgi?id=440435 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440435] New: Krita crashes when trying to overwrite brush tip.
https://bugs.kde.org/show_bug.cgi?id=440435 Bug ID: 440435 Summary: Krita crashes when trying to overwrite brush tip. Product: krita Version: git master (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: alanscode...@gmail.com Target Milestone: --- STEPS TO REPRODUCE: 1. Create a file, draw something, copy a part. 2. Create brush tip named "Test" or a blank. Can be from clipboard or stamp, issue exists with both. 3. Copy some other part (the hash must be different, it doesn't crash if it's the same exact brush tip). 2. Create another brush tip named the same. The crash log is here: https://bugsfiles.kde.org/attachment.cgi?id=140354 I had already submitted it, thinking the issue was a part of https://bugs.kde.org/show_bug.cgi?id=440311 OBSERVED RESULT Crash I also notice that the button is meant to change from Save to Overwrite when an existing brush exists, but this also does not always happen (if nothing is typed, it doesn't change), but it crashes whether it does or not. Also when I first encountered this, I thought it didn't happen after restart, but it does, I must have accidentally avoided it. EXPECTED RESULT Button changes to "Overwrite" and no crash when overwriting tips.. SOFTWARE/OS VERSIONS Windows 10 Krita: 8ebe5e92507e7d519692b5d92785dda517c4be69 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440311] Creating nameless brush tip from clipboard does not save tip correctly and can make krita crash.
https://bugs.kde.org/show_bug.cgi?id=440311 --- Comment #4 from Alan North --- Yeah, tested on nightly (6ebbd5279e) just to be sure, still a problem for me. Did you try this on linux or windows? If on linux and it works and am assuming uses a colon in the file name, I further suspect it's the issue because windows files can't have colons in them. Also I only just realized this, but the lack of the part after the colon means you also get crash #1 when you try to create two different brush tips this way within the same hour (only within the same session, strangely restarting krita between brush tip creations avoids it). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440311] Creating nameless brush tip from clipboard does not save tip correctly and can make krita crash.
https://bugs.kde.org/show_bug.cgi?id=440311 --- Comment #3 from Alan North --- Created attachment 140354 --> https://bugs.kde.org/attachment.cgi?id=140354=edit crash log 2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440311] Creating nameless brush tip from clipboard does not save tip correctly and can make krita crash.
https://bugs.kde.org/show_bug.cgi?id=440311 --- Comment #2 from Alan North --- I built from master (f808f0c53e0a2fb6490c11779ca98ad8a68e0a01 so after that commit), but am still getting all the problems. Does not save correctly. Crashes. I'll try with the nightly when it comes out including that commit just to be sure. Crash log does look different now though, I'll attached it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440311] New: Creating nameless brush tip from clipboard does not save tip correctly and can make krita crash.
https://bugs.kde.org/show_bug.cgi?id=440311 Bug ID: 440311 Summary: Creating nameless brush tip from clipboard does not save tip correctly and can make krita crash. Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: alanscode...@gmail.com Target Milestone: --- Created attachment 140346 --> https://bugs.kde.org/attachment.cgi?id=140346=edit crash log SUMMARY Creating nameless brush tip from clipboard does not save the brush tip file correctly. Also this causes the current version of krita to crash when choosing a preset that has it set as it's brush tip. The crashing does not happen with an older build I had been using (d01cd76e94), though the general problem does. I've lost several tips to this, but just didn't really dig into why at the time. STEPS TO REPRODUCE 1. Create a new file, draw something. Select and copy. 2. Create brush tip from clipboard, don't name it. 4. Restart krita. To make it crash, do the same but save a brush preset before restarting, then try to select it after restart. I've also had problems going to the predefined brush tips in the brush editor making things crash using a database that had several problematic brush presets, but could not replicate with a fresh one. OBSERVED RESULT The brush tip disappears on restart, probably because the brush tip file is empty/invalid. In the log I see `dependent resource "2021-07-26T18:13.gbr" misses.` when I open the brush presets list. In the older version I don't get that, instead when I select the brush I get: `Using fallback brush brushFileName = "2021-07-26T18:13.gbr"` In the resources folder I see it saves a file with a date for a name (e.g. 2021-07-26T18) when I save the brush, but it has no extension or size. Also, I wonder if the lack of the part after the colon in the filename is part of the problem? If I name the tip, this doesn't happen. A proper .gbr file is created. Strangely, deleting the file or even the database, does not help, still crashes. The only fix is deleting the preset manually or using an older build of krita to "fix" the preset and assign a properly saved tip to it, then open in new krita. SOFTWARE/OS VERSIONS Windows 10 Krita: 178019461d -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439128] Can't name brush after a deleted brush.
https://bugs.kde.org/show_bug.cgi?id=439128 --- Comment #6 from Alan North --- Ah, didn't know about the MR, I'll check if it's still a problem (along with some related bugs I filed) as soon as I can. There were some severe crashes on the last commit I tried to rebase my branch to so I reverted back to a weeks old build, will try again. I totally get if the prompting to remove deleted resources has to wait, or if that's not the solution taken. For example, I think more easily allowing real deletion/modification will make it less likely for people to try to go the resources folder to do stuff. Just mentioning it so the potential issue isn't forgotten. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439128] Can't name brush after a deleted brush.
https://bugs.kde.org/show_bug.cgi?id=439128 --- Comment #4 from Alan North --- I remarked it as REPORTED. Not sure if it should still be NEEDSINFO? It was sort of discussed outside of here, the main solution being renaming deleted resources to del_* or something like that. Ideally though, krita would also scan for manually deleted resources and remove them from the database. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439128] Can't name brush after a deleted brush.
https://bugs.kde.org/show_bug.cgi?id=439128 Alan North changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439423] New: Resources remain assigned to deleted tags.
https://bugs.kde.org/show_bug.cgi?id=439423 Bug ID: 439423 Summary: Resources remain assigned to deleted tags. Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tagging Assignee: krita-bugs-n...@kde.org Reporter: alanscode...@gmail.com Target Milestone: --- I would maybe understand if this was the case when not restarting since one can undelete a tag. But after restarting it's just weird. I would expect deleting a tag removes it from all resources that are assigned to it. STEPS TO REPRODUCE 1. Create new tag, `Test`. Assign a resource to it. 2. Go to tag, delete it. 3. Restart krita (not needed, just making the point it also happens on restart). 4. Create the tag `Test` again. OBSERVED RESULT Resource that were assigned to the deleted tag are still assigned to it when that tag is recreated. I say recreated, but imagine this happening weeks apart, to the user they are just creating a new tag. EXPECTED RESULT I would personally expect deleting a tag removes it from all resources that are assigned to it even before a restart. Only undeleting a tag would retag them. SOFTWARE/OS VERSIONS Windows 10 Krita: b4a6f8041a -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439422] New: Can't name tag after older name of renamed tag.
https://bugs.kde.org/show_bug.cgi?id=439422 Bug ID: 439422 Summary: Can't name tag after older name of renamed tag. Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tagging Assignee: krita-bugs-n...@kde.org Reporter: alanscode...@gmail.com Target Milestone: --- I opened the database and the issue seems to be that the tag url isn't getting changed. This happens even after restarting after the rename. STEPS TO REPRODUCE 1. Create new tag, `Test`. 2. Rename tag. 3. Try to create new tag named `Test`. OBSERVED RESULT Fails silently. If doing this from a resource, if the resource was already in the old tag, it will also fail silently, but if it wasn't, it will add the resource to the old tag. EXPECTED RESULT Tag can be created. Resource is assigned to newly created tag. SOFTWARE/OS VERSIONS Windows 10 Krita: b4a6f8041a -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439131] New: Detached brush editor does not respect brush changes done via the Python API
https://bugs.kde.org/show_bug.cgi?id=439131 Bug ID: 439131 Summary: Detached brush editor does not respect brush changes done via the Python API Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: alanscode...@gmail.com Target Milestone: --- SUMMARY I found this because I have a plugin that sets the brush size, but was able to reproduce with the Scripter plugin. STEPS TO REPRODUCE 1. Open Scripter plugin, paste: win = Krita.instance().activeWindow() view = win.activeView() view.setBrushSize(5) 2. Open brush editor (in detached mode). 3. Run script. OBSERVED RESULT Note that the brush size changes in the toolbar but not the brush editor. Changing anything in the brush editor causes the size to reset to what the brush editor thinks it is. This also happens with opacity (setPaintingOpacity) and I'm guessing anything else that can be set via the API. EXPECTED RESULT Changes are "applied" everywhere. SOFTWARE/OS VERSIONS Windows 10 Krita Nightly 4407898 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439128] New: Can't name brush after a deleted brush.
https://bugs.kde.org/show_bug.cgi?id=439128 Bug ID: 439128 Summary: Can't name brush after a deleted brush. Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: alanscode...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Create new brush, name it something, for example "1". Save it. 2. Delete it. 3. Try to save a new brush with the same name "1". OBSERVED RESULT Nothing happens, brush does not appear in any lists. In the log docker I see: Resource "paintoppresets" "1.kpp" already exists in ... Could not add resource "1.kpp" to the storage "" Failed to add resource "1" It seems the preset is not really deleted from my resources, only marked as deleted. Deleting it manually does not help because the database still thinks it's deleted. EXPECTED RESULT I can name a brush after a deleted brush. I wouldn't really expect the preset to be kept around in my resources folder either... SOFTWARE/OS VERSIONS Windows 10 Krita Nightly 4407898 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439127] New: Crash when switching to smudge brush engine with rgba tip in lightness map mode
https://bugs.kde.org/show_bug.cgi?id=439127 Bug ID: 439127 Summary: Crash when switching to smudge brush engine with rgba tip in lightness map mode Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: alanscode...@gmail.com Target Milestone: --- Created attachment 139644 --> https://bugs.kde.org/attachment.cgi?id=139644=edit crash log STEPS TO REPRODUCE 1. Create smudge brush, set tip to an rgba tip, set brush mode to lightness map. 2. Create a new brush in another engine (e.g. pixel) 3. Try to create smudge brush again. SOFTWARE/OS VERSIONS Windows 10 Krita Nightly 4407898 -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 139201] JJ: Settings such as "no headers" and "no vertical scrollbar" not retained
https://bugs.kde.org/show_bug.cgi?id=139201 North changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED CC||terauck-...@yahoo.com.au -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 412264] 'Disable the popup' which appears after editing a klipper entry doesn't work
https://bugs.kde.org/show_bug.cgi?id=412264 --- Comment #6 from North --- Apologies. The popup appears in the bottom RIGHT of my screen. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 412264] 'Disable the popup' which appears after editing a klipper entry doesn't work
https://bugs.kde.org/show_bug.cgi?id=412264 --- Comment #5 from North --- The popup appears in the bottom left of my screen. You may need to check "Enable mime-based actions" to see it. I can't take a screenshot because as soon as I click on "Take a New Screenshot", the popup disappears. It seems to me that the popup serves no useful purpose. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 412264] 'Disable the popup' which appears after editing a klipper entry doesn't work
https://bugs.kde.org/show_bug.cgi?id=412264 --- Comment #3 from North --- The issue occurs even when "Enable mime-based actions" is unchecked. It may be that unchecking is ineffective - see the screenshot attached of the first entry in klipper earlier (it was a partial url). -- You are receiving this mail because: You are watching all bug changes.
