Bug#1075857: [Debian-on-mobile-maintainers] Bug#1075857: phoc frequently crashes with SIGABRT on PinePhone

[Andrey Skvortsov]

Hi Guido,

On 24-07-07 08:10, Guido Günther wrote:
> Hi,
> 
> On Sun, Jul 07, 2024 at 07:34:43AM +0200, Guido Günther wrote:
> > control: retitle -1 Crashes with squeekboard when launching apps or showing 
> > system modal dialogs
> > 
> > Hi,
> > On Sat, Jul 06, 2024 at 09:31:38PM +0200, Guido Günther wrote:
> > > Hi,
> > > On Sat, Jul 06, 2024 at 07:34:11PM +0300, Andrey Skvortsov wrote:
> > > > Package: phoc
> > > > Version: 0.40.0+ds-1
> > > > Severity: normal
> > > > 
> > > > Dear Maintainer,
> > > > 
> > > >after upgrade to 0.40.0+ds-1 phoc started to crash frequently in
> > > >different cases on original PinePhone. If phoc is downgraded to
> > > >0.39.0+ds-2, then phoc doesn't crash anymore
> > > > 
> > > >phoc crashes constantly when I search for 'keypassx' in phosh and
> > > >try to launch it. Another case it crashed a lot, when I unlocked
> > > >ssh key in phosh, when I've tried to connect to remote machine in
> > > >terminal.
> > > > 
> > > >Here is coredump information for one of the crashes.
> > > 
> > > Can you attach a backtrace with debug symbols please? That way we can
> > > see which assertion is hit.
> > 
> > The issue is only triggered with squeekboard (but the bug is clearly in
> > phoc). I adjusted the bug description. phosh-osk-stub can be used as
> > workaround until a fixed phoc hits testing.
> 
> Feedback if
> 
>   https://gitlab.gnome.org/World/Phosh/phoc/-/merge_requests/574
> 
> fixes this would be welcome. The sources contain packaging so
> 
>   sudo apt install git-extras
>   git clone https://gitlab.gnome.org/World/Phosh/phoc
>   git mr 574
>   DEB_BUILD_PROFILES="nocheck nodoc pkg.phoc.embedwlroots" dpkg-buildpackage 
> -uc -us -rfakeroot  -b
> 
> should give an installable deb.

I confirm, that this MR fixes crashes in this case.

-- 
Best regards,
Andrey Skvortsov

Bug#1075857: [Debian-on-mobile-maintainers] Bug#1075857: phoc frequently crashes with SIGABRT on PinePhone

[Andrey Skvortsov]

Hi Guido,

On 24-07-06 21:31, Guido Günther wrote:
> Hi,
> On Sat, Jul 06, 2024 at 07:34:11PM +0300, Andrey Skvortsov wrote:
> > Package: phoc
> > Version: 0.40.0+ds-1
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> >after upgrade to 0.40.0+ds-1 phoc started to crash frequently in
> >different cases on original PinePhone. If phoc is downgraded to
> >0.39.0+ds-2, then phoc doesn't crash anymore
> > 
> >phoc crashes constantly when I search for 'keypassx' in phosh and
> >try to launch it. Another case it crashed a lot, when I unlocked
> >ssh key in phosh, when I've tried to connect to remote machine in
> >terminal.
> > 
> >Here is coredump information for one of the crashes.
> 
> Can you attach a backtrace with debug symbols please? That way we can
> see which assertion is hit.


   PID: 26297 (phoc)
   UID: 1000 (mobian)
   GID: 1000 (mobian)
Signal: 6 (ABRT)
 Timestamp: Sat 2024-07-06 23:45:46 MSK (1min 7s ago)
  Command Line: /usr/bin/phoc -S -C /etc/phosh/phoc.ini -E $'bash -lc \'exec 
gnome-session --disable-acceleration-check --session=phosh\''
Executable: /usr/bin/phoc
 Control Group: /user.slice/user-1000.slice/session-31.scope
  Unit: session-31.scope
 Slice: user-1000.slice
   Session: 31
 Owner UID: 1000 (mobian)
   Boot ID: 4d72862261b1429383ea94d24ebb3dd1
Machine ID: 72d23d3703de45bbb0c5e12a67e9a407
  Hostname: mobian-dev
   Storage: 
/var/lib/systemd/coredump/core.phoc.1000.4d72862261b1429383ea94d24ebb3dd1.26297.172029874600.zst
 (present)
  Size on Disk: 3.7M
   Message: Process 26297 (phoc) of user 1000 dumped core.

Module libzstd.so.1 from deb libzstd-1.5.6+dfsg-1.arm64
Module libblkid.so.1 from deb util-linux-2.40.1-9.arm64
Module libsystemd.so.0 from deb systemd-256.2-1.arm64
Module libmount.so.1 from deb util-linux-2.40.1-9.arm64
Module libudev.so.1 from deb systemd-256.2-1.arm64
Stack trace of thread 26297:
#0  0xa162e6a8 __pthread_kill_implementation (libc.so.6 
+ 0x7e6a8)
#1  0xa15e4d6c __GI_raise (libc.so.6 + 0x34d6c)
#2  0xa15d0980 __GI_abort (libc.so.6 + 0x20980)
#3  0xa1deeae0 g_assertion_message (libglib-2.0.so.0 + 
0x8eae0)
#4  0xa1deeb44 g_assertion_message_expr 
(libglib-2.0.so.0 + 0x8eb44)
#5  0xea1c9cd4 phoc_layer_surface_get_alpha (phoc + 
0x49cd4)
#6  0xea1a9e14 render_layer (phoc + 0x29e14)
#7  0xea1aadf8 phoc_renderer_render_output (phoc + 
0x2adf8)
#8  0xea1a6bcc phoc_output_draw (phoc + 0x26bcc)
#9  0xa1969564 wl_signal_emit_mutable 
(libwayland-server.so.0 + 0x9564)
#10 0xa1879350 n/a (libwlroots.so.12 + 0x59350)
#11 0xa02df040 drmHandleEvent (libdrm.so.2 + 0xf040)
#12 0xa187aa6c n/a (libwlroots.so.12 + 0x5aa6c)
#13 0xa196b918 wl_event_loop_dispatch 
(libwayland-server.so.0 + 0xb918)
#14 0xea195adc wayland_event_source_dispatch (phoc + 
0x15adc)
#15 0xa1dbe500 n/a (libglib-2.0.so.0 + 0x5e500)
#16 0xa1dc08bc n/a (libglib-2.0.so.0 + 0x608bc)
#17 0xa1dc1354 g_main_loop_run (libglib-2.0.so.0 + 
0x61354)
#18 0xea195338 main (phoc + 0x15338)
#19 0xa15d1044 __libc_start_call_main (libc.so.6 + 
0x21044)
#20 0xa15d1118 __libc_start_main_impl (libc.so.6 + 
0x21118)
#21 0xea195470 _start (phoc + 0x15470)

Stack trace of thread 26329:
#0  0xa1695e64 syscall (libc.so.6 + 0xe5e64)
#1  0xa1e222fc g_cond_wait (libglib-2.0.so.0 + 0xc22fc)
#2  0xa1d851fc n/a (libglib-2.0.so.0 + 0x251fc)
#3  0xa1df11ec n/a (libglib-2.0.so.0 + 0x911ec)
#4  0xa1df0768 n/a (libglib-2.0.so.0 + 0x90768)
#5  0xa162ca9c start_thread (libc.so.6 + 0x7ca9c)
#6  0xa169808c thread_start (libc.so.6 + 0xe808c)

Stack trace of thread 26330:
#0  0xa168d61c __GI___poll (libc.so.6 + 0xdd61c)
#1  0xa1dc07f0 n/a (libglib-2.0.so.0 + 0x607f0)
#2  0xa1dc1068 g_main_context_iteration 
(libglib-2.0.so.0 + 0x61068)
#3  0xa1dc10c4 n/a (libglib-2.0.so.0 + 0x610c4)
#4  0xa1df0768 n/a (libglib-2.0.so.0 + 0x90768)
 

Bug#1075857: phoc frequently crashes with SIGABRT on PinePhone

[Andrey Skvortsov]

Package: phoc
Version: 0.40.0+ds-1
Severity: normal

Dear Maintainer,

   after upgrade to 0.40.0+ds-1 phoc started to crash frequently in
   different cases on original PinePhone. If phoc is downgraded to
   0.39.0+ds-2, then phoc doesn't crash anymore

   phoc crashes constantly when I search for 'keypassx' in phosh and
   try to launch it. Another case it crashed a lot, when I unlocked
   ssh key in phosh, when I've tried to connect to remote machine in
   terminal.

   Here is coredump information for one of the crashes.
  
```
   $ coredumpctl info phoc
   PID: 1534 (phoc)
   UID: 1000 (mobian)
   GID: 1000 (mobian)
Signal: 6 (ABRT)
 Timestamp: Sat 2024-07-06 16:25:14 MSK (3h 1min ago)
  Command Line: /usr/bin/phoc -S -C /etc/phosh/phoc.ini -E $'bash -lc \'exec 
gnome-session --disable-acceleration-check --session=phosh\''
Executable: /usr/bin/phoc
 Control Group: /user.slice/user-1000.slice/session-3.scope
  Unit: session-3.scope
 Slice: user-1000.slice
   Session: 3
 Owner UID: 1000 (mobian)
   Boot ID: 93ec88a428004ed680d5d597d116aea9
Machine ID: 72d23d3703de45bbb0c5e12a67e9a407
  Hostname: mobian-dev
   Storage: 
/var/lib/systemd/coredump/core.phoc.1000.93ec88a428004ed680d5d597d116aea9.1534.172027231400.zst
 (present)
  Size on Disk: 6.3M
   Message: Process 1534 (phoc) of user 1000 dumped core.

Module libzstd.so.1 from deb libzstd-1.5.6+dfsg-1.arm64
Module libblkid.so.1 from deb util-linux-2.40.1-9.arm64
Module libsystemd.so.0 from deb systemd-256.1-2.arm64
Module libmount.so.1 from deb util-linux-2.40.1-9.arm64
Module libudev.so.1 from deb systemd-256.1-2.arm64
Stack trace of thread 1534:
#0  0xb53de6a8 __pthread_kill_implementation (libc.so.6 
+ 0x7e6a8)
#1  0xb5394d6c __GI_raise (libc.so.6 + 0x34d6c)
#2  0xb5380980 __GI_abort (libc.so.6 + 0x20980)
#3  0xb5b9eae0 g_assertion_message (libglib-2.0.so.0 + 
0x8eae0)
#4  0xb5b9eb44 g_assertion_message_expr 
(libglib-2.0.so.0 + 0x8eb44)
#5  0xade19cd4 n/a (phoc + 0x49cd4)
#6  0xaddf9e14 n/a (phoc + 0x29e14)
#7  0xaddfadf8 n/a (phoc + 0x2adf8)
#8  0xaddf6bcc n/a (phoc + 0x26bcc)
#9  0xb5719564 wl_signal_emit_mutable 
(libwayland-server.so.0 + 0x9564)
#10 0xb5629350 n/a (libwlroots.so.12 + 0x59350)
#11 0xb408f040 drmHandleEvent (libdrm.so.2 + 0xf040)
#12 0xb562aa6c n/a (libwlroots.so.12 + 0x5aa6c)
#13 0xb571b918 wl_event_loop_dispatch 
(libwayland-server.so.0 + 0xb918)
#14 0xadde5adc n/a (phoc + 0x15adc)
#15 0xb5b6e500 n/a (libglib-2.0.so.0 + 0x5e500)
#16 0xb5b708bc n/a (libglib-2.0.so.0 + 0x608bc)
#17 0xb5b71354 g_main_loop_run (libglib-2.0.so.0 + 
0x61354)
#18 0xadde5338 n/a (phoc + 0x15338)
#19 0xb5381044 __libc_start_call_main (libc.so.6 + 
0x21044)
#20 0xb5381118 __libc_start_main_impl (libc.so.6 + 
0x21118)
#21 0xadde5470 n/a (phoc + 0x15470)

Stack trace of thread 1573:
#0  0xb543d61c __GI___poll (libc.so.6 + 0xdd61c)
#1  0xb5b707f0 n/a (libglib-2.0.so.0 + 0x607f0)
#2  0xb5b71068 g_main_context_iteration 
(libglib-2.0.so.0 + 0x61068)
#3  0xb5b710c4 n/a (libglib-2.0.so.0 + 0x610c4)
#4  0xb5ba0768 n/a (libglib-2.0.so.0 + 0x90768)
#5  0xb53dca9c start_thread (libc.so.6 + 0x7ca9c)
#6  0xb544808c thread_start (libc.so.6 + 0xe808c)

Stack trace of thread 1575:
#0  0xb543d61c __GI___poll (libc.so.6 + 0xdd61c)
#1  0xb5b707f0 n/a (libglib-2.0.so.0 + 0x607f0)
#2  0xb5b71354 g_main_loop_run (libglib-2.0.so.0 + 
0x61354)
#3  0xb5e60608 n/a (libgio-2.0.so.0 + 0x140608)
#4  0xb5ba0768 n/a (libglib-2.0.so.0 + 0x90768)
#5  0xb53dca9c start_thread (libc.so.6 + 0x7ca9c)
#6  0xb544808c thread_start (libc.so.6 + 0xe808c)

Stack trace of thread 1572:
#0  0xb5445e64 syscall (libc.so.6 + 0xe5e64)
#1  0xb5bd22fc g_cond_wait (libglib-2.0.so.0 + 0xc22fc)
#2  0xb5b351fc n/a (libglib-2.0.so.0 + 0x251fc)
#3  0xb5ba11ec n/a (libglib-2.0.so.0 

Bug#1073926: clapper 0.5.2 built against 1.24 doesn't play videos on PinePhone and Librem 5

[Andrey Skvortsov]

Hi Johannes,

On 24-06-20 13:08, Johannes Schauer Marin Rodrigues wrote:
> Hi Andrey–
> 
> Quoting Andrey Skvortsov (2024-06-20 12:14:39)
> > after gstreamer update from 1.22 to 1.23/1.24 clapper stopped playing videos
> > (h264 at least) on PinePhone (ARM aarch64, allwinner a64). The SoC uses v4l2
> > stateless decoder. Librem5 (iMX8) was checked as well on trixie from
> > 19.06.2024 and clapper is not working there either.
> 
> what is the error on the Librem5? I tested this on the MNT Reform 2 which also
> uses the imx8mq just as the librem 5 does and hardware decoding does work 
> there
> with gstreamer 1.24. We used to ship some gstreamer patches for before the 
> 1.24
> release but those were all integrated now.
>

sorry, it took me some time to get hands to L5 again. Both original
PinePhone and Librem 5 fail to play h264 video with the same error:

```
(com.github.rafostar.Clapper:59855): GStreamer-CRITICAL **: 15:30:29.052: 
gst_caps_get_structure: assertion 'index < GST_CAPS_LEN (caps)' failed

