[kdeconnect] [Bug 482540] New: Applications list is empty for blacklist notification
https://bugs.kde.org/show_bug.cgi?id=482540 Bug ID: 482540 Summary: Applications list is empty for blacklist notification Classification: Applications Product: kdeconnect Version: 24.02.0 Platform: Neon OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: fakham...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Created attachment 166478 --> https://bugs.kde.org/attachment.cgi?id=166478&action=edit applications list SUMMARY *** In KDE Connect settings, in section send notifications, applications list is empty for blacklist notification. And its send all notification. *** SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.5.0-21-generic (64-bit) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 482540] Applications list is empty for blacklist notification
https://bugs.kde.org/show_bug.cgi?id=482540 --- Comment #1 from Ali --- This problem happened after updating to version 6 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 419897] Error when accessing filesystem. sshfs finished with exit code 1
https://bugs.kde.org/show_bug.cgi?id=419897 Ali changed: What|Removed |Added CC||fakham...@gmail.com --- Comment #25 from Ali --- This error still persists on KDE Neon 6 SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.5.0-21-generic (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 482540] Applications list is empty for blacklist notification
https://bugs.kde.org/show_bug.cgi?id=482540 Ali changed: What|Removed |Added OS|Android 13.x|Linux -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482542] New: Not same wallpaper in random order for two screen
https://bugs.kde.org/show_bug.cgi?id=482542 Bug ID: 482542 Summary: Not same wallpaper in random order for two screen Classification: Applications Product: systemsettings Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_wallpaper Assignee: plasma-b...@kde.org Reporter: fakham...@gmail.com CC: me...@kde.org Target Milestone: --- SUMMARY *** When I choose wallpaper type slideshow and set order to random and set for all screens, it's set two different images for two screen. *** EXPECTED RESULT Set same image for two screen and change it with together in slideshow. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.5.0-21-generic (64-bit) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482542] Not same wallpaper in random order for two screen
https://bugs.kde.org/show_bug.cgi?id=482542 Ali changed: What|Removed |Added Version|unspecified |6.0.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482543] New: Reset the circle of wallpaper slideshow for lock screen
https://bugs.kde.org/show_bug.cgi?id=482543 Bug ID: 482543 Summary: Reset the circle of wallpaper slideshow for lock screen Classification: Applications Product: systemsettings Version: 6.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_screenlocker Assignee: plasma-b...@kde.org Reporter: fakham...@gmail.com Target Milestone: --- SUMMARY *** I choose wallpaper slideshow for lock screen. When I lock, its start slideshow from beginning, after hours and changing images I unlock. And if I lock again the circle its reset and start slideshow from beginning. *** EXPECTED RESULT Wallpaper slideshow continue from I unlock, even after reboot. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.5.0-21-generic (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155
Ali changed:
What|Removed |Added
CC||fakham...@gmail.com
--- Comment #51 from Ali ---
I have same problem in KDE neon 5.27, Is there a solution?
```
Nov 21 18:08:18 User kdeconnectd[2382]: QDBusAbstractAdaptor: Cannot relay
signal SftpPlugin::packetReceived(NetworkPacket): Unregistered input type in
parameter list: NetworkPacket
Nov 21 18:08:18 User kdeconnectd[55031]: /usr/bin/fusermount: entry for
/run/user/1000/254223ae_f376_48bc_bacd_c5535f54a9d8 not found in /etc/mtab
Nov 21 18:08:18 User dolphin[54983]: MEGASYNCOVERLAYPLUGIN: getOverlays
: 9
Nov 21 18:08:18 User plasmashell[54419]: Could not find the Plasmoid for
Plasma::FrameSvgItem(0x55b7ef6d88e0) QQmlContext(0x55b7eabe9570)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Nov 21 18:08:18 User plasmashell[54419]: Could not find the Plasmoid for
Plasma::FrameSvgItem(0x55b7ef6d88e0) QQmlContext(0x55b7eabe9570)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Nov 21 18:08:18 User kdeconnectd[2382]: QDBusAbstractAdaptor: Cannot relay
signal SftpPlugin::packetReceived(NetworkPacket): Unregistered input type in
parameter list: NetworkPacket
Nov 21 18:08:18 User kdeconnectd[55036]: /usr/bin/fusermount: entry for
/run/user/1000/254223ae_f376_48bc_bacd_c5535f54a9d8 not found in /etc/mtab
Nov 21 18:08:20 User dolphin[54983]: MEGASYNCOVERLAYPLUGIN: getOverlays
: 9
```
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 472117] New: Cannot export animation using the ffmpeg plug in, animation needed for approaching deadline
https://bugs.kde.org/show_bug.cgi?id=472117 Bug ID: 472117 Summary: Cannot export animation using the ffmpeg plug in, animation needed for approaching deadline Classification: Applications Product: krita Version: 5.1.5 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: critical Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: ali.em.di...@hotmail.com Target Milestone: --- Created attachment 160218 --> https://bugs.kde.org/attachment.cgi?id=160218&action=edit pdf of screenshots of issue 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. Go to export animation, follow prompts to download the ffmpeg codec plug in at evermeet.cx/ffmpeg/ 2. Downloaded fmpeg-111376-g13ef5025e3.7z and opened zip file to find a single exec file titled ffmpeg 3. Excec ffmpeg file could not be opened or applied to Krita because it could not be verified. OBSERVED RESULT I ignored the warning and proceeded to render animation. Krita did render a Quicktime file but it was not playable. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 472639] New: kalendar unexpectedly shut down after trying to create a new event. Akonadi is disable.
https://bugs.kde.org/show_bug.cgi?id=472639 Bug ID: 472639 Summary: kalendar unexpectedly shut down after trying to create a new event. Akonadi is disable. Classification: Applications Product: kalendar Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: abukhamsin.al...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 160525 --> https://bugs.kde.org/attachment.cgi?id=160525&action=edit error-screenshot SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION every time I open kalendar to create a new event/task buy clicking the "+" in the top right corner or by double clicking the time slot it will crash. I restarted the application multiple times same result. I disabled akonadi from /home/user/.config/akonadi/akonadiserverrc and set StartServer=false. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 472639] kalendar unexpectedly shut down after trying to create a new event. Akonadi is disable.
https://bugs.kde.org/show_bug.cgi?id=472639 --- Comment #1 from Ali --- (In reply to Ali from comment #0) > Created attachment 160525 [details] > error-screenshot > > SUMMARY > *** > NOTE: If you are reporting a crash, please try to attach a backtrace with > debug symbols. > See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports > *** > > > STEPS TO REPRODUCE > 1. > 2. > 3. > > OBSERVED RESULT > > > EXPECTED RESULT > > > SOFTWARE/OS VERSIONS > Linux/KDE Plasma: Archlinux > (available in About System) > KDE Plasma Version: 5.27.6 > KDE Frameworks Version: 5.108.0 > Qt Version: 5.15.10 > > ADDITIONAL INFORMATION > every time I open kalendar to create a new event/task buy clicking the "+" > in the top right corner or by double clicking the time slot it will crash. I > restarted the application multiple times same result. > I disabled akonadi from /home/user/.config/akonadi/akonadiserverrc and set > StartServer=false. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 489837] New: [regression] "FlatpakApp is not installed but it still has data present" prompt no longer appears after Plasma 6.1
https://bugs.kde.org/show_bug.cgi?id=489837 Bug ID: 489837 Summary: [regression] "FlatpakApp is not installed but it still has data present" prompt no longer appears after Plasma 6.1 Classification: Applications Product: Discover Version: 6.1.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: plasma-b...@kde.org Reporter: radical...@proton.me CC: aleix...@kde.org, jgrul...@redhat.com, trav...@redhat.com Target Milestone: --- SUMMARY Discover never shows the prompt to delete leftover flatpak data after uninstalling or opening a page of a formerly installed flatpak with leftover data (despite it having done so in 5.27 and possibly 6.0.x but I unfortunately have foggy memory in regards to this) STEPS TO REPRODUCE 1. Install and open flatpak app 2. Uninstall flatpak 3. Wait for Discover to give the "FlatpakApp is not installed but it still has data present" prompt OBSERVED RESULT Discover doesn't show the leftover data deletion prompt, not allowing the user to remove leftover data via Discover EXPECTED RESULT Discover should show the prompt, and remove leftover flatpak data. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.6.37-1-lts (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Was reproducible on another device running Fedora KDE 40 with Plasma 6.1.1.2 -- You are receiving this mail because: You are watching all bug changes.
[knetattach] [Bug 489948] New: Allow KNetAttach to use private keys to authenticate SFTP connections
https://bugs.kde.org/show_bug.cgi?id=489948 Bug ID: 489948 Summary: Allow KNetAttach to use private keys to authenticate SFTP connections Classification: Applications Product: knetattach Version: 6.1.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: radical...@proton.me Target Milestone: --- SUMMARY Allow KNetAttach to use private keys to authenticate SFTP connections instead of forcing the user to setup ~/.ssh/config to workaround the issue, just like the SSH Manager in Konsole. (one of my favourite tools as a newbie! <3) SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.6.37-1-lts (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 468995] Dolphin ftp:// cannot access folders with character ':' at the end
https://bugs.kde.org/show_bug.cgi?id=468995 Ali changed: What|Removed |Added CC||radical...@proton.me --- Comment #1 from Ali --- Can reproduce, still happens on Dolphin 24.05.2, didn't want to install FileZilla to access my homebrewed Vita's directories and got excited when everything looked right until I tried to open a directory :,) Expected it to work because Nautilus was able to just fine but unfortunately it wasn't able to. SYSTEM INFO: Operating System: EndeavourOS KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.6.40-1-lts (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6267U CPU @ 2.90GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® Iris® Graphics 550 Manufacturer: Apple Inc. Product Name: MacBookPro13,2 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 489837] [regression] "FlatpakApp is not installed but it still has data present" prompt no longer appears after Plasma 6.1
https://bugs.kde.org/show_bug.cgi?id=489837 --- Comment #2 from Ali --- (In reply to Harald Sitter from comment #1) > Seems to work fine on master (6.2). Indeed looking at the code I don't see > how this could break exactly; it's literally just checking if > ~/.var/$flatpakid exists. > > Does this happen with all flatpaks or maybe just specific ones? I've gotten it working on a fresh image of Neon Testing (build date 2024-07-23), but it's still reproducible on neon stable (build date 2024-07-18, comes with 6.1.2, but prompt doesn't happen on 6.1.3 after updating regardless), fedora kde 40 (on 6.1.3), and endeavourOS/Arch Plasma (on 6.1.3) This seems to be fixed in some nightly bugfix branch, not sure what fixes it tho :l maybe something like https://invent.kde.org/plasma/discover/-/merge_requests/875 ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490743] New: when I change the font, the notifications start looking funny
https://bugs.kde.org/show_bug.cgi?id=490743 Bug ID: 490743 Summary: when I change the font, the notifications start looking funny Classification: Plasma Product: plasmashell Version: 6.1.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: ali93...@gmail.com CC: k...@privat.broulik.de Target Milestone: 1.0 Created attachment 171946 --> https://bugs.kde.org/attachment.cgi?id=171946&action=edit This is what I mean when I say wonky, I don't know how to describe it :3 SUMMARY when I change the font, the notifications start looking wonky STEPS TO REPRODUCE 1. Change your font (in my case I've changed it to ubuntu font) 2. Download something from the internet 3. Hide the popup notification 4. Then open the notifications in the system tray **SOFTWARE/OS VERSIONS** Operating System: EndeavourOS KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.10.0-arch1-2 (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5500 Memory: 15.4 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485614] New: [FEATURE REQUEST] Allow navigation of dolphin while dragging and dropping a file.
https://bugs.kde.org/show_bug.cgi?id=485614 Bug ID: 485614 Summary: [FEATURE REQUEST] Allow navigation of dolphin while dragging and dropping a file. Classification: Applications Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: radical...@proton.me CC: kfm-de...@kde.org Target Milestone: --- == WISHLIST / FEATURE REQUEST == SUMMARY Allow navigation through folders, tabs and side panel shortcuts while dragging and dropping by simply hovering over said objects for a few seconds. This behaviour is in Nautilus and Finder, and makes navigating subdirectories while dragging and dropping files to be less of a painful maneuver. STEPS TO REPRODUCE 1. Drag any file 2. Hover over any folder, tab, or side panel shortcut OBSERVED RESULT You keep holding the file instead of entering the directory EXPECTED RESULT You enter the directory after a few seconds of holding the drag and dropped file. ADDITIONAL INFORMATION Make this a configurable option if possible, maybe even make the time it takes for a directory to be entered from the hover state be changeable? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485977] New: Moving files by dragging and dropping them is crashing dolphin
https://bugs.kde.org/show_bug.cgi?id=485977 Bug ID: 485977 Summary: Moving files by dragging and dropping them is crashing dolphin Classification: Applications Product: dolphin Version: 24.02.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: ali93...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 168810 --> https://bugs.kde.org/attachment.cgi?id=168810&action=edit this is a video of the bug, hope it helps *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Moving files by dragging and dropping them in the navigation is crashing dolphin (Wayland) STEPS TO REPRODUCE 1. make sure you're on a wayland session 2. open dolphin 3. open a folder with files 4. drag one of the files to the parent folder using the navigation bar OBSERVED RESULT Dolphin crashes EXPECTED RESULT The file moved to the parent folder SOFTWARE/OS VERSIONS OS: EndeavourOS Linux x86_64 DE: Plasma 6.0.4 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Graphics Platform: Wayland ADDITIONAL INFORMATION I think this happens on wayland only -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485977] Moving files by dragging and dropping them is crashing dolphin
https://bugs.kde.org/show_bug.cgi?id=485977 --- Comment #1 from ali --- (In reply to ali from comment #0) > Created attachment 168810 [details] > this is a video of the bug, hope it helps > > SUMMARY > Moving files by dragging and dropping them in the navigation is crashing > dolphin (Wayland) > > STEPS TO REPRODUCE > 1. make sure you're on a wayland session > 2. open dolphin > 3. open a folder with files > 4. drag one of the files to the parent folder using the navigation bar > > OBSERVED RESULT > Dolphin crashes > > EXPECTED RESULT > The file moved to the parent folder > > SOFTWARE/OS VERSIONS > OS: EndeavourOS Linux x86_64 > DE: Plasma 6.0.4 > KDE Plasma Version: 6.0.4 > KDE Frameworks Version: 6.1.0 > Qt Version: 6.7.0 > Graphics Platform: Wayland > > ADDITIONAL INFORMATION > I think this happens on wayland only -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486264] Natural (inverted) scrolling doesn't work on system tray.
https://bugs.kde.org/show_bug.cgi?id=486264 Ali changed: What|Removed |Added CC||radical...@proton.me --- Comment #1 from Ali --- +1, Can reproduce with any scrollable icon in systray (volume and brightness) I have natural / inverted scrolling on for both my trackpad and mouse wheel, and it does the same for both, maybe make diff. scrolling directions toggleable in systray config? eitherway, I'm not sure this is intended behaviour or not. Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6267U CPU @ 2.90GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® Iris® Graphics 550 Manufacturer: Apple Inc. Product Name: MacBookPro13,2 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483594] Plasma panel won't dodge windows if placed between dual monitors
https://bugs.kde.org/show_bug.cgi?id=483594 Ali changed: What|Removed |Added CC||radical...@proton.me --- Comment #4 from Ali --- +1, ran into this while trying to have a side panel on the same side as my second screen, dodge windows works perfectly on any other side that isn't on the same side as my second screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483594] Plasma panel won't dodge windows if placed between dual monitors
https://bugs.kde.org/show_bug.cgi?id=483594 --- Comment #5 from Ali --- (In reply to Ali from comment #4) > +1, ran into this while trying to have a side panel on the same side as my > second screen, dodge windows works perfectly on any other side that isn't on > the same side as my second screen. Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 491482] New: Flatpak Add-ons button is completely missing from Flatpak apps pages if they do have them in Plasma 6 Discover
https://bugs.kde.org/show_bug.cgi?id=491482 Bug ID: 491482 Summary: Flatpak Add-ons button is completely missing from Flatpak apps pages if they do have them in Plasma 6 Discover Classification: Applications Product: Discover Version: 6.1.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: plasma-b...@kde.org Reporter: radical...@proton.me CC: aleix...@kde.org, jgrul...@redhat.com, trav...@redhat.com Target Milestone: --- Created attachment 172436 --> https://bugs.kde.org/attachment.cgi?id=172436&action=edit Messy image showing Steam, VLC and OBS' addon buttons and page, alongside comparison of the OBS page between 5.27 and Plasma 6.1 SUMMARY Flatpak app pages in Discover post Plasma 6 seem to be missing the Add-ons button that would take you to the Add-ons page, if the listed app has any available add-ons, this button used to previously exist in Plasma 5.27. (image for reference) Add-ons are also listed on said app's flathub page, apps with flatpak add-ons listed below: https://flathub.org/apps/org.videolan.VLC https://flathub.org/apps/com.obsproject.Studio https://flathub.org/apps/com.valvesoftware.Steam STEPS TO REPRODUCE 1. In Discover, search for a flatpak app that'd have Add-ons (VLC, OBS, Steam, etc) 2. Look at the buttons below the app description. OBSERVED RESULT The Add-ons button is completely missing on (seemingly) any version of Discover post Plasma 6 (including 6.2 Dev as of August 9th) EXPECTED RESULT The Add-ons button should be present and available for apps that have them. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.6.44-3-lts (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Every screenshot within the messy image with exception to the comparison screenshot to Plasma 6.1.4 Discover is discover ran with `plasma-discover --backends flatpak` so this doesn't seem to be a PackageKit issue. (the arch install doesn't have PackageKit installed either), also was able to reproduce on Fedora 40 KDE with 6.1.3, and Neon Unstable Edition with 6.2 Dev. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482543] Reset the circle of wallpaper slideshow
https://bugs.kde.org/show_bug.cgi?id=482543 --- Comment #2 from Ali --- (In reply to Nate Graham from comment #1) > I gather you set the order to something other than "Random"? No, Order is A to Z -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483086] New: Keyboard shortcuts not work for third-party apps
https://bugs.kde.org/show_bug.cgi?id=483086 Bug ID: 483086 Summary: Keyboard shortcuts not work for third-party apps Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: fakham...@gmail.com Target Milestone: --- Created attachment 166854 --> https://bugs.kde.org/attachment.cgi?id=166854&action=edit Crow Translate SUMMARY *** After update to 6 keyboard shortcuts not work for third-party apps, like Crow Translate, NekoRay. *** SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.5.0-25-generic (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483086] Keyboard shortcuts not work for third-party apps
https://bugs.kde.org/show_bug.cgi?id=483086 --- Comment #2 from Ali --- (In reply to Nicolas Fella from comment #1) > Are you using Wayland or X11? wayland -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483312] New: Crash UI after screen goes black
https://bugs.kde.org/show_bug.cgi?id=483312 Bug ID: 483312 Summary: Crash UI after screen goes black Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: fakham...@gmail.com Target Milestone: --- SUMMARY *** Inside x11, when one of the 2 monitors is turned off or the screen is locked and the screen turns black, after turning on one of the monitors, it turns off and blinks, and after a few seconds, the entire user interface crashes. How can I collect and send logs? I have this problem only in x11, and it was in version 5 as well. *** STEPS TO REPRODUCE 1. Physically turning off one of the 2 monitors 2. Turn on that monitor 3. Both or one of 2 monitor start blinking and 4. UI and shell crash STEPS TO REPRODUCE 1. Lock the screen 2. After few second screens goes black 3. After move mouse to turn on and unlock UI and shell crash SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-25-generic (64-bit) Graphics Platform: X11 Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483312] Crash UI after screen goes black
https://bugs.kde.org/show_bug.cgi?id=483312 --- Comment #2 from Ali --- (In reply to Nicolas Fella from comment #1) > If something crashed, we need a backtrace of it so we can figure out what's > going on. Can you please attach a backtrace of the crash using the > coredumpctl command-line program, as detailed in > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? > > Thanks! It doesn't exactly crash. The screen flashes and then goes completely black, and only the mouse cursor remains, and I have to reboot. I typed this command and it had this output. How do I get the log exactly? $ coredumpctl --reverse TIME PID UID GID SIG COREFILE EXE SIZE Wed 2024-03-13 11:31:31 +0330 184700 SIGSEGV inaccessible /snap/cups/1024/sbin/cups-proxyd n/a Wed 2024-03-13 11:29:06 +0330 184000 SIGSEGV inaccessible /snap/cups/1024/sbin/cups-proxyd n/a Wed 2024-03-13 11:21:45 +0330 7921 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 967.9K Wed 2024-03-13 11:21:44 +0330 7766 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 967.1K Wed 2024-03-13 11:21:44 +0330 7639 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 968.7K Wed 2024-03-13 11:21:43 +0330 7504 1000 1000 SIGABRT present /usr/bin/plasmashell 1016.0K Wed 2024-03-13 11:21:43 +0330 7506 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 967.0K Wed 2024-03-13 11:21:43 +0330 7439 1000 1000 SIGABRT present /usr/bin/plasmashell 1016.4K Wed 2024-03-13 11:21:43 +0330 7443 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 967.2K Wed 2024-03-13 11:21:08 +0330 184300 SIGSEGV inaccessible /snap/cups/1024/sbin/cups-proxyd n/a -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 483480] New: Desktop effects (Including Cube) become unstable after using super high quality images as the Skybox in the Cube effect on older/weakerhardware
https://bugs.kde.org/show_bug.cgi?id=483480 Bug ID: 483480 Summary: Desktop effects (Including Cube) become unstable after using super high quality images as the Skybox in the Cube effect on older/weakerhardware Classification: Plasma Product: kdeplasma-addons Version: 6.0.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Cube Assignee: plasma-b...@kde.org Reporter: radical...@proton.me CC: vlad.zahorod...@kde.org Target Milestone: --- SUMMARY Using a high quality / large sized image (for reference, I was using this image: https://unsplash.com/photos/galaxy-digital-wallpaper-rCbdp8VCYhQ) as a skybox on the Cube effect seems to make the effect unstable, make the screen go black, distort and cause some other freaky visual glitches, including not render on both monitors if a second display is connected. Even if you recover back to desktop from a broken Cube effect being used, this seems to also break some other desktop effects (most notably Overview) resulting in the screen going black and distorting until clicked back onto the desktop. This can result in a full system lockup, and in some cases, Cube can render correctly but will delay a decent amount of seconds before appearing, in this delay, the screen goes black till Cube correctly appears. STEPS TO REPRODUCE 1. Enable and configure Cube to use a large sized image as a Skybox on weaker hardware 2. press Meta+C OBSERVED RESULT Various visual glitches are caused by Cube leading either to a system lockup or if recovered from, causing most desktop effects to make the screen black out until the session is restarted. EXPECTED RESULT Cube either renders correctly with no / little delay or warns the user that the effect may be unstable with the image provided for the skybox. (maybe entirely prevents the image and falls back to a plain colour?) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 40 KDE Plasma PreRelease (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Additional Hardware Information for "older / lower end hardware": Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6267U CPU @ 2.90GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® Iris® Graphics 550 Manufacturer: Apple Inc. Product Name: MacBookPro13,2 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 483480] Desktop effects (Including Cube) become unstable after using super high quality images as the Skybox in the Cube effect on older/weakerhardware
https://bugs.kde.org/show_bug.cgi?id=483480 --- Comment #1 from Ali --- https://youtu.be/pc2_gMYasjs video of the bug, playing back the screen recording on VLC caused it to hang a fair few amount of times midplayback which was unique to say the least -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487964] New: help
https://bugs.kde.org/show_bug.cgi?id=487964 Bug ID: 487964 Summary: help Classification: Applications Product: systemsettings Version: 5.27.10 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ailppssppb...@gmail.com Target Milestone: --- Application: systemsettings (5.27.10) (Compiled from sources) Qt Version: 5.15.10 Frameworks Version: 5.115.0 Operating System: Linux 6.6.15-amd64 x86_64 Windowing System: X11 Distribution: Kali GNU/Linux Rolling DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: Problems when I open settings or choose a theme or select and other problems. For example, the theme I searched for does not exist, but it exists on other systems. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: إعدادات النّظام (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7fa1e4a99d44 in KNSCore::EntryInternal::EntryInternal(KNSCore::EntryInternal const&) () from /lib/x86_64-linux-gnu/libKF5NewStuffCore.so.5 #5 0x7fa1e4ab0310 in KNSCore::ItemsModel::data(QModelIndex const&, int) const () from /lib/x86_64-linux-gnu/libKF5NewStuffCore.so.5 #6 0x7fa1e42bdaae in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/libnewstuffqmlplugin.so #7 0x7fa1e42c620b in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/libnewstuffqmlplugin.so #8 0x7fa20f8cfc83 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7fa20f7a7f49 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7fa20f7a9e73 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7fa20f7c729e in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7fa20f7ca9c7 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x7fa20f75b74a in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x7fa20f8eaaa1 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x7fa20f89b17f in QQmlBoundSignalExpression::evaluate(void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #16 0x7fa20f89c8c0 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x7fa20f8cf755 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #18 0x7fa211f05a0c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7fa20d3217a6 in QQuickAction::triggered(QObject*) () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #20 0x7fa20d322812 in ?? () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #21 0x7fa20d31e570 in QQuickAbstractButtonPrivate::trigger() () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #22 0x7fa20d3203e1 in QQuickAbstractButtonPrivate::handleRelease(QPointF const&) () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #23 0x7fa20d33fd49 in QQuickControl::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #24 0x7fa20fe5c348 in QQuickItem::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #25 0x7fa212b62f32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7fa211ecc748 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7fa20fe7a28e in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #28 0x7fa20fe7b981 in QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #29 0x7fa20fe7cb81 in QQuickWindowPrivate::handleMouseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #30 0x7fa21234ba05 in QWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #31 0x7fa212b62f32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x7fa211ecc748 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fa21233f7db in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #34 0x7fa2123131ec in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #35 0x7fa20c0fa15e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #36 0x7fa21030de1f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #37 0x7fa21030fea7 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #38 0x7fa2103104c0 in g_main_context
[kdeplasma-addons] [Bug 480906] Some Widgets ,Within A Grouped Plasmoid, In Vertical Panels Do Not Display Correctly
https://bugs.kde.org/show_bug.cgi?id=480906 Ali changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|1 |0 CC||radical...@proton.me Status|RESOLVED|REPORTED --- Comment #6 from Ali --- Can reproduce on Plasma 6.0.2, Arch Linux, panel size 270 https://imgur.com/a/a08jsG4 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 480906] Some Widgets ,Within A Grouped Plasmoid, In Vertical Panels Do Not Display Correctly
https://bugs.kde.org/show_bug.cgi?id=480906 --- Comment #7 from Ali --- ==further system info== KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.6.23-1-lts (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6267U CPU @ 2.90GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® Iris® Graphics 550 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484794] Some Fullscreen Apps get minimized when switching from one Virtual Desktop to another Virtual Desktop
https://bugs.kde.org/show_bug.cgi?id=484794 Ali changed: What|Removed |Added CC||radical...@proton.me --- Comment #1 from Ali --- +1, I can reproduce on Arch Linux with Plasma 6.0.3 Wayland. Games tested: Stardew Valley - bug doesn't happen - Native Half Life 1 - bug doesn't happen - Native Terraria - bug doesn't happen (though the preview seems a lil glitched when switching back? gameplay is unaffected though) - Native Pizza Tower - bug does happen - Proton/Steam Brawlhalla - bug doesn't happen - Proton/Steam Deltarune - bug does happen - Proton/Steam Shovel Knight - bug does happen - Native Minecraft (Tested under OpenGL/Xwayland, OpenGL/Native Wayland via WayGL,Vulkan/Wayland) - bug does happen - Native (NOTE: Enabling windowed fullscreen by way of clicking the titlebar and enabling the fullscreen option from plasma does not have this bug happen) I think this might apply to other apps that have a fullscreen function built in, but every other app I've fullscreened using the option available by right clicking the title bar > more actions > fullscreen doesn't result in this bug happening. SYSTEM DETAILS: Operating System: Arch Linux KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.6.23-1-lts (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6267U CPU @ 2.90GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® Iris® Graphics 550 Manufacturer: Apple Inc. Product Name: MacBookPro13,2 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 456407] New: error download effects and compositions (error: SETTINGS invalid number of concurrent streams).
https://bugs.kde.org/show_bug.cgi?id=456407 Bug ID: 456407 Summary: error download effects and compositions (error: SETTINGS invalid number of concurrent streams). Product: kdenlive Version: 22.04.2 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: aabbaabb13...@gmail.com Target Milestone: --- Created attachment 150448 --> https://bugs.kde.org/attachment.cgi?id=150448&action=edit This image show this error. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT Can't download effects and compositions but I can download it from the store. EXPECTED RESULT Error in programming SOFTWARE/OS VERSIONS Windows: 10 Pro 21H1 64bit macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 456409] New: error download effects and compositions (error: SETTINGS invalid number of concurrent streams).
https://bugs.kde.org/show_bug.cgi?id=456409 Bug ID: 456409 Summary: error download effects and compositions (error: SETTINGS invalid number of concurrent streams). Product: kdenlive Version: 22.04.2 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: aabbaabb13...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT Can't download effects and compositions but I can download it from the store. EXPECTED RESULT Error in programming SOFTWARE/OS VERSIONS Windows: 10 Pro 21H1 64bit macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 456410] New: Error download effects and compositions (error: SETTINGS invalid number of concurrent streams).
https://bugs.kde.org/show_bug.cgi?id=456410 Bug ID: 456410 Summary: Error download effects and compositions (error: SETTINGS invalid number of concurrent streams). Product: kdenlive Version: 22.04.2 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: aabbaabb13...@gmail.com Target Milestone: --- Created attachment 150449 --> https://bugs.kde.org/attachment.cgi?id=150449&action=edit This image show this error. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT Can't download effects and compositions and transitions but I can download it with the store. EXPECTED RESULT Error in programming. SOFTWARE/OS VERSIONS Windows: 10 Pro 21H1 64bit macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 456409] error download effects and compositions (error: SETTINGS invalid number of concurrent streams).
https://bugs.kde.org/show_bug.cgi?id=456409 Ali changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Ali --- *** This bug has been marked as a duplicate of bug 456407 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 456407] error download effects and compositions (error: SETTINGS invalid number of concurrent streams).
https://bugs.kde.org/show_bug.cgi?id=456407 --- Comment #1 from Ali --- *** Bug 456409 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 456410] Error download effects and compositions (error: SETTINGS invalid number of concurrent streams).
https://bugs.kde.org/show_bug.cgi?id=456410 Ali changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Ali --- *** This bug has been marked as a duplicate of bug 456407 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 456407] error download effects and compositions (error: SETTINGS invalid number of concurrent streams).
https://bugs.kde.org/show_bug.cgi?id=456407 --- Comment #2 from Ali --- *** Bug 456410 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 456407] Error download effects and compositions (error: SETTINGS invalid number of concurrent streams).
https://bugs.kde.org/show_bug.cgi?id=456407 Ali changed: What|Removed |Added Summary|error download effects and |Error download effects and |compositions (error:|compositions (error: |SETTINGS invalid number of |SETTINGS invalid number of |concurrent streams).|concurrent streams). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 456407] Error download effects and compositions (error: SETTINGS invalid number of concurrent streams).
https://bugs.kde.org/show_bug.cgi?id=456407 Ali changed: What|Removed |Added CC||aabbaabb13...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384758] When the panel is set to auto-hide, "Alternatives" pop-up doesn't appear
https://bugs.kde.org/show_bug.cgi?id=384758 ALi changed: What|Removed |Added CC||ali.hosseini...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435677] New: plugin manager is empty
https://bugs.kde.org/show_bug.cgi?id=435677 Bug ID: 435677 Summary: plugin manager is empty Product: krita Version: 4.4.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: overman.supermund...@gmail.com Target Milestone: --- Python plugin manager is empty, starting krita from the command line, i get these errors > Invalid profile : "/usr/share/color/icc/colord/Crayons.icc" "Crayon Colors" Invalid profile : "/usr/share/color/icc/colord/x11-colors.icc" "X11 Colors" Could not set current file 0 "brushes/rake_sparse.png" krita.general: Bundle is broken. File "brushes/rake_sparse.png" is missing Could not set current file 0 "brushes/rock_pitted.gih" krita.general: Bundle is broken. File "brushes/rock_pitted.gih" is missing Could not set current file 0 "brushes/square_rough.png" krita.general: Bundle is broken. File "brushes/square_rough.png" is missing krita.general: Due to missing files and wrong entries in the manifest, "/usr/share/krita/bundles/RGBA_brushes.bundle" will be recreated. QuaZipFile::open(): file open mode 2 incompatible with ZIP open mode 0 Could not open "brushes/Craig_02.png" 0 krita.lib.store: KoStore: You must open before writing krita.lib.store: You must open before closing QuaZipFile::open(): file open mode 2 incompatible with ZIP open mode 0 Could not open "brushes/DA_RGBA bluegreen_small.png" 0 QBuffer::setBuffer: Buffer is open krita.lib.store: KoStore: You must open before writing krita.lib.store: You must open before closing QuaZipFile::open(): file open mode 2 incompatible with ZIP open mode 0 Could not open "brushes/DA_RGBA bluegreen_small1.png" 0 QBuffer::setBuffer: Buffer is open krita.lib.store: KoStore: You must open before writing krita.lib.store: You must open before closing QuaZipFile::open(): file open mode 2 incompatible with ZIP open mode 0 Could not open "brushes/DA_Triangle grain.png" 0 QBuffer::setBuffer: Buffer is open krita.lib.store: KoStore: You must open before writing krita.lib.store: You must open before closing QuaZipFile::open(): file open mode 2 incompatible with ZIP open mode 0 Could not open "brushes/Mountain_Brush_01.png" 0 QBuffer::setBuffer: Buffer is open krita.lib.store: KoStore: You must open before writing krita.lib.store: You must open before closing QuaZipFile::open(): file open mode 2 incompatible with ZIP open mode 0 Could not open "brushes/RGBA anim 01.gih" 0 QBuffer::setBuffer: Buffer is open krita.lib.store: KoStore: You must open before writing krita.lib.store: You must open before closing Could not set current file 0 "brushes/rake_sparse.png" Could not set current file 0 "brushes/rock_pitted.gih" Could not set current file 0 "brushes/square_rough.png" QuaZipFile::open(): file open mode 2 incompatible with ZIP open mode 0 Could not open "paintoppresets/m)_RGBA_01_Thick-dry.kpp" 0 QBuffer::setBuffer: Buffer is open krita.lib.store: KoStore: You must open before writing krita.lib.store: You must open before closing QuaZipFile::open(): file open mode 2 incompatible with ZIP open mode 0 Could not open "paintoppresets/m)_RGBA_02_Thickpaint.kpp" 0 QBuffer::setBuffer: Buffer is open krita.lib.store: KoStore: You must open before writing krita.lib.store: You must open before closing QuaZipFile::open(): file open mode 2 incompatible with ZIP open mode 0 Could not open "paintoppresets/m)_RGBA_03_Rake.kpp" 0 QBuffer::setBuffer: Buffer is open krita.lib.store: KoStore: You must open before writing krita.lib.store: You must open before closing QuaZipFile::open(): file open mode 2 incompatible with ZIP open mode 0 Could not open "paintoppresets/m)_RGBA_04_Impasto.kpp" 0 QBuffer::setBuffer: Buffer is open krita.lib.store: KoStore: You must open before writing krita.lib.store: You must open before closing QuaZipFile::open(): file open mode 2 incompatible with ZIP open mode 0 Could not open "paintoppresets/m)_RGBA_05_Impasto-details.kpp" 0 QBuffer::setBuffer: Buffer is open krita.lib.store: KoStore: You must open before writing krita.lib.store: You must open before closing QuaZipFile::open(): file open mode 2 incompatible with ZIP open mode 0 Could not open "paintoppresets/m)_RGBA_06_Rock.kpp" 0 QBuffer::setBuffer: Buffer is open krita.lib.store: KoStore: You must open before writing krita.lib.store: You must open before closing QuaZipFile::open(): file open mode 2 incompatible with ZIP open mode 0 Could not open "preview.png" 0 QBuffer::setBuffer: Buffer is open krita.general: Could not open preview.png krita.lib.store: KoStore: You must open before writing krita.general: Could not write preview.png krita.lib.store: You must open before closing QuaZipFile::open(): file open mode 2 incompatible with ZIP open mod
[krita] [Bug 440384] New: Krita crashes when exiting
https://bugs.kde.org/show_bug.cgi?id=440384 Bug ID: 440384 Summary: Krita crashes when exiting Product: krita Version: 4.4.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: overman.supermund...@gmail.com Target Milestone: --- Created attachment 140387 --> https://bugs.kde.org/attachment.cgi?id=140387&action=edit crash report SUMMARY Krita crashes when exiting. it works fine, only when i click (x) on the program window, or select file-> Quit, i get prompt to file a crash report, it happens every time. STEPS TO REPRODUCE 1. run Krita 2. chose from menu file-> Quit. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 427119] New: Could not write to sftp
https://bugs.kde.org/show_bug.cgi?id=427119 Bug ID: 427119 Summary: Could not write to sftp Product: dolphin Version: 19.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: khsr...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin fails to copy files over the same sftp connection: STEPS TO REPRODUCE 1. Add a Network folder through an ssh connection 2. Open the folder, split it 3. change the path of one of the sides to somewhere else, but still in same remote connection. 4. Try to select a file from one side and manually copy to the other side OBSERVED RESULT Despite sometimes copy is successful, most of the times it fails to copy, a window opens with: "Internal Error Please send a full bug report at https://bugs.kde.org " And I am sure the problem is not from losing connection. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel: 5.4.0.-47-generic Os Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 427119] Could not write to sftp
https://bugs.kde.org/show_bug.cgi?id=427119 --- Comment #1 from Ali --- Moreover, The problem arises mainly with specific file names. For instance, dolphin is not able to copy a file with this name: "system_100_relax_Z_WIRE_Temp_300.0_glue_15_Tdamp_0.1" Not even able to rename the file. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 427119] Could not write to sftp
https://bugs.kde.org/show_bug.cgi?id=427119 Ali changed: What|Removed |Added Version|unspecified |19.12 --- Comment #2 from Ali --- $apt show kio-extras Package: kio-extras Version: 4:19.12.3a-0ubuntu2 Priority: extra Section: universe/utils Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian/Kubuntu Qt/KDE Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 2.371 kB -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 427119] Could not write to sftp
https://bugs.kde.org/show_bug.cgi?id=427119 --- Comment #4 from Ali --- (In reply to Harald Sitter from comment #3) > Unfortunately the 19.12 release is no longer supported and I cannot > reproduce this on the upcoming 20.12. > Can you try to reproduce this with kio-extras 20.08 or git master? I was not able to install kio-extras 20.08 on Kubuntu 20.04. Compiling git master demanded to install a lot of packages which I do not have. I am waiting for 20.12 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 428540] New: pen pressure registering as if i was doing full pressure then applying almost no pressure making my lines dotty
https://bugs.kde.org/show_bug.cgi?id=428540 Bug ID: 428540 Summary: pen pressure registering as if i was doing full pressure then applying almost no pressure making my lines dotty Product: krita Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: critical Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: duhhell...@gmail.com Target Milestone: --- SUMMARY when put light pressure with my pen It acts as if i was putting full pressure and than instantly applying no pressure. also when i go to edit my brush and draw on that little screen it works perfectly, but once i go back to the main screen it acts up I'm posting a video of whats its doing at SGXHQ on youtube, hopefully the video will be able to explain better STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 428540] pen pressure registering as if i was doing full pressure then applying almost no pressure making my lines dotty
https://bugs.kde.org/show_bug.cgi?id=428540 --- Comment #1 from Ali --- there's a video on youtube @SGXHQ about 5 minutes long it should tell in more detail -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 428540] pen pressure registering as if i was doing full pressure then applying almost no pressure making my lines dotty
https://bugs.kde.org/show_bug.cgi?id=428540 --- Comment #3 from Ali --- So I switched to (windows ink) in tablet settings and not ITS WORKING. For those of you who are wondering, I have a dell inspiron 15.6 and I’m useing a xp pen artist 12 pro. I appreciate the quick replies and the support, I was literally at it for hours trying to figure out how to fix it -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 428540] pen pressure registering as if i was doing full pressure then applying almost no pressure making my lines dotty
https://bugs.kde.org/show_bug.cgi?id=428540 --- Comment #4 from Ali --- Wth so my previous comment said it’s not working I meant it’s WORKING. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426898] Dolphin not opening
https://bugs.kde.org/show_bug.cgi?id=426898 Ali changed: What|Removed |Added CC||alim...@iran.ir -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426898] Dolphin not opening
https://bugs.kde.org/show_bug.cgi?id=426898 --- Comment #11 from Ali --- Created attachment 134168 --> https://bugs.kde.org/attachment.cgi?id=134168&action=edit New crash information added by DrKonqi dolphin (20.12.0) using Qt 5.15.2 Last night I updated 6 apps using the discover app: libpipewire-0.3-0:amd64 (0.3.17-0xneon+20.04+focal+build8, 0.3.18-0xneon+20.04+focal+build10), pipewire:amd64 (0.3.17-0xneon+20.04+focal+build8, 0.3.18-0xneon+20.04+focal+build10), distro-release-notifier:amd64 (0.0+p20.04+git20201129.0022-0, 0.0+p20.04+git20201216.0022-0), libspa-0.2-modules:amd64 (0.3.17-0xneon+20.04+focal+build8, 0.3.18-0xneon+20.04+focal+build10), libpipewire-0.3-modules:amd64 (0.3.17-0xneon+20.04+focal+build8, 0.3.18-0xneon+20.04+focal+build10), pipewire-bin:amd64 (0.3.17-0xneon+20.04+focal+build8, 0.3.18-0xneon+20.04+focal+build10) And today I wanted to open the Dolphin app, which gave me an error every time -- Backtrace (Reduced): #4 0x7f3eb58cd63b in KUrlNavigator::locationUrl(int) const () from /lib/x86_64-linux-gnu/libKF5KIOFileWidgets.so.5 #5 0x7f3eb5cb3af8 in DolphinViewContainer::setSearchModeEnabled (this=this@entry=0x55bfcaea8a70, enabled=true) at /usr/include/c++/9/bits/atomic_base.h:413 #6 0x7f3eb5cb5399 in DolphinViewContainer::DolphinViewContainer (this=0x55bfcaea8a70, url=..., parent=) at ./src/dolphinviewcontainer.cpp:188 #7 0x7f3eb5cbbc45 in DolphinTabPage::createViewContainer (this=this@entry=0x55bfcaf55d70, url=...) at ./src/dolphintabpage.cpp:432 #8 0x7f3eb5cbbf4f in DolphinTabPage::DolphinTabPage (this=0x55bfcaf55d70, primaryUrl=..., secondaryUrl=..., parent=) at ./src/dolphintabpage.cpp:34 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426898] Dolphin not opening
https://bugs.kde.org/show_bug.cgi?id=426898 --- Comment #14 from Ali --- I took a screenshot and when I wanted to determine the path of the save, I tried it with dolphin and now it has been fixed! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457448] New: When copying and pasting Arabic from a PDF file, the text reverse direction
https://bugs.kde.org/show_bug.cgi?id=457448 Bug ID: 457448 Summary: When copying and pasting Arabic from a PDF file, the text reverse direction Product: okular Version: 22.04.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: overman.supermund...@gmail.com Target Milestone: --- Created attachment 151090 --> https://bugs.kde.org/attachment.cgi?id=151090&action=edit When copying and pasting Arabic from a PDF file, the text reverse direction SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION When copying and pasting Arabic from a PDF file, the text reverse direction OS MS Windows 11 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 457284] Lock screen wallpaper is all black after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=457284 Ali changed: What|Removed |Added CC||tats...@gmail.com --- Comment #25 from Ali --- Hi, I just get it fixed by removing the NVIDIA driver completely and reinstall it again. sudo apt-get purge '*nvidia*' -y reboot sudo apt-get install nvidia-driver-515 reboot sudo apt-get install nvidia-modprobe reboot -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 457284] Lock screen wallpaper is all black after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=457284 Ali changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #26 from Ali --- (In reply to Ali from comment #25) > Hi, > I just get it fixed by removing the NVIDIA driver completely and reinstall > it again. > > sudo apt-get purge '*nvidia*' -y > reboot > sudo apt-get install nvidia-driver-515 > reboot > sudo apt-get install nvidia-modprobe > reboot issue reproduced , black background -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 457284] Lock screen wallpaper is all black after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=457284 Ali changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #27 from Ali --- I downgraded the nvidia-driver to 510 and apply this line > sudo chmod +x /usr/share/screen-resolution-extra/nvidia-polkit open nvidia-settings and save the x server display configuration by pressing "save to x configuration file" -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406367] New: crash on saving
https://bugs.kde.org/show_bug.cgi?id=406367 Bug ID: 406367 Summary: crash on saving Product: krita Version: 4.1.7 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: overman.supermund...@gmail.com Target Milestone: --- Application: krita (4.1.7) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.18.0-17-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: it works fine, until i try to save the document , it crashes immediately after closing on the save button in the save dialog The crash can be reproduced every time. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc2d003d280 (LWP 28123))] Thread 4 (Thread 0x7fc278fbf700 (LWP 28144)): [KCrash Handler] #6 0x7fc2c7b72b68 in KoStore::pos() const () at /usr/lib/x86_64-linux-gnu/libkritastore.so.17 #7 0x7fc2a2822bac in () at /usr/lib/x86_64-linux-gnu/libfreeimage.so.3 #8 0x7fc2a28170ed in FreeImage_GetFileTypeFromHandle () at /usr/lib/x86_64-linux-gnu/libfreeimage.so.3 #9 0x7fc2a2aa01de in FreeImageHandler::GetFIF(QIODevice*, QByteArray const&) () at /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libxfreeimage.so #10 0x7fc2a2aa18ec in FreeimageQt5Plugin::capabilities(QIODevice*, QByteArray const&) const () at /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libxfreeimage.so #11 0x7fc2cc6fbaae in () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x7fc2cc6fbd8c in () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x7fc2cc6fc218 in QImageWriter::canWrite() const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #14 0x7fc2cc6fc3d7 in QImageWriter::write(QImage const&) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #15 0x7fc2cc6cfc68 in QImageData::doImageIO(QImage const*, QImageWriter*, int) const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #16 0x7fc2cc6cfe79 in QImage::save(QIODevice*, char const*, int) const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #17 0x7fc26c6e236b in () at /usr/lib/x86_64-linux-gnu/kritaplugins/kritakraexport.so #18 0x7fc26c6e2c8b in () at /usr/lib/x86_64-linux-gnu/kritaplugins/kritakraexport.so #19 0x7fc26c6e2fd5 in () at /usr/lib/x86_64-linux-gnu/kritaplugins/kritakraexport.so #20 0x7fc26c6ded7f in () at /usr/lib/x86_64-linux-gnu/kritaplugins/kritakraexport.so #21 0x7fc2ced7f3b9 in KisImportExportManager::doExportImpl(QString const&, QSharedPointer, KisPinnedSharedPtr) () at /usr/lib/x86_64-linux-gnu/libkritaui.so.17 #22 0x7fc2ced7f698 in KisImportExportManager::doExport(QString const&, QSharedPointer, KisPinnedSharedPtr, bool) () at /usr/lib/x86_64-linux-gnu/libkritaui.so.17 #23 0x7fc2ced81905 in () at /usr/lib/x86_64-linux-gnu/libkritaui.so.17 #24 0x7fc2cbeeb2b2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7fc2cbeee17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7fc2c560f6db in start_thread (arg=0x7fc278fbf700) at pthread_create.c:463 #27 0x7fc2cb5d188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fc280bb7700 (LWP 28132)): #0 0x7fc2cb5c4bf9 in __GI___poll (fds=0x7fc2740234b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc2c3f8a539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc2c3f8a64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc2cc1259bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc2cc0caa1a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc2cbee923a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc2abade2a6 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fc2cbeee17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc2c560f6db in start_thread (arg=0x7fc280bb7700) at pthread_create.c:463 #9 0x7fc2cb5d188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fc28247f700 (LWP 28131)): #0 0x7fc2c3f8991e in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc2c3f8a46b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc2c3f8a64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc2cc1259bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc2cc0caa1a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc2cbee923a in QThread::e
[karbon] [Bug 405546] New: Saving a document crashs the application
https://bugs.kde.org/show_bug.cgi?id=405546 Bug ID: 405546 Summary: Saving a document crashs the application Product: karbon Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ja...@gmx.net Reporter: overman.supermund...@gmail.com Target Milestone: --- Application: karbon (3.0.1) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.18.0-16-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: tried to save a document wither the document is blank (new) or had any drawing, it will always crash The crash can be reproduced every time. -- Backtrace: Application: Karbon (karbon), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4bf2040c80 (LWP 22552))] Thread 4 (Thread 0x7f4bba277700 (LWP 22556)): #0 0x7f4bea79d9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5601e0ef6e98) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f4bea79d9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5601e0ef6e48, cond=0x5601e0ef6e70) at pthread_cond_wait.c:502 #2 0x7f4bea79d9f3 in __pthread_cond_wait (cond=0x5601e0ef6e70, mutex=0x5601e0ef6e48) at pthread_cond_wait.c:655 #3 0x7f4bbfac323b in () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #4 0x7f4bbfac2f67 in () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #5 0x7f4bea7976db in start_thread (arg=0x7f4bba277700) at pthread_create.c:463 #6 0x7f4bf19cf88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f4bd3de3700 (LWP 22554)): #0 0x7f4bf19c2bf9 in __GI___poll (fds=0x7f4bcc012eb0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4be929e539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4be929e64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4bf042290b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f4bf03c79ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4bf01e622a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f4beade5d45 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f4bf01eb16d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f4bea7976db in start_thread (arg=0x7f4bd3de3700) at pthread_create.c:463 #9 0x7f4bf19cf88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f4bdae9f700 (LWP 22553)): #0 0x7f4bf19c2bf9 in __GI___poll (fds=0x7f4bdae9eca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4be294b747 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f4be294d36a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f4bdd7d52a9 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f4bf01eb16d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4bea7976db in start_thread (arg=0x7f4bdae9f700) at pthread_create.c:463 #6 0x7f4bf19cf88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f4bf2040c80 (LWP 22552)): [KCrash Handler] #6 0x7f4bee019cc8 in KoStore::pos() const () at /usr/lib/x86_64-linux-gnu/libkostore.so.15 #7 0x7f4bc29afbac in () at /usr/lib/x86_64-linux-gnu/libfreeimage.so.3 #8 0x7f4bc29a40ed in FreeImage_GetFileTypeFromHandle () at /usr/lib/x86_64-linux-gnu/libfreeimage.so.3 #9 0x7f4bc2c2d1de in FreeImageHandler::GetFIF(QIODevice*, QByteArray const&) () at /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libxfreeimage.so #10 0x7f4bc2c2e8ec in FreeimageQt5Plugin::capabilities(QIODevice*, QByteArray const&) const () at /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libxfreeimage.so #11 0x7f4beb404a4e in () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x7f4beb404d2c in () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x7f4beb4051b8 in QImageWriter::canWrite() const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #14 0x7f4beb405377 in QImageWriter::write(QImage const&) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #15 0x7f4beb3d8c08 in QImageData::doImageIO(QImage const*, QImageWriter*, int) const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #16 0x7f4beb3d8e19 in QImage::save(QIODevice*, char const*, int) const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #17 0x7f4bf1605d64 in KoDocument::saveOasisPreview(KoStore*, KoXmlWriter*) () at /usr/lib/x86_64-linux-gnu/libkomain.so.15 #18 0x7f4bf1606250 in KoDocument::saveNativeFormatODF(KoStore*, QByteArray const&) () at /usr/lib/x86_64-linux-
[karbon] [Bug 405559] New: Crash when trying to save a documents
https://bugs.kde.org/show_bug.cgi?id=405559 Bug ID: 405559 Summary: Crash when trying to save a documents Product: karbon Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ja...@gmx.net Reporter: overman.supermund...@gmail.com Target Milestone: --- Application: karbon (3.0.1) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.18.0-16-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: every time i try to save a document , even if it was brand new, it crashes The crash can be reproduced every time. -- Backtrace: Application: Karbon (karbon), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff5144acc80 (LWP 20644))] Thread 4 (Thread 0x7ff4dcbce700 (LWP 20651)): #0 0x7ff50cc0a9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x558014ef6ee8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7ff50cc0a9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x558014ef6e98, cond=0x558014ef6ec0) at pthread_cond_wait.c:502 #2 0x7ff50cc0a9f3 in __pthread_cond_wait (cond=0x558014ef6ec0, mutex=0x558014ef6e98) at pthread_cond_wait.c:655 #3 0x7ff4e22d923b in () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #4 0x7ff4e22d8f67 in () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #5 0x7ff50cc046db in start_thread (arg=0x7ff4dcbce700) at pthread_create.c:463 #6 0x7ff513e3c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7ff4f6349700 (LWP 20649)): #0 0x7ff513e2b0b4 in __GI___libc_read (fd=7, buf=0x7ff4f6348b60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7ff50b74fcd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff50b70b027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff50b70b4e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff50b70b64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff51288f90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff5128349ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7ff51265322a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff50d252d45 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7ff51265816d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7ff50cc046db in start_thread (arg=0x7ff4f6349700) at pthread_create.c:463 #11 0x7ff513e3c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7ff4fd30c700 (LWP 20648)): #0 0x7ff513e2fbf9 in __GI___poll (fds=0x7ff4fd30bca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff504db8747 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7ff504dba36a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7ff4ffc422a9 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7ff51265816d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff50cc046db in start_thread (arg=0x7ff4fd30c700) at pthread_create.c:463 #6 0x7ff513e3c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7ff5144acc80 (LWP 20644)): [KCrash Handler] #6 0x7ff510486cc8 in KoStore::pos() const () at /usr/lib/x86_64-linux-gnu/libkostore.so.15 #7 0x7ff4e51c5bac in () at /usr/lib/x86_64-linux-gnu/libfreeimage.so.3 #8 0x7ff4e51ba0ed in FreeImage_GetFileTypeFromHandle () at /usr/lib/x86_64-linux-gnu/libfreeimage.so.3 #9 0x7ff4e54431de in FreeImageHandler::GetFIF(QIODevice*, QByteArray const&) () at /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libxfreeimage.so #10 0x7ff4e54448ec in FreeimageQt5Plugin::capabilities(QIODevice*, QByteArray const&) const () at /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libxfreeimage.so #11 0x7ff50d871a4e in () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x7ff50d871d2c in () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x7ff50d8721b8 in QImageWriter::canWrite() const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #14 0x7ff50d872377 in QImageWriter::write(QImage const&) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #15 0x7ff50d845c08 in QImageData::doImageIO(QImage const*, QImageWriter*, int) const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #16 0x7ff50d845e19 in QImage::save(QIODevice*, char const*, int) const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #17 0x7ff513a72d64 in KoDocument::saveOasisPreview(KoStore*, KoXmlWriter*) () at /usr/lib/x86
[krita] [Bug 405730] New: crashed when saving a kirat document
https://bugs.kde.org/show_bug.cgi?id=405730 Bug ID: 405730 Summary: crashed when saving a kirat document Product: krita Version: 4.1.7 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: overman.supermund...@gmail.com Target Milestone: --- Application: krita (4.1.7) Qt Version: 5.9.5 Frameworks Version: 5.47.0 Operating System: Linux 4.18.0-16-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: Everytime i try to save a document in native krita file, it crashes, exporting the document to a different formats work though The crash can be reproduced every time. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd678cf2280 (LWP 3062))] Thread 8 (Thread 0x7fd6037fe700 (LWP 4212)): [KCrash Handler] #6 0x7fd670827b68 in KoStore::pos() const () at /usr/lib/x86_64-linux-gnu/libkritastore.so.17 #7 0x7fd63e7dabac in () at /usr/lib/x86_64-linux-gnu/libfreeimage.so.3 #8 0x7fd63e7cf0ed in FreeImage_GetFileTypeFromHandle () at /usr/lib/x86_64-linux-gnu/libfreeimage.so.3 #9 0x7fd63ea581de in FreeImageHandler::GetFIF(QIODevice*, QByteArray const&) () at /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libxfreeimage.so #10 0x7fd63ea598ec in FreeimageQt5Plugin::capabilities(QIODevice*, QByteArray const&) const () at /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libxfreeimage.so #11 0x7fd6753abaae in () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x7fd6753abd8c in () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x7fd6753ac218 in QImageWriter::canWrite() const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #14 0x7fd6753ac3d7 in QImageWriter::write(QImage const&) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #15 0x7fd67537fc68 in QImageData::doImageIO(QImage const*, QImageWriter*, int) const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #16 0x7fd67537fe79 in QImage::save(QIODevice*, char const*, int) const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #17 0x7fd6157ba36b in () at /usr/lib/x86_64-linux-gnu/kritaplugins/kritakraexport.so #18 0x7fd6157bac8b in () at /usr/lib/x86_64-linux-gnu/kritaplugins/kritakraexport.so #19 0x7fd6157bafd5 in () at /usr/lib/x86_64-linux-gnu/kritaplugins/kritakraexport.so #20 0x7fd6157b6d7f in () at /usr/lib/x86_64-linux-gnu/kritaplugins/kritakraexport.so #21 0x7fd677a2f3b9 in KisImportExportManager::doExportImpl(QString const&, QSharedPointer, KisPinnedSharedPtr) () at /usr/lib/x86_64-linux-gnu/libkritaui.so.17 #22 0x7fd677a2f698 in KisImportExportManager::doExport(QString const&, QSharedPointer, KisPinnedSharedPtr, bool) () at /usr/lib/x86_64-linux-gnu/libkritaui.so.17 #23 0x7fd677a31905 in () at /usr/lib/x86_64-linux-gnu/libkritaui.so.17 #24 0x7fd674b9b2b2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7fd674b9e17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7fd66e2c46db in start_thread (arg=0x7fd6037fe700) at pthread_create.c:463 #27 0x7fd67428188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fd61cd89700 (LWP 3090)): #0 0x7fd66cc85064 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fd66cc3f0d9 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd66cc3f5c0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd66cc3f64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fd674dd59bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd674d7aa1a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd674b9923a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd65aacf2a6 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fd674b9e17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fd66e2c46db in start_thread (arg=0x7fd61cd89700) at pthread_create.c:463 #10 0x7fd67428188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fd61e651700 (LWP 3088)): #0 0x7fd66cc85064 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fd66cc3ea88 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd66cc3f46b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd66cc3f64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fd674dd59bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0
[plasmashell] [Bug 383996] New: Cannot find file when renamed on the desktop
https://bugs.kde.org/show_bug.cgi?id=383996 Bug ID: 383996 Summary: Cannot find file when renamed on the desktop Product: plasmashell Version: 5.8.7 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: alexuk.chamb...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 With desktop in folder view, I copy a file from another folder to the desktop. I used fff.mp3 for the example. I open fff.mp3 in vlc to play it. I close vlc then rename fff.mp3 to abc.mp3. I double click abc.mp3 to open it and get the error: Unable to run the command specified. The file or folder /home/alex/Desktop//fff.mp3 does not exist. This has happened several times - KDE is trying to open the old filename, and not use the new filename. -- You are receiving this mail because: You are watching all bug changes.
[kxkb] [Bug 386442] New: Language layout toggle not works from Persian to English with "Super+Space" or "Alt+Space" keys
https://bugs.kde.org/show_bug.cgi?id=386442 Bug ID: 386442 Summary: Language layout toggle not works from Persian to English with "Super+Space" or "Alt+Space" keys Product: kxkb Version: 3.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: alirazmdide...@gmail.com Target Milestone: --- When I set "Win key + Space" for Language layout toggle, it changes English to Persian well, but not changes from Persian to English and layout is stock on Persian. And I had same issue with "Alt + Space" keys. So I guess this is because of Space key behavior in Persian. But I can't find its reason. And here is my kxkbrc file: [Layout] DisplayNames=, LayoutList=us,ir LayoutLoopCount=-1 Model=pc104 Options=grp:alt_shift_toggle,grp_led:scroll,grp:win_space_toggle ResetOldOptions=true ShowFlag=false ShowLabel=true ShowLayoutIndicator=true ShowSingle=false SwitchMode=Global Use=true And here is the "xmodmap -pke | grep -w 65" output: keycode 65 = space ISO_Next_Group space ISO_Next_Group nobreakspace U202F So why this issue is happened in Persian? Thanks in advance. -- You are receiving this mail because: You are watching all bug changes.
Re: My Inquiry is from Libya.
The President. Hello, My Inquiry is from Libya. Kindly advise if your company has the license or capability to execute a mutil million contract supply project for the Government of Libya. kindly furnish me your response. Thank you and treat very urgent. Looking forward to an early response. Ali
[kwin] [Bug 486149] Option to set FreeSync (VRR) mode has disappeared
https://bugs.kde.org/show_bug.cgi?id=486149 --- Comment #22 from Mufeed Ali --- After a good amount of time, I can confirm that making SDDM use Wayland did in fact fix the issue for me and I haven't faced it since my last comment here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481682] New: Some AppImages and Flatpaks dont have tray icons displayed anymore
https://bugs.kde.org/show_bug.cgi?id=481682 Bug ID: 481682 Summary: Some AppImages and Flatpaks dont have tray icons displayed anymore Classification: Plasma Product: plasmashell Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: kdebugs.undead@kumo.contact CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 166019 --> https://bugs.kde.org/attachment.cgi?id=166019&action=edit Current state of my steam flatpak and filen appimage (filen from AUR has the same issue as well) SUMMARY Some AppImages and Flatpaks that used to have proper tray icons with Plasma 5 dont have any tray icons with Plasma 6 anymore. This is especially important for sync apps like Filen. I want to know the state of sync before I perform some actions, but looking at the tray is now useless. This was working with Plasma 5 earlier. STEPS TO REPRODUCE 1. Run Filen AppImage or Steam flatpak. 2. Note the tray icon for the application ran. OBSERVED RESULT The tray icon is a generic file icon. EXPECTED RESULT The real icon set by the application should show up. SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS (available in About System) KDE Plasma Version: Plasma 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490079] New: Crash upon wake up from suspend
https://bugs.kde.org/show_bug.cgi?id=490079
Bug ID: 490079
Summary: Crash upon wake up from suspend
Classification: Plasma
Product: plasmashell
Version: 6.1.1
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: voodooatt...@hotmail.com
Target Milestone: 1.0
Application: plasmashell (6.1.1)
Qt Version: 6.7.2
Frameworks Version: 6.3.0
Operating System: Linux 6.9.7-200.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 40 (Workstation Edition)"
DrKonqi: 6.1.1 [CoredumpBackend]
-- Information about the crash:
I get this crash handler every time my system wakes from suspend. I have no
idea what's causing it beyond this.
The crash can be reproduced sometimes.
-- Backtrace:
Application: plasmashell (plasmashell), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[New LWP 2415]
[New LWP 2428]
[New LWP 2433]
[New LWP 3032]
[New LWP 2432]
[New LWP 3033]
[New LWP 3064]
[New LWP 3063]
[New LWP 3722]
[New LWP 3065]
[New LWP 3757]
[New LWP 3814]
[New LWP 3826]
[New LWP 3832]
[New LWP 9396]
[New LWP 11807]
[New LWP 3824]
[New LWP 11810]
[New LWP 3761]
[New LWP 3839]
[New LWP 11808]
[New LWP 3845]
[New LWP 9398]
[New LWP 3840]
[New LWP 11819]
[New LWP 11820]
[New LWP 3844]
[New LWP 9397]
[New LWP 9394]
[New LWP 11806]
[New LWP 11809]
[New LWP 11821]
Downloading separate debug info for /usr/lib64/libEGL_nvidia.so.0...
Downloading separate debug info for /usr/lib64/libnvidia-glsi.so.555.58.02...
Downloading separate debug info for
/usr/lib64/libnvidia-eglcore.so.555.58.02...
Downloading separate debug info for
/usr/lib64/libnvidia-gpucomp.so.555.58.02...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
[Current thread is 1 (Thread 0x7f40bc78f400 (LWP 2415))]
Cannot QML trace cores :(
Downloading source file
/usr/src/debug/plasma-workspace-6.1.1-1.fc40.x86_64/shell/panelview.cpp...
Downloading source file
/usr/src/debug/qt6-qtdeclarative-6.7.2-1.fc40.x86_64/src/quick/items/qquickwindow.cpp...
Downloading source file
/usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/gui/kernel/qwindow.cpp...
Downloading source file
/usr/src/debug/qt6-qtdeclarative-6.7.2-1.fc40.x86_64/src/quick/scenegraph/qsgrenderloop.cpp...
Downloading source file
/usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/gui/rhi/qrhigles2.cpp...
Downloading source file
/usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/gui/kernel/qopenglcontext.cpp...
Downloading source file
/usr/src/debug/qt6-qtwayland-6.7.2-1.fc40.x86_64/src/hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp...
Downloading source file
/usr/src/debug/qt6-qtwayland-6.7.2-1.fc40.x86_64/src/hardwareintegration/client/wayland-egl/qwaylandeglwindow.cpp...
[Current thread is 1 (Thread 0x7f40bc78f400 (LWP 2415))]
Thread 32 (Thread 0x7f40556006c0 (LWP 11821)):
#0 0x7f40c24a2be9 in __futex_abstimed_wait_common64 (private=0,
futex_word=0x7f4068008914, expected=0, op=137, abstime=0x7f40555ff9c0,
cancel=true) at futex-internal.c:57
#1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x7f4068008914,
expected=expected@entry=0, clockid=clockid@entry=1,
abstime=abstime@entry=0x7f40555ff9c0, private=private@entry=0,
cancel=cancel@entry=true) at futex-internal.c:87
#2 0x7f40c24a2c6f in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x7f4068008914, expected=expected@entry=0,
clockid=clockid@entry=1, abstime=abstime@entry=0x7f40555ff9c0,
private=private@entry=0) at futex-internal.c:139
#3 0x7f40c24a59a2 in __pthread_cond_wait_common (cond=0x7f40680088e8,
mutex=, clockid=1, abstime=0x7f40555ff9c0) at
pthread_cond_wait.c:503
#4 ___pthread_cond_timedwait64 (cond=0x7f40680088e8, mutex=,
abstime=0x7f40555ff9c0) at pthread_cond_wait.c:643
#5 0x7f40c2d60e7d in QWaitConditionPrivate::wait_relative
(this=0x7f40680088c0, deadline=...) at
/usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/corelib/thread/qwaitcondition_unix.cpp:92
#6 QWaitConditionPrivate::wait (this=0x7f40680088c0, deadline=...) at
/usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/corelib/thread/qwaitcondition_unix.cpp:100
#7 QWaitCondition::wait (this=this@entry=0x7f40680086c0,
mutex=mutex@entry=0x5615721aaa58, deadline=...) at
/usr/src/debug/qt6-qtbase-6.7.2-2.fc40.x86_64/src/corelib/thread/qwaitcondition_unix.cpp:180
#8 0x7f40c2d5dc45 in QThreadPoolThread::run (this=0x7f40680086b0) at
/usr/src/debug
[kscreenlocker] [Bug 490547] New: Unlock button shows up even after security key
https://bugs.kde.org/show_bug.cgi?id=490547 Bug ID: 490547 Summary: Unlock button shows up even after security key Classification: Plasma Product: kscreenlocker Version: 6.1.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kdebugs.undead@kumo.contact Target Milestone: --- SUMMARY There's a redundant Unlock button that comes up when using a U2F security key for unlocking the lock screen. STEPS TO REPRODUCE 1. Configure pam-u2f for unlocking. 2. Lock the screen with Win+L or by suspend. 3. Attempt to unlock. 4. Click any key once to show password field. (This also probably shouldn't be required in the case of security keys? I'm not sure.) 5. This reveals the password field and text above it saying "Please touch the device." 6. Tap on the security key. 7. Now an Unlock button shows up instead of taking me straight to my workspace. OBSERVED RESULT Up to 6.1.3, the Unlock button was not present and it would take me to the workspace. But since 6.1.3, the unlock button is present, adding one more step. EXPECTED RESULT No Unlock button, just straight to desktop or workspace. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.10-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 490547] Unlock button shows up when using security key to unlock
https://bugs.kde.org/show_bug.cgi?id=490547 Mufeed Ali changed: What|Removed |Added Summary|Unlock button shows up even |Unlock button shows up when |after security key |using security key to ||unlock -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486149] New: Option to set FreeSync (VRR) mode has disappeared
https://bugs.kde.org/show_bug.cgi?id=486149 Bug ID: 486149 Summary: Option to set FreeSync (VRR) mode has disappeared Classification: Plasma Product: kwin Version: 6.0.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kdebugs.undead@kumo.contact Target Milestone: --- Created attachment 168916 --> https://bugs.kde.org/attachment.cgi?id=168916&action=edit My display configuration view right now SUMMARY The option in 'Display Configuration' to set Freesync to "Automatic", "Always" and "Off" have completely disappeared for me. I don't know why or since when, but it was definitely present until at least after 6.0.1. STEPS TO REPRODUCE 1. Open System Settings 2. Navigate to Display Configuration OBSERVED RESULT Note that there is no option to control VRR. EXPECTED RESULT Option in 'Display Configuration' to set Freesync to "Automatic", "Always" and "Off" SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux latest rolling KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION I actually dont know if VRR itself is working currently. How would I reliably test that? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486149] Option to set FreeSync (VRR) mode has disappeared
https://bugs.kde.org/show_bug.cgi?id=486149 --- Comment #2 from Mufeed Ali --- Created attachment 168932 --> https://bugs.kde.org/attachment.cgi?id=168932&action=edit drm_info output I've added the drm_info output here -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486149] Option to set FreeSync (VRR) mode has disappeared
https://bugs.kde.org/show_bug.cgi?id=486149 --- Comment #4 from Mufeed Ali --- Created attachment 168939 --> https://bugs.kde.org/attachment.cgi?id=168939&action=edit `kscreen -o` output Looks like you're right. VRR is showing up as "Automatic" here. I also feel like it's working considering that it looked fine when I played Firewatch but that wasn't a lot of time and I don't really know what to look for when it comes to evidence on the contrary. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486149] Option to set FreeSync (VRR) mode has disappeared
https://bugs.kde.org/show_bug.cgi?id=486149 --- Comment #5 from Mufeed Ali --- Okay, sorry for the false alert but the `kscreen -o` output was on this boot and I hadn't checked the system settings app yet. The Adaptive Sync option is back... I have no idea what's going on. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486149] Option to set FreeSync (VRR) mode has disappeared
https://bugs.kde.org/show_bug.cgi?id=486149 --- Comment #6 from Mufeed Ali --- Created attachment 168945 --> https://bugs.kde.org/attachment.cgi?id=168945&action=edit Updated drm_info Rebooted from windows just now and it's not working again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486149] Option to set FreeSync (VRR) mode has disappeared
https://bugs.kde.org/show_bug.cgi?id=486149 Mufeed Ali changed: What|Removed |Added Attachment #168932|0 |1 is obsolete|| Attachment #168939|0 |1 is obsolete|| --- Comment #7 from Mufeed Ali --- Created attachment 168946 --> https://bugs.kde.org/attachment.cgi?id=168946&action=edit updated kscreen -o output Updated kscreen output and drm_info output as well -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486149] Option to set FreeSync (VRR) mode has disappeared
https://bugs.kde.org/show_bug.cgi?id=486149 --- Comment #8 from Mufeed Ali --- Is drm_info a dependency for this feature? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486149] Option to set FreeSync (VRR) mode has disappeared
https://bugs.kde.org/show_bug.cgi?id=486149 --- Comment #9 from Mufeed Ali --- Created attachment 168948 --> https://bugs.kde.org/attachment.cgi?id=168948&action=edit drm_info output when option is available -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486149] Option to set FreeSync (VRR) mode has disappeared
https://bugs.kde.org/show_bug.cgi?id=486149 --- Comment #10 from Mufeed Ali --- Created attachment 168949 --> https://bugs.kde.org/attachment.cgi?id=168949&action=edit kscreen output when working -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486149] Option to set FreeSync (VRR) mode has disappeared
https://bugs.kde.org/show_bug.cgi?id=486149 --- Comment #11 from Mufeed Ali --- I've added output for when it works and when it doesnt work. I've tried rebooting multiple times now. It seems to work on some boots but not on others. Is this a driver bug? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486149] Option to set FreeSync (VRR) mode has disappeared
https://bugs.kde.org/show_bug.cgi?id=486149 --- Comment #13 from Mufeed Ali --- But the driver probably shouldn't be reporting a lack of VRR support in the first place right? Should I try to report that to mesa? Also, if I set it to "Automatic" on a boot where the option appears, would that still apply to a boot where the option isn't present (considering that the driver does in fact still support it)? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491654] New: Plasmashell crashes on upgrading egl-wayland to 3:2.1.1.15-1
https://bugs.kde.org/show_bug.cgi?id=491654 Bug ID: 491654 Summary: Plasmashell crashes on upgrading egl-wayland to 3:2.1.1.15-1 Classification: Plasma Product: plasmashell Version: 6.1.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: salee...@gmail.com Target Milestone: 1.0 *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY plasmashell crashes every time after updating egl-wayland to 3:2.1.1.15-1 from 3:2.1.13.1-1. It works well on 3:2.1.1.13.1-1 and does not crash STEPS TO REPRODUCE 1. run yay -Syu on endeavour os 2. when egl-wayland is upgraded and system is restarted 3. it boot in plasma and crashes on logon everytime. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: linux-6.10.4-arch2-1/6.1.4 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION- Message: Process 5319 (plasmashell) of user 1000 dumped core. Stack trace of thread 5482: #0 0x70da2a0a53f4 n/a (libc.so.6 + 0x963f4) #1 0x70da2a04c120 raise (libc.so.6 + 0x3d120) #2 0x70da2cf87643 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x6643) #3 0x70da2a04c1d0 n/a (libc.so.6 + 0x3d1d0) #4 0x70da2a0a53f4 n/a (libc.so.6 + 0x963f4) #5 0x70da2a04c120 raise (libc.so.6 + 0x3d120) #6 0x70da2a0334c3 abort (libc.so.6 + 0x244c3) #7 0x70da2a0333df n/a (libc.so.6 + 0x243df) #8 0x70da2a044177 __assert_fail (libc.so.6 + 0x35177) #9 0x70da235f4774 n/a (libnvidia-egl-wayland.so.1 + 0x7774) #10 0x70da235f7761 n/a (libnvidia-egl-wayland.so.1 + 0xa761) #11 0x70da218a945e n/a (libEGL_nvidia.so.0 + 0xa945e) #12 0x70da21848e64 n/a (libEGL_nvidia.so.0 + 0x48e64) #13 0x70d9a1dac6f5 n/a (libQt6WebEngineCore.so.6 + 0x1ac6f5) #14 0x70d9a1dac81f n/a (libQt6WebEngineCore.so.6 + 0x1ac81f) #15 0x70d9a28aa9f5 n/a (libQt6WebEngineCore.so.6 + 0xcaa9f5) #16 0x70d9a7ed03c3 n/a (libQt6WebEngineCore.so.6 + 0x62d03c3) #17 0x70d9a8194023 n/a (libQt6WebEngineCore.so.6 + 0x6594023) #18 0x70d9a602d055 n/a (libQt6WebEngineCore.so.6 + 0x442d055) #19 0x70d9a604031a n/a (libQt6WebEngineCore.so.6 + 0x444031a) #20 0x70da2a0a339d n/a (libc.so.6 + 0x9439d) #21 0x70da2a12849c n/a (libc.so.6 + 0x11949c) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491654] Plasmashell crashes on upgrading egl-wayland to 3:2.1.1.15-1
https://bugs.kde.org/show_bug.cgi?id=491654 saleem ali changed: What|Removed |Added Version Fixed In||egl-wayland-4:1.1.13.1-1-x8 ||6 --- Comment #2 from saleem ali --- This seem to be fixed in version egl-wayland-4:1.1.13.1-1-x86 as I am not getting plasmashell crashes on upgrading to this version today. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477977] Contents of Sensors Details section in the settings of System Monitor widgets disappear after a few seconds
https://bugs.kde.org/show_bug.cgi?id=477977 saleem ali changed: What|Removed |Added CC||salee...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 474175] New: Kamoso crashes on startup.
https://bugs.kde.org/show_bug.cgi?id=474175 Bug ID: 474175 Summary: Kamoso crashes on startup. Classification: Applications Product: kamoso Version: 23.04.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: sabir.aliyev.it...@gmail.com Target Milestone: --- Application: kamoso (23.04.3) Qt Version: 5.15.10 Frameworks Version: 5.109.0 Operating System: Linux 6.4.12-200.fc38.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 38 (KDE Plasma) DrKonqi: 5.27.7 [KCrashBackend] -- Information about the crash: Kamoso crashes on startup. OS: Fedora Linux 38 KDE Plasma. Camera: A4tech FHD 1080P PC camera. PC: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 39 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 16 On-line CPU(s) list:0-15 Vendor ID: GenuineIntel Model name: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz CPU family: 6 Model: 165 Thread(s) per core: 2 Core(s) per socket: 8 Socket(s): 1 Stepping: 5 CPU(s) scaling MHz: 89% CPU max MHz:4800. CPU min MHz:800. BogoMIPS: 5799.77 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp vnmi pku ospke md_clear flush_l1d arch_capabilities Virtualization: VT-x L1d cache: 256 KiB (8 instances) L1i cache: 256 KiB (8 instances) L2 cache: 2 MiB (8 instances) L3 cache: 16 MiB (1 instance) NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerability Gather data sampling: Mitigation; Microcode Vulnerability Itlb multihit:KVM: Mitigation: Split huge pages Vulnerability L1tf: Not affected Vulnerability Mds: Not affected Vulnerability Meltdown: Not affected Vulnerability Mmio stale data: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Retbleed: Mitigation; Enhanced IBRS Vulnerability Spec rstack overflow: Not affected Vulnerability Spec store bypass:Mitigation; Speculative Store Bypass disabled via prctl Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2: Mitigation; Enhanced / Automatic IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Vulnerability Srbds:Mitigation; Microcode Vulnerability Tsx async abort: Not affected The crash can be reproduced every time. -- Backtrace: Application: Kamoso (kamoso), signal: Segmentation fault [KCrash Handler] #4 0x7f3f4068b331 in g_type_check_instance_is_fundamentally_a () from /lib64/libgobject-2.0.so.0 #5 0x7f3f40675d10 in g_object_notify () from /lib64/libgobject-2.0.so.0 #6 0x7f3f406644ea in g_closure_invoke () from /lib64/libgobject-2.0.so.0 #7 0x7f3f40692e16 in signal_emit_unlocked_R.isra.0 () from /lib64/libgobject-2.0.so.0 #8 0x7f3f40683cbd in g_signal_emit_valist () from /lib64/libgobject-2.0.so.0 #9 0x7f3f40683f33 in g_signal_emit () from /lib64/libgobject-2.0.so.0 #10 0x7f3f4066f6b4 in g_object_dispatch_properties_changed.lto_priv () from /lib64/libgobject-2.0.so.0 #11 0x7f3f406f28f9 in gst_object_dispatch_properties_changed () from /lib64/libgstreamer-1.0.so.0 #12 0x7f3f40664ab0 in g_object_notify_queue_thaw.lto_priv () from /lib64/libgobject-2.0.so.0 #13 0x7f3f40677ad6 in g_object_set_valist () from /lib64/libgobject-2.0.so.0 #14 0x7f3f40677f1d in g_object_set () from /lib64/libgobject-2.0.so.0 #15 0x7f3effe72c11 in gst_camera_bin_change_state () from /lib64/gstreamer-1.0/libgstcamerabin.so #16 0x7f3f40722a14 in gst_element_c
[kwalletmanager] [Bug 206171] The name org.kde.kwalletd was not provided by any service files
https://bugs.kde.org/show_bug.cgi?id=206171 Md.Mohosin Ali changed: What|Removed |Added CC||mdmohosinalimohosin82@gmail ||.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 474394] New: The name org.kde.kdeconnect was not provided by any .service fil
https://bugs.kde.org/show_bug.cgi?id=474394 Bug ID: 474394 Summary: The name org.kde.kdeconnect was not provided by any .service fil Classification: Applications Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: mdmohosinalimohosi...@gmail.com Target Milestone: --- The name org.kde.kdeconnect was not provided by any .service fil -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 474394] The name org.kde.kdeconnect was not provided by any .service fil
https://bugs.kde.org/show_bug.cgi?id=474394 Md.Mohosin Ali changed: What|Removed |Added CC||andrew.g.r.hol...@gmail.com Component|plasmoid|common --- Comment #1 from Md.Mohosin Ali --- The name org.kde.kdeconnect was not provided by any .service fil -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479712] Plasma 6's SNI implementation doesn't respect the IconThemePath property
https://bugs.kde.org/show_bug.cgi?id=479712 Mufeed Ali changed: What|Removed |Added CC|kdebugs.undead@kumo.contact | -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 458080] Slideshow Remote Pointer makes screen go black
https://bugs.kde.org/show_bug.cgi?id=458080 Ali Rasti changed: What|Removed |Added CC||ali.rasti.1...@gmail.com --- Comment #3 from Ali Rasti --- Same for me, I'm also experiencing this exact problem on Fedora 39 when using the remote pointer, it's as if the pointer's window should've been transparent instead of black. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486149] Option to set FreeSync (VRR) mode has disappeared
https://bugs.kde.org/show_bug.cgi?id=486149 --- Comment #17 from Mufeed Ali --- > Would you be willing to patch KWin to get that information? Sorry for the delay in getting back to you, but i can do that -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486149] Option to set FreeSync (VRR) mode has disappeared
https://bugs.kde.org/show_bug.cgi?id=486149 --- Comment #18 from Mufeed Ali --- I also just wanted to confirm this. It does switch from "vrr_capable = 0" to "vrr_capable = 1" at some point post-boot. This doesn't seem to be the case with my Fedora Silverblue setup though, so might be some issue with my arch setup -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486149] Option to set FreeSync (VRR) mode has disappeared
https://bugs.kde.org/show_bug.cgi?id=486149 --- Comment #19 from Mufeed Ali --- My issue is related to power management somehow. Switching the Power Profile to anything (even Power Save) consistently gets the state to "vrr_capable: 1" immediately. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486149] Option to set FreeSync (VRR) mode has disappeared
https://bugs.kde.org/show_bug.cgi?id=486149 --- Comment #20 from Mufeed Ali --- I am so sorry... What I said above isn't true... Turns out it's me plugging in power into the laptop that triggered the vrr_capable to 1. But booting with power plugged in doesn't set it to 1. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486149] Option to set FreeSync (VRR) mode has disappeared
https://bugs.kde.org/show_bug.cgi?id=486149 --- Comment #21 from Mufeed Ali --- Okay, the real fix was a lot simpler and the reason might also be simple. I set SDDM to use Wayland (https://wiki.archlinux.org/title/SDDM#Wayland) and synced the settings from Plasma to SDDM once. This seems to have completely fixed the issue. I think the reason it wasn't working could be (completely a guess) that SDDM used X11 and I don't have FreeSync configured on X11. I'm not sure. But it works now! SDDM on Wayland is pretty nice btw. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449302] New: ConfigureNotify event not sent under X11 when moving the window
https://bugs.kde.org/show_bug.cgi?id=449302 Bug ID: 449302 Summary: ConfigureNotify event not sent under X11 when moving the window Product: kwin Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: alidev2...@yahoo.fr Target Milestone: --- SUMMARY Only the last ConfigureNotify event is sent when the window is moved by the user if composition is ON. This is not the case for the other WMs or if composition is OFF. Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449302] ConfigureNotify event not sent under X11 when moving the window
https://bugs.kde.org/show_bug.cgi?id=449302 --- Comment #2 from Kettab Ali --- Well, short answer: I need to keep two windows in sync. that is, when one of them (i.e. the main window, appWindow) moves, the other window (overlayWindow), which is always on top of the appWindow should move as well (as if it were part of the appWindow). This works well under Windows. by processing WM_ENTERSIZEMOVE message. Under Linux, all the desktop flavors I tested on (GNOME, Xfce, Cinnamon, MATE, Fluxbox,..) just work as expected too. I wonder if Kwin could just send this event (ConfigureNotify) at least when the window starts moving (and this would be acceptable for me) because the last event is always sent and thus, overlayWindow can be just hidden/shown as needed. Regards. -- You are receiving this mail because: You are watching all bug changes.
