Bug#860296: lirc is spamming syslog with messages

[Ayke van Laethem]

Package: lirc
Version: 0.9.4c-9
Followup-For: Bug #860296

Dear Maintainer,

Unfortunately I can't reproduce the uirw issue I reported (eating up
disk space), but I now have the exact same problem as reported above.

I noticed that by default the services lircd-uinput, irexec and lircmd
are running. Stopping all three makes sure that lirc doesn't have
connected clients preventing the error. I wonder why all these services
are running by default, consuming system resources (and logging a
message once per second).

Semi-related: here is a patch that should make the error somewhat more
descriptive (actually fixing a bug in LIRC):
https://sourceforge.net/u/avl555/lirc/ci/7b25283ef0393035d82cb0a10fe7331fc4629c44/

Bug#860296: lirc is spamming syslog with messages

[Ayke van Laethem]

Package: lirc
Version: 0.9.4c-9
Followup-For: Bug #860296

Dear Maintainer,

I believe this is a real bug. The problem is not that it logs the error
(which it should), the problem is that it *keeps* logging the error
without any form of throttling quickly filling the whole syslog:

$ ls -l /var/log/syslog
-rw-r- 1 root adm 4,2G jul 28 16:33 /var/log/syslog

Sample from syslog:
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Error: uirt2:
reading of byte 0 failed
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Invalid argument
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Error: uirt2:
reading of byte 0 failed
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Invalid argument
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Error: uirt2:
reading of byte 0 failed
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Invalid argument
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Error: uirt2:
reading of byte 0 failed
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Invalid argument

This became a problem during the upgrade from jessie to stretch. During
a large part of the upgrade my whole root disk was filled with useless
log messages (0 bytes free storage), so I'm actually surprised it
finished upgrading without issues. Upgrading is a critical operation so
I would consider this an important bug.

The configuration files attached here *should* be enough to reproduce
the issue. I am willing to provide the original configuration files that
I used.

In my opinion, lirc should be fixed to not retry this often or fail the
first time - there's no use in retrying with an invalid configuration.

A workaround is disabling lirc in stretch:

systemctl disable lirc


-- System Information:
Debian Release: 9.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lirc depends on:
ii  init-system-helpers  1.48
ii  libasound2   1.1.3-5
ii  libc62.24-11+deb9u1
ii  libftdi1-2   1.3-2+b2
ii  libgcc1  1:6.3.0-18
ii  liblirc-client0  0.9.4c-9
ii  liblirc0 0.9.4c-9
ii  libportaudio219.6.0-1
ii  libstdc++6   6.3.0-18
ii  libsystemd0  232-25+deb9u1
ii  libudev1 232-25+deb9u1
ii  libusb-0.1-4 2:0.1.12-30
ii  libusb-1.0-0 2:1.0.21-1
ii  lsb-base 9.20161125
ii  python3  3.5.3-1

Versions of packages lirc recommends:
pn  gir1.2-vte
ii  python3-gi3.22.0-2
ii  python3-yaml  3.12-1

Versions of packages lirc suggests:
pn  ir-keytable  
pn  lirc-compat-remotes  
pn  lirc-doc 
pn  lirc-drv-irman   
pn  lirc-x   
pn  setserial

-- Configuration Files:
/etc/lirc/hardware.conf changed:
LIRCD_ARGS=""
LOAD_MODULES=false
DRIVER="uirt2"
DEVICE="/dev/ttyACM0"
MODULES=""
LIRCD_CONF=""
LIRCMD_CONF=""

/etc/lirc/lircd.conf changed:
begin remote
  name  philips
  bits   32
  eps30
  aeps  100
  one 0 0
  zero0 0
  post_data_bits  16
  post_data  0x0
  gap  114685
  toggle_bit_mask 0xF5108D99
  begin codes
  KEY_LEFT 0x97309DDB
  KEY_LEFT 0x6E3215BE
  KEY_RIGHT0x6FA99F00
  KEY_UP   0xA79C13E5
  KEY_DOWN 0xFB6351AD
  KEY_FORWARD  0x2200
  KEY_REWIND   0x1408
  KEY_PLAYPAUSE0x1500
  KEY_MENU 0xFEF2B8BF
  KEY_INFO 0x0F00
  KEY_INFO 0x0F08
  KEY_MUTE 0x0D08
  KEY_VOLUMEUP 0x1000
  KEY_VOLUMEDOWN   0x1108
  end codes
end remote


-- no debconf information

Bug#864618:

[Ayke van Laethem]

The original patches fix the issue, but don't look very nice. There are now
better patches available (4 commits total, but still a small change):

https://github.com/mate-desktop/mate-themes/commit/b471395f38fa682bbc4d788703e9e3de38016310
https://github.com/mate-desktop/mate-themes/compare/fc73a47e8b842d7eb2bf973f377e23a574303ec0...c0f54222576aa829f83d79e8d92298959bfeaee3

I've attached these two patches (2nd one is combined).
From b471395f38fa682bbc4d788703e9e3de38016310 Mon Sep 17 00:00:00 2001
From: raveit65 
Date: Sat, 10 Jun 2017 07:57:46 +0200
Subject: [PATCH] Gtk+-3.20 BlackMATE: change menuitem accelerator font color

---
 desktop-themes/BlackMATE/gtk-3.0/gtk-widgets.css | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/desktop-themes/BlackMATE/gtk-3.0/gtk-widgets.css b/desktop-themes/BlackMATE/gtk-3.0/gtk-widgets.css
index a0242f41..4ee24cdb 100644
--- a/desktop-themes/BlackMATE/gtk-3.0/gtk-widgets.css
+++ b/desktop-themes/BlackMATE/gtk-3.0/gtk-widgets.css
@@ -2217,7 +2217,7 @@ menu > arrow:disabled,
 menuitem accelerator,
 menu menuitem accelerator,
 .menu menuitem accelerator {
-color: alpha(@theme_main_color, 0.66);
+color: alpha(@theme_fg_color, 0.66);
 }
 
 menuitem accelerator:hover,
diff --git a/desktop-themes/BlackMATE/gtk-3.0/other-applications.css b/desktop-themes/BlackMATE/gtk-3.0/other-applications.css
index e1d9a99e..9a90e573 100644
--- a/desktop-themes/BlackMATE/gtk-3.0/other-applications.css
+++ b/desktop-themes/BlackMATE/gtk-3.0/other-applications.css
@@ -305,3 +305,17 @@ window.background.yumex-dnf-window > box.vertical > box.vertical > box.horizonta
 background-color: shade(@less_dark_color, 2.4);
 }
 
+/**
+ * Google Chrome *
+ */
+
+.chromium textview.view,
+.chromium textview.view text {
+background-color: shade(@theme_bg_color, 1.15);
+color: @theme_selected_fg_color;
+}
+
+.chromium menubar:not(:backdrop) {
+background-color: shade(@theme_bg_color, 0.65);
+}
+

Bug#864618: mate-themes: BlackMATE makes Google Chrome 59 unreadable

[Ayke van Laethem]

Package: mate-themes
Version: 3.22.11-1
Severity: normal
Tags: patch

Dear Maintainer,

The most recent Google Chrome version switched to GTK3 [1]. Because of
this, most of the URL bar and some other parts of Chrome are now
unreadable. See the upstream bug [2] for more details.

The fix is really easy. Upstream has made two simple patches to fix the
issue:


https://github.com/mate-desktop/mate-themes/commit/b471395f38fa682bbc4d788703e9e3de38016310

https://github.com/mate-desktop/mate-themes/commit/bb1f13b4146eed2080c7f4b852fc4158a6973842

It would be great if these could be included in mate-themes.

[1]: https://bugs.chromium.org/p/chromium/issues/detail?id=79722#c110
[2]: https://github.com/mate-desktop/mate-themes/issues/182


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mate-themes depends on:
ii  gtk2-engines  1:2.20.2-3
ii  gtk2-engines-murrine  0.98.1.1-6
ii  gtk2-engines-pixbuf   2.24.31-2
ii  librsvg2-common   2.40.16-1+b1
ii  mate-icon-theme   1.16.2-1

Versions of packages mate-themes recommends:
ii  dmz-cursor-theme  0.4.4

mate-themes suggests no packages.

-- no debconf information

Bug#853288: Bug#851311: closed by Mike Gabriel <sunwea...@debian.org> (Bug#851311: fixed in caja 1.16.2-1)

[Ayke van Laethem]

> But they are in 3.22.6. Are you sure you have 3.22.6 of MATE Themes
> installed? Not sure why your are still having those issue.

I just reinstalled mate-themes (apt-get install --reinstall
mate-themes). This is version 3.22.6-1.
When I open the file
/usr/share/themes/BlackMATE/gtk-3.0/mate-applications.css at line ~219
it does not contain this line:

color: @theme_fg_color;

This line was added with one of the above commits. So I can only
conclude that the patch isn't included.

Bug#853288: Bug#851311: closed by Mike Gabriel <sunwea...@debian.org> (Bug#851311: fixed in caja 1.16.2-1)

[Ayke van Laethem]

> I have studied the recent mate-themes commits between 3.22.6 and 3.22.7 and
> I find nothing related to the above issues. All relevant commit went in
> before the 3.22.6 release.
>
> Can you please re-test your desktop session and report back, if the above
> issue really continues to exist? If yes, I need some commit between 3.22.6
> and 3.22.7 that actually fixes the situation for you. If possible. We'll
> have a chance of getting 3.22.7 into Debian stretch, but I need some
> feedback on this asap, if possible.

These two commits fix the problem for me:

https://github.com/mate-desktop/mate-themes/commit/e74e29105e664c7e204db5d1ba31b08e96b4cdbc
https://github.com/mate-desktop/mate-themes/commit/5bd6942ad7ed10fda2b4b41b8f0694063dc70afa

Bug#851311: closed by Mike Gabriel <sunwea...@debian.org> (Bug#851311: fixed in caja 1.16.2-1)

[Ayke van Laethem]

 BCqPf2VG20787Mt+MmVexRgA5MDRSTONW2W7f7HhktAlCkLxQ5mm69AibLvzFKl4