(com.github.rafostar.Clapper:59855): GStreamer-CRITICAL **: 15:30:29.052: 
gst_structure_set: assertion 'structure != NULL' failed

(com.github.rafostar.Clapper:59855): GStreamer-Video-CRITICAL **: 15:30:29.052: 
gst_video_info_from_caps: assertion 'gst_caps_is_fixed (caps)' failed
**
GStreamer-GL:ERROR:../gst-libs/gst/gl/gstglcolorconvert.c:830:_gst_gl_color_convert_set_caps_unlocked:
 code should not be reached
Bail out! 
GStreamer-GL:ERROR:../gst-libs/gst/gl/gstglcolorconvert.c:830:_gst_gl_color_convert_set_caps_unlocked:
 code should not be reached
Aborted (core dumped)
```

the problem appeared in 1.24.1 and wasn't on 1.24.0. 1.24.1 introduced
DMA_DRM caps support for v4l2codecs and clapper gstreamer sink doesn't
support it.

I think in 0.6 it's handled by following commit:
https://github.com/Rafostar/clapper/commit/681da9e2f39fd5180317113e7349272586ae645d

> > If I take old clapper build before gstreamer update to 1.24, then
> > videoplayback in clapper works.
> > 
> > I've tried to backport upstream clapper fix for gstreamer 1.24.
> > https://github.com/Rafostar/clapper/commit/a9769f95378d1cf20d6f6105eb90df7a3fe3f8f0
> > But it wasn't enough to get clapper 0.5.2 working on PinePhone.
> > 
> > clapper 0.6 contains several fixes for gstreamer 1.24 compatibility. 
> > I've tried to build clapper 0.6 against gstreamer 1.24 localy and video
> > playback started to work on PinePhone.
> 
> I take it then that this is mainly about the PinePhone and not the Librem 5?
> 
> > Please consider updating clapper to the next released version 0.6.
> 
> Certainly! It is on my TODO list now. Should I fail to come back to this, feel
> free to ping me until I get the work done.
> 
> Thanks!
> 
> cheers, josch

-- 
Best regards,
Andrey Skvortsov

Bug#1073926: clapper 0.5.2 built against 1.24 doesn't play videos on PinePhone and Librem 5

[Andrey Skvortsov]

Package: clapper
Version: 0.5.2-8+b1
Severity: important

Dear Maintainer,

after gstreamer update from 1.22 to 1.23/1.24 clapper stopped playing
videos (h264 at least) on PinePhone (ARM aarch64, allwinner a64). The SoC uses 
v4l2
stateless decoder. Librem5 (iMX8) was checked as well on trixie from
19.06.2024 and clapper is not working there either.

If I take old clapper build before gstreamer update to 1.24, then
videoplayback in clapper works.

I've tried to backport upstream clapper fix for gstreamer 1.24.
https://github.com/Rafostar/clapper/commit/a9769f95378d1cf20d6f6105eb90df7a3fe3f8f0
But it wasn't enough to get clapper 0.5.2 working on PinePhone.

clapper 0.6 contains several fixes for gstreamer 1.24 compatibility. 
I've tried to build clapper 0.6 against gstreamer 1.24 localy and video
playback started to work on PinePhone.

Please consider updating clapper to the next released version 0.6.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 6.6.33-sunxi64-mmc-pm (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages clapper depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4+b2
ii  gir1.2-adw-1 1.5.1-1
ii  gir1.2-gst-plugins-base-1.0  1.24.4-1
ii  gir1.2-gstreamer-1.0 1.24.4-1
ii  gir1.2-gtk-4.0   4.12.5+ds-6+b1
ii  gir1.2-soup-3.0  3.4.4-5+b1
ii  gjs  1.80.2-1
ii  gstreamer1.0-plugins-good1.24.4-1
ii  libc62.38-13
ii  libgles2 1.7.0-1+b1
ii  libglib2.0-0t64  2.80.2-2
ii  libgstreamer-gl1.0-0 1.24.4-1
ii  libgstreamer-plugins-base1.0-0   1.24.4-1
ii  libgstreamer1.0-01.24.4-1
ii  libgtk-4-1   4.12.5+ds-6+b1

Versions of packages clapper recommends:
ii  gstreamer1.0-libav1.24.4-1
ii  gstreamer1.0-plugins-bad  1.24.4-2

clapper suggests no packages.

-- no debconf information

Bug#1057494: wpasupplicant: AP doesn't show that it's MFP-capable for WPA2+WPA3 mixed security setup by NM

[Andrey Skvortsov]

Package: wpasupplicant
Version: 2:2.10-15
Severity: normal
Tags: patch upstream

Dear Maintainer,

I'm using Freedombox as main router and wireless access point.
Freedombox uses NetworkManager to setup wireless AP. NetworkManager
sets mixed-security WPA2+WPA3 SAE.

```
WLAN.nmconnection

...
[wifi-security]
key-mgmt=wpa-psk
pairwise=ccmp
group=ccmp
wps-method=1
pmf=2
proto=rsn
...

```


In this case MFP (management frame protection) is optional and NetworkManager 
sets it by default
using pmf in wpa_supplicant, but it doesn't set ieee80211w to the
corresponding value for particular network and default value is set.

As a result AP is up, but it doesn't broadcast that MFP is supported
(MFP-capable in capabilities field). Some wireless clients (probably Broadcom 
based) don't report
such network in scan results at all in this case, probably considering this 
network as broken (WPA3
SAE reported, but AP isn't MFP-capable).

This problem is fixed upstream already by commit "Override ieee80211w
from pmf for AP mode in wpa_supplicant" 
(5f3cdc06489ff1ec16d75c3ff41f5ac7c2f62c7c) [1]

I've built Debian package with that patch and it solves the problem.


1. 
https://www.w1.fi/cgit/hostap/commit/?id=5f3cdc06489ff1ec16d75c3ff41f5ac7c2f62c7c


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


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

Kernel: Linux 6.5.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wpasupplicant depends on:
ii  adduser3.137
ii  libc6  2.37-12
ii  libdbus-1-31.14.10-3
ii  libnl-3-2003.7.0-0.2+b1
ii  libnl-genl-3-200   3.7.0-0.2+b1
ii  libnl-route-3-200  3.7.0-0.2+b1
ii  libpcsclite1   2.0.0-1
ii  libreadline8   8.2-3
ii  libssl33.0.11-1

wpasupplicant recommends no packages.

Versions of packages wpasupplicant suggests:
pn  libengine-pkcs11-openssl  
ii  wpagui2:2.10-15

-- no debconf information

Bug#1029731: libglapi-mesa: Apps fail with 'DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory' after upgrade from 22.3.2-1 to 22.3.3-1

[Andrey Skvortsov]

Dear Maintainer,

Since 22.3.4 is out, I've built 22.3.4 myself and checked currently
available 22.3.4-1 packages from sid. The problem exists in 22.3.4 as well.

Here is link to created upstream issue.
https://gitlab.freedesktop.org/mesa/mesa/-/issues/8198

The problem is caused by commit included in 22.3.3:

```
commit 2adab724e59c662a046cb1da8bfb3177330e01da
Author: Asahi Lina 
Date:   Wed Dec 21 00:37:31 2022 +0900

kmsro: Fix renderonly_scanout BO aliasing

BOs can only have one handle. If renderonly_create_gpu_import_for_resource
ends up importing a BO that was already mapped for scanout, it will get
the same handle. This leaves us with two renderonly_scanout objects for
one handle, and the first one to be destroyed will free it.

Import the BO map tracking logic from asahi, to avoid aliasing
renderonly_scanout objects. Each actual BO now is only represented by a
single object instance, which is reference counted.

Fixes KWin full-screen PipeWire capture breaking scanout entirely.

```

I reverted it and that solved this problem.

On 23-01-27 00:05, Andrey Skvortsov wrote:
> Package: libglapi-mesa
> Version: 22.3.3-1
> Severity: important
> 
> Dear Maintainer,
> 
> 
> after upgrade from 22.3.2-1 to 22.3.3-1 applications starts to crash
> with following error
> 
> ```
> янв 26 23:41:00 mobian-dev dbus-daemon[1018]: [session uid=1000 pid=1018] 
> Activating service name='org.gnome.Console' requested by ':1.34' (uid=1000 
> pid=1250 comm="/usr/libexec/phosh")
> янв 26 23:41:01 mobian-dev dbus-daemon[1018]: [session uid=1000 pid=1018] 
> Successfully activated service 'org.gnome.Console'
> янв 26 23:41:04 mobian-dev org.gnome.Console[6004]: 
> DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory
> янв 26 23:41:04 mobian-dev org.gnome.Console[6004]: 
> DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory
> ```
> 
> The system is aarch64 (arm64) Original PinePhone running Phosh. To
> trigger this problem I start and close different applications (mostly
> gtk3 and gtk4) after some time (~3-5 minutes) no application can start.
> 
> Downgrade to 22.3.2-1 fixes this problem.
> 
> ```
> wget 
> https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/mesa-vdpau-drivers_22.3.2-1_arm64.deb
> wget 
> https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/libegl-mesa0_22.3.2-1_arm64.deb
> wget 
> https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/mesa-va-drivers_22.3.2-1_arm64.deb
> wget 
> https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/libglx-mesa0_22.3.2-1_arm64.deb
> wget 
> https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/libglapi-mesa_22.3.2-1_arm64.deb
> wget 
> https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/libgl1-mesa-dri_22.3.2-1_arm64.deb
> wget 
> https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/libgbm1_22.3.2-1_arm64.deb
> ```
> 
> 
> -- Package-specific info:
> glxinfo:
> 
> DISPLAY is not set.
> 
> /usr/share/bug/xserver-xorg-core/script not available
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers testing-debug
>   APT policy: (500, 'testing-debug'), (500, 'testing')
> Architecture: arm64 (aarch64)
> Foreign Architectures: armhf
> 
> Kernel: Linux 6.1-sunxi64 (SMP w/4 CPU threads)
> Kernel taint flags: TAINT_WARN, TAINT_CRAP, TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages libglapi-mesa depends on:
> ii  libc6  2.36-8
> 
> libglapi-mesa recommends no packages.
> 
> libglapi-mesa suggests no packages.
> 
> -- no debconf information

-- 
Best regards,
Andrey Skvortsov

Bug#1029731: libglapi-mesa: Apps fail with 'DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory' after upgrade from 22.3.2-1 to 22.3.3-1

[Andrey Skvortsov]

Package: libglapi-mesa
Version: 22.3.3-1
Severity: important

Dear Maintainer,


after upgrade from 22.3.2-1 to 22.3.3-1 applications starts to crash
with following error

```
янв 26 23:41:00 mobian-dev dbus-daemon[1018]: [session uid=1000 pid=1018] 
Activating service name='org.gnome.Console' requested by ':1.34' (uid=1000 
pid=1250 comm="/usr/libexec/phosh")
янв 26 23:41:01 mobian-dev dbus-daemon[1018]: [session uid=1000 pid=1018] 
Successfully activated service 'org.gnome.Console'
янв 26 23:41:04 mobian-dev org.gnome.Console[6004]: DRM_IOCTL_MODE_CREATE_DUMB 
failed: Cannot allocate memory
янв 26 23:41:04 mobian-dev org.gnome.Console[6004]: DRM_IOCTL_MODE_CREATE_DUMB 
failed: Cannot allocate memory
```

The system is aarch64 (arm64) Original PinePhone running Phosh. To
trigger this problem I start and close different applications (mostly
gtk3 and gtk4) after some time (~3-5 minutes) no application can start.

Downgrade to 22.3.2-1 fixes this problem.

```
wget 
https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/mesa-vdpau-drivers_22.3.2-1_arm64.deb
wget 
https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/libegl-mesa0_22.3.2-1_arm64.deb
wget 
https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/mesa-va-drivers_22.3.2-1_arm64.deb
wget 
https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/libglx-mesa0_22.3.2-1_arm64.deb
wget 
https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/libglapi-mesa_22.3.2-1_arm64.deb
wget 
https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/libgl1-mesa-dri_22.3.2-1_arm64.deb
wget 
https://snapshot.debian.org/archive/debian/20230104T030543Z/pool/main/m/mesa/libgbm1_22.3.2-1_arm64.deb
```


-- Package-specific info:
glxinfo:

DISPLAY is not set.

/usr/share/bug/xserver-xorg-core/script not available

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 6.1-sunxi64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_CRAP, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libglapi-mesa depends on:
ii  libc6  2.36-8

libglapi-mesa recommends no packages.

libglapi-mesa suggests no packages.

-- no debconf information

Bug#1026998: mmsd-tng shouldn't run for _greetd user

[Andrey Skvortsov]

Package: mmsd-tng
Version: 2.0.0-1
Severity: normal

Dear Maintainer,

on latest Mobian build on OG PP with phog/greetd enabled mmsdtng crashes, when 
it starts under
_greetd user.

```
mobian@mobian:~$ journalctl -b | grep mmsd
Dec 25 23:51:35 mobian mmsdtng[712]: MMSD-TNG version 2.0.0
Dec 25 23:51:35 mobian mmsdtng[712]: Using cross-namespace EXTERNAL 
authentication (this will deadlock if server is GDBus < 2.73.3)
Dec 25 23:51:35 mobian mmsdtng[712]: ../src/main.c:on_bus_acquired() Dbus Bus 
acquired!
Dec 25 23:51:35 mobian mmsdtng[712]: ../src/service.c:__mms_service_init() 
Starting Up MMSD Service Manager
Dec 25 23:51:35 mobian mmsdtng[712]: ../src/plugin.c:__mms_plugin_init() 
Dec 25 23:51:35 mobian mmsdtng[712]: 
../plugins/modemmanager.c:modemmanager_init() Starting Modem Manager Plugin!
Dec 25 23:51:35 mobian mmsdtng[712]: ../src/service.c:mms_service_create() 
service 0x55b4ed0280
Dec 25 23:51:35 mobian mmsdtng[712]: 
../src/service.c:mms_service_set_identity() service 0x55b4ed0280 identity 
modemmanager
Dec 25 23:51:35 mobian mmsdtng[712]: Failed to create path 
/etc/greetd/.mms/modemmanager/mms
Dec 25 23:51:35 mobian mmsdtng[712]: g_key_file_get_string: assertion 'key_file 
!= NULL' failed
Dec 25 23:51:35 mobian mmsdtng[712]: g_key_file_get_string: assertion 'key_file 
!= NULL' failed
Dec 25 23:51:35 mobian mmsdtng[712]: g_key_file_get_string: assertion 'key_file 
!= NULL' failed
Dec 25 23:51:35 mobian systemd-coredump[732]: Removed old coredump 
core.mmsdtng.119.46cdb79a83e646dda6153a968ac63680.1390.167200103900.zst.
Dec 25 23:51:37 mobian systemd-coredump[732]: Process 712 (mmsdtng) of user 119 
dumped core.
  #0  0x005578ac85ec n/a 
