[kscreenlocker] [Bug 485520] Redundant unlock button appears after password when resuming from suspend
https://bugs.kde.org/show_bug.cgi?id=485520 Francesco Zaggia changed: What|Removed |Added Keywords||regression, reproducible -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456639] "Unlock" button on lockscreen after entering correct password
https://bugs.kde.org/show_bug.cgi?id=456639 Francesco Zaggia changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=485520 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485520] Redundant unlock button appears after password when resuming from suspend
https://bugs.kde.org/show_bug.cgi?id=485520 Francesco Zaggia changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=456639 CC||francesco...@gmail.com Summary|Remove unlock button that |Redundant unlock button |appears after typing|appears after password when |password and pressing enter |resuming from suspend |only after resuming from| |suspend | --- Comment #3 from Francesco Zaggia --- Happens to me too, logging in works, but sometimes it displays this unnecessary unlock button after typing the password and confirming. This only happens when resuming from suspend, it doesn't happen if locking the screen without suspending (with Meta+L for example). The system needs to stay suspended for more than 10 seconds, otherwise the unlock button is not shown after entering the correct password. Also it doesn't seems to be related to the say you confirm the password (with Enter key or with the button on the screen), just to how much time it passes. S/W: OS: Arch Linux KDE Plasma ver: 6.0.4 KDE Frameworks: 6.1.0 QT Version: 6.7.0 Kernel Version: 6.8.7-arch1-1 (64 bit) Graphics Platform: Wayland H/W Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor RAM Memory: 32 GB Graphics: AMD Radeon RX 6600 Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482161] New: Significant lag when navigating files and folders with the Orca screen reader
https://bugs.kde.org/show_bug.cgi?id=482161 Bug ID: 482161 Summary: Significant lag when navigating files and folders with the Orca screen reader Classification: Applications Product: dolphin Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: francescotissera1...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- When trying to navigate files and folders in any directory with the Orca screen reader turned on, there is a consistent lag (a second or more) that impedes quick and efficient navigation. STEPS TO REPRODUCE 1. Turn the screen reader on. 2. Open Dolphin. 3. Try to navigate files and folders with the left and right arrows OBSERVED RESULT There is a consistent lag that does not allow a smooth navigation. EXPECTED RESULT This lag should not be present at all. Operating System: Arch Linux KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.6-arch1-2 (64-bit) Graphics Platform: X11, although this happens on Wayland as well. Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82FN System Version: Yoga 6 13ARE05 ADDITIONAL INFORMATION This is some other information that suggests that this might be a problem either related to Dolphin or QT: "Exception in get_child_count: atspi_error: The process appears to be hung.". -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 452763] CPU temperature not working for AMD sensor
https://bugs.kde.org/show_bug.cgi?id=452763 Francesco changed: What|Removed |Added Version|5.27.10 |5.27.5 CC||muzi...@gmail.com --- Comment #22 from Francesco --- I've configured sensors on plasma-systemmonitor before upgrading Debian from 11 (plasma-systemmonitor 5.20.0) to 12 (plasma-systemmonitor 5.27.5) and with the previous version k10temp was listed and plotted without errors. After the ugrade is disappear. I can continue select and using all other sensors (see below) but not k10temp atk0110-acpi-0 Adapter: ACPI interface Vcore Voltage:1.21 V (min = +0.80 V, max = +1.60 V) +3.3V Voltage:3.31 V (min = +2.97 V, max = +3.63 V) +5V Voltage: 5.00 V (min = +4.50 V, max = +5.50 V) +12V Voltage:12.02 V (min = +10.20 V, max = +13.80 V) CPU Fan Speed: 4017 RPM (min = 600 RPM, max = 7200 RPM) Chassis Fan Speed: 0 RPM (min = 600 RPM, max = 7200 RPM) Chassis2 Fan Speed:0 RPM (min = 600 RPM, max = 7200 RPM) Power Fan Speed: 0 RPM (min = 600 RPM, max = 7200 RPM) CPU Temperature: +45.0°C (high = +60.0°C, crit = +95.0°C) MB Temperature: +36.0°C (high = +45.0°C, crit = +75.0°C) k10temp-pci-00c3 Adapter: PCI adapter temp1:+36.8°C (high = +70.0°C) (crit = +90.0°C, hyst = +85.0°C) drivetemp-scsi-3-0 Adapter: SCSI adapter temp1:+37.0°C (low = +0.0°C, high = +60.0°C) (crit low = -41.0°C, crit = +85.0°C) (lowest = +22.0°C, highest = +39.0°C) -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 447946] Kaffeine crashes when changing channels. Additional kioslave5 locks when kaffeine run with --lastchannel parameter.
https://bugs.kde.org/show_bug.cgi?id=447946 Francesco changed: What|Removed |Added CC||muzi...@gmail.com --- Comment #1 from Francesco --- I can confirm, this bug happens to me after upgrading Debian from 11 to 12. Kaffeine has the same version in both releases (2.0.18) When I start kaffeine with option --lastchannel or --tv N I can see two pids using the default dvb frontend (fuser /dev/dvb/adapter0/frontend0) kaffeine and, i think, baloo (/lib/x86_64-linux-gnu/libexec/kf5/kioslave5 /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/tags.so tags ...) After some times, when the KIO process has gone I can switch channel, but only if I haven't trying to switch before kioslave5 process started also without preselecting a tv/dvb option, but if kaffeine starts without --lastchannel/--tv it is able to open dvb device and switch channel because kioslave5 do not access to the device -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479318] Panels in systemsettings are unusable
https://bugs.kde.org/show_bug.cgi?id=479318 Francesco changed: What|Removed |Added Version|unspecified |5.91.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479318] New: Panels in systemsettings are unusable
https://bugs.kde.org/show_bug.cgi?id=479318 Bug ID: 479318 Summary: Panels in systemsettings are unusable Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: chiccocar...@gmail.com Target Milestone: --- Created attachment 164637 --> https://bugs.kde.org/attachment.cgi?id=164637=edit The panel that is not working SUMMARY The majority of the panels in system settings are unusable because of a qml error STEPS TO REPRODUCE 1. Update to the latest beta available on the arch repos 2. Open systemsettings 3. OBSERVED RESULT The majority of the panels in systemsettings are unusable because of a qml error This is what is shown in the display settings panel instead of the panel qrc:/kcm/kcm_kscreen/main.qml:16 Type KCM.SimpleKCM unavailable qrc:/qt/qml/org/kde/kcmutils/SimpleKCM.qml:33 Type Kirigami.ScrollablePage unavailable file:///usr/lib/qt6/qml/org/kde/kirigami/ScrollablePage.qml:68 Type Kirigami.Page unavailable file:///usr/lib/qt6/qml/org/kde/kirigami/Page.qml:237 Type Kirigami.PageRow unavailable file:///usr/lib/qt6/qml/org/kde/kirigami/PageRow.qml:180 Type OverlayDrawer unavailable file:///usr/lib/qt6/qml/org/kde/kirigami/OverlayDrawer.qml:22 Type KT.OverlayDrawer unavailable file:///usr/lib/qt6/qml/org/kde/kirigami/templates/OverlayDrawer.qml:120 Cannot assign object of type "KTP.IconPropertiesGroup" to property of type "IconPropertiesGroup_QMLTYPE_54*" as the former is neither the same as the latter nor a sub-class of it. An example of a panel that works is disks and cameras EXPECTED RESULT SOFTWARE/OS VERSIONS Linux: Arch Linux Latest (available in About System) KDE Plasma Version: Plasma 5.91.0 KDE Frameworks Version: Can't get Qt Version: Can't get ADDITIONAL INFORMATION The informations are missing because the about system panel in system setting isn't working and the plasma version is from neofetch. The version is what is the latest in the kde-unstable arch repo Running nvidia vulkan dev drivers on wayland (issue is the same on x11) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478071] Plasmashell crashes after plugging in a second monitor
https://bugs.kde.org/show_bug.cgi?id=478071 Francesco changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|BACKTRACE |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478071] Plasmashell crashes after plugging in a second monitor
https://bugs.kde.org/show_bug.cgi?id=478071 --- Comment #3 from Francesco --- Application: plasmashell (plasmashell), signal: Segmentation fault PID: 2405 (plasmashell) UID: 1000 (chicco) GID: 1000 (chicco) Signal: 11 (SEGV) Timestamp: Wed 2023-12-06 16:26:19 CET (2s 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 (chicco) Boot ID: e727f1ca82734840b56461623af09ec2 Machine ID: ee64461af8fe4c0f9ab0af91b5faaccc Hostname: ArchChicco Storage: /var/lib/systemd/coredump/core.plasmashell.1000.e727f1ca82734840b56461623af09ec2.2405.170187637900.zst (present) Size on Disk: 24.2M Message: Process 2405 (plasmashell) of user 1000 dumped core. Stack trace of thread 2405: #0 0x7fceb64b19d8 pthread_sigmask (libc.so.6 + 0x939d8) #1 0x7fceb645c90d sigprocmask (libc.so.6 + 0x3e90d) #2 0x7fceb93fb4eb _ZN6KCrash15setCrashHandlerEPFviE (libKF6Crash.so.6 + 0x54eb) #3 0x7fceb93fd958 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x7958) #4 0x7fceb645c710 n/a (libc.so.6 + 0x3e710) #5 0x7fceb97569f1 _ZNK11PlasmaQuick15ContainmentView11containmentEv (libPlasmaQuick.so.6 + 0x469f1) #6 0x55b8e5d8e1a7 n/a (plasmashell + 0x7a1a7) #7 0x7fceb6bb9ec9 n/a (libQt6Core.so.6 + 0x1b9ec9) #8 0x7fceb7200476 _ZN14QWindowPrivate10setVisibleEb (libQt6Gui.so.6 + 0x200476) #9 0x7fceb720496a _ZN14QWindowPrivate7destroyEv (libQt6Gui.so.6 + 0x20496a) #10 0x7fceb71fec52 _ZN7QWindowD2Ev (libQt6Gui.so.6 + 0x1fec52) #11 0x55b8e5d63f3d n/a (plasmashell + 0x4ff3d) #12 0x7fceb6ba5258 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x1a5258) #13 0x7fceb8b7319b _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x17319b) #14 0x7fceb6b62a78 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x162a78) #15 0x7fceb6b62dfb _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x162dfb) #16 0x7fceb6d9ead4 n/a (libQt6Core.so.6 + 0x39ead4) #17 0x7fceb57fef69 n/a (libglib-2.0.so.0 + 0x59f69) #18 0x7fceb585d327 n/a (libglib-2.0.so.0 + 0xb8327) #19 0x7fceb57fd162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162) #20 0x7fceb6d9d074 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x39d074) #21 0x7fceb6b6cf5e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x16cf5e) #22 0x7fceb6b65518 _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x165518) #23 0x55b8e5d42434 n/a (plasmashell + 0x2e434) #24 0x7fceb6445cd0 n/a (libc.so.6 + 0x27cd0) #25 0x7fceb6445d8a __libc_start_main (libc.so.6 + 0x27d8a) #26 0x55b8e5d42bf5 n/a (plasmashell + 0x2ebf5) Stack trace of thread 2412: #0 0x7fceb6520f6f __poll (libc.so.6 + 0x102f6f) #1 0x7fceb585d276 n/a (libglib-2.0.so.0 + 0xb8276) #2 0x7fceb57fd162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162) #3 0x7fceb6d9d09a _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x39d09a) #4 0x7fceb6b6cf5e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x16cf5e) #5 0x7fceb6c4a13f _ZN7QThread4execEv (libQt6Core.so.6 + 0x24a13f) #6 0x7fceb79cd95f n/a (libQt6DBus.so.6 + 0x2f95f) #7 0x7fceb6cc9e63 n/a (libQt6Core.so.6 + 0x2c9e63) #8 0x7fceb64aa9eb n/a (libc.so.6 + 0x8c9eb) #9 0x7fceb652e7cc n/a (libc.so.6 + 0x1107cc) Stack trace of thread 2462: #0 0x7fceb6520f6f __poll (libc.so.6 + 0x102f6f) #1 0x7fceb0f6d936 n/a (libnvidia-egl-wayland.so.1 + 0x5936) #2 0x7fceb64aa9eb n/a (libc.so.6 + 0x8c9eb) #3 0x7fceb652e7cc n/a (libc.so.6 + 0x1107cc) Stack trace of thread 2465: #0 0x7fceb64af794 n/a (libc.so.6 + 0x91794) #1 0x7fcea9ff25fa n/a (libnvidia-eglcore.so.545.29.06 + 0x9f25fa) #2 0x7fcea9ff2852 n
[plasmashell] [Bug 478071] Plasmashell crashes after plugging in a second monitor
https://bugs.kde.org/show_bug.cgi?id=478071 --- Comment #2 from Francesco --- Here is the traceback i got from crashed process wiewer PID: 15938 (plasmashell) UID: 1000 (chicco) GID: 1000 (chicco) Signal: 11 (SEGV) Timestamp: Sun 2023-12-03 20:39:46 CET (2 days 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 (chicco) Boot ID: aced5ed11d234fa690a4e795e10fda93 Machine ID: ee64461af8fe4c0f9ab0af91b5faaccc Hostname: ArchChicco Storage: /var/lib/systemd/coredump/core.plasmashell.1000.aced5ed11d234fa690a4e795e10fda93.15938.170163238600.zst (present) Size on Disk: 41.0M Message: Process 15938 (plasmashell) of user 1000 dumped core. Stack trace of thread 15938: #0 0x7f72130b19d8 pthread_sigmask (libc.so.6 + 0x939d8) #1 0x7f721305c90d sigprocmask (libc.so.6 + 0x3e90d) #2 0x7f7215ebe4eb _ZN6KCrash15setCrashHandlerEPFviE (libKF6Crash.so.6 + 0x54eb) #3 0x7f7215ec0958 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x7958) #4 0x7f721305c710 n/a (libc.so.6 + 0x3e710) #5 0x7f7213977d40 n/a (libQt6Core.so.6 + 0x377d40) #6 0x7f72137b9ec9 n/a (libQt6Core.so.6 + 0x1b9ec9) #7 0x7f7213965eeb n/a (libQt6Core.so.6 + 0x365eeb) #8 0x7f72137a5447 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x1a5447) #9 0x7f721557319b _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x17319b) #10 0x7f7213762a78 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x162a78) #11 0x7f7213762dfb _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x162dfb) #12 0x7f721399ead4 n/a (libQt6Core.so.6 + 0x39ead4) #13 0x7f72122c4f69 n/a (libglib-2.0.so.0 + 0x59f69) #14 0x7f7212323327 n/a (libglib-2.0.so.0 + 0xb8327) #15 0x7f72122c3162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162) #16 0x7f721399d074 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x39d074) #17 0x7f721376cf5e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x16cf5e) #18 0x7f7213765518 _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x165518) #19 0x563ae4df8434 n/a (plasmashell + 0x2e434) #20 0x7f7213045cd0 n/a (libc.so.6 + 0x27cd0) #21 0x7f7213045d8a __libc_start_main (libc.so.6 + 0x27d8a) #22 0x563ae4df8bf5 n/a (plasmashell + 0x2ebf5) Stack trace of thread 15945: #0 0x7f72130a74ae n/a (libc.so.6 + 0x894ae) #1 0x7f72130a9d40 pthread_cond_wait (libc.so.6 + 0x8bd40) #2 0x7f72138cd000 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x2cd000) #3 0x7f721537ea98 n/a (libQt6WaylandClient.so.6 + 0x70a98) #4 0x7f72138c9e63 n/a (libQt6Core.so.6 + 0x2c9e63) #5 0x7f72130aa9eb n/a (libc.so.6 + 0x8c9eb) #6 0x7f721312e7cc n/a (libc.so.6 + 0x1107cc) Stack trace of thread 15944: #0 0x7f721231e258 g_mutex_unlock (libglib-2.0.so.0 + 0xb3258) #1 0x7f72122c5412 n/a (libglib-2.0.so.0 + 0x5a412) #2 0x7f7212323109 n/a (libglib-2.0.so.0 + 0xb8109) #3 0x7f72122c3162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162) #4 0x7f721399d09a _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x39d09a) #5 0x7f721376cf5e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x16cf5e) #6 0x7f721384a13f _ZN7QThread4execEv (libQt6Core.so.6 + 0x24a13f) #7 0x7f72144b295f n/a (libQt6DBus.so.6 + 0x2f95f) #8 0x7f72138c9e63 n/a (libQt6Core.so.6 + 0x2c9e63) #9 0x7f72130aa9eb n/a (libc.so.6 + 0x8c9eb) #10 0x7f721312e7cc n/a (libc.so.6 + 0x1107cc) Stack trace of thread 15984: #0 0x7f72130a7767 n/a (libc.so.6 + 0x89767) #1 0x7f72130af7a3 n/a (libc.so.6 + 0x917a3) #2 0x7f7215f4d07d wl_display_prepare_read_queue (libwayland-client.so.0 + 0x807d
[plasmashell] [Bug 478071] New: Plasmashell crashes after plugging in a second monitor
https://bugs.kde.org/show_bug.cgi?id=478071 Bug ID: 478071 Summary: Plasmashell crashes after plugging in a second monitor Classification: Plasma Product: plasmashell Version: 5.90.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: chiccocar...@gmail.com Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Plug in or unplug your secondary monitor 2. 3. OBSERVED RESULT The plasmashell crashes and relaunches and some window freezes and needs to be restarted EXPECTED RESULT The second montor should be recognized without plasmashell crashing or stopping other windows from opening SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION Running a wayland session with an nvidia gpu with proprietary drivers -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 477622] New: can't find kmail emails
https://bugs.kde.org/show_bug.cgi?id=477622 Bug ID: 477622 Summary: can't find kmail emails Classification: Plasma Product: krunner Version: 5.27.80 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: frances...@gmail.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY *** Email messages from kmail don't show up in krunner. Searching for a email subject present in the inbox folder (or any other folder) doesn't find the email, but does find the akonadi file containing that email *** STEPS TO REPRODUCE 1. Open krunner 2. type some text of a mail OBSERVED RESULT no mail is found, the corresponding akonadi text file is EXPECTED RESULT email should be found SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20231124 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.2-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i5-1235U Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: HP Product Name: HP EliteBook 860 16 inch G9 Notebook PC -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 473483] KPipeWire-based Task Manager window previews are blank on Wayland with Nouveau drivers
https://bugs.kde.org/show_bug.cgi?id=473483 --- Comment #16 from Francesco --- Latest opensuse tumbleweed update (or the subsequent restart of the plasma session) fixed it for me -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 473483] KPipeWire-based Task Manager window previews are blank on Wayland with Nouveau drivers
https://bugs.kde.org/show_bug.cgi?id=473483 Francesco changed: What|Removed |Added CC||frances...@gmail.com --- Comment #15 from Francesco --- I'm seeing the same behaviour (no window preview, just application icon on icon only task manager thumbnail) but slightly different error message: ott 26 15:46:42 localhost.localdomain pipewire[2454]: mod.protocol-native: 0x55f5777d8790: connection_data: client 0x55f57799d450 error -71 (Errore di protocollo) ott 26 15:46:42 localhost.localdomain kwin_wayland[6625]: kwin_screencast: PipeWire remote error: connection error ott 26 15:46:42 localhost.localdomain plasmashell[6807]: kpipewire_logging: Stream error: target not found ott 26 15:46:42 localhost.localdomain plasmashell[6807]: kpipewire_logging: PipeWire remote error: -2 target not found here's my system specs: Operating System: openSUSE Tumbleweed 20231023 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.8-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i5-1235U Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: HP Product Name: HP EliteBook 860 16 inch G9 Notebook PC -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474524] New: Accessibility: 2 to 3 seconds lag when navigating through folders and files with the Orca screen reader.
https://bugs.kde.org/show_bug.cgi?id=474524 Bug ID: 474524 Summary: Accessibility: 2 to 3 seconds lag when navigating through folders and files with the Orca screen reader. Classification: Applications Product: dolphin Version: 23.08.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: francescotissera1...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When navigating the filesystem with the Orca screen reader enabled, Dolphin has a two to three seconds lag when going from one item to another. STEPS TO REPRODUCE 1. Enable Orca. 2. Open Dolphin to any directory with subdirs and files in it. 3. Navigate with left and right arrows or first letter navigation. OBSERVED RESULT Orca takes at least two seconds to announce the next item from when the arrow is pressed or the letter in first letter navigation is pressed. EXPECTED RESULT Dolphin and Orca should work together and be responsive announcing items a few milliseconds after an arrow or a letter is pressed. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) Operating System: Arch Linux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Kernel Version: 6.5.3-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82FN System Version: Yoga 6 13ARE05 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472643] Accessibility: the Orca screenreader does not announce window names when switching through them. in Wayland session
https://bugs.kde.org/show_bug.cgi?id=472643 --- Comment #11 from Francesco Tissera --- When pressing alt+tab to switch through windows, no matter what the window is, Orca doesn't announce it. On X11 this doesn't seem to happen however. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472643] Accessibility: the Orca screenreader does not announce window names when switching through them. in Wayland session
https://bugs.kde.org/show_bug.cgi?id=472643 --- Comment #2 from Francesco Tissera --- Yeah, Orca works on Wayland, Gnome is a good example of that, plus KDE as well. The only thing, as far as I noticed anyway, that doesn't work is the windows not being announced when switching through them. -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 472643] Accessibility: the Orca screenreader does not announce window names when switching through them. in Wayland session
https://bugs.kde.org/show_bug.cgi?id=472643 Francesco Tissera changed: What|Removed |Added Summary|Accessibility: the Orca |Accessibility: the Orca |screenreader does not |screenreader does not |announce window names when |announce window names when |switching through them. |switching through them. in ||Wayland session -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 472643] New: Accessibility: the Orca screenreader does not announce window names when switching through them.
https://bugs.kde.org/show_bug.cgi?id=472643 Bug ID: 472643 Summary: Accessibility: the Orca screenreader does not announce window names when switching through them. Classification: Plasma Product: kwayland-integration Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: francescotissera1...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Tested this on Arch Linux, with plasma 5.27-6 and the last commit of Orca's master branch. When pressing alt+tab to switch around windows, Orca does not announce window names in Plasma's wayland session. This bug does not accour on the X11 session so a lot of users work around the bug by using said session. STEPS TO REPRODUCE 1. Log in to the Wayland session. 2. Turn on the screen reader and open some random applications. 3. navigate around the applications with alt+tab. OBSERVED RESULT Orca does not announce any window name/title when pressing alt+tab to navigate through them. EXPECTED RESULT The screenreader should speak window title/names. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) Operating System: Arch Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.4.6-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82FN System Version: Yoga 6 13ARE05 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 334213] Stuck "Mail filter agent" progressbar
https://bugs.kde.org/show_bug.cgi?id=334213 francesco changed: What|Removed |Added CC||france...@href.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 452074] Deleting files to trash with kio very slow | trash-cli and rm work correctly
https://bugs.kde.org/show_bug.cgi?id=452074 Francesco changed: What|Removed |Added CC||fra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 395023] $topdir/.Trash not created or used on btrfs sub-volumes
https://bugs.kde.org/show_bug.cgi?id=395023 Francesco changed: What|Removed |Added CC||fra...@gmail.com --- Comment #3 from Francesco --- I can confirm the same exact issue, verified today on this two systems: (my main laptop) Operating System: Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-3630QM CPU @ 2.40GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4000 (testing virtual machine) Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-41-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-3630QM CPU @ 2.40GHz Memory: 3.8 GiB of RAM Graphics Processor: SVGA3D; build: RELEASE; LLVM; I verified it either on external btrfs volume connected via usb or an image file with btrfs on it. When I delete a file this is moved to ~/.local/share/Trash instead to .Trash-1000 on the original btrfs volume. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453348] Global menu text color do not follow plasma style, but follows colors in appearance settings.
https://bugs.kde.org/show_bug.cgi?id=453348 Francesco Zaggia changed: What|Removed |Added CC||francesco...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385814] Some icons removed from the favorites list are back when plasma session is restarted
https://bugs.kde.org/show_bug.cgi?id=385814 Francesco Turco changed: What|Removed |Added CC|ftu...@posteo.net | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449470] New: Mouse cursor fails to change shape properly on XWayland apps
https://bugs.kde.org/show_bug.cgi?id=449470 Bug ID: 449470 Summary: Mouse cursor fails to change shape properly on XWayland apps Product: kwin Version: 5.23.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: linux4ev...@gmail.com Target Milestone: --- SUMMARY With KWin 5.23.90-1 and XWayland 21.1.4-1 the cursor doesn't change properly on XWayland apps. STEPS TO REPRODUCE 1. Open an XWayland app (e.g. Google Chrome) 2. Notice that the mouse cursor doesn't change shape on e.g. links SOFTWARE/OS VERSIONS Linux 5.16.4-zen1-1-zen KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 AMD RENOIR APU with Mesa 21.3.5 ADDITIONAL INFORMATION With the last stable version of KWin / Plasma / Frameworks the cursor works properly. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 321374] Multiple accounts
https://bugs.kde.org/show_bug.cgi?id=321374 --- Comment #10 from Francesco Florian --- Not that this concerns me anymore, since I switched to another client, but since when is this specific to Archlinux? -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 321374] Multiple accounts
https://bugs.kde.org/show_bug.cgi?id=321374 Francesco Florian changed: What|Removed |Added CC|flor...@poisson.phc.dm.unip | |i.it| -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405847] SFTP transfer corrupts all files
https://bugs.kde.org/show_bug.cgi?id=405847 --- Comment #70 from Francesco --- I must partially retract my enthusiasm. With the direct_io option seems not completely usable. It works if copy a file from sshfs to local with dolphin. Doesn't work if I open a PDF with okular on the remote folder or run a pdf2ps command on it. Very strange, md5sum on the remote file generates a correct hash and a cat from remote to a local fetching a correct file Also with direct_io the tool vbindiff used to compare the remote file and a local copy show a strange behaviour: when scrolling the content the remote file is stop and doesn't leave firsts 32k bytes -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405847] SFTP transfer corrupts all files
https://bugs.kde.org/show_bug.cgi?id=405847 --- Comment #68 from Francesco --- not a great solution, but adding '-o direct_io' to the sshfs options solve the corruption issue you can see the sshfs options used by kdeconnect with ps aux | grep sshfs -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405847] SFTP transfer corrupts all files
https://bugs.kde.org/show_bug.cgi?id=405847
Francesco changed:
What|Removed |Added
CC||muzi...@gmail.com
--- Comment #67 from Francesco ---
I can confirm this bug, first 32k bytes seems be repeated after 32767
position, then in some case seems to be a simple shift of 32k in other cases it
starts in the same mode but then is much like a random corruption.
My configuration is:
PC:
Debian 10.9
kdeconnect 1.3.3-2
sshfs 2.10+repack-2
Android Device:
Android 8.1.0
kdeconnect 1.16.0
On another device (an ebook reader with Android 4.0.4) the same kdeconnect app
works, I cannot reproduce this bug.
If the file is sent from android to PC as a shared content no corruption is
happen
I think that the kdeconnect application on Linux side could be only a frontend
for sshfs, I can connect to my device (The smartphone with Android 8) with
filezilla and I can't reproduce the problem, file are fetched without
corruption
directories shared are mounted usually at /run/user/1000/{device id}
transfer using dolphin or cp produce the same result
if I mount the directory manually with sshfs the issue still happens
tips to trying a connection with filezilla:
- the connection between sshfs and the kdeconnect app happens with a
ceretificate authentication, the username is "kdeconnect"
- the private key is saved here ~/.config/kdeconnect/privateKey.pem
- for using this key for authentiation with filezilla you need to convert this
in an RSA key with
openssl rsa -in privateKey.pem -out privateRSAKey.pem
and then in a ppk key with
puttygen privateRSAKey.pem -o key.ppk
- the port used by kdeconnect app is 1739
--
You are receiving this mail because:
You are watching all bug changes.
[karbon] [Bug 290441] karbon crashes after simple drawing
https://bugs.kde.org/show_bug.cgi?id=290441 Francesco Riosa changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 from Francesco Riosa --- cannot reproduce -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 311537] akregator crash in kjs
https://bugs.kde.org/show_bug.cgi?id=311537 Francesco Riosa changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Francesco Riosa --- cannot reproduce -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426962] New: Dolphin crashes when navigating sftp folders
https://bugs.kde.org/show_bug.cgi?id=426962 Bug ID: 426962 Summary: Dolphin crashes when navigating sftp folders Product: dolphin Version: 20.08.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: mou...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.08.1) Qt Version: 5.15.0 Frameworks Version: 5.74.0 Operating System: Linux 5.4.0-47-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: I had a sftp folder open for sometimes, in an inactive window. When I interacted again with the same window, trying to navigate to a parent folder, on the same server, through the breadcrumb bar, Dolphin crashed. It happend me 3 times in the last week, but I'm not able to replicate it consistently. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #5 0x7f54069a7859 in __GI_abort () at abort.c:79 #6 0x7f5406a123ee in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5406b3c285 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 #7 0x7f5406a1a47c in malloc_printerr (str=str@entry=0x7f5406b3e628 "double free or corruption (fasttop)") at malloc.c:5347 #8 0x7f5406a1bde5 in _int_free (av=0x7f5406b6db80 , p=0x55e8cdcbecf0, have_lock=0) at malloc.c:4266 #9 0x7f54068b469f in KFileItemModel::slotClear() () from /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5 #10 0x7f540691d977 in DolphinView::setUrl(QUrl const&) () from /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5 #11 0x7f5406bdcd68 in ?? () from /usr/lib/x86_64-linux-gnu/libkdeinit5_dolphin.so #12 0x7f54047ea5ae in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f54067fec99 in KUrlNavigator::urlChanged(QUrl const&) () from /usr/lib/x86_64-linux-gnu/libKF5KIOFileWidgets.so.5 #14 0x7f5406802d64 in KUrlNavigator::setLocationUrl(QUrl const&) () from /usr/lib/x86_64-linux-gnu/libKF5KIOFileWidgets.so.5 #15 0x7f54047ea5e0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f54067f67d2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5KIOFileWidgets.so.5 #17 0x7f540540bdb6 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f54053c8cc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f54053d1ec3 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f54047b36aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f54053d0fd7 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f5405426ffd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f540542a4dc in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f54053c8cc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f54053d1c70 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f54047b36aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f5404cbef78 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #28 0x7f5404cc05b5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #29 0x7f5404c982cb in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #30 0x7f53ff8b199e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #31 0x7f540259dfbd in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x7f540259e240 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x7f540259e2e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7f540480de92 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x7f54047b21bb in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x7f54047ba354 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #37 0x7f5406bc324f in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_dolphin.so #38 0x7f54069a90b3 in
[kbreakout] [Bug 425485] New: Lost focus
https://bugs.kde.org/show_bug.cgi?id=425485 Bug ID: 425485 Summary: Lost focus Product: kbreakout Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: viranch.me...@gmail.com Reporter: francesco.policas...@fastwebnet.it CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY I use Ubuntu 18.04 LTS. When playing kbreakout sometimes the mouse becomes unresponsive, as its focus exits the game window. It would be nice if the mouse could not exit the window unless after pressing some key sequence STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 421705] Make kleopatra be able to use opaque signatures for signing and verifying operations
https://bugs.kde.org/show_bug.cgi?id=421705 Francesco Bonanno changed: What|Removed |Added CC||mibo...@fsfe.org -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 421705] New: Make kleopatra be able to use opaque signatures for signing and verifying operations
https://bugs.kde.org/show_bug.cgi?id=421705 Bug ID: 421705 Summary: Make kleopatra be able to use opaque signatures for signing and verifying operations Product: kleopatra Version: 3.1.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: aheine...@gnupg.org Reporter: mibo...@fsfe.org CC: kdepim-b...@kde.org, m...@kde.org Target Milestone: --- SUMMARY (Even if gpgsm has not yet the support to CAdES compliant signatures, due to the missing but expected function in libksba for signing attributes, and so on) gpgsm can make an opaque signature. So if you do as an example gpgsm gpgsm -s test.txt -o test.txt.p7m, you obtain a signed p7m cryptographic envelope with the file inside. As specified in the source code and in the popup message if you try to do this with kleopatra, it is uncommon, but in some jurisdiciton, like Italy, for the AdES signatures of CMS type (so the CAdES ones), the regulated format is the opaque signature in p7m, not the detached one in p7s. https://www.gazzettaufficiale.it/atto/serie_generale/caricaArticolo?art.progressivo=0=21=1=09A14307=2009-12-03=7=10=1=0 the official gazette of Italy about it. So it will be REALLY nice, to have the possibility to have a button in the sign/encrypt window to choose to use the opaque signature, and in the verify/decrypt window to verify it (gpgsm can do it without issues) or autodetect and verify it. STEPS TO REPRODUCE Try to sign a file with Kleopatra, using a x.509 cert and related private key, making an opaque signature enveloped in a p7m or try to verify a opaque signed envelope. OBSERVED RESULT Kleopatra will complain about the choice of trying renaming the file to a dot p7m, and in any case, the output will be a p7s detached signature. Trying to verify an opaque signed envelope, kleopatra will complain about it. EXPECTED RESULT Kleopatra having a button to choose to make an opaque signature and have as output an opaque signed p7m and verifing no complains about it. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION Obviously, sorry guys if part of this or all the issue is solved already in the master of kleopatra. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416501] Compositing prevents laptop to wake up from sleep state
https://bugs.kde.org/show_bug.cgi?id=416501 --- Comment #4 from Francesco Cartier --- (In reply to Roman Gilg from comment #3) > Can you switch VT via Ctrl+Alt+F# key combination and then check if XServer > and/or KWin are running and restart KWin via DISPLAY=:0 kwin_x11? > > Also try it with Wayland session. The PC is completely unresponsive from user input. The screen backlight turns on, the power button LED and the keyboard too, but any kind of input is off. The key combination you suggested doesn't work with any F# key. I've tested Wayland and it works fine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416501] Compositing prevents laptop to wake up from sleep state
https://bugs.kde.org/show_bug.cgi?id=416501 --- Comment #2 from Francesco Cartier --- (In reply to David Edmundson from comment #1) > Does this happen when another compositor is used? I've only tried XFWM and it didn't reproduce the problem. I've also tried to change the OpenGL version used by KWin from 3.1 to 2.0 but the problem persisted. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416501] New: Compositing prevents laptop to wake up from sleep state
https://bugs.kde.org/show_bug.cgi?id=416501 Bug ID: 416501 Summary: Compositing prevents laptop to wake up from sleep state Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: francescocart...@gmail.com Target Milestone: --- SUMMARY As reported on a few forum posts in the Manjaro forum, on AMD Ryzen laptops the compositor prevents the PC to wake up from a suspend state. When suspending the machine with the compositor enabled, waking it up will result in a black screen without any possibility of user input (the PC looks totally frozen and the only way out is shutting it off with power button). A workaround so far is disabling the compositor before suspending the device, either manually or with a systemd service, but even like this it fails from time to time forcing an hard shutdown. STEPS TO REPRODUCE 1. Enable the compositor 2. Suspend the device 3. Wake up the device OBSERVED RESULT Black screen with no possibility of user input. EXPECTED RESULT Wake up the device. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro 18.1.5 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66 Qt Version: 5.14 ADDITIONAL INFORMATION This issue has been around since I moved to KDE in September 2019, and I've found the same issues in older forum posts since end-2018. All my researches had Ryzen CPUs as common specs, I don't know if it might affect Intel devices. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 400120] Feature Request: PDF View Support
https://bugs.kde.org/show_bug.cgi?id=400120 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414211] (Hidpi) Font rendering into text box for searching WiFI connections - Connections Panel
https://bugs.kde.org/show_bug.cgi?id=414211 Francesco Esposito changed: What|Removed |Added Summary|(Hidpi) Font rendering into |(Hidpi) Font rendering into |text box for searching WiFI |text box for searching WiFI |connections - Connection|connections - Connections |Panel |Panel -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 411149] Discover is slow
https://bugs.kde.org/show_bug.cgi?id=411149
--- Comment #2 from Francesco ---
I solved disabling gpu acceleration and now i use gnome software.Sorry for
waiting because i lost my email password
Il giorno martedì 17 settembre 2019, Nate Graham
ha scritto:
> https://bugs.kde.org/show_bug.cgi?id=411149
>
> Nate Graham changed:
>
>What|Removed |Added
>
> Status|REPORTED|NEEDSINFO
> Resolution|--- |WAITINGFORINFO
>
> --- Comment #1 from Nate Graham ---
> The log shows that the problem is actually because your backends are
missing!
>
> org.kde.plasma.libdiscover: Couldn't find the backend: "kns-backend"
among
> ("packagekit-backend", "kns-backend", "snap-backend")
> org.kde.plasma.libdiscover: Couldn't find a category for
"packagekit-backend"
>
> Did you install Discover by hand, or is this the way it comes by default
in the
> Kubuntu release you're using? Are you using the backports repo, or is this
> stock 19.04?
>
> --
> You are receiving this mail because:
> You reported the bug.
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 411149] New: Discover is slow
https://bugs.kde.org/show_bug.cgi?id=411149 Bug ID: 411149 Summary: Discover is slow Product: Discover Version: 5.16.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: francescoferdinand...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 122286 --> https://bugs.kde.org/attachment.cgi?id=122286=edit Discover loads slowly I can't install applications because Discover is very slow to load itself and I can't uninstall applications for this issue. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 386004] no connection with mariadb (Debian Stretch)
https://bugs.kde.org/show_bug.cgi?id=386004 --- Comment #2 from Francesco Talamona --- In your case "@10.0.0.159"... -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 386004] no connection with mariadb (Debian Stretch)
https://bugs.kde.org/show_bug.cgi?id=386004 Francesco Talamona changed: What|Removed |Added CC||cancellettopu...@gmail.com --- Comment #1 from Francesco Talamona --- I discovered that with MariaDb the suggested command is not sufficient. Instead of: GRANT ALL PRIVILEGES ON amarokdb.* TO amarokuser IDENTIFIED BY 'secret'; it should be: GRANT ALL PRIVILEGES ON amarokdb.* TO amarokuser@localhost IDENTIFIED BY 'secret'; -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385814] Some icons removed from the favorites list are back when plasma session is restarted
https://bugs.kde.org/show_bug.cgi?id=385814 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 166223] favorite folders for Akregator
https://bugs.kde.org/show_bug.cgi?id=166223 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 403582] double click to enter/leave fullscreen sometimes crashes gwenview
https://bugs.kde.org/show_bug.cgi?id=403582 Francesco Riosa changed: What|Removed |Added CC||vivo75+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 403582] double click to enter/leave fullscreen sometimes crashes gwenview
https://bugs.kde.org/show_bug.cgi?id=403582 --- Comment #2 from Francesco Riosa --- Created attachment 118987 --> https://bugs.kde.org/attachment.cgi?id=118987=edit New crash information added by DrKonqi gwenview (18.12.3) using Qt 5.12.2 double click on image, better described by bug 403582 opener -- Backtrace (Reduced): #5 0x7f81f8f11266 in QCursor::shape() const () from /usr/lib64/libQt5Gui.so.5 #6 0x7f81f8f3cf18 in QBasicDrag::updateCursor(Qt::DropAction) () from /usr/lib64/libQt5Gui.so.5 #7 0x7f81f3d4030a in QXcbDrag::handle_xdnd_status(xcb_client_message_event_t const*) () from /usr/lib64/libQt5XcbQpa.so.5 #8 0x7f81f3d40918 in QXcbDrag::handle_xdnd_position(QPlatformWindow*, xcb_client_message_event_t const*, QFlags, QFlags) () from /usr/lib64/libQt5XcbQpa.so.5 #9 0x7f81f3d42a23 in QXcbDrag::move(QPoint const&, QFlags, QFlags) () from /usr/lib64/libQt5XcbQpa.so.5 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 344181] konsole 256 color support differs from xterm/rxvt
https://bugs.kde.org/show_bug.cgi?id=344181 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 319386] Feature Request: Allow Syncing with TTRSS (Tiny Tiny RSS) / Liferea functionality
https://bugs.kde.org/show_bug.cgi?id=319386 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 405106] New: closing one tab crash konsole
https://bugs.kde.org/show_bug.cgi?id=405106 Bug ID: 405106 Summary: closing one tab crash konsole Product: konsole Version: 18.12.2 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: vivo75+...@gmail.com Target Milestone: --- Application: konsole (18.12.2) (Compiled from sources) Qt Version: 5.12.1 Frameworks Version: 5.55.0 Operating System: Linux 4.19.26-desk x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: Closing tabs when "sending input" is active can crash konsole -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f75c4abc880 (LWP 571567))] Thread 15 (Thread 0x7f75a77fe700 (LWP 571583)): #0 0x7f75c7ca70ec in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f75c0f19633 in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f75c0f19387 in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f75c7ca03f3 in start_thread () from /lib64/libpthread.so.0 #4 0x7f75ca451f7f in ?? () from /lib64/libc.so.6 #5 0x in ?? () Thread 14 (Thread 0x7f75acff9700 (LWP 571582)): #0 0x7f75c7ca70ec in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f75c0f19633 in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f75c0f19387 in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f75c7ca03f3 in start_thread () from /lib64/libpthread.so.0 #4 0x7f75ca451f7f in ?? () from /lib64/libc.so.6 #5 0x in ?? () Thread 13 (Thread 0x7f75ad7fa700 (LWP 571581)): #0 0x7f75c7ca70ec in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f75c0f19633 in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f75c0f19387 in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f75c7ca03f3 in start_thread () from /lib64/libpthread.so.0 #4 0x7f75ca451f7f in ?? () from /lib64/libc.so.6 #5 0x in ?? () Thread 12 (Thread 0x7f75adffb700 (LWP 571580)): #0 0x7f75c7ca70ec in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f75c0f19633 in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f75c0f19387 in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f75c7ca03f3 in start_thread () from /lib64/libpthread.so.0 #4 0x7f75ca451f7f in ?? () from /lib64/libc.so.6 #5 0x in ?? () Thread 11 (Thread 0x7f75ae7fc700 (LWP 571579)): #0 0x7f75c7ca70ec in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f75c0f19633 in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f75c0f19387 in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f75c7ca03f3 in start_thread () from /lib64/libpthread.so.0 #4 0x7f75ca451f7f in ?? () from /lib64/libc.so.6 #5 0x in ?? () Thread 10 (Thread 0x7f75aeffd700 (LWP 571578)): #0 0x7f75c7ca70ec in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f75c0f19633 in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f75c0f19387 in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f75c7ca03f3 in start_thread () from /lib64/libpthread.so.0 #4 0x7f75ca451f7f in ?? () from /lib64/libc.so.6 #5 0x in ?? () Thread 9 (Thread 0x7f75af7fe700 (LWP 571577)): #0 0x7f75c7ca70ec in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f75c0f19633 in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f75c0f19387 in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f75c7ca03f3 in start_thread () from /lib64/libpthread.so.0 #4 0x7f75ca451f7f in ?? () from /lib64/libc.so.6 #5 0x in ?? () Thread 8 (Thread 0x7f75a700 (LWP 571576)): #0 0x7f75c7ca70ec in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f75c0f19633 in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f75c0f19387 in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f75c7ca03f3 in start_thread () from /lib64/libpthread.so.0 #4 0x7f75ca451f7f in ?? () from /lib64/libc.so.6 #5 0x in ?? () Thread 7 (Thread 0x7f75a7fff700 (LWP 571575)): #0 0x7f75c7ca70ec in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f75c0f19633 in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f75c0f19387 in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f75c7ca03f3 in start_thread () from /lib64/libpthread.so.0 #4 0x7f75ca451f7f in ?? () from /lib64/libc.so.6 #5
[okular] [Bug 208779] Allow user to set the font
https://bugs.kde.org/show_bug.cgi?id=208779 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm --- Comment #2 from Francesco Turco --- Settings > Configure Backends > EPUB > Default Font -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 391625] Okular displays blurry images when opening epub files
https://bugs.kde.org/show_bug.cgi?id=391625 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404558] Very slow SDDM with Breeze theme when using plasma-workspace-5.15.0
https://bugs.kde.org/show_bug.cgi?id=404558 Francesco Turco changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #11 from Francesco Turco --- Today I installed the new motherboard (Intel DQ45CB). It now supports OpenGL 2.1. The problem with lock screen and the login screen is gone. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393545] Integrate Media Controls with Plasma
https://bugs.kde.org/show_bug.cgi?id=393545 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404558] Very slow SDDM with Breeze theme when using plasma-workspace-5.15.0
https://bugs.kde.org/show_bug.cgi?id=404558 --- Comment #10 from Francesco Turco --- I ordered a used Intel motherboard with a more up-to-date Q45 chipset supporting OpenGL 2.0. In this way I will also be able to switch from xf86-video-intel to the modesetting driver. I really hope this will fix my problems. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404558] Very slow SDDM with Breeze theme when using plasma-workspace-5.15.0
https://bugs.kde.org/show_bug.cgi?id=404558 --- Comment #8 from Francesco Turco --- I asked for help on the Gentoo Forums: https://forums.gentoo.org/viewtopic-p-8311486.html -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404558] Very slow SDDM with Breeze theme when using plasma-workspace-5.15.0
https://bugs.kde.org/show_bug.cgi?id=404558 --- Comment #7 from Francesco Turco --- I'm not sure if related, but I also have another similar problem. Certain online videos (but not all) on Falkon are played in a terribly slow way on my system. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404558] Very slow SDDM with Breeze theme when using plasma-workspace-5.15.0
https://bugs.kde.org/show_bug.cgi?id=404558 --- Comment #6 from Francesco Turco --- I just did some testing. Unfortunately even if I set "Rendering Backend" to "Open GL" both the login screen and the lock screen are still very slow. I guess there's something wrong with hardware acceleration on my system... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404558] Very slow SDDM with Breeze theme when using plasma-workspace-5.15.0
https://bugs.kde.org/show_bug.cgi?id=404558 --- Comment #4 from Francesco Turco --- Oh, wait. I just found the "Plasma Renderer" module. Option "Rendering Backend" is currently set to "Software". The other possible option is "Open GL". I'll do some testing tomorrow. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404558] Very slow SDDM with Breeze theme when using plasma-workspace-5.15.0
https://bugs.kde.org/show_bug.cgi?id=404558 --- Comment #3 from Francesco Turco --- Also: # glxinfo | grep "direct rendering" direct rendering: Yes -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404558] Very slow SDDM with Breeze theme when using plasma-workspace-5.15.0
https://bugs.kde.org/show_bug.cgi?id=404558 --- Comment #2 from Francesco Turco --- I haven't explicitely set software rendering anywhere. But on my system I only have the following option: # eselect opengl list Available OpenGL implementations: [1] xorg-x11 * -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404558] New: Very slow SDDM with Breeze theme when using plasma-workspace-5.15.0
https://bugs.kde.org/show_bug.cgi?id=404558
Bug ID: 404558
Summary: Very slow SDDM with Breeze theme when using
plasma-workspace-5.15.0
Product: plasmashell
Version: 5.15.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: ftu...@fastmail.fm
CC: plasma-b...@kde.org
Target Milestone: 1.0
I use the Plasma desktop environment on a Gentoo Linux system.
Yesterday I upgraded Plasma 5.14.5 to version 5.15.0. Now SDDM (with the Breeze
theme) is very slow at login, especially when you need to type the password.
I really think the problem is due to commit
dbb19ba333043670b616bfa586b054685892f531 because I successfully tried
installing plasma-workspace-5.15.0 and then manually replacing
/usr/share/sddm/themes/breeze/components/{Clock.qml,UserDelegate.qml} with
those from plasma-workspace-5.14.5.1.
I have a 10-year old Intel Core 2 Duo desktop computer with an integrated Intel
GPU.
--
You are receiving this mail because:
You are watching all bug changes.
[Falkon] [Bug 399001] Show page zoom in url bar when different from 100%
https://bugs.kde.org/show_bug.cgi?id=399001 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 69387] sort by album should prefer track number over artist
https://bugs.kde.org/show_bug.cgi?id=69387 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 335283] Unable to sort by column
https://bugs.kde.org/show_bug.cgi?id=335283 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm --- Comment #3 from Francesco Turco --- It seems sorting by column works inside "Collection List" but not inside "Play Queue", for example. I'm using JuK 18.12.2 on a Gentoo Linux system. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 404474] kde-frameworks/kio-5.55.0 Gentoo package - src/core/job_p.h:266:44: warning: ‘opType’ is used uninitialized in this function [-Wuninitialized]
https://bugs.kde.org/show_bug.cgi?id=404474 --- Comment #1 from Francesco Turco --- Created attachment 118152 --> https://bugs.kde.org/attachment.cgi?id=118152=edit info.txt emerge --info -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 404474] kde-frameworks/kio-5.55.0 Gentoo package - src/core/job_p.h:266:44: warning: ‘opType’ is used uninitialized in this function [-Wuninitialized]
https://bugs.kde.org/show_bug.cgi?id=404474 --- Comment #2 from Francesco Turco --- Created attachment 118153 --> https://bugs.kde.org/attachment.cgi?id=118153=edit build.log -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 404474] New: kde-frameworks/kio-5.55.0 Gentoo package - src/core/job_p.h:266:44: warning: ‘opType’ is used uninitialized in this function [-Wuninitialized]
https://bugs.kde.org/show_bug.cgi?id=404474 Bug ID: 404474 Summary: kde-frameworks/kio-5.55.0 Gentoo package - src/core/job_p.h:266:44: warning: ‘opType’ is used uninitialized in this function [-Wuninitialized] Product: frameworks-kio Version: 5.55.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: ftu...@fastmail.fm CC: kdelibs-b...@kde.org Target Milestone: --- I successfully built the kde-frameworks/kio-5.55.0 package on a Gentoo Linux system, but the Portage package manager reports the following warning message: * QA Notice: Package triggers severe warnings which indicate that it *may exhibit random runtime failures. * /var/tmp/portage/kde-frameworks/kio-5.55.0/work/kio-5.55.0/src/core/job_p.h:266:44: warning: ‘opType’ is used uninitialized in this function [-Wuninitialized] * Please do not file a Gentoo bug and instead report the above QA * issues directly to the upstream developers of this software. * Homepage: https://www.kde.org/ I'm using the GCC 8.2.0 compiler. STEPS TO REPRODUCE Run the following command on a Gentoo Linux system: # emerge =kde-frameworks/kio-5.55.0 SOFTWARE/OS VERSIONS Operating System: Gentoo Linux KDE Plasma Version: 5.14.5 Qt Version: 5.11.3 KDE Frameworks Version: 5.55.0 Kernel Version: 4.20.7-gnu OS Type: 64-bit Processors: 2 × Intel® Core™2 Duo CPU E8400 @ 3.00GHz Memory: 7.7 GiB of RAM ADDITIONAL INFORMATION emerge -pv kde-frameworks/kio These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R] kde-frameworks/kio-5.55.0:5/5.55::gentoo USE="X kwallet -acl -debug -doc -handbook -kerberos -test" 0 KiB Total: 1 package (1 reinstall), Size of downloads: 0 KiB -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 403767] New: kate/kio silently fail to save file when using sftp/fish
https://bugs.kde.org/show_bug.cgi?id=403767 Bug ID: 403767 Summary: kate/kio silently fail to save file when using sftp/fish Product: kate Version: 18.12.1 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: vivo75+...@gmail.com Target Milestone: --- when operating on remote files opened with urls like: sftp://user@1.2.3.4/home/user/pippo.txt fish://user@1.2.3.4/home/user/pippo.txt kate fail silently to save the file remotely. However it appears to save it somewhere locally, because hitting "f5" reload the file with latest changes $ kate --version kate 18.12.1 $ kioclient5 --version kioclient 5.14.5 kate output: --- vivo@Monfi ~ $ kate Empty filename passed to function Empty filename passed to function Empty filename passed to function Empty filename passed to function Empty filename passed to function Empty filename passed to function Empty filename passed to function Empty filename passed to function Empty filename passed to function Empty filename passed to function Empty filename passed to function LOGS: --- gen 30 15:25:52 Monfi kiod5[175485]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0 gen 30 15:26:17 Monfi kiod5[175485]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0 gen 30 15:26:18 Monfi plasmashell[3573]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:113: ReferenceError: appIcon is not defined gen 30 15:26:41 Monfi kwin_x11[3545]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 39479, resource id: 46952622, major code: 20 (GetProperty), minor code: 0 gen 30 15:26:41 Monfi kwin_x11[3545]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 39481, resource id: 46952622, major code: 20 (GetProperty), minor code: 0 gen 30 15:26:53 Monfi kdeinit5[3089441]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave gen 30 15:26:58 Monfi kwin_x11[3545]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40787, resource id: 46954207, major code: 20 (GetProperty), minor code: 0 gen 30 15:26:58 Monfi kwin_x11[3545]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40789, resource id: 46954207, major code: 20 (GetProperty), minor code: 0 gen 30 15:27:18 Monfi kdeinit5[3089720]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave gen 30 15:27:23 Monfi kdeinit5[3089441]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave gen 30 15:27:48 Monfi kdeinit5[3089720]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave gen 30 15:27:53 Monfi kdeinit5[3089441]: kf5.kio.core: finished() called twice! Please fix the "kio_sftp" KIO slave gen 30 15:28:00 Monfi openvpn[1626]: VERIFY OK: depth=1, CN=ita1.f1r.eu gen 30 15:28:00 Monfi openvpn[1626]: VERIFY KU OK gen 30 15:28:00 Monfi openvpn[1626]: Validating certificate extended key usage gen 30 15:28:00 Monfi openvpn[1626]: ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication gen 30 15:28:00 Monfi openvpn[1626]: VERIFY EKU OK gen 30 15:28:00 Monfi openvpn[1626]: VERIFY OK: depth=0, CN=ita1-server gen 30 15:28:00 Monfi openvpn[1626]: Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key gen 30 15:28:00 Monfi openvpn[1626]: Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key gen 30 15:28:00 Monfi openvpn[1626]: Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA gen 30 15:28:08 Monfi kiod5[175485]: org.kde.kio.kpasswdserver: User = "rStor" , WindowId = 0 gen 30 15:28:08 Monfi openvpn[1628]: VERIFY OK: depth=1, CN=VPN-Thez gen 30 15:28:08 Monfi openvpn[1628]: VERIFY KU OK gen 30 15:28:08 Monfi openvpn[1628]: Validating certificate extended key usage gen 30 15:28:08 Monfi openvpn[1628]: ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication gen 30 15:28:08 Monfi openvpn[1628]: VERIFY EKU OK gen 30 15:28:08 Monfi openvpn[1628]: VERIFY OK: depth=0, CN=_srv_thez_ gen 30 15:28:08 Monfi openvpn[1628]: Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key gen 30 15:28:08 Monfi openvpn[1628]: Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key gen 30 15:28:08 Monfi openvpn[1628]: Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA gen 30 15:28:09 Monfi kiod5[175485]: org.kde.kio.kpasswdserver: User = "rStor" , WindowId = 0 gen 30 15:28:15 Monfi openvpn[1647]: TLS: soft reset sec=0 bytes=77408/-1 pkts=909/0 gen 30 15:28:15 Monfi openvpn[1647]: VERIFY OK: depth=1, C=IT, ST=TO, L=TORINO, O=OpenVPN-PNPitalia, OU=zeth,
[trojita] [Bug 365299] make transition from qtwebkit to qtwebengine
https://bugs.kde.org/show_bug.cgi?id=365299 --- Comment #11 from Francesco Turco --- @Tobias: my use case is identical to yours. Falkon, Gentoo and QtWebEngine. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 384023] IncidenceEditor sometimes clings to last remaining category
https://bugs.kde.org/show_bug.cgi?id=384023 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 56613] More meta information: rating, play count, last played
https://bugs.kde.org/show_bug.cgi?id=56613 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 356182] Play count in Juk as one of the sorting methods
https://bugs.kde.org/show_bug.cgi?id=356182 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 333340] unable to open and browse my smartphone LG G-Flex
https://bugs.kde.org/show_bug.cgi?id=40 Francesco changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #6 from Francesco --- Oops, I have miss to close this bug report after the upgrade to Debian stretch (KDE Plasma 5) I can browse correctly on my smartphone, so this bug is solved for me -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397169] kmail does not sort mails after moving them to another directory
https://bugs.kde.org/show_bug.cgi?id=397169 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 363067] Feature request: Please support luks dm-crypt encrypted data projects
https://bugs.kde.org/show_bug.cgi?id=363067 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396555] New: KWin crash Segment Fault
https://bugs.kde.org/show_bug.cgi?id=396555 Bug ID: 396555 Summary: KWin crash Segment Fault Product: kwin Version: 5.13.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: fpeders...@kisantechnology.com Target Milestone: --- Application: kwin_x11 (5.13.3) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.17.5-1-zen x86_64 Distribution: "Artix" -- Information about the crash: I was sending an e-mail using Thunderbird. Other open application was: Palemoon, Dolphin, Konsole The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3449409e80 (LWP 2686))] Thread 6 (Thread 0x7f3427304700 (LWP 2864)): #0 0x7ffcd2cb8b04 in clock_gettime () #1 0x7f3448da3d76 in clock_gettime () at /usr/lib/libc.so.6 #2 0x7f344612c712 in () at /usr/lib/libQt5Core.so.5 #3 0x7f344612aefa in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #4 0x7f344612b4f6 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #5 0x7f344612a3f5 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f34460d86fc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f3445f21849 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f34407c39c9 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f3445f2b8f5 in () at /usr/lib/libQt5Core.so.5 #10 0x7f3441d830bc in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f3448d962ff in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f340e005700 (LWP 2836)): #0 0x7f3441d8907c in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f344504caac in () at /usr/lib/libQt5Script.so.5 #2 0x7f344504cac9 in () at /usr/lib/libQt5Script.so.5 #3 0x7f3441d830bc in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f3448d962ff in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f341886a700 (LWP 2835)): #0 0x7ffcd2cb8b04 in clock_gettime () #1 0x7f3448da3d76 in clock_gettime () at /usr/lib/libc.so.6 #2 0x7f344612c712 in () at /usr/lib/libQt5Core.so.5 #3 0x7f344612aefa in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #4 0x7f344612b4f6 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #5 0x7f344612a3f5 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f34460d86fc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f3445f21849 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f34407c39c9 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f3445f2b8f5 in () at /usr/lib/libQt5Core.so.5 #10 0x7f3441d830bc in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f3448d962ff in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f341906b700 (LWP 2834)): #0 0x7f3441d8907c in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f341abaadc4 in () at /usr/lib/dri/nouveau_dri.so #2 0x7f341abaaab8 in () at /usr/lib/dri/nouveau_dri.so #3 0x7f3441d830bc in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f3448d962ff in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f342d8f2700 (LWP 2799)): #0 0x7ffcd2cb8b04 in clock_gettime () #1 0x7f3448da3d76 in clock_gettime () at /usr/lib/libc.so.6 #2 0x7f344612c712 in () at /usr/lib/libQt5Core.so.5 #3 0x7f344612aefa in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #4 0x7f344612b4f6 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #5 0x7f344612a3f5 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f34460d86fc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f3445f21849 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f343f6b5976 in () at /usr/lib/libQt5DBus.so.5 #9 0x7f3445f2b8f5 in () at /usr/lib/libQt5Core.so.5 #10 0x7f3441d830bc in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f3448d962ff in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f3449409e80 (LWP 2686)): [KCrash Handler] #6 0x7f341a712fe5 in () at /usr/lib/dri/nouveau_dri.so #7 0x7f341a4f268e in () at /usr/lib/dri/nouveau_dri.so #8 0x7f341a9f16f7 in () at /usr/lib/dri/nouveau_dri.so #9 0x7f341a9f189a in () at /usr/lib/dri/nouveau_dri.so #10 0x7f341a8be61d in () at /usr/lib/dri/nouveau_dri.so #11 0x7f341a8bea82 in () at /usr/lib/dri/nouveau_dri.so #12 0x7f341a9ed64f in () at /usr/lib/dri/nouveau_dri.so #13 0x7f341a4963fb in () at
[kwin] [Bug 396431] New: System crashed while opening Thunderbird windows
https://bugs.kde.org/show_bug.cgi?id=396431 Bug ID: 396431 Summary: System crashed while opening Thunderbird windows Product: kwin Version: 5.13.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: fpeders...@kisantechnology.com Target Milestone: --- Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fac70d2de80 (LWP 2674))] Thread 6 (Thread 0x7fac4f5ef700 (LWP 3324)): #0 0x7fac706afdd6 in ppoll () at /usr/lib/libc.so.6 #1 0x7fac6da4ccbb in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fac6da4e1ab in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fac6d9fc6fc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fac6d845849 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fac680e79c9 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fac6d84f8f5 in () at /usr/lib/libQt5Core.so.5 #7 0x7fac696a70bc in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fac706ba2ff in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fac318be700 (LWP 2832)): #0 0x7fac696ad07c in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fac6c970aac in () at /usr/lib/libQt5Script.so.5 #2 0x7fac6c970ac9 in () at /usr/lib/libQt5Script.so.5 #3 0x7fac696a70bc in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fac706ba2ff in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fac335ff700 (LWP 2831)): #0 0x7fac706afdd6 in ppoll () at /usr/lib/libc.so.6 #1 0x7fac6da4ccbb in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fac6da4e1ab in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fac6d9fc6fc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fac6d845849 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fac680e79c9 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fac6d84f8f5 in () at /usr/lib/libQt5Core.so.5 #7 0x7fac696a70bc in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fac706ba2ff in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fac4098f700 (LWP 2830)): #0 0x7fac696ad07c in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fac424ced44 in () at /usr/lib/dri/nouveau_dri.so #2 0x7fac424cea38 in () at /usr/lib/dri/nouveau_dri.so #3 0x7fac696a70bc in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fac706ba2ff in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fac5521c700 (LWP 2795)): #0 0x7ffe17f5bb04 in clock_gettime () #1 0x7fac706c7d76 in clock_gettime () at /usr/lib/libc.so.6 #2 0x7fac6da50712 in () at /usr/lib/libQt5Core.so.5 #3 0x7fac6da4eefa in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #4 0x7fac6da4f4f6 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #5 0x7fac6da4e3f5 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fac6d9fc6fc in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fac6d845849 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fac66fd9976 in () at /usr/lib/libQt5DBus.so.5 #9 0x7fac6d84f8f5 in () at /usr/lib/libQt5Core.so.5 #10 0x7fac696a70bc in start_thread () at /usr/lib/libpthread.so.0 #11 0x7fac706ba2ff in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fac70d2de80 (LWP 2674)): [KCrash Handler] #6 0x7fac42036f85 in () at /usr/lib/dri/nouveau_dri.so #7 0x7fac41e1668e in () at /usr/lib/dri/nouveau_dri.so #8 0x7fac42315697 in () at /usr/lib/dri/nouveau_dri.so #9 0x7fac4231583a in () at /usr/lib/dri/nouveau_dri.so #10 0x7fac421e25bd in () at /usr/lib/dri/nouveau_dri.so #11 0x7fac421e2a22 in () at /usr/lib/dri/nouveau_dri.so #12 0x7fac423115ef in () at /usr/lib/dri/nouveau_dri.so #13 0x7fac41dba3fb in () at /usr/lib/dri/nouveau_dri.so #14 0x7fac41db4be3 in () at /usr/lib/dri/nouveau_dri.so #15 0x7fac43b9af21 in () at /usr/lib/libGLX_mesa.so.0 #16 0x7fac43b88769 in () at /usr/lib/libGLX_mesa.so.0 #17 0x7fac56b1131e in () at /usr/lib/qt/plugins/xcbglintegrations/libqxcb-glx-integration.so #18 0x7fac56b11329 in () at /usr/lib/qt/plugins/xcbglintegrations/libqxcb-glx-integration.so #19 0x7fac6e047ddf in QOpenGLContext::destroy() () at /usr/lib/libQt5Gui.so.5 #20 0x7fac6e048178 in QOpenGLContext::~QOpenGLContext() () at /usr/lib/libQt5Gui.so.5 #21 0x7fac6e04819a in QOpenGLContext::~QOpenGLContext() () at /usr/lib/libQt5Gui.so.5 #22 0x7fac54134b94 in () at
[kbackup] [Bug 396279] New: Support for compressing the whole target tarball once instead of each source file individually
https://bugs.kde.org/show_bug.cgi?id=396279 Bug ID: 396279 Summary: Support for compressing the whole target tarball once instead of each source file individually Product: kbackup Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kol...@aon.at Reporter: ftu...@fastmail.fm Target Milestone: --- Currently KBackup compresses each source file individually, and then stores them inside an uncompressed tarball. I would prefer instead to store source files without individual compression, and then compress the whole target tarball just once. What do you think? -- You are receiving this mail because: You are watching all bug changes.
[kbackup] [Bug 396278] New: Support for the xz compression format
https://bugs.kde.org/show_bug.cgi?id=396278 Bug ID: 396278 Summary: Support for the xz compression format Product: kbackup Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kol...@aon.at Reporter: ftu...@fastmail.fm Target Milestone: --- Currently KBackup only supports the bzip2 compression format as far as I know. It would be nice to have support for xz, too, because of its higher compression ratio. See https://tukaani.org/xz/ for details. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 395534] The new Plasma 5.13 Lock Screen animation/blur/multi-state features don't turn off when using a solid color
https://bugs.kde.org/show_bug.cgi?id=395534 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 386114] KRunner on wayland always appears under top panel
https://bugs.kde.org/show_bug.cgi?id=386114 --- Comment #6 from francesco --- I want just to confirm that as for https://bugs.kde.org/show_bug.cgi?id=395840, this bug is still present in plasma 5.13. It is reproducible also with Latte Dock ( so with a latte dock top panel ). Note that also Yakuake first line is covered by the panel. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 352262] KGet does not add a download immediately
https://bugs.kde.org/show_bug.cgi?id=352262 --- Comment #2 from Francesco Turco --- I can reproduce this problem too. I'm using KGet 18.4.2 on a Gentoo Linux system. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 352262] KGet does not add a download immediately
https://bugs.kde.org/show_bug.cgi?id=352262 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 395840] (Wayland) Latte Dock - Top Panel covers Plasma search
https://bugs.kde.org/show_bug.cgi?id=395840 --- Comment #1 from francesco --- Created attachment 113549 --> https://bugs.kde.org/attachment.cgi?id=113549=edit Yakuake first line covered -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 395840] New: (Wayland) Latte Dock - Top Panel covers Plasma search
https://bugs.kde.org/show_bug.cgi?id=395840 Bug ID: 395840 Summary: (Wayland) Latte Dock - Top Panel covers Plasma search Product: latte-dock Version: git (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: postadelm...@gmail.com Target Milestone: --- Created attachment 113548 --> https://bugs.kde.org/attachment.cgi?id=113548=edit My Desk On Wayland (Plasma 5.13) if I set a top Latte panel this will cover: - Plasma Search - Yakuake Note: I am not able to take a proper screenshot of the issue with plasma search because spectacle missbehave under wayland and force me to do a mouse click ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389922] (Wayland) Windows Rules - Wrong Desktop list
https://bugs.kde.org/show_bug.cgi?id=389922 francesco changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from francesco --- I just want to confirm the bug is still present on Plasma 5.13 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 289207] KMail sometimes fails to send messages with cyrus-sasl-2.1.25
https://bugs.kde.org/show_bug.cgi?id=289207 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 387454] MTP doesn't work in KDE with Linux 4.14
https://bugs.kde.org/show_bug.cgi?id=387454 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 386379] Dolphin scrolls faster in icon mode than other Qt/KDE software
https://bugs.kde.org/show_bug.cgi?id=386379 --- Comment #17 from francesco --- Understand the exact problem means the solution is only one step far ... :) What if you share some precise link to the code involved ... eventually some people here can help into find a solution. These are my 2 cents ... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 386379] Dolphin scrolls faster in icon mode than other Qt/KDE software
https://bugs.kde.org/show_bug.cgi?id=386379 --- Comment #16 from francesco --- Understand the exact problem means the solution is only one step far ... :) What if you share some precise link to the code involved ... eventually some people here can help into find a solution. These are my 2 cents ... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 386238] Kmail crashes on start
https://bugs.kde.org/show_bug.cgi?id=386238 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 391293] Frequent Crashing On Start
https://bugs.kde.org/show_bug.cgi?id=391293 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[pimsettingexporter] [Bug 394829] New: Support for archive formats other than ZIP in PIM Setting Exporter
https://bugs.kde.org/show_bug.cgi?id=394829 Bug ID: 394829 Summary: Support for archive formats other than ZIP in PIM Setting Exporter Product: pimsettingexporter Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mon...@kde.org Reporter: ftu...@fastmail.fm Target Milestone: --- I have PIM Setting Exporter 5.8.1 on a Gentoo Linux system. As far as I know PIM Setting Exporter can only create ZIP archives. In my opinion it should also support other archive formats, such as .tar.gz, .tar.bz2 and .tar.xz. Personally I would choose .tar.xz because it has the highest compression ratio. What do you think? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 270808] External hard disks should be spun down when 'safely removed'
https://bugs.kde.org/show_bug.cgi?id=270808 Francesco Turco <ftu...@fastmail.fm> changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 394646] kdeconnect 1.8.2 on android and 1.3.0 on debian do not see each other
https://bugs.kde.org/show_bug.cgi?id=394646 Francesco <fra...@gmail.com> changed: What|Removed |Added CC||fra...@gmail.com --- Comment #2 from Francesco <fra...@gmail.com> --- The same happens to me. Devices don't see each others anymore. It seems happening after the latest update of Kdeconnect on Android (the former was fully functional). PC: Kubuntu 18.04 [frapox@tungsteno ~]$ kdeconnect-cli --version kdeconnect-cli 1.3 Smartphone: Android 8.1 org.kde.kdeconnect_tp version 1.8.4 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 76380] Trashing files on other partitions and disks that are mounted without UID=USERID, GID=USERGROUPID, FMASK=177, DMASK=077 copies them to the Trash directory on /
https://bugs.kde.org/show_bug.cgi?id=76380 Francesco Turco <ftu...@fastmail.fm> changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
