Bug#1010303: networkd-dispatcher: CVE-2022-29799 CVE-2022-29800

[Clayton Craft]

On Tue, 03 May 2022 18:22:37 +0200 Julian Andres Klode  wrote:
> So the way this usually goes is that distros also get notified, and
> fixes are held back until a date (well hour really) coordinated by the
> distros so everyone can release fixes at the same time, by way of
> contacting the distros mailing list 
> (https://oss-security.openwall.org/wiki/mailing-lists/distros) or
> individual email.

I see, thank you for explaining. This is my first CVE rodeo.

> Given that you are just working on this in your spare time and had not
> had to deal with a CVE, I think MS should have at least helped ensure that
> this is being communicated properly.

That makes sense. Let me know if there's anything I can do to help.

-Clayton


signature.asc
Description: PGP signature

Bug#1010303: networkd-dispatcher: CVE-2022-29799 CVE-2022-29800

[Clayton Craft]

Hi folks,

> what is the story there? I don't believe any of those MS reports
> are actually (important) security issues,

The issue is basically that microsoft and/or their customers are allowing
arbitrary code execution under a system user account (the same one that normally
runs systemd-networkd). I can't speak for Debian, but other distros I've seen
restrict who can "own" the systemd-networkd service name on the system dbus
session to that user, so obviously if you allow that user to run arbitrary code
then you're going to allow anything to bypass those restrictions.

That's important in this context because networkd-dispatcher derives paths to
scripts it runs based on the messages it receives on dbus for the
systemd-networkd service. So if something else can "own" that name on the bus
then it can (before the sanitation patch in the latest version) get
networkd-dispatcher to run things located elsewhere.

I should have been sanitizing input from dbus, which networkd-dispatcher does
now. But again, in every other configuration I've seen, the user who is sending
messages under that service is a dedicated system user who is only running
systemd-networkd.

> also why was this being disclosed publicly rather than responsibly?

It was disclosed responsibly, as far as I understand the "responsible
disclosure" process to be. They contacted me privately about a month ago about
it, giving me enough time to come up with something to address it (I'm not paid
to work on this :D) They also gave me a script to reproduce it shortly after
contacting me, which (after a lot of effort) I was able to trigger it a couple
of times in a VM running Arch Linux, but only after doing things that I
shouldn't have been doing in the "real world"
(e.g. sudo -u systemd-network ./foo)

> The fixes for the alleged permission issue also only handles one
> parent directory and classic permissions, but not any other
> (grand)parents or ACLs.

Ya, I'll admit that I'm not entirely sure if that particular change is all that
useful... and I believe that it's up to distros to configure ACLs on the system.
I would welcome any improvements to attempt to verify ACLs.

So to recap:

1) if you don't re-use the systemd-network user (or whatever user your distro
restricts the networkd dbus service name to) for running other things besides
systemd-networkd, then this shouldn't be a problem. 

2) If you do use the systemd-network user to run whatever, then
networkd-dispatcher will now sanitize messages from dbus from the networkd dbus
"service" (regardless of who/what has managed to own the name on the bus), so
that it won't run things. This was shown by Microsoft to completely mitigate the
issue.

3) system admins can still create symlinks to scripts outside of the config
directories (which should be owned by root) the app searches, so it's still
possible for system admins to footgun themselves, but networkd-dispatcher will
at least *try* a little bit better now to prevent running things that are
writeable by non-root users. 

-Clayton

On Tue, 03 May 2022 14:12:14 +0200 Julian Andres Klode  wrote:
> Hi Clayton (CC),
> 
> what is the story there? I don't believe any of those MS reports
> are actually (important) security issues, also why was this being
> disclosed publicly rather than responsibly?
> 
> The fixes for the alleged permission issue also only handles one
> parent directory and classic permissions, but not any other
> (grand)parents or ACLs.
> 
> On Tue, May 03, 2022 at 01:21:12PM +0200, Julian Andres Klode wrote:
> > On Thu, Apr 28, 2022 at 01:53:58PM +0200, Salvatore Bonaccorso wrote:
> > > Source: networkd-dispatcher
> > > Version: 2.1-2
> > > Severity: grave
> > > Tags: security upstream
> > > X-Debbugs-Cc: car...@debian.org, Debian Security Team 
> > > 
> > > 
> > > Hi,
> > > 
> > > The following vulnerabilities were published for networkd-dispatcher.
> > > 
> > > CVE-2022-29799[0] and CVE-2022-29800[1].
> > > 
> > > If you fix the vulnerabilities please also make sure to include the
> > > CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.
> > 
> > I do not believe these are vulnerabilities. Microsoft claims a
> > vulnerability exists if there is vulnerable code running under
> > the systemd-network user, and claims that apt and epmd run under
> > such user, but neither has communicated how those processes are
> > vulnerable, nor why they would run under that user.
> > 
> > It's likely that their tool is a confused deputy, running on a
> > system with broken containers where container _apt and epmd
> > users are mapped to the same UID as the host systemd-network
> > (which still would not give them access 

Bug#931208: Acknowledgement (ecryptfs-utils: Has ecryptfs lost sync with kernel?)

[Clayton]

It seems this error happens when one attempts to use the ecryptfs
utilities while logged in over an SSH session. Using a terminal right on
the machine, things work as expected. If the SSH behavior is expected
(should it be documented?) then this bug report could be closed.

Bug#931208: ecryptfs-utils: Has ecryptfs lost sync with kernel?

[clayton]

Package: ecryptfs-utils
Version: 111-4
Severity: important

Happening today on a mixed testing / unstable machine.

# mount -t ecryptfs test test
Unable to link the KEY_SPEC_USER_KEYRING into the KEY_SPEC_SESSION_KEYRING; 
there is something wrong with your kernel keyring. 
Did you build key retention support into your kernel?

This works with the same version of Debian, as virtual machine in QubesOS using 
a Qubes kernel.

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (990, 'testing'), (700, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages ecryptfs-utils depends on:
ii  gettext-base0.19.8.1-9
ii  keyutils1.6-6
ii  libassuan0  2.5.2-1
ii  libc6   2.28-10
ii  libecryptfs1111-4
ii  libgpg-error0   1.35-1
ii  libgpgme11  1.12.0-6
ii  libkeyutils11.6-6
ii  libpam-runtime  1.3.1-5
ii  libpam0g1.3.1-5
ii  libtspi10.3.14+fixed1-1

ecryptfs-utils recommends no packages.

Versions of packages ecryptfs-utils suggests:
ii  cryptsetup  2:2.1.0-5

-- no debconf information

Bug#913948: segfault, apparently not always at the same location?

[Clayton]

> Sounds a lot like #913573 . Could you try upgrading libasound2 and
> libasound2-plugins?

Seems so As a matter of fact, the new libasound2 & co. landed in
testing as of today, so a simple update later, and sound is working
again. Thanks!

Clayton

Bug#913948: segfault, apparently not always at the same location?

[clayton]

Package: pulseaudio
Version: 12.2-2
Severity: important

Happens every time since a recent upgrade:

$ pulseaudio --start
E: [pulseaudio] main.c: Daemon startup failed.

syslog:
Nov 17 19:49:16 t410 kernel: [ 5309.938318] pulseaudio[9741]: segfault at 50 ip 
0050 sp 7ffca06f4948 error 14 in pulseaudio[561dc906c000+5000]
Nov 17 19:49:16 t410 kernel: [ 5309.938324] Code: Bad RIP value.
   
Nov 17 19:51:30 t410 pulseaudio[9811]: Stale PID file, overwriting. 
   
Nov 17 19:52:18 t410 pulseaudio[9816]: Stale PID file, overwriting. 
   
Nov 17 19:52:18 t410 kernel: [ 5491.725943] pulseaudio[9816]: segfault at 21 ip 
7fc276cb091a sp 7fff65097450 error 6 in 
libasound.so.2.0.0[7fc276ca3000+8f000]
Nov 17 19:52:18 t410 kernel: [ 5491.725950] Code: 55 53 48 83 ec 08 48 8b 35 13 
47 0c 00 48
85 ff 0f 84 0d 01 00 00 48 8b 57 20 48 8b 4f 28 48 89 fb 31 ed 48 8d 05 f6 46 
0c 00 <48> 89
11 48 89 4a 08 48 39 c6 74 05 48 39 00 74 75 8b 03 85 c0 74

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


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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 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 pulseaudio depends on:
ii  adduser  3.118
ii  libasound2   1.1.7-1
ii  libasound2-plugins   1.1.7-2
ii  libc62.27-8
ii  libcap2  1:2.25-1.2
ii  libdbus-1-3  1.12.10-1
ii  libgcc1  1:8.2.0-9
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-6
ii  liborc-0.4-0 1:0.4.28-3
ii  libpulse012.2-2
ii  libsm6   2:1.2.2-1+b3
ii  libsndfile1  1.0.28-4
ii  libsoxr0 0.1.2-3
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   8.2.0-9
ii  libsystemd0  239-11
ii  libtdb1  1.3.16-2
ii  libudev1 239-11
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.7-1
ii  libx11-xcb1  2:1.6.7-1
ii  libxcb1  1.13.1-1
ii  libxtst6 2:1.2.3-1
ii  lsb-base 9.20170808
ii  pulseaudio-utils 12.2-2

Versions of packages pulseaudio recommends:
ii  dbus-user-session  1.12.10-1
ii  libpam-systemd 239-11
ii  rtkit  0.11-6

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  3.0-4
pn  pavumeter
ii  udev 239-11

-- no debconf information


client.conf
Description: /etc/magic


daemon.conf
Description: /etc/magic


default.pa
Description: /etc/magic


system.pa
Description: /etc/magic


bug-pulseaudio-pactl_list.YJKCKe
Description: /etc/magic


bug-pulseaudio-pactl_info.NWqJLV
Description: /etc/magic

Bug#893368: fastboot too old

[Clayton]

On Tue, 6 Nov 2018 04:09:43 +0800
殷啟聰 | Kai-Chung Yan  wrote:

> > /nexus5x-bullhead-install/bullhead-opm3.171019.016$ ./flash-all.sh 
> > fastboot too old
> > 
> > ie. the latest Android Google Nexus factory images cannot be
> > flashed.  
> 
> Thanks for the report. Now that `fastboot` has been updated to Oreo
> release, is it still too old? Please let me know if you find the
> problem fixed.

As a matter of fact, I flashed another Nexus (angler) phone just a
couple of days ago, and although there were issues, I do not believe
fastboot was the problem, there was certainly no "fastboot too old"
message. You can go ahead and close this one.

Thanks for following up,
Clayton

Bug#903960: gnucash: segfaults in QubesOS VM

[Clayton]

> I've forwarded your report to 
> 
>   https://bugs.gnucash.org/show_bug.cgi?id=796771

Good news. They have marked this bug as a duplicate of

https://bugs.gnucash.org/show_bug.cgi?id=796733

which has a workaround. If I start Gnucash in Qubes as follows:

$ GTK_IM_MODULE=ibus gnucash

the crash goes away, and now the delete and backspace keys also work.
This saves me a lot of headache. I was otherwise looking at an
immediate migration to ledger, as there does not look like there will
be a fix anytime soon.

Weird that ibus / input method usage b0rks Gnucash on QubesOS VM but not
on my bare metal install. Some kind of X interaction going on there, I
bet.

If you are at Debconf, so am I.

Bug#903960: gnucash: segfaults in QubesOS VM

[Clayton]

> Thanks. This particular backtrace lacks some symbols so I can't quite
> make much sense of it... I reckon you might need to install some
> -dbgsym packages:
> 
>   * gnucash-dbgsym
>   * libgtk-3-0-dbgsym
> 
> and others. See more at
>   https://wiki.debian.org/AutomaticDebugPackages

The last one had gnucash-dbgsym.

This attempt has

gnucash-dbgsym
guile-2.2-libs-dbgsym:amd64
libgtk-3-0-dbgsym:amd64

For some reason when I installed guile-2.2-libs-dbgsym I was forced to
upgrade libguile to the unstable version. Still segfaults though, does
this backtrace contain enough info?
(gdb) run
Starting program: /usr/bin/gnucash 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe07bf700 (LWP 955)]
[New Thread 0x7fffdd7e8700 (LWP 956)]
[New Thread 0x7fffdcfe7700 (LWP 957)]
[New Thread 0x7fffd7fff700 (LWP 958)]
[New Thread 0x7fffd6ffe700 (LWP 959)]
[New Thread 0x7fffd5e7a700 (LWP 960)]
Found Finance::Quote version 1.47
[New Thread 0x7fffd4a42700 (LWP 966)]
[Thread 0x7fffd4a42700 (LWP 966) exited]

Thread 1 "gnucash" received signal SIGSEGV, Segmentation fault.
0x76973202 in gdk_window_has_impl (window=) at 
../../../../gdk/gdkwindow.c:677
677 ../../../../gdk/gdkwindow.c: No such file or directory.
(gdb) bt
#0  0x76973202 in gdk_window_has_impl (window=) at 
../../../../gdk/gdkwindow.c:677
#1  _gdk_window_has_impl (window=window@entry=0x0) at 
../../../../gdk/gdkwindow.c:678
#2  0x769a947e in gdk_x11_window_get_xid (window=0x0) at 
../../../../../gdk/x11/gdkwindow-x11.c:5566
#3  0x7fffd403e16b in gtk_im_context_xim_filter_keypress 
(context=0x555dc800, event=0x59362180) at 
../../../../../modules/input/gtkimcontextxim.c:673
#4  0x76e329f3 in gtk_im_multicontext_filter_keypress 
(context=0x58fddc60, event=0x59362180) at 
../../../../gtk/gtkimmulticontext.c:359
#5  0x77e6008b in gnucash_sheet_key_press_event (widget=0x568b4590, 
event=0x59362180) at ./gnucash/register/register-gnome/gnucash-sheet.c:1865
#6  0x76e52d57 in _gtk_marshal_BOOLEAN__BOXEDv (closure=0x555e5e40, 
return_value=0x7fffd270, instance=, args=, 
marshal_data=, n_params=, 
param_types=0x555e5720) at ../../../../gtk/gtkmarshalers.c:129
#7  0x755880b0 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x755a30ad in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x755a3e0f in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x76f99ed4 in gtk_widget_event_internal 
(widget=widget@entry=0x568b4590, event=event@entry=0x59362180) at 
../../../../gtk/gtkwidget.c:7744
#11 0x76f9bf4a in gtk_widget_event (widget=widget@entry=0x568b4590, 
event=event@entry=0x59362180) at ../../../../gtk/gtkwidget.c:7314
#12 0x76fba28b in gtk_window_propagate_key_event 
(window=window@entry=0x559ce310, event=event@entry=0x59362180) at 
../../../../gtk/gtkwindow.c:8161
#13 0x76fbdc7b in gtk_window_key_press_event (widget=0x559ce310, 
event=0x59362180) at ../../../../gtk/gtkwindow.c:8194
#14 0x76e52d57 in _gtk_marshal_BOOLEAN__BOXEDv (closure=0x555e5e40, 
return_value=0x7fffd670, instance=, args=, 
marshal_data=, n_params=, 
param_types=0x555e5720) at ../../../../gtk/gtkmarshalers.c:129
#15 0x755881a6 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x755a30ad in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x755a3e0f in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x76f99ed4 in gtk_widget_event_internal (widget=0x559ce310, 
event=0x59362180) at ../../../../gtk/gtkwidget.c:7744
#19 0x76e4fd9f in propagate_event (widget=0x559ce310, 
event=0x59362180, captured=, topmost=0x0) at 
../../../../gtk/gtkmain.c:2685
#20 0x76e51da8 in gtk_main_do_event (event=) at 
../../../../gtk/gtkmain.c:1915
#21 0x76963785 in _gdk_event_emit (event=event@entry=0x59362180) at 
../../../../gdk/gdkevents.c:73
#22 0x76993fa2 in gdk_event_source_dispatch (source=, 
callback=, user_data=) at 
../../../../../gdk/x11/gdkeventsource.c:367
#23 0x77574287 in g_main_context_dispatch () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x775744c0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x775747d2 in g_main_loop_run () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x76e50e85 in gtk_main () at ../../../../gtk/gtkmain.c:1323
#27 0x717d504d in gnc_ui_start_event_loop () at 
./gnucash/gnome-utils/gnc-gnome-utils.c:651
#28 0x812e in inner_main (closure=, argc=, argv=) at ./gnucash/gnucash-bin.c:674
#29 0x77b0f2ed in invoke_main_func (body_data=0x7fffdf50) at 
init.c:340
#30 

Bug#903960: gnucash: segfaults in QubesOS VM

[Clayton]

> Would you be able to attach a backtrace please

Attached, is this helpful?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe07bf700 (LWP 970)]
[New Thread 0x7fffdd7e8700 (LWP 971)]
[New Thread 0x7fffdcfe7700 (LWP 972)]
[New Thread 0x7fffd7fff700 (LWP 973)]
[New Thread 0x7fffd6ffe700 (LWP 974)]
[New Thread 0x7fffd5e5d700 (LWP 975)]
Found Finance::Quote version 1.47
[New Thread 0x7fffd4a25700 (LWP 977)]
[Thread 0x7fffd4a25700 (LWP 977) exited]

Thread 1 "gnucash" received signal SIGSEGV, Segmentation fault.
0x76973202 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
(gdb) bt
#0  0x76973202 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#1  0x769a947e in gdk_x11_window_get_xid () from 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#2  0x7fffd402116b in ?? () from 
/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-xim.so
#3  0x76e329f3 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#4  0x77e6008b in gnucash_sheet_key_press_event (widget=0x5689e460, 
event=0x59280510) at ./gnucash/register/register-gnome/gnucash-sheet.c:1865
#5  0x76e52d57 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#6  0x755880b0 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x755a30ad in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x755a3e0f in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x76f99ed4 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#10 0x76fba28b in gtk_window_propagate_key_event () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#11 0x76fbdc7b in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#12 0x76e52d57 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#13 0x755881a6 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x755a30ad in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x755a3e0f in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x76f99ed4 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#17 0x76e4fd9f in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#18 0x76e51da8 in gtk_main_do_event () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#19 0x76963785 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#20 0x76993fa2 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#21 0x77574287 in g_main_context_dispatch () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x775744c0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x775747d2 in g_main_loop_run () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x76e50e85 in gtk_main () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#25 0x717d504d in gnc_ui_start_event_loop () at 
./gnucash/gnome-utils/gnc-gnome-utils.c:651
#26 0x812e in inner_main (closure=, argc=, argv=) at ./gnucash/gnucash-bin.c:674
#27 0x77b0f2ed in ?? () from /usr/lib/x86_64-linux-gnu/libguile-2.2.so.1
#28 0x77af1b8a in ?? () from /usr/lib/x86_64-linux-gnu/libguile-2.2.so.1
#29 0x77b72a3f in ?? () from /usr/lib/x86_64-linux-gnu/libguile-2.2.so.1
#30 0x77b75277 in scm_call_n () from 
/usr/lib/x86_64-linux-gnu/libguile-2.2.so.1
#31 0x77b63ee2 in ?? () from /usr/lib/x86_64-linux-gnu/libguile-2.2.so.1
#32 0x77af2170 in ?? () from /usr/lib/x86_64-linux-gnu/libguile-2.2.so.1
#33 0x77af2205 in scm_c_with_continuation_barrier () from 
/usr/lib/x86_64-linux-gnu/libguile-2.2.so.1
#34 0x77b62b2c in ?? () from /usr/lib/x86_64-linux-gnu/libguile-2.2.so.1
#35 0x778594e8 in GC_call_with_stack_base () from 
/usr/lib/x86_64-linux-gnu/libgc.so.1
#36 0x77b62e48 in scm_with_guile () from 
/usr/lib/x86_64-linux-gnu/libguile-2.2.so.1
#37 0x77b0f482 in scm_boot_guile () from 
/usr/lib/x86_64-linux-gnu/libguile-2.2.so.1
#38 0x7a30 in main (argc=, argv=) at 
./gnucash/gnucash-bin.c:821
(gdb) 

