[dolphin] [Bug 447580] Dolphin ignores umask
https://bugs.kde.org/show_bug.cgi?id=447580 J changed: What|Removed |Added CC||j...@automatix.de -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 447580] Dolphin ignores umask
https://bugs.kde.org/show_bug.cgi?id=447580 --- Comment #1 from J --- This Bug hits also, if the umask was set in global Xsession, or xprofile. Testet on current Arch Linux. This bug seems to be critc to us, beacuse the company shares it's documents classical using NFS. Not all employees are able to set the right permissions during the work. So this bug makes a lot of trouble. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 447580] Dolphin ignores umask
https://bugs.kde.org/show_bug.cgi?id=447580 J changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468609] New: Loads heif only with 8 bits color depth
https://bugs.kde.org/show_bug.cgi?id=468609 Bug ID: 468609 Summary: Loads heif only with 8 bits color depth Classification: Applications Product: digikam Version: 8.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ImageEditor-Load Assignee: digikam-bugs-n...@kde.org Reporter: i...@j-pfennig.de Target Milestone: --- Currently tiff and jpeg2000 images with > 8 bit color depth load correctly, but this does not work with heif. Heif images are implictly converted to 8 bit depth (probably the same happens with jpeg xl). Also Exif data seems to be ignored on load. How to reproduce 1) I prepared some test images, see https://drive.google.com/drive/folders/1ughS3RvBTwBNac0EF_i6jPtkicxw_U0a?usp=sharing (170 MByte) That folder also includes a tool to convert images using IM 7.x, a test script and some documentation. 2) IM legacy (6.9) does not create >8 bit heif! You need IM 7.x (I used 7.1). Debian/Ubuntu still distribute 6.9. 3) KDE/digikam use libtiff which supports only 8/16 depth. Oly IM would handle other tuple sizes correctly. The 10-bit tiff test image therefore is physically 16-bit and masks-out the lower 6 bits. 4) Verify the color depth with IM identify (7.x) or gimp (2.10.34) or IM -format %k -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464493] Monitor is recognized by Plasma, but will not output anything on kwin wayland
https://bugs.kde.org/show_bug.cgi?id=464493 --- Comment #2 from J --- (In reply to Nate Graham from comment #1) > To be clear, it's just that one monitor that stays black, and not all of > them, right? Correct. The other two monitors are displaying mouse cursor, desktop, everything. The monitor is detected but will not display anything. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464493] Monitor is recognized by Plasma, but will not output anything on kwin wayland
https://bugs.kde.org/show_bug.cgi?id=464493 --- Comment #4 from J --- Unfortunately, I seem to only be able to install plasma 5.26.90. Except for the plasma-meta package which is on 5.27-1 which is okay. I can wait for Arch to update their repos. I will respond back when I am able to update all packages to 5.27? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464493] Monitor is recognized by Plasma, but will not output anything on kwin wayland
https://bugs.kde.org/show_bug.cgi?id=464493 --- Comment #6 from J --- There has been no change in behavior of the display. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464493] Monitor is recognized by Plasma, but will not output anything on kwin wayland
https://bugs.kde.org/show_bug.cgi?id=464493 --- Comment #8 from J --- Created attachment 155725 --> https://bugs.kde.org/attachment.cgi?id=155725&action=edit This is a picture of my monitor active yet still blank using kwin wayland Here is a photo of my monitor detected, but still blank. When I use Spectacle, I can screenshot just this screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464493] Monitor is recognized by Plasma, but will not output anything on kwin wayland
https://bugs.kde.org/show_bug.cgi?id=464493 --- Comment #9 from J --- If there is anythi(In reply to Nate Graham from comment #7) > OK, thanks. I really appreciate you taking the time to look into this, if there is anything I can provide to help further please don't hesitate to ask. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464493] Monitor is recognized by Plasma, but will not output anything on kwin wayland
https://bugs.kde.org/show_bug.cgi?id=464493 J changed: What|Removed |Added Version|5.26.5 |6.1.1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 475150] Dolphin seems not to respect default ACLs on directories
https://bugs.kde.org/show_bug.cgi?id=475150 J changed: What|Removed |Added CC||j...@automatix.de Version|5.27.0 |6.0.0 --- Comment #3 from J --- Also here in current Plasma 6.x.x This Bug is very critica for us! This bug sabotages in critical way the work in a company, team using NFS Shares, it forces us to give root-passwords or sudo rights to standard users, that the amployees can do their jobs and rises big securtiy holes/risks. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 475150] Dolphin seems not to respect default ACLs on directories
https://bugs.kde.org/show_bug.cgi?id=475150 J changed: What|Removed |Added Version|6.0.0 |6.2.0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 439591] WEBM export creates broken file
https://bugs.kde.org/show_bug.cgi?id=439591 J changed: What|Removed |Added CC||unfold1...@gmail.com --- Comment #1 from J --- Same issue: Operating System: Gentoo Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.15.32-gentoo-r1-x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 439591] WEBM export creates broken file
https://bugs.kde.org/show_bug.cgi?id=439591 --- Comment #2 from J --- Managed to resolve this Kdenlive uses ffmpeg as the encoder so it must be built with the vpx flag in order to use libvpx media-video/ffmpeg vpx made the issue go away -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 455945] New: Cannot modify properties when overlaping objects
https://bugs.kde.org/show_bug.cgi?id=455945 Bug ID: 455945 Summary: Cannot modify properties when overlaping objects Product: okular Version: 20.12.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: sixfinger...@gmail.com Target Milestone: --- SUMMARY When it is created a new object in a pdf (let say a new note object) and then, it is created a new object overlapping the previously created object (let say a typewriter object), it cannot be possible to change the properties of the sencod object (the typewriter object). STEPS TO REPRODUCE 1. Create a note object 2. Create a typewriter object on the note object 3. Try to change any property of the typewriter object (as size, font...) OBSERVED RESULT Properties do not change when overlapping objects. If you want to change the object properties, you have to move the object to remove the overlapping, then change the object properties, and then move the object to the original position (overlapping). EXPECTED RESULT Be able to change the object properties even when objects are overlapped. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian 11 stable / KDE Plasma 5.20.5 (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.
[okular] [Bug 455945] Cannot modify properties when overlaping objects
https://bugs.kde.org/show_bug.cgi?id=455945 --- Comment #2 from J --- Created attachment 150229 --> https://bugs.kde.org/attachment.cgi?id=150229&action=edit Changing properties error As you can see in the video, when there are two objects overlapped, Okular changes the bottom object properties even when the top object is selected. In order to change the top object properties you have to move the top object out of the bottom object bounds. Hope this help. Regards. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 439591] WEBM export creates broken file
https://bugs.kde.org/show_bug.cgi?id=439591 J changed: What|Removed |Added CC|unfold1...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 343437] Do not Index NFS
https://bugs.kde.org/show_bug.cgi?id=343437 --- Comment #9 from J --- Ok, bu as "individual" User you should ever have in mind, that Unix ans alike Systems (like Linux, *BSD) are mostly ever used in Network environments. On architecture design, avoid *any* things, or switch them completely off by default, if such a beast may be harmful to others, especially like the balloo behavior in 2015! And a balloctl comand may not help at all, if it was running and crashing the servers. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 399523] Cannot move mouse cursor from edge of display with kdeconnect remote control other than primary display when more than one monitors are connected
https://bugs.kde.org/show_bug.cgi?id=399523 J changed: What|Removed |Added CC||unfold1...@gmail.com --- Comment #8 from J --- Same bug happens to me too :( -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 477327] New: startplasma-x11 fails - no usage possible - no log - no sign of debugging possible
https://bugs.kde.org/show_bug.cgi?id=477327 Bug ID: 477327 Summary: startplasma-x11 fails - no usage possible - no log - no sign of debugging possible Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: j...@automatix.de Target Milestone: --- SUMMARY *** After upgrade from 5.111 -> 5.112 yesterday, starting plasma (startplasma-x11) fails. Ksplash shows start animation, but no worktig session starts up. startplasma-x11 does not log anything, but eats up each second more 200kB of memory, consumes 100% CPU, *** STEPS TO REPRODUCE 1. Arch Linux - AMD CPU - AMDGPURadeon RX 470/480/570/570X/580/580X/590] (rev e1) 2. $HOME on NFS, .config, .local as subvolume from local btrfs 3. sddm, startplasma-x11, config was more than 1 year old, unchanged OBSERVED RESULT: startplasma-x11 leaks memory, 100% CPU usage, looks like a dead-end-loop $HOME/.xsession-errors are not used to log, no working session created EXPECTED RESULT working session SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux current version (2023-11-20) KDE Plasma Versions extracted from pacman.log, shows up the version change, which caused the problem. plasma-framework5 (5.111.0-1 -> 5.112.0-1) KDE Frameworks Version: plasma-framework5 (5.111.0-1 -> 5.112.0-1) Qt Version: upgraded qt5-base (5.15.11+kde+r138-1 -> 5.15.11+kde+r146-1) ADDITIONAL INFORMATION [2023-11-20T11:24:47+0100] [ALPM] upgraded kcoreaddons5 (5.111.0-1 -> 5.112.0-1) Sorry drkonqui or aditional logs are not written or availble. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 477327] startplasma-x11 fails - no usage possible - no log - no sign of debugging possible
https://bugs.kde.org/show_bug.cgi?id=477327 --- Comment #2 from J --- A clean .config works, but is not an option, due a huge amount of kwallet (gnupg) keys and forms data for chromium and saving/restoring them is nessesary. I tried out to remove anything not nessesary out of the way in .cache (deleted completely) .config (deleted partially, execpt license files of commercial licenses, kwallet files, chromium (arch version), gnupg (linked from $HOME/.gnupg -> .config/gnupg. startplasma-x11 was triggered by the sddm standard session startup. Unfortunately no logging in systemd journal or dmesg or .xsession-errors are done. Changing the Xsession start profile to "xterm" and starting "strace /usr/bin/startplasma-x11" in there gives no clue. I'll try to catch the strace out, Last line is IMHO "brk" line, repeating endless, and console top shows up no forks, but 100% cpu and expotentially raising memory usage, each second 200kiB RSS segement. User auth is done by ldap/nslcd/pam_ldap from central ldap server. This Filesystem setup was nessesary, due performance prooblems with kde/plasma users, if a nfs-server home was used: server:/home734002176 198294528 532041728 28% /home /dev/sdb3 1447541220 1324448464 84672400 94% /home/jojo/.cache /dev/sdb3 1447541220 1324448464 84672400 94% /home/jojo/.config /dev/sdb3 1447541220 1324448464 84672400 94% /home/jojo/.fonts /dev/sdb3 1447541220 1324448464 84672400 94% /home/jojo/.local /dev/sdb3 1447541220 1324448464 84672400 94% /home/jojo/.thunderbird tmpfs13184980 156 131848241% /run/user/1 i.E. /home/jojo/.* is mounted as btrfs subvolume, to keep buggy IO-intensive tasks on the local machine. We are a small company, having 20 employee logging in each morning at 8am. The startup of plasma sessions was without "local mounted" helps a DDOS against the NFS Server. standby, I try to grep more logs -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 477327] startplasma-x11 fails - no usage possible - no log - no sign of debugging possible
https://bugs.kde.org/show_bug.cgi?id=477327 --- Comment #3 from J --- Created attachment 163353 --> https://bugs.kde.org/attachment.cgi?id=163353&action=edit startplasma-ps-axef.log Process environment of crashing startplasma-x11 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 477327] startplasma-x11 fails - no usage possible - no log - no sign of debugging possible
https://bugs.kde.org/show_bug.cgi?id=477327 --- Comment #4 from J --- Created attachment 163354 --> https://bugs.kde.org/attachment.cgi?id=163354&action=edit strace log of failing startplasma-x11 manually created stack trace (strace startplasma-x11 &>log) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468609] Loads heif only with 8 bits color depth
https://bugs.kde.org/show_bug.cgi?id=468609 --- Comment #12 from J --- Thank you for your detailed reply. Here are my conclusions: 1. My systems are Debian Bookworm, libde265-1011-1 2. Your plugin tool says libde256 does only 8-bit but on GIT they say that libde256 does support HDR (which makes little sense with 8-bit). Where does the 8-bit limit come from? 3. There should be a warning when saving from a 16 bit workspace to 8-bit Heif 4. IM does HEIF 16 bit, why not using IM to load HEIF? 5. Saving from a 16-bit workspace should offer a way to select the depth. This is a feature request. I found that 10-bit depth is a good compromise between space and quality. 6. If DigiKam does not like to support 10-Bit Tiff (which is not standard but understood by IM) then try to reduce colors by masking away lower bits. 7. Currently Digikam offers limited 16-bit support, best for TIFF. Hopefully the future development will allow a wider support for HiColor and or HDR. 8. Your Image Loader Plugin architecture is quite nice, but for several reasons I would like to use IM codecs, but the IM Loader cannot be selected for HEIF, JPegXl ... ? It seems that there is a long way to go for DigiKam to reach full HiColor/HDR support. Until then I will continue to use intermediate 16-bit Tiffs and convert to/from archive format (JPeg2000) via IM. Jürgen 24. Oktober 2023 04:35, bugzilla_nore...@kde.org schrieb: > https://bugs.kde.org/show_bug.cgi?id=468609 > > --- Comment #10 from caulier.gil...@gmail.com --- > Hi Jurgen, > > To know if your HEIF codec support 8 bits and more, go to digiKam Setup / > Plugins / Loader and double click on HEIF entry. This will open an About > dialog for the plugin. Look on the description section. Mine from the 8.2.0 > AppImage give this : > > https://i.imgur.com/KOu2s0p.png > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 464493] New: Monitor is recognized by Plasma, but will not output anything on kwin wayland
https://bugs.kde.org/show_bug.cgi?id=464493 Bug ID: 464493 Summary: Monitor is recognized by Plasma, but will not output anything on kwin wayland Classification: Plasma Product: KScreen Version: 5.26.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: jandrewsternenb...@gmail.com Target Milestone: --- Created attachment 155421 --> https://bugs.kde.org/attachment.cgi?id=155421&action=edit Monitor is identified correctly and enabled in this screenshot. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Connect monitor to computer 2. Power on system 3. SDDM or LightDM greeter 4. Select Plasma 5. Login OBSERVED RESULT At login monitor displays greeter. Plasma starts, screen goes blank and stays blank EXPECTED RESULT At login monitor displays greeter. Plasma starts, screen turns on and stays on. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.1.6-arch1-3 (64-bit) (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION When logging into Plasma on X11 it will be enabled and display the desktop. When enabled on kwin wayland, the monitor goes blank and stays blank at login. I have to restart the machine once logged into wayland in order to get the monitor to display anything again. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 423827] New: It crashed when I tried to logout, but had been buggy for a little while beforehand
https://bugs.kde.org/show_bug.cgi?id=423827 Bug ID: 423827 Summary: It crashed when I tried to logout, but had been buggy for a little while beforehand Product: www.kde.org Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: jlerossig...@gmail.com Target Milestone: --- Created attachment 129863 --> https://bugs.kde.org/attachment.cgi?id=129863&action=edit Crash report SUMMARY Don't know. It just crashed STEPS TO REPRODUCE 1. I doubt I could reproduce it 2. 3. OBSERVED RESULT Desktop not responding, used terminal to reboot. It did so to windows, fucking Windows! I'd previously removed the possibility of booting into that but if found an old patrician. After fixing the BIOS to booting back into Linux (PopOS 19), the mouse had a 1/2 second sluggish response, like a drunk hamster staggering across my desktop. No I don't remember how I fixed it last time, but usbutils appeared to do the trick this time. Anyhow, the drunk gerbil's gone, but I'd like to now, WTF is going on with KDE Plasma EXPECTED RESULT Not much SOFTWARE/OS VERSIONS Linux/KDE Plasma: tick (available in About System) KDE Plasma Version: 5.0 I think ADDITIONAL INFORMATION Don't know what you'd want -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420555] Sorting mode (natural/alphabetical) is not applied immediately
https://bugs.kde.org/show_bug.cgi?id=420555 J changed: What|Removed |Added CC||unfold1...@gmail.com --- Comment #3 from J --- This is broken for me on 20.04.3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420555] Sorting mode (natural/alphabetical) is not applied immediately
https://bugs.kde.org/show_bug.cgi?id=420555 --- Comment #4 from J --- BTW Manually setting Collation and Sorting (Personalisation > Regional Setting > Formats) to my regional language fixes this issue. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 434297] The "Tab Color" dropdown in "Current Tab Settings" defaults to the wrong value
https://bugs.kde.org/show_bug.cgi?id=434297 J changed: What|Removed |Added CC||osl...@protonmail.com Assignee|konsole-de...@kde.org |osl...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 434297] The "Tab Color" dropdown in "Current Tab Settings" defaults to the wrong value
https://bugs.kde.org/show_bug.cgi?id=434297 --- Comment #1 from J --- Hi Thank you for sending a bug report. I am part of the Bugsquad and not a maintainer. I have followed your steps provided. Reproduced steps: CTRL + SHIFT + T or File > New Tab Right clicked the newly created tab and selected "Configure or Rename Tab" Set tab title format to "Test" Leaft the default tab colour(Mine was White too). Pressed ok Results: The observed results are the same as you have explained, when editing a newly created tab the default tab colour set is white(I too am using the Breeze Theme). I have tested this with a random custom theme and the results are still the same. To test if the profile itself can have the default tab colour changed I went to the tab settings in the current profile via Konsole > Settings > Edit Current profile > "Tabs" on the left side pane > selected "Colour From Theme". It seems the "Colour From Theme" option cannot be applied as default tab colour, my apply button was greyed out and cannot be selected. Any other colour can be selected and applied even a after restart of the Konsole the colour that was originally set in the settings is still remembered and applied. If you then go into settings and then change the default tab colour to "Colour >From Theme" you can now hit the apply button, but even after a restart of the Konsole the default tab colour still defaults to white. I was able to reproduce the issue on my system: SOFTWARE/OS VERSIONS: Operating System: Fedora 33 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.17-200.fc33.x86_64 OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434311] Edited Favorite Menu Item Doesn't Reflect The Change
https://bugs.kde.org/show_bug.cgi?id=434311 J changed: What|Removed |Added Assignee|h...@kde.org|osl...@protonmail.com CC||osl...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434311] Edited Favorite Menu Item Doesn't Reflect The Change
https://bugs.kde.org/show_bug.cgi?id=434311 --- Comment #2 from J --- Hi Thank you for submitting a bug report, I am part of the Bugsquad and not a maintainer. STEPS REPRODUCED: Added 2 programs to my favourites (Gwenview and Kcalc). Edited the properties by > Right Click > Edit Application > Applications tab Added libre office --writer to Gwenview and Gwenview to Kcalc in the command box and hit save. Launched both the newly edited applications from favourites. RESULTS: The newly edited programs saved in favourites both open and run the original application command, Gwenview would open Gwenview and Kcalc would open Kcalc. But as stated when opening both programs fresh and not from the favourites tab they open the programs I have set them via the command field. The only way for them to work as intended it to set the command field before hand and then pin it to the favourites tab, thus when opened it will then run the desired application/command set. CONCLUSION: The issue can be reproduced. SOFTWARE/OS VERSIONS: Operating System: Fedora 33 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 434692] New: App stops working after getting a new notification on desktop
https://bugs.kde.org/show_bug.cgi?id=434692 Bug ID: 434692 Summary: App stops working after getting a new notification on desktop Product: kdeconnect Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: unfold1...@gmail.com Target Milestone: --- SUMMARY Each time i get a new notification on my desktop such as a new message, alert or some other event that raises a notification, the application will not perform any actions until the notification gets timed out. STEPS TO REPRODUCE 1. Sync the desktop and the app 2. Get a new message for example whatsapp or some event that raises a notification 3. Try to use any of the app's functionalities such as multimedia controls or remote input, they will not work until the notification times out which is about 60 secs OBSERVED RESULT Mobile app stops working for a timed period which is tied to the notification on desktop EXPECTED RESULT Notifications on desktop shouldn't restrict, limit or interrupt the mobile app or at least it should be configurable somehow SOFTWARE/OS VERSIONS Operating System: Gentoo Linux KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.4.97-gentoo-x86_64 KDE-Connect: 1.16 ADDITIONAL INFORMATION When you get a call or a message when watching something and you can't pause it for 60 secs is extremely annoying :) Also no idea who should be responsible for this, could also be the desktop integration but raising it as mobile for now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464493] Monitor is recognized by Plasma, but will not output anything on kwin wayland
https://bugs.kde.org/show_bug.cgi?id=464493 --- Comment #13 from J --- (In reply to Zamundaaa from comment #11) > Could you try setting the environment variable > KWIN_DRM_PREFER_COLOR_DEPTH=24 for KWin, and see if it works then? This solution worked. I appreciate that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464493] Monitor is recognized by Plasma, but will not output anything on kwin wayland
https://bugs.kde.org/show_bug.cgi?id=464493 --- Comment #14 from J --- created an environment variable in ~/.config/plasma-workspace/env/ with the command: export KWIN_DRM_PREFER_COLOR_DEPTH=24 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464493] Monitor is recognized by Plasma, but will not output anything on kwin wayland
https://bugs.kde.org/show_bug.cgi?id=464493 --- Comment #10 from J --- Okay, I finally was able to acquire another machine to test this with. On Plasma 6+ Wayland it works with an intel HD 630 igpu using HDMI out. It does NOT work with my RX 6950 XT via HDMI or my RX 5700 XT via HDMI. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464493] Monitor is recognized by Plasma, but will not output anything on kwin wayland
https://bugs.kde.org/show_bug.cgi?id=464493 J changed: What|Removed |Added Version|6.1.1 |6.1.3 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 433945] Background transparency not applied to custom background colors
https://bugs.kde.org/show_bug.cgi?id=433945 J changed: What|Removed |Added Assignee|konsole-de...@kde.org |osl...@protonmail.com CC||osl...@protonmail.com --- Comment #1 from J --- Hi Thank you for creating a report. Can you please send a bit more information on the software/OS Versions you are using please? I am seeing a mixture of information not relating to actual OS, version number etc. Please copy to clipboard from system info and paste is here when you can. Thank you Regards J -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 433945] Background transparency not applied to custom background colors
https://bugs.kde.org/show_bug.cgi?id=433945 --- Comment #3 from J --- Hi No worries :), That's perfect thank you. It mainly for the Devs and for diagnosis/reproducing means. So I have followed your steps specified and viewed the picture you have attached. Reproduced steps: To get to the settings I had to follow Konsole > Settings > Edit Current profile > Appearance > Edit (Chosen colour scheme, mine was Breeeze) > change background transparency to 50% Run the echo command in Konsole with ANSI escape colour code you specified: echo -e '\u001b[40m123456' Results: The background is transparent for me and functions as intended, there is no black background around the text for me like what is specified in the picture. VIM was also opened and displayed the transparent background and scroll bar as intended. To confirm I also tried the colour codes: 42,43,44 and all display the background around text as expected. I have a few more questions? Are you using the default Konsole profile when changing the transparency? Have you tried making a fresh Konsole profile, changing the transparency closing the Konsole and then running the command? Thank you Regards J -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 433945] Background transparency not applied to custom background colors
https://bugs.kde.org/show_bug.cgi?id=433945
--- Comment #6 from J ---
Hi
Thanks for the info, I have installed the One Half Light Theme and had another
play around.
I have run the original ANSI escape code you specified ("echo -e
'\u001b[40m123456'" ) using the One Half Light Theme set to 50% transparency
and it shows the same blocked out text background in your first image.
To confirm it was not the theme itself I tried a variety of colour schemes, and
as you mentioned any black background colour scheme set to 50% transparency
displays the text the correct way(readable), but any colour scheme with a light
or white background displays the text in a black box (Barely readable or
unreadable) same as the example in your first image.
Conclusion:
I was able to reproduce after installing the custom theme (One Half Light) and
testing any default colour scheme with a light or white background.
Software/OS Version:
Operating System: Fedora 33
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.10.17-200.fc33.x86_64
OS Type: 64-bit
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-browser-integration] [Bug 412071] New: Multimedia Controls - Spotify Web Client
https://bugs.kde.org/show_bug.cgi?id=412071 Bug ID: 412071 Summary: Multimedia Controls - Spotify Web Client Product: plasma-browser-integration Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Firefox Assignee: k...@privat.broulik.de Reporter: unfold1...@gmail.com Target Milestone: --- SUMMARY The Spotify web client isn't being picked up by the integration as a source of media playing therefore it's not possible to control it STEPS TO REPRODUCE 1. Go to https://open.spotify.com/ 2. Play a song 3. Go to multimedia controls and see its not playing anything OBSERVED RESULT Media isn't playing according to Plasma integration EXPECTED RESULT Media is playing and should be reflected in multimedia controls SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.60.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412074] New: Multimedia Controls - Process Name\Multiple Instances
https://bugs.kde.org/show_bug.cgi?id=412074 Bug ID: 412074 Summary: Multimedia Controls - Process Name\Multiple Instances Product: kdeconnect Version: 1.3.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: unfold1...@gmail.com Target Milestone: --- SUMMARY Using multiple instances of a media application for example VLC creates each instance as "VLC media player <1>" "VLC media player <2>" etc. it is the name being picked up by KDE connect and displayed in multimedia controls, however when playing something it changes to the media currently playing. having multiple instances of the same application makes it difficult to know which application is which in multimedia controls. STEPS TO REPRODUCE 1. Get Vlc media player 2. Go to Interface options in VLC and uncheck use one instance 3. Open a few VLC instances and have a video file open in each 4. Go to multimedia controls in KDE connect and look at the picked up instances OBSERVED RESULT Process Name is used in multimedia controls which makes multiple instances appear as ordered lists EXPECTED RESULT Multimedia controls should pick up the name of the file open in the player or the title to make it unique from the other instances of the same application SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.60.0 Qt Version: 5.12.3 Might be related to https://bugs.kde.org/show_bug.cgi?id=258692 but i'm not sure why its not fixed then -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412073] New: Multimedia Controls - Browser Media\Youtube
https://bugs.kde.org/show_bug.cgi?id=412073 Bug ID: 412073 Summary: Multimedia Controls - Browser Media\Youtube Product: kdeconnect Version: 1.3.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: unfold1...@gmail.com Target Milestone: --- SUMMARY Kde connect doesn't handle browser media in tabs, having 2 tabs of youtube only shows the first one in multimedia controls STEPS TO REPRODUCE 1. Open 2 Youtube Videos in the browser 2. Go to multimedia controls on KDE connect 3. Look in the list of media playing OBSERVED RESULT Only the first video opened in the browser is being shown in multimedia controls EXPECTED RESULT Each browser tab should be handled separately and appear as its own instance in multimedia controls SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.60.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412072] New: Multimedia Controls - VLC\Media player multiple instance out of sync
https://bugs.kde.org/show_bug.cgi?id=412072 Bug ID: 412072 Summary: Multimedia Controls - VLC\Media player multiple instance out of sync Product: kdeconnect Version: 1.3.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: unfold1...@gmail.com Target Milestone: --- SUMMARY When using a media player for example VLC and having multiple instances of it running multimedia controls gets out of sync and is unable to play\stop the media playing STEPS TO REPRODUCE 1. Get VLC media player 2. Go to Interface options in VLC and uncheck use one instance 3. Open multiple VLC instances playing something 4. Go to Multimedia controls 5. Press Play\Pause OBSERVED RESULT After pressing play\pause one time the button is greyed out and it's impossible to controls the media playing EXPECTED RESULT The play\pause button should work while having multiple instances of the same application SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.60.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412075] New: Multimedia Controls - Spotify Web Client
https://bugs.kde.org/show_bug.cgi?id=412075 Bug ID: 412075 Summary: Multimedia Controls - Spotify Web Client Product: kdeconnect Version: 1.3.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: unfold1...@gmail.com Target Milestone: --- SUMMARY The Spotify web client isn't being picked up by KDE connect as a source of media playing therefore it's not possible to control it STEPS TO REPRODUCE 1. Go to https://open.spotify.com/ 2. Play a song 3. While KDE connect is connected go to multimedia controls and see its not playing anything OBSERVED RESULT Media isn't playing according to KDE connect EXPECTED RESULT Media is playing and should be reflected in the multimedia controls plugin SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.60.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412072] Multimedia Controls - VLC\Media player multiple instance out of sync
https://bugs.kde.org/show_bug.cgi?id=412072 --- Comment #2 from J --- (In reply to Matthijs Tijink from comment #1) > This is a bug in VLC (and doesn't even require non-default settings): they > don't notify MPRIS clients like KDE Connect that playing is allowed. But it works fine with a single instance? -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 412071] Multimedia Controls - Spotify Web Client
https://bugs.kde.org/show_bug.cgi?id=412071 --- Comment #3 from J --- (In reply to Kai Uwe Broulik from comment #1) > Again the issue of Firefox enforcing content-security policy on websites ... > see also Bug 411148 I understand it's not a KDE issue but is there something to be done about it? I tried disabling CSP but it didn't help -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412074] Multimedia Controls - Process Name\Multiple Instances
https://bugs.kde.org/show_bug.cgi?id=412074 --- Comment #2 from J --- (In reply to Matthijs Tijink from comment #1) > I'm not entirely sure what you mean, so let me summarize: > > Currently, if there are multiple players with the same name (e.g. multiple > VLC instances), they get named "Name", "Name [2]" etc. > This makes it unclear which instance is which in the player selection > dropdown. > You propose including the media artist & title in this dropdown, to make > this clearer. > > Is that correct? Yes this is correct, only it's any identifiable info so it should be: media artist || title || anything else like file name -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412072] Multimedia Controls - VLC\Media player multiple instance out of sync
https://bugs.kde.org/show_bug.cgi?id=412072 --- Comment #3 from J --- I'm guessing this is the VLC bug related to this https://trac.videolan.org/vlc/ticket/20125 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412099] New: Add a percentage indicator to the volume slider in multimedia controls
https://bugs.kde.org/show_bug.cgi?id=412099 Bug ID: 412099 Summary: Add a percentage indicator to the volume slider in multimedia controls Product: kdeconnect Version: 1.3.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: unfold1...@gmail.com Target Milestone: --- SUMMARY Add a percentage indicator to the volume slider in multimedia controls -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412074] Multimedia Controls - Process Name\Multiple Instances
https://bugs.kde.org/show_bug.cgi?id=412074 --- Comment #4 from J --- (In reply to Matthijs Tijink from comment #3) > We don't have the filename, but we can add the other things. Anything is good at this point, although i think title is sufficient enough. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412072] Multimedia Controls - VLC\Media player multiple instance out of sync
https://bugs.kde.org/show_bug.cgi?id=412072 --- Comment #5 from J --- (In reply to Matthijs Tijink from comment #4) > Turns out that this bug hasn't been reported to VLC yet (I thought it had), > so see https://trac.videolan.org/vlc/ticket/22785 Thank you for raising the issue with VLC highly appreciated -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 420926] New: No control over multiple or different playback sources
https://bugs.kde.org/show_bug.cgi?id=420926 Bug ID: 420926 Summary: No control over multiple or different playback sources Product: plasma-browser-integration Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: unfold1...@gmail.com Target Milestone: --- SUMMARY When having multiple playback streams like tabs or browser windows, it's not possible to switch between different sources, only the last playing source is picked up by the integration controls, this also goes to KdeConnect. STEPS TO REPRODUCE 1. Open a browser with several tabs or 2 browser instances with 2 youtube videos 2. Play both videos 3. Go to multimedia controls in integration OBSERVED RESULT Only the last media source playing is controlable EXPECTED RESULT It should be possible to switch media sources in the controls SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.60.0 Qt Version: 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 420926] No control over multiple or different playback sources
https://bugs.kde.org/show_bug.cgi?id=420926 --- Comment #2 from J --- Sorry, i searched a few times but couldn't find something similar. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 395461] multiple video support
https://bugs.kde.org/show_bug.cgi?id=395461 --- Comment #4 from J --- If this is fixed in KDEconnect (https://invent.kde.org/kde/kdeconnect-kde/merge_requests/153), is it possible to implement it in a similar way on the Desktop Plasmoid? -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 412071] Multimedia Controls - Spotify Web Client
https://bugs.kde.org/show_bug.cgi?id=412071 --- Comment #6 from J --- Thank you, it works. How soon will there be an updated XPI file to include this permanently? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 414513] New: Playback out of sync when playing at faster speed
https://bugs.kde.org/show_bug.cgi?id=414513 Bug ID: 414513 Summary: Playback out of sync when playing at faster speed Product: kdeconnect Version: 1.3.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: unfold1...@gmail.com Target Milestone: --- SUMMARY When watching Youtube videos at 2X speed the multimedia section inside the mobile app shows the wrong time currently playing STEPS TO REPRODUCE 1. Play a Youtube video at more than 1.0 speed 2. Go to Multimedia controls in the mobile app OBSERVED RESULT After playing a video in 2X the current position is wrongly reflected in the mobile app EXPECTED RESULT The current playing position\timestamp is synced regardless of the video playback speed SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.60.0 Qt Version: 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 414514] New: Add fullscreen control button
https://bugs.kde.org/show_bug.cgi?id=414514 Bug ID: 414514 Summary: Add fullscreen control button Product: kdeconnect Version: 1.3.5 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: unfold1...@gmail.com Target Milestone: --- SUMMARY This is a feature request for having a full screen button in multimedia controls in the KDE connect mobile app, it might be a bit problematic but for most apps the 'F' key is used to control full screen mode -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399376] New: Session crash
https://bugs.kde.org/show_bug.cgi?id=399376 Bug ID: 399376 Summary: Session crash Product: kwin Version: 5.12.6 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: brumbac...@yahoo.com Target Milestone: --- Application: kwin_x11 (5.12.6) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-36-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: I was attempting to save a desktop session from the K-menu / Leave The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f625bbc2cc0 (LWP 17543))] Thread 5 (Thread 0x7f621aa1f700 (LWP 17555)): #0 0x7f62545839f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f6257b1afb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f6257b1af68, cond=0x7f6257b1af90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f6257b1af90, mutex=0x7f6257b1af68) at pthread_cond_wait.c:655 #3 0x7f62578245f4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f6257824639 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f625457d6db in start_thread (arg=0x7f621aa1f700) at pthread_create.c:463 #6 0x7f625b52388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f623923b700 (LWP 17552)): #0 0x7f625b516cf6 in __GI_ppoll (fds=0x7f623d28, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f62589185c1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f6258919cde in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f62588c19ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f62586e022a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f62530696f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f62586e516d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f625457d6db in start_thread (arg=0x7f623923b700) at pthread_create.c:463 #8 0x7f625b52388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f623bb68700 (LWP 17549)): #0 0x7f625b516cf6 in __GI_ppoll (fds=0x7f623400e7b8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f62589185c1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f6258919cde in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f62588c19ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f62586e022a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6251f42d45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7f62586e516d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f625457d6db in start_thread (arg=0x7f623bb68700) at pthread_create.c:463 #8 0x7f625b52388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f6242237700 (LWP 17547)): #0 0x7f625b516bf9 in __GI___poll (fds=0x7f6242236c68, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f625a420747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f625a42236a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f62431162a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f62586e516d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f625457d6db in start_thread (arg=0x7f6242237700) at pthread_create.c:463 #6 0x7f625b52388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f625bbc2cc0 (LWP 17543)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7f625b442801 in __GI_abort () at abort.c:79 #8 0x7f62586cffa7 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f625b02549b in KWin::Workspace::windowTypeToTxt(NET::WindowType) () from /usr/lib/x86_64-linux-gnu/libkwin.so.5 #10 0x7f625b026b40 in KWin::Workspace::storeClient(KConfigGroup&, int, KWin::Client*) () from /usr/lib/x86_64-linux-gnu/libkwin.so.5 #11 0x7f625b02a2e8 in KWin::Workspace::storeSession(KConfig*, KWin::SMSavePhase) () from /usr/lib/x86_64-linux-gnu/libkwin.so.5 #12 0x7f625b02a53d in KWin::Workspace::saveState(
[okular] [Bug 358755] okular crash when opening a file inside gnu screen
https://bugs.kde.org/show_bug.cgi?id=358755 J changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from J --- Right now, with Debian 9.5 and okular 0.26.1 it works and doesn't crash. Consider this fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498069] New: Can no longer set panel themed icons in panel
https://bugs.kde.org/show_bug.cgi?id=498069 Bug ID: 498069 Summary: Can no longer set panel themed icons in panel Classification: Plasma Product: plasmashell Version: 6.2.2 Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jonam1...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 176983 --> https://bugs.kde.org/attachment.cgi?id=176983&action=edit Icons that could previously be black and white now must be symbolic. SUMMARY KDE Plasma previously allowed custom icon theming and alignment with the panel style. For instance a style like pink bunny emphasizes a distinct appearance for which flat symbolic icons would not fit. Previously this could be achieved with the icons in the plasma style. Is there a way to incorporate custom plasma style icons in an icon theme to maintain this functionality? STEPS TO REPRODUCE 1. Set an icon theme 2. Set your theme to fluffy bunny or low opacity theme 3. Look where panel symbolic icons are OBSERVED RESULT Plain symbolic icons are observed reducing readability across different panel styles EXPECTED RESULT Maintain functionality to have custom icons for the panel's theme SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon KDE Plasma Version: 6.2.0 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Attached is an example of icons, that previously could be white and black icons now have to choose a color. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372035] New: Crash while typing PHP code
https://bugs.kde.org/show_bug.cgi?id=372035 Bug ID: 372035 Summary: Crash while typing PHP code Product: kdevelop Version: 5.0.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: julioelpo...@gmail.com Target Milestone: --- Application: kdevelop (5.0.2) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.8.6-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I was writing some code with a couple of files opened. - Custom settings of the application: It's not really a custom setting, but I was loading a couple of remote projects (through kioslaves, sftp:// ), which since the update to 5.0 takes a really long time. I'm not sure if it's related but I thought it may be worth mentioning. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f009800 (LWP 1409))] Thread 23 (Thread 0x7f0a980d2700 (LWP 3594)): #0 0x7f0bb892448d in poll () at /usr/lib/libc.so.6 #1 0x7f0bb0212786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f0bb021289c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f0bb924672b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f0bb91f023a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f0bb90130f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f0bb6af415f in () at /usr/lib/libKDevPlatformLanguage.so.10 #7 0x7f0bb9017d78 in () at /usr/lib/libQt5Core.so.5 #8 0x7f0bb21fb454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f0bb892d7df in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7f0aa3fff700 (LWP 3590)): #0 0x7f0bb892448d in poll () at /usr/lib/libc.so.6 #1 0x7f0bb0212786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f0bb021289c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f0bb924672b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f0bb91f023a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f0bb90130f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f0bb6af415f in () at /usr/lib/libKDevPlatformLanguage.so.10 #7 0x7f0bb9017d78 in () at /usr/lib/libQt5Core.so.5 #8 0x7f0bb21fb454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f0bb892d7df in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7f0b31575700 (LWP 3589)): #0 0x7f0bb220110f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0bb9018c2b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f0bad91c1c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f0bad920988 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f0bad91b263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f0bad9209e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f0bad91b263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f0bad9209e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f0bad91b263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f0bad91e1f9 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f0bb9017d78 in () at /usr/lib/libQt5Core.so.5 #11 0x7f0bb21fb454 in start_thread () at /usr/lib/libpthread.so.0 #12 0x7f0bb892d7df in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7f0b31d76700 (LWP 3588)): #0 0x7f0bb220110f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0bb9018c2b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f0bad91c1c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f0bad920988 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f0bad91b263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f0bad91e1f9 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f0bb9017d78 in () at /usr/lib/libQt5Core.so.5 #7 0x7f0bb21fb454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f0bb892d7df in clone () at /usr/lib/libc.so.6 Thread 19 (Thread 0x7f0b32577700 (LWP 3587)): #0 0x7f0bb220110f in pthre
[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too
https://bugs.kde.org/show_bug.cgi?id=336043 Rick J changed: What|Removed |Added CC||r...@activeservice.co.uk --- Comment #50 from Rick J --- I've just encountered this bug on a new phone (LG G5) running AOS 6. When I open the device in Dolphin I get: > Camera pictures(Internal storage) Camera pictures(SD card) > Internal storage SD card "SD card" is a real card, "Internal storage" is the emulated card. No directories are detected on the SD card. But if I step into the apparently empty SD card directory, then edit the path and add /DCIM on the end (or any other directory that exists) its contents appear. The contents are readable but nothing is writeable, which is a bit of a limitation. I believe the (bonkers) restrictions on the external card introduced in AOS 4 were removed in 5 & 6, so the SD card should be browseable. Non-privileged file managers such as Explorer (non-root version) can see the directories on the card, so KDEconnect should be able to as well. Is there maybe a new API since AOS 4 for doing this? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 373289] New: KDevelop crashes on startup
https://bugs.kde.org/show_bug.cgi?id=373289 Bug ID: 373289 Summary: KDevelop crashes on startup Product: kdevelop Version: 5.0.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: julioelpo...@gmail.com Target Milestone: --- Application: kdevelop (5.0.3) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.8.11-1-zen x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I have some projects open loaded and some files (none of them huge), but when it starts loading them, the process starts hoarding RAM till it exahust all 8GB, and then continues with the swap, after that, the system kills it, but there is no reason for it to consume so much memory. - Custom settings of the application: Most of the projects I was loading are being loaded through SFTP from a remote server. I have no idea if that's of any influence. I am using Arch with all packages up to date. $ uname -a Linux XPS13-9350 4.8.11-1-zen #1 ZEN SMP PREEMPT Sat Nov 26 14:03:07 UTC 2016 x86_64 GNU/Linux Let me know if I can help debugging anything else. This starting happening over a week ago, so I'm guessing is some kind of bug that appeared after the upgrade. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd48d12e800 (LWP 12185))] Thread 21 (Thread 0x7fd3fa857700 (LWP 12273)): #0 0x7fd489f4a48d in poll () at /usr/lib/libc.so.6 #1 0x7fd481832786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fd48183289c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fd48a86c72b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fd48a81623a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fd48a6390f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fd47f8ef2d5 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fd48a63dd78 in () at /usr/lib/libQt5Core.so.5 #8 0x7fd48381f454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fd489f537df in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7fd3fb7fe700 (LWP 12255)): #0 0x7fd4818425d0 in g_poll () at /usr/lib/libglib-2.0.so.0 #1 0x7fd481832786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fd48183289c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fd48a86c72b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fd48a81623a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fd48a6390f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fd48811a36f in () at /usr/lib/libKDevPlatformLanguage.so.10 #7 0x7fd48a63dd78 in () at /usr/lib/libQt5Core.so.5 #8 0x7fd48381f454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fd489f537df in clone () at /usr/lib/libc.so.6 Thread 19 (Thread 0x7fd3fbfff700 (LWP 12231)): #0 0x7fd48382510f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd48a63ec2b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fd47ef3b1c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fd47ef3f988 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fd47ef3a263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fd47ef3f9e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fd47ef3a263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fd47ef3f9e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fd47ef3a263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7fd47ef3d1f9 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7fd48a63dd78 in () at /usr/lib/libQt5Core.so.5 #11 0x7fd48381f454 in start_thread () at /usr/lib/libpthread.so.0 #12 0x7fd489f537df in clone () at /usr/lib/libc.so.6 Thread 18 (Thread 0x7fd418ff9700 (LWP 12230)): #0 0x7fd48382510f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd48a63ec2b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fd47ef3b1c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fd47ef3f988 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x00
[kdevelop] [Bug 373289] KDevelop crashes on startup
https://bugs.kde.org/show_bug.cgi?id=373289 --- Comment #2 from Julio J. --- I can't just provide the files right away since they belong to my company, but I'll try to strip them down to something that still crashes my kdevelop but does not contain any critical code. I'll post them here as soon as I have them. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 450486] New: Kdenlive flatpak crashed when I keep clicked and drag to move to a different part of the video
https://bugs.kde.org/show_bug.cgi?id=450486 Bug ID: 450486 Summary: Kdenlive flatpak crashed when I keep clicked and drag to move to a different part of the video Product: kdenlive Version: 21.12.2 Platform: Flatpak OS: Linux Status: REPORTED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: a.g...@libero.it Target Milestone: --- Created attachment 146890 --> https://bugs.kde.org/attachment.cgi?id=146890&action=edit no debug symbols since it is flatpak SUMMARY It does not happen every time. I noticed it once and I am reporting it. STEPS TO REPRODUCE 1. Drag to move to a different position in the video OBSERVED RESULT Kdenlive crashes SOFTWARE/OS VERSIONS ArchLinux Gnome 41.3 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 466172] New: SIGTRAP crash whenever getaddrinfo call is issued by valgrind
https://bugs.kde.org/show_bug.cgi?id=466172 Bug ID: 466172 Summary: SIGTRAP crash whenever getaddrinfo call is issued by valgrind Classification: Developer tools Product: valgrind Version: 3.20.0 Platform: RedHat Enterprise Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: do.not.spam.me.kde.bugzi...@gmail.com Target Milestone: --- SUMMARY On my work RHEL 7.9 development system, valgrind coredumps and exits following a SIGTRAP generated when calling the C library getaddrinfo function. This occurs when running valgrind on our internal applications that call getaddrinfo(), and also when running valgrind on the 'hostname -d' command. This will produce a core file for the program. Output from valgrind is available below, as is gdb output from the core file. The problem occurs with the memcheck tool, and also the callgrind tool. Further details given below are from running valgrind with hostname -d. No failure occurs when running valgrind when hostname has no args, as it does not generate a getaddrinfo call. Similar results were seen when running the native valgrind v3.15 install for RHEL 7.9, as seen when running a locally compiled valgrind v3.20 release. The stack trace in the core file does not make a lot of sense as the system doesn't currently have debuginfo packages installed. I'm trying to arrange these for the glibc and hostname packages via a sysadmin, but this is not available at the moment. On my home host with VirtualBox, using RHEL 7.9, RHEL 8.7 and Fedora 35, running valgrind with signal tracing turned on against 'hostname -d' shows two SIGSEGV signals are raised but handled by valgrind and it continues to successful command completion. I can't comment as to whether this should or shouldn't happen, I've just used this to establish an expected baseline. When run with strace instead of valgrind, no signals are found to be raised. When running strace with valgrind and hostname -d, both strace and valgrind report the two SIGSEGV signals. STEPS TO REPRODUCE 1. valgrind --trace-signals=yes -v hostname -d 2. 3. OBSERVED RESULT valgrind handles a single SIGSEGV and continues, then handles a SIGTRAP and core dumps. valgrind output indicates the crash happened during a getaddrinfo call. EXPECTED RESULT Program being run with valgrind should survive a call to getaddrinfo and continue running, so that memory leak checking can be carried out. SOFTWARE/OS VERSIONS Linux: RHEL 7.9 server without GUI installed ADDITIONAL INFORMATION Valgrind generates the following output ==80114== Memcheck, a memory error detector ==80114== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==80114== Using Valgrind-3.20.0-5147d671e4-20221024 and LibVEX; rerun with -h for copyright info ==80114== Command: hostname -d ==80114== Parent PID: 20454 ==80114== --80114-- --80114-- Valgrind options: --80114----trace-signals=yes --80114---v --80114----log-file=valgrind.out --80114-- Contents of /proc/version: --80114-- Linux version 3.10.0-1160.81.1.el7.x86_64 (mockbu...@x86-vm-38.build.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC) ) #1 SMP Thu Nov 24 12:21:22 UTC 2022 --80114-- --80114-- Arch and hwcaps: AMD64, LittleEndian, amd64-cx16-lzcnt-rdtscp-sse3-ssse3-avx-avx2-bmi-f16c-rdrand --80114-- Page sizes: currently 4096, max supported 4096 --80114-- Valgrind library directory: /home/auser/local/libexec/valgrind --80114-- Reading syms from /usr/bin/hostname --80114--object doesn't have a symbol table --80114-- Reading syms from /usr/lib64/ld-2.17.so --80114-- Reading syms from /home/auser/local/libexec/valgrind/memcheck-amd64-linux --80114--object doesn't have a dynamic symbol table --80114-- Scheduler: using generic scheduler lock implementation. --80114-- Max kernel-supported signal is 64, VG_SIGVGKILL is 64 --80114-- Reading suppressions file: /home/auser/local/libexec/valgrind/default.supp ==80114== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-80114-by-auser-on-hostname.localdomain ==80114== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-80114-by-auser-on-hostname.localdomain ==80114== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-80114-by-auser-on-hostname.localdomain ==80114== ==80114== TO CONTROL THIS PROCESS USING vgdb (which you probably ==80114== don't want to do, unless you know exactly what you're doing, ==80114== or are doing some strange experiment): ==80114== /home/auser/local/libexec/valgrind/../../bin/vgdb --pid=80114 ...command... ==80114== ==80114== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==80114== /path/to/gdb hostname ==80114== and then give GDB the following command ==80114== target remote | /home/auser/local/libexec/valgrind/../../bin/vgdb --pid=
[valgrind] [Bug 466172] SIGTRAP crash whenever getaddrinfo call is issued by valgrind
https://bugs.kde.org/show_bug.cgi?id=466172 --- Comment #3 from Mike J --- Thanks. Although the sysadmins installed the correct debuginfo for glibc and hostname today, I won't have collatable results from this until 23rd Feb. I'll provide an update then -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 466172] SIGTRAP crash whenever getaddrinfo call is issued by valgrind
https://bugs.kde.org/show_bug.cgi?id=466172 --- Comment #4 from Mike J --- It was noted that we have Dynatrace OneAgent installed, which preloads one of its libraries by adding it to /etc/ld.so.preload. Although originally thought it might be involved in the problem, we have concluded today that it is not involved, by doing two valgrind runs with gdb attached on hostname -d, with and without the preloaded library. The two run details are shown below with gdb output, in the hope that somebody can spot something untoward that valgrind may be doing. In the first run, /etc/ld.so.preload is set up to dynamically link in a Dynatrace OneAgent library for each program started. In the second run, /etc/ld.so.preload is renamed and ldconfig run to relink runtime shared library cache GDB is attached once valgrind is started. Breakpoints are set on show_name and getaddrinfo, but stepped through from the show_name breakpoint to also watch the dynamic linker behaviour in loading the getaddrinfo call. The initial step from show_name() to getaddrinfo() call shows dynamic linker involved in loading call from glibc library. On first entry into getaddrinfo function, the callstack is OK. On the next step instruction, the callstack becomes corrupted. Continuing on leads to a SIGSEGV, rather than a SIGTRAP, which crashes the program. Both runs are identical in outcome. If the debugger is not attached, a SIGTRAP is instead raised, which crashes the program. Lines with @ below are eye catchers for relevant notes @ First run @ [auser@hostname ~]$ cat /etc/ld.so.preload /$LIB/liboneagentproc.so [auser@hostname ~]$ ldd /usr/bin/hostname linux-vdso.so.1 => (0x7ffd02d96000) /$LIB/liboneagentproc.so => /lib64/liboneagentproc.so (0x2af8ce652000) libnsl.so.1 => /usr/lib64/libnsl.so.1 (0x2af8ce86) libc.so.6 => /usr/lib64/libc.so.6 (0x2af8cea7a000) /lib64/ld-linux-x86-64.so.2 (0x2af8ce42e000) Terminal 1 valgrind --trace-signals=yes -v --log-file=valgrind.out.2 --vgdb=full --vgdb-stop-at=startup hostname -d Terminal 2 cat valgrind.out.2 ==77535== Memcheck, a memory error detector ==77535== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==77535== Using Valgrind-3.20.0-5147d671e4-20221024 and LibVEX; rerun with -h for copyright info ==77535== Command: hostname -d ==77535== Parent PID: 111647 ==77535== --77535-- --77535-- Valgrind options: --77535----trace-signals=yes --77535---v --77535----log-file=valgrind.out.2 --77535----vgdb=full --77535----vgdb-stop-at=startup --77535-- Contents of /proc/version: --77535-- Linux version 3.10.0-1160.81.1.el7.x86_64 (mockbu...@x86-vm-38.build.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC) ) #1 SMP Thu Nov 24 12:21:22 UTC 2022 --77535-- --77535-- Arch and hwcaps: AMD64, LittleEndian, amd64-cx16-lzcnt-rdtscp-sse3-ssse3-avx-avx2-bmi-f16c-rdrand --77535-- Page sizes: currently 4096, max supported 4096 --77535-- Valgrind library directory: /home/auser/local/libexec/valgrind --77535-- Reading syms from /usr/bin/hostname --77535-- Considering /usr/lib/debug/.build-id/93/633698bd11eeb4bee21a388c191a5656990d8e.debug .. --77535-- .. build-id is valid --77535-- Reading syms from /usr/lib64/ld-2.17.so --77535-- Considering /usr/lib/debug/.build-id/62/c449974331341bb08dcce3859560a22af1e172.debug .. --77535-- .. build-id is valid --77535-- Reading syms from /home/auser/local/libexec/valgrind/memcheck-amd64-linux --77535--object doesn't have a dynamic symbol table --77535-- Scheduler: using generic scheduler lock implementation. --77535-- Max kernel-supported signal is 64, VG_SIGVGKILL is 64 --77535-- Reading suppressions file: /home/auser/local/libexec/valgrind/default.supp ==77535== (action at startup) vgdb me ... ==77535== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-77535-by-auser-on-hostname.localdomain ==77535== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-77535-by-auser-on-hostname.localdomain ==77535== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-77535-by-auser-on-hostname.localdomain ==77535== ==77535== TO CONTROL THIS PROCESS USING vgdb (which you probably ==77535== don't want to do, unless you know exactly what you're doing, ==77535== or are doing some strange experiment): ==77535== /home/auser/local/libexec/valgrind/../../bin/vgdb --pid=77535 ...command... ==77535== ==77535== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==77535== /path/to/gdb hostname ==77535== and then give GDB the following command ==77535== target remote | /home/auser/local/libexec/valgrind/../../bin/vgdb --pid=77535 ==77535== --pid is optional if only one valgrind process is running ==77535== [auser@hostname ~]$ gdb /usr/bin/hostname Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/g
[valgrind] [Bug 466172] SIGTRAP crash whenever getaddrinfo call is issued by valgrind
https://bugs.kde.org/show_bug.cgi?id=466172 --- Comment #6 from Mike J --- Thanks Paul. I was unaware of TUI mode, its really useful. The following extract is from the TUI asm and command windows. It shows a int3 rather than a push %rbp on the initial entry, where the call stack still shows as being normal. On the stepi (rather than a step tried previously), the call stack has then become corrupted. Is the int3 likely to be something that valgrind might introduce instead of the push %rbp ? B+>x0x534b5e0 <__GI_getaddrinfo>int3 x0x534b5e1 <__GI_getaddrinfo+1> mov%rsp,%rbp x0x534b5e4 <__GI_getaddrinfo+4> push %r15 x0x534b5e6 <__GI_getaddrinfo+6> push %r14 x0x534b5e8 <__GI_getaddrinfo+8> mov%rdi,%r14 x0x534b5eb <__GI_getaddrinfo+11> push %r13 x0x534b5ed <__GI_getaddrinfo+13> mov%rsi,%r13 x0x534b5f0 <__GI_getaddrinfo+16> push %r12 x0x534b5f2 <__GI_getaddrinfo+18> mov%rdx,%r12 x0x534b5f5 <__GI_getaddrinfo+21> push %rbx x0x534b5f6 <__GI_getaddrinfo+22> sub$0x518,%rsp x0x534b5fd <__GI_getaddrinfo+29> test %rdi,%rdi x0x534b600 <__GI_getaddrinfo+32> mov%rcx,-0x530(%rbp) (gdb) where #0 __GI_getaddrinfo (name=0x5632040 "hostname.localdomain", service=service@entry=0x0, hints=hints@entry=0x1ffefff930, pai=pai@entry=0x1ffefff928) at ../sysdeps/posix/getaddrinfo.c:2208 #1 0x00401b19 in show_name (type=type@entry=DNS) at hostname.c:339 #2 0x004013e4 in main (argc=2, argv=0x1ffefffb98) at hostname.c:550 (gdb) stepi stepi >x0x534b5e1 <__GI_getaddrinfo+1> mov%rsp,%rbp x0x534b5e4 <__GI_getaddrinfo+4> push %r15 x0x534b5e6 <__GI_getaddrinfo+6> push %r14 x0x534b5e8 <__GI_getaddrinfo+8> mov%rdi,%r14 x0x534b5eb <__GI_getaddrinfo+11> push %r13 x0x534b5ed <__GI_getaddrinfo+13> mov%rsi,%r13 x0x534b5f0 <__GI_getaddrinfo+16> push %r12 x0x534b5f2 <__GI_getaddrinfo+18> mov%rdx,%r12 x0x534b5f5 <__GI_getaddrinfo+21> push %rbx x0x534b5f6 <__GI_getaddrinfo+22> sub$0x518,%rsp x0x534b5fd <__GI_getaddrinfo+29> test %rdi,%rdi x0x534b600 <__GI_getaddrinfo+32> mov%rcx,-0x530(%rbp) x0x534b607 <__GI_getaddrinfo+39> movq $0x0,-0x4c0(%rbp) (gdb) where where #0 0x0534b5e1 in __GI_getaddrinfo (name=0x5632040 "hostname.localdomain", service=0x0, hints=0x1ffefff930, pai=0x1ffefff928) at ../sysdeps/posix/getaddrinfo.c:2208 #1 0x001ffefffa40 in ?? () #2 0x0529d226 in __GI_getenv (name=0x1ffefff930 "\002") at getenv.c:35 #3 0x in ?? () -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 207309] Provide "Open folders in separate windows" functionality for the DolphinPart
https://bugs.kde.org/show_bug.cgi?id=207309 --- Comment #16 from j wandler --- Looking at the configuration options in dolphin 21.12.3, under "Startup" > "General", there is a checkbox for "Open new folders in tabs" with that option either unchecked or checked, the behavior is still to navigate into the clicked on folder like a browser. I don't know what the "Open new folders in tabs" option is meant to do. A middle click with either checked or unchecked also just opens the clicked on folder will open in a new tab, but never a new window. Looks like the functionality has been entirely removed, and the only way to get a folder opened in a new window is to right click and select open in new window. After so many years, I doubt the functionality is coming back. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 459506] New: Crash when moving a rotoscoped clip to a different timeline track
https://bugs.kde.org/show_bug.cgi?id=459506 Bug ID: 459506 Summary: Crash when moving a rotoscoped clip to a different timeline track Classification: Applications Product: kdenlive Version: 22.08.1 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: is_...@yahoo.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. place clip with rotoscope on timeline track 2 2. attempt to move it down to track 1 3. crash occurs OBSERVED RESULT crash EXPECTED RESULT clip to be moved to track 1 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Kernel: 5.4.0-125-generic x86_64 bits: 64 compiler: gcc v: 9.4.0 Desktop: Cinnamon 5.0.7 wm: muffin dm: LightDM Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 466172] SIGTRAP crash whenever getaddrinfo call is issued by valgrind
https://bugs.kde.org/show_bug.cgi?id=466172 --- Comment #8 from Mike J --- Hi. This bug can be closed. It is not caused by valgrind. In case it is of use in future to anyone, further checks have shown that TaniumClient version 7.4.9.1046 was running on the system and caused the problem. valgrind was working on the system with an earlier TaniumClient release, but stopped working when the TaniumClient package was upgraded late last year, affecting valgrind runs. As indirectly noted in the earlier comments, the C library getaddrinfo() function is dynamically loaded when first called by an application. I took valgrind out of the picture and ran "/usr/bin/hostname -d" under the control of the gdb debugger. - With TaniumClient running, on entry to getaddrinfo(), the int3 instruction is seen instead of the expected push %rbp instruction, corrupting the call stack and raising a SIGTRAP. If run with valgrind, valgrind catches the raised SIGTRAP signal in this case and exits with a core dump, showing a corrupt call stack. - When TaniumClient is stopped, the expected push %rbp instruction is instead seen. If run with valgrind, it runs correctly and completes normally. Thanks to Paul Floyd and Mark Wielaard for checking the problem and debugging advice which pointed me in the right direction for problem diagnosis. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468381] New: Bad Option: Switch to that Virtual Desktop
https://bugs.kde.org/show_bug.cgi?id=468381 Bug ID: 468381 Summary: Bad Option: Switch to that Virtual Desktop Classification: Plasma Product: kwin Version: 5.27.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: czzcy3832...@gmail.com Target Milestone: --- SUMMARY *** The option `System Settings > Window Management > Window Behavior > Advanced > When activating a window on a different desktop` does not work. Whether i set it to `Switch to that Virtual Desktop` or another, and then run `xdg-open .` the exist dolphin window will move to current virtual desktop. `xdg-open https://google.com`, `xdg-open .`, `XDG_CURRENT_DESKTOP=X-Generic xdg-open .` and `XDG_CURRENT_DESKTOP=KDE xdg-open .` are tested. *** STEPS TO REPRODUCE 1. Set `System Settings > Window Management > Window Behavior > Advanced > When activating a window on a different desktop` to `Switch to that Virtual Desktop`. Check `Open new folders in tabs` in dolphin. 2. Open a dolphin window. 3. Switch to another desktop. 4. Run `xdg-open .` OBSERVED RESULT It will be switched to the desktop which holds the dolphin window. EXPECTED RESULT The dolphin window would be moved to the current desktop. SOFTWARE/OS VERSIONS Linux: Manjaro (available in About System) KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 KWin Version: 5.27.3 gui platform: x11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372035] Crash while typing PHP code
https://bugs.kde.org/show_bug.cgi?id=372035 --- Comment #5 from Julio J. --- Hi Justin, I think you can close this ticket, it's been a while since I've used KDevelop for PHP so I don't think I'd be able to reproduce it now. If I ever find it again I'll report it again. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 460076] New: Gmail integration requires application password
https://bugs.kde.org/show_bug.cgi?id=460076 Bug ID: 460076 Summary: Gmail integration requires application password Classification: Applications Product: kmail2 Version: 5.20.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: l7i20j...@mozmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Kmail cannot connect to Gmail if 2-factor authentication is set on a Google Account. Instead, a less secure App Password must be used. STEPS TO REPRODUCE 1. Open Kmail 2. Connect outgoing mail to a Google Account OBSERVED RESULT An App Password is required. EXPECTED RESULT Kmail (and all of Kontact) should use the Online Accounts intergation built into KDE. SOFTWARE/OS VERSIONS Linux: Fedora 36 (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 460191] New: kOrganizer asks me to log in to Google, even though I'm logged in already.
https://bugs.kde.org/show_bug.cgi?id=460191 Bug ID: 460191 Summary: kOrganizer asks me to log in to Google, even though I'm logged in already. Classification: Applications Product: korganizer Version: 5.20.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: groupware Assignee: kdepim-b...@kde.org Reporter: l7i20j...@mozmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When using Google Accounts with kOrganizer, the either kOrganizer or the akonadi daemon opens a page to log into your Google account whenever the computer connects to the internet, despite properly syncing with Google Calendar—even if you close the tab. STEPS TO REPRODUCE 1. Use Google Calendar with kOrganzier 2. Turn off the internet, and turn it back on. OBSERVED RESULT A browser tab opens asking you to sign into your Google account, even though your account is connected properly. EXPECTED RESULT No browser tab opens unless there is a problem SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 36 KDE Spin (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION I don't know if this is a problem with Akonadi or kOrganizer. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 460521] New: Saving layouts not complete
https://bugs.kde.org/show_bug.cgi?id=460521 Bug ID: 460521 Summary: Saving layouts not complete Classification: Applications Product: kdenlive Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: is_...@yahoo.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When you export a layout to use on a different PC using kdenlive, the export function does not copy the timeline toolbar. STEPS TO REPRODUCE 1. Export the kdenlive layout to a file 2. Import that same layout file into a different install on different PC 3. OBSERVED RESULT The timeline changes made by the user do not copy to the layout file and are not imported into the install on a different PC EXPECTED RESULT The layout should be identical to the one exported from the source. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460752] New: Frozen image when window is snapped into corner under X11
https://bugs.kde.org/show_bug.cgi?id=460752 Bug ID: 460752 Summary: Frozen image when window is snapped into corner under X11 Classification: Plasma Product: kwin Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: avery.jettf...@tutanota.com Target Milestone: --- The image will appear frozen when snapped into any corner under X11. This issue does not seem to affect Wayland. STEPS TO REPRODUCE 1. Snap an application such as Firefox, Chromium, or Okular into a corner OBSERVED RESULT The image appears frozen and does not respond to mouse input until unsnapped. Also, some buttons are cut off when snapped. EXPECTED RESULT The image displays correctly and responds when snapped into corner SOFTWARE/OS VERSIONS OS: Manjaro Linux 6.0.2-3-MANJARO KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460752] Frozen image when window is snapped into corner under X11
https://bugs.kde.org/show_bug.cgi?id=460752 --- Comment #2 from Avery J. --- (In reply to Nate Graham from comment #1) > Did this happen in Plasma 5.25? I don't believe so. As far as I can tell, this issue began occurring after the update to 5.26. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 465389] New: Zooming on your calendar is janky and sometimes crashes Korganizer/Kontact
https://bugs.kde.org/show_bug.cgi?id=465389 Bug ID: 465389 Summary: Zooming on your calendar is janky and sometimes crashes Korganizer/Kontact Classification: Applications Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: l7i20j...@mozmail.com Target Milestone: --- Application: kontact (5.22.0 (22.12.0)) Qt Version: 5.15.7 Frameworks Version: 5.101.0 Operating System: Linux 6.1.9-100.fc36.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 36 (KDE Plasma) DrKonqi: 5.26.4 [KCrashBackend] -- Information about the crash: Zooming in and out on the calendar view or Kontact and Korganizer is very janky. The events don't scale with alongside the calendar itself, and the user can even zoom so far in or out the calendar events just give up and go back to the default view. This is caused zooming with CTRL+scroll. Zooming can occasionally cause the program to outright crash with SIGSEGV. It's kind of a shame that Kontact and its suite are so buggy their current state, because they have so much potential to mesh with the rest of KDE. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7fd06bf2a7de in QtSharedPointer::ExternalRefCountData::getAndRef(QObject const*) () from /lib64/libQt5Core.so.5 #5 0x7fd06cdad6cb in QWeakPointer& QWeakPointer::assign(QObject*) [clone .isra.0] () from /lib64/libQt5Widgets.so.5 #6 0x7fd06cdb8757 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #7 0x7fd06c0a8278 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #8 0x7fd06ce0c75f in QWidgetWindow::handleWheelEvent(QWheelEvent*) () from /lib64/libQt5Widgets.so.5 #9 0x7fd06ce0e075 in QWidgetWindow::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #10 0x7fd06cdaed12 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #11 0x7fd06c0a8278 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #12 0x7fd06c567206 in QGuiApplicationPrivate::processWheelEvent(QWindowSystemInterfacePrivate::WheelEvent*) () from /lib64/libQt5Gui.so.5 #13 0x7fd06c54a02c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #14 0x7fd061a073f4 in userEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5WaylandClient.so.5 #15 0x7fd062a73faf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #16 0x7fd062ac92c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #17 0x7fd062a71940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #18 0x7fd06c0f938a in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #19 0x7fd06c0a6cca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #20 0x7fd06c0aed92 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #21 0x5577302335f7 in main () [Inferior 1 (process 3751) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488750] New: Laptop Touchpad Not Detected/Working in Neon/Plasma 6
https://bugs.kde.org/show_bug.cgi?id=488750 Bug ID: 488750 Summary: Laptop Touchpad Not Detected/Working in Neon/Plasma 6 Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: jdver...@duck.com CC: j...@jriddell.org, neon-b...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Touchpad Not Detected/Working in Neon/Plasma 6 STEPS TO REPRODUCE 1. No cursor on boot 2. System settings --> Mouse & Trackpad --> Trackpad 3. No Trackpad found OBSERVED RESULT Built-in trackpad not detected/not working EXPECTED RESULT Either trackpad works on boot, or can be enabled in preferences SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.5.0-1 generic (64 bit) (available in About System) KDE Plasma Version: 6.1 (also in 6.0) KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Touchscreen and usb pointers work as expected. Only issue with built-in touchpad -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488750] Laptop Touchpad Not Detected/Working in Neon/Plasma 6
https://bugs.kde.org/show_bug.cgi?id=488750 --- Comment #2 from J Vernet --- Sorry, I uninstalled Synaptics per this: <https://discuss.kde.org/t/settings-says-no-touchpad-found/14139> (even though my issue differed, as my touchpad wasn't working and not just undetected) There was no result, so I didn't include it in the report. My mistake. On 6/19/2024 2:55 PM, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=488750 > > Nate Graham changed: > > What|Removed |Added > > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > CC||n...@kde.org > > --- Comment #1 from Nate Graham --- > Did you remove or mask the Libinput drivers, and you were previously using the > Synaptics drivers? If so, that's the cause: Synaptics drivers are not > supported > in Plasma 6. > -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488750] Laptop Touchpad Not Detected/Working in Neon/Plasma 6
https://bugs.kde.org/show_bug.cgi?id=488750 --- Comment #4 from J Vernet --- Created new, clean account. Hard restarted. No change. On 6/20/2024 10:26 AM, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=488750 > > --- Comment #3 from Nate Graham --- > Does the issue reproduce in a new clean user account on the same machine? > -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488750] Laptop Touchpad Not Detected/Working in Neon/Plasma 6
https://bugs.kde.org/show_bug.cgi?id=488750 --- Comment #6 from J Vernet --- Sorry, the last time it worked was when it was running Win10 previous to the neon install (this was the first Linux install on this machine) So given your request, I'll try another install, and if it starts working again, I'll try to reverse engineer why and update Thanks for your help! On 6/20/2024 2:10 PM, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=488750 > > --- Comment #5 from Nate Graham --- > Ok, so this suggests a missing package or a root-level configuration issue on > the machine. > > To rule out other possibilities, when was the last time this worked? And when > id did work, was it showing the old Synaptics UI (with a test area and > configurable inertia) or the Libinput UI with a "left handed mode" checkbox? > -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488750] Laptop Touchpad Not Detected/Working in Neon/Plasma 6
https://bugs.kde.org/show_bug.cgi?id=488750 --- Comment #8 from J Vernet --- (I had a feeling about that) Thank you, Nate! On 6/20/2024 4:50 PM, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=488750 > > Nate Graham changed: > > What|Removed |Added > > Resolution|WAITINGFORINFO |UPSTREAM > Status|NEEDSINFO |RESOLVED > > --- Comment #7 from Nate Graham --- > Aha, if it has never worked on Linux, then I think it's more likely this is a > driver issue, I'd recommend reporting it at > https://gitlab.freedesktop.org/libinput/libinput/-/issues/. > -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 478769] Permission denied for sshfs-mounted filesystem with android 13 / latest kdeconnect app
https://bugs.kde.org/show_bug.cgi?id=478769 Jakub J changed: What|Removed |Added CC||k@broken.toxcorp.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 478769] Permission denied for sshfs-mounted filesystem with android 13 / latest kdeconnect app
https://bugs.kde.org/show_bug.cgi?id=478769 --- Comment #2 from Jakub J --- Same here. What works though is `ls mountdir/storage/emulated/0` -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 489584] New: Baloo Search stuck, complains about the
https://bugs.kde.org/show_bug.cgi?id=489584 Bug ID: 489584 Summary: Baloo Search stuck, complains about the Classification: Plasma Product: krunner Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: filesearch Assignee: baloo-bugs-n...@kde.org Reporter: l7i20j...@mozmail.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de, plasma-b...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When searching using baloo6, the search indexer does nothing. Purge does nothing, disabling does nothing, enabling does nothing. When checking the status, the file indexer returns "Baloo Index could not be opened." Monitoring shows the program is doing nothing. This is incredibly frustrating, as there is seemingly no cause as the program is too cryptic to understand. Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.6-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i7-1255U Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: HP Product Name: HP ENVY x360 2-in-1 Laptop 15-ew0xxx System Version: Type1ProductConfigId -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478014] New: Switch on Desktop Edge should only show screen edge glows when there's a desktop that can be switched to in that direction.
https://bugs.kde.org/show_bug.cgi?id=478014 Bug ID: 478014 Summary: Switch on Desktop Edge should only show screen edge glows when there's a desktop that can be switched to in that direction. Classification: Plasma Product: plasmashell Version: master Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: l7i20j...@mozmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Switch on Desktop Edge allows the user to switch virtual desktops just by moving the cursor to an edge of the screen. I find it very useful for dragging windows to other virtual desktops. The UI uses the screen edge glows to indicate this is going to occur, which is very useful. However, it is very misleading and unintuitive when the glow shows even when there is no desktop to go to in that direction. An edge glow should only appear when there is a desktop that can be switched to. STEPS TO REPRODUCE 1. Enable Switch on Desktop Edge (either on Always or Only While Dragging windows). 2. Move the cursor (or drag a window) to an edge of the screen where there is no virtual desktop to switch to. OBSERVED RESULT The glow appears regardless of whether or not a virtual desktop can be switched to in that direction. This is misleading and makes the experience feel very unpolished. EXPECTED RESULT The glow should only appear when there is a virtual desktop that can be switched to in that direction. This is much more intuitive. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.6.2-201.fc39.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 476882] Plasma System Monitor does not open up in Fedora GNOME
https://bugs.kde.org/show_bug.cgi?id=476882 Allexus J changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- Ever confirmed|0 |1 --- Comment #4 from Allexus J --- $ plasma-systemmonitor QSocketNotifier: Can only be used with threads started with QThread QQmlApplicationEngine failed to load component qrc:/main.qml:89:21: Type NewStuff.Action unavailable file:///usr/lib64/qt5/qml/org/kde/newstuff/Action.qml:184:13: Type NewStuff.Page unavailable file:///usr/lib64/qt5/qml/org/kde/newstuff/Page.qml:20:1: module "org.kde.kcm" is not installed and then hangs forever -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482501] New: KDE Connect SMS crashed when sending message
https://bugs.kde.org/show_bug.cgi?id=482501 Bug ID: 482501 Summary: KDE Connect SMS crashed when sending message Classification: I don't know Product: kde Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: j.gahba...@gmail.com Target Milestone: --- Application: kdeconnect-sms (23.08.1) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.5.0-21-lowlatency x86_64 Windowing System: Wayland Distribution: Ubuntu 23.10 DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: Application crashed when or just after sending a SMS message via an Android phone connected via Wifi. KDE Connect Android app set to "never sleep." No other unusual activity noticed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KDE Connect SMS (kdeconnect-sms), signal: Segmentation fault [KCrash Handler] #4 0x7fc93e9a4705 in QDBusAbstractInterface::asyncCallWithArgumentList(QString const&, QList const&) () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #5 0x565075f1306c in ?? () #6 0x565075f151bb in ?? () #7 0x7fc93ecd0ac3 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fc93eba99b9 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7fc93ebab8e0 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7fc93ebc898d in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7fc93ebcc107 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7fc93eb5d566 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x7fc93eceb521 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x7fc93ec9c1ef in QQmlBoundSignalExpression::evaluate(void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x7fc93ec9d978 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #16 0x7fc93ecd059f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x7fc93d705a6c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fc93cf8223b in QQuickAbstractButton::qt_metacall(QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #19 0x7fc93cf826a9 in QQuickButton::qt_metacall(QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #20 0x7fc93ecd0ac3 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #21 0x7fc93eba852d in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #22 0x7fc93ebab8e0 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #23 0x7fc93ebc898d in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #24 0x7fc93ebcc107 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #25 0x7fc93eb5d566 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #26 0x7fc93eceb521 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #27 0x7fc93ec9c1ef in QQmlBoundSignalExpression::evaluate(void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #28 0x7fc93ec9d978 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #29 0x7fc93ecd059f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #30 0x7fc93d705a6c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x7fc93f2518dd in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #32 0x7fc93d6d808e in QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fc93f256648 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #34 0x7fc93f255693 in QQuickItemPrivate::filterKeyEvent(QKeyEvent*, bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #35 0x7fc93f264c89 in QQuickItemPrivate::deliverKeyEvent(QKeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #36 0x7fc93f264f60 in QQuickItem::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #37 0x7fc93e36bc82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #38 0x7fc93d6cc7a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #39 0x7fc93f273
[plasmashell] [Bug 477939] Center-aligned panels cause left/right/top/bottom aligned panels sharing the same edge to not touch that edge
https://bugs.kde.org/show_bug.cgi?id=477939 Julio J. changed: What|Removed |Added CC||julioelpo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484875] On X11, after locking screen and turning off monitor, panels are occasionally placed in the wrong position
https://bugs.kde.org/show_bug.cgi?id=484875 --- Comment #15 from J Bosse --- Created attachment 170179 --> https://bugs.kde.org/attachment.cgi?id=170179&action=edit Panel at top of screen "defloated" downwards after setting the panel position to the top and switching the monitor off and on again this is how the panel looks and it won't move regardless if there is a window touching or not. Note: the window is maximized, and not intentionally moved behind the panel. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 476882] Plasma System Monitor does not open up in Fedora GNOME
https://bugs.kde.org/show_bug.cgi?id=476882 Allexus J changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|DOWNSTREAM |--- Ever confirmed|1 |0 --- Comment #6 from Allexus J --- (In reply to Nate Graham from comment #5) > file:///usr/lib64/qt5/qml/org/kde/newstuff/Page.qml:20:1: module > "org.kde.kcm" is not installed > > This is caused by missing dependencies on your system. I'd recommend > contacting the Fedora people about it. now I have a different output. $ plasma-systemmonitor QSocketNotifier: Can only be used with threads started with QThread -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 473816] Weather Report Stops Fetching Data
https://bugs.kde.org/show_bug.cgi?id=473816 j.gahba...@gmail.com changed: What|Removed |Added CC||j.gahba...@gmail.com Platform|Fedora RPMs |Ubuntu --- Comment #1 from j.gahba...@gmail.com --- I have noticed this, as well. However, as of today (31 Jan 2024), toggling to other weather services and back to NOAA does not fix the issue. No updates are fetched. (Note: the non-NOAA weather services are much less accurate for many US locations). -- You are receiving this mail because: You are watching all bug changes.
[docs.kde.org] [Bug 480757] New: "Activities" description appears to be incomplete
https://bugs.kde.org/show_bug.cgi?id=480757 Bug ID: 480757 Summary: "Activities" description appears to be incomplete Classification: Websites Product: docs.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: docs.kde.org Assignee: kde-doc-engl...@kde.org Reporter: j.gahba...@gmail.com Target Milestone: --- SUMMARY "Activities" documentation is not clear about the function of Activities and does not describe them fully. The current documentation does not make clear that: 1) Activities can contain multiple desktops and can therefore be thought of as *sets* of Desktops, and 2) "Activities" allow Plasma to be used across different "modes" of use - e.g., personal, business, etc, and to assign different pinned taskbar programs, widgets, and unique wallpapers to each. This is very useful; I suggest simpler language to elaborate and clarify the utility of this unique Plasma function. ADDITIONAL INFORMATION Documentation is here: https://docs.kde.org/stable5/en/plasma-desktop/plasma-desktop/activities-interface.html I would be happy to contribute sample text if helpful. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447637] Activity bar widget. Activity name gets cut in half when opening settings
https://bugs.kde.org/show_bug.cgi?id=447637 j.gahba...@gmail.com changed: What|Removed |Added CC||j.gahba...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466649] [Activity Pager] Panel activity switcher text sometimes disappears
https://bugs.kde.org/show_bug.cgi?id=466649 j.gahba...@gmail.com changed: What|Removed |Added CC||j.gahba...@gmail.com Version|5.26.5 |5.27.8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477939] On Wayland, center-aligned panels cause left/right/top/bottom aligned panels sharing the same edge to not touch that edge
https://bugs.kde.org/show_bug.cgi?id=477939 Ethan J changed: What|Removed |Added CC||l7i20j...@mozmail.com --- Comment #21 from Ethan J --- I an am also experiencing the bug after release on Fedora 40. -- You are receiving this mail because: You are watching all bug changes.