> vzklLDzUJN5YJJkuIgnGJwkhxlJoaGwFr9X5PXQKdN3WrS3XgJYmF2IifAEP0TVR
> 8b6GtDRgu3inGqKWziOuBIJSSiySzCRwezAf86h594lTa9IRfYiR3y5XPQDBe/km
> 4Qc+yoVgAHA19C1NEa8sDRYIphsbprZ/1Bkxqx9swQoeoi92WNLBmWxFAFHd92/k
> M7n/b/dBLdnOtP4QrlFmh7JDj8f+SrvXZR3fFVLX5vJW6bDn/Y6YKa5W9gs7H+2m
> laibfvcBFp7iLrTnLx/FyUUaS98+tv9EnkpYGyFhiQa4maVfolXI2ylsGyFfTfWh
> rdftEF0JqgqOEzJed9acNQ+OyySFVPqz/m+Y6/sojjCHQDGzVZZI5wlAanrBYLnG
> 4ucjjHaHdrQZ2oia/1ZW
> =1EUl
> -END PGP SIGNATURE-
>
> -- Doorgestuurd bericht --
> From: Ayke van Laethem <aykevanlaet...@gmail.com>
> To: Debian Bug Tracking System <sub...@bugs.debian.org>
> Cc:
> Date: Fri, 13 Jan 2017 22:39:51 +0100
> Subject: caja: invisible cursor in dark themes
> Package: caja
> Version: 1.16.1-1
> Severity: minor
> Tags: patch
>
> Dear Maintainer,
>
> When using a dark theme (E.g. BlackMATE), the cursor in the text box for
> renaming files often has a barely visible cursor.
> See the upstream bug: https://github.com/mate-desktop/caja/issues/688
>
> It has been fixed upstream and backported to 1.16, so simply updating to
> the latest version (of both caja and mate-themes) should fix the
> problem.
> Otherwise, the patches can be manually applied.
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (500, 'testing'), (500, 'stable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages caja depends on:
> ii  caja-common   1.16.1-1
> ii  desktop-file-utils0.23-1
> ii  gvfs  1.30.3-1
> ii  libatk1.0-0   2.22.0-1
> ii  libc6 2.24-8
> ii  libcairo-gobject2 1.14.8-1
> ii  libcairo2 1.14.8-1
> ii  libcaja-extension11.16.1-1
> ii  libexempi32.3.0-2
> ii  libexif12 0.6.21-2
> ii  libgail-3-0   3.22.5-1
> ii  libgdk-pixbuf2.0-02.36.2-1
> ii  libglib2.0-0  2.50.2-2
> ii  libglib2.0-data   2.50.2-2
> ii  libgtk-3-03.22.5-1
> ii  libice6   2:1.0.9-1+b1
> ii  libmate-desktop-2-17  1.16.1-1
> ii  libpango-1.0-01.40.3-3
> ii  libpangocairo-1.0-0   1.40.3-3
> ii  libselinux1   2.6-3
> ii  libsm62:1.2.2-1+b1
> ii  libstartup-notification0  0.12-4
> ii  libunique-3.0-0   3.0.2-2
> ii  libx11-6  2:1.6.4-2
> ii  libxext6  2:1.3.3-1
> ii  libxml2   2.9.4+dfsg1-2.1
> ii  libxrender1   1:0.9.10-1
> ii  mate-desktop  1.16.1-1
> ii  shared-mime-info  1.7-1
>
> Versions of packages caja recommends:
> ii  gvfs-backends  1.30.3-1
>
> Versions of packages caja suggests:
> ii  engrampa1.16.0-1
> pn  gstreamer1.0-tools  
> ii  meld3.16.4-1
>
> -- no debconf information
>

Bug#852724: golang-1.7: go install -race fails with "permission denied"

[Ayke van Laethem]

Package: golang-1.7
Version: 1.7.4-1
Severity: normal

Dear Maintainer,

Builting a trivial package using Go fails when enabling the race
condition checker. Example code:

---
package main

import (
"fmt"
)

func main() {
fmt.Println("Hello, World")
}
---

Put in src/go-hello/hello.go, built using:

go install -race go-hello

Fails with the following error:

go install runtime/internal/sys:
mkdir /usr/lib/go-1.7/pkg/linux_amd64_race: permission denied

The official Go binaries do not have this problem (from https://golang.org/dl).

It looks like the race-enabled packages are not built. The directory
/usr/local/go/pkg/linux_amd64_race/ contains many packages, while
/usr/lib/go-1.7/pkg/linux_amd64_race/ does not exist.


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages golang-1.7 depends on:
ii  golang-1.7-doc  1.7.4-1
ii  golang-1.7-go   1.7.4-1
ii  golang-1.7-src  1.7.4-1

golang-1.7 recommends no packages.

golang-1.7 suggests no packages.

-- no debconf information

Bug#841642:

[Ayke van Laethem]

This could even be seen as a security issue - the display isn't hidden
at all using the screen lock, the only thing it does is making it
impossible to interact with it. So it is visible what the user was
doing when leaving the computer for some time.

Upstream bug:
https://github.com/mate-desktop/mate-screensaver/issues/103

It appears to be fixed with this patch:
https://github.com/mate-desktop/mate-screensaver/pull/110

It would be nice if this could go into stable stretch.

-- Ayke

Bug#851311: caja: invisible cursor in dark themes

[Ayke van Laethem]

Package: caja
Version: 1.16.1-1
Severity: minor
Tags: patch

Dear Maintainer,

When using a dark theme (E.g. BlackMATE), the cursor in the text box for
renaming files often has a barely visible cursor.
See the upstream bug: https://github.com/mate-desktop/caja/issues/688

It has been fixed upstream and backported to 1.16, so simply updating to
the latest version (of both caja and mate-themes) should fix the
problem.
Otherwise, the patches can be manually applied.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages caja depends on:
ii  caja-common   1.16.1-1
ii  desktop-file-utils0.23-1
ii  gvfs  1.30.3-1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-8
ii  libcairo-gobject2 1.14.8-1
ii  libcairo2 1.14.8-1
ii  libcaja-extension11.16.1-1
ii  libexempi32.3.0-2
ii  libexif12 0.6.21-2
ii  libgail-3-0   3.22.5-1
ii  libgdk-pixbuf2.0-02.36.2-1
ii  libglib2.0-0  2.50.2-2
ii  libglib2.0-data   2.50.2-2
ii  libgtk-3-03.22.5-1
ii  libice6   2:1.0.9-1+b1
ii  libmate-desktop-2-17  1.16.1-1
ii  libpango-1.0-01.40.3-3
ii  libpangocairo-1.0-0   1.40.3-3
ii  libselinux1   2.6-3
ii  libsm62:1.2.2-1+b1
ii  libstartup-notification0  0.12-4
ii  libunique-3.0-0   3.0.2-2
ii  libx11-6  2:1.6.4-2
ii  libxext6  2:1.3.3-1
ii  libxml2   2.9.4+dfsg1-2.1
ii  libxrender1   1:0.9.10-1
ii  mate-desktop  1.16.1-1
ii  shared-mime-info  1.7-1

Versions of packages caja recommends:
ii  gvfs-backends  1.30.3-1

Versions of packages caja suggests:
ii  engrampa1.16.0-1
pn  gstreamer1.0-tools  
ii  meld3.16.4-1

-- no debconf information

Bug#849688: package in debian/testing is development version, severely broken

[Ayke van Laethem]

On Mon, 02 Jan 2017 11:19:47 +0100
=?ISO-8859-1?Q?J=F6rg_Frings-F=FCrst?= 
wrote:
> I set the severity to normal because
>  * there are only 2 open bugs[5] for release 0.25.x at shotwell
>bugtrackerÂ

I just tried using shotwell (I don't use it often) but it turned out
to be barely usable. 'Set title' didn't work, setting tags sometimes
works, sometimes it doesn't. Right-clicking a tag doesn't bring up a
usable menu. Sometimes it crashes (assertion failure or segfault). I
assume all these issues are fixed in the next version.

>  * the next release date is near enough to get it into
>unstable/testing.

I would be glad if these problems get fixed, because in it's current
state it's unusable (and IMHO not fit for stable release). Whether
it's version 0.24 or 0.26 doesn't really matter to me personally.

Bug#846523: mate-notification-daemon: bold formatting is not properly displayed

[Ayke van Laethem]

Package: mate-notification-daemon
Version: 1.16.0-1
Severity: normal
Tags: patch

Dear Maintainer,

Notifications that provide bold text (via text), display these
characters literally instead of actually displaying bold text.
This has been fixed upstream:
https://github.com/mate-desktop/mate-notification-daemon/issues/111
https://github.com/mate-desktop/mate-notification-
daemon/commit/d9ed22c64d341914a91eaf16fa1b2c0771dee4af

I'm reporting the bug here as well, as it would be nice to include this fix in
Stretch before the full freeze.



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mate-notification-daemon depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-7
ii  libcairo-gobject21.14.6-1.1
ii  libcairo21.14.6-1.1
ii  libcanberra-gtk3-0   0.30-3
ii  libcanberra0 0.30-3
ii  libdbus-1-3  1.10.12-1
ii  libdbus-glib-1-2 0.108-1
ii  libgdk-pixbuf2.0-0   2.36.0-1
iu  libglib2.0-0 2.50.2-2
iu  libgtk-3-0   3.22.4-1
ii  libnotify4   0.7.7-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libwnck-3-0  3.20.1-2
ii  libx11-6 2:1.6.3-1
ii  mate-notification-daemon-common  1.16.0-1

mate-notification-daemon recommends no packages.

mate-notification-daemon suggests no packages.

-- no debconf information

Bug#842990: vim-gtk3: gvim has the smallest possible text window

[Ayke van Laethem]

Package: vim-gtk3
Version: 2:8.0.0022-1
Severity: important

Dear Maintainer,

When running gvim (from the vim-gtk3 package), the whole text window is
invisible. It looks like it has shrunk so small to be unusable. See the
attached screenshot. I have tried running gvim using:
8
gvim -u NONE -U NONE -N

Additionally, these errors are printed to the console:

(gvim:5113): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'width >=
-1' failed
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug


(gvim:5113): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'width >=
-1' failed

(gvim:5113): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'width >=
-1' failed
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug


(gvim:5113): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'width >=
-1' failed



-- Package-specific info:

--- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.gtk3
/usr/bin/vim is /usr/bin/vim.gtk3
/usr/bin/gvim is /usr/bin/vim.gtk3

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages vim-gtk3 depends on:
ii  libacl1  2.2.52-3
ii  libc62.24-5
ii  libcairo21.14.6-1+b1
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libglib2.0-0 2.50.1-1
ii  libgpm2  1.20.4-6.2
ii  libgtk-3-0   3.22.2-1
ii  libice6  2:1.0.9-1+b1
ii  liblua5.2-0  5.2.4-1.1+b1
ii  libpango-1.0-0   1.40.3-2
ii  libpangocairo-1.0-0  1.40.3-2
ii  libperl5.24  5.24.1~rc3-3
ii  libpython3.5 3.5.2-6+b1
ii  libruby2.3   2.3.1-5+b1
ii  libselinux1  2.5-3
ii  libsm6   2:1.2.2-1+b1
ii  libtcl8.68.6.6+dfsg-1
ii  libtinfo56.0+20160917-1
ii  libx11-6 2:1.6.3-1
ii  libxt6   1:1.1.5-1
ii  vim-common   2:8.0.0022-1
ii  vim-gui-common   2:8.0.0022-1
ii  vim-runtime  2:8.0.0022-1

vim-gtk3 recommends no packages.

Versions of packages vim-gtk3 suggests:
pn  cscope
ii  fonts-dejavu  2.37-1
ii  gnome-icon-theme  3.12.0-2
pn  vim-doc   

-- no debconf information

Bug#746943:

[Ayke van Laethem]

Red Hat bug: https://bugzilla.redhat.com/show_bug.cgi?id=906591

Workaround I use:
Disable PRUNE_BIND_MOUNTS in /etc/updatedb.conf and manually prune bind
mounts (and btrfs snapshots etc.) using PRUNEPATHS.

Bug#839239: xserver-xorg-core: slight tearing with Intel modesetting driver

[Ayke van Laethem]

Package: xserver-xorg-core
Version: 2:1.18.4-1
Severity: normal

Dear Maintainer,

After upgrading to the new Intel modesetting driver [1] slight tearing appears
in both Firefox (from Debian) and Google Chrome when scrolling fast. It's
visible in a diagonal line from the top left of the screen. It goes in the
direction of the bottom right, but doesn't reach it. Just the top left are
affected. It's hardly visible, and even harder in Firefox, so it's not a big
issue to me. But it can be distracting sometimes. This is a regression, so I'm
reporting it.

Note: this change is still an improvement for me as it fixes some redraw issues
I found in the old driver.

 [1] https://tjaalton.wordpress.com/2016/07/23/intel-graphics-gen4-and-newer-
now-defaults-to-modesetting-driver-on-x/



-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Nov 12  2015 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Jul 20 05:00 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation Broadwell-U 
Integrated Graphics [8086:1616] (rev 09)

/etc/X11/xorg.conf does not exist.

Contents of /etc/X11/xorg.conf.d:
-
total 4
-rw-r--r-- 1 root root 265 Jan  3  2016 input.conf

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.7.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.1 
20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.7.5-1 (2016-09-26)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 31199 Sep 30 16:36 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[  4747.088] 
X.Org X Server 1.18.4
Release Date: 2016-07-19
[  4747.088] X Protocol Version 11, Revision 0
[  4747.088] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[  4747.088] Current Operating System: Linux ayke-laptop-l450 4.7.0-1-amd64 #1 
SMP Debian 4.7.5-1 (2016-09-26) x86_64
[  4747.088] Kernel command line: BOOT_IMAGE=/system/boot/vmlinuz-4.7.0-1-amd64 
root=UUID=5ff607da-2fa3-4e8a-a9e6-03d5e9049688 ro rootflags=subvol=system quiet
[  4747.088] Build Date: 20 July 2016  05:14:41AM
[  4747.088] xorg-server 2:1.18.4-1 (http://www.debian.org/support) 
[  4747.088] Current version of pixman: 0.33.6
[  4747.088]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[  4747.088] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  4747.088] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Sep 30 16:36:50 
2016
[  4747.088] (==) Using config directory: "/etc/X11/xorg.conf.d"
[  4747.088] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  4747.089] (==) No Layout section.  Using the first Screen section.
[  4747.089] (==) No screen section available. Using defaults.
[  4747.089] (**) |-->Screen "Default Screen Section" (0)
[  4747.089] (**) |   |-->Monitor ""
[  4747.089] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[  4747.089] (==) Automatically adding devices
[  4747.089] (==) Automatically enabling devices
[  4747.089] (==) Automatically adding GPU devices
[  4747.089] (==) Max clients allowed: 256, resource mask: 0x1f
[  4747.089] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  4747.089]Entry deleted from font path.
[  4747.089] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[  4747.089]Entry deleted from font path.
[  4747.089] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[  4747.089]Entry deleted from font path.
[  4747.089] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[  4747.089]Entry deleted from font path.
[  4747.089] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[  4747.089]Entry deleted from font path.
[  4747.089] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[  4747.089]Entry deleted from font path.
[  4747.089] (==) FontPath set to:
/usr/share/fonts/X11/misc,
built-ins
[  4747.089] (==) ModulePath set to "/usr/lib/xorg/modules"
[  4747.089] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[  4747.089] (II) Loader magic: 0x55adea1e6dc0
[  4747.089] (II) Module ABI versions:
[  4747.089]X.Org ANSI C Emulation: 0.4
[  4747.089]X.Org Video Driver: 20.0
[  4747.089]X.Org XInput driver : 22.1
[  4747.089]X.Org Server Extension : 9.0
[  4747.090] (++) using VT number 7

[  4747.090] (II) 

Bug#820805: mixxx: missing dependency libqt4-sql-sqlite

[Ayke van Laethem]

Package: mixxx
Version: 2.0.0~dfsg-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When starting mixxx (2.0.0~dfsg-3), it reports this error:

  Unable to establish a database connection.
  Mixxx requires QT with SQLite support. Please read the
  Qt SQL driver documentation for information on how to
  build it.

  Click OK to exit.

Other than that, it's impossible to run Mixxx.

Installing the package  libqt4-sql-sqlite fixes the issue, so it looks like a
missing dependency.

(Please let me know if 'grave' is the wrong severity level for missing
dependencies).



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mixxx depends on:
ii  libc6 2.22-5
ii  libchromaprint0   1.3-1
ii  libflac8  1.3.1-4
ii  libgcc1   1:5.3.1-13
ii  libgl1-mesa-glx [libgl1]  11.1.2-1
ii  libhidapi-libusb0 0.8.0~rc1+git20140818.d17db57+dfsg-1
ii  libid3tag00.15.1b-11
ii  libmad0   0.15.1b-8
ii  libogg0   1.3.2-1
ii  libopusfile0  0.7-1
ii  libportaudio2 19+svn20140130-1
ii  libportmidi0  1:184-2.2
ii  libprotobuf-lite9v5   2.6.1-1.3
ii  libqt4-network4:4.8.7+dfsg-6
ii  libqt4-opengl 4:4.8.7+dfsg-6
ii  libqt4-script 4:4.8.7+dfsg-6
ii  libqt4-scripttools4:4.8.7+dfsg-6
ii  libqt4-sql4:4.8.7+dfsg-6
ii  libqt4-svg4:4.8.7+dfsg-6
ii  libqt4-xml4:4.8.7+dfsg-6
ii  libqtcore44:4.8.7+dfsg-6
ii  libqtgui4 4:4.8.7+dfsg-6
ii  librubberband21.8.1-6+b1
ii  libshout3 2.3.1-3
ii  libsndfile1   1.0.25-10
ii  libsoundtouch11.9.2-2
ii  libsqlite3-0  3.11.1-1
ii  libstdc++65.3.1-13
ii  libtag1v5 1.9.1-2.4
ii  libusb-1.0-0  2:1.0.20-1
ii  libvamp-hostsdk3v52.6~repack0-2
ii  libvamp-sdk2v52.6~repack0-2
ii  libvorbis0a   1.3.5-3
ii  libvorbisenc2 1.3.5-3
ii  libvorbisfile31.3.5-3
ii  libx11-6  2:1.6.3-1
ii  mixxx-data2.0.0~dfsg-3

mixxx recommends no packages.

Versions of packages mixxx suggests:
ii  atril [pdf-viewer]  1.12.2-1

-- no debconf information

Bug#818651: golang: cannot use net package without CGO

[Ayke van Laethem]

Package: golang
Version: 2:1.6-1
Severity: normal

Dear Maintainer,

Golang 1.3 (jessie) can build this file just fine without CGO, but golang 1.5
and 1.6 throws an error:

package main

import (
"fmt"
"net"
)

func main() {
fmt.Println("HostPort:", net.JoinHostPort("google.com", "80"))
}

To reproduce, compile this with the environment variable CGO_ENABLED=0. It
fails with golang 1.5 (jessie-backports) and golang 1.6 (testing) but succeeds
in golang 1.3 (jessie).
The exact (but cryptic) error reported is:

go install net: open /usr/lib/go/pkg/linux_amd64/net.a: permission denied

Since Go 1.2 (according to the docs [1]) it should be possible to use the net
package without CGO on some systems.
My system is linux-amd64 (one with jessie and one with testing).


 [1] https://golang.org/doc/go1.2



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages golang depends on:
ii  golang-doc  2:1.6-1
ii  golang-go   2:1.6-1
ii  golang-src  2:1.6-1

golang recommends no packages.

golang suggests no packages.

-- no debconf information

Bug#805171: xorg: pointer is not scaled with xrandr --scale

[Ayke van Laethem]

Package: xorg
Version: 1:7.7+12
Severity: normal

Dear Maintainer,

I have a HiDPI screen here, of about x1.5 (a DPI of 144). To make the desktop
workable, I'm using a x2 scale on my desktop and scale back to 1.5 using
xrandr, with this command:

xrandr --output eDP1 --scale 1.5x1.5 --panning 2880x1620

(The --panning parameter is a workaround for another bug in xrandr).

This works, with one problem: the mouse pointer is not scaled with the rest of
the desktop (not using xrandr results in the same pointer size but the rest of
the screen is bigger). A workaround is to set the cursor-size to a lower value
in Cinnamon (e.g. 18 to get a cursor size 24), but that is not a real solution.

This appears to be a bigger problem, also reported outside of Debian [1].

I'm using the DMZ-White cursor theme and the Cinnamon desktop, if that matters.
My system is a Lenovo L450 laptop, with a 1920x1080 screen.


$ xdpyinfo | grep -B 2 resolution
screen #0:
  dimensions:2880x1620 pixels (760x427 millimeters)
  resolution:96x96 dots per inch

$ xrdb -query
*customization: -color
Xft.dpi:192
Xft.antialias:  1
Xft.hinting:0
Xft.hintstyle:  hintnone
Xft.rgba:   rgb


 [1] http://unix.stackexchange.com/questions/203251/cursor-is-huge-on-ubuntu-
due-to-high-resolution-monitor



-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Nov 12 14:32 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Oct 28 00:43 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation Broadwell-U
Integrated Graphics [8086:1616] (rev 09)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.2.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.9.3
(Debian 4.9.3-5) ) #1 SMP Debian 4.2.5-1 (2015-10-27)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 23332 Nov 15 14:00 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[  7380.487]
X.Org X Server 1.17.3
Release Date: 2015-10-26
[  7380.487] X Protocol Version 11, Revision 0
[  7380.487] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[  7380.487] Current Operating System: Linux ayke-laptop-l450 4.2.0-1-amd64 #1
SMP Debian 4.2.5-1 (2015-10-27) x86_64
[  7380.487] Kernel command line: BOOT_IMAGE=/system/boot/vmlinuz-4.2.0-1-amd64
root=UUID=5ff607da-2fa3-4e8a-a9e6-03d5e9049688 ro rootflags=subvol=system quiet
[  7380.487] Build Date: 27 October 2015  11:41:02PM
[  7380.487] xorg-server 2:1.17.3-2 (http://www.debian.org/support)
[  7380.487] Current version of pixman: 0.33.4
[  7380.487]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[  7380.487] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  7380.487] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Nov 15 13:58:58
2015
[  7380.487] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  7380.487] (==) No Layout section.  Using the first Screen section.
[  7380.487] (==) No screen section available. Using defaults.
[  7380.487] (**) |-->Screen "Default Screen Section" (0)
[  7380.487] (**) |   |-->Monitor ""
[  7380.488] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[  7380.488] (==) Automatically adding devices
[  7380.488] (==) Automatically enabling devices
[  7380.488] (==) Automatically adding GPU devices
[  7380.488] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  7380.488]Entry deleted from font path.
[  7380.488] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[  7380.488] (==) ModulePath set to "/usr/lib/xorg/modules"
[  7380.488] (II) The server relies on udev to provide the list of input
devices.
If no devices become available, reconfigure udev or disable
AutoAddDevices.
[  7380.488] (II) Loader magic: 0x560a075f0de0
[  7380.488] (II) Module ABI versions:
[  7380.488]X.Org ANSI C Emulation: 0.4
[  7380.488]X.Org Video Driver: 19.0
[  7380.488]X.Org XInput driver : 21.0
[  7380.488]X.Org Server Extension : 9.0
[  7380.489] (EE) systemd-logind: failed to get session: PID 3962 does not
belong to any known session
[  7380.489] (II) xfree86: Adding drm device (/dev/dri/card0)
[  7380.491] (--) 

