[dolphin] [Bug 486896] Browsing SMB causes kioslave5 to throw errors in libnvidia-tls.550.78
https://bugs.kde.org/show_bug.cgi?id=486896 Hugh Phoenix-Hulme changed: What|Removed |Added CC||h...@webnet.org.uk Platform|Other |Ubuntu -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486896] New: Browsing SMB causes kioslave5 to throw errors in libnvidia-tls.550.78
https://bugs.kde.org/show_bug.cgi?id=486896 Bug ID: 486896 Summary: Browsing SMB causes kioslave5 to throw errors in libnvidia-tls.550.78 Classification: Applications Product: dolphin Version: 23.08.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: h...@webnet.org.uk CC: kfm-de...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Install nvidia driver 550.78 2. Open Dolphin 3. Browse to SMB OBSERVED RESULT The Dolphin tab displays the message "The process for the smb://a.b.c.d protocol died unexpectedly." Crash report appears in systray: "kioslave5 Closed Unexpectedly." KDE Crash Handler reports this Developer Information: Application: kioslave5 (kioslave5), signal: Segmentation fault [KCrash Handler] #4 0x7a932e25c618 in ?? () from /lib/x86_64-linux-gnu/libnvidia-tls.so.550.78 #5 0x732e36312d465455 in ?? () #6 0x7a9331e3006f in __gconv_transform_internal_ascii (step=0xec81481574d3d1, data=0x48f0e08348ca2918, inptrp=0x8948098be8e7, inend=0x7ffc9caa2290 "@#\252\234\374\177", outbufstart=0x24b1e8e78948, irreversible=0x89482723e8c7, do_flush=1401505809, consume_incomplete=726164680) at ../iconv/skeleton.c:547 Backtrace stopped: previous frame inner to this frame (corrupt stack?) [Inferior 1 (process 1552475) detached] EXPECTED RESULT None of the above. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 ADDITIONAL INFORMATION libnvidia-tls.so is for Thread Local Storage. Renaming it to prevent it being loaded solves the problem, but why is it being loaded? This seems like a pretty terrible scenario. Some external component is causing undesirable behaviour, but when that component is unavailable, everything works. So literally anything has the potential to break kioslave5. Should kioslave5 be ignoring exceptions while trying to load libraries at this point? Is there a way to blacklist libraries so kioslave5 doesn't try to load them? (I doubt I can get away with removing the thread local storage lib systemwide - I could try it, but I don't expect it'll be pretty.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483448] "undocmented error" reported by plasmashell when Activity Manager ecounters local image as wallpaper on activity desktop: "SwitcherBackend: FAILED to get the thumbnail"
https://bugs.kde.org/show_bug.cgi?id=483448 Hugh Kernohan changed: What|Removed |Added CC||hugh.kerno...@gmail.com Platform|Other |Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483448] New: "undocmented error" reported by plasmashell when Activity Manager ecounters local image as wallpaper on activity desktop: "SwitcherBackend: FAILED to get the thumbnail
https://bugs.kde.org/show_bug.cgi?id=483448
Bug ID: 483448
Summary: "undocmented error" reported by plasmashell when
Activity Manager ecounters local image as wallpaper on
activity desktop: "SwitcherBackend: FAILED to get the
thumbnail"
Classification: Plasma
Product: plasmashell
Version: 6.0.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: Activity Switcher
Assignee: plasma-b...@kde.org
Reporter: hugh.kerno...@gmail.com
CC: ivan.cu...@kde.org
Target Milestone: 1.0
SUMMARY
When a local image is the wallpaper on activity desktop, using Activity Manager
produces "undocmented error" and "SwitcherBackend: FAILED to get the
thumbnail"
STEPS TO REPRODUCE
1. Create new activity
2. Configure Desktop and Wallpaper
3. Add Image: JPEG from local harddisk
4. Save and exit
5. Open Activity Manager from main Panel
OBSERVED RESULT
New image is displayed in Activity Manager, but journalctl reports:
Mar 13 14:38:17 plasmashell[1397]: SwitcherBackend: FAILED to get the thumbnail
"Unknown error code 0 Please send a full bug report at https://bugs.kde.org.;
QList("Undocumented Error", "Undocumented ErrorUnknown
error code 0\n\nPlease send a full bug report at
https://bugs.kde.org.", "Details of the
request:URL: (unknown)Date and time: Wednesday, 13
March 2024 14:38:17 UTCAdditional information: ")
EXPECTED RESULT
No error is reported
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 6 × Intel® Core™ i5-8600 CPU @ 3.10GHz
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 6650 XT
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #51 from Hugh Phoenix-Hulme --- Killing one is working for me, but it's not a great solution. To minimise hassle one could write a script to kill the first process if there are multiple and run it as a cron job every second, but that's obviously not ideal. I'm also seeing this on Ubuntu, not Arch. But generally only after resuming, not just from locking, and not consistently. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Hugh Phoenix-Hulme changed: What|Removed |Added CC||h...@webnet.org.uk --- Comment #49 from Hugh Phoenix-Hulme --- I'm getting this now, and I do see two instances of kscreenlocker_greet. I also see plasmashell and dolphin using high CPU at the same time. Next time it occurs I'll kill one and see if that solves for the other. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 322096] K3b misreports I/O error; should give much better diagnostic
https://bugs.kde.org/show_bug.cgi?id=322096 --- Comment #4 from D. Hugh Redelmeier --- This problem only occurred on an old slow notebook. A decade later I don't have it or any similar computer. So I won't try to duplicate the problem. Since nobody else has reported it, I guess it wasn't important. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424307] Kwin segfault on initial log-in
https://bugs.kde.org/show_bug.cgi?id=424307 Hugh Kernohan changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459441] New: KDE windows etc are still visible after resume, and before the screen is locked
https://bugs.kde.org/show_bug.cgi?id=459441 Bug ID: 459441 Summary: KDE windows etc are still visible after resume, and before the screen is locked Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: h...@webnet.org.uk Target Milestone: --- Not sure where this fits. SUMMARY When I close my laptop lid, the machine suspends. When I open it, all my windows are visible with potentially sensitive information for a second or so before the screen lock kicks in. STEPS TO REPRODUCE 1. Turn on the computer 2. Do something 3. Close the lid 4. Wait for the machine to suspend 5. Open the lid 6. Observe sensitive data OBSERVED RESULT The whole screen is visible for > 500ms before the lock screen kicks in. Someone not privileged to see that information could view some of that information, or if they've observed the effect a few times they could be prepared with a mobile phone or camera. EXPECTED RESULT The screen should be cleared (or overlaid with a black window) before the machine suspends, so that it's still clear inbetween resume and screen lock. I don't know if it's possible but it would be a good addition. This is not a new behaviour, so it's not practical to list all the versions of KDE with which this behaviour could be observed. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 456107] New: Main toolbar keyboard shortcut throwing an error.
https://bugs.kde.org/show_bug.cgi?id=456107 Bug ID: 456107 Summary: Main toolbar keyboard shortcut throwing an error. Product: okular Version: 22.04.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: hugh.ga...@tutamail.com Target Milestone: --- SUMMARY Setup keyboard shortcuts for visibility of okular sidebar and the okular main toolbar within the okular settings. Both are unique and don't clash with any other keyboard shortcuts. Don't show sidebar and main toolbar on application startup. Show main toolbar using shortcut, which works fine, until the sidebar shortcut is used. Now the main toolbar keyboard shortcut stops working. The following error is shown each time it is pressed: kf.xmlgui: Shortcut for action "mainToolBar" "Show Toolbar" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead As soon as the side bar shortcut key is hit the main toolbar shortcut key stops working. Only fix is an application restart. STEPS TO REPRODUCE 1. Set main toolbar keyboard shortcut to "t". 2. Set sidebar keyboard shortcut to "s". 3. Hide both on application start. 4. Open a document in okular, I'm using a pdf. 5. Hit "t" to show the main toolbar. 6. Hit "s" to show the sidebar. 7. Hit "t" to hide the main toolbar. OBSERVED RESULT Main toolbar keyboard shortcuts stops working. The following error message is output: kf.xmlgui: Shortcut for action "mainToolBar" "Show Toolbar" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead Open Okular keyboard shortcut settings and the main toolbar shortcut is not set. Add it back, use sidebar shortcut, and it is missing again. Restarting the application and it is back, until sidebar shortcut is used, the gone again. Strange. EXPECTED RESULT The main toolbar keyboard shortcut continue to work after the sidebar keyboard shortcuts has been used. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95 Qt Version: 5.15.5 ADDITIONAL INFORMATION Okular package version: 22.04.2-3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455757] Please allow WallpaperFader to be disabled for Breeze theme in both SDDM and Lockscreen
https://bugs.kde.org/show_bug.cgi?id=455757 --- Comment #4 from hugh --- Happy to test for FOSS projects, report issues, follow up afterwards. As I said, I don't develop. By choice. I hate coding. Tried it. Detest it. Life is too short to do stuff you hate. Not happening. Ever. Trawling through the breeze code to find a solution to this felt like Andy Dufresne's 500 yard crawl through raw effluent in Shawshank. Unpleasant. But I found a solution anyway. A very simple solution. Trivial actually. WallpaperFader.visible = false In two places. That is all. Been using it since 5.24.3 and works. Perfectly. Even that is not enough. Write the code yourself. Your irrational inflexibility to implement this simple disable mechanism for a UI element that is invasive, ugly and ultimately pointless is very weird. My system works fine now, be nice if others had the same option. Guess not though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455795] Turning off the screen/dpms before suspending causes the screen to stay black after resuming.
https://bugs.kde.org/show_bug.cgi?id=455795 Hugh Kernohan changed: What|Removed |Added CC||hugh.kerno...@gmail.com --- Comment #2 from Hugh Kernohan --- My desktop exhibits the same behaviour as bug 445814. After using suspend-to-RAM, the computer awakes but the two screens remains blank and no keys produce any response. If I access remotely via SSH I can see that kwin_wayland is running variously between 93.5% and 100% CPU. Calling kwin_wayland --replace from the remote has no effect but using kill -KILL does. A new instance of kwin_wayland then starts automatically, the screens return to their normal display and the keyboard is live again. Nothing unusual or obvious is recorded in in the journalctl. I'm using the nvidia-suspend and nvidia-resume mechanism to avoid graphics corruption. Operating System: Arch Linux KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.18.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-8600 CPU @ 3.10GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA driver 515.48.07 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451590] Stutter when opening WindowHeap-based effects
https://bugs.kde.org/show_bug.cgi?id=451590 --- Comment #11 from hugh --- Yeah, this is definitely not fixed in 5.25.1. The destkop effects bugs were fixed, the choppy transition into and out of it is not. Same for the other Window Management destop effects redeveloped for 5.25, they all experience this transition issue, desktop effect is the choppiest though. X11 user. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455757] Please allow WallpaperFader to be disabled for Breeze theme in both SDDM and Lockscreen
https://bugs.kde.org/show_bug.cgi?id=455757 --- Comment #2 from hugh --- I am not a developer. One property setting change in two locations and an additional UI checkbox is too much? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455767] Transition into and out of new Window Management desktop effects is jagged
https://bugs.kde.org/show_bug.cgi?id=455767 hugh changed: What|Removed |Added Component|effects-window-management |effects-desktop-grid -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455767] New: Transition into and out of new Window Management desktop effects is jagged
https://bugs.kde.org/show_bug.cgi?id=455767 Bug ID: 455767 Summary: Transition into and out of new Window Management desktop effects is jagged Product: kwin Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: regression Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: hugh.ga...@tutamail.com Target Milestone: --- SUMMARY The Desktop Grid and Present Windows desktop effects are kwin tools I use a lot. After years of use they are ingrained into my workflow. The transition into and out of these Window Management desktop effects prior to 5.25 was smooth as butter. It looked like some sort of zoom animation was used to transition to and from the active desktop to each specfic desktop effect. Both the speed and smoothness of this transition animation was great. It was easy on the eye. With the redevelopment of these Window Management desktop effects in 5.25 the transitions into and out of them are now rough, jagged and anything but smooth. Overview desktop effect has this issue also. They are jagged and rough enough to give me a headache after about 45 minutes of use. Desktop grid seems to be the worst of the group. It is more jagged than the others. I use between 4 and 8 virtual desktops usually and have anywhere from 4-12 applications open at any one time, on average. A restored 5.24.5 system I tested with 2-8 virtual desktops and 16 open applications was smooth transitioning in and out. My current 5.25.1 system I tested with 2-4 virtual desktops and 4 open applications was very jagged transitioning in and out. Reducing the number of deskops and applications didn't improve smoothness. Hopefully the cause of this regression can be found and a fix developed. Headaches kinda suck. STEPS TO REPRODUCE >From an active desktop open a Window Management desktop effect (desktop grid, present window or overview). OBSERVED RESULT Transition animation into the desktop effect is jagged, rough, jerky and not smooth. Particularly the desktop grid. EXPECTED RESULT Transition animation into the desktop effect should be smooth, like it was in 5.24.5. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95 Qt Version: 5.15.5 ADDITIONAL INFORMATION This is running on an AMD system with a RX590 gpu, FWIW. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 455757] New: Please allow WallpaperFader to be disabled for Breeze theme in both SDDM and Lockscreen.
https://bugs.kde.org/show_bug.cgi?id=455757
Bug ID: 455757
Summary: Please allow WallpaperFader to be disabled for Breeze
theme in both SDDM and Lockscreen.
Product: Breeze
Version: 5.25.1
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: hugh.ga...@tutamail.com
CC: uhh...@gmail.com
Target Milestone: ---
SUMMARY
Currently the breeze theme provides no way to disable the WallpaperFader (ie
the blurry fog) when entering passwords in both the SDDM theme and on the
LockScreen.
Not everyone wants this blurry fog and an option to disable it seems
reasonable, especially considering how easy it is to do.
All that is needed is for WallpaperFader.visible to be set to false in two
locations, one in the SDDM breeze theme and the breeze theme lockscreen.
SDDM:
/usr/share/sddm/themes/breeze/Main.qml ... line 110
When enabled:
WallpaperFader {
visible: config.type === "image"
When disabled:
WallpaperFader {
//visible: config.type === "image"
visible: false
Breeze Lockscreen:
/usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml
... line 219
When enabled:
WallpaperFader {
visible: true
When disabled:
WallpaperFader {
visible: false
A Breeze theme UI change and Breeze SDDM theme UI change would also be required
to toggle and persist this setting.
Presumably a logout and login after setting is changed may be required to
effect the new setting.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.25.1
KDE Frameworks Version: 5.95
Qt Version: 5.15.5
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[yakuake] [Bug 455443] Make yakuake vertical splits even, like implemented in konsole
https://bugs.kde.org/show_bug.cgi?id=455443 --- Comment #3 from hugh --- Duplicate of https://bugs.kde.org/show_bug.cgi?id=455442 . Please remove. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455292] 5.25 Desktop Grid - Can't select a virtual desktop using the keyboard anymore
https://bugs.kde.org/show_bug.cgi?id=455292 --- Comment #7 from hugh --- Thx. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 455688] New: Allow keyboard shortcut navigation for Dolphin Places Section Entries.
https://bugs.kde.org/show_bug.cgi?id=455688 Bug ID: 455688 Summary: Allow keyboard shortcut navigation for Dolphin Places Section Entries. Product: dolphin Version: 22.04.2 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: hugh.ga...@tutamail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY For entries in the Dolphin Places section allow keyboard shortcuts for easier keyboard centric navigation. Currently no provision for this exists. STEPS TO REPRODUCE 1. Add or Edit an entry in Dolphin Places section 2. In addition to label, location and icon also allow a keyboard shortcut to be entered. 3. Allow for navigate to this location using the keyboard shortcut. OBSERVED RESULT Functionality doesn't currently exist. EXPECTED RESULT Keyboard navigation to Places locations without needing a mouse. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.25 KDE Frameworks Version: 5.95 Qt Version: 5.15.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455292] 5.25 Desktop Grid - Can't select a virtual desktop using the keyboard anymore
https://bugs.kde.org/show_bug.cgi?id=455292 --- Comment #3 from hugh --- This is not making it into 5.25.1? As a keyboard centric user I hope this gets fixed soon. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 455443] Make yakuake vertical splits even, like implemented in konsole
https://bugs.kde.org/show_bug.cgi?id=455443 --- Comment #2 from hugh --- Created attachment 149831 --> https://bugs.kde.org/attachment.cgi?id=149831=edit konsole split -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 455443] Make yakuake vertical splits even, like implemented in konsole
https://bugs.kde.org/show_bug.cgi?id=455443 --- Comment #1 from hugh --- Created attachment 149830 --> https://bugs.kde.org/attachment.cgi?id=149830=edit yakuake split -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 455443] New: Make yakuake vertical splits even, like implemented in konsole
https://bugs.kde.org/show_bug.cgi?id=455443 Bug ID: 455443 Summary: Make yakuake vertical splits even, like implemented in konsole Product: yakuake Version: 22.04.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: hugh.ga...@tutamail.com Target Milestone: --- SUMMARY Vertical splits in in yakuake are uneven. The bottom split is continually halved, making them unusable. A similar issue was fixed in konsole. https://bugs.kde.org/447074 Please migrate a similar solution to yakuake to make vertical splits even and much more usable. STEPS TO REPRODUCE 1. Open yakuake 2. Vertical split 3-5 times. OBSERVED RESULT Splits become increasingly smaller and uneven. EXPECTED RESULT Splits should be even, like implemented in konsole, making this function much more usable. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.25 KDE Frameworks Version: 5.95 Qt Version: 5.15.4 ADDITIONAL INFORMATION yakuake package version 22.04.2-1. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 455442] Make yakuake vertical splits even, like implemented in konsole
https://bugs.kde.org/show_bug.cgi?id=455442 --- Comment #1 from hugh --- Created attachment 149829 --> https://bugs.kde.org/attachment.cgi?id=149829=edit konsole split for comparison -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 455442] New: Make yakuake vertical splits even, like implemented in konsole
https://bugs.kde.org/show_bug.cgi?id=455442 Bug ID: 455442 Summary: Make yakuake vertical splits even, like implemented in konsole Product: yakuake Version: 22.04.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: hugh.ga...@tutamail.com Target Milestone: --- Created attachment 149828 --> https://bugs.kde.org/attachment.cgi?id=149828=edit yakuake split SUMMARY Vertical splits in in yakuake are uneven. The bottom split is continually halved, making them unusable. A similar issue was fixed in konsole. https://bugs.kde.org/447074 Please migrate a similar solution to yakuake to make vertical splits even and much more usable. STEPS TO REPRODUCE 1. Open yakuake 2. Vertical split 3-5 times. OBSERVED RESULT Splits become increasingly smaller and uneven. EXPECTED RESULT Splits should be even, like implemented in konsole, making this function much more usable. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.25 KDE Frameworks Version: 5.95 Qt Version: 5.15.4 ADDITIONAL INFORMATION yakuake package version 22.04.2-1. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455292] New: 5.25 Desktop Grid - Keyboard virtual desktop selection missing.
https://bugs.kde.org/show_bug.cgi?id=455292 Bug ID: 455292 Summary: 5.25 Desktop Grid - Keyboard virtual desktop selection missing. Product: kwin Version: 5.25.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: hugh.ga...@tutamail.com Target Milestone: --- SUMMARY New desktop grid implentation in 5.25 does not allow keyboard selection of a virtual desktop whilst in grid mode. Only way to select is to click a desktop with the mouse. Please add this functionality back. STEPS TO REPRODUCE 1. Open desktop grid view. 2. Use number keys or Function keys to select a virtual desktop. OBSERVED RESULT Nada. Keyed desktop does not become active and desktop grid remains open. EXPECTED RESULT Desktop grid closes and selected desktop becomes active. Previous implementation of desktop grid allowed for numerical keyboard selection (ie 1-n) and function key selection (ie F1-Fn). Please add both these back. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.25 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455280] While arranging a single window, all windows in the same workspace move along together.
https://bugs.kde.org/show_bug.cgi?id=455280 --- Comment #2 from hugh --- Created attachment 149722 --> https://bugs.kde.org/attachment.cgi?id=149722=edit Cannot move window to desktop with existing windows either. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455280] While arranging a single window, all windows in the same workspace move along together.
https://bugs.kde.org/show_bug.cgi?id=455280 hugh changed: What|Removed |Added CC||hugh.ga...@tutamail.com --- Comment #1 from hugh --- Created attachment 149721 --> https://bugs.kde.org/attachment.cgi?id=149721=edit Cannot move single window -- You are receiving this mail because: You are watching all bug changes.
[Planet KDE] [Bug 455268] Can't drag only a single window from one virtual desktop to another
https://bugs.kde.org/show_bug.cgi?id=455268 --- Comment #2 from hugh --- Created attachment 149720 --> https://bugs.kde.org/attachment.cgi?id=149720=edit Cannot move to a desktop with existing windows either, swaps them. Cannot move to a desktop with existing windows either, swaps them. -- You are receiving this mail because: You are watching all bug changes.
[Planet KDE] [Bug 455268] Can't drag only a single window from one virtual desktop to another
https://bugs.kde.org/show_bug.cgi?id=455268 hugh changed: What|Removed |Added CC||hugh.ga...@tutamail.com --- Comment #1 from hugh --- Created attachment 149719 --> https://bugs.kde.org/attachment.cgi?id=149719=edit Cannot move a single window Cannot move a single window in desktop grid also. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 454013] Delighted with enhancements in latest version!
https://bugs.kde.org/show_bug.cgi?id=454013 --- Comment #2 from Hugh Esco --- That would be a never mind. With some additional time spent with the upgraded version of this tool, I find it really does allow me to manage its use without having to interact with a mouse !!! Alhamdulillah! -- Hugh Esco On Thu, 19 May 2022 16:02:20 + "Nate Graham" wrote: > https://bugs.kde.org/show_bug.cgi?id=454013 > > Nate Graham changed: > >What|Removed |Added > > CC||n...@kde.org > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Nate Graham --- > Well this is a nice departure from the normal kind of bug report we get! I'm > so > happy you're happy! > > The template lives in the settings window and I can get there via the > keyboard. > Can you describe in detail what exactly the problem is, and what changed > compared the the previous version you were using? > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 454013] Delighted with enhancements in latest version!
https://bugs.kde.org/show_bug.cgi?id=454013 Hugh Esco changed: What|Removed |Added CC||hesco@yourmessagedelivered. ||com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 454013] New: Delighted with enhancements in latest version!
https://bugs.kde.org/show_bug.cgi?id=454013 Bug ID: 454013 Summary: Delighted with enhancements in latest version! Product: Spectacle Version: 20.12.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: he...@yourmessagedelivered.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I just upgraded to Debian v9, Stretch to Debian v11, Bullseye. This is a quick note to express how delighted I am with the new features available with spectacle! I find particularly useful the fact that a subsequent screenshot in the same session now remembers the boundaries of the 'Rectangular Region' which was the subject of the previous screenshot. This makes it so much easier to capture pages from a slide deck during a presentation! Also useful is the new UI showing me the name and a button to 'Open Containing Floder' for the most recently saved screenshot. So far, the only feature I had grown accustomed to in the legacy version which seems to be missing in the new version is the ability to navigate with the keyboard and to select an image name to use as template I can conveniently edit and use to save a new screenshot. This requires that I have to interact with the mouse to complete this task. But that is a very small price to pay for not having to use the mouse to draw the region boundaries for every screenshot. Excellent work, folks! Thank you for these enhancements! -- Hugh Esco Roswell Georgia 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.
[kwin] [Bug 449988] [X11] No Border Window Action Toggle Continually Shrinks the Window Size
https://bugs.kde.org/show_bug.cgi?id=449988 hugh changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #21 from hugh --- Still not working properly. The window size with no border is still smaller than the original window. It should be the same size, at least that was the old behavior, which I believe is correct. See the old behavior vs new behavior video attachments. Borderless window contents should expand into the old window size with borders. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449988] [X11] No Border Window Action Toggle Continually Shrinks the Window Size
https://bugs.kde.org/show_bug.cgi?id=449988 --- Comment #20 from hugh --- Created attachment 146797 --> https://bugs.kde.org/attachment.cgi?id=146797=edit New behavior with 5.24 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449988] [X11] No Border Window Action Toggle Continually Shrinks the Window Size
https://bugs.kde.org/show_bug.cgi?id=449988 --- Comment #19 from hugh --- Created attachment 146796 --> https://bugs.kde.org/attachment.cgi?id=146796=edit No border old behavior, prior to 5.24 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449988] [X11] No Border Window Action Toggle Continually Shrinks the Window Size
https://bugs.kde.org/show_bug.cgi?id=449988 --- Comment #18 from hugh --- Yeah, my bad. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449988] [X11] No Border Window Action Toggle Continually Shrinks the Window Size
https://bugs.kde.org/show_bug.cgi?id=449988 --- Comment #16 from hugh --- Thanks for the fix. Will be in 5.24.1? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449988] [X11] No Border Window Action Toggle Continually Shrinks the Window Size
https://bugs.kde.org/show_bug.cgi?id=449988 --- Comment #10 from hugh --- I have more than 10 arch systems over multiple machines, both virtual and non virtual. This is happening on all of them. If you cannot replicate this then it is relevant. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449988] No Border Window Action Toggle Continually Shrinks the Window Size
https://bugs.kde.org/show_bug.cgi?id=449988 --- Comment #8 from hugh --- Changed Global theme to Breeze Dark, no change, still happening. Are you trying to recreate with a non Arch package base? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449988] No Border Window Action Toggle Continually Shrinks the Window Size
https://bugs.kde.org/show_bug.cgi?id=449988 --- Comment #7 from hugh --- Created attachment 146619 --> https://bugs.kde.org/attachment.cgi?id=146619=edit System settings shrinkage -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449988] No Border Window Action Toggle Continually Shrinks the Window Size
https://bugs.kde.org/show_bug.cgi?id=449988 --- Comment #6 from hugh --- Using Oxygen Application Style, Plasma Style and Window Decorations. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449988] No Border Window Action Toggle Continually Shrinks the Window Size
https://bugs.kde.org/show_bug.cgi?id=449988 --- Comment #5 from hugh --- All windows using X11, don't use Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449988] No Border Window Action Toggle Continually Shrinks the Window Size
https://bugs.kde.org/show_bug.cgi?id=449988 --- Comment #4 from hugh --- Created attachment 146618 --> https://bugs.kde.org/attachment.cgi?id=146618=edit Kate window shrinkag3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449988] No Border Window Action Toggle Continually Shrinks the Window Size
https://bugs.kde.org/show_bug.cgi?id=449988 hugh changed: What|Removed |Added Attachment #146616|0 |1 is obsolete|| --- Comment #3 from hugh --- Created attachment 146617 --> https://bugs.kde.org/attachment.cgi?id=146617=edit Firefox window shrinkage -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449988] No Border Window Action Toggle Continually Shrinks the Window Size
https://bugs.kde.org/show_bug.cgi?id=449988 --- Comment #2 from hugh --- Created attachment 146616 --> https://bugs.kde.org/attachment.cgi?id=146616=edit Firefox window shrinkage -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449988] No Border Window Action Toggle Continually Shrinks the Window Size
https://bugs.kde.org/show_bug.cgi?id=449988 hugh changed: What|Removed |Added OS|Other |Linux Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449988] New: No Border Window Action Toggle Continually Shrinks the Window Size
https://bugs.kde.org/show_bug.cgi?id=449988 Bug ID: 449988 Summary: No Border Window Action Toggle Continually Shrinks the Window Size Product: kwin Version: 5.24.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: hugh.ga...@tutamail.com Target Milestone: --- STEPS TO REPRODUCE 1. Open a window in Plasma 5.24 (X11) 2. Toggle No Border window action 3. Togger No Border again 4. Togger No Border again 5. Togger No Border again OBSERVED RESULT The window will repeatedly shrink with each toggle. When the titlebar and border is toggled off the window contents are not repainted in the existing window area. The titlebar is simply removed and new window size now becomes the existing window area. The window shrinks by the size of the titlebar and border each toggle. EXPECTED RESULT Prior to 5.24 toggling the no border setting did not alter the window size. It remained exactly the same size. SOFTWARE/OS VERSIONS Linux Distro : Arch KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 437070] New: Konsole app crashes after seeting fonts to random colors
https://bugs.kde.org/show_bug.cgi?id=437070 Bug ID: 437070 Summary: Konsole app crashes after seeting fonts to random colors Product: konsole Version: 20.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: hughman-drif...@protonmail.com Target Milestone: --- Application: konsole (20.12.2) Qt Version: 5.15.2 Frameworks Version: 5.81.0 Operating System: Linux 5.11.19-300.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.21.5 Distribution: Fedora 34 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: - Custom settings of the application: Open Konsole go to edit profile. There is a setting to set the font to come up in random colors each time a new session is opened. Clicked that. App immediately crashed. Tried to restart app crashed again. Reboot OS same result when opening Konsole. Just installed Fedora 34 and was adjusting settings to ones I have used for years. The crash can be reproduced every time. -- Backtrace: Application: Konsole (konsole), signal: Aborted [KCrash Handler] #4 0x7fdafb6752a2 in raise () from /lib64/libc.so.6 #5 0x7fdafb65e8a4 in abort () from /lib64/libc.so.6 #6 0x7fdafb536c78 in std::__replacement_assert(char const*, int, char const*, char const*) () from /lib64/libkonsoleprivate.so.20 #7 0x7fdafb5d948f in std::piecewise_linear_distribution::param_type::_M_initialize() () from /lib64/libkonsoleprivate.so.20 #8 0x7fdafb5e05af in Konsole::ColorScheme::colorEntry(int, unsigned int) const () from /lib64/libkonsoleprivate.so.20 #9 0x7fdafb592a29 in Konsole::TerminalDisplay::applyProfile(QExplicitlySharedDataPointer const&) () from /lib64/libkonsoleprivate.so.20 #10 0x7fdafb54a33b in Konsole::ViewManager::applyProfileToView(Konsole::TerminalDisplay*, QExplicitlySharedDataPointer const&) () from /lib64/libkonsoleprivate.so.20 #11 0x7fdafb55284b in Konsole::ViewManager::createView(Konsole::Session*) () from /lib64/libkonsoleprivate.so.20 #12 0x7fdafbe1182e in Konsole::MainWindow::createSession(QExplicitlySharedDataPointer, QString const&) () from /lib64/libkdeinit5_konsole.so #13 0x7fdafbe17a64 in Konsole::Application::newInstance() () from /lib64/libkdeinit5_konsole.so #14 0x7fdafbe22918 in kdemain () from /lib64/libkdeinit5_konsole.so #15 0x7fdafb65fb75 in __libc_start_main () from /lib64/libc.so.6 #16 0x55e6e0d0636e in _start () [Inferior 1 (process 7713) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 434586] PSD filters (Multiply, Screen) not working as expected in this very specific example
https://bugs.kde.org/show_bug.cgi?id=434586 --- Comment #2 from Hugh Phoenix-Hulme --- Thank you! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 434586] New: PSD filters (Multiply, Screen) not working as expected in this very specific example
https://bugs.kde.org/show_bug.cgi?id=434586 Bug ID: 434586 Summary: PSD filters (Multiply, Screen) not working as expected in this very specific example Product: krita Version: 4.4.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Filters Assignee: krita-bugs-n...@kde.org Reporter: h...@webnet.org.uk Target Milestone: --- SUMMARY When loading a PSD file the output is completely different to PhotoShop (not just a bit different) STEPS TO REPRODUCE 1. Load the PSD (100MB): https://www-sub-etha-link.s3-eu-west-1.amazonaws.com/ascension+ebook+source.psd 2. Compare with the PNG (5.2MB): https://www-sub-etha-link.s3-eu-west-1.amazonaws.com/ascension-ebook-cover.png 3. Note that the PSD doesn't look right when loaded in Krita. OBSERVED RESULT Krita's representation of the PSD is much too bright and the vector objects are barely perceivable. EXPECTED RESULT Expected Krita's representation of the PSD to match the PNG output from PhotoShop. SOFTWARE/OS VERSIONS Windows: macOS: Big Sur 11.2.3 Linux/KDE Plasma: Kubuntu 21.04 (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Both macOS and Linux information supplied because I've tried it on both. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417146] compositing disabled on connecting/disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=417146 hugh changed: What|Removed |Added CC||hugh.ga...@tutamail.com --- Comment #13 from hugh --- 5.21 kwin changes exacerbated this issue. Getting the same issue since 5.21 dropped on Arch with an AMD Ryzen RX580 desktop system, but with my primary monitor and not an external secondary monitor. This happens when I turn my only desktop monitor off and on, which I do to save power when I leave long running tasks unattended, which multiple times daily. Kwin_X11 --replace& only way to restore compositing, ALT+SHIFT+F12 doesn't work. Issue with primary monitor didn't occur for me with 5.20, so the wider breadth of this issue is a 5.21 regression too. A few observations : If I disable the Blur Desktop Effect the issue goes away. If I enable the Blur Desktop Effect the issue returns. If I enable the Background Contrast Desktop effect the issue goes away, even if Blur is enabled. Some internet search results recommended enabling Background Contrast Desktop Effect as a temp fix to this issue. Ideally Blur should work in the situation without Background Contrast, but currently it doesn't. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424307] New: Kwin segfault on initial log-in
https://bugs.kde.org/show_bug.cgi?id=424307 Bug ID: 424307 Summary: Kwin segfault on initial log-in Product: kwin Version: 5.19.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: hugh.kerno...@gmail.com Target Milestone: --- Application: kwin_x11 (5.19.3) (Compiled from sources) Qt Version: 5.15.0 Frameworks Version: 5.72.0 Operating System: Linux 5.7.8-arch1-1 x86_64 Windowing system: X11 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Logging in to a test Plasma desktop built from source, using a custom session - Custom settings of the application: KDE Frameworks and Workspace built from source by kdesrc-build on 15 July, into a discrete tree. QT 5.15 not built separately but using /usr/lib installation from my main user set-up. After the crash both monitors are black with a functioning mouse pointer. From a tty log-in, Journalctl shows that the remainder of the Plasma desktop started normally. The X server is still running but attempts to re-start kwin with DISPLAY=0: kwin_x11 fail with a fatal error and unable to open display. pkill -u ... clears the black screens and returns to sddm for graphical log-in. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #4 0x7f0b6c7c7144 in xcb_send_request_with_fds64 () at /usr/lib/libxcb.so.1 #5 0x7f0b6c7c76ba in xcb_send_request () at /usr/lib/libxcb.so.1 #6 0x7f0b6c7cdfd2 in xcb_intern_atom_unchecked () at /usr/lib/libxcb.so.1 #7 0x5643ddbe456c in KWin::KWinSelectionOwner::make_selection_atom(int) (this=0x5643de3d57d0, screen_P=0) at /home/hugh_coder2/kde/src/kwin/main_x11.cpp:164 #8 0x5643ddbe41a9 in KWin::KWinSelectionOwner::KWinSelectionOwner(int) (this=0x5643de3d57d0, screen=0) at /home/hugh_coder2/kde/src/kwin/main_x11.cpp:119 #9 0x5643ddbe04ae in KWin::ApplicationX11::performStartup() (this=0x7ffec144e1f0) at /home/hugh_coder2/kde/src/kwin/main_x11.cpp:219 #10 0x5643ddbe1e9d in main(int, char**) (argc=3, argv=0x7ffec144e378) at /home/hugh_coder2/kde/src/kwin/main_x11.cpp:477 [Inferior 1 (process 18456) detached] Possible duplicates by query: bug 414359, bug 403933, bug 364121, bug 363251, bug 349023. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 418987] Crash in project bin
https://bugs.kde.org/show_bug.cgi?id=418987 --- Comment #1 from Hugh Tebby --- Issue seemed to be with Movit library. I just recompiled after having removed the library from my system. I suppose I must of had gpu acceleration enabled in settings. Will test again later with gpu acceleration enabled and disabled. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 418987] New: Crash in project bin
https://bugs.kde.org/show_bug.cgi?id=418987 Bug ID: 418987 Summary: Crash in project bin Product: kdenlive Version: git-master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: hugh.te...@gmail.com Target Milestone: --- SUMMARY When clicking on several clips in project bin, Kdenlive crashes. STEPS TO REPRODUCE 1. Add a couple of files to empty project (tested with video and/or audio) 2. Select a file and change file using either mouse or keyboard arrows 3. Repeat two or three times OBSERVED RESULT Crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION Reproduced with Git Master, also in version 19.12.2 (deb and snap versions). Works fine in 19.04 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417439] New: NVidia causes Plasma to crash while lockscreen is on
https://bugs.kde.org/show_bug.cgi?id=417439 Bug ID: 417439 Summary: NVidia causes Plasma to crash while lockscreen is on Product: plasmashell Version: 5.17.90 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: h...@webnet.org.uk CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.90) Qt Version: 5.12.5 Frameworks Version: 5.66.0 Operating System: Linux 5.4.0-12-generic x86_64 Windowing system: X11 Distribution: Ubuntu Focal Fossa (development branch) -- Information about the crash: - What I was doing when the application crashed: I had locked the screen and headed off to work. Upon returning, I had the screen that told me to log in with a tty and use loginctl to unlock the session. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x55b40b578c44) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 [Current thread is 1 (Thread 0x7f06fbe93340 (LWP 3144))] Thread 28 (Thread 0x7f0666bfc700 (LWP 26921)): #0 0x7f06ff448c3f in __GI___poll (fds=0x7f06540038b0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f06dfa571c6 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f06dfa48831 in pa_mainloop_poll () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f06dfa48eb3 in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f06dfa48f60 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f06dfa5710d in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f06df7b736c in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.0.so #7 0x7f06fec72669 in start_thread (arg=) at pthread_create.c:479 #8 0x7f06ff455333 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7f06d1e10700 (LWP 25263)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f06f401e474) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f06f401e420, cond=0x7f06f401e448) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f06f401e448, mutex=0x7f06f401e420) at pthread_cond_wait.c:638 #3 0x7f06ff7cbb3f in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f06ff7cbc31 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f07014bf0f9 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f07014bf39d in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f06ff7c5a02 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f06fec72669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f06ff455333 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7f065700 (LWP 20747)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55b40cda33b0) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55b40cda3360, cond=0x55b40cda3388) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55b40cda3388, mutex=0x55b40cda3360) at pthread_cond_wait.c:638 #3 0x7f06ff7cbb3f in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f06ff7cbc31 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f06e8bca050 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f06e8bcdd4e in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f06e8bc9222 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f06e8bcbcb3 in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f06ff7c5a02 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f06fec72669 in start_thread (arg=) at pthread_create.c:479 #11 0x7f06ff455333 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f0667fff700 (LWP 20746)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55b40cda33b0) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55b40cda3360, cond=0x55b40cda3388) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55b40cda3388, mutex=0x55b40cda3360) at pthread_cond_wait.c:638 #3 0x7f06ff7cbb3f in QWaitCondition::wait(QMutex*,
[krunner] [Bug 386114] KRunner on wayland always appears under top panel
https://bugs.kde.org/show_bug.cgi?id=386114 --- Comment #16 from Hugh Williams --- (In reply to mateusz.szynka from comment #15) > There is a walkaround to set position (will test that in the evening) > > https://superuser.com/questions/906983/how-can-i-change-the-screen-position- > of-krunner-in-kde-plasma-5-x I am not sure that window rules are working yet for Plasma Wayland -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 386114] KRunner on wayland always appears under top panel
https://bugs.kde.org/show_bug.cgi?id=386114 Hugh Williams changed: What|Removed |Added CC||hmlwilli...@protonmail.com --- Comment #13 from Hugh Williams --- Is it not possible just to make the startup location for krunner configurable i.e. centred on screen or bottom? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 403776] Powerdevil suddenly crashes during normal operation
https://bugs.kde.org/show_bug.cgi?id=403776 --- Comment #18 from hugh --- Created attachment 118594 --> https://bugs.kde.org/attachment.cgi?id=118594=edit qBittorrent is erroneously suppressing power mgmt, why? qBittorrent is erroneously suppressing power mgmt, why? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 403776] Powerdevil suddenly crashes during normal operation
https://bugs.kde.org/show_bug.cgi?id=403776 --- Comment #16 from hugh --- *** Bug 404998 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 404998] Power devil crashes
https://bugs.kde.org/show_bug.cgi?id=404998 hugh changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from hugh --- *** This bug has been marked as a duplicate of bug 403776 *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 403776] Powerdevil suddenly crashes during normal operation
https://bugs.kde.org/show_bug.cgi?id=403776 hugh changed: What|Removed |Added CC||hugh.ga...@tutamail.com --- Comment #15 from hugh --- Same issue in Manjaro with Plasma 5.15.2 with Qt 5.12.1. Qbittorrent closing can crash powerdevil, openvpn connection dropping can also trigger a powerdevil crash. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 404998] Power devil crashes
https://bugs.kde.org/show_bug.cgi?id=404998 hugh changed: What|Removed |Added CC||hugh.ga...@tutamail.com --- Comment #1 from hugh --- Same issue here on Manjaro. Powerdevil is crashing randomly although I have noticed it occuring when an openvpn connection drops also. Manjaro Plasma 5.12.1 Frameworks 5.55 Qt 5.12.1 Kernel 4.19.26 Mar 07 00:20:56 manjaro org_kde_powerdevil[2529]: "Message recipient disconnected from message bus without replying" Mar 07 00:20:57 manjaro systemd-coredump[2535]: Process 2367 (org_kde_powerde) of user 1000 dumped core. Stack trace of thread 2367: #0 0x7fbc35409d7f raise (libc.so.6) #1 0x7fbc36a3f682 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5) #2 0x7fbc35409e00 __restore_rt (libc.so.6) #3 0x7fbc35863606 _ZeqRK7QStringS1_ (libQt5Core.so.5) #4 0x7fbc369f78be _ZN10PowerDevil11PolicyAgent21onServiceUnregisteredERK7QString (libpowerdevilcore.so.2) #5 0x7fbc36a229fa n/a (libpowerdevilcore.so.2) #6 0x7fbc359ca87c _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5) #7 0x7fbc35cc76c6 _ZN19QDBusServiceWatcher19serviceUnregisteredERK7QString (libQt5DBus.so.5) #8 0x7fbc35cc7f2b n/a (libQt5DBus.so.5) #9 0x7fbc35cc8333 _ZN19QDBusServiceWatcher11qt_metacallEN11QMetaObject4CallEiPPv (libQt5DBus.so.5) #10 0x7fbc35c759ef n/a (libQt5DBus.so.5) #11 0x7fbc359cb152 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5) #12 0x7fbc3599fe99 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5) #13 0x7fbc359a2f38 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5) #14 0x7fbc359f6714 n/a (libQt5Core.so.5) #15 0x7fbc33c23a2f g_main_context_dispatch (libglib-2.0.so.0) #16 0x7fbc33c255e9 n/a (libglib-2.0.so.0) #17 0x7fbc33c2562e g_main_context_iteration (libglib-2.0.so.0) #18 0x7fbc359f5ce9 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #19 0x7fbc3599eb2c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #20 0x7fbc359a6e36 _ZN16QCoreApplication4execEv (libQt5Core.so.5) #21 0x5643dba4018f n/a (org_kde_powerdevil) #22 0x7fbc353f6223 __libc_start_main (libc.so.6) #23 0x5643dba401fe _start (org_kde_powerdevil) Stack trace of thread 2369: #0 0x7fbc354c2c21 __poll (libc.so.6) #1 0x7fbc33c25540 n/a (libglib-2.0.so.0) #2 0x7fbc33c2562e g_main_context_iteration (libglib-2.0.so.0) #3 0x7fbc359f5d04 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x7fbc3599eb2c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x7fbc357e2569 _ZN7QThread4execEv (libQt5Core.so.5) #6 0x7fbc35c69ba6 n/a (libQt5DBus.so.5) #7 0x7fbc357e396c n/a (libQt5Core.so.5) #8 0x7fbc3489ca9d start_thread (libpthread.so.0) #9 0x7fbc354cdb23 __clone (libc.so.6) Stack trace of thread 2371: #0 0x7fbc354c2c21 __poll (libc.so.6) #1 0x7fbc33c25540 n/a (libglib-2.0.so.0) #2 0x7fbc33c265c2 g_main_loop_run (libglib-2.0.so.0) #3 0x7fbc2de1dcb8 n/a (libgio-2.0.so.0) #4 0x7fbc33c0067b n/a (libglib-2.0.so.0) #5 0x7fbc3489ca9d start_thread (libpthread.so.0) #6 0x7fbc354cdb23 __clone (libc.so.6) Stack trace of thread 2370: #0 0x7fbc354c2c21 __poll (libc.so.6) #1 0x7fbc33c25540 n/a (libglib-2.0.so.0) #2 0x7fbc33c2562e g_main_context_iteration (libglib-2.0.so.0) #3 0x7fbc33c25682 n/a (libglib-2.0.so.0) #4 0x7fbc33c0067b n/a (libglib-2.0.so.0) #5 0x7fbc3489ca9d start_thread (libpthread.so.0) #6 0x7fbc354cdb23 __clone (libc.so.6) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400444] New: Background Image & Icons Pushed to One Side
https://bugs.kde.org/show_bug.cgi?id=400444 Bug ID: 400444 Summary: Background Image & Icons Pushed to One Side Product: plasmashell Version: 5.12.6 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: h...@hmmccall.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.6) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-38-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: Occasionally, after booting and logging in, the background desktop and icons will be pushed to the far right side of the screen. I've found no other way to fix it but to kquitapp5 and kstart plasmashell. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd42fc8a800 (LWP 1957))] Thread 8 (Thread 0x7fd36259f700 (LWP 2117)): #0 0x7fd423dc3983 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fd423dc436b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd423dc454c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd429ba390b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd429b489ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd42996722a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd364efb747 in KCupsConnection::run() () at /usr/lib/x86_64-linux-gnu/libkcupslib.so #7 0x7fd42996c16d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fd428aed6db in start_thread (arg=0x7fd36259f700) at pthread_create.c:463 #9 0x7fd42926788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fd3763d3700 (LWP 2069)): #0 0x7fd42925abf9 in __GI___poll (fds=0x7fd370005610, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fd423dc4439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd423dc454c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd429ba390b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd429b489ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd42996722a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd42d6732a6 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fd42996c16d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fd428aed6db in start_thread (arg=0x7fd3763d3700) at pthread_create.c:463 #9 0x7fd42926788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fd409d6a700 (LWP 2066)): #0 0x7fd428af39f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fd42f648fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fd428af39f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7fd42f648f68, cond=0x7fd42f648f90) at pthread_cond_wait.c:502 #2 0x7fd428af39f3 in __pthread_cond_wait (cond=0x7fd42f648f90, mutex=0x7fd42f648f68) at pthread_cond_wait.c:655 #3 0x7fd42f3525f4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7fd42f352639 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7fd428aed6db in start_thread (arg=0x7fd409d6a700) at pthread_create.c:463 #6 0x7fd42926788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fd40bdc7700 (LWP 2041)): #0 0x7fd42925abf9 in __GI___poll (fds=0x7fd43ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fd423dc4439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd423dc454c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd429ba390b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd429b489ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd42996722a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd42cad96f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fd42996c16d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fd428aed6db in start_thread (arg=0x7fd40bdc7700) at pthread_create.c:463 #9 0x7fd42926788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fd411e66700 (LWP 2021)): #0 0x7fd4292560b4 in __GI___libc_read (fd=10, buf=0x7fd411e65b70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1
[kwin] [Bug 400138] New: Desktop cube animation with blur desktop effect creates blurred rectangular artifact in upper screen quadrant
https://bugs.kde.org/show_bug.cgi?id=400138 Bug ID: 400138 Summary: Desktop cube animation with blur desktop effect creates blurred rectangular artifact in upper screen quadrant Product: kwin Version: 5.14.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: hugh.ga...@tutamail.com Target Milestone: --- Created attachment 115820 --> https://bugs.kde.org/attachment.cgi?id=115820=edit Screen grab of the described rectangular blur artifact during desktop cube animation SUMMARY First bug report. I use the desktop cube animate desktop effect to switch between virtual desktops. Since the updated blur modifications introduced in Plasma 5.13 (I think) using desktop cube in combination with the blur desktop effect has led to the upper right quadrant of the screen blurring during transition from one virtual destop to another. Disable the blur desktop effect and the upper right quadrant does not blur during virtual desktop transition via the desktop cube animation. STEPS TO REPRODUCE 1. Enable desktop cube desktop effect in System Settings > Desktop Effects 2. Select the desktop cube animation in System Settings > Virtual Desktops 3. Enable the blur desktop effect in System Settings > Desktop Effects 4. Trigger desktop cube animation by moving from one virtual desktop to another OBSERVED RESULT There is a rectangular region in the upper right quadrant of the screen that blurs. Screen grab of this rectangular region blur is attached. EXPECTED RESULT This rectangular region of the screen should not blur during virtual desktop transition. Looks like it may be a hidden region used in desktop cube animation being mistakenly blurred. Disabling the blur desktop effect is a workaround, but then I am unable to use blur in other parts of my system. SOFTWARE VERSIONS Distro: Manjaro KDE Plasma Version: 5.14.1 KDE Frameworks Version: 5.51 Qt Version: 5.11.2 ADDITIONAL INFORMATION Using an intel onboard gpu using standard i915 driver with xorg-server 1.20.2. This issue was introduced in 5.13 and is still present in 5.14.1. Looked for a similar bug before creating this, did not find one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370975] device notifier pretends it cannot mount usb device while actually mounting it
https://bugs.kde.org/show_bug.cgi?id=370975 D. Hugh Redelmeier <hugh+kde...@mimosa.com> changed: What|Removed |Added CC| |hugh+kde...@mimosa.com -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 267277] configurable delay for autohide/show of panels
https://bugs.kde.org/show_bug.cgi?id=267277 Hugh Williams <hughbertwilli...@gmail.com> changed: What|Removed |Added CC||hughbertwilli...@gmail.com --- Comment #58 from Hugh Williams <hughbertwilli...@gmail.com> --- Would it not be sensible to register this as a bug in plasmashell now as development on plasma 4 has ceased? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 355767] KRunner searches for words inside files, but does not find the file that matches the words provided
https://bugs.kde.org/show_bug.cgi?id=355767 Hugh Gao <hughga...@gmail.com> changed: What|Removed |Added CC||hughga...@gmail.com --- Comment #2 from Hugh Gao <hughga...@gmail.com> --- Search by content annoying in a lot times, because the result list is so long that it's difficult to find what wanted. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 374426] New: Set alternate color scheme when using dark themes.
https://bugs.kde.org/show_bug.cgi?id=374426 Bug ID: 374426 Summary: Set alternate color scheme when using dark themes. Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: hughbertwilli...@gmail.com Target Milestone: --- When utilising dark desktop themes it is impossible to read the text from HTML emails which fail to set a background with dark text on dark backgrounds. A possible workaround is to use per-application theming and choose a lighter theme for KMail, which has been discussed and implemented in KColorSchemeManager I think (see bug #279592)? -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 279592] Allow per-application color scheme
https://bugs.kde.org/show_bug.cgi?id=279592 Hugh Williams <hughbertwilli...@gmail.com> changed: What|Removed |Added CC||hughbertwilli...@gmail.com --- Comment #20 from Hugh Williams <hughbertwilli...@gmail.com> --- What is the best way to pursue getting this feature added to relevant apps e.g. KMail? File a bug/feature request with them and link this thread? -- You are receiving this mail because: You are watching all bug changes.