(mmsdtng + 0x185ec)
  #1  0x005578ac68bc n/a 
(mmsdtng + 0x168bc)
  #2  0x005578ac6988 
__mms_plugin_init (mmsdtng + 0x16988)
  #12 0x005578ab99cc main 
(mmsdtng + 0x99cc)
  #15 0x005578ab9b70 _start 
(mmsdtng + 0x9b70)
Dec 25 23:51:37 mobian systemd[659]: mmsd-tng.service: Main process exited, 
code=dumped, status=11/SEGV
Dec 25 23:51:37 mobian systemd[659]: mmsd-tng.service: Failed with result 
'core-dump'.

```

And /etc/greetd is read-only home directory for _greetd user.
```
mobian@mobian:~$ ls -l /etc/ | grep greetd
drwxr-xr-x 2 root root4096 Dec 25 23:29 greetd
```
IMHO, mmsd-tng shouldn't run in greetd session.
Link to upstream discussuion: https://gitlab.com/kop316/mmsd/-/issues/86

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 5.15.44-sunxi64-page-debug (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mmsd-tng depends on:
ii  init-system-helpers   1.65.2
ii  libc-ares21.18.1-1+b2
ii  libc6 2.36-6
ii  libgcc-s1 12.2.0-10
ii  libglib2.0-0  2.74.2-1
ii  libmm-glib0   1.20.0-1
ii  libphonenumber8 [libphonenumber8-protobuf32]  8.12.57+ds-3
ii  libsoup-3.0-0 3.2.2-1
ii  libstdc++612.2.0-10

Versions of packages mmsd-tng recommends:
ii  modemmanager  1.20.0-1

mmsd-tng suggests no packages.

-- no debconf information

Bug#1022024: python-gitlab FTBFS: test failures

[Andrey Skvortsov]

Hi,

here is MR to fix this issue:
https://salsa.debian.org/debian/python-pygitlab/-/merge_requests/2

and corresponding MR is already merged upstream:
https://github.com/python-gitlab/python-gitlab/pull/2322

This change is included in the next version 3.11. Please consider
upgrading to the next upstream version or at least backporting this change.

-- 
Best regards,
Andrey Skvortsov

Bug#1009104: GTK4 support

[Andrey Skvortsov]

Dear Maintainer,

with GNOME 42 it's not possible to edit/add new VPN connection anymore.
'Error: unable to load VPN connection editor'

This is because GNOME Control Center was moved to GTK 4. Upstream have
added GTK 4 support with 1.4.0. Please consider updating the package,
otherwise network-manager-fortisslvpn-gnome is not much usable in
Debian anymore.

-- 
Best regards,
Andrey Skvortsov

Bug#1003141: Patch to polkit policy breaks automatic/unattended updates

[Andrey Skvortsov]

Hi,

I'm using Mobian (PinePhone) with Debian bookworm arm64 repositories and see 
similar
issue using gnome-software in Phosh.

There are listed updates, but if I click on 'Reboot and update', then
error message is shown 'Unable to install updates: Prepared update not
found: /var/lib/PackageKit/prepared-update'.

Change to
/usr/share/polkit-1/actions/org.freedesktop.packagekit.policy
mentioned by Elias fixed updates. 

This is regression happened with update to packagekit 1.2.4-1. There
was no such problem with packagekit 1.2.2-2.

-- 
Best regards,
Andrey Skvortsov

Bug#973528: telegram-desktop: Assertion Failed! "lines == to.height()" lottie_cache.cpp:150

[Andrey Skvortsov]

The issue is fixed upstream. It doesn't happen on 2.4.7 on arm64 anymore.
Licensing problem for tgcalls library seems to be fixed as well [1]

1.
https://github.com/TelegramMessenger/tgcalls/commit/e884535f1854aa57616b162a4901bd60c8287575

Bug#970291: golang-github-avast-apkverifier-dev misses description in Translation-en.bz2 for Sid

[Andrey Skvortsov]

Package seems to have description defined package source code [1]
and in control file inside a package [3].

[--- control --]
Package: golang-github-avast-apkverifier-dev
Source: golang-github-avast-apkverifier
Version: 0.0~git20191015.7330a51-1
Architecture: all
Maintainer: Debian Go Packaging Team 
Installed-Size: 868
Section: devel
Priority: optional
Homepage: https://github.com/avast/apkverifier
Description: Android APK Signature verification Go library
 apkverifier verifies the signatures on Android APK binaries.  It can
 verify APK Signature scheme v1, v2 and v3 and passes Google apksig's
 testing suite.  It should support all algorithms and downgrade attack
 protection.
 .
 Because Android can handle even broken x509 cerficates and ZIP files,
 apkverifier is using the ZipReader from apkparser package and vendors
 crypto/x509 in internal/x509andr and github.com/fullsailor/pkcs7
 (https://github.com/fullsailor/pkcs7) in the fullsailor/pkcs7 folder.
 The last two have some changes to handle some
 not-entirely-according-to-spec certificates.
 .
 Documentation on GoDoc (https://godoc.org/github.com/avast/apkverifier)
[--]

But for some reason it's missing in Translation-en.bz2 file [2].


[1]
https://salsa.debian.org/go-team/packages/golang-github-avast-apkverifier/-/blob/debian/sid/debian/control#L22
[2] http://ftp.debian.org/debian/dists/sid/main/i18n/Translation-en.bz2
[3]
http://ftp.de.debian.org/debian/pool/main/g/golang-github-avast-apkverifier/golang-github-avast-apkverifier-dev_0.0~git20191015.7330a51-1_all.deb

Bug#973506: packagekit: offline system update don't work after upgrading from 1.1.13-2+b1 to 1.2.1-1

[Andrey Skvortsov]

Package: packagekit
Version: 1.2.1-1
Severity: important

Dear Maintainer,


after updating packagekit from 1.1.13-2+b1 to 1.2.1-1 updates are not
installed anymore. 
If new packages are available software center shows that there are some
update. User can press download, packages will be downloaded and after
that it press "reboot and install". Devices reboots into systemd target
system-update.target, but nothing is installed. Afterwards it reboots
back into user session.
Because nothing was installed, then software center shows again that the
same updates are still available.

I've checked 1.2.1-1 package content and the problem is that symlink for
packagekit-offline-update.service in 
/lib/systemd/system/system-update.target.wants is missing.

After following command
cd /lib/systemd/system/system-update.target.wants; ln -s 
../packagekit-offline-update.service packagekit-offline-update.service
offline system updates work again.


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 5.8-sunxi64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages packagekit depends on:
ii  init-system-helpers 1.58
ii  libappstream4   0.12.11-1
ii  libapt-pkg6.0   2.1.11
ii  libc6   2.31-4
ii  libgcc-s1   10.2.0-15
ii  libglib2.0-02.66.1-2
ii  libglib2.0-bin  2.66.1-2
ii  libgstreamer1.0-0   1.18.0-3
ii  libpackagekit-glib2-18  1.2.1-1
ii  libpolkit-gobject-1-0   0.105-29
ii  libsqlite3-03.33.0-1
ii  libstdc++6  10.2.0-15
ii  libsystemd0 246.6-2
ii  policykit-1 0.105-29

Versions of packages packagekit recommends:
pn  packagekit-tools  
ii  systemd   246.6-2

Versions of packages packagekit suggests:
ii  appstream  0.12.11-1

-- no debconf information

Bug#955037: abootimg: unpack initrd to '/' instead of 'ramdisk'

[Andrey Skvortsov]

Package: abootimg
Version: 0.6-1+b2
Severity: normal
Tags: patch

Dear Maintainer,

If cpio archive contains absolute filenames, files are unpacked
relative to host root '/', not 'ramdisk' directory.
If abootimg-unpack-initrd is run as root, that could break host system
and make it unbootable by overwriting important system files.

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

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

Versions of packages abootimg depends on:
ii  libblkid1  2.34-0.1
ii  libc6  2.30-4

abootimg recommends no packages.

abootimg suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/bin/abootimg-unpack-initrd (from abootimg package)
>From 3e581732879f8bc3975ac0da99beba3785f6ab98 Mon Sep 17 00:00:00 2001
From: Andrey Skvortsov 
Date: Fri, 27 Mar 2020 11:40:21 +0300
Subject: [PATCH] always unpack initrd to relative paths

If cpio archive contains absolute filenames, files are unpacked
relative to host root '/', not 'ramdisk' directory.
If abootimg-unpack-initrd is run as root, that could break host system
and make it unbootable by overwriting important system files.

Signed-off-by: Andrey Skvortsov 
---
 abootimg-unpack-initrd | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/abootimg-unpack-initrd b/abootimg-unpack-initrd
index 987239c..0113f3a 100755
--- a/abootimg-unpack-initrd
+++ b/abootimg-unpack-initrd
@@ -16,5 +16,5 @@ fi
 
 mkdir -p $ramdisk
 
-zcat $initrd | ( cd $ramdisk; cpio -i )
+zcat $initrd | ( cd $ramdisk; cpio -i --no-absolute-filenames)
 
-- 
2.26.0

Bug#906223: Allow adding exception for self signed certificates

[Andrey Skvortsov]

Hi,

this is already fixed.
there is option to enter hash of trusted certificate in the
network manager UI. See Identity->Advanced->Security->Trusted
certificate.

-- 
Best regards,
Andrey Skvortsov


signature.asc
Description: PGP signature

Bug#893574: Auto-suspend

[Andrey Skvortsov]

My use-case is slightly different, but very annoying.

1) user1 logged in GNOME session for a while. 
2) user2 wants to use its account.
3) user1 locks its session.
4) user2 selects 'switch user' and then ...
system is surprisingly suspended after switching to greeter. User2 has
to wakeup system to login.


I've made suggested changes to /etc/gdm3/greeter.dconf-defaults as a
workaround for this behavior:

[org/gnome/settings-daemon/plugins/power]
sleep-inactive-ac-timeout=0
sleep-inactive-battery-timeout=0

I understand that most likely defaults will not be changed, because
they were modify to comply with European and American power-saving
regulations.
Changes in /etc/gdm3/greeter.dconf-defaults have solved my problem,
but other users probably have the same problem.

The problem seems that activity in other seats doesn't reset
inactivity timer in greeter session. As soon as greeter session is
active again (switch user/logout) inactivity timer triggers automatic
system suspend. It would be nice if inactivity timer would be reset on
session switching.

-- 
Best regards,
Andrey Skvortsov


signature.asc
Description: PGP signature

Bug#923307: partial fix for upload functionality

[Andrey Skvortsov]

Hi,

after my freedombox upgraded from stretch to buster, I've noticed that
I can't use coquelicot to share files any more.

Here is patch, that at least makes coquelicot usable on buster.

It's available on salsa as well, if it's more convenient to take.
https://salsa.debian.org/skv-guest/coquelicot

Tags: patch

-- 
Best regards,
Andrey Skvortsov
From b2a2081137b8bae17f9c86554af132e85dec569f Mon Sep 17 00:00:00 2001
From: Andrey Skvortsov 
Date: Mon, 22 Jul 2019 22:48:19 +0300
Subject: [PATCH] fix upload functionality with rack 2.x

because of changes in rack 2.x upload functionality in coquelicot was broken.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923307

First by default rack requires rewindable input stream.
Coquelicot tried to avoid rewindable streams for performance and
security reasons. See HACKING for more details.
This change enables usage of rewindable streams to make rack
happy again.

Because of changes in rack API following build error was fixed as well:

Coquelicot::Rack::Upload#call when called for POST /upload when no file has been submitted should set X_COQUELICOT_FORWARD in env
Failure/Error: @params = Rack::Utils::KeySpaceConstrainedParams.new

ArgumentError:
 wrong number of arguments (given 0, expected 1)
 # ./lib/coquelicot/rack/multipart_parser.rb:26:in `new'
 # ./lib/coquelicot/rack/multipart_parser.rb:26:in `initialize'
 ...
 # ./spec/coquelicot/rack/upload_spec.rb:291:in `block (5 levels) in '
 # ./spec/spec_helper.rb:49:in `block (2 levels) in '

Signed-off-by: Andrey Skvortsov 
---
 lib/coquelicot/app.rb   | 2 +-
 lib/coquelicot/rack/multipart_parser.rb | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/lib/coquelicot/app.rb b/lib/coquelicot/app.rb
index c9c7ed3..7a12b40 100644
--- a/lib/coquelicot/app.rb
+++ b/lib/coquelicot/app.rb
@@ -143,7 +143,7 @@ module Coquelicot
 :pid => settings.pid,
 :listeners => settings.listen,
 :use => :ThreadSpawn,
-:rewindable_input => false,
+:rewindable_input => true,
 :client_max_body_size => nil
   })
   unless options[:no_daemon]
diff --git a/lib/coquelicot/rack/multipart_parser.rb b/lib/coquelicot/rack/multipart_parser.rb
index a4be335..2d99624 100644
--- a/lib/coquelicot/rack/multipart_parser.rb
+++ b/lib/coquelicot/rack/multipart_parser.rb
@@ -23,7 +23,7 @@ module Coquelicot::Rack
   class ManyFieldsStep < Struct.new(:block)
 def initialize(block)
   super
-  @params = Rack::Utils::KeySpaceConstrainedParams.new
+  @params = Rack::Utils::KeySpaceConstrainedParams.new(65536)
 end
 
 def call_handler
@@ -31,7 +31,7 @@ module Coquelicot::Rack
 end
 
 def add_param(name, data)
