[kwin] [Bug 490198] New: Request: Vertical Snapping
https://bugs.kde.org/show_bug.cgi?id=490198 Bug ID: 490198 Summary: Request: Vertical Snapping Classification: Plasma Product: kwin Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Quick Tiling Assignee: kwin-bugs-n...@kde.org Reporter: tro...@hotmail.co.uk Target Milestone: --- SUMMARY Add an option, per display, to snap vertically instead of horizontally. I'd like to be able to snap two windows, on top of each other, on my vertical monitor, by dragging the window to the top or bottom of the screen. There's already a tiling option for "Windows dragged to the left or right edge", I'd like an equivalent for the top and bottom edges. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (available in About System) KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 499509] Icons for hidden folders are smaller than non-hidden ones
https://bugs.kde.org/show_bug.cgi?id=499509 --- Comment #20 from Troy --- Fixed for me too Operating System: Arch Linux KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.6-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 7800 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 503352] Snapping on a vertical monitor using meta + down working incorrectly
https://bugs.kde.org/show_bug.cgi?id=503352 --- Comment #1 from Troy --- Created attachment 180656 --> https://bugs.kde.org/attachment.cgi?id=180656&action=edit Window screenshotted as a region in Spectacle, missing buttons in top right. Width is 1440 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 503352] Snapping on a vertical monitor using meta + down working incorrectly
https://bugs.kde.org/show_bug.cgi?id=503352 Troy changed: What|Removed |Added Attachment #180655|0 |1 is obsolete|| --- Comment #2 from Troy --- Created attachment 180657 --> https://bugs.kde.org/attachment.cgi?id=180657&action=edit Window screenshotted as active window in Spectacle, note that width is aproximately 1530, instead of expected 1440 Needed to crop the image -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 503352] New: Snapping on a vertical monitor using meta + down working incorrectly
https://bugs.kde.org/show_bug.cgi?id=503352 Bug ID: 503352 Summary: Snapping on a vertical monitor using meta + down working incorrectly Classification: Plasma Product: kwin Version: 6.3.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Quick Tiling Assignee: kwin-bugs-n...@kde.org Reporter: tro...@hotmail.co.uk Target Milestone: --- Created attachment 180655 --> https://bugs.kde.org/attachment.cgi?id=180655&action=edit Window screenshotted as active window in Spectacle, note that width is now 1575, instead of expected 1440 SUMMARY When I use meta + down arrow on Firefox, to snap my window to the bottom of my secondary, vertical monitor, it get snapped slightly off-screen, around 50 pixels to the right. Monitor is 1440p vertical (1440 x 2560) Only seems to happen with Firefox, and only when the window is not already snapped. If the Firefox window is already snapped, I can use meta + left and then meta + right to fix the issue. Only happens on bottom half of the screen, snapping to top is fine STEPS TO REPRODUCE 1. Open Firefox with a vertical monitor 2. Snap using Meta + Down 3. Observe that the minimize / maximize / close buttons are now off screen OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, 6.14.3-arch1-1 (64-bit), Wayland KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.13.0 Qt Version: 6.9.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 499509] Icons for hidden folders are smaller than non-hidden ones
https://bugs.kde.org/show_bug.cgi?id=499509 Troy changed: What|Removed |Added CC||tro...@hotmail.co.uk --- Comment #18 from Troy --- Created attachment 178999 --> https://bugs.kde.org/attachment.cgi?id=178999&action=edit Screenshot of mixed icon sizes in Dolphin I also have the issue, except only with hidden files that have a thumbnail. Empty hidden folders are fine, but hidden folders with files inside that have thumbnails, or hidden files with thumbnails such as .gitconfig or .zshrc are smaller than they should be -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455572] New: "Present Windows" task action does nothing
https://bugs.kde.org/show_bug.cgi?id=455572 Bug ID: 455572 Summary: "Present Windows" task action does nothing Product: lattedock Version: 0.10.8 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: connor.t...@tuta.io Target Milestone: --- SUMMARY After update to plasma 5.25, the task action "Present Windows" on left click does not do anything. STEPS TO REPRODUCE 1. Plasma/Kwin 5.25.0-1 2. run `latte-dock -rd --default-layout` 3. Open multiple instances of any app 4. Click on the latte icon for that app OBSERVED RESULT The default left click action for tasks is to present windows. Windows are not presented and nothing is printed to the debug log. EXPECTED RESULT Functionality matching that of KWin's "Toggle Present Windows" should be observed. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.18.5-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 465690] New: When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop
https://bugs.kde.org/show_bug.cgi?id=465690 Bug ID: 465690 Summary: When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop Classification: Frameworks and Libraries Product: frameworks-plasma Version: 5.102.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libplasma Assignee: plasma-b...@kde.org Reporter: tdaw...@redhat.com CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: --- Created attachment 156211 --> https://bugs.kde.org/attachment.cgi?id=156211&action=edit notifications at bottom center SUMMARY *** When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop. This is on RHEL 8, 9 (and it's clones Alma and Rocky) as well as CentOS Stream 8 and 9. It's been happening since we first started using wayland, and has never changed. We thought it was due to an older wayland / plasma / kf5. But with the latest CentOS Stream 9, we have the same versions as Fedora for all of those things. We have also applied the patch that is coming out with kf5 103. It didn't help. https://invent.kde.org/frameworks/plasma-framework/-/commit/eda6caabc484544af8949d0ca0a3ea3ce333 It does the same on virtual machines as well as real hardware. *** STEPS TO REPRODUCE 1. Download CentOS Stream 9 live image 2. Run it. 3. Click on Menu, notifications, or open krunner. OBSERVED RESULT The pop-up dialogs will show up in the exact center, or bottom center of the desktop EXPECTED RESULT Menu should show up in bottom left. Notifications should show up at bottom right. krunner should show up on top center. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION libwayland 1.21.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 465690] When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop
https://bugs.kde.org/show_bug.cgi?id=465690 --- Comment #1 from Troy Dawson --- I forgot to say where to get a CentOS Stream 9 live image. They are currently only available on koji. https://cbs.centos.org/koji/taskinfo?taskID=3227396 x86_64 - https://cbs.centos.org/kojifiles/work/tasks/7397/3227397/CentOS-Stream-Image-KDE-Live.x86_64-9.0.0-9.0.20230212.iso aarch64 - https://cbs.centos.org/kojifiles/work/tasks/7398/3227398/CentOS-Stream-Image-KDE-Live.aarch64-9.0.0-9.0.20230212.iso -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 465690] When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop
https://bugs.kde.org/show_bug.cgi?id=465690 --- Comment #2 from Troy Dawson --- Created attachment 156212 --> https://bugs.kde.org/attachment.cgi?id=156212&action=edit menu at bottom center -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 465690] When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop
https://bugs.kde.org/show_bug.cgi?id=465690 --- Comment #3 from Troy Dawson --- Created attachment 156213 --> https://bugs.kde.org/attachment.cgi?id=156213&action=edit krunner a center -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 465690] When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop
https://bugs.kde.org/show_bug.cgi?id=465690 Troy Dawson changed: What|Removed |Added CC||niccolo.venera...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 465690] When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop
https://bugs.kde.org/show_bug.cgi?id=465690 Troy Dawson changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 465690] When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop
https://bugs.kde.org/show_bug.cgi?id=465690 --- Comment #8 from Troy Dawson --- (In reply to Nate Graham from comment #5) > You said, "It's been happening since we first started using wayland, and has > never changed." How long has that been? Are we talking about weeks, months, > years... Can you give a sense of when you first hit the issue? Years. At least since 2020 with plasma 5.18.4. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 465690] When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop
https://bugs.kde.org/show_bug.cgi?id=465690 --- Comment #9 from Troy Dawson --- (In reply to Nate Graham from comment #6) > If you install the system, does the problem persist? In other words, does it > only reproduce in the live session? > Live or installed, it gives the same results. > Are you sunning this in a VM, or bare metal? > Both Virtual Machines and bare metal. > I also notice that graphics seem to be broken as there's no blur behind the > popups. Perhaps a clue... Possible. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 465690] When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop
https://bugs.kde.org/show_bug.cgi?id=465690 --- Comment #10 from Troy Dawson --- (In reply to Méven Car from comment #7) > Do you use the official Qt 5.12.3 version or the KDE Qt patch collection > (https://community.kde.org/Qt5PatchCollection) ? We are using the KDE QT patch collection. I know the patch collection is beyond 5.12.3 now. But at the time that 5.12.3 was the latest, it had this bug on RHEL, but not on Fedora. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 465690] When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop
https://bugs.kde.org/show_bug.cgi?id=465690 --- Comment #12 from Troy Dawson --- (In reply to Nate Graham from comment #11) > What Qt version and patch collection version are you using right now where > you can reproduce the bug? Oh, I think I put the wrong version in the comment above. 5.15.3 and the patchset that created 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 465690] When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop
https://bugs.kde.org/show_bug.cgi?id=465690 --- Comment #14 from Troy Dawson --- (In reply to Nate Graham from comment #13) > Thanks. Does the issue go away if you upgrade to 5.15.8 with the associated > KDE patches for that release? That will take me some time to rebuild those, along with their dependencies, but I can try that. I'm not confident it will help. At the time we went to qt5 5.15.3 we were the save version and patches as Fedora, yet they were not showing the problem. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 465690] When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop
https://bugs.kde.org/show_bug.cgi?id=465690 --- Comment #16 from Troy Dawson --- Just letting you know that I've gotten the latest QT5 stack built. I am now rebuilding the KDE stack on top of it. Should have it done by the end of the week. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 465690] When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop
https://bugs.kde.org/show_bug.cgi?id=465690 Troy Dawson changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #17 from Troy Dawson --- I have rebuild qt5 so that it matches the latest Fedora version, 5.15.8. I have rebuild the KDE Plasma Desktop so it matches the latest Fedora version 5.27.2, and the kf5 to 5.103, and everything KDE related I can think of to what is in the latest stable release of Fedora. I have to say I like several of the updates, but when running Wayland, the dialogs still are in the center. I have added a new user just incase there was some leftover configuration. Didn't help. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 465690] When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop
https://bugs.kde.org/show_bug.cgi?id=465690 --- Comment #18 from Troy Dawson --- I did a fresh minimal install so there was no qt5 or kde packages installed. Then installed all the new qt5 and kde plasma desktop that I had compiled. Just incase there was some random config file giving issues. Still have the problem. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 465690] When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop
https://bugs.kde.org/show_bug.cgi?id=465690 Troy Dawson changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |NOT A BUG --- Comment #20 from Troy Dawson --- Found and fixed. In the end it was a distribution specific bug. I'm sorry for the noise I created. In the end it was kf5-plasma. There was a conditional in it's spec file that on RHEL based machines, it didn't get the wayland-devel package during building, and it didn't get a wayland cache file. I didn't expect it to be a kf5 error, and my greps through the various spec files were not catching this conditional. Once again, sorry for the noise. And thank you to everyone who helped track this down. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445449] Shutting down from Plasma Wayland causes shutdown to be delayed while stopping SDDM
https://bugs.kde.org/show_bug.cgi?id=445449 Troy Dawson changed: What|Removed |Added CC||tdaw...@redhat.com --- Comment #32 from Troy Dawson --- What was the real problem with this? Why was this kernel related? I haven't seen anything relating to the real problem, just work around so things don't take long to shut down. We are seeing the same thing (Slow SDDM shutdown) and worse on CentOS Stream 8. All of it is fine with an older kernel, but the newer kernel is having issues. Note: We are seeing a blank screen on SDDM startup. If you use a different desktop manager, then ksplash is blank. And then if you lock your screen, you never get a password prompt to unlock it. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 444174] New: ksmserver-logout-greeter not appearing on all displays.
https://bugs.kde.org/show_bug.cgi?id=444174 Bug ID: 444174 Summary: ksmserver-logout-greeter not appearing on all displays. Product: ksmserver Version: 5.23.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: harveyde...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY I am not if this is specific to the greeter or just a multi-monitor issue in general as explained in the additional information section. After clicking shutdown, restart or logout in the system menu it should launch the logout greeter to confirm or cancel on ALL monitors connected to your system. This is no longer happening which due to my setup means I can not always see/interact with that menu. [Monitor 1 (Output is a clone of Monitor 3)] [Monitor 2] [Monitor 3 (Primary display)] The greeter is only appearing on Monitor 2. However alt+tab menu shows 3 instances of the greeter window despite only being shown on 1 display https://i.imgur.com/paHd477.png STEPS TO REPRODUCE 1. Login (Using xorg session) 2. Try shutdown while using a mutli-monitor setup and observe logout greeter behaviour. OBSERVED RESULT Logout greeter asking you to confirm your choice does not appear on primary monitor. EXPECTED RESULT All monitors connected to system should display logout greeter. SOFTWARE/OS VERSIONS Solus KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 Nvidia driver: 470.63.01 ADDITIONAL INFORMATION Elder Scrolls Online has started opening on Monitor 2 which has only started happening after upgrading to Plasma 5.23.0. I managed to solve this problem by changing ESO to use "Fullscreen" instead of "Fullscreen windowed". It still opens on monitor 2 now but will automatically move to my primary display after a couple of seconds with this option enabled. Unable to reproduce with other games so not sure if not opening on the correct display is just a coincidence. After login the desktop wallpaper of the primary display uses the default wallpaper of my distribution for about 20 seconds before it applies my custom wallpaper. Monitor 2 always has my custom wallpaper set immediately upon login. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 444174] ksmserver-logout-greeter not appearing on all displays.
https://bugs.kde.org/show_bug.cgi?id=444174 Troy Harvey changed: What|Removed |Added CC||harveyde...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443787] Multimonitor Telegram click on video/picture opens on other screen flickers wildly
https://bugs.kde.org/show_bug.cgi?id=443787 Troy Harvey changed: What|Removed |Added CC|harveyde...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440849] New: Titlebar disappears in certain circumstances
https://bugs.kde.org/show_bug.cgi?id=440849 Bug ID: 440849 Summary: Titlebar disappears in certain circumstances Product: kwin Version: 5.22.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: tdaw...@redhat.com Target Milestone: --- SUMMARY The titelbar disappears when certain things happens. It is recoverable but inconvenient. STEPS TO REPRODUCE 1. Log into the desktop, picking Plasma(Wayland) 2. Change your window decorations to Plastik (System-Settings-> Appearance -> Window Decorations -> Plastik) 3. Start a program. For this example open Dolphin (graphical file manager). 4. Maximize the window. (Click on upper right button, just left of the X button) 5. Completely close the program. (Click the upper X) 6. Start the program. OBSERVED RESULT The window comes up maximized, but the top titlebar is gone. EXPECTED RESULT The window comes up maximized, but the top titlebar is there. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This doesn't happen in X11. This doesn't happen with the breeze window decorations. It was originally observed in plasma/kwin 5.21.3. I've been able to reproduce this in a fresh KDE install, as well as starting with a fedora workstation (with gnome installed) and then installing KDE Plasma Dekstop. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440849] Titlebar disappears in certain circumstances
https://bugs.kde.org/show_bug.cgi?id=440849 --- Comment #1 from Troy Dawson --- Created attachment 140643 --> https://bugs.kde.org/attachment.cgi?id=140643&action=edit Proper titlebar -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440849] Titlebar disappears in certain circumstances
https://bugs.kde.org/show_bug.cgi?id=440849 --- Comment #2 from Troy Dawson --- Created attachment 140644 --> https://bugs.kde.org/attachment.cgi?id=140644&action=edit Titlebar missing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440849] Titlebar disappears in certain circumstances
https://bugs.kde.org/show_bug.cgi?id=440849 --- Comment #4 from Troy Dawson --- It is fairly interactive. You can right click on it, and get the normal right click selections. If I click around I can eventually hit some buttons, but they seems to be out of place. But it does seem to be "invisible" versus "gone". -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 438458] Yakuake flashes solid color when closing it in Plasma 5.22 in X11
https://bugs.kde.org/show_bug.cgi?id=438458 Troy Harvey changed: What|Removed |Added CC||harveyde...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 438823] "kded5 has requested to open the wallet": no information, no way to reject
https://bugs.kde.org/show_bug.cgi?id=438823 Troy Harvey changed: What|Removed |Added CC||harveyde...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 436442] kwallet fails to open at login most of the time.
https://bugs.kde.org/show_bug.cgi?id=436442 Troy Harvey changed: What|Removed |Added CC||harveyde...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 437788] Kded5 asks to open kwallet everytime the system starts
https://bugs.kde.org/show_bug.cgi?id=437788 Troy Harvey changed: What|Removed |Added CC||harveyde...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 437788] Kded5 asks to open kwallet everytime the system starts
https://bugs.kde.org/show_bug.cgi?id=437788 Troy Harvey changed: What|Removed |Added CC|harveyde...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 436442] kwallet fails to open at login most of the time.
https://bugs.kde.org/show_bug.cgi?id=436442 Troy Harvey changed: What|Removed |Added CC|harveyde...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 438823] "kded5 has requested to open the wallet": no information, no way to reject
https://bugs.kde.org/show_bug.cgi?id=438823 Troy Harvey changed: What|Removed |Added CC|harveyde...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 474742] New: kstars crashes (closes) immediately after starting ekos on remote computer.
https://bugs.kde.org/show_bug.cgi?id=474742 Bug ID: 474742 Summary: kstars crashes (closes) immediately after starting ekos on remote computer. Classification: Applications Product: kstars Version: 3.6.6 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: troym...@att.net Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Works fine running on the Rpi4. Tries 3 PCs with same result. 2 nights ago, everything worked fine. Issue started when trying to run last night using the same procedure I've been using. STEPS TO REPRODUCE 1. Start kstars 2. Start ekos. 3. OBSERVED RESULT kstars closes EXPECTED RESULT kstars keeps running with ekos. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION running latest Astroberry build and no packages have been updated since 2 days ago. No updates to packages available as of today. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 477742] New: Primary camera has to be restarted after each exposure
https://bugs.kde.org/show_bug.cgi?id=477742 Bug ID: 477742 Summary: Primary camera has to be restarted after each exposure Classification: Applications Product: kstars Version: 3.6.7 Platform: Other OS: Other Status: REPORTED Severity: major Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: troym...@att.net Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Make a focus adjustment 2. Try to take a picture of any exposure 3. OBSERVED RESULT Exposure fails EXPECTED RESULT Successful multiple exposures without disconnecting camera SOFTWARE/OS VERSIONS - Rpi 4 running astroberry Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Nearly every time after the first adjustment of focus, the primary camera has to be disconnected in INDI then reconnected to take an exposure. It can take multiple up to the point of a focus adjustment. Then it has to be disconnected and reconnected to take another frame for the rest of the evening otherwise it tries the exposure 3 times before failing. If I use the INDI control panel and trigger an exposure manually, it does the same thing. Restarting the driver does not help. Camera is a ZWO428MC. Not sure how to find any logs that might show what is going on. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476422] New: kdeconnectd does not start - "Could not store certificate file"
https://bugs.kde.org/show_bug.cgi?id=476422 Bug ID: 476422 Summary: kdeconnectd does not start - "Could not store certificate file" Classification: Applications Product: kdeconnect Version: 23.04.3 Platform: RedHat Enterprise Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: tdaw...@redhat.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. On a RHEL 9 or CentOS Stream 9 system, log in with kde-connect installed. or manually 1. #kill all kdeconnect processes 2. rm -rf $HOME/.config/kdeconnect/ 3. /usr/libexec/kdeconnectd OBSERVED RESULT Normal Login: - A crash with normal KDE crash icons and popups Manual start: libEGL warning: failed to get driver name for fd 0 libEGL warning: MESA-LOADER: failed to retrieve device information libEGL warning: failed to get driver name for fd 0 kdeconnect.core: Certificate from "/home/quake/.config/kdeconnect/certificate.pem" is not valid kdeconnect.daemon: "KDE Connect" : "Could not store certificate file: /home/quake/.config/kdeconnect/certificate.pem" $ ls -lh $HOME/.config/kdeconnect/ total 8.0K -rw---. 1 quake quake0 Oct 31 15:07 certificate.pem -rw-r--r--. 1 quake quake 24 Oct 31 15:07 config -rw---. 1 quake quake 1.7K Oct 31 15:07 privateKey.pem EXPECTED RESULT Login: It should just start and not be seen Manual: It just starts with no output, and stays running in that console. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 108 / 23.04.3 Qt Version: 5.15.9-7 ADDITIONAL INFORMATION This has been happening for a long time, not just these latest versions. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476422] kdeconnectd does not start - "Could not store certificate file"
https://bugs.kde.org/show_bug.cgi?id=476422 --- Comment #1 from Troy Dawson --- Crash Report: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x0) at /usr/include/c++/11/bits/atomic_base.h:486 #5 QAtomicOps::loadRelaxed (_q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=0x0) at /usr/include/qt5/QtCore/qbasicatomic.h:107 #7 QtPrivate::RefCount::ref (this=0x0) at /usr/include/qt5/QtCore/qrefcount.h:55 #8 QString::QString (other=..., this=, this=, other=...) at /usr/include/qt5/QtCore/qstring.h:1094 #9 KdeConnectConfig::deviceId (this=) at /usr/src/debug/kde-connect-23.04.3-2.el9.next.x86_64/core/kdeconnectconfig.cpp:131 #10 0x7f204c1adeb7 in NetworkPacket::createIdentityPacket (np=0x7fffe5b525d0) at /usr/src/debug/kde-connect-23.04.3-2.el9.next.x86_64/core/networkpacket.cpp:50 #11 0x7f204c19a4c0 in LanLinkProvider::broadcastToNetwork (this=0x55b2bd9d7540) at /usr/src/debug/kde-connect-23.04.3-2.el9.next.x86_64/core/backends/lan/lanlinkprovider.cpp:138 #12 LanLinkProvider::broadcastToNetwork (this=0x55b2bd9d7540) at /usr/src/debug/kde-connect-23.04.3-2.el9.next.x86_64/core/backends/lan/lanlinkprovider.cpp:124 #13 0x7f204a8dbca9 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #14 0x7f204a8def2e in QTimer::timeout(QTimer::QPrivateSignal) () from /lib64/libQt5Core.so.5 #15 0x7f204a8d2ccf in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7f204b5af533 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7f204a8a7998 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #18 0x7f204a8f8b13 in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #19 0x7f204a8f940c in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #20 0x7f2048fc8e2f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #21 0x7f204901e108 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #22 0x7f2048fc65f3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #23 0x7f204a8f9818 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #24 0x7f204a8a63a2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #25 0x7f204a8ae8d4 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #26 0x55b2bbb360ae in main (argc=, argv=) at /usr/src/debug/kde-connect-23.04.3-2.el9.next.x86_64/daemon/kdeconnectd.cpp:185 [Inferior 1 (process 2674) detached] -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476422] kdeconnectd does not start - "Could not store certificate file"
https://bugs.kde.org/show_bug.cgi?id=476422 --- Comment #2 from Troy Dawson --- Although this sounds similar to the Suse Tumbleweed bugs, we have already checked that both qca-qt5 and qca-qt5-ossl are installed. We eventually installed all the qca packages, with no changes. We have also turned off selinux to see if that was the problem. It wasn't. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491956] New: Touchscreen does not resize when window resizes
https://bugs.kde.org/show_bug.cgi?id=491956 Bug ID: 491956 Summary: Touchscreen does not resize when window resizes Classification: Plasma Product: kwin Version: 6.1.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libinput Assignee: kwin-bugs-n...@kde.org Reporter: tdaw...@redhat.com Target Milestone: --- SUMMARY When you change the resolution of your screen, the touchscreen does not change with it. This causes you touches to be places you are not expecting. Note: This does not happen when you re-scale your display, only when you change the resolution. STEPS TO REPRODUCE 1. Start with a normal Plasma 6 install on a machine with a touchscreen. 2. Change the resolution. Possibly most important, change the aspect ratio (16:9) -> (5:4) 3. Try touching things, especially things not in the center of the screen. I have found that using the onscreen keyboard is the easiest way to see this, because it highlights the keys that are pushed. But it is not related to the keyboard. OBSERVED RESULT Depending on how dramatic the resolution change, and how far off center (both horizontal and vertical) I am touching, where I am touching, and where my desktop thinks I'm touching can be wayyy off. EXPECTED RESULT The desktop should think I am touching where I am touching. SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Fedora 40 and 41 (Rawhide) KDE Plasma Version: 6.1.3 and 6.1.4 KDE Frameworks Version: 6.4.0 and 6.5.0 Qt Version: 6.7.2 Kernel: 6.9.9 and 6.11.0-rc3 ADDITIONAL INFORMATION Everything I have tested has been running Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 433812] New: KStars Android APK issue
https://bugs.kde.org/show_bug.cgi?id=433812 Bug ID: 433812 Summary: KStars Android APK issue Product: kstars Version: unspecified Platform: Android OS: Android 7.x Status: REPORTED Severity: major Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: joey.t...@gmail.com Target Milestone: --- SUMMARY Tried to install KStars 3.3.7 on a Motorola Nexus 6 running stock Android 7.1.1 STEPS TO REPRODUCE 1. Downloaded APK from https://m.apkpure.com/kstars/org.kde.kstars.lite 2. Turned on Unknown sources to install APK from other sources than Play Store 3. After launching the APK and trying to install it states App Not Installed "This app isn't compatible with your phone" ADDITIONAL INFORMATION I was able to install 3.0.1 but 3.3.3 also had the same issue with "This app isn't compatible with your phone" -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 421213] Can no longer copy/move files into a symlinked folder
https://bugs.kde.org/show_bug.cgi?id=421213 Troy Harvey changed: What|Removed |Added CC|harveyde...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421312] Dolphin - cut and paste to symbolic link directory gives prompt to rename when it should not
https://bugs.kde.org/show_bug.cgi?id=421312 Troy Harvey changed: What|Removed |Added CC||harveyde...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421213] Regression: Can no longer copy/move files into a symlinked folder
https://bugs.kde.org/show_bug.cgi?id=421213 Troy Harvey changed: What|Removed |Added CC||harveyde...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot
https://bugs.kde.org/show_bug.cgi?id=343518 --- Comment #56 from Troy Volin --- Everything about restore has been intermittent for me on 5.5.x and 5.6.x. Konsole restore, Kate and Kwrite restore, ... The only thing that has actually been consistent, oddly, is virt-manager (which I think is GTK3). Fedora doesn't present a "save session" on the Leave menu, but I can do it through qdbus. I guess I'll give that a try, and use "saved session" from kdm. Also, I think this is still the case: libreoffice acts as if it had crashed if it is running at session end (logout/restart). Maybe it doesn't talk xsm and ignores the shutdown request, but I doubt it. I think it's more likely related. It's probably no coincidence that it is omitted from ksmserverrc and it was never told to quiesce. On Thu, May 19, 2016, 4:13 PM Piotr Mierzwinski via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=343518 > > --- Comment #55 from Piotr Mierzwinski --- > (In reply to Wolfgang Bauer from comment #54) > > > > I don't how it's possible that restoring Firefox is working in > openSUSE :/. > > > You or someone else told about it. > > > Is it possible that they somehow patched plasma-workspace? > > > > No. > > > > But now that I come to think of it, openSUSE's Firefox (and Thunderbird) > > packages include some custom KDE(4) integration. This *might* make the > > difference between it being restored in openSUSE but not in other > > distributions... > > Though I'm not sure if that detail is really relevant here, the > integration > > is more about using the KDE file dialog and certain KDE settings (like > > preferred applications and proxy settings), things like that. > > Yes. I agree. It seems to be not related. So my question still remains > opened > :/.. > > > > If you are using openSUSE then could you please check at least new > Opera, if > > > it will be restore after relogin. > > > > Well, I did install Opera now (37.0.2178.32), and indeed it is not > restored > > (nor saved to ksmserverrc). > > > > But I tried with KDE4 too, and it isn't restored/saved there as well. > > I can confirm. I tested it in Mageia 5 and new Opera is not restored as > well. > > BTW. > Recently, using Antergos I observed that konsole is restored randomly. > Every > few running (of Plasma) is not restored. It looks similar to behavior > Kubuntu > 15.x with Plasma 5.4.x > > -- > You are receiving this mail because: > You voted for the bug. > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 Troy Volin changed: What|Removed |Added CC||tmvo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 --- Comment #116 from Troy Volin --- I find that the leak persists even when the screensaver kicks in (overnight), so I wake to "kquitapp5 plasmashell && sleep 10s && plasmashell &>/dev/null & disown" every day. I have a handful of systray icons which are handled by the xembed-sni-proxy, and I wonder if that contributes. Also, if I let plasmashell's stdout and stderr come to my terminal window, I see xcb errors every time i move my mouse pointer over the taskbar and hover from one window marker to the next. I don't know if either of these facts are helpful. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 --- Comment #123 from Troy Volin --- I know it's not exactly appropriate to discuss distro-specifics here, but I know Rex Dieter is subscribed to this bug. Of the two patches listed here as resolving this (very important) problem, one is for plasma-breeze and the other is for qt5-qtdeclarative. It looks like the latter is only committed against QT 5.6. Rex (or other Fedora-type person), how can we communicate to the relevant Fedora package maintainers that we need a backport of this for QT 5.5.1 ? (It looks like KDE bug 357800 for breeze is already in a 5.5.x context, and not a problem in master.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 --- Comment #127 from Troy Volin --- Thanks, Rex! And thanks to all who diagnosed this. -- You are receiving this mail because: You are watching all bug changes.