Bug#696856:

[Ayke van Laethem]

I also have this issue on a fully updated jessie installation.

postfix   2.11.3-1
postfix-mysql 2.11.3-1
spamass-milter0.3.2-1+b1
spamassassin  3.4.0-6

Ayke

Bug#804153: gparted: btrfs filesystem resize resizes wrong partition

[Ayke van Laethem]

Package: gparted
Version: 0.19.0-2
Severity: normal
Tags: upstream

Dear Maintainer,

When resizing a btrfs partition that does not have devid 1 (e.g. when you add a
second partition in a RAID1 configuration) GParted does not resize the right
partition.

This issue has been reported upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=723842

The issue is that GParted uses a command like this:

btrfs filesystem resize 1921211392K /tmp/gparted-Hh2WsW

While the man page for btrfs filesystem resize specifies:

resize [:][gkm]|[:]max 

[...]
The devid can be found with btrfs filesystem show and defaults to 1 if not
specified. [...]

So the devid is missing and 1 is used. In my case, devid 2 was needed making
the command fail:

Resize '/tmp/gparted-Hh2WsW' of '1921211392K'
ERROR: unable to resize '/tmp/gparted-Hh2WsW' - File too large

Ubuntu bug:
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1512116



-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gparted depends on:
ii  libatkmm-1.6-12.22.7-2.1
ii  libc6 2.19-18+deb8u1
ii  libgcc1   1:4.9.2-10
ii  libglib2.0-0  2.42.1-1
ii  libglibmm-2.4-1c2a2.42.0-1
ii  libgtk2.0-0   2.24.25-3
ii  libgtkmm-2.4-1c2a 1:2.24.4-1.1
ii  libpangomm-1.4-1  2.34.0-1.1
ii  libparted-fs-resize0  3.2-7
ii  libparted23.2-7
ii  libsigc++-2.0-0c2a2.4.0-1
ii  libstdc++64.9.2-10
ii  libuuid1  2.25.2-6