-  Rack::Utils.normalize_params(@params, name, data)
+  Rack::Utils.default_query_parser.normalize_params(@params, name, data, 100)
 end
 
 # borrowed from Sinatra::Base
-- 
2.11.0

Bug#923768: python-matplotlib: UnicodeDecodeError on importing pyplot in python2

[Andrey Skvortsov]

Package: python-matplotlib
Version: 2.2.3-6
Severity: normal
Tags: upstream, fixed-upstream

Dear Maintainer,

UnicodeDecodeError on importing pyplot If some module in call stack is
located in directory with non-ascii character in path. The problem is
that traceback.format_stack() returns list of 'str' objects in
python2. This problem happens only on python2.

Code for reproduction
Create two modules in a directory with a non-ascii character in the path.

#!/usr/bin/env python
# first_module.py
import second_module

# second_module.py
import matplotlib.pyplot

Run first module.

$ python2 first_module.py


Following traceback happens

Traceback (most recent call last):
  File "./a.py", line 3, in 
import second_module
  File "/home/developer/WorkData/PLC/beremiz/tmp/xыв/beremiz/second_module.py", 
line 3, in 
import matplotlib.pyplot
  File "/usr/lib/python2.7/dist-packages/matplotlib/pyplot.py", line 71, in 

from matplotlib.backends import pylab_setup
  File "/usr/lib/python2.7/dist-packages/matplotlib/backends/__init__.py", line 
16, in 
line for line in traceback.format_stack()
  File "/usr/lib/python2.7/dist-packages/matplotlib/backends/__init__.py", line 
