[KScreen] [Bug 360058] Kscreen should check screen at wakeup from suspend
https://bugs.kde.org/show_bug.cgi?id=360058 --- Comment #5 from Sergio --- So the bug has got to 5.8.1. Sad to hear that, being on in ubuntuland that shall probably get to 5.8.1 in another 6 months. Looks like no one with kde uses laptops that dock to external monitors to realize that this is an issue ;-) On the bright side, I believe that /there should be a solution/ to this problem since plasma 4 was dealing with it just fine. For the time being, as a dirty hack I suggest just adding a script to systemd to assure that it kills the kscreen_backend_laucher on suspend/resume. Can the bug be marked as confirmed? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=343803 --- Comment #85 from Sergio --- So, we have users who saw this bug with xenial and then the bug go away with yakkety, but there are also users (at least me) who did not see the bug with xenial and see it with yakkety. Then we have users on nvidia 361 before 18 see it, then see it disappear with .18 and reappear again with .28 (when possibly nvidia had never touched anything directly related to the issue in the driver). This looks very much like an issue triggered by timings of events / races. And it is very much possible that noveau cures it not because it has "better opengl" but because it is slower in some paths, significantly changing the timing of things. Can it be a Qt issue. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=343803 --- Comment #80 from Sergio --- Note that a comment in the bug thread on the nvidia bug tracker states: "From what I've seen it may not be the nVidia driver which is at fault. There seems to be a complicated threading issue which might or might not be caused by the driver...it may just be this driver exposes the issue differently." The fact that some people saw the issue even in Xenial with Nvidia 340 and I did not, as well as the fact that some report that on more modern graphics cards the issue disappeared with nvidia 361.18 and reappeared in 361.28 seems to confirm that this may just be a race somewhere (Qt?) and not a bug in the nvidia drivers. Is there a Qt bug open on this? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=343803 Sergio changed: What|Removed |Added CC||sergio.calleg...@gmail.com --- Comment #79 from Sergio --- I have started to see the issue on a Kubuntu Yakkety (16.10) machine that uses Nvidia Quadro FX 570 graphics. The graphics card is supported by the Nvidia 340 legacy driver. The software included in Yakkety is plasma 5.7.5, framework 5.26.0, konsole 16.04.3, QT 5.6.1. The symptoms seem to be exactly those described here. Closing the konsole a process is left behind, in my case using 100% cpu. Furthermore, there are occasional crashes of the konsole on exit due to issues with corrupted double linked lists. Moving to the noveau driver resolves both the issues (but brings in other problems on its own). The interesting part is that the same machine with exactly the same hardware, was not showing this issue with ubuntu Xenial, while others report the issue also on Xenial. I thus wonder if the bug may be triggered by some sort of race or ordering/timings in which events occur, that may be influenced by both the hardware and the software stack. If this is the case, the fixing of the issue in the most recent Nvidia drivers could be just luck. For sure, the issue is still present with the latest Nvidia 340 drivers, so please reopen. Even if this is a bug with the Nvidia legacy opengl implementation, avoiding triggering the issue in the beginning in the konsole would be the best. This should be possible as the Qt terminal is reported not to have any issue. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 369674] Okular mismanages font encoding
https://bugs.kde.org/show_bug.cgi?id=369674 --- Comment #4 from Sergio --- Done https://bugs.freedesktop.org/show_bug.cgi?id=98029 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 369674] Okular mismanages font encoding
https://bugs.kde.org/show_bug.cgi?id=369674 --- Comment #2 from Sergio --- With respect to the sample document: correctly working viewers on linux: Mozilla pdf.js masterpdfeditor Foxit PDF reader for linux Broken viewers on linux: xpdf so it may be a poppler bug inherited from xpdf. However, Google PDFium fails on the test case too (although in a different way, i.e. not showing the quotes at all). google pdfium -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 369674] Okular mismanages font encoding
https://bugs.kde.org/show_bug.cgi?id=369674 --- Comment #1 from Sergio --- Created attachment 101390 --> https://bugs.kde.org/attachment.cgi?id=101390&action=edit A document with a testcase for the issue -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 369674] New: Okular mismanages font encoding
https://bugs.kde.org/show_bug.cgi?id=369674 Bug ID: 369674 Summary: Okular mismanages font encoding Product: okular Version: 0.24.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: sergio.calleg...@gmail.com In some documents, Okular mismanages the fonts, printing incorrect chars for non ascii chars Reproducible: Always Steps to Reproduce: 1. Open the attached document with okular 2. Reopen it with some other pdf viewer 3. Check the double quotes in the two cases -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 367959] Okular mangles some characters (non embedded fonts)
https://bugs.kde.org/show_bug.cgi?id=367959 --- Comment #3 from Sergio --- Created attachment 100841 --> https://bugs.kde.org/attachment.cgi?id=100841&action=edit How other pdf readers show the file on the same platform -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 367959] Okular mangles some characters (non embedded fonts)
https://bugs.kde.org/show_bug.cgi?id=367959 --- Comment #2 from Sergio --- Created attachment 100840 --> https://bugs.kde.org/attachment.cgi?id=100840&action=edit How okular shows the demo file -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 367959] Okular mangles some characters (non embedded fonts)
https://bugs.kde.org/show_bug.cgi?id=367959 --- Comment #1 from Sergio --- Created attachment 100839 --> https://bugs.kde.org/attachment.cgi?id=100839&action=edit Demo file A demo file to reproduce the problem -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 367959] New: Okular mangles some characters (non embedded fonts)
https://bugs.kde.org/show_bug.cgi?id=367959 Bug ID: 367959 Summary: Okular mangles some characters (non embedded fonts) Product: okular Version: 0.24.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: sergio.calleg...@gmail.com In some occasions, Okular mangles some chars that are reproduced correctly by other PDF readers (e.g. acroread, masterpdfeditor) on the very same platform. Inkscape also imports the PDF correctly. Might be a poppler problem since xpdf has the same issue. The problem seems to be related to substitution rules for fonts that are not embedded in the PDF document nor available on the platform with exactly the same name. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364032] New: Se cierra la barra KDE
https://bugs.kde.org/show_bug.cgi?id=364032 Bug ID: 364032 Summary: Se cierra la barra KDE Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: silp1...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-22-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: Al cambiar de red, se cierra la barra de inicio y me sale un error. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6a5621b8c0 (LWP 7617))] Thread 17 (Thread 0x7f6a421ff700 (LWP 7620)): #0 0x7f6a5092ee8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f6a549f3c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f6a549f58d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f6a4497f629 in QXcbEventReader::run (this=0x2529a90) at qxcbconnection.cpp:1253 #4 0x7f6a5102484e in QThreadPrivate::start (arg=0x2529a90) at thread/qthread_unix.cpp:331 #5 0x7f6a501116fa in start_thread (arg=0x7f6a421ff700) at pthread_create.c:333 #6 0x7f6a5093ab5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7f6a3b3ea700 (LWP 7624)): #0 0x7f6a5092ee8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f6a4d6c431c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a4d6c442c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a5125ba9b in QEventDispatcherGlib::processEvents (this=0x7f6a340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f6a51202dea in QEventLoop::exec (this=this@entry=0x7f6a3b3e9ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f6a5101f8a4 in QThread::exec (this=this@entry=0x26004f0) at thread/qthread.cpp:503 #6 0x7f6a538c73c5 in QQmlThreadPrivate::run (this=0x26004f0) at qml/ftw/qqmlthread.cpp:141 #7 0x7f6a5102484e in QThreadPrivate::start (arg=0x26004f0) at thread/qthread_unix.cpp:331 #8 0x7f6a501116fa in start_thread (arg=0x7f6a3b3ea700) at pthread_create.c:333 #9 0x7f6a5093ab5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7f6a2eb67700 (LWP 7625)): #0 0x7f6a5092ee8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f6a4d6c431c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a4d6c442c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a5125ba9b in QEventDispatcherGlib::processEvents (this=0x7f6a280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f6a51202dea in QEventLoop::exec (this=this@entry=0x7f6a2eb66ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f6a5101f8a4 in QThread::exec (this=this@entry=0x29b4a20) at thread/qthread.cpp:503 #6 0x7f6a538c73c5 in QQmlThreadPrivate::run (this=0x29b4a20) at qml/ftw/qqmlthread.cpp:141 #7 0x7f6a5102484e in QThreadPrivate::start (arg=0x29b4a20) at thread/qthread_unix.cpp:331 #8 0x7f6a501116fa in start_thread (arg=0x7f6a2eb67700) at pthread_create.c:333 #9 0x7f6a5093ab5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7f6a2cc7c700 (LWP 7626)): #0 0x7f6a5092a9cd in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f6a4d7076c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a4d6c3e04 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a4d6c42c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6a4d6c442c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6a5125ba9b in QEventDispatcherGlib::processEvents (this=0x7f6a28c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7f6a51202dea in QEventLoop::exec (this=this@entry=0x7f6a2cc7bce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7f6a5101f8a4 in QThread::exec (this=this@entry=0x2b681d0) at thread/qthread.cpp:503 #8 0x7f6a538c73c5 in QQmlThreadPrivate::run (this=0x2b681d0) at qml/ftw/qqmlthread.cpp:141 #9 0x7f6a5102484e in QThreadPrivate::start (arg=0x2b681d0) at thread/qthread_unix.cpp:331 #10 0x7f6a501116fa in start_thread (arg=0x7f6a2cc7c700) at pthread_create.c:333 #11 0x7f6a5093ab5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7f6a271c4700 (LWP 7627)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at
[plasmashell] [Bug 358719] fcitx creates blank unusable xembed icon in systray
https://bugs.kde.org/show_bug.cgi?id=358719 --- Comment #12 from Sergio --- OK! Thanks. Got the impression the fix was already in 5.5.5. I'll wait for 5.6 that should be in the kubuntu ppa soon then. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358719] fcitx creates blank unusable xembed icon in systray
https://bugs.kde.org/show_bug.cgi?id=358719 Sergio changed: What|Removed |Added CC||sergio.calleg...@gmail.com --- Comment #10 from Sergio --- Similar issue on Kubuntu 16.04, that ships with plasma 5.5.5. Hence plasma 5.5 does not solve the issue. Please reopen. At times the icons do not appear, at times they appear but still they are not functional (i.e. clicking on them does nothing). The issue seems to be fully repeatable with jitsi (the java based voip client), see https://jitsi.org/. Jitsi should make the problem easy to reproduce since it has packages ready for most distros and logs a lot of information. Among the information provided by the jitsi log you always find complaints about the systray that did not init properly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360958] Instant Messaging
https://bugs.kde.org/show_bug.cgi?id=360958 Sergio changed: What|Removed |Added CC||smlore...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 360058] Kscreen should check screen at wakeup from suspend
https://bugs.kde.org/show_bug.cgi?id=360058 --- Comment #1 from Sergio --- Note that whenever the system remains "usable enough" at 6) to perform some action, a workaround for the issue is to switch to a text console and to issue a killall kscreen_backend_launcher with this the kscreen backend is restarted and a subsequent visit to the systems settings lets one see the correct monitor setup (apart from the resolution that often remains messed, but that can be adjusted manually at this point). Unfortunately the killall of the kscreen_backend_launcher may cause the system settings process to segfault if it is already open. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 360058] New: Kscreen should check screen at wakeup from suspend
https://bugs.kde.org/show_bug.cgi?id=360058 Bug ID: 360058 Summary: Kscreen should check screen at wakeup from suspend Product: KScreen Version: 5.5.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: common Assignee: se...@kde.org Reporter: sergio.calleg...@gmail.com When using a laptop together with an external monitor/connector, a typical workflow involves 1) work work work 2) close lid 3) detach connectors (usb/powersupply/monitor) 4) do something else, move to another place 5) place laptop on desk, attach connectors (usb/powersupply/monitor) 6) open lid 7) work work work With this, the external monitor gets changed while the laptop is suspended. In KDE, kscreen completely misses this fact. The result is that at step 6) the presence of an external monitor different enough from the one used at point 3) or the fact that at 3) one has an external monitor and at 6) one has not or viceversa causes the system to be unusable or to crash. Kscreen should check the screen configuration when the system wakes up from sleep. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 340290] KDE print dialog does not report printer location
https://bugs.kde.org/show_bug.cgi?id=340290 Sergio changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #2 from Sergio --- This seems to be resolved in newer versions of KDE framework. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359118] Extremely poor rendering of Verdana bold font embedded as CID Truetype (subset)
https://bugs.kde.org/show_bug.cgi?id=359118 --- Comment #7 from Sergio --- Thanks for the almost instantanous diagnosis, I'll open the bug for poppler. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359118] Extremely poor rendering of Verdana bold font embedded as CID Truetype (subset)
https://bugs.kde.org/show_bug.cgi?id=359118 --- Comment #5 from Sergio --- Created attachment 97076 --> https://bugs.kde.org/attachment.cgi?id=97076&action=edit Sample rendering of text -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359118] Extremely poor rendering of Verdana bold font embedded as CID Truetype (subset)
https://bugs.kde.org/show_bug.cgi?id=359118 --- Comment #4 from Sergio --- Also firefox with pdf.js renders OK. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359118] Extremely poor rendering of Verdana bold font embedded as CID Truetype (subset)
https://bugs.kde.org/show_bug.cgi?id=359118 --- Comment #3 from Sergio --- Version is in fact 0.23.2 Using KDE Development Platform 4.14.15 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359118] Extremely poor rendering of Verdana bold font embedded as CID Truetype (subset)
https://bugs.kde.org/show_bug.cgi?id=359118 --- Comment #2 from Sergio --- Created attachment 97075 --> https://bugs.kde.org/attachment.cgi?id=97075&action=edit Sample document -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359118] New: Extremely poor rendering of Verdana bold font embedded as CID Truetype (subset)
https://bugs.kde.org/show_bug.cgi?id=359118 Bug ID: 359118 Summary: Extremely poor rendering of Verdana bold font embedded as CID Truetype (subset) Product: okular Version: 0.23.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: sergio.calleg...@gmail.com Opening a document containing the font in subject, its rendering is extremely poor and almost unreadable. Acroread for linux renders the font just fine. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359059] FictionBook: Incorrect whitespace treatment
https://bugs.kde.org/show_bug.cgi?id=359059 Sergio changed: What|Removed |Added CC||sergio.pokrovs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359059] FictionBook: Incorrect whitespace treatment
https://bugs.kde.org/show_bug.cgi?id=359059 --- Comment #2 from Sergio --- Created attachment 97043 --> https://bugs.kde.org/attachment.cgi?id=97043&action=edit A correct rendition by CoolReader -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359059] FictionBook: Incorrect whitespace treatment
https://bugs.kde.org/show_bug.cgi?id=359059 --- Comment #1 from Sergio --- Created attachment 97042 --> https://bugs.kde.org/attachment.cgi?id=97042&action=edit test file t.fb2 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359059] New: FictionBook: Incorrect whitespace treatment
https://bugs.kde.org/show_bug.cgi?id=359059 Bug ID: 359059 Summary: FictionBook: Incorrect whitespace treatment Product: okular Version: 0.20.3 Platform: Ubuntu Packages URL: http://pok.heliohost.org/unix/t.fb2 OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: sergio.pokrovs...@gmail.com 1. I could not find the "FictionBook Backend" in the menu. So I am writing to "general". 2. My Synaptic does not show any update for my "Version 0.19.3; Using KDE Development Platform 4.13.3" nor "Fiction Book Backend Version 0.1.5"; these version too are not available in the bugtracker menu. 3. THE PROBLEM. When presenting a Fictionbook file Okular does not collapse extra spaces between and ; it does not treat line breaks in the source text as a space. As a result a structured source text is rendered with unwanted spaces and newlines. This is a deviation from XML Spec (Section 2.10: White Space). 4. Another problem is that the element is silently ignored. Reproducible: Always Steps to Reproduce: 1. Please download a test book (1.2k): http://pok.heliohost.org/unix/t.fb2 2. Open t.fb2 in Okular. Actual Results: What I see with Okular is http://pok.heliohost.org/unix/okular.png Please note unwanted line break after "One"; unwanted spaces before "two" and "six". Please note the missing attribution of the quotation. Expected Results: The expected (correct) rendition (by CoolReader) is shown at http://pok.heliohost.org/unix/cr3.png Basically, something like this: , | One two three. | Four five six. | Nine. | Ten. | | , | | In editing XML documents, it is often convenient to use “white | | space” (spaces, tabs, and blank lines) to set apart the markup for | | greater readability. Such white space is typically not intended | | for inclusion in the delivered version of the document. | ` XML 1.0 Spec, 2.10 (White Space Handling) ` -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 351785] Crash when clicking 'Configure...' button in Accounts settings
https://bugs.kde.org/show_bug.cgi?id=351785 Sergio changed: What|Removed |Added CC||sergio.calleg...@gmail.com --- Comment #67 from Sergio --- I see the same issue with plasma 5.5.3 and framework 5.18.0 with the latest kubuntu updates on ubuntu 15.10. Pressing configure crashes plasma. Is there anything that I am missing? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 341930] Session management in porting preproc branch
https://bugs.kde.org/show_bug.cgi?id=341930 Sergio changed: What|Removed |Added CC|sergio.calleg...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348753] more issues with nvidia legacy (304.xxx) blob and explicit syncing (here on login)
https://bugs.kde.org/show_bug.cgi?id=348753 --- Comment #45 from Sergio --- I got the whole of the array of updates that arrived via the Kubuntu ppa and that included 5.4.3. It may have not been kwin in the end, but maybe some animation effect or something in the theme. I must admit that I have not been diligent enough to try disabling the effects one by one or try changing the theme. The issue was as follow: - Plasma started providing a screen that was looking OK - Immediately after that the bottom panel got distorted and everything hung - Using Ctrl-Alt-F1 and Ctrl-Alt+F7 I could go back and forth between the text console and X and in this way plasma seemed to be able to perform operations one step "per switch". In any case, the system with 7025 and nvidia 304 is usable again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348753] more issues with nvidia legacy (304.xxx) blob and explicit syncing (here on login)
https://bugs.kde.org/show_bug.cgi?id=348753 --- Comment #43 from Sergio --- Hi, I have just noticed that the version of kwin in 5.4.3 (that I got from the kubuntu ppa) works again with the KWIN_EXPLICIT_SYNC=0 trick. It was only 5.4.2 failing. Good news on this front. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 352055] plasma-pa plasmoid not shown in systemtray after startup
https://bugs.kde.org/show_bug.cgi?id=352055 Sergio changed: What|Removed |Added CC|sergio.calleg...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 352055] plasma-pa plasmoid not shown in systemtray after startup
https://bugs.kde.org/show_bug.cgi?id=352055 --- Comment #26 from Sergio --- I would not hold my breath waiting for distros to backport things or apply patches downstream E.g., the issue with hplip not being able to work on plasma 5 has been having a patch since 2014-07-29 thanks to Harald Sitter, but still, after more than 1 year the patch is not applied in (K)ubuntu... Is there any news of some distro picking up Qt 5.6 for their next release? Will (K)ubuntu 16.04 be 5.6 or 5.5.x? -- You are receiving this mail because: You are watching all bug changes.