[kwin] [Bug 483229] Sometimes unable to bring background apps to the front while Chrome/Chromium is running
https://bugs.kde.org/show_bug.cgi?id=483229 --- Comment #10 from Dean Hoover --- > by any chance are you using a scale factor below 100%, and is Chrome/Chromium running in native Wayland mode? I am running native Wayland on the laptop, but the scale factor is set to 100% (it was originally set to 125% by the OS when I first installed it but I changed it soon after). I read the bug you listed. Although my situation is with the scale factor at 100% I will try to sneak some time to see if lowering/raising the factor makes a dent. Dean On Mon, Apr 1, 2024 at 12:22 PM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=483229 > > --- Comment #9 from Nate Graham --- > (In reply to Dean Hoover from comment #8) > > Created attachment 167474 [details] > > attachment-371693-0.html > > > > The only apps that I've been able to recreate this is Google Chrome and > > UnGoogled Chromium. I don't use any other Chromium-based browser, and it > > doesn't seem to happen with Firefox. > > > > It's almost as if the browser believes that the window is larger than it > > actually is. For example, the browser window might be 800x1000 but it > > tells the DE that it's 800x1050 so that if the mouse clicks between the > > 1000 and 1050 the browser window becomes the foreground instead of the > > actual app that they are trying to get to. > Hmm... by any chance are you using a scale factor below 100%, and is > Chrome/Chromium running in native Wayland mode? If so this sounds very much > like Bug 477676. > > > Appreciate your time Nate. I've been a UNIX and Linux server user and > > administrator for almost 40 years, but every DE I've tried never worked > > well enough for me. KDE has changed my mind, and if it wasn't for a > couple > > Windows-only apps (Cisco ASDM, Teams' ability to take control of PC, etc) > > I'd be 100% Linux and KDE for work and home. > Thanks for the kind words! We try hard to make it a pleasant and productive > environment. :) > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483229] Sometimes unable to bring background apps to the front while Chrome/Chromium is running
https://bugs.kde.org/show_bug.cgi?id=483229 --- Comment #8 from Dean Hoover --- The only apps that I've been able to recreate this is Google Chrome and UnGoogled Chromium. I don't use any other Chromium-based browser, and it doesn't seem to happen with Firefox. It's almost as if the browser believes that the window is larger than it actually is. For example, the browser window might be 800x1000 but it tells the DE that it's 800x1050 so that if the mouse clicks between the 1000 and 1050 the browser window becomes the foreground instead of the actual app that they are trying to get to. Unless you think this still might be a KDE issue, I think you can close this ticket. I also submitted feedback to Google but I honestly don't think they will say or do anything about it. And now that I have a better grasp of where and when it happens, I can adjust the way I do things to mitigate the issue. Appreciate your time Nate. I've been a UNIX and Linux server user and administrator for almost 40 years, but every DE I've tried never worked well enough for me. KDE has changed my mind, and if it wasn't for a couple Windows-only apps (Cisco ASDM, Teams' ability to take control of PC, etc) I'd be 100% Linux and KDE for work and home. Keep up the great work! Dean On Mon, Mar 18, 2024 at 5:00 PM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=483229 > > Nate Graham changed: > >What|Removed |Added > > > Summary|Unable to click background |Sometimes unable to bring >|app/window to foreground|background apps to the >|using mouse |front while > Chrome/Chromium >||is running > > --- Comment #7 from Nate Graham --- > Thanks. From those screen recordings, it looks like the problem only > happens > while Chrome/Chromium is running, and when it happens, it seemingly > randomly > affects all kinds of apps and not just Chrome/Chromium itself, right? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483229] Unable to click background app/window to foreground using mouse
https://bugs.kde.org/show_bug.cgi?id=483229 --- Comment #6 from Dean Hoover --- Let's try it over Google Drive. Also - I was able to recreate it with UnGoogled-Chromium - just much smaller area than with Google Chrome. Google-Chrome-switching-screens.webm <https://drive.google.com/file/d/1zCWYjroq-i2VWBhdVdDM950YyeJnnkUa/view?usp=drive_web> Firefox-switching-screens.webm <https://drive.google.com/file/d/1L1L0u1y2ZJhyTA_S8odceTUJ2vUXWeuw/view?usp=drive_web> On Sat, Mar 16, 2024 at 7:52 AM Dean Hoover wrote: > Hello Nate, > > I was definitely able to recreate it, but playing around a bit I think > this might have something to do with Google Chrome. I can't recreate it if > I'm using Firefox or even UnGoogled Chromium. > > I attached two Spectacle videos to kind of show you what I mean (if you > don't get them let me know and I'll attach them to my Nextcloud or Google > Drive) For some reason, Chrome extends beyond that actual window size. > > Not sure if this is KDE or Chrome - let me know what you think. > > Dean > > On Thu, Mar 14, 2024 at 12:31 PM Nate Graham > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=483229 >> >> --- Comment #4 from Nate Graham --- >> No worries. If it works in a clean user account, we know it's caused by >> come >> configuration in your original user account somehow. >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483229] Unable to click background app/window to foreground using mouse
https://bugs.kde.org/show_bug.cgi?id=483229 --- Comment #5 from Dean Hoover --- Hello Nate, I was definitely able to recreate it, but playing around a bit I think this might have something to do with Google Chrome. I can't recreate it if I'm using Firefox or even UnGoogled Chromium. I attached two Spectacle videos to kind of show you what I mean (if you don't get them let me know and I'll attach them to my Nextcloud or Google Drive) For some reason, Chrome extends beyond that actual window size. Not sure if this is KDE or Chrome - let me know what you think. Dean On Thu, Mar 14, 2024 at 12:31 PM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=483229 > > --- Comment #4 from Nate Graham --- > No worries. If it works in a clean user account, we know it's caused by > come > configuration in your original user account somehow. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483229] Unable to click background app/window to foreground using mouse
https://bugs.kde.org/show_bug.cgi?id=483229 --- Comment #3 from Dean Hoover --- Sorry Nate - haven't forgot about you. I did play with the new user, and I couldn't seem to recreate it. That being said, I have only gotten to test it for about 5-10 minutes. I hope to dig more into it tonight or possibly this weekend. Dean On Mon, Mar 11, 2024 at 5:26 PM Dean Hoover wrote: > Hello Nate, > > I've been using Wayland for quite a while now. > > Once I'm finished with something else I'll test with a clean use account. > > Thanks - Dean > > On Mon, Mar 11, 2024 at 3:09 PM Nate Graham > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=483229 >> >> Nate Graham changed: >> >>What|Removed |Added >> >> >> Product|Active Window Control |kwin >> Resolution|--- |WAITINGFORINFO >> Status|REPORTED|NEEDSINFO >> Component|General |general >>Assignee|zrenf...@gmail.com |kwin-bugs-n...@kde.org >> Version|unspecified |6.0.0 >> CC||n...@kde.org >> >> --- Comment #1 from Nate Graham --- >> Does it work as expected in a new clean user account? >> >> Does this happen on X11, Wayland, or both? >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483229] Unable to click background app/window to foreground using mouse
https://bugs.kde.org/show_bug.cgi?id=483229 --- Comment #2 from Dean Hoover --- Hello Nate, I've been using Wayland for quite a while now. Once I'm finished with something else I'll test with a clean use account. Thanks - Dean On Mon, Mar 11, 2024 at 3:09 PM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=483229 > > Nate Graham changed: > >What|Removed |Added > > > Product|Active Window Control |kwin > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > Component|General |general >Assignee|zrenf...@gmail.com |kwin-bugs-n...@kde.org > Version|unspecified |6.0.0 > CC||n...@kde.org > > --- Comment #1 from Nate Graham --- > Does it work as expected in a new clean user account? > > Does this happen on X11, Wayland, or both? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 483229] New: Unable to click background app/window to foreground using mouse
https://bugs.kde.org/show_bug.cgi?id=483229 Bug ID: 483229 Summary: Unable to click background app/window to foreground using mouse Classification: Plasma Product: Active Window Control Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: kb7...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- I apologize if this isn't the right place to put this. STEPS TO REPRODUCE 1. Load multiple, different apps on desktop (e.g. Chrome, Firefox, PuTTY, Remmina, etc) 2. Left-click on one of the background apps to try and bring it to foreground OBSERVED RESULT Under most circumstances, I am not able to use the mouse to take the background app/window and bring it to be the foreground app/window. Also not able to bring it to foreground by clicking on the top, bottom, or side border. Just my observation, but the only time I seem to be able to make it work is if there is some type of written text in the area where I clicked. EXPECTED RESULT This functionality has worked with Windows since I can remember, and I can certainly recreate it with Windows 10 and 11. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE 6 (also able to recreate in previous versions of KDE 5) (available in About System) KDE Plasma Version: 6.0 KDE Frameworks Version: can provide more specifics if needed Qt Version: can provide more specifics if needed ADDITIONAL INFORMATION I submitted this using my work PC running Windows 11 - if more specific details are needed, just let me know and I'll provide it on my home laptop. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429892] support set display an alternate calendar system under the main calendar
https://bugs.kde.org/show_bug.cgi?id=429892 dean changed: What|Removed |Added CC||seo1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477559] Plasma shell crashed after removing default panel
https://bugs.kde.org/show_bug.cgi?id=477559 --- Comment #1 from Dean Sellis --- Created attachment 163500 --> https://bugs.kde.org/attachment.cgi?id=163500=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477559] New: Plasma shell crashed after removing default panel
https://bugs.kde.org/show_bug.cgi?id=477559 Bug ID: 477559 Summary: Plasma shell crashed after removing default panel Classification: Plasma Product: plasmashell Version: 5.27.9 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dean.sel...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.9) Qt Version: 5.15.11 Frameworks Version: 5.112.0 Operating System: Linux 6.6.2-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.9 [CoredumpBackend] -- Information about the crash: I was editing hte default panel, decided to remove it, and when I closed the notification that the panel was deleted, Plasma crashed. After plasma recovered, I was able to add the default panel back and I'm having no issues. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 0x7f23eb2943ed in QtQml::qmlExecuteDeferred(QObject*) () at /lib64/libQt5Qml.so.5 #6 0x7f23eb778e99 in QQuickTransition::prepare(QList&, QList&, QQuickTransitionManager*, QObject*) () at /lib64/libQt5Quick.so.5 #7 0x7f23eb76e3a7 in QQuickTransitionManager::transition(QList const&, QQuickTransition*, QObject*) () at /lib64/libQt5Quick.so.5 #8 0x7f23e9d18e5b in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #9 0x7f23ea9a519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 The reporter indicates this bug may be a duplicate of or related to bug 473058, bug 475099, bug 475405, bug 476590. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 417284] Support for the "just play literally any music, and keep going until i say stop" use case
https://bugs.kde.org/show_bug.cgi?id=417284 Dylan Dean changed: What|Removed |Added CC||dylancvd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 471099] Tags can't be renamed nor be deleted
https://bugs.kde.org/show_bug.cgi?id=471099 --- Comment #8 from Dean Rikrik Ichsan Hakiki --- (In reply to tagwerk19 from comment #7) > > ... 'balooctl status' took quite a long time to return the result ... > Balooctl is looking through the index and counting the files that still need > to be indexed - at the same time as baloo is indexing and adding results to > it. The two do a little dance as to who gets access to the file > > One thing to double-check: Watch out whether you are using symlinks. Baloo > does not follow these when it discovers what needs to be indexed. If you've > created your text file in a folder "elsewhere" in your system and symlinked > to it, then it is not going to be indexed. > > Second, there's a recent change (something that is being looked at again at > the moment) that caps the amount of memory that baloo can use. You might > want to check the: > > /usr/lib/systemd/user/kde-baloo.service > > file (if it exists...) If there's a memory limit is there as a: > > MemoryHigh=512M > > line, you can try changing it to: > > MemoryHigh=50% > > and see whether the indexing changes. > > However the underlying problem is likely to be with BTRFS (and the fact that > when you reboot your disc might be mounted with a different device number - > and this makes baloo think that all your files are "new files"). It's worth > looking at Bug 470665. I do use symlinks but when I found this issue I was editing a normal file in the root of my home folder. Also, I assume that Baloo won't follow/index the symlinked folder if the folder is not explicitly added to the index list on the KDE Settings, right? Because after the Baloo behaved normally, I can add the symlinked folder into it and it index the folder just fine. Let's say the folder is located at `/mnt/tier_1/diagrams` and I symlinked it to the home folder, so the path would look like `~/diagrams`, and I add `~/diagrams` explicitly into the indexed folder on the File Search settings and it now indexed and detect tag changes to the file inside this `diagrams` folder, whether I change it from `~` or from `/mnt/tier_1` I checked and the service file exists and it also contains the `MemoryHigh` config with the same value, is it the limit of system memory that Baloo can use? Does it have anything to do with the Baloo index size through `balooctl indexSize`? Also, does 50% means 50% of the total system memory? And the bug you mentioned seems interesting because I've never experienced Baloo reindexing my partition again and again (or either because it's an SSD so it didn't really matter or I just don't pay any attention), even when previously it was non-responsive it just stays idle, I forgot to check the CPU usage but it seems that it doesn't do anything since I have quite underpowered and relatively old CPU (i3-8100) and doesn't feel anything become sluggish or my fan ramping up when start-up, but just the Baloo itself quite slow to respond (among other things I've stated and explained), but definitely will check the next time when I'm going to do a restart. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 471099] Tags can't be renamed nor be deleted
https://bugs.kde.org/show_bug.cgi?id=471099 --- Comment #6 from Dean Rikrik Ichsan Hakiki --- (In reply to tagwerk19 from comment #5) > > ... sorry if somehow I make this bug report section like a forum discussion > > and break any guidelines ... > First off, no worries. The perception and description of a bug grows and > changes with time. That should be expected... > > > ... but baloo doesn't seem to detect this changes and stays at "Idle" on > > the `balooctl monitor` command ... > If you were doing "content indexing" and editing a file (that might happen > if you were changing embedded tags in an MP3 or JPG), then baloo would need > to open the file, read the metadata and index it. > > With 'xattr', the info is "filesystem metadata", akin to the file > modification time. Baloo just picks this up and you won't see the file > appearing in "balooctl monitor". The good news is that you can make use of > tags even if you are not doing content indexing... > > What does "balooshow -x your-tagged-file.txt" give you? Do you get any > (some? all?) details? When I try the command `balooshow -x /path/to/my/file.extension` it shows something like this `36acae1002d 45 57330401 /path/to/my/file.extension: No index information found` But the getfattr returns the applied tags just fine. And I think I found out why, for some reason, even though Baloo didn't do anything, idling, with the indexing progress at 100%, it just becomes unresponsive, it happened for the first 2 purges and restart attempts, and to note that at the time only my home folder being indexed and the hidden folder/file is **unchecked**. What I also found is `balooctl monitor` works just fine but something like `balooctl status` took quite a long time to return the result, and opening the `Search` settings on the KDE System settings took around the same time before showing up the page, and the status is Idle at 100% indexed while executing `balooctl disable` only says disabling and stopping the baloo but seems failed to do so, and with the apparent result when I do `balooctl purge` because it is waiting for the baloo to stop, but at the end of the wait it says failed to stop baloo. But after that, I do some purge and restart cycles again and it seems Baloo is well-behaved now, so maybe the actual bug was Baloo sometimes can become unresponsive and it persist across restarts. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 471099] Tags can't be renamed nor be deleted
https://bugs.kde.org/show_bug.cgi?id=471099 --- Comment #4 from Dean Rikrik Ichsan Hakiki --- (In reply to tagwerk19 from comment #3) > There's layers > > If you want to start at the bottom and check, the tags are stored in xattr > and you can see them with: > > getfattr -d your-tagged-file.txt > > You'll see your tags listed as a "user.xdg.tags" comma-separated list of > values. If you've added tags through Dolphin you can see whether they've got > to the filesystem with a "getfattr" > > You can check whether baloo has indexed the file with balooshow: > > balooshow -x your-tagged-file.txt > > (look for the "XAttr Terms" line), if that's worked, then you should be able > to find the file when searching by the tag: > > baloosearch tags:"yourtag" > > If it's gone wrong up to here, then there's an issue with baloo. > > You don't say what sort of filesystem you are using. It's possible that your > "baloosearch" would show several matches for each file, that can happen if > you are using BTRFS and the best bet then to recreate the index, try > > balooctl purge > > (You might need patience while the files are reindexed) > > Dolphin queries baloo to get its "tag folders", however it caches results > and it can be that it gets hung up with stale results. It should show the > same results in the left hand panel that you see when you manually open > "tags:" > > Possibly an F5 would refresh the data but very likely not, closing Dolphin > and relaunching can help but it's a bit distribution dependent, sometimes > there's a copy of Dolphin running quietly in the background. > > If you want to look deeper, there are likely "tags.so" processes running, > these are the processes that cache the results from baloo. If you've got > more than one "tags.so" process, there's a chance that the different > processes are holding different sets of results (this happened a while back, > possible it's been fixed...) I see, yes, I'm using BTRFS, I apologize for not mentioning it, and indeed `balooctl purge` seems to fix things, but now it seems that baloo doesn't even indexing or monitoring any changes after a purge and then a restart. I restart the computer after executing `balooctl purge` (wait till it finishes the purge), and sure enough the Tag is now gone, and I waited a little while until baloo have 100% indexing my home folder, and then trie to modify a tag of a file in my home folder, the tag seems to be applied and I can see it through `getfattr` command, but baloo doesn't seem to detect this changes and stays at "Idle" on the `balooctl monitor` command resulting in no tags added to Dolphin collection, I think I need some time to see the behaviour of these two software, but I guess it's the bug? Also, sorry if somehow I make this bug report section like a forum discussion and break any guidelines. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 471099] Tags can't be renamed nor be deleted
https://bugs.kde.org/show_bug.cgi?id=471099 --- Comment #2 from Dean Rikrik Ichsan Hakiki --- (In reply to tagwerk19 from comment #1) > > Note that (at least in my case) the two tags still remain, even though > > there's no file in the whole system that uses that tag > The Tags shown the left hand panel depend on baloo having "caught up" with > any changes - new tags, changed tags, old tags etc. > > It can be that a "balooctl check" nudges baloo to go back and double check > for changes. > > There's a tracking bug - Bug 454952 - that tries to collect and summarise > the various tag "eccentricities "... If the tag on the left-hand panel depends on Baloo, then what do the Tags on the All Tags folder (tags:/) depend on? Because now it seems these two groups of tags are different. And the bug I experiencing seems to persist across restarts, I think it's mostly a problem with Dolphin (or Baloo?) because I still can add or remove a tag from a file, but Dolphin stops keeping track of it anymore, which is kinda annoying, and for that note, is there a way to "fix" this like, for example, a graphical glitch on Plasma somehow can be fixed by turning off and on the compositor (the effect stuff) but just for refreshing and resyncing the Tags? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 471099] New: Tags can't be renamed nor be deleted
https://bugs.kde.org/show_bug.cgi?id=471099 Bug ID: 471099 Summary: Tags can't be renamed nor be deleted Classification: Applications Product: dolphin Version: 23.04.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: deanrikrikichsanhakiki+kde...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY My Dolphin now has 2 tags that can't be renamed nor deleted, opening Dolphin through the terminal doesn't show any meaning full log (doesn't show any log at all in the process of renaming or deleting the tags), except `kf.kio.workers.tags: "tags:/Test" stat() invalid url`, when trying to open the "tag folder", `Test` here is what the Tag should be renamed to, not the original/previous name. STEPS TO REPRODUCE - Select a file - Click `Add` on the tag section on the preview/information panel (the panel on the right side of the dolphin) - Add multiple tags in quick succession - Notice that (at least in my case) after a while, the `Tags` section on the left side of the Dolphin shows "All Tags", "Tags 1", and "Tags 2" (in my case) but not the other/rest of the tags I added to the previous file. - Adjust the previous file's tag by removing every tag first, close the tag dialog for the file, then click `Add` again on the file info - Notice that (at least in my case) available tags are only the "Tags 1" and "Tags 2", the previously added tag has gone - Add the remaining tags to the file, close the dialog afterwards - Click the `Edit` on the tag section of the file info again (modify the file tag) - Remove every tag from the file, close the dialog afterwards - Note that (at least in my case) the two tags still remain, even though there's no file in the whole system that uses that tag - Now either try to delete or rename the actual tag (not the Tags section on the left of the dolphin) - Refresh (F5) after doing so - Note that (at least in my case) the tags are neither got renamed nor deleted OBSERVED RESULT - No tag is being renamed or deleted. EXPECTED RESULT - The tag should be renamed or deleted. SOFTWARE/OS VERSIONS Linux/KDE Plasma: - KDE Plasma Version: 5.27.5 - KDE Frameworks Version: 5.106.0 - Qt Version: 5.15.9 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 462615] Use KActionCollection::setDefaultShortcut(s) instead
https://bugs.kde.org/show_bug.cgi?id=462615 Dean changed: What|Removed |Added CC||k...@dsnxt.de Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 465490] Feature request
https://bugs.kde.org/show_bug.cgi?id=465490 --- Comment #2 from Zero Dean --- Created attachment 156091 --> https://bugs.kde.org/attachment.cgi?id=156091=edit A mockup of a dual gallery setup allowing users to see a separate gallery of rated items from that particular folder/gallery A mockup of a "dual gallery/window" setup allowing users to see a separate gallery of rated items from that particular folder/gallery. If you're familiar with Blender, it would be like being able to add an additional viewport. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 465490] New: Feature request
https://bugs.kde.org/show_bug.cgi?id=465490 Bug ID: 465490 Summary: Feature request Classification: Applications Product: digikam Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Usability-Ergonomy Assignee: digikam-bugs-n...@kde.org Reporter: zdrelay+digi...@gmail.com Target Milestone: --- Long time digikam user. Thank you. Feature requests for your consideration: 1. Please consider some easy visual cues for gallery sorting. For example, some icons at the top of the thumbnail viewer that allow users to quickly and easily change the sort order to items. This would be much more efficient than having to go to the view menu each time. 2. Please consider having a small reserved or toggleable space/window specifically for starred/rated items. This way I can browse a main gallery and also see which items have also been rated. Currently sorting by rated throws off the sorting every time you add a new item to the rated items. I would like to be able to see thumbnails of rated items while also being able to browse unrated items (and rate them). Being able to see both at the same time would be a huge time saver. 3. Also, this bug-tracking system is horrendously complicated especially for someone who just wants to submit a feature request. -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 463906] New: New note from clipboard doesn't 'paste' the content correctly
https://bugs.kde.org/show_bug.cgi?id=463906 Bug ID: 463906 Summary: New note from clipboard doesn't 'paste' the content correctly Classification: Applications Product: knotes Version: 5.22.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: programmer.pesesoft+...@gmail.com CC: myr...@kde.org Target Milestone: --- SUMMARY When copying/cutting multi-line text content, and use the `New note from clipboard` tray icon menu, the content is not pasted properly (not retaining the new line), but when creating and pasting manually, it does correctly paste the content. STEPS TO REPRODUCE 1. Create multi-line text content in other app, e.g. KWrite 2. Copy the whole content 3. Right-click the KNote tray icon -> Select New note from clipboard 4. New note created and appeared 5. The content is appeared in one line separated by a single space instead of a new line OBSERVED RESULT The content that being 'pasted' is appeared in a single line text separated by a single space where a new line should be EXPECTED RESULT The content should be 'pasted' properly as if it was pasted manually, retaining the multi-line form. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION Kernel: 6.1.1-1-MANJARO Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461609] When panel loads, it displaces widgets an amount equal to its height
https://bugs.kde.org/show_bug.cgi?id=461609 --- Comment #10 from dean.yeag...@gmail.com --- BTW & REF plasma 5.26.3 not only fixed this problem but a problem where sound would not work on reboot - only after a restart and where Spectacle randomly, most of the time had the Spectacle widow overlaying the screenshot window or full screen (other mode not tested as the problem went away) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 461608] Randomly, usually at first snapshot, the Spectacle window is overlays the snapshot-ed window
https://bugs.kde.org/show_bug.cgi?id=461608 dean.yeag...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 461608] Randomly, usually at first snapshot, the Spectacle window is overlays the snapshot-ed window
https://bugs.kde.org/show_bug.cgi?id=461608 --- Comment #2 from dean.yeag...@gmail.com --- Can you please close this problem? It disappeared on a plasma upgrade to 5.26.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461609] When panel loads, it displaces widgets an amount equal to its height
https://bugs.kde.org/show_bug.cgi?id=461609 --- Comment #8 from dean.yeag...@gmail.com --- (In reply to Nate Graham from comment #6) > Thank you. I thought they might. This confirms my theory that it's the panel > which is pushing them up when it appears > > I *think* we may have fixed with in Plasma 5.26. Any chance yo can use the > Kubuntu Backports PPA to upgrade your system to Plasma 5.26? (In reply to dean.yeag...@gmail.com from comment #7) > Created attachment 153766 [details] > info panel for plasma 5.26.2 upgrade > > info panel for plasma 5.26.2 upgrade (In reply to dean.yeag...@gmail.com from comment #7) > Created attachment 153766 [details] > info panel for plasma 5.26.2 upgrade > > info panel for plasma 5.26.2 upgrade I have installed plasma 5.26.2 from current backport of 2022-11-15 after a handful of restarts and reboots, all is well. Thank you very much -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461609] When panel loads, it displaces widgets an amount equal to its height
https://bugs.kde.org/show_bug.cgi?id=461609 --- Comment #7 from dean.yeag...@gmail.com --- Created attachment 153766 --> https://bugs.kde.org/attachment.cgi?id=153766=edit info panel for plasma 5.26.2 upgrade info panel for plasma 5.26.2 upgrade -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461609] Widgets in bottom half of screen move upward (and possibly shrink) after each reboot
https://bugs.kde.org/show_bug.cgi?id=461609 --- Comment #5 from dean.yeag...@gmail.com --- (In reply to Nate Graham from comment #4) > The panel is the bar at the bottom of the screen with icons on it. > > To make it thicker, right-click on it > Enter Edit Mode > change its size > via the "Panel Height" spinbox. Make it significantly taller or shorter, > then reboot. After the reboot, have the widgets on the desktop moved by an > amount that's equal to the new panel height, rather than the old panel > height? exactly .. they moved up much further -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461609] Widgets in bottom half of screen move upward (and possibly shrink) after each reboot
https://bugs.kde.org/show_bug.cgi?id=461609 --- Comment #3 from dean.yeag...@gmail.com --- (In reply to Nate Graham from comment #2) > If you make your panel thicker or thinner, does the amount of movement > change accordingly? I do not understand what is panel and how to make thicker/thinner -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 461609] Widgets in bottom half of screen move upward (and possibly shrink) after each reboot
https://bugs.kde.org/show_bug.cgi?id=461609 dean.yeag...@gmail.com changed: What|Removed |Added CC||dean.yeag...@gmail.com --- Comment #1 from dean.yeag...@gmail.com --- Created attachment 153600 --> https://bugs.kde.org/attachment.cgi?id=153600=edit Screenshop showint=g starting positions and size of widgets -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 461609] New: Widgets in bottom half of screen move upward (and possibly shrink) after each reboot
https://bugs.kde.org/show_bug.cgi?id=461609 Bug ID: 461609 Summary: Widgets in bottom half of screen move upward (and possibly shrink) after each reboot Classification: Plasma Product: Active Window Control Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: dean.yeag...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 153599 --> https://bugs.kde.org/attachment.cgi?id=153599=edit After reboot widget movement example Widgets on bottom half of screen migrate (and possiably shrink to fit) a bit more after each reboot STEPS TO REPRODUCE 1. lace widgets 2. reboot 3. OBSERVED RESULT widgets move slightly upward on bottom half of screen EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.25.5 (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION 8* AMD Ryzen 7 4700 with Radeon graphics, 15Gb, Renoir graphics processor in SER4 AZW Mini PC attached image shows the memory, Network, Analog Clock, Digital clock, Fuzzy Clock Widgets and the awireguard.sh icon move upward a bit on each reboot. the Memory widget shrinks to accommodate the Network Widget movement -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 461608] Randomly, usually at first snapshot, the Spectacle window is overlays the snapshot-ed window
https://bugs.kde.org/show_bug.cgi?id=461608 dean.yeag...@gmail.com changed: What|Removed |Added CC||dean.yeag...@gmail.com --- Comment #1 from dean.yeag...@gmail.com --- Created attachment 153598 --> https://bugs.kde.org/attachment.cgi?id=153598=edit full screen snapshot example with dolphin window overlaied -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 461608] New: Randomly, usually at first snapshot, the Spectacle window is overlays the snapshot-ed window
https://bugs.kde.org/show_bug.cgi?id=461608 Bug ID: 461608 Summary: Randomly, usually at first snapshot, the Spectacle window is overlays the snapshot-ed window Classification: Applications Product: Spectacle Version: 22.08.1 Platform: Kubuntu OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: dean.yeag...@gmail.com CC: k...@david-redondo.de Target Milestone: --- This occurs randomly and after 3-5 additional snapshots it may produce a non overlaid image. This also occurs with Gwenview and Dolphin of the items I can test. I have sent the full image as it shows only the dolphin part is affected. Delay does not seem to effect it. STEPS TO REPRODUCE 1. start Spectacle 2. select "Take a New Snapshot" 3. the part of the Spectacle window overlays the snapshot area's image OBSERVED RESULT the part of the Spectacle window overlays the snapshot area EXPECTED RESULT image of window SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.25.5 with 5.19.0-23-generic (64-bit) Kernal (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION 8 * AMD Rysen 7 4700, 15Gb, Renoir graphics processor, AZW PC, SER4 series -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 457157] New: Latte crashing when switching from TV to 2monitor config using autorandr
https://bugs.kde.org/show_bug.cgi?id=457157 Bug ID: 457157 Summary: Latte crashing when switching from TV to 2monitor config using autorandr Product: lattedock Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: fort...@gmail.com Target Milestone: --- Application: latte-dock (0.10.77) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.18.12-zen1-1-zen x86_64 Windowing System: X11 Distribution: Garuda Linux DrKonqi: 5.25.3 [KCrashBackend] -- Information about the crash: i have configured autorandr to switch from: 1080p tv single display to 2x1080p led monitor display on hotkey. When i click randomly on latte after that it crashes and restarts. The crash can be reproduced every time. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x7fe94e599cb8 in QScreen::handle() const () at /usr/lib/libQt5Gui.so.5 #5 0x7fe94803cba2 in () at /usr/lib/qt/plugins/xcbglintegrations/libqxcb-glx-integration.so #6 0x7fe94e5baf93 in QOpenGLContext::create() () at /usr/lib/libQt5Gui.so.5 #7 0x7fe94fe1198a in () at /usr/lib/libQt5Quick.so.5 #8 0x7fe94fe15ce4 in () at /usr/lib/libQt5Quick.so.5 #9 0x7fe94dec72ca in () at /usr/lib/libQt5Core.so.5 #10 0x7fe94d94554d in () at /usr/lib/libc.so.6 #11 0x7fe94d9ca874 in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7fe8e59f2640 (LWP 201790) "QSGRenderThread"): #1 0x7fe94d944920 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7fe94dece744 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #3 0x7fe94fe160d3 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fe94dec72ca in () at /usr/lib/libQt5Core.so.5 #5 0x7fe94d94554d in () at /usr/lib/libc.so.6 #6 0x7fe94d9ca874 in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7fe8e61f3640 (LWP 201766) "threaded-ml"): #1 0x7fe9177dd8c7 in () at /usr/lib/libpulse.so.0 #2 0x7fe9177c746c in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #3 0x7fe9177d142c in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7fe9177d14e1 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7fe9177e1c02 in () at /usr/lib/libpulse.so.0 #6 0x7fe91777dc47 in () at /usr/lib/pulseaudio/libpulsecommon-16.1.so #7 0x7fe94d94554d in () at /usr/lib/libc.so.6 #8 0x7fe94d9ca874 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7fe8f8d8c640 (LWP 201756) "QSGRenderThread"): #1 0x7fe94d944920 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7fe94dece744 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #3 0x7fe94fe160d3 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fe94dec72ca in () at /usr/lib/libQt5Core.so.5 #5 0x7fe94d94554d in () at /usr/lib/libc.so.6 #6 0x7fe94d9ca874 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7fe8fa0c4640 (LWP 201755) "QSGRenderThread"): #1 0x7fe94d944920 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7fe94dece744 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #3 0x7fe94fe160d3 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fe94dec72ca in () at /usr/lib/libQt5Core.so.5 #5 0x7fe94d94554d in () at /usr/lib/libc.so.6 #6 0x7fe94d9ca874 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fe8fab06640 (LWP 201754) "CPMMListener"): #1 0x7fe936122dac in () at /usr/lib/libnvidia-glcore.so.515.57 #2 0x7fe9360bd7c4 in () at /usr/lib/libnvidia-glcore.so.515.57 #3 0x7fe9360bdada in () at /usr/lib/libnvidia-glcore.so.515.57 #4 0x7fe9360bb3da in () at /usr/lib/libnvidia-glcore.so.515.57 #5 0x7fe94d94554d in () at /usr/lib/libc.so.6 #6 0x7fe94d9ca874 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fe8fb748640 (LWP 201753) "QSGRenderThread"): #1 0x7fe94d944920 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7fe94dece744 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #3 0x7fe94fe160d3 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fe94dec72ca in () at /usr/lib/libQt5Core.so.5 #5 0x7fe94d94554d in () at /usr/lib/libc.so.6 #6 0x7fe94d9ca874 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fe914d1e640 (LWP 201749) "KCupsConnection"): #1 0x7fe94c38cf68 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fe94c334392 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fe94e0ba34f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe94e06827c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fe94deca49f in QThread::exec() () at
[Discover] [Bug 455055] System Software update entry keep appearing even if the package has been updated or doesn't have an update
https://bugs.kde.org/show_bug.cgi?id=455055 --- Comment #4 from Dean --- (In reply to Nate Graham from comment #3) > So PackageKit does think that there are available updates. This is where > Discover gets its information from, so if there's a mismatch, you'll need to > report an issue to that library's developer at > https://github.com/PackageKit/PackageKit/issues. > > The reason why Pamac agrees with `pacman` is because it directly talks to > `pacman` rather than going through the PackageKit abstraction library. Ah I see, will do -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 455055] System Software update entry keep appearing even if the package has been updated or doesn't have an update
https://bugs.kde.org/show_bug.cgi?id=455055 Dean changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Dean --- (In reply to Nate Graham from comment #1) > What does `pkcon get-updates` say? Getting updates [=] Finished [=] Normal python-pyqt5-5.15.6-7.1.x86_64 (extra) A set of Python bindings for the Qt5 toolkit Normal taglib-extras-1.0.1-7.0.x86_64 (community) Additional taglib plugins -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 455055] New: System Software update entry keep appearing even if the package has been updated or doesn't have an update
https://bugs.kde.org/show_bug.cgi?id=455055 Bug ID: 455055 Summary: System Software update entry keep appearing even if the package has been updated or doesn't have an update Product: Discover Version: 5.24.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updates (interactive) Assignee: lei...@leinir.dk Reporter: programmer.pesesoft+...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 149562 --> https://bugs.kde.org/attachment.cgi?id=149562=edit A screenshot showing pacman -Syyu result, pamac update screen and Discover update screen SUMMARY Some of the package entry in the Update section, specifically on the System Software group is always listed, even if the package has been updated or doesn't have any update. In my case, it is "python-pyqt5" and recently there's another entry which is "taglib-extras" STEPS TO REPRODUCE 1. Open Discover 2. Go to the Update section 3. Check for Update 4. Update packages 5. Check for Update OBSERVED RESULT Some entry (python-pyqt5 and taglib-extras in this case) is still listed even if it has been updated through Discover or other Package Managers like Pacman or pamac, or even if it doesn't have any update or are already up to date. EXPECTED RESULT There is should no updated package entry. SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Manjaro KDE KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION This is the console log from startup to click the "Update" section: ``` qrc:/qml/DiscoverWindow.qml:116:19: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 15. Use 'sequences: [ ]' to bind to all of them. qrc:/qml/DiscoverPage.qml:42:37: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 15. Use 'sequences: [ ]' to bind to all of them. adding empty sources model QStandardItemModel(0x559179265dc0) org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend" file:///usr/lib/qt/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5: QML Binding: Binding loop detected for property "value" Fwupd Error 10 no metadata URIs for vendor-directory qml: message: no metadata URIs for vendor-directory ** (process:50767): WARNING **: 05:55:01.274: Found icon of unknown type 'unknown' in 'system/flatpak/flatpak/cc.nift.nsm/*', skipping it. ** (process:50767): WARNING **: 05:55:01.274: Found icon of unknown type 'unknown' in 'system/flatpak/flatpak/cc.nift.nsm/*', skipping it. kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_aspell.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_aspell.so: (libaspell.so.15: cannot open shared object file: No such file or directory)" kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so: (libhspell.so.0: cannot open shared object file: No such file or directory)" kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so: (libvoikko.so.1: cannot open shared object file: No such file or directory)" kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_aspell.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_aspell.so: (libaspell.so.15: cannot open shared object file: No such file or directory)" kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so: (libhspell.so.0: cannot open shared object file: No such file or directory)" kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so: (libvoikko.so.1: cannot open shared object file: No such file or directory)" qrc:/qml/DiscoverPage.qml:42:37: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 15. Use 'sequences: [ ]' to bind to all of them. ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455039] Clipboard content cannot be pasted if the application of the content is closed before pasting
https://bugs.kde.org/show_bug.cgi?id=455039 --- Comment #4 from Dean --- (In reply to Dean from comment #3) > (In reply to Dean from comment #2) > > (In reply to Nate Graham from comment #1) > > > Have you set your clipboard history to be "0" or disabled the "Clipboard" > > > System Tray applet? > > > > I don't know where to "Disable Clipboard" but my Clipboard History is set to > > 20 (I think it is the default) > > If what you meant is the System Tray Settings -> Entries -> Clipboard, then > no, I set it to Always Shown I think I found the cause, so the System Tray applet is added to Latte Dock Panel, and since I'm curious tried to disable every shortcut from Klipper on this system tray, and then add a new default plasma panel (not Latte Dock) and add System Tray applet there and set up the shortcut key for the Klipper, while the Latte Dock panel still have the System Tray applet, it still happened, the content can't be pasted. And then I remove the whole System Tray applet from the Latte Dock, and now it is working as it should be. So I think the bug is related to Latte Dock, should I re-report this to Latte Dock? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455039] Clipboard content cannot be pasted if the application of the content is closed before pasting
https://bugs.kde.org/show_bug.cgi?id=455039 --- Comment #3 from Dean --- (In reply to Dean from comment #2) > (In reply to Nate Graham from comment #1) > > Have you set your clipboard history to be "0" or disabled the "Clipboard" > > System Tray applet? > > I don't know where to "Disable Clipboard" but my Clipboard History is set to > 20 (I think it is the default) If what you meant is the System Tray Settings -> Entries -> Clipboard, then no, I set it to Always Shown -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455039] Clipboard content cannot be pasted if the application of the content is closed before pasting
https://bugs.kde.org/show_bug.cgi?id=455039 --- Comment #2 from Dean --- (In reply to Nate Graham from comment #1) > Have you set your clipboard history to be "0" or disabled the "Clipboard" > System Tray applet? I don't know where to "Disable Clipboard" but my Clipboard History is set to 20 (I think it is the default) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455039] Clipboard content cannot be pasted if the application of the content is closed before pasting
https://bugs.kde.org/show_bug.cgi?id=455039 Dean changed: What|Removed |Added Summary|Clipboard content cannot be |Clipboard content cannot be |pasted if the application |pasted if the application |of the content is closed|of the content is closed ||before pasting -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455039] Clipboard content cannot be pasted if the application of the content is closed
https://bugs.kde.org/show_bug.cgi?id=455039 Dean changed: What|Removed |Added Summary|Clipboard content cannot be |Clipboard content cannot be |pasted if the source of the |pasted if the application |content being copied/cut is |of the content is closed |closed (e.g by CTRL+Q quit | |or similar) | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455039] New: Clipboard content cannot be pasted if the source of the content being copied/cut is closed (e.g by CTRL+Q quit or similar)
https://bugs.kde.org/show_bug.cgi?id=455039 Bug ID: 455039 Summary: Clipboard content cannot be pasted if the source of the content being copied/cut is closed (e.g by CTRL+Q quit or similar) Product: plasmashell Version: 5.24.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: programmer.pesesoft+...@gmail.com Target Milestone: 1.0 SUMMARY The clipboard content, be it Text or Image (should also happen to file reference like copying a file from Dolphin), cannot be pasted if the application where the content comes from (be it from Copy or Cut) is closed, even if the content is listed on the popup menu. It however can still be pasted if we open the popup (Open Klipper at Mouse Position) and select the content, then paste. STEPS TO REPRODUCE # Text 1. Open KWrite 2. Open Kate 3. Write something, for example, "Hello World" into either KWrite or Kate, let's use Kate for simplicity 4. Select all the text and either Copy or Cut 5. Close Kate, if asked, discard/don't save the content 6. Go to/focus on KWrite 7. Try to paste the content (Right Click Paste or CTRL + V) # Image 1. Take a screenshot using spectacle, either by opening the app or through a keyboard shortcut 2. If opening the app or the shortcut is opening the spectacle dialog, save the content to the clipboard and close the spectacle 3. Try to paste the content to GIMP, Discord, Krita, or any program that accepts an image OBSERVED RESULT Nothing is being pasted, either by Context menu or Keyboard Shortcut, it can still be pasted by opening Klipper at the cursor position, selecting the first entry (which is the previously copied/cut content) and then trying to paste again either using Context Menu or Keyboard Shortcut EXPECTED RESULT The content should be still being pasted regardless if the source application is closed or not SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Manjaro KDE KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION This is the recording of the bug https://streamable.com/tz5p9w -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 455035] "Up" action should preserve the selected folder just like the "Back" action
https://bugs.kde.org/show_bug.cgi?id=455035 --- Comment #1 from Dean --- I'm sorry for being out of topic, I wish we have the ability to edit the detail of the bug as I create some typos and grammar mistakes and can't seem to find an edit anchor to edit the content, so I apologize for the badly written content on this one. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 455035] New: "Up" action should preserve the selected folder just like the "Back" action
https://bugs.kde.org/show_bug.cgi?id=455035 Bug ID: 455035 Summary: "Up" action should preserve the selected folder just like the "Back" action Product: dolphin Version: 22.04.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: programmer.pesesoft+...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Whenever you press or invoke "Up" action from the toolbar button or using a shortcut (e.g. Alt+Up), the previously selected (and focused/entered) directory is not preserved and instead being reset, so when you press any arrow key, the selection will start from the very first item instead of the previously selected, focused/entered directory. Which basically the same behaviour as the Back action, because when you go back either pressing the toolbar button or using shortcut (e.g Alt+Left, Backspace) the previously selected directory is still selected. Yes I know the actual behaviour is quite different as Back means back from where we came from as for Up is going up the directory tree, so I just want the "previously entered directory" is preselected when we go "Up" STEPS TO REPRODUCE 1. Open a directory, preferably any directory that is in the middle of the view 2. Go Up 3. Press any cursor to select a directory, e.g Right OBSERVED RESULT - The selected directory is reset to the very first item, so when you are traversing a directory manually and press Up, you have to manually select the last directory which is annoying and tedious EXPECTED RESULT - The previously entered directory is preselected just like when using Back action SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Manjaro KDE KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 211416] Optimise kde performance on nfs
https://bugs.kde.org/show_bug.cgi?id=211416 --- Comment #25 from Dean Montogmery --- (In reply to Daniel Moyne from comment #24) > not sure it is related to this bug ; since installation of version 20.04 it > is impossible to establish an nfs connection betwenne 2 computers on my lan Sorry Daniel, your problem is unrelated to kde and nfs optimizations. We have been using 20.04 for several years with an nfs diskless filesystem. You will have to post your question on an nfs support group page. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443410] Please restore the Desktop Cube switching effect
https://bugs.kde.org/show_bug.cgi?id=443410 --- Comment #29 from Dean Schaf --- 2011-11-05 Still no Flip-Switch and still no 3-D Desktop Cube They're forever dead! Every Friday, I yearn to report that Flip-Switch and 3-D Desktop Cube are still dead so that I can maintain my melancholy despondency about the demise of KDE. Farewell noble services. You were loved dearly, but the powers that be hate you because you brought your users joy. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 444190] New: kcmshell5 kcm_users Does Nothing!
https://bugs.kde.org/show_bug.cgi?id=444190 Bug ID: 444190 Summary: kcmshell5 kcm_users Does Nothing! Product: kde Version: unspecified Platform: PCLinuxOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: deanyourfriendi...@yahoo.com Target Milestone: --- I searched, but could not find a bug-category for kcmshell5, let alone kcmshell5 kcm_users. STEPS TO REPRODUCE 01. Open a terminal 02. Type: kcmshell5 kcm_users 03. On your computer's keyboard, press-n-release: Enter 04. In the window that opens, left-click the button labelled: Add New User 05. In the box labelled Name, type a person's name 06. In the box labelled Username, type a sensible user-name 07. In the drop-down list labelled Account, choose Standard 08. In the box labelled Password, type a password 09. In the box labelled Confirm password, type the same password used in step 8 10. Left-click the button labelled: Create 11. Open another terminal and type: ls -lh /home 12. On your computer's keyboard, press-n-release: Enter Observe that no new user has been created using the User Management module of kcmshell5, at least not in the /home directory. OBSERVED RESULT No new users are created using the module kcmshell5 kcm_users EXPECTED RESULT New users should be created using the module kcmshell5 kcm_users SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.14.14/5.23.1 (available in About System) KDE Plasma Version: 5.23.1 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Aside from seeing that no user directory is created in /home for users that are "created" in kcmshell5 kcm_users, one can also open the Control Center (in my fave distro), click on "Manage users on system", and see that no new user is created using the kcmshell5 kcm_users module. I should very, very, very much genuinely appreciate it if you kindly KDE/Plasma folks could pretty please with sugar on top rip out the code for kcmshell5 kcm_users (the work of which is already done [in the distro I use] quite nicely by userdrake) and put the new code for a modern, highly polished, incredibly user-configurable and glitzy version of Desktop Cube and Flip Switch back into KDE/Plasma. None of the Bug IDs listed as Possible Duplicates (which appeared below where I typed this bug report) [BugIDs: 337230, 342588, 382874, 384107, 411758, 432838] list the same problem as the one I'm reporting in above. 423221, Incalculably appreciatively, Dean -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438883] Re-implement Desktop Cobe effect with modern effects API
https://bugs.kde.org/show_bug.cgi?id=438883 Dean Schaf changed: What|Removed |Added CC||deanyourfriendi...@yahoo.co ||m --- Comment #11 from Dean Schaf --- I am very disappointed that you have removed the coolest eye-candy features from KDE Plasma, (Flip Switch and Desktop Cube). They were two of the gems that made me like KDE. I used the glitz-n-glam features since long ago, and now my KDE Plasma usage is utterly boring, disjointed, and ugly. Please bring back the 3-D Desktop Cube and Flip Switch (in all their former glory). Dismayed and gloomy, Keltonix -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443410] Please restore the Desktop Cube switching effect
https://bugs.kde.org/show_bug.cgi?id=443410 Dean Schaf changed: What|Removed |Added Platform|unspecified |PCLinuxOS CC||deanyourfriendi...@yahoo.co ||m --- Comment #2 from Dean Schaf --- I should like to know why you're intending to remove the "Desktop Cube" from KDE Plasma? That feature is one of the things that first drew me into KDE. I use the "Desktop Cube" to organize all the programs that I keep open and to flip between them with keyboard shortcuts that I have become used to using. I don't want you to remove the "Desktop Cube". Of course, since tyrannical dictatorship is the order of the day, and you've probably already made up your dictatorial little minds to remove "Desktop Cube", you'll just have more glee the more people you disappoint. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430947] Can't find my Windows 10 Samba share in smb:/
https://bugs.kde.org/show_bug.cgi?id=430947 Dean changed: What|Removed |Added CC||deano_ferr...@hotmail.com --- Comment #26 from Dean --- (In reply to Nate Graham from comment #25) > Harald had a brainwave and suggested that I disable the firewall with > systemctl stop firewalld.service, and then the share was discovered! It > turns out that this was an openSUSE bug all along because they are currently > blacklisting the wsdd service in the default firewall configuration. I have > filed https://bugzilla.opensuse.org/show_bug.cgi?id=1183995. > > Sorry for the wile goose chase. :( I found the following rule is required to allow Windows hosts to be discovered by WSD when firewalld is active... firewall-cmd --permanent --zone=public --add-source-port=3702/udp -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421053] New: SystemSettings crashed when attempting to edit Plastik settings
https://bugs.kde.org/show_bug.cgi?id=421053 Bug ID: 421053 Summary: SystemSettings crashed when attempting to edit Plastik settings Product: systemsettings Version: 5.17.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dean_jenk...@mentor.com Target Milestone: --- Application: systemsettings5 (5.17.5) Qt Version: 5.13.2 Frameworks Version: 5.68.0 Operating System: Linux 5.6.8-200.fc31.x86_64 x86_64 Distribution: "Fedora release 31 (Thirty One)" -- Information about the crash: - What I was doing when the application crashed: I started systemsettings5 from the command line to view any error messages. Using the "System Settings" GUI, navigate to Appearance -> Application Style -> Window Decorations. Clicked on the Plastik icon to edit the settings, and crash occurs. - Unusual behavior I noticed: I wanted to edit the Plastik settings as the Konsole window had no border width which was annoying me. Running systemsettings5 from the command line showed the following errors reported including a problem concerning border width. $ systemsettings5 QQmlEngine::setContextForObject(): Object already has a QQmlContext Couldn't load plugin: "The shared library was not found." QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib64/qt5/qml/org/kde/kcm/GridDelegate.qml:206: TypeError: Cannot read property 'pointSize' of undefined Module 'org.kde.kwin.decoration' does not contain a module identifier directive - it cannot be protected from external registrations. file:///usr/share/kwin/decorations/kwin4_decoration_qml_plastik/contents/ui/main.qml:92: TypeError: Cannot read property 'borderSize' of null file:///usr/lib64/qt5/qml/org/kde/kwin/decoration/MenuButton.qml:22: TypeError: Cannot read property 'closeOnDoubleClickOnMenu' of null file:///usr/lib64/qt5/qml/org/kde/kwin/decoration/MenuButton.qml:22: TypeError: Cannot read property 'closeOnDoubleClickOnMenu' of null file:///usr/share/kwin/decorations/kwin4_decoration_qml_plastik/contents/ui/main.qml:92: TypeError: Cannot read property 'borderSize' of null file:///usr/share/kwin/decorations/kwin4_decoration_qml_plastik/contents/ui/main.qml:92: TypeError: Cannot read property 'borderSize' of null file:///usr/lib64/qt5/qml/org/kde/kwin/decoration/MenuButton.qml:22: TypeError: Cannot read property 'closeOnDoubleClickOnMenu' of null file:///usr/lib64/qt5/qml/org/kde/kcm/GridDelegate.qml:206: TypeError: Cannot read property 'pointSize' of undefined file:///usr/lib64/qt5/qml/org/kde/kcm/GridDelegate.qml:206: TypeError: Cannot read property 'pointSize' of undefined file:///usr/lib64/qt5/qml/org/kde/kwin/decoration/MenuButton.qml:22: TypeError: Cannot read property 'closeOnDoubleClickOnMenu' of null file:///usr/share/kwin/decorations/kwin4_decoration_qml_plastik/contents/ui/main.qml:92: TypeError: Cannot read property 'borderSize' of null file:///usr/lib64/qt5/qml/org/kde/kwin/decoration/MenuButton.qml:22: TypeError: Cannot read property 'closeOnDoubleClickOnMenu' of null file:///usr/share/kwin/decorations/kwin4_decoration_qml_plastik/contents/ui/main.qml:92: TypeError: Cannot read property 'borderSize' of null file:///usr/share/kwin/decorations/kwin4_decoration_qml_plastik/contents/ui/main.qml:92: TypeError: Cannot read property 'borderSize' of null file:///usr/lib64/qt5/qml/org/kde/kwin/decoration/MenuButton.qml:22: TypeError: Cannot read property 'closeOnDoubleClickOnMenu' of null file:///usr/lib64/qt5/qml/org/kde/kwin/decoration/MenuButton.qml:22: TypeError: Cannot read property 'closeOnDoubleClickOnMenu' of null file:///usr/share/kwin/decorations/kwin4_decoration_qml_plastik/contents/ui/main.qml:92: TypeError: Cannot read property 'borderSize' of null file:///usr/lib64/qt5/qml/org/kde/kwin/decoration/MenuButton.qml:22: TypeError: Cannot read property 'closeOnDoubleClickOnMenu' of null file:///usr/share/kwin/decorations/kwin4_decoration_qml_plastik/contents/ui/main.qml:92: TypeError: Cannot read property 'borderSize' of null file:///usr/lib64/qt5/qml/org/kde/kwin/decoration/MenuButton.qml:22: TypeError: Cannot read property 'closeOnDoubleClickOnMenu' of null file:///usr/share/kwin/decorations/kwin4_decoration_qml_plastik/contents/ui/main.qml:92: TypeError: Cannot read property 'borderSize' of null file:///usr/share/kwin/decorations/kwin4_decoration_qml_plastik/contents/ui/main.qml:92: TypeError: Cannot read property 'borderSize' of null file:///usr/lib64/qt5/qml/org/kde/kwin/decoration/MenuButton.qml:22: TypeError: Cannot read property 'closeOnDoubleClickOnMenu' of null file:///usr/lib64/qt5/qml/org/kde/kcm/GridDelegate.qml:206: TypeError: Cannot read property 'pointSize' of undefined file:///usr/lib64/qt5/qml/org/kde/kcm/GridDelegate.qml:206: TypeError: Cannot read
[Discover] [Bug 415059] New: Frozen/Crashed - "Discovery Software Center"
https://bugs.kde.org/show_bug.cgi?id=415059 Bug ID: 415059 Summary: Frozen/Crashed - "Discovery Software Center" Product: Discover Version: 5.14.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: ma.moody.dev.wo...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.14.5) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-7-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: - What I was doing when the application crashed: I was browsing through the program menu's and the application froze. Then without any other report it crashed and I was given a notification that it unexpected closed. Thanks for looking into it.! -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f921472a800 (LWP 9891))] Thread 12 (Thread 0x7f91daffe700 (LWP 10006)): #0 0x7f9216fc2e69 in g_mutex_lock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f9216f78140 in g_main_context_acquire () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9216f78ff5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9216f7925c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9218a547b3 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9218a021cb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9218851e96 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f921885ba87 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f92179f4fa3 in start_thread (arg=) at pthread_create.c:486 #9 0x7f921854b4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f91f2df9700 (LWP 10005)): #0 0x7f9218540819 in __GI___poll (fds=0x7f91e8000b20, nfds=1, timeout=97533) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f9216f79136 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9216f7925c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9218a547b3 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9218a021cb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9218851e96 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f921885ba87 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f92179f4fa3 in start_thread (arg=) at pthread_create.c:486 #8 0x7f921854b4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f91dbfff700 (LWP 9930)): #0 0x7f921853c494 in __GI___libc_read (nbytes=16, buf=0x7f91dbffeb80, fd=30) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7f921853c494 in __GI___libc_read (fd=30, buf=0x7f91dbffeb80, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f9216fbeaa0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9216f78c0f in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9216f790e0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9216f7925c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f9218a547b3 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9218a021cb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9218851e96 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f921885ba87 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f92179f4fa3 in start_thread (arg=) at pthread_create.c:486 #11 0x7f921854b4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f91f101e700 (LWP 9904)): #0 0x7f9218540819 in __GI___poll (fds=0x557ec92d3450, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f9216f79136 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9216f794c2 in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f91f225b266 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f9216fa1415 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f92179f4fa3 in start_thread (arg=) at pthread_create.c:486 #6 0x7f921854b4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f91f181f700 (LWP 9903)): #0 0x7f9216f78cd2 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f9216f791c8 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9216f7925c in
[docs] [Bug 399426] New: Display and Monitor Conpositor documentation missing from Help Menu
https://bugs.kde.org/show_bug.cgi?id=399426 Bug ID: 399426 Summary: Display and Monitor Conpositor documentation missing from Help Menu Product: docs Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Missing Content Assignee: kde-doc-engl...@kde.org Reporter: deano_ferr...@hotmail.com Target Milestone: --- SUMMARY No Compositor help information present in KDE Plasma 5 (v 5.12.6) documentation. I did find KDE 4 documentation that is largely still applicable and could be incorporated? https://userbase.kde.org/Desktop_Effects_Performance#OpenGL_mode STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE VERSIONS (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.
[frameworks-kio] [Bug 372029] When you call the network:/ then systems take about 5 minutes discover
https://bugs.kde.org/show_bug.cgi?id=372029 --- Comment #6 from Dean --- (In reply to Dean from comment #5) > I can also confirm that when using 'network:/' and 'zeroconf:/' to discover > Avahi services, Dolphin is not working as expected. Refreshing (with F5) > sometimes helps with zeroconf:/, but it is not consistent. Interestingly, > using Gnome's Nautilus file manager does find the 'missing' remote shares > consistently. I would like to know what the Dolphin KIOs are doing 'under > the hood' that leads to the failure unreliability. I note that when I bounce a remote host's (DHCP) network connectivity, then Dolphin (network:/ KIO) suddenly (more often than not) displays that host as being available, but that seems to be all the only event than can trigger it. Dynamic detection does not seem to be occurring as one would hope. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 372029] When you call the network:/ then systems take about 5 minutes discover
https://bugs.kde.org/show_bug.cgi?id=372029 Dean changed: What|Removed |Added CC||deano_ferr...@hotmail.com --- Comment #5 from Dean --- I can also confirm that when using 'network:/' and 'zeroconf:/' to discover Avahi services, Dolphin is not working as expected. Refreshing (with F5) sometimes helps with zeroconf:/, but it is not consistent. Interestingly, using Gnome's Nautilus file manager does find the 'missing' remote shares consistently. I would like to know what the Dolphin KIOs are doing 'under the hood' that leads to the failure unreliability. I can get a 'complete' discovery output from 'avahi-browse -art' however, so I know all published services are present. If any additional information would help with the process of diagnosing and resolving this issue, I'm keen to assist to help progress it. Dolphin version 17.12.3 KDE Plasma 5.12.5 KDE Framework 5.45.0 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 361764] Cannot add event to calendar with correct time: Add event window will not accept an "A.M." time
https://bugs.kde.org/show_bug.cgi?id=361764 Dean Cording <d...@cording.id.au> changed: What|Removed |Added CC||d...@cording.id.au --- Comment #18 from Dean Cording <d...@cording.id.au> --- Can confirm that the problem with Kontact changing AM times to PM in the Australia timezone is still an issue in Version 5.7.3. Changing the time format in the System Setting Module to 'United Kingdom - British English' is a work-around. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 361764] Cannot add event to calendar with correct time: Add event window will not accept an "A.M." time
https://bugs.kde.org/show_bug.cgi?id=361764 Dean Cording <d...@cording.id.au> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #17 from Dean Cording <d...@cording.id.au> --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 392554] security: escaping from bracketed paste seems to be possible
https://bugs.kde.org/show_bug.cgi?id=392554 Dean Serenevy <d...@serenevy.net> changed: What|Removed |Added CC||d...@serenevy.net --- Comment #4 from Dean Serenevy <d...@serenevy.net> --- FYI, here is a link to the article for non-subscribers (Note: meets their acceptable use policy for links bypassing the paywall): https://lwn.net/SubscriberLink/749992/d3a6b4d1e90c2f39/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388507] El programa se detiene
https://bugs.kde.org/show_bug.cgi?id=388507 Dean Griss <grissam_1...@hotmail.com> changed: What|Removed |Added CC||grissam_1...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388507] New: El programa se detiene
https://bugs.kde.org/show_bug.cgi?id=388507 Bug ID: 388507 Summary: El programa se detiene Product: krita Version: 3.3.2 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: grissam_1...@hotmail.com Target Milestone: --- Cuando quiero guardar los fotogramas de animación o actualizar el caché se detiene el programa y se cierra. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386916] New: Plasma crash on login
https://bugs.kde.org/show_bug.cgi?id=386916 Bug ID: 386916 Summary: Plasma crash on login Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dplin...@netscape.net CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-98-generic x86_64 Distribution: Ubuntu 16.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: Logged in and did nothing else. While dealing with my login, Plasma crashed. -- 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 0x7f6ccf7fc8c0 (LWP 1894))] Thread 7 (Thread 0x7f6c094ad700 (LWP 2142)): #0 0x7f6cc6ceda94 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6cc6ca8db9 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6cc6ca9330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6cc6ca949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6cca8427eb in QEventDispatcherGlib::processEvents (this=0x7f6c040008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f6cca7e9b4a in QEventLoop::exec (this=this@entry=0x7f6c094accc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f6cca606834 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f6c0b98b7d7 in KCupsConnection::run() () from /usr/lib/x86_64-linux-gnu/libkcupslib.so #8 0x7f6cca60b7be in QThreadPrivate::start (arg=0x3243640) at thread/qthread_unix.cpp:331 #9 0x7f6cc96f76ba in start_thread (arg=0x7f6c094ad700) at pthread_create.c:333 #10 0x7f6cc9f213dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f6c9bba5700 (LWP 1969)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6ccf253bd4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f6ccf253c19 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f6cc96f76ba in start_thread (arg=0x7f6c9bba5700) at pthread_create.c:333 #4 0x7f6cc9f213dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f6ca1523700 (LWP 1964)): #0 0x7f6cc9f1570d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f6cc6ca938c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6cc6ca949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6cca8427eb in QEventDispatcherGlib::processEvents (this=0x7f6c940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f6cca7e9b4a in QEventLoop::exec (this=this@entry=0x7f6ca1522ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f6cca606834 in QThread::exec (this=this@entry=0x1c93670) at thread/qthread.cpp:503 #6 0x7f6ccceae3c5 in QQmlThreadPrivate::run (this=0x1c93670) at qml/ftw/qqmlthread.cpp:141 #7 0x7f6cca60b7be in QThreadPrivate::start (arg=0x1c93670) at thread/qthread_unix.cpp:331 #8 0x7f6cc96f76ba in start_thread (arg=0x7f6ca1523700) at pthread_create.c:333 #9 0x7f6cc9f213dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f6ca3390700 (LWP 1958)): #0 0x7f6cc96fe2e8 in __GI___pthread_getspecific (key=3) at pthread_getspecific.c:31 #1 0x7f6cc6cd0060 in g_thread_self () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6cc6ca948d in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6cca8427eb in QEventDispatcherGlib::processEvents (this=0x7f6c9c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f6cca7e9b4a in QEventLoop::exec (this=this@entry=0x7f6ca338fce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f6cca606834 in QThread::exec (this=this@entry=0x1912800) at thread/qthread.cpp:503 #6 0x7f6ccceae3c5 in QQmlThreadPrivate::run (this=0x1912800) at qml/ftw/qqmlthread.cpp:141 #7 0x7f6cca60b7be in QThreadPrivate::start (arg=0x1912800) at thread/qthread_unix.cpp:331 #8 0x7f6cc96f76ba in start_thread (arg=0x7f6ca3390700) at pthread_create.c:333 #9 0x7f6cc9f213dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f6ca7c77700 (LWP 1957)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6cab62c74b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x7f6cab62c477 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x7f6cc96f76ba in
[tellico] [Bug 382409] New: Preview pane does not display thunbnails
https://bugs.kde.org/show_bug.cgi?id=382409 Bug ID: 382409 Summary: Preview pane does not display thunbnails Product: tellico Version: 3.0.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ro...@periapsis.org Reporter: d...@defreitas.net Target Milestone: --- Created attachment 106669 --> https://bugs.kde.org/attachment.cgi?id=106669=edit Screenshot The preview pane (bottom right) does not display thumbnails when built on Fedora 24 system. See attached screenshot. Same issue was noted on both 3.0 and 3.0.1 as well. Environment: KDE Frameworks 5.33.0 Qt 5.6.2 (built against 5.6.2) The xcb windowing system plasma-workspace-common-5.8.7-1.fc24.x86_64 Linux (x86_64) release 4.11.9-100.fc24.x86_64 These are the only optional components not compiled in: -- The following OPTIONAL packages have not been found: * KF5Cddb , Support for CDDB searches , <https://cgit.kde.org/libkcddb.git> * Btparse , External support for parsing and processing BibTeX data files , <https://metacpan.org/release/Text-BibTeX> Build process: mkdir build && cd build cmake .. -DCMAKE_INSTALL_PREFIX=/usr && make -j5 && sudo make install This is the only issue keeping me migrating from tellico-2.3.11-1.fc24.x86_64 in the Fedora repositories. All other functionality works as expected thus far. Dean -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 381511] GeoDataLineString::setTessellate function fails to unset tessellation.
https://bugs.kde.org/show_bug.cgi?id=381511 --- Comment #3 from Dean Adamson <dadamson.dumping.gro...@gmail.com> --- I tried to add a view request but I need a login for that and I can not find any place for me to create my own login at http://phabricator.kde.org. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 381511] GeoDataLineString::setTessellate function fails to unset tessellation.
https://bugs.kde.org/show_bug.cgi?id=381511 --- Comment #1 from Dean Adamson <dadamson.dumping.gro...@gmail.com> --- Happy to fix this my self if someone would pass me the instructions on how to submit my changes. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 381511] New: GeoDataLineString::setTessellate function fails to unset tessellation.
https://bugs.kde.org/show_bug.cgi?id=381511
Bug ID: 381511
Summary: GeoDataLineString::setTessellate function fails to
unset tessellation.
Product: marble
Version: unspecified
Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: marble-b...@kde.org
Reporter: dadamson.dumping.gro...@gmail.com
Target Milestone: ---
When you pass in false into the function GeoDataLineString::setTessellate in
GeoDataLineString.cpp lines 478-493, it can actually set tessellation on
instead of off. This happens because the function is using a xor operator when
it should be using an and operator. See below:
if ( tessellate ) {
p()->m_tessellationFlags |= Tessellate;
p()->m_tessellationFlags |= RespectLatitudeCircle;
} else {
p()->m_tessellationFlags ^= Tessellate;
p()->m_tessellationFlags ^= RespectLatitudeCircle;
}
The above should really be the following:
if ( tessellate ) {
p()->m_tessellationFlags |= (Tessellate | RespectLatitudeCircle);
} else {
p()->m_tessellationFlags &= ~(Tessellate | RespectLatitudeCircle);
}
--
You are receiving this mail because:
You are watching all bug changes.
[kde] [Bug 372498] New: plasmashell-20161115-035507.kcrash
https://bugs.kde.org/show_bug.cgi?id=372498 Bug ID: 372498 Summary: plasmashell-20161115-035507.kcrash Product: kde Version: unspecified Platform: PCLinuxOS OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: deanyourfriendi...@yahoo.com Target Milestone: --- Created attachment 102244 --> https://bugs.kde.org/attachment.cgi?id=102244=edit A text file generated by the crash reporting assistant Listen. I love KDE. I love GNU/Linux. I hate the crash reporter. The KDE crash reporting assistant NEVER produces a useful backtrace when I awake my computer from sleep. EVERY time I awake my computer from sleep, KDE crashes and automagically restarts. The only reason I know that there has been a crash is because of the lady-bug-looking icon in the systray. You should either revamp the KDE crash reporting assistant, so that it works, or eliminate it. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 372266] New: plasmashell crash (on resume from sleep)
https://bugs.kde.org/show_bug.cgi?id=372266 Bug ID: 372266 Summary: plasmashell crash (on resume from sleep) Product: kde Version: unspecified Platform: PCLinuxOS OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: deanyourfriendi...@yahoo.com Target Milestone: --- Created attachment 102153 --> https://bugs.kde.org/attachment.cgi?id=102153=edit Text file with allegedly relevant info about the crash Application: plasmashell (5.8.3) Qt Version: 5.6.2 Frameworks Version: 5.27.0 Operating System: Linux 4.8.6-pclos1 x86_64 Distribution: "PCLinuxOS" -- Information about the crash: The crash can be reproduced every time. -- Backtrace: A useful backtrace could not be generated BUT HERE'S WHAT WAS HAPPENING WHEN THE CRASH OCCURRED: I had put the computer on standby (sleep). When I came back to use it and woke it up, I was greeted with the notification that the plasmashell had crashed. And, I was given the chance to report the bug. Tragically, the bug-report creation system is an epic failure, so I put this silly blurb together just for Esses & Gees. Report to https://bugs.kde.org/ Application: Plasma (plasmashell), signal: Segmentation fault [Current thread is 1 (process 3452)] Thread 1 (process 3452): #0 0x7fac7aa7467f in ?? () #1 0x in ?? () About The System SOFTWARE KDE Framworks Version: 5.27.0 Qt Version: 5.6.2 Kernel Version: 4.8.6-pclos1 OS Type: 64-bit HARDWARE CPU: AMD Athlon(tm) X4 860K Quad-Core Processor RAM: 16 GBs (2 x 8 GBs) DISKS: * sda Seagate ST3750528S HDD ⱺ sda1 . Linux Swap ⱺ sda2 . ext4 * sdb Seagate ST3320620AS HDD ⱺ sdb1 . ext4 * sdc SanDisk SDSSDA120G SSD ⱺ sdc1 . ext4 / ⱺ sdc2 . ext4 /home GRAPHICAL INFORMATION Server Information Name of the Display::0 Vendor String: The X.Org Foundation Vendor Release Number: 11,804,000 Version Number: 11.0 Display Adapter: nVidia GeForce GT 610 GC LP 2GB DDR3 64BIT Motherboard: MSI A58M-E33 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368209] New: Plasma crash after creating USB partition
https://bugs.kde.org/show_bug.cgi?id=368209 Bug ID: 368209 Summary: Plasma crash after creating USB partition Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dplin...@netscape.net CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-34-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: Created fat32 partition on USB drive using KDE Partition Manager. This may be a dup of 346517, but the crash reporting assistant did not respond properly. After indicating that my crash is related to 346517, the asistant was upset that I had not selected a related crash. I had, so it was confused. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ffbb4def8c0 (LWP 3519))] Thread 12 (Thread 0x7ffad98e8700 (LWP 3862)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7ffbafbfdaeb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x3be2a60) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x4355b10, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7ffafa2d92bf in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7ffafa2dd4e8 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7ffafa2d846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7ffafa2dd542 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7ffafa2d846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7ffafa2dd542 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7ffafa2d846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7ffafa2dd542 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7ffafa2d846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7ffafa2dd542 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #13 0x7ffafa2d846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #14 0x7ffafa2db353 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #15 0x7ffbafbfc84e in QThreadPrivate::start (arg=0x433f490) at thread/qthread_unix.cpp:331 #16 0x7ffbaece96fa in start_thread (arg=0x7ffad98e8700) at pthread_create.c:333 #17 0x7ffbaf512b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7ffada0e9700 (LWP 3861)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7ffbafbfdaeb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x3be2a60) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x4355b10, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7ffafa2d92bf in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7ffafa2dd4e8 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7ffafa2d846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7ffafa2dd542 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7ffafa2d846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7ffafa2dd542 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7ffafa2d846d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7ffafa2db353 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7ffbafbfc84e in QThreadPrivate::start (arg=0x7ffad4003190) at thread/qthread_unix.cpp:331 #12 0x7ffbaece96fa in start_thread (arg=0x7ffada0e9700) at pthread_create.c:333 #13 0x7ffbaf512b5d in clone () at
[dolphin] [Bug 361694] The search (Find) function in Dolphin is useless, doesn't return results as it should
https://bugs.kde.org/show_bug.cgi?id=361694 Dean <deanpac...@yahoo.co.uk> changed: What|Removed |Added CC||deanpac...@yahoo.co.uk --- Comment #7 from Dean <deanpac...@yahoo.co.uk> --- Having had numerous issues with Dolphin I now find that after upgrading the libkf5plasma5 package to 5.23 as a fix to other desktop issues, Dolphin has started working for me again.. Admittedly it is dog-slow, but it seems to work for searches in mounted volumes and user accounts. I started a search in root and will probably need another shave by the time it returns, assuming it ever does. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365214] New: No widget context menu on widgets after plasma 5 update
https://bugs.kde.org/show_bug.cgi?id=365214 Bug ID: 365214 Summary: No widget context menu on widgets after plasma 5 update Product: plasmashell Version: master Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: deanpac...@yahoo.co.uk CC: plasma-b...@kde.org Since updating plasma desktop to 4:5.6.5-1, the context menu on unlocked widgets no longer appears when the mouse is right clicked. First noticed on the application menu as the menu can no longer be accessed to edit the content or to create or re-sequence the menu items but other widget context menus (e.g. on the waste basket) are no longer available. Behaviour does not change irrespective of whether widgets are locked or not. Reproducible: Always Steps to Reproduce: 1. Right click on any widget. 2. 3. Actual Results: No context menu with widgets locked or unlocked. Expected Results: Context menu to edit settings. -- You are receiving this mail because: You are watching all bug changes.