18, in 
if not line.startswith('  File "https://github.com/matplotlib/matplotlib/issues/11955

and it was fixed and release as part of 2.2.4 release
https://github.com/matplotlib/matplotlib/commit/69b4233a7d8ef0750f83aa63ff20b939e996cc4f

It makes python programs installed in user's directories with non-ascii symbols 
in path unusable.
Would be nice to get this minor change backported to be included in Buster.


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

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

Versions of packages python-matplotlib depends on:
ii  libc6 2.28-7
ii  libfreetype6  2.9.1-3
ii  libgcc1   1:8.2.0-21
ii  libjs-jquery  3.3.1~dfsg-1
ii  libjs-jquery-ui   1.12.1+dfsg-5
ii  libpng16-16   1.6.36-5
ii  libstdc++68.2.0-21
ii  python2.7.15-4
ii  python-backports.functools-lru-cache  1.5-2
ii  python-cycler 0.10.0-1
ii  python-dateutil   2.7.3-3
ii  python-kiwisolver 1.0.1-2+b1
ii  python-matplotlib2-data   2.2.3-6
ii  python-numpy [python-numpy-abi9]  1:1.16.1-1
ii  python-pyparsing  2.2.0+dfsg1-2
ii  python-six1.12.0-1
ii  python-subprocess32   3.5.3-1
ii  python-tz 2018.9-1
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages python-matplotlib recommends:
ii  python-pil  5.4.1-1
ii  python-tk   2.7.15-1+b1

Versions of packages python-matplotlib suggests:
pn  dvipng  
ii  ffmpeg  7:4.1.1-1
ii  ghostscript 9.26a~dfsg-2
ii  gir1.2-gtk-3.0  3.24.5-1
ii  inkscape0.92.4-2
pn  ipython 
ii  librsvg2-common 2.44.10-1
pn  python-cairocffi
pn  python-configobj
pn  python-excelerator  
ii  python-gi   3.30.4-1
ii  python-gobject-22.28.6-13+b1
pn  python-matplotlib2-doc  
ii  python-nose 1.3.7-4
ii  python-qt4  4.12.1+dfsg-2+b1
pn  python-scipy
ii  python-sip  4.19.13+dfsg-2
pn  python-tornado  
pn  python-traits   
ii  python-wxgtk3.0 3.0.2.0+dfsg-8
pn  texlive-extra-utils 
ii  texlive-latex-extra 2018.20190131-1
pn  ttf-staypuft

-- no debconf information

Bug#905036: libvirt0: qemu sandbox option prevents built-in qemu smb server from working

[Andrey Skvortsov]

Package: libvirt0
Version: 4.5.0-1
Severity: normal

Dear Maintainer,

some virtual machines uses built-in qemu samba to share directory with host.
This is done using 'qemu:commandline' tag in VM xml file.









After upgrading from 4.2.0-2 to 4.3.0-1 this does not work anymore. The reason
is that since 4.3.0-1
following command line options are added to qemu command line:
'-sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny'

elevateprivileges=deny causes corresponding qemu thread to be killed as soon as
samba share is accessed.

I don't think this is a major problem and it should be fixed. Sandbox is a good
thing.
This bug report just points that upgrading (for example, from stretch to
buster)
could cause problems in some cases.



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

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

Versions of packages libvirt0 depends on:
ii  libacl1 2.2.52-3+b1
ii  libapparmor12.12-5
ii  libaudit1   1:2.8.3-1+b1
ii  libavahi-client30.7-4
ii  libavahi-common30.7-4
ii  libc6   2.27-5
ii  libcap-ng0  0.7.9-1
ii  libcurl3-gnutls 7.60.0-2
ii  libdbus-1-3 1.12.8-3
ii  libdevmapper1.02.1  2:1.02.145-4.1
ii  libgnutls30 3.5.19-1
ii  libnl-3-200 3.4.0-1
ii  libnl-route-3-200   3.4.0-1
ii  libnuma12.0.11-2.2
ii  libsasl2-2  2.1.27~101-g0780600+dfsg-3.1
ii  libselinux1 2.8-1+b1
ii  libssh2-1   1.8.0-1
ii  libxml2 2.9.4+dfsg1-7+b1
ii  libyajl22.1.0-2+b3

Versions of packages libvirt0 recommends:
ii  lvm2  2.02.176-4.1

libvirt0 suggests no packages.

-- no debconf information

Bug#899376: gnome-terminal: Ctrl-Shift-Enter/Ctrl-Enter in MC isn't working on Wayland

[Andrey Skvortsov]

Package: gnome-terminal
Version: 3.28.0-1
Severity: normal

Dear Maintainer,

if gnome-terminal is running in GNOME running on Wayland,
then it's impossible to use Ctrl-Shift-Enter and Ctrl-Enter hotkeys in Midnight
Commander (MC).
Instead of coping full path or directory (or file) name into command line,
mc enters selected directory like if only 'Enter' key was pressed.
These hotkeys are working in gnome-terminal running on Xorg. They are also in
mc started in xterm running on Wayland.
Therefore I expect this problem is specific to gnome-terminal.

To reproduce the problem start mc in gnome-terminal.
Select any directory in mc panel using arrow keys and press Ctrl-Shift-Enter or
Ctrl-Enter.
Correspondingly full path or directory name should be copied into command line.



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

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

Versions of packages gnome-terminal depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.8-2
ii  dbus-x11 [dbus-session-bus]   1.12.8-2
ii  dconf-gsettings-backend [gsettings-backend]   0.28.0-2
ii  gnome-terminal-data   3.28.0-1
ii  gsettings-desktop-schemas 3.28.0-1
ii  libatk1.0-0   2.28.1-1
ii  libc6 2.27-3
ii  libdconf1 0.28.0-2
ii  libglib2.0-0  2.56.1-2
ii  libgtk-3-03.22.29-3
ii  libpango-1.0-01.42.0-1
ii  libuuid1  2.32-0.1
ii  libvte-2.91-0 0.52.0-1
ii  libx11-6  2:1.6.5-1

Versions of packages gnome-terminal recommends:
ii  gvfs   1.36.1-1
ii  nautilus-extension-gnome-terminal  3.28.0-1
ii  yelp   3.28.1-1

gnome-terminal suggests no packages.

-- no debconf information

Bug#739363: miredo and .service

[Andrey Skvortsov]

>On 25/02/16 12:41:34, Tomasz Buchert wrote:
>> Hello,
>>
>> On Tue, Feb 16, 2016 at 03:54:19PM +0300, Andrey Skvortsov wrote:
>> > your solution is not complete. At least in my case it's not
>> enough.
>> > There are a bit more requirements:
>> >
>> > 1. Add in miredo.service
>> > After=network-online.target
>> > Wants=network-online.target
>>
>> There is one more thing missing: dependency on nss-lookup.target. As
>> the
>> name teredo-debian.remlab.net needs to be resolvable, the local DNS
>> recursive resolver must be running as well (in case it is used, I'm
>> using dnssec-trigger for that).
>>
>> > 2. By default network-online.target is not waiting really for the
>> > network to come up. Depend on your configuration you need to pull
>> > into
>> > network-online.target other services:
>> > NetworkManager-wait-online.service or
>> > systemd-networkd-wait-online.servce. By default both services are
>> > disabled and don't slow down boot process.
>> >
>> > I use NetworkManager, therefore I enabled
>> > NetworkManager-wait-online.service and only then miredo started
>> > after the
>> > network was really online.
>>
>> I can confirm that Miredo starts in my case after adding
>> dependencies on
>> network-online.target and nss-lookup.target (and enabling
>> NetworkManager-wait-online.service).
>>
>>
>> --
>> pozdr(); // Jarek
>>
>
>Hi Jarek,
>
> I'm still not convinced that this is the right solution. Not everybody
> uses NetworkManager + the fact that you need to manually enable
> anything seems wrong to me.
>
> A long time ago I wanted to fix the behavior of miredo to let it
> continue even if there are DNS errors (and retry or something). This really
> seems like the only way to really fix it "at the core".
>
> That said, I worked a long time ago on this. I'll have to refresh my
> mind about it and hopefully this time I get it done. I also welcome
> other people doing this for me! :D

Hi Tomasz,

agree, adding NetworkManager-wait-online.service or 
systemd-networkd-wait-online.servce slows boot process significantly and has 
probably big impact on the system overall.

What about adding automatic restart to miredo service?

Restart=on-failure 
RestartSec=60

In my case it does fix the problem and doesn't slow down boot process.


--
Best regards,
Andrey Skvortsov


signature.asc
Description: PGP signature

Bug#892491: mosquitto: systemctl restart failed because 'Address already in use' error

[Andrey Skvortsov]

Package: mosquitto
Version: 1.4.15-1
Severity: normal

Dear Maintainer,

command 'systemctl restart mosquitto.service' is executed successfully,
journalctl doesn't show any error as well, but mosquitto server is not started,
because old instance isn't entirely down and keeps listening on the TCP socket,
according to mosquitto's log.

Because of that it's necessary execute systemctl restart twice. So the server
is really started next time.


Below there are messages from mosquitto's log:

1520609740: mosquitto version 1.4.15 (build date Wed, 28 Feb 2018 11:29:47
+) starting
1520609740: Config loaded from /etc/mosquitto/mosquitto.conf.
1520609740: Opening ipv4 listen socket on port 1883.
1520609740: Error: Address already in use
1520609740: mosquitto version 1.4.15 terminating




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

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

Versions of packages mosquitto depends on:
ii  adduser 3.117
ii  libc6   2.27-1
ii  libssl1.1   1.1.0g-2
ii  libuuid12.31.1-0.4
ii  libwebsockets8  2.0.3-3
ii  libwrap07.6.q-27
ii  lsb-base9.20170808

mosquitto recommends no packages.

Versions of packages mosquitto suggests:
ii  apparmor  2.12-3

-- no debconf information

Bug#888946: [Pkg-utopia-maintainers] Bug#888946: network-manager-gnome: Can't establish VPN connection using GNOME UI

[Andrey Skvortsov]

On 18-01-31 16:12, Michael Biebl wrote:
> 
> Am 31.01.2018 um 13:43 schrieb Andrey Skvortsov:
> 
> > Jan 31 15:14:43 new-nest gnome-shell[18013]: Invalid VPN service type 
> > (cannot
> > find authentication binary)
> > Jan 31 15:14:43 new-nest gnome-shell[18013]: Invalid VPN service type 
> > (cannot
> > find authentication binary)
> > Jan 31 15:14:43 new-nest NetworkManager[8842]:  [1517400883.9090] 
> > vpn-
> > connection[0x55a425bce680,b2919892-9619-46a0-91c2-4c499b02b8fe,"ST",0]: 
> > Failed
> > to request VPN secrets #3: No agents were available for this request.
> 
> Duplicate of #888653
> 
> Short answer: Install gnome-shell from unstable. It's currently blocked
> by gjs from entering testing.
> 
> It's not a problem of network-manager-gnome

Thanks for the info.
#888653 is for network-manager-openvpn.
I'm using network-manager-vpnc-gnome. So it is affected as well.

I'll wait for gnome-shell entering testing. So far I'm okay to run
nm-applet occasionally by hand. Thanks.

-- 
Best regards,
Andrey Skvortsov




signature.asc
Description: PGP signature

Bug#888946: network-manager-gnome: Can't establish VPN connection using GNOME UI

[Andrey Skvortsov]

Package: network-manager-gnome
Version: 1.8.10-2
Severity: normal

Dear Maintainer,

- login to GNOME (I've tried GNOME on X11 and on Wayland),
- go to network manager UI and try to establish VPN connection
- VPN icon appears and immediately disappers

Here is log from journal:

Jan 31 15:14:43 new-nest NetworkManager[8842]:   [1517400883.8650] audit:
op="connection-activate" uuid="b2919892-9619-46a0-91c2-4c499b02b8fe" name="ST"
pid=18013 uid=1001 result="success"
Jan 31 15:14:43 new-nest NetworkManager[8842]:   [1517400883.8675] vpn-
connection[0x55a425bce680,b2919892-9619-46a0-91c2-4c499b02b8fe,"ST",0]: Started
the VPN service, PID 19381
Jan 31 15:14:43 new-nest NetworkManager[8842]:   [1517400883.8745] vpn-
connection[0x55a425bce680,b2919892-9619-46a0-91c2-4c499b02b8fe,"ST",0]: Saw the
service appear; activating connection
Jan 31 15:14:43 new-nest gnome-shell[18013]: Invalid VPN service type (cannot
find authentication binary)
Jan 31 15:14:43 new-nest gnome-shell[18013]: Invalid VPN service type (cannot
find authentication binary)
Jan 31 15:14:43 new-nest NetworkManager[8842]:  [1517400883.9090] vpn-
connection[0x55a425bce680,b2919892-9619-46a0-91c2-4c499b02b8fe,"ST",0]: Failed
to request VPN secrets #3: No agents were available for this request.
Jan 31 15:14:43 new-nest NetworkManager[8842]:   [1517400883.9097] vpn-
connection[0x55a425bce680,b2919892-9619-46a0-91c2-4c499b02b8fe,"ST",0]: VPN
plugin: state changed: stopped (6)

If I start nm-applet manually, then VPN connection can be established without
any issue.
`ps -A | grep nm-applet` run just after GNOME login doesn't show nm-applet
running.

As man page for nm-applet says, it should start automatically during login.
But apparently it's not.

There is similar bug report for Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/1725779



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

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

Versions of packages network-manager-gnome depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.2-1
ii  dbus-x11 [dbus-session-bus]   1.12.2-1
ii  dconf-gsettings-backend [gsettings-backend]   0.26.1-3
ii  gnome-flashback [polkit-1-auth-agent] 3.26.0-2
ii  gnome-shell [polkit-1-auth-agent] 3.26.2-3
ii  libatk1.0-0   2.26.1-3
ii  libc6 2.26-4
ii  libcairo2 1.15.8-3
ii  libgdk-pixbuf2.0-02.36.11-1
ii  libglib2.0-0  2.54.3-2
ii  libgtk-3-03.22.26-2
ii  libjansson4   2.10-1
ii  libmm-glib0   1.6.8-2
ii  libnm01.10.2-4
ii  libnma0   1.8.10-2
ii  libnotify40.7.7-3
ii  libpango-1.0-01.40.14-1
ii  libpangocairo-1.0-0   1.40.14-1
ii  libsecret-1-0 0.18.5-5
ii  libselinux1   2.7-2
ii  mate-polkit [polkit-1-auth-agent] 1.18.2-2
ii  network-manager   1.10.2-4
ii  policykit-1-gnome [polkit-1-auth-agent]   0.105-6

Versions of packages network-manager-gnome recommends:
ii  gnome-flashback [notification-daemon]   3.26.0-2
ii  gnome-keyring   3.20.1-2
ii  gnome-shell [notification-daemon]   3.26.2-3
ii  iso-codes   3.77-1
ii  mate-notification-daemon [notification-daemon]  1.18.1-1
ii  mobile-broadband-provider-info  20170903-1
ii  notification-daemon 3.20.0-2

Versions of packages network-manager-gnome suggests:
pn  network-manager-openconnect-gnome  
ii  network-manager-openvpn-gnome  1.8.0-2
pn  network-manager-pptp-gnome 
ii  network-manager-vpnc-gnome 1.2.4-6

-- no debconf information

Bug#876675: snapper: Avoid filling up btrfs, as it break the system?

[Andrey Skvortsov]

Hi,

I've run into the same problem. btrfs partition was full of snapper
snapshots and has made the system unbootable.
what about decrease default number of snapshots?

I see in Debian wiki it's recommended not to have more than 12
snapshots [1].

1. https://wiki.debian.org/Btrfs

-- 
Best regards,
Andrey Skvortsov


signature.asc
Description: PGP signature

Bug#861230: mutt: assumed_charset is ignored after verification of traditional pgp signature

[Andrey Skvortsov]

As a workaround for this issue I've added following lines to my .muttrc.

#
# because default codepage is not applied with traditional PGP and
# as a result non-latin messages with traditional signatures are unreadable
# use message-hook for that instead
unset pgp_auto_decode
message-hook '!(~g|~G) ~b"^-BEGIN\ PGP\ (SIGNED\ )?MESSAGE"' "push 
'; charset=utf-8'"


-- 
Best regards,
Andrey Skvortsov


signature.asc
Description: PGP signature

Bug#864864: hunspell: encoding error when using both en_US and ru_RU distionaries at the same time

[Andrey Skvortsov]

I see the same issue with 1.6.2 from buster.

huspell reports a lot of following errors, when Russian and English
are used at the same time.
'error - iconv: ISO8859-1 -> UTF-8'

ISO8856-1 comes probably from en_US dictionary encoding.
I've tried to use Russian and German dictionaries together as well.
The same issue happens. German dictionary is using ISO8859-1 as well.

I converted en_US dictionary to UTF-8 and this fixed my problem.

cp /usr/share/hunspell/en_US.aff  /usr/share/hunspell/en_US.aff.orig
cp /usr/share/hunspell/en_US.dic  /usr/share/hunspell/en_US.dic.orig
iconv --from ISO8859-1 /usr/share/hunspell/en_US.aff.orig > 
/usr/share/hunspell/en_US.aff
iconv --from ISO8859-1 /usr/share/hunspell/en_US.dic.orig > 
/usr/share/hunspell/en_US.dic
sed -i /usr/share/hunspell/en_US.aff  's/SET ISO8859-1/SET UTF-8/'


-- 
Best regards,
Andrey Skvortsov


signature.asc
Description: PGP signature

Bug#871652: jnoise: Italian translation of package description has a little typo

[Andrey Skvortsov]

On 17-08-30 23:23, Mattia Rizzolo wrote:
> Control: tag -1 l10n
> 
> On Thu, Aug 10, 2017 at 02:24:41PM +0200, Leandro Noferini wrote:
> > Package: jnoise
> > Severity: minor
> > 
> > The word "rumero" is a typo for "rumore" -> noise
> 
> This is not coming from the package itself, but from the DDTP.
> CCing debian-i...@lists.debian.org as I have no idea how to update the
> translated description of the packages.

Hi Leandro,

you could use DDTSS for that
https://ddtp2.debian.net/ddtss/index.cgi/it

There is field 'Fetch specific description' with option 'Force
fetching even if not untranslated' there. Put name of your package
there and then you can retranslate package description. Afterwards
someone should review your translation and then it'll
be submitted.

More information you can find here:
https://www.debian.org/international/l10n/ddtp
https://wiki.debian.org/it/L10n/Italian/DDTP/DDTSS/Tools

-- 
Best regards,
Andrey Skvortsov




signature.asc
Description: PGP signature

Bug#783387: dhclient does not wait for ipv6 dad

[Andrey Skvortsov]

Hi,

this bug still exists in Debian Stretch and Buster.
I have similar problem on my Freedombox running Debian Stretch.

Ubuntu tracker has the same issue [1] and they already have fix for
that [2]. I tried the patch and it works and solves problem for me.

1. https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1633479
2. https://launchpadlibrarian.net/289550738/suggested-fix.diff

-- 
Best regards,
Andrey Skvortsov




signature.asc
Description: PGP signature

Bug#865195: www.debian.org: Some broken links on the page "Downloading Debian CD images with BitTorrent"

[Andrey Skvortsov]

Package: www.debian.org
Severity: normal

Dear Maintainer,

on the page "Downloading Debian CD images with BitTorrent"
https://www.debian.org/CD/torrent-cd/
in section 'Official torrents for the "stable" release'

for CD link to "source"
https://cdimage.debian.org/debian-cd/current/source/bt-cd/ returns 404.

for DVD link to "multi-arch"
https://cdimage.debian.org/debian-cd/current/multi-arch/bt-dvd/ returns 404.

Are multi-arch DVD not going to be generated or just something went wrong?


Best regards,
Andrey Skvortsov



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

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

Bug#861230: mutt: assumed_charset is ignored after verification of traditional pgp signature

[Andrey Skvortsov]

is unset
keywords_legacy is set
keywords_standard is unset
mail_check=180
mail_check_recent is set
mail_check_stats is unset
mail_check_stats_interval=60
mailcap_path="~/.mailcap:/usr/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap"
mailcap_sanitize is set
maildir_header_cache_verify is set
maildir_trash is unset
maildir_check_cur is unset
mark_macro_prefix="'"
mark_old is set
markers is unset
mask="!^\\.[^.]"
mbox="~/mbox"
mbox_type=Maildir
menu_context=0
menu_move_off is set
menu_scroll is set
message_cache_clean is unset
message_cachedir="~/.mutt/cache/bodies"
message_format="%s"
meta_key is unset
metoo is unset
mh_purge is unset
mh_seq_flagged="flagged"
mh_seq_replied="replied"
mh_seq_unseen="unseen"
mime_forward=ask-no
mime_forward_decode is unset
mime_forward_rest=yes
mime_subject is set
mix_entry_format="%4n %c %-16s %a"
mixmaster="mixmaster-filter"
move=no
narrow_tree is unset
net_inc=10
new_mail_command=""
news_cache_dir="~/.mutt"
news_server=""
newsgroups_charset="utf-8"
newsrc="~/.newsrc"
nntp_authenticators=""
nntp_context=1000
nntp_listgroup is set
nntp_load_description is set
nntp_user=""
nntp_pass=""
nntp_poll=60
nm_open_timeout=5
nm_default_uri=""
nm_hidden_tags="unread,draft,flagged,passed,replied,attachment,signed,encrypted"
nm_exclude_tags=""
nm_unread_tag="unread"
nm_db_limit=0
nm_query_type="messages"
nm_record is unset
nm_record_tags=""
nm_query_window_duration=0
nm_query_window_timebase="week"
nm_query_window_current_search=""
nm_query_window_current_position=0
pager="builtin"
pager_context=5
pager_format="-%Z- %C/%m: %-20.20n   %s%*  -- (%P)"
pager_index_lines=8
pager_stop is set
pgp_auto_decode is unset
pgp_autoinline is unset
pgp_check_exit is set
pgp_clearsign_command="gpg --no-verbose --batch --quiet --output - 
%?p?--passphrase-fd 0 --pinentry-mode=loopback? --armor --textmode --clearsign 
%?a?-u %a? %f"
pgp_decode_command="gpg --status-fd=2 %?p?--passphrase-fd 0 
--pinentry-mode=loopback? --no-verbose --quiet --batch --output - %f"
pgp_decrypt_command="gpg --status-fd=2 %?p?--passphrase-fd 0 
--pinentry-mode=loopback? --no-verbose --quiet --batch --output - %f"
pgp_decryption_okay="^\\[GNUPG:\\] DECRYPTION_OKAY"
pgp_encrypt_only_command="/usr/lib/mutt/pgpewrap gpg --batch --quiet 
--no-verbose --output - --encrypt --textmode --armor --always-trust -- -r %r -- 
%f"
pgp_encrypt_sign_command="/usr/lib/mutt/pgpewrap gpg %?p?--passphrase-fd 0 
--pinentry-mode=loopback? --batch --quiet --no-verbose --textmode --output - 
--encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f"
pgp_entry_format="%4n %t%f %4l/0x%k %-4a %2c %u"
pgp_export_command="gpg --no-verbose --export --armor %r"
pgp_getkeys_command=""
pgp_good_sign="^\\[GNUPG:\\] GOODSIG"
pgp_ignore_subkeys is set
pgp_import_command="gpg --no-verbose --import %f"
pgp_list_pubring_command="gpg --no-verbose --batch --quiet --with-colons 
--with-fingerprint --with-fingerprint --list-keys %r"
pgp_list_secring_command="gpg --no-verbose --batch --quiet --with-colons 
--with-fingerprint --with-fingerprint --list-secret-keys %r"
pgp_long_ids is set
pgp_mime_auto=ask-yes
pgp_replyinline is unset
pgp_retainable_sigs is unset
pgp_show_unusable is set
pgp_sign_as="0x22362F2657A3AEAD"
pgp_sign_command="gpg --no-verbose --batch --quiet --output - 
%?p?--passphrase-fd 0 --pinentry-mode=loopback? --armor --detach-sign 
--textmode %?a?-u %a? %f"
pgp_sort_keys=address
pgp_strict_enc is set
pgp_timeout=1800
pgp_use_gpg_agent is unset
pgp_verify_command="gpg --status-fd=2 --no-verbose --quiet --batch --output - 
--verify %s %f"
pgp_verify_key_command="gpg --verbose --batch --fingerprint --check-sigs %r"
pipe_decode is unset
pipe_sep="\n"
pipe_split is unset
pop_auth_try_all is set
pop_authenticators=""
pop_checkinterval=60
pop_delete=ask-no
pop_host=""
pop_last is unset
pop_pass=""
pop_reconnect=ask-yes
pop_user=""
post_indent_string=""
post_moderated=ask-yes
postpone=ask-yes
postponed="=[Gmail].Drafts"
postpone_encrypt is unset
postpone_encrypt_as=""
preconnect=""
print=ask-no
print_command="lpr"
print_decode is set
print_split is unset
prompt_after is set
query_command="lbdbq %s 2>/dev/null"
query_format="%4c %t %-25.25a %-25.25n %?e?(%e)?"
quit=yes
quote_regexp="^([ \t]*[|>:}#])+"
read_inc=10
read_only is unset
realname="Andrey Skvortsov"
recall=ask-yes
record=""
reflow_space_quotes is set
reflow_text

Bug#856341: python-wxgtk3.0: Warning about wxPython is using an older C++ ABI

[Andrey Skvortsov]

Package: python-wxgtk3.0
Version: 3.0.2.0+dfsg-3
Severity: minor

Dear Maintainer,

If wxPython application (for example wxglade) is started, warning about
mismatching C++ ABI is shown.

Here is simple example to reproduce the case.

$ python -c 'import wx'
11:15:20: Warning: Mismatch between the program and library build versions
detected.
The library used 3.0 (wchar_t,compiler with C++ ABI 1010,wx
containers,compatible with 2.8),
and wxPython used 3.0 (wchar_t,compiler with C++ ABI 1009,wx
containers,compatible with 2.8).

Probably wxPython needs to be rebuilt to make this warning go away.



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

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

Versions of packages python-wxgtk3.0 depends on:
ii  libc6 2.24-9
ii  libgcc1   1:6.3.0-6
ii  libstdc++66.3.0-6
ii  libwxbase3.0-0v5  3.0.2+dfsg-2+b1
ii  libwxgtk3.0-0v5   3.0.2+dfsg-2+b1
ii  python2.7.13-2
ii  python-wxversion  3.0.2.0+dfsg-3
pn  python:any

python-wxgtk3.0 recommends no packages.

Versions of packages python-wxgtk3.0 suggests:
pn  wx3.0-doc  

-- no debconf information

Bug#822183: Crossbar.io dependencies

[Andrey Skvortsov]

I looked at the list of missing dependencies and it's much shorter now.
Only three packages are missing:
python{3}-pytrie
python{3}-shutilwhich
python{3}-wsaccel

-- 
Best regards,
Andrey Skvortsov

Bug#835866: icedove fails to connect to existing google apps accounts

[Andrey Skvortsov]

Same here.
I'm using icedove only for calendar management with iceowl. To access
google calendar I'm using calendar-google-provider.

After upgrade to 45.2.0-4+b1 calendar stopped working.
I got authentication error messages in console. To update OAuth2
authentication credentials I removed old credentials.
Now icedove shows empty window there it asked in the past e-mail and password to
access google calendar.

I get activity log for all modules, but it's 30M.
NSPR_LOG_MODULES=all:5 NSPR_LOG_FILE=~/icedove-activity.log icedove


-- 
Best regards,
Andrey Skvortsov




signature.asc
Description: PGP signature

Bug#837045: mutt: wrong handling of symbol '>' in conditional expression

[Andrey Skvortsov]

On 16-09-08 11:37, Richard Russon wrote:
> I haven't decided how to fix this problem, yet, so you have two options.
> Escape the <> chars, or choose different ones.
> 
> The upstream (NeoMutt) bug is tracked, here:
> https://github.com/neomutt/neomutt/issues/113
>

Thanks for the info.
For myself I just choose different characters instead of '<' and '>'.

-- 
Best regards,
Andrey Skvortsov


signature.asc
Description: PGP signature

Bug#837046: picocom: missing support of stop bit setting

[Andrey Skvortsov]

Package: picocom
Version: 1.7-1
Severity: normal

It's impossible to open serial port with two stop bits.

This is fixed upstream already.

https://github.com/npat-
efault/picocom/commit/8fd1e4de410afd0038767a1525f5a082ed5fabe1
https://github.com/npat-
efault/picocom/commit/c24a3bcf410afcf7b30c53a91cd89f0647344827

It'd be nice to have newer upstream version packaged.



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

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

Versions of packages picocom depends on:
ii  libc6  2.23-4

picocom recommends no packages.

picocom suggests no packages.

-- no debconf information

Bug#837045: mutt: wrong handling of symbol '>' in conditional expression

[Andrey Skvortsov]

Package: mutt
Version: 1.7.0-1
Severity: normal

Dear Maintainer,

after upgrading from mutt 1.6.0-1 to mutt 1.7.0-1 (NeoMutt) in testing I see
following regression.

I have this setting in my muttrc
set index_format="%4C | %Z [%D] %-35.35F (%-4.4c) %?M?<%M> ?%s"

The problem is in part '%?M?<%M> ?'. Number of hidden messages in thread are
only shown it thread is collapsed, like this '<10>'.
If thread is not collapsed and no messages are hidden, then nothig should be
shown.
So it worked on mutt 1.6.0.

In NeoMutt 1.7.0 I see following issue. With the same index_format if thread is
not collapsed ' >' is shown.


If index_format is modified to
"%4C | %Z [%D] %-35.35F (%-4.4c) %?M?before>after?%s"

In mutt 'after>' is shown, there nothing should be shown at all.
If I replace with '>' there with any other character, then all works correctly
as before, nothing is shown if thread is not collapsed.

It looks like mutt takes all characters after '>' in if_string, prints they
regardless of condition value and appends at the end symbol '>'.



-- Package-specific info:
NeoMutt  (1.7.0)
Copyright (C) 1996-2016 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 4.7.0 (x86_64)
libidn: 1.33 (compiled with 1.33)
hcache backend: tokyocabinet 1.4.48

Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.2.0-1' 
--with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs 
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-6 --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib 
--disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo 
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre --enable-java-home 
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64 
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--enable-objc-gc --enable-multiarch --with-arch-32=i686 --with-abi=m64 -
 -with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix
gcc version 6.2.0 20160822 (Debian 6.2.0-1) 

Configure options: '--build=x86_64-linux-gnu' '--prefix=/usr' 
'--includedir=\${prefix}/include' '--mandir=\${prefix}/share/man' 
'--infodir=\${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var' 
'--disable-silent-rules' '--libdir=\${prefix}/lib/x86_64-linux-gnu' 
'--libexecdir=\${prefix}/lib/x86_64-linux-gnu' '--disable-maintainer-mode' 
'--disable-dependency-tracking' '--with-mailpath=/var/mail' 
'--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' 
'--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-pop' 
'--enable-sidebar' '--enable-nntp' '--enable-notmuch' '--disable-fmemopen' 
'--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with-mixmaster' 
'--with-sasl' '--without-gdbm' '--without-bdb' '--without-qdbm' 
'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 
-fdebug-prefix-map=/build/mutt-wQLglL/mutt-1.7.0=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security' 'LDFLAGS=-fPIE -pie 
-Wl,-z,relro -Wl,-z,now' 'CPPFLAGS=-Wdate-time -D_FORT
 IFY_SOURCE=2'

Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O2 
-fdebug-prefix-map=/build/mutt-wQLglL/mutt-1.7.0=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security

Compile options:
+CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME 
+DEBUG +DL_STANDALONE +ENABLE_NLS -EXACT_ADDRESS -HOMESPOOL -LOCALES_HACK 
-SUN_ATTACHMENT +HAVE_BKGDSET +HAVE_COLOR +HAVE_CURS_SET +HAVE_GETADDRINFO 
+HAVE_GETSID +HAVE_ICONV +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR 
+HAVE_LIBIDN +HAVE_META +HAVE_REGCOMP +HAVE_RESIZETERM +HAVE_START_COLOR 
+HAVE_TYPEAHEAD +HAVE_WC_FUNCS +ICONV_NONTRANS +USE_COMPRESSED +USE_DOTLOCK 
+USE_FCNTL -USE_FLOCK -USE_FMEMOPEN -USE_GNU_REGEX +USE_GSS +USE_HCACHE 
+USE_IMAP +USE_NOTMUCH +USE_NNTP +USE_POP +USE_SASL +USE_SETGID +USE_SIDEBAR 
+USE_SMTP +USE_SSL_GNUTLS -USE_SSL_OPENSSL 
-DOMAIN
MIXMASTER="mixmaster"
-ISPELL
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/mail"
PKGDATADIR="/usr/share/mutt"
SYSCONFDIR="/etc"
EXECSHELL="/bin/sh"

patch-compress-neomutt
patch-cond-date-neomutt
patch-fmemopen-neomutt
patch-ifdef-neomutt
patch-index-color-neomutt
patch-initials-neomutt

Bug#796141: Patch to fix the issue

[Andrey Skvortsov]

Hi,

here is the patch that makes qct gracefully ignore missing settings in
config file.

-- 
Best regards,
Andrey Skvortsov
# HG changeset patch
# User Andrey Skvortsov <andrej.skvort...@gmail.com>
# Date 1464616629 -10800
#  Mon May 30 16:57:09 2016 +0300
# Node ID dc45740c1cbf1b372fc3f416ad1fec7e148f1a12
# Parent  c5f6a035039b8f9d53b8c06777e15cba5eefe5d4
qctlib/vcs/hg: make run qct when qct.signoff property is missing in hg config file

diff -r c5f6a035039b -r dc45740c1cbf qctlib/vcs/hg.py
--- a/qctlib/vcs/hg.py	Tue Jan 25 08:24:34 2011 -0600
+++ b/qctlib/vcs/hg.py	Mon May 30 16:57:09 2016 +0300
@@ -86,8 +86,12 @@
 # To enable an auto-matic sign-off message:
 # [qct]
 # signoff = Sign-Off: Steve Borho
-self.signOff = self.hgcmd(['showconfig', 'qct.signoff'])[0]
-
+try:
+self.signOff = self.hgcmd(['showconfig', 'qct.signoff'])[0]
+except ProgramError:
+self.signOff = None
+pass
+
 # Determine if this repository has any applied Mercurial Queue patches
 (output, err) = self.hgcmd(['qheader'], okresults=[0,1,255])
 if err and "unknown command" in err:


signature.asc
Description: PGP signature

Bug#821401: libreoffice-gtk3: First [Ctrl+Scroll Down] after changing focus to LO makes LO to zoom in instead of zoom out

[Andrey Skvortsov]

Package: libreoffice-gtk3
Version: 1:5.1.2-3
Severity: normal

Dear Maintainer,

steps to reproduce the problem:
1. install libreoffice with libreoffice-gtk3 package.
2. start any libreoffice program
3. start other application (it can be even other LO editor)
4. change focus to libreoffice program started at step 2
5. try to zoom out using [Ctrl + scroll down]
6. on first scroll down even LO zooms in (that is wrong) and on next scroll
down events it zooms out like it should.

The problem is only the first [Ctrl + scroll down] event after changing focus
to the editor. Zoom in ([Ctrl + scroll up]) works correctly.

If libreoffice-gtk3 package is removed, then libreoffice doesn't have native
gtk3 look, but zoom out works correctly. Therefore I decided that problems is
somethere in libreoffice-gtk3 package. I've not found such problem in other
applications.



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

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

Versions of packages libreoffice-gtk3 depends on:
ii  dpkg  1.18.4
ii  libatk1.0-0   2.20.0-1
ii  libc6 2.22-6
ii  libcairo-gobject2 1.14.6-1+b1
ii  libcairo2 1.14.6-1+b1
ii  libdbus-1-3   1.10.8-1
ii  libdbus-glib-1-2  0.106-1
ii  libgcc1   1:5.3.1-14
ii  libgdk-pixbuf2.0-02.32.3-2
ii  libgl1-mesa-glx [libgl1]  11.1.2-1
ii  libglew1.13   1.13.0-2
ii  libglib2.0-0  2.48.0-1
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgtk-3-03.18.9-1
ii  libice6   2:1.0.9-1+b1
ii  libpango-1.0-01.38.1-1
ii  libpangocairo-1.0-0   1.38.1-1
ii  libreoffice-core  1:5.1.2-3
ii  libsm62:1.2.2-1+b1
ii  libstdc++65.3.1-14
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  uno-libs3 5.1.2-3
ii  ure   5.1.2-3

Versions of packages libreoffice-gtk3 recommends:
ii  libreoffice-style-tango  1:5.1.2-3

libreoffice-gtk3 suggests no packages.

-- no debconf information

Bug#739363: miredo and .service

[Andrey Skvortsov]

Hi Ruslan,

your solution is not complete. At least in my case it's not enough.
There are a bit more requirements:

1. Add in miredo.service
After=network-online.target
Wants=network-online.target

2. By default network-online.target is not waiting really for the
network to come up. Depend on your configuration you need to pull into
network-online.target other services: NetworkManager-wait-online.service or
systemd-networkd-wait-online.servce. By default both services are
disabled and don't slow down boot process.

I use NetworkManager, therefore I enabled
NetworkManager-wait-online.service and only then miredo started after the
network was really online.

-- 
Best regards,
Andrey Skvortsov

Secure eMail with gnupg: See http://www.gnupg.org/
PGP Key ID: 0x57A3AEAD


signature.asc
Description: PGP signature

Bug#779207: comment

[Andrey Skvortsov]

I'm pretty often have this problem with Cyrillic characters in
filenames. So this is not related only to German, but for all locales
with non-latin characters.
This problem is already solved by Altlinux (Russian Linux distro).
Ubuntu is using their patch. 

unzip (6.0-20ubuntu1) xenial; urgency=medium

  * Resynchronise with Debian. Remaining changes:
- Add patch from archlinux which adds the -O option, allowing a charset
  to be specified for the proper unzipping of non-Latin and non-Unicode
  filenames.

Archlinux uses it too, according to the bug report:
https://bugs.archlinux.org/task/8383

Patch from Ubuntu is attached.

-- 
Best regards,
Andrey Skvortsov

Secure e-mail with gnupg: See http://www.gnupg.org/
PGP Key ID: 0x57A3AEAD


From: Giovanni Scafora 
Subject: unzip files encoded with non-latin, non-unicode file names
Last-Update: 2015-02-11

Updated 2015-02-11 by Marc Deslauriers <marc.deslauri...@canonical.com>
to fix buffer overflow in charset_to_intern()

Index: unzip-6.0/unix/unix.c
===
--- unzip-6.0.orig/unix/unix.c	2015-02-11 08:46:43.675324290 -0500
+++ unzip-6.0/unix/unix.c	2015-02-11 09:18:04.902081319 -0500
@@ -30,6 +30,9 @@
 #define UNZIP_INTERNAL
 #include "unzip.h"
 
+#include 
+#include 
+
 #ifdef SCO_XENIX
 #  define SYSNDIR
 #else  /* SCO Unix, AIX, DNIX, TI SysV, Coherent 4.x, ... */
@@ -1874,3 +1877,102 @@
 }
 }
 #endif /* QLZIP */
