[dolphin] [Bug 483031] New: Dolphin: I can't RMB > "Open terminal here" or shortcut to open terminal/konsole
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 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: terminal Assignee: dolphin-bugs-n...@kde.org Reporter: yafuli...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY In Dolphin, external Konsole/Terminal it is not opened with keyboard shortcuts to do so or with the Right Mouse Button > Open Terminal Here STEPS TO REPRODUCE 1. Open Dolphin 2. (Right Mosue Button > Open Terminal Here) or (Keyboard shortcut to open konsole in folder) OBSERVED RESULT Nothing happens. If I open Dolphin from terminal this is the output with "Open Terminal Here" action): $ dolphin qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile true actions!!! Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8. Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead. If this causes problems, reconfigure your locale. See the locale(1) manual for more information. qt.qpa.xcb: could not connect to display qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin. qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: minimalegl, vkkhrdisplay, eglfs, wayland, minimal, offscreen, wayland-egl, vnc, xcb, linuxfb. EXPECTED RESULT The expected thing would be for Konsole to open in the location where Dolphin is, but nothing happens SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kde Neon User Edition (X11) KDE Plasma Version: 6.0 KDE Frameworks Version: 6.0 according "kinfocenter". Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450119] Plasma slow/freezes on resume - possible memory leak?
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 has always given me some kind of problems when resuming from suspend mode, whether related to Kwin and effects and compositing problems, or Plasma slowness issues and plasmashell incremental memory usage every time I resume from suspend mode (needed to kill and restart plasmashell). But these kinds of problems were not as frequent as the one that started happening about a month ago. Now the problem occurs about 1 out of 3 times wehen resume from suspend mode. Killing plasmashell and restarting the process fixes the problem (but it's very annoying to have to do this so frequently) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403563] Memory leak in plasma desktop (plasmashell)
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 to RAM and resume the PC several times without plasmashell memory leak problem happening, but suddenly sometime when I resume the PC the problem starts to occur and I can notice it when I resume from suspend to RAM and I get a little freeze in Plasma until it does it becomes responsive after a few seconds. So from this point I start to check Plasmashell RAM usage, and from this point the problem after suspending RAM and Resume is always reproducible. From this point every time you suspend to RAM and Resume, plasmashell increases RAM usage up to a lot and plasma becomes slower every time. I'm not sure how to debug the problem when it occurs in order to provide some useful information. -- 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
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 old KMenuEdit entry with that new script never worked again. I have not been able to determine when it works and when it does not. -- 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
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
https://bugs.kde.org/show_bug.cgi?id=430768 YAFU changed: What|Removed |Added Platform|Other |Neon Packages Version|unspecified |5.20.4 -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 430768] New: Shortcut in KMenuEdit does not work with scripts in /usr/bin
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 Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: yafuli...@gmail.com Target Milestone: --- SUMMARY Keyboard shortcuts created from KMenuEdit for scripts in /usr/bin do not work. STEPS TO REPRODUCE 1.Create a Script in /usr/bin, for example $ kate /usr/bin/screenpowersave.sh With content: #!/bin/bash sleep 5; xset dpms force standby 2. Open KMenu edit, create a new entry to launch the script, In General tab, select the script in Command field: /usr/bin/screenpowersave.sh 3. In Advanced tab create a new keyboard shortcut to launch the script, and save the changes OBSERVED RESULT When you press the keyboard shortcut to run the script, it is not executed EXPECTED RESULT Run the script SOFTWARE/OS VERSIONS KDE Neon 20.04 (Testing) KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 ADDITIONAL INFORMATION The method I describe above had always worked for me. It stopped working about a year ago when many bugs related to custom keyboard shortcuts had also been reported. Run the script from the Applications Menu or run "/usr/bin/screenpowersave.sh" from Krunner, the script is executed correctly. Only trying to run with the configured shortcut en KMenuEdit doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 430388] Custom Shortcuts cannot record key presses
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 the beginning just in case. -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 430481] New: Custom Shortcuts cannot record key presses (Kmenuedit)
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 Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: yafuli...@gmail.com Target Milestone: --- Created attachment 134125 --> https://bugs.kde.org/attachment.cgi?id=134125=edit A short video to demonstrate the issue SUMMARY I couldn't set shortcut keys in KDE Menu Editor, Advanced tab, "Current Shortcut Key" setting because it failed to record my key presses. STEPS TO REPRODUCE 1. Open KDE Menu Editor and select some app 2. Open "Advanced" tab. 3. In "Current Shortcut Key" click in shortcut field and Press desired key or key combination to set the shortcut. OBSERVED RESULT Key presses were not recorded. The shortcut button still showed "None". A line of error "kf.guiaddons: Cannot record without a window" appeared in terminal every time when pressing the shortcut button. EXPECTED RESULT Key presses are correctly recorded. SOFTWARE/OS VERSIONS Operating System: KDE Neon (Testing) KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430388] Custom Shortcuts cannot record key presses
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 because: You are watching all bug changes.
[systemsettings] [Bug 430388] Custom Shortcuts cannot record key presses
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
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 combination) and new key combination is not entered. The problem is recent and happens in both cases at the same time. The source of the problem should be the same, or is it really a very strange coincidence. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421329] New Global Shortcuts KCM: shortcuts to launch 3rd-party apps don't work
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-party apps/scripts do not work, some of the reports about it had been closed as duplicates to this one, but had never actually been resolved. When the new bug is fixed and I can continue testing, I may open a new report about the old problem if it continues to occur. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430388] Custom Shortcuts cannot record key presses
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 changes.
[kmenuedit] [Bug 417495] Application launcher shortcuts well recorded but launch nothing
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: You are watching all bug changes.
[systemsettings] [Bug 421329] New Global Shortcuts KCM: shortcuts to launch 3rd-party apps don't work
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 from KDE Neon (Testing) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 429029] Neon (Testing) Plasmashell crash with segmentation fault
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 everything and leave the user without an environment. There should be some kind of safe mode where plasmashell enters in case of a problem -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 429029] Neon (Testing) Plasmashell crash with segmentation fault
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.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from plasmashell...
Reading symbols from
/usr/lib/debug/.build-id/df/73274d93b770a186f37963d5074fe11faa2bd9.debug...
(gdb) run
Starting program: /usr/bin/plasmashell
[Depuración de hilo usando libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Nuevo Thread 0x70e98700 (LWP 56429)]
[Nuevo Thread 0x7fffebf32700 (LWP 56430)]
kf.plasma.quick: Applet preload policy set to 1
[Nuevo Thread 0x7fffeac3c700 (LWP 56431)]
Cyclic dependency detected between
"file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
and
"file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
[Detaching after fork from child process 58638]
[Detaching after fork from child process 58784]
file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:445:13:
QML ToolButton: Binding loop detected for property "icon.height"
file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:431:13:
QML ToolButton: Binding loop detected for property "icon.height"
file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:411:17:
QML ToolButton: Binding loop detected for property "icon.height"
file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:398:17:
QML ToolButton: Binding loop detected for property "icon.height"
file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:385:17:
QML ToolButton: Binding loop detected for property "icon.height"
file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:372:17:
QML ToolButton: Binding loop detected for property "icon.height"
file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:160:13:
QML TextArea: Binding loop detected for property "implicitWidth"
[Nuevo Thread 0x7fffdb200700 (LWP 58812)]
qml: Reading places from configuration:
[{"providerId":"yrno","placeIdentifier":"Argentina/Córdoba/Córdoba","placeAlias":"Córdoba"}]
[Nuevo Thread 0x7fffda9ff700 (LWP 58813)]
qml: Reading places from configuration:
[{"providerId":"yrno","placeIdentifier":"Argentina/Córdoba/Córdoba","placeAlias":"Córdoba"}]
qml: cacheBackend failed to initialize
qml: Reading places from configuration:
[{"providerId":"yrno","placeIdentifier":"Argentina/Córdoba/Córdoba","placeAlias":"Córdoba"}]
[Nuevo Thread 0x7fffd9c20700 (LWP 58814)]
[Nuevo Thread 0x7fffd93f8700 (LWP 58815)]
[Thread 0x7fffd9c20700 (LWP 58814) terminado]
[Thread 0x7fffd93f8700 (LWP 58815) terminado]
trying to show an empty dialog
file:///home/yafu/.local/share/plasma/plasmoids/org.kde.weatherWidget/contents/ui/CompactRepresentation.qml:38:5:
Unable to assign [undefined] to double
file:///home/yafu/.local/share/plasma/plasmoids/org.kde.weatherWidget/contents/ui/CompactRepresentation.qml:36:5:
Unable to assign [undefined] to double
trying to show an empty dialog
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19:
QML Loader: Binding loop detected for property "height"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19:
QML Loader: Binding loop detected for property "height"
[Nuevo Thread 0x7fffd93f8700 (LWP 58816)]
file:///home/yafu/.local/share/plasma/plasmoids/org.kde.weatherWidget/contents/ui/CompactRepresentation.qml:38:5:
Unable to assign [undefined] to double
file:///home/yafu/.local/share/plasma/plasmoids/org.kde.weatherWidget/contents/ui/CompactRepresentation.qml:36:5:
Unable to assign [undefined] to double
file:///usr/share/plasma/plasm
[neon] [Bug 429029] Neon (Testing) Plasmashell crash with segmentation fault
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 this mail because: You are watching all bug changes.
[neon] [Bug 429029] Neon (Testing) Plasmashell crash with segmentation fault
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=168758 Apparently last update brought incompatibility with some plasmoids. In my case the problematic plamsoid was p-state v1.0.6: https://store.kde.org/p/1282623/ https://github.com/jsalatas/plasma-pstate But, in case of some plasmoid losing compatibility, we shouldn't have this problem where the user runs out of desktop environment, right? At most a message that tells us that a plasmoid is no longer supported, but not this I guess. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 429029] New: Neon (Testing) Plasmashell crash with segmentation fault
https://bugs.kde.org/show_bug.cgi?id=429029 Bug ID: 429029 Summary: Neon (Testing) Plasmashell crash with segmentation fault Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Testing Edition Assignee: neon-b...@kde.org Reporter: yafuli...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Neon (Testing) 20.04 After installing many updates of today Thursday 12 November, when I reboot the PC then plasmashell it loads for a second but then I get a completely black screen. When starting plasmashell from the terminal the same thing happens. This is the end of the output I get in the terminal: === file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/Tooltip.qml:66:9: QML GridLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth" file:///usr/share/plasma/plasmoids/org.kde.panel/contents/ui/main.qml:30:1: QML DropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumHeight" file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:200:17: QML Binding: Not restoring previous value because restoreMode has not been set. This behavior is deprecated. You have to import QtQml 2.15 after any QtQuick imports and set the restoreMode of the binding to fix this warning. In Qt < 6.0 the default is Binding.RestoreBinding. In Qt >= 6.0 the default is Binding.RestoreBindingOrValue. Error: cannot change the containment to AppletsLayout libkcups: CUPS-Get-Printers last error: 1030 No se han añadido destinos. libkcups: Create-Printer-Subscriptions last error: 0 successful-ok libkcups: Get-Jobs last error: 0 successful-ok libkcups: Get-Jobs last error: 0 successful-ok Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationHeader.qml" qml: +++ new BUtton textsDesactivar,Cancelar qml: +++ new BUtton textsDesactivar,Cancelar file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components/Dialog.qml:308:9: QML QQuickItem: Binding loop detected for property "height" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components/Dialog.qml:308:9: QML QQuickItem: Binding loop detected for property "height" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components/Dialog.qml:274:5: QML QQuickItem: Binding loop detected for property "width" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components/Dialog.qml:274:5: QML QQuickItem: Binding loop detected for property "width" qml: in external window file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:53:17: Unable to assign [undefined] to int file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlasmoidHeading.qml:53:5: Unable to assign [undefined] to int libkcups: 0 libkcups: 0 trying to show an empty dialog file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" trying to show an empty dialog Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. trying to show an empty dialog qt.svg: link #use3956 is undefined! file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/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" ' denied, not owned by root, executable flag not set. kf.config.core: Access to ' "/home/yafu/Escritorio/user-home.desktop" ' denied, not owned by root, executable flag not set. kf.config.core: Access to ' "/home/yafu/Escritorio/trash-can.desktop" ' denied, not owned by root, executable flag not set. kf.config.core: Access to ' "/home/yafu/Escritorio/trash-can.desktop" ' denied, not owned by root, executable flag not set. kf.config.core: Access to ' "/home/yafu/Escrito
[neon] [Bug 427992] Neon "libkf5solid5" incompatible with Ubuntu "libudev1" (Testing)
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 watching all bug changes.
[neon] [Bug 427992] Neon "libkf5solid5" incompatible with Ubuntu "libudev1" (Testing)
https://bugs.kde.org/show_bug.cgi?id=427992 YAFU changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 427992] Neon "libkf5solid5" incompatible with Ubuntu "libudev1" (Testing)
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 receiving this mail because: You are watching all bug changes.
[neon] [Bug 427992] Neon "libkf5solid5" incompatible with Ubuntu "libudev1" (Testing)
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 mail because: You are watching all bug changes.
[neon] [Bug 427992] New: Neon "libkf5solid5" incompatible with Ubuntu "libudev1" (Testing)
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 Status: REPORTED Severity: normal Priority: NOR Component: Packages Testing Edition Assignee: neon-b...@kde.org Reporter: yafuli...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Hi. Neon 20.04 (testing) For a few days I have been having a dependency problem with "libkf5solid5_5.75.0+p20.04+git20201017.0151-0_amd64.deb" package. Apparently it depends on libudev1 >=246.6, but Ubuntu 20.04 repositories version is 245.4. $ pkcon update Getting updates [=] Finished [=] Loading cache [ == ] QCommandLineParser: already having an option named "h" QCommandLineParser: already having an option named "help-all" QCommandLineParser: already having an option named "v" [=] Testing changes [=] Finished [=] Fatal error: The following packages have unmet dependencies: libkf5solid5: Depende: libkf5solid5-data (= 5.75.0+p20.04+git20201015.0112-0) but 5.75.0+p20.04+git20201017.0151-0 is to be installed == == I clarify that my installation is not a pure Neon installation. I had a Kubuntu 20.04 installation to which I added Neon repository (testing), and after various dependencies fixes using "aptitude", I was able to have Neon without problems, until a few days ago where this problem appeared. Related Thread: https://forum.kde.org/viewtopic.php?f=309=168336=438685# There are other people there having problems with udev too. -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 417495] Application launcher shortcuts well recorded but launch nothing
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 released. -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 417495] kde menu editor, user defined shortcuts well recorded but launch nothing
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" worked about a month ago. I think from some Kubuntu update about a month ago, new keyboard shortcuts configured from "KDE menu editor" don't work (old shortcuts configured from "KDE menu editor" still work). -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 417495] kde menu editor, user defined shortcuts well recorded but launch nothing
https://bugs.kde.org/show_bug.cgi?id=417495 YAFU changed: What|Removed |Added CC||yafuli...@gmail.com --- Comment #5 from YAFU --- *** Bug 418871 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 418871] New shortcuts from KDE menu editor don't work
https://bugs.kde.org/show_bug.cgi?id=418871 YAFU changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from YAFU --- *** This bug has been marked as a duplicate of bug 417495 *** -- You are receiving this mail because: You are watching all bug changes.
[pulseaudio-qt] [Bug 418874] Changing device profile to HDMI is reset to default after monitor goes into powersave
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 watching all bug changes.
[pulseaudio-qt] [Bug 418874] New: Changing device profile to HDMI is reset to default after monitor goes into powersave
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 OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: nicolas.fe...@gmx.de Reporter: yafuli...@gmail.com Target Milestone: --- System: Kubuntu 20.04 beta 64bits There is an old report, but this still happens: https://bugs.freedesktop.org/show_bug.cgi?id=93946 The problem sometimes happens when monitor enters power save mode or when I suspend/resume the system. The device is set to headphones by default when the problem occurs. == === My audio devices output: $ pactl list sinks Sink #0 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.hdmi-stereo Description: Built-in Audio Digital Stereo (HDMI) Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 6 Mute: no Volume: front-left: 36700 / 56% / -15,11 dB, front-right: 36700 / 56% / -15,11 dB balance 0,00 Base Volume: 65536 / 100% / 0,00 dB Monitor Source: alsa_output.pci-_00_1b.0.hdmi-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE DECIBEL_VOLUME LATENCY SET_FORMATS Properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "HDMI 0" alsa.id = "HDMI 0" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "3" alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf791 irq 36" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1e20" device.product.name = "7 Series/C216 Chipset Family High Definition Audio Controller (P8Z77-V LX Motherboard)" device.form_factor = "internal" device.string = "hdmi:0" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "hdmi-stereo" device.profile.description = "Digital Stereo (HDMI)" device.description = "Built-in Audio Digital Stereo (HDMI)" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: hdmi-output-0: HDMI / DisplayPort (priority: 5900, available) Active Port: hdmi-output-0 Formats: pcm = == Mentioned workaround in old previous report still works: https://askubuntu.com/questions/776883/pulseaudio-drops-hdmi-output-at-screen-power-save -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 418871] New: New shortcuts from KDE menu editor don't work
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 Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: yafuli...@gmail.com Target Milestone: --- 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" worked about a month ago. I think from some Kubuntu update about a month ago, new keyboard shortcuts configured from "KDE menu editor" don't work (old shortcuts configured from "KDE menu editor" still work). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 --- Comment #16 from YAFU <yafuli...@gmail.com> --- @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 "Desktop effects were restarted due to a graphics reset" message and the composition breaks down, it starts blinking/flickering in Brisa window decorator title bar, the task manager in panel starts to work wrong, some applications are not shown and panel becomes full transparent. It is really annoying. Running Markus script returns everything to normal. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370975] device notifier pretends it cannot mount usb device while actually mounting it
https://bugs.kde.org/show_bug.cgi?id=370975 --- Comment #25 from YAFU <yafuli...@gmail.com> --- 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 always shows an error message when you try to mount the device first time, the device is not opened in Dolphin but it is mounted correctly. Then at the second attempt it does not show error message and device is opened in Dolphin. The messages that I get in Spanish: >From Dolphin: "Ocurrió un error al acceder a «Carpeta personal», el sistema respondió: El dispositivo ya está montado: Device /dev/sdb3 is already mounted at `/media/yafu/PART 1'." >From removable device manager in panel a window message titled "Error Cliente KIO ?" and "Formato de URL erroneo" message. By the way, in a recent Dolphin update, when you mount partitions from the small folder/home icon to the left of the Dolphin address bar (that icon only appears if you have Panels > Places disabled), every time you Mount a device from there that menu is filled enormously with "Umount <>" items. Really annoying. -- You are receiving this mail because: You are watching all bug changes.
