[neon] [Bug 476481] Firefox Crashes de whole OS, mostly but not only, when watching videos.
https://bugs.kde.org/show_bug.cgi?id=476481 --- Comment #1 from Sebastian Gauna --- Please can someone respond to this? I can't use Firefox anymore, I don't wan't to stop using it, but I have to. If we don't support Firefox, it's going to dissapear and Chromium will take 100% over... -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 476481] New: Firefox Crashes de whole OS, mostly but not only, when watching videos.
https://bugs.kde.org/show_bug.cgi?id=476481 Bug ID: 476481 Summary: Firefox Crashes de whole OS, mostly but not only, when watching videos. Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: gau...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY I don't know how long ago, probably no more than two months, my system began crashing mostly when viewing videos in Youtube with Firefox. Although it also crashed once just having Whatsapp Web opened. Let me point out that I didn't do any hardware change. STEPS TO REPRODUCE 1. Open Firefox 2. Start watching videos on YouTube 3. Wait until everything crashes OBSERVED RESULT Both of my screens go black, but the mouse cursor remains visible and frozen. Audio keeps working, for instance, if I'm having a remote call, the call continues, I can still talk with the other party. If I was sharing screen, I ask the other party to tell my if my cursor moves when I move the mouse, and it doesn't. It seems all inputs get frozen since I cannot even access any tty with CTRL+ALT+FX The only thing I can do at this point is a hard reset. EXPECTED RESULT To be able to use Firefox wihout any crashes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.27 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Graphics Platform: X11 Graphic Card: ASUSTeK Computer Inc. Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] ADDITIONAL INFORMATION I usually run xanmod kernel but I tried with the general kernel and the problem is exactly the same. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 475581] New: Keyboard Shurtcuts to access tty not working as expected.
https://bugs.kde.org/show_bug.cgi?id=475581 Bug ID: 475581 Summary: Keyboard Shurtcuts to access tty not working as expected. Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: gau...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY I used to have access to tty2 through tty6 with CTRL+ALT+F2 to F6 and back to deskto with CTRL+ALT+F1 Now (I don't really now since when), it does not behave like that STEPS TO REPRODUCE 1. From Desktop press CTRL+ALT+F1 through F6 OBSERVED RESULT CTRL+ALT+F1 takes me to (kind of) a boot log that says: - With kernel 6.5.7-x64v1-xanmod1 => [FAILED] Failed to start LSB: OpenIPMI Driver Init script. - With kernel generic 6.2.0-34 => [ 0.160030] x86/cpu: SGX disabled by BIOS. CTRL+ALT+F2 takes me to Desktop. CTRL+ALT+F3 through F6 take me to tty3 to tty6 No access to tty2 EXPECTED RESULT CTRL+ALT+F1 should take me to Desktop and +F2 though F6 to the corresponding tty SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.27 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465016] Dolphin started treating files/folders with hidden property set in NTFS files the same as any Linux hidden file/folder
https://bugs.kde.org/show_bug.cgi?id=465016 --- Comment #8 from Sebastian Gauna --- I appreciate it, thanks. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465016] Dolphin started treating files/folders with hidden property set in NTFS files the same as any Linux hidden file/folder
https://bugs.kde.org/show_bug.cgi?id=465016 --- Comment #6 from Sebastian Gauna --- Felix, there's something strange here, I would bet that this wasn't behaving like this short time ago... I felt there was some update that changed it... Am I wrong? Was this like this since long time ago? (or even the begining of Dolphin) If I am, and this was always like this, my apologies, I know that people (like me) get used to things and you'll start getting reports the other way around... But I really started noticing it recently, I might be wrong though. If this was alwyas like this, I would only suggest to add an option to configure the behavior. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465016] Dolphin started treating files/folders with hidden property set in NTFS files the same as any Linux hidden file/folder
https://bugs.kde.org/show_bug.cgi?id=465016 --- Comment #4 from Sebastian Gauna --- I'll try to explain myself better. What's the normal or expected behavior in Linux for a file to be hidden? A hidden file in Linux has to be a Dotfile. Would you expect a file to be hidden in Windows if its name begins with a dot but the file is not marked hidden? I think this behavior breaks the "Principle of Least Astonishment" from a Linux perspective. What I didn't have into consideration is that Dolphin can be run in Windwos as well. But, why not use a differentiated bahavior depending on the installed OS? Why should Dolphin behave differently than a terminal in Linux? It makes no sense to me, or at least I think there should be an option to change the behavior and the default in Linux, IMHO, should be to show hidden NTFS files as normal files, not even grayed out. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465016] Dolphin started treating files/folders with hidden property set in NTFS files the same as any Linux hidden file/folder
https://bugs.kde.org/show_bug.cgi?id=465016 --- Comment #2 from Sebastian Gauna --- Felix, I think this is a very opinionated behavior... And I think there is no right or wrong, but that's also why I think there should be an option to change it. I'm pretty sure this was not happening before, I'm used to see the hidden NTFS files as regular Linux files from KDE. Usually, hidden files are system files or not user files right? So, to me, a file that is a system file in Windows makes no sense to be hidden in Linux... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465016] New: Dolphin started treating files/folders with hidden property set in NTFS files the same as any Linux hidden file/folder
https://bugs.kde.org/show_bug.cgi?id=465016 Bug ID: 465016 Summary: Dolphin started treating files/folders with hidden property set in NTFS files the same as any Linux hidden file/folder Classification: Applications Product: dolphin Version: 22.12.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: gau...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY The files and folders set to hidden in NTFS files/folders are now not shown if you don't enable "Show hidden files", and once you enable that option, they appear grayed out. It seems there's no option to change that behavior. This is Dolphin specific since if you list the files in a terminal (without -a option) they are treated as not hidden files/folders I also changed the driver back from ntfs to ntfs-3g to see if that made a difference but no, there wasn't any. If there are people to whom this is useful, shouldn't all the rest of us have an option to change that behavior? STEPS TO REPRODUCE 1. Set a file or folder as "hidden" in a NTFS drive (I do it from my Windows dual boot, don't know how to do it in Linux) 2. Open the containing folder in Dolphin OBSERVED RESULT If the option "Show hidden files" is not set, you won't see the file/folder EXPECTED RESULT I expect to see the file as any non "dot hidden" Linux file. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.26 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462845] The default button changed to Cancel at permanent delete
https://bugs.kde.org/show_bug.cgi?id=462845 Sebastian Gauna changed: What|Removed |Added CC||gau...@gmail.com --- Comment #19 from Sebastian Gauna --- This was a terrible change to me, glad it wasn't intentional, I hope it'll be reverted soon. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461417] spice-vdagentd not autostarting due to "X-GNOME-Autostart-Phase" in desktop file; consider patching it out
https://bugs.kde.org/show_bug.cgi?id=461417 --- Comment #18 from Sebastian Gauna --- OK, thanks -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461417] spice-vdagentd not autostarting due to "X-GNOME-Autostart-Phase" in desktop file; consider patching it out
https://bugs.kde.org/show_bug.cgi?id=461417 --- Comment #16 from Sebastian Gauna --- So then the problem is not happening in Ubuntu because it uses Gnome, and it's no happening in Kubuntu because they probably patched it for that distro? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461417] spice-vdagentd not running at startup and cannot be enabled to do it
https://bugs.kde.org/show_bug.cgi?id=461417 --- Comment #12 from Sebastian Gauna --- Output of 'systemctl --version' is 'systemd 249 (249.11-0ubuntu3.6)' for the three of them. Output of 'apt list --installed spice*' is 'spice-vdagent/jammy,now 0.22.1-1 amd64 [installed,automatic]' for the three of them as well. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461417] spice-vdagentd not running at startup and cannot be enabled to do it
https://bugs.kde.org/show_bug.cgi?id=461417 --- Comment #10 from Sebastian Gauna --- (In reply to Nate Graham from comment #7) > If the output and outcome of running `sudo systemctl enable spice-vdagentd` > is different between Ubuntu/Kubuntu and Neon, that's due to either > differences in those distros' Systemd versions and configurations, or > differences in the service files for spice which come from the app that > provides them, not any KDE software code. Moving to Neon. Actually in Ubuntu/Kubuntu there's no need to run 'sudo systemctl enable spice-vdagentd' it just enabled by default -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461417] spice-vdagentd not running at startup and cannot be enabled to do it
https://bugs.kde.org/show_bug.cgi?id=461417 --- Comment #9 from Sebastian Gauna --- Both my host and VMs are 22.04 My host was a 20.04 ugraded to 22.04 and the VMs are installed with the latest ISO -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461417] spice-vdagentd not running at startup and cannot be enabled to do it
https://bugs.kde.org/show_bug.cgi?id=461417 --- Comment #6 from Sebastian Gauna --- Sorry, I'm not a Linux expert, I don't understand exactly how it works, because spice has 2 executables: /usr/bin/spice-vdagent /usr/sbin/spice-vdagentd There is no .desktop file as far as I can see, it runs as a service It just comes preinstalled out of the box in Ubuntu, Kubuntu and Neon but in Neon the service is not enabled... if you throw a 'sudo service spice-vdagent status' or 'sudo service spice-vdagentd status' in a fresh and clean installation of Ubuntu or Kubuntu you get: Loaded: loaded (/lib/systemd/system/spice-vdagentd.service; indirect; vendor preset: enabled) Active: active (running) since Sat 2022-11-05 10:51:41 -03; 1h 26min ago TriggeredBy: ● spice-vdagentd.socket Process: 1162 ExecStart=/usr/sbin/spice-vdagentd $SPICE_VDAGENTD_EXTRA_ARGS (code=exited, status=0/SUCCESS) Main PID: 1164 (spice-vdagentd) Tasks: 2 (limit: 4551) Memory: 960.0K CPU: 3.711s CGroup: /system.slice/spice-vdagentd.service └─1164 /usr/sbin/spice-vdagentd ^^ Now if you do the same in a fresh install of Neon you get: ○ spice-vdagentd.service - Agent daemon for Spice guests Loaded: loaded (/lib/systemd/system/spice-vdagentd.service; indirect; vendor preset: enabled) Active: inactive (dead) TriggeredBy: ● spice-vdagentd.socket ^^ And in Neon if you try to enable the service, you get the error I posted... The file /lib/systemd/system/spice-vdagentd.service has de the same content in the three distros I really don't know what else to look for. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461417] spice-vdagentd not running at startup and cannot be enabled to do it
https://bugs.kde.org/show_bug.cgi?id=461417 --- Comment #4 from Sebastian Gauna --- I can confirm you that this is a Neon specific problem since I just installed a Kubuntu 22.04 VM guest and spice-vdagentd starts just fine by default. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461417] spice-vdagentd not running at startup and cannot be enabled to do it
https://bugs.kde.org/show_bug.cgi?id=461417 --- Comment #3 from Sebastian Gauna --- I mean, I installed nothing form QEMU in the Neon guest as I didn't either in the Ubuntu guest. In a fresh installation of Ubuntu service spice-vdagentd is installed and started by default. In a fresh installation of Neon it's not even enabled. There's no QEMU involved here as far as I can tell, QEMU is in my host. Besides, being that KDE Neon is Ubuntu, it seems to me that something was modified in Neon. Sorry, I don't understand why I should report this to QEMU... -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461417] spice-vdagentd not running at startup and cannot be enabled to do it
https://bugs.kde.org/show_bug.cgi?id=461417 --- Comment #2 from Sebastian Gauna --- (In reply to Nate Graham from comment #1) > As that error message shows, the systemd service file is misconfigured. > You'll need to report this to the QEMU people. Sorry if I didn't explain myself well, the error happens inside the VM within the guest, not in the host, besides it works just fine in Ubuntu 22.04 guests... -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461417] New: spice-vdagentd not running at startup and cannot be enabled to do it
https://bugs.kde.org/show_bug.cgi?id=461417 Bug ID: 461417 Summary: spice-vdagentd not running at startup and cannot be enabled to do it Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: gau...@gmail.com Target Milestone: --- SUMMARY When running KDE Neon as a VM guest in QEMU, I'm not getting screen auto-resize or clipboard sharing, etc. I have to manually run 'spice-vdagent'. It works out of the box in Ubuntu though. If I want to enable the service with 'sudo systemctl enable spice-vdagentd I get: vvv The unit files have no installation config (WantedBy=, RequiredBy=, Also=, Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. vvv STEPS TO REPRODUCE 1. Run KDE Neon guest VM in QEMU 2. Open it with Virtual Machine Manager or Remove Viewer 3. If opening it with Virtual Machine Manager enable the option "Autoresize VM with window" 4. Resize VM window. 5. Also, copy something to clipboard in your host 6. Try to paste it in your guest 7. Copy something to clipboard in your guest 8. Try to paste it in your host OBSERVED RESULT Guest resolution does not adjust. Clipboard sharing does not occur. EXPECTED RESULT Auto adjust guest resolution. Clipboard sharing. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.26 KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[kdemultimedia] [Bug 454174] New: Thumbnails within Dolphin for at least MP4 and JPG files no longer working on NTFS partitions
https://bugs.kde.org/show_bug.cgi?id=454174 Bug ID: 454174 Summary: Thumbnails within Dolphin for at least MP4 and JPG files no longer working on NTFS partitions Product: kdemultimedia Version: 22.04.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ffmpegthumbs Assignee: unassigned-b...@kde.org Reporter: gau...@gmail.com Target Milestone: --- SUMMARY I have some partitions in NTFS mounted with ntfs-3g, and thumbnails for at least mp4 and jpg files (didn't try other formats) don't work anymore. Thumbs in my ext4 partitions work as expected. STEPS TO REPRODUCE 1. Mount a NTFS drive with ntfs-3g 2. Place some JPG and/or MP4 files anywhere in the partition 3. Open with Dolphin the location where the files reside OBSERVED RESULT Thumbnails for files not being generated, I just get the standard multimedia Icon corresponding to the file format. EXPECTED RESULT The thumbnail for each file should show up. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.24 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93 Qt Version: 5.15.3 ADDITIONAL INFORMATION I can't tell when this started happening since I've been out home for three months, when I started using my computer again I did all the updates and there's when it stoped working. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 452533] "Stop charging at" not saved after restart.
https://bugs.kde.org/show_bug.cgi?id=452533 --- Comment #2 from Sebastian Gauna --- (In reply to Nate Graham from comment #1) > Do you have an Asus laptop? If so, this is Bug 450551. What hardware are you > using? Oh my! Yes... An Asus M515 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 452533] New: "Stop charging at" not saved after restart.
https://bugs.kde.org/show_bug.cgi?id=452533 Bug ID: 452533 Summary: "Stop charging at" not saved after restart. Product: Powerdevil Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gau...@gmail.com Target Milestone: --- SUMMARY The value of "Stop charging at" in "Advance Power Settings" is not kept after restarting. STEPS TO REPRODUCE 1. Got to Advanced Power Settings 2. Set te valu of "Stop charing at" to a different value than 100% 3. Click Apply 4. Restart OBSERVED RESULT If system is not restarted the value is kept and respected, the battery stops charging at the configured value. After a system restart the value goes back to 100% EXPECTED RESULT The value should stay as configured even after restart or shutdown. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.24 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 439018] Wrong (?) "Storage Device Problem" SMART notification.
https://bugs.kde.org/show_bug.cgi?id=439018 --- Comment #2 from Sebastian Gauna --- Anyone there? -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 439018] Wrong (?) "Storage Device Problem" SMART notification.
https://bugs.kde.org/show_bug.cgi?id=439018 Sebastian Gauna changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 439018] Wrong (?) "Storage Device Problem" SMART notification.
https://bugs.kde.org/show_bug.cgi?id=439018 --- Comment #1 from Sebastian Gauna --- Created attachment 139586 --> https://bugs.kde.org/attachment.cgi?id=139586=edit SMART Status GOOD and one off value -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 439018] New: Wrong (?) "Storage Device Problem" SMART notification.
https://bugs.kde.org/show_bug.cgi?id=439018 Bug ID: 439018 Summary: Wrong (?) "Storage Device Problem" SMART notification. Product: plasma-disks Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gau...@gmail.com CC: sit...@kde.org Target Milestone: --- Created attachment 139585 --> https://bugs.kde.org/attachment.cgi?id=139585=edit System Tray Notification SUMMARY I don't know if this is the correct component to fill the bug for. I started getting a "Storage Device Problem" pop up notification from the System Tray when I start the OS, in two computers running the exact same KDE Neon. If check the SMART status within KDE Partition Manager or any other tool, the status of the disks is actualy good in both computers There is just some off value for "Ultra DMA CRC Error Count" in one of them, and in the other disk I don't get to see what might be wrong, and I don't know how to get what's the value SMART is complaining about. EXPECTED RESULT Probably notifying just once? Or giving the option to dismiss any further notification for that exact same issue? Being that the actual SMART status is GOOD. I know I can get rid of that message by dismissing the drive completely, but for obvious reasons I don't want to do that. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon User Edition KDE Plasma Version: 5.22.1 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION One of my disks is a HDD and the other an SATA SDD. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438662] Disk & Devices suddenly pops-up from System Tray when pressing ESC key
https://bugs.kde.org/show_bug.cgi?id=438662 --- Comment #15 from Sebastian Gauna --- I installed KDE Neon in a VM, updated everything to leave it just like my primary OS, but I couldn't duplicate de issue. So I presume that the bug in question is just that I can't delete the setting permanently, but not also that it appeared out of nowhere. Probably some program caused this, but it should still be considered a bug the fact that I cannot delete the setting right? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438834] Discover Notifier Icon incorrectly shows up with "Updates Available" notification.
https://bugs.kde.org/show_bug.cgi?id=438834 --- Comment #3 from Sebastian Gauna --- My KDE Neon is not a brand new installation, I don't remember exactly but It's been several months since I've installed it. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438834] New: Discover Notifier Icon incorrectly shows up with "Updates Available" notification.
https://bugs.kde.org/show_bug.cgi?id=438834 Bug ID: 438834 Summary: Discover Notifier Icon incorrectly shows up with "Updates Available" notification. Product: Discover Version: 5.22.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifier Assignee: aleix...@kde.org Reporter: gau...@gmail.com Target Milestone: --- SUMMARY Discover Notifier shows the "Updates Available" icon in the System Tray but there are actually no updates. STEPS TO REPRODUCE Just start the system and the tray icon appears. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.22 User Edition KDE Plasma Version: 5.22.1 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION It doesn't matter if you go to Discover and click "Check for Updates" (which shows no updates), or if you right click the system tray icon and select "Refresh" (which does nothing), or if you do a pkcon refresh && pkcon update (wich shows no updates available), there is no way to make the icon dissapear unless you explicitly right click on it an select "QUIT" I don't think that it has something to do with this problem but know that I uninstalled snap, anyway this problem started very recently and I uninstalled snap long time ago. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438662] Disk & Devices suddenly pops-up from System Tray when pressing ESC key
https://bugs.kde.org/show_bug.cgi?id=438662 --- Comment #13 from Sebastian Gauna --- But there's another thing, I never added that shortcut key configuration, it just appeared... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438662] Disk & Devices suddenly pops-up from System Tray when pressing ESC key
https://bugs.kde.org/show_bug.cgi?id=438662 --- Comment #11 from Sebastian Gauna --- Created attachment 139399 --> https://bugs.kde.org/attachment.cgi?id=139399=edit plasma-org.kde.plasma.desktop-appletsrc -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438662] Disk & Devices suddenly pops-up from System Tray when pressing ESC key
https://bugs.kde.org/show_bug.cgi?id=438662 --- Comment #9 from Sebastian Gauna --- I just uploaded the file, thanks for the path hint! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438662] Disk & Devices suddenly pops-up from System Tray when pressing ESC key
https://bugs.kde.org/show_bug.cgi?id=438662 --- Comment #8 from Sebastian Gauna --- Created attachment 139392 --> https://bugs.kde.org/attachment.cgi?id=139392=edit kglobalshortcutsrc Here it goes the file after removing the shortcut. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438662] Disk & Devices suddenly pops-up from System Tray when pressing ESC key
https://bugs.kde.org/show_bug.cgi?id=438662 --- Comment #5 from Sebastian Gauna --- OK, I was several hours without rebooting and the setting didn't come back on it's own. So that means it only comes back after rebooting. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438662] Disk & Devices suddenly pops-up from System Tray when pressing ESC key
https://bugs.kde.org/show_bug.cgi?id=438662 --- Comment #4 from Sebastian Gauna --- If I delete the setting with the trash can icon and then click Apply, everything gets back to normal until I restart the OS, that's what I meant by "resetting", restarting/rebooting the OS I couldn't replicate the setting comming back without rebooting, I might probably have rebooted without remembering it when I thought the setting came back by its own without rebooting... I'll keep checking this. But I can assure you that rebooting the system gets the setting back even if I deleted it with the trash can and apply it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438662] Disk & Devices suddenly pops-up from System Tray when pressing ESC key
https://bugs.kde.org/show_bug.cgi?id=438662 Sebastian Gauna changed: What|Removed |Added Summary|Disk & Devices suddenly |Disk & Devices suddenly |pops-up from System Trat|pops-up from System Tray |when pressing ESC key |when pressing ESC key -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438662] Disk & Devices suddenly pops-up from System Trat when pressing ESC key
https://bugs.kde.org/show_bug.cgi?id=438662 --- Comment #2 from Sebastian Gauna --- I just noticed that the configuration get's back without even restarting the system, I did nothing, I even went away from the computer and when I came back it was there again... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438662] Disk & Devices suddenly pops-up from System Trat when pressing ESC key
https://bugs.kde.org/show_bug.cgi?id=438662 --- Comment #1 from Sebastian Gauna --- Created attachment 139329 --> https://bugs.kde.org/attachment.cgi?id=139329=edit Settings The configuration in question. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438662] New: Disk & Devices suddenly pops-up from System Trat when pressing ESC key
https://bugs.kde.org/show_bug.cgi?id=438662 Bug ID: 438662 Summary: Disk & Devices suddenly pops-up from System Trat when pressing ESC key Product: systemsettings Version: 5.22.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_khotkeys Assignee: k...@michael-jansen.biz Reporter: gau...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Whenever I press the ESC key, the "Disk & Devices" suddenly started coming up from the System Tray. I found that a config appeared in System Settings -> Shortcuts for "Plasma". I remove it but after resetting the system it appears again. STEPS TO REPRODUCE I just press the Esc Key and the "Disk & Devices" pops-up from System Tray. EXPECTED RESULT The default and typical Esc key behaviour. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon KDE Plasma Version: 5.22 KDE Frameworks Version: 5.83 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430450] Profiles and realtime preview not working
https://bugs.kde.org/show_bug.cgi?id=430450 --- Comment #9 from Sebastian Gauna --- I just applied the update from today and Kosole was updated to v4.20.12.1 The problem seems to be solved. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430450] Profiles and realtime preview not working
https://bugs.kde.org/show_bug.cgi?id=430450 --- Comment #3 from Sebastian Gauna --- @Ahmad Samir, I did what you say and I just got: QObject::connect: signal not found in Konsole::ProfileManager QObject::connect: signal not found in Konsole::ProfileManager QObject::connect: signal not found in Konsole::ProfileManager QObject::connect: signal not found in Konsole::ProfileManager QObject::connect: signal not found in Konsole::ProfileList QObject::connect: signal not found in Konsole::ProfileManager QObject::connect: signal not found in Konsole::ProfileManager QObject::connect: signal not found in Konsole::ProfileManager That's it. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430450] New: Profiles and realtime preview not working
https://bugs.kde.org/show_bug.cgi?id=430450 Bug ID: 430450 Summary: Profiles and realtime preview not working Product: konsole Version: 20.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: emulation Assignee: konsole-de...@kde.org Reporter: gau...@gmail.com Target Milestone: --- SUMMARY Profiles are not working. At the beginning I noticed that when changing colors it wasn't being preview in real time as it used to be. Then I realized that if I create different profiles I does nothing when I select them by using Settings -> Switch Profile. Also the first column that had a checkbox in the Profiles List dissapeared and the list of profiles when going to Settings -> Switch prfiles, contains invalid (non current) entries. STEPS TO REPRODUCE 1. Go to create a new profile. 2. Go to appearance and select a color scheme, it does not preview. 3. Save profile 4. Go to Settings -> Switch Profile OBSERVED RESULT - Color schemes are not previewed in real time - Profiles are not loaded when switching them. EXPECTED RESULT Just the normal functionality... SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77 Qt Version: 5.15.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