+
+
+typedef struct {
+char *local_charset;
+char *archive_charset;
+} CHARSET_MAP;
+
+/* A mapping of local <-> archive charsets used by default to convert filenames
+ * of DOS/Windows Zip archives. Currently very basic. */
+static CHARSET_MAP dos_charset_map[] = {
+{ "ANSI_X3.4-1968", "CP850" },
+{ "ISO-8859-1", "CP850" },
+{ "CP1252", "CP850" },
+{ "UTF-8", "CP866" },
+{ "KOI8-R", "CP866" },
+{ "KOI8-U", "CP866" },
+{ "ISO-8859-5", "CP866" }
+};
+
+char OEM_CP[MAX_CP_NAME] = "";
+char ISO_CP[MAX_CP_NAME] = "";
+
+/* Try to guess the default value of OEM_CP based on the current locale.
+ * ISO_CP is left alone for now. */
+void init_conversion_charsets()
+{
+const char *local_charset;
+int i;
+
+/* Make a guess only if OEM_CP not already set. */ 
+if(*OEM_CP == '\0') {
+	local_charset = nl_langinfo(CODESET);
+	for(i = 0; i < sizeof(dos_charset_map)/sizeof(CHARSET_MAP); i++)
+		if(!strcasecmp(local_charset, dos_charset_map[i].local_charset)) {
+			strncpy(OEM_CP, dos_charset_map[i].archive_charset,
+	sizeof(OEM_CP));
+			break;
+		}
+}
+}
+
+/* Convert a string from one encoding to the current locale using iconv().
+ * Be as non-intrusive as possible. If error is encountered during covertion
+ * just leave the string intact. */
+static void charset_to_intern(char *string, char *from_charset)
+{
+iconv_t cd;
+char *s,*d, *buf;
+size_t slen, dlen, buflen;
+const char *local_charset;
+
+if(*from_charset == '\0')
+	return;
+
+buf = NULL;
+local_charset = nl_langinfo(CODESET);
+
+if((cd = iconv_open(local_charset, from_charset)) == (iconv_t)-1)
+return;
+
+slen = strlen(string);
+s = string;
+
+/*  Make sure OUTBUFSIZ + 1 never ends up smaller than FILNAMSIZ
+ *  as this function also gets called with G.outbuf in fileio.c
+ */
+buflen = FILNAMSIZ;
+if (OUTBUFSIZ + 1 < FILNAMSIZ)
+{
+buflen = OUTBUFSIZ + 1;
+}
+
+d = buf = malloc(buflen);
+if(!d)
+	goto cleanup;
+
+bzero(buf,buflen);
+dlen = buflen - 1;
+
+if(iconv(cd, , , , ) == (size_t)-1)
+	goto cleanup;
+strncpy(string, buf, buflen);
+
+cleanup:
+free(buf);
+iconv_close(cd);
+}
+
+/* Convert a string from OEM_CP to the current locale charset. */
+inline void oem_intern(char *string)
+{
+charset_to_intern(string, OEM_CP);
+}
+
+/* Convert a string from ISO_CP to the current locale charset. */
+inline void iso_intern(char *string)
+{
+charset_to_intern(string, ISO_CP);
+}
Index: unzip-6.0/unix/unxcfg.h
===
--- unzip-6.0.orig/unix/unxcfg.h	2015-02-11 08:46:43.675324290 -0500
+++ unzip-6.0/unix/unxcfg.h	2015-02-11 08:46:43.671324260 -0500
@@ -228,4 +228,30 @@
 /* wild_dir, dirname, wildname, matchname[], dirnamelen, have_dirname, */
 /*and notfirstcall are used by do_wild().  */
 
