<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.kde.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugs.kde.org/"
          
          maintainer="sysadmin@kde.org"
>

    <bug>
          <bug_id>359661</bug_id>
          
          <creation_ts>2016-02-22 06:51:20 +0000</creation_ts>
          <short_desc>Digital clock is not updated consistently</short_desc>
          <delta_ts>2016-08-25 19:33:41 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>4</classification_id>
          <classification>Plasma</classification>
          <product>plasmashell</product>
          <component>Digital Clock widget</component>
          <version>5.7.1</version>
          <rep_platform>Gentoo Packages</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>DUPLICATE</resolution>
          <dup_id>353983</dup_id>
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>NOR</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>1.0</target_milestone>
          
          
          <everconfirmed>0</everconfirmed>
          <reporter name="Fabio Coatti">fabio.coatti</reporter>
          <assigned_to name="Martin Klapetek">mklapetek</assigned_to>
          <cc>bugs.kde.org</cc>
    
    <cc>donjajo4all</cc>
    
    <cc>kde</cc>
    
    <cc>kde</cc>
    
    <cc>kde</cc>
    
    <cc>plasma-bugs-null</cc>
          
          <cf_commitlink></cf_commitlink>
          <cf_versionfixedin></cf_versionfixedin>
          <cf_sentryurl></cf_sentryurl>
          <votes>0</votes>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>1577936</commentid>
    <comment_count>0</comment_count>
    <who name="Fabio Coatti">fabio.coatti</who>
    <bug_when>2016-02-22 06:51:20 +0000</bug_when>
    <thetext>The time shown by digital clock in default panel (lower right bottom) is updated with some delay or even jumping some seconds. Say, from :49 it goes to :51. I&apos;ve seen that also for minutes, when I configured it to do not show seconds.
It seems to have this behaviour only in 5.5.4, but I can&apos;t be sure of this. 
My usual config is to show seconds, timezone and long date format.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1578452</commentid>
    <comment_count>1</comment_count>
    <who name="Kai Uwe Broulik">kde</who>
    <bug_when>2016-02-24 14:20:57 +0000</bug_when>
    <thetext>When you open Kickoff (&quot;the start menu&quot;) and hover entries there, do you also only have every second item highlighted as you move around? If so, this is a driver issue.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1578455</commentid>
    <comment_count>2</comment_count>
    <who name="Fabio Coatti">fabio.coatti</who>
    <bug_when>2016-02-24 14:24:23 +0000</bug_when>
    <thetext>Yep, exactly so!

the higlight happens only on second item, good catch. What driver are you referring to? video card? something in mesa layer?

Many thanks for the answer!</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1579037</commentid>
    <comment_count>3</comment_count>
    <who name="Jajo">donjajo4all</who>
    <bug_when>2016-02-26 10:10:55 +0000</bug_when>
    <thetext>Same issue here
I use Debian Stretch and Plasma 5</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1607882</commentid>
    <comment_count>4</comment_count>
    <who name="Fabio Coatti">fabio.coatti</who>
    <bug_when>2016-07-14 07:49:41 +0000</bug_when>
    <thetext>After a while, the issue is reappeared. I don&apos;t think is related to xf86-intel driver (I&apos;m on 2.99.917 and I&apos;ve also tried to downgrade it).

Now I&apos;m on plasma 5.7.1 (same behaviour on 5.7.0), gentoo packages. I can provide all information required or try different versions of packages, just let me know.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1610508</commentid>
    <comment_count>5</comment_count>
    <who name="Erik Quaeghebeur">bugs.kde.org</who>
    <bug_when>2016-07-25 21:34:47 +0000</bug_when>
    <thetext>I can confirm this behavior on plasma 5.5.5. It appears it&apos;s also been reported elsewhere: https://bugzilla.redhat.com/show_bug.cgi?id=1307178</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1610738</commentid>
    <comment_count>6</comment_count>
    <who name="">kde</who>
    <bug_when>2016-07-26 23:15:39 +0000</bug_when>
    <thetext>I can confirm this behavior on Plasma 5.6.5 (using backports PPA on Kubuntu 16.04). The clock widget only seems to update once every two seconds. Occasionally it&apos;ll show two consecutive seconds. My usual display is 24-hour time with seconds and long date, e.g.

