[kwin] [Bug 455526] Blur glitches started to appear in wayland again
https://bugs.kde.org/show_bug.cgi?id=455526 Fabio changed: What|Removed |Added CC||fabio96...@gmail.com --- Comment #16 from Fabio --- Can reproduce this bug on Plasma 5.27 beta, but usually only if I open a console in Dolphin. Operating System: openSUSE Tumbleweed 20230201 KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.8-1-default (64-bit) Graphics Platform: Wayland Processors: AMD Ryzen 7 5800H with Radeon Graphics (actually using the Nvidia newest proprietary driver on a RTX 3060) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 478539] New: baloo file extractor crashed
https://bugs.kde.org/show_bug.cgi?id=478539 Bug ID: 478539 Summary: baloo file extractor crashed Classification: Frameworks and Libraries Product: frameworks-baloo Version: 5.113.0 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: fabbaoshort...@gmail.com Target Milestone: --- Application: baloo_file_extractor (5.113.0) Qt Version: 5.15.11 Frameworks Version: 5.113.0 Operating System: Linux 6.6.7-arch1-1 x86_64 Windowing System: X11 Distribution: Arch Linux DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: QSocketNotifier: Invalid socket 5 and type 'Read', disabling... QSocketNotifier: Invalid socket 9 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Read', disabling... Process 1648 (baloo_file_extr) of user 1000 dumped core. Stack trace of thread 1648: #0 0x7f30668ac83c n/a (libc.so.6 + 0x8e83c) #1 0x7f306685c668 raise (libc.so.6 + 0x3e668) #2 0x7f3067be488f _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x788f) #3 0x7f306685c710 n/a (libc.so.6 + 0x3e710) #4 0x7f30668ac83c n/a (libc.so.6 + 0x8e83c) #5 0x7f306685c668 raise (libc.so.6 + 0x3e668) #6 0x7f30668444b8 abort (libc.so.6 + 0x264b8) #7 0x7f306680cb56 n/a (liblmdb.so + 0x5b56) #8 0x7f306680ac6e n/a (liblmdb.so + 0x3c6e) #9 0x7f30668188c6 n/a (liblmdb.so + 0x118c6) #10 0x7f306680ffa3 n/a (liblmdb.so + 0x8fa3) #11 0x7f3066811bec n/a (liblmdb.so + 0xabec) #12 0x7f3066814716 mdb_cursor_put (liblmdb.so + 0xd716) #13 0x7f3066815668 mdb_put (liblmdb.so + 0xe668) #14 0x7f3067c002f3 _ZN5Baloo10PositionDB3putERK10QByteArrayRK7QVectorINS_12PositionInfoEE (libKF5BalooEngine.so.5 + 0x172f3) #15 0x7f3067c0d963 _ZN5Baloo16WriteTransaction6commitEv (libKF5BalooEngine.so.5 + 0x24963) #16 0x7f3067c0397e _ZN5Baloo11Transaction6commitEv (libKF5BalooEngine.so.5 + 0x1a97e) #17 0x56107d7cdfc5 n/a (baloo_file_extractor + 0x13fc5) #18 0x7f30670d3317 n/a (libQt5Core.so.5 + 0x2d3317) #19 0x7f30670c3b4e _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2c3b4e) #20 0x7f306709c168 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x29c168) #21 0x7f30670ea7cb _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x2ea7cb) #22 0x7f30670eae02 n/a (libQt5Core.so.5 + 0x2eae02) #23 0x7f3065b0df69 n/a (libglib-2.0.so.0 + 0x59f69) #24 0x7f3065b6c367 n/a (libglib-2.0.so.0 + 0xb8367) #25 0x7f3065b0c162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162) #26 0x7f30670eaf7c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2eaf7c) #27 0x7f306709ae74 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x29ae74) #28 0x7f306709c313 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x29c313) #29 0x56107d7c3d4e n/a (baloo_file_extractor + 0x9d4e) #30 0x7f3066845cd0 n/a (libc.so.6 + 0x27cd0) #31 0x7f3066845d8a __libc_start_main (libc.so.6 + 0x27d8a) #32 0x56107d7c3e75 n/a (baloo_file_extractor + 0x9e75) Stack trace of thread 1649: #0 0x7f3066920f6f __poll (libc.so.6 + 0x102f6f) #1 0x7f3065b6c2b6 n/a (libglib-2.0.so.0 + 0xb82b6) #2 0x7f3065b0c162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162) #3 0x7f30670eaf9f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2eaf9f) #4 0x7f306709ae74 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x29ae74) #5 0x7f3066ef74f6 _ZN7QThread4execEv (libQt5Core.so.5 + 0xf74f6) #6 0x7f3067397a9a n/a (libQt5DBus.so.5 + 0x18a9a) #7 0x7f3066ef371a n/a (libQt5Core.so.5 + 0xf371a) #8 0x7f30668aa9eb n/a (libc.so.6 + 0x8c9eb) #9 0x7f306692e7cc n/a (libc.so.6 + 0x1107cc) Stack trace of thread 1651: #0 0x7f306692b561 pselect (libc.so.6 + 0x10d561) #1 0x7f3065e4f6f9 n/a (libusbmuxd-2.0.so.6 + 0x36f9) #2 0x7f3065e503cc n/a (libusbmuxd-2.0.so.6 + 0x43cc) #3 0x7f30668aa9eb n/a (libc.so.6 + 0x8c9eb) #4 0x7f306692e7cc n/a (libc.so.6 + 0x1107cc) ELF object binary architecture: AMD x86-64 Process 1195 (baloo_file_extr) of user 1000 dumped core. Stack trace of thread 1195: #0 0x7f24d6eac83c n/a (libc.so.6 + 0x8e83c) #1 0x7f24d6e5c668 raise (libc.so.6 + 0x3e668) #2 0x7f24d819a88f _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x788f) #3 0x7f24d6e5c710 n/a (libc.so.6 + 0x3e710) #4 0x7f24d6eac83c n/a (libc.so.6 + 0x8e83c) #5 0x7f24d6e5c668 raise (libc.so.6 + 0x3e668) #6 0x7f24d6e444b8 abort (libc.so.6 + 0x264b8) #7 0x7f24d6dcbb56 n/a (liblmdb.so + 0x5b56) #8 0x7f24d6dc9c6e n/a (liblmdb.so + 0x3c6e) #9 0x7f24d6dd78c6 n/a
[NeoChat] [Bug 481969] New: NEOCHAT WITHOUT BACKGROUND
https://bugs.kde.org/show_bug.cgi?id=481969 Bug ID: 481969 Summary: NEOCHAT WITHOUT BACKGROUND Classification: Applications Product: NeoChat Version: 24.02.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: fabiojlbc1...@gmail.com CC: c...@carlschwan.eu 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 *** STEPS TO REPRODUCE 1. After closing NeoChat, it does not reopen via the notification icon 2. The notification icon should be a warning that NeoChat is running in the background, but it only reopens when the main icon is used. 3. One of the functions with Neochat open is that the notification icon minimizes the program window, but it only blinks and nothing else. 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 NeoChat, while I searched for something else in the available settings, showed freezes where nothing matched any single or double click forcing me to restart the computer. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485652] New: Random artefacts on main screen
https://bugs.kde.org/show_bug.cgi?id=485652 Bug ID: 485652 Summary: Random artefacts on main screen Classification: Plasma Product: kwin Version: 6.0.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: fabio.loregg...@gmail.com Target Milestone: --- Created attachment 168599 --> https://bugs.kde.org/attachment.cgi?id=168599&action=edit Screenshot showcasing the pixel artefacts on the bottom of the screen SUMMARY Weird artefacts at the bottom of the screen during normal usage (i.e opening chrome after a reboot) STEPS TO REPRODUCE 1. Installed the plasma DE in arch linux machine (Linux 6.8.5-arch1-1) on the new Framework 16 2. Packages included: plasma-meta, kde-applications 3. I have a multimonitor setup, with 2 1920x1080 screens and the main laptop screen at 2560x1600 (150%) OBSERVED RESULT There seems to be some weird artefacts that always show up after a normal usage. It appears consistently at the bottom of the screen (there seems to be a line of black pixels which it stays within) EXPECTED RESULT Not to see those artefacts SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Graphics: Wayland ADDITIONAL INFORMATION Framework 16 laptop -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 483638] TAB key not functional inside rdp windows client
https://bugs.kde.org/show_bug.cgi?id=483638 Fabio changed: What|Removed |Added CC||ctrlal...@gmail.com --- Comment #6 from Fabio --- https://invent.kde.org/network/krdc/-/merge_requests/94 fixes this issue. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 486342] New: Equalizer
https://bugs.kde.org/show_bug.cgi?id=486342 Bug ID: 486342 Summary: Equalizer Classification: Applications Product: amarok Version: 3.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Tools/Equalizer Assignee: amarok-bugs-d...@kde.org Reporter: fabiom...@gmail.com Target Milestone: kf5 The equalizer, even when activated, does not work -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 486343] New: Unable to install Amarok
https://bugs.kde.org/show_bug.cgi?id=486343 Bug ID: 486343 Summary: Unable to install Amarok Classification: Applications Product: amarok Version: 3.0.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: fabioam...@gmail.com Target Milestone: kf5 Created attachment 169033 --> https://bugs.kde.org/attachment.cgi?id=169033&action=edit error *** Dear Team, when I try to install the new version of amarok, I get the following error (attachment) *** SUMMARY I try to install Amarok from the following link: appstream://org.kde.amarok Using Lubuntu 24.04 and Discover app. Can you please package this application? STEPS TO REPRODUCE 1. click on appstream://org.kde.amarok OBSERVED RESULT see attachment EXPECTED RESULT Amarok is installed. 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.
[amarok] [Bug 486342] Equalizer
https://bugs.kde.org/show_bug.cgi?id=486342 --- Comment #2 from Fabio --- Hello, This is exactly the symptom, it happened here I had to stop the music and start it again to get the equalizer effect. I don't know if it helps but I have VLC installed Em 30/04/2024 12:34, Tuomas Nurmi escreveu: > https://bugs.kde.org/show_bug.cgi?id=486342 > > Tuomas Nurmi changed: > > What|Removed |Added > > CC||tuo...@norsumanageri.org > > --- Comment #1 from Tuomas Nurmi --- > Thank you for your report. I assume you are using phonon-vlc backend. I tried > changing equalizer settings, and for them to have effect, I had to stop the > playback and start the track again (they didn't have effect right away). Can > you confirm if this is the case for you? > -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 485215] KRDC hangs when trying to connect to VNC host
https://bugs.kde.org/show_bug.cgi?id=485215 Fabio changed: What|Removed |Added CC||ctrlal...@gmail.com --- Comment #5 from Fabio --- The original issue is possibly a duplicate of BUG 486178 -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 486645] New: Issue with the order of Activities (Plasma 6)
https://bugs.kde.org/show_bug.cgi?id=486645 Bug ID: 486645 Summary: Issue with the order of Activities (Plasma 6) Classification: Plasma Product: Active Window Control Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: fabiom...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 169228 --> https://bugs.kde.org/attachment.cgi?id=169228&action=edit Image of my desktop in the Activities settings. I'm not sure if I chose the right topic, but the problem is with Activities. Plasma comes with the Default Activity, but when creating a second activity, it sets the Default Activity as the second one instead of the first, which is bad for organization. Interestingly, after creating the second activity, it assumes the correct sequential order, except that the second activity becomes the first one. I'll send a picture for better clarification. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 485289] New: no open the file
https://bugs.kde.org/show_bug.cgi?id=485289 Bug ID: 485289 Summary: no open the file Classification: Applications Product: gwenview Version: 24.02.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: gwenview-bugs-n...@kde.org Reporter: fabiom...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDEneon 6.03 (available in About System) KDE Plasma Version: 6.03 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Doesn't open large files I believe that's the problem, I'm attaching the file that I can't open for analysis, remembering that in the windows viewer it opens normally -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 485372] New: open file
https://bugs.kde.org/show_bug.cgi?id=485372 Bug ID: 485372 Summary: open file Classification: Applications Product: gwenview Version: 24.02.1 Platform: Neon OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: fabiom...@gmail.com Target Milestone: --- Created attachment 168388 --> https://bugs.kde.org/attachment.cgi?id=168388&action=edit error image *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I have a 215mb png file that doesn't open in gwenview, remembering that this same file opens in any image viewer, is it some size limitation bug? Thank you -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 483824] New: Timer does not play sound when finished
https://bugs.kde.org/show_bug.cgi?id=483824 Bug ID: 483824 Summary: Timer does not play sound when finished Classification: Applications Product: KClock Version: 24.02.0 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: espi...@gmail.com Reporter: fabio.for...@gmail.com CC: hanyo...@protonmail.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 *** STEPS TO REPRODUCE 1. set a timer 2. wait for the timer to end OBSERVED RESULT system message, dialog window EXPECTED RESULT system message, dialog window + sound SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: Kernel: 6.5.0-25-generic x86_64 bits: 64 compiler: N/A Desktop: MATE 1.26.0 info: mate-panel wm: marco 1.26.0 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy ADDITIONAL INFORMATION In the last version it worked! -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 484666] Copy - Paste is not working
https://bugs.kde.org/show_bug.cgi?id=484666 Fabio changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/netw ||ork/krdc/-/commit/d1cc1829a ||554696a2893a02d5d400e6e6353 ||48c9 --- Comment #4 from Fabio --- Git commit d1cc1829a554696a2893a02d5d400e6e635348c9 by Fabio Bas. Committed on 17/05/2024 at 12:36. Pushed by ctrlaltca into branch 'master'. rdp: add clipboard support M +1-0rdp/CMakeLists.txt A +371 -0rdp/rdpcliprdr.cpp [License: GPL(v2.0+)] A +26 -0rdp/rdpcliprdr.h [License: GPL(v2.0+)] M +34 -7rdp/rdpsession.cpp M +21 -0rdp/rdpsession.h M +1-1rdp/rdpview.cpp M +1-0rdp/rdpview.h https://invent.kde.org/network/krdc/-/commit/d1cc1829a554696a2893a02d5d400e6e635348c9 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 487140] Clipboard doesn't work
https://bugs.kde.org/show_bug.cgi?id=487140 Fabio changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||ctrlal...@gmail.com --- Comment #1 from Fabio --- Duplicate of 484666. Fixed in current development version *** This bug has been marked as a duplicate of bug 484666 *** -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 484666] Copy - Paste is not working
https://bugs.kde.org/show_bug.cgi?id=484666 Fabio changed: What|Removed |Added CC||sunwe...@gmail.com --- Comment #5 from Fabio --- *** Bug 487140 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482137] Regression: Filesystem/Clipboard not shared anymore
https://bugs.kde.org/show_bug.cgi?id=482137 Fabio changed: What|Removed |Added CC||ctrlal...@gmail.com --- Comment #3 from Fabio --- Clipboard has been fixed in current development version (see BUG 484666), filesystem sharing is still missing. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 484607] Copy and Paste and Folder Sharing not working
https://bugs.kde.org/show_bug.cgi?id=484607 Fabio changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||ctrlal...@gmail.com --- Comment #1 from Fabio --- Clipboard has been fixed in current development version (see BUG 484666), filesystem sharing is still missing. *** This bug has been marked as a duplicate of bug 482137 *** -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482137] Regression: Filesystem/Clipboard not shared anymore
https://bugs.kde.org/show_bug.cgi?id=482137 Fabio changed: What|Removed |Added CC||teej.d@gmail.com --- Comment #4 from Fabio --- *** Bug 484607 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 455691] Cannot connect to older Windows server "ERRCONNECT_TLS_CONNECT_FAILED"
https://bugs.kde.org/show_bug.cgi?id=455691 Fabio changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/krdc/-/commit/8bca0c765 ||c75e38f26f38bde650a48308ab1 ||aaeb Status|REPORTED|RESOLVED CC||ctrlal...@gmail.com Resolution|--- |FIXED Version Fixed In||24.05 --- Comment #1 from Fabio --- Fixed by https://invent.kde.org/network/krdc/-/merge_requests/65 An option to set the minimum TLS security level has been added -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 486342] Equalizer
https://bugs.kde.org/show_bug.cgi?id=486342 --- Comment #5 from Fabio --- Yes, I confirm that the analyzer applet is not working together with the equalizer my system is KDE neon 6.0.4 intel core i5 processor 16gb memory wayland graphics server Em 22/05/2024 17:57, Sebastian escreveu: > https://bugs.kde.org/show_bug.cgi?id=486342 > > Sebastian changed: > > What|Removed |Added > > CC||sebastian.ku...@mailbox.org > > --- Comment #4 from Sebastian --- > Hi, I was looking for a potential bug report as in Amarok Version 3.0.0 the > Analyzer Applet is not working for me. > > However, I found this Equalizer issue, and I can confirm the same behavior. > > I am running the following system: > Operating System: openSUSE Tumbleweed 20240521 > KDE Plasma Version: 6.0.4 > KDE Frameworks Version: 6.2.0 > Qt Version: 6.7.0 > Kernel Version: 6.9.1-1-default (64-bit) > Graphics Platform: Wayland > Processors: 4 × AMD A8-7650K Radeon R7, 10 Compute Cores 4C+6G > Memory: 14.6 GiB of RAM > Graphics Processor: KAVERI > > Would be great to get an update here, and *maybe* the issue is even related to > the Analyzer Applet? > > Many thanks! > -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 486342] Equalizer
https://bugs.kde.org/show_bug.cgi?id=486342 --- Comment #11 from Fabio --- ok, thank you for your effort, I understand the technical difficulty, and I look forward to a solution in the near future, a big hug! Em 23/05/2024 18:58, Sebastian escreveu: > https://bugs.kde.org/show_bug.cgi?id=486342 > > --- Comment #10 from Sebastian --- > (In reply to Tuomas Nurmi from comment #9) >> Yes, fine questions. Some answers: >> As phonon-gstreamer backend is unmaintainend (related discussion at >> https://invent.kde.org/libraries/phonon-gstreamer/-/issues/1 ) and thus >> unsupported, it has lately been removed from various distribution >> repositories. For openSUSE, the packages are still available at various >> experimental repositories ( >> https://software.opensuse.org/package/phonon4qt5-backend-gstreamer ) >> However, due to fact that it is unsupported, even its most obvious and >> fixable bugs will not get fixed (e.g. >> https://bugs.kde.org/show_bug.cgi?id=475880 ) >> >> If multiple backends are installed, Phonon backend can be changed using >> phononsettings application (available from separate phononsettings package, >> at least on openSUSE). The packagers have set phonon-vlc-qt5 as dependency >> probably as it is the only supported backend at the moment (okay, there's >> apparently also phonon4qt5-backend-mpv but I have no experience with that >> one, and it being a fork of phonon-vlc, its features are likely subset of >> those of phonon-vlcs), and some backend is needed. >> >> When talking about "phonon-vlc team", one should be aware that although >> there are some people keeping the lights on with phonon-vlc, the actual >> development work on it (as well as anything phonon-related) has been quite >> limited for 5 years or so, as observable from e.g. the code history at >> https://invent.kde.org/libraries/phonon-vlc/-/commits/master/?ref_type=HEADS >> >> Additionally, I believe Amarok is the only software using the more specific >> audio functionalities in Phonon nowadays. >> (Some Amarok functionality related phonon-vlc bugreports, which are not very >> likely to get implemented any time soon mostly due to vlc library >> architechture:https://bugs.kde.org/show_bug.cgi?id=323332 and >> https://bugs.kde.org/show_bug.cgi?id=320215 ) >> >> Next steps of Amarok audio playback technology are something that should >> receive some thoughts after/during Qt6 porting, I think. (The most obvious >> options being someone spending a lot of effort on phonon-vlc, someone taking >> up maintaining phonon-gstreamer, or rewriting Amarok audio playback to use >> e.g. gstreamer directly) > Ok, all is understood. Many thanks for the hint for phononsettings - I tried > that (it was installed already under openSUSE); however, it only shows Phonon > VLC in the backend section but no gstreamer. That's weird, as gstreamer is > installed, too. > > Anyway, it seems that there is only one chance to solve the issue - the Amarok > Qt6 porting. It is pretty pity that there is no immediate solution; Amarok in > my eyes is one of the best players... > > Anything else I can help with? Otherwise, I would propose to close this issue > as there is no fast solution available. > -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 453297] New: KMail + Akonadi crash
https://bugs.kde.org/show_bug.cgi?id=453297 Bug ID: 453297 Summary: KMail + Akonadi crash Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: fmdefrance...@gmail.com Target Milestone: --- Application: kmail (5.14.2 (20.04.2)) Qt Version: 5.12.7 Frameworks Version: 5.76.0 Operating System: Linux 5.3.18-150300.59.60-default x86_64 Windowing system: X11 Distribution: openSUSE Leap 15.3 -- Information about the crash: KMail and Akonadi crash while retrieving mails. They crash at the same time. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/7/bits/atomic_base.h:396 #5 QAtomicOps::load (_q_value=) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227 #6 QBasicAtomicInteger::load (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103 #7 QtPrivate::RefCount::isShared (this=) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:101 #8 QList::append (this=0x118, t=@0x7ffc4b94ad90: 0x5624e0fb8680) at ../../include/QtCore/../../src/corelib/tools/qlist.h:584 #9 0x7f7f74aff858 in QWidget::insertAction (this=0x5624e0fb8680, before=, action=0x5624e0ea02b0) at kernel/qwidget.cpp:3314 #10 0x7f7f72ce4fd2 in KXMLGUI::ActionList::plug(QWidget*, int) const () from /usr/lib64/libKF5XmlGui.so.5 #11 0x7f7f72ce8912 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&, QTypedArrayData::iterator const&) () from /usr/lib64/libKF5XmlGui.so.5 #12 0x7f7f72ce8ad6 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) () from /usr/lib64/libKF5XmlGui.so.5 #13 0x7f7f72ce8b13 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) () from /usr/lib64/libKF5XmlGui.so.5 #14 0x7f7f72ce8b13 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) () from /usr/lib64/libKF5XmlGui.so.5 #15 0x7f7f72ce23eb in KXMLGUIFactory::plugActionList(KXMLGUIClient*, QString const&, QList const&) () from /usr/lib64/libKF5XmlGui.so.5 #16 0x7f7f6e5f6b5d in PimCommon::PluginInterface::initializePluginActions (this=, prefix=..., guiClient=0x5624e405bf10) at /usr/src/debug/pimcommon-20.04.2-bp153.2.2.1.x86_64/src/pimcommonakonadi/genericplugins/plugininterface.cpp:168 #17 0x7f7f75c883fe in KMMainWidget::initializePluginActions (this=this@entry=0x5624e478c770) at /usr/src/debug/kmail-20.04.2-bp153.3.2.1.x86_64/src/kmmainwidget.cpp:4217 #18 0x7f7f75c8fc83 in KMMainWidget::slotShowStartupFolder (this=0x5624e478c770) at /usr/src/debug/kmail-20.04.2-bp153.3.2.1.x86_64/src/kmmainwidget.cpp:4121 #19 0x7f7f73c7ee44 in QtPrivate::QSlotObjectBase::call (a=0x7ffc4b94b1c0, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #20 QSingleShotTimer::timerEvent (this=0x5624e33faac0) at kernel/qtimer.cpp:318 #21 0x7f7f73c729db in QObject::event (this=0x5624e33faac0, e=) at kernel/qobject.cpp:1283 #22 0x7f7f74ac7f9c in QApplicationPrivate::notify_helper (this=this@entry=0x5624e0792f30, receiver=receiver@entry=0x5624e33faac0, e=e@entry=0x7ffc4b94b500) at kernel/qapplication.cpp:3701 #23 0x7f7f74acf5b0 in QApplication::notify (this=0x7ffc4b94bc70, receiver=0x5624e33faac0, e=0x7ffc4b94b500) at kernel/qapplication.cpp:3447 #24 0x7f7f73c42368 in QCoreApplication::notifyInternal2 (receiver=0x5624e33faac0, event=0x7ffc4b94b500) at kernel/qcoreapplication.cpp:1088 #25 0x7f7f73c9e859 in QTimerInfoList::activateTimers (this=0x5624e079b370) at kernel/qtimerinfo_unix.cpp:643 #26 0x7f7f73c9f021 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:182 #27 0x7f7f666a8694 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x7f7f666a8a30 in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x7f7f666a8abc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #30 0x7f7f73c9f3ef in QEventDispatcherGlib::processEvents (this=0x5624e0876d10, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #31 0x7f7f73c405ba in QEventLoop::exec (this=this@entry=0x7ffc4b94b750, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #32 0x7f7f73c497c0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1389 #33 0x5624df7cea5b in main (argc=, argv=) at /usr/src/debug/kmail-20.04.2-bp153.3.2.1.x86_64/src/main.cpp:163 [Inferior 1 (process 8505) detached] Possible duplicates by query: bug 452717, bug 449952, bug 449891, bug 443784, bug 440840. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 453092] New: Akonadi server crashes while using KMail
https://bugs.kde.org/show_bug.cgi?id=453092 Bug ID: 453092 Summary: Akonadi server crashes while using KMail Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: kdepim-b...@kde.org Reporter: fmdefrance...@gmail.com Target Milestone: --- Application: akonadi_imap_resource (5.14.2 (20.04.2)) Qt Version: 5.12.7 Frameworks Version: 5.76.0 Operating System: Linux 5.3.18-150300.59.60-default x86_64 Windowing system: X11 Distribution: openSUSE Leap 15.3 -- Information about the crash: Akonadi server crashes while using KMail The crash can be reproduced sometimes. -- Backtrace: Application: Google Mail (fmdefrancesco) (akonadi_imap_resource), signal: Segmentation fault [KCrash Handler] #4 ImapAccount::authenticationMode() const (this=0x0) at /usr/src/debug/kdepim-runtime-20.04.2-bp153.2.2.1.x86_64/resources/imap/imapaccount.cpp:85 #5 0x559f7be83216 in SessionPool::requestPassword() (this=0x559f7e09b2f0) at /usr/src/debug/kdepim-runtime-20.04.2-bp153.2.2.1.x86_64/resources/imap/sessionpool.cpp:88 #6 0x559f7be87ad5 in SessionPool::processPendingRequests() (this=0x559f7e09b2f0) at /usr/src/debug/kdepim-runtime-20.04.2-bp153.2.2.1.x86_64/resources/imap/sessionpool.cpp:302 #7 0x7f408473be44 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffcd368c580, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #8 QSingleShotTimer::timerEvent(QTimerEvent*) (this=0x559f806f01e0) at kernel/qtimer.cpp:318 #9 0x7f408472f9db in QObject::event(QEvent*) (this=0x559f806f01e0, e=) at kernel/qobject.cpp:1283 #10 0x7f4085936f9c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x559f7dc31ad0, receiver=receiver@entry=0x559f806f01e0, e=e@entry=0x7ffcd368c8c0) at kernel/qapplication.cpp:3701 #11 0x7f408593e5b0 in QApplication::notify(QObject*, QEvent*) (this=0x7ffcd368cbc0, receiver=0x559f806f01e0, e=0x7ffcd368c8c0) at kernel/qapplication.cpp:3447 #12 0x7f40846ff368 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x559f806f01e0, event=0x7ffcd368c8c0) at kernel/qcoreapplication.cpp:1088 #13 0x7f408475b859 in QTimerInfoList::activateTimers() (this=0x559f7dc39d10) at kernel/qtimerinfo_unix.cpp:643 #14 0x7f408475c059 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:182 #15 idleTimerSourceDispatch(GSource*, GSourceFunc, gpointer) (source=) at kernel/qeventdispatcher_glib.cpp:229 #16 0x7f407d083694 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #17 0x7f407d083a30 in () at /usr/lib64/libglib-2.0.so.0 #18 0x7f407d083abc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #19 0x7f408475c3ef in QEventDispatcherGlib::processEvents(QFlags) (this=0x559f7dd14d40, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #20 0x7f40846fd5ba in QEventLoop::exec(QFlags) (this=this@entry=0x7ffcd368cb10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #21 0x7f40847067c0 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1389 #22 0x7f408833b8ed in Akonadi::ResourceBase::init(Akonadi::ResourceBase&) (r=...) at /usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/agentbase/resourcebase.cpp:611 #23 0x559f7be21d0f in Akonadi::ResourceBase::init(int, char**) (argc=, argv=) at /usr/include/KF5/AkonadiAgentBase/resourcebase.h:199 #24 0x7f4083a6a2bd in __libc_start_main () at /lib64/libc.so.6 #25 0x559f7be1ff6a in _start () at ../sysdeps/x86_64/start.S:120 [Inferior 1 (process 4585) detached] Possible duplicates by query: bug 435427, bug 418599, bug 415960, bug 415930, bug 415339. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 453126] New: KMail + Akonadi Server crash at the same time
https://bugs.kde.org/show_bug.cgi?id=453126 Bug ID: 453126 Summary: KMail + Akonadi Server crash at the same time Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: fmdefrance...@gmail.com Target Milestone: --- Application: kmail (5.14.2 (20.04.2)) Qt Version: 5.12.7 Frameworks Version: 5.76.0 Operating System: Linux 5.3.18-150300.59.60-default x86_64 Windowing system: X11 Distribution: openSUSE Leap 15.3 -- Information about the crash: - What I was doing when the application crashed: I was not using KMail, just browsing with Google Chrome. However KMail was downloading, filtering, and archiving emails. This kinds of crashes happen about 3 times per 8 hours of working day. Akonadi + KMail often crashe also when the desktop is locked, therefore these crashes are not due to user's actions. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 Akonadi::Item::parentCollection (this=this@entry=0x7ffd3021f1e0) at /usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/core/item.cpp:275 #5 0x7f5455982bad in Akonadi::EntityTreeModelPrivate::isHiddenImpl (this=0x55c9d98ae330, entity=..., type=) at /usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/core/models/entitytreemodel_p.cpp:304 #6 0x7f545597f38b in Akonadi::EntityTreeModelPrivate::isHidden (item=..., this=0x55c9d98ae330) at /usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/core/models/entitytreemodel_p.cpp:321 #7 Akonadi::EntityTreeModelPrivate::monitoredItemRemoved (this=this@entry=0x55c9d98ae330, item=..., parentCollection=...) at /usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/core/models/entitytreemodel_p.cpp:1122 #8 0x7f545596df6a in Akonadi::EntityTreeModel::qt_static_metacall (_o=, _c=, _id=, _a=0x7ffd3021f100) at /usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/build/src/core/KF5AkonadiCore_autogen/include/moc_entitytreemodel.cpp:233 #9 0x7f545db50e75 in QMetaObject::activate (sender=0x55c9d98ae8f0, signalOffset=, local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffd3021f100) at kernel/qobject.cpp:3804 #10 0x7f545db51587 in QMetaObject::activate (sender=, m=m@entry=0x7f5455c16de0 , local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffd3021f100) at kernel/qobject.cpp:3657 #11 0x7f54558b1f25 in Akonadi::Monitor::itemRemoved (this=, _t1=...) at /usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/build/src/core/KF5AkonadiCore_autogen/include/moc_monitor.cpp:950 #12 0x7f54558c0781 in Akonadi::MonitorPrivate::emitToListeners (signal=, this=0x55c9d948e160) at /usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/core/monitor_p.h:404 #13 Akonadi::MonitorPrivate::emitItemsNotification (this=this@entry=0x55c9d948e160, msg_=..., items=..., collection=..., collectionDest=...) at /usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/core/monitor_p.cpp:1077 #14 0x7f54558c188b in Akonadi::MonitorPrivate::emitNotification (this=this@entry=0x55c9d948e160, msg=...) at /usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/core/monitor_p.cpp:558 #15 0x7f54558676fe in Akonadi::ChangeRecorderPrivate::emitNotification (this=0x55c9d948e160, msg=...) at /usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/core/changerecorder_p.cpp:238 #16 0x7f54558bfb7c in Akonadi::MonitorPrivate::dispatchNotifications (this=0x55c9d948e160) at /usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/core/monitor_p.cpp:1003 #17 0x7f545db50e75 in QMetaObject::activate (sender=sender@entry=0x7f5388005030, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3804 #18 0x7f545db51587 in QMetaObject::activate (sender=sender@entry=0x7f5388005030, m=m@entry=0x7f5455c16660 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3657 #19 0x7f54558963c0 in Akonadi::EntityCacheBase::dataAvailable (this=this@entry=0x7f5388005030) at /usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/build/src/core/KF5AkonadiCore_autogen/include/moc_entitycache_p.cpp:151 #20 0x7f545586314a in Akonadi::EntityCache::processResult (this=0x7f5388005030, job=) at /usr/src/debug/akonadi-server-20.04.2-bp153.4.2.1.x86_64/src/core/entitycache_p.h:214 #21 0x7f545db50e75 in QMetaObject::activate (sender=sender@entry=0x55ca1c7e5d80, signalOffset=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffd3021f6c0) at kernel/qobject.cpp:3804 #22 0x7f545db51587 in QMetaObject::activate (sender=sender@entry=0x55ca1c7e5d80, m=m@entry=0x7f545f353580 , local_signal_index=local_signal_index@en
[kmail2] [Bug 456580] New: KMail crashes while updating IMAP folders
https://bugs.kde.org/show_bug.cgi?id=456580 Bug ID: 456580 Summary: KMail crashes while updating IMAP folders Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: fmdefrance...@gmail.com Target Milestone: --- Application: kmail (5.20.2 (22.04.2)) Qt Version: 5.15.5 Frameworks Version: 5.95.0 Operating System: Linux 5.18.9-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.2 [KCrashBackend] -- Information about the crash: KMail crashes at least once in a couple of hours. I see it happens while working to synchronize folders with an IMAP account (gmail.com) The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x7f2637fc21ca in Akonadi::Item::parentCollection() const () from /lib64/libKF5AkonadiCore.so.5 #5 0x7f263805c649 in ?? () from /lib64/libKF5AkonadiCore.so.5 #6 0x7f2638049db8 in ?? () from /lib64/libKF5AkonadiCore.so.5 #7 0x7f26380425b3 in ?? () from /lib64/libKF5AkonadiCore.so.5 #8 0x7f2639f12e9c in ?? () from /lib64/libQt5Core.so.5 #9 0x7f2637fc8d35 in Akonadi::Monitor::itemRemoved(Akonadi::Item const&) () from /lib64/libKF5AkonadiCore.so.5 #10 0x7f2637fdc399 in Akonadi::MonitorPrivate::emitItemsNotification(Akonadi::Protocol::ItemChangeNotification const&, QVector const&, Akonadi::Collection const&, Akonadi::Collection const&) () from /lib64/libKF5AkonadiCore.so.5 #11 0x7f2637fd6e6a in Akonadi::MonitorPrivate::emitNotification(QSharedPointer const&) () from /lib64/libKF5AkonadiCore.so.5 #12 0x7f2637fa1a3e in ?? () from /lib64/libKF5AkonadiCore.so.5 #13 0x7f2637fd62dc in Akonadi::MonitorPrivate::dispatchNotifications() () from /lib64/libKF5AkonadiCore.so.5 #14 0x7f2639f12e6f in ?? () from /lib64/libQt5Core.so.5 #15 0x7f2639f12e9c in ?? () from /lib64/libQt5Core.so.5 #16 0x7f2642d025d5 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #17 0x7f2642d0677b in KJob::finishJob(bool) () from /lib64/libKF5CoreAddons.so.5 #18 0x7f2639f07760 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #19 0x7f263aba541e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7f2639edbfb8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7f2639edef51 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #22 0x7f2639f33c53 in ?? () from /lib64/libQt5Core.so.5 #23 0x7f2634832ea0 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #24 0x7f2634833258 in ?? () from /lib64/libglib-2.0.so.0 #25 0x7f26348332ec in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #26 0x7f2639f33456 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #27 0x7f2639edaa2b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #28 0x7f2639ee2b96 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #29 0x5563ce8e6661 in ?? () #30 0x7f26394405b0 in __libc_start_call_main () from /lib64/libc.so.6 #31 0x7f2639440679 in __libc_start_main_impl () from /lib64/libc.so.6 #32 0x5563ce8e6fc5 in ?? () [Inferior 1 (process 5493) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438874] Disk & Devices applet doesn't show USB removable devices and SD cards after disconnecting and re-connecting them
https://bugs.kde.org/show_bug.cgi?id=438874 --- Comment #42 from Fabio --- > Is there any howto which explains how I can test your merge? > I'm using archlinux. I have no idea about the correct way to do this kind of testing on Arch, but as a dirty hack you can just grab the three updated files from https://invent.kde.org/plasma/plasma-workspace/-/tree/master/applets/devicenotifier/package/contents/ui and replace the ones in your current installation; in my case they are in the /usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui folder. Once the files are replaced, you need to restart plasma for it to pick up the new version. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 436218] Rectangular region grab under xwayland doesn't work
https://bugs.kde.org/show_bug.cgi?id=436218 --- Comment #5 from Fabio --- Yes, the bug is still present. Spectacle is not able to grab a rectangular area screenshot under XWayland. To be honest I switched to using a full wayland session (without xwayland) just to avoid this bug, so it doesn't affect me anymore. Operating System: Slackware 15.0 (current) KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.4 Kernel Version: 5.18.11 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: HP Product Name: HP ProBook 635 Aero G7 Notebook PC -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 353957] Akonadi IMAP resource crashed when checked maildir
https://bugs.kde.org/show_bug.cgi?id=353957 Fabio changed: What|Removed |Added CC||fmdefrance...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 353957] Akonadi IMAP resource crashed when checked maildir
https://bugs.kde.org/show_bug.cgi?id=353957 Fabio changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 436218] Rectangular region grab under xwayland doesn't work
https://bugs.kde.org/show_bug.cgi?id=436218 Fabio changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 441847] No longer possible to change panel launcher icons to a different image
https://bugs.kde.org/show_bug.cgi?id=441847 Fabio changed: What|Removed |Added Assignee|cf...@kde.org |kio-bugs-n...@kde.org Version|unspecified |5.86.0 Product|frameworks-kiconthemes |frameworks-kio CC||ctrlal...@gmail.com Component|general |Properties dialog --- Comment #1 from Fabio --- I verified this bug, it happens with the "icon" applet. The applet tries to set the "filename" lineedit readonly: https://invent.kde.org/plasma/plasma-workspace/-/blob/master/applets/icon/iconapplet.cpp#L561 this causes the lineedit to get set to an empty text: https://invent.kde.org/frameworks/kio/-/blob/master/src/widgets/kpropertiesdialog.cpp#L1242 but because of this signal/slot connection created on the ctor, the ok button gets disabled if the lineedit is empty: https://invent.kde.org/frameworks/kio/-/blob/master/src/widgets/kpropertiesdialog.cpp#L1032 A possible solution would be to disable the connection to the KFilePropsPlugin::nameFileChanged slot when setFileNameReadOnly() gets called. A quick workaround for users to edit the icons: locate the relevant desktop file in ~/.local/share/plasma_icons and run eg: kioclient5 openProperties ~/.local/share/plasma_icons/org.kde.kate.desktop Please don't change the file name, or it will probably break. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442765] Can't delete file on desktop from contestual menu (right mouse button + click "Elimina")
https://bugs.kde.org/show_bug.cgi?id=442765 Fabio changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||ctrlal...@gmail.com --- Comment #5 from Fabio --- I can reproduce the bug. My guess is that OP enabled the "delete" contextual action (from the dolphin options), so in the right-click popup menu he has both the "trash" and "delete" actions available. Move to trash works fine. https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/552 added some code to filter "shift" keypresses and make "shift+trash" works as "delete". Due to this code now also the "delete" action needs an actual shift keypress in order to work; just pressing the menu action "delete" won't actually work. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 428075] [Wayland] Unable to paste to some GTK apps when selecting an entry in klipper
https://bugs.kde.org/show_bug.cgi?id=428075 Fabio changed: What|Removed |Added CC||ctrlal...@gmail.com --- Comment #16 from Fabio --- I can reproduce this problem every single time; it is a mayor annoyance. Is there a way I can help in debugging this issue and getting it fixed? Thank you SOFTWARE/OS VERSIONS Operating System: Slackware Linux -current KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.14 OS Type: 64-bit Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15,0 GiB of RAM Graphics Processor: AMD RENOIR -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 394352] Kopete crashes after chat window close
https://bugs.kde.org/show_bug.cgi?id=394352 Fabio changed: What|Removed |Added CC||ctrlal...@gmail.com --- Comment #2 from Fabio --- SOFTWARE/OS VERSIONS Operating System: Slackware Linux -current KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.14 OS Type: 64-bit Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15,0 GiB of RAM Graphics Processor: AMD RENOIR I can reproduce this issue every time a chat window gets closed. It only happens on a plasma wayland session; no crash under x11. The crash signature is the same: #4 0x7f0fecb35c50 in QScrollArea::widget() const () from /usr/lib64/libQt5Widgets.so.5 #5 0x7f0fc325bf79 in KHTMLView::contentsHeight() const () from /usr/lib64/libKF5KHtml.so.5 #6 0x7f0fd40989d3 in ChatMessagePart::slotScrollView() () from /usr/lib64/libkopetechatwindow_shared.so.1 -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 394352] Kopete crashes after chat window close
https://bugs.kde.org/show_bug.cgi?id=394352 --- Comment #3 from Fabio --- I debugged this issue a bit. There's a workaround, just disabling "Input auto-resize" from the "Format" menu avoids the crash when closing the chat window. The crash is due to KopeteRichTextWidget triggering a size recalc on the chatview of the window that has just been closed; this leads to a call to ChatMessagePart::keepScrolledDown() to ensure the view is scrolled down to the last message. Here's the backtrace up to the method emitting the signal: #0 ChatMessagePart::keepScrolledDown (this=0xd76ba0) at /home/fabio/prj/kopete/kopete/chatwindow/chatmessagepart.cpp:650 #1 0x7fffd81c4324 in ChatView::slotRecalculateSize (this=0x10bda20, difference=0) at /home/fabio/prj/kopete/kopete/chatwindow/chatview.cpp:488 #2 0x7fffd81bf0ab in ChatView::qt_static_metacall (_o=0x10bda20, _c=QMetaObject::InvokeMetaMethod, _id=25, _a=0x7fffbf30) at /home/fabio/prj/kopete/buid/kopete/chatwindow/kopete_chatwindow_autogen/EWIEGA46WW/moc_chatview.cpp:275 #3 0x755d4845 in ?? () from /usr/lib64/libQt5Core.so.5 #4 0x7fffd81641b4 in KopeteRichTextWidget::documentSizeUpdated (this=0xf474c0, _t1=0) at /home/fabio/prj/kopete/buid/kopete/chatwindow/kopetechatwindow_shared_autogen/EWIEGA46WW/moc_kopeterichtextwidget.cpp:250 #5 0x7fffd817c093 in KopeteRichTextWidget::slotDocumentSizeUpdated (this=0xf474c0) at /home/fabio/prj/kopete/kopete/chatwindow/kopeterichtextwidget.cpp:152 #6 0x7fffd8163e6d in KopeteRichTextWidget::qt_static_metacall (_o=0xf474c0, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0x7fffc070) at /home/fabio/prj/kopete/buid/kopete/chatwindow/kopetechatwindow_shared_autogen/EWIEGA46WW/moc_kopeterichtextwidget.cpp:163 #7 0x755d4845 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x755d4845 in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x76294a83 in QWidgetTextControl::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQt5Widgets.so.5 #10 0x755d455d in ?? () from /usr/lib64/libQt5Core.so.5 #11 0x75aa8a1c in QTextDocumentPrivate::finishEdit() () from /usr/lib64/libQt5Gui.so.5 #12 0x76292401 in ?? () from /usr/lib64/libQt5Widgets.so.5 #13 0x7628a32a in QWidgetTextControl::processEvent(QEvent*, QPointF const&, QWidget*) () from /usr/lib64/libQt5Widgets.so.5 #14 0x7626e219 in QTextEdit::inputMethodEvent(QInputMethodEvent*) () from /usr/lib64/libQt5Widgets.so.5 #15 0x760fdace in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #16 0x761a204e in QFrame::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #17 0x7fffd817dd27 in KopeteRichTextWidget::event (this=0xf474c0, event=0x7fffc6d0) at /home/fabio/prj/kopete/kopete/chatwindow/kopeterichtextwidget.cpp:463 #18 0x760c126f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #19 0x755a034a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #20 0x7372051f in ?? () from /usr/lib64/libQt5WaylandClient.so.5 #21 0x760c4f6d in QApplication::setActiveWindow(QWidget*) () from /usr/lib64/libQt5Widgets.so.5 #22 0x760e69e7 in QWidgetPrivate::deactivateWidgetCleanup() () from /usr/lib64/libQt5Widgets.so.5 #23 0x760f2be5 in QWidgetPrivate::hide_sys() () from /usr/lib64/libQt5Widgets.so.5 #24 0x760f9470 in QWidgetPrivate::hide_helper() () from /usr/lib64/libQt5Widgets.so.5 #25 0x760fd868 in QWidgetPrivate::setVisible(bool) () from /usr/lib64/libQt5Widgets.so.5 #26 0x760f98b2 in QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) () from /usr/lib64/libQt5Widgets.so.5 #27 0x76118267 in ?? () from /usr/lib64/libQt5Widgets.so.5 #28 0x760c126f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #29 0x755a034a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #30 0x75980a57 in QGuiApplicationPrivate::processCloseEvent(QWindowSystemInterfacePrivate::CloseEvent*) () from /usr/lib64/libQt5Gui.so.5 #31 0x7595b9d5 in bool QWindowSystemInterfacePrivate::handleWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib64/libQt5Gui.so.5 #32 0x70e4094d in ?? () from /usr/lib64/libffi.so.7 #33 0x70e3ff48 in ?? () from /usr/lib64/libffi.so.7 #34 0x7368deb2 in ?? () from /usr/lib64/libwayland-client.so.0 #35 0x7368a91a in ?? () from /usr/lib64/libwayland-client.so.0 #36 0x7368be6c in wl_display_dispatch_queue_pending () from /usr/lib64/libwayland-client.so.0 #37 0x7370d0c3 in QtWaylandClient::QWaylandDisplay::flushRequests() () from /usr/lib64/libQt5WaylandClient.so.5 #38 0x755d4845 in ?? () from /usr/lib64/libQt5Core.so.5 #39 0x755d7a6f in QSocketNotifier::activated(
[Elisa] [Bug 434436] Add equalizer support
https://bugs.kde.org/show_bug.cgi?id=434436 Fabio changed: What|Removed |Added CC||fabiom...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 434436] Add equalizer support
https://bugs.kde.org/show_bug.cgi?id=434436 Fabio changed: What|Removed |Added Version|20.12.3 |21.08.0 Platform|Other |Neon Packages --- Comment #1 from Fabio --- Elisa is a beautiful software that works fluidly, but urgently needs an equalizer to be perfect I look forward to it, hugs to all developers -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438874] Disk & Devices applet doesn't show USB removable devices and SD cards after disconnecting and re-connecting them
https://bugs.kde.org/show_bug.cgi?id=438874 Fabio changed: What|Removed |Added CC||ctrlal...@gmail.com --- Comment #37 from Fabio --- I just created a merge request that fixes this bug for me. It would be nice if someone could confirm if this is working. https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1039 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 436218] Rectangular region grab under xwayland doesn't work
https://bugs.kde.org/show_bug.cgi?id=436218
Fabio changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|DUPLICATE |---
Status|RESOLVED|REOPENED
--- Comment #3 from Fabio ---
I'm now running spectacle 21.04.2 on plasma 5.22, and the bug is still present.
I saw the introduction of the new PlatformKWinWayland2 interface but it still
uses QGuiApplication::screens() to get the screen name used in the dbus request
to KWin.
When running spectacle in a mixed wayland/xwayland session (as used by suse and
slackware), spectacle will default using the xcb backend.
This means that QGuiApplication::screens() will return the dummy XWayland
screen, while KWin expects to get a request for a Wayland screen name.
This obviously fails.
My current workaround just comments out QGuiApplication::screens() and
hardcodes my laptop screen name QStringLiteral("eDP-1"), but that's obviously a
dirty hack.
I found no way from a qt app running inside xwayland to get the wayland screen
names.
I can see a few possible solutions to this problem:
* let kwin enumerate the available screens somewhere in its dbus interface for
spectacle to pick it up
* always force spectacle to use the wayland backend if available
--
You are receiving this mail because:
You are watching all bug changes.
[Spectacle] [Bug 436218] Rectangular region grab under xwayland doesn't work
https://bugs.kde.org/show_bug.cgi?id=436218 Fabio changed: What|Removed |Added CC||ctrlal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 436218] New: Rectangular region grab under xwayland doesn't work
https://bugs.kde.org/show_bug.cgi?id=436218 Bug ID: 436218 Summary: Rectangular region grab under xwayland doesn't work Product: Spectacle Version: 21.04.0 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: ctrlal...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 137927 --> https://bugs.kde.org/attachment.cgi?id=137927&action=edit dbus-monitor output SUMMARY Some distro (eg slackware, suse) use a "mixed" wayland session, where both the xcb and the wayland platforms are available. Basically each app can decide to start as pure wayland or inside XWayland using xcb. When spectacle is run in XWayland, it is not able to grab rectangle regions. STEPS TO REPRODUCE 1. run spectacle with the xcb platform inside a wayland session 2. try to grab a rectangular region OBSERVED RESULT The correct wayland platform is loaded by looking at XDG_SESSION_TYPE, but something goes wrong during the screen grab. Console output: Error calling KWin DBus interface: "org.kde.kwin.Screenshot.Error.ScreenMissing" "Screen not found" EXPECTED RESULT A rectangle region grab SOFTWARE/OS VERSIONS Operating System: Slackware 14.2 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.12.0 OS Type: 64-bit Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR ADDITIONAL INFORMATION I tried the current master version that uses the new PlatformKWinWayland2, but I still get the same error -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 436218] Rectangular region grab under xwayland doesn't work
https://bugs.kde.org/show_bug.cgi?id=436218 --- Comment #1 from Fabio --- Sorry, my KWin doesn't provide org.kde.KWin.ScreenShot2 so spectacle/master is still using the old PlatformKWinWayland. It looks like before plasma 5.21 the "ractangular region" grab used "screenshotFullscreen" that doesn't require a screen, while now it uses "screenshotScreens" providing a screen obtained from QGuiApplication::screens(). I suspect the problem is due to QGuiApplication::screens() returning the Xwayland screen instead of the Wayland one. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 478580] RDP connection fails with cliprdr error
https://bugs.kde.org/show_bug.cgi?id=478580 Fabio changed: What|Removed |Added CC||ctrlal...@gmail.com --- Comment #2 from Fabio --- Created attachment 16 --> https://bugs.kde.org/attachment.cgi?id=16&action=edit 1-minute patch -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 478580] RDP connection fails with cliprdr error
https://bugs.kde.org/show_bug.cgi?id=478580 --- Comment #3 from Fabio --- I'm having the same issue; some investigation lead to this method on the freerdp sample client: https://github.com/FreeRDP/FreeRDP/blob/master/client/Sample/tf_channels.c#L41 I've attached a 1-minute patch that reproduces the same code in krdc; it avoid the error, so now the connection works, but i didn't check if there are any implications. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 477915] Can't mount encrypted drives
https://bugs.kde.org/show_bug.cgi?id=477915 Fabio changed: What|Removed |Added CC||ctrlal...@gmail.com --- Comment #9 from Fabio --- I was bitten by this same bug, recompiling Solid with https://invent.kde.org/frameworks/solid/-/merge_requests/134 fixed the issue for me. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 473505] New: KMail crashes while synchronizing IMAP folders
https://bugs.kde.org/show_bug.cgi?id=473505 Bug ID: 473505 Summary: KMail crashes while synchronizing IMAP folders Classification: Applications Product: kmail2 Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: fmdefrance...@gmail.com Target Milestone: --- Application: kmail (5.23.3 (23.04.3)) Qt Version: 5.15.10 Frameworks Version: 5.108.0 Operating System: Linux 6.4.9-1-default x86_64 Windowing System: X11 Distribution: openSUSE Tumbleweed DrKonqi: 5.27.7 [KCrashBackend] -- Information about the crash: KMail crashes while synchronizing IMAP folders. The user were not present at the keyboard. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x7fcb8c08d56a in Akonadi::Item::parentCollection() const () at /lib64/libKPim5AkonadiCore.so.5 #5 0x7fcb8c129a99 in () at /lib64/libKPim5AkonadiCore.so.5 #6 0x7fcb8c115ad8 in () at /lib64/libKPim5AkonadiCore.so.5 #7 0x7fcb8c10f723 in () at /lib64/libKPim5AkonadiCore.so.5 #8 0x7fcb8df257b3 in () at /lib64/libQt5Core.so.5 #9 0x7fcb8c093f35 in Akonadi::Monitor::itemRemoved(Akonadi::Item const&) () at /lib64/libKPim5AkonadiCore.so.5 #10 0x7fcb8c0a71a9 in Akonadi::MonitorPrivate::emitItemsNotification(Akonadi::Protocol::ItemChangeNotification const&, QVector const&, Akonadi::Collection const&, Akonadi::Collection const&) () at /lib64/libKPim5AkonadiCore.so.5 #11 0x7fcb8c0a2133 in Akonadi::MonitorPrivate::emitNotification(QSharedPointer const&) () at /lib64/libKPim5AkonadiCore.so.5 #12 0x7fcb8c06cf8e in () at /lib64/libKPim5AkonadiCore.so.5 #13 0x7fcb8c0a11fc in Akonadi::MonitorPrivate::dispatchNotifications() () at /lib64/libKPim5AkonadiCore.so.5 #14 0x7fcb8df25812 in () at /lib64/libQt5Core.so.5 #15 0x7fcb8df257b3 in () at /lib64/libQt5Core.so.5 #16 0x7fcb96da9845 in KJob::result(KJob*, KJob::QPrivateSignal) () at /lib64/libKF5CoreAddons.so.5 #17 0x7fcb96dadbeb in () at /lib64/libKF5CoreAddons.so.5 #18 0x7fcb8df19320 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #19 0x7fcb8eba519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #20 0x7fcb8deed568 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #21 0x7fcb8def0b61 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #22 0x7fcb8df46c93 in () at /lib64/libQt5Core.so.5 #23 0x7fcb89d2b9b8 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #24 0x7fcb89d2bdc8 in () at /lib64/libglib-2.0.so.0 #25 0x7fcb89d2be5c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #26 0x7fcb8df464a6 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #27 0x7fcb8deebffb in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #28 0x7fcb8def4490 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #29 0x55755f7b8841 in () #30 0x7fcb8d4281f0 in __libc_start_call_main () at /lib64/libc.so.6 #31 0x7fcb8d4282b9 in __libc_start_main_impl () at /lib64/libc.so.6 #32 0x55755f7b91d5 in () [Inferior 1 (process 5948) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 448328] New: loading albums at startup extremely long, after forced application kill
https://bugs.kde.org/show_bug.cgi?id=448328 Bug ID: 448328 Summary: loading albums at startup extremely long, after forced application kill Product: digikam Version: 7.4.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-Engine Assignee: digikam-bugs-n...@kde.org Reporter: fabio.for...@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 *** After using digiKam for few times, I have extremely long boot time, the splash screen is blocked on "loading Albums". The animation of the three blue circles is not moving. STEPS TO REPRODUCE 1. Start to use digiKam, with new database. 2. use the "detect duplicates function 3. when the 100% is reached, the program does not respond, and the progress bar is blocked on 100% 4. upon forced kill and reboot the loading time is long, with no moving circles in the splashscreen animation 5. the time grows over time, and after several sessions it becomes as long as 5 or 10 minutes OBSERVED RESULT Around 1 or 2 minutes of loading time at startup EXPECTED RESULT few seconds of loading time at startup SOFTWARE/OS VERSIONS Linux/KDE Plasma: Mint 20.2 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.15.3 ADDITIONAL INFORMATION I have SQLlite database, with around 70'000 images -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 423892] New: GTK apps not displaying menus
https://bugs.kde.org/show_bug.cgi?id=423892 Bug ID: 423892 Summary: GTK apps not displaying menus Product: kded-appmenu Version: 5.19.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: top menubar Assignee: plasma-b...@kde.org Reporter: slayer.dasi...@gmail.com Target Milestone: --- SUMMARY gimp and transmission (gtk) won't display menus at the top bar when opened, but after minimized and maximized again, menus will show STEPS TO REPRODUCE 1. open gimp or transmission-gtk 2. minimize/maximize again OBSERVED RESULT when first opened some gtk apps will not show menus at the top bar but after minimized once, they will EXPECTED RESULT menus show upon app opening SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch/ 5.19.2 (available in About System) KDE Plasma Version: 5.19.2 KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 411593] wxgtk3 apps don't have global menus
https://bugs.kde.org/show_bug.cgi?id=411593 fabio changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||slayer.dasi...@gmail.com --- Comment #2 from fabio --- confirmed in plasma 5.19.2 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 438716] Lid close leads to suspend even when external monitor is attached
https://bugs.kde.org/show_bug.cgi?id=438716 Fabio changed: What|Removed |Added CC||ctrlal...@gmail.com --- Comment #18 from Fabio --- I'm experiencing the same issue on 5.23.5. The cause of the issue is that the external monitor is reported of an "unknown" type, and so it's not considered as an external monitor. Basically reverting this fixes the issue: https://invent.kde.org/plasma/powerdevil/-/commit/d3162725cfffb79da7bb8f276a31a915e3349dab Of course reverting this will break suspend for the original post of the bug. A better fix would be to correctly detect the monitor type, but how? Maybe a possible workaround would be to check if: * there's only one "unkown" monitor connected => that's possibly the laptop panel => then suspend * there's more than one monitor connected, and one of them is type "unkown" => that's possibly an external monitor => don't suspend -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 438716] Lid close leads to suspend even when external monitor is attached
https://bugs.kde.org/show_bug.cgi?id=438716 --- Comment #21 from Fabio --- (In reply to Kai Uwe Broulik from comment #19) > Can you provide the output of kscreendoctor -o and xrandr -q > > Maybe there's some exotic connector type that we don't know. The heuristic > for identifying monitor types is in > https://invent.kde.org/plasma/libkscreen/-/blob/master/backends/utils.cpp kscreen-dotctor -o --- Output: 1 AU Optronics eDP-1-sconosciuto enabled connected Panel Modes: 0:1920x1080@40 1:1680x1050@60 2:1280x1024@60 3:1440x900@60 4:1280x800@60 5:1280x720@60 6:1024x768@60 7:800x600@60 8:640x480@60 9:1920x1080@60*! Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 2 BNQ BenQ GW2780/ETP9L04484SL enabled connected primary Unknown Modes: 0:1920x1080@60 1:1920x1080@60 10:1280x720@60 11:1280x720@60 12:1280x720@60 13:1280x720@50 14:1024x768@75 15:1024x768@60 16:832x624@75 17:800x600@75 18:800x600@60 19:720x576@50 2:1920x1080@50 20:720x576@50 21:720x480@60 22:720x480@60 23:720x480@60 24:720x480@60 25:720x480@60 26:640x480@75 27:640x480@60 28:640x480@60 29:640x480@60 3:1680x1050@60 30:720x400@70 31:1920x1080@60*! 4:1600x900@60 5:1280x1024@75 6:1280x1024@60 7:1440x900@60 8:1280x800@60 9:1152x864@75 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown primary --- xrandr -q --- Screen 0: minimum 16 x 16, current 1920 x 1080, maximum 32767 x 32767 XWAYLAND1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 600mm x 340mm 1920x1080 59.96*+ ... XWAYLAND2 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 290mm x 170mm 1920x1080 59.96*+ ... --- -- You are receiving this mail because: You are watching all bug changes.
[plasma-simplemenu] [Bug 490251] New: I don't move the icons anymore
https://bugs.kde.org/show_bug.cgi?id=490251 Bug ID: 490251 Summary: I don't move the icons anymore Classification: Plasma Product: plasma-simplemenu Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: h...@kde.org Reporter: fabiom...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 171646 --> https://bugs.kde.org/attachment.cgi?id=171646&action=edit I don't move the icons anymore In the full screen application launcher it is no longer possible to drag favorite application icons to organize them to our liking KDEneon 6.1.2 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 490251] I don't move the icons anymore
https://bugs.kde.org/show_bug.cgi?id=490251 --- Comment #2 from Fabio --- Yes, I can add and remove from favorites, the problem is only when organizing the favorites that I can't drag the icons to the position I want Em 14/07/2024 13:16, bugzilla_nore...@kde.org escreveu: > https://bugs.kde.org/show_bug.cgi?id=490251 > > duha.b...@gmail.com changed: > > What|Removed |Added > > CC||duha.b...@gmail.com > > --- Comment #1 fromduha.b...@gmail.com --- > Can you right click and add to favorite or does this not work either? > -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 428075] [Wayland] Unable to paste to some GTK apps when selecting an entry in klipper
https://bugs.kde.org/show_bug.cgi?id=428075 --- Comment #17 from Fabio --- Just submitted a proposal fix: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/676 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 410364] New: Shortcut to edit DOI
https://bugs.kde.org/show_bug.cgi?id=410364 Bug ID: 410364 Summary: Shortcut to edit DOI Product: KBibTeX Version: 0.9 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: fisc...@unix-ag.uni-kl.de Reporter: x95a31x...@gmail.com Target Milestone: --- Hello, Is it possible to add an entry to edit the element's DOI in the "Element Entry -> Publication" window? Best regards -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 410364] Shortcut to edit DOI
https://bugs.kde.org/show_bug.cgi?id=410364 Fabio changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Fabio --- There is ad-hoc table to manage DOI in "Element Entry -> External". -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 410472] New: MiniZinc syntax highlight
https://bugs.kde.org/show_bug.cgi?id=410472 Bug ID: 410472 Summary: MiniZinc syntax highlight Product: kate Version: 19.04.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: x95a31x...@gmail.com Target Milestone: --- Hello, Is it possible to add the syntax highlight for the MiniZinc/FlatZinc language? - Here there is the reference manual of the language: https://www.minizinc.org/doc-latest/en/part_4_reference.html - Here there is an open-source IDE made with Qt: https://github.com/MiniZinc/MiniZincIDE Best regards -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 411337] New: Scale factor per display not applied
https://bugs.kde.org/show_bug.cgi?id=411337 Bug ID: 411337 Summary: Scale factor per display not applied Product: KScreen Version: 1.0.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: se...@kde.org Reporter: x95a31x...@gmail.com Target Milestone: --- SUMMARY The scale factor used is the last scale factor set via System Settings, regardless of which monitor is connected. STEPS 1. Connect a second display. 2. Set the scale factor to 1 for the main display 2. Set the scale factor to 2 for the second display 3. Boot the system with only the first display connected OBSERVED RESULT The GUI is rendered with scale factor 2 EXPECTED RESULT The GUI is rendered with scale factor 1 ADDITIONAL INFORMATION The current scale factor and the displays scale factor are correctly saved in .config/kdeglobals under the [KScreen] section. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 411337] Scale factor per display not applied
https://bugs.kde.org/show_bug.cgi?id=411337 --- Comment #2 from Fabio --- No, I am on X11 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 419674] Open dolphin crash
https://bugs.kde.org/show_bug.cgi?id=419674 Fabio changed: What|Removed |Added CC||carniani.fa...@gmail.com --- Comment #1 from Fabio --- Created attachment 128030 --> https://bugs.kde.org/attachment.cgi?id=128030&action=edit log file created with valgrind -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 416405] New: kmix controls won't respond to mouse wheel scroll
https://bugs.kde.org/show_bug.cgi?id=416405 Bug ID: 416405 Summary: kmix controls won't respond to mouse wheel scroll Product: kmix Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: es...@kde.org Reporter: slayer.dasi...@gmail.com Target Milestone: --- SUMMARY Volume controls will not respond to mouse wheel. STEPS TO REPRODUCE 1. click on kmix 2. try to change the volume with the mouse wheel scroll 3. OBSERVED RESULT a sound efect is played but volume levels won't change 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.
[plasmashell] [Bug 385920] Plasma Wayland: Mouse cursor huge when hovering over Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=385920 Fabio changed: What|Removed |Added CC||fabio96...@gmail.com --- Comment #16 from Fabio --- (In reply to Dr. Chapatin from comment #14) > Same bug in plasma 5.12 beta, Arch Linux. > Cursor is bigger when I hover any native Wayland software (except its window > decoration). > Xwayland softwares are not affected. Same thing happening to me on the same system (latest Arch with Plasma 5.11.95). Setting the breeze cursor to 24 instead of "resolution dependent" in systemsettings fixed it. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 386432] Broken google scholar search
https://bugs.kde.org/show_bug.cgi?id=386432 --- Comment #7 from Fabio --- (In reply to Thomas Fischer from comment #6) > > I cannot access to the commit. Following the link I get: "Bad object id: > > 9e95172cef34ac" > > cgit.kde.org doesn't seem to be up to date (latest commits shown are from > 2016, definitively outdated). > Therefore, manually check out repository > clones/kbibtex/thomasfischer/kbibtex.git from KDE's Git. There you will find > a branch 'bugs/kde386432' which contains this commit. Cloned, compiled and executed. Not working, probably due to bad libraries. This is the output from command line: KGlobal::locale(): Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work kbibtex(5113) DocumentPreview::DocumentPreviewPrivate::setupGUI: No 'KDE 4'-based Okular part for PDF or PostScript document preview available. kbibtex(5113)/kdecore (KLibrary) findLibraryInternal: plugins should not have a 'lib' prefix: "libkhtmlpart.so" kbibtex(5113)/kdecore (KLibrary) kde4Factory: The library "/usr/lib/kde4/kbibtexpart.so" does not offer a qt_plugin_instance function. kbibtex(5113)/kdeui (KAction) KActionCollection::setComponentData: this does not work on a KActionCollection containing actions! kbibtex(5113) BibUtils::available: No or only an incomplete installation of BibUtils found kbibtex(5113) OnlineSearchAbstract::iconDownloadFinished: Could not download icon "https://isbndb.com/favicon.ico"; kbibtex(5113)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0x56422c6a5900 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. *** Error in `./kbibtex': double free or corruption (!prev): 0x56422c721860 *** KCrash: Application 'kbibtex' crashing... Fatal Error: Accessed global static 'KGlobalPrivate *globalData()' after destruction. Defined at /build/kdelibs/src/kdelibs-4.14.37/kdecore/kernel/kglobal.cpp:128 Unable to start Dr. Konqi -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 385875] New: Multitouch gestures
https://bugs.kde.org/show_bug.cgi?id=385875 Bug ID: 385875 Summary: Multitouch gestures Product: kdeconnect Version: unspecified Platform: Android OS: Android 7.x Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: x95a31x...@gmail.com Target Milestone: --- Hello, I am opening this feature request (another one will be open for Okular) because I would like use the remote control extension to move to the next/previous slide of my presentations by swiping left/right on the touchscreen of my smartphone. Moreover it would be nice use also the pinch to zoom gesture to zoom in/out. Is possible add this gestures to the remote control extension? Best regards -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 385877] New: Multitouch gestures
https://bugs.kde.org/show_bug.cgi?id=385877 Bug ID: 385877 Summary: Multitouch gestures Product: okular Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: x95a31x...@gmail.com Target Milestone: --- Hello, I am opening this feature request (another one will be open for KDEConnect) because I would like use the remote control extension to move to the next/previous slide of my presentations by swiping left/right on the touchscreen of my smartphone. Moreover it would be nice use also the pinch to zoom gesture to zoom in/out. Is possible modify Okular to handle these gestures? Best regards -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 385877] Multitouch gestures
https://bugs.kde.org/show_bug.cgi?id=385877 --- Comment #3 from Fabio --- None left to track :) -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 386432] New: Broken google scholar search
https://bugs.kde.org/show_bug.cgi?id=386432 Bug ID: 386432 Summary: Broken google scholar search Product: KBibTeX Version: 0.6 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Network/online search Assignee: fisc...@unix-ag.uni-kl.de Reporter: x95a31x...@gmail.com Target Milestone: --- I was looking for "A preliminary review of literature on parallel constraint solving" but not resoult found. From the website I can found it. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 386432] Broken google scholar search
https://bugs.kde.org/show_bug.cgi?id=386432 --- Comment #5 from Fabio --- (In reply to Thomas Fischer from comment #4) > (In reply to Fabio from comment #0) > > I was looking for "A preliminary review of literature on parallel constraint > > solving" but not resoult found. From the website I can found it. > > Before diving into the IEEE issue, let's first fix Google Scholar. > I made a fix for the kbibtex/0.7 branch which fixes the problem for me: > https://commits.kde.org/clones/kbibtex/thomasfischer/kbibtex/9e95172cef34ac > (not yet the official repo!) > Please test and confirm if it is working, then I'll forward-port the fix to > the master branch. I cannot access to the commit. Following the link I get: "Bad object id: 9e95172cef34ac" -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 364680] feature request: restore previous session
https://bugs.kde.org/show_bug.cgi?id=364680 Fabio changed: What|Removed |Added CC||fabio96...@gmail.com --- Comment #1 from Fabio --- I would also love this feature. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 377886] Store text along with annotations like highlight, underline and squiggle
https://bugs.kde.org/show_bug.cgi?id=377886 Fabio changed: What|Removed |Added CC||fabio.muccia...@gmail.com --- Comment #1 from Fabio --- Yes please, this is important to give a sense to annotations. I would also suggest to default that text to the original selected text (or at least a short amount), and display it directly in the annotation tree at the place of page number. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 382691] New: ktorrent crash when trying to activate scheduler plugin
https://bugs.kde.org/show_bug.cgi?id=382691 Bug ID: 382691 Summary: ktorrent crash when trying to activate scheduler plugin Product: ktorrent Version: 5.0 Platform: Slackware Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: slayer.dasi...@gmail.com Target Milestone: --- trying to activate scheduler plugin will cause ktorrent to crash -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482137] Regression: Filesystem/Clipboard not shared anymore
https://bugs.kde.org/show_bug.cgi?id=482137 --- Comment #21 from Fabio --- (In reply to Marcel Hasler from comment #20) > I guess that warning came too late, the same thing is in fact already being > done in other places. As a test I printed the proxy and gateway settings > with qDebug() just before the call to freerdp_connect(). As expected the > output is complete garbage and after the message that it cannot connect, > krdc crashes. > > According to the sources it looks like freerdp actually takes ownership of > all settings strings and frees them on exit, so using strdup (or _strdup > from or std::strdup once available) would be the correct > solution here. Thank you for checking the rest of the code. A MR is already queued that adds support for freerdp3 and also changes the way all the settings are set, using freerdp_settings_set_string() that internally calls update_string_copy_(), so that freerdp creates its own copy of the char* when they still exists. I guess that should fix the other issues you found, see eg.: https://invent.kde.org/network/krdc/-/merge_requests/113/diffs?commit_id=e1c9965f52d0aa7e2e0d9d02f9b4417914ea8748#22035f78003a0693934d972e85db265b9deaa2f4_474_574 > > qstrdup is already used for ServerHostname, Username and Password. I would, > however, recommend using C strdup, because qstrdup uses new[] to allocate > the string which should be deallocated with delete[] accordingly, whereas > freerdp naturally uses free() instead. So using qstrdup to copy the strings > would once again be UB. Thanks, will integrate this in the MR -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482137] Regression: Filesystem/Clipboard not shared anymore
https://bugs.kde.org/show_bug.cgi?id=482137 --- Comment #7 from Fabio --- (In reply to Marcel Hasler from comment #6) > This is a bug in RdpSession::start(). I confirm your patch fixes the issue. A small variant has been submitted here: https://invent.kde.org/network/krdc/-/merge_requests/114 > 3. The pointer returned by m_preferences->shareMedia().toLocal8Bit().data() > is no longer valid by the time it's passed to > freerdp_client_add_device_channel, since it references a temporary object > that no longer exists at this point FreeRDP internally calls _strdup on that parameter in https://github.com/FreeRDP/FreeRDP/blob/stable-2.0/client/common/cmdline.c#L185 , so it's safe to use -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482137] Regression: Filesystem/Clipboard not shared anymore
https://bugs.kde.org/show_bug.cgi?id=482137 Fabio changed: What|Removed |Added Version Fixed In||24.08.3 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #8 from Fabio --- Fix has been merged and backported; will be available in 24.08.3, expected release on november 7 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482137] Regression: Filesystem/Clipboard not shared anymore
https://bugs.kde.org/show_bug.cgi?id=482137 --- Comment #10 from Fabio --- (In reply to Marcel Hasler from comment #9) > But here's a simple example to show that you cannot rely on the data > remaining valid: I know that when the local function variable goes out of scope it's not safe to use anymore. FreeRDP creates an internal duplicate of the "path" string using _strdup(): > if ((!isPath && !isSpecial) || !(drive->Path = _strdup(path))) >From that point FreeRDP will use its internal copy of the string stored in drive->Path. So, even if our variable gets deleted, it doesn't matter. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482137] Regression: Filesystem/Clipboard not shared anymore
https://bugs.kde.org/show_bug.cgi?id=482137 --- Comment #18 from Fabio --- Looking at the third test case I finally got your point. Thank you for your patience Fixed in https://invent.kde.org/network/krdc/-/merge_requests/116/diffs -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482137] Regression: Filesystem/Clipboard not shared anymore
https://bugs.kde.org/show_bug.cgi?id=482137 --- Comment #12 from Fabio --- (In reply to Marcel Hasler from comment #11) > The point I was trying to make is that by the time freerdp actually calls > _strdup, both temporary QByteArray instances have already been destroyed and > the pointers are therefore no longer valid. It's true in your code example in https://bugs.kde.org/show_bug.cgi?id=482137#c9 because of the curly braces specifically added to declare data1 inside a different scope. It's not true in the code used in the fix for krdc: https://invent.kde.org/network/krdc/-/merge_requests/114/diffs -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 496656] Keyboard no longer works in remote systems
https://bugs.kde.org/show_bug.cgi?id=496656 --- Comment #4 from Fabio --- Can i ask you again the krdc version it should be something like 24.05.x or 24.08.x -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 496656] Keyboard no longer works in remote systems
https://bugs.kde.org/show_bug.cgi?id=496656 --- Comment #10 from Fabio --- Thank you for the video, it made me realize what broke the keyboard handling for you (spoiler: focus interaction with the "remote desktops" left sidebar). https://invent.kde.org/network/krdc/-/merge_requests/131 fixes this issue, so now keypresses works also then "grab keys" is disabled. One problem left: from your video "grab keys" steals keypresses from other windows even when krdc is not focused. I've not been able to reproduce this problem yet, but it's the next thing i'm working on. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 496692] Most of default shortcuts should be set to None or something that is never used
https://bugs.kde.org/show_bug.cgi?id=496692 Fabio changed: What|Removed |Added CC||ctrlal...@gmail.com --- Comment #2 from Fabio --- https://invent.kde.org/network/krdc/-/merge_requests/134 fixes this issue for me, overriding application shortcuts when "grab keys" is enabled. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 496692] Most of default shortcuts should be set to None or something that is never used
https://bugs.kde.org/show_bug.cgi?id=496692 Fabio changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||24.12 Latest Commit||https://invent.kde.org/netw ||ork/krdc/-/commit/af52d0b1b ||15228a2170dbbf83d4bdd1fd4ce ||b763 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 494230] [wayland] wlfreerdp window has wrong size if global global scaling is used
https://bugs.kde.org/show_bug.cgi?id=494230 Fabio changed: What|Removed |Added Resolution|--- |FIXED CC||ctrlal...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Fabio --- Krdc doesn't use xfreerdp/wlfreerdp anymore since version 24.02. It now directly links to libfreerdp, and fixes has been added to correctly support scaling even on wayland. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 475878] krdc doesn't send correct username if it contains backslash
https://bugs.kde.org/show_bug.cgi?id=475878 Fabio changed: What|Removed |Added Version Fixed In||24.02 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 492822] KRDC drastic changes to program after latest update from update manager - Linux Mint flatpak
https://bugs.kde.org/show_bug.cgi?id=492822 Fabio changed: What|Removed |Added CC||ctrlal...@gmail.com --- Comment #1 from Fabio --- The option dialog has changed to make room for the newly added options. It can be improved, since adding new options is making the dialog too crowded. We'll probably address this in a future version. Folder share has been fixed in 24.08.3 Regarding to the "grab keys" problems: * are you running krdc under X or Wayland? * what version were you using before? -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 491514] Gateway settings not used for RDP
https://bugs.kde.org/show_bug.cgi?id=491514 Fabio changed: What|Removed |Added Resolution|--- |FIXED CC||ctrlal...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Fabio --- Will be fixed in v24.12, thank you Commit: https://invent.kde.org/network/krdc/-/commit/a51c6201f292740eb51b741bc5d97b9be658d7cd -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 Fabio changed: What|Removed |Added Resolution|--- |LATER Status|CONFIRMED |RESOLVED CC||ctrlal...@gmail.com --- Comment #26 from Fabio --- Trying to sum this up: Krdc < 24 internally runs a copy of xfreerdp, so as log as xfreerdp works, krdc works too. Since version 24 krdc uses the libfreerdp library directly. If you were not able to connect or you get disconnected immediately / after some time: initial libfreerdp support was barebone and a few bugs causing disconnections were found and fixed in the following versions. We are still working out such bugs, eg. v24.12 will fix a disconnection bug on touchpad scroll. If you are ale to connect but get a black/blue screen or screen artifacts (on wayland): this is caused by a wrong/mismatched acceleration or security setting. Regarding acceleration, avoid H.264 and try to use RemoteFX or disable acceleration and it should work. Regarding security, automatic negotiation has seen fixes and should be working now. We already implemented an option to manually set the security method and it will be released in a future version. I'm closing this bug since it became a mess of different reports related to different bugs. Some of them have already been fixed as of v24.08.3 / v24.12, so I encourage everyone to try again using one of these versions and open a new bug if you are still experiencing problems. Thank you for your patience. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 496656] Keyboard no longer works in remote systems
https://bugs.kde.org/show_bug.cgi?id=496656 Fabio changed: What|Removed |Added CC||ctrlal...@gmail.com --- Comment #1 from Fabio --- Pleae reportd krdc / qt version; you can find them in Help menu -> about krdc Also, what DE are you running? gnome on wayland? -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 496656] Keyboard no longer works in remote systems
https://bugs.kde.org/show_bug.cgi?id=496656 --- Comment #7 from Fabio --- I've just sent a change implementing the "cursor shape": https://invent.kde.org/network/krdc/-/merge_requests/130 About the keyboard grab problem, I've not been able to reproduce the problem on plasma/wayland, plasma/x11 and xfce/x11. I'll try to create a fedora 41/mate vm and test on it. -- You are receiving this mail because: You are watching all bug changes.
[KPublicTransport] [Bug 497034] New: Compile error with Protobuf 29
https://bugs.kde.org/show_bug.cgi?id=497034
Bug ID: 497034
Summary: Compile error with Protobuf 29
Classification: Frameworks and Libraries
Product: KPublicTransport
Version: 24.08.3
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: vkra...@kde.org
Reporter: ctrlal...@gmail.com
Target Milestone: ---
SUMMARY
Trying to compile KPublicTransport 24.08.3 using protobuf 29 causes the
following error:
[ 9%] Building CXX object
src/osm/io/CMakeFiles/KOSM_pbfioplugin.dir/__/osmpbfparser.cpp.o
In file included from /usr/include/absl/log/internal/vlog_config.h:37,
from /usr/include/absl/log/absl_vlog_is_on.h:61,
from /usr/include/absl/log/internal/log_impl.h:18,
from /usr/include/absl/log/absl_log.h:36,
from /usr/include/google/protobuf/io/coded_stream.h:107,
from
/tmp/kde_build/applications/kpublictransport-24.08.3/cmake-build/src/osm/io/fileformat.pb.h:20,
from
/tmp/kde_build/applications/kpublictransport-24.08.3/src/osm/osmpbfparser.cpp:9:
/usr/include/google/protobuf/message_lite.h: In instantiation of ‘MessageLite*
google::protobuf::internal::MessageCreator::PlacementNew(const MessageLite*,
const MessageLite*, void*, google::protobuf::Arena*) const [with bool test_call
= false; MessageLite = google::protobuf::MessageLite]’:
/usr/include/google/protobuf/message_lite.h:415:40: required from here
415 | return message_creator.PlacementNew(prototype, prototype, mem,
arena);
|
^~
/usr/include/google/protobuf/message_lite.h:1202:7: error: ambiguous overload
for ‘operator<’ (operand types are ‘const
google::protobuf::internal::MessageCreator::Tag’ and ‘int’)
1202 | if (ABSL_PREDICT_FALSE(kMustBeFunc || as_tag < 0)) {
| ^~
/usr/include/google/protobuf/message_lite.h:1202:7: note: candidate:
‘operator<(int, int)’ (built-in)
In file included from
/tmp/kde_build/applications/kpublictransport-24.08.3/src/osm/osmpbfparser.h:11,
from
/tmp/kde_build/applications/kpublictransport-24.08.3/src/osm/osmpbfparser.cpp:7:
/tmp/kde_build/applications/kpublictransport-24.08.3/src/osm/datatypes.h:464:13:
note: candidate: ‘bool OSM::operator<(const Elem&, Id) [with Elem =
google::protobuf::internal::MessageCreator::Tag; Id = long int]’
464 | inline bool operator<(const Elem &elem, Id id)
| ^~~~
make[2]: *** [src/osm/io/CMakeFiles/KOSM_pbfioplugin.dir/build.make:157:
src/osm/io/CMakeFiles/KOSM_pbfioplugin.dir/__/osmpbfparser.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:780:
src/osm/io/CMakeFiles/KOSM_pbfioplugin.dir/all] Error 2
make: *** [Makefile:136: all] Error 2
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Slackware64-current
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.1
--
You are receiving this mail because:
You are watching all bug changes.
[KPublicTransport] [Bug 497034] Compile error with Protobuf 29
https://bugs.kde.org/show_bug.cgi?id=497034 --- Comment #2 from Fabio --- I confirm the commit fixes the compilation issue. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 331576] password needed at dialog every connect
https://bugs.kde.org/show_bug.cgi?id=331576 Fabio changed: What|Removed |Added CC||ctrlal...@gmail.com --- Comment #11 from Fabio --- This weird behavior is caused by the way krdc stores connections. Connections are identified by the URL specified by the user, eg. rdp://192.168.1.1 or rdp://user@192.168.1.1 The username is retrieved from the URL, so if it's not present you will be asked at every connection to specify it again. I've tried as workaround to force the username specified in the "request password dialog" in the saved URL, and it works, but this causes duplicate connections being saved. Other problems exists in the way connections are stored, eg. there's no way to edit an existing connection URL. I guess this section needs a major overhaul. In the meanwhile, ensure the username is specified in the connection URL to ensure it will get saved. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 497111] Refactored unpressModifiers ignores nativeVirtualKey which is required by VNC plugin
https://bugs.kde.org/show_bug.cgi?id=497111 --- Comment #2 from Fabio --- Hello Luke, can you please confirm if https://invent.kde.org/network/krdc/-/merge_requests/138 fixes the issue for you? Thank you -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 497111] Refactored unpressModifiers ignores nativeVirtualKey which is required by VNC plugin
https://bugs.kde.org/show_bug.cgi?id=497111 Fabio changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/krdc/-/commit/bcee020d2 |ork/krdc/-/commit/e1576b40e |79392e87a933e3be9e1f8593fe8 |0fe36c9eda610c74fc524bbffd2 |75ea|b7d4 --- Comment #4 from Fabio --- Git commit e1576b40e0fe36c9eda610c74fc524bbffd2b7d4 by Fabio Bas. Committed on 07/12/2024 at 14:29. Pushed by ctrlaltca into branch 'release/24.12'. Add the nativeVirtualKey value to fake keyrelease events generated to unpress modifiers They are needed for the vnc backend to properly handle the keys (cherry picked from commit bcee020d279392e87a933e3be9e1f8593fe875ea) 84a4c377 Add the nativeVirtualKey value to fake keyrelease events generated to unpress modifiers; Co-authored-by: Fabio Bas M +5-3core/remoteview.cpp M +6-1core/remoteview.h https://invent.kde.org/network/krdc/-/commit/e1576b40e0fe36c9eda610c74fc524bbffd2b7d4 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 497111] Refactored unpressModifiers ignores nativeVirtualKey which is required by VNC plugin
https://bugs.kde.org/show_bug.cgi?id=497111 Fabio changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/netw ||ork/krdc/-/commit/bcee020d2 ||79392e87a933e3be9e1f8593fe8 ||75ea Status|ASSIGNED|RESOLVED --- Comment #3 from Fabio --- Git commit bcee020d279392e87a933e3be9e1f8593fe875ea by Fabio Bas. Committed on 07/12/2024 at 14:29. Pushed by ctrlaltca into branch 'master'. Add the nativeVirtualKey value to fake keyrelease events generated to unpress modifiers They are needed for the vnc backend to properly handle the keys M +5-3core/remoteview.cpp M +6-1core/remoteview.h https://invent.kde.org/network/krdc/-/commit/bcee020d279392e87a933e3be9e1f8593fe875ea -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 493346] linux -> windows rdp session graphical bugs
https://bugs.kde.org/show_bug.cgi?id=493346 --- Comment #4 from Fabio --- Currently krdc can be built against last freerdp3 version where this bug is fixed. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 497111] Refactored unpressModifiers ignores nativeVirtualKey which is required by VNC plugin
https://bugs.kde.org/show_bug.cgi?id=497111 Fabio changed: What|Removed |Added Version Fixed In||24.12.1 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 498058] Compiling issue for v3.2.0 Qt6
https://bugs.kde.org/show_bug.cgi?id=498058 --- Comment #4 from Fabio --- Nice, it is compiling fine and running with GCC but fail with Clang: [ 91%] Building CXX object tests/importers/CMakeFiles/testbansheeimporter.dir/__/__/src/importers/banshee/BansheeConfigWidget.cpp.o /home/fabio/Dev/Github/PKGBUILD-AUR_fix/a/amarok-qt6-git/src/amarok/tests/importers/TestImporterBase.cpp:404:51: error: parameter declarator cannot be qualified 404 | const QString testName( QLatin1String( QTest::currentDataTag() ) ); |~~~^ /home/fabio/Dev/Github/PKGBUILD-AUR_fix/a/amarok-qt6-git/src/amarok/tests/importers/TestImporterBase.cpp:404:27: warning: parentheses were disambiguated as a function declaration [-Wvexing-parse] 404 | const QString testName( QLatin1String( QTest::currentDataTag() ) ); | ^~~~ /home/fabio/Dev/Github/PKGBUILD-AUR_fix/a/amarok-qt6-git/src/amarok/tests/importers/TestImporterBase.cpp:404:29: note: add a pair of parentheses to declare a variable 404 | const QString testName( QLatin1String( QTest::currentDataTag() ) ); | ^ | ( ) /home/fabio/Dev/Github/PKGBUILD-AUR_fix/a/amarok-qt6-git/src/amarok/tests/importers/TestImporterBase.cpp:406:37: error: reference to type 'const QString' could not bind to an lvalue of type 'const QString (QLatin1String ((*)()))' 406 | QVERIFY( trackForName.contains( testName ) ); | ^~~~ /usr/include/qt6/QtTest/qtestcase.h:60:43: note: expanded from macro 'QVERIFY' 60 | if (!QTest::qVerify(static_cast(statement), #statement, "", __FILE__, __LINE__))\ | ^ /usr/include/qt6/QtCore/qmap.h:342:30: note: passing argument to parameter 'key' here 342 | bool contains(const Key &key) const | ^ /home/fabio/Dev/Github/PKGBUILD-AUR_fix/a/amarok-qt6-git/src/amarok/tests/importers/TestImporterBase.cpp:408:49: error: reference to type 'const QString' could not bind to an lvalue of type 'const QString (QLatin1String ((*)()))' 408 | const TrackPtr &track = trackForName.value( testName ); | ^~~~ /usr/include/qt6/QtCore/qmap.h:358:24: note: passing argument to parameter 'key' here 358 | T value(const Key &key, const T &defaultValue = T()) const |^ 1 warning generated. [ 91%] Linking CXX executable ../../../../../bin/testsqlartist -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 498307] New: Error while loading page: qrc:/ui/MapPage.qml:9 module "QtQuick.Shapes" is not installed
https://bugs.kde.org/show_bug.cgi?id=498307 Bug ID: 498307 Summary: Error while loading page: qrc:/ui/MapPage.qml:9 module "QtQuick.Shapes" is not installed Classification: Applications Product: filelight Version: 23.08.5 Platform: Ubuntu OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: fabioam...@gmail.com CC: martin.sandsm...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY STEPS TO REPRODUCE 1. lunch filelight from terminal 2. 3. OBSERVED RESULT fabio@a514:~$ filelight Disabling QML cache because of low disk space QFont::fromString: Invalid description 'Ubuntu,10,-1,5,400,0,0,0,0,0,0,0,0,0,0,1' QQmlComponent: Component is not ready file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/PageRow.qml:914: Error: Error while loading page: qrc:/ui/MapPage.qml:9 module "QtQuick.Shapes" is not installed and the application doesn't start EXPECTED RESULT the application starts SOFTWARE/OS VERSIONS Linux/KDE Plasma: Lubuntu 24.10 ADDITIONAL INFORMATION n/a -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 498058] New: Compiling issue for v3.2.0 Qt6
https://bugs.kde.org/show_bug.cgi?id=498058 Bug ID: 498058 Summary: Compiling issue for v3.2.0 Qt6 Classification: Applications Product: amarok Version: 3.2.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: fabio.l...@disroot.org Target Milestone: kf5 SUMMARY Hi, I'm the maintainer of Amarok on AUR and I have made a separate pkgbuild also with clang to build the Qt6 version just to test it * https://aur.archlinux.org/packages/amarok * https://github.com/FabioLolix/PKGBUILD-AUR_fix/blob/master/a/amarok-qt6/PKGBUILD * https://github.com/FabioLolix/PKGBUILD-AUR_fix/blob/master/a/amarok-qt6_clang/PKGBUILD STEPS TO REPRODUCE On Arch Linux sudo pacman -Syyu git base-devel git clone https://github.com/FabioLolix/PKGBUILD-AUR_fix cd PKGBUILD-AUR_fix/a/amarok-qt6 makepkg -s OBSERVED RESULT Fails to compile EXPECTED RESULT Compile successfully SOFTWARE/OS VERSIONS Linux: linux-lts 6.6.68 KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.9.0 Qt Version: 6.8.1 ADDITIONAL INFORMATION Building with GCC 14.2.1 ``` 57%] Linking CXX shared library ../bin/libamaroklib.so /usr/bin/ld: CMakeFiles/amaroklib.dir/browsers/filebrowser/FileView.cpp.o: warning: relocation against `_ZN12PopupDropper5clearEv' in read-only section `.text' /usr/bin/ld: CMakeFiles/amaroklib.dir/browsers/CollectionTreeView.cpp.o: in function `CollectionTreeView::mouseReleaseEvent(QMouseEvent*)': CollectionTreeView.cpp:(.text+0xba48): undefined reference to `PopupDropper::fadeHideFinished()' /usr/bin/ld: CMakeFiles/amaroklib.dir/browsers/CollectionTreeView.cpp.o: relocation R_X86_64_PC32 against undefined protected symbol `_ZN12PopupDropper16fadeHideFinishedEv' can not be used when making a shared object /usr/bin/ld: final link failed: bad value collect2: error: ld returned 1 exit status make[2]: *** [src/CMakeFiles/amaroklib.dir/build.make:7527: bin/libamaroklib.so.1.0.0] Error 1 make[1]: *** [CMakeFiles/Makefile2:12657: src/CMakeFiles/amaroklib.dir/all] Error 2 make: *** [Makefile:146: all] Error 2 ==> ERROR: A failure occurred in build(). ``` Building with clang+lld v18.1.8 ``` [ 57%] Linking CXX shared library ../bin/libamaroklib.so ld.lld: error: undefined protected symbol: PopupDropper::PopupDropper(QWidget*, bool) >>> referenced by PopupDropperFactory.cpp >>> >>> CMakeFiles/amaroklib.dir/PopupDropperFactory.cpp.o:(PopupDropperFactory::createPopupDropper(QWidget*, >>> bool)) >>> did you mean: PopupDropper::PopupDropper(QWidget*, bool) >>> defined in: ../bin/libamarokpud.so ld.lld: error: undefined protected symbol: PopupDropper::setSvgRenderer(QSvgRenderer*) >>> referenced by PopupDropperFactory.cpp >>> >>> CMakeFiles/amaroklib.dir/PopupDropperFactory.cpp.o:(PopupDropperFactory::createPopupDropper(QWidget*, >>> bool)) >>> referenced by PrettyListView.cpp >>> >>> CMakeFiles/amaroklib.dir/playlist/view/listview/PrettyListView.cpp.o:(Playlist::PrettyListView::startDrag(QFlags)) ld.lld: error: undefined protected symbol: PopupDropper::setQuitOnDragLeave(bool) >>> referenced by PopupDropperFactory.cpp >>> >>> CMakeFiles/amaroklib.dir/PopupDropperFactory.cpp.o:(PopupDropperFactory::createPopupDropper(QWidget*, >>> bool)) ld.lld: error: undefined protected symbol: PopupDropper::setFadeInTime(int) >>> referenced by PopupDropperFactory.cpp >>> >>> CMakeFiles/amaroklib.dir/PopupDropperFactory.cpp.o:(PopupDropperFactory::createPopupDropper(QWidget*, >>> bool)) ld.lld: error: undefined protected symbol: PopupDropper::setFadeOutTime(int) >>> referenced by PopupDropperFactory.cpp >>> >>> CMakeFiles/amaroklib.dir/PopupDropperFactory.cpp.o:(PopupDropperFactory::createPopupDropper(QWidget*, >>> bool)) ld.lld: error: undefined protected symbol: PopupDropper::setColors(QColor const&, QColor const&, QColor const&, QColor const&, QColor const&) >>> referenced by PopupDropperFactory.cpp >>> >>> CMakeFiles/amaroklib.dir/PopupDropperFactory.cpp.o:(PopupDropperFactory::createPopupDropper(QWidget*, >>> bool)) ld.lld: error: undefined protected symbol: PopupDropperItem::PopupDropperItem(QGraphicsItem*) >>> referenced by PopupDropperFactory.cpp >>> >>> CMakeFiles/amaroklib.dir/PopupDropperFactory.cpp.o:(PopupDropperFactory::createItem(QAction*)) ld.lld: error: undefined protected symbol: PopupDropperItem::setAction(QAction*) >>> referenced by PopupDropperFactory.cpp >>> >>> CMakeFiles/amaroklib.dir/PopupDropperFactory.cpp.o:(PopupDropperFactory::createItem(QAction*)) ld.lld: error: undefined protected symbol: PopupDropperItem::text() const >>> referenced by PopupDropperFactory.cpp >>> >>> CMakeFiles/amaroklib.dir/PopupDropperFactory.cpp.o:(PopupDropperFactory::createIt
