[systemsettings] [Bug 345234] Adding/Removing fonts shows wait dialog forever

[Walter Nicholls via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=345234

--- Comment #18 from Walter Nicholls  ---
  Christoph Feck  marked bug 349673  as a dupe of this one, and I just accepted
it, but indeed the description doesn't match up.   I should have read more
closely than just accepting. Reposting on that other bug , although I don't
have the rights to mark it as "unresolved".

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 349673] kcm_fontinst: Backend crashes on systemwide fonts installations

[Walter Nicholls via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=349673

--- Comment #4 from Walter Nicholls  ---
I hope someone with the rights to reopen this bug can reopen it.   If I search
KDE bugs for the string "backend died, but it has been restarted"  this is the
only entry I can find.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 349673] kcm_fontinst: Backend crashes on systemwide fonts installations

[Walter Nicholls via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=349673

Walter Nicholls  changed:

   What|Removed |Added

 CC||wal...@nic.gen.nz

--- Comment #3 from Walter Nicholls  ---
This bug is NOT a duplicate of bug 345234 !

I also confirm still a problem on Kubuntu 15.10 - fully up-to-date. Two
separate computers. Attempt to install 2 of more fonts systemwide - asks for
sudo and then crashes on the second font. 1. Add 2. Select two TTF files 3. "Do
you wish to install the font(s) for personal use (only available to you), or
system-wide (available to all users)?" - select SYSTEM 4. "Modifying the
system-wide font configuration requires privileges." - enter password and OK 5.
"Error Backend died, but has been restarted. Please try again." observed -
first font in selection has been expected - no error message at (5) and all
fonts installed at once. This bug reported in 2015 but I'm pretty sure it was
going on years before that. (I don't install fonts very often). 

Apparently this is still a problem in Plasma 5.6.2.  
*** NO IT IS NOT RESOLVED BY ANY STRETCH OF THE IMAGINATION  ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 345234] Adding/Removing fonts shows wait dialog forever

[Walter Nicholls via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=345234

Walter Nicholls  changed:

   What|Removed |Added

 CC||wal...@nic.gen.nz

--- Comment #16 from Walter Nicholls  ---
Confirm still a problem on Kubuntu 15.10  - fully up-to-date. Two separate
computers.

Attempt to install 2 of more fonts systemwide - asks for sudo and then crashes
on the second font.

1.  Add
2.  Select two TTF files
3. "Do you wish to install the font(s) for personal use (only available to
you), or system-wide (available to all users)?"  - select SYSTEM
4. "Modifying the system-wide font configuration requires privileges."  - enter
password and OK
5. "Error   Backend died, but has been restarted. Please try again."

observed - first font in selection has been 
expected - no error message at (5) and all fonts installed at once.

This bug reported 2015-03  but I'm pretty sure it was going on years before
that.  (I don't install fonts very often).

Since commit was to Plasma 5.4, then seems iike that it will be solved in
Kubuntu 16.04 (which ships Plasma 5.5) . Here's hoping.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related

[Walter Nicholls via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=343661

--- Comment #62 from Walter Nicholls  ---
After that last comment, of course the problem reoccurred this evening.  (ha ha
ha...)   External monitor not plugged in at moment, although it had been
several times since last reboot.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related

[Walter Nicholls via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=343661

--- Comment #61 from Walter Nicholls  ---
I haven't seen this problem reoccur for me in the last month. Maybe a software
patch has changed behaviour:
Kernel now 4.2.0-35-generic 
plasma-workspace at  4:5.4.2-0ubuntu1.1
nvidia-352  version 352.63-0ubuntu0.15.10.1
(I'm not sure which packages are actually relevant to this).

Other family members with KDE computers haven't ever seen this, by the way,
although my wife did have a problem which toggling Alt-Ctrl-F12 fixed for her.
Something about the plasma bar getting corrupted? Could have been same issue.
Fairly old Toshiba laptop with intel video.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related

[Walter Nicholls via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=343661

--- Comment #55 from Walter Nicholls  ---
OK that didn't seem to fix it.   kwin_x11 process definitely has environment
variable set:

walter@rukbat:~$ xargs --null --max-args=1 < /proc/`pidof kwin_x11`/environ |
grep KWIN
KWIN_EXPLICIT_SYNC=0

This occurred with firefox, had about 3 tabs open, then opened two new tabs
(with Ctrl-Click on link) - they 'seemed' to be taking a long time. Then I
realised why...
Then it "infected" the next firefox window,  the one I was adding this comment
on.
So once occurred - can click on each tab in the firefox window and the TITLE
BAR changes (eg to 
"New Tab - Mozilla Firefox" ,  then "Slashdot: News for nerds ... - Mozilla
Firefox"  etc) but the client area of the window is not redrawn.  That includes
scrollbars, the tab bar itself, menu bar (although menus themselves pop down:
probably they are new windows).   I can right-click on tab and select "Move to
New Window" which is what I've just done to type this!

Pressing Shift-Alt-F12 twice (to toggle the compositor) repairs the problem and
the window starts updating again.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related

[Walter Nicholls via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=343661

--- Comment #56 from Walter Nicholls  ---
I still haven't tracked down a trigger, but I did wonder about these:
  - I've only ever seen this when external monitor is plugged in.  But that is
90% of the work day..
  - or maybe, I have a Windows 7 VM in VirtualBox, full-screened on my external
monitor. Again, that's not uncommon in my work day.
Don't want to get hung up on the dual-monitor thing, but it might explain why
this problem isn't more widespread.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related

[Walter Nicholls via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=343661

--- Comment #54 from Walter Nicholls  ---
(In reply to Thomas Lübking from comment #53) You can only sync to one screen -
HW limitation
Yes, I know, but the tearing started around the same time, after a year or more
of no display issues at all, so I wondered if they could be related. It doesn't
look like they are, so we can drop discussing it here! Thanks, though.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related

[Walter Nicholls via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=343661

--- Comment #44 from Walter Nicholls  ---
It might take a while but I'll experiment. I'll wait for repaint issue to
reoccur first and see what Shlft-Alt-F12 does, then of course will have to wait
again, possibly for several weeks, to be sure it is gone away with the SYNC
setting. I'm guessing 

Thanks for your attention to this bug.  So often I look up annoying behaviour
and find that a bug is logged but seems to be abandoned.  I'm a bit motivated
to get some of these bugs squashed -  I love KDE/Kubuntu but am seriously
having to consider whether to switch OSes (at worst, to Windows) to get
stability on my work machine.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related

[Walter Nicholls via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=343661

--- Comment #45 from Walter Nicholls  ---
> I'm guessing 
Oops, meant:  I'm guessing there might be a performance penalty with this
setting?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related

[Walter Nicholls via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=343661

--- Comment #47 from Walter Nicholls  ---
I've just created   ~/.config/plasma-workspace/env/kwin.sh with that setting as
noted on some similar bugs. It will be few days before I am sure it fixes
anything!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related

[Walter Nicholls via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=343661

--- Comment #51 from Walter Nicholls  ---
So in an attempt to  work around one bug I discover another bug, a commit that
frankly should never have hit trunk.  Big Sigh!  As I said, "seriously having
to consider whether to switch OS"  oh well, I've applied the patch in the
hope that Kubuntu won't distribute another borked version, and hopefully will
see both this probably and the dual-monitor repaint/tearing issue go.  Thanks
for all your assistance this weekend.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related

[Walter Nicholls via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=343661

--- Comment #49 from Walter Nicholls  ---
Sage advice, Thomas.  This is odd. Did not survive a reboot.  It runs the
script but doesn't set the setting.  This might be getting a bit off topic, but
looks like it is time to further debug kde.  I hope this formats ok and makes
sense.

kwin.sh contains (extra logging to prove it ran and did its job, or not, as is
the case)
  #!/bin/sh
  echo kwin.sh was run! >>/var/log/kde_debug_temp.log
  echo In script Before KWIN_EXPLICIT_SYNC is: $KWIN_EXPLICIT_SYNC 
>>/var/log/kde_debug_temp.log
  export KWIN_EXPLICIT_SYNC=0
  echo In script After KWIN_EXPLICIT_SYNC is: $KWIN_EXPLICIT_SYNC 
>>/var/log/kde_debug_temp.log

If, from bash prompt, I run /home/walter/.config/plasma-workspace/env/kwin.sh  
then as expected nothing is set;  if I source
/home/walter/.config/plasma-workspace/env/kwin.sh  then KWIN_EXPLICIT_SYNC is
set afterwars as expected. If I create newtest.sh  containing only  the line " 
.  kwin.sh "  then KWIN_EXPLICIT_SYNC is set as expected (well ,for the
duration of the script anyway since it isn't itself sourced).

However if I modify startkde so that it contains logging
echo In startkde Before KWIN_EXPLICIT_SYNC is: $KWIN_EXPLICIT_SYNC 
>>/var/log/kde_debug_temp.log
for prefix in `echo $scriptpath`; do
  for file in "$prefix"/env/*.sh; do
(test -r "$file" && . "$file") || :
  done
done
echo In startkde After KWIN_EXPLICIT_SYNC is: $KWIN_EXPLICIT_SYNC 
>>/var/log/kde_debug_temp.log

Now reboot and look at the log file , it shows:
  In startkde Before KWIN_EXPLICIT_SYNC is: 
  In script Before KWIN_EXPLICIT_SYNC is:   
  In script After KWIN_EXPLICIT_SYNC is: 0  
  In startkde After KWIN_EXPLICIT_SYNC is:   

So my script is DEFINITELY executing, it is DEFINITELY setting the env var, but
that extra indirection in startkde -  (test -r "$file" && . "$file") - 
is enough to stop the setting from taking.  So how 

[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related

[Walter Nicholls via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=343661

Walter Nicholls  changed:

   What|Removed |Added

 CC||wal...@nic.gen.nz

--- Comment #42 from Walter Nicholls  ---
I can report I get this with annoying regularilty, Kubuntu 15.10, NVidia (HP
Envy laptop).  It seems to have occurred since 15.04:  a window simply stops
being refreshed unless it is resized.  

The problem is attached to the window, not the application: using Chrome or
Firefox, I can drag a tab out into its own window and that new window updates
fine, I can even drag all the tabs one by one onto the new one until the old
window is empty (and thus destroys). (Until it occurs again on the new window,
sigh!).Not all applications can be recovered this way . It's particularly
annoying with virtual machines where the only way to get a new window is to
shut the VM down (or at least, sleep it).

I have not found any pattern in when a window decides to stop updating. 

(A second thing that may or may not be related, but I'm mentioning it for
completeness:  if I plug in a second monitor , then I also get a lot of tearing
or incomplete paints. I first noticed this on a image view program - as each
new image was displayed it would be blurry or leave some of the previous image
in view. It's not just that program, seen it with Virtualbox as well. However
in this case, wiggling the mouse forces the window to paint correctly, even if
the mouse doesn't travel over the corrupt area;  and I've only ever seen it
happen on the external monitor).

I'm very interested to hear that kwin_x11 --replace might solve/reset the
problem, I'll definitely try this next time.
I notice bug is 12 months old, about 4 people are reporting it, yet it still
has status "unconfirmed". What does it take to confirm a bug then? 

-- 
You are receiving this mail because:
You are watching all bug changes.