[kscreenlocker] [Bug 485520] Redundant unlock button appears after password when resuming from suspend
https://bugs.kde.org/show_bug.cgi?id=485520 Stefan Becker changed: What|Removed |Added CC||chemob...@gmail.com --- Comment #19 from Stefan Becker --- Could it be that this fix causes bug #490547 ? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 490547] Unlock button shows up when using security key to unlock
https://bugs.kde.org/show_bug.cgi?id=490547 Stefan Becker changed: What|Removed |Added CC||chemob...@gmail.com See Also||https://bugs.kde.org/show_b ||ug.cgi?id=485520 --- Comment #1 from Stefan Becker --- I can confirm this bug: it appeared after upgrading to 6.1.3. Maybe this is related to the fix for bug #485520 ? Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.11-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485520] Redundant unlock button appears after password when resuming from suspend
https://bugs.kde.org/show_bug.cgi?id=485520 Stefan Becker changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=490547 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 485094] When click Scale button image disappears
https://bugs.kde.org/show_bug.cgi?id=485094 Stefan Becker changed: What|Removed |Added CC||chemob...@gmail.com --- Comment #1 from Stefan Becker --- When krdc is running in "window mode", i.e. not full screen, there is only the "Scale" button. When you click that, the (VNC) session output is scaled down to 1x1, i.e. it "disappears". I happened to switch the session to full screen mode and hold and behold: **there is a SLIDER right of the scale button!** It shows the wrong setting, i.e. 0%, but once you move the slider, the session output is correctly scaled. And the best part is: now krdc remembers the chosen scale value for the session, i.e. when you next time open krdc and open the session it remembers the values correctly and the session is scaled. Now I can use my VNC session again on a high resolution display. Fedora 40 x86_64 krdc 24.02.2 (with deadlock fix for VNC plugin applied) KDE Frameworks Version 6.1.0 Qt Version 6.7.0 (built against 6.7.0) The wayland windowing system -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 486178] VNC plugin deadlocks on connection
https://bugs.kde.org/show_bug.cgi?id=486178 --- Comment #5 from Stefan Becker --- I can confirm that after applying the patch VNC connections work again with krdc. -- 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 Stefan Becker changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from Stefan Becker --- Yeah, that looks like the same issue. *** This bug has been marked as a duplicate of bug 486178 *** -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 486178] VNC plugin deadlocks on connection
https://bugs.kde.org/show_bug.cgi?id=486178 Stefan Becker changed: What|Removed |Added CC||chemob...@gmail.com --- Comment #4 from Stefan Becker --- *** Bug 485215 has been marked as a duplicate of this bug. *** -- 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 --- Comment #3 from Stefan Becker --- (In reply to foxfire-auspex from comment #2) > > I'm not sure that I've encountered the exact same bug, but they're > superficially similar enough that I'll just add my information here. Your bug is not a bug, I fear. The log clearly shows that FreeRDP crypto rejects the self-signed certificate offered by the RDP host. After that the connection is closed. KRDC does *NOT* freeze up as it does with VNC connections. > KRDC: Starting RDP session > [13:52:25:888] [18828:18828] [WARN][com.freerdp.crypto] - Certificate > verification failure 'self-signed certificate (18)' at stack position 0 > [13:52:25:888] [18828:18828] [WARN][com.freerdp.crypto] - CN = > SHARED-W10-VM.campoint.net I'm not sure if KRDC/FreeRDP has an option/dialog to ignore certificate errors. There may also have been a tightening of system TLS security settings in Fedora 40 (there have been several rounds of that in the last releases), which you would need to loosen to be able to connect. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 485262] Only plays one song from playlist and then stops
https://bugs.kde.org/show_bug.cgi?id=485262 --- Comment #4 from Stefan Becker --- Confirmed: problem is no longer reproducible with 24.02.2. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 485262] Only plays one song from playlist and then stops
https://bugs.kde.org/show_bug.cgi?id=485262 --- Comment #2 from Stefan Becker --- Reproduced the problem on a 2nd machine with Fedora 40 Beta. I have tried with Ogg Vorbis (.ogg) and FLAC files. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 485262] New: Only plays one song from playlist and then stops
https://bugs.kde.org/show_bug.cgi?id=485262 Bug ID: 485262 Summary: Only plays one song from playlist and then stops Classification: Applications Product: Elisa Version: 24.02.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: chemob...@gmail.com Target Milestone: --- SUMMARY Elisa stops playing after the end of the current track on the playlist. STEPS TO REPRODUCE 1. select "Clear All" in playlist side bar 2. select "Play" icon on an album in the albums tab to create new playlist and start playing first track OBSERVED RESULT Elisa plays first track from playlist and then stops. EXPECTED RESULT Elisa should continue and play the next song on the playlist SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.2-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION * this seems to be regression compared to Plasma5/Qt5 version. It used to work fine on Fedora 39 * I tried different playlist repeat modes: same result * I removed all Elisa related configuration from my home directory and tried again: same result When I run Elisa from the command line I get the following message at the end of the first track from the playlist . rest of log messages removed libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 # message after song ends: [vorbis @ 0x55e3d1eeda80] Could not update timestamps for discarded samples. # selected the next song on playlist, played that and at the end again... [vorbis @ 0x55e3d1eeda80] Could not update timestamps for discarded samples. ... # cleared the playlist and added an album with FLAC tracks # no message at the end of the tracks... It seems that this vorbis message is not the root cause for the problem. -- 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 --- Comment #1 from Stefan Becker --- Just found a RDP host @ work. Connection with krdc works, it checks the certificate and then asks to username & password (I have no login there). So I assume that the RDP plugin is fully working and only the VNC plugin is broken. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 485215] New: [Plasma 6 REGRESSION] KRDC hangs when trying to connect to VNC host
https://bugs.kde.org/show_bug.cgi?id=485215 Bug ID: 485215 Summary: [Plasma 6 REGRESSION] KRDC hangs when trying to connect to VNC host Classification: Applications Product: krdc Version: 24.02.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: VNC Assignee: uwol...@kde.org Reporter: chemob...@gmail.com Target Milestone: --- SUMMARY I just upgraded from Fedora 39 to 40, i.e. I moved from KDE Plasma 5 to Plasma 6. KRDC connections using VNC plugin stopped working: KRDC hangs before even trying to create a network connection. STEPS TO REPRODUCE 1. start connection to host using vnc protocol OBSERVED RESULT Nothing: krdc application stops responding. E.g. disconnect or close window leads to "krdc application does not respond" dialog. According to networking status krdc hangs before even trying to create a network connection. I.e. this problem can even be reproduced by trying to connect to a non-existing VNC host. EXPECTED RESULT Connection to VNC host succeeds. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.2-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION * I tried on two different systems: same result * I used tigervnc client to connect to VNC host: works fine * I tried "krdc --platform xcb": no result * I deleted all KRDC configurations from my home directory and then tried to create a new connection: same result (i.e. not caused by old Plasma 5 settings) * I enabled TEST plugin and created a connection using "test:" protocol: works fine, i.e. I get a window with yellow background (I guess that is what the test plugin generates). I can successfully disconnect from this connection * (I don't have a RDP host available for real testing, sorry) I created a RDP connection to a non-existing host: KRDC tries to connect to the host and returns after a short while "can't connect to host", i.e. it seems that RDP plugin works fine. When I run "krdc" from the konsole the only messages I get are these at startup: ~~~ kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/krdc/libkrdc_vncplugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/krdc/libkrdc_testplugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/krdc/libkrdc_rdpplugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed qt.core.qobject.connect: QObject::connect: No such signal KBookmarkManager::changed(QString,QString) ~~~ There are no additional messages when I try to create the VNC connection -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467269] LC_PAGE should be LC_PAPER?
https://bugs.kde.org/show_bug.cgi?id=467269 --- Comment #1 from Stefan Becker --- Maybe further evidence that LC_PAGE is not the correct variable: $ LC_PAGE= LC_PAPER= libreoffice -> print dialog shows "letter" as paper size (CORRECT for LANG=es_US.UTF-8) $ LC_PAGE=fi_FI.UTF-8 LC_PAPER= libreoffice -> print dialog shows "letter" as paper size (WRONG) $ LC_PAGE= LC_PAPER=fi_FI.UTF-8 libreoffice -> print dialog shows "A4" as paper size (CORRECT) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467269] New: LC_PAGE should be LC_PAPER?
https://bugs.kde.org/show_bug.cgi?id=467269 Bug ID: 467269 Summary: LC_PAGE should be LC_PAPER? Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_regionandlang Assignee: plasma-b...@kde.org Reporter: chemob...@gmail.com CC: hanyo...@protonmail.com Target Milestone: --- SUMMARY The changes for Bug 420928 introduced LC_PAGE into the System Settings: https://invent.kde.org/plasma/plasma-workspace/commit/73bfdcff3d7d16e648aaf9ea7630a3967376412e https://invent.kde.org/plasma/plasma-workspace/commit/c7c2a3a85e5b7f74dcb2eadc35defe9e4b55c737 * they talk about paper size, not page size * seem to read from LC_PAPER environment variable? (maybe I didn't understand the code correctly) * write LC_PAGE to ./config/plasma-localerc instead of LC_PAPER When I login to the desktop, open a console and execute "locale" I get LC_PAPER set to the default specified by LANG, instead of the KDE setting. System Settings should either write LC_PAPER or write LC_PAPER & LC_PAGE into the configuration file. But as far as I can tell LC_PAGE is *not* an official locale category and should be dropped. STEPS TO REPRODUCE 1. open System Settings 2. select a paper size different from the locale default (I selected "Suomi", i.e. paper size from finnish locale) 3. log out and in again 4. open konsole 5. run "locale" command OBSERVED RESULT # before change: $ cat .config/plasma-localerc [Formats] LANG=en_US.UTF-8 LC_ADDRESS=fi_FI.UTF-8 LC_MEASUREMENT=fi_FI.UTF-8 LC_MONETARY=fi_FI.UTF-8 LC_NAME=fi_FI.UTF-8 LC_TELEPHONE=fi_FI.UTF-8 LC_TIME=en_GB.UTF-8 # after change $ cat .config/plasma-localerc [Formats] LANG=en_US.UTF-8 LC_ADDRESS=fi_FI.UTF-8 LC_MEASUREMENT=fi_FI.UTF-8 LC_MONETARY=fi_FI.UTF-8 LC_NAME=fi_FI.UTF-8 LC_PAGE=fi_FI.UTF-8 LC_TELEPHONE=fi_FI.UTF-8 LC_TIME=en_GB.UTF-8 $ locale LANG="en_US.UTF-8" LC_PAPER="en-US.UTF-8" EXPECTED RESULT $ locale LANG="en_US.UTF-8" ... LC_PAPER="fi_FI.UTF-8" SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 37 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 453280] kded5 leaks X-Window connections: Maximum number of clients reached
https://bugs.kde.org/show_bug.cgi?id=453280 --- Comment #22 from Stefan Becker --- FYI: this is fixed on Fedora 36 with kscreen-1:5.24.5-2.fc36 (https://bodhi.fedoraproject.org/updates/FEDORA-2022-f7b84908ae) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 453280] kded5 leaks X-Window connections: Maximum number of clients reached
https://bugs.kde.org/show_bug.cgi?id=453280 Stefan Becker changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kscreen/commit/0270a4932 ||8aa70b14dd08e2ed5a425ca3f8e ||4fd5 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #19 from Stefan Becker --- Git commit 0270a49328aa70b14dd08e2ed5a425ca3f8e4fd5 by Stefan Becker. Committed on 30/05/2022 at 04:23. Pushed by davidedmundson into branch 'master'. X11: fix kded xcb resource leak This fixes commit 579358f501ae978aa527a25eb3ef9dd42557db46 XOpenDisplay() internally calls xcb_connect(), creating a new XCB client connection. This means that on every KScreen configuration change event the kded5 process creates a new connection until XCB runs into the hard limit of 256 of clients, leading to the dreaded "Maximum number of clients reached" error. Re-use the display from QX11Info instead of calling XOpenDisplay(). M +8-9kded/daemon.cpp https://invent.kde.org/plasma/kscreen/commit/0270a49328aa70b14dd08e2ed5a425ca3f8e4fd5 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 453280] kded5 leaks X-Window connections: Maximum number of clients reached
https://bugs.kde.org/show_bug.cgi?id=453280 Stefan Becker changed: What|Removed |Added Version|5.94.0 |5.24.5 Product|frameworks-kded |KScreen CC||notm...@gmail.com Ever confirmed|0 |1 Assignee|fa...@kde.org |kscreen-bugs-n...@kde.org Component|general |kded Status|REPORTED|CONFIRMED --- Comment #17 from Stefan Becker --- Forgot to mention: kded doesn't know anything about X11, there are no references in the source code But KScreen has a piece of code running in kded5 process context: the kscreen kded plugin. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 453280] kded5 leaks X-Window connections: Maximum number of clients reached
https://bugs.kde.org/show_bug.cgi?id=453280 --- Comment #16 from Stefan Becker --- Created attachment 149318 --> https://bugs.kde.org/attachment.cgi?id=149318=edit kscreen: fix XCB connection resource leak After digging through the source code and running kded5 under ltrace $ ltrace -e xcb_connect+xcb_connect_to_display_with_auth_info+xcb_connect_to_fd+xcb_disconne...@libxcb.so.1 kded5 I was able to track down the resource leak. This error is mis-attributed to "kded", the culprit is "kscreen". More specifically the problem was introduced by this git commit: commit 09b988e6628093e7d4c8b92cd8a0a1fe2da2f77e Author: Marco Martin Date: Fri Mar 4 09:05:19 2022 + X11: align touchscreen to internal display On Wayland is the compositor itself that keeps the touchscreen coordinates mapped to the size and position of the internal screen, also keeping rotation into account. on X11, needs to be done via XInput, do it when KScreen actually applies a configuration. BUG: 415683 XOpenDisplay() internally calls xcb_connect(), which allocates a new XCB connection. Therefore you need to call XCloseDisplay() again to release the connection. This is what the attached patch does. With it the problem can no longer be reproduced. There may be other or better ways to fix this, e.g. * determine X Display from the XCB connection retrieved from QX11Info * use XCB calls with XCB connection instead of X calls that require X Display but I was unable to determine that based on API documentation. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 453280] kded5 leaks X-Window connections: Maximum number of clients reached
https://bugs.kde.org/show_bug.cgi?id=453280 Stefan Becker changed: What|Removed |Added CC||chemob...@gmail.com --- Comment #12 from Stefan Becker --- I was just going to open a bug report for this. I agree this is highly annoying and it took a while to track it down to kded5. Thanks Raman for the systemctl tip for Fedora. Manually killing kded5 seems sometimes to have negative side-effects I can confirm that on one of the machines, where I encountered this issue, it is related to output switching. The machine is connected via HDMI to an AV receiver. Simply switching the amplifier off or on increases the amount of X11 client connections kded5 increases by various amounts (+2 to +6 connections). Another bit of information: disabling the KScreen background service, i.e. the service that detects and propagates output changes, also "fixes" the issue as kded5 no longer is made aware of those changes. I'm not aware ever seeing this error message before it started to appear a few months back. That probably indicates that some change to Plasma 5.24.x introduced the issue. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 415488] New: Remove double ppa entries automaticly like linux mint
https://bugs.kde.org/show_bug.cgi?id=415488 Bug ID: 415488 Summary: Remove double ppa entries automaticly like linux mint Product: Discover Version: 5.17.4 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: ste...@gmail.com CC: aleix...@kde.org Target Milestone: --- add a maintanance section to Remove double ppa entries automaticly like linux mint -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409008] New: crash during deinstalltion from a second installesdlanguage ( polski )
https://bugs.kde.org/show_bug.cgi?id=409008 Bug ID: 409008 Summary: crash during deinstalltion from a second installesdlanguage ( polski ) Product: systemsettings Version: 5.16.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ste...@gmail.com Target Milestone: --- Application: systemsettings5 (5.16.1) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 5.1.12-050112-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - i select the second installed language ( polski ) the first installaed language is german The crash can be reproduced every time. -- Backtrace: Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5cf9b76680 (LWP 28309))] Thread 7 (Thread 0x7f5cba0ed700 (LWP 28317)): #0 0x7f5cee185379 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f5cee13ea33 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5cee13f3fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5cee13f5dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f5cf5a21dcb in QEventDispatcherGlib::processEvents (this=0x7f5cb4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f5cf59c303a in QEventLoop::exec (this=this@entry=0x7f5cba0ecd40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f5cf57ea4ca in QThread::exec (this=this@entry=0x5572b5ee43a0) at thread/qthread.cpp:531 #7 0x7f5cf35a0115 in QQmlThreadPrivate::run (this=0x5572b5ee43a0) at qml/ftw/qqmlthread.cpp:148 #8 0x7f5cf57ebc72 in QThreadPrivate::start (arg=0x5572b5ee43a0) at thread/qthread_unix.cpp:361 #9 0x7f5cf04fd6db in start_thread (arg=0x7f5cba0ed700) at pthread_create.c:463 #10 0x7f5cf50eb88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f5cc0c17700 (LWP 28316)): #0 0x7f5cee13ea18 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f5cee13f3fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5cee13f5dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5cf5a21dcb in QEventDispatcherGlib::processEvents (this=0x7f5cbc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f5cf59c303a in QEventLoop::exec (this=this@entry=0x7f5cc0c16d40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f5cf57ea4ca in QThread::exec (this=this@entry=0x5572b3173d90) at thread/qthread.cpp:531 #6 0x7f5cf35a0115 in QQmlThreadPrivate::run (this=0x5572b3173d90) at qml/ftw/qqmlthread.cpp:148 #7 0x7f5cf57ebc72 in QThreadPrivate::start (arg=0x5572b3173d90) at thread/qthread_unix.cpp:361 #8 0x7f5cf04fd6db in start_thread (arg=0x7f5cc0c17700) at pthread_create.c:463 #9 0x7f5cf50eb88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f5cc958f700 (LWP 28314)): #0 0x7f5cf50da0b4 in __GI___libc_read (fd=13, buf=0x7f5cc958eb30, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f5cee184000 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5cee13efb7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5cee13f470 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f5cee13f5dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f5cf5a21dcb in QEventDispatcherGlib::processEvents (this=0x7f5cc4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f5cf59c303a in QEventLoop::exec (this=this@entry=0x7f5cc958ed40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f5cf57ea4ca in QThread::exec (this=this@entry=0x5572b2e0e550) at thread/qthread.cpp:531 #8 0x7f5cf35a0115 in QQmlThreadPrivate::run (this=0x5572b2e0e550) at qml/ftw/qqmlthread.cpp:148 #9 0x7f5cf57ebc72 in QThreadPrivate::start (arg=0x5572b2e0e550) at thread/qthread_unix.cpp:361 #10 0x7f5cf04fd6db in start_thread (arg=0x7f5cc958f700) at pthread_create.c:463 #11 0x7f5cf50eb88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f5cd5914700 (LWP 28312)): #0 0x7f5cf05039f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5572b2ae6958) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5572b2ae6908, cond=0x5572b2ae6930) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5572b2ae6930, mutex=0x5572b2ae6908) at
[palapeli] [Bug 402655] puzzel part move hang
https://bugs.kde.org/show_bug.cgi?id=402655 --- Comment #1 from Stefan Becker --- SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5,53,0 Qt Version: 5.11.2 --- Comment #2 from Stefan Becker --- SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5,53,0 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[palapeli] [Bug 402655] puzzel part move hang
https://bugs.kde.org/show_bug.cgi?id=402655 --- Comment #1 from Stefan Becker --- SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5,53,0 Qt Version: 5.11.2 --- Comment #2 from Stefan Becker --- SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5,53,0 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[palapeli] [Bug 402655] New: puzzel part move hang
https://bugs.kde.org/show_bug.cgi?id=402655 Bug ID: 402655 Summary: puzzel part move hang Product: palapeli Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: majew...@gmx.net Reporter: ste...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. change background to single cokor 2. can't move the puzzel parts 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 399449] [PRIVACY VIOLATION] plasma-browser-integration-host creates network connections
https://bugs.kde.org/show_bug.cgi?id=399449 Stefan Becker changed: What|Removed |Added URL|https://bugzilla.mozilla.or |https://bugzilla.mozilla.or |g/show_bug.cgi?id=1496991 |g/show_bug.cgi?id=1452461 --- Comment #7 from Stefan Becker --- My Mozilla bug got marked as duplicate -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 399449] [PRIVACY VIOLATION] plasma-browser-integration-host creates network connections
https://bugs.kde.org/show_bug.cgi?id=399449 --- Comment #5 from Stefan Becker --- Created attachment 115453 --> https://bugs.kde.org/attachment.cgi?id=115453=edit Patch with improved workaround I poked around in the workaround code and figured out that the only way to avoid Firefox to busy loop is to *only* close() sockets and leave the rest alone. Thus we still have leaked file descriptors lying around, but at least we're getting rid of all leaked network connections at start. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 399449] [PRIVACY VIOLATION] plasma-browser-integration-host creates network connections
https://bugs.kde.org/show_bug.cgi?id=399449 --- Comment #4 from Stefan Becker --- Unfortunately the workaround has a nasty side-effect: firefox starts to busy-loop :-( I guess there are some FDs that firefox is using to communicate with the host binary and those should not be closed. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 399449] [PRIVACY VIOLATION] plasma-browser-integration-host creates network connections
https://bugs.kde.org/show_bug.cgi?id=399449 --- Comment #3 from Stefan Becker --- After applying the workaround and restarting Firefox I do not see any "outgoing network connections" by plasma-browser-integration-host anymore. Thanks -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 399449] [PRIVACY VIOLATION] plasma-browser-integration-host creates network connections
https://bugs.kde.org/show_bug.cgi?id=399449 Stefan Becker changed: What|Removed |Added URL||https://bugzilla.mozilla.or ||g/show_bug.cgi?id=1496991 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 399449] [PRIVACY VIOLATION] plasma-browser-integration-host creates network connections
https://bugs.kde.org/show_bug.cgi?id=399449 --- Comment #2 from Stefan Becker --- As recommended I filed a bug upstream https://bugzilla.mozilla.org/show_bug.cgi?id=1496991 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 399449] New: [PRIVACY VIOLATION] plasma-browser-integration-host creates network connections
https://bugs.kde.org/show_bug.cgi?id=399449 Bug ID: 399449 Summary: [PRIVACY VIOLATION] plasma-browser-integration-host creates network connections Product: plasma-browser-integration Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Firefox Assignee: k...@privat.broulik.de Reporter: chemob...@gmail.com Target Milestone: --- After upgrading to F29 beta with Plasme 5.13.5 I got the reminder about the Browser integration. I installed the Firefox extension and started to test it. No problems there firefox-62.0-3.fc29.x86_64 plasma-browser-integration-5.13.5-1.fc29.x86_64 [this might also apply to Chromium, but I didn't activate the integration for it] ...but afterwards I had a look at "netstat -tp" and was surprised to see that the browser integration seems to create *outgoing* network connections on its own. Which is rather surprising when you read the statement from the Wiki https://community.kde.org/Plasma/Browser_Integration#Privacy: Everything is handled on your PC between the browser and your desktop, no additional data is sent via the web. Snapshot from my test system: $ netstat -tnp | fgrep -e plasma- -e firefox tcp0 0 192.168.3.6:39846:443 ESTABLISHED 1753/firefox tcp0 0 192.168.3.6:33556:443 ESTABLISHED 1753/firefox ... many more open connections from firefox tcp 2194537 0 192.168.3.6:49664 :443 ESTABLISHED 1753/firefox tcp1 0 192.168.3.6:35696 104.16.111.25:443 CLOSE_WAIT 2686/plasma-browser tcp 32 0 192.168.3.6:57386 151.101.193.69:443 CLOSE_WAIT 2686/plasma-browser ... tcp 8692 0 192.168.3.6:50810 104.20.117.11:443 CLOSE_WAIT 2686/plasma-browser [NOTE: at other times I also saw ESTABLISHED connections. I tried to reverse look up the IPs but didn't get any usable information from them] $ ps -efw | fgrep 2686 stefanb 2686 1753 0 09:38 ?00:00:00 /usr/bin/plasma-browser-integration-host /usr/lib64/mozilla/native-messaging-hosts/org.kde.plasma.browser_integration.json plasma-browser-integrat...@kde.org The above connections are not created by firefox, because firefox connections are associated with the firefox process. I haven't yet studied the source code for the messaging host binary to check for network connection creation, but I'll try to do so when I get the time. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 351256] Way to distinguish more monitors with the same vendor/model label
https://bugs.kde.org/show_bug.cgi?id=351256 Stefan Becker <chemob...@gmail.com> changed: What|Removed |Added CC||chemob...@gmail.com --- Comment #4 from Stefan Becker <chemob...@gmail.com> --- I'm now running plasma 5.6.2 and can add another case where kscreen/plasma gets confused: because both monitors are identical the panel appears randomly on one or the other after switching from laptop LVDS to docking station DP-2/DP-3 DP-conected monitors BTW: when looking at the files in $HOME/.local/share/kscreen/ I can see that both entries for the external screen the same ID value. I guess that SHA-1 value is calculated only from data which is exactly the same for both monitors. IMHO including "name" field (== xrandr output name) from "metadata" map would make the ID unique. With 5.5.x the behaviour was different: the panel always appeared on the primary output. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356723] Incomplete window updates after updating to Plasma 5.5.0
https://bugs.kde.org/show_bug.cgi?id=356723 Stefan Becker <chemob...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #11 from Stefan Becker <chemob...@gmail.com> --- Confirmed. After latest F23 updates konsole works fine again. Package information (compare to original description): Updated previously: qt5-qtbase-5.5.1-11.fc23.x86_64 kf5-plasma-5.18.0-1.fc23.x86_64 Updates that arrived today: kwin-5.5.4-1.fc23.x86_64 konsole5-15.12.1-1.fc23.x86_64 plasma-workspace-5.5.4-1.fc23.x86_64 plasma-desktop-5.5.4-1.fc23.x86_64 I don't see any code changes between konsole5 5.12.0 and 5.12.1. Only two changes between kwin 5.5.3 and 5.5.4. IMHO it could be this change for bug #357543, because it talks about corrupted visuals: https://quickgit.kde.org/?p=kwin.git=commitdiff=a18177cc24d20bca02f60a95b67f2dcbd1ee8afc Closing as FIXED. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356723] Incomplete window updates after updating to Plasma 5.5.0
https://bugs.kde.org/show_bug.cgi?id=356723 --- Comment #4 from Stefan Becker <chemob...@gmail.com> --- Just updated to latest Fedora 23 "updates" repo contents. Problem is still there. I checked "updates-testing": there are no new Qt/KF/Plasma/Konsole packages in there, so updating to updates-testing wouldn't solve the problem either. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356723] Incomplete window updates after updating to Plasma 5.5.0
https://bugs.kde.org/show_bug.cgi?id=356723 --- Comment #1 from Stefan Becker <chemob...@gmail.com> --- BTW: I checked https://bugs.kde.org/show_bug.cgi?id=356343 but that looks like a different issue. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356723] New: Incomplete window updates after updating to Plasma 5.5.0
https://bugs.kde.org/show_bug.cgi?id=356723 Bug ID: 356723 Summary: Incomplete window updates after updating to Plasma 5.5.0 Product: konsole Version: 15.08.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: chemob...@gmail.com After updating to Plasma 5.5.0 konsole window updates are incomplete. When konsole starts to scroll only the lowest 2-3 lines of text (and some random lines above) are updated. To get the real current content of the konsole window, you have to click outside the konsole window (deactivates window) and click on the konsole window (activates window again). NOTE: konsole was not updated when I received the Plasma 5.5.0 update. So this issue might be related to Plasma changes. But as far as I can see only konsole has issues with window updates. I updated now to konsole 5.12.0, but the problem is still there. Several other people I have discussed on IRC with have also noticed this issues on their system with different HW and open source drivers, so this is not an Nvidia issue. I use a Dell laptop with Nvidia blob driver and describe how I can reproduce this on my system. Changing compositor settings or disabling compositor completely does not fix this problem. Reproducible: Always Steps to Reproduce: - laptop out of docking station, i.e. one screen only - login to KDE session - force scrolling in konsole sessions, e.g. commands with many lines of output -> window updates are OK - put laptop into docking station, switch to 2 external screens - force scrolling in konsole sessions or scroll konsole window -> lowest 2-3 lines are usually updated, randomly some other lines too - switch back to 1-screen mode (laptop display) - force scrolling in konsole sessions or scroll konsole window -> issue is still there qt5-qtbase-5.5.1-8.fc23.x86_64 kf5-plasma-5.16.0-4.fc23.x86_64 plasma-desktop-5.5.0-4.fc23.x86_64 plasma-workspace-5.5.0-3.fc23.x86_64 kwin-5.5.0-1.fc23.x86_64 konsole5-15.12.0-1.fc23.x86_64 -- You are receiving this mail because: You are watching all bug changes.
