[dolphin] [Bug 492362] Dolphin - "Folders" (F7) Left panel content disappears after suspend/resume PC (X11)

2024-09-01 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=492362 --- Comment #2 from YAFU --- Hi. It's probably not a KDE bug. Before the Dolphin problem appeared I had been trying to fix some problems with Kernel 6.8 and nvidia, and maybe I messed it up by modifying something. I've reverted some c

[dolphin] [Bug 492362] Dolphin - "Folders" (F7) Left panel content disappears after suspend/resume PC (X11)

2024-08-29 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=492362 YAFU changed: What|Removed |Added Summary|Dolphin - "Folders" (F7)|Dolphin - "Folders" (F7)

[dolphin] [Bug 492362] Dolphin - "Folders" (F7) Left panel content disappears after suspend/resume PC

2024-08-29 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=492362 --- Comment #1 from YAFU --- Correction: Where says "" should be " and I mean that there shows the location where it was before suspend/resume action (My English is not good and Google translator either) -- You are receiving this ma

[dolphin] [Bug 492362] New: Dolphin - "Folders" (F7) Left panel content disappears after suspend/resume PC

2024-08-29 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=492362 Bug ID: 492362 Summary: Dolphin - "Folders" (F7) Left panel content disappears after suspend/resume PC Classification: Applications Product: dolphin Version: 24.08.0 Platform:

[dolphin] [Bug 483031] New: Dolphin: I can't RMB > "Open terminal here" or shortcut to open terminal/konsole

2024-03-09 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=483031 Bug ID: 483031 Summary: Dolphin: I can't RMB > "Open terminal here" or shortcut to open terminal/konsole Classification: Applications Product: dolphin Version: 24.02.0 Platfor

[plasmashell] [Bug 450119] Plasma slow/freezes on resume - possible memory leak?

2022-03-19 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=450119 --- Comment #11 from YAFU --- Hello. Distro: KDE Neon user edition (Updated - X11) Nvidia GTX 960 - 510.54 I have the same kind of problem as the user who opened the report and it also started happening from about the same date. Actually, KDE/Plasma

[plasmashell] [Bug 403563] Memory leak in plasma desktop (plasmashell)

2021-04-18 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=403563 --- Comment #12 from YAFU --- Hi. I see that there are many similar reports about Plasmashell Memory Leak problem occurring even to this day. I don't use slideshow wallpaper. I never power off my PC, I always sleep/suspend to RAM. I can suspend t

[kmenuedit] [Bug 430768] Shortcut in KMenuEdit does not work with scripts in /usr/bin

2020-12-23 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=430768 --- Comment #2 from YAFU --- Ok, this is driving me crazy. I have tried recreating the steps for a whole new script, with a whole new entry in KMenuEdit and a whole new shortcut and it worked. But then removing that new entry and trying to configure

[kmenuedit] [Bug 430768] Shortcut in KMenuEdit does not work with scripts in /usr/bin

2020-12-23 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=430768 --- Comment #1 from YAFU --- In the description in Step 1 I forgot the step that you have to give the script permission to execute, of course. $ sudo chmod +x screenpowersave.sh -- You are receiving this mail because: You are watching all bug changes.

[kmenuedit] [Bug 430768] Shortcut in KMenuEdit does not work with scripts in /usr/bin

2020-12-23 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=430768 YAFU changed: What|Removed |Added Platform|Other |Neon Packages Version|unspecified

[kmenuedit] [Bug 430768] New: Shortcut in KMenuEdit does not work with scripts in /usr/bin

2020-12-23 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=430768 Bug ID: 430768 Summary: Shortcut in KMenuEdit does not work with scripts in /usr/bin Product: kmenuedit Version: unspecified Platform: Other OS: Linux

[frameworks-kxmlgui] [Bug 430388] Custom Shortcuts cannot record key presses

2020-12-23 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=430388 --- Comment #28 from YAFU --- Entering new shortcuts now works here in KDE Neon (Testing). Thanks to all the developers. @Nate Graham, sorry for my attitude. Regardless of what was causing the problem, perhaps I should have opened the new report from

[kmenuedit] [Bug 430481] New: Custom Shortcuts cannot record key presses (Kmenuedit)

2020-12-16 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=430481 Bug ID: 430481 Summary: Custom Shortcuts cannot record key presses (Kmenuedit) Product: kmenuedit Version: 5.20.4 Platform: Neon Packages OS: Linux Status: REPORTED