Bug#903960: gnucash: segfaults in QubesOS VM

[clayton]

Package: gnucash
Version: 1:3.2-1
Severity: important

Given two Debian testing OSes, up-to-date as of today:

* while being quirky, gnucash basically works on bare-metal Debian using MATE 
desktop

* in a Debian VM under QubesOS, using XFCE desktop, every time I place the 
cursor in a register and
  hit the keyboard to type something, there is an immediate segfault.

Even with --debug turned on I am seeing no interesting errors.
This is new behavior as of version 3.2, this worked just days ago under 2.x.

Interestingly, there has for a long time (always?) been some weirdness about 
data
entry in gnucash under QubesOS. IIRC, in the past the Delete and Backspace keys 
did not work.
To accomplish a delete I had to highlight and then us Ctrl-x, or highlight and 
then paste
(Ctrl-v). This may very well be just a more severe manifestation of the same 
underlying issue.

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

Kernel: Linux 4.14.41-1.pvops.qubes.x86_64 (SMP w/2 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)

Versions of packages gnucash depends on:
ii  gnucash-common   1:3.2-1
ii  guile-2.22.2.3+1-3+b1
ii  guile-2.2-libs   2.2.3+1-3+b1
ii  libaqbanking35   5.7.8-1
ii  libaqbanking35-plugins   5.7.8-1
ii  libatk1.0-0  2.28.1-1
ii  libboost-date-time1.62.0 1.62.0+dfsg-6
ii  libboost-filesystem1.62.01.62.0+dfsg-6
ii  libboost-locale1.62.01.62.0+dfsg-6
ii  libboost-regex1.62.0 1.62.0+dfsg-6
ii  libboost-system1.62.01.62.0+dfsg-6
ii  libc62.27-3
ii  libcairo-gobject21.15.10-3
ii  libcairo21.15.10-3
ii  libcrypt-ssleay-perl 0.73.06-1
ii  libdate-manip-perl   6.72-1
ii  libdbi1  0.9.0-5
ii  libfinance-quote-perl1.47-1
ii  libgc1c2 1:7.4.2-8.3
ii  libgcc1  1:8.1.0-10
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libglib2.0-0 2.56.1-2
ii  libgtk-3-0   3.22.30-2
ii  libgwenhywfar60  4.20.0-1
ii  libhtml-tableextract-perl2.15-1
ii  libhtml-tree-perl5.07-1
ii  libicu60 60.2-6
ii  libjavascriptcoregtk-4.0-18  2.20.3-1
ii  libktoblzcheck1v51.49-4
ii  libofx7  1:0.9.13-2
ii  libpango-1.0-0   1.42.1-2
ii  libpangocairo-1.0-0  1.42.1-2
ii  libsecret-1-00.18.6-1
ii  libsoup2.4-1 2.62.2-2
ii  libstdc++6   8.1.0-10
ii  libwebkit2gtk-4.0-37 2.20.3-1
ii  libwww-perl  6.34-1
ii  libxml2  2.9.4+dfsg1-7+b1
ii  libxslt1.1   1.1.32-2
ii  perl 5.26.2-6
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages gnucash recommends:
ii  gnucash-docs 3.2-1
ii  python3-gnucash  1:3.2-1
ii  yelp 3.28.1-1

Versions of packages gnucash suggests:
pn  libdbd-mysql
pn  libdbd-pgsql
pn  libdbd-sqlite3  

-- no debconf information

Bug#903047: Netinst image cannot load e1000e, ixgbe, igb eth. drivers

[Clayton Craft]

Quoting Cyril Brulebois (2018-07-07 15:07:08)
> Control: severity -1 normal
> 
> Hi,
> 
> Clayton Craft  (2018-07-05):
> > Package: installation-reports
> > Justification: Unable to install debian with netinst image on systems with 
> > these NICs
> > 
> > 
> > With the latest weekly Debian testing netinst image (06-25 and 07-02 
> > tested),
> 
> Please always include the full URL to the image you're reporting an
> issue against.

The image was found under here, but has since been removed:
https://cdimage.debian.org/cdimage/daily-builds/daily/

> 
> > the e1000e, ixgbe, and igb modules cannot load.
> > Attempting to do so generates this message in the kernel log:
> > 
> > Unknown symbol: refcount_inc (error 0)
> > 
> > The kernel on this image is reported as 4.16.0-2, and magic ver from
> > 'modinfo' reports the same version. Perhaps there's some other module
> > dependency that is not included in the image?
> 
> It's rather due to having an installer embedding the kernel at version
> 4.16.12-1 (current when that installer was built) while the debian-cd
> tooling included more recent kernel udebs (4.16.16-2, current when the
> installation image was built).

Well that's not confusing at all. /sarcasm

> 
> For reference, the exact kernel version can be seen using:
> 
> cat /proc/version
> 
> > Note that I did not try to load all ethernet drivers included in the
> > image, so it's possible that there are more drivers affected.
> > 
> > This issue makes it impossible to install Debian testing with the
> > netinst image on system with these ethernet adapters.
> 
> Please use released images instead?
> 
> This issue is common during development phases, and I'd usually advise
> running either a released image (esp. for this netinst usecase), or a
> d-i daily build (esp. for the netboot usecase). Please note the latter
> is only a d-i build against unstable, there's no matching installation
> image.

> 
> See the last announce:
>   https://www.debian.org/devel/debian-installer/News/2018/20180619
> 
> More on:
>   https://www.debian.org/devel/debian-installer/
> 
> 
> Awaiting feedback, but this is a good candidate for a not-a-bug closure.

What's the point in producing testing images if you're not willing to accept bug
reports against it? Would you rather bugs like this make it into a release
before being reported? If no one is supposed to use testing images, perhaps
consider renaming them to "DO NOT USE THIS IMAGE.iso"

> 
> 
> Cheers,
> -- 
> Cyril Brulebois (k...@debian.org)<https://debamax.com/>
> D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: signature

Bug#903047: not only Intel NICs affected..

[Clayton Craft]

I just discovered that other modules seem to be affected as well, for example
dm-mod does not load for the same reason, so it's not possible to partition with
anything that requires devicemapper...


signature.asc
Description: signature

Bug#903047: Netinst image cannot load e1000e, ixgbe, igb eth. drivers

[Clayton Craft]

Package: installation-reports
Version: testing
Severity: critical
Justification: Unable to install debian with netinst image on systems with these
NICs


With the latest weekly Debian testing netinst image (06-25 and 07-02 tested),
the e1000e, ixgbe, and igb modules cannot load.
Attempting to do so generates this message in the kernel log:

Unknown symbol: refcount_inc (error 0)

The kernel on this image is reported as 4.16.0-2, and magic ver from 'modinfo'
reports the same version. Perhaps there's some other module dependency that is
not included in the image?

Note that I did not try to load all ethernet drivers included in the image, so
it's possible that there are more drivers affected.

This issue makes it impossible to install Debian testing with the netinst image
on system with these ethernet adapters.



signature.asc
Description: signature

Bug#902600: hopenpgp-tools: hokey lint does not seem to do anything

[clayton]

Package: hopenpgp-tools
Version: 0.20.1-1
Severity: normal

I actually left it running over night.
No output, no error messages, no apparent activity.
And no return.
It looks like it is waiting for user input, minus the prompt.

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

Kernel: Linux 4.14.41-1.pvops.qubes.x86_64 (SMP w/2 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)

Versions of packages hopenpgp-tools depends on:
ii  libbz2-1.01.0.6-8.1
ii  libc6 2.27-3
ii  libffi6   3.2.1-8
ii  libgmp10  2:6.1.2+dfsg-3
ii  libncursesw6  6.1+20180210-4
ii  libnettle63.4-1
ii  libtinfo6 6.1+20180210-4
ii  libyaml-0-2   0.1.7-2
ii  zlib1g1:1.2.11.dfsg-1

hopenpgp-tools recommends no packages.

hopenpgp-tools suggests no packages.

-- no debconf information

Bug#895161: snapd: "broken"

[clayton]

Package: snapd
Version: 2.30-5+b1
Severity: important

Running Debian Testing, up to date.
No idea what provoked this exactly, but:

$ snap list
Name Version  Rev   Developer  Notes
core  4206  canonical  broken
skype 23skype  broken

$ snap run skype
error: cannot find installed snap "skype" at revision 23

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

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

Versions of packages snapd depends on:
ii  adduser  3.117
ii  apparmor 2.12-4
ii  ca-certificates  20170717
ii  gnupg2.2.5-1
ii  gnupg1   1.4.22-4
ii  libapparmor1 2.12-4
ii  libc62.27-3
ii  libcap2  1:2.25-1.2
ii  libseccomp2  2.3.1-2.1
ii  libudev1 238-4
ii  openssh-client   1:7.6p1-4
ii  squashfs-tools   1:4.3-6
ii  systemd  238-4

snapd recommends no packages.

snapd suggests no packages.

-- no debconf information

Bug#860950: steam: crashes on startup

[Clayton]

> I think it can probably be closed, then?

I would say so, yes.

> > "Linux
> > 
> > 32-bit Linux distributions are also no longer supported.
> > Please install a 64-bit Linux distribution to make use of the Steam
> > browser."
> > 
> > This sounds to me like it might be the end of the road for Steam on
> > 32-bit.  
> 
> Because the Steam client is a 32-bit binary with 32-bit dependencies,
> we have to distribute it as steam:i386 anyway - otherwise its
> dependencies on libraries like libGL wouldn't work correctly.
> 
> If the embedded web browser (a separate process, I think) doesn't work
> on a pure i386 system but only on an amd64 + i386 multiarch system,
> then that isn't really something we can fix. If I remember correctly
> from using Windows Steam under Wine at a time when Wine failed to run
> the embedded web browser, the Steam client can work enough without its
> web browser to log in (during startup) and install and run games that
> were bought by using a different web browser or a different machine,
> as long as those games are themselves 32-bit; so I think "works with
> severely degraded functionality" would be a reasonable summary?

That's fair ball, TBH I will probably not even try again as in browsing
through the games library I did not see too much that would likely run
well (if at all) on an ancient machine, so I have since scrounged a
64-bit machine with a bit more oomph for permanent use as game machine.

Thanks for staying on top of steam,
Clayton

Bug#860950: steam: crashes on startup

[Clayton]

Finally had a chance to do a clean install on a 32-bit machine, and got
farther than ever before on that platform, which suggests the original
cause of this bug report has been overcome by events. However, when
attempting to login, I found precisely this:

https://support.steampowered.com/kb_article.php?ref=4090-RTKZ-4347
"The Steam Browser is Disabled"

and to quote from further down on this page:

"Linux

32-bit Linux distributions are also no longer supported. Please
install a 64-bit Linux distribution to make use of the Steam
browser."

This sounds to me like it might be the end of the road for Steam on
32-bit.

Clayton

Bug#893368: fastboot too old

[clayton]

Package: fastboot
Version: 1:7.0.0+r33-2
Severity: important

/nexus5x-bullhead-install/bullhead-opm3.171019.016$ ./flash-all.sh 
fastboot too old

ie. the latest Android Google Nexus factory images cannot be flashed.

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

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

Versions of packages fastboot depends on:
ii  android-libadb 1:7.0.0+r33-2
ii  android-libbase1:7.0.0+r33-2
ii  android-libcutils  1:7.0.0+r33-2
ii  android-libext4-utils  7.0.0+r33-1
ii  android-libf2fs-utils  7.0.0+r33-1
ii  android-libsparse  1:7.0.0+r33-2
ii  android-libziparchive  1:7.0.0+r33-2
ii  libc6  2.27-2
ii  libgcc11:8-20180312-2
ii  libstdc++6 8-20180312-2

fastboot recommends no packages.

fastboot suggests no packages.

-- no debconf information

Bug#860950: steam: crashes on startup

[Clayton]

> > tar: Error is not recoverable: exiting now
> > find: ‘/home/user/.steam/ubuntu12_32/steam-runtime’: No such file or
> > directory  
> 
> This looks like an incomplete download.  Try backing up your
> ubuntu12_32 folder, and execute steam again.
> 
> If that works, the script will need to try to clean up after a failed
> download.

Yup, you nailed it, steam now works again on my 64-bit machine. I should
be able to retry a 32-bit machine when I get home next week.

Thanks

Bug#860950: steam: crashes on startup

[Clayton]

On Sat, 17 Feb 2018 17:08:08 -0500
Michael Gilbert <mgilb...@debian.org> wrote:

> Do you have an nvidia graphics card?  If so, could you try installing
> nvidia-driver-libs-i386?  If that works, this duplicates #839592.

Hi Mike,

I see there was a new steam came down recently, I am on the road and
don't have a 32-bit machine handy, so tried on this 64-bit laptop that
used to work. Not any longer, this is how running "steam" in a terminal
finishes:
 
[2018-02-18 12:49:56] Downloading update (274,863 of 274,863 KB)...
[2018-02-18 12:49:56] Download Complete.
[2018-02-18 12:49:56] uninstalled manifest found
in /home/user/.steam/package/steam_client_ubuntu12 (1). 
[2018-02-18 12:49:56] Extracting package... 
[2018-02-18 12:50:25] Installing update... 
[2018-02-18 12:50:27] Cleaning up... 
[2018-02-18 12:50:27] Update complete, launching... 
[2018-02-18 12:50:27] Shutdown tar: This does not look like a tar
archive xz: (stdin): File format not recognized
tar: Child returned status 1
tar: Error is not recoverable: exiting now
find: ‘/home/user/.steam/ubuntu12_32/steam-runtime’: No such file or
directory

which looks pretty similar to how the 32-bit machine used to fail,
minus the display errors. I won't be able to check the video card on
the 32-bit machine until I get home, but I very much doubt it is
nvidia. I generally have a policy of not buying things with nvidia
cards.

It is probably worth underlining that all of my desktop machines are
always running Debian Testing, not a Debian Stable to be seen anywhere
except in the occasional virtual machine, and I avoid customization
like the plague. Almost everything should be very standard, just as the
package maintainers intended.

Clayton

Bug#889527: puppet: Puppet master/agent on testing/buster fails with SSL errors

[Clayton]

Attached is the debug output that goes along with those SSL errors.
Debug: Applying settings catalog for sections main, agent, ssl
Debug: Caching environment 'production' (ttl = 0 sec)
Debug: Evicting cache entry for environment 'production'
Debug: Caching environment 'production' (ttl = 0 sec)
Debug: Evicting cache entry for environment 'production'
Debug: Caching environment 'production' (ttl = 0 sec)
Debug: Evicting cache entry for environment 'production'
Debug: Caching environment 'production' (ttl = 0 sec)
Debug: Using settings: adding file resource 'confdir': 
'File[/etc/puppet]{:path=>"/etc/puppet", :ensure=>:directory, 
:loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'codedir': 
'File[/etc/puppet/code]{:path=>"/etc/puppet/code", :ensure=>:directory, 
:loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Evicting cache entry for environment 'production'
Debug: Caching environment 'production' (ttl = 0 sec)
Debug: Failed to load library 'cfpropertylist' for feature 
'cfpropertylist'
Debug: Evicting cache entry for environment 'production'
Debug: Caching environment 'production' (ttl = 0 sec)
Debug: Evicting cache entry for environment 'production'
Debug: Caching environment 'production' (ttl = 0 sec)
Debug: Puppet::Type::User::ProviderDirectoryservice: file 
/usr/bin/uuidgen does not exist
Debug: Failed to load library 'ldap' for feature 'ldap'
Debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
Debug: Puppet::Type::User::ProviderPw: file pw does not exist
Debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not 
exist
Debug: /User[puppet]: Provider useradd does not support features 
libuser; not managing attribute forcelocal
Debug: Failed to load library 'cfpropertylist' for feature 
'cfpropertylist'
Debug: Puppet::Type::Group::ProviderDirectoryservice: file /usr/bin/dscl 
does not exist
Debug: Failed to load library 'ldap' for feature 'ldap'
Debug: Puppet::Type::Group::ProviderLdap: feature ldap is missing
Debug: Puppet::Type::Group::ProviderPw: file pw does not exist
Debug: /Group[puppet]: Provider groupadd does not support features 
libuser; not managing attribute forcelocal
Debug: Using settings: adding file resource 'vardir': 
'File[/var/cache/puppet]{:path=>"/var/cache/puppet", :owner=>"puppet", 
:group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, 
:backup=>false}'
Debug: Using settings: adding file resource 'logdir': 
'File[/var/log/puppet]{:path=>"/var/log/puppet", :mode=>"750", 
:owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'statedir': 
'File[/var/cache/puppet/state]{:path=>"/var/cache/puppet/state", :mode=>"1755", 
:ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'rundir': 
'File[/run/puppet]{:path=>"/run/puppet", :mode=>"755", :owner=>"puppet", 
:group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, 
:backup=>false}'
Debug: Using settings: adding file resource 'libdir': 
'File[/var/cache/puppet/lib]{:path=>"/var/cache/puppet/lib", 
:ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'hiera_config': 
'File[/etc/puppet/hiera.yaml]{:path=>"/etc/puppet/hiera.yaml", :ensure=>:file, 
:loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'preview_outputdir': 
'File[/var/cache/puppet/preview]{:path=>"/var/cache/puppet/preview", 
:mode=>"750", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, 
:loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'certdir': 
'File[/var/lib/puppet/ssl/certs]{:path=>"/var/lib/puppet/ssl/certs", 
:mode=>"755", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, 
:loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'ssldir': 
'File[/var/lib/puppet/ssl]{:path=>"/var/lib/puppet/ssl", :mode=>"771", 
:owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'publickeydir': 
'File[/var/lib/puppet/ssl/public_keys]{:path=>"/var/lib/puppet/ssl/public_keys",
 :mode=>"755", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, 
:loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file resource 'requestdir': 

Bug#889527: puppet: Puppet master/agent on testing/buster fails with SSL errors

[clayton]

Package: puppet
Version: 4.10.4-2
Severity: important

I have been running puppet master on testing for (many?) years, withou
major mishap until recently, when I started to get what looks to me
like SSL errors. Is there an SSL library problem?

On an up-to-date testing machine, running agent against a master on the
same machine, I am getting these errors:

# puppet agent --test --verbose --debug > /tmp/puppet-debug.txt
Warning: Unable to fetch my node definition, but the agent run will continue:
Warning: SSL_read: decryption failed or bad record mac
Error: /File[/var/cache/puppet/facts.d]: Failed to generate additional 
resources using 'eval_generate': SSL_read: decryption failed or bad record mac
Error: /File[/var/cache/puppet/facts.d]: Could not evaluate: Could not retrieve 
file metadata for puppet:///pluginfacts: SSL_read: decryption failed or bad 
record mac
Error: /File[/var/cache/puppet/lib]: Failed to generate additional resources 
using 'eval_generate': SSL_read: decryption failed or bad record mac
Error: /File[/var/cache/puppet/lib]: Could not evaluate: Could not retrieve 
file metadata for puppet:///plugins: SSL_read: decryption failed or bad record 
mac
Error: Could not retrieve catalog from remote server: SSL_read: decryption 
failed or bad record mac
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
Error: Could not send report: SSL_read: decryption failed or bad record mac

This has been going on for weeks, I thought it would just go away
but no such luck.

I will e-mail the debug output once I have a bug report number for this.

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

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