16:10:26
Tuesday, July 26, 2016

I thought maybe it might have something to do with the fact that I normally have two clock widgets, one at the right edge of the bottom panel on each of my two monitors, but I removed one of the clocks and the other clock still only updates every ~2 seconds or so.

Also, Plasmashell is currently using about 30% CPU according to GNU top. (By contrast, on my old 14.04 machine, plasma-desktop is currently using about 0.7% CPU.) I killed plasmashell (with &quot;kdequitapp5 plasmashell&quot;) and then ran plasmashell &amp; again, and now it&apos;s using around 1% CPU, and the clock widget is updating every second.

So it looks like it&apos;s not a bug with the clock per se, but the fact that Plasmashell eventually decides to just start chewing up tons of CPU for no apparent reason.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1610806</commentid>
    <comment_count>7</comment_count>
    <who name="Erik Quaeghebeur">bugs.kde.org</who>
    <bug_when>2016-07-27 09:04:11 +0000</bug_when>
    <thetext>(I&apos;m now at Plasma 5.6.5.1)

(In reply to kde from comment #6)
&gt;
&gt; Also, Plasmashell is currently using about 30% CPU according to GNU top. [...]
&gt; I killed plasmashell (with &quot;kdequitapp5 plasmashell&quot;) and then
&gt; ran plasmashell &amp; again, and now it&apos;s using around 1% CPU, and the clock
&gt; widget is updating every second.
&gt; 
&gt; So it looks like it&apos;s not a bug with the clock per se, but the fact that
&gt; Plasmashell eventually decides to just start chewing up tons of CPU for no
&gt; apparent reason.

I get the second-skipping behavior even when plasma eats no discernible amount of cpu resources. So although this may also cause this issue, or exacerbate it, it cannot be the root cause.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1610808</commentid>
    <comment_count>8</comment_count>
    <who name="Erik Quaeghebeur">bugs.kde.org</who>
    <bug_when>2016-07-27 09:09:46 +0000</bug_when>
    <thetext>(In reply to Fabio Coatti from comment #4)
&gt;
&gt; xf86-intel driver (I&apos;m on 2.99.917 [...]).

N.B.: I&apos;m using the same driver and also have the entry-skipping behavior.

Do all affected people use the (this?) intel driver?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1610873</commentid>
    <comment_count>9</comment_count>
    <who name="">kde</who>
    <bug_when>2016-07-27 14:22:54 +0000</bug_when>
    <thetext>(In reply to Erik Quaeghebeur from comment #8)
&gt; (In reply to Fabio Coatti from comment #4)
&gt; &gt; xf86-intel driver (I&apos;m on 2.99.917 [...]).
&gt; 
&gt; N.B.: I&apos;m using the same driver and also have the entry-skipping behavior.
&gt; Do all affected people use the (this?) intel driver?

Yeah, I&apos;m using that same driver too.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1616649</commentid>
    <comment_count>10</comment_count>
    <who name="David Edmundson">kde</who>
    <bug_when>2016-08-25 01:47:18 +0000</bug_when>
    <thetext>

*** This bug has been marked as a duplicate of bug 353983 ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1616675</commentid>
    <comment_count>11</comment_count>
    <who name="Fabio Coatti">fabio.coatti</who>
    <bug_when>2016-08-25 06:54:15 +0000</bug_when>
    <thetext>I tried to remove xf86-intel driver completely, relying on kms setup, and the issue disappeared. I don&apos;t really know what are the drawbacks, maybe the grpahics (not really sure, though) are a bit slower but for my usage it is fine.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1616778</commentid>
    <comment_count>12</comment_count>
    <who name="Erik Quaeghebeur">bugs.kde.org</who>
    <bug_when>2016-08-25 19:33:41 +0000</bug_when>
    <thetext>(In reply to David Edmundson from comment #10) 
&gt; 
&gt; *** This bug has been marked as a duplicate of bug 353983 ***

David, I don&apos;t see how this is a duplicate. Can you explain?</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>