[systemsettings] [Bug 430388] Custom Shortcuts cannot record key presses

2020-12-16 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=430388 --- Comment #7 from YAFU --- If they have different system shortcuts, then you look for the source of the problem in Qt/GUI and the field type for shortcut input. I don't believe in these kinds of coincidences. -- You are receiving this mail be

[systemsettings] [Bug 430388] Custom Shortcuts cannot record key presses

2020-12-16 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=430388 --- Comment #4 from YAFU --- And I get the same error with kmenuedit: kf.guiaddons: Cannot record without a window -- You are receiving this mail because: You are watching all bug changes.

[systemsettings] [Bug 430388] Custom Shortcuts cannot record key presses

2020-12-16 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=430388 --- Comment #3 from YAFU --- In both cases from System Settings or KDE Menu Editor the same thing happens, when you click on the field to enter a new key combination, the field does not react and it keeps showing "none" (or old key combinatio

[systemsettings] [Bug 421329] New Global Shortcuts KCM: shortcuts to launch 3rd-party apps don't work

2020-12-15 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=421329 --- Comment #42 from YAFU --- Apparently the new problem that I have where it is not possible to enter new shortcuts is the same as this report: https://bugs.kde.org/show_bug.cgi?id=430388 Regarding previous reports where keyboard shortcuts for third

[systemsettings] [Bug 430388] Custom Shortcuts cannot record key presses

2020-12-15 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=430388 --- Comment #1 from YAFU --- Hi. The same thing is happening to me when I want to configure keyboard shortcuts from KDE Menu Editor. KDE Neon (Testing) KDE Frameworks Version: 5.77.0 -- You are receiving this mail because: You are watching all bug

[kmenuedit] [Bug 417495] Application launcher shortcuts well recorded but launch nothing

2020-12-13 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=417495 --- Comment #31 from YAFU --- Not only has this never been fixed, it is even worse. KDE Menu Editor won't even let me enter new combinations keys. So, what to do? Using KDE 5.76.0 from KDE Neon (Testing) -- You are receiving this mail because

[systemsettings] [Bug 421329] New Global Shortcuts KCM: shortcuts to launch 3rd-party apps don't work

2020-12-13 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=421329 --- Comment #38 from YAFU --- I come from here: https://bugs.kde.org/show_bug.cgi?id=417495 Not only has this never been fixed, it is even worse. KDE Menu Editor won't even let me enter new combinations keys. So, what to do? Using KDE 5.76.0 fro

[neon] [Bug 429029] Neon (Testing) Plasmashell crash with segmentation fault

2020-11-13 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=429029 --- Comment #5 from YAFU --- There is a note on the p-state plasmoid site: >The widget breaks the whole desktop if you are using Qt 5.15.1. The point is, Plasma should be safer for the user. It should not happen that a plasmoid can break everyth

[neon] [Bug 429029] Neon (Testing) Plasmashell crash with segmentation fault

2020-11-13 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=429029 --- Comment #4 from YAFU --- I installed "libkf5plasma5-dbgsym" y "plasma-workspace-dbg" packages. This is the output of "gdb": === === = $ gdb plasmashell GNU gdb (Ubuntu 9.2-0ubuntu1~20.0

[neon] [Bug 429029] Neon (Testing) Plasmashell crash with segmentation fault

2020-11-13 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=429029 --- Comment #3 from YAFU --- @David Redondo The documentation appears to be out of date. Currently there is no kdelibs5-dbgsym package for example. >Always install kdelibs5-dbgsym, because all KDE applications use kdelibs -- You are receiving t

[neon] [Bug 429029] Neon (Testing) Plasmashell crash with segmentation fault

2020-11-12 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=429029 --- Comment #1 from YAFU --- Other users are having similar problems. https://forum.kde.org/viewtopic.php?f=309&t=168758 Apparently last update brought incompatibility with some plasmoids. In my case the problematic plamsoid was p-state v1.0.6: h

[neon] [Bug 429029] New: Neon (Testing) Plasmashell crash with segmentation fault

2020-11-12 Thread YAFU
asma/extras/PlasmoidHeading.qml:53:5: Unable to assign [undefined] to int file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components.3/ComboBox.qml:74:9: Unable to assign [undefined] to QQmlComponent* kf.config.core: Access to ' "/home/yafu/Escritorio/user-home.desktop" &