Versions of packages puppet depends on:
ii  adduser  3.116
ii  facter   2.4.6-1
ii  hiera3.2.0-2
ii  init-system-helpers  1.51
ii  lsb-base 9.20170808
ii  ruby 1:2.3.3
ii  ruby-augeas  1:0.5.0-3+b5
ii  ruby-deep-merge  1.1.1-1
ii  ruby-rgen0.8.0-1
ii  ruby-safe-yaml   1.0.4-1
ii  ruby-shadow  2.4.1-1+b3

Versions of packages puppet recommends:
ii  debconf-utils  1.5.65
ii  lsb-release9.20170808
ii  ruby-selinux   2.7-2+b1

Versions of packages puppet suggests:
pn  ruby-rrd  

-- no debconf information

Bug#875941: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: virtualbox-guest-dkms module build fails)

[Clayton]

On Sat, 16 Sep 2017 10:33:04 +
ow...@bugs.debian.org (Debian Bug Tracking System) wrote:

> new kernel and old vbox don't match. Use vbox from unstable or
> testing.

But that kernel came from neither testing nor unstable:

$ apt-cache policy linux-image-4.9.0-3-amd64
linux-image-4.9.0-3-amd64:
  Installed: 4.9.30-2+deb9u3
  Candidate: 4.9.30-2+deb9u3
  Version table:
 *** 4.9.30-2+deb9u3 500
500 http://security.debian.org stretch/updates/main amd64
Packages 100 /var/lib/dpkg/status
 4.9.30-2+deb9u2 500
500 http://http.debian.net/debian stretch/main amd64 Packages

Surely stable should have mutually compatible versions of kernel and at
least virtualbox guest tools?

Clayton

Bug#875941: virtualbox-guest-dkms module build fails

[clayton]

Package: virtualbox-guest-dkms
Version: 4.3.36-dfsg-1+deb8u1
Severity: important

Loading new virtualbox-guest-4.3.36 DKMS files...
Building for 4.9.0-3-amd64
Building initial module for 4.9.0-3-amd64
Error! Bad return status for module build on kernel: 4.9.0-3-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox-guest/4.3.36/build/make.log for more 
information.

  CC [M]  
/var/lib/dkms/virtualbox-guest/4.3.36/build/vboxguest/r0drv/linux/memobj-r0drv-linux.o
/var/lib/dkms/virtualbox-guest/4.3.36/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:
 In function â:
/var/lib/dkms/virtualbox-guest/4.3.36/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:581:21:
 error: implicit declaration of function â 
[-Werror=implicit-function-declaration]
 page_cache_release(pMemLnx->apPages[iPage]);
 ^~
/var/lib/dkms/virtualbox-guest/4.3.36/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:
 In function â:
/var/lib/dkms/virtualbox-guest/4.3.36/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:1032:29:
 warning: passing argument 1 of â makes integer from pointer without a cast 
[-Wint-conversion]
 rc = get_user_pages(pTask,  /* Task for fault 
accounting. */
 ^
In file included from 
/var/lib/dkms/virtualbox-guest/4.3.36/build/vboxguest/r0drv/linux/the-linux-kernel.h:88:0,
 from 
/var/lib/dkms/virtualbox-guest/4.3.36/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:31:
/usr/src/linux-headers-4.9.0-3-common/include/linux/mm.h:1302:6: note: expected 
â but argument is of type â
 long get_user_pages(unsigned long start, unsigned long nr_pages,

etc. etc.

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

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

Versions of packages virtualbox-guest-dkms depends on:
ii  dkms2.3-2
ii  virtualbox-guest-utils  4.3.36-dfsg-1+deb8u1

virtualbox-guest-dkms recommends no packages.

virtualbox-guest-dkms suggests no packages.

-- no debconf information

Bug#873293: ssl.SSLError: [SSL: UNSUPPORTED_PROTOCOL] unsupported protocol (_ssl.c:719)

[clayton]

Package: python3-boto
Version: 2.44.0-1
Severity: normal

Suddenly, every time I call cloudwatch.describe_alarms() I am getting an 
exception:

Traceback (most recent call last):
  File "deployCloudFormation.py", line 904, in 
deploy.diagnostics()
  File "deployCloudFormation.py", line 800, in diagnostics
alarmsAllSource = common.AWSiterator( cwSource.describe_alarms )
  File "/usr/lib/python3/dist-packages/boto/ec2/cloudwatch/__init__.py", line 
383, in describe_alarms
[('MetricAlarms', MetricAlarms)])
  File "/usr/lib/python3/dist-packages/boto/connection.py", line 1170, in 
get_list
response = self.make_request(action, params, path, verb)
  File "/usr/lib/python3/dist-packages/boto/connection.py", line 1116, in 
make_request
return self._mexe(http_request)
  File "/usr/lib/python3/dist-packages/boto/connection.py", line 1030, in _mexe
raise ex
  File "/usr/lib/python3/dist-packages/boto/connection.py", line 943, in _mexe
request.body, request.headers)
  File "/usr/lib/python3.5/http/client.py", line 1107, in request
self._send_request(method, url, body, headers)
  File "/usr/lib/python3.5/http/client.py", line 1152, in _send_request
self.endheaders(body)
  File "/usr/lib/python3.5/http/client.py", line 1103, in endheaders
self._send_output(message_body)
  File "/usr/lib/python3.5/http/client.py", line 934, in _send_output
self.send(msg)
  File "/usr/lib/python3.5/http/client.py", line 877, in send
self.connect()
  File "/usr/lib/python3/dist-packages/boto/https_connection.py", line 131, in 
connect
ca_certs=self.ca_certs)
  File "/usr/lib/python3.5/ssl.py", line 1077, in wrap_socket
ciphers=ciphers)
  File "/usr/lib/python3.5/ssl.py", line 760, in __init__
self.do_handshake()
  File "/usr/lib/python3.5/ssl.py", line 996, in do_handshake
self._sslobj.do_handshake()
  File "/usr/lib/python3.5/ssl.py", line 641, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: UNSUPPORTED_PROTOCOL] unsupported protocol (_ssl.c:719)

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

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

Versions of packages python3-boto depends on:
ii  python3   3.5.3-3
ii  python3-requests  2.18.1-1
ii  python3-six   1.10.0-4

python3-boto recommends no packages.

python3-boto suggests no packages.

-- no debconf information

Bug#872388: rss2email: cannot change send-to e-mail address for all existing feeds?

[clayton]

Package: rss2email
Version: 1:3.9-2.1
Severity: wishlist

The only way I can see currently to change the e-mail address that existing
r2e feeds are sent to, is to delete each feed and recreate it individually.
Obviously, this scales horribly.

There should be an option to reset all existing feeds to a new e-mail address.

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

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

Versions of packages rss2email depends on:
ii  python-xdg  0.25-4
ii  python2.7   2.7.13-2
ii  python3 3.5.3-3
ii  python3-feedparser  5.1.3-3
ii  python3-html2text   2016.9.19-1

Versions of packages rss2email recommends:
ii  python3-bs4  4.6.0-1

Versions of packages rss2email suggests:
pn  esmtp  

-- no debconf information

Bug#870337: Stretch: /lib/systemd/system/tor@default.service broken

[Clayton]

> Any symlinks for /home or /root or anything weird?  This looks like
> systemd and your specific setup being weird.

No, though I have seen weird things in OpenVZ-land before. I recently
tried to use a Debian image that was so sketchy it utterly failed to
upgrade between Debian versions from a minimal install state. Another
time I saw something that might be quite pertinent: after an upgrade to
the pre-release Stretch, systemd was pretty much hosed. The machine
would still boot, but there was no networking, none of the services
would autostart. There were lots of cgroup type of errors in the logs.
I managed to talk the tech support into upgrading the kernel on the
OpenVZ host to a more recent patch level and after that systemd worked.
(Did not try Tor on that machine though.)

I see that the kernel here, while appearing to be close to the same
vintage, is clearly different from OpenVZ machines I run with other
providers, and in fact every provider I am using seems to have a
slightly different kernel version.

If you are pretty sure it isn't a problem with this package, I would be
tempted to point a finger at the OpenVZ kernel. But, sadly, tech
support with this provider seems to be somewhat hostile and I am not in
a position to engage with them any further.

> If you google for 'systemd  Failed at step NAMESPACE spawning  Too
> many levels' you can find a few more examples of where things may go
> wrong.
> 
> I don't think this is a bug in the Debian package, but I'd still like
> to learn what is causing this on your system, exactly.

I see you have a PGP key. If you are interested and would like root on
the machine to poke around for a while to satisfy your curiosity, you
are welcome. It is still at a fairly early stage of installation, and
as a heavy OpenVZ user I too would like to see Tor work properly here
as well.

Clayton

Bug#870337: Stretch: /lib/systemd/system/tor@default.service broken

[Clayton]

> > What kind of non-standard Debian is this?  Kernel?  VPS?  

OpenVZ VPS,

# uname -a
Linux qhsg 2.6.32-042stab120.16 #1 SMP Tue Dec 13 20:58:28 MSK 2016
x86_64 GNU/Linux

I have Tor running on a very similar VPS, but Ubuntu 16.04, elsewhere.

> Also,
>   ls
> -ld /tmp /var/tmp /run /var /var/run /var/run/tor /var/run/tor-instances
> please.

# ls -ld /tmp/
drwxrwxrwt 10 root root 260 Aug  1 07:17 /tmp/

# ls -ld /var/tmp/
drwxrwxrwt 3 root root 4096 Aug  1 06:59 /var/tmp/

# ls -ld /run
drwxr-xr-x 18 root root 620 Aug  1 04:00 /run

# ls -ld /var
drwxr-xr-x 11 root root 4096 Aug 30  2015 /var

# ls -ld /var/run
lrwxrwxrwx 1 root root 4 Jul 25 04:11 /var/run -> /run

# ls -ld /var/run/tor/
drwxr-sr-x 2 debian-tor debian-tor 60 Aug  1 06:59 /var/run/tor/

/var/run/tor-instances does not exist.

Clayton

Bug#870337: Stretch: /lib/systemd/system/tor@default.service broken

[Clayton]

On Tue, 1 Aug 2017 08:35:46 +
Peter Palfrader <wea...@debian.org> wrote:

> Control: tags -1 + unreproducible
> On Tue, 01 Aug 2017, clayton wrote:
> 
> > On stretch, tor does not start after installation.  
> 
> You will need to provide more information.  Show the output of
> journalctrl -f while restarting the service, and show me your torrc.

See attached for journalctrl -f and torrc. torrc should (deliberately)
still be in the default state.

Clayton

torrc
Description: Binary data
journalctrl -f with those lines commented out (working Tor):

Aug 01 06:54:50 qhsg systemd[1]: Stopping Anonymizing overlay network for TCP...
Aug 01 06:54:50 qhsg systemd[1]: Stopped Anonymizing overlay network for TCP 
(multi-instance-master).
Aug 01 06:54:50 qhsg systemd[1]: Stopping Anonymizing overlay network for TCP 
(multi-instance-master)...
Aug 01 06:54:50 qhsg systemd[1]: tor.service: Failed to set invocation ID on 
control group /system.slice/tor.service, ignoring: Operation not permitted
Aug 01 06:54:50 qhsg systemd[1]: Starting Anonymizing overlay network for TCP 
(multi-instance-master)...
Aug 01 06:54:50 qhsg systemd[1]: Stopped Anonymizing overlay network for TCP.
Aug 01 06:54:50 qhsg systemd[1]: tor@default.service: Failed to set invocation 
ID on control group /system.slice/system-tor.slice/tor@default.service, 
ignoring: Operation not permitted
Aug 01 06:54:50 qhsg systemd[1]: Starting Anonymizing overlay network for TCP...
Aug 01 06:54:51 qhsg systemd[1]: Started Anonymizing overlay network for TCP 
(multi-instance-master).
Aug 01 06:54:51 qhsg systemd[1]: tor.service: Failed to set invocation ID on 
control group /system.slice/tor.service, ignoring: Operation not permitted
Aug 01 06:54:51 qhsg tor[30428]: Aug 01 06:54:51.112 [notice] Tor 0.2.9.11 
(git-572f4570e1771890) running on Linux with Libevent 2.0.21-stable, OpenSSL 
1.1.0f and Zlib 1.2.8.
Aug 01 06:54:51 qhsg tor[30428]: Aug 01 06:54:51.113 [notice] Tor can't help 
you if you use it wrong! Learn howto be safe at 
https://www.torproject.org/download/download#warning
Aug 01 06:54:51 qhsg tor[30428]: Aug 01 06:54:51.113 [notice] Read 
configuration file "/usr/share/tor/tor-service-defaults-torrc".
Aug 01 06:54:51 qhsg tor[30428]: Aug 01 06:54:51.113 [notice] Read 
configuration file "/etc/tor/torrc".
Aug 01 06:54:51 qhsg tor[30428]: Configuration was valid
Aug 01 06:54:51 qhsg tor[30431]: Aug 01 06:54:51.154 [notice] Tor 0.2.9.11 
(git-572f4570e1771890) running on Linux with Libevent 2.0.21-stable, OpenSSL 
1.1.0f and Zlib 1.2.8.
Aug 01 06:54:51 qhsg tor[30431]: Aug 01 06:54:51.155 [notice] Tor can't help 
you if you use it wrong! Learn howto be safe at 
https://www.torproject.org/download/download#warning
Aug 01 06:54:51 qhsg tor[30431]: Aug 01 06:54:51.155 [notice] Read 
configuration file "/usr/share/tor/tor-service-defaults-torrc".
Aug 01 06:54:51 qhsg tor[30431]: Aug 01 06:54:51.155 [notice] Read 
configuration file "/etc/tor/torrc".
Aug 01 06:54:51 qhsg tor[30431]: Aug 01 06:54:51.159 [notice] I think we have 8 
CPUS, but only 1 of them are available. Telling Tor to only use 1. You can 
override this with the NumCPUs option
Aug 01 06:54:51 qhsg tor[30431]: Aug 01 06:54:51.159 [notice] Opening Socks 
listener on 127.0.0.1:9050
Aug 01 06:54:51 qhsg systemd[1]: Started Anonymizing overlay network for TCP.

journalctrl -f with those lines NOT commented out (broken Tor), over and over 
again:

Aug 01 06:59:38 qhsg systemd[1]: Starting Anonymizing overlay network for TCP...
Aug 01 06:59:38 qhsg systemd[30528]: tor@default.service: Failed at step 
NAMESPACE spawning /usr/bin/install: Too many levels of symbolic links
Aug 01 06:59:38 qhsg systemd[1]: tor@default.service: Control process exited, 
code=exited status=226
Aug 01 06:59:38 qhsg systemd[1]: Failed to start Anonymizing overlay network 
for TCP.
Aug 01 06:59:38 qhsg systemd[1]: tor@default.service: Unit entered failed state.
Aug 01 06:59:38 qhsg systemd[1]: tor@default.service: Failed with result 
'exit-code'.
Aug 01 06:59:38 qhsg systemd[1]: tor@default.service: Service hold-off time 
over, scheduling restart.
Aug 01 06:59:38 qhsg systemd[1]: Stopped Anonymizing overlay network for TCP.
Aug 01 06:59:38 qhsg systemd[1]: tor@default.service: Start request repeated 
too quickly.
Aug 01 06:59:38 qhsg systemd[1]: Failed to start Anonymizing overlay network 
for TCP.
Aug 01 06:59:38 qhsg systemd[1]: tor@default.service: Unit entered failed state.
Aug 01 06:59:38 qhsg systemd[1]: tor@default.service: Failed with result 
'exit-code'.

Bug#870337: Stretch: /lib/systemd/system/tor@default.service broken

[clayton]

Package: tor
Version: 0.2.9.11-1~deb9u1
Severity: normal

On stretch, tor does not start after installation.

After I comment out these

# ReadOnlyDirectories=/
# ReadWriteDirectories=-/proc
# ReadWriteDirectories=-/var/lib/tor
# ReadWriteDirectories=-/var/log/tor
# ReadWriteDirectories=-/var/run 

lines in /lib/systemd/system/tor@default.service this

systemctl start tor.service

will work.

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

Kernel: Linux 2.6.32-042stab120.16 (SMP w/1 CPU core)
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)

Versions of packages tor depends on:
ii  adduser  3.115
ii  init-system-helpers  1.48
ii  libc62.24-11+deb9u1
ii  libevent-2.0-5   2.0.21-stable-3
ii  libseccomp2  2.3.1-2.1
ii  libssl1.11.1.0f-3
ii  libsystemd0  232-25+deb9u1
ii  lsb-base 9.20161125
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages tor recommends:
ii  logrotate3.11.0-0.1
ii  tor-geoipdb  0.2.9.11-1~deb9u1
ii  torsocks 2.2.0-1

Versions of packages tor suggests:
pn  apparmor-utils   
pn  mixmaster
ii  obfs4proxy   0.0.7-1+b2
pn  obfsproxy
pn  socat
pn  tor-arm  
pn  torbrowser-launcher  

-- no debconf information

Bug#849364: closed by Alexandre Viau <av...@debian.org> (Fixed in 20161221.2.7bd7d91~dfsg1-1)

[Clayton]

On Thu, 06 Jul 2017 19:21:09 +
ow...@bugs.debian.org (Debian Bug Tracking System) wrote:

> Afaik this should be fixed in 20161221.2.7bd7d91~dfsg1-1.

As of this moment, it works on my bare metal Debian Testing machine, but
not my Qubes OS Debian Stretch virtual machine. (Both are within a day
or so of being fully up-to-date.)

On Qubes, I continue to see the same behavior as in the original report.

Clayton

Bug#864344: mate-screensaver: mate screen lock retains alternate ibus input method (cannot login!)

[Clayton]

> This certainly is an upstream issue. Would you mind filing a bug
> report here? https://github.com/mate-desktop/mate-screensaver/issues
> 
> ... and get back to us with the URL of the reported upstream bug?

https://github.com/mate-desktop/mate-screensaver/issues/129

Bug#864344: mate-screensaver: mate screen lock retains alternate ibus input method (cannot login!)

[clayton]

Package: mate-screensaver
Version: 1.16.1-1
Severity: important

I was using ibus to type some Chinese, and stepping away for a few minutes,
locked my screen with alt-ctl-l

When I came back and tried to enter my password to unlock the screen, I
was still typing Chinese via ibus in the password field! And the screen locker 
ignored the 
keyboard shortcut (typically meta-space, but configurable) to switch back to 
normal english
keyboard output.

I was finally able to unlock the screen without resorting to pulling the plug,
by selecting "login as a different user", getting the desktop login screen back,
and logging in there as the same user for which the screen was locked.

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

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

Versions of packages mate-screensaver depends on:
ii  dbus-x11  1.10.18-1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11
ii  libcairo-gobject2 1.14.8-1
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.18-1
ii  libdbus-glib-1-2  0.108-2
ii  libgdk-pixbuf2.0-02.36.5-2
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libglib2.0-0  2.50.3-2
ii  libgtk-3-03.22.11-1
ii  libice6   2:1.0.9-2
ii  libmate-desktop-2-17  1.16.2-2
ii  libmate-menu2 1.16.0-2
ii  libmatekbd4   1.16.0-2
ii  libnotify40.7.7-2
ii  libpam0g  1.1.8-3.6
ii  libpango-1.0-01.40.5-1
ii  libpangocairo-1.0-0   1.40.5-1
ii  libsm62:1.2.2-1+b3
ii  libstartup-notification0  0.12-4+b2
ii  libsystemd0   232-24
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxklavier16 5.4-2
ii  libxss1   1:1.2.2-1
ii  libxxf86vm1   1:1.1.4-1+b2
ii  mate-desktop-common   1.16.2-2
ii  mate-screensaver-common   1.16.1-1
ii  mate-session-manager  1.16.1-1

Versions of packages mate-screensaver recommends:
ii  mate-power-manager  1.16.2-1

