Bug#977237: icewm: background image not shown

[Michal Suchanek]

Source: icewm
Followup-For: Bug #977237

Not a problem with icewm 2.0.0 fro testing.

-- System Information:
Debian Release: 10.7
  APT prefers stable
  APT policy: (990, 'stable'), (800, 'oldoldstable'), (800, 'testing'), (500, 
'oldoldstable'), (400, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#977237: icewm: background image not shown

[Michal Suchanek]

Source: icewm
Followup-For: Bug #977237

Looks like upstream fix for this issue is commit 479a1e1f ("Fixes for
locating background images in theme directory for issue #319.")

Please consider applying it to the version in Debian.

Thanks

Michal

-- System Information:
Debian Release: 10.7
  APT prefers stable
  APT policy: (990, 'stable'), (800, 'oldoldstable'), (800, 'testing'), (500, 
'oldoldstable'), (400, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#977237: icewm: background image not shown

[Michal Suchanek]

Source: icewm
Version: 1.4.3.0~pre-20181030-2
Severity: normal

Hello,

I tried to apply a theme with background image but the image is not
shown. The problem goes away when icewmbg is stopped and restarted in the
theme directory.

-- System Information:
Debian Release: 10.7
  APT prefers stable
  APT policy: (990, 'stable'), (800, 'oldoldstable'), (800, 'testing'), (500, 
'oldoldstable'), (400, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#976797: icewm: The "Terminal" menu does not work with terminal other than xterm

[Michal Suchanek]

Source: icewm
Severity: normal

Hello,

I removed xterm because it is difficult to configure and now I cannot
start terminal with the top menu item in the icewm menu.

The menuitem is hardcoded to "x-terminal-emulator -ls". While -l support
is common -s is specific to xterm. When x-terminal-emulator points to
something else the menu fails to start a terminal.

Please consider dropping the -s.

Thanks

Michal

-- System Information:
Debian Release: 10.7
  APT prefers stable
  APT policy: (990, 'stable'), (800, 'oldoldstable'), (800, 'testing'), (500, 
'oldoldstable'), (400, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#919195: cups: gutenprint driver nmo longer workin after upgrade

[Michal Suchanek]

Package: cups
Version: 2.2.10-3
Severity: normal

Hello,

I upgraded cups from stable to testing and I am no longer able to print.

The driver used with stable was something like 'HP LaserJet 6MP
CUPS+gutenprint v5.2' and after upgrade this driver is no longer
available. There is something like 'HP LaserJet 6MP CUPS+gutenprint v5.3.2'
(just different version number in the string) but it needs to be
selected manually after upgrade. During upgrade I was required to type
root password to do some upgrade but in spite of that the driver is not
upgraded.

Please consider performing upgrade to current gutenprint driver as par
of this postint upgrade process.

Thanks

Michal


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (900, 'stable'), (505, 'oldstable'), (500, 
'oldoldstable'), (171, 'unstable'), (151, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages cups depends on:
ii  cups-client2.2.10-3
ii  cups-common2.2.10-3
ii  cups-core-drivers  2.2.10-3
ii  cups-daemon2.2.10-3
ii  cups-filters   1.21.6-2
ii  cups-ppdc  2.2.10-3
ii  cups-server-common 2.2.10-3
ii  debconf [debconf-2.0]  1.5.69
ii  ghostscript9.26~dfsg-2
ii  libavahi-client3   0.7-4+b1
ii  libavahi-common3   0.7-4+b1
ii  libc6  2.28-2
ii  libcups2   2.2.10-3
ii  libcupsimage2  2.2.10-3
ii  libgcc11:8.2.0-13
ii  libstdc++6 8.2.0-13
ii  libusb-1.0-0   2:1.0.22-2
ii  poppler-utils  0.69.0-2
ii  procps 2:3.3.15-2

Versions of packages cups recommends:
ii  avahi-daemon 0.7-4+b1
ii  colord   1.4.3-3+b1
ii  cups-filters [ghostscript-cups]  1.21.6-2
ii  printer-driver-gutenprint5.3.1-6

Versions of packages cups suggests:
ii  cups-bsd   2.2.10-3
pn  cups-pdf   
pn  foomatic-db-compressed-ppds | foomatic-db  
pn  hplip  
pn  printer-driver-hpcups  
pn  smbclient  
ii  udev   240-2

-- debconf information:
  cupsys/raw-print: true
  cupsys/backend: lpd, socket, usb, snmp, dnssd

Bug#918792: /usr/bin/amixer: amixer cannot set pulseaudiio volume

[Michal Suchanek]

Package: alsa-utils
Version: 1.1.3-1
Severity: normal
File: /usr/bin/amixer

Hello,

the amixer documentation is spotty at best so I cannot tell if this is
supposed to work or how. Anyway, using amixer on hardware card works, on
pulseaudio it fails without any explanation whatsoever. Alsamixer works
on either:

~ $ amixer
Simple mixer control 'Master',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 65536
  Mono:
  Front Left: Playback 0 [0%] [on]
  Front Right: Playback 0 [0%] [on]
Simple mixer control 'Capture',0
  Capabilities: cvolume cswitch cswitch-joined
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 65536
  Front Left: Capture 65536 [100%] [on]
  Front Right: Capture 65536 [100%] [on]
~ $ amixer -c 0 sset Master playback 1dB-
Simple mixer control 'Master',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback 0 - 39
  Mono: Playback 25 [64%] [-21.00dB] [on]
~ $ amixer -c 0 sset Master playback 1dB+
Simple mixer control 'Master',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback 0 - 39
  Mono: Playback 26 [67%] [-19.50dB] [on]
~ $ amixer sset Master playback 1dB-
amixer: Invalid command!


-- System Information:
Debian Release: 9.6
  APT prefers stable
  APT policy: (900, 'stable'), (505, 'oldstable'), (500, 'oldoldstable'), (500, 
'testing'), (171, 'unstable'), (151, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages alsa-utils depends on:
ii  dialog1.3-20160828-2
ii  kmod  23-2
ii  libasound21.1.3-5
ii  libc6 2.28-2
ii  libfftw3-single3  3.3.5-3
ii  libncursesw5  6.0+20161126-1+deb9u2
ii  libsamplerate00.1.8-8+b2
ii  libtinfo5 6.0+20161126-1+deb9u2
ii  lsb-base  9.20161125
ii  whiptail  0.52.19-1+b1

alsa-utils recommends no packages.

alsa-utils suggests no packages.

-- no debconf information

Bug#913434: gscan2pdf: Problem printing to an USB printer using the toolbar button

[Michal Suchanek]

Package: gscan2pdf
Version: 1.6.0-5
Severity: normal

Hello,

I get repeated problem reports from a user trying to print using the
printer button on the toolbar.

The problem is that the USB printer being a hotplugged piece of
hardware does not end up preselected as the device to print on. As other
dummy print queues exist on the system one of these gets selected and no
printer output is observed when pressing the printer button on the
toolbar.

Workaround is to press Ctrl+P, select the hardware printer in the print
dialog, and print the image on the hardware printer. However, the user
tends to forget this workaround because it is not necessary in other
applications (ie Libreoffice).

Can the automatic printer selection be improved so that the toolbar
printer button works automagically as it does in other software?
If not possible can it be removed or made removable?

I am not sure how this problem happens and I cannot reproduce it myself.

Possible problem scenarios include

1) attach scanner, start gscan2pdf, scan, attach printer, press 'print'
button

2) detach printer, start gscan2pdf (gscan2pdf detects missing hardware
printer and selects another queue), quit gscan2pdf (printer selection
saved), start gscan2pdf with printer attached (dummy queue still
selected)

It might be helpful to not save print settings when nothing was printed
if something like that is done in the application.

As I cannot reproduce the problem myself the above is only guess based
on problem description from the user. If you cannot reproduce the issue
I can try to get a hardware printer to provide more accurate
description.

Thanks

Michal


-- System Information:
Debian Release: 9.5
  APT prefers stable
  APT policy: (900, 'stable'), (505, 'oldstable'), (500, 'oldoldstable'), (500, 
'testing'), (171, 'unstable'), (151, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages gscan2pdf depends on:
ii  imagemagick8:6.9.7.4+dfsg-11+deb9u5
ii  imagemagick-6.q16 [imagemagick]8:6.9.7.4+dfsg-11+deb9u5
ii  libconfig-general-perl 2.63-1
ii  libdate-calc-perl  6.4-1
ii  libfilesys-df-perl 0.92-6+b1
ii  libgoo-canvas-perl 0.06-2+b3
ii  libgtk2-ex-simple-list-perl0.50-2
ii  libgtk2-imageview-perl 0.05-2+b3
ii  libhtml-parser-perl3.72-3
ii  libimage-magick-perl   8:6.9.7.4+dfsg-11+deb9u5
ii  liblist-moreutils-perl 0.416-1+b1
ii  liblocale-gettext-perl 1.07-3+b1
ii  liblog-log4perl-perl   1.48-1+deb9u1
ii  libossp-uuid-perl [libdata-uuid-perl]  1.6.2-1.5+b4
ii  libpdf-api2-perl   2.030-1
ii  libproc-processtable-perl  0.53-2
ii  libreadonly-perl   2.050-1
ii  librsvg2-common2.40.16-1+b1
ii  libsane-perl   0.05-2+b4
ii  libset-intspan-perl1.19-1
ii  libtiff-tools  4.0.8-2+deb9u2
ii  libtry-tiny-perl   0.28-1
ii  sane-utils 1.0.25-4.1

Versions of packages gscan2pdf recommends:
ii  djvulibre-bin  3.5.27.1-7
ii  libgtk2-ex-podviewer-perl  0.18-1
ii  sane   1.0.14-12
ii  tesseract-ocr  3.04.01-5
ii  unpaper6.1-2+b1
ii  xdg-utils  1.1.1-1+deb9u1

gscan2pdf suggests no packages.

-- no debconf information

Bug#886551: xserver-xorg-input-wacom: log spam in Xorg.log

[Michal Suchanek]

Package: xserver-xorg-input-wacom
Version: 0.34.0-1
Severity: normal

Hello,

while diagnosing unrelated issue I noticed megabytes of

[  4407.128] (EE) BUG: triggered 'if (in_input_thread())'
[  4407.128] (EE) BUG: ../../../../os/io.c:661 in WriteToClient()
[  4407.128] (EE)  WriteToClient called from input thread *
[  4407.128] (EE) 
[  4407.128] (EE) Backtrace:
[  4407.128] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x556b0650665a]
[  4407.128] (EE) 1: /usr/lib/xorg/Xorg (WriteToClient+0x162) [0x556b06509c72]
[  4407.128] (EE) 2: /usr/lib/xorg/Xorg (WriteEventsToClient+0x252) 
[0x556b063acbb2]
[  4407.128] (EE) 3: /usr/lib/xorg/Xorg (TryClientEvents+0x120) [0x556b063acd50]
[  4407.129] (EE) 4: /usr/lib/xorg/Xorg (0x556b0634d000+0x634ba) 
[0x556b063b04ba]
[  4407.129] (EE) 5: /usr/lib/xorg/Xorg (DeliverEventsToWindow+0x1d7) 
[0x556b063b07a7]
[  4407.129] (EE) 6: /usr/lib/xorg/Xorg (0x556b0634d000+0x146a79) 
[0x556b06493a79]
[  4407.129] (EE) 7: /usr/lib/xorg/Xorg (0x556b0634d000+0x1524ef) 
[0x556b0649f4ef]
[  4407.129] (EE) 8: /usr/lib/xorg/Xorg (XIChangeDeviceProperty+0x358) 
[0x556b0649fea8]
[  4407.129] (EE) 9: /usr/lib/xorg/modules/input/wacom_drv.so 
(0x7f3dc0553000+0x10df9) [0x7f3dc0563df9]
[  4407.129] (EE) 10: /usr/lib/xorg/modules/input/wacom_drv.so 
(0x7f3dc0553000+0x76a7) [0x7f3dc055a6a7]
[  4407.129] (EE) 11: /usr/lib/xorg/modules/input/wacom_drv.so 
(0x7f3dc0553000+0x8864) [0x7f3dc055b864]
[  4407.129] (EE) 12: /usr/lib/xorg/modules/input/wacom_drv.so 
(0x7f3dc0553000+0xe38f) [0x7f3dc056138f]
[  4407.129] (EE) 13: /usr/lib/xorg/modules/input/wacom_drv.so 
(0x7f3dc0553000+0x616b) [0x7f3dc055916b]
[  4407.129] (EE) 14: /usr/lib/xorg/modules/input/wacom_drv.so 
(0x7f3dc0553000+0x63a6) [0x7f3dc05593a6]
[  4407.129] (EE) 15: /usr/lib/xorg/Xorg (0x556b0634d000+0x1bb7cc) 
[0x556b065087cc]
[  4407.129] (EE) 16: /usr/lib/xorg/Xorg (0x556b0634d000+0x1bdeb1) 
[0x556b0650aeb1]
[  4407.129] (EE) 17: /usr/lib/xorg/Xorg (0x556b0634d000+0x1bb626) 
[0x556b06508626]
[  4407.129] (EE) 18: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f3dcef9e000+0x7494) [0x7f3dcefa5494]
[  4407.129] (EE) 19: /lib/x86_64-linux-gnu/libc.so.6 (clone+0x3f) 
[0x7f3dcece7aff]
[  4407.129] (EE) 

are logged in Xorg.log

Can you please update to fixed version of the driver or disable the spam?

Thanks

-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (900, 'stable'), (505, 'oldstable'), (500, 'oldoldstable'), (500, 
'testing'), (171, 'unstable'), (151, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages xserver-xorg-input-wacom depends on:
ii  libc6  2.24-11+deb9u1
ii  libudev1   232-25+deb9u1
ii  libx11-6   2:1.6.4-3
ii  libxext6   2:1.3.3-1+b2
ii  libxi6 2:1.7.9-1
ii  libxinerama1   2:1.1.3-1+b3
ii  libxrandr2 2:1.5.1-1
ii  xserver-xorg-core [xorg-input-abi-24]  2:1.19.2-1+deb9u2

xserver-xorg-input-wacom recommends no packages.

Versions of packages xserver-xorg-input-wacom suggests:
ii  xinput  1.6.2-1+b1

-- no debconf information

Bug#886233: vlc: VLC cannot be instaled with recent Mesa

[Michal Suchanek]

On 3 January 2018 at 16:28, Sebastian Ramacher <sramac...@debian.org> wrote:
> Control: found -1 2.2.4-13
> Control: notfound -1 2.2.6-6
> Control: forcemerge -1 855117
>
> On 2018-01-03 14:29:43, Michal Suchanek wrote:
>> Package: src:vlc
>> Followup-For: Bug #886233
>>
>> Actually, the issue is with libegl1-mesa which does not have the
>> corresponding "vendor neutral" package.
>
> vlc (2.2.5-2) experimental; urgency=medium
>
>   [ Mateusz Łukasik ]
>   * debian/{control,rules,vlc-plugin-video-output.install}: Disable OpenGL
> ES 1 support, mesa has dropped it. (Closes: #855117)
>
> So this is a duplicate of #855117. I don't think this is worth a backport to
> stable if that's what you are asking for. After all, mesa in stable is at
> version 13.

Yes, the stable mesa and stable vlc work together. The part that this
is fixed in 2.2.5 in experimental and is still broken in 2.2.7 in
stable is quite confusing, though.

I probably installed 2.2.6 from unstable or experimental together with
newer mesa when my graphics was broken and now the 'upgrade' to stable
version does not work.

I think it still makes sense to remove the dependency in stable. It
makes it possible to test newer mesa with stable vlc in case of
graphics issues. As things are now you need to rebuild vlc to backport
recent mesa which is not exactly nice.

Thanks

Michal

Bug#884466: mesa: firefox, thunderbird, chromium don't start with mesa 17.3.0-1

[Michal Suchanek]

Package: libglx-mesa0
Followup-For: Bug #884466

This works for me with [AMD/ATI] Baffin [Radeon RX 460] (rev cf)

I can open chromium and firefox just fine.

-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (900, 'stable'), (505, 'oldstable'), (500, 'oldoldstable'), (500, 
'testing'), (171, 'unstable'), (151, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages libglx-mesa0:amd64 depends on:
ii  libc62.24-11+deb9u1
ii  libdrm2  2.4.89-1
ii  libexpat12.2.0-2+deb9u1
ii  libgl1-mesa-dri  17.3.1-1
ii  libglapi-mesa17.3.1-1
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb-dri2-01.12-1
ii  libxcb-dri3-01.12-1
ii  libxcb-glx0  1.12-1
ii  libxcb-present0  1.12-1
ii  libxcb-sync1 1.12-1
ii  libxcb-xfixes0   1.12-1
ii  libxcb1  1.12-1
ii  libxdamage1  1:1.1.4-2+b3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxshmfence11.2-1+b2
ii  libxxf86vm1  1:1.1.4-1+b2
ii  zlib1g   1:1.2.8.dfsg-5

libglx-mesa0:amd64 recommends no packages.

libglx-mesa0:amd64 suggests no packages.

-- no debconf information

Bug#886233: vlc: VLC cannot be instaled with recent Mesa

[Michal Suchanek]

Package: src:vlc
Followup-For: Bug #886233

Actually, the issue is with libegl1-mesa which does not have the
corresponding "vendor neutral" package.

Anyway, the issue no longer occurs with vlc 3 which does not require the
libegl1 library.

-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (900, 'stable'), (505, 'oldstable'), (500, 'oldoldstable'), (500, 
'testing'), (171, 'unstable'), (151, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages vlc depends on:
ii  vlc-bin  3.0.0~rc2-2
ii  vlc-l10n 3.0.0~rc2-2
ii  vlc-plugin-base  3.0.0~rc2-2
ii  vlc-plugin-qt3.0.0~rc2-2
ii  vlc-plugin-video-output  3.0.0~rc2-2

Versions of packages vlc recommends:
ii  vlc-plugin-notify  3.0.0~rc2-2
ic  vlc-plugin-samba   2.2.5-1
ii  vlc-plugin-skins2  3.0.0~rc2-2
ii  vlc-plugin-video-splitter  3.0.0~rc2-2
ii  vlc-plugin-visualization   3.0.0~rc2-2

vlc suggests no packages.

Versions of packages libvlc-bin depends on:
ii  libc62.24-11+deb9u1
ii  libvlc5  3.0.0~rc2-2

Versions of packages libvlc5 depends on:
ii  libc62.24-11+deb9u1
ii  libvlccore9  3.0.0~rc2-2

Versions of packages libvlc5 recommends:
ii  libvlc-bin  3.0.0~rc2-2

Versions of packages libvlccore8 depends on:
ii  dpkg 1.18.24
ii  libc62.24-11+deb9u1
ii  libdbus-1-3  1.10.24-0+deb9u1
ii  libidn11 1.33-1

Versions of packages libvlccore8 recommends:
ii  libproxy-tools  0.4.14-2

Versions of packages vlc-bin depends on:
ii  libc6   2.24-11+deb9u1
ii  libvlc-bin  3.0.0~rc2-2
ii  libvlc5 3.0.0~rc2-2

Versions of packages vlc-plugin-base depends on:
ii  liba52-0.7.4 0.7.4-19
ii  libarchive13 3.2.2-2
ii  libaribb24-0 1.0.3-1
ii  libasound2   1.1.3-5
ii  libass9  1:0.14.0-1
ii  libavahi-client3 0.6.32-2
ii  libavahi-common3 0.6.32-2
ii  libavc1394-0 0.5.4-4+b1
ii  libavcodec57 7:3.4.1-1+b1
ii  libavformat577:3.4.1-1+b1
ii  libavutil55  7:3.4.1-1+b1
ii  libbasicusageenvironment12017.10.28-2
ii  libbluray2   1:1.0.2-1
ii  libc62.24-11+deb9u1
ii  libcairo21.14.8-1
ii  libcddb2 1.3.2-5
ii  libchromaprint1  1.4.2-1
ii  libcrystalhd31:0.0~git20110715.fdd2f19-12
ii  libdbus-1-3  1.10.24-0+deb9u1
ii  libdc1394-22 2.2.5-1
ii  libdca0  0.0.5-10
ii  libdvbpsi10  1.3.0-5
ii  libdvdnav4   5.0.3-3
ii  libdvdread4  5.0.3-2
ii  libebml4v5   1.3.5-2
ii  libfaad2 2.8.0~cvs20161113-1
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.12.6-0.1
ii  libfreetype6 2.6.3-3.2
ii  libfribidi0  0.19.7-1+b1
ii  libgcc1  1:7.2.0-18
ii  libgcrypt20  1.8.1-4
ii  libglib2.0-0 2.50.3-2
ii  libgnutls30  3.5.8-5+deb9u3
ii  libgpg-error01.26-2
ii  libgroupsock82017.10.28-2
ii  libharfbuzz0b1.4.2-1
ii  libjpeg62-turbo  1:1.5.1-2
ii  libkate1 0.4.1-7+b1
ii  liblirc-client0  0.9.4c-9
ii  liblivemedia61   2017.10.28-2
ii  liblua5.2-0  5.2.4-1.1+b2
ii  libmad0  0.15.1b-8
ii  libmatroska6v5   1.4.5-2
ii  libmicrodns0 0.0.3-3
ii  libmpcdec6   2:0.1~r495-1+b1
ii  libmpeg2-4   0.5.1-7+b2
ii  libmpg123-0  1.23.8-1+b1
ii  libmtp9  1.1.13-1
ii  libncursesw5 6.0+20161126-1+deb9u1
ii  libnfs8  1.11.0-2
ii  libogg0  1.3.2-1
ii  libopenmpt-modplug1  0.2.7386~beta20.3-3+deb9u2
ii  libopus0 1.2~alpha2-1
ii  libpng16-16  1.6.28-1
ii  libpostproc547:3.4.1-1+b1
ii  libprotobuf-lite10   3.0.0-9
ii  libpulse010.0-1+deb9u1
ii  libraw1394-11 

Bug#886233: vlc: VLC cannot be instaled with recent Mesa

[Michal Suchanek]

Package: src:vlc
Version: 2.2.6-6
Severity: important

Hello,

VLC 2.2.7+ video output depends on libgles2 which is present in Mesa 13-
making VLC uninstallable with Mesa 17.

So please make the gles output a separate package if possible or do not
build it.

Thanks

-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (900, 'stable'), (505, 'oldstable'), (500, 'oldoldstable'), (500, 
'testing'), (171, 'unstable'), (151, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages vlc depends on:
ii  vlc-bin  2.2.6-6
ii  vlc-l10n 2.2.6-6
ii  vlc-plugin-base  2.2.6-6
ii  vlc-plugin-qt2.2.6-6
ii  vlc-plugin-video-output  2.2.6-6

Versions of packages vlc recommends:
ii  vlc-plugin-notify  2.2.6-6
pn  vlc-plugin-samba   
ii  vlc-plugin-skins2  2.2.6-6
ii  vlc-plugin-video-splitter  2.2.6-6
ii  vlc-plugin-visualization   2.2.6-6

vlc suggests no packages.

Versions of packages libvlc-bin depends on:
ii  libc62.24-11+deb9u1
ii  libvlc5  2.2.7-1~deb9u1

Versions of packages libvlc5 depends on:
ii  dpkg 1.18.24
ii  libc62.24-11+deb9u1
ii  libvlccore8  2.2.6-6

Versions of packages libvlc5 recommends:
ii  libvlc-bin  2.2.6-6

Versions of packages libvlccore8 depends on:
ii  libc62.24-11+deb9u1
ii  libdbus-1-3  1.10.24-0+deb9u1
ii  libidn11 1.33-1

Versions of packages libvlccore8 recommends:
ii  libproxy-tools  0.4.14-2

Versions of packages vlc-bin depends on:
ii  libc6   2.24-11+deb9u1
ii  libvlc-bin  2.2.6-6
ii  libvlc5 2.2.7-1~deb9u1

Versions of packages vlc-plugin-base depends on:
ii  liba52-0.7.4   0.7.4-19
ii  libasound2 1.1.3-5
ii  libass91:0.14.0-1
ii  libavahi-client3   0.6.32-2
ii  libavahi-common3   0.6.32-2
ii  libavc1394-0   0.5.4-4+b1
ii  libbasicusageenvironment1  2017.10.28-2
ii  libbluray2 1:1.0.2-1
ii  libbz2-1.0 1.0.6-8.1
ii  libc6  2.24-11+deb9u1
ii  libcairo2  1.14.8-1
ii  libcddb2   1.3.2-5
ii  libcdio13  0.83-4.3+b1
ii  libchromaprint11.4.2-1
ii  libcrystalhd3  1:0.0~git20110715.fdd2f19-12
ii  libdbus-1-31.10.24-0+deb9u1
ii  libdc1394-22   2.2.5-1
ii  libdca00.0.5-10
ii  libdvbpsi101.3.0-5
ii  libdvdnav4 5.0.3-3
ii  libdvdread45.0.3-2
ii  libebml4v5 1.3.5-2
ii  libfaad2   2.8.0~cvs20161113-1
ii  libflac8   1.3.2-1
ii  libfontconfig1 2.12.6-0.1
ii  libfreetype6   2.6.3-3.2
ii  libfribidi00.19.7-1+b1
ii  libgcc11:7.2.0-18
ii  libgcrypt201.7.6-2+deb9u2
ii  libglib2.0-0   2.50.3-2
ii  libgme00.6.0-4
ii  libgnutls303.5.8-5+deb9u3
ii  libgpg-error0  1.26-2
ii  libgroupsock8  2017.10.28-2
ii  libgsm11.0.13-4+b2
ii  libjpeg62-turbo1:1.5.1-2
ii  libkate1   0.4.1-7+b1
ii  liblirc-client00.9.4c-9
ii  liblivemedia58 2017.09.12-1
ii  liblua5.2-05.2.4-1.1+b2
ii  liblzma5   5.2.2-1.2+b1
ii  libmad00.15.1b-8
ii  libmatroska6v5 1.4.5-2
ii  libmp3lame03.99.5+repack1-9+b2
ii  libmpcdec6 2:0.1~r495-1+b1
ii  libmpeg2-4 0.5.1-7+b2
ii  libmtp91.1.13-1
ii  libncursesw5   6.0+20161126-1+deb9u1
ii  libogg01.3.2-1
ii  libopenmpt-modplug10.2.7386~beta20.3-3+deb9u2
ii  libopus0   1.2~alpha2-1
ii  libpng16-161.6.28-1
ii  libpulse0  10.0-1+deb9u1
ii  libraw1394-11  2.1.2-1+b1
ii  libresid-builder0c2a   2.1.1-15
ii  librsvg2-2 2.40.16-1+b1
ii  librtmp1   2.4+20151223.gitfa8646d.1-1+b1
ii  libsamplerate0 0.1.8-8+b2
ii  libsdl-image1.21.2.12-5+b8
ii  libsdl1.2debian1.2.15+dfsg1-4
ii  libshine3  3.1.0-5
ii  libshout3  2.3.1-3
ii  libsidplay22.1.1-15
ii  libsnappy1v5   1.1.3-3
ii  libsndio6.11.1.0-3
ii  libspeex1  1.2~rc1.2-1+b2
ii  libspeexdsp1   1.2~rc1.2-1+b2
ii  libssh-gcrypt-40.7.3-2
ii  libssh2-1  1.7.0-1
ii  libstdc++6 6.3.0-18
ii  libtag1v5  1.11.1+dfsg.1-0.1
ii  libtheora0 

Bug#885860: wine registers mime handlers with too high priority

[Michal Suchanek]

Package: wine
Followup-For: Bug #885860

Hello,

indeed removing files previously created by wine I can no longer
reproduce the problem. I used many older versions of wine so one of them
created these files.

It is unfortunate that winemenubuilder cannot identify the old files and
remove them when updating the associations but this should not reappear
on new systems at least.

Thanks

-- Package-specific info:
/usr/bin/wine points to /usr/bin/wine-stable.

-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (900, 'stable'), (505, 'oldstable'), (500, 'oldoldstable'), (500, 
'testing'), (171, 'unstable'), (151, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages wine depends on:
ii  wine32  1.8.7-2
ii  wine64  1.8.7-2

wine recommends no packages.

Versions of packages wine suggests:
ii  dosbox   0.74-4.2+b2
pn  playonlinux  
pn  winbind  
ii  wine-binfmt  1.8.7-2
ii  winetricks   0.0+20170101-1

Versions of packages wine is related to:
ii  fonts-wine   1.8.7-2
ii  wine 1.8.7-2
ii  wine-development [wine]  3.0~rc1-1
ii  wine32   1.8.7-2
ii  wine64   1.8.7-2

-- no debconf information

Bug#885860: wine registers mime handlers with too high priority

[Michal Suchanek]

Package: wine
Version: 1.8.7-2
Severity: important

Hello,

once you install wine text files open in notepad, pictures, PDFs and
HTML files in winebrowser.

This breaks the desktop integration.

It is fine to install these alternatives as very low priority but the
priority for thes slow-starting nearly useless applications in the
highest. Higher than gedit, evince, gqview, imagemagick, ..

This is broken

Please fix the priority of wine pre-installed applicatins to work with
the rest of the distribution.

Thanks

-- Package-specific info:
/usr/bin/wine points to /usr/bin/wine-stable.

-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (900, 'stable'), (505, 'oldstable'), (500, 'oldoldstable'), (500, 
'testing'), (171, 'unstable'), (151, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages wine depends on:
ii  wine32  1.8.7-2
ii  wine64  1.8.7-2

wine recommends no packages.

Versions of packages wine suggests:
ii  dosbox   0.74-4.2+b2
pn  playonlinux  
pn  winbind  
ii  wine-binfmt  1.8.7-2
ii  winetricks   0.0+20170101-1

Versions of packages wine is related to:
ii  fonts-wine   1.8.7-2
ii  wine 1.8.7-2
ii  wine-development [wine]  3.0~rc1-1
ii  wine32   1.8.7-2
ii  wine64   1.8.7-2

-- no debconf information

Bug#861857: chromium: when posting an inaccessible file as part of a form submission chromium claims the remote site is not accessible

[Michal Suchanek]

Package: chromium
Version: 61.0.3163.100-1~deb9u1
Followup-For: Bug #861857

Hello,

The exact error message is:

This site can’t be reached

The webpage at http://paste.debian.net/ might be temporarily down or it
may have moved permanently to a new web address.
ERR_ACCESS_DENIED


which is the result of

echo Hello > test.txt

chmod 000 test.txt

upload test.txt as paste to paste.debian.net

This is also an issue with google-chrome.

Best regards

Michal

Bug#879277: systemd: After resume from suspend to ram system immediiately hibernates

[Michal Suchanek]

Hello,

On 22 October 2017 at 14:14, Michael Biebl <bi...@debian.org> wrote:
> Am 22.10.2017 um 13:43 schrieb Michal Suchanek:

> Please try downgrading the kernel to the previous version and report back.

Downgrading the kernel is not really an option. It was broken so I did
not keep a backup and the build is gone from the archives.

> That said, you can enable persistent journal by creating the directory
> following the instructions in /usr/share/doc/systemd/README.Debian.gz

I will keep that filed in case I do have some logs to collect.

>
>> However, I noticed that I have hibernate logs and comparing earlier
>> hibernate logs with recent ones I can see that earlier logs have an
>> error saying the s2d device is not available while recent hibernate
>> logs say the system was suspended to disk.
>>
>> Disabling any suspend methods in hibernate resolves the problem.
>>
>
> What exactly did you disable and how?

All suspend methods in /etc/hibernate.conf

> Are you using the hibernate tool from the "hibernate" package?

I would not say exactly using. I have it installed and hooked to the
acpid scripts but long time ago when I upgraded to Debian version that
requires systemd it stopped working because systemd took over handling
the power key.

Now it is obviously hooked to something somewhere again because it
runs in parallel to the systemd power button handling.

This is quite unfortunate. I am not aware of doing anything that would
re-enable it. My expectation is that only one package handles power
button.

Thanks

Michal

Bug#879277: systemd: After resume from suspend to ram system immediiately hibernates

[Michal Suchanek]

On 21 October 2017 at 17:13, Michael Biebl <bi...@debian.org> wrote:
> Control: severity -1 normal
> Control: tags -1 moreinfo
>
> Am 21.10.2017 um 14:29 schrieb Michal Suchanek:
>> Package: systemd
>> Version: 232-25+deb9u1
>> Severity: important
>>
>> Hello,
>>
>> after recent upgrade I was unable to wake up from suspend.
>
> Which packages were updated?

Hard to tell. Have any handy utility to get that from dpkg log?

With grepping I found the only remotely related packag is dbus and of
course the kernel.

> systemd in stable was not updated for 9.2.

Yes, it seems the case.

> Why do you suspect that systemd is the culprit

Because it insists on doing everything so when anything breaks it's
systemd's fault.

In particular it took over handling power key so when power key
handling breaks it's systemd's fault.

>
>> Examining the system closely during suspend/resume the system suspends,
>> then resumes, then hibernates, and tehn fails to resume from
>> hibernation. It is quite possible that in some cases it hibernates
>> straight away and fails to resume from hibernatiion on next boot
>> wiithout ever suspending.
>>
>
> Are you using hybrid suspend?

How do I tell? I told systemd to suspend my system when power key is pressed.

Even if it used hybrid suspend it should suspend to disk and ram at
the same time and not one ofter another.

> What is triggering the
> - suspend
power key
> - resume
power key
> - hibernate
bug
> - resume from hibernation
power key
>
> A debug log for logind might be helpful as well. For that run
> systemctl edit systemd-logind, then add
> [Service]
> Environment=SYSTEMD_LOG_LEVEL=debug
>
> This will create a file
> /etc/systemd/system/systemd-logind.service.d/override.conf. Then reboot

Yes, right. logind cannot be reconfigured while system is running?

I guess 'telinit q' or 'systemctl daemon-reload' followed by restart
of logind should work as well.

> and attach the output of
> journalctl -b -u systemd-logind.service
> after you reproduced the issue.

It does not contain any relevant data because -b selects the current
boot and the system suspended in the previous boot.

Using -b -1 gives

Specifying boot ID has no effect, no persistent journal was found

So much for producing logs of the issue.

However, I noticed that I have hibernate logs and comparing earlier
hibernate logs with recent ones I can see that earlier logs have an
error saying the s2d device is not available while recent hibernate
logs say the system was suspended to disk.

Disabling any suspend methods in hibernate resolves the problem.

Looking through the logind log I see no reference to hibernate, though.

So what runs hibernate(8) is a mystery.

And presumably hibernate putting the system to sleep should avoid
systemd doing the same or the other way around.

Best regards

Michal

Bug#800573: heimdall-flash: fails to download PIT for Galaxy S5 (G900T3)

[Michal Suchanek]

Package: heimdall-flash
Followup-For: Bug #800573

Hello,

I see similar problem with Galaxy J5 SM-510F.

It is resolved by upgrading to heimdall 1.4.2

You can try the package here:
https://build.opensuse.org/package/show/home:michals:debian/heimdall

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'oldoldstable'), (500, 'testing'), (500, 
'oldstable'), (171, 'unstable'), (151, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages heimdall-flash depends on:
ii  libc6 2.24-11+deb9u1
ii  libgcc1   1:6.3.0-18
ii  libstdc++66.3.0-18
ii  libusb-1.0-0  2:1.0.21-1

heimdall-flash recommends no packages.

heimdall-flash suggests no packages.

-- no debconf information

Bug#872788: heimdall-flash: new upstream release 1.4.2

[Michal Suchanek]

Package: heimdall-flash
Version: 1.4.1-2+b1
Severity: normal

Hello,

new upstream release is available.

Package at
https://build.opensuse.org/package/show/home:michals:debian/heimdall

Please update the Debian package

Thanks

Michal

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'oldoldstable'), (500, 'testing'), (500, 
'oldstable'), (171, 'unstable'), (151, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages heimdall-flash depends on:
ii  libc6 2.24-11+deb9u1
ii  libgcc1   1:6.3.0-18
ii  libstdc++66.3.0-18
ii  libusb-1.0-0  2:1.0.21-1

heimdall-flash recommends no packages.

heimdall-flash suggests no packages.

-- no debconf information

Bug#862543: /bin/systemctl: no tab completion for systemctl

[Michal Suchanek]

Package: systemd
Version: 232-22
Severity: important
File: /bin/systemctl

Hello,

unlike init systemctl has services that can be in about half dozen
places and cannot be started directly. To boot the argunet order is
inverted compared to any other service manipulation command to date.

This makes it very important to get argument completion working for
systemctl but there is none whatsoever. Not even for the arguments.

-- Package-specific info:

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (900, 'testing'), (700, 'stable'), (600, 'oldstable'), (171, 
'unstable'), (151, 'experimental')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages systemd depends on:
ii  adduser 3.115
ii  libacl1 2.2.52-3+b1
ii  libapparmor12.11.0-3
ii  libaudit1   1:2.6.7-2
ii  libblkid1   2.29.2-1
ii  libc6   2.24-10
ii  libcap2 1:2.25-1
ii  libcryptsetup4  2:1.7.3-3
ii  libgcrypt20 1.7.6-1
ii  libgpg-error0   1.26-2
ii  libidn111.33-1
ii  libip4tc0   1.6.0+snapshot20161117-6
ii  libkmod223-2
ii  liblz4-10.0~r131-2+b1
ii  liblzma55.2.2-1.2+b1
ii  libmount1   2.29.2-1
ii  libpam0g1.1.8-3.5
ii  libseccomp2 2.3.1-2.1
ii  libselinux1 2.6-3+b1
ii  libsystemd0 232-22
ii  mount   2.29.2-1
ii  util-linux  2.29.2-1

Versions of packages systemd recommends:
ii  dbus1.10.18-1
ii  libpam-systemd  232-22

Versions of packages systemd suggests:
ii  policykit-10.105-17
pn  systemd-container  
ii  systemd-ui 3-4+b1

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.130
ii  udev 232-22

-- no debconf information

Bug#861857: chromium: when posting an inaccessible file as part of a form submission chromium claims the remote site is not accessible

[Michal Suchanek]

Package: chromium
Version: 58.0.3029.81-1
Severity: normal

Hello,

I tried to attach a log file as part of a bugzilla bug report form and
the log file is not accessible from my user account. The result is
chromium claims that form post url is inaccessible while in fact the
submitted local file is inaccessible.

Please correct the error message

Thanks

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (900, 'testing'), (700, 'stable'), (600, 'oldstable'), (171, 
'unstable'), (151, 'experimental')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages chromium depends on:
ii  libasound2   1.1.3-5
ii  libatk1.0-0  2.22.0-1
ii  libavcodec57 7:3.2.4-1
ii  libavformat577:3.2.4-1
ii  libavutil55  7:3.2.4-1
ii  libc62.24-10
ii  libcairo21.14.8-1
ii  libcups2 2.2.1-8
ii  libdbus-1-3  1.10.18-1
ii  libevent-2.0-5   2.0.21-stable-3
ii  libexpat12.2.0-2
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgcc1  1:6.3.0-14
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgtk2.0-0  2.24.31-2
ii  libharfbuzz0b1.4.2-1
ii  libicu57 57.1-6
ii  libjpeg62-turbo  1:1.5.1-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26.2-1
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpng16-16  1.6.28-1
ii  libpulse010.0-1
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.3-3
ii  libstdc++6   6.3.0-14
ii  libvpx4  1.6.1-3
ii  libwebp6 0.5.2-1
ii  libwebpdemux20.5.2-1
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.14-1+b4
ii  libxdamage1  1:1.1.4-2+b3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-2.2
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.29-2.1
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.3-1
ii  x11-utils7.7+3+b1
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
pn  chromium-driver
pn  chromium-l10n  
pn  chromium-shell 
pn  chromium-widevine  

-- no debconf information

Bug#857013: reportbug: Attaching patch

[Michal Suchanek]

On 19 April 2017 at 03:07, Sandro Tosi <mo...@debian.org> wrote:
> On Thu, Apr 13, 2017 at 4:52 AM, Michal Suchanek <hramr...@gmail.com> wrote:
>> --- /usr/lib/python3/dist-packages/reportbug/utils.py   2017-04-13 
>> 10:49:24.126454516 +0200
>> +++ /usr/lib/python3/dist-packages/reportbug/utils.py~  2017-04-13 
>> 10:49:17.663966502 +0200
..
> is this in reverse order?

Yes, you can see that the file marked with +++ is a backup file and
has the current code.

Thanks

Michal

Bug#829255: oss4-dkms: Fails to build for 4.6.0-1-amd64

[Michal Suchanek]

Package: oss4-dkms
Followup-For: Bug #829255

Hello,

the patch works for me with linux 4.9 and 4.10.

Please uppload fixed package to distributions that use the new kernels.

Thanks

Michal

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (900, 'testing'), (700, 'stable'), (600, 'oldstable'), (171, 
'unstable'), (151, 'experimental')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages oss4-dkms depends on:
ii  dkms  2.3-2
ii  dpkg-dev  1.18.23
ii  libc6-dev [libc-dev]  2.24-9
ii  oss4-base 4.2-build2010-2

Versions of packages oss4-dkms recommends:
ii  linux-headers-amd64  4.9+79

oss4-dkms suggests no packages.

-- no debconf information

Bug#860495: chromium: cannot sign into Ankama Zendesk

[Michal Suchanek]

Package: chromium
Version: 58.0.3029.68-1
Severity: normal

Hello,

there is a problem with Chromium on Debian and Ankama Zendesk system.

When you complete registration to their Zendesk and log in with your
email and password the tab just freezes.

It did not work even with version 57 of Chrome which broke extensions so
I guess it's safe to say extensions have nothing to do with it.

It works with Google Chrome 57 on same machine.

To test this you can go to https://support.ankama.com/hc/en-us press
"Sign In" button, go to "Sign Up" link, enter an email address, once you
get confirmation e-mail set a password using the link you received.

Then in any other browser I tried I can log in with that e-mail and
password combination but in Chrome on Debian the tab with Zendesk just
freezes after pressing the "Sign In" button with correct e-mail and
password combination.

I can use Google Chrome as a workaround but I guess it would be nice to
track down and fix this. I have no idea if this affects other Zendesk
installations.

Thanks

Michal

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

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

Versions of packages chromium depends on:
ii  libasound2   1.1.3-5
ii  libatk1.0-0  2.22.0-1
ii  libavcodec-extra57   7:3.2.4-1
ii  libavformat577:3.2.4-1
ii  libavutil55  7:3.2.4-1
ii  libc62.24-9
ii  libcairo21.14.8-1
ii  libcups2 2.2.1-8
ii  libdbus-1-3  1.10.18-1
ii  libevent-2.0-5   2.0.21-stable-3
ii  libexpat12.2.0-2
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.1
ii  libgcc1  1:6.3.0-12
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgtk2.0-0  2.24.31-2
ii  libharfbuzz0b1.4.2-1
ii  libicu57 57.1-5
ii  libjpeg62-turbo  1:1.5.1-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26.2-1
ii  libpango-1.0-0   1.40.4-1
ii  libpangocairo-1.0-0  1.40.4-1
ii  libpng16-16  1.6.28-1
ii  libpulse010.0-1
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.3-3
ii  libstdc++6   6.3.0-12
ii  libvpx4  1.6.1-3
ii  libwebp6 0.5.2-1
ii  libwebpdemux20.5.2-1
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.14-1+b4
ii  libxdamage1  1:1.1.4-2+b3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-2.2
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.29-2.1
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.3-1
ii  x11-utils7.7+3+b1
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
pn  chromium-driver
pn  chromium-l10n  
pn  chromium-shell 
pn  chromium-widevine  

-- no debconf information

Bug#857013: reportbug: Attaching patch

[Michal Suchanek]

Package: reportbug
Version: 7.1.5
Followup-For: Bug #857013

Fix:


--- /usr/lib/python3/dist-packages/reportbug/utils.py   2017-04-13 
10:49:24.126454516 +0200
+++ /usr/lib/python3/dist-packages/reportbug/utils.py~  2017-04-13 
10:49:17.663966502 +0200
@@ -369,9 +369,7 @@
 confmode = False
 else:
 # re is used to identify also conffiles with spaces in the name
-tmp = re.findall(r' (.+) ([0-9a-f]+).*$', line)
-if len(tmp) > 0:
-conffiles = conffiles + [tmp[0]]
+conffiles = conffiles + [re.findall(r' (.+) ([0-9a-f]+).*$', 
line)[0]]
 
 if versionre.match(line):
 (crud, pkgversion) = line.split(": ", 1)

Versions of packages reportbug depends on:
ii  apt1.4
ii  python3-reportbug  7.1.5
pn  python3:any
--- /usr/lib/python3/dist-packages/reportbug/utils.py   2017-04-13 
10:49:24.126454516 +0200
+++ /usr/lib/python3/dist-packages/reportbug/utils.py~  2017-04-13 
10:49:17.663966502 +0200
@@ -369,9 +369,7 @@
 confmode = False
 else:
 # re is used to identify also conffiles with spaces in the name
-tmp = re.findall(r' (.+) ([0-9a-f]+).*$', line)
-if len(tmp) > 0:
-conffiles = conffiles + [tmp[0]]
+conffiles = conffiles + [re.findall(r' (.+) ([0-9a-f]+).*$', 
line)[0]]
 
 if versionre.match(line):
 (crud, pkgversion) = line.split(": ", 1)

Bug#860235: irqbalance: fails to configure

[Michal Suchanek]

Package: irqbalance
Version: 1.1.0-2.3
Severity: normal

Hello,

installing irqbalance fails:

# dpkg -P irqbalance
(Reading database ... 307003 files and directories currently installed.)
Removing irqbalance (1.1.0-2.3) ...
Purging configuration files for irqbalance (1.1.0-2.3) ...
Processing triggers for man-db (2.7.6.1-2) ...
stall Processing triggers for systemd (232-22) ...
# apt-get install irqbalance
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following NEW packages will be installed:
  irqbalance
0 upgraded, 1 newly installed, 0 to remove and 9 not upgraded.
Need to get 0 B/40.4 kB of archives.
After this operation, 115 kB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously unselected package irqbalance.
(Reading database ... 306996 files and directories currently installed.)
Preparing to unpack .../irqbalance_1.1.0-2.3_amd64.deb ...
Unpacking irqbalance (1.1.0-2.3) ...
Processing triggers for systemd (232-22) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up irqbalance (1.1.0-2.3) ...
update-rc.d: error: initscript does not exist: /etc/init.d/irqbalance
dpkg: error processing package irqbalance (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 irqbalance
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

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

Versions of packages irqbalance depends on:
ii  debconf [debconf-2.0]  1.5.60
ii  init-system-helpers1.47
ii  libc6  2.24-9
ii  libcap-ng0 0.7.7-3+b1
ii  libglib2.0-0   2.50.3-2
ii  libnuma1   2.0.11-2.1
ii  libsystemd0232-22
ii  lsb-base   9.20161125

irqbalance recommends no packages.

irqbalance suggests no packages.

-- debconf information:
  irqbalance/enable: true
  irqbalance/oneshot: false

Bug#857013: reportbug crashes: conffiles = conffiles + [re.findall(r' (.+) ([0-9a-f]+).*$', line)[0]]: IndexError: list index out of range

[Michal Suchanek]

Package: reportbug
Version: 7.1.5
Severity: normal

Hello,

reporting bug in irqbalance does not work for some reason.

The bug is that irqbalance does not have an init script so it may be that it 
has no conffiles now but had in the past.

$ reportbug irqbalance

(reportbug:17718): Gtk-WARNING **: Theme parsing error: gtk.css:25:25: The 
style property GtkWidget:link-color is deprecated and shouldn't be used 
anymore. It will be removed in a future version

(reportbug:17718): Gtk-WARNING **: Theme parsing error: gtk.css:26:33: The 
style property GtkWidget:visited-link-color is deprecated and shouldn't be used 
anymore. It will be removed in a future version

(reportbug:17718): Gtk-WARNING **: Theme parsing error: gtk.css:50:42: Not 
using units is deprecated. Assuming 'px'.

(reportbug:17718): Gtk-WARNING **: Theme parsing error: gtk.css:57:15: The 
:insensitive pseudo-class is deprecated. Use :disabled instead.

(reportbug:17718): Gtk-WARNING **: Theme parsing error: gtk.css:71:13: The 
:insensitive pseudo-class is deprecated. Use :disabled instead.
*** Welcome to reportbug.  Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address of the 
submitter).
Detected character set: UTF-8
Please change your locale if this is incorrect.

Using 'Michal Suchanek <hramr...@gmail.com>' as your from address.
Getting status for irqbalance...
Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2234, in 
main()
  File "/usr/bin/reportbug", line 1107, in main
return iface.user_interface()
  File "/usr/bin/reportbug", line 1408, in user_interface
status = utils.get_package_status(package)
  File "/usr/lib/python3/dist-packages/reportbug/utils.py", line 372, in 
get_package_status
conffiles = conffiles + [re.findall(r' (.+) ([0-9a-f]+).*$', line)[0]]
IndexError: list index out of range



-- Package-specific info:
** Environment settings:
EMAIL="Michal Suchanek <hramr...@gmail.com>"
INTERFACE="text"

** /home/hramrach/.reportbugrc:
reportbug_version "3.39"
mode standard
ui text
realname "Michal Suchanek"
email "hramr...@gmail.com"
no-cc
header "X-Debbugs-CC: hramr...@gmail.com"
smtphost smtp.centrio.cz

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

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

Versions of packages reportbug depends on:
ii  apt1.4~rc2
ii  python3-reportbug  7.1.5
pn  python3:any

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail   
ii  debconf-utils1.5.60
pn  debsums  
pn  dlocate  
pn  emacs23-bin-common | emacs24-bin-common  
ii  file 1:5.29-3
ii  gir1.2-gtk-3.0   3.22.8-1
pn  gir1.2-vte-2.91  
ii  gnupg2.1.18-6
ii  python3-gi   3.22.0-2
ii  python3-gi-cairo 3.22.0-2
pn  python3-gtkspellcheck
pn  python3-urwid
ii  ssmtp [mail-transport-agent] 2.64-8+b2
ii  xdg-utils1.1.1-1

Versions of packages python3-reportbug depends on:
ii  apt1.4~rc2
ii  file   1:5.29-3
ii  python3-debian 0.1.30
ii  python3-debianbts  2.6.1
ii  python3-requests   2.12.4-1
pn  python3:any

python3-reportbug suggests no packages.

-- no debconf information

Bug#855063: vboot-kernel-utils: requires a bootloader

[Michal Suchanek]

Package: vboot-kernel-utils
Version: 0~R52-8350.B-2
Severity: important

Dear Maintainer,

I tried to build a kernel image for my XE303 (Snow) notebook.
vbutil_kernel now requires a bootloader which the version 0~20121212-3
did not. This is a regression. I do not have/need a bootloader in the
kernel image. It is built into the device.

Please make it possible to build images for XE303 with the current
version of the utilities as well. Perhaps the error is requiring the
bootloader on ARM platform while it is needed on x86 and EFI enabled ARM
devices only.

Or should I provide an empty file for bootloader with the new version?

Thanks

Michal

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

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

Versions of packages vboot-kernel-utils depends on:
ii  libc62.24-9
ii  libssl1.0.0  1.0.2d-1

vboot-kernel-utils recommends no packages.

vboot-kernel-utils suggests no packages.

-- no debconf information

Bug#576829: xdg-settings: cannot set default-web-browser

[Michal Suchanek]

Package: xdg-utils
Followup-For: Bug #576829

Hello,

this is probably upstream bug report for this issue:
https://bugs.freedesktop.org/show_bug.cgi?id=98562

Bug#849594: systemd service ignores /etc/default

[Michal Suchanek]

Package: triggerhappy
Version: 0.5.0-1
Followup-For: Bug #849594

Hello,

sending a patch for the triggerhappy service file which adds the ability
to read options from /etc/default/triggerhappy


--- /lib/systemd/system/triggerhappy.service2016-08-30 09:26:25.0 
+0200
+++ /etc/systemd/system/triggerhappy.service2016-12-29 20:12:51.662411251 
+0100
@@ -4,7 +4,9 @@
 
 [Service]
 Type=notify
-ExecStart=/usr/sbin/thd --triggers /etc/triggerhappy/triggers.d/ --socket 
/run/thd.socket --user nobody --deviceglob /dev/input/event*
+EnvironmentFile=-/etc/default/triggerhappy
+ExecStart=/usr/sbin/thd --triggers /etc/triggerhappy/triggers.d/ --socket 
/run/thd.socket --user nobody --deviceglob /dev/input/event* $DAEMON_OPTS
+
 
 [Install]
 WantedBy=multi-user.target


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

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

Versions of packages triggerhappy depends on:
ii  init-system-helpers  1.46
ii  libc62.24-5
ii  libsystemd0  232-6

triggerhappy recommends no packages.

triggerhappy suggests no packages.

-- Configuration Files:
/etc/default/triggerhappy changed:
DAEMON_OPTS="--user root"


-- no debconf information
--- /lib/systemd/system/triggerhappy.service	2016-08-30 09:26:25.0 +0200
+++ /etc/systemd/system/triggerhappy.service	2016-12-29 20:12:51.662411251 +0100
@@ -4,7 +4,9 @@
 
 [Service]
 Type=notify
-ExecStart=/usr/sbin/thd --triggers /etc/triggerhappy/triggers.d/ --socket /run/thd.socket --user nobody --deviceglob /dev/input/event*
+EnvironmentFile=-/etc/default/triggerhappy
+ExecStart=/usr/sbin/thd --triggers /etc/triggerhappy/triggers.d/ --socket /run/thd.socket --user nobody --deviceglob /dev/input/event* $DAEMON_OPTS
+
 
 [Install]
 WantedBy=multi-user.target

Bug#849594: triggerhappy initegrates with systemd

[Michal Suchanek]

Package: triggerhappy
Version: 0.5.0-1
Severity: normal

Hello,

since installing systemd my triggers no longer work.

This is because my triggers require root privileges so I uncommented the
/etc/default/triggerhappy config line which makes triggerhappy run as root.

Alas, the triggerhappy systemd script does not take /etc/default into
account and just hardcodes running as nobody.

I see no way out of this except removing the systemd integration and
forcing the sysv compatibility layer to run a proper init script.

Thanks

Michal

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

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

Versions of packages triggerhappy depends on:
ii  init-system-helpers  1.46
ii  libc62.24-5
ii  libsystemd0  232-6

triggerhappy recommends no packages.

triggerhappy suggests no packages.

-- Configuration Files:
/etc/default/triggerhappy changed [not included]

-- no debconf information

Bug#847804: libsane:amd64: please update to recent snapshot suporting lide 120

[Michal Suchanek]

Hello,

On 23 December 2016 at 10:02, Jörg Frings-Fürst
 wrote:

> At the list[1] the Status of "CanoScan LiDE 120" is unsupported.

That's technically true. AFAIK no SANE release supports it.

> I think the best way is to ask the Upstream direct at[2].

And with the build of upstream git snapshot provided at [3] it works for me.

> [1] http://www.sane-project.org/sane-mfgs.html#Z-CANON
> [2] http://lists.alioth.debian.org/mailman/listinfo/sane-devel
[3] 
https://build.opensuse.org/package/show/home:michals:debian/sane-backends-new

Thanks

Michal

Bug#847804: libsane:amd64: please update to recent snapshot suporting lide 120

[Michal Suchanek]

Package: libsane
Version: 1.0.26~20161106200323~6484ff8-1
Severity: wishlist

Hello,

I tried sane from stable, testing, and experimental and neither
supported Canon LIDE 120 so I built a newer git snapshot which does.

The experimental version of the package talks to the scanner but all
scanned data is just white.

Package:
https://build.opensuse.org/package/show/home:michals:debian/sane-backends-new

Thanks

Michal

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

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

Versions of packages libsane:amd64 depends on:
ii  acl2.2.52-3
ii  adduser3.115
ii  libavahi-client3   0.6.32-1
ii  libavahi-common3   0.6.32-1
ii  libc6  2.24-5
ii  libexif12  0.6.21-2
ii  libgphoto2-6   2.5.10-3
ii  libgphoto2-port10  2.5.4-1.1+b2
ii  libieee1284-3  0.2.11-12
ii  libjpeg62-turbo1:1.5.1-2
ii  libsane-common 1.0.26~20161106200323~6484ff8-1
ii  libtiff5   4.0.7-1
ii  libusb-1.0-0   2:1.0.21-1
ii  makedev2.3.1-93
ii  multiarch-support  2.24-5
ii  udev   232-6

Versions of packages libsane:amd64 recommends:
ii  libsane-extras  1.0.22.3
ii  sane-utils  1.0.25-2+b1

Versions of packages libsane:amd64 suggests:
ii  avahi-daemon  0.6.32-1
pn  hplip 

-- no debconf information

Bug#840897: general: framebuffer modules for non-dri graphics cards are not loaded

[Michal Suchanek]

Package: general
Severity: normal

Hello,

I dusted off a notebook with hardware serial port which also happens to have a
Mach64 graphics card.

Accidentally during system upgrade an extra display manager was installed which
broke the text console. Running two X servers without KMS is problematic.

Upstream has a solution that should prevent most of these problems. The current
X drivers seem to work reasonably well with fbdev so long as the fb module is
loaded before the X server is started. At least the Mach64 driver looks ok.
Since the X driver appears to have fbdev integration it should not break the
console so long as fbdev is available.

Unfortunately, atyfb is not loaded by Debian. What's worse, adding the driver
to /etc/modules or /etc/initramfs-tools/modules has no effect. The module is
not loaded.

So I would like the fbdev modules removed from whatever blacklist prevents
loading them and have them loaded on systems that don't have dri modules to
handle graphics.

Thanks

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

Kernel: Linux 4.7.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)

[Michal Suchanek]

On 26 August 2016 at 13:34, Raphael Hertzog  wrote:
> On Fri, 26 Aug 2016, adrian15 wrote:
>> > Well, it sucks compared to the default visual appearance of
>> > isolinux/syslinux in live-build.
>> I know, but the purpose of my patch is to add UEFI support. Not to improve
>> visual appearance of grub2 so that it matches the isolinux/syslinux one.
>
> Well, my initial patch added EFI support on top of syslinux-efi and it
> thus had a nice visual appearance by default. So for me it's a
> regression...
>
> But I assume it's not a regression in terms of computers supported because
> I believe that syslinux-efi works for less cases than grub-efi and hence
> why I did not commit my own patch in the first place. Also I expect that
> secure boot will be easier to add on top of grub than on top of syslinux.

It works for Ubuntu so you can just pull the packages from there either through
apt pinning or by building a personal repo with them.

It seems some parts of the stuff are landing in experimental/sid but it would
be nice to have support for this in debian-live when it's complete.

I am probably not going to look into this any time soon, though.

>
> So I agree to apply your patch but I hope that you will stick around to
> help improve the visual appearance.

This bug is totally not about look of grub menus in debian-live.

If you are concerned about that file a separate bug about it.

>
>> These: /install/vmlinuz and /install/initrd.gz strings seem to be hardcoded.
>> That explains why I did not see them in binary_syslinux .
>> What does happen if you request both x86 and amd64 in your Debian Live? The
>> first kernel gets into the /install/vmlinuz and the second kernel gets
>> discarded?
>
> I don't know, I never tried to build images for multiple architectures.
> It's not a need for me.

It depends on the grub live scripts/templates, obviously.

Presumably fixing the installer support is needed to get full UEFI live support
but just filing it as an additional bug after this one is resolved may
be also fine.

It will be easier to fix once live media with *some* UEFI support are available.

Also I am fine with debootstrapping my system so that's not complete
installation blocker.

Unfortunately, most systems that need UEFI support also need secure boot
so solving that is probably most urgent UEFI problem.

The few I have access to right now do require it.

Thanks

Michal

Bug#573173: support multiple kernel versions with same flavour

[Michal Suchanek]

Package: live-build
Followup-For: Bug #573173

Hello,

sending fixed/updated version of the patch.

This works for me quite well with live-build in Debian and Syslinux.

Grub is unsupported.
Build menu for multiple kernels of the same flavour.

 - does not crash if multiple kernels of same flavour are installed
 - includes all kernels in boot menu
 - handles snapshot flavours (ending with +)

This allows to include stable and sid kernel as well as custom built kernel
snapshot in single image to support wider range of hardware.

Kernel version is included in menu label. This allows differentiating multiple
kernel versions of same flavour and gives useful information for single kernel
images as well.

The main menu text which lists kernel version was broken. The version list
included (none) - either due to duplicate packages in release/updates or
different sources between binary and chroot. Use dpkg to determine kernel
version rather than apt-cache.

TODO:
 * support fo non-syslinux bootloaders


Index: live-build-20151215mk1/scripts/build/binary_syslinux
===
--- live-build-20151215mk1.orig/scripts/build/binary_syslinux	2016-08-19 15:14:10.253502710 +0200
+++ live-build-20151215mk1/scripts/build/binary_syslinux	2016-08-23 10:44:53.491514403 +0200
@@ -197,52 +197,54 @@
 if [ -e "${_TARGET}/live.cfg.in" ]
 then
 	# This is all rather suboptimal.. needs prettifying at some point
-	_FLAVOURS="$(echo ${LB_LINUX_FLAVOURS} | wc -w)"
+	_FLAVOURS="$(echo ${LB_LINUX_FLAVOURS} | tr " " "\n" | sed -e '/^$/d')"
+	if ! echo "${_FLAVOURS}" | grep -q signed
+	then
+		_FLAVOURS="$(echo ${_FLAVOURS} | sed -e '/^$/d' -e 's/$/-signed/')
+		${_FLAVOURS}
+		$(echo ${_FLAVOURS} | sed -e '/^$/d' -e 's/$/-unsigned/')"
+	fi
+	if echo ${_FLAVOURS} | grep -q +$
+	then
+		_FLAVOURS_GIT=""
+	else
+		_FLAVOURS_GIT="$(echo ${_FLAVOURS} | sed -e '/^$/d' -e 's/$/+/')"
+	fi
+
+	_NUMBER="0"
+
+	for _FLAVOUR in ${_FLAVOURS} ${_FLAVOURS_GIT}
+	do
+		_KERNELS="$(ls -r --sort=version binary/${_INITRAMFS}/vmlinuz-*-${_FLAVOUR} 2>/dev/null || :)"
+		_KVERSIONS="$(for _KERNEL in ${_KERNELS} ; do basename "${_KERNEL}" -"${_FLAVOUR}" | sed -e 's/vmlinuz-//' ; done)"
+		for _KVER in ${_KVERSIONS}
+		do
+			_NUMBER="$((${_NUMBER} + 1))"
+			_KERNEL="vmlinuz-${_KVER}-${_FLAVOUR}"
+			_INITRD="initrd.img-${_KVER}-${_FLAVOUR}"
+			mv "binary/${_INITRAMFS}/${_KERNEL}" "binary/${_INITRAMFS}/vmlinuz${_NUMBER}"
+			mv "binary/${_INITRAMFS}/${_INITRD}" "binary/${_INITRAMFS}/initrd${_NUMBER}.img"
+
+			if [ "${_NUMBER}" -gt 1 ]
+			then
+echo >> "${_TARGET}/live.cfg"
+grep -v 'menu default' "${_TARGET}/live.cfg.in" >> "${_TARGET}/live.cfg"
+			else
+cat "${_TARGET}/live.cfg.in" >> "${_TARGET}/live.cfg"
+			fi
+
+			sed -i -e "s|@FLAVOUR@|${_FLAVOUR}-${_KVER}|g" \
+			-e "s|@LINUX@|/${_INITRAMFS}/vmlinuz${_NUMBER}|g" \
+			-e "s|@INITRD@|/${_INITRAMFS}/initrd${_NUMBER}.img|g" \
+			"${_TARGET}/live.cfg"
+		done
+	done
 
-	case "${_FLAVOURS}" in
-		1)
-			# If multiple initrd images are being generated (by DKMS packages, etc),
-			# we likely only want the latest version.
-			mv $(ls -r1 --sort=version binary/${_INITRAMFS}/vmlinuz-* | head -n 1) binary/${_INITRAMFS}/vmlinuz
-			mv $(ls -r1 --sort=version binary/${_INITRAMFS}/initrd.img-* | head -n 1) binary/${_INITRAMFS}/initrd.img
-
-			sed -e "s|@FLAVOUR@|${LB_LINUX_FLAVOURS}|g" \
-			-e "s|@LINUX@|/${_INITRAMFS}/vmlinuz|g" \
-			-e "s|@INITRD@|/${_INITRAMFS}/initrd.img|g" \
-			"${_TARGET}/live.cfg.in" >> "${_TARGET}/live.cfg"
-
-			rm -f "${_TARGET}/live.cfg.in"
-			;;
-
-		*)
-			_NUMBER="0"
-
-			for _FLAVOUR in ${LB_LINUX_FLAVOURS}
-			do
-_NUMBER="$((${_NUMBER} + 1))"
-
-mv binary/${_INITRAMFS}/vmlinuz-*-${_FLAVOUR} binary/${_INITRAMFS}/vmlinuz${_NUMBER}
-mv binary/${_INITRAMFS}/initrd.img-*-${_FLAVOUR} binary/${_INITRAMFS}/initrd${_NUMBER}.img
-
-if [ "${_NUMBER}" -gt 1 ]
-then
-	echo "" >> "${_TARGET}/live.cfg"
-	grep -v 'menu default' "${_TARGET}/live.cfg.in" >> "${_TARGET}/live.cfg"
-else
-	cat "${_TARGET}/live.cfg.in" >> "${_TARGET}/live.cfg"
-fi
-
-sed -i -e "s|@FLAVOUR@|${_FLAVOUR}|g" \
-   -e "s|@LINUX@|/${_INITRAMFS}/vmlinuz${_NUMBER}|g" \
-   -e "s|@INITRD@|/${_INITRAMFS}/initrd${_NUMBER}.img|g" \
-"${_TARGET}/live.cfg"
-			done
-
-			rm -f "${_TARGET}/live.cfg.in"
-			;;
-	esac
+	rm -f "${_TARGET}/live.cfg.in"
 fi
 
+Echo_message "Menu for $_NUMBER kernels created..."
+
 if [ -e chroot/etc/os-release ]
 then
 	_VERSION="$(. chroot/etc/os-release && echo ${VERSION_ID})"
@@ -261,7 +263,8 @@
 _MINUTE="$(date +%M)"
 _SECOND="$(date +%S)"
 
-_LINUX_VERSIONS="$(for _LINUX in chroot/boot/vmlinuz-* ; do chroot chroot apt-cache policy $(basename ${_LINUX} | sed -e 's|vmlinuz-|linux-image-|') | awk '/Installed: / { print $2 }' ; done | sort -Vru | tr "\n" " ")"
+_LINUX_VERSIONS="$(for i in chroot/boot/vmlinuz-* ; do chroot chroot dpkg -S 

Bug#573173: support multiple kernel versions with same flavour

[Michal Suchanek]

Package: live-build
Version: 1:20151215
Followup-For: Bug #573173

Hello,

sending patch against version of live-build currently in debian:
20151215

The patch was rejected in the past mainly due to pending rewrite of
live-build in python which is no longer planned AFAIK.

This patch makes the menu more verbose showing the kernel version and
also makes it possible to build image with multiple kernels of the same
flavour.

Kernels are sorted lowest first (from stable to experimental).

-- Package-specific info:

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (910, 'testing'), (900, 'stable'), (610, 'oldstable'), (410, 
'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages live-build depends on:
ii  debootstrap  1.0.81

Versions of packages live-build recommends:
ii  apt-utils   1.3~pre2
ii  cpio2.11+dfsg-5
ii  live-boot-doc   1:20160511
ii  live-config-doc 5.20160608
pn  live-manual-html | live-manual  
ii  wget1.18-2

Versions of packages live-build suggests:
ii  debian-keyring  2016.07.02
ii  gpgv1.4.20-6

-- no debconf information
Build menu for multiple kernels of the same flavour.

This allows to include stable and sid kernel in single image to support wider
range of hardware.

Kernel version is included in menu label. This allows differentiating multiple
kernels of same flavour and gives useful information for single kernel images
as well.


Index: live-build-20151215mk1/scripts/build/binary_syslinux
===
--- live-build-20151215mk1.orig/scripts/build/binary_syslinux	2016-08-16 11:20:07.691549799 +0200
+++ live-build-20151215mk1/scripts/build/binary_syslinux	2016-08-16 11:20:07.687549755 +0200
@@ -197,50 +197,43 @@
 if [ -e "${_TARGET}/live.cfg.in" ]
 then
 	# This is all rather suboptimal.. needs prettifying at some point
-	_FLAVOURS="$(echo ${LB_LINUX_FLAVOURS} | wc -w)"
+	_FLAVOURS="$(echo ${LB_LINUX_FLAVOURS} | tr " " "\n" | sed -e '/^$/d')"
+	if echo ${_FLAVOURS} | grep -q +$
+	then
+		_FLAVOURS_GIT=""
+	else
+		_FLAVOURS_GIT="$(echo ${LB_LINUX_FLAVOURS} | tr " " "\n" | sed -e '/^$/d' -e 's/$/+/')"
+	fi
+
+	_NUMBER="0"
+
+	for _FLAVOUR in ${_FLAVOURS} ${_FLAVOURS_GIT}
+	do
+		for _KERNEL in $(ls binary/live/vmlinuz-*-${_FLAVOUR})
+		do
+			_NUMBER="$((${_NUMBER} + 1))"
+			_KVER=$(basename "${_KERNEL}" -"${_FLAVOUR}" | sed -e 's/vmlinuz-//')
+			_INITRD="$(echo "${_KERNEL}" | sed -e 's|/vmlinuz-|/initrd.img-|')"
+			mv "${_KERNEL}" binary/${_INITRAMFS}/vmlinuz${_NUMBER}
+			mv "${_INITRD}" binary/${_INITRAMFS}/initrd${_NUMBER}.img
+
+			if [ "${_NUMBER}" -gt 1 ]
+			then
+grep -v 'menu default' "${_TARGET}/live.cfg.in" >> "${_TARGET}/live.cfg"
+			else
+cat "${_TARGET}/live.cfg.in" >> "${_TARGET}/live.cfg"
+			fi
+
+			sed -i -e "s|@FLAVOUR@|${_FLAVOUR} ${_KVER}|g" \
+			-e "s|@LINUX@|${_INITRAMFS}/vmlinuz${_NUMBER}|g" \
+			-e "s|@INITRD@|${_INITRAMFS}/initrd${_NUMBER}.img|g" \
+			-e "s|@APPEND_LIVE@|${LB_BOOTAPPEND_LIVE}|g" \
+			-e "s|@APPEND_FAILSAFE@|${LB_BOOTAPPEND_FAILSAFE}.img|g" \
+			"${_TARGET}/live.cfg"
+		done
+	done
 
-	case "${_FLAVOURS}" in
-		1)
-			# If multiple initrd images are being generated (by DKMS packages, etc),
-			# we likely only want the latest version.
-			mv $(ls -r1 --sort=version binary/${_INITRAMFS}/vmlinuz-* | head -n 1) binary/${_INITRAMFS}/vmlinuz
-			mv $(ls -r1 --sort=version binary/${_INITRAMFS}/initrd.img-* | head -n 1) binary/${_INITRAMFS}/initrd.img
-
-			sed -e "s|@FLAVOUR@|${LB_LINUX_FLAVOURS}|g" \
-			-e "s|@LINUX@|/${_INITRAMFS}/vmlinuz|g" \
-			-e "s|@INITRD@|/${_INITRAMFS}/initrd.img|g" \
-			"${_TARGET}/live.cfg.in" >> "${_TARGET}/live.cfg"
-
-			rm -f "${_TARGET}/live.cfg.in"
-			;;
-
-		*)
-			_NUMBER="0"
-
-			for _FLAVOUR in ${LB_LINUX_FLAVOURS}
-			do
-_NUMBER="$((${_NUMBER} + 1))"
-
-mv binary/${_INITRAMFS}/vmlinuz-*-${_FLAVOUR} binary/${_INITRAMFS}/vmlinuz${_NUMBER}
-mv binary/${_INITRAMFS}/initrd.img-*-${_FLAVOUR} binary/${_INITRAMFS}/initrd${_NUMBER}.img
-
-if [ "${_NUMBER}" -gt 1 ]
-then
-	echo "" >> "${_TARGET}/live.cfg"
-	grep -v 'menu default' "${_TARGET}/live.cfg.in" >> "${_TARGET}/live.cfg"
-else
-	cat "${_TARGET}/live.cfg.in" >> "${_TARGET}/live.cfg"
-fi
-
-sed -i -e "s|@FLAVOUR@|${_FLAVOUR}|g" \
-   -e "s|@LINUX@|/${_INITRAMFS}/vmlinuz${_NUMBER}|g" \
-   -e "s|@INITRD@|/${_INITRAMFS}/initrd${_NUMBER}.img|g" \
-"${_TARGET}/live.cfg"
-			done
-
-			rm -f "${_TARGET}/live.cfg.in"
-			;;
-	esac
+	rm -f "${_TARGET}/live.cfg.in"
 

Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)

[Michal Suchanek]

Hello,

On 31 July 2016 at 09:35, adrian15  wrote:
> This new update tries to implement actual support for multiple bootloaders.
> It only enforces grub-legacy not to be an extra bootloader because it's
> current implementation in binary-iso is not compatible (without hacking)
> with multiple bootloaders.
>
>
> * Branch were I added these last improvement / fixes:
> https://github.com/rescatux/live-build/tree/efi_support_based_on_debian_cd_michal
> * Final rebased branched:
> https://github.com/rescatux/live-build/tree/efi_support_based_on_debian_cd_rebased_7

I skimmed through this final rebased branch and it looks generally good.

I would suggest removing the unrelated whitespace changes and
squashing commits that
rewrite new code with commits introducing said code.

I have no idea who can pull this so it can be released in Debian.

Thanks

Michal

Bug#820910: apt no longer verifies repositories using sha1 hash

[Michal Suchanek]

Package: apt
Version: 1.2.10
Severity: important

Hello,

I tried to install a compiler from emdebian because there is no
corresponding version in debian main archives and

 - apt warns that the source uses SHA1 hash
 - the package is shown as untrusted

Since no exploit is known for sha1 apt (and aptitude) should show
warning about weak hash but not show the packages as untrusted.

I canot tell totally unsigned packages from packages which use hash that
Debian maintainers somehow dislike.

This is unacceptable with many archives around using these hashes.

Thanks

Michal

-- Package-specific info:


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (910, 'testing'), (900, 'stable'), (610, 'oldstable'), (410, 
'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages apt depends on:
ii  adduser 3.114
ii  debian-archive-keyring  2014.3
ii  gnupg   1.4.20-5
ii  gnupg2  2.1.11-6
ii  gpgv1.4.20-5
ii  init-system-helpers 1.29
ii  libapt-pkg5.0   1.2.10
ii  libc6   2.22-5
ii  libgcc1 1:5.3.1-13
ii  libstdc++6  5.3.1-13

apt recommends no packages.

Versions of packages apt suggests:
ii  apt-doc 1.2.10
ii  aptitude0.7.5-3
ii  dpkg-dev1.18.4
ii  python-apt  1.1.0~beta2

-- no debconf information

Bug#624122: Hash Sum mismatch

[Michal Suchanek]

Package: apt
Version: 1.2.10
Followup-For: Bug #624122

Hello,

I seem to also have a hash sum mismatch on presumably correct
repositories. One is from google and one is my personal repo hosted on
LP to get autobuild. The latter is unmodified for ages.

Thanks

Michal

The following NEW packages will be installed:
  glade-gtk2 google-talkplugin
0 upgraded, 2 newly installed, 0 to remove and 72 not upgraded.
Need to get 8,716 kB of archives.
After this operation, 20.0 MB of additional disk space will be used.
Get:1 http://dl.google.com/linux/talkplugin/deb stable/main amd64 
google-talkplugin amd64 5.41.0.0-1 [7,813 kB]
Get:2 http://ppa.launchpad.net/hramrach/ppa/ubuntu oneiric/main amd64 
glade-gtk2 amd64 3.8.0-0ubuntu1+ren1.1 [902 kB]
Err:1 http://dl.google.com/linux/talkplugin/deb stable/main amd64 
google-talkplugin amd64 5.41.0.0-1
  Hash Sum mismatch
Err:2 http://ppa.launchpad.net/hramrach/ppa/ubuntu oneiric/main amd64 
glade-gtk2 amd64 3.8.0-0ubuntu1+ren1.1
  Hash Sum mismatch
Fetched 8,716 kB in 1s (5,197 kB/s)
E: Failed to fetch 
http://ppa.launchpad.net/hramrach/ppa/ubuntu/pool/main/g/glade-3/glade-gtk2_3.8.0-0ubuntu1+ren1.1_amd64.deb
  Hash Sum mismatch

E: Failed to fetch 
http://dl.google.com/linux/talkplugin/deb/pool/main/g/google-talkplugin/google-talkplugin_5.41.0.0-1_amd64.deb
  Hash Sum mismatch

E: Internal Error, ordering was unable to handle the media swap

-- /etc/apt/sources.list.d/google-talkplugin.list:

### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# You may comment out this entry, but any other modifications may be lost.
deb http://dl.google.com/linux/talkplugin/deb/ stable main

-- the ppa bits:

deb http://ppa.launchpad.net/hramrach/ppa/ubuntu oneiric main 
deb-src http://ppa.launchpad.net/hramrach/ppa/ubuntu oneiric main 

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (910, 'testing'), (900, 'stable'), (610, 'oldstable'), (410, 
'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages apt depends on:
ii  adduser 3.114
ii  debian-archive-keyring  2014.3
ii  gnupg   1.4.20-5
ii  gnupg2  2.0.28-3
ii  gpgv1.4.20-5
ii  init-system-helpers 1.29
ii  libapt-pkg5.0   1.2.10
ii  libc6   2.22-5
ii  libgcc1 1:5.3.1-13
ii  libstdc++6  5.3.1-13

apt recommends no packages.

Versions of packages apt suggests:
ii  apt-doc 1.2.10
ii  aptitude0.7.5-3
ii  dpkg-dev1.18.4
ii  python-apt  1.1.0~beta2

-- no debconf information

Bug#819328: avrdude: arduino pro mini reset problem

[Michal Suchanek]

Package: avrdude
Version: 6.2-5
Followup-For: Bug #819328

Hello,

I fixed the reset problem with pro mini by inverting the DTR handling in
arduino.c

Since the UNO works with the unmodified avrdude it probably has
different reset circuit.

Tried to put together a patch that makes both boards work.

Ideally an extra argument would be added to switch which method is tried
first.

Thanks

Michal

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

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

Versions of packages avrdude depends on:
ii  libc6 2.21-7
ii  libelf1   0.163-5.1
ii  libftdi1  0.20-4
ii  libncurses5   6.0+20151024-2
ii  libreadline6  6.3-8+b4
ii  libtinfo5 6.0+20151024-2
ii  libusb-0.1-4  2:0.1.12-28

avrdude recommends no packages.

Versions of packages avrdude suggests:
pn  avrdude-doc  

-- no debconf information
Index: avrdude-6.2/arduino.c
===
--- avrdude-6.2.orig/arduino.c	2016-03-28 18:25:31.648762178 +0200
+++ avrdude-6.2/arduino.c	2016-03-28 18:31:02.925108185 +0200
@@ -80,6 +80,22 @@
   return 3;
 }
 
+static void arduino_frob_reset(PROGRAMMER * pgm)
+{
+  static bool dtr = 1;
+
+avrdude_message(MSG_INFO, "%s: arduino_open(): DTR is %sset\n",
+		progname, dtr ? "" : "not ");
+  /* Clear DTR and RTS to unload the RESET capacitor 
+   * (for example in Arduino) */
+  serial_set_dtr_rts(>fd, 1 ^ dtr);
+  usleep(250*1000);
+  /* Set DTR and RTS back to high */
+  serial_set_dtr_rts(>fd, 0 ^ dtr);
+  usleep(50*1000);
+  dtr = dtr ^ 1;
+}
+
 static int arduino_open(PROGRAMMER * pgm, char * port)
 {
   union pinfo pinfo;
@@ -89,13 +105,7 @@
 return -1;
   }
 
-  /* Clear DTR and RTS to unload the RESET capacitor 
-   * (for example in Arduino) */
-  serial_set_dtr_rts(>fd, 0);
-  usleep(250*1000);
-  /* Set DTR and RTS back to high */
-  serial_set_dtr_rts(>fd, 1);
-  usleep(50*1000);
+  arduino_frob_reset(pgm);
 
   /*
* drain any extraneous input
@@ -129,4 +139,5 @@
   pgm->read_sig_bytes = arduino_read_sig_bytes;
   pgm->open = arduino_open;
   pgm->close = arduino_close;
+  pgm->frob_reset = arduino_frob_reset;
 }
Index: avrdude-6.2/doc/Makefile.in
===
--- avrdude-6.2.orig/doc/Makefile.in	2016-03-28 18:25:31.648762178 +0200
+++ avrdude-6.2/doc/Makefile.in	2016-03-28 18:25:31.620762488 +0200
@@ -339,6 +339,7 @@
 prefix = @prefix@
 program_transform_name = @program_transform_name@
 psdir = @psdir@
+runstatedir = @runstatedir@
 sbindir = @sbindir@
 sharedstatedir = @sharedstatedir@
 srcdir = @srcdir@
@@ -472,9 +473,6 @@
 
 maintainer-clean-vti:
 	-rm -f $(srcdir)/stamp-vti $(srcdir)/version.texi
-.dvi.ps:
-	$(AM_V_DVIPS)TEXINPUTS="$(am__TEXINFO_TEX_DIR)$(PATH_SEPARATOR)$$TEXINPUTS" \
-	$(DVIPS) $(AM_V_texinfo) -o $@ $<
 
 uninstall-dvi-am:
 	@$(NORMAL_UNINSTALL)
@@ -826,11 +824,11 @@
 
 all-local: info html ps pdf
 
-html: avrdude-html/avrdude.html
+html: avrdude-html/index.html
 
-avrdude-html/avrdude.html: $(srcdir)/$(info_TEXINFOS) $(GENERATED_TEXINFOS)
-	texi2html -split_node $(srcdir)/$(info_TEXINFOS)
-	if [ -e ./avrdude.html -o -e ./avrdude_1.html ]; then \
+avrdude-html/index.html: $(srcdir)/$(info_TEXINFOS) $(GENERATED_TEXINFOS)
+	makeinfo --html --split=node $(srcdir)/$(info_TEXINFOS)
+	if [ -e ./index.html -o -e ./avrdude_1.html ]; then \
 	 mkdir -p avrdude-html ; \
 	 mv -f *.html avrdude-html ; \
 	else \
@@ -841,6 +839,13 @@
 $(builddir)/avrdude.dvi: $(GENERATED_TEXINFOS)
 $(builddir)/avrdude.pdf: $(GENERATED_TEXINFOS)
 
+.dvi.ps:
+	$(AM_V_DVIPS)TEXINPUTS="$(am__TEXINFO_TEX_DIR)$(PATH_SEPARATOR)$$TEXINPUTS" \
+	$(DVIPS) $(AM_V_texinfo) -o $@.tmp $<
+	printf "[ /CreationDate (%s)\n/DOCINFO pdfmark\n" "`date -u -r ../debian/changelog +%Y-%m-%dT%H:%M:%SZ`" > $@.mark
+	gs -q -dBATCH -dNOPAUSE -sDEVICE=ps2write -sOutputFile=$@ $@.tmp $@.mark
+	rm -f $@.mark $@.tmp
+
 # if it does not exist make this first
 ../avrdude$(EXEEXT):
 	$(MAKE) -C .. avrdude$(EXEEXT)
Index: avrdude-6.2/libavrdude.h
===
--- avrdude-6.2.orig/libavrdude.h	2016-03-28 18:25:31.648762178 +0200
+++ avrdude-6.2/libavrdude.h	2016-03-28 18:25:31.624762443 +0200
@@ -649,6 +649,7 @@
   unsigned char *res, int count);
   int  (*open)   (struct programmer_t * pgm, char * port);
   void (*close)  (struct programmer_t * pgm);
+  void (*frob_reset) (struct programmer_t * pgm);
   int  (*paged_write)(struct programmer_t * pgm, AVRPART * p, AVRMEM * m, 
   unsigned int page_size, unsigned int 

Bug#819328: avrdude: arduino pro mini reset problem

[Michal Suchanek]

Package: avrdude
Version: 6.2-5
Severity: normal

Hello,

I tried to flash an arduino pro mini clone over an USB TTL cable.

Some wiring guide on the internet suggests to wire DTR to RST so the ARV
resets automagically. Since I had Blink on the AVR I could tell it
indeed resets. However, it stays in reset the whole time avrdude tries
to communicate with the AVR and hence avrdude reports there is no
response.

Unwiring DTR and resetting board by hand solves the problem.

Can this be handled in avrdude? It seems whatever it does works for UNO
but not Pro Mini. Or is the wiring of the reset supposed to be
different?

Thanks

Michal

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

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

Versions of packages avrdude depends on:
ii  libc6 2.21-7
ii  libelf1   0.163-5.1
ii  libftdi1  0.20-4
ii  libncurses5   6.0+20151024-2
ii  libreadline6  6.3-8+b4
ii  libtinfo5 6.0+20151024-2
ii  libusb-0.1-4  2:0.1.12-28

avrdude recommends no packages.

Versions of packages avrdude suggests:
pn  avrdude-doc  

-- no debconf information

Bug#819167: blueproximity: bluetooth device used with blueproximity is unusable for anything else

[Michal Suchanek]

Package: blueproximity
Version: 1.2.5-6
Severity: important

Hello,

I tried to use blueproximity with my phone and bluetooth headphones.

When my phone was used for blueproximity I could not talk on the phone
bacause its audio output was connected to /dev/null.

When I used my headphones for blueproximity the audio which should have
been sent to the headphones was sent to /dev/null instead.

So it looks like I would have to wear an otherwise useless device such
as a BT beacon to use blueproximity.

This is disappointing.

There are tools which report device signal strength without making the
device completely useless so I would expect the same from blueproximity.

Thanks

Michal

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (910, 'testing'), (900, 'stable'), (610, 'oldstable'), (410, 
'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages blueproximity depends on:
ii  bluetooth 5.36-1
ii  librsvg2-common   2.40.11-2
ii  python2.7.11-1
ii  python-bluez  0.22-1
ii  python-configobj  5.0.6-2
ii  python-glade2 2.24.0-4
ii  python-gobject3.18.2-2
ii  python-gtk2   2.24.0-4

blueproximity recommends no packages.

Versions of packages blueproximity suggests:
ii  xscreensaver  5.34-1

-- no debconf information

Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)

[Michal Suchanek]

On 21 March 2016 at 23:06, adrian15 <adrian15...@gmail.com> wrote:
> El 21/03/16 a las 22:19, Michal Suchanek escribió:
>

>> The bootloader support in live-build is limited. With your patches it
>> becomes wrong. eg. compatibility of bootloader with selected
>> filesystem and image type is only checked for first bootloader and EFI
>> support is added only when grub-efi extra bootloader but not when it
>> is the first bootloader.
>>
>> This is not fixed by renaming the variables.
>
>
> Ok. So I recognise that my patch:
>
> * Adds a limited support of UEFI only available when it's used as an extra
> bootloader
> * Does not check compatibility with selected filesystem in the extra
> bootloader because it blindly relies on selected filesystem selected in
> first bootloader being compatible with the extra bootloader too.
> * It does not work for hdd binaries (only iso binaries)
>
> and it does in addition to what live-build already did.

No, it does not.

live-build only installed bootloader which was compatible with
selected filesystem and image type which is no longer true with your
patch. In fact, if I choose grub-efi as first bootloader the efi
support is not added and compatibility of any extra bootloaders with
the filesystem chosen is not checked so the image may be completely
unbootable.

So please consider either

1) fixing your current patch so there is no primary or first
bootloader and all installed bootloaders are equal

2) don't pretend you add support for multiple bootloaders when you are
not wiling to do so and just and some option like --bolt-on-grub-efi
which installs grub-efi if image type and filesystem is compatible
with grub-efi and fails the build otherwise

BTW it has been pointed out already that -eltorito-alt-boot is just
separator that starts new boot entry so there are no special
secondary/extra bootloader options. Any bootloader can be
first/second/third/whatever.

Thanks

Michal

Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)

[Michal Suchanek]

Hello,

On 21 March 2016 at 21:09, adrian15  wrote:

>
> The branch which include specifically the commits I attach here as patches
> is:
>
> https://github.com/rescatux/live-build/tree/efi_support_based_on_debian_cd_rebased_5
>
> .
>
> About the variable names issue: I think the new terms: first and extra are
> ok because they are not implying some sort of rank while explaining what's
> the difference between them. Also, notice, that these are internal variables
> which final user of live-build does not see. I think we should focus on
> other aspects of my patch if there are more problems for it.

The problem is not with the name of the variable.

The problem is that you use it at all. In most places when you check
for primary or secondary bootloader you should just loop all
bootloaders and check each. In fact, in the previous batch of patches
I found no place where checking for primary or secondary bootloader
made any sense.

>
> If you think that the way bootloaders is currently managed by live-build is
> wrong please file up a new bug and send there your patch with your
> improvements so that it's get discussed.

The bootloader support in live-build is limited. With your patches it
becomes wrong. eg. compatibility of bootloader with selected
filesystem and image type is only checked for first bootloader and EFI
support is added only when grub-efi extra bootloader but not when it
is the first bootloader.

This is not fixed by renaming the variables.

Thanks

Michal

Bug#814988: chromium: build for armhf

[Michal Suchanek]

Package: chromium
Version: 47.0.2526.80-1~deb8u1
Severity: wishlist

Hello,

chromium builds for armhf on other distributions so there should not be
anything fundamental in the sources preventing an armhf build on
Debian.

I see that armhf was once enabled and then disabled in changelog.

Can you reenable buildidng for armhf?

Thanks

Michal

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (910, 'testing'), (900, 'stable'), (610, 'oldstable'), (410, 
'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages chromium depends on:
ii  libasound2   1.1.0-1
ii  libatk1.0-0  2.18.0-1
ii  libc62.21-7
ii  libcairo21.14.6-1
ii  libcups2 2.1.2-2+b1
ii  libdbus-1-3  1.10.6-1
ii  libexpat12.1.0-7
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.6.1-0.1
ii  libgcc1  1:5.3.1-8
ii  libgdk-pixbuf2.0-0   2.32.3-1.2
ii  libglib2.0-0 2.46.2-3
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk2.0-0  2.24.29-1
ii  libjpeg62-turbo  1:1.4.2-2
ii  libnspr4 2:4.11-1
ii  libnss3  2:3.21-1
ii  libnss3-1d   2:3.21-1
ii  libpango-1.0-0   1.38.1-1
ii  libpangocairo-1.0-0  1.38.1-1
ii  libpci3  1:3.3.1-1.1
ii  libspeechd2  0.8-7
ii  libsrtp0 1.4.5~20130609~dfsg-1.1
ii  libstdc++6   5.3.1-8
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.6-1
ii  libxml2  2.9.3+dfsg1-1
ii  libxrandr2   2:1.5.0-1
ii  libxrender1  1:0.9.9-2
ii  libxslt1.1   1.1.28-2.1
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1

chromium recommends no packages.

Versions of packages chromium suggests:
pn  chromium-inspector  
pn  chromium-l10n   

-- no debconf information

Bug#814987: chromium: does not run flash automagically

[Michal Suchanek]

Package: chromium
Version: 47.0.2526.80-1~deb8u1
Severity: normal

Hello,

in chrome flash applets are run automatically.

It chromium flash applets are not run unless enabled by hand. This is
generally desirable.

However, if you visit a site which has important part implemented in
flash this is very annoying and there is no obvious way to whitelist a
particular applet to run automatically.

I specifically installed chromium for this purpose since it has one of
the best maintained flash plugins on Linux but it has failed me.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (910, 'testing'), (900, 'stable'), (610, 'oldstable'), (410, 
'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages chromium depends on:
ii  libasound2   1.1.0-1
ii  libatk1.0-0  2.18.0-1
ii  libc62.21-7
ii  libcairo21.14.6-1
ii  libcups2 2.1.2-2+b1
ii  libdbus-1-3  1.10.6-1
ii  libexpat12.1.0-7
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.6.1-0.1
ii  libgcc1  1:5.3.1-8
ii  libgdk-pixbuf2.0-0   2.32.3-1.2
ii  libglib2.0-0 2.46.2-3
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk2.0-0  2.24.29-1
ii  libjpeg62-turbo  1:1.4.2-2
ii  libnspr4 2:4.11-1
ii  libnss3  2:3.21-1
ii  libnss3-1d   2:3.21-1
ii  libpango-1.0-0   1.38.1-1
ii  libpangocairo-1.0-0  1.38.1-1
ii  libpci3  1:3.3.1-1.1
ii  libspeechd2  0.8-7
ii  libsrtp0 1.4.5~20130609~dfsg-1.1
ii  libstdc++6   5.3.1-8
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.6-1
ii  libxml2  2.9.3+dfsg1-1
ii  libxrandr2   2:1.5.0-1
ii  libxrender1  1:0.9.9-2
ii  libxslt1.1   1.1.28-2.1
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1

chromium recommends no packages.

Versions of packages chromium suggests:
pn  chromium-inspector  
pn  chromium-l10n   

-- no debconf information

Bug#814771: nemo: refuses to launch application symlinks

[Michal Suchanek]

Package: nemo
Version: 2.8.6-2
Severity: normal

Hello,

I made a symlink on my desktop

lrwxrwxrwx chromium.desktop -> /usr/share/applications/chromium.desktop

When I try to start chromium from my desktop nemo complains that the
application is non-executable and untrusted. There is no reasonable way to make
the application file in /usr/share/applications executable. The symlink itself
is.

Please amend this mechanism so that launching symlinks to system applications
is possible without nemo complaining.

Thanks

Michal

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (900, 'stable'), (800, 'oldstable'), (500, 
'unstable'), (110, 'experimental')
Architecture: i386 (i686)

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

Versions of packages nemo depends on:
ii  desktop-file-utils 0.22-1
ii  gsettings-desktop-schemas  3.18.1-1
ii  gvfs   1.26.2-1+b1
ii  libatk1.0-02.18.0-1
ii  libc6  2.21-7
ii  libcairo-gobject2  1.14.6-1
ii  libcairo2  1.14.6-1
ii  libcinnamon-desktop4   2.8.0-1
ii  libexempi3 2.2.2-2+b1
ii  libexif12  0.6.21-2
ii  libgail-3-03.18.7-1
ii  libgdk-pixbuf2.0-0 2.32.3-1.2
ii  libglib2.0-0   2.46.2-3
ii  libglib2.0-data2.46.2-3
ii  libgtk-3-0 3.18.7-1
ii  libnemo-extension1 2.8.6-2
ii  libnotify4 0.7.6-2
ii  libpango-1.0-0 1.38.1-1
ii  libpangocairo-1.0-01.38.1-1
ii  libx11-6   2:1.6.3-1
ii  libxml22.9.3+dfsg1-1
ii  nemo-data  2.8.6-2
ii  shared-mime-info   1.5-2

Versions of packages nemo recommends:
ii  cinnamon-l10n2.8.3-1
ii  gvfs-backends1.26.2-1+b1
ii  librsvg2-common  2.40.11-2
ii  nemo-fileroller  2.8.0-1

Versions of packages nemo suggests:
pn  eog  
pn  evince | pdf-viewer  
pn  totem | mp3-decoder  
ii  xdg-user-dirs0.15-2

-- no debconf information

Bug#813154: xmonad: does not run on ARM

[Michal Suchanek]

Hello,

On 31 January 2016 at 11:55, Joachim Breitner  wrote:
> Hi Michal,
>
> I see you are running stable. What version of 7.10 precisely are you
> using? From testing or jessie-backports?

I am using testing ghc.

>
> Does the problem go a way if you upgrade llvm-3.5 to the version in
> jessie-backports?

I cannot install llvm3.5 from backports.

backports llvm uses libllvm3.5v5 which conflicts with libllvm3.5
(non-v5) used by mesa which is used by pretty much everything.

mesa is not backported hence only option is to install mesa from
testing which depends on libstdc++ v5 which requires dist-upgrade.

Upgrading to Stretch the problem with ghc goes away.

Thanks

Michal

Bug#813303: comix: scrolling up goes to next page

[Michal Suchanek]

Package: comix
Version: 4.0.4-1
Severity: normal

Hello,

when viewing in fit-width mode scrolling down displays rest of page and
then next page and scrolling up also displays next page. There is no
obvious way to get to previous page with mouse.

Specifically, scrolling up should always scroll up, even across page
boundaries.

Thanks

Michal

-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (901, 'stable'), (512, 'testing'), (510, 'unstable'), (505, 
'experimental'), (500, 'oldstable')
Architecture: armhf (armv7l)
Foreign Architectures: i386

Kernel: Linux 4.5.0-rc1-00069-g44cb9f7 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages comix depends on:
ii  gconf2  3.2.6-3
ii  python  2.7.9-1
ii  python-gtk2 2.24.0-4
ii  python-imaging  2.6.1-2

comix recommends no packages.

Versions of packages comix suggests:
ii  python  2.7.9-1
ii  unrar   1:5.2.7-0.1

-- no debconf information

Bug#813303: comix: scrolling up goes to next page

[Michal Suchanek]

Package: comix
Version: 4.0.4-1
Followup-For: Bug #813303

Ok, I added lots of debug prints and found the issue.

Side scrolling causes page flips right away.

Using a touch device it is quite possible that a random page flip is
generated way before comix counts to 3 and flips the page due to
excessive scrolling outside of the page area.

Attaching a debdiff.

Thanks

Michal

-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (901, 'stable'), (512, 'testing'), (510, 'unstable'), (505, 
'experimental'), (500, 'oldstable')
Architecture: armhf (armv7l)
Foreign Architectures: i386

Kernel: Linux 4.5.0-rc1-00069-g44cb9f7 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages comix depends on:
ii  gconf2  3.2.6-3
ii  python  2.7.9-1
ii  python-gtk2 2.24.0-4
ii  python-imaging  2.6.1-2

comix recommends no packages.

Versions of packages comix suggests:
ii  python  2.7.9-1
ii  unrar   1:5.2.7-0.1

-- no debconf information
diff -u comix-4.0.4/debian/rules comix-4.0.4/debian/rules
--- comix-4.0.4/debian/rules
+++ comix-4.0.4/debian/rules
@@ -19,6 +19,7 @@
 	dh_testroot
 
 	# Add here commands to clean up after the build process.
+	rm -f src/*.pyc
 
 	dh_clean 
 
diff -u comix-4.0.4/debian/changelog comix-4.0.4/debian/changelog
--- comix-4.0.4/debian/changelog
+++ comix-4.0.4/debian/changelog
@@ -1,3 +1,9 @@
+comix (4.0.4-1scroll1) UNRELEASED; urgency=medium
+
+  * fix scrolling on touch devices
+
+ -- Emfox Zhou   Sun, 31 Jan 2016 15:25:15 +0100
+
 comix (4.0.4-1) unstable; urgency=low
 
   * New upstream release
only in patch2:
unchanged:
--- comix-4.0.4.orig/src/event.py
+++ comix-4.0.4/src/event.py
@@ -240,10 +240,11 @@
 self._scroll_with_flipping(70, 0)
 else:
 self._scroll_with_flipping(0, 70)
+""" This part makes it pretty much impossible to scroll with touch devices
 elif event.direction == gtk.gdk.SCROLL_RIGHT:
 self._window.next_page()
 elif event.direction == gtk.gdk.SCROLL_LEFT:
-self._window.previous_page()
+self._window.previous_page() """
 
 def mouse_press_event(self, widget, event):
 """Handle mouse click events on the main layout area."""

Bug#722880: /usr/bin/apt-get: Re: apt: Apt fails to solve some dependencies in a multiarch scenario.

[Michal Suchanek]

On 30 January 2016 at 10:22, Stepan Golosunov <ste...@golosunov.pp.ru> wrote:
> 30.01.2016 в 01:15:27 +0100 Michal Suchanek написал:
>> I still cannot install arch:i386 package that depends on arch:all
>> package because apt wrongly tries to search for the arch:all package as
>> arch:i386.
>>
>> # apt-get -m  -d install libgtksourceview2.0-0:i386
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> Some packages could not be installed. This may mean that you have
>> requested an impossible situation or if you are using the unstable
>> distribution that some required packages have not yet been created
>> or been moved out of Incoming.
>> The following information may help to resolve the situation:
>>
>> The following packages have unmet dependencies:
>>  libgtksourceview2.0-0:i386 : Depends: libgtksourceview2.0-common:i386 (>= 
>> 2.10) but it is not installable
>>   Depends: libgtksourceview2.0-common:i386 (< 
>> 2.11) but it is not installable
>> E: Unable to correct problems, you have held broken packages.
>
> That's exactly the expected situation given that
> libgtksourceview2.0-common package forbids installation of
> foreign-arch reverse dependencies by not providing a
> "Multi-Arch: foreign" header.
>
> Lack of that header is probably a bug in libgtksourceview2.0-common.
>

Lack of multiarch headers is probably a bug in libgtksourceview2.0 all
right. That would prevent installing the library for two archs. I
install only Arch:i386 and Arch:all package so there should be nothing
preventing the installation. Arch:all is still Arch:all.

Thanks

Michal

Bug#813154: xmonad: does not run on ARM

[Michal Suchanek]

Package: xmonad
Followup-For: Bug #813154

Ok, so this is ghc platform-specific problem.

Installing i386 ghc binary allows the simplified as well as the full
xmonad config to run.

So either there is a bug in xmonad or one of the libraries that only
manifests on ghc 7.10 on arm or something gets miscompiled.

I don't have enough depth to debug ghc output so I will leave it at
that.

Thanks

Michal

Bug#813251: libgtksourceview2.0 lacks multiarch support

[Michal Suchanek]

Package: libgtksourceview2.0-common
Version: 2.10.5-2
Severity: normal

Hello,

libgtksourceview lacks multiarch package headers which prevents
installing foreign architecture binaries that depend on gtksourceview.

It also installs the shared library in /usr/lib :s

Repacking the libraries in the correct directory and adding the headers
seems to work. So just following some multiarch package cookbook should
work well enough.

Thanks

Michal

-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (901, 'stable'), (512, 'testing'), (510, 'unstable'), (505, 
'experimental'), (500, 'oldstable')
Architecture: armhf (armv7l)
Foreign Architectures: i386

Kernel: Linux 4.5.0-rc1-00069-g44cb9f7 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

-- no debconf information

Bug#722880: /usr/bin/apt-get: Re: apt: Apt fails to solve some dependencies in a multiarch scenario.

[Michal Suchanek]

Package: apt
Version: 1.0.9.8.2
Followup-For: Bug #722880


Hello,

I still cannot install arch:i386 package that depends on arch:all
package because apt wrongly tries to search for the arch:all package as
arch:i386.

# apt-get -m  -d install libgtksourceview2.0-0:i386
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libgtksourceview2.0-0:i386 : Depends: libgtksourceview2.0-common:i386 (>= 
2.10) but it is not installable
  Depends: libgtksourceview2.0-common:i386 (< 2.11) 
but it is not installable
E: Unable to correct problems, you have held broken packages.


Package: libgtksourceview2.0-common
Status: install ok installed
Priority: optional
Section: libs
Installed-Size: 3079
Maintainer: Debian GNOME Maintainers 

Architecture: all
Source: gtksourceview2
Version: 2.10.5-2
Description: common files for the GTK+ syntax highlighting widget
 GtkSourceView is a text widget that extends the standard GTK+ 2.x text widget
 GtkTextView. It improves GtkTextView by implementing syntax highlighting and
 other features typical of a source editor.
 .
 This package contains the language specifications files for Ada, C, C++, C#,
 CSS, ".desktop", ".diff" (patch), Fortran 95, GtkRC, Haskell, HTML, IDL,
 ".ini", Java, JavaScript, LaTeX, Lua, MSIL, Nemerle, Pascal, Perl, PHP, ".po"
 (gettext), Python, R, Ruby, sh, SQL, Tcl, Texinfo, VB.NET, Verilog, VHDL and
 XML.
Homepage: http://projects.gnome.org/gtksourceview/

-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (901, 'stable'), (512, 'testing'), (510, 'unstable'), (505, 
'experimental'), (500, 'oldstable')
Architecture: armhf (armv7l)
Foreign Architectures: i386

Kernel: Linux 4.5.0-rc1-00069-g44cb9f7 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages apt depends on:
ii  debian-archive-keyring  2014.3
ii  gnupg   1.4.18-7
ii  libapt-pkg4.12  1.0.9.8.2
ii  libc6   2.19-18+deb8u2
ii  libgcc1 1:4.9.2-10
ii  libstdc++6  4.9.2-10

apt recommends no packages.

Versions of packages apt suggests:
pn  apt-doc 
ii  aptitude0.6.11-1+b1
pn  dpkg-dev
ii  python-apt  0.9.3.12

-- no debconf information

Bug#813154: xmonad: does not run on ARM

[Michal Suchanek]

Package: xmonad
Version: 0.12-1
Severity: normal

Hello,

I tried to install a library which required upgrading ghc from 7.6 to
7.10  and xmonad from 0.11 to 0.12.

As a result xmonad no longer starts:

xmonad.hs:

import XMonad hiding (Tall(..))
import XMonad.Config (defaultConfig)

main = xmonad $ defaultConfig

output:

xmonad-arm-linux: schedule: re-entered unsafely.
   Perhaps a 'foreign import unsafe' should be 'safe'?

-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (900, 'stable'), (510, 'unstable'), (505, 'experimental'), (500, 
'oldstable')
Architecture: armhf (armv7l)
Foreign Architectures: i386

Kernel: Linux 4.5.0-rc1-00069-g44cb9f7 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages xmonad depends on:
ii  libc6 2.19-18+deb8u2
ii  libffi6   3.1-2+b2
ii  libgmp10  2:6.0.0+dfsg-6
ii  libx11-6  2:1.6.2-3
ii  libxext6  2:1.3.3-1
ii  libxinerama1  2:1.1.3-1+b1
ii  libxrandr22:1.4.2-1+b1
ii  x11-utils 7.7+2

Versions of packages xmonad recommends:
ii  libghc-xmonad-dev  0.12-1
pn  libghc-xmonad-doc  
ii  xfonts-base1:1.0.3

Versions of packages xmonad suggests:
pn  gnome-session-flashback  
ii  suckless-tools [dmenu]   40-1

-- no debconf information

Bug#813156: ghc should depend on version of binutils that understands its objects

[Michal Suchanek]

Package: ghc
Version: 7.10.3-6
Severity: normal

Hello,

stable binutils do not understand objects installed as part of testing
haskell libraries. As many haskell libraries do not seem to be compiled
for stable it is likely that installing a haskell library pulls testing
ghc on a stable system.


/usr/bin/ld: 
/usr/lib/haskell-packages/ghc/lib/i386-linux-ghc-7.10.3/X11-1.6.1.2-LN1z6AJRA5dI5d2mzKRchU/libHSX11-1.6.1.2-LN1z6AJRA5dI5d2mzKRchU.a(XUtils.o):
 unrecognized relocation (0x2b) in section `.text'
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
ghc: user error (If you can read this, shutdownHaskellAndExit did not exit.)

ii  binutils 2.25-5  i386   
 GNU assembler, linker and binary utilities

-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (900, 'stable'), (510, 'unstable'), (505, 'experimental'), (500, 
'testing'), (500, 'oldstable')
Architecture: armhf (armv7l)
Foreign Architectures: i386

Kernel: Linux 4.5.0-rc1-00069-g44cb9f7 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages ghc depends on:
ii  dpkg 1.17.26
ii  gcc  4:4.9.2-2
ii  libbsd-dev   0.7.0-2
ii  libc62.19-18+deb8u2
ii  libc6-dev2.19-18+deb8u2
ii  libffi-dev   3.1-2+b2
ii  libffi6  3.1-2+b2
ii  libgmp-dev   2:6.0.0+dfsg-6
ii  libgmp10 2:6.0.0+dfsg-6
ii  libncurses5-dev  6.0+20151024-2
ii  libtinfo56.0+20151024-2

ghc recommends no packages.

Versions of packages ghc suggests:
pn  ghc-doc  
pn  ghc-prof 
pn  haskell-doc  
pn  llvm-3.5 
ii  perl 5.20.2-3+deb8u3

-- no debconf information

Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)

[Michal Suchanek]

On 26 January 2016 at 23:20, adrian15 <adrian15...@gmail.com> wrote:
> El 26/01/16 a las 10:18, Michal Suchanek escribió:

>>
>>>
>>> My use case is the following one. The final user requests:
>>>
>>> --bootloaders=grub-efi,syslinux
>>>
>>> so I show him:
>>>
>>> "Warning. You are using: syslinux as a non first bootloader. This might
>>> work
>>> but it is not advised."
>>>
>>> How do I know that I have to output this message?
>>
>>
>> for bootloader in $BOOTLOADERS ; do
>>
>>  # some bootloader foo
>>
>>  if echo $BIOS_BOOTLOADERS | grep "${bootloader}" >/dev/null; then
>> # a fixed list of bootloaders that load through legacy BIOS -
>> currently should be "syslinux grub-pc" although grub is not well
>> supported
>>  case $MEDIA_TYPE in # or whatever the variable
>>  iso*)
>>  case "${BOOTLOADERS}" in
>>  "${bootloader}"*);;
>>  *) echo "Warning: it is recommended to specify
>> $bootloader first in bootloader list so it gets installed as first
>> el-torito boot entry."
>>  ;;
>>  esac ;;
>>  esac
>>  fi
>> done
>
> Here you are creating a new variable: $BIOS_BOOTLOADERS which will have to
> be updated manually each time a new bios bootloader binary_ file is added.

So what? Any other way to recognize a BIOS bootloader as such?

>
> The grep part should be improved to avoid problems (e.g. syslinux is inside
> syslinux-efi).

Except $BIOS_BOOTLOADERS does not include syslinux-efi so it does not happen ;-)

>
>>> Because I compare the internal variable:
>>>
>>> LB_FIRST_BOOTLOADER="grub-efi"
>>>
>>> with the bootloader name "syslinux" and I see they are not the same one.
>>>
>>> So, as you see I need to use:
>>>
>>> "non first bootloader" term
>>
>>
>> Why that has to be a term? Just say it should come first in the list
>> of bootloaders if specified at all.
>
>
> "It should come first". "It should not come first". Ok. I can do that and
> ditch the "non first bootloader" or "first bootloader" from my messages.
>
>>
>>> and
>>> LB_FIRST_BOOTLOADER variable.
>>
>>
>> what for?
>
>
> For two reasons:
>
> 1) Being able to use current live-build code which used LB_BOOTLOADER in the
> past.
>
> Check what it's in current alioth git (Seach for LB_PRIMARY_BOOTLOADER on
> there):
>
> https://anonscm.debian.org/cgit/debian-live/live-build.git/tree/scripts/build/binary_hdd?id=1ccb41623046f2a8f823d62a5f417cdae724c22b
>
> https://anonscm.debian.org/cgit/debian-live/live-build.git/tree/scripts/build/binary_iso?id=1ccb41623046f2a8f823d62a5f417cdae724c22b
>
> https://anonscm.debian.org/cgit/debian-live/live-build.git/tree/functions/defaults.sh?id=1ccb41623046f2a8f823d62a5f417cdae724c22b

Skimming through that code in every place LB_PRIMARY_BOOTLOADER is
used the code is broken.

If a bootloader is requested then you should install its files/check
that the filesystem is compatible/... regardless of the el-torito
record number it is installed in.

>
> 2) Not having to use awk each time I need to compare a first / default
> bootloader... when I can just use a variable with previous (once only)
> calculated value.

Which if used correctly would be used once or twice if at all.

Thanks

Michal

Bug#812365: /usr/bin/apt-get: when download of a package list timeouts it is reported as Ign rather than Err

[Michal Suchanek]

Package: apt
Followup-For: Bug #812365


Hello,

It seems to be no longer a problem with current apt.

There was some library dependency problem so it would not auto-update
for a while.

Thanks

Michal

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

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

Versions of packages apt depends on:
ii  adduser 3.113+nmu3
ii  debian-archive-keyring  2014.3
ii  gnupg   1.4.20-1
ii  gnupg2  2.0.28-3
ii  gpgv1.4.20-1
ii  libapt-pkg5.0   1.2
ii  libc6   2.21-6
ii  libgcc1 1:5.3.1-5
ii  libstdc++6  5.3.1-5

apt recommends no packages.

Versions of packages apt suggests:
pn  apt-doc 
ii  aptitude0.7.5-3
ii  dpkg-dev1.18.4
ii  python-apt  1.1.0~beta1

-- no debconf information

Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)

[Michal Suchanek]

On 25 January 2016 at 21:33, adrian15 <adrian15...@gmail.com> wrote:
>
>
> El 25/01/16 a las 16:12, Michal Suchanek escribió:
>>
>> On 25 January 2016 at 03:05, adrian15 <adrian15...@gmail.com> wrote:
>>>
>>> El 24/01/16 a las 16:51, Michal Suchanek escribió:
>>
>>
>>> What you are describing here is what it's actually implemented in my
>>> patch
>>> (Well, actually the first patch version because the current one enforces
>>> bootloader roles).
>>
>>
>> Actually, no.
>>
>> Nowhere in the description is any bootloader designated primary or
>> secondary or first or second. On purpose.
>
> Neither it is on my patch (initial implementation). Yes, the term
> PRIMARY_BOOTLOADER is used there for reusing old code. But using:
>
> --bootloaders=syslinux,grub-efi
>
> did not enforce syslinux to be in the first place or grub-efi to be in the
> second place.
>
> That's the specific part I meant.
>
>>
>>> So what about primary and secondary terms? Or first or
>>> second terms?
>>
>>
>> Both are broken and confusing.
>
> Ok...
>>>
>>>
>>> These terms are used in two places:
>>> * Internal variables and functions to handle bootloaders
>>> * Information shown to the final user
>>>
>>> I'm most convinced to use the first and non-first notation. So that the
>>> old
>>> code that referred to LB_BOOTLOADER can just refer to:
>>> LB_FIRST_BOOTLOADER.
>>
>>
>> For what piece of code we have does it make sense to reference
>> LB_FIRST_BOOTLOADER when not also referencing LB_SECOND_BOOTLOADER?
>> Will that be extended to LB_THIRD_BOOTLOADER once x86 grows support
>> for coreboot or l-b grows support for some other platform with many
>> firmware variants?
>>
>> If you set bootloaders like
>>
>> LB_BOOTLOADERS="syslinux grub-efi"
>>
>> then you can just do
>>
>> for bootloader in $LB_BOOTLOADERS ; do some $bootloader foo
>
> Mostly what current path does but with commas instead.

IIRC multivalue options use mostly spaces for separator in l-b so far.

>>
>>
>> after you check that you have at most two bootloaders and if you have
>> more than one then only the latter one ends with -efi.
>
>
> This is not a good approach. You are requesting the bootloaders to end in
> "-efi". The current approach is to name them based on the Debian package
> name. These packages do not need to end in "-efi".

It so happens that bootloaders that support efi are packaged as
packages with -efi suffix (well, except elilo). Maybe there is some
intent there?

However, grub-pc is now split in grub-pc scripts that are meant to
install the bootloader in the system which you probably don't want and
grub-pc-bin which just includes the binaries. The situation is even
more complicated with the 32bit and 64bit efi packages. Also expect
that at some point the maintainers figure out some new completely
awesome way to split the bootloader into packages and then the package
sets will be different in stable/testing/oldstable.

So naming the l-b option *exactly* like the package is not that good idea.

>
> My use case is the following one. The final user requests:
>
> --bootloaders=grub-efi,syslinux
>
> so I show him:
>
> "Warning. You are using: syslinux as a non first bootloader. This might work
> but it is not advised."
>
> How do I know that I have to output this message?

for bootloader in $BOOTLOADERS ; do

# some bootloader foo

if echo $BIOS_BOOTLOADERS | grep "${bootloader}" >/dev/null; then
# a fixed list of bootloaders that load through legacy BIOS -
currently should be "syslinux grub-pc" although grub is not well
supported
case $MEDIA_TYPE in # or whatever the variable
iso*)
case "${BOOTLOADERS}" in
"${bootloader}"*);;
*) echo "Warning: it is recommended to specify
$bootloader first in bootloader list so it gets installed as first
el-torito boot entry."
;;
esac ;;
esac
fi
done


>
> Because I compare the internal variable:
>
> LB_FIRST_BOOTLOADER="grub-efi"
>
> with the bootloader name "syslinux" and I see they are not the same one.
>
> So, as you see I need to use:
>
> "non first bootloader" term

Why that has to be a term? Just say it should come first in the list
of bootloaders if specified at all.

> and
> LB_FIRST_BOOTLOADER variable.

what for?

>
> So...
>
> 1) I don't mind renami

Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)

[Michal Suchanek]

On 25 January 2016 at 03:05, adrian15 <adrian15...@gmail.com> wrote:
> El 24/01/16 a las 16:51, Michal Suchanek escribió:

> What you are describing here is what it's actually implemented in my patch
> (Well, actually the first patch version because the current one enforces
> bootloader roles).

Actually, no.

Nowhere in the description is any bootloader designated primary or
secondary or first or second. On purpose.

> So what about primary and secondary terms? Or first or
> second terms?

Both are broken and confusing.

>
> These terms are used in two places:
> * Internal variables and functions to handle bootloaders
> * Information shown to the final user
>
> I'm most convinced to use the first and non-first notation. So that the old
> code that referred to LB_BOOTLOADER can just refer to: LB_FIRST_BOOTLOADER.

For what piece of code we have does it make sense to reference
LB_FIRST_BOOTLOADER when not also referencing LB_SECOND_BOOTLOADER?
Will that be extended to LB_THIRD_BOOTLOADER once x86 grows support
for coreboot or l-b grows support for some other platform with many
firmware variants?

If you set bootloaders like

LB_BOOTLOADERS="syslinux grub-efi"

then you can just do

for bootloader in $LB_BOOTLOADERS ; do some $bootloader foo

after you check that you have at most two bootloaders and if you have
more than one then only the latter one ends with -efi.

Thanks

Michal

Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)

[Michal Suchanek]

On 24 January 2016 at 00:41, adrian15  wrote:
> El 23/01/16 a las 09:21, Thomas Schmitt escribió:
>>
>> There is a fourth dimension to be expressed: Bootloader.
>> Then there is the dimension of ISO filesystem objects.
>> A user wish would contain at least
>>ISO-Object, Bootloader, Medium, Firmware, Architecture
>>
>> E.g.
>>
>>Appended Partition, with GRUB2 content, for CDROM and HDD, via EFI, on
>> i386
>>
>>ISO Data File, with SYSLINUX content, for HDD, via BIOS, on i386 and
>> amd64
>>
>> I am not sure whether this list of more or less combinable
>> dimensions is complete yet.
>>
>> Further one will want to express whether the gaps between partitions
>> should be filled, which kinds of partition tables shall emerge, ...
>> These properties are global to the ISO, not specific to a single
>> boot image. Some are combinable, some are mutally exclusive.
>>
>> (Maybe it is time to break out an UML editor.)
>
>
> I propose you to send these concerns to live-wrapper project which has just
> begun and it's advertised as highly modular by Iain. It would be quite nice
> if all these concerns were properly addressed by Iain's tool.
>
>   I am not saying that they are not welcomed to live-build but, right now, I
> think we should focus on making UEFI to boot and not re-thinking all the
> bootloader handling.
>
>> grub-mkrescue layout is rarely used for distro ISOs.
>> I blame this on the existing SYSLINUX based production software
>> for distro ISOs. In principle, a pure GRUB2 or a pure SYSLINUX
>> equipment appears to be the more reasonable choice.
>
>
> I once asked in a Debconf why the people were so stubborn to use syslinux
> instead of using grub2 (which seems technically superior to me). It would
> seem that the same people that maintain syslinux happen to maintain the
> kernel boot stack (or whatever it is called, I mean what happens just after
> the bootloader handling the execution to the kernel). So, that means, it's
> far easier to them to debug why the kernel is refusing to boot.
>

I was wondering that also. The GRUB is so cool and can do everything, right?

It also means it can crumble and fall apart in so many interesting ways.

I mean if you install grub on a LVM soft-RAID array and it then does
not boot you are wondering why it happened when it has all those RAID
modules. And you find that it has RAID modules only for the *previous*
revision of the LVM format.

So you do what you would plan for from the start with Syslinux - plug
in an USB stick and put a boot partition on it, yay.

Could have saved hours of debugging by going with the stupid limited
Syslinux from the start, right?

>>> Maybe we can just name them as:
>>> "Main bootloader"
>>> and
>>> "Alternate bootloader".
>>
>>
>> The model does not imply any ranking. "First", "Second", "Third"
>> could be justified, because there are lists in El Torito and
>> partition tables where the boot entries have to line up in sequence.
>>
>> For my taste, "Main" or "Primary" too much implies a rank.
>
>
> So... what about using:
>
> FIRST_BOOTLOADER
> and
> SECOND_BOOTLOADER
>
> instead of my current:
>
> PRIMARY_BOOTLOADER
> and
> SECONDARY_BOOTLOADER
>


why not BOOTLOADERS?

The concept of being primary or secondary is just broken.

You can store 64 el-torito catalog entries on a CD. The different
entries are separated by -eltorito-alt-boot option. When you put the
CD with a BIOS and EFI entry in a machine that prefers UEFI the efi
entry is primary even when there is a CSM. When you put the CD into a
machine with legacy BIOS the BIOS entry is primary in the EFI one
useless.

There are some technical details like it is desirable to put the BIOS
entry before the EFI entry. This may be either enforced by reordering
the bootloader list automagically or just by setting the default to
syslinux,grub-efi and explaining in the docs that this is the usual
order and changing the order may potentially cause issues.

There are more technical details like the bootloader for i386 and
amd64 BIOS is the same one and on EFI it's two different binaries. Or
that when there is an EFI bootloader it's desirable to create another
e-torito entry for it as APM to boot on Macs. The technical details of
creating multiple partitions, boot entries, and whatnot are
implementation details. It's nice to document these details somewhere
for people who want to further butcher the created medium, add support
for more bootloaders, etc.

So basically what we have is support for two PC firmware types:

BIOS
EFI

and two bootloader alternatives for each firmware type

syslinux
grub

and for simlicity only one bootloader for one firmware type is
supported on single medium. Since booting on BIOS platform is well
supported with syslinux and booting on EFI platform is well-supported
with grub it is desirable to have the option to specify different
bootloader type for each supported platform and make it the default.
So rather than

BOOTLOADER=syslinux

Bug#812365: /usr/bin/apt-get: when download of a package list timeouts it is reported as Ign rather than Err

[Michal Suchanek]

Package: apt
Version: 1.0.10.2
Severity: normal
File: /usr/bin/apt-get

Hello,

I was wondering why apt-get update randomly ignores some packages files
and after adding some debug options it turns out that the download times
out and apt reports Ign before the source name.

This is a rather unfortunate way to report download failure.

Timeout should cause Err to be printed just like any other error.

Thanks

Michal

-- Package-specific info:

-- (/etc/apt/preferences present, but not submitted) --


-- (/etc/apt/sources.list present, but not submitted) --


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

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

Versions of packages apt depends on:
ii  debian-archive-keyring  2014.3
ii  gnupg   1.4.19-6
ii  libapt-pkg4.16  1.0.10.2
ii  libc6   2.19-22
ii  libgcc1 1:5.2.1-23
ii  libstdc++6  5.2.1-23

apt recommends no packages.

Versions of packages apt suggests:
pn  apt-doc 
ii  aptitude0.7.4-1
ii  dpkg-dev1.18.3
ii  python-apt  1.0.1

-- no debconf information

Bug#812375: e17: mouse cursor flashing

[Michal Suchanek]

Package: e17
Version: 0.17.6-1
Severity: normal

Hello,

the default mouse cursor in e17 is ridiculously small.

Looking in mouse settings the preset reads 32 pixels.

Setting the cursor to anything larger than 64 pixels causes the cursor
to flash. It seems worse in some applications than others. eg. in the
mouse settings the flashing tends to be minor but in fullscreen terminal
window the cursor can become nearly invisible for seconds.

Maybe if there is some hardware limitation on sensible cursor size the
control panel should try harder to detect it.

Thanks

Michal

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

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

Versions of packages e17 depends on:
ii  dbus-x11   1.10.6-1
ii  e17-data   0.17.6-1
ii  libasound2 1.0.29-1
ii  libc6  2.19-22
ii  libdbus-1-31.10.6-1
ii  libecore-con1  1.8.6-2.3
ii  libecore-evas1 1.8.6-2.3
ii  libecore-file1 1.8.6-2.3
ii  libecore-imf1  1.8.6-2.3
ii  libecore-input11.8.6-2.3
ii  libecore-ipc1  1.8.6-2.3
ii  libecore-x11.8.6-2.3
ii  libecore1  1.8.6-2.3
ii  libedbus1  1.7.10-1
ii  libedje-bin1.8.6-2.3
ii  libedje1   1.8.6-2.3
ii  libeet11.8.6-2.3
ii  libeeze1   1.8.6-2.3
ii  libefreet-bin  1.8.6-2.3
ii  libefreet1a1.8.6-2.3
ii  libeina1   1.8.6-2.3
ii  libeio11.8.6-2.3
ii  libevas1   1.8.6-2.2
ii  libevas1-engines-x [libevas1-engine-software-x11]  1.8.6-2.3
ii  libpam0g   1.1.8-3.2
ii  libxcb-keysyms10.4.0-1
ii  libxcb-shape0  1.11.1-1
ii  libxcb11.11.1-1

Versions of packages e17 recommends:
ii  pm-utils  1.4.1-15

e17 suggests no packages.

-- no debconf information

Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)

[Michal Suchanek]

On 18 January 2016 at 10:43, adrian15 <adrian15...@gmail.com> wrote:
> El 18/01/16 a las 07:31, Michal Suchanek escribió:
>>
>> Hello,
>>
>> thanks for working on this.
>>

>
>> As to the primary and secondary bootloader - how is the efi bootloader
>> secondary? It boots the same as the legacy bootloader. You probably
>> want a concept of compatible bootloaders - that is pairs of
>> bootloaders that can be installed alongside on the same medium.
>
> * What is it a secondary bootloader?
>
> It's what happens when you request mkisofs that your bootloader to be boot
> in second place or as a second partition. I don't know how it actually
> works.
>
> So in grub-efi we just add to the xorriso options:
>
> -eltorito-alt-boot \
>  -e boot/grub/efi.img \
>  -no-emul-boot \
>  -isohybrid-gpt-basdat \
>  -isohybrid-apm-hfsplus
>
> And in syslinux-efi (currently) we add:
>
> -eltorito-alt-boot \
>  --efi-boot boot/efi.img \
>  -append_partition 2 0x01 \
>  binary/boot/efi.img

-eltorito-alt-boot is not documented option of xorriso. For
genisoimage -eltorito-alt-boot denotes start of new bootloader
parameters. So any bootloader is made primary by leaving out
-eltorito-alt-boot.

>
> .
>
> So, I guess the -eltorito-alt-boot does the magic but I'm not sure. Maybe
> someone else can explain it better than me.
>
>
> * About current compatible bootloaders.
> The technology is there. I mean. This is what it's currently available:
>
> binary_grub-efi : Secondary bootloader
> binary_grub-legacy : Primary bootloader
> binary_grub-pc : Primary bootloader
> binary_syslinux : Primary bootloader
> binary_syslinux-efi : Secondary bootloader
>
> so that means, in theory you can request one of these 9 combinations:
>
> grub-legacy
> grub-pc
> syslinux
>
> grub-legacy,grub-efi
> grub-pc,grub-efi
> syslinux,grub-efi
>
> grub-legacy,syslinux-efi
> grub-pc,syslinux-efi
> syslinux,syslinux-efi

You can probably use only one legacy bootloader but syslinux-efi and
grub-efi use different files so it should be possible to install both.
I am not sure how selecting one or the other would work, though.

>
>> Unless
>> the user requests two bootloaders that are incompatible the medium can
>> be created.
>>
>> Ignoring bootloaders is not a good idea. If the user requested
>> something that is not possible the build should report an error and
>> stop.
>
> Yeah, that it's hard to implement from the perspective of a single
> bootloader script. So I decided not to implement it.
>
> You could add an additional script or function named:
> check_compatible_bootable_pairs (as you propose) but then you need to
> maintain that fictional database each time a new bootloader gets in.
>
> That's why I decide to avoid it using it.
>
> What it's straight-forward to implement is one of the only-secondary
> bootloaders finding themselves as a primary bootloader and outputting a
> warning message. But, I'm not sure what to put there as a warning. Any
> suggestion?

Unsupported bootloader combination or whatever.

It should not be a warning however. The script should avoid making
unbootable medium.

Thanks

Michal

Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)

[Michal Suchanek]

Hello,

thanks for working on this.

On 18 January 2016 at 05:24, adrian15  wrote:
> In my last message I forgot to CC many people who are involved in this bug
> so I'm going to refer to my former message, CC some people and finally point
> you to my repo/branches where you might find interesting commits.
>
>
> 1) My original message with attached patches (which you can download to your
> email program and reply from there) can be found at:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731709#153
>
>
> 2) Repo / Branches:
>
> * efi_support_based_on_debian_cd  (
> https://github.com/adrian15/live-build/tree/efi_support_based_on_debian_cd )
> : Original dirty branch where I worked in both syslinux-efi and grub-efi
> bootloaders at the same time
>
> * efi_support_based_on_debian_cd_rebased (
> https://github.com/adrian15/live-build/tree/efi_support_based_on_debian_cd_rebased
> ) : The same branch rebased to have minimal useful commits. syslinux-efi was
> removed from it because it did not boot.

I have checked what EFI platforms I have and it seems neither would be
bootable with this.

1) a Windows tablet that needs signed bootloader - signed grub is
available as non-free package (because it cannot be modified to not
break the signature) and presumably allows booting on such systems
without going through the unlocking stuff which may break your windows
installation.

2) a mac mini which probably needs a GPT and the bootloader stored on
a HFS+ volume or something. Also the bootloader needs to be 'blessed'.
Command for that exists in grub and crashes. Never got this working on
an USB stick.

As to the primary and secondary bootloader - how is the efi bootloader
secondary? It boots the same as the legacy bootloader. You probably
want a concept of compatible bootloaders - that is pairs of
bootloaders that can be installed alongside on the same medium. Unless
the user requests two bootloaders that are incompatible the medium can
be created.

Ignoring bootloaders is not a good idea. If the user requested
something that is not possible the build should report an error and
stop.

Finally it seems that some of the patches reference grub-efi before
the patch that adds support for it. Support for grub-efi should
probably be added before it's referenced in other code (eg set as
default).

Thanks

Michal

Bug#810911: cinnamon: when cinnamon crashes failsafe session is no longer started

[Michal Suchanek]

Package: cinnamon
Version: 2.6.13-1
Severity: normal

Hello,

I upgraded cinnamon to current version and the failsafe session no longer 
includes gnome panel.

This reduces dependencies but when cinnamon actually fails you are left with a 
black screen with a mouse cursor.

It turns out that this screen actually shows my desktop folder (empty after 
fresh installation) so strategically placing some program icons there allows me 
to continue with the session.

Also right-clicking the black screen gives a menu which allows starting a 
terminal.

Neither is very obvious, however.

It would be nice if the failsafe session included some visible program 
menu/launcher.

Thanks

Michal


Xsession: X session started for user at Wed Jan 13 17:24:40 CET 2016
localuser:user being added to access control list
** Message: couldn't access control socket: /run/user/1000/keyring/control: No 
such file or directory
** Message: couldn't access control socket: /run/user/1000/keyring/control: No 
such file or directory
** Message: couldn't access control socket: /run/user/1000/keyring/control: No 
such file or directory
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
=== xinerama setup Configuration ===
  Clone: false
  Output: (null) attached to VGA-0
 status: off
 width: -1
 height: -1
 rate: -1
 primary: false
 position: -1 -1
  Output: Laptop attached to LVDS
 status: on
 width: 1024
 height: 768
 rate: 60
 primary: true
 position: 0 0
  Output: (null) attached to S-video
 status: off
 width: -1
 height: -1
 rate: -1
 primary: false
 position: -1 -1
=== Applying Configuration Configuration ===
  Clone: false
  Output: (null) attached to VGA-0
 status: off
 width: -1
 height: -1
 rate: -1
 primary: false
 position: -1 -1
  Output: Laptop attached to LVDS
 status: on
 width: 1024
 height: 768
 rate: 60
 primary: true
 position: 0 0
  Output: (null) attached to S-video
 status: off
 width: -1
 height: -1
 rate: -1
 primary: false
 position: -1 -1

(cinnamon-settings-daemon:584): power-plugin-WARNING **: Unable to inhibit lid 
switch: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Permission denied

(cinnamon-settings-daemon:584): media-keys-plugin-WARNING **: Unable to inhibit 
keypresses: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Permission 
denied

(cinnamon-settings-daemon:584): color-plugin-WARNING **: There is no colord 
server available
[1452702349,000,xklavier.c:xkl_engine_start_listen/]The backend does not 
require manual layout management - but it is provided by the application
/usr/bin/cinnamon-launcher:8: PyGIWarning: Gtk was imported without specifying 
a version first. Use gi.require_version('Gtk', '3.0') before import to ensure 
that the right version gets loaded.
  from gi.repository import Gtk
x-session-manager[508]: WARNING: Failed to start app: Unable to start 
application: Failed to execute child process "zeitgeist-datahub" (No such file 
or directory)

** (polkit-gnome-authentication-agent-1:697): WARNING **: Unable to register 
authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An 
authentication agent already exists for the given subject
Cannot register authentication agent: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent 
already exists for the given subject
/usr/bin/cinnamon-killer-daemon:7: PyGIWarning: Gtk was imported without 
specifying a version first. Use gi.require_version('Gtk', '3.0') before import 
to ensure that the right version gets loaded.
  from gi.repository import Gtk, Gio

** (nemo:687): WARNING **: Can not determine workarea, guessing at layout
Cjs-Message: JS LOG: About to start Cinnamon
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
x-session-manager[508]: WARNING: Could not launch application 
'print-applet.desktop': Unable to start application: Failed to execute child 
process "system-config-printer-applet" (No such file or directory)

(cinnamon-settings-daemon:584): power-plugin-WARNING **: failed to set dim 
backlight to 30%: csd-backlight-helper failed: Could not get or set the value 
of the backlight: No backlight devices present

St-Message: cogl npot texture sizes NOT supported
Window manager warning: Trying to remove non-existent custom keybinding 
"magnifier-zoom-in".
Window manager warning: Trying to remove non-existent custom keybinding 
"magnifier-zoom-out".
Cjs-Message: JS LOG: Cinnamon started at Wed Jan 13 2016 17:27:52 GMT+0100 (CET)
Cjs-Message: JS LOG: network applet: Cannot find connection for active (or 
connection cannot be read)
failed to create drawable
Cjs-Message: JS LOG: Invalid network device type, is 14
Cjs-Message: JS LOG: network applet: Found connection for active

(cinnamon:680): AccountsService-WARNING **: Could not get current seat: No data 
available

(cinnamon:680): Cogl-WARNING **: 

Bug#810914: /usr/bin/Xorg: cannot start X server

[Michal Suchanek]

Package: xserver-xorg-core
Version: 2:1.17.3-2
Severity: normal
File: /usr/bin/Xorg

Hello,

after recent upgrade I cannot start X server from the console (as root).

X server starts normally when systemd spawns the display manager on boot.

However, starting the X server by hand or resterting the display manager from 
console fails.

I have no idea what to check here.

Thanks

Michal


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

lrwxrwxrwx 1 root root 13 Oct  3  2014 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Oct 28 00:32 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
01:05.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] RS200M [Radeon IGP 330M/340M/345M/350M] [1002:4337]

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

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

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

Kernel version (/proc/version):
---
Linux version 4.3.0-1-686 (debian-ker...@lists.debian.org) (gcc version 5.3.1 
20160101 (Debian 5.3.1-5) ) #1 SMP Debian 4.3.3-5 (2016-01-04)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 21424 Jan 13 17:45 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 21424 Jan 13 17:46 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[   213.334] 
X.Org X Server 1.17.3
Release Date: 2015-10-26
[   213.356] X Protocol Version 11, Revision 0
[   213.364] Build Operating System: Linux 3.16.0-4-amd64 i686 Debian
[   213.372] Current Operating System: Linux nc4000 4.3.0-1-686 #1 SMP Debian 
4.3.3-5 (2016-01-04) i686
[   213.373] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.3.0-1-686 
root=UUID=fde9fa62-0a08-4a39-b63c-610fb20cf7c1 ro quiet splash
[   213.386] Build Date: 27 October 2015  11:29:29PM
[   213.394] xorg-server 2:1.17.3-2 (http://www.debian.org/support) 
[   213.401] Current version of pixman: 0.33.4
[   213.414]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   213.415] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   213.444] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jan 13 17:46:35 
2016
[   213.452] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   213.452] (==) No Layout section.  Using the first Screen section.
[   213.452] (==) No screen section available. Using defaults.
[   213.452] (**) |-->Screen "Default Screen Section" (0)
[   213.452] (**) |   |-->Monitor ""
[   213.453] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   213.453] (==) Automatically adding devices
[   213.453] (==) Automatically enabling devices
[   213.453] (==) Automatically adding GPU devices
[   213.453] (WW) The directory "/usr/share/fonts/X11/misc" does not exist.
[   213.453]Entry deleted from font path.
[   213.453] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   213.453]Entry deleted from font path.
[   213.453] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[   213.453]Entry deleted from font path.
[   213.453] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[   213.453]Entry deleted from font path.
[   213.453] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[   213.453]Entry deleted from font path.
[   213.453] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[   213.453]Entry deleted from font path.
[   213.453] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[   213.453]Entry deleted from font path.
[   213.453] (==) FontPath set to:
built-ins
[   213.453] (==) ModulePath set to "/usr/lib/xorg/modules"
[   213.453] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[   213.453] (II) Loader magic: 0x8026b700
[   213.453] (II) Module ABI versions:
[   213.453]X.Org ANSI C Emulation: 0.4
[   213.453]X.Org Video Driver: 19.0
[   213.453]X.Org XInput driver : 21.0
[   213.453]X.Org Server Extension : 9.0
[   213.466] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_31
[   213.469] (II) xfree86: Adding drm device (/dev/dri/card0)
[   213.471] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
[   213.473] (--) PCI:*(0:1:5:0) 1002:4337:0e11:005a rev 0, Mem @ 
0x9800/134217728, 0x9000/65536, I/O @ 0x2000/256, BIOS @ 
0x/131072
[   213.473] (II) LoadModule: "glx"
[   213.474] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   213.477] (II) Module glx: vendor="X.Org 

Bug#810687: mdadm: eats all cpu time on all cores

[Michal Suchanek]

Package: mdadm
Version: 3.3.4-1.1+b1
Severity: normal

hello,

mdadm eats all CPU time of all cores.

This ShouldNotHappen(tm)

I had a lvm volume on a disk which failed while I was trying to upgrade
the volume to raid1 so my raid configureation is very broken.

killing mdadm only helps temporarily. it restarts itself.

Is there any debug information I can provide before I trash the disks?

Thanks

Michal


-- Package-specific info:
--- mdadm.conf
CREATE owner=root group=disk mode=0660 auto=yes
HOMEHOST 
MAILADDR root
ARRAY metadata=ddf UUID=587baab3:c41402e5:c334b912:99c2ce3f
ARRAY container=587baab3:c41402e5:c334b912:99c2ce3f member=0 
UUID=363fa001:b5660ad0:24715b0d:afaecdb2

--- /etc/default/mdadm
INITRDSTART='none'
AUTOCHECK=true
START_DAEMON=true
DAEMON_OPTIONS="--syslog"
VERBOSE=false

--- /proc/mdstat:
Personalities : [linear] [raid1] 
md126 : inactive sdg[0]
  975585280 blocks super external:/md127/0
   
md127 : inactive sdg[0](S)
  1177304 blocks super external:ddf
   
unused devices: 

--- /proc/partitions:
major minor  #blocks  name

   8   80   31266648 sdf
   8   814193280 sdf1
   8   82   27070464 sdf2
   8   96  976762584 sdg
   8  112  244198584 sdh
   8  113  244197376 sdh1
   8  128  244198584 sdi
   8  129   20481024 sdi1
   8  1303148740 sdi2
   8  132  220564417 sdi4
   70   55562240 loop0
   80   30310400 sda
   81   30310384 sda1

--- LVM physical volumes:
  PV VG   Fmt  Attr PSize   PFree
  /dev/sdg   scratchg lvm2 a--  931.51g 8.00m
--- mount output
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=1005252,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,relatime,size=1612848k,mode=755)
/dev/sdf2 on / type ext3 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=35,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
/dev/sdh1 on /srv/rhev type ext4 (rw,relatime,data=ordered)
/dev/sdi1 on /home type ext3 (rw,relatime,errors=remount-ro,data=ordered)
/dev/sdi4 on /scratch type ext3 (rw,relatime,data=ordered)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=806424k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
usmb on /home/hramrach/mnt type fuse.usmb 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000,max_read=32768)
servo:/srv/samba/au on /home/hramrach/au type fuse.sshfs 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
servo:/srv/scratch/Incoming on /home/hramrach/inc type fuse.sshfs 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
usmb on /home/hramrach/win type fuse.usmb 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000,max_read=32768)
/dev/sda1 on /srv/flash type ext4 (rw,relatime,data=ordered)
usmb on /home/hramrach/data type fuse.usmb 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000,max_read=32768)
usmb on /home/hramrach/inst type fuse.usmb 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000,max_read=32768)
heretic:/media/sdg1 on /home/hramrach/test type fuse.sshfs 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

--- initrd.img-3.16.0-4-amd64:

gzip: /boot/initrd.img-3.16.0-4-amd64: 

Bug#810688: shadowsocks: man page references texinfo documents which don't exist

[Michal Suchanek]

Package: shadowsocks
Version: 2.1.0-1
Severity: normal

Hello,

when reading shadowsocks(1) man page I get this at the bottom:

SEE ALSO
   The  programs  are  documented fully by Shell Xu
    and Clowwindy ,
   available via the
  Info system.

However, both info shadowsocks and info ssserver return the stub
manpages and no actual texinfo documentation.

Please add the texinfo documentation or remove the reference.

Thanks

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (910, 'testing'), (900, 'stable'), (610, 'oldstable'), (410, 
'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages shadowsocks depends on:
ii  dpkg  1.18.3
ii  python2.7.11-1
ii  python-m2crypto   0.22.6~rc4-1
ii  python-pkg-resources  18.8-1

shadowsocks recommends no packages.

shadowsocks suggests no packages.

-- no debconf information

Bug#809221: pkg-config: does not install

[Michal Suchanek]

Package: pkg-config
Version: 0.29-2
Severity: important

Hello,

during upgrade I get this message:

Unpacking pkg-config (0.29-2) over (0.28-1.1) ...
dpkg: error processing archive
/var/cache/apt/archives/pkg-config_0.29-2_amd64.deb (--unpack):
 trying to overwrite '/usr/bin/pkg-config', which is also in package
 pkg-config-bin 0.28-1.1

So upgrade from Jessie version is impossible.

Please fix.

Thanks

Michal



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (910, 'testing'), (900, 'stable'), (610, 'oldstable'), (410, 
'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages pkg-config depends on:
ii  pkg-config-bin  0.28-1.1

pkg-config recommends no packages.

pkg-config suggests no packages.

-- no debconf information

Bug#804349: mplayer2: pulseaudio output poor quality

[Michal Suchanek]

Package: mplayer2
Version: 2.0-728-g2c378c7-4+b1
Followup-For: Bug #804349

Ok, so now I see the problem with pulseaudio/ALSA with USB sound card.

So not OSS specific or sound-card specific.

There is some mplayer <-> pulse incompatibility.

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

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

Versions of packages mplayer2 depends on:
ii  liba52-0.7.4  0.7.4-18
ii  libasound21.0.29-1
ii  libass5   0.13.0-1
ii  libavcodec56  6:11.4-1~deb8u1
ii  libavformat56 6:11.4-1~deb8u1
ii  libavresample26:11.4-1~deb8u1
ii  libavutil54   6:11.4-1~deb8u1
ii  libbluray11:0.9.1-1
ii  libbs2b0  3.1.0+dfsg-2.1
ii  libc6 2.19-22
ii  libcaca0  0.99.beta19-2
ii  libcdio-cdda1 0.83-4.2
ii  libcdio-paranoia1 0.83-4.2
ii  libcdio13 0.83-4.2
ii  libdca0   0.0.5-7
ii  libdirectfb-1.2-9 1.2.10.0-5.1
ii  libdv41.0.0-6
ii  libdvdread4   5.0.3-1
ii  libenca0  1.16-2
ii  libfaad2  2.8.0~cvs20150510-1
ii  libgif4   4.1.6-11
ii  libgl1-mesa-glx [libgl1]  11.0.5-1
ii  libjack-jackd2-0 [libjack-0.116]  1.9.10+20150825git1ed50c92~dfsg-1
ii  libjpeg62-turbo   1:1.4.1-2
ii  liblcms2-22.6-3+b3
ii  liblircclient00.9.0~pre1-1.2
ii  libmad0   0.15.1b-8
ii  libmpg123-0   1.22.4-1
ii  libogg0   1.3.2-1
ii  libpng12-01.2.50-2+b2
ii  libpostproc52 6:0.git20120821-4
ii  libpulse0 7.1-2
ii  libquvi7  0.4.1-3
ii  libsdl1.2debian   1.2.15-12
ii  libsmbclient  2:4.1.17+dfsg-4
ii  libspeex1 1.2~rc1.2-1
ii  libswscale3   6:11.4-1~deb8u1
ii  libtheora01.1.1+dfsg.1-7
ii  libtinfo5 6.0+20151024-2
ii  libvdpau1 1.1.1-3
ii  libvorbis0a   1.3.4-3
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxinerama1  2:1.1.3-1+b1
ii  libxss1   1:1.2.2-1
ii  libxv12:1.0.10-1+b1
ii  libxvidcore4  2:1.3.4-1
ii  libxxf86vm1   1:1.1.4-1
ii  zlib1g1:1.2.8.dfsg-2+b1

mplayer2 recommends no packages.

mplayer2 suggests no packages.

-- no debconf information

Bug#808127: /usr/sbin/grub-macbless: grub-macbless crashes

[Michal Suchanek]

Package: grub-common
Version: 2.02~beta2-29
Severity: normal
File: /usr/sbin/grub-macbless

Hello,

I tried to bless a bootloader and what I get is this:

# gdb grub-macbless
GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from grub-macbless...(no debugging symbols found)...done.
(gdb) r /mnt/EFI/BOOT/BOOTX64.EFI
Starting program: /usr/sbin/grub-macbless /mnt/EFI/BOOT/BOOTX64.EFI
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00462394 in ?? ()
(gdb) bt full
#0  0x00462394 in ?? ()
No symbol table info available.
#1  0x00462b39 in ?? ()
No symbol table info available.
#2  0x00402d1d in ?? ()
No symbol table info available.
#3  0x777f9b45 in __libc_start_main (main=0x402c90, argc=2, 
argv=0x7fffe368, init=, fini=, 
rtld_fini=, stack_end=0x7fffe358) at libc-start.c:287
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, -6085335661786610454, 
4206283, 140737488348000, 0, 0, 6085335660801115370, 
6085319165722969322}, mask_was_saved = 0}}, priv = {pad = {0x0, 
0x0, 0x47a0c0, 0x7fffe368}, data = {prev = 0x0, 
  cleanup = 0x0, canceltype = 4694208}}}
not_first_call = 
#4  0x00402ef4 in ?? ()
No symbol table info available.

Something more should be probably specified on the commandline.

However, it should not crash.

Thanks

Michal


-- Package-specific info:

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

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

Versions of packages grub-common depends on:
ii  gettext-base0.19.6-1
ii  libc6   2.19-22
ii  libdevmapper1.02.1  2:1.02.110-1
ii  libfreetype62.6-2
ii  libfuse22.9.4-1
ii  liblzma55.1.1alpha+20120614-2.1

Versions of packages grub-common recommends:
pn  os-prober  

Versions of packages grub-common suggests:
ii  console-setup  1.134
pn  desktop-base   
pn  grub-emu   
pn  multiboot-doc  
ii  xorriso1.4.0-3

-- no debconf information

Bug#804349: mplayer2: pulseaudio output poor quality

[Michal Suchanek]

Package: mplayer2
Version: 2.0-728-g2c378c7-4+b1
Followup-For: Bug #804349

Hello,

this seems to be resolved disabling vmix in oss.

Thanks

Michal

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

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

Versions of packages mplayer2 depends on:
ii  liba52-0.7.4  0.7.4-18
ii  libasound21.0.29-1
ii  libass5   0.13.0-1
ii  libavcodec56  6:11.4-1~deb8u1
ii  libavformat56 6:11.4-1~deb8u1
ii  libavresample26:11.4-1~deb8u1
ii  libavutil54   6:11.4-1~deb8u1
ii  libbluray11:0.9.1-1
ii  libbs2b0  3.1.0+dfsg-2.1
ii  libc6 2.19-22
ii  libcaca0  0.99.beta19-2
ii  libcdio-cdda1 0.83-4.2
ii  libcdio-paranoia1 0.83-4.2
ii  libcdio13 0.83-4.2
ii  libdca0   0.0.5-7
ii  libdirectfb-1.2-9 1.2.10.0-5.1
ii  libdv41.0.0-6
ii  libdvdread4   5.0.3-1
ii  libenca0  1.16-2
ii  libfaad2  2.8.0~cvs20150510-1
ii  libgif4   4.1.6-11
ii  libgl1-mesa-glx [libgl1]  11.0.5-1
ii  libjack-jackd2-0 [libjack-0.116]  1.9.10+20150825git1ed50c92~dfsg-1
ii  libjpeg62-turbo   1:1.4.1-2
ii  liblcms2-22.6-3+b3
ii  liblircclient00.9.0~pre1-1.2
ii  libmad0   0.15.1b-8
ii  libmpg123-0   1.22.4-1
ii  libogg0   1.3.2-1
ii  libpng12-01.2.50-2+b2
ii  libpostproc52 6:0.git20120821-4
ii  libpulse0 7.1-2
ii  libquvi7  0.4.1-3
ii  libsdl1.2debian   1.2.15-12
ii  libsmbclient  2:4.1.17+dfsg-4
ii  libspeex1 1.2~rc1.2-1
ii  libswscale3   6:11.4-1~deb8u1
ii  libtheora01.1.1+dfsg.1-7
ii  libtinfo5 6.0+20151024-2
ii  libvdpau1 1.1.1-3
ii  libvorbis0a   1.3.4-3
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxinerama1  2:1.1.3-1+b1
ii  libxss1   1:1.2.2-1
ii  libxv12:1.0.10-1+b1
ii  libxvidcore4  2:1.3.4-1
ii  libxxf86vm1   1:1.1.4-1
ii  zlib1g1:1.2.8.dfsg-2+b1

mplayer2 recommends no packages.

mplayer2 suggests no packages.

-- no debconf information

Bug#804349: mplayer2: pulseaudio output poor quality

[Michal Suchanek]

Package: mplayer2
Followup-For: Bug #804349

Hello,

installing an USB sound card resolves the problem with ALSA sound driver
and alsa can be used for non-bluetooth oputput. With pulse/ALSA there is
no problem. So the problem is specific to using pulse/OSS.

Thanks

Michal

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

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

Versions of packages mplayer2 depends on:
ii  liba52-0.7.4  0.7.4-18
ii  libasound21.0.29-1
ii  libass5   0.13.0-1
ii  libavcodec56  6:11.4-1~deb8u1
ii  libavformat56 6:11.4-1~deb8u1
ii  libavresample26:11.4-1~deb8u1
ii  libavutil54   6:11.4-1~deb8u1
ii  libbluray11:0.9.0-1
ii  libbs2b0  3.1.0+dfsg-2.1
ii  libc6 2.19-22
ii  libcaca0  0.99.beta19-2
ii  libcdio-cdda1 0.83-4.2
ii  libcdio-paranoia1 0.83-4.2
ii  libcdio13 0.83-4.2
ii  libdca0   0.0.5-7
ii  libdirectfb-1.2-9 1.2.10.0-5.1
ii  libdv41.0.0-6
ii  libdvdread4   5.0.3-1
ii  libenca0  1.16-2
ii  libfaad2  2.8.0~cvs20150510-1
ii  libgif4   4.1.6-11
ii  libgl1-mesa-glx [libgl1]  11.0.4-1
ii  libjack-jackd2-0 [libjack-0.116]  1.9.10+20150825git1ed50c92~dfsg-1
ii  libjpeg62-turbo   1:1.4.1-2
ii  liblcms2-22.6-3+b3
ii  liblircclient00.9.0~pre1-1.2
ii  libmad0   0.15.1b-8
ii  libmpg123-0   1.22.4-1
ii  libogg0   1.3.2-1
ii  libpng12-01.2.50-2+b2
ii  libpostproc52 6:0.git20120821-4
ii  libpulse0 7.0-1+b1
ii  libquvi7  0.4.1-3
ii  libsdl1.2debian   1.2.15-12
ii  libsmbclient  2:4.1.17+dfsg-4
ii  libspeex1 1.2~rc1.2-1
ii  libswscale3   6:11.4-1~deb8u1
ii  libtheora01.1.1+dfsg.1-7
ii  libtinfo5 6.0+20151024-1
ii  libvdpau1 1.1.1-3
ii  libvorbis0a   1.3.4-3
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxinerama1  2:1.1.3-1+b1
ii  libxss1   1:1.2.2-1
ii  libxv12:1.0.10-1+b1
ii  libxvidcore4  2:1.3.4-1
ii  libxxf86vm1   1:1.1.4-1
ii  zlib1g1:1.2.8.dfsg-2+b1

mplayer2 recommends no packages.

mplayer2 suggests no packages.

-- no debconf information

Bug#804349: mplayer2: pulseaudio output poor quality

[Michal Suchanek]

Package: mplayer2
Version: 2.0-728-g2c378c7-4+b1
Severity: normal

Hello,

I routed my audio through pulse so that I can make use of bluetooth
audio when connected.

When playing though pulse to OSS sound card I get all kind of cracking
and popping. This goes away when using the OSS card directly. I did not
notice any issue with xmms2 using pulse output.

I cannot use ALSA with the sound card because there is some floating
input causing noise and alsa does not provide the mute control to turn
it off.

I am not sure what is with the missing dependencies. The swscale3
library is definitely there:
$ dpkg -S /usr/lib/x86_64-linux-gnu/libswscale.so.3
libswscale3:amd64: /usr/lib/x86_64-linux-gnu/libswscale.so.3

$ dpkg -s libswscale3:amd64
Package: libswscale3
Status: deinstall ok installed
Priority: optional
Section: libs
Installed-Size: 365
Maintainer: Debian Multimedia Maintainers

Architecture: amd64
Multi-Arch: same
Source: libav
Version: 6:11.4-1~deb8u1
Depends: libavutil54 (>= 6:11~beta1), libc6 (>= 2.14)
Pre-Depends: multiarch-support
Description: Libav video scaling library
 Libav is a complete, cross-platform solution to decode, encode, record,
  convert and stream audio and video.
   .
This is the video software scaling library from Libav.
Homepage: http://libav.org/

Any idea how can mplayer output sound through pulse reliably?

iirc I had some pulse problems with mplayer earlier whic I resolved by
removing pulse from my system. With BT audio pulse seems unavoidable,
unfortunately.

Thanks

Michal

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

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

Versions of packages mplayer2 depends on:
ii  liba52-0.7.4  0.7.4-18
ii  libasound21.0.29-1
ii  libass5   0.13.0-1
ii  libavcodec56  6:11.4-1~deb8u1
ii  libavformat56 6:11.4-1~deb8u1
ii  libavresample26:11.4-1~deb8u1
ii  libavutil54   6:11.4-1~deb8u1
ii  libbluray11:0.9.0-1
ii  libbs2b0  3.1.0+dfsg-2.1
ii  libc6 2.19-22
ii  libcaca0  0.99.beta19-2
ii  libcdio-cdda1 0.83-4.2
ii  libcdio-paranoia1 0.83-4.2
ii  libcdio13 0.83-4.2
ii  libdca0   0.0.5-7
ii  libdirectfb-1.2-9 1.2.10.0-5.1
ii  libdv41.0.0-6
ii  libdvdread4   5.0.3-1
ii  libenca0  1.16-2
ii  libfaad2  2.8.0~cvs20150510-1
ii  libgif4   4.1.6-11
ii  libgl1-mesa-glx [libgl1]  11.0.4-1
ii  libjack-jackd2-0 [libjack-0.116]  1.9.10+20150825git1ed50c92~dfsg-1
ii  libjpeg62-turbo   1:1.4.1-2
ii  liblcms2-22.6-3+b3
ii  liblircclient00.9.0~pre1-1.2
ii  libmad0   0.15.1b-8
ii  libmpg123-0   1.20.1-2
ii  libogg0   1.3.2-1
ii  libpng12-01.2.50-2+b2
pn  libpostproc52 
ii  libpulse0 7.0-1
ii  libquvi7  0.4.1-3
ii  libsdl1.2debian   1.2.15-11
ii  libsmbclient  2:4.1.17+dfsg-4
ii  libspeex1 1.2~rc1.2-1
pn  libswscale3   
ii  libtheora01.1.1+dfsg.1-7
ii  libtinfo5 6.0+20150810-1
ii  libvdpau1 1.1.1-3
ii  libvorbis0a   1.3.4-3
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxinerama1  2:1.1.3-1+b1
ii  libxss1   1:1.2.2-1
ii  libxv12:1.0.10-1+b1
ii  libxvidcore4  2:1.3.4-1
ii  libxxf86vm1   1:1.1.4-1
ii  zlib1g1:1.2.8.dfsg-2+b1

mplayer2 recommends no packages.

mplayer2 suggests no packages.

-- no debconf information

Bug#803265: bluetooth.service: sap-server: Operation not permitted (1)

[Michal Suchanek]

Package: bluez
Version: 5.33-1
Followup-For: Bug #803265

Hello,

purging everything bluetooth and reinstalling fixed the problem.

● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Tue 2015-11-03 13:31:15 CET; 1min 4s ago
 Docs: man:bluetoothd(8)
 Main PID: 23714 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
   └─23714 /usr/lib/bluetooth/bluetoothd

Nov 03 13:31:15 iscsi bluetoothd[23714]: Not enough free handles to register 
service
Nov 03 13:31:15 iscsi bluetoothd[23714]: Current Time Service could not be 
registered
Nov 03 13:31:15 iscsi bluetoothd[23714]: gatt-time-server: Input/output error 
(5)
Nov 03 13:31:15 iscsi bluetoothd[23714]: Not enough free handles to register 
service
Nov 03 13:31:15 iscsi bluetoothd[23714]: Not enough free handles to register 
service
Nov 03 13:31:15 iscsi bluetoothd[23714]: Sap driver initialization failed.
Nov 03 13:31:15 iscsi bluetoothd[23714]: sap-server: Operation not permitted (1)
Nov 03 13:31:15 iscsi bluetoothd[23714]: hci0 Load Connection Parameters 
failed: Unknown Command (0x01)
Nov 03 13:31:15 iscsi bluetoothd[23714]: Endpoint registered: sender=:1.998 
path=/MediaEndpoint/A2DPSource
Nov 03 13:31:15 iscsi bluetoothd[23714]: Endpoint registered: sender=:1.998 
path=/MediaEndpoint/A2DPSink

The error message persists so it is in fact just warning that should not
prevent bluetooth from starting. As to the bluetooth service hang on
start there is no useful diagnostic. I suspect it might be caused by
dbus problem but it's working now so I cannot really tell.

Thanks

Michal

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

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

Versions of packages bluez depends on:
ii  dbus 1.10.0-3
ii  init-system-helpers  1.24
ii  kmod 21-1
ii  libc62.19-22
ii  libdbus-1-3  1.10.0-3
ii  libglib2.0-0 2.46.1-1
ii  libreadline6 6.3-8+b3
ii  libudev1 227-2
ii  lsb-base 9.20150917
ii  udev 227-2

bluez recommends no packages.

bluez suggests no packages.

-- Configuration Files:
/etc/init.d/bluetooth [Errno 2] No such file or directory: 
u'/etc/init.d/bluetooth'

-- no debconf information

Bug#803265: bluetooth.service: sap-server: Operation not permitted (1)

[Michal Suchanek]

Package: bluez
Version: 5.33-1
Severity: normal
File: bluetooth.service

Hello,

I tried to use bluetooth headphones.

However, bluetooth does not start.

There are missing configuration files. I did not remove thsese so
probably some upgrade script did.

● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: timeout) since Fri 2015-10-23 18:34:06 CEST; 4 days 
ago
 Docs: man:bluetoothd(8)
  Process: 27310 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, 
status=0/SUCCESS)
 Main PID: 27310 (code=exited, status=0/SUCCESS)
   Status: "Quitting"

Oct 23 18:32:36 iscsi bluetoothd[27310]: Sap driver initialization failed.
Oct 23 18:32:36 iscsi bluetoothd[27310]: sap-server: Operation not permitted (1)
Oct 23 18:32:36 iscsi bluetoothd[27310]: hci0 Load Connection Parameters 
failed: Unknown Command (0x01)
Oct 23 18:34:06 iscsi systemd[1]: bluetooth.service: Start operation timed out. 
Terminating.
Oct 23 18:34:06 iscsi bluetoothd[27310]: Terminating
Oct 23 18:34:06 iscsi bluetoothd[27310]: Stopping SDP server
Oct 23 18:34:06 iscsi bluetoothd[27310]: Exit
Oct 23 18:34:06 iscsi systemd[1]: Failed to start Bluetooth service.
Oct 23 18:34:06 iscsi systemd[1]: bluetooth.service: Unit entered failed state.
Oct 23 18:34:06 iscsi systemd[1]: bluetooth.service: Failed with result 
'timeout'.


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

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

Versions of packages bluez depends on:
ii  dbus 1.10.0-3
ii  init-system-helpers  1.23
ii  kmod 18-3
ii  libc62.19-22
ii  libdbus-1-3  1.10.0-3
ii  libglib2.0-0 2.46.0-2
ii  libreadline6 6.3-8+b3
ii  libudev1 215-17+deb8u2
ii  lsb-base 9.20150917
ii  udev 215-17+deb8u2

bluez recommends no packages.

bluez suggests no packages.

-- Configuration Files:
/etc/init.d/bluetooth [Errno 2] No such file or directory: 
u'/etc/init.d/bluetooth'
/etc/init/bluetooth.conf e6b0122c1e5cd56016859a0767a8cfcb [Errno 2] No such 
file or directory: u'/etc/init/bluetooth.conf e6b0122c1e5cd56016859a0767a8cfcb'

-- no debconf information

Bug#802795: /usr/bin/spicy: man page incomplete

[Michal Suchanek]

Package: spice-client-gtk
Version: 0.29-1
Severity: normal
File: /usr/bin/spicy

Hello,

I wanted to forward my spice server port but I did not find what port is
used for spice in the spicy(1) man page. This man page also references
spicec(1) man page which is not present.

Please fix.

Thanks

Michal

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

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

Versions of packages spice-client-gtk depends on:
ii  libatk1.0-0 2.18.0-1
ii  libc6   2.19-22
ii  libcacard0  1:2.4+dfsg-4
ii  libcairo2   1.14.2-2
ii  libfontconfig1  2.11.0-6.3
ii  libfreetype62.6-2
ii  libgdk-pixbuf2.0-0  2.32.1-1
ii  libglib2.0-02.46.0-2
ii  libgtk2.0-0 2.24.25-3
ii  libjpeg62-turbo 1:1.3.1-12
ii  liblz4-10.0~r130-1
ii  libnspr42:4.10.7-1
ii  libnss3 2:3.17.2-1.1+deb8u2
ii  libopus01.1-2
ii  libpango-1.0-0  1.38.0-3
ii  libpangocairo-1.0-0 1.38.0-3
ii  libpangoft2-1.0-0   1.38.0-3
ii  libpixman-1-0   0.33.2-2
ii  libpulse-mainloop-glib0 7.0-1
ii  libpulse0   7.0-1
ii  libsasl2-2  2.1.26.dfsg1-13+deb8u1
ii  libspice-client-glib-2.0-8  0.29-1
ii  libspice-client-gtk-2.0-4   0.29-1
ii  libssl1.0.0 1.0.2d-1
ii  libusb-1.0-02:1.0.19-1
ii  libusbredirhost10.7-1
ii  libusbredirparser1  0.7-1
ii  libx11-62:1.6.3-1
ii  libxrandr2  2:1.5.0-1
ii  zlib1g  1:1.2.8.dfsg-2+b1

spice-client-gtk recommends no packages.

spice-client-gtk suggests no packages.

-- no debconf information

Bug#801775: iceweasel: eats all memory

[Michal Suchanek]

Package: iceweasel
Version: 41.0.1-1
Severity: normal

Hello

displaying certain profile page on liknedin causes iceweasel to eat all
memory. Usual memory consumption is about 20-30%. With this page
displayed memory consumption is 23%-OOM kill.

Tested versions: 41.0.1-1, 38.2.1esr-1~deb8u, 38.3.0esr-1~deb8u1

As the applets on linkedin are loaded depending on the logged-in user
the exact url is pointless.

FWIW on this page I get the 'get introduced to' applet since I have
linkedin connection to several users that have conenction to the user
whose profile page I am viewing.

However, there are other parts of the profile page that never load fully
before iceweasel crashes.

As all iceweasel/firefox bugs I don't expect it is ever resolved except
by pure chance. I file the bug just for reference in case somebody
stumbles across a usable testcase.

Thanks

Michal


-- Package-specific info:

-- Extensions information
 *tons*
-- Plugins inormation
Name: Google Talk Plugin
Location: /opt/google/talkplugin/libnpgoogletalk.so
Package: google-talkplugin
Status: disabled

Name: Google Talk Plugin Video Renderer
Location: /opt/google/talkplugin/libnpo1d.so
Package: google-talkplugin
Status: enabled

Name: IcedTea-Web Plugin (using IcedTea-Web 1.5.2 (1.5.2-1.1))
Location: /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so
Package: icedtea-7-plugin:amd64
Status: enabled

Name: Shockwave Flash (11.2.202.521)
Location: /usr/lib/flashplugin-nonfree/libflashplayer.so
Status: enabled

Name: Spice Firefox Plugin 2.8
Location: /usr/lib/mozilla/plugins/libnsISpicec.so
Status: enabled


-- Addons package information
ii  google-talkplu 5.41.0.0-1   amd64Google Talk Plugin
ii  icedtea-7-plug 1.5.2-1.1amd64web browser plugin based on OpenJ
ii  iceweasel  41.0.1-1 amd64Web browser based on Firefox

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (910, 'testing'), (900, 'stable'), (610, 'oldstable'), (410, 
'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages iceweasel depends on:
ii  debianutils   4.5.1
ii  fontconfig2.11.0-6.3
ii  libasound21.0.29-1
ii  libatk1.0-0   2.18.0-1
ii  libc6 2.19-22
ii  libcairo2 1.14.2-2
ii  libdbus-1-3   1.10.0-3
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-2
ii  libffi6   3.2.1-3
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.6-2
ii  libgcc1   1:5.2.1-21
ii  libgdk-pixbuf2.0-02.32.1-1
ii  libglib2.0-0  2.46.0-2
ii  libgtk2.0-0   2.24.28-1
ii  libhunspell-1.3-0 1.3.3-3+b1
ii  libnspr4  2:4.10.9-2
ii  libnss3   2:3.20-1
ii  libpango-1.0-01.38.0-3
ii  libsqlite3-0  3.8.11.1-1
ii  libstartup-notification0  0.12-4
ii  libstdc++65.2.1-21
ii  libvpx2   1.4.0-4
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.8-1+b1
ii  libxt61:1.1.4-1+b1
ii  procps2:3.3.10-2
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages iceweasel recommends:
ii  gstreamer1.0-libav 1.6.0-1
ii  gstreamer1.0-plugins-good  1.6.0-1

Versions of packages iceweasel suggests:
ii  fonts-lmodern  2.004.5-1
ii  fonts-stix [otf-stix]  1.1.1-4
ii  libcanberra0   0.30-2.1
ii  libgnomeui-0   2.24.5-3
ii  libgssapi-krb5-2   1.13.2+dfsg-2
pn  mozplugger 

-- no debconf information

Bug#801505: texlive-latex-extra: complaint about weong file in dpkg trigger

[Michal Suchanek]

On 11 October 2015 at 15:32, Norbert Preining <prein...@logic.at> wrote:
> On Sun, 11 Oct 2015, Michal Suchanek wrote:
>> I tried to ugrade libstdc++ and as a result I also needed to upgrade
>> TeX.
> ...
>>   APT prefers stable
>
> Are you running stable? If yes, then you cannot do a partial

I am upgrading from stable. As this upgrade broke 3D on one PC I am
trying to do the upgrade in multiple steps to see if I can find where
it breaks.

> upgrade. You need also to update lmodern and all other packages
> to the versions in testing/unstable.

I tried to upgrade all of TeX and especially texlive-latex-extra is
definitely upgraded.

This is probably the part of the dpkg log that produced the above messages:

2015-10-11 13:17:13 status half-configured man-db:amd64 2.7.0.2-5
2015-10-11 13:17:14 status installed man-db:amd64 2.7.0.2-5
2015-10-11 13:17:15 startup packages configure
2015-10-11 13:17:15 configure fonts-lmodern:all 2.004.5-1 
2015-10-11 13:17:15 status unpacked fonts-lmodern:all 2.004.5-1
2015-10-11 13:17:15 status unpacked fonts-lmodern:all 2.004.5-1
2015-10-11 13:17:15 status half-configured fonts-lmodern:all 2.004.5-1
2015-10-11 13:17:15 status installed fonts-lmodern:all 2.004.5-1
2015-10-11 13:17:15 configure lmodern:all 2.004.5-1 
2015-10-11 13:17:15 status unpacked lmodern:all 2.004.5-1
2015-10-11 13:17:15 status unpacked lmodern:all 2.004.5-1
2015-10-11 13:17:15 status half-configured lmodern:all 2.004.5-1
2015-10-11 13:17:16 status installed lmodern:all 2.004.5-1
2015-10-11 13:17:16 status triggers-pending tex-common:all 6.03
2015-10-11 13:17:16 status triggers-awaited lmodern:all 2.004.5-1
2015-10-11 13:17:16 configure jadetex:all 3.13-16 
2015-10-11 13:17:16 status unpacked jadetex:all 3.13-16
2015-10-11 13:17:16 status unpacked jadetex:all 3.13-16
2015-10-11 13:17:16 status half-configured jadetex:all 3.13-16
2015-10-11 13:17:16 status installed jadetex:all 3.13-16
2015-10-11 13:17:16 status triggers-pending tex-common:all 6.03
2015-10-11 13:17:16 status triggers-awaited jadetex:all 3.13-16
2015-10-11 13:17:17 configure texinfo:amd64 6.0.0.dfsg.1-3 
2015-10-11 13:17:17 status unpacked texinfo:amd64 6.0.0.dfsg.1-3
2015-10-11 13:17:17 status half-configured texinfo:amd64 6.0.0.dfsg.1-3
2015-10-11 13:17:17 status installed texinfo:amd64 6.0.0.dfsg.1-3
2015-10-11 13:17:17 trigproc tex-common:all 6.03 
2015-10-11 13:17:17 status half-configured tex-common:all 6.03
2015-10-11 13:17:17 status installed jadetex:all 3.13-16
2015-10-11 13:17:17 status installed lmodern:all 2.004.5-1
2015-10-11 13:17:23 status installed tex-common:all 6.03
2015-10-11 13:17:24 startup packages configure
2015-10-11 13:51:33 startup archives unpack


>
> Which version of lmodern do you have installed?
>

It would be 2.004.5-1 at that time.

Thanks

Michal

Bug#801505: texlive-latex-extra: complaint about weong file in dpkg trigger

[Michal Suchanek]

Package: texlive-latex-extra
Version: 2015.20150917-1
Severity: normal

Hello,

I tried to ugrade libstdc++ and as a result I also needed to upgrade
TeX.

The TeX dpkg trigger complains about wrong file.

Is this expected transitional state until some packages are rebuilt or
is something broken?

Thanks

Michal

Processing triggers for tex-common (6.03) ...


Warning: Old configuration style found in /etc/texmf/updmap.d
Warning: For now these files have been included, 
Warning: but expect inconsistencies.
Warning: These packages should be rebuild with tex-common.
Warning: Please see /usr/share/doc/tex-common/NEWS.Debian.gz
Warning: found file: /etc/texmf/updmap.d/10lmodern.cfg
Warning: found file: /etc/texmf/updmap.d/10texlive-latex-extra.cfg



##
 List of ls-R files

-rw-r--r-- 1 root root 1498 Oct 11 13:17 /var/lib/texmf/ls-R
-rw-rw-r-- 1 root staff 80 Oct 17  2013 /usr/local/share/texmf/ls-R
lrwxrwxrwx 1 root root 29 Sep  3 02:24 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Sep 17 06:57 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Sep 17 06:57 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
-rw-r--r-- 1 root root 2966 Oct 16  2014 /usr/share/texlive/texmf/ls-R
##
 Config files
-rw-r--r-- 1 root root 838 Oct 11 13:12 /etc/texmf/web2c/texmf.cnf
-rw-r--r-- 1 root root 4030 Oct 11 12:58 /var/lib/texmf/web2c/fmtutil.cnf
lrwxrwxrwx 1 root root 32 Sep 17 06:57 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 2763 Oct 11 13:17 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Jun 27  2011 mktex.cnf
-rw-r--r-- 1 root root 838 Oct 11 13:12 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf
1df66bc319cec731e202eaf39f5d85e1  /etc/texmf/texmf.d/96JadeTeX.cnf

-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'oldstable'), (171, 'unstable'), (151, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages texlive-latex-extra depends on:
ii  preview-latex-style11.87-3+deb8u1
ii  tex-common 6.03
ii  texlive-base   2015.20150917-1
ii  texlive-binaries   2015.20150524.37493-6
ii  texlive-latex-recommended  2015.20150917-1
ii  texlive-pictures   2015.20150917-1

Versions of packages texlive-latex-extra recommends:
ii  texlive-fonts-recommended  2015.20150917-1
ii  texlive-latex-extra-doc2015.20150917-1

Versions of packages texlive-latex-extra suggests:
ii  libfile-which-perl  1.09-1
pn  libspreadsheet-parseexcel-perl  
ii  python-pygments 2.0.1+dfsg-1.1

Versions of packages tex-common depends on:
ii  dpkg  1.17.25
ii  ucf   3.0030

Versions of packages tex-common suggests:
ii  debhelper  9.20150101

Versions of packages texlive-latex-extra is related to:
ii  tex-common6.03
ii  texlive-binaries  2015.20150524.37493-6

-- Configuration Files:
/etc/texmf/tex/latex/contour/contour.cfg 81b59058e250cbe26694be3c10a3fbc1 
[Errno 2] No such file or directory: u'/etc/texmf/tex/latex/contour/contour.cfg 
81b59058e250cbe26694be3c10a3fbc1'
/etc/texmf/updmap.d/10texlive-latex-extra.cfg a7e327c9ad8c69f7fbabd7101047ad13 
[Errno 2] No such file or directory: 
u'/etc/texmf/updmap.d/10texlive-latex-extra.cfg 
a7e327c9ad8c69f7fbabd7101047ad13'

-- debconf information:
  tex-common/check_texmf_missing:
  tex-common/check_texmf_wrong:

Bug#801294: dmsetup segfaults

[Michal Suchanek]

Package: dmsetup
Version: 2:1.02.104-1
Severity: normal

Hello,

I have some problem with my lvm volumes.

one command used for inspecting the volumes would be dmsetup.

However,

$ /sbin/dmsetup --help
Segmentation fault

GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /sbin/dmsetup...(no debugging symbols found)...done.
(gdb) r
Starting program: /sbin/dmsetup --help
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
__strcmp_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:210
210 ../sysdeps/x86_64/multiarch/../strcmp.S: No such file or directory.
(gdb) bt full
#0  __strcmp_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:210
No locals.
#1  0xc134 in ?? ()
No symbol table info available.
#2  0x775f6b45 in __libc_start_main (main=0xb3f0, argc=2, 
argv=0x7fffe378, init=, fini=, 
rtld_fini=, stack_end=0x7fffe368) at libc-start.c:287
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, -3506698109183282375, 
93824992270913, 140737488348016, 0, 0, 3506698109358486329, 
3506714323120730937}, mask_was_saved = 0}}, priv = {pad = {0x0, 
0x0, 0x7fffe390, 0x77ffe1a8}, data = {prev = 0x0, 
  cleanup = 0x0, canceltype = -7280}}}
not_first_call = 
#3  0xda6a in ?? ()
No symbol table info available.

$ ldd /sbin/dmsetup 
linux-vdso.so.1 (0x7ffeadbcd000)
libdevmapper.so.1.02.1 => /lib/x86_64-linux-gnu/libdevmapper.so.1.02.1 
(0x7fa9a934)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fa9a9138000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fa9a8d8e000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 
(0x7fa9a8b69000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7fa9a8b49000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fa9a892b000)
/lib64/ld-linux-x86-64.so.2 (0x55c6f6b66000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7fa9a86bd000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fa9a84b9000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fa9a81b7000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7fa9a7fa)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7fa9a7d9a000)
libattr.so.1 => /lib/x86_64-linux-gnu/libattr.so.1 (0x7fa9a7b94000)


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (910, 'testing'), (900, 'stable'), (610, 'oldstable'), (410, 
'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages dmsetup depends on:
ii  libc6   2.19-22
ii  libdevmapper1.02.1  2:1.02.104-1
ii  util-linux  2.27-3

dmsetup recommends no packages.

dmsetup suggests no packages.

-- no debconf information

Bug#801315: device-mapper: reload ioctl on (251:3) failed: Invalid argument

[Michal Suchanek]

Package: lvm2
Version: 2.02.127-1
Severity: normal
File: /sbin/lvm

Hello,

after trying to mirror my lvm volume it becomes inaccessible with the
error device-mapper: reload ioctl on (251:3) failed: Invalid argument

Examining the stored configurations I restored the most reasonably
looking one but the error persists.

IMHO lvm2 should either report an intelligible error or supply valid arguments
to IOCTLs. As in this ShouldNotHappen(tm).

Thanks

Michal

# lvchange -v -v -ay scratchg/build
  Setting activation/monitoring to 1
  Setting global/locking_type to 1
  Setting global/wait_for_locks to 1
  File-based locking selected.
  Setting global/prioritise_write_locks to 1
  Setting global/locking_dir to /run/lock/lvm
  Setting global/use_lvmlockd to 0
Using logical volume(s) on command line.
  Locking /run/lock/lvm/V_scratchg RB
  Setting response to OK
  Setting response to OK
  Setting name to scratchg
  Setting metadata/format to lvm2
  Setting id to NCqDJK-LdD1-WFg0-ygJt-fQn6-L5sS-dekEX3
  Setting format to lvm2
  Setting device to 2144
  Setting dev_size to 1953525168
  Setting label_sector to 1
  Setting size to 1044480
  Setting start to 4096
  Setting ignore to 0
  Setting response to OK
  Setting response to OK
  Adding scratchg/build to the list of LVs to be processed.
  Processing LV build in VG scratchg.
Activating logical volume "build".
  Locking 
/run/lock/lvm/A_JsXCdjvRu0FIy6Za11Gv8qiCNUAmdZ1cjwibtF1hPITaoVaidRizBVVAkgp18OC 
WB
  Locking LV 
7JsXCdjvRu0FIy6Za11Gv8qiCNUAmdZ1cjwibtF1hPITaoVaidRizBVVAkgp18OC (R)
activation/volume_list configuration setting not defined: Checking only 
host tags for scratchg/build
  /dev/sdg: read_ahead is 256 sectors
  Locking memory
  Setting activation/use_mlockall to 0
  Setting activation/verify_udev_operations to 0
  Getting driver version
  Getting target version for linear
  Found linear target v1.2.1.
  Getting target version for striped
  Found striped target v1.5.1.
Creating scratchg-build
Loading scratchg-build table (251:3)
  device-mapper: reload ioctl on (251:3) failed: Invalid argument
Removing scratchg-build (251:3)
  Unlocking 
/run/lock/lvm/A_JsXCdjvRu0FIy6Za11Gv8qiCNUAmdZ1cjwibtF1hPITaoVaidRizBVVAkgp18OC
  Unlocking memory
  Unlocking /run/lock/lvm/V_scratchg


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (910, 'testing'), (900, 'stable'), (610, 'oldstable'), (410, 
'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages lvm2 depends on:
ii  dmeventd  2:1.02.104-1
ii  dmsetup   2:1.02.104-1
ii  init-system-helpers   1.23
ii  initscripts   2.88dsf-59.2
ii  libc6 2.19-22
ii  libdevmapper-event1.02.1  2:1.02.104-1
ii  libdevmapper1.02.12:1.02.104-1
ii  liblvm2app2.2 2.02.127-1
ii  libreadline5  5.2+dfsg-3
ii  libudev1  226-3
ii  lsb-base  9.20150917

lvm2 recommends no packages.

Versions of packages lvm2 suggests:
pn  thin-provisioning-tools  

-- no debconf information

Bug#731709: Status of 731709

[Michal Suchanek]

Hello,

On 22 September 2015 at 18:47, Has  wrote:
> What's the status of this bug?
>
>>Attached is an updated patch that works on top of 4.0.4
>
> jessie live-build is at version 4.0.3, stretch is at 5.0. Does this patch
> work in stretch? I'm hoping I can patch 5.0 and backport it to jessie as
> this is a very important feature.

1) this patch is not complete

It should pull a bootloader from Debian packages and not depend on the
user adding it as binary include.

2) while includeing the EFI bootloader should make the image EFI
bootable it is not obvious

 - if the image is also BIOS bootable (possibly but not explicitly stated)
 - if the EFI method also works with HDD images with no ISO filesystem
 - what partitions the image includes and if rearranging the
partitions eg to add a data partition as the first entry affects
bootability (currently state of the art bootable USB stick with
Windows-compatible data storage is created by moving the partition
entry for Debian Live partition to second position and creating a data
partition at the first position in MBR using the unallocated space at
the end of the medium)

Thanks

Michal

Bug#733858: aptitude crashes when installing systemd-sysvinit and upgrading sysvinit at the same time

[Michal Suchanek]

Hello,

On 18 September 2015 at 02:09, Manuel A. Fernandez Montecelo
<manuel.montez...@gmail.com> wrote:
> Control: tags -1 + moreinfo
>
>
> Hi Michal,
>
> 2014-01-01 13:15 Michal Suchanek:
>>
>> Package: aptitude
>> Version: 0.6.8.2-1
>> Severity: normal
>>
>> Hello,
>>
>> I wanted to try systemd so
>>
>> 1) installed systemd
>>
>> 2) marked non-conflicting version of sysvinit and systemd-sysv for
>> install
>>
>> 3) proceeded with installetion
>>
>> aptitude crashed endlessly printing information about systemd-sysv
>> conflicting with the sysvinit currently installed
>
>
> In principle this is happening with apt (can be a stack overflow due to
> recursion, and pkgPackageManager::SmartUnPack calls itself and had
> problems with that before, according to the changelog).
>
> But it is possible that it was happening because of aptitude feeding
> wrong values for some reason.  However, with this information and no
> other reports of people complaining about the same issue, it's difficult
> to know what's going on; and right now I cannot set up a similar
> environment to try to reproduce it.
>
> I see that you have a mix of systems, but highest priority stable, so I
> guess that most packages are from the stable distribution at the time
> (didn't check if all versions match, though).
>
> Do you know if this also happened with other packages, or with same
> packages but with later versions of aptitude?

I haven't seen this recently so I guess this is fixed with the apt change.

Thanks

Michal

Bug#797299: wine-development: wine should have stricter dependencies

[Michal Suchanek]

Package: wine-development
Version: 1.7.50-1
Severity: normal

Hello,

I managed to install different pieces of wine in different version which
causes errors and should not happen.

One possibiliy to prevent this is for libwine which is multiarch and
already should conflict with different versions of itself to conflict
with wine bits that are different version than the currently instaled
libwine.

The reasons for this happening may vary - package pinning which pulls
some packages but others do not follow, not all archs uploaded at the
same time, a package index file failing to download for a part of the
archive, etc.

So in case any of this happens the wine package inter-dependencies
should keep all bits the same version.

Thanks

Michal

-- System Information:
Debian Release: 8.1
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'oldstable'), (171, 'unstable'), (151, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages wine-development depends on:
ii  wine32-development  1.7.50-1
ii  wine64-development  1.7.50-1

wine-development recommends no packages.

wine-development suggests no packages.

-- no debconf information

Bug#797058: initramfs-tools: raid1 lvm configuration unsupported

[Michal Suchanek]

Package: initramfs-tools
Version: 0.116
Severity: normal

Hello,

after a power cut I could not boot my system due to missing driver.

I have a lvm raid1 (as opposed to mirror) volume as root.

Unless manually instructed initramfs-tools do not include the dm_raid
and raid1 modules rendering the system unbootable.

I am not sure if this ever worked. This may be the first time I tried to
boot after reconfiguring the lvm.

It would be nice if this worked automagically.

Thanks

Michal

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 12M Aug 26 21:44 /boot/initrd.img-3.2.0-4-amd64
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64 root=/dev/mapper/placka-placka--root ro quiet 
quiet

-- resume
# RESUME=/dev/sda1
RESUME='LABEL=placka-swap'
-- /proc/filesystems
ext4
fuseblk

-- lsmod
Module  Size  Used by
8021q  23480  0 
garp   13193  1 8021q
binfmt_misc12957  1 
ib_iser31680  0 
rdma_cm31663  1 ib_iser
ib_addr12912  1 rdma_cm
iw_cm  13122  1 rdma_cm
ib_cm  31380  1 rdma_cm
ib_sa  22877  2 ib_cm,rdma_cm
ib_mad 36359  2 ib_sa,ib_cm
ib_core48285  6 ib_mad,ib_sa,ib_cm,iw_cm,rdma_cm,ib_iser
iscsi_tcp  17670  0 
libiscsi_tcp   17497  1 iscsi_tcp
libiscsi   35920  3 libiscsi_tcp,iscsi_tcp,ib_iser
scsi_transport_iscsi39337  4 libiscsi,iscsi_tcp,ib_iser
fuse   62012  1 
bridge 70603  0 
stp12437  2 bridge,garp
xt_length  12460  2 
xt_mark12453  39 
cls_fw 12965  5 
sch_sfq13172  5 
sch_htb17923  1 
iptable_mangle 12536  1 
xt_tcpudp  12570  91 
xt_conntrack   12681  6 
xt_state   12503  4 
xt_dscp12523  0 
xt_DSCP12643  0 
xt_CLASSIFY12429  0 
ipt_LOG12605  0 
ipt_REJECT 12502  0 
xt_owner   12423  1 
nf_nat_ftp 12460  0 
nf_conntrack_ftp   12605  1 nf_nat_ftp
nf_nat_sip 12923  0 
nf_conntrack_sip   26054  1 nf_nat_sip
nf_nat_h32312918  0 
nf_conntrack_h323  42413  1 nf_nat_h323
nf_nat_pptp12603  0 
nf_nat_proto_gre   12517  1 nf_nat_pptp
nf_conntrack_pptp  12769  1 nf_nat_pptp
nf_conntrack_proto_gre12974  1 nf_conntrack_pptp
nf_nat_irc 12454  0 
nf_conntrack_irc   12427  1 nf_nat_irc
iptable_filter 12536  1 
iptable_nat12928  1 
ipt_MASQUERADE 12594  1 
nf_nat 18242  8 
ipt_MASQUERADE,iptable_nat,nf_nat_irc,nf_nat_proto_gre,nf_nat_pptp,nf_nat_h323,nf_nat_sip,nf_nat_ftp
xt_multiport   12548  0 
xt_iprange 12504  0 
nf_conntrack_ipv4  14078  13 nf_nat,iptable_nat
nf_defrag_ipv4 12483  1 nf_conntrack_ipv4
nf_conntrack   52720  17 
nf_conntrack_ipv4,nf_nat,ipt_MASQUERADE,iptable_nat,nf_conntrack_irc,nf_nat_irc,nf_conntrack_proto_gre,nf_conntrack_pptp,nf_nat_pptp,nf_conntrack_h323,nf_nat_h323,nf_conntrack_sip,nf_nat_sip,nf_conntrack_ftp,nf_nat_ftp,xt_state,xt_conntrack
ip_tables  22042  3 iptable_nat,iptable_filter,iptable_mangle
x_tables   19118  18 
ip_tables,xt_iprange,xt_multiport,ipt_MASQUERADE,iptable_nat,iptable_filter,xt_owner,ipt_REJECT,ipt_LOG,xt_CLASSIFY,xt_DSCP,xt_dscp,xt_state,xt_conntrack,xt_tcpudp,iptable_mangle,xt_mark,xt_length
kvm_amd47218  0 
kvm   291965  1 kvm_amd
loop   22641  0 
btusb  17502  0 
psmouse69265  0 
arc4   12458  2 
eeepc_wmi  12564  0 
asus_wmi   18726  1 eeepc_wmi
radeon722295  1 
ath9k  64619  0 
ath9k_common   12728  1 ath9k
serio_raw  12931  0 
pcspkr 12579  0 
evdev  17562  5 
sparse_keymap  12760  1 asus_wmi
ath3k  12671  0 
ath9k_hw  322112  2 ath9k_common,ath9k
ath21370  3 ath9k_hw,ath9k_common,ath9k
mac80211  192806  1 ath9k
cfg80211  137243  3 mac80211,ath,ath9k
sp5100_tco 12900  0 
powernow_k817618  0 
ttm53664  1 radeon
bluetooth 119455  2 ath3k,btusb
drm_kms_helper 31370  1 radeon
mperf  12453  1 powernow_k8
snd_hda_codec_realtek   188851  1 
i2c_piix4  12536  0 
rfkill 19012  4 bluetooth,cfg80211,asus_wmi
drm   183952  3 drm_kms_helper,ttm,radeon
mcs783013240  0 
usbnet 18027  1 mcs7830
snd_hda_codec_hdmi 30824  1 
k10temp12611  0 
snd_hda_intel  26259  0 
snd_hda_codec  78031  3 

Bug#94200: should work on RAID partitions

[Michal Suchanek]

Package: grub
Version: 0.97-66
Followup-For: Bug #94200

Hello,

I have a lvm raid1 root and after power cut I was unable to boot.

I moved /boot to an USB stick and installed grub there to be able to
boot.

grub does not seem to understand lvm raid1 at all.


grub-probe: info: Scanning for dmraid_nv RAID devices on disk hd0.
grub-probe: info: the size of hd0 is 7744512.
grub-probe: info: the size of hd0 is 7744512.
grub-probe: info: Scanning for dmraid_nv RAID devices on disk hd1.
grub-probe: info: the size of hd1 is 7814037168.
grub-probe: info: the size of hd1 is 7814037168.
grub-probe: info: Scanning for dmraid_nv RAID devices on disk hd2.
grub-probe: info: the size of hd2 is 3907029168.
grub-probe: info: the size of hd2 is 3907029168.
grub-probe: info: scanning hd0 for LVM.
grub-probe: info: the size of hd0 is 7744512.
grub-probe: info: no LVM signature found.
grub-probe: info: the size of hd0 is 7744512.
grub-probe: info: scanning hd1 for LVM.
grub-probe: info: the size of hd1 is 7814037168.
grub-probe: info: no LVM signature found.
grub-probe: info: the size of hd1 is 7814037168.
grub-probe: info: scanning hd2 for LVM.
grub-probe: info: the size of hd2 is 3907029168.
grub-probe: info: no LVM signature found.
grub-probe: info: the size of hd2 is 3907029168.
grub-probe: info: Scanning for mdraid09 RAID devices on disk hd0.
grub-probe: info: the size of hd0 is 7744512.
grub-probe: info: the size of hd0 is 7744512.
grub-probe: info: Scanning for mdraid09 RAID devices on disk hd1.
grub-probe: info: the size of hd1 is 7814037168.
grub-probe: info: the size of hd1 is 7814037168.
grub-probe: info: Scanning for mdraid09 RAID devices on disk hd2.
grub-probe: info: the size of hd2 is 3907029168.
grub-probe: info: the size of hd2 is 3907029168.
grub-probe: info: Scanning for mdraid1x RAID devices on disk hd0.
grub-probe: info: the size of hd0 is 7744512.
grub-probe: info: the size of hd0 is 7744512.
grub-probe: info: Scanning for mdraid1x RAID devices on disk hd1.
grub-probe: info: the size of hd1 is 7814037168.
grub-probe: info: the size of hd1 is 7814037168.
grub-probe: info: Scanning for mdraid1x RAID devices on disk hd2.
grub-probe: info: the size of hd2 is 3907029168.
grub-probe: info: the size of hd2 is 3907029168.
grub-probe: info: Scanning for mdraid09 RAID devices on disk hd0.
grub-probe: info: the size of hd0 is 7744512.
grub-probe: info: the size of hd0 is 7744512.
grub-probe: info: Scanning for mdraid09 RAID devices on disk hd0,msdos1.
grub-probe: info: the size of hd0 is 7744512.
grub-probe: info: Scanning for mdraid09 RAID devices on disk hd1.
grub-probe: info: the size of hd1 is 7814037168.
grub-probe: info: the size of hd1 is 7814037168.
grub-probe: info: Scanning for mdraid09 RAID devices on disk hd1,gpt1.
grub-probe: info: the size of hd1 is 7814037168.
grub-probe: info: Scanning for mdraid09 RAID devices on disk hd2.
grub-probe: info: the size of hd2 is 3907029168.
grub-probe: info: the size of hd2 is 3907029168.
grub-probe: info: Scanning for mdraid09 RAID devices on disk hd2,gpt1.
grub-probe: info: the size of hd2 is 3907029168.
grub-probe: info: Scanning for mdraid1x RAID devices on disk hd0.
grub-probe: info: the size of hd0 is 7744512.
grub-probe: info: the size of hd0 is 7744512.
grub-probe: info: Scanning for mdraid1x RAID devices on disk hd0,msdos1.
grub-probe: info: the size of hd0 is 7744512.
grub-probe: info: Scanning for mdraid1x RAID devices on disk hd1.
grub-probe: info: the size of hd1 is 7814037168.
grub-probe: info: the size of hd1 is 7814037168.
grub-probe: info: Scanning for mdraid1x RAID devices on disk hd1,gpt1.
grub-probe: info: the size of hd1 is 7814037168.
grub-probe: info: Scanning for mdraid1x RAID devices on disk hd2.
grub-probe: info: the size of hd2 is 3907029168.
grub-probe: info: the size of hd2 is 3907029168.
grub-probe: info: Scanning for mdraid1x RAID devices on disk hd2,gpt1.
grub-probe: info: the size of hd2 is 3907029168.
grub-probe: info: scanning hd0 for LVM.
grub-probe: info: the size of hd0 is 7744512.
grub-probe: info: no LVM signature found.
grub-probe: info: the size of hd0 is 7744512.
grub-probe: info: scanning hd0,msdos1 for LVM.
grub-probe: info: the size of hd0 is 7744512.
grub-probe: info: no LVM signature found.
grub-probe: info: scanning hd1 for LVM.
grub-probe: info: the size of hd1 is 7814037168.
grub-probe: info: no LVM signature found.
grub-probe: info: the size of hd1 is 7814037168.
grub-probe: info: scanning hd1,gpt1 for LVM.
grub-probe: info: the size of hd1 is 7814037168.
grub-probe: info: unknown LVM type raid1
..
grub-probe: info: unknown LVM type raid1
..
grub-probe: info: unknown LVM type raid1
..
grub-probe: info: unknown LVM type raid1
..
grub-probe: info: the size of hd1 is 7814037168.
grub-probe: info: scanning hd2 for LVM.
grub-probe: info: the size of hd2 is 3907029168.
grub-probe: info: no LVM signature found.
grub-probe: info: the size of hd2 is 3907029168.
grub-probe: info: scanning hd2,gpt1 for LVM.
grub-probe: info: 

Bug#797102: linux-image-4.0.0-1-amd64: radeon KMS display regression - monitor blank

[Michal Suchanek]

Package: src:linux
Version: 4.0.2-1
Severity: normal

Hello,

After power outage when my system rebooted my display would show just
Input not supported message.

This is the earliest broken kernel and this goes up to 4.2.0-rc8

Out of the kernels I have installed latest working is
linux-image-3.18.0-trunk 3.18.5-1~exp1

The monitor is connected over displayport and works in 1920x1080 but not
the native 2560x1440 resolution.

This is probably upstream problem.

 RADEON(0): Chipset: ATI Radeon HD 5670 (ChipID = 0x68d8)

I guess I will just remove the newer kernels.

Thanks

Michal

-- Package-specific info:
** Version:
Linux version 4.0.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.9.2 
(Debian 4.9.2-16) ) #1 SMP Debian 4.0.2-1 (2015-05-11)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.0.0-1-amd64 
root=UUID=c24506ba-3af2-456e-a23c-53fa182a57bf ro

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[   13.257388]  uvdvclk: 0 dclk: 0
[   13.257388]  power level 0sclk: 15700 mclk: 3 vddc: 1000 
vddci: 0
[   13.257389]  power level 1sclk: 4 mclk: 9 vddc: 1000 
vddci: 0
[   13.257389]  power level 2sclk: 77500 mclk: 10 vddc: 1100 
vddci: 0
[   13.257390]  status: c 
[   13.257390] switching to power state:
[   13.257391]  ui class: performance
[   13.257391]  internal class: none
[   13.257392]  caps: video 
[   13.257392]  uvdvclk: 0 dclk: 0
[   13.257393]  power level 0sclk: 4 mclk: 10 vddc: 1100 
vddci: 0
[   13.257393]  power level 1sclk: 4 mclk: 10 vddc: 1100 
vddci: 0
[   13.257394]  power level 2sclk: 77500 mclk: 10 vddc: 1100 
vddci: 0
[   13.257394]  status: r 
[   13.361638] Console: switching to colour frame buffer device 160x64
[   13.365439] radeon :01:00.0: fb0: radeondrmfb frame buffer device
[   13.365442] radeon :01:00.0: registered panic notifier
[   13.376066] [drm] Initialized radeon 2.41.0 20080528 for :01:00.0 on 
minor 0
[   13.763407] usbcore: registered new interface driver usbserial
[   13.763426] usbcore: registered new interface driver usbserial_generic
[   13.763442] usbserial: USB Serial support registered for generic
[   13.766615] usbcore: registered new interface driver pl2303
[   13.766634] usbserial: USB Serial support registered for pl2303
[   13.70] pl2303 7-1:1.0: pl2303 converter detected
[   13.778312] usb 7-1: pl2303 converter now attached to ttyUSB0
[   24.558494] EXT4-fs (sdf3): mounted filesystem with ordered data mode. Opts: 
(null)
[   24.577883] EXT4-fs (sdf4): mounted filesystem with ordered data mode. Opts: 
(null)
[   24.591748] EXT4-fs (sda): mounted filesystem with ordered data mode. Opts: 
(null)
[   24.744279] tun: Universal TUN/TAP device driver, 1.6
[   24.744282] tun: (C) 1999-2004 Max Krasnyansky m...@qualcomm.com
[   24.878772] bridge: automatic filtering via arp/ip/ip6tables has been 
deprecated. Update your scripts to load br_netfilter if you need this.
[   24.884052] device tap0 entered promiscuous mode
[   24.886089] device tap1 entered promiscuous mode
[   24.886939] device tap2 entered promiscuous mode
[   24.888454] device tap3 entered promiscuous mode
[   24.889376] tapbr: port 4(tap3) entered forwarding state
[   24.889381] tapbr: port 4(tap3) entered forwarding state
[   24.889383] tapbr: port 3(tap2) entered forwarding state
[   24.889385] tapbr: port 3(tap2) entered forwarding state
[   24.889387] tapbr: port 2(tap1) entered forwarding state
[   24.889389] tapbr: port 2(tap1) entered forwarding state
[   24.889391] tapbr: port 1(tap0) entered forwarding state
[   24.889392] tapbr: port 1(tap0) entered forwarding state
[   25.705977] Adding 5191676k swap on /scratch/build/swap.  Priority:1 
extents:1505 across:5583632k SSFS
[   25.744030] tapbr: port 1(tap0) entered disabled state
[   25.744051] tapbr: port 2(tap1) entered disabled state
[   25.744061] tapbr: port 3(tap2) entered disabled state
[   25.744070] tapbr: port 4(tap3) entered disabled state
[   25.961636] iscsi: registered transport (iser)
[   30.622880] RPC: Registered named UNIX socket transport module.
[   30.622883] RPC: Registered udp transport module.
[   30.622884] RPC: Registered tcp transport module.
[   30.622884] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   30.690306] FS-Cache: Loaded
[   30.780832] FS-Cache: Netfs 'nfs' registered for caching
[   30.916481] systemd-journald[234]: Received request to flush runtime journal 
from PID 1
[   31.056674] Installing knfsd (copyright (C) 1996 o...@monad.swb.de).
[   31.281157] oss_hdaudio: HDA codec 0x11d41882 not known yet
[   31.291008] oss_hdaudio: Too many connections(B) for widget 35 (24)
[   31.296761] oss_hdaudio: HDA codec 0x11d41882 not known yet
[   32.660947] Process accounting resumed
[   33.998231] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery 
directory
[   33.999047] NFSD: starting 90-second grace period (net 

Bug#793783: mtd-utils: mtd_debug does not check amount of data read

[Michal Suchanek]

Package: mtd-utils
Version: 1:1.5.1-1.1rck1
Severity: normal

Hello,

the kernel refuses to read more data from a MTD device than the device
size. However, mtd_debug does not check the amount of data read as
returned by read(2) and assumes the requested amount is always read when
there is no error. Reading 8M data from a 4M flash chip results in 8M
file containing the flash data at the start.

Attaching patch to fix the issue.

Thanks

Michal

-- System Information:
Debian Release: 8.1
  APT prefers stable
  APT policy: (900, 'stable'), (510, 'unstable'), (505, 'experimental'), (500, 
'oldstable')
Architecture: armhf (armv7l)
Foreign Architectures: i386

Kernel: Linux 4.2.0-rc3-00168-gf94f5ae (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages mtd-utils depends on:
ii  libc6  2.19-18
ii  liblzo2-2  2.08-1.2
ii  libuuid1   2.25.2-6
ii  zlib1g 1:1.2.8.dfsg-2+b1

mtd-utils recommends no packages.

mtd-utils suggests no packages.

-- no debconf information
Index: mtd-utils-1.5.1/mtd_debug.c
===
--- mtd-utils-1.5.1.orig/mtd_debug.c	2015-07-27 15:31:52.143449285 +0200
+++ mtd-utils-1.5.1/mtd_debug.c	2015-07-27 15:32:12.153449294 +0200
@@ -141,7 +141,10 @@
 			perror(read());
 			goto err2;
 		}
-		err = write(outfd, buf, size);
+		if (err  size) {
+			fprintf(stderr, %s: short read, requested %#x, read %#x\n, __func__, size, err);
+		}
+		err = write(outfd, buf, err);
 		if (err  0) {
 			fprintf(stderr, %s: write, size %#x, n %#x\n, __func__, size, n);
 			perror(write());

Bug#763895: cinnamon crashes when a window opens

[Michal Suchanek]

Package: cinnamon
Followup-For: Bug #763895

Hello,

I upgraded the system with this problem to Jessie release and booted the stable 
kernel and the problem did not go away.

So I upgraded kernel, libdrm, mesa, cogl, cairo, muffin and Xorg to latest 
versions in Debian and the problem went away.

I can run a terminal and it shows a dropshadow and cinnamon does not crash.

So that's it. I guess kernel, libdrm and mesa are most important here.


Thanks

Michal



-- System Information:
Debian Release: 8.1
  APT prefers stable
  APT policy: (900, 'stable'), (800, 'oldstable'), (600, 'testing'), (500, 
'unstable'), (110, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.1.0-trunk-586
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: upstart (via init_is_upstart())

Versions of packages cinnamon depends on:
ii  caribou  0.4.15-1
ii  cinnamon-common  2.6.12-1
ii  cinnamon-control-center  2.6.0-1
ii  cinnamon-desktop-data2.6.5-1
ii  cinnamon-screensaver 2.6.4-1
ii  cinnamon-session 2.6.3-1
ii  cinnamon-settings-daemon 2.6.3-1
ii  cjs  2.6.2-1
ii  cups-pk-helper   0.2.5-2+b1
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  gir1.2-accountsservice-1.0   0.6.37-3+b1
ii  gir1.2-caribou-1.0   0.4.15-1
ii  gir1.2-clutter-1.0   1.22.4-1
ii  gir1.2-cmenu-3.0 2.6.0-2
ii  gir1.2-cogl-1.0  1.20.0-2
ii  gir1.2-gconf-2.0 3.2.6-3
ii  gir1.2-gdkpixbuf-2.0 2.31.1-2+b1
ii  gir1.2-gkbd-3.0  3.6.0-1
ii  gir1.2-glib-2.0  1.42.0-2.2
ii  gir1.2-gnomedesktop-3.0  3.14.1-1
ii  gir1.2-gtk-3.0   3.14.5-1
ii  gir1.2-gtkclutter-1.01.6.0-1
ii  gir1.2-javascriptcoregtk-3.0 2.4.8-2
ii  gir1.2-keybinder-3.0 0.3.0-1
ii  gir1.2-meta-muffin-0.0   2.6.1-3
ii  gir1.2-networkmanager-1.00.9.10.0-7
ii  gir1.2-notify-0.70.7.6-2
ii  gir1.2-pango-1.0 1.36.8-3
ii  gir1.2-polkit-1.00.105-8
ii  gir1.2-soup-2.4  2.48.0-1
ii  gir1.2-upowerglib-1.00.99.1-3.2
ii  gir1.2-webkit-3.02.4.8-2
ii  gkbd-capplet 3.6.0-1
ii  gnome-backgrounds3.14.1-1
ii  gnome-icon-theme-symbolic3.12.0-1
ii  gnome-themes-standard3.14.2.2-1
ii  gsettings-desktop-schemas3.14.1-1
ii  libatk-bridge2.0-0   2.14.0-2
ii  libatk1.0-0  2.14.0-1
ii  libc62.19-18
ii  libcairo21.14.2-2
ii  libcinnamon-menu-3-0 2.6.0-2
ii  libcjs0  2.6.2-1
ii  libclutter-1.0-0 1.22.4-1
ii  libcogl-pango20  1.20.0-2
ii  libcogl-path20   1.20.0-2
ii  libcogl201.20.0-2
ii  libcroco30.6.8-3+b1
ii  libgcc1  1:4.9.2-10
ii  libgdk-pixbuf2.0-0   2.31.1-2+b1
ii  libgirepository-1.0-11.42.0-2.2
ii  libgl1-mesa-glx [libgl1] 10.5.9-2
ii  libglib2.0-0 2.42.1-1
ii  libglib2.0-bin   2.42.1-1
ii  libgstreamer1.0-01.4.4-2
ii  libgtk-3-0   3.14.5-1
ii  libjs-jquery 1.7.2+dfsg-3.2
ii  libmozjs-24-024.2.0-2
ii  libmuffin0   2.6.1-3
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpulse-mainloop-glib0  5.0-13
ii  libpulse05.0-13
ii  libstartup-notification0 0.12-4
ii  libx11-6 2:1.6.2-3
ii  libxfixes3   1:5.0.1-2+b2
ii  libxml2  2.9.1+dfsg1-5
ii  mesa-utils   8.2.0-1
ii  nemo 2.6.7-1
pn  policykit-1-gnomenone
ii  python   

Bug#765017: SECURITY - normal users are allowed full access to USB devices per default

[Michal Suchanek]

Package: libspice-client-glib-2.0-8
Version: 0.28-1
Followup-For: Bug #765017

Hello,

This problem is no longer present with current version of
libspice-client-glib-2.0-8

This is probably due to a change in the policykit and/or the helper
included with the library.

Either way, I cannot access devices for which I have write permission
since policykit denies the access and opening the device directly is not
attempted.

I guess you can close this.

Thanks

Michal


-- System Information:
Debian Release: 8.1
  APT prefers stable
  APT policy: (900, 'stable'), (610, 'oldstable'), (500, 'testing'), (410, 
'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.1.0-rc7+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages libspice-client-glib-2.0-8 depends on:
ii  libc6 2.19-18
ii  libglib2.0-0  2.42.1-1
ii  libjpeg62-turbo   1:1.3.1-12
ii  liblz4-1  0.0~r122-2
ii  libopus0  1.1-2
ii  libpixman-1-0 0.32.6-3
ii  libpulse-mainloop-glib0   5.0-13
ii  libpulse0 5.0-13
ii  libsasl2-22.1.26.dfsg1-13
ii  libssl1.0.0   1.0.1k-3+deb8u1
ii  libusb-1.0-0  2:1.0.19-1
ii  libusbredirhost1  0.7-1
ii  libusbredirparser10.7-1
ii  multiarch-support 2.19-18
ii  spice-client-glib-usb-acl-helper  0.25-1+b1
ii  zlib1g1:1.2.8.dfsg-2+b1

libspice-client-glib-2.0-8 recommends no packages.

libspice-client-glib-2.0-8 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#790426: libspice-client-glib-2.0-8: Cannot access USB devices from spice client

[Michal Suchanek]

Package: libspice-client-glib-2.0-8
Version: 0.28-1
Severity: normal

Hello,

I set up udev rules to enable access to select USB devices from my
account but I cannot redirect them from the spice client.

This is because I did not set up policy kit permissions for those
devices and opening the device directly is not attempted when policylit
support is enabled.

Sending a patch that fixes this.

Thanks

Michal

-- System Information:
Debian Release: 8.1
  APT prefers stable
  APT policy: (900, 'stable'), (610, 'oldstable'), (500, 'testing'), (410, 
'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.1.0-rc7+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages libspice-client-glib-2.0-8 depends on:
ii  libc6 2.19-18
ii  libglib2.0-0  2.42.1-1
ii  libjpeg62-turbo   1:1.3.1-12
ii  liblz4-1  0.0~r122-2
ii  libopus0  1.1-2
ii  libpixman-1-0 0.32.6-3
ii  libpulse-mainloop-glib0   5.0-13
ii  libpulse0 5.0-13
ii  libsasl2-22.1.26.dfsg1-13
ii  libssl1.0.0   1.0.1k-3+deb8u1
ii  libusb-1.0-0  2:1.0.19-1
ii  libusbredirhost1  0.7-1
ii  libusbredirparser10.7-1
ii  multiarch-support 2.19-18
ii  spice-client-glib-usb-acl-helper  0.25-1+b1
ii  zlib1g1:1.2.8.dfsg-2+b1

libspice-client-glib-2.0-8 recommends no packages.

libspice-client-glib-2.0-8 suggests no packages.

-- no debconf information
Even if polkit is used try to open the device first.
Otherwise user accessible devices are denied because of negative polkit reply.
Index: spice-gtk-0.28/gtk/channel-usbredir.c
===
--- spice-gtk-0.28.orig/gtk/channel-usbredir.c	2015-02-06 02:24:10.0 +0100
+++ spice-gtk-0.28/gtk/channel-usbredir.c	2015-06-29 14:49:44.962340089 +0200
@@ -319,9 +319,7 @@
 {
 SpiceUsbredirChannelPrivate *priv = channel-priv;
 GSimpleAsyncResult *result;
-#if ! USE_POLKIT
 GError *err = NULL;
-#endif
 
 g_return_if_fail(SPICE_IS_USBREDIR_CHANNEL(channel));
 g_return_if_fail(device != NULL);
@@ -348,28 +346,28 @@
 priv-device = libusb_ref_device(device);
 priv-spice_device = g_boxed_copy(spice_usb_device_get_type(),
   spice_device);
+if (!spice_usbredir_channel_open_device(channel, err)) {
 #if USE_POLKIT
-priv-result = result;
-priv-state  = STATE_WAITING_FOR_ACL_HELPER;
-priv-acl_helper = spice_usb_acl_helper_new();
-g_object_set(spice_channel_get_session(SPICE_CHANNEL(channel)),
- inhibit-keyboard-grab, TRUE, NULL);
-spice_usb_acl_helper_open_acl(priv-acl_helper,
-  libusb_get_bus_number(device),
-  libusb_get_device_address(device),
-  cancellable,
-  spice_usbredir_channel_open_acl_cb,
-  channel);
-return;
+priv-result = result;
+priv-state  = STATE_WAITING_FOR_ACL_HELPER;
+priv-acl_helper = spice_usb_acl_helper_new();
+g_object_set(spice_channel_get_session(SPICE_CHANNEL(channel)),
+inhibit-keyboard-grab, TRUE, NULL);
+spice_usb_acl_helper_open_acl(priv-acl_helper,
+libusb_get_bus_number(device),
+libusb_get_device_address(device),
+cancellable,
+spice_usbredir_channel_open_acl_cb,
+channel);
+return;
 #else
-if (!spice_usbredir_channel_open_device(channel, err)) {
 g_simple_async_result_take_error(result, err);
 libusb_unref_device(priv-device);
 priv-device = NULL;
 g_boxed_free(spice_usb_device_get_type(), priv-spice_device);
 priv-spice_device = NULL;
-}
 #endif
+}
 
 done:
 g_simple_async_result_complete_in_idle(result);

Bug#790417: fonts-misaki: zero font height

[Michal Suchanek]

Package: fonts-misaki
Version: 11-20080603-15
Severity: normal

Hello,

the Misaki font has zero font height which crashes Wine. For details see
bug #788809

Workaround in Wine is applied but this should be fixed in the font as
well.

Thanks

Michal


-- System Information:
Debian Release: 8.1
  APT prefers stable
  APT policy: (900, 'stable'), (610, 'oldstable'), (500, 'testing'), (410, 
'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.1.0-rc7+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages fonts-misaki depends on:
ii  dpkg  1.17.25

fonts-misaki recommends no packages.

fonts-misaki 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#788809: wine-development: floating point exception rendereing Mitra Mono font

[Michal Suchanek]

Package: wine-development
Version: 1.7.45-1
Followup-For: Bug #788809

Hello,

after some more testing I found that the culprit is Misaki font:

Removing ttf-misaki (11-20080603-13) ...
Removing fonts-misaki (11-20080603-15) ...

It is alphabetically before Mitra so Mitra appeared selected when Wine
was trying to render the character preview for Misaki and crashed.

I cannot see the name of either font in the backtrace.

Thanks

Michal

-- System Information:
Debian Release: 8.1
  APT prefers stable
  APT policy: (900, 'stable'), (610, 'oldstable'), (500, 'testing'), (410, 
'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.1.0-rc7+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages wine-development depends on:
ii  wine32-development  1.7.45-1
ii  wine64-development  1.7.45-1

wine-development recommends no packages.

wine-development 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#788809: wine-development: floating point exception rendereing Mitra Mono font

[Michal Suchanek]

Package: wine-development
Version: 1.7.29-1
Severity: normal

Hello,

I was trying to select a font in a WIndows application (wakan - free to
download dictionary application) and when choosing Mitra Mono the
application would lock up. Runnig in winedbg shows a FPE.

This affects wine 1.7.29 and 1.7.45.

000d:0032: create process 'C:\Program Files\Wakan\wakan.exe'/0x110678 @0x56b3dc 
(00)
000d:0032: create thread I @0x56b3dc
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word.
000d:0032: loads DLL C:\windows\system32\KERNEL32.dll @0x7b81 (00)
000d:0032: loads DLL C:\windows\system32\ntdll.dll @0x7bc1 (00)
000d:0032: loads DLL C:\windows\system32\advapi32.dll @0x7eb1 (00)
000d:0032: loads DLL C:\windows\system32\gdi32.dll @0x7eb9 (00)
000d:0032: loads DLL C:\windows\system32\version.dll @0x7eff (00)
000d:0032: loads DLL C:\windows\system32\user32.dll @0x7ecb (00)
000d:0032: loads DLL C:\windows\system32\rpcrt4.dll @0x7e82 (00)
000d:0032: loads DLL C:\windows\system32\ole32.dll @0x7e8b (00)
000d:0032: loads DLL C:\windows\system32\oleaut32.dll @0x7e9e (00)
000d:0032: loads DLL C:\windows\system32\comctl32.dll @0x7e72 (00)
000d:0032: loads DLL C:\windows\system32\shlwapi.dll @0x7e47 (00)
000d:0032: loads DLL C:\windows\system32\shell32.dll @0x7e4f (00)
000d:0032: loads DLL C:\windows\system32\winspool.drv @0x7e35 (00)
000d:0032: loads DLL C:\windows\system32\comdlg32.dll @0x7e39 (00)
000d:0032: loads DLL C:\windows\system32\ws2_32.dll @0x7e2f (00)
000d:0032: loads DLL C:\windows\system32\iphlpapi.dll @0x7e2d (00)
000d:0032: loads DLL C:\windows\system32\wsock32.dll @0x7e33 (00)
000d:0032: loads DLL C:\windows\system32\imm32.dll @0x7e2b (00)
000d:0032: loads DLL C:\windows\system32\winex11.drv @0x7e10 (00)
000d:0032: loads DLL C:\windows\system32\uxtheme.dll @0x7dee (00)
000d:0032: exception code=0x8003
start_process (peb=0x7ffdf000) at process.c:1104
1104process.c: No such file or directory.
trace: 98 = 80
Wine-gdb handle SIGABRT nostop print pass
SignalStop  Print   Pass to program Description
SIGABRT   NoYes Yes Aborted
Wine-gdb c
Continuing.

Program received signal SIGABRT, Aborted.

Program received signal SIGABRT, Aborted.

Program received signal SIGABRT, Aborted.

Program received signal SIGABRT, Aborted.

Program received signal SIGABRT, Aborted.

Program received signal SIGABRT, Aborted.

Program received signal SIGABRT, Aborted.

Program received signal SIGABRT, Aborted.

Program received signal SIGABRT, Aborted.

Program received signal SIGABRT, Aborted.

Program received signal SIGFPE, Arithmetic exception.
0x7ebef995 in freetype_SelectFont (dev=0x188668, hfont=0x9c014c, 
aa_flags=0x33eba0) at freetype.c:5401
5401freetype.c: No such file or directory.
Wine-gdb bt full
#0  0x7ebef995 in freetype_SelectFont (dev=0x188668, hfont=0x9c014c, 
aa_flags=0x33eba0) at freetype.c:5401
ret = 0xb897b8
face = 0x154740
best = optimized out
best_bitmap = optimized out
family = 0x154718
last_resort_family = optimized out
height = 48
width = optimized out
score = optimized out
new_score = optimized out
diff = 48
newdiff = optimized out
bd = optimized out
it = optimized out
can_use_bitmap = 8192
lf = {lfHeight = 48, lfWidth = 0, lfEscapement = 0, lfOrientation = 0, 
lfWeight = 400, lfItalic = 0 '\000', lfUnderline = 0 '\000', 
  lfStrikeOut = 0 '\000', lfCharSet = 1 '\001', lfOutPrecision = 0 
'\000', lfClipPrecision = 0 '\000', lfQuality = 0 '\000', 
  lfPitchAndFamily = 0 '\000', lfFaceName = {77, 105, 115, 97, 107, 
105, 32, 77, 105, 110, 99, 104, 111, 0, 60464, 51, 9091, 64, 9091, 64, 
5176, 88, 14630, 64, 9047, 64, 60500, 51, 9092, 64, 60464, 0}}
csi = {ciCharset = 2097968704, ciACP = 2113449302, fs = {fsUsb = 
{2113538041, 2114658304, 2097968680, 2113449302}, fsCsb = {0, 2113559112}}}
dcmat = {eM11 = 1, eM12 = 0, eM21 = 0, eM22 = 1}
psub = 0x0
dc = 0x1884f0
font_link = optimized out
__FUNCTION__ = freetype_SelectFont
#1  0x7e126d1c in X11DRV_SelectFont (dev=optimized out, hfont=0x9c014c, 
aa_flags=0x33eba0) at init.c:319
No locals.

Bug#788809: wine-development: floating point exception rendereing Misaki font

[Michal Suchanek]

Package: wine-development
Followup-For: Bug #788809

Hello,

Attaching patch.

After some fiddling with debug options the warning is produced:

warn:font:freetype_SelectFont font face LMisaki Mincho file
L/home/hramrach/.wine/dosdevices/c:/windows/Fonts/misakimn.ttf has
zero face height!

Thanks

Michal

-- System Information:
Debian Release: 8.1
  APT prefers stable
  APT policy: (900, 'stable'), (610, 'oldstable'), (500, 'testing'), (410, 
'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.1.0-rc7+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages wine-development depends on:
ii  wine32-development  1.7.44-2fpe1
ii  wine64-development  1.7.44-2fpe1

wine-development recommends no packages.

wine-development suggests no packages.

-- no debconf information
Index: wine-development-1.7.44/dlls/gdi32/freetype.c
===
--- wine-development-1.7.44.orig/dlls/gdi32/freetype.c	2015-05-29 13:56:03.0 +0200
+++ wine-development-1.7.44/dlls/gdi32/freetype.c	2015-06-15 12:39:27.299285988 +0200
@@ -5398,7 +5398,13 @@
 if (height != 0) height = diff;
 height += face-size.height;
 
-scale = (height + face-size.height - 1) / face-size.height;
+scale = 1;
+if (face-size.height)
+scale = (height + face-size.height - 1) / face-size.height;
+else
+WARN(font face %s file %s has zero face height!\n,
+debugstr_w(face-FullName),
+debugstr_w(face-file));
 scaled_height = scale * face-size.height;
 /* Only jump to the next height if the difference = 25% original height */
 if (scale  2  scaled_height - height  face-size.height / 4) scale--;

Bug#788440: linux-image-4.0.0-1-amd64: wacom tablet touch arbitration is backwards

[Michal Suchanek]

Package: src:linux
Version: 4.0.2-1
Severity: normal
Tags: upstream

Hello,

on Wacom Pen  Touch tablet when the touch is in proximity (eg your hand
touches the tablet surface) no pen events are reported until touch is
out of proximity (eg you lift your hand from the tablet surface).

This makes Wacom PT tablets unusable with Linux 4.0.

This is fixed in Linux 4.1

Please update to later kernel or import fixes if this is supposed to be
the next stable kernel.

Thanks

Michal

-- Package-specific info:
** Kernel log: boot messages should be attached


** USB devices:
Bus 008 Device 002: ID 0644:0200 TEAC Corp. All-In-One Multi-Card Reader 
CA200/B/S
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 005: ID 056a:00d1 Wacom Co., Ltd Bamboo Pen  Touch (CTH-460-DE)
Bus 006 Device 004: ID 04b3:301b IBM Corp. SK-8815 Keyboard
Bus 006 Device 003: ID 04b3:301a IBM Corp. 
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle 
(HCI mode)
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 004: ID 0ace:1215 ZyDAS ZD1211B 802.11g
Bus 007 Device 003: ID 0409:0059 NEC Corp. HighSpeed Hub
Bus 007 Device 002: ID 0b95:772b ASIX Electronics Corp. AX88772B
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


-- System Information:
Debian Release: 8.1
  APT prefers stable
  APT policy: (900, 'stable'), (610, 'oldstable'), (500, 'testing'), (410, 
'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.1.0-rc7+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-4.0.0-1-amd64 depends on:
ii  debconf [debconf-2.0]   1.5.56
ii  initramfs-tools [linux-initramfs-tool]  0.120
ii  kmod18-3
ii  linux-base  3.5
ii  module-init-tools   18-3

Versions of packages linux-image-4.0.0-1-amd64 recommends:
ii  firmware-linux-free  3.3
ii  irqbalance   1.0.6-3

Versions of packages linux-image-4.0.0-1-amd64 suggests:
pn  debian-kernel-handbook  none
ii  extlinux3:6.03+dfsg-5
ii  grub-pc 2.02~beta2-22
pn  linux-doc-4.0   none

Versions of packages linux-image-4.0.0-1-amd64 is related to:
ii  firmware-atheros0.43
pn  firmware-bnx2   none
pn  firmware-bnx2x  none
pn  firmware-brcm80211  none
pn  firmware-intelwimax none
pn  firmware-ipw2x00none
pn  firmware-ivtv   none
pn  firmware-iwlwifinone
pn  firmware-libertas   none
pn  firmware-linux  none
ii  firmware-linux-nonfree  0.44
pn  firmware-myricomnone
pn  firmware-netxen none
pn  firmware-qlogic none
ii  firmware-ralink 0.43
ii  firmware-realtek0.43
pn  xen-hypervisor  none

-- debconf information:
  linux-image-4.0.0-1-amd64/postinst/depmod-error-initrd-4.0.0-1-amd64: false
  linux-image-4.0.0-1-amd64/postinst/mips-initrd-4.0.0-1-amd64:
  linux-image-4.0.0-1-amd64/prerm/removing-running-kernel-4.0.0-1-amd64: true


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

Bug#788347: linux-image-4.0.0-1-amd64: rtl8192cu does not work after unplug/replug

[Michal Suchanek]

Package: src:linux
Version: 4.0.2-1
Followup-For: Bug #788347

This is still broken with 4.1.0-rc7 upstream.

https://bugzilla.kernel.org/show_bug.cgi?id=99821

Kernel: Linux 4.1.0-rc7+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-4.0.0-1-amd64 depends on:
ii  debconf [debconf-2.0]   1.5.56
ii  initramfs-tools [linux-initramfs-tool]  0.120
ii  kmod18-3
ii  linux-base  3.5
ii  module-init-tools   18-3

Versions of packages linux-image-4.0.0-1-amd64 recommends:
ii  firmware-linux-free  3.3
ii  irqbalance   1.0.6-3

Versions of packages linux-image-4.0.0-1-amd64 suggests:
pn  debian-kernel-handbook  none
ii  extlinux3:6.03+dfsg-5
ii  grub-pc 2.02~beta2-22
pn  linux-doc-4.0   none

Versions of packages linux-image-4.0.0-1-amd64 is related to:
ii  firmware-atheros0.43
pn  firmware-bnx2   none
pn  firmware-bnx2x  none
pn  firmware-brcm80211  none
pn  firmware-intelwimax none
pn  firmware-ipw2x00none
pn  firmware-ivtv   none
pn  firmware-iwlwifinone
pn  firmware-libertas   none
pn  firmware-linux  none
ii  firmware-linux-nonfree  0.44
pn  firmware-myricomnone
pn  firmware-netxen none
pn  firmware-qlogic none
ii  firmware-ralink 0.43
ii  firmware-realtek0.43
pn  xen-hypervisor  none


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