gparted recommends no packages.

Versions of packages gparted suggests:
ii  dmraid 1.0.0.rc16-5
ii  dmsetup2:1.02.90-2.2
ii  dosfstools 3.0.27-1
pn  gpart  
pn  jfsutils   
ii  kpartx 0.5.0-6+deb8u1
ii  mtools 4.0.18-2
ii  ntfs-3g1:2014.2.15AR.2-1+deb8u2
pn  reiser4progs   
pn  reiserfsprogs  
pn  xfsprogs   
ii  yelp   3.14.1-1

-- no debconf information

Bug#766801: mate-applets: battery charge monitor icon goes the reverse order while charging

[Ayke van Laethem]

Well, this is strange. The issue is gone.

I'm not sure when, but I think since I reinstalled mate-applets after
playing with it a bit (compiling from source etc.), the applet behaves
exactly as expected now. So maybe there was an update that maybe
wasn't applied properly or something like that. I'm puzzled.
I'm sure it was there before. It certainly was there when I was still
using MATE 1.6 under LMDE, and it also was there not long ago. I'm
quite sure I have seen it when I had installed mate-applets from
source (via apt-src), but then it just... vanished.

I guess this means the issue can be closed then, and no further
testing is needed...


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#766801: mate-applets: battery charge monitor icon goes the reverse order while charging

[Ayke van Laethem]

Unfortunately, I cannot test other notebooks. I don't have another and
I don't think anyone I know would be glad to lend me a notebook when
there's a (small) chance that their current O.S. gets wiped just to
check for a bug in an O.S. that they don't know and don't care
about...

 Which Thinkpad T60 is that exactly? Please look at the bottom and post the 
 full type number here. Please also provide your BIOS and EC firmware versions 
 and anything else that could be relevant.

It says on the bottom:

  TYPE 2007-CTO  S/N L3-4X4D7 07/05
  PRODUCT ID:2007VW1

This is what the BIOS says:

  BIOS Version2.26 (79ETE6WW)
  BIOS Date (Year-Month-Day)  2010-04-01
  Embedded Controller Version 1.07
  System-unit serial number   VF0T875G2E0
  CPU TypeIntel(R) Core(TM)2 CPU   T7200
  CPU Speed   2.00GHz
  Installed Memory4096MB