Versions of packages mate-screensaver suggests:
pn  rss-glx
ii  xscreensaver-data  5.36-1

-- no debconf information

Bug#860950: steam: crashes at startup

[Clayton]

> Can you provide more information about your system and how to
> reproduce this?  Others have tried and failed, so there must be more
> to it.  Try backing up .steam somewhere else so it tries to start
> fresh.

I just tried on a different x86_64 machine and it works for me there
too. However on the original i386 machine from which I reported the
bug, I can still reliably reproduce.

Clayton

Bug#860950: steam: crashes on startup

[clayton]

Package: steam
Version: 1.0.0.54-2
Severity: important

$ steam
ILocalize::AddFile() failed to load file "public/steambootstrapper_english.txt".
[2017-04-22 20:46:20] Startup - updater built Nov 23 2016 01:05:42
Xlib:  extension "GLX" missing on display ":0.0".
*** Error in `/home/expatit/.steam/ubuntu12_32/steam': free(): invalid pointer: 
0xbfdf6750 ***
=== Backtrace: =
/lib/i386-linux-gnu/libc.so.6(+0x6737a)[0xb72c437a]
/lib/i386-linux-gnu/libc.so.6(+0x6dfb7)[0xb72cafb7]
/lib/i386-linux-gnu/libc.so.6(+0x6e776)[0xb72cb776]
/usr/lib/i386-linux-gnu/libX11.so.6(XFree+0x18)[0xb764b018]
/home/expatit/.steam/ubuntu12_32/steam(+0x51406)[0x800c2406]
/home/expatit/.steam/ubuntu12_32/steam(+0x520ee)[0x800c30ee]
/home/expatit/.steam/ubuntu12_32/steam(+0x22420)[0x80093420]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xb7275276]
/home/expatit/.steam/ubuntu12_32/steam(+0x25ae9)[0x80096ae9]
=== Memory map: 
80071000-80422000 r-xp  00:13 583491 
/expatit/.steam/ubuntu12_32/steam
80422000-80436000 r--p 003b1000 00:13 583491 
/expatit/.steam/ubuntu12_32/steam

etc.

b77a1000-b77a2000 r--p 00022000 00:13 33039  /lib/i386-linux-gnu/ld-2.24.so
b77a2000-b77a3000 rw-p 00023000 00:13 33039  /lib/i386-linux-gnu/ld-2.24.so
bfdda000-bfdfb000 rw-p  00:00 0  [stack]
Aborted
tar: This does not look like a tar archive
xz: (stdin): File format not recognized
tar: Child returned status 1
tar: Error is not recoverable: exiting now
find: ‘/home/expatit/.steam/ubuntu12_32/steam-runtime’: No such file or 
directory

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing'), (700, 'unstable'), (1, 'experimental')
Architecture: i386
 (i686)

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

Versions of packages steam depends on:
ii  debconf [debconf-2.0]1.5.60
ii  libc62.24-9
ii  libgl1-mesa-dri  13.0.6-1
ii  libgl1-mesa-glx  13.0.6-1
ii  libgpg-error01.26-2
ii  libstdc++6   6.3.0-12
ii  libtxc-dxtn-s2tc [libtxc-dxtn0]  1.0+git20151227-2
ii  libudev1 232-22
ii  libx11-6 2:1.6.4-3
ii  libxinerama1 2:1.1.3-1+b3
ii  xz-utils 5.2.2-1.2+b1

Versions of packages steam recommends:
ii  fonts-liberation  1:1.07.4-2
ii  gnome-terminal [x-terminal-emulator]  3.22.2-1
ii  libxss1   1:1.2.2-1
ii  lxterminal [x-terminal-emulator]  0.3.0-1
ii  termit [x-terminal-emulator]  3.0-1+b1
ii  xterm [x-terminal-emulator]   327-2
ii  zenity3.22.0-1+b1

Versions of packages steam suggests:
pn  steam-devices  

-- debconf information:
* steam/license:
  steam/purge:
* steam/question: I AGREE

Bug#856432: Can't be reproduced

[Joshua Clayton]

Balalsankar,

Thanks for testing.

my install attempt has been on a long lived VM that was recently upgraded.

postgres 9.1, 9.4 and the respective postgres clients were still installed.

After purging those, and reinstalling postgreSQL 9.6, the reinstall still failed

I removed everything aptitude listed under locally installed or obsolete

...purged everything with gitlab in the name...

apt install gitlab...

Had to remove a /usr/local/bin/rake that was installed somehow I don't recall

uninstall apache, apache passenger, everything apache...

(after uninstalling apache, nginx is pulled in and installed)

... uninstall gitlab and reinstall again.

Remove nginx default site.
 
...and everything is copacetic! Yay!

Wow that was painful, but it would work on a clean install.
Maybe this could be improved, but its working

On 03/01/2017 12:39 AM, Balasankar C wrote:
> Hi,
>
> I tried reproducing this bug in a Stretch image using docker and was unable 
> to do so. GitLab was installed and configured without any issues. See the log 
> for the complete installation details. I installed gitlab-8.13.11+dfsg-4 from 
> unstable.
>
> PS: I was on docker, which restricted automatic starting of postgresql 
> service. So I first installed postgresql and started the service and then 
> installed gitlab.
>
> Regards
> Balasankar C

Bug#856432: gitlab --configure looks for postgres 9.1, but 9.6 is installed

[Joshua Clayton]

Package: gitlab
Version: 8.13.11+dfsg-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

gitlab installs, but will not complete configuration, because (at least)
it is looking for a wrong version of a postgresql extension. 
Possibly also incompatible with latest postgresql

Create database if not present
Make gitlab user owner of gitlab database...
ALTER DATABASE
Grant all priveleges to gitlab user...
GRANT
ERROR:  could not openextension control file 
"/usr/share/postgresql/9.1/extension/pg_trgm.control": No such file or directory
dpkg: error processing package gitlab (--configure):
 subprocess installed post-installation script returned error exit status 1


Tried adding a symlink from /usr/share/postgresql/9.1 -> 9.6
(I have no idea whether this is a valid thing to do in this case)

Then the error changes to 

Create database if not present
Make gitlab user owner of gitlab database...
ALTER DATABASE
Grant all priveleges to gitlab user...
GRANT
ERROR:  syntax error at or near "PARALLEL"
dpkg: error processing package gitlab (--configure):
 subprocess installed post-installation script returned error exit status 1


First encountered on stretch/testing.
Symptoms exactly the same with sid

Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 4.9.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  adduser   3.115
ii  apache2 [httpd]   2.4.25-3
ii  asciidoctor   1.5.4-2
ii  bc1.06.95-9+b2
ii  bundler   1.13.6-2
ii  debconf [debconf-2.0] 1.5.60
ii  git   1:2.11.0-2
ii  gitlab-shell  3.6.6-4
ii  gitlab-workhorse  0.8.5+debian-3
ii  init-system-helpers   1.47
ii  libjs-chartjs 1.0.2-1
ii  libjs-clipboard   1.4.2-1
ii  libjs-fuzzaldrin-plus 0.3.1+git.20161008.da2cb58+dfsg-4
ii  libjs-graphael0.5+dfsg-1
ii  libjs-jquery-cookie   11-3
ii  libjs-jquery-history  11-3
ii  libjs-jquery-nicescroll   3.6.6-1
ii  lsb-base  9.20161125
ii  nodejs4.7.2~dfsg-2
ii  openssh-client1:7.4p1-6
ii  postfix [mail-transport-agent]3.1.4-4
ii  postgresql-client 9.6+179
ii  postgresql-client-9.1 [postgresql-client  9.1.23-0+deb7u1
ii  postgresql-client-9.4 [postgresql-client  9.4.9-0+deb8u1
ii  postgresql-client-9.6 [postgresql-client  9.6.2-1
ii  postgresql-contrib9.6+179
ii  rake  10.5.0-2
ii  redis-server  3:3.2.8-1
ii  ruby  1:2.3.3
ii  ruby-ace-rails-ap 4.1.1-1
ii  ruby-activerecord-session-store   1.0.0-2
ii  ruby-acts-as-taggable-on  4.0.0-2
ii  ruby-addressable  2.4.0-1
ii  ruby-after-commit-queue   1.3.0-1
ii  ruby-akismet  2.0.0-1
ii  ruby-allocations  1.0.3-1+b2
ii  ruby-asana0.4.0-1
ii  ruby-attr-encrypted   3.0.1-2
ii  ruby-babosa   1.0.2-2
ii  ruby-base32   0.3.2-3
ii  ruby-bootstrap-sass   3.3.5.1-3
ii  ruby-browser  2.2.0-2
ii  ruby-cal-heatmap-rails3.6.0+dfsg-1
ii  ruby-carrierwave  0.10.0+gh-4
ii  ruby-charlock-holmes  0.7.3+dfsg-2+b3
ii  ruby-chronic  0.10.2-3
ii  ruby-chronic-duration 0.10.6-1
ii  ruby-coffee-rails 4.1.0-2
ii  ruby-coffee-script-source 1.10.0-1
ii  ruby-connection-pool  2.2.0-1
ii  ruby-creole   0.5.0-2
ii  ruby-d3-rails 3.5.6+dfsg-1
ii  ruby-default-value-for3.0.1-1
ii  ruby-devise   4.2.0-1
ii  ruby-devise-two-factor3.0.0-2
ii  ruby-diffy3.0.6-1
ii  ruby-doorkeeper   4.2.0-3
ii  ruby-dropzonejs-rails 0.7.1-1
ii  ruby-email-reply-parser   0.5.8-1
ii  ruby-fog-aws  0.12.0-1
ii  ruby-fog-azure0.0.2-1
ii  ruby-fog-core 

Bug#855903: bitcoin-qt: does not start after update

[clayton]

Package: bitcoin-qt
Version: 0.13.1-0.1+b2
Severity: important

This is a Debian Testing box, just brought completely up to date.
Trying to start bitcoin-qt fails like this:

$ bitcoin-qt
bitcoin-qt: chain.cpp:96: CBlockIndex* CBlockIndex::GetAncestor(int): 
Assertion `pindexWalk->pprev' failed.

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

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

Versions of packages bitcoin-qt depends on:
ii  libboost-chrono1.62.0   1.62.0+dfsg-4
ii  libboost-filesystem1.62.0   1.62.0+dfsg-4
ii  libboost-program-options1.62.0  1.62.0+dfsg-4
ii  libboost-system1.62.0   1.62.0+dfsg-4
ii  libboost-thread1.62.0   1.62.0+dfsg-4
ii  libc6   2.24-9
ii  libdb5.3++  5.3.28-12+b1
ii  libevent-2.0-5  2.0.21-stable-3
ii  libevent-pthreads-2.0-5 2.0.21-stable-3
ii  libgcc1 1:6.3.0-6
ii  libminiupnpc10  1.9.20140610-2.1
ii  libprotobuf10   3.0.0-9
ii  libqrencode33.4.4-1+b1
ii  libqt5core5a5.7.1+dfsg-3+b1
ii  libqt5dbus5 5.7.1+dfsg-3+b1
ii  libqt5gui5  5.7.1+dfsg-3+b1
ii  libqt5network5  5.7.1+dfsg-3+b1
ii  libqt5widgets5  5.7.1+dfsg-3+b1
ii  libssl1.1   1.1.0e-1
ii  libstdc++6  6.3.0-6
ii  libzmq5 4.2.1-2

bitcoin-qt recommends no packages.

bitcoin-qt suggests no packages.

-- no debconf information

Bug#841295: closed by Lars Wirzenius <l...@liw.fi> (Bug#841295: fixed in obnam 1.20-1)

[Clayton]

On Sat, 29 Oct 2016 15:27:22 +
ow...@bugs.debian.org (Debian Bug Tracking System) wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the obnam package:
> 
> #841295: ERROR: RD5FA4X: System
> error: /tmp/tmpZmTUlC/S.gpg-agent.rstrd: 2: No such file or directory
> 
> It has been closed by Lars Wirzenius .

It just came down and is working for me. Thanks much!

Bug#849364: ring: Segmentation fault gnome-ring

[clayton]

Package: ring
Version: 20161207.2.7a29ace~dfsg1-1
Severity: important

This happens every time for me:

$ gnome-ring&
[1] 3283
user@qubes-insecure:~/clientsCode/tweriod/var-www-tweriod$ ** Message: Ring 
GNOME client version: 1.0.0
** Message: git ref: unknown
libEGL warning: DRI2: failed to authenticate
libEGL warning: DRI2: failed to open swrast (search paths 
/usr/lib/x86_64-linux-gnu/dri:${ORIGIN}/dri:/usr/lib/dri)
libEGL warning: DRI2: failed to authenticate
libEGL warning: DRI2: failed to open swrast (search paths 
/usr/lib/x86_64-linux-gnu/dri:${ORIGIN}/dri:/usr/lib/dri)

(gnome-ring:3283): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' 
failed
libEGL warning: DRI2: failed to authenticate
libEGL warning: DRI2: failed to open swrast (search paths 
/usr/lib/x86_64-linux-gnu/dri:${ORIGIN}/dri:/usr/lib/dri)

(gnome-ring:3283): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' 
failed

Happy to help debug, if necessary!

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

Kernel: Linux 4.1.24-10.pvops.qubes.x86_64 (SMP w/3 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 ring depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  libappindicator3-1   0.4.92-4
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-8
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libclutter-1.0-0 1.26.0+dfsg-2
ii  libclutter-gtk-1.0-0 1.8.2-1
ii  libcogl-pango20  1.22.2-2
ii  libcogl-path20   1.22.2-2
ii  libcogl201.22.2-2
ii  libdbus-1-3  1.10.14-1
ii  libdbus-glib-1-2 0.108-1
ii  libdbusmenu-glib412.10.2-1
ii  libdrm2  2.4.74-1
ii  libebackend-1.2-10   3.22.3-1
ii  libebook-1.2-16  3.22.3-1
ii  libebook-contacts-1.2-2  3.22.3-1
ii  libedata-book-1.2-25 3.22.3-1
ii  libedataserver-1.2-223.22.3-1
ii  libegl1-mesa [libegl1-x11]   13.0.2-1
ii  libgbm1  13.0.2-1
ii  libgcc1  1:6.2.1-5
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk-3-0   3.22.5-1
ii  libjavascriptcoregtk-4.0-18  2.14.2-1
ii  libjson-glib-1.0-0   1.2.2-1
ii  libnm-glib4  1.4.2-3
ii  libnm-util2  1.4.2-3
ii  libnotify4   0.7.7-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libqrencode3 3.4.4-1+b1
ii  libqt5core5a 5.7.1+dfsg-1
ii  libqt5dbus5  5.7.1+dfsg-1
ii  libsecret-1-00.18.5-2
ii  libsoup2.4-1 2.56.0-1
ii  libstdc++6   6.2.1-5
ii  libwayland-client0   1.12.0-1
ii  libwayland-cursor0   1.12.0-1
ii  libwayland-egl1-mesa [libwayland-egl1]   13.0.2-1
ii  libwayland-server0   1.12.0-1
ii  libwebkit2gtk-4.0-37 2.14.2-1
ii  libx11-6 2:1.6.4-2
ii  libxcomposite1   1:0.4.4-1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.8-1
ii  libxkbcommon00.7.0-1
ii  libxml2  2.9.4+dfsg1-2.1
ii  libxrandr2   2:1.5.1-1
ii  ring-daemon  20161207.2.7a29ace~dfsg1-1

ring recommends no packages.

ring suggests no packages.

-- no debconf information

Bug#841295: ERROR: RD5FA4X: System error: /tmp/tmpZmTUlC/S.gpg-agent.rstrd: 2: No such file or directory

[clayton]

Package: obnam
Version: 1.19.1-1
Severity: normal

Context: I have a shell script pushing obnam backups from my desktop to
multiple other machines using SFTP. All remote backups
are GPG-encrypted using obnam's built-in capability,
in exactly the same way. This has been working
flawlessly for over a year.

Suddenly, backing up to just one of those machines results in
the above error message. fsck results in the same error. The remote
causing the error is running an up-to-date stretch, as are multiple
other machines that are accepting backups just fine. This happens
reliably every time on this one machine, and never happens on the
other machines.

This is the trace that shows up in my syslog:

Oct 19 20:10:23 t410 obnam: CRITICAL Caught OSError: [Errno 2] No such
file or directory: '/tmp/tmp8XfPQ3/S.gpg-agent.rstrd'#012Traceback
(most recent call last):#012  File
"/usr/lib/python2.7/dist-packages/obnamlib/app.py", line 208, in
process_args#012cliapp.Application.process_args(self, args)#012
File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 589, in
process_args#012method(args[1:])#012  File
"/usr/lib/python2.7/dist-packages/obnamlib/plugins/fsck_plugin.py",
line 320, in fsck#012self.repo.lock_everything()#012  File
"/usr/lib/python2.7/dist-packages/obnamlib/repo_interface.py", line
422, in lock_everything#012self.lock_chunk_indexes()#012  File
"/usr/lib/python2.7/dist-packages/obnamlib/fmt_6/repo_fmt_6.py", line
751, in lock_chunk_indexes#012self._raw_lock_chunk_indexes()#012
File "/usr/lib/python2.7/dist-packages/obnamlib/fmt_6/repo_fmt_6.py",
line 734, in _raw_lock_chunk_indexes#012
self._chunksums.start_changes()#012  File
"/usr/lib/python2.7/dist-packages/obnamlib/fmt_6/repo_tree.py", line
82, in start_changes#012self.dirname)#012  File
"/usr/lib/python2.7/dist-packages/obnamlib/hooks.py", line 187, in
call#012self.hooks[name].call_callbacks(*args, **kwargs)#012  File
"/usr/lib/python2.7/dist-packages/obnamlib/hooks.py", line 64, in
call_callbacks#012callback(*args, **kwargs)#012  File
"/usr/lib/python2.7/dist-packages/obnamlib/plugins/encryption_plugin.py",
line 128, in toplevel_init#012pubkeys.add(self.pubkey)#012  File
"/usr/lib/python2.7/dist-packages/obnamlib/encryption.py", line 216, in
add#012self.gpg(True, ['--import'], stdin=key)#012  File
"/usr/lib/python2.7/dist-packages/obnamlib/encryption.py", line 232, in
gpg#012self._cleanup()#012  File
"/usr/lib/python2.7/dist-packages/obnamlib/encryption.py", line 181, in
_cleanup#012shutil.rmtree(self._gpghome)#012  File
"/usr/lib/python2.7/shutil.py", line 252, in rmtree#012
onerror(os.remove, fullname, sys.exc_info())#012  File
"/usr/lib/python2.7/shutil.py", line 250, in rmtree#012
os.remove(fullname)#012OSError: [Errno 2] No such file or directory:
'/tmp/tmp8XfPQ3/S.gpg-agent.rstrd' 

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

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

Versions of packages obnam depends on:
ii  libc6 2.24-3
ii  python2.7.11-2
ii  python-cliapp 1.20160724-1
ii  python-fuse   2:0.2.1-14
ii  python-larch  1.20151025-1
ii  python-paramiko   2.0.0-1
ii  python-tracing0.9-1
ii  python-ttystatus  0.32-1
ii  python-yaml   3.12-1

obnam recommends no packages.

obnam suggests no packages.

-- no debconf information

Bug#841052: tinc: systemctl start tinc.service does not work, fails silently

[clayton]

Package: tinc
Version: 1.0.29-1
Severity: normal

However

systemctl start tinc@netname.service

DOES work. And thereafter

systemctl restart tinc.service  &
systemctl stop tinc.service

work correctly. I can reproduce this at least on two recent stretch installs.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'unstable')
Architecture: i386 (i686)

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

