[kwin] [Bug 450009] New: cannot move applications to different monitor in overview effect
https://bugs.kde.org/show_bug.cgi?id=450009 Bug ID: 450009 Summary: cannot move applications to different monitor in overview effect Product: kwin Version: 5.24.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: shawn.peter...@posteo.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 *** In the overview effect, you cannot drag windows from one monitor to another in multimonitor setups. Overview shows on all monitors with the apps showing on the correct monitor, which is great. Just need to be able to move them to a different one. As an aside, I realize that you can drag from the actual monitor to the other, but this would still be very useful when you have a lot of applications open at the same time. STEPS TO REPRODUCE 1. activate overview with at least two active monitors 2. try to move an application to another monitor. 3. OBSERVED RESULT The application does not move and goes right back to the starting place in the overview effect. EXPECTED RESULT The application should move to the expected monitor. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: opensuse tumbleweed (available in About System) KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 466298] KDE Network Manager shows incorrect Primary Nameserver
https://bugs.kde.org/show_bug.cgi?id=466298 Shawn changed: What|Removed |Added CC||sh...@n4hab.com --- Comment #1 from Shawn --- Seeing this as well with the same software versions as qtm...@gmail.com except Networkmanager updated to 1.42.2-1 today with the same result. Also noticed the IP displayed in IPv4 Primary Nameserver changes with every reboot. Mine is displaying 40.211.92.136 (Eli Lilly in Germany), however I've also seen IPs from the USPS and various other organizations. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445259] Several Chromium-based browsers suddenly fail to bring up their browser windows on Wayland
https://bugs.kde.org/show_bug.cgi?id=445259 Shawn changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED CC||sh...@n4hab.com --- Comment #16 from Shawn --- Seeing this again, spontaneously just started using Arch, Plasma 5.27.5, Frameworks 5.106.0, QT 5.15.9 . Tested it with Brave, Chromium, Evolution email and Dolphin. Icon goes orange but won't open the window from the taskbar, unless the browser isn't open or launched. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445259] Several Chromium-based browsers suddenly fail to bring up their browser windows on Wayland
https://bugs.kde.org/show_bug.cgi?id=445259 Shawn changed: What|Removed |Added Version|5.23.2 |5.27.5 Platform|openSUSE|Archlinux -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483128] New: vertical floating panel bleeds into adjacent monitor when window maximized.
https://bugs.kde.org/show_bug.cgi?id=483128 Bug ID: 483128 Summary: vertical floating panel bleeds into adjacent monitor when window maximized. Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: shawn.peter...@posteo.net CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY *** In a multi-monitor setup, I have a vertical panel on the left side of the right monitor (so, moving the cursor past the panel gets to the left monitor). The panel is set to floating. When it reverts from maximized windows, the panel bleeds several pixels into the left monitor. In my system, it covers up part of the close button (and all the way down) of screens on the left monitor. STEPS TO REPRODUCE 1. Have floating panel set vertically on screen edge adjacent to edge of other monitor in multi-monitor setup. 2. maximize a window on the same screen as the panel (not full-screen). 3. Panel stops floating, but bleeds into the other monitor. OBSERVED RESULT Bleeds over to the other monitor, covering parts up. EXPECTED RESULT Not cover parts of other monitor. SOFTWARE/OS VERSIONS Linux/KDE Plasma: endeavouros (arch) (available in About System) KDE Plasma Version: plasma 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.0.2 ADDITIONAL INFORMATION It is not deal breaking. I just tested turning off floating panel and it works as intended (not bleeding over). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483128] vertical floating panel bleeds into adjacent monitor when window maximized.
https://bugs.kde.org/show_bug.cgi?id=483128 --- Comment #1 from Shawn --- Created attachment 166888 --> https://bugs.kde.org/attachment.cgi?id=166888&action=edit vertical tab bleed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483128] vertical floating panel bleeds into adjacent monitor when window maximized.
https://bugs.kde.org/show_bug.cgi?id=483128 --- Comment #2 from Shawn --- (In reply to Shawn from comment #0) > SUMMARY > *** > In a multi-monitor setup, I have a vertical panel on the left side of the > right monitor (so, moving the cursor past the panel gets to the left > monitor). The panel is set to floating. When it reverts from maximized > windows, the panel bleeds several pixels into the left monitor. In my > system, it covers up part of the close button (and all the way down) of > screens on the left monitor. > > > STEPS TO REPRODUCE > 1. Have floating panel set vertically on screen edge adjacent to edge of > other monitor in multi-monitor setup. > 2. maximize a window on the same screen as the panel (not full-screen). > 3. Panel stops floating, but bleeds into the other monitor. > > OBSERVED RESULT > Bleeds over to the other monitor, covering parts up. > > EXPECTED RESULT > Not cover parts of other monitor. > > SOFTWARE/OS VERSIONS > Linux/KDE Plasma: endeavouros (arch) > (available in About System) > KDE Plasma Version: plasma 6.0.1 > KDE Frameworks Version: 6.0.0 > Qt Version: 6.0.2 > > ADDITIONAL INFORMATION > It is not deal breaking. I just tested turning off floating panel and it > works as intended (not bleeding over). EDIT: Also, this is on an amd ryzen 5 5600 cpu, and amd radeon rx 6600 fwiw. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482142] drag in drop files in Google Chrome renders Chrome unusable
https://bugs.kde.org/show_bug.cgi?id=482142 Shawn changed: What|Removed |Added CC||sh...@n4hab.com --- Comment #49 from Shawn --- kwin 6.0.5-2 was just released to Arch and seems to have fixed the issue. I can't make it crash when dragging something in Chromium, Brave etc. So nice to be able to switch the browser back to Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 452708] New: Option to pull accent color from Android 13
https://bugs.kde.org/show_bug.cgi?id=452708 Bug ID: 452708 Summary: Option to pull accent color from Android 13 Product: kdeconnect Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: marioman1203...@gmail.com Target Milestone: --- With Android 13's introduction of Material You and customizable accent colors, I would like to see a way to use KDE Connect to sync said accent color from Android to Plasma. IE, my current accent color on Android is #EADDFF, and I'd want KDE Connect to set my Plasma accent color to the same value. When I change the accent on my phone, I'd like it to reflect in KDE as well. The implementation I'm interested in is unidirectional, although I believe it could technically be implemented bidirectionally, as there's other apps on Android that let you modify accent colors. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 387455] Column view in Dolphin
https://bugs.kde.org/show_bug.cgi?id=387455 Shawn changed: What|Removed |Added CC||shawn.peter...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 444284] New: On a multi-monitor setup, the screenlocker persists visually on the secondary monitor when unlocked.
https://bugs.kde.org/show_bug.cgi?id=444284 Bug ID: 444284 Summary: On a multi-monitor setup, the screenlocker persists visually on the secondary monitor when unlocked. Product: kscreenlocker Version: 5.23.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: shawn.peter...@gmx.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY On a multi-monitor setup, the screenlocker persists visually on the secondary monitor when unlocked. Hilariously, if you click on it, it goes away, but then comes back when you click back on the primary monitor. This does not seem to affect functionality as you can drag windows over there and it will display fine. It also seems to go away after about a minute. STEPS TO REPRODUCE 1. Have two monitors, and lock the screen. 2. unlock. 3. OBSERVED RESULT See the screen locker on the secondary monitor after unlocked. EXPECTED RESULT No screen locker. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: opensuse tumbleweed (available in About System) KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION My system is running nvidia 470.74. Also, this is on x11. Have not looked at wayland. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 444284] On a multi-monitor setup, the screenlocker persists visually on the secondary monitor when unlocked.
https://bugs.kde.org/show_bug.cgi?id=444284 --- Comment #1 from Shawn --- I just noticed it seems to only happen when the computer is asleep (wrong word? Black screen that wakes to screen locker). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 456972] custom shortcut, does not work anymore
https://bugs.kde.org/show_bug.cgi?id=456972 Shawn changed: What|Removed |Added CC||sh...@n4hab.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 456972] custom shortcut, does not work anymore
https://bugs.kde.org/show_bug.cgi?id=456972 --- Comment #14 from Shawn --- I can add a shortcut to a non-KDE app, or use some of the existing shortcuts, but there is no way to add or use a shortcut to Kate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393781] wallpaper cannot span multiple screens
https://bugs.kde.org/show_bug.cgi?id=393781 Shawn changed: What|Removed |Added CC||shawn.peter...@gmx.com --- Comment #1 from Shawn --- This is a couple of years old now, but I too would like to see this implemented. Just as an fyi, there is an external program that will accomplish this in the meantime: superpager. It's a little geeky on the interface, but it gets the job done. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 427186] New: feature request: smart playlist
https://bugs.kde.org/show_bug.cgi?id=427186 Bug ID: 427186 Summary: feature request: smart playlist Product: elisa Version: 20.08.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: shawn.peter...@gmx.com Target Milestone: --- SUMMARY Would be nice to have a smart playlist that can fetch songs dynamically based on specified criteria. My music collection is large enough now that this is basically the only way I listen to music now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427253] New: konsole window doesn't open on correct (in focus) monitor, or tile correctly
https://bugs.kde.org/show_bug.cgi?id=427253 Bug ID: 427253 Summary: konsole window doesn't open on correct (in focus) monitor, or tile correctly Product: kwin Version: 5.19.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: shit...@gmail.com Target Milestone: --- SUMMARY Prior to updating to kwin 5.19.5 and konsole 20.08.1, an opened konsole windows would open on the monitor that is in focus and tile appropriately. Now it ignores tiling and always opens in the top left of the main monitor. Window tiling is set to minimal overlap. STEPS TO REPRODUCE 1. have the above mentioned versions of software 2. open konsole through start menu, krunner or keyboard shortcut 3. OBSERVED RESULT all konsole windows open in top left corner of main monitor EXPECTED RESULT windows should tile side by side on whatever monitor is in focus SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Manjaro KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION I have a konsole window rule to set size (but not position). Editing this didn't effect anything. All other window behave correctly so maybe this report belongs in the konsole section? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427253] konsole window doesn't open on correct (in focus) monitor, or tile correctly
https://bugs.kde.org/show_bug.cgi?id=427253 --- Comment #1 from shawn --- (In reply to shawn from comment #0) > SUMMARY > Prior to updating to kwin 5.19.5 and konsole 20.08.1, an opened konsole > windows would open on the monitor that is in focus and tile appropriately. > Now it ignores tiling and always opens in the top left of the main monitor. > Window tiling is set to minimal overlap. > > STEPS TO REPRODUCE > 1. have the above mentioned versions of software > 2. open konsole through start menu, krunner or keyboard shortcut > 3. > > OBSERVED RESULT > all konsole windows open in top left corner of main monitor > > EXPECTED RESULT > windows should tile side by side on whatever monitor is in focus > > SOFTWARE/OS VERSIONS > Linux/KDE Plasma: KDE Manjaro > KDE Plasma Version: 5.19.5 > KDE Frameworks Version: 5.74.0 > Qt Version: 5.15.1 > > ADDITIONAL INFORMATION > I have a konsole window rule to set size (but not position). Editing this > didn't effect anything. > > All other window behave correctly so maybe this report belongs in the > konsole section? Edit: after multiple restarts it seems that the konsole window is not limited to the upper left but will sometimes appear in the middle or other locations still with windows sitting on top of each other instead of obeying window rules -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427253] konsole window doesn't open on correct (in focus) monitor, or tile correctly
https://bugs.kde.org/show_bug.cgi?id=427253 --- Comment #3 from shawn --- (In reply to Vlad Zahorodnii from comment #2) > Is this issue gone after removing .config/konsolerc file? (make a backup > copy of your konsolerc file before actually removing it) renaming/removing this file caused the position to reset but did not fix the tiling issue. Windows still stack instead of obeying minimal overlap. I can also set the position that the window will open with: DP-0 DVI-D-0 XPosition=2560 DP-0 DVI-D-0 YPosition=29 (I have 2 monitors DP and DVI) here is the full config: [Desktop Entry] DefaultProfile=Profile 1.profile [DownloadDialog Settings] Height 1080=494 Width 1920=700 [Favorite Profiles] Favorites=small font.profile,Shell.profile [MainWindow] DP-0 DVI-D-0 Height 1080=484 DP-0 DVI-D-0 Height 1440=484 DP-0 DVI-D-0 Width 1920=648 DP-0 DVI-D-0 Width 2560=648 DP-0 DVI-D-0 XPosition=2560 DP-0 DVI-D-0 YPosition=29 Height 1080=484 Height 1440=484 State=/wD9AogAAAHGBAQICPwA ToolBarsMovable=Disabled Width 1920=648 Width 2560=648 [TabBar] ExpandTabWidth=true TabBarPosition=Top [ThumbnailsSettings] ThumbnailCtrl=true I've also tried clearing out all my kwin window rules with no success -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 440089] New: python syntax highlighting breaks with binary strings
https://bugs.kde.org/show_bug.cgi?id=440089 Bug ID: 440089 Summary: python syntax highlighting breaks with binary strings Product: kate Version: 21.04.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: shit...@gmail.com Target Milestone: --- Created attachment 140221 --> https://bugs.kde.org/attachment.cgi?id=140221&action=edit screenshot of issue SUMMARY Binary string highlighting affects the entire file after the string ends. So if strings are highlighted red, typing `b"test"` will cause all text after that to appear red note that the code runs as expected, so its not a syntax error STEPS TO REPRODUCE 1. Open python file in kate 2. Add a line like print(b"test") to the file OBSERVED RESULT All text after the binary string is highlighted the same color as the string (changing the color doesn't affect the bug) EXPECTED RESULT the color should revert back to normal after closing quote SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION note that I am using Qtile as a standalone WM but still have a full KDE environment installed but not in use. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 440089] python syntax highlighting breaks with binary strings
https://bugs.kde.org/show_bug.cgi?id=440089 --- Comment #2 from shawn --- (In reply to Jan Paul Batrina from comment #1) > Hello, thanks for the bug report! > > This will be fixed if > https://invent.kde.org/frameworks/syntax-highlighting/-/merge_requests/227 > is merged cool thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 439107] New: Do-not-Disturb integration
https://bugs.kde.org/show_bug.cgi?id=439107 Bug ID: 439107 Summary: Do-not-Disturb integration Product: kdeconnect Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: shawnshy...@mail.com Target Milestone: --- Hi, I toggle the Do-Not-Disturb on my phone a lot. I have an NFC tag on my desk to do so, but it's a 50/50 chance of working. What I would consider ideal is if KDE Connect had a way to toggle DND for the following use-cases (obviously just the ones I thought of, and I welcome others to suggest other use-cases): - User's phone has DND off normally, but DND enables when they get on their PC. if their PC locks/sleeps from inactivity, it should disable DND. this way, when they're on their PC, they'll see the notifications there, otherwise, their phone will audibly/physically notify them. (my use-case) - User toggles on DND on their Desktop's OS, and their phone also goes into DND. When they toggle it off, DND toggles off on their phone as well. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 421974] [Wayland] Spectacle Doesn't Copy To The Clipboard The Screenshot Automatically
https://bugs.kde.org/show_bug.cgi?id=421974 Shawn changed: What|Removed |Added CC||sh...@n4hab.com --- Comment #12 from Shawn --- Still seeing this with Spectacle 21.04.2, Plasma 5.22.2, Frameworks 5.83.0, Qt 5.15.2 using Wayland. Screenshots using Spectacle show up in Clipboard and will copy/paste to email but can't paste to Facebook or Twitter using any browser. Copying a saved graphic from a drive to clipboard will paste to FB and Twitter. Can reproduce this on all 3 local KDE machines. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 431109] KDE Networkmanager can not disable IPv6
https://bugs.kde.org/show_bug.cgi?id=431109 Shawn changed: What|Removed |Added CC||sh...@n4hab.com --- Comment #7 from Shawn --- Would love to see this merged. So important to KDE. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 407918] Does not find music on other partition (ext4 or NTFS) even when added to search paths
https://bugs.kde.org/show_bug.cgi?id=407918 Shawn changed: What|Removed |Added CC||shawn.peter...@gmx.com --- Comment #28 from Shawn --- I am unclear if this bug is still open, but I am having the same issue on my manjaro system. Difference being my music folder is the main partition in the default place (still ext4). Sometimes it scans the music, sometimes it does not. And when it does find them, it is probably gone when I restart the application. It can find them and play them just fine through the internal file browser. I have better luck with the "scan files directly" toggled on, but better only means that I sometimes see the music. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424223] Impossible to click on the taskbar to bring up Dota 2 after a recent update
https://bugs.kde.org/show_bug.cgi?id=424223 Shawn changed: What|Removed |Added CC||shawn.peter...@gmx.com --- Comment #3 from Shawn --- I can confirm that this has nothing to do with dota 2. It appears to be any fullscreen application (although the only ones that I have that I can test are games. I have tested it with dota 2, dota underlords, as well as 0ad (not a steam game). I tried a different kernel, and I tried switching between different compositing layer thingies (open gl 2.1, 3, xrender). None of this makes any difference. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424223] Impossible to click on the taskbar to bring up Dota 2 after a recent update
https://bugs.kde.org/show_bug.cgi?id=424223 --- Comment #5 from Shawn --- (In reply to dave knippers from comment #4) > i must not have tested enough to say for sure it's only in dota, but it was > the only one i managed to get it to fail on. What application did the bug not show up for? Just curious what the difference is. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 431792] PDF Form checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=431792 Shawn changed: What|Removed |Added CC||shawn.peter...@posteo.net --- Comment #11 from Shawn --- Just for future reference, it seems that Andreas did file a bug report for poppler: https://gitlab.freedesktop.org/poppler/poppler/-/issues/1055 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kservice] [Bug 430157] KDE .desktop parser complains about files that have Type= "Application" but no Exec line, although this situation is normal.
https://bugs.kde.org/show_bug.cgi?id=430157 Shawn changed: What|Removed |Added CC||sh...@n4hab.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427253] konsole window doesn't open on correct (in focus) monitor, or tile correctly
https://bugs.kde.org/show_bug.cgi?id=427253 shawn changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #4 from shawn --- I'm closing this because reinstalling the entire OS for unrelated reasons happened to fixed the issue, so apparently it was just a quirk on my old system. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary one.
https://bugs.kde.org/show_bug.cgi?id=427875 Shawn changed: What|Removed |Added CC||shawn.peter...@gmx.com --- Comment #25 from Shawn --- I have a dual monitor setup with both resolutions at 2560x14440. I can't do any of the coding stuff that you guys do, but if there is something I can test to help, let me know. I say this because most of the comments I see are from ppl that have a laptop + some other screen, possibly with different resolutions. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary one.
https://bugs.kde.org/show_bug.cgi?id=427875 --- Comment #27 from Shawn --- (In reply to Claudius Ellsel from comment #26) > (In reply to Shawn from comment #25) > > I have a dual monitor setup with both resolutions at 2560x14440. I can't do > > any of the coding stuff that you guys do, but if there is something I can > > test to help, let me know. I say this because most of the comments I see > > are from ppl that have a laptop + some other screen, possibly with different > > resolutions. > > A screenshot of your screen setup (and arrangement) from the systemsettings > might be interesting. Okay. Probably doesn't matter, but I have two taskbars. One on each screen showing only the applications that are on that screen. Also, the add attachment feature I think would make the picture unreadable if I tried to scale it down that much, so I used an external link. Never done this before, so hopefully okay. =) [url=https://postimg.cc/hQrhShz8][img]https://i.postimg.cc/hQrhShz8/desktop-screenshot.png[/img][/url] -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary one.
https://bugs.kde.org/show_bug.cgi?id=427875 --- Comment #28 from Shawn --- err, let me try again I guess. Sorry: https://i.postimg.cc/t706Nx9c/desktop-screenshot.png -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424135] New: trashcan highlights red when empty
https://bugs.kde.org/show_bug.cgi?id=424135 Bug ID: 424135 Summary: trashcan highlights red when empty Product: dolphin Version: 20.04.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: panels: places Assignee: dolphin-bugs-n...@kde.org Reporter: shit...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY trashcan icon is highlighted red when the trash is empty STEPS TO REPRODUCE 1. Open Dolphin 2. Leave Dolphin open for awhile OBSERVED RESULT Trashcan icon is highlighted red with option to empty even though the trash is empty (including hidden files). EXPECTED RESULT Trashcan icon should be white (or whatever the color scheme makes it) with with the empty option grayed out. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Manjaro KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION Manjaro seems to be waiting awhile for plasma 5.19 to become stable so this bug may already be fixed in later versions of kde/plasma/dolphin. Possibly related to 341035 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429995] New: Unexpected Media Server listening on *:8200 - Should have been informed / given the option during 1st run setup.
https://bugs.kde.org/show_bug.cgi?id=429995 Bug ID: 429995 Summary: Unexpected Media Server listening on *:8200 - Should have been informed / given the option during 1st run setup. Product: digikam Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Plugin-Generic-MediaServer Assignee: digikam-bugs-n...@kde.org Reporter: s...@skhu.us Target Milestone: --- SUMMARY Dismayed to find digikam provided kipi-plugins by default, and along with it installed a new network service on my computer. STEPS TO REPRODUCE 1. apt-get install digikam 2. launch digikam 3. OBSERVED RESULT minidlna8u IPv4 31166 0t0 TCP *:8200 (LISTEN) EXPECTED RESULT Be forced to choose whether I want to host a Media Server during install or first run. SOFTWARE/OS VERSIONS Linux: Debian 10 / XFCE (available in About System) KDE Plasma Version: n/a KDE Frameworks Version: n/a Qt Version: 5.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429995] Unexpected Media Server listening on *:8200 - Should have been informed / given the option during 1st run setup.
https://bugs.kde.org/show_bug.cgi?id=429995 --- Comment #3 from Shawn --- using digikam v5.9 Yup, a bit old, but that's what's in Debian Stable repo. If wish already granted in newer versions, great, but didn't seem like something that would change w/o a request. I've already disabled / removed the unwanted service, so mitigated for now. Thank You, Shawn Hughes On 12/3/20 10:54 PM, bugzilla_nore...@kde.org wrote: > https://bugs.kde.org/show_bug.cgi?id=429995 > > caulier.gil...@gmail.com changed: > > What|Removed |Added > > CC||caulier.gil...@gmail.com > > --- Comment #1 from caulier.gil...@gmail.com --- > witch digiKam version did you use ? > > Gilles Caulier > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429995] Unexpected Media Server listening on *:8200 - Should have been informed / given the option during 1st run setup.
https://bugs.kde.org/show_bug.cgi?id=429995 --- Comment #4 from Shawn --- Maik, Thank you: Seems you're saying I explicitly enabled the Media Server. While I don't recall turning on anything like 'media server' (I just installed digikam on Nov 11), I'll take your word for it and pay closer attention next time. rdepends reports minidlna is used by kipi-plugins which appears to primarily provide for pushing images to social networks. Any chance this is an unintended feature of kipi-plugins? My apologies to all I've interrupted if this is a non-issue. Otherwise, I am completely thrilled with digikam. Many thanks to all who made it happen. -- Shawn Hughes On 12/4/20 5:19 AM, Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=429995 > > Maik Qualmann changed: > > What|Removed |Added > > CC||metzping...@gmail.com > > --- Comment #2 from Maik Qualmann --- > Debian 10 was supposed to ship digiKam-5.9.0, which is a very, very old > version. But even this version did not start the media server automatically by > default. Go to the media server and disable the start. > > Maik > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429995] Unexpected Media Server listening on *:8200 - Should have been informed / given the option during 1st run setup.
https://bugs.kde.org/show_bug.cgi?id=429995 Shawn changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #6 from Shawn --- per comment 5, clearly not an issue with current versions. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 396469] Provide option to import passwords from CSV
https://bugs.kde.org/show_bug.cgi?id=396469 Shawn changed: What|Removed |Added CC||shawn.peter...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 417089] Settings for identical monitors get inappropriately cloned on reboot and end up overlapping
https://bugs.kde.org/show_bug.cgi?id=417089 Shawn changed: What|Removed |Added CC||shawn.peter...@posteo.net --- Comment #10 from Shawn --- Nicolas, thanks. That worked for me. Nate, I wanted to mention that I did not experience this bug until I switched both of my connection cords to display ports. Prior to that, I had one of them as hdmi and one of them as display. I did not get the bug until then. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 290747] Column view is not available anymore in Dolphin 2.0
https://bugs.kde.org/show_bug.cgi?id=290747 Shawn changed: What|Removed |Added CC||shawn.peter...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420622] New: Maia Konsole theme disappeared
https://bugs.kde.org/show_bug.cgi?id=420622 Bug ID: 420622 Summary: Maia Konsole theme disappeared Product: konsole Version: 20.04.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: shit...@gmail.com Target Milestone: --- SUMMARY Maia Konsole theme disappeared STEPS TO REPRODUCE 1. update konsole from 19.12 to 20.04 OBSERVED RESULT Maia Konsole theme disappears EXPECTED RESULT Maia Konsole theme should remain SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.6.7-1-MANJARO (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Found the theme here: https://github.com/manjaro/manjaro-kde-settings/blob/master/usr/share/konsole/Maia.colorscheme In case anyone needs it: [Background] Color=44,44,44 [BackgroundIntense] Color=44,44,44 [Color0] Color=63,63,63 [Color0Intense] Color=112,144,128 [Color1] Color=112,80,80 [Color1Intense] Color=220,163,163 [Color2] Color=96,180,138 [Color2Intense] Color=114,213,163 [Color3] Color=223,175,143 [Color3Intense] Color=240,223,175 [Color4] Color=52,152,219 [Color4Intense] Color=126,178,230 [Color5] Color=91,44,112 [Color5Intense] Color=155,89,182 [Color6] Color=140,208,211 [Color6Intense] Color=147,224,227 [Color7] Color=220,220,204 [Color7Intense] Color=255,255,255 [Foreground] Color=26,188,156 [ForegroundIntense] Color=26,188,156 [General] Description=Maia Opacity=1 Wallpaper= -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420622] Maia Konsole theme disappeared
https://bugs.kde.org/show_bug.cgi?id=420622 --- Comment #2 from shawn --- (In reply to Kurt Hindenburg from comment #1) > This would seem to be a packaging issue w/ your distro Manjaro. Okay. If its not an issue on KDE's end then I'll just close this. Thanks -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420622] Maia Konsole theme disappeared
https://bugs.kde.org/show_bug.cgi?id=420622 shawn changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419961] New: Scrolling no longer works on desktop
https://bugs.kde.org/show_bug.cgi?id=419961 Bug ID: 419961 Summary: Scrolling no longer works on desktop Product: plasmashell Version: 5.18.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: shit...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Scrolling no longer works on desktop STEPS TO REPRODUCE 1. Update to plasma 5.18.4? (at least that when the problem started happening) 2. Click on desktop 3. Use scroll wheel EXPECTED RESULTS Should switch between virtual desktops or do whatever "right click > configure desktop > mouse actions > vertical scroll" is set to do. ACTUAL RESULTS Nothing happens. OTHER NOTES Change virtual desktop with any other mouse button works. Scrolling in other applications still works. Scrolling with mouse over virtual desktop icon on taskbar works. "qdbus org.kde.KWin /KWin nextDesktop" command works as expected. (Should I be posting this report under kwin?) ~/.config/plasma-org.kde.plasma.desktop-appletsrc has been reset to no effect. Bug 413104 seems similar but no solution has been provided in that thread. SOFTWARE/OS VERSIONS OS: Manjaro KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419961] Scrolling no longer works on desktop
https://bugs.kde.org/show_bug.cgi?id=419961 --- Comment #2 from shawn --- I created a temporary workaround with xbindkeys and xdotool. In ~/.xbindkeysrc I added the lines: "bash /home/username/scroll_down.sh" b:5 "bash /home/username/scroll_up.sh" b:4 The contents of the shell files are: #!/bin/bash eval $(xdotool getmouselocation --shell) echo $WINDOW name=$(xdotool getwindowname $WINDOW) base="Desktop — Plasma" if [ "$name" = "$base" ]; then echo succ qdbus org.kde.KWin /KWin nextDesktop fi With "nextDesktop" in the scroll_down/sh file and "previousDesktop" in the scroll_up.sh file. The "qdbus" command could also be replaces with "xdotool set_desktop" This assumes that you have two desktops stacked vertically. Also there is no wrap around scrolling. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419961] Scrolling no longer works on desktop
https://bugs.kde.org/show_bug.cgi?id=419961 --- Comment #3 from shawn --- forgot to remove unnecessary "echo $WINDOW" and "echo succ" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419867] Unable to use scrollwheel on desktop to change Virtual Desktop
https://bugs.kde.org/show_bug.cgi?id=419867 --- Comment #6 from shawn --- I created a temporary workaround with xbindkeys and xdotool. In ~/.xbindkeysrc I added the lines: "bash /home/username/scroll_down.sh" b:5 "bash /home/username/scroll_up.sh" b:4 The contents of the shell files are: #!/bin/bash eval $(xdotool getmouselocation --shell) name=$(xdotool getwindowname $WINDOW) base="Desktop — Plasma" if [ "$name" = "$base" ]; then qdbus org.kde.KWin /KWin nextDesktop fi With "nextDesktop" in the scroll_down/sh file and "previousDesktop" in the scroll_up.sh file. The "qdbus" command could also be replaced with "xdotool set_desktop" This assumes that you have two desktops stacked vertically. Also there is no wrap around scrolling. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 496994] New: color schemes don't work and stuck in light mode
https://bugs.kde.org/show_bug.cgi?id=496994 Bug ID: 496994 Summary: color schemes don't work and stuck in light mode Classification: Applications Product: dolphin Version: 24.08.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: shit...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin is stuck in light (aka flashbang) mode. changing themes fro me the commandline or the kde system settigns does nothing (changing icon themes and window decoration themes works). STEPS TO REPRODUCE 1. update dolphin to 24.08.3 with KDE Manjaro 2. open dolphin OBSERVED RESULT Dolphin is stuck in light mode. When run from command line get the error message: kf.config.core: Watching absolute paths is not supported "/usr/share/color-schemes/BreezeLight.colors" EXPECTED RESULT dolphin should respect theme set from cmd or settings menu SOFTWARE/OS VERSIONS kinfo output Operating System: Manjaro Linux rolling KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Kernel Version: 6.6.63-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2 ADDITIONAL INFORMATION I have qt6ct installed with $QT_QPA_PLATFORMTHEME but disabling it doesn't do anything. I've also tried $QT_STYLE_OVERRIDE but that does nothing dolphin --platformtheme also does nothing. I've used kfind to search as many files as possible (name and contents) looking for a config file that explicitly has the absolute path but can't find anything. the error message specifically comes from https://github.com/KDE/kconfig/blame/master/src/core/kconfigwatcher.cpp but I'm not much of a programmer so I don't know where to go from there. Rant: This could very well be a Manjaro specific issue. I'm so done with their jank but too lazy to just switch to plain Arch. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373204] New: Plasma displayed desktop icons when switching video displays and crashes
https://bugs.kde.org/show_bug.cgi?id=373204 Bug ID: 373204 Summary: Plasma displayed desktop icons when switching video displays and crashes Product: plasmashell Version: 5.8.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: shawn.st...@rogers.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.4) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.9.0-rc7+ x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: - What I was doing when the application crashed: Started KDE up - Unusual behavior I noticed: I wonder if kscreen gets confused when using the following options for kernel booting video=LVDS-1:d video=VGA-0:e If you boot without them, then with them back on, kscreen/plasma gets confused and displays incorrectly which can crash. My setup typically is to close laptop lid and power the laptop display off to redirect to VGA to bigger screen. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f30e8d643c0 (LWP 1256))] Thread 7 (Thread 0x7f304178b700 (LWP 1451)): #0 0x7f30efb77814 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7f30efb3168c in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #2 0x7f30efb3207b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f30efb3226c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f30f7bafd8b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f30f7b610ba in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f30f79be643 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f30fb5b9ca6 in QQuickPixmapReader::run() () at /lib64/libQt5Quick.so.5 #8 0x7f30f79c2a1a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f30f61006ca in start_thread () at /lib64/libpthread.so.0 #10 0x7f30f6db5f6f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f30cbfff700 (LWP 1450)): #0 0x7f30f6106460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f30fd452bd4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7f30fd452c19 in () at /lib64/libQt5Script.so.5 #3 0x7f30f61006ca in start_thread () at /lib64/libpthread.so.0 #4 0x7f30f6db5f6f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f30d5dd1700 (LWP 1446)): #0 0x7f30f6da5bdd in read () at /lib64/libc.so.6 #1 0x7f30efb76450 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f30efb31c60 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f30efb320f4 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f30efb3226c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f30f7bafd8b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f30f7b610ba in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f30f79be643 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f30fac32735 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #9 0x7f30f79c2a1a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7f30f61006ca in start_thread () at /lib64/libpthread.so.0 #11 0x7f30f6db5f6f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f30d77cb700 (LWP 1356)): #0 0x7f30efb77814 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7f30efb3168c in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #2 0x7f30efb3207b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f30efb3226c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f30f7bafd8b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f30f7b610ba in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f30f79be643 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f30fac32735 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #8 0x7f30f79c2a1a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f30f61006ca in start_thread () at /lib64/libpthread.so.0 #10 0x7f30f6db5f6f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f30dd273700 (LWP 1330)): #0 0x7f30f7bae86f in QTimerInfoList::timerWait(timespec&) () at /lib64/libQt5Core.so.5 #1 0x7f30f7bafa2c in timerSourcePrepareHelper(GTimerSource*, int*) () at /lib64/libQt5Core.so.5 #2 0x7f30f7bafaf5 in timerSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5 #3 0x000
[Akonadi] [Bug 373242] New: Crash in akonadi_indexing_agent unknown cause processing emails received
https://bugs.kde.org/show_bug.cgi?id=373242 Bug ID: 373242 Summary: Crash in akonadi_indexing_agent unknown cause processing emails received Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Indexer Assignee: kdepim-b...@kde.org Reporter: shawn.st...@rogers.com CC: chrig...@fastmail.fm, dvra...@kde.org Target Milestone: --- Created attachment 102607 --> https://bugs.kde.org/attachment.cgi?id=102607&action=edit Crash from program Crash dump from Bug reporter (unable to submit bug since it doesn't know what component) Application: akonadi_indexing_agent (akonadi_indexing_agent) I don't know what triggered this but I've attached the crash. This is Fedora 25 official RPMs RPM: kf5-akonadi-search-16.08.2-1.fc25.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 455563] New: clip monitor: playback with forward speed of 1.5x is at the same speed of 1x
https://bugs.kde.org/show_bug.cgi?id=455563 Bug ID: 455563 Summary: clip monitor: playback with forward speed of 1.5x is at the same speed of 1x Product: kdenlive Version: 21.08.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: bigfl...@gmail.com Target Milestone: --- Created attachment 149903 --> https://bugs.kde.org/attachment.cgi?id=149903&action=edit clip monitor at 1.5x playback 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 downloaded and installed the binary installer. MLT version 7.1.0 STEPS TO REPRODUCE 1. Create a new project, and add a video clip (here it is of MP4 format). drag the newly-added video clip to the tracks area. 2. click the clip monitor. Click the cursor in the timeline bar above the buttons. 3. click the forward button twice, and 1.5x is shown at the upper left corner in the monitor. However, the playback speed is actually 1x. I timed with a stopwatch app (on mobile phone), and compared with the timestamp shown to the right of the forward button. 4. click the cursor in the timeline bar above the tracks. click the forward button twice, and 1.5x is shown at the upper left corner in the monitor. Playback speed is actually 1x. OBSERVED RESULT 1x playback speed. EXPECTED RESULT 1.5x playback speed. When I click the forward button one more time, and 2x is shown and the playback speed is actually 2x. So the 1.5x playback speed cannot be achieved. SOFTWARE/OS VERSIONS Windows: 10 21H2 (19044.1766). macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Same issue happened in Kdenlive for MacOS, v22.04.01. I downloaded the binary installer. KDE frameworks v5.94.0 Qt v5.15.2. MLT 7.7.0. MacOS version: Monterey v12.4 -- You are receiving this mail because: You are watching all bug changes.
[kimagemapeditor] [Bug 459752] New: erroneous html generated by default; plus a request for a setting
https://bugs.kde.org/show_bug.cgi?id=459752 Bug ID: 459752 Summary: erroneous html generated by default; plus a request for a setting Classification: Applications Product: kimagemapeditor Version: 22.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: j_sch...@informatik.uni-kl.de Reporter: s...@ecloud.org Target Milestone: --- SUMMARY 1. the tag is missing its usemap property 2. the tag is not closed 3. the tag uses an absolute path STEPS TO REPRODUCE 1. load an image 2. define some areas 3. save the html OBSERVED RESULT EXPECTED RESULT Probably it's best to have a setting for whether to use absolute or relative links. I see that you have Image | Edit Usemap to set the usemap property, but the problem is it's blank by default, so it's easy to forget to do that. I think it should use the map name by default. That is "unnamed", which is noticeable already in the Maps list at startup, so I can see that I should probably rename it. But I can't see the usemap name in the UI, it's just when I save the html that I find out that usemap is missing and it doesn't work in the browser. SOFTWARE/OS VERSIONS Linux: latest Arch Linux; running plain X11 desktop, not KDE Qt Version: 5.15.6+kde+r177-1 ADDITIONAL INFORMATION Anyway thanks for writing this! I was glad to see that there is such a utility at all. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442101] Crash when dragging a clip onto the timeline
https://bugs.kde.org/show_bug.cgi?id=442101 Shawn Rutledge changed: What|Removed |Added CC||s...@ecloud.org --- Comment #15 from Shawn Rutledge --- I haven't been able to use kdenlive since some time early last year (?) because of this. #0 0x74e0b34c in __pthread_kill_implementation () at /usr/lib/libc.so.6 #1 0x74dbe4b8 in raise () at /usr/lib/libc.so.6 #2 0x74da8534 in abort () at /usr/lib/libc.so.6 #3 0x74dff397 in __libc_message () at /usr/lib/libc.so.6 #4 0x74e1533c in () at /usr/lib/libc.so.6 #5 0x74e185ec in _int_malloc () at /usr/lib/libc.so.6 #6 0x74e19629 in malloc () at /usr/lib/libc.so.6 #7 0x75f0ad88 in QImageData::create(QSize const&, QImage::Format) () at /usr/lib/libQt5Gui.so.5 #8 0x75f0aeb1 in QImage::QImage(QSize const&, QImage::Format) () at /usr/lib/libQt5Gui.so.5 #9 0x75f0aef8 in QImage::QImage(int, int, QImage::Format) () at /usr/lib/libQt5Gui.so.5 #10 0x75f12bb7 in QImage::copy(QRect const&) const () at /usr/lib/libQt5Gui.so.5 #11 0x75f0b9b7 in QImage::detach() () at /usr/lib/libQt5Gui.so.5 #12 0x75f11ccd in QImage::setColor(int, unsigned int) () at /usr/lib/libQt5Gui.so.5 #13 0x702046b3 in () at /usr/lib/libQt5XcbQpa.so.5 #14 0x7618c200 in QTextureGlyphCache::textureMapForGlyph(unsigned int, QFixed) const () at /usr/lib/libQt5Gui.so.5 #15 0x7620d512 in QOpenGLTextureGlyphCache::fillTexture(QTextureGlyphCache::Coord const&, unsigned int, QFixed) () at /usr/lib/libQt5Gui.so.5 #16 0x76185164 in QTextureGlyphCache::fillInPendingGlyphs() () at /usr/lib/libQt5Gui.so.5 #17 0x77017992 in () at /usr/lib/libQt5Quick.so.5 #18 0x770a627b in QQuickTextNode::addGlyphs(QPointF const&, QGlyphRun const&, QColor const&, QQuickText::TextStyle, QColor const&, QSGNode*) () at /usr/lib/libQt5Quick.so.5 #19 0x770b5aa9 in () at /usr/lib/libQt5Quick.so.5 #20 0x770a3275 in QQuickTextNode::addTextLayout(QPointF const&, QTextLayout*, QColor const&, QQuickText::TextStyle, QColor const&, QColor const&, QColor const&, QColor const&, int, int, int, int) () at /usr/lib/libQt5Quick.so.5 #21 0x770acc01 in QQuickText::updatePaintNode(QSGNode*, QQuickItem::UpdatePaintNodeData*) () at /usr/lib/libQt5Quick.so.5 #22 0x77096768 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*) () at /usr/lib/libQt5Quick.so.5 #23 0x77096f35 in QQuickWindowPrivate::updateDirtyNodes() () at /usr/lib/libQt5Quick.so.5 #24 0x77084145 in QQuickWindowPrivate::syncSceneGraph() () at /usr/lib/libQt5Quick.so.5 #25 0x7711385e in QQuickRenderControl::sync() () at /usr/lib/libQt5Quick.so.5 #26 0x77380f55 in () at /usr/lib/libQt5QuickWidgets.so.5 #27 0x773826d4 in QQuickWidget::timerEvent(QTimerEvent*) () at /usr/lib/libQt5QuickWidgets.so.5 #28 0x75546766 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #29 0x765661c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #30 0x755225aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #31 0x7556ddd5 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #32 0x7556e402 in () at /usr/lib/libQt5Core.so.5 #33 0x7359b163 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #34 0x735f19e9 in () at /usr/lib/libglib-2.0.so.0 #35 0x735986c5 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #36 0x7556e57a in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #37 0x7551a88b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #38 0x75ef907a in QBasicDrag::drag(QDrag*) () at /usr/lib/libQt5Gui.so.5 #39 0x75efb479 in QDragManager::drag(QDrag*) () at /usr/lib/libQt5Gui.so.5 #40 0x75efb972 in QDrag::exec(QFlags, Qt::DropAction) () at /usr/lib/libQt5Gui.so.5 #41 0x5570f13d in () #42 0x7659c826 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #43 0x7664d4c3 in QFrame::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #44 0x7552132a in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #45 0x765661b5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #46 0x7656aff7 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442101] Crash when dragging a clip onto the timeline
https://bugs.kde.org/show_bug.cgi?id=442101 --- Comment #16 from Shawn Rutledge --- ... that's across quite a few versions, but the current one is extra/kdenlive 21.12.3-1 on Arch; melt --version says 7.6.0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442101] Crash when dragging a clip onto the timeline
https://bugs.kde.org/show_bug.cgi?id=442101 --- Comment #17 from Shawn Rutledge --- Created attachment 147855 --> https://bugs.kde.org/attachment.cgi?id=147855&action=edit screenshot showing weird circled-number glyphs Since gdb shows that it has something to do with populating glyphs into the cache while rendering text, I wonder if this is related: parts of the UI are choosing a strange font or unicode range (?) to show time values. Maybe at some point it chooses a glyph that doesn't exist, that generates a zero-size image or so? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442101] Crash when dragging a clip onto the timeline
https://bugs.kde.org/show_bug.cgi?id=442101 --- Comment #18 from Shawn Rutledge --- It doesn't matter whether I "Use GPU processing", in fact I didn't have movit installed until now, so that was not possible before. But FWIW I have a Radeon RX480, amdgpu driver, Linux 5.14.6 and I doubt that it could be a driver or Mesa bug since I have been testing Qt Quick and Qt Quick 3D regularly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444443] New: [FE] Ability to add menu options to Plasma Desktop context menu
https://bugs.kde.org/show_bug.cgi?id=43 Bug ID: 43 Summary: [FE] Ability to add menu options to Plasma Desktop context menu Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: shawn.st...@rogers.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY It would be good to allow programs to add context menu hooks to the Plasma Desktop menu, similar to Microsoft Windows shell supporting menu context additions. STEPS TO REPRODUCE 1. Left Plasma Desktop to open Context menu -> Configure Desktop & Wallpaper , no option for extending the context menu. OBSERVED RESULT No option to edit Plasma Desktop context menu EXPECTED RESULT Ability to add shortcuts to context menu, name the context menu and the action when clicking it should do. If The Plasma Desktop Folder View could support some sort of extensions directory it could load. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 36 KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.15.0-0.rc3.25.fc36.x86_64 (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.8 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444443] [FE] Ability to add menu options to Plasma Desktop context menu
https://bugs.kde.org/show_bug.cgi?id=43 --- Comment #1 from Shawn Starr --- Something like Folder View could do is read some $HOME/.config/plasmamenus/*.kdelnk or something -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444443] [FE] Ability to add menu options to Plasma Desktop context menu
https://bugs.kde.org/show_bug.cgi?id=43 --- Comment #3 from Shawn Starr --- Plasma Desktop Folder View v3.0 plugin, or does this respect Dolphin's view of that context menu(?) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444443] [FE] Ability to add menu options to Plasma Desktop context menu
https://bugs.kde.org/show_bug.cgi?id=43 --- Comment #5 from Shawn Starr --- Not within Dolphin which has its own context menus, but the root desktop itself that Plasma shell owns via Desktop Folder View plugin I guess -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 441610] Hiding/minimizing, then showing a konsole window, makes it revert to its default size
https://bugs.kde.org/show_bug.cgi?id=441610 --- Comment #14 from Shawn Rutledge --- Thanks for the fix. I downgraded to 21.04 for now; I hope this really shows up soonish in an Arch packagae. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 432707] New: [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 Bug ID: 432707 Summary: [Wayland] KScreen does not detect external displays such as DisplayPort on laptops Product: KScreen Version: git Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libkscreen Assignee: kscreen-bugs-n...@kde.org Reporter: shawn.st...@rogers.com Target Milestone: --- SUMMARY I have two laptops, one is a Dell Precision M6800, with an integrated GPU and dedicated GPU: Laptop #1 = Model: Dell Precision M6800 Integrated GPU: Intel HD Graphics 4600 (HSW GT2) Dedicated GPU: AMD FirePro M6100 (AMD Radeon HD 8950) Xrandr info - Xorg -- Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 16384 x 16384 DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440144.00*+ 120.0059.95 1920x1080239.76 143.98 120.00 119.8860.0050.0059.94 1680x1050 59.95 1600x900 60.00 1280x1024 75.0260.02 1440x900 59.89 1280x800 59.81 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00 720x480 60.0059.94 640x480 75.0072.8166.6760.0059.94 720x400 70.08 DisplayPort-2 disconnected (normal left inverted right x axis y axis) DisplayPort-3 disconnected (normal left inverted right x axis y axis) eDP-1-1 connected (normal left inverted right x axis y axis) 1920x1080 60.01 + 60.0159.9759.9659.93 1680x1050 59.9559.88 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1280x800 59.9959.9759.8159.91 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 700x525 59.98 800x450 59.9559.82 640x512 60.02 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 640x400 59.8859.98 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 VGA-1-1 disconnected (normal left inverted right x axis y axis) DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) 1680x1050 (0x4c) 146.250MHz -HSync +VSync h: width 1680 start 1784 end 1960 total 2240 skew0 clock 65.29KHz v: height 1050 start 1053 end 1059 total 1089 clock 59.95Hz 1280x1024 (0x53) 108.000MHz +HSync +VSync h: width 1280 start 1328 end 1440 total 1688 skew0 clock 63.98KHz v: height 1024 start 1025 end 1028 total 1066 clock 60.02Hz 1280x800 (0x5d) 83.500MHz -HSync +VSync h: width 1280 start 1352 end 1480 total 1680 skew0 clock 49.70KHz v: height 800 start 803 end 809 total 831 clock 59.81Hz 1024x768 (0x64) 65.000MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.36KHz v: height 768 start 771 end 777 total 806 clock 60.00Hz 800x600 (0x73) 40.000MHz +HSync +VSync h: width 800 start 840 end 968 total 1056 skew0 clock 37.88KHz v: height 600 start 601 end 605 total 628 clock 60.32Hz 800x600 (0x74) 36.000MHz +HSync +VSync h: width 800 start 824 end 896 total 1024 skew0 clock 35.16KHz v: height 600 start 601 end 603 total 625 clock 56.25Hz 640x480 (0x80) 25.175MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew0 clock 31.47KHz v: height 480 start 490 end 492 total 525 clock 59.94Hz Laptop #2: == Model: ThinkPad W500 (4058CTO) Integrated GPU: disabled in BIOS Dedicated GPU: Mobility Radeon HD 3650 (RV635) xrandr info - Xorg -- Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192 DVI-0 disconnecte
[KScreen] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #2 from Shawn Starr --- Yes, X11 its fine. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #4 from Shawn Starr --- Seeing im on 5.20.90, 5.21 will not fix issue since it is 5.21 beta :) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #6 from Shawn Starr --- I will later this week provide the log. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #7 from Shawn Starr --- Ill provide log tonight -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433297] Locale-aware alphabetic index/category in kickoff for non-English applications
https://bugs.kde.org/show_bug.cgi?id=433297 Shawn Rutledge changed: What|Removed |Added CC||s...@ecloud.org --- Comment #5 from Shawn Rutledge --- I'm a bit surprised that Chinese people consider the first character of modern pinyin a better index character than the ancient symbols that are actually seen on the screen. If a file clerk is organizing folders in a paper file cabinet, is there an implicit order that they always use? Why should digital apps be different? What's the convention in non-Qt contexts, e.g. in native contacts apps on phones? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 441610] New: when switching virtual desktops on OpenBox, konsole windows revert to their default sizes
https://bugs.kde.org/show_bug.cgi?id=441610 Bug ID: 441610 Summary: when switching virtual desktops on OpenBox, konsole windows revert to their default sizes Product: konsole Version: 21.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: s...@ecloud.org Target Milestone: --- SUMMARY when switching virtual desktops on OpenBox, konsole windows revert to their default sizes STEPS TO REPRODUCE 1. open a konsole window 2. resize it 3. switch to a different virtual desktop 4. switch back OBSERVED RESULT konsole window will now be the same size as configured in General | Initial terminal size EXPECTED RESULT stay the same as it was resized to SOFTWARE/OS VERSIONS Arch Linux, running openbox, not plasma desktop KDE Plasma Version: plasma-integration 5.22.4-1 plasma-workspace 5.22.4-3 KDE Frameworks Version: plasma-framework 5.85.0-2 Qt Version: 6.1.2 ADDITIONAL INFORMATION seems to be a new bug, just started happening after pacman -Syu [zen][16:26:20] pacman -Ss plasma |grep installed extra/breeze 5.22.4-1 (plasma) [installed] extra/kactivitymanagerd 5.22.4-1 (plasma) [installed] extra/kde-cli-tools 5.22.4-1 (plasma) [installed] extra/kdecoration 5.22.4-1 (plasma) [installed] extra/kscreenlocker 5.22.4-1 (plasma) [installed] extra/ksystemstats 5.22.4-1 (plasma) [installed] extra/kwayland-server 5.22.4-1 (plasma) [installed] extra/kwin 5.22.4-1 (plasma) [installed] extra/layer-shell-qt 5.22.4-1 (plasma) [installed] extra/libkscreen 5.22.4-1 (plasma) [installed] extra/libksysguard 5.22.4-1 (plasma) [installed] extra/milou 5.22.4-1 (plasma) [installed] extra/plasma-framework 5.85.0-2 (kf5) [installed] extra/plasma-integration 5.22.4-1 (plasma) [installed] extra/plasma-workspace 5.22.4-3 (plasma) [installed] [zen][16:27:58] pacman -Ss kf5 |grep installed extra/attica 5.85.0-1 (kf5) [installed] extra/baloo 5.85.0-1 (kf5) [installed] extra/breeze-icons 5.85.0-1 (kf5) [installed] extra/extra-cmake-modules 5.85.0-1 (kf5) [installed] extra/frameworkintegration 5.85.0-1 (kf5) [installed] extra/kactivities 5.85.0-1 (kf5) [installed] extra/kactivities-stats 5.85.0-1 (kf5) [installed] extra/karchive 5.85.0-1 (kf5) [installed] extra/kauth 5.85.0-1 (kf5) [installed] extra/kbookmarks 5.85.0-1 (kf5) [installed] extra/kcmutils 5.85.0-1 (kf5) [installed] extra/kcodecs 5.85.0-1 (kf5) [installed] extra/kcompletion 5.85.0-1 (kf5) [installed] extra/kconfig 5.85.0-1 (kf5) [installed] extra/kconfigwidgets 5.85.0-1 (kf5) [installed] extra/kcoreaddons 5.85.0-1 (kf5) [installed] extra/kcrash 5.85.0-1 (kf5) [installed] extra/kdbusaddons 5.85.0-1 (kf5) [installed] extra/kdeclarative 5.85.0-1 (kf5) [installed] extra/kded 5.85.0-1 (kf5) [installed] extra/kdelibs4support 5.85.0-1 (kf5-aids) [installed] extra/kdesu 5.85.0-1 (kf5) [installed] extra/kdnssd 5.85.0-1 (kf5) [installed] extra/kemoticons 5.85.0-1 (kf5) [installed] extra/kfilemetadata 5.85.0-1 (kf5) [installed] extra/kglobalaccel 5.85.0-1 (kf5) [installed] extra/kguiaddons 5.85.0-1 (kf5) [installed] extra/kholidays 1:5.85.0-1 (kf5) [installed] extra/ki18n 5.85.0-1 (kf5) [installed] extra/kiconthemes 5.85.0-1 (kf5) [installed] extra/kidletime 5.85.0-1 (kf5) [installed] extra/kinit 5.85.0-1 (kf5) [installed] extra/kio 5.85.0-1 (kf5) [installed] extra/kirigami2 5.85.0-1 (kf5) [installed] extra/kitemmodels 5.85.0-1 (kf5) [installed] extra/kitemviews 5.85.0-1 (kf5) [installed] extra/kjobwidgets 5.85.0-1 (kf5) [installed] extra/knewstuff 5.85.0-1 (kf5) [installed] extra/knotifications 5.85.0-1 (kf5) [installed] extra/knotifyconfig 5.85.0-1 (kf5) [installed] extra/kpackage 5.85.0-1 (kf5) [installed] extra/kparts 5.85.0-1 (kf5) [installed] extra/kpeople 5.85.0-1 (kf5) [installed] extra/kpty 5.85.0-1 (kf5) [installed] extra/kquickcharts 5.85.0-1 (kf5) [installed] extra/krunner 5.85.0-1 (kf5) [installed] extra/kservice 5.85.0-1 (kf5) [installed] extra/ktexteditor 5.85.0-1 (kf5) [installed] extra/ktextwidgets 5.85.0-1 (kf5) [installed] extra/kunitconversion 5.85.0-1 (kf5) [installed] extra/kwallet 5.85.0-1 (kf5) [installed] extra/kwayland 5.85.0-1 (kf5) [installed] extra/kwidgetsaddons 5.85.0-1 (kf5) [installed] extra/kwindowsystem 5.85.0-1 (kf5) [installed] extra/kxmlgui 5.85.0-1 (kf5) [installed] extra/oxygen-icons 1:5.85.0-1 (kf5) [installed] extra/plasma-framework 5.85.0-2 (kf5) [installed] extra/prison 5.85.0-1 (kf5) [installed] extra/purpose 5.85.0-1 (kf5) [installed] extra/qqc2-desktop-style 5.85.0-1 (kf5) [installed] extra/solid 5.85.0-1 (kf5) [installed] extra/sonnet 5.85.0-1 (kf5) [installed] extra/syndication 5.85.0-1 (kf5) [installed] extra/syntax-highlighting 5.85.0-1 (kf5) [installed] extra/threadweaver 5.85.0-1 (kf5) [installed] -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 196998] Konsole should reflow the text when resizing
https://bugs.kde.org/show_bug.cgi?id=196998 --- Comment #47 from Shawn Rutledge --- The new re-wrapping feature is awesome! I was delighted when it showed up on Arch a few weeks ago. Thanks Carlos for getting this done. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 Shawn Starr changed: What|Removed |Added Attachment #137782|0 |1 is obsolete|| --- Comment #77 from Shawn Starr --- Created attachment 137797 --> https://bugs.kde.org/attachment.cgi?id=137797&action=edit dumb-import + primary-gpu-context log dumb-import + primary-gpu-context log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 Shawn Starr changed: What|Removed |Added Attachment #137797|0 |1 is obsolete|| --- Comment #78 from Shawn Starr --- Created attachment 137810 --> https://bugs.kde.org/attachment.cgi?id=137810&action=edit dumb-import branch only dumb-import branch only -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #79 from Shawn Starr --- Created attachment 137838 --> https://bugs.kde.org/attachment.cgi?id=137838&action=edit dumb-import branch only - latest test dumb-import branch only - latest test -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 Shawn Starr changed: What|Removed |Added Attachment #137810|0 |1 is obsolete|| Attachment #137838|0 |1 is obsolete|| --- Comment #80 from Shawn Starr --- Created attachment 137848 --> https://bugs.kde.org/attachment.cgi?id=137848&action=edit dumb-import - April 23rd - log dumb-import - April 23rd - log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #81 from Shawn Starr --- Created attachment 137851 --> https://bugs.kde.org/attachment.cgi?id=137851&action=edit dumb-import - April 23rd - log - Latest dumb-import - April 23rd - log - Latest -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #82 from Shawn Starr --- With latest changes to dumb-import both displays turn on now! Attached outputs -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 Shawn Starr changed: What|Removed |Added Attachment #137848|0 |1 is obsolete|| Attachment #137851|0 |1 is obsolete|| --- Comment #83 from Shawn Starr --- Created attachment 138131 --> https://bugs.kde.org/attachment.cgi?id=138131&action=edit Kwin + latest KWayland server + protocols - both displays turn on Kwin + latest KWayland server + protocols - both displays turn on -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #57 from Shawn Starr --- Will compile and report back today -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #58 from Shawn Starr --- Well, something appeared but it was garbage output on the DisplayPort. I had to alt-tab to switch VT then back and then I noticed my laptop display lit up. Attached is log. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #59 from Shawn Starr --- Created attachment 137423 --> https://bugs.kde.org/attachment.cgi?id=137423&action=edit Wayland Errors Log - with work/zamundaaa/dumb-import branch for kwin Wayland Errors Log - with work/zamundaaa/dumb-import branch for kwin -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #60 from Shawn Starr --- Results: In the first log, I created a new user - Started Plasma Wayland session, Laptop screen and DisplayPort didnt turn on, VT switched, the DisplayPort turned on saw an X cursor but nothing else, laptop screen did not turn on. In the second log, before I switched to Wayland from X11, I forced Kscreen to make the laptop screen primary and DisplayPort secondary. - Started Plasma Wayland session, Laptop screen and DisplayPort didn't turn on, VT switched. Laptop screen turned on, DisplayPort screen failed... Still no go with latest test branch. Attached are both logs. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #61 from Shawn Starr --- Created attachment 137442 --> https://bugs.kde.org/attachment.cgi?id=137442&action=edit Wayland Errors Log - New user - with work/zamundaaa/dumb-import branch for kwin Wayland Errors Log - New user - with work/zamundaaa/dumb-import branch for kwin -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #62 from Shawn Starr --- Created attachment 137443 --> https://bugs.kde.org/attachment.cgi?id=137443&action=edit Wayland Errors Log - Existing user - Laptop screen made primary - with work/zamundaaa/dumb-import branch for kwin Wayland Errors Log - Existing user - Laptop screen made primary - with work/zamundaaa/dumb-import branch for kwin -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #64 from Shawn Starr --- I hate to bring this up but: https://gitlab.com/kwinft/kwinft/-/issues/137 Why exactly are we not using wlroots? It's not exactly 'fun' to have to implement your own drm plugin for kwin, deal with all the complexities of display management like Xorg DDX did for us behind the scenes.. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #66 from Shawn Starr --- That's not confirmed... and wlroots devs dispute this im told on IRC so... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #68 from Shawn Starr --- You should sort that out with them. Upon installing Sway for Fedora, starting Sway from SDDM, both displays turned on immediately. So... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #70 from Shawn Starr --- Coming back to the KDE side of things.. right now nothing works for me. I can wait and will have to wait. I would prefer we have a common EDID/display detection framework not one for every DE though... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #71 from Shawn Starr --- Created attachment 137697 --> https://bugs.kde.org/attachment.cgi?id=137697&action=edit New log from latest code changes New log from latest code changes -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #72 from Shawn Starr --- Created attachment 137698 --> https://bugs.kde.org/attachment.cgi?id=137698&action=edit Coredump from Kwin Coredump from the session tested,segfaulted -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #73 from Shawn Starr --- Interesting results with kwin branches: work/zamundaaa/dumb-import + work/primary-gpu-context merged together with latest kwayland-server master + protocols. I *DO* get the DisplayPort turning on, although only *one* screen is able to turn on now.. Log attached -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 Shawn Starr changed: What|Removed |Added Attachment #136854|0 |1 is obsolete|| Attachment #137046|0 |1 is obsolete|| Attachment #137423|0 |1 is obsolete|| Attachment #137442|0 |1 is obsolete|| Attachment #137443|0 |1 is obsolete|| --- Comment #74 from Shawn Starr --- Created attachment 137761 --> https://bugs.kde.org/attachment.cgi?id=137761&action=edit Wayland Error logs - with dumb-import + primary-gpu-context branches Wayland Error logs - with dumb-import + primary-gpu-context branches -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #75 from Shawn Starr --- Created attachment 137781 --> https://bugs.kde.org/attachment.cgi?id=137781&action=edit New log from latest testing - dumb-import + primary-gpu-context + fix-hotplug New log from latest testing - dumb-import + primary-gpu-context + fix-hotplug -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 Shawn Starr changed: What|Removed |Added Attachment #137697|0 |1 is obsolete|| Attachment #137698|0 |1 is obsolete|| Attachment #137761|0 |1 is obsolete|| Attachment #137781|0 |1 is obsolete|| --- Comment #76 from Shawn Starr --- Created attachment 137782 --> https://bugs.kde.org/attachment.cgi?id=137782&action=edit dumb-import + primary-gpu-context + fix-hotplug w/o SDDM/Xorg VT dumb-import + primary-gpu-context + fix-hotplug w/o SDDM/Xorg VT -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 462061] On X11, portal-based "Choose Application" window is not brought to the front automatically when Focus stealing prevention is enabled due to a questionable QtXcb b
https://bugs.kde.org/show_bug.cgi?id=462061
Shawn Rutledge changed:
What|Removed |Added
CC||s...@ecloud.org
--- Comment #11 from Shawn Rutledge ---
So Fushan Wen is proposing to fix it by no longer checking whether a window is
transient before setting WM_TRANSIENT_FOR; but why is this "Choose Application"
window not transient according to the definition in qxcbwindow.cpp?
// Returns \c true if we should set WM_TRANSIENT_FOR on \a w
static inline bool isTransient(const QWindow *w)
{
return w->type() == Qt::Dialog
|| w->type() == Qt::Sheet
|| w->type() == Qt::Tool
|| w->type() == Qt::SplashScreen
|| w->type() == Qt::ToolTip
|| w->type() == Qt::Drawer
|| w->type() == Qt::Popup;
}
--
You are receiving this mail because:
You are watching all bug changes.
[KScreen] [Bug 423456] New: Unable to use external screen with KScreen in Wayland
https://bugs.kde.org/show_bug.cgi?id=423456 Bug ID: 423456 Summary: Unable to use external screen with KScreen in Wayland Product: KScreen Version: git Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: libkscreen Assignee: kscreen-bugs-n...@kde.org Reporter: shawn.st...@rogers.com Target Milestone: --- SUMMARY When I use a DisplayPort connector on a laptop KScreen does not detect the external display (It is a DisplayPort to VGA adaptor but still 'displayport' to whoever sees the device). STEPS TO REPRODUCE 1. Start KDE Wayland 5.18.x likely 5.19+ also kwin/plasma 2. Go to systemsettings, Check the display only see Laptop display listed OBSERVED RESULT Only Laptop display is available EXPECTED RESULT All external detected displays shown SOFTWARE/OS VERSIONS Linux/KDE Plasma: System Settings Version 5.18.5 - Fedora KDE (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION RANDR info Screen 0: minimum 320 x 200, current 3839 x 1200, maximum 16384 x 16384 eDP-1 connected 1920x1080+1919+0 (normal left inverted right x axis y axis) 382mm x 215mm 1920x1080 60.01 + 60.0159.9759.9659.93* 1680x1050 59.9559.88 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1280x800 59.9959.9759.8159.91 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 700x525 59.98 800x450 59.9559.82 640x512 60.02 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 640x400 59.8859.98 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 VGA-1 disconnected (normal left inverted right x axis y axis) DP-4 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DisplayPort-1-0 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 59.95*+ 1920x1080 59.95 1600x1200 60.00 1680x1050 59.95 1280x1024 75.0260.02 1440x900 59.95 1280x960 60.00 1280x800 59.95 1152x864 75.00 1280x720 59.95 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 640x480 75.0072.8166.6759.94 720x400 70.08 DisplayPort-1-1 disconnected (normal left inverted right x axis y axis) DisplayPort-1-2 disconnected (normal left inverted right x axis y axis) 1280x1024 (0x4e) 108.000MHz +HSync +VSync h: width 1280 start 1328 end 1440 total 1688 skew0 clock 63.98KHz v: height 1024 start 1025 end 1028 total 1066 clock 60.02Hz 1280x960 (0x50) 108.000MHz +HSync +VSync h: width 1280 start 1376 end 1488 total 1800 skew0 clock 60.00KHz v: height 960 start 961 end 964 total 1000 clock 60.00Hz 1024x768 (0x56) 65.000MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.36KHz v: height 768 start 771 end 777 total 806 clock 60.00Hz 800x600 (0x5a) 40.000MHz +HSync +VSync h: width 800 start 840 end 968 total 1056 skew0 clock 37.88KHz v: height 600 start 601 end 605 total 628 clock 60.32Hz 800x600 (0x5b) 36.000MHz +HSync +VSync h: width 800 start 824 end 896 total 1024 skew0 clock 35.16KHz v: height 600 start 601 end 603 total 625 clock 56.25Hz 640x480 (0x5f) 25.175MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew0 clock 31.47KHz v: height 480 start 490 end 492 total 525 clock 59.94Hz -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 423456] Unable to use external screen with KScreen in Wayland
https://bugs.kde.org/show_bug.cgi?id=423456 Shawn Starr changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #2 from Shawn Starr --- No, upgraded to 5.19.2 and still see issue: Display Configuration in systemsettings shows Laptop Screen, but no options for any other displays to select. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 423456] Unable to use external screen with KScreen in Wayland
https://bugs.kde.org/show_bug.cgi?id=423456 --- Comment #3 from Shawn Starr --- Created attachment 129654 --> https://bugs.kde.org/attachment.cgi?id=129654&action=edit dbus session starting Kwin Plasma Wayland dbus session starting Kwin Plasma Wayland -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 423456] Unable to use external screen with KScreen in Wayland
https://bugs.kde.org/show_bug.cgi?id=423456 --- Comment #4 from Shawn Starr --- It should be noted this laptop has two GPUs: 1) Intel(R) HD Graphics 4600 (HSW GT2) 2) AMD Radeon HD 8950 (BONAIRE, DRM 3.37.0, 5.7.0-1.fc33.x86_64, LLVM 10.0.0) But I do not see the other GPU being detected at all. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #21 from Shawn Starr --- Well I got built, it is failing attached is wayland-errors log. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432707] [Wayland] KScreen does not detect external displays such as DisplayPort on laptops
https://bugs.kde.org/show_bug.cgi?id=432707 --- Comment #22 from Shawn Starr --- Created attachment 136708 --> https://bugs.kde.org/attachment.cgi?id=136708&action=edit Wayland Error log #2 Wayland Error log #2 -- You are receiving this mail because: You are watching all bug changes.
