Bug#899031: [roxterm] Please provide new roxterm packages

[Tony Houghton]

On Thu, 20 Sep 2018 at 11:30, Egmont Koblinger  wrote:

> ... and he's also the maintainer of the Debian package, haha, I missed
> this bit :)
>
> Tony, do you feel like reviving maintenance of the Debian package, or
> perhaps finding a new maintainer for it?
>

I was only a sponsored maintainer, and I found the release process a bit of
a pain to be honest. I would prefer it if a 3rd party maintainer could be
found. There wouldn't be much for them to do because I have kept the debian
subdirectory up to date - which also makes it easy for users to build their
own package straight from git, so I don't really see a huge demand for
making it official again.

Bug#900378: glx-alternative-nvidia: Fails to enable proprietary accelerated OpenGL and does not report the problem

[Tony Houghton]

Package: glx-alternative-nvidia
Version: 0.8.3
Severity: normal

Since a dist-upgrade I noticed a poor framerate and high CPU usage in
Minecraft. glxinfo seems to indicate it's using software rendering:

name of display: :1
display: :1  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
...
Extended renderer info (GLX_MESA_query_renderer):
Vendor: VMware, Inc. (0x)
Device: llvmpipe (LLVM 6.0, 128 bits) (0x)
Version: 18.0.4
Accelerated: no
...

I think the source of the problem is that the available version of most
of the binary packages of nvidia-graphics-drivers is 390.59-1 but for
libgl1-glvnd-nvidia-glx it's 390.48-3 (can there really be a lag of a
whole day for packages from the same source package to make it into the
archive?) so it can't be installed. But seeing as
glx-alternative-nvidia's main job is to activate the proprietary driver
it should report the problem if it's unable to do that and/or it should
depend on all the packages it needs.

-- Package-specific info:
Diversions:
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.0.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.7.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.7.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.2.0 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.0.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.0.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.7.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.7.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.2.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.2.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2.1.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2.1.0 by glx-diversions
diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by 
glx-diversions
diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
glx-diversions
div

Bug#885081: brasero: Can not burn cue/bin image to audio CD

[Tony Houghton]

Package: brasero
Version: 3.12.2-4
Severity: important

After failing to burn directly to CD due to bug #885080 I instead used
Brasero to create a cue/bin image. This stage worked just fine, but then
Brasero failed to burn the image to CD. When the dialog opened it first
reported the space on the disc correctly, but after selecting the cue
file it changed to claim the disc had 18.4EB available! I proceeded
anyway, but Brasero just ejected the disc then reported there was an
"unknown error".

Burning the image with cdrdao on the command line worked correctly and
the disc appears to work (from an admittedly brief test) in an audio CD
player.

My drive is a SATA DVD-RAM burner branded LG, which Brasero identifies
as HL-DT-ST DVDRAM GH22NS70.

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

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

Versions of packages brasero depends on:
ii  brasero-common  3.12.2-4
ii  gstreamer1.0-plugins-base   1.12.4-1
ii  gvfs1.34.1-2
ii  libbrasero-media3-1 3.12.2-4
ii  libc6   2.25-5
ii  libcairo2   1.15.8-3
ii  libgdk-pixbuf2.0-0  2.36.11-1
ii  libglib2.0-02.54.2-4
ii  libgstreamer-plugins-base1.0-0  1.12.4-1
ii  libgstreamer1.0-0   1.12.4-1
ii  libgtk-3-0  3.22.26-2
ii  libpango-1.0-0  1.40.14-1
ii  libtotem-plparser18 3.26.0-2
ii  libtracker-sparql-2.0-0 2.0.2-1
ii  libxml2 2.9.4+dfsg1-5.2

Versions of packages brasero recommends:
ii  brasero-cdrkit  3.12.2-4
ii  nautilus-extension-brasero  3.12.2-4
ii  yelp3.26.0-2

Versions of packages brasero suggests:
pn  libdvdcss2  
ii  tracker 2.0.2-1
pn  vcdimager   

-- no debconf information

Bug#885080: brasero: Can not burn from MP3s directly to CD

[Tony Houghton]

Package: brasero
Version: 3.12.2-4
Severity: normal

I tried to create an audio CD from a set of MP3 files, using Brasero's
default options. Everything appears OK, including correct reporting of
how much free space will remain on the disc (which may be significant
for another bug I'm about to report), until a dialog appears saying
"Burning audio CD" ... "Starting to record". This is suspect, because it
appears before Brasero could have had enough time to decode the MP3s.
After a few seconds it freezes, without using significant CPU, and has
to be killed.

Brasero is able to create a valid cue/bin image from the files, which
works after burning with cdrdao, but Brasero can't actually burn this
image itself. The symptoms are somewhat different, so I'll report that
as a separate bug.

My drive is a SATA DVD-RAM burner branded LG, which Brasero identifies
as HL-DT-ST DVDRAM GH22NS70.

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

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

Versions of packages brasero depends on:
ii  brasero-common  3.12.2-4
ii  gstreamer1.0-plugins-base   1.12.4-1
ii  gvfs1.34.1-2
ii  libbrasero-media3-1 3.12.2-4
ii  libc6   2.25-5
ii  libcairo2   1.15.8-3
ii  libgdk-pixbuf2.0-0  2.36.11-1
ii  libglib2.0-02.54.2-4
ii  libgstreamer-plugins-base1.0-0  1.12.4-1
ii  libgstreamer1.0-0   1.12.4-1
ii  libgtk-3-0  3.22.26-2
ii  libpango-1.0-0  1.40.14-1
ii  libtotem-plparser18 3.26.0-2
ii  libtracker-sparql-2.0-0 2.0.2-1
ii  libxml2 2.9.4+dfsg1-5.2

Versions of packages brasero recommends:
ii  brasero-cdrkit  3.12.2-4
ii  nautilus-extension-brasero  3.12.2-4
ii  yelp3.26.0-2

Versions of packages brasero suggests:
pn  libdvdcss2  
ii  tracker 2.0.2-1
pn  vcdimager   

-- no debconf information

Bug#878845: thunderbird: Thunderbird displays artifacts on screen

[Tony Houghton]

Package: thunderbird
Version: 1:52.3.0-4
Followup-For: Bug #878845

I'm seeing the same thing, but on a hidpi screen, so the vertical lines
are thinner, and I didn't notice at first that they're red and that
there are also dots. Apart from the higher resolution I think it's
exactly as the OP described, only appearing about a day ago when I
upgraded other packages, but I don't update every day.

Certain dialogs don't seem to be affected eg Print and Save As, but
Print Preview is affected (including the buttons in the action area). I
guess the first two are standard GTK dialogs, while Print Preview is
specific to Thunderbird.

I think it's caused by having font subpixel antialiasing enabled; when I
switched it to greyscale/standard I couldn't see the artifacts any more.
This still looks OK in hidpi, but SD screen users would probably notice
a slight degradation in font rendering quality across their desktop. Is
there an environment variable or something that can be set to give
Thunderbird different font settings from the rest of the desktop?

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

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

Versions of packages thunderbird depends on:
ii  debianutils   4.8.2
ii  fontconfig2.12.3-0.2
ii  libatk1.0-0   2.26.0-2
ii  libc6 2.24-17
ii  libcairo-gobject2 1.14.10-1
ii  libcairo2 1.14.10-1
ii  libdbus-1-3   1.11.20-1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-6
ii  libfontconfig12.12.3-0.2
ii  libfreetype6  2.8.1-0.1
ii  libgcc1   1:7.2.0-10
ii  libgdk-pixbuf2.0-02.36.11-1
ii  libglib2.0-0  2.54.1-1
ii  libgtk-3-03.22.24-2
ii  libhunspell-1.6-0 1.6.2-1
ii  libpango-1.0-01.40.12-1
ii  libpangocairo-1.0-0   1.40.12-1
ii  libpangoft2-1.0-0 1.40.12-1
ii  libpixman-1-0 0.34.0-1
ii  libstartup-notification0  0.12-4+b2
ii  libstdc++67.2.0-10
ii  libvpx4   1.6.1-3
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  psmisc23.1-1
ii  x11-utils 7.7+3+b1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages thunderbird recommends:
ii  hunspell-en-gb [hunspell-dictionary]  1:5.2.5-1
ii  hunspell-en-us [hunspell-dictionary]  20070829-7
ii  lightning 1:52.3.0-4

Versions of packages thunderbird suggests:
pn  apparmor  
pn  fonts-lyx 
ii  libgssapi-krb5-2  1.15.1-2

-- no debconf information

Bug#878165: firmware-iwlwifi: Some firmware versions cause 8260 Bluetooth malfunction

[Tony Houghton]

Package: firmware-iwlwifi
Version: 20170823-1
Severity: normal

I have a 4th generation Lenovo Thinkpad Carbon X1 with Intel 8260
wifi/bluetooth:

04:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] 
(rev 3a)
Subsystem: Intel Corporation Wireless 8260 [8086:1130]
Flags: bus master, fast devsel, latency 0, IRQ 130
Memory at f110 (64-bit, non-prefetchable) [size=8K]
Capabilities: 
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

When trying to use my bluetooth mouse yesterday, I couldn't get it to
connect successfully. I tried again today, and after a lot of hassle
turning Bluetooth on and off in GNOME and pressing the mouse's connect
button it connected. But it only worked for a short time, about a
minute, then the mouse stopped working even though the BT config said it
was connected. This kept happening each time I reconnected.

I've replaced the package with 20161130-3 from stable, and bluetooth
seems to work correctly with this older firmware. But I had the same
problem a few months ago (which I commented on at a now closed bug
) with kernel
4.9.6-3 and firmware-iwlwifi 20161130-2, so it seems like something that
was changed between 20161130-2 and -3 cured this problem, but it has now
regressed.

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

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

firmware-iwlwifi depends on no packages.

firmware-iwlwifi recommends no packages.

Versions of packages firmware-iwlwifi suggests:
ii  initramfs-tools  0.130

-- no debconf information

Bug#876198: libinput10: Can't initiate a touchpad motion near a corner

[Tony Houghton]

Package: libinput10
Version: 1.8.2-1
Severity: normal

When using GNOME on Wayland I can't move the pointer with the touchpad
if I initially start touching it near a corner. Even if I drag my finger
across the middle from the corner, the pointer doesn't move, and no
events are shown in libinput-debug-events. If I do the opposite, ie
start the motion near the middle of the touchpad, it continues to track
my finger correctly if I move it into the corners.

I only noticed this recently, so it's probably something in the most
recent version to enter Debian. GNOME on Xorg is not affected; AIUI
GNOME on Wayland uses libinput, and something else on Xorg, so I guessed
this is the culprit package.

The machine is a Lenovo Thinkpad Carbon X1 4th Generation. From
libinput-list-devices:

Device:   SynPS/2 Synaptics TouchPad
Kernel:   /dev/input/event1
Group:8
Seat: seat0, default
Size: 100x57mm
Capabilities: pointer
Tap-to-click: disabled
Tap-and-drag: enabled
Tap drag lock:disabled
Left-handed:  disabled
Nat.scrolling:disabled
Middle emulation: disabled
Calibration:  n/a
Scroll methods:   *two-finger edge
Click methods:*button-areas clickfinger
Disable-w-typing: enabled
Accel profiles:   none
Rotation: n/a

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

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

Versions of packages libinput10 depends on:
ii  libc6 2.24-17
ii  libevdev2 1.5.7+dfsg-1
ii  libinput-bin  1.8.2-1
ii  libmtdev1 1.1.5-1+b1
ii  libudev1  234-3
ii  libwacom2 0.24-1

libinput10 recommends no packages.

libinput10 suggests no packages.

-- no debconf information

Bug#875793: evolution: Does not restore mail pane sizes when reloading

[Tony Houghton]

Package: evolution
Version: 3.26.0-1
Severity: normal

Evolution has recently started to fail to restore the message pane sizes
each time it starts up. Whether in Classic or Vertical view it opens
with an approximate 2:1 split between the message list pane and message
preview, ie the former is twice as big as the latter, so the message
preview is too small.

Strangely, when I tried 3.22.6-1/stable and 3.24.5-3/testing they both
had the same problem (although 3.22 seemed to use a 1:1 split) even
though I only started to experience it since a dist-upgrade (unstable)
yesterday.  So I think some sort of interaction with another component
has caused this, which is why I'm reporting it here instead of upstream.

With dconf-editor open I can see the
/org/gnome/evolution/mail/paned-size or hpaned-size values changing when
I move the border between the panes, but they seem to change the
opposite way I would expect, because the schema descriptions say they're
the size of the message-list pane, but they get smaller if I increase
the size of the message list (reducing the size of the message preview).

The default value for paned-size's schema is 144, but when I load
Evolution in Classic View it gets set to 192. In Vertical View
hpaned-size gets set to 357, its default is 450.

FWIW I'm using GNOME on Wayland with a hidpi display of 2560x1440.

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

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

Versions of packages evolution depends on:
ii  dbus   1.11.16+really1.10.22-1
ii  evolution-common   3.26.0-1
ii  evolution-data-server  3.26.0-1
ii  libc6  2.24-17
ii  libcamel-1.2-603.26.0-1
ii  libclutter-gtk-1.0-0   1.8.4-1
ii  libecal-1.2-19 3.26.0-1
ii  libedataserver-1.2-22  3.26.0-1
ii  libevolution   3.26.0-1
ii  libglib2.0-0   2.54.0-1
ii  libgtk-3-0 3.22.21-1
ii  libical2   2.0.0-0.5+b1
ii  libnotify4 0.7.7-2
ii  libsoup2.4-1   2.60.0-1
ii  libwebkit2gtk-4.0-37   2.16.6-1
ii  libxml22.9.4+dfsg1-4
ii  psmisc 23.1-1

Versions of packages evolution recommends:
ii  evolution-plugin-bogofilter  3.26.0-1
ii  evolution-plugin-pstimport   3.26.0-1
ii  evolution-plugins3.26.0-1
ii  yelp 3.22.0-1

Versions of packages evolution suggests:
pn  evolution-ews   
pn  evolution-plugins-experimental  
ii  gnupg   2.2.0-3
ii  network-manager 1.8.2-1

-- debconf information:
  evolution/needs_shutdown:
  evolution/kill_processes:

Bug#873343: gstreamer1.0-vaapi: Does not work with Wayland

[Tony Houghton]

retitle 873343 Hard crash attempting to use vaapivp8encoder
thanks
On Mon, 2017-08-28 at 17:06 +0200, Víctor Jáquez wrote:

>
>There are several bugs related to this:
>
>https://bugzilla.gnome.org/show_bug.cgi?id=784429
>https://bugzilla.gnome.org/show_bug.cgi?id=783169
>https://bugzilla.gnome.org/show_bug.cgi?id=781972

[Snip]

>This is another issue, when using vaapisink with mutter:
>
>https://bugzilla.gnome.org/show_bug.cgi?id=775698
OK, thanks. I guess I could have tried harder to find these, but not 
much was showing up in Google, and I wasn't sure whether it was 
Debian-specific.

>> opengl-backend=wayland
>> vo=opengl
>> hwdec=vaapi

>
>This is like if you were doing this:
>
>GST_GL_WINDOW=wayland gst-play-1.0 /home/tony/Videos/paul.mkv -- > 
videosink=glimagesink

>
>And it should work.
Sort of... I get some sort of picture, but it flickers badly, and I 
think it keeps alternating between the first frame and current frame. So 
it could be a deinterlacing issue, because it's a clip from a DVB 
recording, which is 1080i AFAIK. Then it segfaults at the end of the clip.