Versions of packages tinc depends on:
ii  init-system-helpers  1.45
ii  libc62.24-3
ii  liblzo2-22.08-1.2
ii  libssl1.0.2  1.0.2j-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

tinc recommends no packages.

tinc suggests no packages.

-- no debconf information

Bug#838692: cdogmy69: TaxDefense

[Clayton Erceg]

Fuck off


On Mon, 26 Sep 2016 at 7:41 AM, IRS___Tax__Debt  wrote:

> cdogmy69___Smile
>
> If you have an IRS__Tax of any kind
>
> Now you can eliminate__it in one___go
>
> Get an__evaluation __now __for ___free__
>

Bug#825725: evolution: Crashes on start: GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' failed

[clayton]

Package: evolution
Version: 3.20.2-2
Severity: important

Context: my environment is uncommon, this is Debian Testing running headless as 
a VM on Qubes OS
with the Xserver running in dom0. This used to work before recent updates, so I 
am thinking
glibc?

This is what happens now when I try to start evolution in an xterm in Debian on 
Qubes:

$ evolution&
libEGL warning: DRI2: failed to authenticate
libEGL warning: DRI2: failed to open swrast (search paths 
/usr/lib/x86_64-linux-gnu/dri:${ORIGIN}/dri:/usr/lib/dri)
libEGL warning: DRI2: failed to authenticate
libEGL warning: DRI2: failed to open swrast (search paths 
/usr/lib/x86_64-linux-gnu/dri:${ORIGIN}/dri:/usr/lib/dri)
(evolution:3059): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' 
failed

I have the nearly exact same version of Debian Testing running on bare metal, 
with a somewhat
different selection of packages, where evolution currently starts just fine.

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

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

Versions of packages evolution depends on:
ii  dbus   1.10.8-1
ii  evolution-common   3.20.2-2
ii  evolution-data-server  3.20.2-2
ii  libc6  2.22-9
ii  libcamel-1.2-573.20.2-2
ii  libclutter-gtk-1.0-0   1.8.0-1
ii  libecal-1.2-19 3.20.2-2
ii  libedataserver-1.2-21  3.20.2-2
ii  libevolution   3.20.2-2
ii  libglib2.0-0   2.48.1-1
ii  libgtk-3-0 3.20.4-1
ii  libical2   2.0.0-0.4
ii  libicu55   55.1-7
ii  libnotify4 0.7.6-2
ii  libsoup2.4-1   2.54.1-1
ii  libwebkitgtk-3.0-0 2.4.11-1+b1
ii  libxml22.9.3+dfsg1-1
ii  psmisc 22.21-2.1+b1

Versions of packages evolution recommends:
ii  bogofilter 1.2.4+dfsg1-4
ii  evolution-plugins  3.20.2-2
ii  yelp   3.20.1-1

Versions of packages evolution suggests:
pn  evolution-ews   
pn  evolution-plugins-experimental  
ii  gnupg   1.4.20-6
ii  network-manager 1.2.2-1

-- no debconf information

Bug#825463: gnome-screensaver: gnome screensaver not working

[clayton]

Package: gnome-screensaver
Version: 3.6.1-7+b1
Severity: important

gnome-core installed, gnome-screensaver installed, gdm3 is my default display 
manager,
screen lock is turned on in gnome settings: nothing happens. The screensaver 
does not turn on
automatically, nor is there any obvious way to turn it on manually.

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

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

Versions of packages gnome-screensaver depends on:
ii  dbus-x11   1.10.8-1
ii  gnome-icon-theme   3.12.0-1
ii  gnome-session-bin  3.20.1-2
ii  gsettings-desktop-schemas  3.20.0-3
ii  libc6  2.22-9
ii  libcairo2  1.14.6-1+b1
ii  libdbus-1-31.10.8-1
ii  libdbus-glib-1-2   0.106-1
ii  libgdk-pixbuf2.0-0 2.34.0-1
ii  libglib2.0-0   2.48.1-1
ii  libgnome-desktop-3-12  3.20.2-1
ii  libgnomekbd8   3.6.0-1
ii  libgtk-3-0 3.20.4-1
ii  libpam0g   1.1.8-3.2
ii  libsystemd0229-6
ii  libx11-6   2:1.6.3-1
ii  libxext6   2:1.3.3-1
ii  libxklavier16  5.2.1-1
ii  libxxf86vm11:1.1.4-1

Versions of packages gnome-screensaver recommends:
ii  gnome-power-manager   3.20.0-1
ii  libpam-gnome-keyring  3.20.0-1

gnome-screensaver suggests no packages.

-- debconf-show failed

Bug#817783: chromium: IPv6 broken?

[clayton]

Package: chromium
Version: 49.0.2623.75-2
Severity: normal

I am using miredo to provide basic IPv6 connectivity on my desktop for testing,
it is point-and-shoot: just install it and turn on the daemon. Then:

ping6 ipv6.google.com works fine.

Firefox and w3m work fine on http://v6.testmyipv6.com/

But if I direct chromium to the same link, I get:

This site can’t be reached
v6.testmyipv6.com’s server DNS address could not be found.
DNS_PROBE_FINISHED_BAD_CONFIG

even if I start this way: chromium --enable-ipv6

However, dig works fine on the same machine:

$ dig v6.testmyipv6.com 
;; ANSWER SECTION:
v6.testmyipv6.com.  1186IN  2001:4830:2502:8001::a00:a

It looks to me like my machine is handling IPv6 alright, but Chromium is not.

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

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

Versions of packages chromium depends on:
ii  libasound21.1.0-1
ii  libatk1.0-0   2.18.0-1
ii  libavcodec-ffmpeg56   7:2.8.6-1+b1
ii  libavformat-ffmpeg56  7:2.8.6-1+b1
ii  libavutil-ffmpeg547:2.8.6-1+b1
ii  libc6 2.21-9
ii  libcairo2 1.14.6-1
ii  libcups2  2.1.3-3
ii  libdbus-1-3   1.10.6-1
ii  libexpat1 2.1.0-7
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.6.3-3
ii  libgcc1   1:5.3.1-10
ii  libgdk-pixbuf2.0-02.32.3-1.2
ii  libglib2.0-0  2.46.2-3
ii  libgnome-keyring0 3.12.0-1+b1
ii  libgtk2.0-0   2.24.29-1
ii  libjpeg62-turbo   1:1.4.2-2
ii  libnspr4  2:4.11-1
ii  libnss3   2:3.21-1.1
ii  libpango-1.0-01.38.1-1
ii  libpangocairo-1.0-0   1.38.1-1
ii  libpci3   1:3.3.1-1.1
ii  libspeechd2   0.8-7
ii  libsrtp0  1.4.5~20130609~dfsg-1.1
ii  libstdc++65.3.1-10
ii  libx11-6  2:1.6.3-1
ii  libxcomposite11:0.4.4-1
ii  libxcursor1   1:1.1.14-1+b1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxi62:1.7.6-1
ii  libxml2   2.9.3+dfsg1-1
ii  libxrandr22:1.5.0-1
ii  libxrender1   1:0.9.9-2
ii  libxslt1.11.1.28-2.1
ii  libxss1   1:1.2.2-1
ii  libxtst6  2:1.2.2-1+b1
ii  x11-utils 7.7+3
ii  xdg-utils 1.1.1-1

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

Versions of packages chromium suggests:
pn  chromium-l10n  

-- no debconf information

Bug#798460: apt: Testing transition broken

[Clayton]

On Wed, 9 Sep 2015 22:08:18 +0200
David Kalnischkies <da...@kalnischkies.de> wrote:

> Hi,
> 
> On Wed, Sep 09, 2015 at 10:45:01PM +0800, clayton wrote:
> > I am a Testing user. One of my machines is upgraded. A couple days
> > later and I try to upgrade another with the gcc5 transition, and
> > apt is broken. "apt-get dist-upgrade" wants to remove 254 packages
> > and "apt-get install apt" wants to remove 121 packages.
> 
> I read broken and instantly thing about segfaults, gcc5 linkr errors
> or other big headache stuff – and "all" you are complaining about is
> that APT presents you a solution you don't like…
> I am happy if that is all.  :)
>
> Unstable users had to live with that for quite a while now thanks to
> the gcc5 & libstdc++6 transition.  Testing users should be /mostly/
> uneffected, but now that the first parts of the transition entered
> testing you will see softer versions of transition pain as well.
> 
> Its probably best to contact a debian support channel like a
> debian-user mailinglist and ask there for advice – but you will have
> to provide details details details for them – like the output apt
> actually produced.
> 
> Removes aren't all "dangerous" removes. Many if not all of these
> removes are likely of the form "install new package libfoov5;
> removing package libfoo".  That is 'normal' for the gcc5 transition.
> Then there will be packages who still depend on libfoo – like
> obsolete packages, packages not in testing at the moment, packages
> proposefully temporarily broken in testing to get the sub-transition
> over with faster, packages from third-party repositories … but nobody
> can help if all you tell us is "254" and "121".
> 
> I am inclined to close as 'notabug', but I will give you a second
> chance at giving us some details so that it is actually possible to
> figure out what is the problem.

Just because it is not "OMG ITS COMPLETELY BROKEN" does not mean it is
not still broken. apt-get dist-upgrade basically wants to remove my
whole desktop. "apt-get install apt" still wants to remove essential
desktop apps: most or all of KDE and libreoffice, for starters.

Hey, I have been using Debian Testing for a long time (like more than a
decade) I am used to my desktop of preference breaking and then moving
to another for a while. But I don't think I am alone in viewing
libreoffice as essential and irreplaceable, and I would expect not to
be able to get libreoffice installed again for a while if I was to
upgrade in this state.

So I cannot upgrade in this state, therefore transition is broken for
me on this machine until the repository state changes. So I can wait for
a few days, sure.

But I would like to be able to recommend Debian as a desktop to my
Ubuntu-using friends. I personally do not consider a two+-year old
Debian Stable a reasonable desktop option. Therefore Debian Testing
must work for a reasonable person who is not a software engineer if we
are to compete with Ubuntu. This behavior does not make the cut.

Perhaps a bug against apt is not the place to make this stand, perhaps
apt can absolutely do no better in this scenario, and now it is your
turn to make that statement if it applies.

But for Debian as a whole this is definitely broken behavior that is not
suitable for public consumption. Most casual users would just upgrade
without paying much attention to the details and find themselves with
some serious breakage like uninstallable essential apps.

Clayton

Bug#798460: apt: Testing transition broken

[Clayton]

On Fri, 11 Sep 2015 15:02:49 +0200
Julian Andres Klode <j...@debian.org> wrote:

> On Fri, Sep 11, 2015 at 07:59:27PM +0800, Clayton wrote:
> > On Wed, 9 Sep 2015 22:08:18 +0200
> > David Kalnischkies <da...@kalnischkies.de> wrote:
> > 
> > Just because it is not "OMG ITS COMPLETELY BROKEN" does not mean it
> > is not still broken. apt-get dist-upgrade basically wants to remove
> > my whole desktop. "apt-get install apt" still wants to remove
> > essential desktop apps: most or all of KDE and libreoffice, for
> > starters.
> 
> Be sure to do an upgrade (with --with-new-pkgs if you are still using
> apt-get) before the dist-upgrade. This way all packages will be
> upgraded that do not conflict with an installed one.

A dozen or so packages got through that way.

> You can then try to dist-upgrade. 

Which is still in basically the same state.

> If it does not work, you can try specifying package names you
> absolutely want to keep. Keep in mind that maybe not all those
> packages are installable, as some were forcefully broken in testing
> to ease the transition.

Only one cherry-pick worked, netting another dozen packages. Several
hundred to go. I guess I will just wait a few days and see if things
improve.

There was a narrow window there where the transition was working. I
have a laptop with Gnome, KDE, multiple other desktops, and a whole
crap-load of other stuff that upgraded flawlessly. Wait a couple days,
and the other laptop (the subject of this e-mail) is a mess.

> > But I would like to be able to recommend Debian as a desktop to my
> > Ubuntu-using friends. I personally do not consider a two+-year old
> > Debian Stable a reasonable desktop option. Therefore Debian Testing
> > must work for a reasonable person who is not a software engineer if
> > we are to compete with Ubuntu. This behavior does not make the cut.
> 
> It usually is. But this is the hardest transition since the libc
> transition, and it is a huge pain. It's not like this normally
> happens.

That is some comfort, I had not realized that recent events had already
become infamous. The reason I spoke up myself is I don't remember the
last time I saw such a mess on my own desktop (that did not involve my
own stupidity). Breaking the rolling release once in ten years is not
too bad.

Thanks,
Clayton

Bug#798460: apt: Testing transition broken

[clayton]

Package: apt
Version: 1.0.9.10
Severity: important

I am a Testing user. One of my machines is upgraded. A couple days later and I 
try to upgrade another with the gcc5 transition,
and apt is broken. "apt-get dist-upgrade" wants to remove 254 packages and 
"apt-get install apt" wants to remove 121 packages.

-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-4\.0\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-image-4\.1\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.0\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.1\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.0\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.1\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.0\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.1\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.0\.0-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.1\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.0\.0-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.1\.0-1-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.0\.0-2-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.1\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.0\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.1\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.0\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.1\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.0\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.1\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.0\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.1\.0-1-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Never-MarkAuto-Sections:: "oldlibs";
APT::Never-MarkAuto-Sections:: "restricted/oldlibs";
APT::Never-MarkAuto-Sections:: "universe/oldlibs";
APT::Never-MarkAuto-Sections:: "multiverse/oldlibs";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 4 --method 
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo 
> /dev/null";
APT::Default-Releast "testing";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Architectures:: "i386";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "1";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "2";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-9n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compressor::bzip2 "";
APT::Compressor::bzip2::Name "bzip2";
APT::Compressor::bzip2::Extension ".bz2";
APT::Compressor::bzip2::Binary "bzip2";
APT::Compressor::bzip2::Cost "3";
APT::Compressor::bzip2::CompressArg "";
APT::Compressor::bzip2::CompressArg:: "-9";
APT::Compressor::bzip2::UncompressArg "";
APT::Compressor::bzip2::UncompressArg:: "-d";
APT::Compressor::xz "";
APT::Compressor::xz::Name "xz";
APT::Compressor::xz::Extension ".xz";
APT::Compressor::xz::Binary "xz";
APT::Compressor::xz::Cost "4";
APT::Compressor::xz::CompressArg "";
APT::Compressor::xz::CompressArg:: "-6";
APT::Compressor::xz::UncompressArg "";
APT::Compressor::xz::UncompressArg:: "-d";
APT::Compressor::lzma "";
APT::Compressor::lzma::Name "lzma";
APT::Compressor::lzma::Extension ".lzma";
APT::Compressor::lzma::Binary "xz";
APT::Compressor::lzma::Cost "5";
APT::Compressor::lzma::CompressArg "";

Bug#787165: python-pip: some pip commands don't work: freeze, list, maybe others

[clayton]

Package: python-pip
Version: 1.5.6-6
Severity: important

For instance:

root@t410:~# pip freeze
Exception:
Traceback (most recent call last):
  File /usr/lib/python2.7/dist-packages/pip/basecommand.py, line 122, in main
status = self.run(options, args)
  File /usr/lib/python2.7/dist-packages/pip/commands/freeze.py, line 74, in 
run
req = pip.FrozenRequirement.from_dist(dist, dependency_links, 
find_tags=find_tags)
  File /usr/lib/python2.7/dist-packages/pip/__init__.py, line 299, in 
from_dist
assert len(specs) == 1 and specs[0][0] == '=='
AssertionError

Storing debug log for failure in /root/.pip/pip.log
root@t410:~# pip list
apsw (3.8.6.post1)
archivemail (0.9.0)
argparse (1.2.1)
BeautifulSoup (3.2.1)
beautifulsoup4 (4.1.3)
Exception:
Traceback (most recent call last):
  File /usr/lib/python2.7/dist-packages/pip/basecommand.py, line 122, in main
status = self.run(options, args)
  File /usr/lib/python2.7/dist-packages/pip/commands/list.py, line 80, in run
self.run_listing(options)
  File /usr/lib/python2.7/dist-packages/pip/commands/list.py, line 142, in 
run_listing
self.output_package_listing(installed_packages)
  File /usr/lib/python2.7/dist-packages/pip/commands/list.py, line 151, in 
output_package_listing
if dist_is_editable(dist):
  File /usr/lib/python2.7/dist-packages/pip/util.py, line 367, in 
dist_is_editable
req = FrozenRequirement.from_dist(dist, [])
  File /usr/lib/python2.7/dist-packages/pip/__init__.py, line 299, in 
from_dist
assert len(specs) == 1 and specs[0][0] == '=='
AssertionError


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

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

Versions of packages python-pip depends on:
ii  ca-certificates   20141019
ii  python2.7.9-1
ii  python-colorama   0.3.3-1
ii  python-distlib0.2.0-2
ii  python-html5lib   0.999-3
ii  python-pkg-resources  16.0-2
ii  python-requests   2.4.3-6
ii  python-setuptools 16.0-2
ii  python-six1.9.0-3
pn  python:anynone

Versions of packages python-pip recommends:
ii  build-essential  11.7
pn  python-dev-all   none
ii  python-wheel 0.24.0-1

python-pip 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#781167: claws-mail-pgpinline: pgpinline encrypts an e-mail, then cannot decrypt the same e-mail in it's own Sent folder

[clayton]

Package: claws-mail-pgpinline
Version: 3.11.1-3
Severity: normal

For e-mail in Sent folder, claws reports Couldn't decrypt: Decryption failed.

If I save the encrypted attachment and then do a gpg --decrypt filename 
then gpg reports 
gpg: decryption failed: secret key not available

No feedback yet from recipient as to whether he was able to decrypt.

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

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

Versions of packages claws-mail-pgpinline depends on:
ii  claws-mail   3.11.1-3
ii  claws-mail-pgpmime [claws-mail-pgpcore]  3.11.1-3
ii  libarchive13 3.1.2-11
ii  libassuan0   2.1.2-2
ii  libatk1.0-0  2.14.0-1
ii  libc62.19-15
ii  libcairo21.14.0-2.1
ii  libdb5.3 5.3.28-9
ii  libetpan17   1.5-2
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.5.2-3
ii  libgdk-pixbuf2.0-0   2.31.1-2+b1
ii  libglib2.0-0 2.42.1-1
ii  libgnutls-deb0-283.3.8-6
ii  libgpg-error01.17-3
ii  libgpgme11   1.5.1-6
ii  libgtk2.0-0  2.24.25-3
ii  liblockfile1 1.09-6
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpangoft2-1.0-01.36.8-3
ii  libsasl2-2   2.1.26.dfsg1-13
ii  zlib1g   1:1.2.8.dfsg-2+b1

claws-mail-pgpinline recommends no packages.

claws-mail-pgpinline 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#781167: gpg or gpg2

[Clayton]

Does claws use gpg or gpg2? I am seeing some odd errors when I try to
operate on my keyring with gpg instead of gpg2.


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

Bug#779432: ooniprobe: Error Opening file /usr/share/GeoIP/GeoLiteCity.dat

[clayton]

Package: ooniprobe
Version: 1.2.2-1
Severity: normal

running ooniresources --update-geoip without error does not correct this.

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

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

Versions of packages ooniprobe depends on:
ii  geoip-database   20150209-1
ii  python   2.7.8-3
ii  python-geoip 1.3.2-1
ii  python-ipaddr2.1.11-2
ii  python-openssl   0.14-1
ii  python-parsley   1.2-1
ii  python-pypcap1.1.2+debian-2.2
ii  python-scapy 2.2.0-1
ii  python-twisted   14.0.2-3
ii  python-txsocksx  1.13.0.3-1
ii  python-txtorcon  0.11.0-1
ii  python-yaml  3.11-2
ii  tor  0.2.5.10-1