+
+#define MAX_CP_NAME 25 
+   
+#ifdef SETLOCALE
+#  undef SETLOCALE
+#endif
+#define SETLOCALE(category, locale) setlocale(category, locale)
+#include 
+   
+#ifdef _ISO_INTERN
+#  undef _ISO_INTERN
+#endif
+#define _ISO_INTERN(str1) iso_intern(str1)
+
+#ifdef _OEM_INTERN
+#  undef _OEM_INTERN
+#endif
+#ifndef IZ_OEM2ISO_ARRAY
+#  define IZ_OEM2IS

Bug#810530: subdownloader: Subdownloader does not download subtitles anymore

[andrey skvortsov]

Package: subdownloader
Version: 2.0.18-1
Severity: important

Dear Maintainer,

in Dezember 2015 opensubtitles.org changed their API slightly, so SubDownloader
is not working anymore. On download subtitle program reports "It's not
possible".

The bug is known by upstream and patch is already available here:
https://bugs.launchpad.net/subdownloader/+bug/1528605



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

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

Versions of packages subdownloader depends on:
ii  python   2.7.11-1
ii  python-crypto2.6.1-6
ii  python-kaa-metadata  0.7.7+svn4596-4
pn  python:any   

Versions of packages subdownloader recommends:
ii  python-qt4  4.11.4+dfsg-1+b2

subdownloader suggests no packages.

-- no debconf information

Bug#807127: wireshark: license tab is empty, missing COPYING file

[Andrey Skvortsov]

Package: wireshark
Version: 2.0.0+g9a73b82-1
Severity: normal

Dear Maintainer,

to reproduce the bug
1. run wireshark,
2. select menu "Help->About",
3. switch to "License" tab.
4. There is no license


If wireshark is run from terminal. It's possible to see error message about
that problem:

"QIODevice::read (QFile, "/usr/share/wireshark/COPYING"): device not open"

I expect to see the license there.



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

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

Versions of packages wireshark depends on:
ii  wireshark-qt  2.0.0+g9a73b82-1

wireshark recommends no packages.

wireshark suggests no packages.

-- no debconf information

Bug#805585: gnome-control-center: IPv6 address is set for the Ethernet interface dispite of the settings in gnome-control-center

[Andrey Skvortsov]

Package: gnome-control-center
Version: 1:3.18.2-1
Severity: normal
Tags: ipv6

Dear Maintainer,

my network have IPv6 support and all my machines get IPv6 addresses by default.

I tried to disable IPv6 addresses on one machine on certain interface using
gnome-control-center.
But despite of the disabled IPv6 option network interfaces gets IPv6 address
after reconnection.
IPv6 option in gnome-control-center is still disabled.
I expected, that network interface shouldn't have IPv6 address if the option is
disabled.



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

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

Versions of packages gnome-control-center depends on:
ii  accountsservice0.6.40-3
ii  apg2.2.3.dfsg.1-2
ii  colord 1.2.12-1
ii  desktop-file-utils 0.22-1
ii  gnome-control-center-data  1:3.18.2-1
ii  gnome-desktop3-data3.18.2-1
ii  gnome-icon-theme   3.12.0-1
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  gnome-settings-daemon  3.18.2-1
ii  gsettings-desktop-schemas  3.18.1-1
ii  libaccountsservice00.6.40-3
ii  libatk1.0-02.18.0-1
ii  libc6  2.19-22
ii  libcairo-gobject2  1.14.4-1
ii  libcairo2  1.14.4-1
ii  libcanberra-gtk3-0 0.30-2.1
ii  libcanberra0   0.30-2.1
ii  libcheese-gtk253.18.1-2
ii  libcheese8 3.18.1-2
ii  libclutter-1.0-0   1.24.2-1
ii  libclutter-gtk-1.0-0   1.6.6-1
ii  libcolord-gtk1 0.1.25-1.1+b1
ii  libcolord2 1.2.12-1
ii  libcups2   2.1.0-6
ii  libdbus-glib-1-2   0.102-1
ii  libfontconfig1 2.11.0-6.3
ii  libgdk-pixbuf2.0-0 2.32.2-1
ii  libgl1-mesa-glx [libgl1]   11.0.5-1
ii  libglib2.0-0   2.46.2-1
ii  libgnome-bluetooth13   3.18.1-1
ii  libgnome-desktop-3-12  3.18.2-1
ii  libgoa-1.0-0b  3.18.2.1-1
ii  libgoa-backend-1.0-1   3.18.2.1-1
ii  libgrilo-0.2-1 0.2.14-1
ii  libgtk-3-0 3.18.2-1
ii  libgtop-2.0-10 2.32.0-1
ii  libgudev-1.0-0 230-2
ii  libibus-1.0-5  1.5.10-1
ii  libkrb5-3  1.13.2+dfsg-4
ii  libmm-glib01.4.12-1
ii  libnm-glib-vpn11.0.6-1
ii  libnm-glib41.0.6-1
ii  libnm-gtk0 1.0.6-2
ii  libnm-util21.0.6-1
ii  libpango-1.0-0 1.38.1-1
ii  libpangocairo-1.0-01.38.1-1
ii  libpolkit-gobject-1-0  0.105-13
ii  libpulse-mainloop-glib07.1-2
ii  libpulse0  7.1-2
ii  libpwquality1  1.2.3-1
ii  libsmbclient   2:4.1.17+dfsg-4
ii  libsoup2.4-1   2.52.1-1
ii  libupower-glib30.99.3-1+b2
ii  libwacom2  0.15-1
ii  libx11-6   2:1.6.3-1
ii  libxi6 2:1.7.5-1
ii  libxml22.9.2+zdfsg1-4

Versions of packages gnome-control-center recommends:
ii  cracklib-runtime 2.9.2-1+b1
ii  cups-pk-helper   0.2.5-2+b1
ii  gkbd-capplet 3.6.0-1
ii  gnome-online-accounts3.18.2.1-1
ii  gnome-user-guide 3.18.1-1
ii  gnome-user-share 3.18.0-1
ii  iso-codes3.63-1
ii  libnss-myhostname227-2
ii  mate-polkit [policykit-1-gnome]  1.10.2-1
ii  mesa-utils   8.2.0-3+b1
ii  mousetweaks  3.12.0-1
ii  network-manager-gnome1.0.6-2
ii  policykit-1-gnome0.105-2
ii  pulseaudio-module-bluetooth  7.1-2
ii  realmd   0.16.2-1
ii  rygel0.28.1-1
ii  rygel-tracker0.28.1-1
ii  system-config-printer1.5.7-1

Versions of packages gnome-control-center suggests:
ii  gstreamer1.0-pulseaudio  1.6.1-1
ii  libcanberra-gtk-module   0.30-2.1
ii  libcanberra-gtk3-module  0.30-2.1
ii  x11-xserver-utils7.7+5

-- debconf-show failed

Bug#797598: gpodder: sync does not stop if no space left on the device

[Andrey Skvortsov]

Package: gpodder
Version: 3.8.4-1
Severity: normal
Tags: upstream

Dear Maintainer,

if during synchronization with filesystem-based player no space is left on the
device, synchronization does not stop. It continues until all episodes staged
for synchronization are processed. No error message appears, but not all
episodes are copied to the player.

If option "After syncing an episode" is "Mask as played", all episodes are
marked as played, even unsynced.
The most annoying thing is here, that user needs manual to check and to mark
all episodes that aren't exist on the player, i. e. were not synced.

Possible the things are even worser, if option "After syncing an episode" is
"Delete from gpodder". This would lead to deleted unsynced episodes. I've not
tested this option by myself, but there is old bug report about this:

https://bugs.gpodder.org/show_bug.cgi?id=1644


The best solution would be to stop synchronization, if there is no space on the
destination player.



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

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

Versions of packages gpodder depends on:
ii  libjs-jquery 1.7.2+dfsg-3.2
ii  libjs-jquery-mobile  1.2.0+dfsg-2
ii  python   2.7.9-1
ii  python-dbus  1.2.0-2+b3
ii  python-feedparser5.1.3-3
ii  python-gtk2  2.24.0-4
ii  python-mygpoclient   1.7-1
ii  python-webkit1.1.8-3
pn  python:any   

Versions of packages gpodder recommends:
ii  dbus-x11 1.8.20-1
ii  libqtwebkit-qmlwebkitplugin  2.3.4.dfsg-3
pn  python-appindicator  
ii  python-simplejson3.7.3-1

Versions of packages gpodder suggests:
ii  gnome-bluetooth  3.16.1-1
pn  mplayer  

-- no debconf information

Bug#781384: installation-report: successful installation on UEFI machine

[Andrey Skvortsov]

Package: installation-reports
Version: 2.58
Severity: normal

Dear Maintainer,

-- Package-specific info:

Boot method: USB
Image version: daily snapshot (2015-02-14) of netinst image amd64
Date: 2015-02-14

Machine: ASUS P8H67-M PRO with Intel i5-2500
Partitions: 
/dev/sdb2  ext4 55538044   8896812   43796972  17% /
/dev/sdc6  ext4926917244 720512892  159298060  82% /home
/dev/sdb3  vfat  2043988   1322043856   1% /boot/efi
/dev/sdb1  btrfs  1894907904 155287160 1737733968   9% /media/BACKUP


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [ ]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

On latest defconf Steve McIntyre recommended to force UEFI during
installations, if possible and send reports even if no bug were
happen.
So my machine was UEFI capable and d-i worked as expected, no problems at all.


-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=8 (jessie) - installer build 20150214-00:02
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux nest 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt4-3 (2015-02-03) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core 
Processor Family DRAM Controller [8086:0100] (rev 09)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:844d]
lspci -knn: Kernel driver in use: snb_uncore
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd 
Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd 
Generation Core Processor Family Integrated Graphics Controller [8086:0102] 
(rev 09)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:844d]
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 6 
Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:844d]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 
Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:844d]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series 
Chipset Family High Definition Audio Controller [8086:1c20] (rev 05)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:841b]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b5)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 5 [8086:1c18] (rev b5)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 6 [8086:1c1a] (rev b5)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.6 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 7 [8086:1c1c] (rev b5)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.7 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge 
[8086:244e] (rev b5)
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 
Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 05)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:844d]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation H67 Express Chipset 
Family LPC Controller [8086:1c4a] (rev 05)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:844d]
lspci -knn: 00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 
Series Chipset Family SATA AHCI Controller [8086:1c02] (rev 05)
lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:844d]
lspci -knn: Kernel driver in use: ahci
lspci 

Bug#781401: installation-report: successful installation

[andrey skvortsov]

Package: installation-reports
Version: 2.58
Severity: normal

Dear Maintainer,

-- Package-specific info:

Boot method: USB
Image version: daily snapshot of netinst amd64 (2015-01-29)
Date: 2015-01-29

Machine: DELL Vostro 1500
Partitions: 
/dev/sdb1  ext4  38314312  18513664  17831296  51% /
/dev/sda2  ext4 470207904 399248072  47051592  90% /media/data
/dev/sdb2  ext4  69104664  30731320  34839956  47% /home


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [ ]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]