(And UUID and MAC adress but those don't seem relevant to me.)

 We have plenty of different ThinkPad T60 at work and my personal work laptop 
 is a T60 as well.

 I haven't observed your particular issue yet myself on my T60, but I could 
 check the other variants we have in case I can find a similar model or even 
 the same one.

Nice!


 Adrian

Ayke


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#775500: mate-power-manager: brightness change popup using media keys has inconsistent 'progress bar'

[Ayke van Laethem]

Package: mate-power-manager
Version: 1.8.1+dfsg1-3
Severity: normal

Dear Maintainer,

My laptop (Lenovo Thinkpad T60) has seven screen brightness levels, I'll call
them level 0-6. Changing the brightness using the hardware keys occurs in two
steps, e.g. from 0 to 2, from 1 to 3 etc., and the same in the reverse order.
When the brightness is one step from the lowest or highest level, the
brightness will change only one step as it can't change more than that.

Now, when pressing these hardware keys a popup is shown displaying the new
brightness value in a 'progress bar' (see fixed bug #766749). This works,
except for the fact that when the last step is only a single level change (from
1 to 0 or from 5 to 6), no change is displayed. The progress bar stays at the
second-to-last value (1 or 5) and doesn't jump to the last one (0 or 6).

I tried fiddling aroud with it a bit, and it looks like it does sometimes jump
to the last level when pressing the keys quickly, and sometimes when pressing
the keys quickly it doesn't jump to the last level when the level goes from 2
to 0 or from 4 to 6.

Of course, I would expect the brightness level to be displayed properly, not
stuck at the previous value.

I tried a few different themes but none of them affect this behavior in any
way.

For type information about my laptop, see bug #766801.



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mate-power-manager depends on:
ii  consolekit  0.4.6-5
ii  dbus-x111.8.12-3
ii  libatk1.0-0 2.14.0-1
ii  libc6   2.19-13
ii  libcairo2   1.14.0-2.1
ii  libcanberra-gtk00.30-2.1
ii  libcanberra00.30-2.1
ii  libdbus-1-3 1.8.12-3
ii  libdbus-glib-1-20.102-1
ii  libfontconfig1  2.11.0-6.3
ii  libfreetype62.5.2-2
ii  libgdk-pixbuf2.0-0  2.31.1-2+b1
ii  libglib2.0-02.42.1-1
ii  libgnome-keyring0   3.12.0-1+b1
ii  libgtk2.0-0 2.24.25-1
ii  libmate-panel-applet-4-11.8.1+dfsg1-3
ii  libnotify4  0.7.6-2
ii  libpango-1.0-0  1.36.8-3
ii  libpangocairo-1.0-0 1.36.8-3
ii  libpangoft2-1.0-0   1.36.8-3
ii  libunique-1.0-0 1.1.6-5
ii  libupower-glib3 0.99.1-3.1
ii  libx11-62:1.6.2-3
ii  libxext62:1.3.3-1
ii  libxrandr2  2:1.4.2-1+b1
ii  libxrender1 1:0.9.8-1+b1
ii  mate-notification-daemon [notification-daemon]  1.8.1-2
ii  mate-power-manager-common   1.8.1+dfsg1-3
ii  notification-daemon 0.7.6-2
ii  policykit-1 0.105-8
ii  systemd 215-8
ii  upower  0.99.1-3.1

Versions of packages mate-power-manager recommends:
ii  udisks  1.0.5-1+b1

Versions of packages mate-power-manager suggests:
ii  mate-polkit  1.8.0+dfsg1-4

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#773680: mpv: wrong version number in --version

[Ayke van Laethem]

Oops - yes. I built mpv locally. Sorry about that (I didn't check properly).

— Ayke

Bug#773680: mpv: wrong version number in --version

[Ayke van Laethem]

Package: mpv
Version: 0.6.2-2
Severity: normal

Dear Maintainer,

MPV will give the wrong version number when running without arguments, or when
running mpv --version.

Example:

~$ mpv --version
mpv 0.5.0-git-88f247c (C) 2000-2014 mpv/MPlayer/mplayer2 projects
 built on 2014-08-15T12:38:45
ffmpeg library versions:
   libavutil   52.92.100
   libavcodec  55.69.100
   libavformat 55.48.100
   libswscale  2.6.100
   libavfilter 4.11.100
   libavresample   1.3.0


The version should be something like 0.6.2-2, not 0.5.0.

(I'm not sure what importance this bug should have. It doesn't affect
usuability at all, but it looks like something that 'must be fixed' to me at
the same time).



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mpv depends on:
ii  libasound2  1.0.28-1
ii  libass5 0.10.2-3
ii  libavcodec566:11-2
ii  libavdevice55   6:11-2
ii  libavfilter56:11-2
ii  libavformat56   6:11-2
ii  libavresample2  6:11-2
ii  libavutil54 6:11-2
ii  libbluray1  1:0.6.2-1
ii  libbs2b03.1.0+dfsg-2.1
ii  libc6   2.19-13
ii  libcdio-cdda1   0.83-4.2
ii  libcdio-paranoia1   0.83-4.2
ii  libcdio13   0.83-4.2
ii  libdvdnav4  5.0.1-1
ii  libdvdread4 5.0.0-1
ii  libegl1-mesa [libegl1-x11]  10.3.2-1
ii  libenca01.16-1
ii  libgl1-mesa-glx [libgl1]10.3.2-1
ii  libguess1   1.2-1
ii  libjack-jackd2-0 [libjack-0.116]1.9.10+20140719git3eb0ae6a~dfsg-2
ii  libjpeg62-turbo 1:1.3.1-11
ii  liblcms2-2  2.6-3+b3
ii  liblircclient0  0.9.0~pre1-1.1
ii  liblua5.2-0 5.2.3-1.1
ii  libmpg123-0 1.20.1-2
ii  libpulse0   5.0-13
ii  libquvi70.4.1-2.1
ii  libsdl2-2.0-0   2.0.2+dfsg1-6
ii  libswscale3 6:11-2
ii  libuuid12.25.2-4
ii  libva-glx1  1.4.1-1
ii  libva-x11-1 1.4.1-1
ii  libva1  1.4.1-1
ii  libvdpau1   0.8-3
ii  libwayland-client0  1.6.0-2
ii  libwayland-cursor0  1.6.0-2
ii  libwayland-egl1-mesa [libwayland-egl1]  10.3.2-1
ii  libx11-62:1.6.2-3
ii  libxext62:1.3.3-1
ii  libxinerama12:1.1.3-1+b1
ii  libxkbcommon0   0.4.3-2
ii  libxrandr2  2:1.4.2-1+b1
ii  libxss1 1:1.2.2-1
ii  libxv1  2:1.0.10-1+b1
ii  zlib1g  1:1.2.8.dfsg-2+b1

mpv recommends no packages.

mpv suggests no packages.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#771180: libgtk-3-0: file open dialog has redrawing issues with a theme (BlackMATE)

[Ayke van Laethem]

Package: libgtk-3-0
Version: 3.14.5-1
Severity: minor

Dear Maintainer,

When the BlackMATE theme is applied, there are redrawing issues when hovering
over the left sidebar with the mouse. See the attached screenshot. The
directory and device names are not drawn at the right location, making clicking
on the right one harder.

I have only been able to reproduce this bug using the BlackMATE theme and only
in applications that depend on libgtk-3-0 (other application, I think using
gtk-2.0, are not affected). I use the MATE desktop.

I'm reporting it here as I don't think a theme should cause redrawing issues.

For this bug, I installed libgtk-3-0 from unstable, but the bug is still
present in that version. So at least both 3.14.5-1 and 3.14.4-2 are affected.



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libgtk-3-0 depends on:
ii  libatk-bridge2.0-0   2.14.0-2
ii  libatk1.0-0  2.14.0-1
ii  libc62.19-13
ii  libcairo-gobject21.14.0-2.1
ii  libcairo21.14.0-2.1
ii  libcolord2   1.2.1-1+b1
ii  libcups2 1.7.5-7
ii  libfontconfig1   2.11.0-6.1
ii  libfreetype6 2.5.2-2
ii  libgdk-pixbuf2.0-0   2.31.1-2+b1
ii  libglib2.0-0 2.42.0-2
ii  libgtk-3-common  3.14.5-1
ii  libjson-glib-1.0-0   1.0.2-1
ii  libpango-1.0-0   1.36.8-2
ii  libpangocairo-1.0-0  1.36.8-2
ii  libpangoft2-1.0-01.36.8-2
ii  librest-0.7-00.7.92-2
ii  libsoup2.4-1 2.48.0-1
ii  libwayland-client0   1.6.0-2
ii  libwayland-cursor0   1.6.0-2
ii  libx11-6 2:1.6.2-3
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.1-2+b1
ii  libxi6   2:1.7.4-1+b1
ii  libxinerama1 2:1.1.3-1+b1
ii  libxkbcommon00.4.3-2
ii  libxml2  2.9.1+dfsg1-4
ii  libxrandr2   2:1.4.2-1+b1
ii  multiarch-support2.19-13
ii  shared-mime-info 1.3-1

Versions of packages libgtk-3-0 recommends:
ii  hicolor-icon-theme  0.13-1
ii  libgtk-3-bin3.14.5-1

Versions of packages libgtk-3-0 suggests:
ii  gvfs 1.22.1-1
ii  librsvg2-common  2.40.5-1

Bug#771180: libgtk-3-0: file open dialog has redrawing issues with a theme (BlackMATE)

[Ayke van Laethem]

found 771180 3.14.4-2

I hope adding this version in jessie will work...

— Ayke

2014-11-27 12:42 GMT+01:00 Ayke van Laethem aykevanlaet...@gmail.com:

 Package: libgtk-3-0
 Version: 3.14.5-1
 Severity: minor

 Dear Maintainer,

 When the BlackMATE theme is applied, there are redrawing issues when
 hovering
 over the left sidebar with the mouse. See the attached screenshot. The
 directory and device names are not drawn at the right location, making
 clicking
 on the right one harder.

 I have only been able to reproduce this bug using the BlackMATE theme and
 only
 in applications that depend on libgtk-3-0 (other application, I think using
 gtk-2.0, are not affected). I use the MATE desktop.

 I'm reporting it here as I don't think a theme should cause redrawing
 issues.

 For this bug, I installed libgtk-3-0 from unstable, but the bug is still
 present in that version. So at least both 3.14.5-1 and 3.14.4-2 are
 affected.



 -- System Information:
 Debian Release: jessie/sid
   APT prefers testing
   APT policy: (500, 'testing')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386

 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash

 Versions of packages libgtk-3-0 depends on:
 ii  libatk-bridge2.0-0   2.14.0-2
 ii  libatk1.0-0  2.14.0-1
 ii  libc62.19-13
 ii  libcairo-gobject21.14.0-2.1
 ii  libcairo21.14.0-2.1
 ii  libcolord2   1.2.1-1+b1
 ii  libcups2 1.7.5-7
 ii  libfontconfig1   2.11.0-6.1
 ii  libfreetype6 2.5.2-2
 ii  libgdk-pixbuf2.0-0   2.31.1-2+b1
 ii  libglib2.0-0 2.42.0-2
 ii  libgtk-3-common  3.14.5-1
 ii  libjson-glib-1.0-0   1.0.2-1
 ii  libpango-1.0-0   1.36.8-2
 ii  libpangocairo-1.0-0  1.36.8-2
 ii  libpangoft2-1.0-01.36.8-2
 ii  librest-0.7-00.7.92-2
 ii  libsoup2.4-1 2.48.0-1
 ii  libwayland-client0   1.6.0-2
 ii  libwayland-cursor0   1.6.0-2
 ii  libx11-6 2:1.6.2-3
 ii  libxcomposite1   1:0.4.4-1
 ii  libxcursor1  1:1.1.14-1+b1
 ii  libxdamage1  1:1.1.4-2
 ii  libxext6 2:1.3.3-1
 ii  libxfixes3   1:5.0.1-2+b1
 ii  libxi6   2:1.7.4-1+b1
 ii  libxinerama1 2:1.1.3-1+b1
 ii  libxkbcommon00.4.3-2
 ii  libxml2  2.9.1+dfsg1-4
 ii  libxrandr2   2:1.4.2-1+b1
 ii  multiarch-support2.19-13
 ii  shared-mime-info 1.3-1

 Versions of packages libgtk-3-0 recommends:
 ii  hicolor-icon-theme  0.13-1
 ii  libgtk-3-bin3.14.5-1

 Versions of packages libgtk-3-0 suggests:
 ii  gvfs 1.22.1-1
 ii  librsvg2-common  2.40.5-1

Bug#766093:

[Ayke van Laethem]

 this should be fixed in -3. (Currently uploading, should hit mirrors
 in a couple of hours.)

Yes, it's fixed. Thank you!

Bug#770760: caja: filename font color does not always get picked up from theme

[Ayke van Laethem]

Package: caja
Version: 1.8.2-1
Severity: minor

Dear Maintainer,

The font color of filenames in the directory listing of caja sometimes do not
get applied as they should according to the theme.

A few cases in which I have seen this happening:
  * When the BlackMATE theme has been applied. The filename font color is still
black on the dark background, making the filenames harder to read (see the
attached screenshot).
  * When switching from BlackMATE to a lighter theme. The filenames become
light and thus barely readable on the white background. This is resolved
with a restart of caja.

Strangely, this only happens in the 'icons' and 'compact' display type, not in
the 'list' display type. Switching from the 'icons' to the 'list' and back to
the 'icons' type makes the filenames the right color (light gray or white).

The 'High Contrast Inverse' theme doesn't have this problem.

(I know this could be a mate-themes bug but as the right color does get applied
under certain conditions, it seems like caja is messing up somewhere).



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages caja depends on:
ii  caja-common   1.8.2-1
ii  desktop-file-utils0.22-1
ii  gvfs  1.22.1-1
ii  libatk1.0-0   2.14.0-1
ii  libc6 2.19-13
ii  libcairo2 1.14.0-2.1
ii  libcaja-extension11.8.2-1
ii  libexempi32.2.1-2
ii  libexif12 0.6.21-2
ii  libfontconfig12.11.0-6.1
ii  libfreetype6  2.5.2-2
ii  libgail18 2.24.25-1
ii  libgdk-pixbuf2.0-02.31.1-2+b1
ii  libglib2.0-0  2.42.0-2
ii  libglib2.0-data   2.42.0-2
ii  libgtk2.0-0   2.24.25-1
ii  libice6   2:1.0.9-1
ii  libmate-desktop-2-17  1.8.1+dfsg1-2
ii  libpango-1.0-01.36.8-2
ii  libpangocairo-1.0-0   1.36.8-2
ii  libpangoft2-1.0-0 1.36.8-2
ii  libselinux1   2.3-2
ii  libsm62:1.2.2-1
ii  libstartup-notification0  0.12-4
ii  libunique-1.0-0   1.1.6-5
ii  libx11-6  2:1.6.2-3
ii  libxext6  2:1.3.3-1
ii  libxml2   2.9.1+dfsg1-4
ii  libxrender1   1:0.9.8-1+b1
ii  mate-desktop  1.8.1+dfsg1-2
ii  shared-mime-info  1.3-1

caja recommends no packages.

Versions of packages caja suggests:
ii  engrampa 1.8.1+dfsg1-1
pn  gstreamer0.10-tools  none
ii  meld 3.12.1-1

Bug#770477: mate-themes: dark themes make parts of libreoffice unreadable

[Ayke van Laethem]

Package: mate-themes
Version: 1.9.1-1
Severity: minor

Dear Maintainer,

I am not sure whether this is a mate-themes or a libreoffice bug, but here it
goes.

When applying the theme 'BlackMATE' or 'High Contrast Inverse', some parts of
LibreOffice (the ruler, parts of the status bar) become either hard to see
(BlackMate) or practically impossible to see (High Contrast Inverse, a theme
designed for accessibility). I would expect those icons and lines to have a
lighter color so they're visible on the dark background.

I think this not only is a theming issue, but also an accessibility issue as
the High Contrast Inverse theme is affected.

I have attached two screenshots, one with a light theme (BlueMenta) and one
with a dark theme (BlackMATE) to see the difference.



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mate-themes depends on:
ii  gtk2-engines  1:2.20.2-3
ii  gtk2-engines-murrine  0.98.1.1-5
ii  gtk2-engines-pixbuf   2.24.25-1
ii  librsvg2-common   2.40.5-1
ii  mate-icon-theme   1.8.0-1

Versions of packages mate-themes recommends:
ii  dmz-cursor-theme  0.4.4

mate-themes suggests no packages.

-- no debconf information

Bug#770482: gnome-themes-standard: some themes (like Adwaita) do not have the required window manager theme

[Ayke van Laethem]

Package: gnome-themes-standard
Version: 3.14.0-1
Severity: normal

Dear Maintainer,

When changing the theme to Adwaita (or High Contrast) in mate-appearance-
properties, it says:

This theme will not look as intended because the required window manager
theme 'Adwaita' is not installed.

And indeed, the window borders do not change theme when switching to Adwaita.

Maybe some other package needs to be installed, but I don't know which. And I
would expect that package to be a Depends or a Recommends of gnome-themes-
standard[-data].

This bug was reported before as #632181 but was closed as gnome-appearance-
properties was removed. I believe this bug is independent of gnome-appearances-
properties.



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-themes-standard depends on:
ii  gnome-themes-standard-data  3.14.0-1
ii  libatk1.0-0 2.14.0-1
ii  libc6   2.19-13
ii  libcairo2   1.14.0-2.1
ii  libfontconfig1  2.11.0-6.1
ii  libfreetype62.5.2-2
ii  libgdk-pixbuf2.0-0  2.31.1-2+b1
ii  libglib2.0-02.42.0-2
ii  libgtk2.0-0 2.24.25-1
ii  libpango-1.0-0  1.36.8-2
ii  libpangocairo-1.0-0 1.36.8-2
ii  libpangoft2-1.0-0   1.36.8-2
ii  multiarch-support   2.19-13

Versions of packages gnome-themes-standard recommends:
ii  gnome-accessibility-themes  3.14.0-1
ii  gtk2-engines-pixbuf 2.24.25-1

gnome-themes-standard suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#766093:

[Ayke van Laethem]

I still get an assertion failure, using hugin version 2014.0.0+dfsg-2 (the
system Debian jessie/testing, fully updated right now).

ASSERT INFO:
/usr/include/wx-3.0/wx/strvararg.h(456): assert (argtype 
(wxFormatStringSpecifierT::value)) == argtype failed in
wxArgNormalizer(): format specifier doesn't match argument type

BACKTRACE:
[1] CPImageCtrl::setCtrlPoint(HuginBase::ControlPoint const, bool)
[2] CPEditorPanel::UpdateDisplay(bool)
[3] CPEditorPanel::setRightImage(unsigned int)
[4] PreviewLayoutLinesTool::MouseButtonEvent(wxMouseEvent)
[5] ToolHelper::MouseButtonEvent(wxMouseEvent)
[6] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor,
wxEvent) const
[7] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const,
wxEvtHandler*, wxEvent)
[8] wxEventHashTable::HandleEvent(wxEvent, wxEvtHandler*)
[9] wxEvtHandler::TryHereOnly(wxEvent)
[10] wxEvtHandler::ProcessEventLocally(wxEvent)
[11] wxEvtHandler::ProcessEvent(wxEvent)
[12] wxEvtHandler::SafelyProcessEvent(wxEvent)
[13] g_closure_invoke
[14] g_signal_emit_valist
[15] g_signal_emit
[16] gtk_propagate_event
[17] gtk_main_do_event
[18] g_main_context_dispatch
[19] g_main_loop_run
[20] gtk_main
[21] wxGUIEventLoop::DoRun()
[22] wxEventLoopBase::Run()
[23] wxAppConsoleBase::MainLoop()
[24] wxEntry(int, wchar_t**)
[25] main
[26] __libc_start_main
[27] _start

I got it when clicking on one of the lines between two photos in the
'Layout' tab.

I also got assertion failures when clicking the 'Align' tab before, but
somehow they disappeared after running apt-get autoremove (I still have the
backtrace if needed).

— Ayke

Bug#770221: caja: e-book reader media handler opens twice when connected

[Ayke van Laethem]

Package: caja
Version: 1.8.2-1
Severity: normal

Dear Maintainer,

When I insert my e-reader (a Kobo Aura), the application I have chosen to
automatically run on insert is run twice. When I set it (in the caja settings)
to ask what to do when an e-reader is inserted, the window asking what to do
with the e-reader is shown twice. Of course, I would expect it to only run
once.

Strangely, this only happens on my laptop (a Lenovo Thinkpad T60 laptop), but
not on my desktop (a Dell machine).

The single interesting line from lsusb (it is the only one inserted, and thus
the only line that's interesting):
Bus 005 Device 005: ID 2237:4203 Kobo Inc.
On the desktop, the relevant line is this:
Bus 002 Device 007: ID 2237:4203 Kobo Inc.

I have no idea what causes the difference. Both systems (laptop and desktop)
are fully updated. The desktop hardware is a lot newer though. There are small
differences in installed packages. Both run Debian jessie (testing). I am
running reportbug on the laptop.

I tried logging in as another user (a test account), and the behaviour is the
same (the window asking what to do is shown twice). I also tested inserting my
phone while logged in to my primary account, and it only showed one window.
The e-reader is recognized as one device. That is, the e-reader is shown only
once on the desktop and in the 'Computer' place.

(I don't know whether caja itself causes this bug, but I have no idea where
else to look.)



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages caja depends on:
ii  caja-common   1.8.2-1
ii  desktop-file-utils0.22-1
ii  gvfs  1.22.1-1
ii  libatk1.0-0   2.14.0-1
ii  libc6 2.19-13
ii  libcairo2 1.14.0-2.1
ii  libcaja-extension11.8.2-1
ii  libexempi32.2.1-2
ii  libexif12 0.6.21-2
ii  libfontconfig12.11.0-6.1
ii  libfreetype6  2.5.2-2
ii  libgail18 2.24.25-1
ii  libgdk-pixbuf2.0-02.31.1-2+b1
ii  libglib2.0-0  2.42.0-2
ii  libglib2.0-data   2.42.0-2
ii  libgtk2.0-0   2.24.25-1
ii  libice6   2:1.0.9-1
ii  libmate-desktop-2-17  1.8.1+dfsg1-2
ii  libpango-1.0-01.36.8-2
ii  libpangocairo-1.0-0   1.36.8-2
ii  libpangoft2-1.0-0 1.36.8-2
ii  libselinux1   2.3-2
ii  libsm62:1.2.2-1
ii  libstartup-notification0  0.12-4
ii  libunique-1.0-0   1.1.6-5
ii  libx11-6  2:1.6.2-3
ii  libxext6  2:1.3.3-1
ii  libxml2   2.9.1+dfsg1-4
ii  libxrender1   1:0.9.8-1+b1
ii  mate-desktop  1.8.1+dfsg1-2
ii  shared-mime-info  1.3-1

caja recommends no packages.

Versions of packages caja suggests:
ii  engrampa 1.8.1+dfsg1-1
pn  gstreamer0.10-tools  none
ii  meld 3.12.0-1


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#766871: mate-control-center: many settings are unavailable

[Ayke van Laethem]

I tried upgrading mate-control-center but that did not help. Upgrading
marco *did* help. So it looks more like an issue in marco to me.
Anyway, it has been fixed now (window management keyboard shortcuts
are now shown).


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#766871: mate-control-center: many settings are unavailable

[Ayke van Laethem]

Package: mate-control-center
Version: 1.8.2+dfsg1-1
Severity: important

Dear Maintainer,

mate-keybinding-properties only lists some options under Sound and Desktop.
I remember seeing much more options, and a screenshot I found on the internet
[1] also shows some options now not visible anymore. Maybe this has been done
on purpose, but I can hardly imagine so, so I'm reporting it as a bug.
(Severity important as an important part of the functionality is impacted).

I have attached a screenshot of mate-keybinding-properties.

Some of my (modified?) configuration:

~$ dconf dump /org/mate/marco/
[general]
theme='BlackMATE'
num-workspaces=16

[global-keybindings]
switch-to-workspace-right='PrimaryAltl'
run-command-terminal='disabled'
switch-to-workspace-left='PrimaryAlth'
switch-to-workspace-down='PrimaryAltj'
switch-to-workspace-up='PrimaryAltk'

[window-keybindings]
maximize='disabled'
toggle-maximized='PrimaryMod4Up'
unmaximize='PrimaryMod4Down'
move-to-workspace-up='PrimaryShiftAltk'
toggle-fullscreen='PrimaryAltf'
move-to-workspace-right='PrimaryShiftAltl'
move-to-workspace-left='PrimaryShiftAlth'
move-to-workspace-down='PrimaryShiftAltj'

Many of these options are not available anymore, and can only be set using for
example dconf-editor.

[1] http://onemoretech.files.wordpress.com/2014/09/mapping-delete.png



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mate-control-center depends on:
ii  caja-common 1.8.2-1
ii  desktop-file-utils  0.22-1
ii  gsettings-desktop-schemas   3.14.0-1
ii  libatk1.0-0 2.14.0-1
ii  libc6   2.19-11
ii  libcairo2   1.12.16-5
ii  libcanberra-gtk00.30-2.1
ii  libcanberra00.30-2.1
ii  libdbus-1-3 1.8.8-2
ii  libdbus-glib-1-20.102-1
ii  libdconf1   0.22.0-1
ii  libfontconfig1  2.11.0-6.1
ii  libfreetype62.5.2-2
ii  libgdk-pixbuf2.0-0  2.31.1-2+b1
ii  libglib2.0-02.42.0-2
ii  libglib2.0-bin  2.42.0-2
ii  libgtk2.0-0 2.24.25-1
ii  libice6 2:1.0.9-1
ii  libmarco-private0   1.8.2+dfsg1-1
ii  libmate-desktop-2-171.8.1+dfsg1-1
ii  libmate-menu2   1.8.0-5
ii  libmate-slab0   1.8.2+dfsg1-1
ii  libmate-window-settings11.8.2+dfsg1-1
ii  libmatekbd4 1.8.0-2
ii  libpango-1.0-0  1.36.8-2
ii  libpangocairo-1.0-0 1.36.8-2
ii  libpangoft2-1.0-0   1.36.8-2
ii  libsm6  2:1.2.2-1
ii  libstartup-notification00.12-4
ii  libunique-1.0-0 1.1.6-5
ii  libx11-62:1.6.2-3
ii  libxcursor1 1:1.1.14-1
ii  libxext62:1.3.3-1
ii  libxft2 2.3.2-1
ii  libxi6  2:1.7.4-1
ii  libxklavier16   5.2.1-1
ii  libxml2 2.9.1+dfsg1-4
ii  libxss1 1:1.2.2-1
ii  marco-common1.8.2+dfsg1-1
ii  mate-control-center-common  1.8.2+dfsg1-1
ii  mate-desktop1.8.1+dfsg1-1
ii  mate-icon-theme 1.8.0-1
ii  mate-menus  1.8.0-5
ii  mate-settings-daemon1.8.1-2

mate-control-center recommends no packages.

Versions of packages mate-control-center suggests:
ii  gconf2  3.2.6-3

-- no debconf information

Bug#671121:

[Ayke van Laethem]

This bug has been fixed in the upstream release of lightdm-gtk-greeter. See:

https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1024482
(comment #21)
https://github.com/mate-desktop/mate-settings-daemon/issues/46#issuecomment-57939325

Would it be possible to include this patch in jessie?

— Ayke


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#766749: mate-power-manager: brightness is not shown while changing brightness using hardware keys

[Ayke van Laethem]

Package: mate-power-manager
Version: 1.8.1+dfsg1-1
Severity: normal

Dear Maintainer,

When pressing Fn+Home or Fn+End, the hardware keys to change the display
brightness on a Lenovo Thinkpad T60, a small grey (depending on theme) square
is shown in the center of the bottom half of the screen, but the actual
brightness is not shown. I would expect the new (changed) brightness to be
shown in the square, and I remember seeing it before (probably in Linux Mint
Debian Edition, MATE 1.6). I have attached an image of the square on a browser
background.

Note: I submitted this bug on a different system, but the version
information etc. should be of the affected system (I copied the full
body of the generated bug message).



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mate-power-manager depends on:
ii  consolekit  0.4.6-5
ii  dbus-x111.8.8-2
ii  libatk1.0-0 2.14.0-1
ii  libc6   2.19-11
ii  libcairo2   1.12.16-5
ii  libcanberra-gtk00.30-2.1
ii  libcanberra00.30-2.1
ii  libdbus-1-3 1.8.8-2
ii  libdbus-glib-1-20.102-1
ii  libfontconfig1  2.11.0-6.1
ii  libfreetype62.5.2-2
ii  libgdk-pixbuf2.0-0  2.31.1-2+b1
ii  libglib2.0-02.42.0-2
ii  libgnome-keyring0   3.12.0-1+b1
ii  libgtk2.0-0 2.24.25-1
ii  libmate-panel-applet-4-11.8.1+dfsg1-1
ii  libnotify4  0.7.6-2
ii  libpango-1.0-0  1.36.8-2
ii  libpangocairo-1.0-0 1.36.8-2
ii  libpangoft2-1.0-0   1.36.8-2
ii  libunique-1.0-0 1.1.6-5
ii  libupower-glib3 0.99.1-3
ii  libx11-62:1.6.2-3
ii  libxext62:1.3.3-1
ii  libxrandr2  2:1.4.2-1
ii  libxrender1 1:0.9.8-1
ii  mate-notification-daemon [notification-daemon]  1.8.0-2
ii  mate-power-manager-common   1.8.1+dfsg1-1
ii  notification-daemon 0.7.6-2
ii  policykit-1 0.105-7
ii  systemd 215-5+b1
ii  upower  0.99.1-3

Versions of packages mate-power-manager recommends:
ii  udisks  1.0.5-1+b1

Versions of packages mate-power-manager suggests:
ii  mate-polkit  1.8.0+dfsg1-4

-- no debconf information

Bug#766801: mate-applets: battery charge monitor icon goes the reverse order while charging

[Ayke van Laethem]

Package: mate-applets
Version: 1.8.1+dfsg1-3
Severity: normal

Dear Maintainer,

When my laptop is on AC power, the Battery Charge Monitor shows a near-empty
battery icon when the battery has fully recharged, and a full battery when it
is empty. When the laptop (a Lenovo Thinkpad T60) runs on battery power, the
applet works as expected: the battery icon shows a graphic representation of
the actual charge level. I would expect the icon to behave in a similar way
regardless of whether it is charging or not.
(Additionally, when the power plug is inserted or removed, the icon isn't
updated immediately, but I think that issue is only a side effect of this bug).

I have attached a screenshot of the applet when the battery is full.

(This bug, like #766749, has been submitted using a different system
than where it occurs, because sendmail does not work on my laptop for
some reason).


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mate-applets depends on:
ii  gir1.2-mate-panel   1.8.1+dfsg1-1
ii  gsettings-desktop-schemas   3.14.0-1
ii  gstreamer0.10-alsa  0.10.36-2
ii  gstreamer0.10-plugins-good  0.10.31-3+nmu4+b1
ii  gvfs1.22.1-1
ii  libatk1.0-0 2.14.0-1
ii  libc6   2.19-11
ii  libcairo2   1.12.16-5
ii  libcpufreq0 008-1
ii  libdbus-1-3 1.8.8-2
ii  libdbus-glib-1-20.102-1
ii  libfontconfig1  2.11.0-6.1
ii  libfreetype62.5.2-2
ii  libgdk-pixbuf2.0-0  2.31.1-2+b1
ii  libglib2.0-02.42.0-2
ii  libgtk2.0-0 2.24.25-1
ii  libgtksourceview2.0-0   2.10.5-2
ii  libgtop2-7  2.28.5-2
ii  libice6 2:1.0.9-1
ii  libmate-desktop-2-171.8.1+dfsg1-1
ii  libmate-panel-applet-4-11.8.1+dfsg1-1
ii  libmateweather1 1.8.0-2
ii  libnotify4  0.7.6-2
ii  libpango-1.0-0  1.36.8-2
ii  libpangocairo-1.0-0 1.36.8-2
ii  libpangoft2-1.0-0   1.36.8-2
ii  libpolkit-gobject-1-0   0.105-7
ii  libsm6  2:1.2.2-1
ii  libstartup-notification00.12-4
ii  libupower-glib3 0.99.1-3
ii  libwnck22   2.30.7-2
ii  libx11-62:1.6.2-3
ii  libxml2 2.9.1+dfsg1-4
ii  mate-applets-common 1.8.1+dfsg1-3
ii  mate-icon-theme 1.8.0-1
ii  mate-panel  1.8.1+dfsg1-1
ii  python  2.7.8-1
ii  python-dbus 1.2.0-2+b3
ii  python-gi   3.14.0-1
ii  python-gobject  3.14.0-1
ii  python-gst0.10  0.10.22-3
ii  python-notify   0.1.1-3

Versions of packages mate-applets recommends:
ii  cpufrequtils 008-1
ii  mate-media   1.8.0+dfsg1-3
ii  mate-polkit  1.8.0+dfsg1-4
ii  mate-system-monitor  1.8.0+dfsg1-2

mate-applets suggests no packages.

-- no debconf information

Bug#766806: mate-power-manager: LCD brightness changes on login while running on battery power

[Ayke van Laethem]

Package: mate-power-manager
Version: 1.8.1+dfsg1-1
Severity: normal

Dear Maintainer,

On login, the LCD brightness is changed to the value in the Power Management
Preferences, under the On AC Power tab. This happens not only on AC power (as
expected), but also when running a laptop on battery power, which I would not
expect (I would expect the value listed there only to be applied on AC power,
not on battery power).

Oddly, when changing the brightness slider in the settings (Set display
brightness to), the new brightness is applied immediately when on AC power,
but is not (immediately) applied when running on battery power.

As a separate issue, but I'm mentioning it here anyway as it's related, there
is no way to *not* change brightness when running on AC power on login (and,
due to this bug, also on battery power). I personally prefer to set the
brightness depending on the environment, not (normally) based on battery power.
I can report a different bug for this if necessary, but maybe that feature is
too close to the freeze to be added anyway.

Here are my power management preferences:

~$ dconf dump /org/mate/power-manager/
[/]
button-power='interactive'
sleep-display-battery=600
brightness-ac=22.0
info-last-device='/org/freedesktop/UPower/devices/mouse_0003o046DoC52Bx0004'
backlight-battery-reduce=false
button-lid-ac='nothing'
spindown-enable-battery=true
info-stats-graph-points=true
info-stats-graph-smooth=false
action-critical-battery='suspend'
button-suspend='suspend'
info-history-graph-points=true
info-history-time=86400
info-page-number=0
idle-dim-ac=false
info-history-type='charge'
idle-dim-battery=false
button-lid-battery='suspend'
info-stats-type='charge-data'
info-history-graph-smooth=false
icon-policy='never'

By changing the Set display brightness to setting a few times and logging out
and back in, I have confirmed it is really set to that setting. And it is that
setting it is set to when it is on battery power as well.

I have attached a screenshot of the Power Management Preferences window.



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mate-power-manager depends on:
ii  consolekit  0.4.6-5
ii  dbus-x111.8.8-2
ii  libatk1.0-0 2.14.0-1
ii  libc6   2.19-11
ii  libcairo2   1.12.16-5
ii  libcanberra-gtk00.30-2.1
ii  libcanberra00.30-2.1
ii  libdbus-1-3 1.8.8-2
ii  libdbus-glib-1-20.102-1
ii  libfontconfig1  2.11.0-6.1
ii  libfreetype62.5.2-2
ii  libgdk-pixbuf2.0-0  2.31.1-2+b1
ii  libglib2.0-02.42.0-2
ii  libgnome-keyring0   3.12.0-1+b1
ii  libgtk2.0-0 2.24.25-1
ii  libmate-panel-applet-4-11.8.1+dfsg1-1
ii  libnotify4  0.7.6-2
ii  libpango-1.0-0  1.36.8-2
ii  libpangocairo-1.0-0 1.36.8-2
ii  libpangoft2-1.0-0   1.36.8-2
ii  libunique-1.0-0 1.1.6-5
ii  libupower-glib3 0.99.1-3
ii  libx11-62:1.6.2-3
ii  libxext62:1.3.3-1
ii  libxrandr2  2:1.4.2-1
ii  libxrender1 1:0.9.8-1
ii  mate-notification-daemon [notification-daemon]  1.8.0-2
ii  mate-power-manager-common   1.8.1+dfsg1-1
ii  notification-daemon 0.7.6-2
ii  policykit-1 0.105-7
ii  systemd 215-5+b1
ii  upower  0.99.1-3
ii  xfce4-notifyd [notification-daemon] 0.2.4-3

Versions of packages mate-power-manager recommends:
ii  udisks  1.0.5-1+b1

Versions of packages mate-power-manager suggests:
ii  mate-polkit  1.8.0+dfsg1-4

Bug#765573: hugin: Creation timestamp metadata not set on created panorama (regression)

[Ayke van Laethem]

Trying again, I cannot reproduce the issue. I'm not sure why I saw it
before, but now timestamps are properly set (with existing .hugin directory
and after moving it away), so I would suggest closing this bug.

— Ayke

2014-10-18 13:54 GMT+02:00 Andreas Metzler ametz...@bebt.de:

 On 2014-10-16 Ayke van Laethem aykevanlaet...@gmail.com wrote:
  I've seen this feature being referenced in a different bug, so it
  really was there before:
  https://bugs.launchpad.net/hugin/+bug/679932

  were these two headers be copied from (one of) the input images or
  were they set by hugin (time of panorama generation)?

  They were set to the same time as the first input image. The first
  being the one with the oldest timestamp, the first in an alphabetic
  directory listing, or the first image being added. I'm not entirely
  sure how it picks the 'first' image, but as the Create time is the
  same, it must have copied it.

 Hello,

 thanks for the additional info.

 However, I cannot reproduce the problem. I have just taken some old
 images of mine and restitched them (starting freshly, not using the old
 project file) and indeed as you decribed Create Date|Date/Time
 Original was copied from the first image:
 ametzler@argenau:/tmp/Sospel$ exiftool testimage_fused.tif | grep -E
 'Create Date|Date/Time Original'
 Date/Time Original  : 2008:09:02 10:03:15
 Create Date : 2008:09:02 10:03:15

 Could you doublecheck whether some local setting is broken by
 temporarily moving away ~/.hugin and checking with a simple project
 (starting from scratch)?

 cu Andreas
 --
 `What a good friend you are to him, Dr. Maturin. His other friends are
 so grateful to you.'
 `I sew his ears on from time to time, sure'

Bug#765573: hugin: Creation timestamp metadata not set on created panorama (regression)

[Ayke van Laethem]

Package: hugin
Version: 2014.0.0+dfsg-1
Severity: normal

Dear Maintainer,

When creating a panorama using Create panorama in the Assistant tab,
Hugin doesn't save the Create Date or Date/Time Original Exif
headers. This used to work previously for me. I'm not exactly sure when
it worked, possibly on Ubuntu =12.04, but older panoramas created using
Hugin do have this metadata.

In the preferences, Copy metadata into final files using ExifTool
is set. The ExifTool argfile text box is empty. Maybe I could fix it by
setting something in there, but I'm not sure how to do that.
The processor used is Hugin_stitch_project, if that matters.

Interestingly, the Make and Camera Model Name headers are set.

I have installed hugin from unstable, but the rest of the system is
testing (jessie).

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages hugin depends on:
ii  enblend   4.1.3+dfsg-2
ii  enfuse4.1.3+dfsg-2
ii  hugin-tools   2014.0.0+dfsg-1
ii  libboost-system1.55.0 1.55.0+dfsg-3
ii  libboost-thread1.55.0 1.55.0+dfsg-3
ii  libc6 2.19-11
ii  libexiv2-13   0.24-4
ii  libgcc1   1:4.9.1-16
ii  libgl1-mesa-glx [libgl1]  10.2.8-1
ii  libglew1.10   1.10.0-3
ii  libglu1-mesa [libglu1]9.0.0-2
ii  libimage-exiftool-perl9.72-1
ii  libpano13-3   2.9.19+dfsg-1+b1
ii  libstdc++64.9.1-16
ii  libtiff5  4.0.3-10+b1
ii  libwxbase3.0-03.0.2-1
ii  libwxgtk3.0-0 3.0.2-1
ii  make-guile [make] 4.0-8

hugin recommends no packages.

hugin suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#765573: hugin: Creation timestamp metadata not set on created panorama (regression)

[Ayke van Laethem]

I've seen this feature being referenced in a different bug, so it
really was there before:
https://bugs.launchpad.net/hugin/+bug/679932

 were these two headers be copied from (one of) the input images or
 were they set by hugin (time of panorama generation)?

They were set to the same time as the first input image. The first
being the one with the oldest timestamp, the first in an alphabetic
directory listing, or the first image being added. I'm not entirely
sure how it picks the 'first' image, but as the Create time is the
same, it must have copied it.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#750690: mate-themes: BlackMATE tooltips in Chromium are unreadable

[Ayke van Laethem]

Package: mate-themes
Version: 1.8.1-1
Severity: minor

Dear Maintainer,

When using the BlackMATE theme on the MATE desktop, tooltips in Chromium have a
light background, but unchanged (white) text color. This makes them practically
unreadable in Chromium. The same happens in Google Chrome (not included in
Debian). Other applications appear to work fine (including Firefox, if that
matters).



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mate-themes depends on:
ii  gtk2-engines  1:2.20.2-3
ii  gtk2-engines-murrine  0.98.1.1-5
ii  gtk2-engines-pixbuf   2.24.23-1
ii  librsvg2-common   2.40.2-1
ii  mate-icon-theme   1.8.0-1

Versions of packages mate-themes recommends:
ii  dmz-cursor-theme  0.4.4

mate-themes suggests no packages.

-- no debconf information