Versions of packages ooniprobe recommends:
ii  python-dumbnet  1.12-6

Versions of packages ooniprobe suggests:
pn  geoip-database-contrib  none
ii  obfsproxy   0.2.12-1

-- 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#774137: tor: Tor fails to manage obfsproxy

[Clayton]

As promised, I just installed this configuration on another older
machine, a Thinkpad x60s which is even older than the x201i that is
failing. Also with an older install than the t410 where it is working.
The x60s is also not working, same symptoms.

So to summarize, we have working:

t410: fastest, with a newly installed OS

We have NOT working:

x201i, x60s: both with older installs, both slower machines

Everything up-to-date with the latest testing/Jessie, and a few
unstable packages.

Clayton


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

Bug#774137: tor: Tor fails to manage obfsproxy

[Clayton]

On Fri, 20 Feb 2015 12:02:14 +0100
Peter Palfrader wea...@debian.org wrote:

 On Tue, 30 Dec 2014, Clayton wrote:
 
  On Tue, 30 Dec 2014 11:16:29 +0100
  intrigeri intrig...@debian.org wrote:
  
   clayton wrote (29 Dec 2014 10:23:43 GMT) :
The communication stream of managed proxy '/usr/bin/obfsproxy'
is 'closed'. Most probably the managed proxy stopped running.
etc
   
Then I added the logging bits in the ClientTransportPlugin line
above. But, no /tmp/obfsproxy.log file is created. However, if
I run
   
/usr/bin/obfsproxy --log-min-severity info
--log-file /tmp/obfsproxy.log managed
   
straight from the command line, a /tmp/obfsproxy.log is created.
   
   Do you have AppArmor enabled?
  
  Nope, not a trace of it.
 
 I can't reproduce it.  Does that still happen on your system?  What
 does an strace -f report?  What is your complete and uncensored
 configuration?  What else is weird on your system?

As luck would have it, I just got a newer laptop and did a clean Jessie
install. My configuration works perfectly on the newly installed
machine.

On the old machine where things are not working, I updated everything.
Both machines are running an almost identical testing/Jessie setup
with a smattering of unstable packages, enforced in large part by
Puppet. I try to deviate from 'testing' as little as possible,
generally speaking.

I then purged both tor and obfsproxy, and re-installed. Still not
working.

My torrc (enforced by Puppet on both machines!) is very simple:

ClientTransportPlugin obfs3 exec /usr/bin/obfsproxy
--log-min-severity info --log-file /tmp/obfsproxy.log managed

UseBridges 1

Bridge obfs3 IP:port key
Bridge obfs3 IP:port key
Bridge obfs3 IP:port key

I can share the bridge details privately with you if it would be
helpful, but I re-iterate: this works on one of my machines.

The difference between the two machines is the broken one's install is
older, with the obvious consequences. I have at least one more machine
I am going to try this on, another day.

And now the final kick in the pants ;-) :

strace -o /tmp/tor-strace.log -f /usr/bin/tor
--defaults-torrc /usr/share/tor/tor-service-defaults-torrc

actually works! I get to Bootstrapped 100%: Done in the Tor log. But
if I then kill the strace'd process and go back and start Tor with
systemd, it fails again. I iterated a couple times, and it is
repeatable.

Perhaps an issue with systemd? Or a race condition (this is a slightly
older/slower machine, Thinkpad x201i)?

apt-get purge install sysvinit-core

and then reboot with sysvinit resulted in no gain. Tor still cannot
start obfsproxy, same symptoms. I am inclined to no longer suspect
systemd.

Clayton


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

Bug#774137: tor: Tor fails to manage obfsproxy

[Clayton]

On Wed, 25 Feb 2015 09:37:27 +0100
Peter Palfrader wea...@debian.org wrote:

 On Wed, 25 Feb 2015, Clayton wrote:
 
  And now the final kick in the pants ;-) :
  
  strace -o /tmp/tor-strace.log -f /usr/bin/tor
  --defaults-torrc /usr/share/tor/tor-service-defaults-torrc
  
  actually works! I get to Bootstrapped 100%: Done in the Tor log.
  But if I then kill the strace'd process and go back and start Tor
  with systemd, it fails again. I iterated a couple times, and it is
  repeatable.
 
 Do you have a /usr/sbin/aa-status?  If yes, and you run it, what's its
 exit status?

Nope, /usr/sbin/aa-status does not exist. And no apparmor installed
anywhere. I have another machine that is even a bit older and slower, I
will try on that tomorrow if I get a chance.

Clayton


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

Bug#778886: Acknowledgement (claws-mail: dropdown menu bar has disappeared, cannot get back)

[Clayton]

On Mon, 23 Feb 2015 09:44:39 +
Paul cl...@thewildbeast.co.uk wrote:

 F12 toggles the display of the menu bar.

Thanks Paul, indeed. Then this becomes a documentation bug report
against this page

http://www.claws-mail.org/manual/claws-mail-manual.html#ap_keyboard

I do believe. I did RTFM, and it did not help.

Thanks again,
Clayton


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

Bug#778886: Acknowledgement (claws-mail: dropdown menu bar has disappeared, cannot get back)

[Clayton]

Just restored .claws-mail/ from backup, which fixed the problem. Then
diff'ed the restored/fixed and the broken dirs, and found this:

mainwin_menubar=0

in clawsrc of the broken configuration. To re-iterate, I did nothing
KNOWINGLY that changed this value. My best guess for a culprit is
possibly an accidental drag'n'drop of something on the window by my lame
touchpad.

Clayton


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

Bug#778886: claws-mail: dropdown menu bar has disappeared, cannot get back

[clayton]

Package: claws-mail
Version: 3.11.1-3
Severity: important

I think this may have been a touchpad accident, but am not entirely sure what 
happened exactly.
Suddenly no menu bar, everything else is there including the button bar right 
below it.

And I can find no way to get it back. (I tried stopping and restarting, of 
course.)

This is quite serious, as I can no longer access settings, filters, account 
manager, many things.

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

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

Versions of packages claws-mail depends on:
ii  libarchive13 3.1.2-10
ii  libassuan0   2.1.2-2
ii  libatk1.0-0  2.14.0-1
ii  libc62.19-13
ii  libcairo21.14.0-2.1
ii  libcompfaceg11:1.5.2-5
ii  libdb5.3 5.3.28-7~deb8u1
ii  libdbus-1-3  1.8.12-3
ii  libdbus-glib-1-2 0.102-1
ii  libenchant1c2a   1.6.0-10.1
ii  libetpan17   1.5-2
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.5.2-2
ii  libgdk-pixbuf2.0-0   2.31.1-2+b1
ii  libglib2.0-0 2.42.1-1
ii  libgnutls-deb0-283.3.8-5
ii  libgpg-error01.17-3
ii  libgpgme11   1.5.1-6
ii  libgtk2.0-0  2.24.25-1
ii  libice6  2:1.0.9-1+b1
ii  libldap-2.4-22.4.40-4
ii  liblockfile1 1.09-6
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpangoft2-1.0-01.36.8-3
ii  libpisock9   0.12.5-dfsg-1
ii  libsasl2-2   2.1.26.dfsg1-12
ii  libsm6   2:1.2.2-1+b1
ii  xdg-utils1.1.0~rc1+git20111210-7.3
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages claws-mail recommends:
ii  aspell-en [aspell-dictionary]  7.1-0-1.1
ii  claws-mail-i18n3.11.1-3
ii  xfonts-100dpi  1:1.0.3
ii  xfonts-75dpi   1:1.0.3

Versions of packages claws-mail suggests:
ii  chromium [www-browser]   40.0.2214.91-1
pn  claws-mail-doc   none
pn  claws-mail-tools none
ii  iceweasel [www-browser]  31.4.0esr-1
ii  konqueror [www-browser]  4:4.14.2-1
ii  kwrite   4:4.14.2-2
ii  w3m [www-browser]0.5.3-19

-- 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#774137: tor: Tor fails to manage obfsproxy

[Clayton]

On Tue, 30 Dec 2014 11:16:29 +0100
intrigeri intrig...@debian.org wrote:

 clayton wrote (29 Dec 2014 10:23:43 GMT) :
  The communication stream of managed proxy '/usr/bin/obfsproxy' is
  'closed'. Most probably the managed proxy stopped running.
  etc
 
  Then I added the logging bits in the ClientTransportPlugin line
  above. But, no /tmp/obfsproxy.log file is created. However, if I run
 
  /usr/bin/obfsproxy --log-min-severity info
  --log-file /tmp/obfsproxy.log managed
 
  straight from the command line, a /tmp/obfsproxy.log is created.
 
 Do you have AppArmor enabled?

Nope, not a trace of it.


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

Bug#774137: tor: Tor fails to manage obfsproxy

[clayton]

Package: tor
Version: 0.2.6.1-alpha-1
Severity: normal

(Note: I tried the version of Tor in testing first.)

Here is the config line from my torrc:

ClientTransportPlugin obfs3 exec /usr/bin/obfsproxy --log-min-severity info 
--log-file /tmp/obfsproxy.log managed

And here is what I get in /var/log/tor/log on every restart:

The communication stream of managed proxy '/usr/bin/obfsproxy' is 'closed'. 
Most probably the managed proxy 
stopped running. etc

Then I added the logging bits in the ClientTransportPlugin line above. But, no 
/tmp/obfsproxy.log
file is created. However, if I run

/usr/bin/obfsproxy --log-min-severity info --log-file 
/tmp/obfsproxy.log managed

straight from the command line, a /tmp/obfsproxy.log is created.

From this I infer that Tor is never getting to the point of starting obfsproxy.
Perhaps there is an issue with the Debian environment?

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages tor depends on:
ii  adduser 3.113+nmu3
ii  libc6   2.19-13
ii  libevent-2.0-5  2.0.21-stable-1.1
ii  libseccomp2 2.1.1-1
ii  libssl1.0.0 1.0.1j-1
ii  lsb-base4.1+Debian13+nmu1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages tor recommends:
ii  logrotate3.8.7-1+b1
ii  tor-geoipdb  0.2.5.10-1
ii  torsocks 2.0.0-3

Versions of packages tor suggests:
pn  apparmor-utils none
pn  mixmaster  none
ii  obfsproxy  0.2.12-1
ii  privoxy3.0.21-4
pn  socat  none
pn  tor-armnone
pn  xul-ext-torbutton  none

-- Configuration Files:
/etc/tor/torrc changed [not included]

-- 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#768407: cryptsetup: dm-crypt disk unlocks on older Debian, does not on current testing

[Clayton]

As the original reporter, I can confirm that it is indeed fixed now for
me. Thanks guys!

Clayton


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

Bug#770678: claws-mail-pgpinline: pgpinline does not automatically encrypt / decrypt attachments

[clayton]

Package: claws-mail-pgpinline
Version: 3.11.1-1
Severity: wishlist

This is the first time I have ever had the opportunity to used PGP-encrypted 
e-mail,
and it is mostly two thumbs up on claws!

But: the organization I am working with (mostly) uses Outlook with a gpg4o 
plugin which is apparently
not PGP-MIME compatible. On there end Outlook is not decrypting my PGP-MIME 
e-mail, they have to decrypt manually.
E-mail text only works properly between us if I use PGP-inline to communicate 
with them.

However, on there side, this gpg4o thing DOES automatically encypt / decrypt 
attachments, which puts
me at a bit of a disadvantage because our PGP-inline DOES NOT, and I cannot use 
PGP-MIME

So if possible, it would be very convenient for me if PGP-inline were to handle 
attachments automatically.

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

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

Versions of packages claws-mail-pgpinline depends on:
ii  claws-mail   3.11.1-1
ii  claws-mail-pgpmime [claws-mail-pgpcore]  3.11.1-1
ii  libarchive13 3.1.2-9
ii  libassuan0   2.1.2-2
ii  libatk1.0-0  2.14.0-1
ii  libc62.19-13
ii  libcairo21.14.0-2.1
ii  libdb5.3 5.3.28-6
ii  libetpan17   1.5-1
ii  libfontconfig1   2.11.0-6.1
ii  libfreetype6 2.5.2-2
it  libgdk-pixbuf2.0-0   2.31.1-2+b1
ii  libglib2.0-0 2.42.0-2
ii  libgnutls-deb0-283.3.8-4
ii  libgpg-error01.17-2
ii  libgpgme11   1.5.1-6
ii  libgtk2.0-0  2.24.25-1
ii  liblockfile1 1.09-6
ii  libpango-1.0-0   1.36.8-2
ii  libpangocairo-1.0-0  1.36.8-2
ii  libpangoft2-1.0-01.36.8-2
ii  libsasl2-2   2.1.26.dfsg1-12
ii  zlib1g   1:1.2.8.dfsg-2

claws-mail-pgpinline recommends no packages.

claws-mail-pgpinline 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#768407: cryptsetup: dm-crypt disk unlocks on older Debian, does not on current testing

[clayton]

Package: cryptsetup
Version: 2:1.6.6-3
Severity: important

I have an old dm-crypt partition that I have been using for long-term backups.
This is the crypttab:

backcrypt /dev/sdb2 none 
cipher=aes-cbc-plain,size=256,hash=ripemd160,noauto,loud

which I normally start with

cryptdisks_start backcrypt

Suddenly (or not so suddenly, I have not accessed this partition in several 
months)
when I try to mount the result of the above:

# mount -t ext3 /dev/mapper/backcrypt /media/backcrypt/
mount: wrong fs type, bad option, bad superblock on /dev/mapper/backcrypt,

cryptdisks_start generates no errors either in the terminal or in the log, but 
something is not right.
(Note that this is not a passphrase issue because I always copypaste the 
passphrase from keepassx.
And I tried several times. Not finger problems.)

I just happen to have an old bootable USB of Debian that has not been updated 
in (many?) months.
When I boot that disk, with the same crypttab, and an older cryptsetup, the 
partition unlocks and mounts just fine.

Something silent and fairly destructive has changed in the default behavior of 
dm-crypt.
I very nearly wrote the partition off as corrupted before I thought of trying 
to mount it
with an old Debian installation.

I assume that something needs to change in my crypttab, but I have no idea what.

-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.16-3-amd64 root=/dev/mapper/x201i--vg-root ro quiet

-- /etc/crypttab
sda5_crypt UUID=cd5aa5f3-5cf8-45a2-b174-c21bc18b0c47 none luks

backcrypt /dev/sdb2 none 
cipher=aes-cbc-plain,size=256,hash=ripemd160,noauto,loud

-- /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# file system mount point   type  options   dump  pass
/dev/mapper/x201i--vg-root /   ext4errors=remount-ro 0   1
# /boot was on /dev/sda1 during installation
UUID=efbc99f2-a47e-45e5-840f-9e2326011560 /boot   ext2defaults  
  0   2
/dev/mapper/x201i--vg-home /home   ext4defaults0   2
/dev/mapper/x201i--vg-swap_1 noneswapsw  0   0

/dev/x201i-vg/protected-x201i /protected ext4 defaults 0 0
/dev/x201i-vg/scratch-x201i /scratch ext4 defaults 0 0

# /dev/mapper/backcrypt /media/backcrypt ext3 rw,user 0 0

-- lsmod
Module  Size  Used by
cbc12696  1 
usb_storage56215  1 
bnep   17431  2 
bluetooth 374429  5 bnep
6lowpan_iphc   16588  1 bluetooth
tun26385  2 
binfmt_misc16949  1 
pci_stub   12429  1 
vboxpci23077  0 
vboxnetadp 25443  0 
vboxnetflt 23324  0 
vboxdrv   340067  3 vboxnetadp,vboxnetflt,vboxpci
ipt_MASQUERADE 12594  8 
xt_recent  17246  1 
xt_comment 12427  16 
xt_owner   12459  2 
iptable_nat12646  1 
nf_nat_ipv412912  1 iptable_nat
ipt_REJECT 12465  4 
xt_addrtype12557  4 
xt_mark12453  1 
iptable_mangle 12536  1 
xt_tcpudp  12527  73 
xt_CT  12842  22 
iptable_raw12524  1 
xt_multiport   12518  4 
nf_conntrack_ipv4  18455  53 
nf_defrag_ipv4 12483  1 nf_conntrack_ipv4
xt_conntrack   12681  30 
ipt_ULOG   12819  0 
xt_NFLOG   12462  0 
nfnetlink_log  17201  1 xt_NFLOG
xt_LOG 17171  8 
nf_nat_tftp12422  0 
nf_nat_snmp_basic  16904  0 
nf_conntrack_snmp  12443  3 nf_nat_snmp_basic
nf_nat_sip 17053  0 
nf_nat_pptp12562  0 
nf_nat_proto_gre   12517  1 nf_nat_pptp
nf_nat_irc 12454  0 
nf_nat_h32316935  0 
nf_nat_ftp 12460  0 
nf_nat_amanda  12424  0 
ts_kmp 12535  5 
nf_conntrack_amanda12437  3 nf_nat_amanda
nf_nat 18241  11 
nf_nat_ftp,nf_nat_irc,nf_nat_sip,nf_nat_amanda,ipt_MASQUERADE,nf_nat_proto_gre,nf_nat_h323,nf_nat_ipv4,nf_nat_pptp,nf_nat_tftp,iptable_nat
nf_conntrack_sane  12428  2 
nf_conntrack_tftp  12433  3 nf_nat_tftp
nf_conntrack_sip   26053  3 nf_nat_sip
nf_conntrack_proto_udplite12931  0 
nf_conntrack_proto_sctp17268  0 
nf_conntrack_pptp  12619  3 nf_nat_pptp
nf_conntrack_proto_gre13024  1 nf_conntrack_pptp
nf_conntrack_netlink35433  0 
nfnetlink  12989  2 nfnetlink_log,nf_conntrack_netlink
nf_conntrack_netbios_ns12445  2 
nf_conntrack_broadcast12365  2 nf_conntrack_netbios_ns,nf_conntrack_snmp
nf_conntrack_irc   12427  3 nf_nat_irc
nf_conntrack_h323  58618  5 nf_nat_h323
nf_conntrack_ftp   16783  3 nf_nat_ftp
nf_conntrack   87432  30 

Bug#768407: cryptsetup: dm-crypt disk unlocks on older Debian, does not on current testing

[Clayton]

Hi Milan,

On Fri, 07 Nov 2014 11:08:31 +0100
Milan Broz gmazyl...@gmail.com wrote:

  backcrypt /dev/sdb2 none
  cipher=aes-cbc-plain,size=256,hash=ripemd160,noauto,loud
 
 If it is not passphrase, are you sure these were the correct
 parameters? Who added them there? (mainly check mode:
 -plain /-essiv:sha256, key size 128/256 ?)

I created that crypttab in 2010 under the advice of Jonas Meurer per

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586120

and my /etc is under git/etckeeper. That file has not changed since the
initial install on this machine more than a year ago, and it has worked
many times before  since then on this and other machines. Until now.

I will try those other parameters next time I get a chance, but I am
not optimistic because

 (it should be, these are old cryptsetup plain defaults but you should
 check old crypttab backups for sure... 

like I said that file has not changed. The same partition unlocks
using an older cryptsetup on an older Debian and EXACTLY the same
crypttab. Therefore, something ails the new version of cryptsetup -or-
there is some kind of new undocumented default behavior.

 really better use LUKS to avoid this problem, 

Yes, I use LUKS on all new installs, but this disk was built many years
ago. I am sure there will be a few Wheezy -- Jessie upgrades with
similar legacy disks.

 or even better - if you have systtem which opens
 it correctly, use cryptsetup status for active device and check it)
 
 See
 https://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions#8._Issues_with_Specific_Versions_of_cryptsetup

Like you said,

cipher=aes-cbc-plain,size=256,hash=ripemd160

are the old old defaults and should work. And they still do. With a
slightly older version of crytpsetup, same encrypted partition.