-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=8 (jessie) - installer build 20150129-00:02
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux crion86 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt4-2 (2015-01-27) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 
PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c)
lspci -knn: Subsystem: Dell Device [1028:0228]
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c)
lspci -knn: Subsystem: Dell Device [1028:0228]
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 
GM965/GL960 Integrated Graphics Controller (secondary) [8086:2a03] (rev 0c)
lspci -knn: Subsystem: Dell Device [1028:0228]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #4 [8086:2834] (rev 02)
lspci -knn: Subsystem: Dell Device [1028:0228]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.1 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #5 [8086:2835] (rev 02)
lspci -knn: Subsystem: Dell Device [1028:0228]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.7 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB2 EHCI Controller #2 [8086:283a] (rev 02)
lspci -knn: Subsystem: Dell Device [1028:0228]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) 
HD Audio Controller [8086:284b] (rev 02)
lspci -knn: Subsystem: Dell Device [1028:0228]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 1 [8086:283f] (rev 02)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 2 [8086:2841] (rev 02)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) 
PCI Express Port 4 [8086:2845] (rev 02)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #1 [8086:2830] (rev 02)
lspci -knn: Subsystem: Dell Device [1028:0228]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1d.1 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #2 [8086:2831] (rev 02)
lspci -knn: Subsystem: Dell Device [1028:0228]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1d.2 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB UHCI Controller #3 [8086:2832] (rev 02)
lspci -knn: Subsystem: Dell Device [1028:0228]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1d.7 USB controller [0c03]: Intel Corporation 82801H (ICH8 
Family) USB2 EHCI Controller #1 [8086:2836] (rev 02)
lspci -knn: Subsystem: Dell Device [1028:0228]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI 
Bridge [8086:2448] (rev f2)
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801HM (ICH8M) LPC 
Interface Controller [8086:2815] (rev 02)
lspci -knn: Subsystem: Dell Device [1028:0228]
lspci -knn: 00:1f.1 IDE interface [0101]: Intel Corporation 82801HM/HEM 
(ICH8M/ICH8M-E) IDE Controller [8086:2850] (rev 

Bug#780857: installation-report: successful installation

[Andrey Skvortsov]

Package: installation-reports
Version: 2.58
Severity: normal

Dear Maintainer,

-- Package-specific info:

Boot method: network
Image version: netinst amd64. daily snapshot 2015-03-20
Date: Date and time of the install

Machine: qemu virtual machine run on Debian Wheezy as a host
Partitions: df -Tl will do; the raw partition table is preferred


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [ ]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:


-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=8 (jessie) - installer build 20150320-00:04
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux debian7 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC 
[Natoma] [8086:1237] (rev 02)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA 
[Natoma/Triton II] [8086:7000]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE 
[Natoma/Triton II] [8086:7010]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: Kernel driver in use: ata_piix
lspci -knn: 00:01.2 USB controller [0c03]: Intel Corporation 82371SB PIIX3 USB 
[Natoma/Triton II] [8086:7020] (rev 01)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI 
[8086:7113] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Red Hat, Inc. QXL 
paravirtual graphic card [1b36:0100] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:03.0 Ethernet controller [0200]: Red Hat, Inc Virtio network 
device [1af4:1000]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:0001]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: 00:04.0 Audio device [0403]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller 
[8086:2668] (rev 01)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:05.0 Communication controller [0780]: Red Hat, Inc Virtio 
console [1af4:1003]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:0003]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: 00:06.0 SCSI storage controller [0100]: Red Hat, Inc Virtio block 
device [1af4:1001]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:0002]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: 00:07.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory 
balloon [1af4:1002]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:0005]
lspci -knn: Kernel driver in use: virtio-pci
usb-list: 
usb-list: Bus 01 Device 01: UHCI Host Controller [1d6b:0001]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 3.16.0-4-amd64 uhci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 01 Device 02: QEMU USB Tablet [0627:0001]
usb-list:Level 01 Parent 01 Port 00  Class 00(ifc ) Subclass 00 Protocol 00
usb-list:Manufacturer: QEMU 1.1.2
usb-list:Interface 00: Class 03(HID  ) Subclass 00 Protocol 02 Driver usbhid
lsmod: Module  Size  Used by
lsmod: ufs73486  0 
lsmod: qnx4   13036  0 
lsmod: hfsplus97295  0 
lsmod: hfs53845  0 
lsmod: minix  31387  0 
lsmod: msdos  17046  0 
lsmod: ntfs  194605  0 
lsmod: usblp  17274  0 
lsmod: fuse   83350  0 
lsmod: battery13356  0 
lsmod: dm_mod 89373  0 
lsmod: md_mod107672  0 
lsmod: xfs   779874  0 
lsmod: libcrc32c  12426  1 xfs
lsmod: jfs   172859  0 
lsmod: crc32c_generic 12656  2 
lsmod: btrfs   

Bug#780532: lbdb-fetchaddr cuts too less characters if multi-byte UTF-8 symbols are used

[Andrey Skvortsov]

Package: lbdb
Version: 0.39
Severity: normal
Tags: patch

Dear Maintainer,

I observe following problem. The lbdb-fetchaddr cuts too less characters from
original input names, if UTF-8 is used and input name contains Cyrillic
symbols.
The problem is that lbdb-fetchaddr cuts all personal names that are longer that
30 bytes.
I use UTF-8 as default encoding for outgoing mails. This is multi-byte encoding
and 30 bytes in UTF-8 is 15
Cyrillic symbols (2-byte per symbol).

15 symbols for name is too short. Almost always we use patronymic name in our
personal name especially
in official work/business mails and that makes personal
names even longer. My own full name is 25 Cyrillic characters long (50
bytes) and I don't have the longest personal name.
From the technical point of view I don't see any technical problem to extend
this limitation.

The attached patch increases max name length to 70 bytes.



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

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

Versions of packages lbdb depends on:
ii  libc62.19-15
ii  libvformat0  1.13-10
ii  perl 5.20.2-2

lbdb recommends no packages.

Versions of packages lbdb suggests:
pn  abooknone
ii  finger   0.17-15
ii  libauthen-sasl-perl  2.1600-1
pn  libnet-ldap-perl none
pn  libpalm-perl none
ii  mutt 1.5.23-3
ii  procmail 3.22-24

-- no debconf information
From 9314aab41a0de0286426d5a3f56fa14bebd71dbc Mon Sep 17 00:00:00 2001
From: Andrey Skvortsov andrej.skvort...@gmail.com
Date: Mon, 22 Dec 2014 17:08:48 +0300
Subject: [PATCH] fetchaddr.c: replace magic numbers that handle maximal length
 of personal name with a macro definition and extend personal name width.

---
 fetchaddr.c | 8 +---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/fetchaddr.c b/fetchaddr.c
index 46235d5..16f3cb2 100644
--- a/fetchaddr.c
+++ b/fetchaddr.c
@@ -32,7 +32,8 @@
 #include rfc2047.h
 
 #define MAXHDRS 21
-
+ /* max personal length in bytes */
+#define MAX_PERSONAL_LENGTH 70
 struct header
 {
   char *tag;
@@ -88,8 +88,10 @@ int writeout(struct header *h, const char *datefmt,
 }
 if(!p-group  p-mailbox  *p-mailbox  p-personal)
 {
-  if(p-personal  strlen(p-personal)  30)
-	strcpy(p-personal + 27, ...);
+  const char end[] = ...;
+
+  if(p-personal  strlen(p-personal)  MAX_PERSONAL_LENGTH)
+	strcpy(p-personal + MAX_PERSONAL_LENGTH - strlen(end), end);
 
   if ((c=strchr(p-mailbox,'@')))
 	for(c++; *c; c++)

Bug#779022: aqemu: parallel port redirection sets wrong command line option

[Andrey Skvortsov]

Package: aqemu
Version: 0.8.2-2+b1
Severity: normal
Tags: patch

Dear Maintainer,

if LPT parallel option is selected, then qemu fails to start, because wrong
command line option is set.
AQemu sets '-Parallel', but the right option for that is '-parallel' according
to the qemu-system's manual page.
Screenshot with error message and patch with a fix are attached.



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

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

Versions of packages aqemu depends on:
ii  libc6   2.19-13
ii  libgcc1 1:4.9.1-19
ii  libqt4-network  4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-test 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-xml  4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtcore4  4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtgui4   4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libstdc++6  4.9.1-19
ii  libvncclient0   0.9.9+dfsg-6.1
ii  qemu1:2.1+dfsg-11

Versions of packages aqemu recommends:
ii  qemu-kvm  1:2.1+dfsg-11

aqemu suggests no packages.
diff --git a/VM.cpp b/VM.cpp
index 04c6173..fb45b3b 100644
--- a/VM.cpp
+++ b/VM.cpp
@@ -6084,7 +6084,7 @@ QStringList Virtual_Machine::Build_QEMU_Args()
 	{
 		if( Parallel_Ports[ix].Get_Port_Redirection() == VM::PR_Default ) continue;
 		
-		Args  -Parallel;
+		Args  -parallel;
 		
 		switch( Parallel_Ports[ix].Get_Port_Redirection() )
 		{

Bug#772845: freetuxtv: package keeps crushing at startup screen

[andrey skvortsov]

Package: freetuxtv
Version: 0.6.6~dfsg1-1
Followup-For: Bug #772845

Dear Maintainer,

the same here. As I start freetuxtv it syncronize all tv/radio channels and
crashes after that
with segmentation fault. It's known bug and it seems to be fixed in upstream
(https://code.google.com/p/freetuxtv/issues/detail?id=189). In Jessie freetuxtv
is not usable at all now.

Here is log:

freetuxtv
[FreetuxTV]INFO   : Compiled with GTK3
[FreetuxTV]INFO   : Compiled with LibVLC version 2.2.0
[FreetuxTV]INFO   : Compiled with libnotify version 0.7.6
[FreetuxTV]INFO   : Loading FreetuxTV 0.6.6
[FreetuxTV]INFO   : Loading user interface from path
/usr/share/freetuxtv/ui
[FreetuxTV]INFO   : Initializing user interface
[GMMKeys]  INFO   : Initialize
[GMMKeys]  INFO   : Activating media player keys
[GMMKeys]  CRITICAL   : Unable to grab media player keys: Could not get
owner of name 'org.gnome.SettingsDaemon': no such name
[FreetuxTV]INFO   : Using user configuration dir:
/home/andrey/.config/FreetuxTV
[FreetuxTV]INFO   : DBSync open database
[DBEvolution]  INFO   : Starting database evolution
[DBEvolution]  INFO   : Current database version is 0.6.0.2
[FreetuxTV]INFO   : DBSync close database
[FreetuxTV]INFO   : Loading config file
/home/andrey/.config/FreetuxTV/config.ini
[FreetuxTV]INFO   : Cannot load config file
[FreetuxTV]INFO   : Creating media player widget
[FreetuxTV]INFO   : Initializing LibVLC instance
[LibVLC-Gtk]   INFO   : Using instance vlc with 3 options [--no-xlib
--ignore-config --no-video-title-show]
[FreetuxTV]INFO   : DBSync open database
[FreetuxTV]MESSAGE: Synchronizing the tv channels list
[FreetuxTV]INFO   : Loading the list of channels
[FreetuxTV]INFO   : Loading the list of recordings
[FreetuxTV]INFO   : DBSync close database
[FreetuxTV]INFO   : Showing the main window, hide splashscreen
[FreetuxTV]INFO   : Loading GtkBuilder object dialogaddgroup from
/usr/share/freetuxtv/ui/addchannelsgroups.glade

** (freetuxtv:21559): CRITICAL **: gtk_builder_window_get_top_window: assertion
'GTK_IS_WINDOW(pObject)' failed

(freetuxtv:21559): Gtk-CRITICAL **: gtk_window_set_transient_for: assertion
'GTK_IS_WINDOW (window)' failed

(freetuxtv:21559): Gtk-CRITICAL **: gtk_window_set_position: assertion
'GTK_IS_WINDOW (window)' failed

(freetuxtv:21559): Gtk-CRITICAL **: gtk_tree_view_get_selection: assertion
'GTK_IS_TREE_VIEW (tree_view)' failed

(freetuxtv:21559): Gtk-CRITICAL **: gtk_tree_selection_set_mode: assertion
'GTK_IS_TREE_SELECTION (selection)' failed

(freetuxtv:21559): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(freetuxtv:21559): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion
'G_TYPE_CHECK_INSTANCE (instance)' failed

(freetuxtv:21559): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(freetuxtv:21559): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion
'G_TYPE_CHECK_INSTANCE (instance)' failed

(freetuxtv:21559): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(freetuxtv:21559): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion
'G_TYPE_CHECK_INSTANCE (instance)' failed

(freetuxtv:21559): Gtk-CRITICAL **: gtk_tree_store_clear: assertion
'GTK_IS_TREE_STORE (tree_store)' failed
Segmentation fault



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

Kernel: Linux 3.19.0-rc7-150201- (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: systemd (via /run/systemd/system)

Versions of packages freetuxtv depends on:
ii  libatk1.0-0  2.14.0-1
ii  libc62.19-13
ii  libcairo-gobject21.14.0-2.1
ii  libcairo21.14.0-2.1
ii  libcurl3 7.38.0-4
ii  libdbus-1-3  1.8.12-3
ii  libdbus-glib-1-2 0.102-1
ii  libgdk-pixbuf2.0-0   2.31.1-2+b1
ii  libglib2.0-0 2.42.1-1
ii  libgtk-3-0   3.14.5-1
ii  libnotify4   0.7.6-2
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libsqlite3-0 3.8.7.1-1
ii  libvlc5  2.2.0~rc2-2
ii  vlc  2.2.0~rc2-2

freetuxtv recommends no packages.

freetuxtv suggests no packages.

-- debconf-show failed


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

Bug#778666: gnome-themes-extras: recommends package missing in the archive (gnome-themes-more)

[Andrey Skvortsov]

Package: gnome-themes-extras
Version: 2.22.0-3
Severity: minor

Dear Maintainer,

As gnome-themes-extras was installed on jessie, I noticed that gnome-themes-
extras recommends package that is not present in the archive (gnome-themes-
more). The same is for wheezy. Gnome-themes-more exists only for squeeze.
Maybe it would be useful to remove it from recommendations, if it's not
supported anymore.



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

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

Versions of packages gnome-themes-extras depends on:
ii  gtk2-engines 1:2.20.2-2
ii  librsvg2-common  2.36.1-2

Versions of packages gnome-themes-extras recommends:
pn  gnome-themes-more  none

gnome-themes-extras 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#778569: gnome-session-flashback: switching between different keyboard layouts does not work

[Andrey Skvortsov]

Package: gnome-session-flashback
Version: 3.8.1-7
Severity: important

Dear Maintainer,

On clean Jessie installation in GNOME flashback session I setup two keyboard
layouts (ru and us).
But layout switching does not work neither with default shortcut (Alt-Shift,
Super-Space) nor with others (Menu, Ctrl-Shift). I've not checked all possible
keyboard shortcuts settings. Layout switching is broken only in flashback
session in normal gnome session layout can be switched as expected.

As a temporary solution I installed gxneur and created script, that is started
automatically as user logs in.

#!/bin/sh
setxkbmap -option grp:switch,grp:alt_shift_toggle,grp_led:scroll us,ru
gxneur 






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

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

Versions of packages gnome-session-flashback depends on:
ii  gnome-flashback 3.10.0-3
ii  gnome-panel 3.8.1-7+b1
ii  gnome-screensaver   3.6.1-4
ii  gnome-session-bin   3.14.0-2
ii  gnome-session-common3.14.0-2
ii  gnome-settings-daemon   3.14.2-2
ii  mate-notification-daemon [notification-daemon]  1.8.1-2
ii  mate-polkit [policykit-1-gnome] 1.8.0+dfsg1-4
ii  metacity1:3.14.3-1
ii  nautilus3.14.1-2
ii  notification-daemon 0.7.6-2
ii  policykit-1-gnome   0.105-2

Versions of packages gnome-session-flashback recommends:
ii  gnome-power-manager  3.14.1-1

Versions of packages gnome-session-flashback suggests:
ii  desktop-base  8.0.2
ii  gnome-keyring 3.14.0-1+b1
ii  gnome-user-guide  3.14.1-1

-- debconf-show failed


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