In README, 2.2.1. Step 1 says I need to add ”execute pathogen#infect()” to .vimrc, while the second point in the checklist at the end of 2.2.2. Step 2 says it should have been ”call pathogen#infect()”. I’m guessing both work, but it should probably be consistently the same in the instructions.

IN 12.04 at least, this seems to be tied to Xorg’s blanking which by default happens after 10 minutes/600 seconds. It can be unset via xset on the commandline, but I finally managed to do this via xorg.conf, like so:

jani@saegusa:~$ cat /etc/X11/xorg.conf.d/*
Section ”Extensions”
Option ”DPMS” ”Disable”
Option ”MIT-SCREEN-SAVER” ”Disable”
EndSection

Section ”Device”
Identifier ”Intel Graphics”
Driver ”intel”
Option ”DPMS” ”Disable”
EndSection

Section ”ServerFlags”
Option ”NoPM” ”true”
EndSection

Section ”ServerLayout”
Identifier ”X.org Configured”
Option ”BlankTime” ”0”
Option ”StandbyTime” ”0”
Option ”SuspendTime” ”0”
Option ”OffTime” ”0”
EndSection

It could be that just the ServerLayout section is actually required (and I’m not sure if other graphics drivers even have a DPMS option of their own like intel does), as none of the other sections by themselves nor together prevented the screen from turning off. (The most confusing one is MIT-SCREEN-SAVER, which I thought was exactly what the xset timeouts were controlling, but apparently not so, as disabling it does not prevent the issue either.)

Thanks Michael. I’ve added lxpanel as being affected, hopefully someone there can take a look.

The indicator blinks between what looks like an empty graph (in a vertically shorter box) and the actual graph (in a full-sized box). This is best demonstrated in a video so I’m attaching one below.

Both the official repository version (0.4) and the one from daily PPA (0.5) exhibit this. Different color schemes don’t seem to affect it (i.e. the problem remains). There’s further problems when I add a third graph, but this report is just about the blinking.

(Bug #1336828 is about the indicator missing entirely in 14.04, so I decided to report this slightly different issue separately.)

• Indicator (0.5) blinking in Lubuntu 14.10 Edit (1.1 MiB, video/ogg)

For the ’Incorrect padding’ issue, Bug #1012358. (Leaving this as non-duplicate, since the reporter has other ’damaged’ errors besides that one.)

I acknowledge that (and as I said, it hasn’t really caused any issues with the backups), I was just responding to this being ”fixed” (above). If it’s not really an issue in the code, maybe we should close this as invalid? (Although I could argue that the message makes it seem as if there is a problem with the code when in fact there isn’t, so the bug could be ”this warning is slightly misleading”. But that’s up for interpretation.)

Sorry, but 5.0.0-1ubuntu1 didn’t fix this. In Utopic, with the same ’The Snowman’ DVD as before, I still get:

*** Zero check failed in src/ifo_read.c:903
for pgc->subp_control[i] = 0x00000001
*** Zero check failed in src/ifo_read.c:903
for pgc->subp_control[i] = 0x00000001
*** Zero check failed in src/ifo_read.c:903
for pgc->subp_control[i] = 0x00000001

jani@ubudev:~/lumiukko$ apt-cache policy libdvdread4
libdvdread4:
Installed: 5.0.0-1ubuntu1
Candidate: 5.0.0-1ubuntu1
Version table:
*** 5.0.0-1ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages
100 /var/lib/dpkg/status

I’ve worked around that enum error (since before owncloud 7 already) by adding this in 3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Platforms/MySqlPlatform.php:

@@ -661,6 +661,7 @@
     protected function initializeDoctrineTypeMappings()
     {
         $this->doctrineTypeMapping = array(
+            'enum' => 'string',
             'tinyint'       => 'boolean',
             'smallint'      => 'smallint',
             'mediumint'     => 'integer',

Reopening. It didn’t go away after all, looks like the occurrence varies (didn’t see it yesterday), perhaps those Chromium settings just made it more probable.

I take that back, it seems to have been caused by Chromium all along (more specifically either #threaded-compositing-mode or #deadline-scheduling), despite those glitches appearing outside of Chromium too. Sot it’s a Chromium bug, but I’m too lazy to debug this further (the issue goes away with those configuration flags set to default) so I’ll just mark this as invalid.