Clayton


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

Bug#758794: Acknowledgement (taskcoach: app freezes when I try to edit any task)

[Clayton]

Today after an apt-get upgrade, network-manager also stopped working
despite multiple restarts, forcing me to reboot. Post reboot, both
network-manager and taskcoach now work properly. This now looks like a
messed-up transition of some Python dependency.


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

Bug#758794: taskcoach: app freezes when I try to edit any task

[clayton]

Package: taskcoach
Version: 1.4.0-1
Severity: important

This is what I see everytime in the terminal at the moment of the freeze:

$ taskcoach
QDBusConnection: session D-Bus connection created before QCoreApplication. 
Application may misbehave.

This happens for both double-clicking the task in the list, or right clicking 
the task
and then selecting edit. Every time.

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

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

Versions of packages taskcoach depends on:
ii  fonts-dejavu  2.34-1
ii  libxss1   1:1.2.2-1
ii  python2.7.8-1
ii  python-chardet2.2.1-2
ii  python-dateutil   1.5+dfsg-1
ii  python-keyring4.0-1
ii  python-lockfile   1:0.8-2
ii  python-pyparsing  2.0.2+dfsg1-1
ii  python-squaremap  1:1.0.4-1
ii  python-twisted14.0.0-2
ii  python-wxgtk2.8   2.8.12.1+dfsg2-1
ii  python-wxversion  2.8.12.1+dfsg2-1
ii  python-xdg0.25-4
ii  x11-utils 7.7+2

Versions of packages taskcoach recommends:
ii  libavahi-compat-libdnssd1  0.6.31-4
ii  libgnome-2-0   2.32.1-5
ii  python-notify  0.1.1-3

Versions of packages taskcoach suggests:
pn  espeak   none
ii  python-kde4  4:4.13.3-1

-- 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#749312: Bitcoin excessive overeating

[Clayton]

On Mon, 16 Jun 2014 23:23:40 -0400
Scott Howard showard...@gmail.com wrote:

 Sorry to hear about bitcoin crashing. If you download the client from
 bitcoin.org, does it also do that? To be safe, backup/move your
 ~/.bitcoin directory before playing around just to be extra safe.
 ~Scott

Just tried the upstream tarball as you requested, and it behaves exactly
the same. My most vulnerable laptop (the Thinkpad) overheats and shuts
down within a couple of minutes.

If anyone else is running into this, I have found a way to mitigate
this behavior: start the client in a terminal with the -par=1 parameter,
ie.

bitcoin-qt -par=1 

Apparently par=1 limits the bitcoin client to just one thread, so it
can only max out the CPU on one core. This renders my Toshiba quite
reliable, and my Thinkpad often manages to not shutdown.

Clayton


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

Bug#752522: rss2email: does nothing after today's upgrade

[clayton]

Package: rss2email
Version: 1:3.8-1
Severity: important

As of today's upgraded version,

r2e run
r2e list

do absolutely nothing except give me a new prompt. Not even an error message.

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

Kernel: Linux 3.14-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

Versions of packages rss2email depends on:
ii  python-xdg  0.25-4
ii  python2.7   2.7.7-2
ii  python3-feedparser  5.1.3-2
ii  python3-html2text   3.200.3-2
pn  python3:any none

rss2email recommends no packages.

Versions of packages rss2email suggests:
pn  esmtp  none

-- 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#752522: rss2email: does nothing after today's upgrade

[Clayton]

On Tue, 24 Jun 2014 15:29:09 +0200
Etienne Millon m...@emillon.org wrote:

 rss2email 3.x changed its config file format, and now reads from a
 different file with a different syntax. The r2e-migrate tool can help
 you transfer your data.
 
 However, an improvement is possible: it is possible to patch r2e to
 check if a 2.x database exists and write a message about it. I'm
 retitling the bug and setting the severity accordingly.
 
 This breaking change is described in
 /usr/share/doc/rss2email/NEWS.Debian.gz ; you can install the
 apt-listchanges package which will warn you when you upgrade a package
 that contains such an incompatible change.
 
 Feel free to file a new bug if the migration does not work.
 
 Sorry for the inconvenience, and thanks for your bug report!

Thanks, r2e-migrate works nicely.

Clayton


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

Bug#686625: chromium: Must be able to get user data directory!

[Clayton]

On Sat, 31 May 2014 18:13:55 +0200
Jan Braun janbr...@gmx.net wrote:

 Clayton schrob:
  Now, in LXDE, when I:
  sux other_user
  chromium
  There are no error messages in the terminal.
  The chromium window does not appear in the display.
  But the chromium process is still there according to ps.
 
 Thank you.
 What happens when you don't use sux, but su and set
 DISPLAY/XAUTHORITY, or su -p and adjust HOME?

su -p and adjust HOME? --

[0618/182317:FATAL:chrome_main_delegate.cc(372)] Check failed:
process_type.empty(). Unable to get the user data directory for
process type: zygote

There were no other error messages, and like with sux, the
process is there but no window displays

su and set DISPLAY/XAUTHORITY

Must confess I am not sure what exactly to do with XAUTHORITY

Clayton


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

Bug#686625: chromium: Must be able to get user data directory!

[Clayton]

Hi Jan,

I still have sux installed from before it disappeared. Current behavior
has changed, but is still broken. Now, in LXDE, when I:

sux other_user
chromium

There are no error messages in the terminal.
The chromium window does not appear in the display.
But the chromium process is still there according to ps.

Clayton


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

Bug#749312: bitcoin-qt: overheating -- shutdown, every time

[clayton]

Package: bitcoin-qt
Version: 0.9.1-1
Severity: important

This is new behavior. I have two laptops (one ThinkPad, one Toshiba, neither of 
them particularly new)
which overheat and shut down every time I run bitcoin-qt. I have tried to slow 
things down with trickle,
but then the client segfaults, also every time!!

The excessive use of CPU is in itself perhaps just a minor pathology, but
I am tagging this important because it creates the unfortunate situation I am 
now in: I am going 
to have to try and SOMEHOW get the clients updated such that I can move the 
bitcoin out to electrum.

One expects a degree of stability and reliability from the reference client.
For me at least, that is currently being shaken.

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

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

Versions of packages bitcoin-qt depends on:
ii  libboost-chrono1.54.0   1.54.0-5
ii  libboost-filesystem1.54.0   1.54.0-5
ii  libboost-program-options1.54.0  1.54.0-5
ii  libboost-system1.54.0   1.54.0-5
ii  libboost-thread1.54.0   1.54.0-5
ii  libc6   2.18-5
ii  libdb5.3++  5.3.28-3
ii  libgcc1 1:4.9.0-2
ii  libminiupnpc8   1.6-3
ii  libprotobuf82.5.0-9
ii  libqrencode33.4.2-1
ii  libqt4-dbus 4:4.8.6+dfsg-1
ii  libqt4-network  4:4.8.6+dfsg-1
ii  libqt4-xml  4:4.8.6+dfsg-1
ii  libqtcore4  4:4.8.6+dfsg-1
ii  libqtgui4   4:4.8.6+dfsg-1
ii  libssl1.0.0 1.0.1g-3
ii  libstdc++6  4.9.0-2

bitcoin-qt recommends no packages.

bitcoin-qt 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#733288: Acknowledgement (bitcoin-qt: Failed to write block at 6 days behind)

[Clayton]

Update: I have been sharing my blockchain between two machines, using
Bittorent Sync to copy changes from one to the other. I have stopped
doing that and now bitcoin-qt works again on both machines, after an
rsync to repair the blockchain on the broken machine (reported by this
bug report).

Apparently bitcoin-qt cannot handle nor recover from something Bittorent
Sync is doing, which is probably not a good thing, but IMO not a fatal
flaw.

IMO this bug report could be downgraded or closed.


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

Bug#733288: bitcoin-qt: Failed to write block at 6 days behind

[clayton]

Package: bitcoin-qt
Version: 0.8.6-1
Severity: important

My bitcoin client reported blockchain corruption yesterday and spent most of 
yesterday rebuilding the blockchain. Today it got the point of 6 days behind, 
and 
now repeatedly quits with the error Failed to write block.

None of the file systems on this machine is full, the closest to full is 
showing 
90%. There do not appear to be any permission problems, and in fact the client 
has 
been doing a lot of writing in the past couple of days, up to this point.

With -debug turned on, there is nothing obviously interesting in the logs. 

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

Kernel: Linux 3.11-2-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 bitcoin-qt depends on:
ii  libboost-filesystem1.54.0   1.54.0-4+b1
ii  libboost-program-options1.54.0  1.54.0-4+b1
ii  libboost-system1.54.0   1.54.0-4+b1
ii  libboost-thread1.54.0   1.54.0-4+b1
ii  libc6   2.17-97
ii  libdb5.1++  5.1.29-6
ii  libgcc1 1:4.8.2-1
ii  libminiupnpc8   1.6-3
ii  libqrencode33.4.2-1
ii  libqt4-dbus 4:4.8.5+git192-g085f851+dfsg-2
ii  libqt4-network  4:4.8.5+git192-g085f851+dfsg-2
ii  libqtcore4  4:4.8.5+git192-g085f851+dfsg-2
ii  libqtgui4   4:4.8.5+git192-g085f851+dfsg-2
ii  libssl1.0.0 1.0.1e-4
ii  libstdc++6  4.8.2-1

bitcoin-qt recommends no packages.

bitcoin-qt 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#718550: Acknowledgement (testing: apache upgrade has broken web interface)

[Clayton]

Tnanks, this did it for me too:

/etc/apache2/conf-enabled/backuppc.conf - /etc/backuppc/apache.conf


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

Bug#718550: testing: apache upgrade has broken web interface

[clayton]

Package: backuppc
Version: 3.2.1-5.1
Severity: important

I run Debian testing. A new apache came down today, and the results for

http://server60gtinc/backuppc/

are now

Not Found
The requested URL /backuppc/ was not found on this server.
Apache/2.4.6 (Debian) Server at server60gtinc Port 80

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

Kernel: Linux 3.9-1-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages backuppc depends on:
ii  adduser 3.113+nmu3
ii  apache2 2.4.6-2
ii  apache2-bin [httpd] 2.4.6-2
ii  bzip2   1.0.6-4
ii  debconf [debconf-2.0]   1.5.50
ii  dpkg1.16.10
ii  iputils-ping3:20121221-1
ii  libarchive-zip-perl 1.30-7
ii  libc6   2.17-7
pn  libcompress-zlib-perl   none
ii  libtime-modules-perl2011.0517-1
ii  libwww-perl 6.05-1
ii  perl [libdigest-md5-perl]   5.14.2-21
ii  postfix [mail-transport-agent]  2.10.0-3
ii  samba-common-bin2:3.6.16-2
ii  smbclient   2:3.6.16-2
ii  tar 1.26+dfsg-6
ii  ucf 3.0027+nmu1

Versions of packages backuppc recommends:
ii  libfile-rsyncp-perl  0.70-1
ii  libio-dirent-perl0.05-1
ii  openssh-client [ssh-client]  1:6.2p2-6
ii  rrdtool  1.4.7-2
ii  rsync3.0.9-4

Versions of packages backuppc suggests:
pn  par2   none
ii  w3m [www-browser]  0.5.3-8

-- Configuration Files:
/etc/backuppc/hosts changed:
hostdhcpusermoreUsers # --- do not edit this line
x60s0   backuppc
satellite   0   backuppc


-- debconf information:
* backuppc/configuration-note:
  backuppc/restart-webserver: true
* backuppc/reconfigure-webserver: apache2


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

Bug#714430: apt-cacher-ng: suddenly stopped working the last few days

[Clayton]

On Tue, 9 Jul 2013 11:36:47 +0200
Eduard Bloch e...@gmx.de wrote:

 tags 714430 +moreinfo
 thanks
 
 Hallo,
 * clayton [Sat, Jun 29 2013, 03:48:22PM]:
 
  This worked up until a few days ago.
  If I comment out Acquire::http { Proxy http://x60s:3142;; }; in
  apt.conf, I do not get the errors below:
  
  Err http://ftp.debian.org testing/main i386 Packages  
502  Bad Gateway [IP: 127.0.1.1 3142]  
  Err http://ftp.debian.org testing/contrib i386 Packages  
502  Bad Gateway [IP: 127.0.1.1 3142]  
  Err http://ftp.debian.org testing/non-free i386 Packages  
502  Bad Gateway [IP: 127.0.1.1 3142]  
  Fetched 105 kB in 14s (7,013 B/s)  
  W: Failed to fetch
  http://ftp.debian.org/debian/dists/testing/main/binary-i386/Packages
  502  Bad Gateway [IP: 127.0.1.1 3142]  
 
 If this ever happens again, please do me a favor and send some
 information from the server.
 
  - a list of open file handles ( lsof | grep ^apt-ca )
  - a list of all running threads ( ps -eLf | grep apt-ca )
  - a memory dump (made with the gcore tool, compress the file
afterwards... or let't discuss later how to transfer if gets too
 big)

Hi Eduard,

I would be delighted to. As you seem to have guessed, this behavior has
since spontaneously gone away, and apt-cacher-ng is back to it's
reliable self.

'Til next time,
Clayton


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

Bug#714530: miro: locking up hard

[clayton]

Package: miro
Version: 4.0.4-1
Severity: important

Recently (since python updates?) Miro has become close to unusable for me. It 
very often
locks up such that I have to kill the process. This

2013-06-30 21:56:19,629 INFO root: Starting auto downloader...
2013-06-30 21:56:19,950 INFO root: this platform has the built-in 
autoupdate parser disabled.  Skipping.
/usr/lib/pymodules/python2.7/miro/plat/frontends/widgets/miroappindicator.py:155:
 Warning: 
/build/buildd-glib2.0_2.36.1-2build1-i386-ERPr_E/glib2.0-2.36.1/./gobject/gsignal.c:2475:
 signal `child-added' is invalid for instance `0xed45600' of type `GtkMenu'
  self.indicator.set_menu(popup_menu)

is generally the last thing I see in the terminal.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.9-1-686-pae (SMP w/2 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 miro depends on:
ii  gstreamer0.10-ffmpeg1:0.10.13-dmo1
ii  gstreamer0.10-plugins-bad   0.10.23-7.1
ii  gstreamer0.10-plugins-base  0.10.36-1.1
ii  gstreamer0.10-plugins-good  0.10.31-3+nmu1
ii  gstreamer0.10-x 0.10.36-1.1
ii  libatk1.0-0 2.8.0-2
ii  libavcodec537:0.10.3-dmo1
ii  libavformat53   7:0.10.3-dmo1
ii  libavutil51 8:1.0.7-dmo1
ii  libc6   2.17-3
ii  libcairo2   1.12.14-4
ii  libfontconfig1  2.9.0-7.1
ii  libfreetype62.4.9-1.1
ii  libgdk-pixbuf2.0-0  2.28.2-1
ii  libglib2.0-02.36.1-2build1
ii  libgtk2.0-0 2.24.18-1
ii  libjavascriptcoregtk-1.0-0  1.8.1-3.4
ii  libpango1.0-0   1.32.5-5+b1
ii  libsoup2.4-12.38.1-2
ii  libwebkitgtk-1.0-0  1.8.1-3.4
ii  libx11-62:1.6.0-1
ii  miro-data   4.0.4-1
ii  python  2.7.5-2
ii  python-dbus 1.2.0-2
ii  python-gconf2.28.1+dfsg-1
ii  python-glade2   2.24.0-3+b1
ii  python-gst0.10  0.10.22-3
ii  python-gtk2 2.24.0-3+b1
ii  python-libtorrent   0.15.10-1+b1
ii  python-mutagen  1.20-1
ii  python-pycurl   7.19.0-7
ii  python-pysqlite22.6.3-3
ii  python-support  1.0.15
ii  python-webkit   1.1.8-3

Versions of packages miro recommends:
pn  python-psyco  none

Versions of packages miro suggests:
ii  ffmpeg  8:1.2.1-dmo3
pn  ffmpeg2theora   none
ii  gstreamer0.10-plugins-ugly  0.10.19-2+b2
pn  libavahi-compat-libdnssd1   none
ii  python-notify   0.1.1-3
ii  ttf-dejavu  2.33+svn2514-3

-- 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#714430: apt-cacher-ng: suddenly stopped working the last few days

[clayton]

Package: apt-cacher-ng
Version: 0.7.13-1
Severity: important

This worked up until a few days ago.
If I comment out Acquire::http { Proxy http://x60s:3142;; }; in apt.conf,
I do not get the errors below:

Err http://ftp.debian.org testing/main i386 Packages  
  502  Bad Gateway [IP: 127.0.1.1 3142]  
Err http://ftp.debian.org testing/contrib i386 Packages  
  502  Bad Gateway [IP: 127.0.1.1 3142]  
Err http://ftp.debian.org testing/non-free i386 Packages  
  502  Bad Gateway [IP: 127.0.1.1 3142]  
Fetched 105 kB in 14s (7,013 B/s)  
W: Failed to fetch 
http://ftp.debian.org/debian/dists/testing/main/binary-i386/Packages  502  Bad 
Gateway [IP: 127.0.1.1 3142]  
  
W: Failed to fetch 
http://ftp.debian.org/debian/dists/testing/contrib/binary-i386/Packages  502  
Bad Gateway [IP: 127.0.1.1 3142]  
  
W: Failed to fetch 
http://ftp.debian.org/debian/dists/testing/non-free/binary-i386/Packages  502  
Bad Gateway [IP: 127.0.1.1 3142]  
  
E: Some index files failed to download. They have been ignored, or old ones 
used instead.

-- Package-specific info:

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (800, 'testing')
Architecture: i386 (i686)

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

Versions of packages apt-cacher-ng depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.50
ii  dpkg   1.16.10
ii  libbz2-1.0 1.0.6-4
ii  libc6  2.17-3
ii  libgcc11:4.8.1-2
ii  liblzma5   5.1.1alpha+20120614-2
ii  libstdc++6 4.8.1-2
ii  libwrap0   7.6.q-24
ii  zlib1g 1:1.2.8.dfsg-1

Versions of packages apt-cacher-ng recommends:
ii  avahi-daemon  0.6.31-2
ii  ed1.6-2
ii  perl  5.14.2-21

Versions of packages apt-cacher-ng suggests:
ii  curl  7.31.0-2
ii  doc-base  0.10.5
ii  libfuse2  2.9.2-4
ii  wget  1.14-2

-- Configuration Files:
/etc/apt-cacher-ng/backends_debian changed:
http://mirrors.163.com/debian/
http://debian.bjtu.edu.cn/debian/

/etc/apt-cacher-ng/security.conf [Errno 13] Permission denied: 
u'/etc/apt-cacher-ng/security.conf'

-- debconf information:
  apt-cacher-ng/gentargetmode: No automated setup


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

Bug#707192: gpodder: cannot find config after python upgrade

[Clayton]

On Wed, 8 May 2013 08:58:04 +0200 (CEST)
Thomas Perl t...@thp.io wrote:

 Hi Clayton,
 
 On Wed, 8 May 2013, clayton wrote:
  Yesterday I used gpodder, and it was normal.
  Last night I did an apt-get upgrade, and a lot of packages came
  down, including some Python packages, but as I recall, not a new
  gpodder.
 
  Today when I start gpodder it cannot find it's old config, my
  podcasts are all gone and it is pretending that it is a new
  installation.
 
 Yes, gPodder was probably upgraded from version 2.x to 3.x, requiring
 a manual database upgrade. You can do this via
 gpodder-migrate2tres, an utility included in the gPodder 3
 distribution.

Yep, that worked nicely, thanks!

Clayton


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

Bug#707192: gpodder: cannot find config after python upgrade

[clayton]

Package: gpodder
Version: 3.5.1-1
Severity: important

Yesterday I used gpodder, and it was normal.
Last night I did an apt-get upgrade, and a lot of packages came down,
including some Python packages, but as I recall, not a new gpodder.

Today when I start gpodder it cannot find it's old config, my podcasts are all 
gone
and it is pretending that it is a new installation.

I run Debian testing, so last night's upgrade was the first dump of new stuff 
after
the freeze was lifted.

-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 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 gpodder depends on:
ii  python  2.7.3-4
ii  python-dbus 1.1.1-1
ii  python-feedparser   5.1.2-1
ii  python-gtk2 2.24.0-3+b1
ii  python-mygpoclient  1.7-1
ii  python-support  1.0.15
ii  python-webkit   1.1.8-2

Versions of packages gpodder recommends:
ii  dbus-x11 1.6.8-1
pn  libqtwebkit-qmlwebkitplugin  none
ii  python-gst0.10   0.10.22-3
ii  python-simplejson2.6.2-1

Versions of packages gpodder suggests:
ii  gnome-bluetooth  3.4.2-1
ii  mplayer  3:1.1-dmo9
pn  python-eyed3 none

-- 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#706438: installation-report: Perfect install on Toshiba Satellite C675

[clayton]

Package: installation-reports
Version: 2.49
Severity: normal
Tags: d-i

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

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

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


-- Package-specific info:

Boot method: CD
Image version: debian-wheezy-DI-rc1-amd64-netinst.iso
Date: mid-April, 2013

Machine: Toshiba Satellite C675
Partitions: df -Tl will do; the raw partition table is preferred

# df -Tl
Filesystem  Type 1K-blocks Used Available Use% 
Mounted on
rootfs  rootfs 9611492  6080544   3042708  67% /
udevdevtmpfs 102400 10240   0% /dev
tmpfs   tmpfs   396972  748396224   1% /run
/dev/mapper/satellite-root  ext4   9611492  6080544   3042708  67% /
tmpfs   tmpfs 51200  5120   0% 
/run/lock
tmpfs   tmpfs   793940 3040790900   1% 
/run/shm
/dev/sda1   ext223319121397199353  10% /boot
/dev/mapper/satellite-home  ext4  20642428  3071268  16522584  16% /home
/dev/mapper/satellite-protected ext4  30963708 19487084   9903760  67% 
/protected
/dev/mapper/satellite-scratch   ext4 410785072 95461760 294456652  25% 
/scratch

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:  [O]
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:  [ ]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

Lately I have been doing LVM over full-hard-drive encryption, which the 
installer supports 
nicely in automatic mode. However, I find the 10G root partition a little small 
for a 
desktop machine, and ideally I would like to dip into manual mode and tweak 
that a bit 
bigger. However, I find manual mode extremely obtuse, and just didn't bother 
this last 
time.

I also did this install on a 500G drive. It took more then 24 hours for the 
encryption 
process to go through and wipe the drive. (At least that is what I think it was 
doing.)
Minimum there should be a warning about this, and ideally it would be nice to 
skip it 
with the option of doing it manually (for non-root partitions) later. This is a 
personal 
laptop, and I am not guarding military secrets. ;-) 24 hours seems to be a bit 
much.

-- 

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=7.0 (wheezy) - installer build 20130211
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux satellite 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core 
Processor Family DRAM Controller [8086:0104] (rev 09)
lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:fc70]
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd 
Generation Core Processor Family Integrated Graphics Controller [8086:0106] 
(rev 09)
lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:fc70]
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: Toshiba America Info Systems Device [1179:fc76]
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: Toshiba America Info Systems Device [1179:fc76]
lspci -knn: Kernel driver in use: ehci_hcd
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: Toshiba America Info Systems Device [1179:fc74]
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: 

