Re: Bookworm: Mouse cursor issues after upgrading to FireFox v128?
Il 08/10/24 17:44, local10 ha scritto: Hi, Problem: After upgrading to Firefox v128 from v115, Firefox seems to have stopped using some mouse cursors as per the active KDE mouse cursor theme (the Oxygen White theme, in my case). For some reason, instead of showing the white arrow mouse cursor as per the theme, FF now shows a black mouse cursor. Used to work fine in FF v115 (and many prior FF versions) before the upgrade. More info: 1. The issue appears to affect all mouse cursor themes (Adwaita, all Oxygen, etc) with the exception of Breeze cursor themes (maybe because I'm using Breeze global desktop theme?). 2. Only the first (and perhaps the most important) arrow mouse cursor is affected, the rest seem to work properly. For example, with the Oxygen White cursor theme active, FF v128 shows black arrow mouse cursor instead of the white arrow cursor, but also correctly shows the white hand from the the Oxygen White theme when the cursor hovers over the links. 3. With the Breeze Light theme active, FF v128 correctly shows all mouse cursors, including showing the white arrow cursor when appropriate. Any ideas? Thanks KDE global theme: Breeze KDE mouse cursor theme: Oxygen White (other Oxygen mouse cursor themes also have the above issue) $ aptitude show firefox-esr Package: firefox-esr Version: 128.3.0esr-1~deb12u1 Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-26-amd64 (64-bit) Graphics Platform: X11 https://bbs.archlinux.org/viewtopic.php?id=293178 -- Saluti, Luca Pedrielli
Re: Black folder icons in Dolphin
Il 18/09/24 19:32, Marc Bres Gil ha scritto: Good afternoon, I saw this mail yesterday and was hoping somebody gives a solution as I am having the same behavior on my testing installation, is not a big deal as everything works, but annoys me every time I open Dolphin. Unfortunately I haven't been able to find a solution, was thinking that may have been some issue with my installation, but as it happens to at least one more person seems that may be something elsewhere. Thanks Marc. My workaround is extract icons from previous breeze-icon-theme in .local/share/icons Missatge de Angus A Mackenzie del dia dt., 17 de set. 2024 a les 14:42: I'm using Unstable amd64, and I note a couple of people have mentioned Breeze icon themed desktops are showing black folder icons instead of the usual blue. Plasma 5.27.11 is in use with frameworks 5.115.0 Is this expected behaviour for now, or have I missed an easy fix? AAM -- Marc Bres Gil m...@bres.cat marc.b...@gmail.com -- Saluti, Luca Pedrielli
Re: Smaller Plasma bugs in unstable
Il 19/08/24 12:53, Aurélien COUDERC ha scritto:
Yes, I saw that. Dolphin icon in Plasma and folder icons inside Gwenview (and
probably other places) are black. Curriously enough, folder icons *inside*
dolphin itself and in file browsing popups are fine.
That’s the only issue I could find now that we’re running a dual kf5+kf6 stack
and I don’t consider it a blocker.
I’m betting on a small breakage of backwards compatibility in breeze-icons
(which is supposed to be backwards compatible), or maybe just in our packaging
? If someone can analyse and find a fix I’m willing to upload it. But I won’t
look into it myself, it’s both transitional and cosmetic issue and there are
more important things to do.
It’s fixed in Plasma 6 which is not 100% ready for unstable prime time yet.
Happy hacking,
--
Aurélien
=
$ diff /usr/share/icons/breeze/places/96/folder.svg
.local/share/icons/test/places/96/folder.svg
7c7
< .ColorScheme-Accent {
---
> .ColorScheme-Highlight {
15c15
< class="ColorScheme-Accent"
---
> class="ColorScheme-Highlight"
=
ColorScheme-Accent seems to be the culprit.
It's a new ColorScheme introduced in Kde Framwork 6.4
As a fix I extracted old breeze icons in .local ;)
--
Saluti, Luca Pedrielli
Re: Smaller Plasma bugs in unstable
Il 19/08/24 12:53, Aurélien COUDERC ha scritto: Yes, I saw that. Dolphin icon in Plasma and folder icons inside Gwenview (and probably other places) are black. Curriously enough, folder icons *inside* dolphin itself and in file browsing popups are fine. That’s the only issue I could find now that we’re running a dual kf5+kf6 stack and I don’t consider it a blocker. I’m betting on a small breakage of backwards compatibility in breeze-icons (which is supposed to be backwards compatible), or maybe just in our packaging ? If someone can analyse and find a fix I’m willing to upload it. But I won’t look into it myself, it’s both transitional and cosmetic issue and there are more important things to do. It’s fixed in Plasma 6 which is not 100% ready for unstable prime time yet. This issue arrived in testing. It is not limited to just the dolphin icon, but all "blue folders" and inode-directory.svg displayed in dolphin and gwenview. rename .cache/icon-cache.kcache and test -- Saluti, Luca Pedrielli
Re: Save session is not working after lastest upgrade
Il 09/06/24 10:23, Martin Šoltis ha scritto: Hi, thanks but this is not the case, I am still on X11. And as I said, it is not working maybe for the last week. Thanks Martin https://bugs.kde.org/show_bug.cgi?id=487936 -- Saluti, Luca Pedrielli
Re: Save session is not working after lastest upgrade
Il 09/06/24 10:23, Martin Šoltis ha scritto: Hi, thanks but this is not the case, I am still on X11. And as I said, it is not working maybe for the last week. Thanks Martin I can confirm. X11 and testing full updated. -- Saluti, Luca Pedrielli
Re: hoe do I use spectacle screen recording?
Il 26/05/24 23:18, Gary Dale ha scritto: I've just switched into a Plasma/Wayland session on my Debian/Trixie AMD64 system so I could try out screen recording with Spectacle. However I can't figure out how to get it to work. I switch to the "recording: tab, and select the video format, but then what? I can select "workspace", "selected screen" or "selected window" , after which clicking somewhere starts recording but the "Finish recording" button seems to react but actually does nothing. The recording timer keeps incrementing and I can't seem to save the recording. Same here. $ spectacle qrc:/src/Gui/CaptureOptions.qml:44:5: QML CaptureSettingsColumn (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth" kpipewire_logging: Stream error: no more input formats kpipewire_logging: PipeWire remote error: -32 no more input formats *** pw_stream_set_active called from wrong context, check thread and locking: Not in loop *** impl_ext_end_proxy called from wrong context, check thread and locking: Not in loop -- Saluti, Luca Pedrielli
Re: Setting minimal mouse double-click interval?
Il 15/06/23 09:39, local10 ha scritto: Hi, Is there a way to set a minimal mouse double-click interval in KDE? By editing some config file or whatever? Thanks Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-9-amd64 (64-bit) Graphics Platform: X11 you can try ~/.config/kdeglobals, [KDE] section, "DoubleClickInterval=" -- Saluti, Luca Pedrielli
Re: Bookworm: Dolphin no longer shows "RMB click > Open with > Other applications" dialog
Il 13/02/23 18:51, Helge Reimer ha scritto: Am Montag, 13. Februar 2023, 18:29:39 CET schrieb luca.pedrielli: is xdg-desktop-portal-kde installed? Now yes. And that solved it. Thanks. I always wonder how you should know about this. It has always worked and suddenly an additional package is needed. Where is that written? if you start dolphin in console a message error says that org.freedesktop.impl.portal.desktop.kde is not found and yes, maybe a dependency is needed -- Saluti, Luca Pedrielli
Re: Bookworm: Dolphin no longer shows "RMB click > Open with > Other applications" dialog
Il 13/02/23 18:16, Helge Reimer ha scritto: Am Montag, 13. Februar 2023, 06:37:37 CET schrieb local10: When doing the above, Dolphin used to show a dialog that would allow to select an alternative app that would be used to open the file but not anymore. I haven't noticed it before because I rarely use it, but here it's the same problem. I'm using Debian Sid with the same Dolphin version 4:22.12.2-1. is xdg-desktop-portal-kde installed? -- Saluti, Luca Pedrielli
Re: Dragging icons at desktop
Il 24/12/22 12:30, Miguel A. Vallejo ha scritto: Interesting... My system is running X on a Intel 530 HD Graphics card. When I drag an icon, and move the mouse pointer slowly, the icon follow the mouse pointer a few centimeters behind moving somewhat irregularly If I move the mouse at "medium" speed, the icon can be 15 or 20 centimeters behind the mouse cursor. If I move the mouse cursor fast, the icon does not move at all until I drop the icon, then it moves slowly from the old to the new position. Otherwise, moving windows is as fast as usual, they move in real time under the mouse pointer without any problem. It happens with any icon, even with icons inside Dolphin or Ark. I must admit I thought it was a new desktop effect. I also noticed plasmashell CPU usage is quite high (around 60 - 65 % CPU usage) while dragging icons. Xorg is also high CPU usage (35 - 40%) while dragging icons. In fact both plasmashell and Xorg CPU usages added are always very close to 100%. They do not use as much CPU moving windows (well under 10%). I didn't see any suspicious problems both in syslog or .xsession-errors Any ideas to find where the problem is? Thanks in advance What happens if you try to suspend the compositor (SHIFT+Alt+F12)? -- Saluti, Luca Pedrielli
Re: Dragging icons at desktop
Il 24/12/22 02:15, Miguel A. Vallejo ha scritto: El lun, 28 nov 2022 a las 23:34, Martin Steigerwald () escribió: Miguel A. Vallejo - 28.11.22, 23:26:52 CET: Recently I noticed when I drag an icon in the desktop (fully updated Sid), the icon lags behind the mouse cursor instead of following the mouse cursor under it as it always did. After almost a month of usage I can't get used to this "feature", it makes the desktop feel sluggish and unresponsive. But I still haven't found where to disable it, so should I open a bug? Against what package? At Debian or KDE? Thanks in advance. I can confirm this issue, but not on all my machines. For example in virtualbox with 3D disabled, drag is immediate, it lags when 3D is enabled. So it seems gpu related. It's ok with my intel graphic card. -- Saluti, Luca Pedrielli
Re: Unable to access SMB shares when credential are needed - kio-extras
kio-extras 4:22.12.0-2 solves. Thanks. -- Saluti, Luca Pedrielli
Discover does not notify about updates
In testing and unstable Discover does not notify about updates since latest packagekit updates. Revert to previous packagekit version solves. -- Saluti, Luca Pedrielli
Re: kded5 crashes
Il 07/12/22 15:47, tv.debian ha scritto: Le 07/12/2022 à 12:25, Diederik de Haas a écrit : On Wednesday, 7 December 2022 11:49:21 CET luca.pedrielli wrote: i removed apper and things seems to be better. waiting for confirmation from the other guys too. I didin't have apper installed to begin with, so maybe that's why I wasn't seeing it? now only plasmashell crashes ;) ... #1 0x7f488f65aef2 raise (libc.so.6 + 0x3bef2) #2 0x7f4891a93be1 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5be1) #3 0x7f488f65af90 n/a (libc.so.6 + 0x3bf90) #4 0x7f4882a1c158 n/a (vmwgfx_dri.so + 0x61c158) #5 0x7f4882a1c343 n/a (vmwgfx_dri.so + 0x61c343) #6 0x7f4882dcbcad n/a (vmwgfx_dri.so + 0x9cbcad) #7 0x7f4882575083 n/a (vmwgfx_dri.so + 0x175083) #8 0x7f48824b0a23 n/a (vmwgfx_dri.so + 0xb0a23) #9 0x7f48824b40cc n/a (vmwgfx_dri.so + 0xb40cc) #10 0x7f48898f9104 n/a (libGLX_mesa.so.0 + 0x43104) #11 0x7f48898e2a38 n/a (libGLX_mesa.so.0 + 0x2ca38) #12 0x7f488ce49ccc n/a (libGLX.so.0 + 0x4ccc) dri, GLX and mesa all point to graphics subsystem, so it's probably useful to share the GPU that you're using. I am not seeing this either out of 6 bare metal machines on SID. Mix of AMD desktop GPU and Intel laptops. None have "Apper" installed, all are running Wayland sessions. There is some KDE noise in the logs, but nothing like what's reported here. Is there a bug report opened somewhere? Here is another example. -- Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. PID: 2597 (plasmashell) UID: 1000 (ilprof) GID: 1000 (ilprof) Signal: 11 (SEGV) Timestamp: Wed 2022-12-07 16:57:47 CET (18s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (ilprof) Boot ID: 305afcfdae664e7a8857639f127e51b5 Machine ID: ad6738af96e1470e8772413d7f9c5dd0 Hostname: unstable Storage: /var/lib/systemd/coredump/core.plasmashell.1000.305afcfdae664e7a8857639f127e51b5.2597.167042866700.zst (present) Size on Disk: 10.5M Message: Process 2597 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.2-2.amd64 Module libudev.so.1 from deb systemd-252.2-2.amd64 Stack trace of thread 2597: #0 0x7f8ba10a9ccc __pthread_kill_implementation (libc.so.6 + 0x8accc) #1 0x7f8ba105aef2 __GI_raise (libc.so.6 + 0x3bef2) #2 0x7f8ba3471be1 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5be1) #3 0x7f8ba105af90 __restore_rt (libc.so.6 + 0x3bf90) #4 0x7f8b9c0fc419 _ZN19QXcbBasicConnection10internAtomEPKc (libQt5XcbQpa.so.5 + 0x6e419) #5 0x7f8b9c0dde6b _ZN8QXcbMime18mimeAtomsForFormatEP14QXcbConnectionRK7QString (libQt5XcbQpa.so.5 + 0x4fe6b) #6 0x7f8b9c0d04c5 _ZN13QXcbClipboard20sendTargetsSelectionEP9QMimeDatajj (libQt5XcbQpa.so.5 + 0x424c5) #7 0x7f8b9c0d1141 _ZN13QXcbClipboard22handleSelectionRequestEP29xcb_selection_request_event_t (libQt5XcbQpa.so.5 + 0x43141) #8 0x7f8b9c0d4616 _ZN14QXcbConnection14handleXcbEventEP19xcb_generic_event_t (libQt5XcbQpa.so.5 + 0x46616) #9 0x7f8b9c0d5946 _ZN14QXcbConnection16processXcbEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5XcbQpa.so.5 + 0x47946) #10 0x7f8b9c0fbc73 xcbSourceDispatch (libQt5XcbQpa.so.5 + 0x6dc73) #11 0x7f8b9f2667a9 g_main_dispatch (libglib-2.0.so.0 + 0x547a9) #12 0x7f8b9f266a38 g_main_context_iterate (libglib-2.0.so.0 + 0x54a38) #13 0x7f8b9f266acc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #14 0x7f8ba15094b6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x3094b6) #15 0x7f8ba14b019b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b019b) #16 0x7f8ba14b8306 _ZN16QCoreApplication4execEv (libQt5C
Re: kded5 crashes
dri, GLX and mesa all point to graphics subsystem, so it's probably useful to share the GPU that you're using. Yes, sorry. Sid on a virtualbox vm, VMSVGA with 3D enabled. Intel graphics on host.
Re: kded5 crashes
Il 07/12/22 11:10, Sune Vuorela ha scritto: On 2022-12-06, luca.pedrielli wrote: #6 0x7fa425233563 n/a (kded_apperd.so + 0xe563) #7 0x7fa425233b99 n/a (kded_apperd.so + 0xeb99) Can you try remove apper and see if that is the culprit ? /Sune i removed apper and things seems to be better. waiting for confirmation from the other guys too. now only plasmashell crashes ;) -- Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. PID: 1019 (plasmashell) UID: 1000 (ilprof) GID: 1000 (ilprof) Signal: 11 (SEGV) Timestamp: Wed 2022-12-07 11:34:26 CET (3min 39s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (ilprof) Boot ID: cafc24ad58f24c5489c9ffa748d8f32f Machine ID: ad6738af96e1470e8772413d7f9c5dd0 Hostname: unstable Storage: /var/lib/systemd/coredump/core.plasmashell.1000.cafc24ad58f24c5489c9ffa748d8f32f.1019.167040926600.zst (present) Size on Disk: 16.3M Message: Process 1019 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.2-2.amd64 Module libudev.so.1 from deb systemd-252.2-2.amd64 Stack trace of thread 1019: #0 0x7f488f6a9ccc n/a (libc.so.6 + 0x8accc) #1 0x7f488f65aef2 raise (libc.so.6 + 0x3bef2) #2 0x7f4891a93be1 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5be1) #3 0x7f488f65af90 n/a (libc.so.6 + 0x3bf90) #4 0x7f4882a1c158 n/a (vmwgfx_dri.so + 0x61c158) #5 0x7f4882a1c343 n/a (vmwgfx_dri.so + 0x61c343) #6 0x7f4882dcbcad n/a (vmwgfx_dri.so + 0x9cbcad) #7 0x7f4882575083 n/a (vmwgfx_dri.so + 0x175083) #8 0x7f48824b0a23 n/a (vmwgfx_dri.so + 0xb0a23) #9 0x7f48824b40cc n/a (vmwgfx_dri.so + 0xb40cc) #10 0x7f48898f9104 n/a (libGLX_mesa.so.0 + 0x43104) #11 0x7f48898e2a38 n/a (libGLX_mesa.so.0 + 0x2ca38) #12 0x7f488ce49ccc n/a (libGLX.so.0 + 0x4ccc) #13 0x7f4889964fff n/a (libqxcb-glx-integration.so + 0xafff) #14 0x7f48899621b7 n/a (libqxcb-glx-integration.so + 0x81b7) #15 0x7f488ff8262d _ZN14QOpenGLContext6createEv (libQt5Gui.so.5 + 0x18262d) #16 0x7f489160d2ce n/a (libQt5Quick.so.5 + 0x20d2ce) #17 0x7f488ff495b5 _ZN7QWindow5eventEP6QEvent (libQt5Gui.so.5 + 0x1495b5) #18 0x7f4890762f5e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162f5e) #19 0x7f488fab1718 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b1718) #20 0x7f488ff3e73d _ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE (libQt5Gui.so.5 + 0x13e73d) #21 0x7f488ff11e1c _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Gui.so.5 + 0x111e1c) #22 0x7f488a6fbc7a n/a (libQt5XcbQpa.so.5 + 0x6dc7a) #23 0x7f488d91f7a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) #24 0x7f488d91fa38 n/a (libglib-2.0.so.0 + 0x54a38) #25 0x7f488d91facc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #26 0x7f488fb094b6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x3094b6) #27 0x7f488fab019b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b019b) #28 0x7f488fab8306 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b8306) #29 0x5629241c1c6c n/a (plasmashell + 0x25c6c) #30 0x7f488f64618a n/a (libc.so.6 + 0x2718a) #31 0x7f488f646245 __libc_start_main (libc.so.6 + 0x27245) #32 0x5629241c1d81 n/a (plasmashell + 0x25d81) Stack trace of thread 1046: #0 0x7f488f71b0af __poll (libc.so.6 + 0xfc0af) #1 0x7f488d91f9ae n/a (libglib-2.0.so.0 + 0x549ae) #2 0x7f488d91facc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #3
Re: kded5 crashes
Il 06/12/22 20:30, tv.debian ha scritto: Le 06/12/2022 à 13:45, Miguel A. Vallejo a écrit : Since a few days ago I've been experiencing problems with KDE in a fully upgraded Sid. The symptoms are always the same: kded5 crashes a few minutes after boot and then icons from no KDE programs (like Telegram) disappears from the system tray. A lot of errors in syslog from plasmashell, kwin_x11 and kded5 itself. Any ideas? Thanks in advance Hi, I am on Sid and I don't see this. I use Wayland, are all the affected users here still on X11? It is crashing in Wayland too. Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. PID: 924 (kded5) UID: 1000 (ilprof) GID: 1000 (ilprof) Signal: 11 (SEGV) Timestamp: Tue 2022-12-06 22:03:23 CET (2min 48s ago) Command Line: /usr/bin/kded5 Executable: /usr/bin/kded5 Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kded.service Unit: user@1000.service User Unit: plasma-kded.service Slice: user-1000.slice Owner UID: 1000 (ilprof) Boot ID: b91cecf0c7f64f6abd137d6cfbe575ba Machine ID: ad6738af96e1470e8772413d7f9c5dd0 Hostname: unstable Storage: /var/lib/systemd/coredump/core.kded5.1000.b91cecf0c7f64f6abd137d6cfbe575ba.924.167036060300.zst (present) Size on Disk: 4.7M Message: Process 924 (kded5) of user 1000 dumped core. Module libudev.so.1 from deb systemd-252.2-1.amd64 Module libsystemd.so.0 from deb systemd-252.2-1.amd64 Stack trace of thread 924: #0 0x7fa444be6bb4 pthread_sigmask (libc.so.6 + 0x8fbb4) #1 0x7fa444b93179 sigprocmask (libc.so.6 + 0x3c179) #2 0x7fa445ce3eab _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4eab) #3 0x7fa445ce4bd9 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5bd9) #4 0x7fa444b92f90 n/a (libc.so.6 + 0x3bf90) #5 0x7fa424d77740 _ZNK10PackageKit11Transaction3tidEv (libpackagekitqt5.so.1 + 0x1a740) #6 0x7fa425233563 n/a (kded_apperd.so + 0xe563) #7 0x7fa425233b99 n/a (kded_apperd.so + 0xeb99) #8 0x7fa4448e8caf n/a (libQt5Core.so.5 + 0x2e8caf) #9 0x7fa424d6b095 _ZN10PackageKit6Daemon22transactionListChangedERK11QStringList (libpackagekitqt5.so.1 + 0xe095) #10 0x7fa4448e8cdc n/a (libQt5Core.so.5 + 0x2e8cdc) #11 0x7fa424d83b38 n/a (libpackagekitqt5.so.1 + 0x26b38) #12 0x7fa424d84d73 n/a (libpackagekitqt5.so.1 + 0x27d73) #13 0x7fa44552661b n/a (libQt5DBus.so.5 + 0x2361b) #14 0x7fa4448dd450 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2dd450) #15 0x7fa445762f5e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162f5e) #16 0x7fa4448b1718 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b1718) #17 0x7fa4448b46b1 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b46b1) #18 0x7fa444909dd3 n/a (libQt5Core.so.5 + 0x309dd3) #19 0x7fa44371f7a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) #20 0x7fa44371fa38 n/a (libglib-2.0.so.0 + 0x54a38) #21 0x7fa44371facc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #22 0x7fa4449094b6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x3094b6) #23 0x7fa4448b019b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b019b) #24 0x7fa4448b8306 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b8306) #25 0x55e42173c359 n/a (kded5 + 0x7359) #26 0x7fa444b7e18a n/a (libc.so.6 + 0x2718a) #27 0x7fa444b7e245 __libc_start_main (libc.so.6 + 0x27245) #28 0x55e42173c541 n/a (kded5 + 0x7541) Stack trace of thread 931: #0 0x7fa444bdcd36 n/a (libc.so.6 + 0x85d36) #1 0x7fa444bdf3f8 pthread_cond_wait (libc.so.6 + 0x883f8) #2 0x7fa4446d199b _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd199b) #3 0x7fa440b2faef n/a (libQt5WaylandClient.so.5 + 0x7aaef) #4 0x7fa4446cbcd1 n/a (libQt5Core.so.5 + 0xcbcd1) #5 0x000
Re: kded5 crashes
Il 06/12/22 13:45, Miguel A. Vallejo ha scritto: Since a few days ago I've been experiencing problems with KDE in a fully upgraded Sid. The symptoms are always the same: kded5 crashes a few minutes after boot I can confirm. -- Saluti, Luca Pedrielli
Re: Bookworm: Dolphin file manager doesn't show comment content in the Details view mode?
Il 26/07/22 16:41, local10 ha scritto: Hi, Tried adding comments to files (a useful feature in some cases) and the comments are added and saved. A file comment can be seen by selecting the file, doing a RMB click > Properties > Details > Comment. The comment is there. However, the Dolphin File Manager doesn't show the comment content in the Details View Mode even though it shows the (empty) comment column. Am using ext4. Any ideas? Thanks Operating System: Debian 12 Bookworm GNU/Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.18.0-2-amd64 (64-bit) Graphics Platform: X11 working with baloo enabled -- Saluti, Luca Pedrielli
Re: Bookworm: Dolphin file manager doesn't show comment content in the Details view mode?
Il 26/07/22 16:41, local10 ha scritto: Hi, Tried adding comments to files (a useful feature in some cases) and the comments are added and saved. A file comment can be seen by selecting the file, doing a RMB click > Properties > Details > Comment. The comment is there. However, the Dolphin File Manager doesn't show the comment content in the Details View Mode even though it shows the (empty) comment column. Am using ext4. Any ideas? Thanks Operating System: Debian 12 Bookworm GNU/Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.18.0-2-amd64 (64-bit) Graphics Platform: X11 I can reproduce also wih "tags" and "rating" :( -- Saluti, Luca Pedrielli
Re: Bookworm: Juk 22.04.1 broken?
Il 19/07/22 09:22, local10 ha scritto: Jul 19, 2022, 06:17 byago...@gmail.com: I can not reproduce. Are there some errors if you start it in konsole? No errors and/or exceptions are reported when starting Juk from the konsole: it starts and behaves as I described in my previous message, that is, shows the directory but doesn't show any files. Are there any Juk config settings besides the following? 1. ~/.config/jukrc 2. ~/.local/share/juk Thanks .local/share/jukcoverdb and if you try to add another dir with other audio file? -- Saluti, Luca Pedrielli
Re: Bookworm: Juk 22.04.1 broken?
Il 19/07/22 05:18, local10 ha scritto: Jul 15, 2022, 23:05 by loca...@tutanota.com: Hi, Juk v22.04.1 doesn't seems to work for me. Tried the following but couldn't resolve the issue. Any ideas? Thanks 1. mv ~/.config/jukrc ~/.config/jukrc.old> 2. mv ~/.local/share/juk ~/.local/share/juk.old 3. Open juk 4. Use Ctrl+D to add a directory with about 10 audio files. 5. Juk adds the directory, shows its name in the "Collection List" pane but fails to show any audio files in the right pane, where they are normally shown. 6. Doing a RMB click on the directory and selecting "Reload" seems to have no effect, no audio files are loaded. # aptitude show juk Package: juk Version: 4:22.04.1-1 State: installed Operating System: Debian 12 Bookworm GNU/Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.18.0-2-amd64 (64-bit) Graphics Platform: X11 Any feedback? Is just me and Juk 22.04.1 is working for everyone else? The description above was updated a bit to reflect the current state of my Juk efforts. Thanks I can not reproduce. Are there some errors if you start it in konsole? -- Saluti, Luca Pedrielli
Re: digikam
Il 03/07/22 17:21, Dietz Proepper ha scritto: Hi, since the update to the kde version from unstable some days ago digikam is no longer installable. Are there plans underway to fix that? (Simply rebuilding from source failed due to some compilation error.) Kindest regards, Dietz and it is removed from testing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014071 -- Saluti, Luca Pedrielli
Re: Thank you!
+1 Il 02/06/22 08:26, Martin Steigerwald ha scritto: Hi! A huge thanks to the Debian Qt/KDE maintainer team for the continued work on Qt/KDE related packages. Thank you to Pino, Patrick, Aurélien and of course all the others for tirelessly packaging newest versions of Qt, including Qt 6 which KDE will switch to at some time, Plasma, KDE Frameworks, KDE Gear, KDEPIM and all the other applications from KDE, including new ones like the Korganizer alternative Kalendar. I bet in total that could easily be about one thousand packages, maybe even more. It is a huge effort to pull this off! While not all of this is available within unstable yet, at least not in most recent versions, most of it is and the state of the art in unstable regarding KDE related packages is very decent. Thank you for this continued effort to all of you, of course also to those who I did not mention specifically including those long term team members who advice newcomers to the team on packaging questions and those who contributed a lot previously. I appreciate your effort! Best, -- Saluti, Luca Pedrielli
Re: Bookworm: Kwrite/Kate Tools menu
Il 31/05/22 15:39, local10 ha scritto: Hi, Is it just me or Kwrite/Kate Tools menu is now missing some entries that used to be there for a long time, for example: Tools → Comment (Ctrl+D) Tools → Uncomment (Ctrl+Shift+D) Tools → Uppercase (Ctrl+U) Tools → Lowercase (Ctrl+Shift+U) Tools → Capitalize (Ctrl+Alt+U) The keyboard shortcuts still work, I think, but the above menu entries can no longer be found under the Tools menu. Any ideas? Thanks Operating System: Debian 12 Bookworm GNU/Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Kernel Version: 5.17.0-1-amd64 (64-bit) Graphics Platform: X11 Selection -> Capitalization -- Saluti, Luca Pedrielli
Re: Bookwork KDE task switchers
Il 24/04/22 09:22, Sami Erjomaa ha scritto: On Sun, 24 Apr 2022 at 10:08, luca.pedrielli wrote: Il 24/04/22 06:58, local10 ha scritto: Hi, After migrating from Bullseye to Bookworm, it appears that the only task switchers available to me in Bookworm are "Breeze", "Breeze Dark" and "Breeze Twilight", no other task switchers are available. Currently I use Breeze, which works but I would prefer to get the "Flip Switch" back that I used to use in Bullseye. Not sure why other task switchers have disappeared, maybe I'm missing a package or maybe the KDE compositor crashed? Had a similar issue some years back when the KDE compositor crashed and KDE disabled it afterwards, resulting in the loss of some task switchers, IIRC. Any ideas? Thanks some effects where dropped * coverswitch * cube * cubeslide * flipswitch :( -- Saluti, Luca Pedrielli Hi, I have Compact, Cover Switch, Flip Switch, Grid, Informative, Large Icons and Small Icons + the 3 Breeze Those other switchers come in the kwin-addons package -- Sami Erjomaa linktr.ee/erjomaa <https://linktr.ee/erjomaa> Hi Sami, they where dropped and replaced :( Thanks https://bugs.kde.org/show_bug.cgi?id=450230 -- Saluti, Luca Pedrielli
Re: Bookwork KDE task switchers
Il 24/04/22 06:58, local10 ha scritto: Hi, After migrating from Bullseye to Bookworm, it appears that the only task switchers available to me in Bookworm are "Breeze", "Breeze Dark" and "Breeze Twilight", no other task switchers are available. Currently I use Breeze, which works but I would prefer to get the "Flip Switch" back that I used to use in Bullseye. Not sure why other task switchers have disappeared, maybe I'm missing a package or maybe the KDE compositor crashed? Had a similar issue some years back when the KDE compositor crashed and KDE disabled it afterwards, resulting in the loss of some task switchers, IIRC. Any ideas? Thanks some effects where dropped * coverswitch * cube * cubeslide * flipswitch :( -- Saluti, Luca Pedrielli
Re: Digital clock wizard and 24-hour format
Il 21/03/22 02:40, local10 ha scritto: Mar 20, 2022, 16:52 by ago...@gmail.com: and if you try with a different Region? I tried setting "osa_US" -- which also uses 24-hour time format -- as the time format in KDE but "Copy to Clipboard" still showed time in the AM/PM format. Regards, and if you try with Region "it_IT" and "Detailed Settings" disabled + logout/login ? -- Saluti, Luca Pedrielli
Re: Digital clock wizard and 24-hour format
Il 20/03/22 13:39, local10 ha scritto: Hi, Am struggling to get the KDE Digital clock wizard to use the 24-hour format when using the "Copy to clipboard" menu option. See [1] and [2] for my settings. The Digital Clock wizard uses 24-hour format when it shows the time in the panel but when using its "Copy to clipboard" option it still uses the AM/PM format. I couldn't find any way to fix this. Any ideas? Thanks 1. https://i.postimg.cc/025NB9P5/regional-settings.png 2. https://i.postimg.cc/bNRmqH7H/regional-settings-2.png Operating System: Debian GNU/Linux 11 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.0-12-amd64 OS Type: 64-bit and if you try with a different Region? -- Saluti, Luca Pedrielli
Re: KDE Digital Clock widget config file?
Il 08/03/22 14:53, local10 ha scritto: Mar 8, 2022, 07:27 byago...@gmail.com: take a look at .config/plasma-org.kde.plasma.desktop-appletsrc,search> plugin=org.kde.plasma.digitalclock, > but be careful> The following is what I have in the "~/.config/plasma-org.kde.plasma.desktop-appletsrc" file related to the Digital Clock widget: ... [Containments][1][Applets][42] immutability=1 plugin=org.kde.plasma.digitalclock ... [Containments][1][Applets][8] immutability=1 plugin=org.kde.plasma.digitalclock ... [Containments][2][Applets][44] immutability=1 plugin=org.kde.plasma.digitalclock Strangely it doesn't contain any settings for the Digital Clock from the "Configure Digital Clock" window, just lists the widget three (!) times. Any ideas? Thanks I suggest you to copy ~/.config/plasma-org.kde.plasma.desktop-appletsrc in ~/.config/plasma-org.kde.plasma.desktop-appletsrc.save, change something in "Configure Digital Clock" and diff the files to understand how it works. - $ diff plasma-org.kde.plasma.desktop-appletsrc.sv plasma-org.kde.plasma.desktop-appletsrc 10c10 < ItemGeometriesHorizontal=Applet-21:112,80,272,272,0;Applet-22:672,16,272,272,0; --- > ItemGeometriesHorizontal=Applet-21:112,80,272,272,0;Applet-22:672,16,272,272,0;Applet-25:1216,176,176,80,0; 42a43,54 > > [Containments][1][Applets][25] > immutability=1 > plugin=org.kde.plasma.digitalclock > > [Containments][1][Applets][25][Configuration][Appearance] > showLocalTimezone=true > showSeconds=true > > [Containments][1][Applets][25][Configuration][ConfigDialog] > DialogHeight=540 > DialogWidth=720 - -- Saluti, Luca Pedrielli
Re: KDE Digital Clock widget config file?
Il 07/03/22 18:03, local10 ha scritto: Hi, Something got screwed up with the KDE Digital Clock widget and I can't find any way to fix it via the "Configure Digital Clock" window. Where does the Digital Clock widget store all the settings from the the "Configure Digital Clock" window? My plan is to see if the following would work: 1. Remove the Clock widget from the panel. 2. Delete the widget config file. 3. Add the widget to the panel and reconfigure it again. Thanks, # cat /etc/debian_version && uname -a 11.2 Linux test 5.10.0-11-amd64 #1 SMP Debian 5.10.92-2 (2022-02-28) x86_64 GNU/Linux take a look at .config/plasma-org.kde.plasma.desktop-appletsrc, search plugin=org.kde.plasma.digitalclock, but be careful -- Saluti, Luca Pedrielli
Re: User settings error
Il 02/11/21 15:14, lists.deb...@netc.eu ha scritto: Hello to all, I just installed a new Debian 11 system, and I choose KDE Plasma as my desktop environment. I only having a problem by change my users settings. At my Debian install, I define a root user account. After install, I've tried to go to the settings/user settings and I found that I can't change any setting on my users : 1. First I hed just one user, "marc". I tryed to add an email and make it an "Administrator", but I had an error when applying the changes. 2. I then try to add a 2nd user "cat". It did work, but when I try to change it to admin or add the email address, I had the same error than before. 3. Using the terminal, I add "marc" to the sudoers file. But even than I wasn't abble to add the users email or change "cat" account to admin. Can youpeople help me to figure out what is happening? Thanks in advance for all your help, Best regards, Marc I had the same problem. org.kde.kcm_users: "org.freedesktop.Accounts.Error.Failed" "file '/home/mario/.face' is not a regular file" If I choose an avatar seems working -- Saluti, Luca Pedrielli
Re: Bullseye KDE logout lasts 10 sec.minimum
Happy to help you. https://lists.debian.org/debian-kde/2021/02/msg6.html Il 09/10/21 20:43, Herbert Schwarzer ha scritto: Thank you for your replies. I have tested before a lot around i.e. to check logfiles - but there comes a heavy load of messages. So the first step for THIS answer I wrote journalctl-output to 2 files (attached) but I am worried about the many lines although I have started output only just in time if I LOGGED OUT from KDE and stopped when I returned to new login-window. Maybe YOU can recognize something . BUT @ Luca Podrelli --> the solution for me too has been deinstalling kdeconnect. Don't know WHY this troubles the logout. Thank you - so the problem is solved. Can anyone of the Debian KDE people eliminate this conflict within a next Debian 11 update ... Saluti a Luca et Am Samstag, 9. Oktober 2021, 15:35:37 CEST schrieb luca.pedrielli: Il 09/10/21 12:17, Herbert ha scritto: Hello to all readers Logout from KDE (Plasma 5.20.5) lasts more then 10 sec. This is abnormal as under Buster logout passed immediately (login screen: sddm or lightdm, does not matter) appeared just in time. If I log in as root (only under lightdm possible) there is no delay in logging out. Even creating a fresh new user same behavior. Any idea about the reason ? Herbert S. Hi Herbert, have you tried to compare the logs of the last session(root and user) using journalctl -b -1? you can also enable a debug-shell with |systemctl enable debug-shell (turn it on only as needed and disable it afterwards) and use it on logout| |||https://fedoraproject.org/wiki/Systemd_early_debug-shell?rd=Systemd_early |||_debug_shell| ||| ||| ||| |||I had a similar problem ago, solved by removing Kdeconnect, but I don't think it's your same problem.| -- Saluti, Luca Pedrielli
Re: Bullseye KDE logout lasts 10 sec.minimum
Il 09/10/21 12:17, Herbert ha scritto: Hello to all readers Logout from KDE (Plasma 5.20.5) lasts more then 10 sec. This is abnormal as under Buster logout passed immediately (login screen: sddm or lightdm, does not matter) appeared just in time. If I log in as root (only under lightdm possible) there is no delay in logging out. Even creating a fresh new user same behavior. Any idea about the reason ? Herbert S. Hi Herbert, have you tried to compare the logs of the last session(root and user) using journalctl -b -1? you can also enable a debug-shell with |systemctl enable debug-shell (turn it on only as needed and disable it afterwards) and use it on logout| || |||https://fedoraproject.org/wiki/Systemd_early_debug-shell?rd=Systemd_early_debug_shell| || |||I had a similar problem ago, solved by removing Kdeconnect, but I don't think it's your same problem.| -- Saluti, Luca Pedrielli
Re: Default browser settings muddle
I found this: https://askubuntu.com/questions/1277683/links-from-apps-always-open-a-file-url I hope it helps. Il 25/04/21 11:38, Brad Rogers ha scritto: Hello, I've recently been trying a few different browsers, altering default browser settings via KDE/Plasma settings software. I've finally settled on a browser, but some apps, when they call the browser, open a page such as; file:///home/brad/.cache/kioexec/krun/49841_0/somepageorother rather than http://url.of.website/somepageorother The number in the 'file:///...' call will be different each time. I've ensured that both gnome-browser and x-www-browser point to the correct browser, but cannot for the life of me figure out why some calls are being mishandled. Note: I'm not pointing fingers at KDE/Plasma, it's almost certainly something *I've* screwed up. My online searches have proved fruitless (clearly my search fu isn't up to snuff) and am hopeful that someone far more knowledgeable than I can shed some light. Using Debian testing, with KDE plasma 5.20 Any help greatly appreciated. -- Saluti, Luca Pedrielli
plasma slow logout due to kdeconnect
In a fresh debian testing installation(full updated) i noticed an annoying delay of a few seconds in the plasma logout. Removing kdeconnect (strange that it can't be disabled) solved the problem. I found this in the logs when I logged out: - feb 07 09:56:13 ilprof5 org.kde.kdeconnect[8388]: kdeconnect.core: Could not query capabilities from notifications server feb 07 09:56:23 ilprof5 org.kde.kdeconnect[8388]: ICE default IO error handler doing an exit(), pid = 8388, errno = 11 feb 07 09:58:14 ilprof5 org.kde.kdeconnect[9385]: kdeconnect.core: Could not query capabilities from notifications server feb 07 09:58:24 ilprof5 org.kde.kdeconnect[9385]: ICE default IO error handler doing an exit(), pid = 9385, errno = 11 feb 07 09:58:43 ilprof5 org.kde.kdeconnect[10333]: kdeconnect.core: Could not query capabilities from notifications server feb 07 09:58:53 ilprof5 org.kde.kdeconnect[10333]: ICE default IO error handler doing an exit(), pid = 10333, errno = 11 - -- Saluti, Luca Pedrielli
Re: Plasma 5.20.4: System Preferences -> User Management: User image does not change.
Il 26/12/20 10:23, Rik Mills ha scritto: Perhaps https://bugs.kde.org/show_bug.cgi?id=422177 I think you are right. Thanks. -- Saluti, Luca Pedrielli
Re: Plasma 5.20.4: System Preferences -> User Management: User image does not change.
Il 25/12/20 22:00, Norbert Preining ha scritto:
Hi
On Fri, 25 Dec 2020, luca.pedrielli wrote:
It seems that sddm looks for avatar in ~/.face.icon or in
/usr/share/sddm/faces (you can change it
Hmm, according to https://github.com/sddm/sddm/issues/683 this icons of
AccountsService should be available since sometime in 2018 ...
And sddm hasn't changed in this respect I think, and the former
user-manager also used AccountsService.
Checking the source of sddm:
const QString userFace =
QStringLiteral("%1/.face.icon").arg(user->homeDir);
const QString systemFace =
QStringLiteral("%1/%2.face.icon").arg(facesDir).arg(user->name);
QString accountsServiceFace =
QStringLiteral("/var/lib/AccountsService/icons/%1").arg(user->name);
if (QFile::exists(userFace))
user->icon = QStringLiteral("file://%1").arg(userFace);
else if (QFile::exists(accountsServiceFace))
user->icon = accountsServiceFace;
else if (QFile::exists(systemFace))
user->icon = QStringLiteral("file://%1").arg(systemFace);
so it checks
- ~/.face.icon
- sddm face dir/$USER.face.icon
- /var/lib/AccountsService/icons/$USER
So changes *should* show up ...
I am a bit puzzled.
Norbert
Hi Norbert,
I've tested with new users and sddm works as you say:
$ LC_ALL=C strace -f sddm-greeter --test-mode --theme
/usr/share/sddm/themes/breeze 2>&1 | grep 'Accounts\|face.icon'
[pid 11780]
access("/usr/share/sddm/themes/debian-theme/faces/.face.icon", F_OK) =
-1 ENOENT (No such file or directory)
[pid 11780] access("/home/ilprof/.face.icon", F_OK) = -1 ENOENT (No such
file or directory)
[pid 11780] access("/var/lib/AccountsService/icons/ilprof", F_OK) = 0
[pid 11780] access("/home/mario/.face.icon", F_OK) = -1 ENOENT (No such
file or directory)
[pid 11780] access("/var/lib/AccountsService/icons/mario", F_OK) = -1
ENOENT (No such file or directory)
[pid 11780] access("/usr/share/sddm/faces/mario.face.icon", F_OK) = -1
ENOENT (No such file or directory)
[pid 11780] access("/var/lib/AccountsService/icons/ilprof", F_OK) = 0
[pid 11780] openat(AT_FDCWD, "/var/lib/AccountsService/icons/ilprof",
O_RDONLY|O_CLOEXEC) = 19
[pid 11780] openat(AT_FDCWD, "/usr/share/sddm/faces/.face.icon",
O_RDONLY|O_CLOEXEC) = 19
but the strange behaviour of kcm_users remains:
If you choose a default image /var/lib/AccountsService/icons/$USER is
not updated
Best, Luca
--
PREINING Norbert https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
--
Saluti, Luca Pedrielli
Re: Plasma 5.20.4: System Preferences -> User Management: User image does not change.
I can confirm. It seems that sddm looks for avatar in ~/.face.icon or in /usr/share/sddm/faces (you can change it with the FaceDir key in the sddm configuration file) In the new kcm_users, if you choose the avatar from file, it write in /var/lib/AccountsService/icons and update the Icon key in /var/lib/AccountsService/user. If you choose a default image only the Icon key in /var/lib/AccountsService/user is updated. :( Best, Luca. Il 25/12/20 11:28, Héctor Sales Llamas ha scritto: *Update:* it also doesn't seem to work on the login screen with sddm the image don't change! Regards El vie, 25 dic 2020 a las 10:01, Héctor Sales Llamas (mailto:hectorvicentesa...@gmail.com>>) escribió: If I choose the image from the file the user image changes correctly (Screenshot1) but if I choose one of the images that come by default they do not change (Screenshot2) *Note: *This strange behavior has happened to me in both sid and testing (upgrade from unstable plasma 5.20 and frameworks 5.77.0-2) Best Regards -- Saluti, Luca Pedrielli
Re: KDE Stops opening new programs
Il 25/11/20 18:17, Miguel A. Vallejo ha scritto: Norbert Preining wote: Does the same happen with a directory of say 5 PDF files? Yes, I entered in a directory with 8 pdf files and the count of thumbnail.so processes increased by 6 And are thumbnails generated in a directory with say 5 PDF files? No, as I told before I have never seen a pdf previsualization in dolphin, just the typical pdf icon. is kdegraphics-thumbnailers installed ? -- Saluti, Luca Pedrielli
Re: No Log In Notification
Il 20/11/20 14:29, Brad Rogers ha scritto: Hello, Using Debian Testing; Since updates to Plasma a week or so ago, I've not had any log in notification (play sound). The relevant file exists, plays audio elsewhere, just doesn't get played during log in. Toggling off and on the notification setting didn't help. Log out notification works and, as far as I can tell, so does every other notification I have set. Turning notifications on in a new user results in the same non-playing behaviour. Today's minor updates to plasma ( kf5lib notification & manager) in Testing didn't changes things. It's not a big deal, I can live with it (I rarely log in/out or reboot), but is anyone else seeing similar behaviour? I can confirm. https://bugs.kde.org/show_bug.cgi?id=422948 -- Saluti, Luca Pedrielli
Re: Plasma-discover (5.19.5-3) on testing closes unexpectedly( drkonqi)
Fixed in Frameworks 5.75 or Plasma 5.20. Il 13/11/20 20:01, Rik Mills ha scritto: Sounds like https://bugs.kde.org/show_bug.cgi?id=425670 On 13/11/2020 17:53, Héctor Sales Llamas wrote: After update testing (few minutes): I open Plasma-discover (5.19.5-3)--->Preferences--->closes unexpectedly( drkonqi) "Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7fb2643076df in QQmlData::createQQmlData(QObjectPrivate*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #5 0x7fb26423bcbd in QV4::QObjectWrapper::wrap_slowPath(QV4::ExecutionEngine*, QObject*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fb26423c10a in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fb26423d5b2 in QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, QQmlPropertyData**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fb2643834e3 in QV4::QQmlTypeWrapper::virtualGet(QV4::Managed const*, QV4::PropertyKey, QV4::Value const*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7fb2641d38ed in QV4::Lookup::getterFallback(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value const&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7fb20c123825 in ?? () #11 0x in ?? () [Inferior 1 (process 3397) detached]" Best Regards -- Saluti, Luca Pedrielli
Re: Plasma-discover (5.19.5-3) on testing closes unexpectedly( drkonqi)
Il 13/11/20 18:53, Héctor Sales Llamas ha scritto: After update testing (few minutes): I open Plasma-discover (5.19.5-3)--->Preferences--->closes unexpectedly( drkonqi) "Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7fb2643076df in QQmlData::createQQmlData(QObjectPrivate*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #5 0x7fb26423bcbd in QV4::QObjectWrapper::wrap_slowPath(QV4::ExecutionEngine*, QObject*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fb26423c10a in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fb26423d5b2 in QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, QQmlPropertyData**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fb2643834e3 in QV4::QQmlTypeWrapper::virtualGet(QV4::Managed const*, QV4::PropertyKey, QV4::Value const*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7fb2641d38ed in QV4::Lookup::getterFallback(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value const&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7fb20c123825 in ?? () #11 0x in ?? () [Inferior 1 (process 3397) detached]" Best Regards = Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7fdb81ea80c6 in QQmlData::wasDeleted (object=0x564640735120) at ../../include/QtQml/5.15.1/QtQml/private/../../../../../src/qml/qml/qqmldata_p.h:338 #5 QV4::QObjectWrapper::wrap (object=0x564640735120, engine=0x56463ef0d610) at jsruntime/qv4qobjectwrapper_p.h:213 #6 loadProperty (v4=0x56463ef0d610, object=0x56464080d020, property=...) at jsruntime/qv4qobjectwrapper.cpp:139 #7 0x7fdb81ea95b2 in QV4::QObjectWrapper::getQmlProperty (engine=engine@entry=0x56463ef0d610, qmlContext=qmlContext@entry=0x5646403b14d0, object=0x56464080d020, name=0x7fdb78c59628, revisionMode=revisionMode@entry=QV4::QObjectWrapper::IgnoreRevision, hasProperty=hasProperty@entry=0x0, property=0x0) at jsruntime/qv4qobjectwrapper.cpp:388 #8 0x7fdb81fef4e3 in QV4::QQmlTypeWrapper::virtualGet (m=0x7fdb78c59618, id=..., receiver=0x7fdb78c59618, hasProperty=0x0) at ../../include/QtQml/5.15.1/QtQml/private/../../../../../src/qml/common/qv4staticvalue_p.h:325 #9 0x7fdb81e3f8ed in QV4::Object::get (receiver=0x7fdb78c59618, hasProperty=0x0, name=0x7fdb78c59620, this=0x7fdb78c59618) at ../../include/QtQml/5.15.1/QtQml/private/../../../../../src/qml/jsruntime/qv4string_p.h:167 #10 QV4::Lookup::getterFallback (l=, engine=0x56463ef0d610, object=...) at jsruntime/qv4lookup.cpp:201 #11 0x7fdb81ec6aa9 in QV4::Moth::VME::interpret (frame=0x7ffee48aa110, engine=0x56463ef0d610, code=0x7fdb614836d4 ":*\030\006\002") at jsruntime/qv4vme_moth.cpp:638 #12 0x7fdb81ecaf07 in QV4::Moth::VME::exec (frame=frame@entry=0x7ffee48aa110, engine=engine@entry=0x56463ef0d610) at jsruntime/qv4vme_moth.cpp:463 #13 0x7fdb81e6684d in QV4::Function::call (this=this@entry=0x56463f74fd20, thisObject=, argv=argv@entry=0x7fdb78c595b0, argc=, context=out>) at jsruntime/qv4function.cpp:69 #14 0x7fdb81fde585 in QQmlJavaScriptExpression::evaluate (this=this@entry=0x56464093c310, callData=0x7fdb78c59580, isUndefined=isUndefined@entry=0x7ffee48aa2ef) at ../../include/QtQml/5.15.1/QtQml/private/../../../../../src/qml/jsruntime/qv4value_p.h:343 #15 0x7fdb81fe3684 in QQmlBinding::evaluate (this=this@entry=0x56464093c310, isUndefined=isUndefined@entry=0x7ffee48aa2ef) at ../../include/QtQml/5.15.1/QtQml/private/../../../../../src/qml/jsruntime/qv4jscall_p.h:95 #16 0x7fdb81fe7527 in QQmlNonbindingBinding::doUpdate (this=0x56464093c310, watcher=..., flags=..., scope=...) at qml/qqmlbinding.cpp:254 #17 0x7fdb81fe5304 in QQmlBinding::update (this=0x56464093c310, flags=...) at qml/qqmlbinding.cpp:194 #18 0x7fdb81ea891b in QQmlData::flushPendingBinding (propertyIndex=..., o=0x5646403b1780) at ../../include/QtQml/5.15.1/QtQml/private/../../../../../src/qml/qml/qqmldata_p.h:421 #19 QV4::QObjectWrapper::getProperty (engine=0x56463ef0d610, object=0x5646403b1780, property=0x7fdb7018b498) at jsruntime/qv4qobjectwrapper.cpp:236 #21 QV4::QQmlContextWrapper::lookupScopeObjectProperty (l=0x56463f74e910, engine=0x56463ef0d610, base=) at jsruntime/qv4qmlcontext.cpp:569 #22 0x7fdb81ec5fe0 in QV4::Moth::VME::interpret (frame=0x7ffee48aa680, engine=0x56463ef0d610, code=0x7fdb61483630 ":\":#:$p\030\006\002") at jsruntime/qv4vme_moth.cpp:585 #23 0x7fdb81ecaf07 in QV4::Moth::VME::exec (frame=frame@entry=0x7ffee48aa680, engine=engine@entry=0x56463ef0d610) at jsruntime/qv4vme_moth.cpp:463 #24 0x7fdb81e6684d in QV4::Function::call (this=this@entry=0x56463f74fc80, thisObject=, argv=argv@entry=0x7fdb78c59500, argc=, context=out>) at jsruntime/qv4function.cpp:69 #25 0x7fdb81fde585 in QQmlJavaScri
Re: Plasma-discover (5.19.5-3) on testing closes unexpectedly( drkonqi)
Il 13/11/20 18:53, Héctor Sales Llamas ha scritto: After update testing (few minutes): I open Plasma-discover (5.19.5-3)--->Preferences--->closes unexpectedly( drkonqi) "Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7fb2643076df in QQmlData::createQQmlData(QObjectPrivate*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #5 0x7fb26423bcbd in QV4::QObjectWrapper::wrap_slowPath(QV4::ExecutionEngine*, QObject*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fb26423c10a in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fb26423d5b2 in QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, QQmlPropertyData**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fb2643834e3 in QV4::QQmlTypeWrapper::virtualGet(QV4::Managed const*, QV4::PropertyKey, QV4::Value const*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7fb2641d38ed in QV4::Lookup::getterFallback(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value const&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7fb20c123825 in ?? () #11 0x in ?? () [Inferior 1 (process 3397) detached]" Best Regards I can confirm :( -- Saluti, Luca Pedrielli
Re: Configure GNOME/GTK Application Style
Il 12/11/20 16:34, Pino Toscano ha scritto: In data giovedì 12 novembre 2020 11:17:07 CET, luca.pedrielli ha scritto: after updating my Debian testing, I no longer find the ability to change Gnome / gtk application style in systemsettings. kde-config-gtk-style: amd64 4: 5.19.5-3 is installed. i can manually edit .config / gtk-3.0 / settings.ini and it works. Am I the only one? I'm blind? ;) The GTK style configuration was refactored, and integrated in the main style configuration in System Settings: System Settings -> Application Style -> Application Style -> Configure GNOME/GTK Application Style (button) This means it is part of plasma-desktop or plasma-workspace (I don't remember which), and neither of them nor systemsettings 5.19 migrated to testing yet. Hopefully almost everything (excluding plasma-vault) will migrate tomorrow. Thanks Pino, I was too quick to update the system and report the problem. I have seen in sid the new placing. -- Saluti, Luca Pedrielli
Re: Configure GNOME/GTK Application Style
Il 12/11/20 12:06, Brad Rogers ha scritto: On Thu, 12 Nov 2020 11:17:07 +0100 "luca.pedrielli" wrote: Hello luca.pedrielli, kde-config-gtk-style: amd64 4: 5.19.5-3 is installed. i can manually edit .config / gtk-3.0 / settings.ini and it works. Not updated yet, because various parts (IDK exactly how many) of 5.19 didn't migrate today. Will keep an eye open for issues when I do. As Martin Steigerwald often reminds us, I'm waiting to ensure a full(er) transition of parts. For example, libkdecorations has issues that Norbert Preining tells us are addressed in the -4 update, which hasn't transitioned to testing from sid today. Since 'appearance' is allied (at least verbally) to 'decoration' there might be some correlation there. However, that is purely supposition on my part, as I can't see a direct dependency link between the relevant parts. I'm always a little apprehensive when large transitions occur. Having just set about an upgrade (testing it out, not actually performing it), I see that to satisfy issues, removing kde-style-oxygen-qt5 is suggested, but as that's my preferred style, I'd rather keep it if possible. This too, /might/ be related to kdecorations transition. Hi Brad, you are right, it is working in sid, so it might depend on kdecorations transition. Thanks, Luca. --
Configure GNOME/GTK Application Style
after updating my Debian testing, I no longer find the ability to change Gnome / gtk application style in systemsettings. kde-config-gtk-style: amd64 4: 5.19.5-3 is installed. i can manually edit .config / gtk-3.0 / settings.ini and it works. Am I the only one? I'm blind? ;) Thanks, Luca.
Re: Smart location no longer smart
Il 10/11/20 18:10, Brad Rogers ha scritto: On Tue, 10 Nov 2020 17:08:55 +0100 "luca.pedrielli" wrote: Hello luca.pedrielli, add AllowKDEAppsToRememberWindowPositions=false in ~/.config/kdeglobals I'm seeing some undesirable side effects now; Close gadget now toggles maximised window. Maximize gadget minimizes window to taskbar. Minimize gadget does nothing. This time I can not confirm and Minimize/maximize/Close and RollUp are working properly here. How critical is position of AllowKDEAppsToRememberWindowPositions=false in kdeglobals? I've placed it in the section headed [General] Me too. At the end of [General] section. Not a big deal, as I can workaround the issues, but it'll take a day or two to get used to. Then I'll probably have to 'unlearn' the changes later. -- Saluti, Luca Pedrielli
Re: Smart location no longer smart
Il 10/11/20 16:56, Brad Rogers ha scritto:
On Tue, 10 Nov 2020 16:42:05 +0100
"luca.pedrielli" wrote:
Hello luca.pedrielli,
https://www.reddit.com/r/kde/comments/j96kmq/window_placement_settings_not_working/ga90m1h/
Nice find. Thanks again.
Just have to play the waiting game now.
{fx: taps foot impatiently}
it's working here:
add AllowKDEAppsToRememberWindowPositions=false in ~/.config/kdeglobals
/[General]/
/.../
/.../
/.../
/AllowKDEAppsToRememberWindowPositions=false//
/
and logout/login
--
Saluti, Luca Pedrielli
Re: Smart location no longer smart
Il 10/11/20 15:35, Brad Rogers ha scritto: Hello, Using Debian testing, regularly updated (almost daily). I have KDE set to locate windows using the "Smart" option. For the last week or so, I've noticed that Dolphin (maybe others, but I've not noticed the same behaviour with other software) is now always located in the same place. IOW, when I open a second instance, it gets placed exactly over the top of the existing window. That is, 'smart' location seems to not work. I've looked in KDE & Dolphin settings, thinking I may well have set something incorrectly, but without luck. There seems to be no existing bug reports, further leading me to think the problem is local. I tried setting up a new user, and found that exhibited the same behaviour. Deleting dolphinrc didn't help. There are no special window or application rules for dolphin, so I'm at a loss. Anybody have any suggestions. Any help greatly appreciated. Thanks. https://www.reddit.com/r/kde/comments/j96kmq/window_placement_settings_not_working/ga90m1h/ -- Saluti, Luca Pedrielli
Re: Smart location no longer smart
Il 10/11/20 15:35, Brad Rogers ha scritto: Hello, Using Debian testing, regularly updated (almost daily). I have KDE set to locate windows using the "Smart" option. For the last week or so, I've noticed that Dolphin (maybe others, but I've not noticed the same behaviour with other software) is now always located in the same place. IOW, when I open a second instance, it gets placed exactly over the top of the existing window. That is, 'smart' location seems to not work. I've looked in KDE & Dolphin settings, thinking I may well have set something incorrectly, but without luck. There seems to be no existing bug reports, further leading me to think the problem is local. I tried setting up a new user, and found that exhibited the same behaviour. Deleting dolphinrc didn't help. There are no special window or application rules for dolphin, so I'm at a loss. Anybody have any suggestions. Any help greatly appreciated. Thanks. I can confirm :( I tried with konsole and the behavieur is the same. Tried also with other Window placement (cascade, random, Under-mouse) with no luck. -- Saluti, Luca Pedrielli
Re: [SOLVED] Re: Automatic screen locking
Il 02/09/20 16:47, local10 ha scritto: Aug 20, 2020, 01:56 by loca...@tutanota.com: Aug 18, 2020, 19:22 by ago...@gmail.com: an example: https://lists.debian.org/debian-kde/2019/11/msg7.html You were right, it was juk that was preventing automatic screen locking from working correctly. A bit strange though as juk controls are on the lock page and one can control juk even if the system is locked. Thanks to everyone who responded. ;) https://bugs.kde.org/show_bug.cgi?id=421011 -- Saluti, Luca Pedrielli
Re: Automatic screen locking
Il 20/08/20 03:56, local10 ha scritto: Aug 18, 2020, 19:22 by ago...@gmail.com: an example: https://lists.debian.org/debian-kde/2019/11/msg7.html I'm running sddm but do not have ktorrent installed. More info: $ cat ~/.config/kscreenlockerrc [$Version] update_info=kscreenlocker.upd:0.1-autolock [Daemon] LockGrace=30 Timeout=1 $ cat ./.xsession-errors | grep -i lock 2020-08-19T21:16:39 Checking update-file '/usr/share/kconf_update/kscreenlocker.upd' for new updates 2020-08-19T21:16:39 Checking update-file '/usr/share/kconf_update/webengineurlinterceptoradblock.upd' for new updates Configuring Lock Action org.kde.plasmaquick: New Applet "Digital Clock" with a weight of 54 org.kde.plasmaquick: Delayed preload of "Digital Clock" after 3.347 seconds org.kde.plasmaquick: Applet "Digital Clock" loaded after 163 msec $ cat ./.xsession-errors | grep -i screen 2020-08-19T21:16:39 Checking update-file '/usr/share/kconf_update/kscreenlocker.upd' for new updates kscreen.kded: UPower not available, lid detection won't work kscreen.kded: PowerDevil SuspendSession action not available! kscreen: Requesting missing EDID for outputs (81) powerdevil: Handle button events action could not check for screen configuration $ cat ./.xsession-errors | grep -i err Qt: Session management error: networkIdsList argument is NULL qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 814, resource id: 46137352, major code: 3 (GetWindowAttributes), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 815, resource id: 46137352, major code: 14 (GetGeometry), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2533, resource id: 65011717, major code: 18 (ChangeProperty), minor code: 0 org.kde.pim.akonadicore: Job error: "" for collection: QVector() libepub (II): Found containerr libepub (II): Found containerr qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3136, resource id: 10485765, major code: 18 (ChangeProperty), minor code: 0 Qt: Session management error: networkIdsList argument is NULL qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 8191, resource id: 2097194, major code: 18 (ChangeProperty), minor code: 0 : QML QQuickLayoutAttached: Binding loop detected for property "preferredHeight" qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2731, resource id: 10485763, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2759, resource id: 54525958, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2765, resource id: 56623110, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2776, resource id: 48234502, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2808, resource id: 58720263, major code: 142 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 2935, resource id: 71303174, major code: 142 (Unknown), minor code: 3 powerdevil: Added interrupt session ... See https://pastebin.com/x66hiscg for complete .xsession-errors file. Thanks At this point I don't know how to help you anymore :( However you may have to confront the running programs, configuration files and log files with the new working user. -- Saluti, Luca Pedrielli
Re: Automatic screen locking
Il 18/08/20 19:54, local10 ha scritto: Aug 18, 2020, 17:33 by ago...@gmail.com: maybe is running a program that prevent automatic screen locking? I don't recall specifically installing anything like that. Unless something was installed as a part of recommended packages and then somehow got activated. Thanks, an example: https://lists.debian.org/debian-kde/2019/11/msg7.html -- Saluti, Luca Pedrielli
Re: Automatic screen locking
Il 18/08/20 18:57, local10 ha scritto: Aug 18, 2020, 12:51 by perezme...@gmail.com: I haven't noticed that myself. Try creating a new user to see if it's a configuration issue or a system issue. For a new user automatic screen locking work properly, that is, the system locks the screen after a specified amount of time. Not sure why it doesn't do this for my regular account though. Thanks, maybe is running a program that prevent automatic screen locking? -- Saluti, Luca Pedrielli
Re: KDE Stops opening new programs
Il 17/08/20 12:38, Miguel A. Vallejo ha scritto: https://bugs.kde.org/show_bug.cgi?id=404652 is related? Probably... because another thing I noticed recently is some file extensions do not appear with an icon in Dolphin, just blank. I noticed it too :(
Re: KDE Stops opening new programs
Il 17/08/20 10:07, Miguel A. Vallejo ha scritto: Luca wrote: maybe this way you can find the culprit: $ lsof -U +c 15 | cut -f1 -d' ' | sort | uniq -c | sort -rn | head -3 And the winner is: thumbnail.so I found the way to reproduce the problem. In Dolphin, select a file. Right click and select delete. Press Ok in confirmation dialog. When pressing Ok a new "thumbnail.so [kdeinit5] thumbnail" process appears in state S (interruptible sleep (waiting for an event to complete) according to ps) and a new "Qt Selection Owner for thumbnail.so" entry in xrestop. When entries reach 256, X stops to open new windows. Fortunately a simple killall -9 thumbnail.so solves the problem. Looking in debian packages there are two packages with a thumbnail.so file in it: Imagemagick and kio-extras. I suspect the one bugging me is kio-extras. Is it time to file a new bug against kio-extras? https://bugs.kde.org/show_bug.cgi?id=404652 is related? -- Saluti, Luca Pedrielli
Re: KDE Stops opening new programs
Il 16/08/20 18:05, Miguel A. Vallejo ha scritto: Hello I'm experiencing a weird behaviour from KDE for a few days with an up to date debian unstable. From time to time it stops opening new programs, and programs already opened are unable to display dialogs. I suspect it is unable to open any new window. Keeping a terminal open I tried to launch new programs when the problem appears and I get this error: "Maximum number of clients reached Error: cannot open display: :0" Tried xrestop and it is full of entries with PID as ? and Identifier ""Qt Selection Owner for thumbnail.so" Log out / in does not solve the problem, a system reboot is needed to return to normality (for a while) Any ideas? Thanks in advance maybe this way you can find the culprit: $ lsof -U +c 15 | cut -f1 -d' ' | sort | uniq -c | sort -rn | head -3 -- Best, Luca Pedrielli
Re: window manager crash
Il 03/08/20 20:14, Rainer Dorsch ha scritto: Hi, I have for one user on a Debian 10 system an issue which looks like a window manager crash. I.e. one application (e.g. kmail) is full screen w/o window decoration. I can start new apps using the (former) K-menu, they also start immediately fullscreen. It is particularly likely to happen after a switch user Can anybody advise on how to debug this? Or as a workaround to restart the window manager. It seems also the keyboard is dead e.g. no input possible into a console on that session (though swtiching to another VTT is still possible (Alt+Ctrl+Fx). alt+F2(krunner) is working? if yes maybe you can try with $ kquitapp5 plasmashell $ kstart5 plasmashell and restart plasma If it is too hard to debug, is there a good way to reset all KDE configurations for a user? Is mv .kde .kde.old mv .local .local.old mv .config .config.old sufficient? Any ideas on less drastic measures are welcome :-) Thanks Rainer -- Saluti, Luca Pedrielli
Re: A way to drop into shell/terminal from KDE login screen?
you mean this? https://wiki.debian.org/Console Il 01/08/20 17:42, local10 ha scritto: Hi, Is there a way to drop into shell/terminal from the KDE login screen? Under "Sessions" dropdown I just have "Plasma" and that's it. I'm using sddm and X11. Any ideas? Thanks # echo "It's a Debian Buster PC"; uname -a It's a Debian Buster PC Linux tst 4.19.0-10-amd64 #1 SMP Debian 4.19.132-1 (2020-07-24) x86_64 GNU/Linux -- Saluti, Luca Pedrielli
Re: Status of Plasma 5.18/5.19?
Il 27/07/20 11:53, Marco Valli ha scritto: In data lunedì 27 luglio 2020 10:19:41 CEST, luca.pedrielli ha scritto: Thanks Marco for another great comment. Lol, I have to assume you've never heard of the novacula Occami. regards Thanks twice. -- Saluti, Luca Pedrielli
Re: Status of Plasma 5.18/5.19?
Il 27/07/20 09:46, Marco Valli ha scritto: In data martedì 21 luglio 2020 21:03:15 CEST, hai scritto: I certainly use Sid as a rolling release, and many other people do the same. Many people would like to experience the reliability, maturity, and democratic governance of Debian while having updated packages, and sid offers that for them. In particular, KDE Plasma improves dramatically each release and I certainly can't stand using old versions of Plasma full of already-fixed bugs, and I expect other Plasma users feel the same. I also use sid but i don't break the balls to the guys of the debian kde team if it's not updated enough. regards Thanks Marco for another great comment. -- Saluti, Luca Pedrielli
Re: Okular crashes opening some PDFs
Il 25/07/20 11:27, Miguel A. Vallejo ha scritto:
I don't understand anything. Does Okular depend on firefox?
who knows ;)
$ strace -f okular BOE-A-2018-5704.pdf 2>&1 | grep mozilla | grep -v
"non esistente"
[pid 25893] openat(AT_FDCWD, "/home/ilprof/.mozilla/firefox/",
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 13
[pid 25893] openat(AT_FDCWD,
"/home/ilprof/.mozilla/firefox/r9w66mt8.default/pkcs11.txt", O_RDONLY) = 13
[pid 25893]
access("/home/ilprof/.mozilla/firefox/r9w66mt8.default/cert9.db", F_OK) = 0
[pid 25893]
lstat("/home/ilprof/.mozilla/firefox/r9w66mt8.default/cert9.db",
{st_mode=S_IFREG|0600, st_size=458752, ...}) = 0
[pid 25893] openat(AT_FDCWD,
"/home/ilprof/.mozilla/firefox/r9w66mt8.default/cert9.db",
O_RDONLY|O_NOFOLLOW|O_CLOEXEC) = 13
[pid 25893]
stat("/home/ilprof/.mozilla/firefox/r9w66mt8.default/cert9.db",
{st_mode=S_IFREG|0600, st_size=458752, ...}) = 0
[pid 25893]
statfs("/home/ilprof/.mozilla/firefox/r9w66mt8.default/cert9.db",
{f_type=EXT2_SUPER_MAGIC, f_bsize=4096, f_blocks=19460017,
f_bfree=14366049, f_bavail=13366766, f_files=4980736, f_ffree=4767779,
f_fsid={val=[318426972, 2131749708]}, f_namelen=255, f_frsize=4096,
f_flags=ST_VALID|ST_RELATIME}) = 0
[pid 25893]
access("/home/ilprof/.mozilla/firefox/r9w66mt8.default/key4.db", F_OK) = 0
[pid 25893]
lstat("/home/ilprof/.mozilla/firefox/r9w66mt8.default/key4.db",
{st_mode=S_IFREG|0600, st_size=294912, ...}) = 0
[pid 25893]
stat("/home/ilprof/.mozilla/firefox/r9w66mt8.default/key4.db",
{st_mode=S_IFREG|0600, st_size=294912, ...}) = 0
[pid 25893] openat(AT_FDCWD,
"/home/ilprof/.mozilla/firefox/r9w66mt8.default/key4.db",
O_RDONLY|O_NOFOLLOW|O_CLOEXEC) = 14
[pid 25893]
stat("/home/ilprof/.mozilla/firefox/r9w66mt8.default/key4.db",
{st_mode=S_IFREG|0600, st_size=294912, ...}) = 0
[pid 25893]
statfs("/home/ilprof/.mozilla/firefox/r9w66mt8.default/key4.db",
{f_type=EXT2_SUPER_MAGIC, f_bsize=4096, f_blocks=19460017,
f_bfree=14366049, f_bavail=13366766, f_files=4980736, f_ffree=4767779,
f_fsid={val=[318426972, 2131749708]}, f_namelen=255, f_frsize=4096,
f_flags=ST_VALID|ST_RELATIME}) = 0
Anyway thank you for the clues. Now it is working.
happy to help.
Best, Luca.
Re: Okular crashes opening some PDFs
Il 25/07/20 01:18, Miguel A. Vallejo ha scritto: Thank you for your advice. I reverted the packages to the ones available in sid. Now waiting for okular to upgrade I really miss it when working with these PDF files Thank you The strange thing is that here in "sid" okular works correctly. -- root@Sid:/tmp# dpkg -l| grep okular ii libokular5core9 4:20.04.2-1 amd64 libraries for the Okular document viewer ii okular 4:20.04.2-1 amd64 universal document viewer root@Sid:/tmp# dpkg -l| grep poppler ii libpoppler-cpp0v5:amd64 0.71.0-6 amd64 PDF rendering library (CPP shared library) ii libpoppler-glib8:amd64 0.71.0-6 amd64 PDF rendering library (GLib-based shared library) ii libpoppler-qt5-1:amd64 0.71.0-6 amd64 PDF rendering library (Qt 5 based shared library) ii libpoppler82:amd64 0.71.0-6 amd64 PDF rendering library ii poppler-data 0.4.9-2 all encoding data for the poppler PDF rendering library ii poppler-utils 0.71.0-6 amd64 PDF utilities (based on Poppler) -- However I can reproduce the error if I run okular from a homedir without .mozilla (where it seems to look for some certs) root@Sid:/tmp# pdfsig BOE-A-2018-5704.pdf Digital Signature Info of: BOE-A-2018-5704.pdf Internal Error (0): couldn't find default Firefox Folder Errore di segmentazione -- Saluti, Luca Pedrielli
Re: Okular crashes opening some PDFs
Il 24/07/20 21:27, Miguel A. Vallejo ha scritto: luca.pedrielli wrote: $ pdfsig your_signed.pdf is working? No, it is not ~$ pdfsig BOE-A-2018-5704.pdf Digital Signature Info of: BOE-A-2018-5704.pdf Segmentation fault https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924050 -- Saluti, Luca Pedrielli
Re: Okular crashes opening some PDFs
Il 24/07/20 12:13, Miguel A. Vallejo ha scritto: https://bugs.kde.org/show_bug.cgi?id=407369 It does not make sense... Those PDF files worked for me up to some weeks ago. The PDF files seem to open normally right now on testing. I think it is a different buf. $ pdfsig your_signed.pdf is working? -- Saluti, Luca Pedrielli
Re: Okular crashes opening some PDFs
Il 24/07/20 11:55, Miguel A. Vallejo ha scritto: maybe it's related to pdf digitally signed? Probably yes libnss3 is involved? https://forum.kde.org/viewtopic.php?f=309&t=160361 My libnss3 hasn't been upgraded since I reinstalled the system last February, so I'm not sure https://bugs.kde.org/show_bug.cgi?id=407369 -- Saluti, Luca Pedrielli
Re: Okular crashes opening some PDFs
Il 24/07/20 11:28, Miguel A. Vallejo ha scritto: After playing to downgrade all the Okular dependencies I can't determine what package makes Okular to crash opening certain PDF files. It's true I couldn't downgrade all packages without breaking the whole system, but the ones I was able to downgrade are not the culprits. I guess my only option now is to file a bug report. maybe it's related to pdf digitally signed? libnss3 is involved? https://forum.kde.org/viewtopic.php?f=309&t=160361 -- Saluti, Luca Pedrielli
Re: Okular crashes opening some PDFs
it's working here in testing(daily updated) with okular 4:20.04.2-1. Il 22/07/20 09:46, Miguel A. Vallejo ha scritto: John Scott wrote: Do you have one you're comfortable sharing (possibly off-list)? Yes, for example this one: https://www.boe.es/boe/dias/2018/04/26/pdfs/BOE-A-2018-5704.pdf Just download it to your hard disk. I have consulted it regularly since 2018 but since a few days it makes okular to crash. It opens fine in other readers, for example in Chrome. eoz@waterhole:~$ okular BOE-A-2018-5704.pdf KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = okular path = /usr/bin pid = 3924 KCrash: Arguments: /usr/bin/okular BOE-A-2018-5704.pdf KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi >From Dr Konqi: Application: Okular (okular), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f010dc97840 (LWP 3924))] Thread 7 (Thread 0x7f00f5fc2700 (LWP 3930)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55adb441b3b8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55adb441b368, cond=0x55adb441b390) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55adb441b390, mutex=0x55adb441b368) at pthread_cond_wait.c:638 #3 0x7f00fe12575b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f00fe125377 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f0110e64ea7 in start_thread (arg=) at pthread_create.c:477 #6 0x7f0111928dcf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f00f67c3700 (LWP 3929)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55adb441b3b8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55adb441b368, cond=0x55adb441b390) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55adb441b390, mutex=0x55adb441b368) at pthread_cond_wait.c:638 #3 0x7f00fe12575b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f00fe125377 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f0110e64ea7 in start_thread (arg=) at pthread_create.c:477 #6 0x7f0111928dcf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f00f6fc4700 (LWP 3928)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55adb441b3b8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55adb441b368, cond=0x55adb441b390) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55adb441b390, mutex=0x55adb441b368) at pthread_cond_wait.c:638 #3 0x7f00fe12575b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f00fe125377 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f0110e64ea7 in start_thread (arg=) at pthread_create.c:477 #6 0x7f0111928dcf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f00f77c5700 (LWP 3927)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55adb441b3b8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55adb441b368, cond=0x55adb441b390) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55adb441b390, mutex=0x55adb441b368) at pthread_cond_wait.c:638 #3 0x7f00fe12575b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f00fe125377 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f0110e64ea7 in start_thread (arg=) at pthread_create.c:477 #6 0x7f0111928dcf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f0106d32700 (LWP 3926)): #0 __GI___libc_read (nbytes=16, buf=0x7f0106d31b20, fd=7) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=7, buf=0x7f0106d31b20, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f01103c0f4f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f011037933e in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0110379792 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f011037990f in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f0111eb390b in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0111e5b89b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0111c868be in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f0112104507 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7f0111c87988 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f0110e64ea7 in start_thread (arg=) at pthread_create.c:477 #12 0x7f0111928dcf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f010ceb1700 (LWP 3925)): #0
Re: where to report these issues properly?
Il 05/06/20 21:09, Marco Möller ha scritto: (2) In the "Info Center" after a first upgrade on the 2nd of June, if I remember correctly, new categories (for instance some tree with graphics and openGL (?) related information) appeared (or I have not noticed them to arrive earlier). But then arrived the second upgrade on the 4th of June and since then names of the root entries in the shown trees have no title text visible anymore, and they for sure have still been visible after the upgrade from 2nd of June. There are displayed now the tree names "System Information", "Memory", "Energy Information", "File Index Monitor", all these 4 actually not being trees but a single root entry, and then coming 3 more root entries having subtrees which do not display a name for the root entry anymore. Looking into the subtrees, the first of the 3 starts with "Device Viewer", then next one with "Network Interfaces", and the last tree has as the first subtree item name set to "X-Server". https://bugs.kde.org/show_bug.cgi?id=421830 -- Saluti, Luca Pedrielli
Re: which commands are executed by the "bluetooth enable" button?
Il 03/05/20 00:09, Marco Möller ha scritto:
the question how KDE is achieving to unblock the soft block on
bluetooth (even without this package being installed) did not become
clarified to me. :-(
I'm not a qml expert, but it should do in this way(from Toolbar.qml):
var enable = !btManager.bluetoothOperational;
btManager.bluetoothBlocked = !enable;
for (var i = 0; i < btManager.adapters.length; ++i) {
var adapter = btManager.adapters[i];
adapter.powered = enable;
}
--
Saluti, Luca Pedrielli
Re: which commands are executed by the "bluetooth enable" button?
Il 29/04/20 16:23, Marco Möller ha scritto: On 29.04.20 10:15, luca.pedrielli wrote: |#!/bin/bashifrfkill list bluetooth |grep -q 'yes$';thenrfkill unblock bluetooth elserfkill block bluetooth fi| Hmmm. I have no rfkill installed in my system. I may install it and try it out. The GUI button will know another trick, though. rfkill is working here, but you can also try this(working here too): $ dbus-send --system --dest=org.bluez --print-reply /org/bluez/hci0 org.freedesktop.DBus.Properties.Set string:org.bluez.Adapter1 string:Powered variant:boolean:true or false https://medium.com/@konchunas/how-to-toggle-bluetooth-with-shortcut-on-linux-the-proper-way-a440dd88605e -- Saluti, Luca Pedrielli
Re: which commands are executed by the "bluetooth enable" button?
Il 29/04/20 16:23, Marco Möller ha scritto: On 29.04.20 10:15, luca.pedrielli wrote: |#!/bin/bashifrfkill list bluetooth |grep -q 'yes$';thenrfkill unblock bluetooth elserfkill block bluetooth fi| Hmmm. I have no rfkill installed in my system. I may install it and try it out. The GUI button will know another trick, though. also bluez-tools can be useful -- Saluti, Luca Pedrielli
Re: which commands are executed by the "bluetooth enable" button?
Il 29/04/20 16:23, Marco Möller ha scritto: On 29.04.20 10:15, luca.pedrielli wrote: |#!/bin/bashifrfkill list bluetooth |grep -q 'yes$';thenrfkill unblock bluetooth elserfkill block bluetooth fi| Hmmm. I have no rfkill installed in my system. I may install it and try it out. The GUI button will know another trick, though. you can take a look at /usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/Toolbar.qml -- Saluti, Luca Pedrielli
Re: which commands are executed by the "bluetooth enable" button?
you can try: |#!/bin/bashifrfkill list bluetooth |grep -q 'yes$';thenrfkill unblock bluetooth elserfkill block bluetooth fi| https://askubuntu.com/questions/1144596/set-a-shortcut-to-toggle-bluetooth-on-or-off Il 28/04/20 23:03, Marco Möller ha scritto: There are two buttons for triggering Bluetooth availability by a mouse click, and they appear to do some magic. I would need to find out about this, I am searching for the commands which become executed by these buttons. After a reboot Bluetooth is still deactivated, and for activating it I can go here: System Settings - Network - Bluetooth There, I find emphasized by alarming color "Bluetooth is disabled" and next to it is then nicely provided an "Enable" button which perfectly works. After Bluetooth becomes activated in this way, then there appears the related System Tray icon in the panel of KDE Plasma, and from now on I can there deactivate Bluetooth, or activate it there again, forth and back, repeatedly, which works as expected. In another thread I asked how to set a keyboard shortcut for this activation/deactivation of Bluetooth, and quickly got the very helpful answer how to set the needed "custom shortcut" (Thanks, Helge!). However, the command which has to become executed by the shortcut troubles. It worked for Helge, but not for me, and the Internet is full about the problem and error message as I receive it. There obviously is something more going on behind this buttons, than simply calling the commands "bluetoothctl power on" or "bluetoothctl power off". I tested the "bluetoothctl" command interactively on a CLI as the user or with sudo and got with sub-command "devices" (and others) the error message: "No default controller available". The internet is full of questions about this and by now I could not find any good answer. There are suggestions that the problem would have been solved after a cold start (not simply a reboot), after driver re-installation, booting into Windows and back into Linux, and many more weird solutions. BUT: if I use the mouse in order to trigger the button, then bluetooth becomes enabled or disabled without any problems, forth and back, repeatedly. And if it first becomes enabled by the mouse click on the button, I then afterwards also succeed on the CLI with the commands given as a normal user "bluetoothctl power off" and "bluetoothctl power on", forth and back, repeatedly (and also the keyboard shortcut works for me, then). Once I use the mouse for deactivating Bluetooth by the button, then the bluetoothctl commands again fail with said error message. Obviously, the buttons know the magic trick how to activate/deactivate the communication with the present hardware at a state, when bluetoothctl cannot succeed to get access to the device. I should add, that "systemctl status bluetooth" confirms this service to all the time being active, and obviously there are no drivers or configurations missing - the buttons can do the job. So, nothing is missing but to find out which commands these buttons trigger. Well, I am now searching for this full series of commands, for achieving on the CLI the same result as these buttons are doing it. Could you help? Marco. -- Saluti, Luca Pedrielli
Re: bulk change of KATE session files
Il 31/03/20 02:28, Gary Dale ha scritto: I've found it necessary to change the location of a directory that contained files from several KATE sessions. I'm looking for a way to modify the KATE configuration files to reflect the new locations rather than having to create new sessions. Two files in my .config folder contain the directory and file names - katemetainfos and katerc - but when I make the changes there, they don't seem to be picked up by KATE. Instead it opens the old session, showing the files in their old locations but greyed out because they don't exist in that (non-existent) location. Is there a way to do what I want? did you take a look at .local/share/kate/sessions ? -- Saluti, Luca Pedrielli
Re: Plasma 5.17.5 coming to unstable
Il 16/02/20 23:26, Pino Toscano ha scritto: In data venerdì 14 febbraio 2020 21:58:21 CET, Pino Toscano ha scritto: Plasma 5.17.5 is slowly coming to unstable, some pieces are being uploaded as of this email. Semi-important note: tomorrow few libraries (kdecoration, libkscreen, libksysguard) will migrate to testing, while the rest should hopefully migrate on Thursday. Since their usage in a 5.14.x environment is not a tested scenario, and thus they might cause issues, my recommendation is to avoid upgrading them for few days (so together with the rest of Plasma 5.17). bug reported and confirmed: https://bugs.kde.org/show_bug.cgi?id=417953 -- Saluti, Luca Pedrielli
Re: Plasma 5.17.5 coming to unstable
Il 16/02/20 23:26, Pino Toscano ha scritto: In data venerdì 14 febbraio 2020 21:58:21 CET, Pino Toscano ha scritto: Plasma 5.17.5 is slowly coming to unstable, some pieces are being uploaded as of this email. Semi-important note: tomorrow few libraries (kdecoration, libkscreen, libksysguard) will migrate to testing, while the rest should hopefully migrate on Thursday. Since their usage in a 5.14.x environment is not a tested scenario, and thus they might cause issues, my recommendation is to avoid upgrading them for few days (so together with the rest of Plasma 5.17). Hi, installed in testing and it seems ok. I found only a regression in plasma-notes. Before I was able to drag and drop a link from the browser and it was correctly recognized from old plasma-note version. now I'm not able to drop the link in the textarea and a new plasmoid on the desktop is created. coping manually the old main.qml it works. -- Saluti, Luca Pedrielli
Re: Plasma 5.17.5 coming to unstable
Il 14/02/20 21:58, Pino Toscano ha scritto: Hi, Plasma 5.17.5 is slowly coming to unstable, some pieces are being uploaded as of this email. Hence: please wait at least 12/24 hours to everything is uploaded, built, and available in the mirrors as update. Make sure everything is from Plasma 5.17.5 before reporting issues. Otherwise, feel free to report issues, as usual. Hi, updated this morning with no problems. I only had some trouble to close the plasma session opened during the update(forced reboot via konsole;)) I've done some tests and all seems ok. Many thanks. -- Saluti, Luca Pedrielli
Re: Plasma 5.17.5 coming to unstable
Il 15/02/20 17:30, Pino Toscano ha scritto: In data sabato 15 febbraio 2020 12:46:30 CET, Martin Steigerwald ha scritto: Reading your mail my motivation does not increase. I did not meant any offense or accusation. Neither did I. Considering that it is well known to us (packagers) how often KDE components/products are released, pointing out explicitly that "Frameworks are old" does not give me any actionable nor new bits of information, nor helps users in any way. Hence the only actionable item in this situation is actually do something about it, and this is why I asked whether you would have wanted to volunteer yourself in this of work. Easy. Please do not hijack this thread (which is about Plasma 5.17). -- Saluti, Luca Pedrielli
Re: How to set the default browser ?
Il 03/02/20 09:48, Michal BULIK ha scritto: Hi Luca, Yes, xdg-desktop-portal-kde is installed : ii xdg-desktop-portal-kde 5.14.5-2 amd64 backend implementation for xdg-desktop-portal using Qt When I launch firefox after unsetting GTK_USE_PORTAL it complains no more about being non-default. In fact I've set GTK_USE_PORTAL in my .bashrc in order to have KDE dialogs for file saving etc. Now I've commented it out. Thank you, Michal you can also simply uncheck "Always check if Firefox is your default browser" in firefox preferences in order to keep KDE dialogs. Best, Luca. Il 31/01/20 10:00, Michal Bulik ha scritto: Hi, Every day my Firefox says to me that it's not the default, I click on the right button to make it default. I also go to the Control Panel -> Applications -> Default Applications -> Browser and I choose Firefox but the effects do not last ... In the alternatives x-www-browser points the /usr/bin/firefox ... Any hint how to fix it ? Thank you Michal PS. I'm running bullseye (upgraded very frequently). is xdg-desktop-portal-kde installed? if yes try this: $ unset GTK_USE_PORTAL; firefox -- Saluti, Luca Pedrielli
Re: How to set the default browser ?
Il 03/02/20 09:48, Michal BULIK ha scritto: Hi Luca, Yes, xdg-desktop-portal-kde is installed : ii xdg-desktop-portal-kde 5.14.5-2 amd64 backend implementation for xdg-desktop-portal using Qt When I launch firefox after unsetting GTK_USE_PORTAL it complains no more about being non-default. In fact I've set GTK_USE_PORTAL in my .bashrc in order to have KDE dialogs for file saving etc. Now I've commented it out. Thank you, Michal Il 31/01/20 10:00, Michal Bulik ha scritto: Hi, Every day my Firefox says to me that it's not the default, I click on the right button to make it default. I also go to the Control Panel -> Applications -> Default Applications -> Browser and I choose Firefox but the effects do not last ... In the alternatives x-www-browser points the /usr/bin/firefox ... Any hint how to fix it ? Thank you Michal PS. I'm running bullseye (upgraded very frequently). is xdg-desktop-portal-kde installed? if yes try this: $ unset GTK_USE_PORTAL; firefox happy you've solved. https://bugzilla.mozilla.org/show_bug.cgi?id=1516290 -- Saluti, Luca Pedrielli
Re: How to set the default browser ?
Il 31/01/20 10:00, Michal Bulik ha scritto: Hi, Every day my Firefox says to me that it's not the default, I click on the right button to make it default. I also go to the Control Panel -> Applications -> Default Applications -> Browser and I choose Firefox but the effects do not last ... In the alternatives x-www-browser points the /usr/bin/firefox ... Any hint how to fix it ? Thank you Michal PS. I'm running bullseye (upgraded very frequently). is xdg-desktop-portal-kde installed? if yes try this: $ unset GTK_USE_PORTAL; firefox -- Saluti, Luca Pedrielli
Re: Something broke
Il 19/01/20 16:21, Rob Brewer ha scritto: luca.pedrielli wrote: maybe it is only a cache problem. try to clear it. or a configuration problem. try to remove/add printers Had another look today and found an outstanding print job on a switched off network printer. I deleted that job and was able to add the 'Printers' item again to the System Tray without crashing plasmashell. So maybe as you suggested it was a print queue problem that caused the crash although it is a bit surprising that this could prevent plasma from starting up correctly. Rob if you can reproduce the error situation, you should open a bug report. -- Saluti, Luca Pedrielli
Re: Something broke
Il 18/01/20 18:35, Rob Brewer ha scritto: Rob Brewer wrote: Not sure if this is a cups issue or a plasmashell issue though. On further checking /usr/lib/x86_64-linux-gnu/libkcupslib.so is in the print-manager package. Rob maybe it is only a cache problem. try to clear it. or a configuration problem. try to remove/add printers. -- Saluti, Luca Pedrielli
Re: Something broke
Il 18/01/20 16:52, Rob Brewer ha scritto: luca.pedrielli wrote: Hi, did you try with a new user? It's difficult as this is a single user box. are you using some strange plasmoid? Not as far as I am aware. The desktop hasn't changed for quite some time. Best, Luca. Thank you for the suggestions. Rob plasmashell seems crashing after printer-manager activity can you stop cups service and restart plasmashell? -- Saluti, Luca Pedrielli
Re: Something broke
Hi,
did you try with a new user?
are you using some strange plasmoid?
Best, Luca.
Il 18/01/20 14:45, Rob Brewer ha scritto:
Martin Steigerwald wrote:
You symptoms look like Plasma Shell can not start. What happens if you
start "plasmashell" from a shell window? Are there any error messages?
If so, please post them. You can use KRunner by pressing Alt-Space to
start Plasma Shell, in case KRunner still runs on your desktop.
Also there may be something in ~/.xsession-errors or /var/log/user.log
(in case you use Systemd).
Yes it does look like plasmashell isn't starting. When starting from krunner
the system tray with task bar appear momentarily and then disappear.
When started from konsole I get errors:
plasmashell
Aborting shell load: The activity manager daemon (kactivitymanagerd) is not
running.
If this Plasma has been installed into a custom prefix, verify that its D-Bus
services dir is known to the system for the daemon to be activatable.
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_performance.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kio_fonts.so"
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/libkcm_device_automounter.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/miloutextplugin.so"
snip metadata errors
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_networkmanagement.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_clock.so"
org.kde.plasmaquick: Applet preload policy set to 1
kf5.kpackage: No metadata file in the package, expected it at:
"/home/rwb/Pictures/2103/"
kf5.kpackage: No metadata file in the package, expected it at:
"/home/rwb/Pictures/2103/"
kf5.kpackage: No metadata file in the package, expected it at:
"/home/rwb/Pictures/2103/"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:62:5:
Unable to assign [undefined] to int
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:53:5:
Unable to assign [undefined] to int
file:///usr/share/plasma/packages/org.kde.desktoptoolbox/contents/ui/ToolBoxRoot.qml:101:5:
QML ToolBoxButton: Found duplicate state name: topleft
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"
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/PulseAudio.qml:22:1:
module "org.kde.plasma.private.volume" is not installed
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
trying to show an empty dialog
QQmlComponent: Cannot create new component instance before completing the
previous
libkcups: Create-Printer-Subscriptions last error: 0 successful-ok
libkcups: CUPS-Get-Printers last error: 0 successful-ok
libkcups: Cancel-Subscription last error: 0 successful-ok
libkcups: Create-Printer-Subscriptions last error: 0 successful-ok
libkcups: Get-Jobs last error: 0 successful-ok
Plasma Shell startup completed
libkcups: Get-Jobs last error: 0 successful-ok
libkcups: 5 "EPSON_Stylus_Photo_R800_tuscan3"
libkcups: 3 "HLL8260CDW"
libkcups: 3 "HP_LaserJet_5000_Series_tuscan3"
libkcups: 2
"1 instead of 2 arguments to message {Printing %1 with %2} supplied before
conversion."
file:///usr/share/plasma/plasmoids/org.kde.plasma.mediacontroller/contents/ui/main.qml:55:
TypeError: Cannot read property 'Identity' of undefined
file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/batterymonitor.qml:43:
TypeError: Cannot read property 'Has Cumulative' of undefined
file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/batterymonitor.qml:94:
TypeError: Cannot read property 'Remaining msec' of undefined
Both point size and pixel size set. Using pixel size.
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"
libkcups: 129
KCrash: Attempting to start /usr/bin/plasmashell from kdeinit
sock_file=/run/user/1000/kdeinit5__0
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasmashell path = /usr/bin pid = 31691
So it looks like plasmashell is not starting because kactivitymanagerd isn't
running but if I try to start it I get
:~$ /usr/bin/kactivitymanagerd
Already running
and
:~$ ps aux |grep activity
xxx30089 0.0 0.2 553044 35104 ?Sl 13:25 0:00
/usr
Re: Capslock / Numlock indicator not work in KDE (& sddm)
Il 01/12/19 19:18, Lisandro Damián Nicanor Pérez Meyer ha scritto: Hi! On Thu, 28 Nov 2019 at 07:06, luca.pedrielli wrote: Il 27/11/19 15:14, Franklin Weng ha scritto: luca.pedrielli 於 2019/11/27 下午6:25 寫道: seems search for libkmodifierkey_xcb.so ..that I have not found in debian maybe plasma_engine_keystate.so have some ploblems sddm themes, keyboardindicator, but also others plasmoids like keystate, use qml scripts where the engine is keystate. they work in buster, but not in testing. Thanks. With your survey I found a bug report for plasma-workspace: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942429 I've replied it. Thanks, Franklin Hi Franklin, I have rebuilded kguiaddons-5.62 on my pc. a kmodifierkey_xcb.so is genereted, but non included in the .deb, so I have copied it in /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/ and the error is gone. logout/login and the key indicator(in some way) works. pkg problem? + Indeed it was! Thanks **a lot** fro the triaging and the bug report! I have just uploaded the fix, so I guess it will be available in the next mirror push. Once again, thanks a lot!!! Installed and working in sid. Thanks -- Saluti, Luca Pedrielli
Re: Capslock / Numlock indicator not work in KDE (& sddm)
Il 27/11/19 15:14, Franklin Weng ha scritto: luca.pedrielli 於 2019/11/27 下午6:25 寫道: seems search for libkmodifierkey_xcb.so ..that I have not found in debian maybe plasma_engine_keystate.so have some ploblems sddm themes, keyboardindicator, but also others plasmoids like keystate, use qml scripts where the engine is keystate. they work in buster, but not in testing. Thanks. With your survey I found a bug report for plasma-workspace: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942429 I've replied it. Thanks, Franklin also systemsettings -> numlock on starting session is working too -- Saluti, Luca Pedrielli
Re: Capslock / Numlock indicator not work in KDE (& sddm)
Il 27/11/19 15:14, Franklin Weng ha scritto: luca.pedrielli 於 2019/11/27 下午6:25 寫道: seems search for libkmodifierkey_xcb.so ..that I have not found in debian maybe plasma_engine_keystate.so have some ploblems sddm themes, keyboardindicator, but also others plasmoids like keystate, use qml scripts where the engine is keystate. they work in buster, but not in testing. Thanks. With your survey I found a bug report for plasma-workspace: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942429 I've replied it. Thanks, Franklin with kmodifierkey_xcb.so also sddm capslock alert is working ;) -- Saluti, Luca Pedrielli
Re: Capslock / Numlock indicator not work in KDE (& sddm)
Il 27/11/19 15:14, Franklin Weng ha scritto: luca.pedrielli 於 2019/11/27 下午6:25 寫道: seems search for libkmodifierkey_xcb.so ..that I have not found in debian maybe plasma_engine_keystate.so have some ploblems sddm themes, keyboardindicator, but also others plasmoids like keystate, use qml scripts where the engine is keystate. they work in buster, but not in testing. Thanks. With your survey I found a bug report for plasma-workspace: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942429 I've replied it. Thanks, Franklin Hi Franklin, I have rebuilded kguiaddons-5.62 on my pc. a kmodifierkey_xcb.so is genereted, but non included in the .deb, so I have copied it in /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/ and the error is gone. logout/login and the key indicator(in some way) works. pkg problem? Saluti, Luca Pedrielli
Re: Capslock / Numlock indicator not work in KDE (& sddm)
Il 27/11/19 15:14, Franklin Weng ha scritto: luca.pedrielli 於 2019/11/27 下午6:25 寫道: seems search for libkmodifierkey_xcb.so ..that I have not found in debian maybe plasma_engine_keystate.so have some ploblems sddm themes, keyboardindicator, but also others plasmoids like keystate, use qml scripts where the engine is keystate. they work in buster, but not in testing. Thanks. With your survey I found a bug report for plasma-workspace: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942429 I've replied it. Thanks, Franklin Hi Franklin, thanks for bug-reporting. Let's see what happens ;) -- Saluti, Luca Pedrielli
Re: Capslock / Numlock indicator not work in KDE (& sddm)
Il 27/11/19 10:54, Franklin Weng ha scritto:
Jimmy Johnson 於 2019/11/27 下午2:08 寫道:
On 11/26/19 4:06 PM, Franklin Weng wrote:
Jimmy Johnson 於 2019/11/27 上午6:55 寫道:
On 11/26/19 11:26 AM, Shai Berger wrote:
For some reason, both Jimmy and Luca insist on connecting this to the
wrong problem:
On Tue, 26 Nov 2019 01:30:01 -0800
Jimmy Johnson wrote:
On 11/25/19 7:10 AM, Franklin Weng wrote:
luca.pedrielli 於 2019年11月25日 週一 22:44
Numlock problems had already been reported
https://lists.debian.org/debian-kde/2019/09/msg00033.html
Not sure, but it looks like not the same problem. My problem is
about the indicator not the status itself. The NumLock/Capslock
status is correct according to the xset -q.
The settings for numlock have changed in testing kde5.
I think the systemsettings, input device module is suppose to be
handling numlock on/off at sddm start.
And Luca, later:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941505
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940872
Everything Luca and Jimmy are mentioning is about the state of
numlock when sddm or plasma start.
This is *not* what Franklin or I are talking about. We are talking
about Caps/Num Lock being at the state they should be, as set by
pressing the relevant keys. It is only the visual indicators which
are
not working -- the systray icons in plasma, and the caps-is-on
warning
in the lock or login screen.
Listen to me! Remove your numlockx software,
https://i.imgur.com/G4hSFii.png
go to /etc/sddm.conf and change it to on or off,
https://i.imgur.com/c4k4yTd.png
go to systemsettings and make sure keyboard, numlock is set to no
change.
https://i.imgur.com/c3x5oSt.png
Do it and then come back
https://i.imgur.com/EMjLxsy.jpg
=> Login screen (taken from my phone, after all the settings above were
done of course), the CAPSLOCK warning is always shown
https://i.imgur.com/saGAqD7.png
=> Status of Capslock is off, Numlock is on, but the indicator (red
frame in left and bottom-right corner) shows nothing.
Have you tried a different keyboard layout?
Not too many, but yes.
But as you may have known, no differences.
Also I've seen a new a package named 'numlock', remove it if it's
installed.
It's never been installed in my Debian system.
and tell me I don't know what you're talking about. until then stuff a
sock!
You don't know what I'm talking about.
So do I have to stuff a sock now?
I don't know what you're doing. You look like a ms windows keyboard
jockey in a gui environment. So until I know different, keep the sock
stuffed.
Fortunately I don't understand what you mean.
Let me repeat Shai's quote, also my question:
Everything Luca and Jimmy are mentioning is about the state of
numlock when sddm or plasma start.
This is *not* what Franklin or I are talking about. We are talking
about *Caps/Num Lock being at the state they should be, as set by **
**pressing the relevant keys. It is only the visual indicators which
are **
**not working -- the systray icons in plasma, and the caps-is-on
warning **
**in the lock or login screen.*
I doubt if it is something wrong with D-bus, but I have no idea how to
find the problem out.
When I asked in kde mailing list someone told me it should be Debian
packager's issue. And now in Debian-kde mailing list I have a pair of
socks in my mouth. You may or may not know, in 2017 KDE community
selected one of the goals: onboarding and welcoming for newcomers[1].
However IMO until now the _core_ people still haven't seen the real
problem of KDE community, which -- fortunately or unfortunately -- you
all have shown a perfect example.
Franklin
[1]
https://mail.kde.org/mailman/private/kde-ev-membership/2019-October/037029.html
$ plasmawindowed org.kde.plasma.keyboardindicator
return an error after testing update, while is working in buster:
---
Error: could not load plugin for platform "" error: "The shared library
was not found." QObject(0x0)
---
$ strace -f plasmawindowed org.kde.plasma.keyboardindicator
-
14519 openat(AT_FDCWD,
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/dataengine/plasma_engine_keystate.so",
O_RDONLY|O_CLOEXEC) = 22
14519 read(22,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0@D\0\0\0\0\0\0"..., 832)
= 832
14519 fstat(22, {st_mode=S_IFREG|0644, st_size=105120, ...}) = 0
14519 mmap(NULL, 107088, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 22, 0) =
0x7fbbe4e3b000
14519 mmap(0x7fbbe4e3f000, 69632, PROT_READ|PROT_EXEC,
MAP_PRIVA
Re: Capslock / Numlock indicator not work in KDE (& sddm)
Il 26/11/19 20:26, Shai Berger ha scritto: For some reason, both Jimmy and Luca insist on connecting this to the wrong problem: On Tue, 26 Nov 2019 01:30:01 -0800 Jimmy Johnson wrote: On 11/25/19 7:10 AM, Franklin Weng wrote: luca.pedrielli 於 2019年11月25日 週一 22:44 Numlock problems had already been reported https://lists.debian.org/debian-kde/2019/09/msg00033.html Not sure, but it looks like not the same problem. My problem is about the indicator not the status itself. The NumLock/Capslock status is correct according to the xset -q. The settings for numlock have changed in testing kde5. I think the systemsettings, input device module is suppose to be handling numlock on/off at sddm start. And Luca, later: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941505 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940872 Everything Luca and Jimmy are mentioning is about the state of numlock when sddm or plasma start. This is *not* what Franklin or I are talking about. We are talking about Caps/Num Lock being at the state they should be, as set by pressing the relevant keys. It is only the visual indicators which are not working -- the systray icons in plasma, and the caps-is-on warning in the lock or login screen. Thanks, Shai. What I say is that systemsetting is no more able to handle numlock on/off at session start and keyboardindicator is no more working. This after KF and Qt updates. -- Saluti, Luca Pedrielli
Re: Capslock / Numlock indicator not work in KDE (& sddm)
Il 25/11/19 22:39, Shai Berger ha scritto: On Mon, 25 Nov 2019 23:10:57 +0800 Franklin Weng wrote: luca.pedrielli 於 2019年11月25日 週一 22:44 寫道： Il 24/11/19 02:26, Franklin Weng ha scritto: It looks like no problem in X window level, but the status does not pass to sddm/plasma correctly. No suggestion, but I can confirm this behaviour. Numlock problems had already been reported https://lists.debian.org/debian-kde/2019/09/msg00033.html Not sure, but it looks like not the same problem. My problem is about the indicator not the status itself. The NumLock/Capslock status is correct according to the xset -q. I can also confirm this. My situation is exactly what Franklin described, with one exception: I use lightdm rather than sddm, and there the "Caps On" warning is always off (even when caps is pressed), not always on. Shai https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941505 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940872 -- Saluti, Luca Pedrielli
Re: Capslock / Numlock indicator not work in KDE (& sddm)
Il 24/11/19 02:26, Franklin Weng ha scritto: Hi, I'm using Debian testing and run KDE Plasma 5 (Framework 5.62.0, Qt 5.12.5, xcb window system, Application 19.08.1, kde-plasma-desktop version 5:104). Originally the indicator worked: in sddm login screen it would show warning when Capslock is ON; after logging into Plasma session a small icon would show beside the system tray when Capslock is ON. However from some day it didn't work anymore. The current status of my system is: * In sddm login screen, the Capslock ON warning *always* shows. * In Plasma the keyboard indicator plasmoids (org.kde.plasma.keyboardindicator) shows nothing no matter what the capslock/numlock status is. * Using xset -q I can get *correct* Capslock/Numlock status. Using xev I can see events of Capslock key being pressed and released. It looks like no problem in X window level, but the status does not pass to sddm/plasma correctly. Any idea or suggestion for finding or fixing the problem? Regards, Franklin No suggestion, but I can confirm this behaviour. Numlock problems had already been reported https://lists.debian.org/debian-kde/2019/09/msg00033.html -- Saluti, Luca Pedrielli
Re: Debian/Bullseye plasma screen doesn't lock
Il 30/10/19 12:53, Gary Dale ha scritto: On 2019-10-25 10:35 a.m., Shai Berger wrote: On Fri, 25 Oct 2019 08:29:15 -0400 Gary Dale wrote: Since mid-August, my screen doesn't lock automatically after 10 minutes Any suggestions on how to fix this? I think this may have to do with the display manager. I've been happily using lightm with no issues, because sddm was giving me issues (so long ago that I don't even remember what they were). If you're on a different display manager, maybe consider switching. Unfortunately that didn't work. I tried GDM3 and got the same issue. I have these rows in .xsession-errors when ksmserver starts screenlock: - lock called Lock window Id: - and you? is $HOME/.config/kscreenlockerrc present and without errors? - Saluti, Luca Pedrielli
Re: Transition of Qt to 5.12.5
Downloaded latest plasma-workspace 4:5.14.5.1-4 and it works. Thanks!! Il 24/10/19 07:32, Matthieu Gallien ha scritto: On Wednesday, October 23, 2019 9:05:11 PM CEST Lisandro Damián Nicanor Pérez Meyer wrote: Hi! Hello El mié., 23 oct. 2019 16:01, luca.pedrielli escribió: Thanks for your workI'm still not very familiar with debian tools Best, Luca. I have just uploaded plasma-workspace, it should fix the crash Thanks a lot for the very quick fix. Thanks to all people involved in solving this. Best regards -- Saluti, Luca Pedrielli
Re: Transition of Qt to 5.12.5
Thanks for your workI'm still not very familiar with debian tools Best, Luca. Il 23/10/19 20:37, Martin Steigerwald ha scritto: Dear Luca. Martin Steigerwald - 23.10.19, 18:51:19 CEST: luca.pedrielli - 23.10.19, 11:45:46 CEST: plasmashell crashes with notification :( I can reproduce it everytime with: $ kdialog --passivepopup 'text' 5 Thank you for report. I can reproduce it. So while apt dist-upgrade worked smoothly so far, you may like to wait with an upgrade until this is fixed or a generic work-around if found. plasma-workspace: plasmashell with Qt 5.12.5 crashes on any notification https://bugs.debian.org/943344 […] Of course next time, Luca, feel free to report a bug yourself. I just reported the issue straight away on bug tracker and pinged other Debian/ Kubuntu Qt/KDE team members on IRC channel so it can quickly be acted upon. A fix is being tested. If it works it may be uploaded soon. Thank you again for your contribution. Best,