[neon] [Bug 427992] Neon "libkf5solid5" incompatible with Ubuntu "libudev1" (Testing)

2020-10-19 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=427992 --- Comment #3 from YAFU --- As this has been resolved with the latest packages, I mark this as fixed. I'm not sure if only moderators were allowed to do it, sorry if that's the case. -- You are receiving this mail because: You are watchi

[neon] [Bug 427992] Neon "libkf5solid5" incompatible with Ubuntu "libudev1" (Testing)

2020-10-19 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=427992 YAFU changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[neon] [Bug 427992] Neon "libkf5solid5" incompatible with Ubuntu "libudev1" (Testing)

2020-10-19 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=427992 --- Comment #2 from YAFU --- I switched back to Testing repositories. Apparently today there have been changes in this regard and I can update correctly now. Sorry I didn't try this today, I didn't know there were changes. -- You are rece

[neon] [Bug 427992] Neon "libkf5solid5" incompatible with Ubuntu "libudev1" (Testing)

2020-10-19 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=427992 --- Comment #1 from YAFU --- I clarify that this was until yesterday. Then I switched to "user" repositories. So if there were changes today in "testing" that fixed the problem, I have not tested it. -- You are receiving this m

[neon] [Bug 427992] New: Neon "libkf5solid5" incompatible with Ubuntu "libudev1" (Testing)

2020-10-19 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=427992 Bug ID: 427992 Summary: Neon "libkf5solid5" incompatible with Ubuntu "libudev1" (Testing) Product: neon Version: unspecified Platform: Other OS: Linux

[khotkeys] [Bug 417495] Application launcher shortcuts well recorded but launch nothing

2020-04-04 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=417495 --- Comment #16 from YAFU --- Hi. Have the developers been able to reproduce this problem? Do you need us to share more information about our systems where the problem is present? I hope this issue is resolved before Kubuntu 20.04 is officially

[kmenuedit] [Bug 417495] kde menu editor, user defined shortcuts well recorded but launch nothing

2020-03-16 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=417495 --- Comment #6 from YAFU --- System: Kubuntu 20.04 (beta) 64bits KDE/Plasma 5.18.3 I have installed Kubuntu 20.04 pre beta a couple of months ago (upgrading it from Kubuntu 18.04). Keyboard shortcuts configured from "KDE menu editor" work

[kmenuedit] [Bug 417495] kde menu editor, user defined shortcuts well recorded but launch nothing

2020-03-16 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=417495 YAFU changed: What|Removed |Added CC||yafuli...@gmail.com --- Comment #5 from YAFU

[kmenuedit] [Bug 418871] New shortcuts from KDE menu editor don't work

2020-03-16 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=418871 YAFU changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[pulseaudio-qt] [Bug 418874] Changing device profile to HDMI is reset to default after monitor goes into powersave

2020-03-15 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=418874 --- Comment #1 from YAFU --- Sorry, I think I confused the website and this report does not belong to KDE. This is the correct report: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/826 -- You are receiving this mail because: You are

[pulseaudio-qt] [Bug 418874] New: Changing device profile to HDMI is reset to default after monitor goes into powersave

2020-03-15 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=418874 Bug ID: 418874 Summary: Changing device profile to HDMI is reset to default after monitor goes into powersave Product: pulseaudio-qt Version: 1.2 Platform: Other O

[kmenuedit] [Bug 418871] New: New shortcuts from KDE menu editor don't work

2020-03-15 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=418871 Bug ID: 418871 Summary: New shortcuts from KDE menu editor don't work Product: kmenuedit Version: 5.18.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Se

[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset

2018-04-13 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=385324 --- Comment #16 from YAFU --- @Markus, Thank you very much for the workaround. I have the same problem in Kubuntu 18.04. Currently 390.48 nvidia driver installed. Most of the time when I resume/wake up PC from sleep/suspend to RAM, I get "De

[plasmashell] [Bug 370975] device notifier pretends it cannot mount usb device while actually mounting it

2018-03-25 Thread YAFU
https://bugs.kde.org/show_bug.cgi?id=370975 --- Comment #25 from YAFU --- Currently 5.12 or 5.44 plasma packages in Kubuntu 18.04. = I have this problem when trying to mount any removable device or internal disk partition, either from Dolphin or from removable device manager in panel. It