Bug#706438: installation-report: Perfect install on Toshiba Satellite C675

[Clayton]

On Tue, 30 Apr 2013 23:23:54 +0100
Miguel Figueiredo el...@debianpt.org wrote:

 Hi,
 
 [...]
 It took more then 24 hours for the encryption
  process to go through and wipe the drive. (At least that is what I
  think it was doing.) Minimum there should be a warning about this,
  and ideally it would be nice to skip it with the option of doing it
  manually (for non-root partitions) later.
 
 hitting cancel while the partition it's being wiped, skips the 
 exhaustive wipe and jumps to the next step of the installation.
 
 BTW, this suggestion seems to be the same as in #678015.

Yes, that is exactly the same issue. And note the author said:

I noticed the Cancel button after a few hours, but because I
was unsure of what exactly it would  cancel, and whether it was
a required or optional step of the process, I opted not to
risk wasting all the time already invested and didn't cancel
anything.

If one does not know what exactly the thing is doing, and what the
consequences of hitting cancel might be, I (for one) would not be
inclined to risk losing hours of install time hitting cancel and then
having to start all over again.

Of course, I know different now, but the average user who does this on
a big drive for the first time will not.

Clayton


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

Bug#686625: Acknowledgement (chromium: Must be able to get user data directory!)

[Clayton]

I just discovered this does not happen on the XFCE desktop, but ALWAYS
happens on the LXDE desktop. Perhaps this should be handed over to the
LXDE people?


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

Bug#646125: empathy: Certificate complaints of every connect despite selecting remember

[Clayton Falzone]

Running XFCE desktop with gnome-keyring and suggested/recommended packages.
Adding the aforementioned .desktop files to autostart with XFCE desktop
works

/etc/xdg/autostart/gnome-keyring-gpg.desktop
/etc/xdg/autostart/gnome-keyring-pkcs11.desktop
/etc/xdg/autostart/gnome-keyring-secrets.desktop
/etc/xdg/autostart/gnome-keyring-ssh.desktop


-Clayton

Bug#646125: empathy: Certificate complaints of every connect despite selecting remember

[Clayton Falzone]

That might explain, the pinned certificates are stored in
gnome-keyring. You should take care of starting it properly.

Cheers

Laurent Bigonville

I am similarly affected by this bug. Installing the gnome-keyring
package does not fix the behavior (though it does cause the passwords
to be remembered, it does not prevent empathy from asking to remember
the certificate each time)


-Clayton

Bug#693772: apt-cacher-ng: InRelease is expired.... Updates for this repository will not be applied

[clayton]

Package: apt-cacher-ng
Version: 0.7.10-1
Severity: normal

Some time ago I removed http.debian.net from all my sources.lists because it 
seems to be problematic when used with acng.

Today, however, despite an apt-get upgrade working correctly on my i386 machine 
(where acng is also hosted)
on my amd64 machine I get the following:

# apt-get update
Hit http://security.debian.org testing/updates InRelease

Hit http://security.debian.org testing/updates/main amd64 Packages  
  
Ign http://ppa.launchpad.net precise InRelease  

Hit http://www.deb-multimedia.org testing InRelease 
 
Hit http://mirrors.163.com testing InRelease

Hit http://mirrors.163.com unstable InRelease   
 
Hit http://security.debian.org testing/updates/contrib amd64 Packages   
 
Hit http://ppa.launchpad.net precise Release.gpg
 
Hit http://http.debian.net testing/updates InRelease
 
E: Release file for 
http://http.debian.net/debian-security/dists/testing/updates/InRelease is 
expired (invalid since 94d 18h 8min 15s). Updates for this repository will not 
be applied.

I have tried to remove every reference I can find to http.debian.net 
everywhere, in both acng and on the amd64 machine
throwing the error, but to no avail. I cannot get rid of the above error.

-- Package-specific info:

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'unstable')
Architecture: i386 (i686)

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

Versions of packages apt-cacher-ng depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.46
ii  dpkg   1.16.9
ii  libbz2-1.0 1.0.6-4
ii  libc6  2.13-35
ii  libgcc11:4.7.2-4
ii  liblzma5   5.1.1alpha+20120614-1
ii  libstdc++6 4.7.2-4
ii  libwrap0   7.6.q-24
ii  zlib1g 1:1.2.7.dfsg-13

Versions of packages apt-cacher-ng recommends:
ii  ed1.6-2
ii  perl  5.14.2-15

Versions of packages apt-cacher-ng suggests:
ii  doc-base  0.10.4
ii  libfuse2  2.9.0-2

-- Configuration Files:
/etc/apt-cacher-ng/acng.conf [Errno 2] No such file or directory: 
u'/etc/apt-cacher-ng/acng.conf'
/etc/apt-cacher-ng/backends_debian changed:
http://mirrors.163.com/debian/
http://debian.bjtu.edu.cn/debian/

/etc/apt-cacher-ng/security.conf [Errno 13] Permission denied: 
u'/etc/apt-cacher-ng/security.conf'

-- debconf information:
  apt-cacher-ng/gentargetmode: No automated setup


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

Bug#687589: libimage-base-bundle-perl: Spelling error in control file (package description) W/ Patch

[Clayton Casciato]

Package: libimage-base-bundle-perl
Version: 1.0.7-3
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu quantal ubuntu-patch

Dear Maintainer,

  * Spelling fix (Requred  Required) in control file (package description)

Thanks for considering the patch.


-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5.3-030503-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
=== modified file 'debian/changelog'

=== modified file 'debian/control'
--- debian/control	2008-08-15 16:01:00 +
+++ debian/control	2012-09-14 01:43:58 +
@@ -21,4 +21,4 @@
   Image::Xpm
   Image::Xbm
  .
- Requred by Image::Info to parse xpm and xbm files.
+ Required by Image::Info to parse xpm and xbm files.

Bug#687590: liblqr: Three spelling errors in control file (package description) W/ Patch

[Clayton Casciato]

Package: liblqr
Version: 0.4.1-2
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu quantal ubuntu-patch

Dear Maintainer,

  * Grammer Fix (permits to  permits one to - thrice) in control file 
(package description)

Thanks for considering the patch.


-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5.3-030503-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
=== modified file 'debian/changelog'

=== modified file 'debian/control'
--- debian/control	2012-06-04 18:40:42 +
+++ debian/control	2012-09-14 01:48:44 +
@@ -38,7 +38,7 @@
* The automatic feature detection algorithm can be tuned by
  selecting among different energy gradient functions
* Reports progress through a customizable interface
-   * A signalling system permits to cleanly handle errors
+   * A signalling system permits one to cleanly handle errors
  .
  The library implements the algorithm described in the paper Seam
  Carving for Content-Aware Image Resizing by Shai Avidan and Ariel
@@ -76,7 +76,7 @@
* The automatic feature detection algorithm can be tuned by
  selecting among different energy gradient functions
* Reports progress through a customizable interface
-   * A signalling system permits to cleanly handle errors
+   * A signalling system permits one to cleanly handle errors
  .
  The library implements the algorithm described in the paper Seam
  Carving for Content-Aware Image Resizing by Shai Avidan and Ariel
@@ -114,7 +114,7 @@
* The automatic feature detection algorithm can be tuned by
  selecting among different energy gradient functions
* Reports progress through a customizable interface
-   * A signalling system permits to cleanly handle errors
+   * A signalling system permits one to cleanly handle errors
  .
  The library implements the algorithm described in the paper Seam
  Carving for Content-Aware Image Resizing by Shai Avidan and Ariel

Bug#687591: libmoosex-meta-typeconstraint-forcecoercion-perl: Grammer error in control file (package description) W/ Patch

[Clayton Casciato]

Package: libmoosex-meta-typeconstraint-forcecoercion-perl
Version: 0.01-1
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu quantal ubuntu-patch

Dear Maintainer,

  * Grammer Fix (allows to  allows one to) in control file (package 
description)

Thanks for considering the patch.


-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5.3-030503-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
=== modified file 'debian/changelog'

=== modified file 'debian/control'
--- debian/control	2009-05-18 20:49:35 +
+++ debian/control	2012-09-14 01:53:02 +
@@ -16,7 +16,7 @@
 Depends: ${perl:Depends}, ${misc:Depends}, libnamespace-autoclean-perl,
   libmoose-perl
 Description: Perl modeule for forcing coercion when validating type constraints
- MooseX::Meta::TypeConstraint::ForceCoercion allows to wrap any
+ MooseX::Meta::TypeConstraint::ForceCoercion allows one to wrap any
  Moose::Meta::TypeConstraint in a way that will force coercion of the
  value when checking or validating a value against it.
 

Bug#687592: libmoosex-semiaffordanceaccessor-perl: Spelling error in control file (package description) W/ Patch

[Clayton Casciato]

Package: libmoosex-semiaffordanceaccessor-perl
Version: 0.09-1
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu quantal ubuntu-patch

Dear Maintainer,

  * Spelling Fix (explictly  explicitly) in control file (package 
description)

Thanks for considering the patch.


-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5.3-030503-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
=== modified file 'debian/changelog'

=== modified file 'debian/control'
--- debian/control	2011-04-21 20:43:25 +
+++ debian/control	2012-09-14 01:56:20 +
@@ -23,7 +23,7 @@
  policy for the loading class so that methods are separated into accessors
  (which have the same name as the attribute) and mutators (via set_ methods).
  .
- It is compatible with existing naming schemes, since attributes that explictly
+ It is compatible with existing naming schemes, since attributes that explicitly
  provide a reader or writer name are left unchanged. The terminology
  semi-affordance is inspired by David Wheeler's Class::Meta module (see
  libclass-meta-perl).

Bug#687593: liborigin: Spelling error in control file (package description) W/ Patch

[Clayton Casciato]

Package: liborigin
Version: 20080225-2.1
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu quantal ubuntu-patch

Dear Maintainer,

  * Spelling Fix (informations  information) in control file (package 
description) W/ Patch

Thanks for considering the patch.


-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5.3-030503-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
=== modified file 'debian/changelog'

=== modified file 'debian/control'
--- debian/control	2008-03-15 08:27:53 +
+++ debian/control	2012-09-14 02:10:07 +
@@ -19,7 +19,7 @@
  data analysis capabilities and includes several new tools that simplify common
  operations.
  .
- See http://www.originlab.com for more informations about OriginLab Origin.
+ See http://www.originlab.com for more information about OriginLab Origin.
  .
  This package contains the development files.
 

Bug#687467: libgtk2-spell-perl: Grammer error in control file (package description) W/ Patch

[Clayton Casciato]

Package: libgtk2-spell-perl
Version: 1.04-1
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu quantal ubuntu-patch

Dear Maintainer,
  * Grammer Fix (allows to  allows one to) in control file (package 
description)

Thanks for considering the patch.


-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5.3-030503-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
=== modified file 'debian/changelog'

=== modified file 'debian/control'
--- debian/control	2012-01-20 20:10:35 +
+++ debian/control	2012-09-13 00:09:48 +
@@ -19,7 +19,7 @@
  libglib-perl (= 2:1.240), libgtk2-perl (= 1.00)
 Pre-Depends: dpkg (= 1.15.6)
 Description: Perl interface to the GtkSpell library
- libgtk2-spell-perl allows to use the GtkSpell library in Perl applications
+ libgtk2-spell-perl allows one to use the GtkSpell library in Perl applications
  using a Gtk2/GNOME interface. It can be used in concert with Gtk2::TextView
  to provide highlighting of mis-spelled words and a right click pop-up menu
  with possible corrections.

Bug#687468: libhtml-formfu-model-dbic-perl: Grammer error in control file (package description) W/ Patch

[Clayton Casciato]

Package: libhtml-formfu-model-dbic-perl
Version: 0.09002-1
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu quantal ubuntu-patch

Dear Maintainer,

  * Grammer Fix (allows to  allows one to) in control file (package 
description)

Thanks for considering the patch.


-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5.3-030503-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
=== modified file 'debian/changelog'

=== modified file 'debian/control'
--- debian/control	2011-07-16 09:35:37 +
+++ debian/control	2012-09-13 00:12:45 +
@@ -33,5 +33,5 @@
  HTML::FormFu is a HTML form creation, rendering and validation framework.
  .
  This package contains the HTML::FormFu::Model::DBIC module, providing
- integration with DBIx::Class. It allows to set a form's default values from a
+ integration with DBIx::Class. It allows one to set a form's default values from a
  DBIx::Class row object and to update the database from a submitted form.

Bug#687351: hgsvn: Grammer Error in control file (package description) W/ Patch

[Clayton Casciato]

Package: hgsvn
Version: 0.1.8-1
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu quantal ubuntu-patch

Dear Maintainer,

  * Grammer Fix (allows to  allows one to) in control file (package 
description)

Thanks for considering the patch.


-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5.3-030503-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
=== modified file 'debian/changelog'

=== modified file 'debian/control'
--- debian/control	2010-02-04 17:21:35 +
+++ debian/control	2012-09-12 03:24:33 +
@@ -16,7 +16,7 @@
   python-elementtree | python (= 2.5)
 Provides: ${python:Provides}
 Description: Scripts to work locally on Subversion checkouts using Mercurial
- This set of scripts allows to work locally on Subversion-managed projects
+ This set of scripts allows one to work locally on Subversion-managed projects
  using the Mercurial distributed version control system.
  .
  Why use Mercurial ? You can do local (disconnected) work, pull the latest

Bug#687352: icecc-monitor: Grammer/Spelling Error in control file (package description) W/ Patch

[Clayton Casciato]

Package: icecc-monitor
Version: 2.0~svn951472-2
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu quantal ubuntu-patch

Dear Maintainer,

  * Grammer/Spelling Fix (informations  information) in control file 
(package description)

Thanks for considering the patch.


-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5.3-030503-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
=== modified file 'debian/changelog'

=== modified file 'debian/control'
--- debian/control	2009-04-11 09:57:31 +
+++ debian/control	2012-09-12 03:33:30 +
@@ -17,4 +17,4 @@
  a view on the distributed compile network, which jobs run where and details
  about jobs and nodes (statistics and overview information).
  .
- See the 'icecc' package for more informations.
+ See the 'icecc' package for more information.

Bug#687353: kbibtex: Spelling error in control file (package description) W/ Patch

[Clayton Casciato]

Package: kbibtex
Version: 0.4-2
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu quantal ubuntu-patch

Dear Maintainer,

  * Spelling Fix (ressources  resources) in control file (package 
description)

Thanks for considering the patch.


-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5.3-030503-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
=== modified file 'debian/changelog'

=== modified file 'debian/control'
--- debian/control	2011-07-18 09:29:48 +
+++ debian/control	2012-09-12 03:36:11 +
@@ -20,7 +20,7 @@
  can be used as a standalone program, but can also be embedded into other KDE 
  applications (e.g. as bibliography editor into Kile).
  .
- KBibTeX can query online ressources (e.g. Google scholar) via customizable 
+ KBibTeX can query online resources (e.g. Google scholar) via customizable 
  search URLs. It is also able to import complete datasets from NCBI Pubmed.
  It also supports tagging references with keywords and manages references to
  local files.

Bug#687354: kcollectd: Two grammer errors in control file (package description) W/ Patch

[Clayton Casciato]

Package: kcollectd
Version: 0.9-2.1
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu quantal ubuntu-patch

Dear Maintainer,

  * Grammer Fix (allows to  allows one to - twice) in control file 
(package description)

Thanks for considering the patch.


-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5.3-030503-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
=== modified file 'debian/changelog'

=== modified file 'debian/control'
--- debian/control	2011-08-25 00:30:43 +
+++ debian/control	2012-09-12 03:39:15 +
@@ -11,6 +11,6 @@
 Depends: ${shlibs:Depends}, ${misc:Depends}, collectd
 Suggests: khelpcenter4
 Description: simple collectd graphing frontend for KDE
- Kcollectd is a graphical KDE-frontend to collectd that allows to view
- RRD files that have been created by collectd. It allows to easily
+ Kcollectd is a graphical KDE-frontend to collectd that allows one to view
+ RRD files that have been created by collectd. It allows one to easily
  navigate in the data with the mouse and can be used as a chart recorder.