>I also tried to make green-recorder (an alternative front-end for
> GNOME's screencast feature) use vaapiv8enc and the system

[Correction: vaapivp8enc. ^^]

> completely froze. I don't know if that has the same underlying> cause.
Judging by the links you posted, I think this is a separate issue, so 
it's probably worth keeping this ticket open for it, with a more 
specific title.

Bug#873343: gstreamer1.0-vaapi: Does not work with Wayland

[Tony Houghton]

Package: gstreamer1.0-vaapi
Version: 1.12.2-1+b1
Severity: normal

gstreamer-vaapi appears not to work in a GNOME Wayland environment. If I
run totem from the command line it shows an error message, but
apparently falls back to software rendering:

libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

Trying to play a file with gst-launch:

$ gst-launch-1.0 playbin uri=file:///home/tony/Videos/paul.mkv
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Got context from element 'vaapisink0': gst.vaapi.Display=context, 
gst.vaapi.Display=(GstVaapiDisplay)"\(GstVaapiDisplayWayland\)\ 
vaapidisplaywayland1";
Redistribute latency...
Got context from element 'playsink': gst.vaapi.Display=context, 
gst.vaapi.Display=(GstVaapiDisplay)"\(GstVaapiDisplayWayland\)\ 
vaapidisplaywayland1";
Redistribute latency...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstPulseSinkClock
wl_surface@7: error 2: Failed to create a texture for surface 7
ERROR: from element 
/GstPlayBin:playbin0/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0: 
Internal error: could not render surface
Additional debug info:
../../../gst/vaapi/gstvaapisink.c(1482): gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin0/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0
Execution ended after 0:00:00.000574388
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...

Both work without errors in X11. I think VAAPI itself is OK, because
vainfo works, and so does mpv, provided I use this config:

opengl-backend=wayland
vo=opengl
hwdec=vaapi

I also tried to make green-recorder (an alternative front-end for
GNOME's screencast feature) use vaapiv8enc and the system completely
froze. I don't know if that has the same underlying cause.

This machine is a Lenovo Thinkpad Carbon X1 4th Gen with an Intel
Skylake GPU.

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

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

Versions of packages gstreamer1.0-vaapi depends on:
ii  libc6   2.24-17
ii  libdrm2 2.4.82-1
ii  libegl1-mesa [libegl1-x11]  17.1.5-1
ii  libgl1-mesa-glx [libgl1]17.1.5-1
ii  libglib2.0-02.53.6-1
ii  libgstreamer-plugins-bad1.0-0   1.12.2-1+b1
ii  libgstreamer-plugins-base1.0-0  1.12.2-1
ii  libgstreamer1.0-0   1.12.2-1
ii  libudev1234-2.3
ii  libva-drm1  1.8.3-1
ii  libva-wayland1  1.8.3-1
ii  libva-x11-1 1.8.3-1
ii  libva1  1.8.3-1
ii  libwayland-client0  1.14.0-1
ii  libx11-62:1.6.4-3
ii  libxrandr2  2:1.5.1-1
ii  libxrender1 1:0.9.10-1

gstreamer1.0-vaapi recommends no packages.

Versions of packages gstreamer1.0-vaapi suggests:
pn  gstreamer1.0-vaapi-doc  

-- no debconf information

Bug#859964: emacs25: No scrollbars

[Tony Houghton]

reassign 859964 emacs24
forcemerge 790098 859964
affects 790098 emacs25
thanks

It suddenly occurred to me that I should check whether this bug is 
hidpi-specific, and it is. Adding hidpi to my search I found this is an 
old bug.

Bug#859964: emacs25: No scrollbars

[Tony Houghton]

Package: emacs25
Version: 25.1+1-3+b1
Severity: normal

I just installed emacs25 and discovered that it doesn't support
scrollbars. It apears to be reserving space for them, by drawing a light
grey line near the edge of the screen, but the space is empty and
doesn't respond to mouse clicks. `M-x toggle-scroll-bar-mode' just moves
the grey line to the very edge of the window. I tried emacs24 too, it
has the same problem.

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

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

Versions of packages emacs25 depends on:
ii  emacs25-bin-common 25.1+1-3+b1
ii  gconf-service  3.2.6-4+b1
ii  libacl12.2.52-3+b1
ii  libasound2 1.1.3-5
ii  libatk1.0-02.22.0-1
ii  libc6  2.24-9
ii  libcairo-gobject2  1.14.8-1
ii  libcairo2  1.14.8-1
ii  libdbus-1-31.10.18-1
ii  libfontconfig1 2.11.0-6.7+b1
ii  libfreetype6   2.6.3-3.1
ii  libgconf-2-4   3.2.6-4+b1
ii  libgdk-pixbuf2.0-0 2.36.5-2
ii  libgif75.1.4-0.4
ii  libglib2.0-0   2.50.3-2
ii  libgnutls303.5.8-5
ii  libgomp1   6.3.0-12
ii  libgpm21.20.4-6.2+b1
ii  libgtk-3-0 3.22.11-1
ii  libice62:1.0.9-2
ii  libjpeg62-turbo1:1.5.1-2
ii  libm17n-0  1.7.0-3+b1
ii  libmagickcore-6.q16-3  8:6.9.7.4+dfsg-3
ii  libmagickwand-6.q16-3  8:6.9.7.4+dfsg-3
ii  libotf00.9.13-3+b1
ii  libpango-1.0-0 1.40.5-1
ii  libpangocairo-1.0-01.40.5-1
ii  libpng16-161.6.28-1
ii  librsvg2-2 2.40.16-1+b1
ii  libselinux12.6-3+b1
ii  libsm6 2:1.2.2-1+b3
ii  libtiff5   4.0.7-5
ii  libtinfo5  6.0+20161126-1
ii  libx11-6   2:1.6.4-3
ii  libx11-xcb12:1.6.4-3
ii  libxcb11.12-1
ii  libxfixes3 1:5.0.3-1
ii  libxft22.3.2-1+b2
ii  libxinerama1   2:1.1.3-1+b3
ii  libxml22.9.4+dfsg1-2.2
ii  libxpm41:3.5.12-1
ii  libxrandr2 2:1.5.1-1
ii  libxrender11:0.9.10-1
ii  zlib1g 1:1.2.8.dfsg-5

emacs25 recommends no packages.

Versions of packages emacs25 suggests:
pn  emacs25-common-non-dfsg  

-- no debconf information

Bug#859031: glibmm2.4: Lack of dbg package

[Tony Houghton]

Source: glibmm2.4
Version: 2.50.0-1
Severity: important

There is no libglibmm-2.4-dbg package corresponding to this version.
This makes it much harder to debug applications using glibmm.

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

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

Bug#852872: roxterm actual window size not honoring settings in preferences

[Tony Houghton]

I decided to stop development of ROXTerm for various reasons (the work 
needed to fix this bug being just one of them). It wasn't in a fit state 
to be in Debian any more so I had it removed, which is why the latest 
available package (frozen at jessie) is older than the one you had 
already downloaded from testing or unstable.


The old GTK2 version will continue to work, but all GTK3 versions will 
have this problem which was caused by a change in GTK 3.20.


Another developer has volunteered to fix this bug, and has made a bit of 
progress, despite the messy code and being unfamiliar with GTK. If he 
manages to get it into a usable state we might be able to keep it 
ticking over.

Bug#731486: gimp-dds: Unable to save multiple layers as mipmaps

[Tony Houghton]

This should fix it.

Upstream appears to be dead, but hopefully this plugin will continue to
work for the foreseeable future. There are a couple of github repos that
were exported from Google Code, but they look inactive too.
Description: Fix size chain for non-square mipmaps
Author: Tony Houghton 
Forwarded: No
Last-Update: 2016-11-20
Index: gimp-dds-3.0.1/mipmap.c
===
--- gimp-dds-3.0.1.orig/mipmap.c
+++ gimp-dds-3.0.1/mipmap.c
@@ -143,11 +143,11 @@ unsigned int get_volume_mipmapped_size(i
 int get_next_mipmap_dimensions(int *next_w, int *next_h,
int  curr_w, int  curr_h)
 {
-   if(curr_w == 1 || curr_h == 1)
+   if(curr_w == 1 && curr_h == 1)
   return(0);
 
-   if(next_w) *next_w = curr_w >> 1;
-   if(next_h) *next_h = curr_h >> 1;
+   if(next_w) *next_w = curr_w == 1 ? 1 : curr_w >> 1;
+   if(next_h) *next_h = curr_h == 1 ? 1 : curr_h >> 1;
 
return(1);
 }

Bug#843642: gnome-terminal: Scrolling with touchpad combines smooth and rough movement

[Tony Houghton]

In ROXTerm nearly all mouse events are passed through to the VteTerminal 
widget, except IIRC right-click for the popup menu and ctrl-double-click 
to open a URI. Now the same bug has been found in gnome-terminal there 
are at least 2 reasons to suspect the problem lies in vte. We should 
probably reassign and forward upstream (I can't seem to find an existing 
upstream report for this, but I've never been good at finding existing 
bug reports).

Bug#840640: npm search runs out of memory

[Tony Houghton]

Package: npm
Version: 1.4.21+ds-2
Severity: normal

When running npm search it appeared to run out of memory while building
its index. I was monitoring it in top and the memory usage seemed to be
fairly stable at 23.x% (of 8GB) rather than steadily climbing. Perhaps
node is imposing a limit to keep overall use below 2GB?

Output:

$ npm search minimatch
npm WARN Building the local index for the first time, please be patient

<--- Last few GCs --->

  137285 ms: Scavenge 1393.4 (1449.8) -> 1393.4 (1449.8) MB, 3.2 / 0 ms
[allocation failure].
  137289 ms: Scavenge 1393.4 (1449.8) -> 1393.4 (1449.8) MB, 3.0 / 0 ms
[allocation failure].
  137292 ms: Scavenge 1393.4 (1449.8) -> 1393.4 (1449.8) MB, 3.0 / 0 ms
[allocation failure].
  138179 ms: Mark-sweep 1393.4 (1449.8) -> 1392.9 (1449.8) MB, 887.8 / 0
ms [last resort gc].
  139082 ms: Mark-sweep 1392.9 (1449.8) -> 1393.1 (1449.8) MB, 902.8 / 0
ms [last resort gc].


<--- JS stacktrace --->

 JS stack trace =

Security context: 0x6def95b4629 
1: stringify [native json.js:157] [pc=0x1681a58539e4]
(this=0x6def95ac529 ,u=0x23c6d6a1da49
,v=0x6def95041b9
,I=0x6def95041b9 )
2: arguments adaptor frame: 1->3
3: /* anonymous */
[/usr/share/npm/node_modules/npm-registry-client/lib/get.js:100]
[pc=0x1681a583d317] (this=0x650e961c479 

Bug#832093: [Pkg-utopia-maintainers] Bug#832093: NetworkManager-wait-online.service fails to start and delays boot

[Tony Houghton]

On Sun, 7 Aug 2016 13:56:45 +0200 Michael Biebl  wrote:

It was disabled in the past but I decided to enable it by default (as in
other distros, like Fedora or Ubuntu).
The reason for this is, that nm-wait-online is required to make remote
mounts work or services in general which depend on network-online.target
(aka $network).

Trading boot speed for that is acceptable imho and users who don't need
that can opt-out of nm-wait-online.


How can I "opt out"? I've tried disabling 
NetworkManager-wait-online.service, but that didn't help. I found some 
info about it for Arch, which suggested to mask the service rather than 
disable it, but that hasn't worked either.


I'm not sure making the desktop wait for the network by default is a 
good idea, because you sometimes need the desktop to be able to get 
online, eg to choose a new wifi network and enter its password.


--
TH

Bug#840326: python3-gi-cairo: Significant amount of cairo API is unavailable

[Tony Houghton]

Package: python3-gi-cairo
Version: 3.22.0-1
Severity: important
Tags: upstream
Control: reassign -1 python3-gi-cairo,pyhton-gi-cairo

IMO this package is unusable, to the extent that I considered making the
severity "grave" rather than "important".

I say the API is unavailable because bindings for many important
functions, constants etc are either unimplemented or non-deducible and
undocumented (help(cairo) makes it look as if #640846 has returned with
a vengeance).

For example, I want to use cairo_image_surface_create_for_data(). This
doesn't seem to exist in python-gi. The similar function,
cairo_image_surface_create() can be found to exist with dir(cairo) but,
even if I did want to use that instead, I wouldn't be much better off
because I can't find any mapping for cairo_format_t, and
cairo.image_surface_create.get_arguments() returns an empty tuple.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), 
(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_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-gi-cairo depends on:
ii  libc6  2.24-3
ii  libcairo-gobject2  1.14.6-1+b1
ii  libcairo2  1.14.6-1+b1
ii  libgirepository-1.0-1  1.50.0-1
ii  libglib2.0-0   2.50.0-2
ii  python33.5.1-4
ii  python3-cairo  1.10.0+dfsg-5+b1
ii  python3-gi 3.22.0-1

python3-gi-cairo recommends no packages.

python3-gi-cairo suggests no packages.

-- no debconf information

Bug#839005: vim-youcompleteme: ValueError: bad marshal data (unknown type code)

[Tony Houghton]

Package: vim-youcompleteme
Severity: important
Tags: upstream

I usually use the upstream version with tern enabled, but after my
latest dist-upgrade it stopped working and kept printing "ValueError:
bad marshal data (unknown type code)" at the bottom of the vim window. I
tried rebuilding the plugin, downgrading from vim 8.0 (unstable) to 7.4
(testing) and also installing this Debian package instead of using
upstream, but I kept getting the same error.

I couldn't find any YouCompleteMe-specific references to this error
message on Google, but the search revealed that it's python-related, so
I tried rebuilding upstream with python3 (python3 ./install.py ...) and
this seems to have cured it. So it would probably be a good idea to
migrate this package and ycmd to python3 now.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), 
(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_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#838795: gnome-shell: Startup notification fails on Wayland

[Tony Houghton]

Package: gnome-shell
Version: 3.22.0-1
Severity: normal

When launching an application the spinner continues to show next to its
name in the taskbar, and the app menu can not be opened, for several
seconds after the app has opened, presumably until it times out. Sorry
if this is the wrong package, I don't know what's responsible if it
isn't gnome-shell.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), 
(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_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  evolution-data-server3.20.5-1
ii  gir1.2-accountsservice-1.0   0.6.40-3
ii  gir1.2-atspi-2.0 2.20.2-2
ii  gir1.2-caribou-1.0   0.4.21-1
ii  gir1.2-freedesktop   1.50.0-1
ii  gir1.2-gcr-3 3.20.0-2
ii  gir1.2-gdesktopenums-3.0 3.22.0-1
ii  gir1.2-gdm-1.0   3.22.0-1
ii  gir1.2-glib-2.0  1.50.0-1
ii  gir1.2-gnomebluetooth-1.03.20.0-1
ii  gir1.2-gnomedesktop-3.0  3.22.0-1
ii  gir1.2-gtk-3.0   3.22.0-1
ii  gir1.2-gweather-3.0  3.20.3-1
ii  gir1.2-ibus-1.0  1.5.11-1
ii  gir1.2-mutter-3.03.22.0-1
ii  gir1.2-networkmanager-1.01.4.0-3
ii  gir1.2-nmgtk-1.0 1.4.0-2
ii  gir1.2-pango-1.0 1.40.3-2
ii  gir1.2-polkit-1.00.105-16
ii  gir1.2-soup-2.4  2.56.0-1
ii  gir1.2-telepathyglib-0.120.24.1-1.1
ii  gir1.2-telepathylogger-0.2   0.8.2-1
ii  gir1.2-upowerglib-1.00.99.4-4
ii  gjs  1.46.0-1
ii  gnome-backgrounds3.22.0-2
ii  gnome-settings-daemon3.22.0-1
ii  gnome-shell-common   3.22.0-1
ii  gsettings-desktop-schemas3.22.0-1
ii  libatk-bridge2.0-0   2.20.1-4
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-3
ii  libcairo21.14.6-1+b1
ii  libcanberra-gtk3-0   0.30-3
ii  libcanberra0 0.30-3
ii  libcroco30.6.11-2
ii  libdbus-glib-1-2 0.108-1
ii  libecal-1.2-19   3.20.5-1
ii  libedataserver-1.2-213.20.5-1
ii  libgcr-base-3-1  3.20.0-2
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libgirepository-1.0-11.50.0-1
ii  libgjs0e [libgjs0-libmozjs-24-0] 1.46.0-1
ii  libglib2.0-0 2.50.0-1
ii  libglib2.0-bin   2.50.0-1
ii  libgstreamer1.0-01.8.3-1
ii  libgtk-3-0   3.22.0-1
ii  libical2 2.0.0-0.5+b1
ii  libicu57 57.1-4
ii  libjson-glib-1.0-0   1.2.2-1
ii  libmozjs-24-024.2.0-3.1
ii  libmutter0i  3.22.0-1
ii  libnm-glib4  1.4.0-3
ii  libnm-util2  1.4.0-3
ii  libpango-1.0-0   1.40.3-2
ii  libpangocairo-1.0-0  1.40.3-2
ii  libpolkit-agent-1-0  0.105-16
ii  libpolkit-gobject-1-00.105-16
ii  libpulse-mainloop-glib0  9.0-3
ii  libpulse09.0-3
ii  libsecret-1-00.18.5-2
ii  libstartup-notification0 0.12-4
ii  libsystemd0  231-7
ii  libtelepathy-glib0   0.24.1-1.1
ii  libwayland-client0   1.11.0-2
ii  libx11-6 2:1.6.3-1
ii  libxfixes3   1:5.0.2-1
ii  mutter   3.22.0-1
ii  python3  3.5.1-4
ii  telepathy-mission-control-5  1:5.16.3-2

Versions of packages gnome-shell recommends:
ii  gdm33.22.0-1
ii  gkbd-capplet   

Bug#838793: libgtk-3-0: Menus are too small in GNOME on Wayland

[Tony Houghton]

Package: libgtk-3-0
Version: 3.22.0-1
Severity: important

Since upgrading to 3.22 (I think I was using 3.21 before) many, but not
all, GTK3 applications have broken menus in Wayland. They open very
small with only enough vertical room for scroll arrows and one item, or
less, and far narrower than necessary. Positioning is also incorrect,
and there seems to be some corruption of the content too.

This could be a HiDPI issue because I'm using a Mac Retina, but I
haven't checked another system yet. The affected apps also seem to
ignore the window scaling setting in gnome-tweak-tool, as if it's
hardwried at 2.

One unaffected app is vim-gtk3. I noticed it still depends on gtk 3.19,
so could it be that only apps which have been recompiled against 3.22
are affected?

Launching gedit from a terminal and opening its popup menu shows these
errors:

(gedit:3498): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to
underallocate toplevel GtkWindow 0x5615ae656a40. Allocation is 92x115,
but minimum required size is 173x41.

(gedit:3498): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to
underallocate GtkWindow's child GtkMenu 0x5615aeb4cb40. Allocation is
80x103, but minimum required size is 161x29.

(gedit:3498): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to
underallocate GtkMenuItem's child GtkAccelLabel 0x5615aeb0fd90.
Allocation is 43x17, but minimum required size is 54x17.

(gedit:3498): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to
underallocate GtkMenu's child GtkMenuItem 0x5615af33a190. Allocation is
80x25, but minimum required size is 111x25.

(gedit:3498): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to
underallocate GtkMenuItem's child GtkAccelLabel 0x5615af2d4b70.
Allocation is 17x17, but minimum required size is 73x17.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), 
(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_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libgtk-3-0 depends on:
ii  adwaita-icon-theme  3.22.0-1
ii  hicolor-icon-theme  0.15-1
ii  libatk-bridge2.0-0  2.20.1-4
ii  libatk1.0-0 2.22.0-1
ii  libc6   2.24-3
ii  libcairo-gobject2   1.14.6-1+b1
ii  libcairo2   1.14.6-1+b1
ii  libcolord2  1.3.3-2
ii  libcups22.2.0-2
ii  libepoxy0   1.3.1-1
ii  libfontconfig1  2.11.0-6.7
ii  libfreetype62.6.3-3+b1
ii  libgdk-pixbuf2.0-0  2.36.0-1
ii  libglib2.0-02.50.0-1
ii  libgtk-3-common 3.22.0-1
ii  libjson-glib-1.0-0  1.2.2-1
ii  libpango-1.0-0  1.40.3-2
ii  libpangocairo-1.0-0 1.40.3-2
ii  libpangoft2-1.0-0   1.40.3-2
ii  librest-0.7-0   0.8.0-1
ii  libsoup2.4-12.56.0-1
ii  libwayland-client0  1.11.0-2
ii  libwayland-cursor0  1.11.0-2
ii  libwayland-egl1-mesa [libwayland-egl1]  12.0.3-1
ii  libx11-62:1.6.3-1
ii  libxcomposite1  1:0.4.4-1
ii  libxcursor1 1:1.1.14-1+b1
ii  libxdamage1 1:1.1.4-2+b1
ii  libxext62:1.3.3-1
ii  libxfixes3  1:5.0.2-1
ii  libxi6  2:1.7.6-1
ii  libxinerama12:1.1.3-1+b1
ii  libxkbcommon0   0.6.1-1
ii  libxml2 2.9.4+dfsg1-2
ii  libxrandr2  2:1.5.0-1
ii  shared-mime-info1.7-1

Versions of packages libgtk-3-0 recommends:
ii  libgtk-3-bin  3.21.5-3

Versions of packages libgtk-3-0 suggests:
ii  gvfs 1.30.0-1
ii  librsvg2-common  2.40.16-1

-- no debconf information

Bug#838586: roxterm false on start up segfault

[Tony Houghton]

I've discontinued roxterm because the amount of work needed to fix 
outstanding bugs and continue to maintain it was more than it was worth. 
gnome-terminal is pretty good these days, and there are other terminals.


This bug looks like it's caused by an ABI change in VTE, which you would 
need roxterm version 3 for, but there was also another nasty 
incompatibility with GTK 3.20, hence its removal from Debian.


If you really badly want to keep using roxterm and don't mind missing 
some features you could try roxterm-gtk2.


--
TH

Bug#832077: Gtk-WARNING **: EmacsFixed 0x95c12e8 is drawn without a current allocation. This should not happen.

[Tony Houghton]

reassign 832077 libgtk-3-0 3.21.5-1
thanks

I'm getting similar warnings from vim-gtk3 (GtkForm) and gnome-terminal 
(TerminalWindow), so I'm pretty sure this is a GTK3 bug, not specific to 
Emacs.


--
TH

Bug#836774: network-manager: Fails to connect to wifi, "Too many open files"

[Tony Houghton]

Package: network-manager
Version: 1.4.0-3
Severity: important

After a dist-upgrade network-manager will no longer connect to my wifi.
The logs say "Too many open files in system", but this doesn't seem
likely, because nothing else is broken (except for a minor GTK3 issue
which seems irrelevant). The connection works if I add it to
/etc/network/interfaces and use ifup. I'm attaching a log from
journalctl, because that seems much more useful than /var/log/daemon.log
as suggested on
. Their advice
about getting more info from wpa_supplicant doesn't apply to current
Debian either (adding -f... to the dbus file doesn't do anything), I
hope you've got enough in this log.

I found #832093, which looks like a similar issue at first, but I think
this is something different. But that mentions "opting out of
nm-wait-online" to avoid network issues holding up the boot sequence.
Please could you explain how I do that because, while I'm not a systemd
hater, I still don't know much about using it.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), 
(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_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages network-manager depends on:
ii  adduser3.115
ii  dbus   1.10.10-1
ii  init-system-helpers1.42
ii  libaudit1  1:2.6.6-1
ii  libbluetooth3  5.36-1+b2
ii  libc6  2.24-2
ii  libglib2.0-0   2.49.6-1
ii  libgnutls303.5.3-4
ii  libgudev-1.0-0 230-3
ii  libmm-glib01.6.0-1
ii  libndp01.6-1
ii  libnewt0.520.52.18-3
ii  libnl-3-2003.2.27-1
ii  libnm0 1.4.0-3
ii  libpam-systemd 231-5
ii  libpolkit-agent-1-00.105-16
ii  libpolkit-gobject-1-0  0.105-16
ii  libreadline6   6.3-8+b4
ii  libselinux12.5-3
ii  libsoup2.4-1   2.55.90-1
ii  libsystemd0231-5
ii  libteamdctl0   1.26-1
ii  libuuid1   2.28.1-1
ii  lsb-base   9.20160629
ii  policykit-10.105-16
ii  udev   231-5
ii  wpasupplicant  2.5-2+v2.4-2

Versions of packages network-manager recommends:
ii  crda 3.13-1+b1
ii  dnsmasq-base 2.76-4
ii  iptables 1.6.0-3
ii  iputils-arping   3:20150815-2
ii  isc-dhcp-client  4.3.4-1
pn  modemmanager 
ii  ppp  2.4.7-1+3

Versions of packages network-manager suggests:
pn  libteam-utils  

-- no debconf information

Bug#827768: RM: roxterm -- ROM; Upstream discontinued; has RC bug

[Tony Houghton]

On 27/07/16 07:56, Andrew Shadura wrote:


Tony, do you really think that the right thing to do? What am I supposed
to do now? What other users are? Are you serious?

I understand your frustration about GTK+, but that's not the reason to
abandon software lots of people use, that's unfair to its users. ROXTerm
has been the terminal of my choice for the last 8 years, and now I'm
supposed to look for something else, as I won't be able to install it
very soon. Okay, I get it, there's a bug. But — fsck that bug, I think
it can be overridden with the window manager, I guess (I haven't run
into it as I don't use GTK 3.20 yet), or at the end it could be fixed
even that's not trivial as you mentioned.

But abandoning it altogether?

You disappoint me :(


The geometry bug was just the biggest symptom. Like I said, I don't have 
the motivation to do it justice any more and the quality would slide. If 
it was such a vital project somebody would have tried to take it over or 
fork it or whatever. There are dozens of terminal emulators, and 
gnome-terminal has improved a lot since I first wrote ROXTerm. It does 
everything I want.


There are also loads of major Linux projects which aren't officially 
abandoned, but without vital work being done on them, like upgrading 
from GTK2 to 3 at all, making them useless or horrible to large numbers 
of users. I don't want that for ROXTerm.


--
TH

Bug#832364: kodi: Crashes on trying to play any TV recording

[Tony Houghton]

Package: kodi
Version: 16.1+dfsg1-1
Severity: normal

If I try to play any of my TV recordings, kodi crashes. It doesn't seem
to matter whether they're HD or SD. The recordings are made with
hts/tvheadend running on another PC with Ubuntu 16.04. Live TV works OK
with the same server, although HD can be a bit hit & miss.

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

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

Versions of packages kodi depends on:
ii  kodi-bin   16.1+dfsg1-1
ii  kodi-data  16.1+dfsg1-1

kodi recommends no packages.

kodi suggests no packages.

-- no debconf information
## Kodi CRASH LOG ###

 SYSTEM INFO 
 Date: Sun 24 Jul 18:11:51 BST 2016
 Kodi Options: 
 Arch: x86_64
 Kernel: Linux 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 (2016-07-18)
 Release: Debian GNU/Linux
## END SYSTEM INFO ##

### STACK TRACE #
=>  Core file: /home/tony/core (2016-07-24 18:11:50.956764090 +0100)
=
[New LWP 997]
[New LWP 958]
[New LWP 983]
[New LWP 965]
[New LWP 969]
[New LWP 985]
[New LWP 955]
[New LWP 977]
[New LWP 998]
[New LWP 966]
[New LWP 946]
[New LWP 999]
[New LWP 978]
[New LWP 980]
[New LWP 979]
[New LWP 981]
[New LWP 961]
[New LWP 956]
[New LWP 970]
[New LWP 957]
[New LWP 962]
[New LWP 963]
[New LWP 964]
[New LWP 968]
[New LWP 972]
[New LWP 973]
[New LWP 975]
[New LWP 976]
[New LWP 984]
[New LWP 967]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/x86_64-linux-gnu/kodi/kodi.bin'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7fc591cd81c8 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
[Current thread is 1 (Thread 0x7fc506ffd700 (LWP 997))]

Thread 30 (Thread 0x7fc55493b700 (LWP 967)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x0121032b in CThread::Sleep(unsigned int) ()
#2  0x0104b6bd in PVR::CPVRClients::Process() ()
#3  0x012103ff in CThread::Action() ()
#4  0x012106bf in CThread::staticThread(void*) ()
#5  0x7fc59ab5a464 in start_thread (arg=0x7fc55493b700) at 
pthread_create.c:333
#6  0x7fc591d8c30d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 29 (Thread 0x7fc507fff700 (LWP 984)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x0121032b in CThread::Sleep(unsigned int) ()
#2  0x00a93988 in EPG::CEpgContainer::Process() ()
#3  0x012103ff in CThread::Action() ()
#4  0x012106bf in CThread::staticThread(void*) ()
#5  0x7fc59ab5a464 in start_thread (arg=0x7fc507fff700) at 
pthread_create.c:333
#6  0x7fc591d8c30d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 28 (Thread 0x7fc51700 (LWP 976)):
#0  0x7fc591d84f73 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x00e95662 in NPT_BsdSocketFd::WaitForCondition(bool, bool, bool, 
int) ()
#2  0x00e9752d in 
NPT_BsdTcpServerSocket::WaitForNewClient(NPT_Socket*&, int, unsigned int) ()
#3  0x011ce945 in PLT_HttpListenTask::DoRun() ()
#4  0x00eb46d5 in PLT_ThreadTask::Run() ()
#5  0x00e9a973 in NPT_PosixThread::EntryPoint(void*) ()
#6  0x7fc59ab5a464 in start_thread (arg=0x7fc51700) at 
pthread_create.c:333
#7  0x7fc591d8c30d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 27 (Thread 0x7fc534b7f700 (LWP 975)):
#0  0x7fc591d84f73 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x00e95662 in NPT_BsdSocketFd::WaitForCondition(bool, bool, bool, 
int) ()
#2  0x00e9607d in NPT_BsdUdpSocket::Receive(NPT_DataBuffer&, 
NPT_SocketAddress*) ()
#3  0x011fc6bc in PLT_InputDatagramStream::Read(void*, unsigned int, 
unsigned int*) ()
#4  0x00ef146b in NPT_BufferedInputStream::FillBuffer() ()
#5  0x00ef125a in NPT_BufferedInputStream::ReadLine(char*, unsigned 
int, unsigned int*, bool) ()
#6  0x00ef168a in NPT_BufferedInputStream::ReadLine(NPT_String&, 
unsigned int, bool) ()
#7  0x00ec143f in NPT_HttpRequest::Parse(NPT_BufferedInputStream&, 
NPT_SocketAddress const*, NPT_HttpRequest*&) ()
#8  0x011cfc36 in 
PLT_HttpServerSocketTask::Read(NPT_Reference&, 
NPT_HttpRequest*&, NPT_HttpRequestContext*) ()
#9  0x011cf6ad in PLT_HttpServerSocketTask::DoRun() ()
#10 0x00eb46d5 in PLT_ThreadTask::Run() ()
#11 0x00e9a973 in NPT_PosixThread::EntryPoint(void*) ()

Bug#820627: ttf-mscorefonts-installer: Does not update font cache

[Tony Houghton]

Package: ttf-mscorefonts-installer
Version: 3.6
Followup-For: Bug #820627

Same problem here, on a system I installed earlier today.

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

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

Versions of packages ttf-mscorefonts-installer depends on:
ii  cabextract 1.6-1
ii  debconf [debconf-2.0]  1.5.59
ii  wget   1.18-2
ii  xfonts-utils   1:7.7+3

Versions of packages ttf-mscorefonts-installer recommends:
ii  fonts-liberation  1.07.4-1

ttf-mscorefonts-installer suggests no packages.

-- debconf information:
  msttcorefonts/baddldir:
  msttcorefonts/http_proxy:
  msttcorefonts/dldir:
  msttcorefonts/savedir:
  msttcorefonts/dlurl:

Bug#829188: SEGVs too frequently (~every other day)

[Tony Houghton]

Package: icedove
Version: 1:45.2~b1-1
Followup-For: Bug #829188

I've also been experiencing frequent crashes with version 4x. I'm not
sure, but it seems to occur just after it's opened and displayed a
message. One particular message has just triggered a crash twice in a
row, but not every time I open it; it's multipart html+text but with no
images.

I recently got around to hacking up a start-up wrapper and the desktop
file to enable core dumps. It's quite a big file so I've uploaded it to
.

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

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

Versions of packages icedove depends on:
ii  debianutils   4.8
ii  fontconfig2.11.0-6.4
ii  libasound21.1.1-2
ii  libatk1.0-0   2.20.0-1
ii  libc6 2.22-13
ii  libcairo2 1.14.6-1+b1
ii  libdbus-1-3   1.10.8-1
ii  libdbus-glib-1-2  0.106-1
ii  libevent-2.0-52.0.21-stable-2+b1
ii  libffi6   3.2.1-4
ii  libfontconfig12.11.0-6.4
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:6.1.1-8
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.48.1-1
ii  libgtk2.0-0   2.24.30-2
ii  libhunspell-1.4-0 1.4.1-2
ii  libicu55  55.1-7
ii  libnspr4  2:4.12-2
ii  libnss3   2:3.23-2
ii  libpango-1.0-01.40.1-1
ii  libpangocairo-1.0-0   1.40.1-1
ii  libpangoft2-1.0-0 1.40.1-1
ii  libpixman-1-0 0.33.6-1
ii  libsqlite3-0  3.13.0-1
ii  libstartup-notification0  0.12-4
ii  libstdc++66.1.1-8
ii  libvpx3   1.5.0-3
ii  libx11-6  2:1.6.3-1
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.2-1
ii  libxrender1   1:0.9.9-2
ii  libxt61:1.1.5-1
ii  psmisc22.21-2.1+b1
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages icedove recommends:
ii  hunspell-en-gb [hunspell-dictionary]  1:5.1.3-2
ii  hunspell-en-us [hunspell-dictionary]  20070829-6
ii  iceowl-extension  1:45.2~b1-1

Versions of packages icedove suggests:
pn  fonts-lyx 
ii  libgssapi-krb5-2  1.14.2+dfsg-1

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/applications/icedove.desktop (from icedove 
package)

Bug#827768: RM: roxterm -- ROM; Upstream discontinued; has RC bug

[Tony Houghton]

Package: ftp.debian.org
Severity: normal

I am the upstream developer as well as maintainer of this package. For
some time I have lacked the time and motivation to maintain and develop
it effectively, and thought about giving it up. GTK 3.20 has caused a
nasty bug (#821357) which would be very difficult to fix, so I've
decided I should commit to discontinuing roxterm now.

Bug#821744: icedove: Missing scrollbars

[Tony Houghton]

Package: icedove
Version: 1:45.0~b4-2
Severity: normal

This experimental version appears to be using its own theme instead of
the system theme, and the scrollbars aren't being drawn properly. Only
the grey background appears; the draggable bar is invisible, but it
appears to behave as if it is present if I click and drag etc.

FWIW I'm using a Macbook Retina (hidpi display with Intel Iris
graphics).

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

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

Versions of packages icedove depends on:
ii  debianutils   4.7
ii  fontconfig2.11.0-6.4
ii  libasound21.1.0-1
ii  libatk1.0-0   2.20.0-1
ii  libc6 2.22-6
ii  libcairo-gobject2 1.14.6-1+b1
ii  libcairo2 1.14.6-1+b1
ii  libdbus-1-3   1.10.8-1
ii  libdbus-glib-1-2  0.106-1
ii  libevent-2.0-52.0.21-stable-2+b1
ii  libffi6   3.2.1-4
ii  libfontconfig12.11.0-6.4
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:5.3.1-14
ii  libgdk-pixbuf2.0-02.32.3-2
ii  libglib2.0-0  2.48.0-1
ii  libgtk-3-03.20.3-1
ii  libhunspell-1.3-0 1.3.3-4
ii  libicu55  55.1-7
ii  libnspr4  2:4.12-2
ii  libnss3   2:3.23-2
ii  libpango-1.0-01.38.1-1
ii  libpangocairo-1.0-0   1.38.1-1
ii  libpangoft2-1.0-0 1.38.1-1
ii  libpixman-1-0 0.33.6-1
ii  libsqlite3-0  3.11.1-1
ii  libstartup-notification0  0.12-4
ii  libstdc++65.3.1-14
ii  libvpx3   1.5.0-2
ii  libx11-6  2:1.6.3-1
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxrender1   1:0.9.9-2
ii  libxt61:1.1.5-1
ii  psmisc22.21-2.1+b1
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages icedove recommends:
ii  hunspell-en-gb [hunspell-dictionary]  1:5.1.2-1
ii  hunspell-en-us [hunspell-dictionary]  20070829-6
ii  iceowl-extension  1:45.0~b4-2

Versions of packages icedove suggests:
pn  fonts-lyx 
ii  libgssapi-krb5-2  1.13.2+dfsg-5

-- no debconf information

Bug#820627: ttf-mscorefonts-installer: Does not update font cache

[Tony Houghton]

Package: ttf-mscorefonts-installer
Version: 3.6
Severity: normal

After installing this package the MS fonts were not available to
applications as expected, but they were present in
/usr/share/fonts/truetype/msttcorefonts. I had to run
`fc-cache /usr/share/fonts/truetype/msttcorefonts` manually to make them
available.

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

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

Versions of packages ttf-mscorefonts-installer depends on:
ii  cabextract 1.6-1
ii  debconf [debconf-2.0]  1.5.59
ii  wget   1.17.1-1+b1
ii  xfonts-utils   1:7.7+3

Versions of packages ttf-mscorefonts-installer recommends:
ii  fonts-liberation  1.07.4-1

ttf-mscorefonts-installer suggests no packages.

-- debconf information:
  msttcorefonts/dlurl:
  msttcorefonts/savedir:
  msttcorefonts/baddldir:
  msttcorefonts/http_proxy:
  msttcorefonts/dldir:

Bug#818914: adwaita-icon-theme: Missing icon for bluetooth speaker

[Tony Houghton]

Package: adwaita-icon-theme
Version: 3.18.0-2
Severity: normal

Both GNOME Settings and pavucontrol show the "missing" icon for my
bluetooth speaker. I added a little logging to pavucontrol and it
appears the icon name it requests is "audio-handsfree-bluetooth".

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

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

Versions of packages adwaita-icon-theme depends on:
ii  hicolor-icon-theme  0.13-1
ii  libgtk-3-bin3.18.9-1
ii  librsvg2-common 2.40.13-3

adwaita-icon-theme recommends no packages.

adwaita-icon-theme suggests no packages.

-- no debconf information

Bug#818913: pulseaudio: Have to restart pulseaudio after (re)connecting bluetooth speaker

[Tony Houghton]

Package: pulseaudio
Version: 8.0-1
Severity: normal

I have a Multitech The Block 4.0 bluetooth speaker. I've followed
, including adding
'load-module module-switch-on-connect' to /etc/pulse/default.pa and it
basically now works.

However, if I turn the speaker off and then back on later, I have to
restart pulseaudio (killall pulseaudio) to be able to use it. It shows
up in pavucontrol's Configuration tab, but its Profile is "Off" there.
If I change it (to A2DP Sink) it still doesnt show up in Output Devices,
and if I reload pavucontrol I find the profile has changed back to Off.
After pulseaudio is killed and restarted the speaker chimes (presumably
to indicate the laptop has just connected) and becomes available as an
output device.

-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


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

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

Versions of packages pulseaudio depends on:
ii  adduser   3.114
ii  libasound21.1.0-1
ii  libasound2-plugins1.1.0-1
ii  libc6 2.22-3
ii  libcap2   1:2.24-12
ii  libdbus-1-3   1.10.8-1
ii  libfftw3-single3  3.3.4-2+b1
ii  libgcc1   1:5.3.1-11
ii  libice6   2:1.0.9-1+b1
ii  libltdl7  2.4.6-0.1
ii  liborc-0.4-0  1:0.4.25-1
ii  libpulse0 8.0-1
ii  libsm62:1.2.2-1+b1
ii  libsndfile1   1.0.25-10
ii  libsoxr0  0.1.2-1
ii  libspeexdsp1  1.2~rc1.2-1
ii  libstdc++65.3.1-11
ii  libsystemd0   229-2
ii  libtdb1   1.3.8-2
ii  libudev1  229-2
ii  libwebrtc-audio-processing-0  0.1-3
ii  libx11-6  2:1.6.3-1
ii  libx11-xcb1   2:1.6.3-1
ii  libxcb1   1.11.1-1
ii  libxtst6  2:1.2.2-1+b1
ii  lsb-base  9.20160110
ii  pulseaudio-utils  8.0-1
ii  udev  229-2

Versions of packages pulseaudio recommends:
ii  pulseaudio-module-x11  8.0-1
ii  rtkit  0.11-4

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  3.0-3+b2
pn  pavumeter

-- Configuration Files:
/etc/pulse/default.pa changed:
.nofail
.fail
load-module module-device-restore
load-module module-stream-restore
load-module module-card-restore
load-module module-augment-properties
load-module module-switch-on-port-available
.ifexists module-udev-detect.so
load-module module-udev-detect
.else
load-module module-detect
.endif
.ifexists module-jackdbus-detect.so
.nofail
load-module module-jackdbus-detect channels=2
.fail
.endif
.ifexists module-bluetooth-policy.so
load-module module-bluetooth-policy
.endif
.ifexists module-bluetooth-discover.so
load-module module-bluetooth-discover
.endif
.ifexists module-esound-protocol-unix.so
load-module module-esound-protocol-unix
.endif
load-module module-native-protocol-unix
.ifexists module-gconf.so
.nofail
load-module module-gconf
.fail
.endif
load-module module-default-device-restore
load-module module-rescue-streams
load-module module-always-sink
load-module module-intended-roles
load-module module-suspend-on-idle
.ifexists module-console-kit.so
load-module module-console-kit
.endif
.ifexists module-systemd-login.so
load-module module-systemd-login
.endif
load-module module-position-event-sounds
load-module module-role-cork
load-module module-filter-heuristics
load-module module-filter-apply
load-module module-switch-on-connect


-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-so

Bug#782688: bluetooth speaker is not recognized in jessie

[Tony Houghton]

Package: pulseaudio
Followup-For: Bug #782688

Does this help?


# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa

; log-target = auto
; log-level = notice
; log-meta = no
; log-time = no
; log-backtrace = 0

; resample-method = speex-float-1
; enable-remixing = yes
; enable-lfe-remixing = yes
; lfe-crossover-freq = 120

; flat-volumes = yes

; rlimit-fsize = -1
; rlimit-data = -1
; rlimit-stack = -1
; rlimit-core = -1
; rlimit-as = -1
; rlimit-rss = -1
; rlimit-nproc = -1
; rlimit-nofile = 256
; rlimit-memlock = -1
; rlimit-locks = -1
; rlimit-sigpending = -1
; rlimit-msgqueue = -1
; rlimit-nice = 31
; rlimit-rtprio = 9
; rlimit-rttime = 20

; default-sample-format = s16le
; default-sample-rate = 44100
; alternate-sample-rate = 48000
; default-sample-channels = 2
; default-channel-map = front-left,front-right

; default-fragments = 4
; default-fragment-size-msec = 25

; enable-deferred-volume = yes
; deferred-volume-safety-margin-usec = 8000
; deferred-volume-extra-delay-usec = 0
#!/usr/bin/pulseaudio -nF
#
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

# This startup script is used only if PulseAudio is started per-user
# (i.e. not in system mode)

.nofail

### Load something into the sample cache
#load-sample-lazy x11-bell /usr/share/sounds/freedesktop/stereo/bell.oga
#load-sample-lazy pulse-hotplug 
/usr/share/sounds/freedesktop/stereo/device-added.oga
#load-sample-lazy pulse-coldplug 
/usr/share/sounds/freedesktop/stereo/device-added.oga
#load-sample-lazy pulse-access /usr/share/sounds/freedesktop/stereo/message.oga

.fail

### Automatically restore the volume of streams and devices
load-module module-device-restore
load-module module-stream-restore
load-module module-card-restore

### Automatically augment property information

Bug#816472: roxterm: Menu is still triggered by menu key

[Tony Houghton]

On 03/03/16 07:39, gustavo panizzo wrote:


I didn't mean the F10 key or Shift+F10 key, I meant the menu key, the
one between alt and control (on my keyboard)


Oh, that. I forgot about it because I'm currently using a Mac, which 
doesn't have one.



Maybe I should report this bug upstream as it is a limitation on the
roxterm code not the packaging


Here is fine, I'm the sole person responsible for both, and I prefer 
Debian's bug tracking anyway. I'm not sure if this is really a bug 
though. I thought the intention for that key was that it was a 
desktop-wide GUI menu key, and as far as console applications are 
concerned it doesn't exist. Do you know some applications where it does 
something useful (by default - not just because xterm or something 
passes the even through and a user can configure it to do something)?

Bug#816472: roxterm: Menu is still triggered by menu key

[Tony Houghton]

On 02/03/16 04:16, gustavo panizzo wrote:


I've disabled menu access key, but when I press Menu key the menu is
opened


It seems to be working correctly for me. With the "disable menu access 
key" option unchecked F10 opens the File menu if the menu bar is 
enabled, but sends characters to the terminal if the menu bar is hidden. 
Shift-F10 opens the popup-menu whether or not the menu bar is enabled, 
but this also sends characters to the terminal instead if I check the 
"disable menu access key" option.

Bug#651589: iceweasel: Iceweasel has no GTK3

[Tony Houghton]

On Fri, 4 Dec 2015 19:38:31 +0900 Mike Hommey  wrote:


Upstream is not going to release with Gtk+3 support on until 45.


GTK+3 support has been available upstream for some time (since 38?). 
It's considered stable and was only disabled by default in case it 
caused upgrade difficulties for users who didn't have GTK+3 installed 
yet. These difficulties shouldn't exist for Debian, and there are 
tangible benefits in GTK+3 such as support for hidpi (and Wayland?). So 
please could the GTK+3 support be enabled now instead of waiting for 45.

Bug#810536: RFS: roxterm/3.3.2-1

[Tony Houghton]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for the latest version of my package "roxterm"

 * Package name: roxterm
   Version : 3.3.2-1
   Upstream Author : Tony Houghton 
 * URL : http://roxterm.sourceforge.net
 * License : GPL2+
   Section : x11

It builds these binary packages:

 roxterm  - Multi-tabbed GTK+/VTE terminal emulator - binaries
 roxterm-data - Multi-tabbed GTK+/VTE terminal emulator - data files
 roxterm-dbg  - Debugging symbols for roxterm
 roxterm-gtk2 - Transitional package to upgrade roxterm-gtk2 to
roxterm
 roxterm-gtk2-dbg - Transitional package to upgrade roxterm-gtk2-dbg to
roxterm-dbg
 roxterm-gtk3 - Transitional package to upgrade roxterm-gtk3 to
roxterm
 roxterm-gtk3-dbg - Transitional package to upgrade roxterm-gtk3-dbg to
roxterm-dbg

To access further information about this package,
please visit the following URL:

  http://mentors.debian.net/package/roxterm

Alternatively, one can download the package with dget using this command:

dget -x
http://mentors.debian.net/debian/pool/main/r/roxterm/roxterm_3.3.2-1.dsc

More information about roxterm can be obtained from
http://roxterm.sourceforge.net

Changes since the last upload:

roxterm (3.3.2-1) unstable; urgency=medium

  * Removed debian/dirs to prevent creation of now empty 
/usr/share/pixmaps.

  * Build-Depends avoids buggy version of gettext (Closes: #809570).
  * debian/rules: Use --enable-nls instead of deprecated 
--enable-translations.

  * New upstream release:
+ Fixed ssh port number in config ui (upstream #120).
+ Fixed configure --disable-nls.
+ Update New Window/Tab With Profile submenus when profiles change
  (upstream #121).
+ Fade text and background colour labels along with buttons
  (Closes: #810016).
+ Documented shortcuts translation problem described by #809719.

 -- Tony Houghton   Sat, 09 Jan 2016 14:00:02 +

Bug #809570 is actually due to a gettext bug (which is now fixed), but I
decided to keep a separate ticket open for roxterm because I changed its
Build-Depends to avoid the buggy version of gettext.

Bug#809719: roxterm: Most shortcuts are ineffective

[Tony Houghton]

On 05/01/16 15:23, François Gannaz wrote:
> Le 2016-01-05, Tony Houghton  a écrit :
>>
>> Can you try building replacement debian packages to test? You should
>> just be able to run debuild -b in the git/source directory.
>
> I had to install itstool and po4a. The resulting package had no
> keyboard shortcuts.

Strange.

> The new roxterm executable was the same size as the official one,
> though the MD5 sum was different. The locally-compiled (outside
> debuild) file was 43% larger.

The difference in size is probably because the debian build strips out 
the debugging symbols and puts them in a separate package (roxterm-dbg).

I think the most likely reason for the self-build working and the
debian build not is because the latter sets PREFIX to /usr. Without
being set eg by debian/rules it defaults to /usr/local, so I would have
expected your self-build to fail to find some files. Does it appear all
in English instead of partially French (the French translation is only
71% complete)?

There's also a script called AppRun in the source tree. It's designed
to run roxterm directly from its build directory and point it to its 
default resource files supplied with the source. It would be
interesting to know whether that works.

I've just had an idea. The shortcuts might not be matching, because the 
menu strings have been translated to French so they don't match the 
strings in the Shortcuts/Default file. Do they work if you edit your 
Shortcuts file to translate the strings to French so they match the 
translated menus?

>>> The keypad decimal bug is not affected by this, so it should go in
>>> another bug report.
>>
>> Could you test that in gnome-terminal instead of xfce4-terminal?  I
>> think xfce4 is still based on GTK+2.0 with a much older version of
>> vte. Also try other text fields from gnome-terminal, roxterm and/or
>> other GTK+3.0-based programs.
>
> To sum it up:
>
> xev:.
> xfce4-terminal: . (GTK+2, libvte 0.28)
> gnome-terminal: ,
> roxterm 3.3.1:  , (libvte 0.42)
>
> Unless you suggest something else, I suppose I shall open a new ticket
> in libgtk-3-0.

Check some other text entry widgets too to test whether it's all of
GTK3 or just VTE.

PS Make sure you don't install gettext 0.19.7-1 because bug #809846 
prevents roxterm from being built with translations.

Bug#810016: Roxterm does not allow to set the background color anymore

[Tony Houghton]

On 05/01/16 16:09, Douglas A. Augusto wrote:


Since I've upgraded to roxterm version 3.3.1 (from 2.9.5), I can't anymore set
the background color. It seems to simply ignore the value of the background
color variable in the color scheme file (background=#...). Also, trying to set
it using the menus doesn't work as well (Preferences/Edit Current Colour
Scheme/Background colour).


If the "Get text and background colours from palette" option is checked 
in the colour scheme the text and background colour widgets are disabled 
and the colours are taken from the first and last widgets in the upper 
palette row. It seems that this option is stuck on, so I need to fix 
that. And it's really hard to see that the colour widgets are faded in 
the default theme so I suppose I'd better make it fade the labels too.

Bug#809719: roxterm: Most shortcuts are ineffective

[Tony Houghton]

On 05/01/16 10:43, François Gannaz wrote:

On my laptop, I compiled roxterm from the source, using the git tag 3.3.1.
I wanted to bisect the bug, but shortcuts worked flawlessly with this
self-compiled roxterm. I followed the default process, didn't set any
configuration option, and simply run `./build/roxterm --separate`.

If I copy this new roxterm binary to my desktop computer (both are
Testing Debian amd64) in /usr/bin/, shortcuts are also fixed.


Can you try building replacement debian packages to test? You should
just be able to run debuild -b in the git/source directory.


The keypad decimal bug is not affected by this, so it should go in
another bug report.


Could you test that in gnome-terminal instead of xfce4-terminal?  I
think xfce4 is still based on GTK+2.0 with a much older version of vte.
Also try other text fields from gnome-terminal, roxterm and/or other
GTK+3.0-based programs.

Bug#809570: roxterm: FTBFS: MaitchNotFoundError: Resource '[..]/debian/build/po/glade.pot'

[Tony Houghton]

block 809570 809846
thanks

It looks like xgettext's support for glade has broken. If it doesn't get 
fixed soon I can probably work around it by using po4a to generate 
glade.pot.

Bug#809846: gettext: Does not recognise glade

[Tony Houghton]

Package: gettext
Version: 0.19.7-1
Severity: normal

Dear Maintainer,

The current version of xgettext seems to be unable to process glade
files, warning that it doesn't recognise the extension '.glade' on the
input file, and ignoring -L Glade and --language=Glade options. No
output .pot file is produced, but it returns a 0 exit code. For example:

$ /usr/bin/xgettext --package-name=roxterm -L Glade -o 
/home/tony/Dev/roxterm/build/po/glade.pot ../src/roxterm-config.glade
/usr/bin/xgettext: warning: file '../src/roxterm-config.glade' extension 
'glade' is unknown; will try C
.../src/roxterm-config.glade:81: warning: unterminated character constant
.../src/roxterm-config.glade:208: warning: unterminated character constant
.../src/roxterm-config.glade:209: warning: unterminated character constant
.../src/roxterm-config.glade:1466: warning: unterminated character constant
.../src/roxterm-config.glade:1467: warning: unterminated character constant
.../src/roxterm-config.glade:1729: warning: unterminated character constant
.../src/roxterm-config.glade:1987: warning: unterminated character constant
.../src/roxterm-config.glade:1988: warning: unterminated character constant
.../src/roxterm-config.glade:2212: warning: unterminated character constant
.../src/roxterm-config.glade:2218: warning: unterminated character constant
.../src/roxterm-config.glade:2466: warning: unterminated character constant
.../src/roxterm-config.glade:2485: warning: unterminated character constant
.../src/roxterm-config.glade:3433: warning: unterminated character constant
.../src/roxterm-config.glade:3434: warning: unterminated character constant
.../src/roxterm-config.glade:4057: warning: unterminated character constant

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

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

Versions of packages gettext depends on:
ii  dpkg   1.18.4
ii  gettext-base   0.19.7-1
ii  install-info   6.0.0.dfsg.1-4
ii  libc6  2.21-6
ii  libcroco3  0.6.11-1
ii  libglib2.0-0   2.46.2-3
ii  libgomp1   5.3.1-4
ii  libncurses56.0+20151024-2
ii  libtinfo5  6.0+20151024-2
ii  libunistring0  0.9.3-5.2+b1
ii  libxml22.9.3+dfsg1-1

Versions of packages gettext recommends:
ii  wget  1.17.1-1

Versions of packages gettext suggests:
ii  autopoint 0.19.7-1
pn  gettext-doc   
pn  libasprintf-dev   
pn  libgettextpo-dev  

-- no debconf information

Bug#809719: roxterm: Most shortcuts are ineffective

[Tony Houghton]

tags 809719 - moreinfo
thanks

It looks like there's a problem in roxterm's locale handling, maybe 
specifically fr_FR.utf8. The reporter of #804144, which looks related, 
has the same locale.

Bug#804144: roxterm: Default copy paste shortcuts do not work anymore

[Tony Houghton]

tags 804144 + unreproducible moreinfo
thanks

On Thu, 05 Nov 2015 13:02:05 +0100 Raphael Rigo


after upgrading roxterm to 3.2.1 from 3.1.5, the copy paste shortcuts
(Shift-Ctrl-C and Shift-Ctrl-V) that used to work are now non
functionnal.
It looks like "Shift-Ctrl-V" is now interpreted as Ctrl-C.


This looks related to 
. Please can 
you check your config. If a file for your config exists in 
~/.config/roxterm.sourceforge.net/Shortcuts please post it here and see 
if removing it restores correct behaviour.

Bug#809719: roxterm: Most shortcuts are ineffective

[Tony Houghton]

tags 809719 + unreproducible moreinfo
thanks

On 03/01/16 11:13, François Gannaz wrote:


After updating my distribution, most shortcuts defined in the default
profile of roxterm are ineffective. The same behaviour occurs on my
laptop, after updating it to the latest Stretch.

The configuration file for shortcuts is unchanged:
`~/.config/roxterm.sourceforge.net/Shortcuts/Default`


Please post that file here here. It's possible there might have been a 
format change over the years, or at least I can try the config here and 
hopefully be able to reproduce the problem.


If the shortcuts are unchanged you shouldn't need that config file and 
it will use the one from /usr/share/roxterm/Config. Does removing the 
one in ~/.config/ fix it? If so, does editing the shortcuts break it again?

Bug#806898: RFS: roxterm/3.3.1-1

[Tony Houghton]

On 08/12/15 14:05, Mattia Rizzolo wrote:

On Tue, Dec 08, 2015 at 01:59:56PM +, Tony Houghton wrote:

I must remember to change the level in my lintian options as well as fixing


I believe (because I have a pbuilder hook that runs lintian for me, I
rarely run it manyally) just dumping the following in ~/.lintianrc is
enough:
info=yes
display-info=yes
display-experimental=yes
pedantic=yes
show-overrides=no
color=always


I put in display-info=yes already, but I might as well include all of those.


this specific problem. It looks like a leftover from the deprecated debian
menu entry, but for some reason I can't find it in debian/rules or the
upstream build system.


just remove debian/dirs :)


I didn't spot that when I grepped the debian directory!

Bug#806898: RFS: roxterm/3.3.1-1

[Tony Houghton]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for the latest version of my package "roxterm"

 * Package name: roxterm
   Version : 3.3.1-1
   Upstream Author : Tony Houghton 
 * URL : http://roxterm.sourceforge.net
 * License : GPL2+
   Section : x11

It builds these binary packages:

 roxterm  - Multi-tabbed GTK+/VTE terminal emulator - binaries
 roxterm-data - Multi-tabbed GTK+/VTE terminal emulator - data files
 roxterm-dbg  - Debugging symbols for roxterm
 roxterm-gtk2 - Transitional package to upgrade roxterm-gtk2 to
roxterm
 roxterm-gtk2-dbg - Transitional package to upgrade roxterm-gtk2-dbg to
roxterm-dbg
 roxterm-gtk3 - Transitional package to upgrade roxterm-gtk3 to
roxterm
 roxterm-gtk3-dbg - Transitional package to upgrade roxterm-gtk3-dbg to
roxterm-dbg

To access further information about this package,
please visit the following URL:

  http://mentors.debian.net/package/roxterm

Alternatively, one can download the package with dget using this command:

dget -x
http://mentors.debian.net/debian/pool/main/r/roxterm/roxterm_3.3.1-1.dsc

More information about roxterm can be obtained from
http://roxterm.sourceforge.net

Changes since the last upload:

Bug#803395: RFS: roxterm/3.2.1-1

[Tony Houghton]

Package: sponsorship-requests
Severity: normal

Dear Vicent and/or other potential sponsors,

I am looking for a sponsor for the latest version of my package "roxterm"

 * Package name: roxterm
   Version : 3.2.1-1
   Upstream Author : Tony Houghton 
 * URL : http://roxterm.sourceforge.net
 * License : GPL2+
   Section : x11

It builds these binary packages:

 roxterm  - Multi-tabbed GTK+/VTE terminal emulator - binaries
 roxterm-data - Multi-tabbed GTK+/VTE terminal emulator - data files
 roxterm-dbg  - Debugging symbols for roxterm
 roxterm-gtk2 - Transitional package to upgrade roxterm-gtk2 to
roxterm
 roxterm-gtk2-dbg - Transitional package to upgrade roxterm-gtk2-dbg to
roxterm-dbg
 roxterm-gtk3 - Transitional package to upgrade roxterm-gtk3 to
roxterm
 roxterm-gtk3-dbg - Transitional package to upgrade roxterm-gtk3-dbg to
roxterm-dbg

To access further information about this package,
please visit the following URL:

  http://mentors.debian.net/package/roxterm

Alternatively, one can download the package with dget using this command:

dget -x
http://mentors.debian.net/debian/pool/main/r/roxterm/roxterm_3.2.1-1.dsc

More information about roxterm can be obtained from
http://roxterm.sourceforge.net

Changes since the last upload:

roxterm (3.2.1-1) unstable; urgency=medium

  * New upstream version:
+ Use vte 0.40's new word char API (Closes: #798656).
  * Don't use deprecated debian menu system.

 -- Tony Houghton   Thu, 29 Oct 2015 13:12:11 +

Bug#803319: chromium: GPU accelerated video decode failure

[Tony Houghton]

Package: chromium
Version: 47.0.2526.16-1
Severity: normal

GPU accelerated decode for HTML5 video appears to be failing and
chromium is falling back to CPU, judging by the high CPU usage.  It
produces the following output on startup, with no further messages when
attempting to play a video. I've installed chromium-dbg but it didn't
affect the backtrace. Please advise if there's a way I can convert these
addresses to function names and source location etc.

[2069:2069:1028/175848:FATAL:sandbox_seccomp_bpf_linux.cc(203)] Check failed: 
policy->PreSandboxHook(). 
#0 0x55651de392de 
#1 0x55651de4eae0 
#2 0x55652172f538 
#3 0x55652172e88c 
#4 0x55652172e161 
#5 0x5565215f658c 
#6 0x5565215f5c09 
#7 0x55651de0c4ef 
#8 0x55651de0b610 
#9 0x55651d96e088 ChromeMain
#10 0x7f7794de7b45 __libc_start_main
#11 0x55651d96df2f 

Received signal 6
#0 0x55651de38db8 
#1 0x7f779517e8d0 
#2 0x7f7794dfb107 gsignal
#3 0x7f7794dfc4e8 abort
#4 0x55651de382a2 
#5 0x55651de4ed77 
#6 0x55652172f538 
#7 0x55652172e88c 
#8 0x55652172e161 
#9 0x5565215f658c 
#10 0x5565215f5c09 
#11 0x55651de0c4ef 
#12 0x55651de0b610 
#13 0x55651d96e088 ChromeMain
#14 0x7f7794de7b45 __libc_start_main
#15 0x55651d96df2f 
  r8: d567a29f3fa0  r9: d567a29f3f90 r10: 0008 r11: 
0202
 r12: 7ffd8239f678 r13: 5565244d0ef0 r14: 7ffd8239f688 r15: 
7f779591b260
  di: 0815  si: 0815  bp: 7ffd8239f678  bx: 

  dx: 0006  ax:   cx: 7f7794dfb107  sp: 
7ffd8239f0a8
  ip: 7f7794dfb107 efl: 0202 cgf: 635f0033 erf: 

 trp:  msk:  cr2: 
[end of stack trace]
[2019:2047:1028/175848:ERROR:browser_gpu_channel_host_factory.cc(132)] Failed 
to launch GPU process.

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

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

Versions of packages chromium depends on:
ii  libasound21.0.29-1
ii  libatk1.0-0   2.18.0-1
ii  libavcodec-ffmpeg56   7:2.8.1-1
ii  libavformat-ffmpeg56  7:2.8.1-1
ii  libavutil-ffmpeg547:2.8.1-1
ii  libc6 2.19-22
ii  libcairo2 1.14.2-2
ii  libcups2  2.1.0-4
ii  libdbus-1-3   1.10.0-3
ii  libexpat1 2.1.0-7
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.6-2
ii  libgcc1   1:5.2.1-22
ii  libgdk-pixbuf2.0-02.32.1-1
ii  libglib2.0-0  2.46.1-1
ii  libgnome-keyring0 3.12.0-1+b1
ii  libgtk2.0-0   2.24.28-1
ii  libjpeg62-turbo   1:1.4.1-2
ii  libnspr4  2:4.10.9-2
ii  libnss3   2:3.20-1
ii  libpango-1.0-01.38.1-1
ii  libpangocairo-1.0-0   1.38.1-1
ii  libpci3   1:3.3.1-1
ii  libspeechd2   0.8-7
ii  libsrtp1  1.5.2~dfsg-1
ii  libstdc++65.2.1-22
ii  libx11-6  2:1.6.3-1
ii  libxcomposite11:0.4.4-1
ii  libxcursor1   1:1.1.14-1+b1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxi62:1.7.5-1
ii  libxml2   2.9.2+zdfsg1-4
ii  libxrandr22:1.5.0-1
ii  libxrender1   1:0.9.8-1+b1
ii  libxslt1.11.1.28-2+b2
ii  libxss1   1:1.2.2-1
ii  libxtst6  2:1.2.2-1+b1
ii  x11-utils 7.7+3
ii  xdg-utils 1.1.1-1

chromium recommends no packages.

Versions of packages chromium suggests:
ii  chromium-l10n  47.0.2526.16-1

-- no debconf information

Bug#799802: [roxterm] Dodgy filename locks up roxterm during rsync (100% CPU)

[Tony Houghton]

reassign 799802 libvte-2.91-0
thanks

On 22/09/15 20:31, OmegaPhil wrote:


While it doesn't recreate the freeze, the following test does stall
output to the terminal until you SIGINT it:


[Snip]


XFCE4's Terminal has no problems echoing this.

Is this a bug for you? If not I'll just fix the directories and move on.


I can reproduce the symptoms in gnome-terminal too, so I think it's a 
vte bug. The reason XFCE4 is OK with it is probably because it uses GTK2 
and the corresponding older generation of vte.

Bug#798656: roxterm: Double clicking on URL doesn't select URL anymore

[Tony Houghton]

On 11/09/15 15:18, Raphael Rigo wrote:


after upgrading to the current version from version 2.9, the behaviour
of double clicking on URL changed : it's not longer selecting the whole
URL.
For example, a double click on https://www.debian.org would select only
//www.debian.org. Changing the option for "select by word characters" to
include ':' doesn't fix it.


The old function for dealing with word characters was removed from vte, 
in version 0.36 I think. I thought it was being reinstated (in 0.38?) 
and tried to handle this without having to recompile (ignoring the 
option when the function was missing), but it seems in 0.40 they've 
replaced it with a slightly different function, so I'll have to release 
a new version of roxterm to fix this.

Bug#796138: [roxterm] Setting up multi-tab terminal 'sessions' breaks with GTK3 roxterm - --tab call blocks?

[Tony Houghton]

On 20/08/15 20:32, OmegaPhil wrote:


==

roxterm --fork --replace tab -n "Bash 2 - %s" && roxterm --tab -n
"Editing 1 - %s"

==

The terminal window quickly appears and disappears. I can see the Bash 2
tab is being made, but I can't quite make out if the Editing 1 tab is.
Nothing is output on stdout/err.

Does that happen for you?


No, I get one window with 2 tabs as expected, and it stays put. Were you 
using 3.1.4 above? It had a bugged --fork which would explain the 
problem you're having now. 3.1.5 has been uploaded and should appear in 
the repositories shortly.

Bug#796261: RFS: roxterm/3.1.5-1

[Tony Houghton]

Package: sponsorship-requests
Severity: normal

Dear Vicent and/or other potential sponsors,

I am looking for a sponsor for the latest version of my package "roxterm"

 * Package name: roxterm
   Version : 3.1.5-1
   Upstream Author : Tony Houghton 
 * URL : http://roxterm.sourceforge.net
 * License : GPL2+
   Section : x11

It builds these binary packages:

 roxterm  - Multi-tabbed GTK+/VTE terminal emulator - binaries
 roxterm-data - Multi-tabbed GTK+/VTE terminal emulator - data files
 roxterm-dbg  - Debugging symbols for roxterm
 roxterm-gtk2 - Transitional package to upgrade roxterm-gtk2 to
roxterm
 roxterm-gtk2-dbg - Transitional package to upgrade roxterm-gtk2-dbg to
roxterm-dbg
 roxterm-gtk3 - Transitional package to upgrade roxterm-gtk3 to
roxterm
 roxterm-gtk3-dbg - Transitional package to upgrade roxterm-gtk3-dbg to
roxterm-dbg

It fixes upstream bug <https://sourceforge.net/p/roxterm/bugs/116/>
which is quite severe.

To access further information about this package,
please visit the following URL:

  http://mentors.debian.net/package/roxterm

Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/r/roxterm/roxterm_3.1.5-1.dsc


More information about roxterm can be obtained from
http://roxterm.sourceforge.net

Changes since the last upload:

roxterm (3.1.5-1) unstable; urgency=medium

  * Prevent --fork crashing on broken DBUS messages.

 -- Tony Houghton   Thu, 20 Aug 2015 16:21:44 +0100

Bug#796138: [roxterm] Setting up multi-tab terminal 'sessions' breaks with GTK3 roxterm - --tab call blocks?

[Tony Houghton]

On 19/08/15 20:06, OmegaPhil wrote:


Since I've noticed the gtk2 package is marked deprecated (itself a bad
thing - how can I reduce the height of the retardedly large GTK3 tab
bar?), I've attempted to switch over to the main package - however none
of my scripts to start up a window with more than one tab ('session')
work anymore. Investigating, it appears that the --tab command now blocks:



roxterm --tab -n "Bash 2 - %s" && roxterm --tab -n "Editing 1 - %s"


The first instance should always have blocked anyway, unless you use the 
--fork option. Use --fork instead of & in the shell, because it's 
supposed to wait until the first instance is ready to handle further 
commands. That didn't always work, but I've changed something in 3.1 
which hopefully fixes it.


The gtk2 version wouldn't have been possible to keep in Debian because 
the old vte packages are being removed in the next release. The gtk3 
version of vte has made some useful new features possible too.

Bug#793815: chromium: Enable accelerated video decoding

[Tony Houghton]

There were some unrelated issues with using the Ubuntu version on 
Debian, so I took the patch and added it to the official Debian source 
package. It applies and builds cleanly, and works well as far as I can 
tell. I've attached it here.


I think it's safe to include this patch from a stability standpoint, 
because even if there are problems, the acceleration can be enabled and 
disabled in about:config and defaults to off anyway.
Description: Enables using VA-API hardware acceleration in Linux. The patch for bpf_gpu_policy_linux.cc initially came from https://codereview.chromium.org/15955009/diff/92001/content/common/sandbox_linux/bpf_gpu_policy_linux.cc.

Index: beta.wily/content/common/gpu/media/gpu_video_decode_accelerator.cc
===
--- beta.wily.orig/content/common/gpu/media/gpu_video_decode_accelerator.cc	2015-07-17 00:25:47.768347000 -0400
+++ beta.wily/content/common/gpu/media/gpu_video_decode_accelerator.cc	2015-07-17 00:25:47.762347078 -0400
@@ -33,7 +33,7 @@
 #include "content/common/gpu/media/dxva_video_decode_accelerator.h"
 #elif defined(OS_MACOSX)
 #include "content/common/gpu/media/vt_video_decode_accelerator.h"
-#elif defined(OS_CHROMEOS)
+#elif defined(OS_CHROMEOS) || defined(OS_LINUX)
 #if defined(USE_V4L2_CODEC)
 #include "content/common/gpu/media/v4l2_device.h"
 #include "content/common/gpu/media/v4l2_slice_video_decode_accelerator.h"
@@ -346,7 +346,7 @@
 scoped_ptr
 GpuVideoDecodeAccelerator::CreateVaapiVDA() {
   scoped_ptr decoder;
-#if defined(OS_CHROMEOS) && defined(ARCH_CPU_X86_FAMILY)
+#if (defined(OS_CHROMEOS) || defined(OS_LINUX)) && defined(ARCH_CPU_X86_FAMILY)
   decoder.reset(new VaapiVideoDecodeAccelerator(
   make_context_current_, base::Bind(&GpuVideoDecodeAccelerator::BindImage,
 base::Unretained(this;
Index: beta.wily/content/content_common.gypi
===
--- beta.wily.orig/content/content_common.gypi	2015-07-17 00:25:47.768347000 -0400
+++ beta.wily/content/content_common.gypi	2015-07-17 00:25:47.762347078 -0400
@@ -824,7 +824,7 @@
 },
   ],
 }],
-['chromeos==1', {
+['chromeos==1 or desktop_linux==1', {
   'sources': [
 'common/gpu/media/accelerated_video_decoder.h',
 'common/gpu/media/h264_decoder.cc',
@@ -873,7 +873,7 @@
 'common/gpu/media/tegra_v4l2_device.h',
   ],
 }],
-['target_arch != "arm" and chromeos == 1', {
+['target_arch != "arm" and (chromeos == 1 or desktop_linux == 1)', {
   'dependencies': [
 '../media/media.gyp:media',
 '../third_party/libyuv/libyuv.gyp:libyuv',
Index: beta.wily/content/content_gpu.gypi
===
--- beta.wily.orig/content/content_gpu.gypi	2015-07-17 00:25:47.768347000 -0400
+++ beta.wily/content/content_gpu.gypi	2015-07-17 00:25:47.762347078 -0400
@@ -36,7 +36,7 @@
 ],
   },
 }],
-['target_arch!="arm" and chromeos == 1', {
+['target_arch!="arm" and (chromeos == 1 or desktop_linux == 1)', {
   'include_dirs': [
 '<(DEPTH)/third_party/libva',
   ],
Index: beta.wily/content/content_tests.gypi
===
--- beta.wily.orig/content/content_tests.gypi	2015-07-17 00:25:47.768347000 -0400
+++ beta.wily/content/content_tests.gypi	2015-07-17 00:25:47.763347065 -0400
@@ -1652,7 +1652,7 @@
   },
 ]
 }],
-['chromeos==1 and target_arch != "arm"', {
+['(chromeos==1 or desktop_linux==1) and target_arch != "arm"', {
   'targets': [
   {
 'target_name': 'vaapi_jpeg_decoder_unittest',
Index: beta.wily/content/public/common/content_switches.cc
===
--- beta.wily.orig/content/public/common/content_switches.cc	2015-07-17 00:25:47.768347000 -0400
+++ beta.wily/content/public/common/content_switches.cc	2015-07-17 00:25:47.763347065 -0400
@@ -960,7 +960,7 @@
 // Disable web audio API.
 const char kDisableWebAudio[]   = "disable-webaudio";
 
-#if defined(OS_CHROMEOS)
+#if defined(OS_CHROMEOS) || defined(OS_LINUX)
 // Disables panel fitting (used for mirror mode).
 const char kDisablePanelFitting[]   = "disable-panel-fitting";
 
Index: beta.wily/content/public/common/content_switches.h
===
--- beta.wily.orig/content/public/common/content_switches.h	2015-07-17 00:25:47.768347000 -0400
+++ beta.wily/content/public/common/content_switches.h	2015-07-17 00:25:47.764347052 -0400
@@ -273,7 +273,7 @@
 
 CONTENT_EXPORT extern const char kDisableWebAudio[];
 
-#if defined(OS_CHROMEOS)
+#if defined(OS_CHROMEOS) || defined(OS_LINUX)
 CONTENT_EXPORT extern const char kDisablePanelFitting[];
 CONTENT_EXPORT extern const char kDisableVaapiAcceleratedVideoEncode[];
 #endif
I

Bug#795551: roxterm: tries to overwrite /usr/share/pixmaps/roxterm.xpm, which is also in package roxterm-data 3.1.4-1

[Tony Houghton]

retitle 795529 conflicting file roxterm.xpm also provided by roxterm-data
severity 795529 important
severity 795551 important
forcemerge 795529 795551
thanks

Making the severity important because there's a workaround described in 
#795529.


I know what I did wrong, but for some reason the mistake didn't lead to 
the file being added to both (all?) packages when I built it here. I'll 
upload a fixed version soonest.

Bug#795402: base-files: Please add Creative Commons license texts

[Tony Houghton]

Package: base-files
Version: 9.2
Severity: wishlist

The Creative Commons licenses are quite popular for non-code files and
at least some of them are acknowledged to be DFSG-compatible since 3.0.
 only explicitly lists CC-BY-SA,
but I believe at least the more permissive CC-BY is also compatible.

I think it would be helpful to add the texts for these to
/usr/share/common-licenses so that they don't have to be included in
the copyright files of multiple packages.

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

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

Versions of packages base-files depends on:
ii  gawk [awk]  1:4.1.1+dfsg-1
ii  mawk [awk]  1.3.3-17

base-files recommends no packages.

base-files suggests no packages.

-- no debconf information

Bug#795298: #795298 RFS: roxterm/3.1.3-1

[Tony Houghton]

Oops, please wait until I change it to 3.1.4-1. I overlooked the appdata 
file in #795217. It contains some outdated content so I need to change 
it upstream.

Bug#795298: #795298 RFS: roxterm/3.1.3-1

[Tony Houghton]

On 12/08/15 19:39, Tony Houghton wrote:

Oops, please wait until I change it to 3.1.4-1. I overlooked the appdata
file in #795217. It contains some outdated content so I need to change
it upstream.


OK, 3.1.4-1 is ready now. The dget command is now:

dget -x 
http://mentors.debian.net/debian/pool/main/r/roxterm/roxterm_3.1.4-1.dsc


and the ChangeLog since the last release is:

roxterm (3.1.4-1) unstable; urgency=medium

  * Make --fork wait until dbus service name has been acquired.
  * Fixed child-exited signal handler for vte-2.91's new signature.
  * Support named user sessions.
  * Removed profile option for initial number of tabs.
  * Updated roxterm.svg's and roxterm.appdata.xml.in's licence and
copyright (Closes: #795217).
  * debian/control: Changed descriptions and dependencies of dummy
packages to prevent lintian warnings.
  * Added lintian overrides for warnings about dummy dbg packages.

 -- Tony Houghton   Wed, 12 Aug 2015 19:54:53 +0100

Bug#795298: RFS: roxterm/3.1.3-1

[Tony Houghton]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "roxterm"

 * Package name: roxterm
   Version : 3.1.3-1
   Upstream Author : Tony Houghton 
 * URL : http://roxterm.sourceforge.net
 * License : GPL2+
   Section : x11

It builds these binary packages:

  roxterm -  Multi-tabbed GTK+/VTE terminal emulator - binaries
  roxterm-data - Multi-tabbed GTK+/VTE terminal emulator - data
 files
  roxterm-dbg -  Debugging symbols for roxterm
  roxterm-gtk2 - Transitional package to updgrade roxterm-gtk2 to
 roxterm
  roxterm-gtk2-dbg - Transitional package to updgrade roxterm-gtk2-dbg
 to roxterm-dbg
  roxterm-gtk3 - Transitional package to updgrade roxterm-gtk3 to
 roxterm
  roxterm-gtk3-dbg - Transitional package to updgrade roxterm-gtk3-dbg
 to roxterm-dbg

To access further information about this package, please visit the
following URL:

  http://mentors.debian.net/package/roxterm

Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/r/roxterm/roxterm_3.1.3-1.dsc


More information about roxterm can be obtained from
http://roxterm.sourceforge.net

Changes since the last upload:

roxterm (3.1.3-1) unstable; urgency=medium

  * Make --fork wait until dbus service name has been acquired.
  * Fixed child-exited signal handler for vte-2.91's new signature.
  * Support named user sessions.
  * Removed profile option for initial number of tabs.
  * Updated SVG icon's licence and copyright (Closes: #795217).
  * debian/control: Changed descriptions and dependencies of dummy 
packages to

prevent lintian warnings.
  * Added lintian overrides for warnings about dummy dbg packages.

 -- Tony Houghton   Wed, 12 Aug 2015 18:13:04 +0100

Regards,
  Tony Houghton

Bug#795217: missing license in debian/copyright

[Tony Houghton]

I've heard back from the original author and he says his icons are 
public domain and I can use any licence I like. I think it would be best 
if I stick to CC-BY and update the metadata and copyright file.

Bug#795217: missing license in debian/copyright

[Tony Houghton]

On 11/08/15 21:40, Thorsten Alteholz wrote:


please add the missing license of:
  roxterm-3.0.2/roxterm.appdata.xml.in
to your debian/copyright and remove all files that are licensed under
CC 2.0 (which is not DFSG compatible):
  roxterm-3.0.2/roxterm.svg
  roxterm-3.0.2/.DirIcon


Hi,

roxterm.svg is a derivative of the "Etiquette" terminal icon described 
in its metadata. I've asked the original author for permission to change 
the licence to CC-BY 4.0, but in case he's no longer reachable at the 
address I found for him, I think I might be able to change the licence 
anyway. I've read a few things that imply CC 2.0 does allow derivative 
works to be distributed under later versions of the licence, but I don't 
understand the legalese in the official licence well enough to confirm 
that. For example  says, "In 
addition, the version 2.0 and 2.5 [of CC-BY-SA] are NOT transitively 
compatible because of clause 4b, since that only allows redistribution 
of *derivative works* under later versions of the license." Can you 
confirm whether I'm allowed to use a newer version of CC in this case, 
or should I ask debian-legal?



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

Bug#792200: closed by Vincent Cheng (Re: Bug#792200: RFS: roxterm/3.0.2-1)

[Tony Houghton]

Hi,

I got emails saying that roxterm 3.0.1-1 and then 3.0.2-1 were uploaded 
and the RFS bugs closed (the latter on 13 July), but the latest version 
showing up in the archives is still 2.9.5-1. Has something gone wrong 
with the upload?



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

Bug#793815: chromium: Enable accelerated video decoding

[Tony Houghton]

Package: chromium
Version: 44.0.2403.107-1
Severity: wishlist

By default Chromium doesn't support accelerated video decoding on
desktop Linux, but with a few tweaks to the source etc it can easily be
enabled due to the support in ChromeOS (using VAAPI). I think the
situation is that upstream just don't have anyone prepared to maintain
it properly in non-ChromeOS Linux at the moment, and earlier issues
about it being unstable in Linux are obsolete.

IMO chromium is severely hampered without this feature. It needs quite a
modern/high-end CPU to be able to play HD at full speed, and even if you
have one it can cause unwanted fan noise.

There is an Ubuntu PPA for Chromium Beta which has VAAPI enabled at
. I've
tried using it to watch a few youtube videos on a few machines
(including using the VDPAU backend for VAAPI with an AMD GPU) and it
worked well on all of them.

The patches the PPA adds to the source look quite simple, just changing
a few #ifs to enable the code in other versions of Linux besides
ChromeOS, and fixing the way the va library is opened (upstream were
depending on hardcoded paths in ChromeOS).

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

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

Versions of packages chromium depends on:
ii  libasound2   1.0.29-1
ii  libatk1.0-0  2.16.0-2
ii  libc62.19-19
ii  libcairo21.14.2-2
ii  libcups2 2.0.3-6
ii  libdbus-1-3  1.8.18-1
ii  libexpat12.1.0-6+b3
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.5.2-4
ii  libgdk-pixbuf2.0-0   2.31.4-2
ii  libglib2.0-0 2.44.1-1.1
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk2.0-0  2.24.28-1
ii  libharfbuzz0b0.9.41-1
ii  libjpeg62-turbo  1:1.4.0-7
ii  libnspr4 2:4.10.8-2
ii  libnss3  2:3.19.2-1
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpci3  1:3.2.1-3
ii  libspeechd2  0.8-7
ii  libspeex11.2~rc1.2-1
ii  libsrtp0 1.4.5~20130609~dfsg-1.1
ii  libstdc++6   5.1.1-14
ii  libx11-6 2:1.6.3-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.1-2+b2
ii  libxi6   2:1.7.4-1+b2
ii  libxml2  2.9.1+dfsg1-5
ii  libxrandr2   2:1.4.2-1+b1
ii  libxrender1  1:0.9.8-1+b1
ii  libxslt1.1   1.1.28-2+b2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+3
ii  xdg-utils1.1.0~rc1+git20111210-7.4

chromium recommends no packages.

Versions of packages chromium suggests:
pn  chromium-l10n  

-- 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#728133: roxterm: lockups when trying to rename tabs while output is happening

[Tony Houghton]

tags 728133 + unreproducible moreinfo
thanks

I was never able to reproduce this, can you test whether it's still a 
problem in the latest version?



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

Bug#719333: /usr/bin/roxterm: Block cursor hides underlying character by default

[Tony Houghton]

block 719333 792194
severity 719333 wishlist
forwarded 792194 https://bugzilla.gnome.org/show_bug.cgi?id=695011
thanks

I thought I'd already replied to this, I must have replied only 
privately to Keith by mistake. I don't think the patch is necessary 
because if the cursor colour option isn't enabled by the user this 
results in NULL being passed to vte_terminal_set_color_cursor() anyway.


To allow a custom cursor background colour with a contrasting foreground 
I need vte to be enhanced as per #792194 
.



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

Bug#792200: RFS: roxterm/3.0.2-1

[Tony Houghton]

Package: sponsorship-requests
Severity: normal

Dear mentors,

By Murphy's Law (or is it Sod's Law) I found quite a serious bug in
roxterm a day or two after the last release, so I've uploaded a new
version which needs sponsoring. TIA.

 * Package name: roxterm
   Version : 3.0.2-1
   Upstream Author : Tony Houghton 
 * URL : http://roxterm.sourceforge.net
 * License : GPL2+
   Section : x11

It builds these binary packages:

 roxterm- Multi-tabbed GTK+/VTE terminal emulator - binaries
 roxterm-data - Multi-tabbed GTK+/VTE terminal emulator - data files
 roxterm-dbg - Debugging symbols for roxterm
 roxterm-gtk2 - Multi-tabbed GTK+/VTE terminal emulator - transitional 
package
 roxterm-gtk2-dbg - Multi-tabbed GTK+/VTE terminal emulator - 
transitional package
 roxterm-gtk3 - Multi-tabbed GTK+/VTE terminal emulator - transitional 
package
 roxterm-gtk3-dbg - Multi-tabbed GTK+/VTE terminal emulator - 
transitional package


To access further information about this package, please visit the
following URL:

  http://mentors.debian.net/package/roxterm


Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/r/roxterm/roxterm_3.0.2-1.dsc


More information about roxterm can be obtained from
http://roxterm.sourceforge.net

Changes since the last upload:

roxterm (3.0.2-1) unstable; urgency=medium

  * Fixed crash when dragging a tab from one window to another.
  * Added note about python 2-3 migration to news.html.

 -- Tony Houghton   Sun, 12 Jul 2015 14:11:47 +0100


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

Bug#688292: roxterm-gtk2: Hide menubar setting is not saved

[Tony Houghton]

Closing: Not a bug.


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

Bug#792194: libvte-2.91-0: Requires option to set cursor foreground colour

[Tony Houghton]

Package: libvte-2.91-0
Version: 0.40.2-1
Severity: wishlist
Tags: upstream

vte provides vte_terminal_set_color_cursor() which only affects the
cursor's background colour, and there is no way to set the cursor
foreground colour. This can result in a pair of colours with inadequate
contrast to be able to read the character under the cursor.

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

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

Versions of packages libvte-2.91-0 depends on:
ii  libatk1.0-0  2.16.0-2
ii  libc62.19-18
ii  libcairo-gobject21.14.2-2
ii  libcairo21.14.2-2
ii  libgdk-pixbuf2.0-0   2.31.4-2
ii  libglib2.0-0 2.44.1-1.1
ii  libgnutls-deb0-283.3.15-7
ii  libgtk-3-0   3.16.4-2
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libvte-2.91-common   0.40.2-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

libvte-2.91-0 recommends no packages.

libvte-2.91-0 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#790816: RFS: roxterm/3.0.1-1

[Tony Houghton]

On 08/07/15 07:09, Vincent Cheng wrote:


NameError: name 'reload' is not defined
debian/rules:48: recipe for target 'override_dh_auto_clean' failed


Oh, I didn't notice reload was python 2 only. And setdefaultencoding 
doesn't work any more in python 3 anyway.



However, I was able to build your package just by adding "export
LC_ALL=C.UTF-8" to d/rules. I can upload your package with this
change, or if you'd rather fix this upstream, that's fine with me as
well.


I tried that with pdebuild and it didn't work for me. I got a series of 
errors from perl that it couldn't set the locale and was falling back to 
"C", and then mscript/maitch failed the same way as before.


In any case I'd rather fix the problem upstream, in a way that doesn't 
depend on the environment, and I finally found a way to do that, by 
adding an encoding argument to open(). With this change it does build 
for me with pdebuild so I've uploaded it again, and hopefully we've got 
rid of all these problems at last.


There is one other change, in src/roxterm-config.ui I rearranged the 
Tabs section of the profile editor slightly, in response to a simple 
issue that was raised upstream this morning.



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

Bug#790816: RFS: roxterm/3.0.1-1

[Tony Houghton]

On 07/07/15 09:21, Vincent Cheng wrote:


UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
836: ordinal not in range(128)

debian/rules:36: recipe for target 'override_dh_auto_build' failed

I've attached the full build log.


I think the problem is that the PC you tried the build on doesn't have 
utf8 as its default encoding, so I need to enforce that in the script. 
This would need to apply upstream too so I think the best way is to 
change mscript.py with the attached patch. Would you be able to test 
that for me before I upload a new version?




--- mscript.py.old	2015-07-07 14:00:48.380541102 +0100
+++ mscript.py	2015-07-07 14:01:52.855115233 +0100
@@ -1,6 +1,10 @@
 #!/usr/bin/env python3
 
-import errno, os, re, sys, time
+import sys
+reload(sys)
+sys.setdefaultencoding('UTF8')
+
+import errno, os, re, time
 
 from maitch import *
 

Bug#790816: RFS: roxterm/3.0.1-1

[Tony Houghton]

On 04/07/15 22:29, Vincent Cheng wrote:


(If you have time, please upload an updated package to mentors so it's
easier to discuss any further changes.)


I've done that, hopefully it will be available by the time you read
this. The Breaks/Replaces I've decided on are as follows:

Package: roxterm-data
Replaces: roxterm-common
Breaks: roxterm-common (<< 3.0.0)

I don't think it needs to explicitly Break any other packages,
because their removal/replacement will be forced along with
roxterm-common.

Package: roxterm
Replaces: roxterm-gtk3 (<< 3.0.0), roxterm-gtk2 (<< 3.0.0)
Breaks: roxterm-gtk3 (<< 3.0.0), roxterm-gtk2 (<< 3.0.0)

I originally also had it Break the old -dbg packages, but I think
that's superfluous for the same reason as above.

Package: roxterm-dbg
Replaces: roxterm-gtk3-dbg (<< 3.0.0), roxterm-gtk2-dbg (<< 3.0.0)
Breaks: roxterm-gtk3-dbg (<< 3.0.0), roxterm-gtk2-dbg (<< 3.0.0)


roxterm-gtk2, roxterm-gtk3, roxterm-gtk2 and roxterm-gtk3 are now all
dummy packages, they don't Break or Replace anything because the
packages they depend on should take care of everything, and as virtual
packages they don't contain files that clash with others.

Nothing explicitly breaks the old virtual package roxterm, I can't see a
need for that with all the other relationships I have.

I've tested what should be the most difficult upgrade scenario in the
piuparts chroot and it went smoothly.

Other changes:

I think debian/rules was passing CFLAGS etc to ./mscript.py configure
incorrectly so I've fixed that.

During testing I had a problem with changes wrt the tarball in a pot
file while trying to repeat a build so I've added a
debian/source/options with extend-diff-ignore for .pot and .po.


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

Bug#790816: RFS: roxterm/3.0.1-1

[Tony Houghton]

On 04/07/15 10:19, Vincent Cheng wrote:

On Fri, Jul 3, 2015 at 8:30 AM, Tony Houghton  wrote:


My thinking is that anybody still using roxterm-gtk2 has some good
reason to do so and will not want to upgrade to a GTK3 version even if
it means missing out on the latest features and bug fixes; they are
already missing out on some useful features from vte-2.90. With the
relationships the way they are at the moment users can keep roxterm-gtk2
without having to pin it. I tested that scenario and it seems to work.
But, since vte9 (the GTK2 version of vte) is scheduled for removal from
the archive, is this undesirable?


Ah, I didn't realize that this is actually intentional. Well, IMHO
it's saner to offer users an upgrade path by default (i.e. to the gtk3
version), and let them choose to manually pin packages if they don't
want to upgrade for some reason. However, I can't find a Policy
reference that mandates all binary packages to have an upgrade path or
similar, so I'll leave the choice to you.


I think I'll change my decision on that. There do seem to be stronger
reasons for providing an automatic upgrade from roxterm-gtk2 than to
make things easier for users who want to keep it without continued
support and maintenance.


Ack, roxterm should declare Breaks: roxterm-gtk2 (in addition to
-gtk3) and roxterm-dbg should declare Breaks: roxterm-gtk2-dbg (in
addition to -gtk3-dbg). Why wouldn't you want the equivalent Replaces
relationships here as well? Having roxterm declare Replaces:
roxterm-gtk2 is not going to force roxterm-gtk2 to be automatically
upgraded in the first scenario I described in my last email (where the
user has roxterm-gtk2 and roxterm-common installed, but not roxterm;
nothing gets upgraded in this scenario). Without Replaces, users who
currently have only roxterm-gtk2 and roxterm-common installed, who
then decide to switch to the gtk3 version by running apt-get install
roxterm, can't do so (at least, not without removing roxterm-gtk2
first).


One other point I noticed is that currently I have roxterm-data Breaks
and Replaces roxterm << 3.0.0-1 (actually I put 2 instead of 3 by
mistake so that needs changing anyway), where roxterm << 3 is the old
virtual package. As there is no direct replacement for that, do you
agree I should keep the Breaks where it is but remove the Replaces?
Breaks probably isn't strictly necessary either, but it might be a good
idea just in case there's a clash in /usr/share/doc/roxterm.


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

Bug#790816: RFS: roxterm/3.0.1-1

[Tony Houghton]

On 02/07/15 21:09, Vincent Cheng wrote:

Control: tag -1 + moreinfo
Control: owner -1 !

Hi Tony,

On Wed, Jul 1, 2015 at 1:22 PM, Tony Houghton  wrote:


I thought I had released 2.9.6-1 and 2.9.7-1 via sponsorship too, but
for some reason the current version in unstable is still 2.9.5-1. Is the
changelog OK as above or should I merge these entries?


Please merge the above d/changelog entries.


Done. I think I've realised/remembered the reason for the "missing"
releases. I released them upstream and in my Ubuntu PPA, but not for
Debian because it was in freeze at the time and I didn't think the
changes were important enough for an unblock.


I just skimmed the debdiff between 2.9.5-1 and your package on mentors
and noticed a few small things:
- your newly added d/copyright stanza for ".ycm_extra_conf.py.in" has
a License: GPL-3+ header, but the license body references GPL-2
multiple times.


Fixed. But I have some more questions before I upload a new version...


- d/rules: CFLAGS = $(shell dpkg-buildflags | grep '^CFLAGS=') is
quite brittle; I suggest using dpkg-buildflags --get CFLAGS instead
(ditto for CPPFLAGS and LDFLAGS)


That's better, I don't know how I missed that, unless it's a recent
addition to dpkg-buildflags. The way I get the parallel option looks
quite nasty too, is there a better way to do that?


Regarding your package split, have you tested other possible upgrade
scenarios? There's a few scenarios I can think of that are broken or
not ideal:
- A user who just has roxterm-gtk2 installed (and roxterm-common
auto-installed), without the roxterm metapackage, will not get any
updates because both of these packages are no longer built from
src:roxterm


My thinking is that anybody still using roxterm-gtk2 has some good
reason to do so and will not want to upgrade to a GTK3 version even if
it means missing out on the latest features and bug fixes; they are
already missing out on some useful features from vte-2.90. With the
relationships the way they are at the moment users can keep roxterm-gtk2
without having to pin it. I tested that scenario and it seems to work.
But, since vte9 (the GTK2 version of vte) is scheduled for removal from
the archive, is this undesirable?


- A user has roxterm-gtk2 and roxterm-gtk2-dbg installed. Aside from
the same problem as the first scenario, if he/she now chooses to
apt-get install roxterm-dbg, (I think) dpkg will explode due to file
conflicts between roxterm-gtk2-dbg and roxterm-dbg.


So I should add Breaks: roxterm-gtk2-dbg to roxterm-dbg, and I think it
would also be more appropriate to move Breaks: roxterm-gtk2 and
roxterm-gtk3 from roxterm-data to roxterm, because the latter is the
package that contains the corresponding files. But, if the previous
point about preventing roxterm-gtk2 from being automatically upgraded is
OK, I don't want to add Replaces: roxterm-gtk2(-dbg).


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

Bug#790816: RFS: roxterm/3.0.1-1

[Tony Houghton]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "roxterm"

 * Package name: roxterm
   Version : 3.0.1-1
   Upstream Author : Tony Houghton 
 * URL : http://roxterm.sourceforge.net
 * License : GPL2+
   Section : x11

It builds these binary packages:

 roxterm- Multi-tabbed GTK+/VTE terminal emulator - binaries
 roxterm-data - Multi-tabbed GTK+/VTE terminal emulator - data files
 roxterm-dbg - Debugging symbols for roxterm
 roxterm-gtk3 - Multi-tabbed GTK+/VTE terminal emulator - transitional 
package
 roxterm-gtk3-dbg - Multi-tabbed GTK+/VTE terminal emulator - 
transitional package


To access further information about this package, please visit the 
following URL:


  http://mentors.debian.net/package/roxterm


Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/r/roxterm/roxterm_3.0.1-1.dsc


More information about roxterm can be obtained from
http://roxterm.sourceforge.net

Changes since the last upload:

roxterm (3.0.1-1) unstable; urgency=medium

  * Updated Standards-Version to 3.9.6.
  * Build uses python3 (updated Build-Depends accordingly).
  * Upstream tarball now uses .xz compression.
  * Added Select All menu item.
  * Allow unlimited scrollback lines.
  * Fixed some unsafe uses of sprintf.
  * Provide option to rewrap text when terminal width changes.
  * Drop support for GTK2 etc (Closes: #790183).
  * Reorganized surviving binary packages.
  * Use vte-2.91 API (Closes: #788028).

 -- Tony Houghton   Wed, 01 Jul 2015 18:50:46 +0100

roxterm (2.9.7-1) unstable; urgency=low

  * Fixed colour/shortcut shceme CLI switch clash.
  * Fixed --tab aiming to target most recently focused window.

 -- Tony Houghton   Mon, 30 Mar 2015 18:24:17 +0100

roxterm (2.9.6-1) unstable; urgency=low

  * debian/copyright: Added .ycm_extra_conf.py.in.
  * Fade text in unselected tabs.
  * Fix maximise and full screen buttons in profile.

 -- Tony Houghton   Thu, 08 Jan 2015 21:16:21 +

I thought I had released 2.9.6-1 and 2.9.7-1 via sponsorship too, but
for some reason the current version in unstable is still 2.9.5-1. Is the
changelog OK as above or should I merge these entries?

  Regards,
   Tony Houghton


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

Bug#787939: gnome-session: "Something has gone wrong" temporarily displayed when logging in

[Tony Houghton]

Package: gnome-session
Version: 3.16.0-1
Severity: normal

Dear Maintainer,

When I log in to GNOME 3 I always get the "Oh no! Something has gone
wrong," screen, but it disappears after a couple of seconds and my
desktop appears as normal.

I don't know how you're supposed to diagnose what has gone wrong when
you see this screen, but I'm attaching what appears in the systemd
journal at the time in case it's of any use.

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

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

Versions of packages gnome-session depends on:
ii  gnome-session-bin  3.16.0-1
ii  gnome-session-common   3.16.0-1
ii  gnome-settings-daemon  3.14.2-3
ii  gnome-shell3.14.4-1

gnome-session recommends no packages.

Versions of packages gnome-session suggests:
ii  desktop-base  8.0.2
ii  gnome-keyring 3.16.0-2
ii  gnome-user-guide  3.16.1-1

-- no debconf information
Jun 06 15:04:03 jeanette gdm-password][2380]: pam_unix(gdm-password:session): 
session opened for user tony by (unknown)(uid=0)
Jun 06 15:04:03 jeanette systemd[2391]: pam_unix(systemd-user:session): session 
opened for user tony by (uid=0)
Jun 06 15:04:03 jeanette systemd-logind[533]: New session 3 of user tony.
Jun 06 15:04:03 jeanette systemd[2391]: Starting Paths.
Jun 06 15:04:03 jeanette systemd[2391]: Reached target Paths.
Jun 06 15:04:03 jeanette systemd[2391]: Starting Timers.
Jun 06 15:04:03 jeanette systemd[2391]: Reached target Timers.
Jun 06 15:04:03 jeanette systemd[2391]: Starting Sockets.
Jun 06 15:04:03 jeanette systemd[2391]: Reached target Sockets.
Jun 06 15:04:03 jeanette systemd[2391]: Starting Basic System.
Jun 06 15:04:03 jeanette systemd[2391]: Reached target Basic System.
Jun 06 15:04:03 jeanette systemd[2391]: Starting Default.
Jun 06 15:04:03 jeanette systemd[2391]: Reached target Default.
Jun 06 15:04:03 jeanette systemd[2391]: Startup finished in 7ms.
Jun 06 15:04:03 jeanette org.a11y.Bus[2315]: g_dbus_connection_real_closed: 
Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an 
async read (g-io-error-quark, 0). Exiting.
Jun 06 15:04:03 jeanette gnome-session[2311]: WARNING: Lost name on bus: 
org.gnome.SessionManager
Jun 06 15:04:03 jeanette org.a11y.atspi.Registry[2321]: 
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Jun 06 15:04:03 jeanette gnome-session[2311]: gnome-session[2311]: WARNING: 
Lost name on bus: org.gnome.SessionManager
Jun 06 15:04:03 jeanette gnome-session[2311]: (gnome-settings-daemon:2331): 
GLib-GIO-WARNING **: Error releasing name org.gnome.SettingsDaemon: The 
connection is closed
Jun 06 15:04:03 jeanette gnome-session[2311]: (gnome-settings-daemon:2331): 
GLib-GIO-WARNING **: Invalid id 5 passed to g_bus_unown_name()
Jun 06 15:04:03 jeanette gnome-session[2311]: g_dbus_connection_real_closed: 
Remote peer vanished with error: Error receiving message: Connection reset by 
peer (g-io-error-quark, 44). Exiting.
Jun 06 15:04:03 jeanette ca.desrt.dconf[2315]: g_dbus_connection_real_closed: 
Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an 
async read (g-io-error-quark, 0). Exiting.
Jun 06 15:04:03 jeanette colord[846]: Automatic remove of 
icc-a1e201739e5f5ceba132c4da84d00981 from xrandr-Apple Computer Inc-Color LCD
Jun 06 15:04:03 jeanette colord[846]: Profile removed: 
icc-a1e201739e5f5ceba132c4da84d00981
Jun 06 15:04:03 jeanette colord[846]: device removed: xrandr-Apple Computer 
Inc-Color LCD
Jun 06 15:04:03 jeanette polkitd(authority=local)[827]: Unregistered 
Authentication Agent for unix-session:c3 (system bus name :1.97, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8) 
(disconnected from bus)
Jun 06 15:04:03 jeanette /etc/gdm3/Xsession[2400]: /etc/gdm3/Xsession: 
Beginning session setup...
Jun 06 15:04:03 jeanette /etc/gdm3/Xsession[2400]: localuser:tony being added 
to access control list
Jun 06 15:04:03 jeanette /etc/gdm3/Xsession[2400]: openConnection: connect: No 
such file or directory
Jun 06 15:04:03 jeanette /etc/gdm3/Xsession[2400]: cannot connect to brltty at 
:0
Jun 06 15:04:03 jeanette org.a11y.Bus[2453]: Activating service 
name='org.a11y.atspi.Registry'
Jun 06 15:04:03 jeanette org.a11y.Bus[2453]: Successfully activated service 
'org.a11y.atspi.Registry'
Jun 06 15:04:03 jeanette org.a11y.atspi.Registry[2459]: SpiRegistry daemon is 
running with well-known name - org.a11y.atspi.Registry
Jun 06 15:04:03 jeanette rtkit-daemon[936]: Successfully made thread 2486 of 
process 2486 (/usr/bin/pulseaudio) owned by '1000' high priority

Bug#738837: python-lockfile: New upstream release with py3k support

[Tony Houghton]

This issue is preventing me from updating a script to python3. The 
script isn't part of a debian package, but it is crucial to building 
roxterm, which is packaged. I'm willing to use a new lockfile API as 
part of the update to python3, whereas most projects which aren't 
prioritising on migrating from 2 to 3 are probably more "legacy" and the 
maintainers won't want to have to deal with an API change.


So that gave me an idea, would it make sense to deal with it by keeping 
the existing package for python2, and only supporting python3 for >= 0.9 
and renaming the binary package to python3-lockfile? That way legacy 
packages can carry on working for now without having to change anything, 
while those wanting to migrate from python 2 to 3 can move on.



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

Bug#773713: broadcom-sta: Please support kernel 3.18

[Tony Houghton]

Package: broadcom-sta-dkms
Version: 6.30.223.248-4
Followup-For: Bug #773713

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Tony Houghton 
To: Debian Bug Tracking System <773...@bugs.debian.org>
Subject: Re: broadcom-sta: Please support kernel 3.18
Bcc: Tony Houghton 
Message-ID: <20150415141153.1889.39110.reportbug@jeanette.centauri>
X-Mailer: reportbug 6.6.3
Date: Wed, 15 Apr 2015 15:11:53 +0100

Package: broadcom-sta-dkms
Version: 6.30.223.248-3
Followup-For: Bug #773713

This package seems to work fine with 3.19-trunk from experimental when
pacthed appropriately. I used patches from Ubuntu and Arch:

<https://github.com/longsleep/bcmwl-ubuntu/blob/master/debian/patches/0015-add-support-for-Linux-3.18.patch>
<https://gist.github.com/hobarrera/ac0e6225210ac5bb13f6#file-broadcom-sta-6-30-223-248-linux-3-18-null-pointer-crash-patch>

I had to change the paths to add amd64/ before src/, I guess you'll have
to make copies to do the same for i386 in the official package.

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages broadcom-sta-dkms depends on:
ii  dkms  2.2.0.3-2

Versions of packages broadcom-sta-dkms recommends:
ii  wireless-tools  30~pre9-8

broadcom-sta-dkms suggests no packages.

-- no debconf information

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages broadcom-sta-dkms depends on:
ii  dkms  2.2.0.3-2

Versions of packages broadcom-sta-dkms recommends:
ii  wireless-tools  30~pre9-8

broadcom-sta-dkms 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#618426: transmission: Stops torrents which have no tracker

[Tony Houghton]

On 31/03/15 22:36, Sandro Tosi wrote:

Hello,
I suspect this has been fixed a long ago, can you confim?


Sorry, I've been using rtorrent instead for the last few years.


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

Bug#771358: unblock: roxterm/2.9.5-1

[Tony Houghton]

tags 771358 - moreinfo
thanks

On 30/11/2014 11:46, Ivo De Decker wrote:


Please go ahead, and remove the moreinfo tag from this bug once the upload is
in ustable.


OK, it's been sponsored (thanks Gregor Herrmann) and is now in unstable. 
Thanks for allowing the unblock.



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

Bug#771361: RFS: roxterm/2.9.5-1

[Tony Houghton]

On 29/11/2014 00:18, gregor herrmann wrote:

On Fri, 28 Nov 2014 19:35:02 +, Tony Houghton wrote:


I am looking for a sponsor for my package "roxterm". I have also posted an
unblock request which is #771358. Should I merge these two "bugs"?


Please add the requested information (i.e. a debdiff of the .dsc
files) to #771358. It would make sense to have a yay/nay from the
release team before uploading the new version to unstable.


I've been asked to go ahead in #771358 so I'd be grateful for someone to 
proceed with the sponsorship.



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

Bug#771358: unblock: roxterm/2.9.5-1

[Tony Houghton]

tags 771358 - moreinfo
thanks

On 28/11/14 19:46, Jonathan Wiltshire wrote:

Control: tag -1 moreinfo

On Fri, Nov 28, 2014 at 07:27:21PM +, Tony Houghton wrote:

Please unblock package roxterm; I have uploaded version 2.9.5-1 to
mentors.debian.net for sponsorship.


I can't unblock anything that's not in sid.


OK. I did things in the wrong order, but it's turned out to have a 
positive outcome because a potential sponsor would like to see your 
decision before accepting it into unstable (#771361).



I'm certainly willing to consider new upstream releases case-by-case, but
the debdiff output you sent is for the binary packages, not the source.

Please attach a source debdiff (i.e. against the .dscs, not the .changes)
and remove the moreinfo tag, and I'll happily take a look.


Sorry about that. Correct debdiff attached.

diff -Nru roxterm-2.9.4/AppInfo.xml roxterm-2.9.5/AppInfo.xml
--- roxterm-2.9.4/AppInfo.xml   2014-09-17 15:33:31.0 +0100
+++ roxterm-2.9.5/AppInfo.xml   2014-11-28 18:27:26.0 +
@@ -3,7 +3,7 @@
   Run text-based programs (command prompt)
   
 A medium-weight terminal emulator with a flexible GUI
-2.9.4 (2014-09-17)
+    2.9.5 (2014-11-28)
 Tony Houghton <h...@realh.co.uk>
 GNU General Public License
 http://roxterm.sourceforge.net
diff -Nru roxterm-2.9.4/ChangeLog roxterm-2.9.5/ChangeLog
--- roxterm-2.9.4/ChangeLog 2014-09-17 15:48:42.0 +0100
+++ roxterm-2.9.5/ChangeLog 2014-11-28 18:21:48.0 +
@@ -1,6 +1,12 @@
+Version 2.9.5
+Author: Tony Houghton 
+Date:   Fri, 28 Nov 2014 18:21:07 +
+ * Recognise _NET_WM_DESKTOP value 0x
+ * Check for unset $EDITOR when editing shortcuts
+
 Version 2.9.4
 Author: Tony Houghton 
-Date:   Wed, 17 Sep 2014 15:47:06 +0100
+Date:   Wed, 17 Sep 2014 17:17:35 +0100
  * Fixed metadata_license and screenshot in appdata
  * Defer writing AppInfo.xml to mscript.py dist
  * Output translation files correctly
diff -Nru roxterm-2.9.4/debian/changelog roxterm-2.9.5/debian/changelog
--- roxterm-2.9.4/debian/changelog  2014-09-17 17:17:14.0 +0100
+++ roxterm-2.9.5/debian/changelog  2014-11-28 18:29:10.0 +
@@ -1,3 +1,11 @@
+roxterm (2.9.5-1) unstable; urgency=medium
+
+  * Recognise _NET_WM_DESKTOP special value 0x correctly.
+  * Don't crash if EDITOR env variable is unset when editing shortcuts
+(Closes: #771022).
+
+ -- Tony Houghton   Fri, 28 Nov 2014 18:20:06 +
+
 roxterm (2.9.4-1) unstable; urgency=low
 
   * Fixed metadata_license and non-default screenshot in appdata.
diff -Nru roxterm-2.9.4/Help/Changes roxterm-2.9.5/Help/Changes
--- roxterm-2.9.4/Help/Changes  2014-09-17 15:48:42.0 +0100
+++ roxterm-2.9.5/Help/Changes  2014-11-28 18:21:48.0 +
@@ -1,6 +1,12 @@
+Version 2.9.5
+Author: Tony Houghton 
+Date:   Fri, 28 Nov 2014 18:21:07 +
+ * Recognise _NET_WM_DESKTOP value 0x
+ * Check for unset $EDITOR when editing shortcuts
+
 Version 2.9.4
 Author: Tony Houghton 
-Date:   Wed, 17 Sep 2014 15:47:06 +0100
+Date:   Wed, 17 Sep 2014 17:17:35 +0100
  * Fixed metadata_license and screenshot in appdata
  * Defer writing AppInfo.xml to mscript.py dist
  * Output translation files correctly
diff -Nru roxterm-2.9.4/po/es.po roxterm-2.9.5/po/es.po
--- roxterm-2.9.4/po/es.po  2014-09-17 15:48:46.0 +0100
+++ roxterm-2.9.5/po/es.po  2014-11-28 18:21:58.0 +
@@ -10,7 +10,7 @@
 msgstr ""
 "Project-Id-Version: roxterm\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-08-06 19:48+0100\n"
+"POT-Creation-Date: 2014-09-29 16:59+0100\n"
 "PO-Revision-Date: 2013-05-23 15:18+\n"
 "Last-Translator: Tony Houghton \n"
 "Language-Team: Spanish (http://www.transifex.com/projects/p/roxterm/language/";
@@ -1132,154 +1132,154 @@
 msgid "Invalid geometry specification"
 msgstr ""
 
-#: ../src/roxterm.c:4705
+#: ../src/roxterm.c:4706
 msgid ""
 "Closing this ROXTerm tab may cause loss of data. Are you sure you want to "
 "continue?"
 msgstr ""
 
-#: ../src/roxterm.c:4709
+#: ../src/roxterm.c:4710
 msgid ""
 "You are about to close a ROXTerm window; this may cause loss of data. Are "
 "you sure you want to continue?"
 msgstr ""
 
-#: ../src/roxterm.c:4713
+#: ../src/roxterm.c:4714
 msgid ""
 "You are about to close a window containing multiple ROXTerm tabs; this may "
 "cause loss of data. Are you sure you want to continue?"
 msgstr ""
 
-#: ../src/roxterm.c:4722
+#: ../src/roxterm.c:4723
 msgid "ROXTerm: Confirm close"
 msgstr ""
 
-#: ../src/roxterm.c:4726
+#: ../src/roxterm.c:4727
 msgid "_Don't show this again"
 msgstr ""
 
-#: ../src/roxterm.c:4734
+#: ../src/roxterm.c:4735
 msgid "Only warn i

Bug#771361: RFS: roxterm/2.9.5-1

[Tony Houghton]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "roxterm". I have also posted 
an unblock request which is #771358. Should I merge these two "bugs"?


* Package name: roxterm
* Version : 2.9.5-1
* Upstream Author : Tony Houghton 
* URL : http://roxterm.sourceforge.net
* License : GPL-2+, LGPL-3+
* Section : x11

It builds these binary packages:

roxterm - Multi-tabbed GTK+/VTE terminal emulator - virtual package for GTK3
roxterm-common - Multi-tabbed GTK+/VTE terminal emulator - common files
roxterm-gtk2 - Multi-tabbed GTK+/VTE terminal emulator - GTK2 version
roxterm-gtk2-dbg - Debugging symbols for GTK2 version of roxterm
roxterm-gtk3 - Multi-tabbed GTK+/VTE terminal emulator - GTK3 version
roxterm-gtk3-dbg - Debugging symbols for GTK3 version of roxterm

To access further information about this package, please visit the
following URL:

http://mentors.debian.net/package/roxterm


Alternatively, one can download the package with dget using this command:

dget -x
http://mentors.debian.net/debian/pool/main/r/roxterm/roxterm_2.9.5-1.dsc

More information about roxterm can be obtained from
http://roxterm.sourceforge.net

Changes since the last upload:

roxterm (2.9.5-1) unstable; urgency=medium

  * Recognise _NET_WM_DESKTOP special value 0x correctly.
  * Don't crash if EDITOR env variable is unset when editing shortcuts
    (Closes: #771022).

 -- Tony Houghton   Fri, 28 Nov 2014 18:20:06 +0000

Regards,
Tony Houghton


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

Bug#771358: unblock: roxterm/2.9.5-1

[Tony Houghton]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal

Please unblock package roxterm; I have uploaded version 2.9.5-1 to
mentors.debian.net for sponsorship.

This release includes a fix for #771022 which I think is important, or
more severe, because crashing roxterm can cause loss of data in any
applications running in its terminals.

I see that new upstream releases are not normally unblocked, but I hope
that it can be considered in this case, although I am prepared to follow
the rules to the letter if deemed necessary. I am the upstream
maintainer as well as for the Debian package, and the changes are also
necessary upstream and have been committed to the main git branch for
some time. I think having two different version numbers for what is
effectively the same version would be more confusing for users and make
preparing the package a more complicated process for me.

The other change, although not related to a Debian bug, fixes a problem
with workspace handling reported upstream, and involves a small,
unobtrusive code modification. Again, I think trying to leave this
change out would cause more complication in preparing the package than
to leave it in.

debdiff output:

[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in second set of .debs but not in first
-
-rw-r--r--  root/root 
/usr/lib/debug/.build-id/26/936947ed3879eef5b3dde8270eb801b36f9f39.debug
-rw-r--r--  root/root 
/usr/lib/debug/.build-id/44/4b78c6124ee00425fb2622e90872d7fbb1d800.debug
-rw-r--r--  root/root 
/usr/lib/debug/.build-id/a1/d275a3c797b3be2e7fb89ac82b378cb0635172.debug
-rw-r--r--  root/root 
/usr/lib/debug/.build-id/de/ade18468b44efecf87e3974f7731a7b3a5099a.debug


Files in first set of .debs but not in second
-
-rw-r--r--  root/root 
/usr/lib/debug/.build-id/6a/1bda729e9d8223a914e170d19e5add35bbb65c.debug
-rw-r--r--  root/root 
/usr/lib/debug/.build-id/85/759ff0d63a91554bfbfbd32205f5e5ea9a1159.debug
-rw-r--r--  root/root 
/usr/lib/debug/.build-id/c6/91bd8c96d27fe7ad89f6e82ffea4858a2c7c4d.debug
-rw-r--r--  root/root 
/usr/lib/debug/.build-id/c8/1167229518ae6281d2a5fb896252542258d2e7.debug


Control files of package roxterm: lines which differ (wdiff format)
---
Depends: roxterm-gtk3 (>= [-2.9.4-1)-] {+2.9.5-1)+}
Installed-Size: [-40-] {+64+}
Version: [-2.9.4-1-] {+2.9.5-1+}

Control files of package roxterm-common: lines which differ (wdiff format)
--
Installed-Size: [-887-] {+1095+}
Version: [-2.9.4-1-] {+2.9.5-1+}

Control files of package roxterm-gtk2: lines which differ (wdiff format)

Depends: librsvg2-common, roxterm-common (= [-2.9.4-1),-] {+2.9.5-1),+} 
libc6 (>= 2.14), libdbus-1-3 (>= 1.0.2), libdbus-glib-1-2 (>= 0.78), 
libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.37.3), libgtk2.0-0 
(>= 2.24.0), libice6 (>= 1:1.0.0), libpango-1.0-0 (>= 1.14.0), libsm6, 
libvte9 (>= 1:0.28.0), libx11-6

Installed-Size: [-395-] {+431+}
Version: [-2.9.4-1-] {+2.9.5-1+}

Control files of package roxterm-gtk2-dbg: lines which differ (wdiff format)

Depends: roxterm-gtk2 (= [-2.9.4-1)-] {+2.9.5-1)+}
Installed-Size: [-568-] {+611+}
Version: [-2.9.4-1-] {+2.9.5-1+}

Control files of package roxterm-gtk3: lines which differ (wdiff format)

Depends: librsvg2-common, roxterm-common (= [-2.9.4-1),-] {+2.9.5-1),+} 
libc6 (>= 2.14), libdbus-1-3 (>= 1.0.2), libdbus-glib-1-2 (>= 0.78), 
libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.37.3), libgtk-3-0 (>= 
3.9.12), libice6 (>= 1:1.0.0), libpango-1.0-0 (>= 1.14.0), libsm6, 
libvte-2.90-9 (>= 1:0.27.90), libx11-6

Installed-Size: [-391-] {+427+}
Version: [-2.9.4-1-] {+2.9.5-1+}

Control files of package roxterm-gtk3-dbg: lines which differ (wdiff format)

Depends: roxterm-gtk3 (= [-2.9.4-1)-] {+2.9.5-1)+}
Installed-Size: [-494-] {+538+}
Version: [-2.9.4-1-] {+2.9.5-1+}



unblock roxterm/2.9.5-1

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

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


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

Bug#771022: roxterm: Segmentation fault when trying to edit current shortcut scheme

[Tony Houghton]

On 25/11/14 23:18, Lukas F. Hartmann wrote:


I freshly installed roxterm and started it from xfce4-terminal. When going to the 
menu Preferences > Edit Current Shortcuts Scheme, roxterm crashes with: 
Segmentation fault.


I think I know what this is, but for some reason I didn't get round to 
releasing a fixed version. Can you try setting the EDITOR environment 
variable before running roxterm? If it works correctly with that set 
I'll go ahead and release the fixed version which checks EDITOR 
properly, hopefully it'll be just in time for jessie.


If it still crashes with EDITOr set please install roxterm-gtk3-dbg and 
get a stack backtrace. In that case it would probably also help to see 
~/.config/roxterm.sourceforge.net/Global and whichever file it 
references in ~/.config/roxterm.sourceforge.net/Shortcuts.



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

Bug#762011: RFS: roxterm/2.9.4-1

[Tony Houghton]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "roxterm"

* Package name: roxterm
* Version : 2.9.4-1
* Upstream Author : Tony Houghton 
* URL : http://roxterm.sourceforge.net
* License : GPL-2+, LGPL-3+
* Section : x11

It builds these binary packages:

roxterm - Virtual package for roxterm-gtk3
roxterm-common - Multi-tabbed GTK+/VTE terminal emulator - common files
roxterm-gtk2 - Multi-tabbed GTK+/VTE terminal emulator - GTK2 version
roxterm-gtk2-dbg - Debugging symbols for GTK2 version of roxterm
roxterm-gtk3 - Multi-tabbed GTK+/VTE terminal emulator - GTK3 version
roxterm-gtk3-dbg - Debugging symbols for GTK3 version of roxterm

To access further information about this package, please visit the
following URL:

http://mentors.debian.net/package/roxterm


Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/r/roxterm/roxterm_2.9.4-1.dsc


More information about roxterm can be obtained from 
<http://roxterm.sourceforge.net>.


Changes since the last upload:

roxterm (2.9.4-1) unstable; urgency=low

  * Fixed metadata_license and non-default screenshot in appdata.
  * debian/control Build-Depends:
+ Added libtool-bin (Closes: #761785).
+ Added librsvg2-bin.
+ Removed graphicsmagick option:- it can't create favicon.ico.

Regards,
Tony Houghton


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

Bug#756634: RFS: roxterm/2.9.3-1 (was 2.9.1-1)

[Tony Houghton]

retitle 756634 RFS: roxterm/2.9.3-1
thanks

On 08/08/14 09:48, Vincent Cheng wrote:

On Thu, Aug 7, 2014 at 6:06 AM, Tony Houghton  wrote:

Except that wasn't working for me, it said it was incompatible with source
format 3.0 (Quilt) (see above). Or was it specifically my regex or syntax?
It looked OK to me.


Have you tried building roxterm twice in a row in an up-to-date sid
chroot (you're probably already doing this since it's best practice
anyways, but it can't hurt to ask I guess)? Does that error message
still appear then? Ruling out differences in your build environment, I
don't see anything else that could be causing the problem you're
having with extend-diff-ignore.


To be honest I've been a bit lazy and not done that, but I've hopefully 
found another solution to the problem and also made sure to run a 
dist-upgrade before building.


I've changed upstream so that AppInfo.xml only gets written at the 
configure stage if it doesn't already exist, otherwise it only gets 
updated when generating the tarball. The new version is 2.9.3-1, dsc at 
<http://mentors.debian.net/debian/pool/main/r/roxterm/roxterm_2.9.3-1.dsc>.


Fingers crossed this problem is finally laid to rest!


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

Bug#756634: RFS: roxterm/2.9.1-1

[Tony Houghton]

On 07/08/14 09:27, Vincent Cheng wrote:

On Wed, Aug 6, 2014 at 3:01 PM, Tony Houghton  wrote:

retitle 756634 RFS: roxterm/2.9.2-1
thanks

I think I've managed to fix the build now so that the debian package can be
built repeatedly. Most of the changes are upstream so there is a new
version. Please use the new link:

http://mentors.debian.net/debian/pool/main/r/roxterm/roxterm_2.9.2-1.dsc

Thanks for helping to improve this package and to get the new version into
Debian.


Building twice in a row still fails (the date in AppInfo.xml can
change; you can easily just workaround this with extend-diff-ignore,
of course):


Except that wasn't working for me, it said it was incompatible with 
source format 3.0 (Quilt) (see above). Or was it specifically my regex 
or syntax? It looked OK to me.


AppInfo.xml is a hangover from when I used to use the ROX desktop. 
Shipping it in the tarball allows users to see info about the app before 
compiling it. I don't know whether any roxterm users are still using 
that, but I don't want to delete the ROX bits just in case. Next time I 
change upstream I should change the build so that it doesn't regenerate 
AppInfo.xml, and get my update-tags script to change it instead (I'll 
keep forgetting if I rely on doing it manually).


But for now I'd like to fix this without a new upstream release. If I 
can't get extend-diff-ignore to work would it be OK to have debian/rules 
copy the file into debian at the start of the build and restore it 
afterwards? Or is that too nasty a kludge?



Also, if you don't mind me being a bit pedantic, can you run
wrap-and-sort -s so that e.g. it'd be easier to review changes to your
deps and build-deps in debian/control?


OK, one dep per line, that makes sense. Is there anything I should do to 
have it applied to other files generated from control after expanding

${misc:Depends} etc?


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

Bug#756634: RFS: roxterm/2.9.1-1

[Tony Houghton]

retitle 756634 RFS: roxterm/2.9.2-1
thanks

I think I've managed to fix the build now so that the debian package can 
be built repeatedly. Most of the changes are upstream so there is a new 
version. Please use the new link:


http://mentors.debian.net/debian/pool/main/r/roxterm/roxterm_2.9.2-1.dsc

Thanks for helping to improve this package and to get the new version 
into Debian.



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

Bug#756634: RFS: roxterm/2.9.1-1

[Tony Houghton]

On 04/08/14 21:58, Vincent Cheng wrote:

On Mon, Aug 4, 2014 at 12:24 PM, Tony Houghton  wrote:

On 04/08/14 07:11, Vincent Cheng wrote:


On Thu, Jul 31, 2014 at 10:15 AM, Eriberto Mota 
wrote:


 - Allow the content modification of the po/roxterm.pot. To make it,
create the file debian/source/options with this content[1]:

extend-diff-ignore = "^po/roxterm.pot$"



I did that, but I get this warning:

dpkg-source: warning: --extend-diff-ignore:=(^|/)po/roxterm.pot$ is not a
valid option for Dpkg::Source::Package::V3::Quilt


This seems to work (there are a lot more files that dpkg-source
complains about):

extend-diff-ignore =
"^(po/((.*).mo|roxterm.pot)|(.*).xml|Help/(.*)|roxterm.spec)$"


That still doesn't work for me, I get the same warning as before. If it 
works for you I'll upload a new version with that and some other changes 
designed to fix this, but there are still several underlying problems 
with the build, creating things like .mo files in the top source 
directory instead of in the build directory, and building in 
debian/build-gtk* causes the .pot files to show different paths for the 
source files than if it's run in the default upstream build directory. I 
think I really need to switch to a different build system to fix this, 
so that would probably take a few days :-(.



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

Bug#431359: #431359 - gnome-menus: Icons in wrong place

[Tony Houghton]

On 05/08/14 14:12, Pedro Beja wrote:

Hey Tony,

This is an old bug.

it's probably obsolete.
upstream closed as incomplete already.

Should we close it?


I think so, it looks like the reason it was "incomplete" was just 
because somebody didn't report back to confirm that the fix worked.



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

Bug#756634: RFS: roxterm/2.9.1-1

[Tony Houghton]

On 04/08/14 07:11, Vincent Cheng wrote:

On Thu, Jul 31, 2014 at 10:15 AM, Eriberto Mota  wrote:


- Allow the content modification of the po/roxterm.pot. To make it,
create the file debian/source/options with this content[1]:

extend-diff-ignore = "^po/roxterm.pot$"


I did that, but I get this warning:

dpkg-source: warning: --extend-diff-ignore:=(^|/)po/roxterm.pot$ is not 
a valid option for Dpkg::Source::Package::V3::Quilt


and the package still can't be built twice from the same directory. 
Besides roxterm.pot it also detects changes to the po/*.po files. I 
think these get updated with a new POT-Creation-Date header. I can 
probably find a way to prevent these files from being updated with no 
changes other than date stamps, but I'm puzzled why extend-diff-ignore 
doesn't work with format 3.0 (quilt). I can't find any information as to 
why not. Is there another way to make it ignore these?



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

Bug#756634: RFS: roxterm/2.9.1-1

[Tony Houghton]

On 04/08/14 07:11, Vincent Cheng wrote:

On Thu, Jul 31, 2014 at 10:15 AM, Eriberto Mota  wrote:


1. Update DH from 7 to 9.


Thanks for the feedback. I'm not quite sure what that bit means though. 
Do I just need to update Build-Depends to debhelper (>= 9)?



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

Bug#756634: RFS: roxterm/2.9.1-1

[Tony Houghton]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

I am looking for a sponsor for my package "roxterm"

* Package name: roxterm
* Version : 2.9.1-1
* Upstream Author : Tony Houghton 
* URL : http://roxterm.sourceforge.net
* License : GPL-2+, LGPL-3+
* Section : x11

It builds those binary packages:

roxterm - Multi-tabbed GTK+/VTE terminal emulator - virtual package for GTK3
roxterm-common - Multi-tabbed GTK+/VTE terminal emulator - common files
roxterm-gtk2 - Multi-tabbed GTK+/VTE terminal emulator - GTK2 version
roxterm-gtk2-dbg - Debugging symbols for GTK2 version of roxterm
roxterm-gtk3 - Multi-tabbed GTK+/VTE terminal emulator - GTK3 version
roxterm-gtk3-dbg - Debugging symbols for GTK3 version of roxterm

To access further information about this package, please visit the 
following URL:


http://mentors.debian.net/package/roxterm


Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/r/roxterm/roxterm_2.9.1-1.dsc


More information about hello can be obtained from http://www.example.com.

Changes since the last upload:

roxterm (2.9.1-1) unstable; urgency=low

  * Changed default GTK colour scheme:
+ Make bold black (LP: #1340721).
+ Don't set cursor colour due to
  <https://bugzilla.gnome.org/show_bug.cgi?id=695011>.
  * Add support for launching ssh from matching URIs
(based on a patch by Karl E. Jorgensen).
  * Support popular SCM URIs (copy to clipboard only).
  * Fixed background transparency support for recent versions of vte.
  * Don't crash trying to use a copy of an empty profile (Closes: #752253).
  * Allow Shortcuts files to be reloaded and edited as text.
  * Override --tab to false if no match for --title.
  * debian/control: Added Build-Depends on imagemagick, itstool.
  * debian/copyright: Updated year.
  * Support XDG AppData spec.
  * Corrected profile editor page selection when background options
are disabled (doesn't affect Debian).
  * Changed keyboard shortcut for Find Next to avoid clash with New Window.
  * Fixed wrapping of some dialog labels.
  * Exclude logo source xcf (gimp) file from installation.
  * Added GTK & VTE version summary to About dialog.

 -- Tony Houghton   Thu, 31 Jul 2014 15:34:01 +0100

Regards,
Tony Houghton


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

Bug#754828: Bug #754828: Proposed new nvidia-graphics-drivers package FTBS

[Tony Houghton]

Sorry, I forgot to add some context to my previous message. I downloaded 
the svn from message #30 and the above was the tail end of what happened 
when I tried to build it with debuild -b -uc -us.



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

Bug#754828: Bug #754828: Proposed new nvidia-graphics-drivers package FTBS

[Tony Houghton]

dh_testdir
ln -s NVIDIA-Linux-amd64 NVIDIA-Linux
QUILT_PATCHES=debian/patches QUILT_SERIES=series-postunpack quilt 
--quiltrc /dev/null push -a || test $? = 2

Applying patch man-fixes-nvidia-smi.patch
patching file NVIDIA-Linux/nvidia-smi.1

Now at patch man-fixes-nvidia-smi.patch
ls -al
total 128296
drwxr-xr-x 7 tony tony 4096 Jul 19 20:32 .
drwxr-xr-x 8 tony tony 4096 Jul 19 20:31 ..
drwxr-xr-x 6 tony tony12288 Jul 19 20:31 debian
lrwxrwxrwx 1 tony tony   18 Jul 19 20:32 NVIDIA-Linux -> 
NVIDIA-Linux-amd64
lrwxrwxrwx 1 tony tony   26 Jul 19 20:31 NVIDIA-Linux-amd64 -> 
NVIDIA-Linux-x86_64-340.24
lrwxrwxrwx 1 tony tony   36 Jul 19 20:32 NVIDIA-Linux-armhf -> 
NVIDIA-Linux-armv7l-gnueabihf-340.24
drwxr-xr-x 5 tony tony 4096 Jul 19 20:32 
NVIDIA-Linux-armv7l-gnueabihf-340.24
-rwxr-xr-x 1 tony tony 23234463 Jul 19 09:06 
NVIDIA-Linux-armv7l-gnueabihf-340.24.run
lrwxrwxrwx 1 tony tony   23 Jul 19 20:31 NVIDIA-Linux-i386 -> 
NVIDIA-Linux-x86-340.24

drwxr-xr-x 6 tony tony 4096 Jul 19 20:31 NVIDIA-Linux-x86-340.24
-rwxr-xr-x 1 tony tony 38451146 Jul 19 09:01 NVIDIA-Linux-x86-340.24.run
drwxr-xr-x 7 tony tony 4096 Jul 19 20:32 NVIDIA-Linux-x86_64-340.24
-rwxr-xr-x 1 tony tony 69647833 Jul 19 09:05 NVIDIA-Linux-x86_64-340.24.run
drwxr-xr-x 3 tony tony 4096 Jul 19 20:32 .pc
touch unpack-stamp
sed-e '0,/A. Supported\|APPENDIX A: SUPPORTED/d' \
-e '0,/Appendix A. Supported\|APPENDIX A: SUPPORTED/d' \
-e '0,/^Below\|APPENDIX B/{/ 0x/s/.* 
0x\([0-9a-fA-F]\{4\}\).*/10de\1/p};d' \

NVIDIA-Linux/README.txt \
| tr a-f A-F | sort -u > nv-readme.ids
+ cmp -s debian/nv-readme.ids nv-readme.ids
+ diff -u debian/nv-readme.ids nv-readme.ids
--- debian/nv-readme.ids2014-07-19 20:29:40.239950569 +0100
+++ nv-readme.ids2014-07-19 20:32:00.694640823 +0100
@@ -299,6 +299,7 @@
 10DE0E3B
 10DE0F00
 10DE0F01
+10DE0F02
 10DE0FC0
 10DE0FC1
 10DE0FC2
@@ -457,6 +458,7 @@
 10DE1282
 10DE1284
 10DE1286
+10DE1287
 10DE1290
 10DE1291
 10DE1292
+ true
+ : *** Supported PCI IDs have changed. See diff above. Aborting. ***
+ exit 1
debian/rules:104: recipe for target 'nv-readme.ids' failed
make[1]: *** [nv-readme.ids] Error 1
make[1]: Leaving directory 
'/home/tony/src/nvidia-graphics-drivers-340.24.orig'

debian/rules:133: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
debuild: fatal error at line 1364:
dpkg-buildpackage -rfakeroot -D -us -uc -b failed


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

Bug#576792: #576792 - gnome: Unable to automount a vfat formatted USB stick

[Tony Houghton]

On 18/07/14 17:58, Pedro Beja wrote:

Hey,

this is an old bug.

Could you please still reproduce this issue with newer nautilus 
version like 3.4.2-1+build1 or 3.8.2-3 ?


I haven't had any problems like that for a long time. I think the 
underlying system has changed a lot since GNOME 3 replaced GNOME 2 so it 
would hardly be relevant any more.



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

Bug#752253: roxterm: Segmentation Fault with the copy of default profile

[Tony Houghton]

forwarded #752253 https://sourceforge.net/p/roxterm/bugs/84/
thanks

Thanks for the detailed information. Similar crashes had already been 
reported upstream but I couldn't reproduce the problem. This time I 
managed to work out the cause and fix it. I'm working on a new release 
with this and other fixes. If you're stuck with 2.6.5-1 you can fix the 
new config files by adding a keyfile section header. For example, edit:


~/.config/roxterm.sourceforge.net/Profiles/Default01

and add the line:

[roxterm profile]

For colour schemes the header is:

[roxterm colour scheme]

(note British spelling of 'colour')

and for shortcuts:

[roxterm shortcuts scheme]


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