Bug#926509: Package orphaned?

[nemo Inis]

On Wed, 14 Aug 2019 21:25:35 -0400 John Scott  wrote:
> On Wednesday, August 14, 2019 9:20:13 PM EDT you wrote:
> > I'm not being snarky here - this is a safety issue.
> How so? It doesn't seem to have any security issues

Quick excerpt from the release notes for the versions unavailable on Debian:

Improve resilience against memory attacks - overwrite memory before free [#3020]
Fix data loss due to not reading all database attachments if duplicates exist 
[#3180]
Fix database deletion when using unsafe saves to a different file system [#2889]
Warn user if deleting entries that are referenced. [#1744]
Linux: Prevent Klipper from storing secrets in clipboard [#1969]

Bug#926509: Package orphaned?

[nemo Inis]

Has this package been orphaned? It seems unlikely that a security tool such as 
a password
manager would lag one year behind upstream's current version?

Should we just call it quit and switch to the upstream AppImage?

I'm not being snarky here - this is a safety issue. A word of reassurance (or 
of any other
news) from the maintainer would be welcome.

Bug#916968: w3mman support for section number during keyword search

[Nemo Inis]

Package: w3m
Version: 0.5.3-36+b1
Severity: wishlist
Tags: patch

Dear Maintainer,

I've noticed that w3mman does not support specifying a section number during a
keyword search, i.e., the equivalent of 'man -s N -k keyword'

Here's a little patch that does that. It is now possible to type:
w3mman 1 -k text
to get a list of only the section 1 man pages relating to text. A section
number entered in the interactive form will also be respected.

cheers



diff --git a/scripts/w3mman/w3mman.1.in b/scripts/w3mman/w3mman.1.in
index 8c433a7..b85b0a0 100644
--- a/scripts/w3mman/w3mman.1.in
+++ b/scripts/w3mman/w3mman.1.in
@@ -30,6 +30,8 @@ w3mman \- an interface to the on-line reference manuals via
w3m(1)
 .B w3mman
 [
 .BI \-M " path"
+] [
+.I section
 ]
 .BI \-k " keyword"
 .br
diff --git a/scripts/w3mman/w3mman.in b/scripts/w3mman/w3mman.in
index 6a27e70..2a33438 100644
--- a/scripts/w3mman/w3mman.in
+++ b/scripts/w3mman/w3mman.in
@@ -6,8 +6,8 @@ $SCRIPT = 'file:///$LIB/w3mman2html.cgi';

 sub usage {
   ($_ = $0) =~ s@.*/@@;
-  print STDERR "$_ [-M ] [[] ]\n";
-  print STDERR "$_ [-M ] [-k ]\n";
+  print STDERR "$_ [-M ] [] ]\n";
+  print STDERR "$_ [-M ] [] [-k ]\n";
   print STDERR "$_ [-l ]\n";
   exit 1;
 }
@@ -20,7 +20,8 @@ while (@ARGV) {
 $ENV{'MANPATH'} = shift @ARGV;
   } elsif (/^-k$/) {
 @ARGV || ();
-$query = "?keyword=" . _encode(shift @ARGV);
+if ( $query eq "" ) { $query = "?quit=ok"; }
+$query .= "=" . _encode(shift @ARGV);
   } elsif (/^-l$/) {
 @ARGV || ();
 $query = "?quit=ok=" . _encode(shift @ARGV);
@@ -28,11 +29,11 @@ while (@ARGV) {
   } elsif (/^-/) {
 ();
   } elsif (/^\d/ || $_ eq 'n') {
-@ARGV || ();
-$query = "?quit=ok=" . _encode(shift @ARGV);
+if ( $query eq "" ) { $query = "?quit=ok"; }
 $query .= "=" . _encode($_);
   } else {
-$query = "?quit=ok=" . _encode($_);
+if ( $query eq "" ) { $query = "?quit=ok"; }
+$query .= "=" . _encode($_);
   }
 }

diff --git a/scripts/w3mman/w3mman2html.cgi.in
b/scripts/w3mman/w3mman2html.cgi.in
index 2cd00f9..d660681 100644
--- a/scripts/w3mman/w3mman2html.cgi.in
+++ b/scripts/w3mman/w3mman2html.cgi.in
@@ -23,17 +23,23 @@ if ((! $query{"man"}) && (! $query{"local"})) {
   if ($query{"keyword"}) {
 $keyword = $query{"keyword"};
 $k = _quote($keyword);
+if ($query{"section"}) {
+  $section = $query{"section"};
+  $sectionopt = "-s $section ";
+} else {
+  $sectionopt = "";
+}
 print <
-man -k $k
+man $sectionopt-k $k
 
-man -k $k
+man $sectionopt-k $k
 
 EOF
 $keyword =~ s:([^-\w\200-\377.,])::g;
-open(F, "$MAN -k $keyword 2> /dev/null |");
+open(F, "$MAN $sectionopt -k $keyword 2> /dev/null |");
 while() {
   chop;
   $_ = _quote($_);
@@ -58,10 +64,10 @@ Content-Type: text/html
 
 
 
-Manual:
-Section:
-Keyword:
- 
+Manual:
+Section:
+Keyword:
+ 
 






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

Kernel: Linux 4.18.0-3-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, 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 w3m depends on:
ii  libc6  2.28-2
ii  libgc1c2   1:7.6.4-0.4
ii  libgpm21.20.7-5
ii  libssl1.1  1.1.1a-1
ii  libtinfo6  6.1+20181013-1
ii  zlib1g 1:1.2.11.dfsg-1

Versions of packages w3m recommends:
ii  ca-certificates  20170717

Versions of packages w3m suggests:
pn  cmigemo   
ii  curl  7.62.0-1
pn  dict  
pn  dict-wn   
pn  dictd 
pn  libsixel-bin  
ii  man-db2.8.4-3
ii  mime-support  3.61
hi  mpv   0.29.1-1
pn  w3m-el
pn  w3m-img   
ii  wget  1.19.5-2
ii  xdg-utils 1.1.3-1
ii  xsel  1.2.0+git9bfc13d.20180109-1

-- no debconf information

Bug#916297: reportbug: crash after using "Display modified configuration files"

[nemo Inis]

That. IS. the. Full. Traceback.

And speaking of making lives much easier, get off my back.



On 13/12/2018 15.57, Sandro Tosi wrote:
> Just. Report. The. Full. Traceback.
> 
> That would make our lives so much easier
> 
> Thanks!
> 
> On Thu, Dec 13, 2018, 18:45 nemo Inis  
>> Sandro,
>>
>> 1) that one 'TypeError' line IS the 'unaltered, complete reportbug
>> traceback'
>>
>> 2) I don't think the specific package matters, only that it had a modified
>> config file. e.g. in
>> my case apt-cacher-ng, or apache2, or 
>>
>> 3) the bug is in reportbug/ui/gtk2_ui.py, in the class 'SystemPage(Page)'
>> which defines
>> 'on_child_exited' with two parameters when it should be three (the third
>> parameter being the
>> child's exit status code, as per Vte.Terminal.signals.child_exited
>> documentation for Vte 2.91)
>>
>>
>>
>> On 12/12/2018 12.13, Sandro Tosi wrote:
>>>> When reporting a bug, reportbug sometimes issues a warning that "The
>> following
>>>> configuration files have been modified:" (for the package being reported
>>>> against).
>>>> It then gives the option to Send the modified files, or "Display
>> modified
>>>> configuration files (exit with "q")"
>>>>
>>>> Clicking that button displays the pertinent configuration files OK, but
>> after
>>>> pressing q to exit back to the bug, reportbug dies with:
>>>>
>>>> TypeError: on_child_exited() takes 2 positional arguments but 3 were
>> given
>>>
>>> please report the unaltered. complete reportbug traceback.
>>>
>>> Does it happen for a specific package only or for multiple ones? in
>>> any case, report the exact package this is happening on
>>>
>>
> 

Bug#916297: reportbug: crash after using "Display modified configuration files"

[nemo Inis]

Sandro,

1) that one 'TypeError' line IS the 'unaltered, complete reportbug traceback'

2) I don't think the specific package matters, only that it had a modified 
config file. e.g. in
my case apt-cacher-ng, or apache2, or 

3) the bug is in reportbug/ui/gtk2_ui.py, in the class 'SystemPage(Page)' which 
defines
'on_child_exited' with two parameters when it should be three (the third 
parameter being the
child's exit status code, as per Vte.Terminal.signals.child_exited 
documentation for Vte 2.91)



On 12/12/2018 12.13, Sandro Tosi wrote:
>> When reporting a bug, reportbug sometimes issues a warning that "The 
>> following
>> configuration files have been modified:" (for the package being reported
>> against).
>> It then gives the option to Send the modified files, or "Display modified
>> configuration files (exit with "q")"
>>
>> Clicking that button displays the pertinent configuration files OK, but after
>> pressing q to exit back to the bug, reportbug dies with:
>>
>> TypeError: on_child_exited() takes 2 positional arguments but 3 were given
> 
> please report the unaltered. complete reportbug traceback.
> 
> Does it happen for a specific package only or for multiple ones? in
> any case, report the exact package this is happening on
> 

Bug#916297: reportbug: crash after using "Display modified configuration files"

[Nemo Inis]

Package: reportbug
Version: 7.5.1
Severity: important

Dear Maintainer,

When reporting a bug, reportbug sometimes issues a warning that "The following
configuration files have been modified:" (for the package being reported
against).
It then gives the option to Send the modified files, or "Display modified
configuration files (exit with "q")"

Clicking that button displays the pertinent configuration files OK, but after
pressing q to exit back to the bug, reportbug dies with:

TypeError: on_child_exited() takes 2 positional arguments but 3 were given




-- Package-specific info:
** Environment settings:
EDITOR="vi"
PAGER="less -iXE"
INTERFACE="gtk2"

** /home/jpd/.reportbugrc:
reportbug_version "6.2.1"
mode novice
ui gtk2
realname "Nemo Inis"
email "nemoi...@hotmail.com"
no-cc
header "X-Debbugs-CC: nemoi...@hotmail.com"
smtphost smtp.telus.net

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

Kernel: Linux 4.17.0-3-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, 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 reportbug depends on:
ii  apt1.8.0~alpha2
ii  python33.6.7-1
ii  python3-reportbug  7.5.1
ii  sensible-utils 0.0.12

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
pn  debconf-utils  
pn  debsums
pn  dlocate
pn  emacs24-bin-common | emacs25-bin-common
ii  exim4  4.91-8
ii  exim4-daemon-light [mail-transport-agent]  4.91-8+b1
ii  file   1:5.34-2
ii  gnupg  2.2.11-1
pn  python3-urwid  
pn  reportbug-gtk  
ii  xdg-utils  1.1.3-1

Versions of packages python3-reportbug depends on:
ii  apt1.8.0~alpha2
ii  file   1:5.34-2
ii  python33.6.7-1
ii  python3-apt1.7.0
ii  python3-debian 0.1.33
ii  python3-debianbts  2.7.2
ii  python3-requests   2.20.0-2

python3-reportbug suggests no packages.

-- no debconf information

Bug#916296: apt-cacher-ng: distkill.pl script referred in documentation is not included

[Nemo Inis]

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

Dear Maintainer,

Sections 7.2 and 8.2 refer to a distkill.pl script which allows hand-pruning
unneeded distribution releases from the archive.
That script is not included in the current version of apt-cacher-ng.



-- Package-specific info:

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

Kernel: Linux 4.17.0-3-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, 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 apt-cacher-ng depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.69
ii  dpkg   1.19.2
ii  libbz2-1.0 1.0.6-9
ii  libc6  2.27-8
ii  libgcc11:8.2.0-9
ii  liblzma5   5.2.2-1.3
ii  libssl1.1  1.1.1a-1
ii  libstdc++6 8.2.0-9
ii  libsystemd0239-13
ii  libwrap0   7.6.q-27
ii  lsb-base   10.2018112800
ii  zlib1g 1:1.2.11.dfsg-1

apt-cacher-ng recommends no packages.

Versions of packages apt-cacher-ng suggests:
pn  avahi-daemon  
pn  doc-base  
ii  libfuse2  2.9.8-2

-- Configuration Files:
/etc/apt-cacher-ng/acng.conf changed [not included]
/etc/apt-cacher-ng/security.conf [Errno 13] Permission denied: 
'/etc/apt-cacher-ng/security.conf'

-- debconf information excluded

Bug#784968: temporary workaround

[nemo Inis]

Filing bugs against colord is currently disabled at

and it's not listed either in freedesktop's gitlab instance at 
.

So for people desperate to get these warnings off their journals, you can limit 
the daemon's
logging level to errors only. Use 'systemctl edit colord' to create an override 
for colord:


[Service]
# colord spams the system log with 'Cannot adopt OID in ...' messages
# whenever a disk is plugged-in or out. see debian bug #784968
LogLevelMax=err

Bug#908924: possible fix

[nemo Inis]

> Is someone could tell us the good way in debian to patch our kernel to
> fix this issue?

There is some info in the debian wiki. Or you can wait: that commit is in 
kernel 4.19.1, the
next LTS kernel, according to:



Should come out soon.

Bug#908924: possible fix

[nemo Inis]

I have not tried it, though.

https://bugzilla.kernel.org/show_bug.cgi?id=200709#c6
https://lkml.org/lkml/2018/10/14/62

Bug#908924: dma_direct_map_sg: overflow on USB access after upgrade to kernel 4.18

[nemo Inis]

On 2018-09-16 01:16, Salvatore Bonaccorso wrote:
> Does the issue still happens with the current version in experimental
> (4.19~rc3-1~exp1)?

Yes, same exact behavior. I think we need a fix for the kernel bug I linked to 
above.

Bug#771545: Possible cause

[nemo Inis]

I just hit this (with reportbug 7.5.0).

I had started reportbug from a terminal inside my XFCE session, and after the 
GUI froze, I
found this on the terminal:

Use sudo to read the kernel log?

I replied "y", and sudo prompted me for my password. After giving it, reportbug 
worked normally.

So I think the issue is that reportbug's GUI is doing I/O on its controlling 
terminal, and sits
there waiting for a reply that never comes (because the user is looking at the 
GUI).

Bug#908924: dma_direct_map_sg: overflow on USB access after upgrade to kernel 4.18

[Nemo Inis]

Package: src:linux
Version: 4.18.6-1
Severity: important

Dear Maintainer,

Plugged my Kobo eReader's USB plug into a machine just upgraded from kernel
4.17 (4.17.17-1) to 4.18 (4.18.6-1), and got 112,738,316 kernel messages in the
the system log:

kernel: ehci-pci :00:1a.7: dma_direct_map_sg: overflow
0x000216f3c000+4096 of device mask 

Downgrading to 4.17 fixes this.

Relevant lspci output:

00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI
Controller #2 (rev 02) (prog-if 20 [EHCI])
Subsystem: Gigabyte Technology Co., Ltd 82801I (ICH9 Family) USB2 EHCI
Controller
Flags: bus master, medium devsel, latency 0, IRQ 18
Memory at fb204000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci


I think this is https://bugzilla.kernel.org/show_bug.cgi?id=200709




-- Package-specific info:
** Version:
Linux version 4.18.0-1-686-pae (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-29)) #1 SMP Debian 4.18.6-1 (2018-09-06)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.18.0-1-686-pae 
root=UUID=54edf79e-1432-4836-8ea6-c744253ba306 ro fbcon=scrollback:128k quiet 
ipv6.disable=1

** Tainted: PO (4097)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.

** Kernel log:
[7.535676] PM: Image not found (code -22)
[7.560085] cryptd: max_cpu_qlen set to 1000
[7.710342] EXT4-fs (sde1): mounted filesystem with ordered data mode. Opts: 
(null)
[7.871897] systemd[1]: systemd 239 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid)
[7.888134] systemd[1]: Detected architecture x86.
[7.891501] systemd[1]: Set hostname to .
[8.068161] random: systemd: uninitialized urandom read (16 bytes read)
[8.068233] systemd[1]: Listening on Journal Audit Socket.
[8.068273] random: systemd: uninitialized urandom read (16 bytes read)
[8.068351] systemd[1]: Listening on Journal Socket (/dev/log).
[8.068370] random: systemd: uninitialized urandom read (16 bytes read)
[8.068456] systemd[1]: Listening on Journal Socket.
[8.070712] systemd[1]: Starting Load Kernel Modules...
[8.071637] systemd[1]: Mounting POSIX Message Queue File System...
[8.073195] systemd[1]: Starting Journal Service...
[8.073487] systemd[1]: Set up automount Arbitrary Executable File Formats 
File System Automount Point.
[8.081443] loop: module loaded
[8.087374] it87: Found IT8718F chip at 0x290, revision 4
[8.087394] it87: Beeping is supported
[8.092733] sd 2:0:0:0: Attached scsi generic sg0 type 0
[8.092784] sd 3:0:0:0: Attached scsi generic sg1 type 0
[8.092831] sd 4:0:0:0: Attached scsi generic sg2 type 0
[8.092870] sd 5:0:0:0: Attached scsi generic sg3 type 0
[8.092910] sd 7:0:0:0: Attached scsi generic sg4 type 0
[8.092951] sr 9:0:0:0: Attached scsi generic sg5 type 5
[8.093300] EXT4-fs (sde1): re-mounted. Opts: errors=remount-ro,commit=300
[8.112927] RPC: Registered named UNIX socket transport module.
[8.112928] RPC: Registered udp transport module.
[8.112929] RPC: Registered tcp transport module.
[8.112930] RPC: Registered tcp NFSv4.1 backchannel transport module.
[8.156231] nvidia: loading out-of-tree module taints kernel.
[8.156241] nvidia: module license 'NVIDIA' taints kernel.
[8.156242] Disabling lock debugging due to kernel taint
[8.170688] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=io+mem
[8.171674] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on 
minor 0
[8.171684] NVRM: loading NVIDIA UNIX x86 Kernel Module  340.107  Thu May 24 
21:04:34 PDT 2018
[8.240244] systemd-journald[296]: Received request to flush runtime journal 
from PID 1
[8.615060] snd_hda_intel :01:00.1: Disabling MSI
[8.615069] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[8.650522] snd_hda_codec_realtek hdaudioC0D2: autoconfig for ALC889A: 
line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
[8.650525] snd_hda_codec_realtek hdaudioC0D2:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[8.650527] snd_hda_codec_realtek hdaudioC0D2:hp_outs=1 
(0x1b/0x0/0x0/0x0/0x0)
[8.650528] snd_hda_codec_realtek hdaudioC0D2:mono: mono_out=0x0
[8.650529] snd_hda_codec_realtek hdaudioC0D2:dig-out=0x1e/0x0
[8.650531] snd_hda_codec_realtek hdaudioC0D2:inputs:
[8.650533] snd_hda_codec_realtek hdaudioC0D2:  Rear Mic=0x18
[8.650535] snd_hda_codec_realtek hdaudioC0D2:  Front Mic=0x19
[8.650536] snd_hda_codec_realtek hdaudioC0D2:  Line=0x1a
[8.650538] snd_hda_codec_realtek hdaudioC0D2:  CD=0x1c
[8.650539] snd_hda_codec_realtek hdaudioC0D2:dig-in=0x1f
[

Bug#893166: libexo-helpers: i386 helpers refer to wrong arch path /usr/lib/x86_64-linux-gnu/xfce4/exo-1/

[Nemo Inis]

Package: libexo-helpers
Version: 0.12.0-1
Severity: important

Dear Maintainer,

The following helpers installed in /usr/share/xfce4/helpers by libexo-
helpers_0.12.0-1
all refer to /usr/lib/x86_64-linux-gnu/xfce4/exo-1/exo-compose-mail-1 which
does not
exist on i386 installations:

balsa.desktop
evolution.desktop
geary.desktop
icedove.desktop
kmail.desktop
mozilla-mailer.desktop
mutt.desktop
muttng.desktop
sylpheed-claws.desktop
sylpheed.desktop
thunderbird.desktop

Proper path on for i386 is /usr/lib/i386-linux-gnu/xfce4/exo-1/



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

Kernel: Linux 4.14.0-3-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, 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 libexo-helpers depends on:
ii  libexo-common  0.12.0-1

libexo-helpers recommends no packages.

libexo-helpers suggests no packages.

-- no debconf information

Bug#851626: sogo.service specifies wrong RuntimeDirectory

[nemo Inis]

Package: sogo
Version: 3.2.5-2
Severity: important

(also affects 3.2.4 in testing)

sogo.service specifies /run/sogo as the RuntimeDirectory. The service fails to 
start because
systemd expects a simple name not a path. See man 5 systemd.exec

Bug#847415: easy-rsa fails if its path contains spaces

[Nemo Inis]

Package: easy-rsa
Version: 2.2.2-2
Severity: important

Dear Maintainer,

easy-rsa fails if the path to it (when copied to a user directory as
recommended, or the path created by make-cadir) contains a space.
At the very least, the following scripts aren't space-safe: vars,
whichopensslcnf, build-dh



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

Kernel: Linux 4.7.0-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, 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 easy-rsa depends on:
ii  openssl  1.1.0c-2

Versions of packages easy-rsa recommends:
pn  opensc  

easy-rsa suggests no packages.

-- no debconf information

Bug#847280: qpdfview: Debian version is 3 releases behind, missing important features

[Nemo Inis]

Package: qpdfview
Version: 0.4.14-1
Severity: important

Dear Maintainer,

qpdfview 0.4.17 has been released. Could we replace the 0.4.14 version we have
in Debian?

Thanks for great work!



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

Kernel: Linux 4.7.0-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, 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 qpdfview depends on:
ii  hicolor-icon-theme0.15-1
ii  libc6 2.24-5
ii  libcups2  2.2.1-2
ii  libgcc1   1:6.2.0-13
ii  libgl1-mesa-glx [libgl1]  12.0.4-2
ii  libpoppler-qt5-1  0.48.0-2
ii  libqt5concurrent5 5.7.1~20161021+dfsg-6
ii  libqt5core5a  5.7.1~20161021+dfsg-6
ii  libqt5dbus5   5.7.1~20161021+dfsg-6
ii  libqt5gui55.7.1~20161021+dfsg-6
ii  libqt5printsupport5   5.7.1~20161021+dfsg-6
ii  libqt5sql55.7.1~20161021+dfsg-6
ii  libqt5sql5-sqlite 5.7.1~20161021+dfsg-6
ii  libqt5svg55.7.1~20161021-2
ii  libqt5widgets55.7.1~20161021+dfsg-6
ii  libqt5xml55.7.1~20161021+dfsg-6
ii  libstdc++66.2.0-13
ii  zlib1g1:1.2.8.dfsg-2+b3

Versions of packages qpdfview recommends:
pn  qpdfview-djvu-plugin   
pn  qpdfview-ps-plugin 
pn  qpdfview-translations  

qpdfview suggests no packages.

-- no debconf information

Bug#845944: gddrescue: ddrescue 1.19 --direct option fails

[Nemo Inis]

Package: gddrescue
Version: 1.19-2+b1
Severity: important

Dear Maintainer,

the --direct option (-d) of gddrescue 1.19-2+b1 fails on all (32-bit) machines
I have tried it on, kernels 4.5, 4.7. or 4.8.
strace shows that it's getting thousands of EINVAL while trying to read:

access("/dev/sdb", F_OK)= 0
_llseek(3, 500629504, [500629504], SEEK_SET) = 0
read(3, 0x81098ca0, 65536)  = -1 EINVAL (Invalid argument)


It does not matter what disk is being read or what block size, just that "-d"
is used.  I have not tried 64-bit machines.

The same commands with gddrescue 1.21 work fine.



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

Kernel: Linux 4.7.0-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, 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 gddrescue depends on:
ii  libc6   2.24-5
ii  libgcc1 1:6.2.0-10
ii  libstdc++6  6.2.0-10

gddrescue recommends no packages.

gddrescue suggests no packages.

-- no debconf information

Bug#842521: More Information

[nemo Inis]

My bug report is clear as mud without the following information:

- the ssh logins I mention are with public key authentication, which does 
explain why Private
is not mounted (there is no user login password to unwrap the passphrase with)

- the bug is really in the fact that a logout of an ssh session that did NOT 
mount Private will
unmount Private "from under the feet" of a session that did mount it.

Bug#842521: ecryptfs-utils: Private directory mount count is wrong if first login is via ssh

[Nemo Inis]

Package: ecryptfs-utils
Version: 111-2
Severity: normal

Dear Maintainer,

0) Use ecryptfs-setup-private to setup a Private directory in a user account.

1) After a fresh boot, if the first login to that user account is via ssh
instead of via GUI (lightdm), then the Private dir is not mounted;
/dev/shm/ecryptfs-$USER-private exists but is EMPTY (or, if this is your second
go-around, contains 0). While still logged via ssh, if you login via GUI, the
Private dir is mounted and /dev/shm/ecryptfs-$USER-private contains 1 (which is
wrong of course, it should be 2). While still logged in the GUI, if you log out
of the ssh session, /dev/shm/ecryptfs-$USER-private becomes 0 and Private is
umounted.

2) If the first login is via GUI, Private is mounted and /dev/shm/ecryptfs
-$USER-private contains 1. Further logins via ssh do increment it properly, and
logouts decrement it properly. Logging out of the GUI with no active ssh
session brings you back to condition 1) above.

This bug exists in fresh Jessie 8.6 installs as well as in Stretch.



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

Kernel: Linux 4.7.0-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, 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 ecryptfs-utils depends on:
ii  gettext-base0.19.8.1-1
ii  keyutils1.5.9-9
ii  libassuan0  2.4.3-1
ii  libc6   2.24-3
ii  libecryptfs1111-2
ii  libgpg-error0   1.24-1
ii  libgpgme11  1.7.0-1
ii  libkeyutils11.5.9-9
ii  libpam-runtime  1.1.8-3.3
ii  libpam0g1.1.8-3.3
ii  libtspi10.3.13-4+b1

ecryptfs-utils recommends no packages.

Versions of packages ecryptfs-utils suggests:
ii  cryptsetup  2:1.7.2-4

-- no debconf information

Bug#841498: also affects exposure tone curve widgets

[nemo Inis]

Just FYI for anyone googling for a reason for symptoms:

This bug (i.e., rawtherapee 4.2.1241 is incompatible with GTK 3.22) also makes 
the rawtherapee
exposure tone curve widgets unusable: they don't refresh properly, so the 
curves become unreadable.

Best to downgrade to 4.2.0 until support for GTK 3.22 is added

Bug#825235: obnam: make --exclude work during restore

[Nemo Inis]

Package: obnam
Version: 1.19.1-1
Severity: wishlist

Dear Maintainer,

I wanted to restore (from scratch) a system where / and /home are mounted on
separate partitions, but backed into the same obnam repository.

First try was to mount /dev/newdrive1 on /target, /dev/newdrive2 on
/target/home, then have obnam restore the last backup to /target.
Can't do that: obnam won't restore to a non-empty dir. (which, by the way, also
includes "lost+found" so you can't restore to a blank partition unless you get
rid of that first.)

Second try was to restore --exclude /home/ --to /target
Can't do that: obnam ignores --exclude during restore.

I ended up listing every root folder except home in the restore command, then
create and mount home, and restore that. This kind of pain could be avoided if
--exclude worked on restore commands. I'm sure there are lots of other use
cases for this.

Bonus points if you also let obnam restore to a non-empty dir (with a --force-
merge option), merging source dirs into existing target dirs, and overwriting
existing files.

Thanks!



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

Kernel: Linux 4.5.0-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, 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.22-7
ii  python2.7.11-1
ii  python-cliapp 1.20160316-1
ii  python-fuse   2:0.2.1-12
ii  python-larch  1.20151025-1
ii  python-paramiko   1.16.0-1
ii  python-tracing0.9-1
ii  python-ttystatus  0.32-1
ii  python-yaml   3.11-3+b1

obnam recommends no packages.

obnam suggests no packages.

-- no debconf information

Bug#813335: mdadm: Upgrade from jessie to testing breaks boot with raid on lvm2

[Nemo Inis]

On Tue, 2 Feb 2016 16:49:08 +0100 Lennart Weller  wrote:

> Try reversing the patch locally and see if it fixes your problem:

Reversing the patch fixed the problem for me. Thanks, Lennart!

Bug#816852: flashplugin-nonfree: missing gnupg2 dependency

[Nemo Inis]

Package: flashplugin-nonfree
Version: 1:3.6.1+b1
Severity: normal

Dear Maintainer,

flashplugin-nonfree has a "Depends: gnupg" clause, which makes it depend on
GnuPG v1 only.
The clause should be "Depends: gnupg | gnupg2" to allow for systems with GnuPG
v2 only.




-- Package-specific info:
Debian version: stretch/sid
Architecture: i386
Package version: 1:3.6.1+b1
Adobe Flash Player version: LNX 11,2,202,569
MD5 checksums:
88aa056c9d4f919bfc9c301f099fe0d1  
/var/cache/flashplugin-nonfree/adobewebpage.html
160a01dd00527304e5291e65eb0c65e2  
/var/cache/flashplugin-nonfree/get-upstream-version.pl
4a43aafd3e23167487168df8fbcf2b96  
/var/cache/flashplugin-nonfree/install_flash_player_11_linux.i386.tar.gz
d933470c6e6c40ae214758082d658e39  
/usr/lib/flashplugin-nonfree/libflashplayer.so
Alternatives:
flash-mozilla.so - auto mode
  link best version is /usr/lib/flashplugin-nonfree/libflashplayer.so
  link currently points to 
/usr/lib/flashplugin-nonfree/libflashplayer.so
  link flash-mozilla.so is /usr/lib/mozilla/plugins/flash-mozilla.so
/usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50
lrwxrwxrwx 1 root root 34 Aug 29  2015 
/usr/lib/mozilla/plugins/flash-mozilla.so -> /etc/alternatives/flash-mozilla.so
/usr/lib/mozilla/plugins/flash-mozilla.so: symbolic link to 
/etc/alternatives/flash-mozilla.so

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

Kernel: Linux 4.3.0-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, 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 flashplugin-nonfree depends on:
ii  binutils   2.26-4
ii  ca-certificates20160104
ii  debconf [debconf-2.0]  1.5.58
ii  gnupg  1.4.20-4
ii  libatk1.0-02.18.0-1
ii  libcairo2  1.14.6-1
ii  libcurl3-gnutls7.47.0-1
ii  libfontconfig1 2.11.0-6.3
ii  libfreetype6   2.6.1-0.1
ii  libgcc11:5.3.1-8
ii  libglib2.0-0   2.46.2-3
ii  libgtk2.0-02.24.29-1
ii  libnspr4   2:4.11-1
ii  libnss32:3.21-1.1
ii  libpango1.0-0  1.38.1-1
ii  libstdc++6 5.3.1-8
ii  libx11-6   2:1.6.3-1
ii  libxext6   2:1.3.3-1
ii  libxt6 1:1.1.5-1
ii  wget   1.17.1-1+b1

flashplugin-nonfree recommends no packages.

Versions of packages flashplugin-nonfree suggests:
pn  flashplugin-nonfree-extrasound  
ii  fonts-dejavu2.35-1
pn  hal 
ii  iceweasel   44.0.2-1
pn  konqueror-nsplugins 
ii  ttf-mscorefonts-installer   3.6
pn  ttf-xfree86-nonfree 

-- no debconf information

Bug#809082: Linux kernel 4.3.3 PAE causes disk errors

[Nemo Inis]

Package: linux-image-686-pae
Version: 4.3+70: i386
Severity: grave

Package: linux-image-4.3.0-1-686-pae
Version: 4.3.3-2

This is an FYI to update this kernel as soon as the fix is released.

Linux kernel 4.3.3 has a serious bug in its PAE support, which causes all kinds 
of disk access
errors.
The bug has been reported upstream at:
https://bugzilla.kernel.org/show_bug.cgi?id=109661

Bug#798591: libreoffice: Long click closes Libre Office 5

[Nemo Inis]

Package: libreoffice
Version: 1:5.0.1-1
Followup-For: Bug #798591

I can reproduce this here. Backtrace is identical to Junior Polegato's (except
different hex addresses.)
All packages freshly updated from stretch.



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

Kernel: Linux 4.1.0-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, 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 libreoffice depends on:
ii  fonts-dejavu 2.35-1
ii  fonts-sil-gentium-basic  1.1-7
ii  libreoffice-avmedia-backend-vlc  1:5.0.1-1
ii  libreoffice-base 1:5.0.1-1
ii  libreoffice-calc 1:5.0.1-1
ii  libreoffice-core 1:5.0.1-1
ii  libreoffice-draw 1:5.0.1-1
ii  libreoffice-impress  1:5.0.1-1
ii  libreoffice-java-common  1:5.0.1-1
ii  libreoffice-math 1:5.0.1-1
ii  libreoffice-report-builder-bin   1:5.0.1-1
ii  libreoffice-writer   1:5.0.1-1
ii  python3-uno  1:5.0.1-1

Versions of packages libreoffice recommends:
ii  fonts-liberation   1.07.4-1
ii  libpaper-utils 1.1.24+nmu4
ii  ttf-mscorefonts-installer  3.6

Versions of packages libreoffice suggests:
ii  cups-bsd   2.0.3-10
ii  default-jre [java5-runtime]2:1.7-52
ii  gstreamer1.0-libav 1:1.4.5-dmo1
ii  gstreamer1.0-plugins-bad   1.4.5-3
ii  gstreamer1.0-plugins-base  1.4.5-2
ii  gstreamer1.0-plugins-good  1.4.5-2+b2
ii  gstreamer1.0-plugins-ugly  1.4.5-2+b2
pn  hunspell-dictionary
pn  hyphen-hyphenation-patterns
ii  iceweasel  38.2.0esr-1~stretch
ii  imagemagick8:6.8.9.9-5.1
ii  libgl1-mesa-glx [libgl1]   10.6.3-1
ii  libreoffice-gnome  1:5.0.1-1
pn  libreoffice-grammarcheck   
ii  libreoffice-help-en-us [libreoffice-help-5.0]  1:5.0.1-1
pn  libreoffice-l10n-5.0   
pn  libreoffice-officebean 
ii  libsane1.0.24-13
ii  libxrender11:0.9.8-1+b1
pn  myspell-dictionary 
pn  mythes-thesaurus   
ii  openclipart-libreoffice1:0.18+dfsg-14
ii  openjdk-7-jre [java5-runtime]  7u85-2.6.1-3
ii  pstoedit   3.62-2+b4
ii  unixodbc   2.3.1-3

Versions of packages libreoffice-core depends on:
ii  fontconfig2.11.0-6.3
ii  fonts-opensymbol  2:102.6+LibO5.0.1-1
ii  libatk1.0-0   2.16.0-2
ii  libboost-date-time1.58.0  1.58.0+dfsg-3
ii  libc6 2.19-19
ii  libcairo2 1.14.2-2
ii  libclucene-contribs1v52.3.3.4-4.1
ii  libclucene-core1v52.3.3.4-4.1
ii  libcmis-0.5-5v5   0.5.0-3
ii  libcups2  2.0.3-10
ii  libcurl3-gnutls   7.44.0-1
ii  libdbus-1-3   1.8.20-1
ii  libdbus-glib-1-2  0.102-1
ii  libeot0   0.01-3
ii  libexpat1 2.1.0-7
ii  libexttextcat-2.0-0   3.4.4-1
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-4
ii  libgcc1   1:5.2.1-16
ii  libgdk-pixbuf2.0-02.31.5-1
ii  libgl1-mesa-glx [libgl1]  10.6.3-1
ii  libglew1.10   1.10.0-3
ii  libglib2.0-0  2.44.1-1.1
ii  libgltf-0.0-0v5   0.0.2-4
ii  libglu1-mesa [libglu1]9.0.0-2
ii  libgraphite2-31.2.4-3
ii  libgtk2.0-0   2.24.28-1
ii  libharfbuzz-icu0  1.0.1-1+b1
ii  libharfbuzz0b 1.0.1-1+b1
ii  libhunspell-1.3-0 1.3.3-3+b1
ii  libhyphen02.8.8-2
ii  libice6   2:1.0.9-1+b1
ii  libicu55  55.1-4
ii  libjpeg62-turbo   1:1.4.1-2
ii  liblangtag1   0.5.1-3
ii  liblcms2-22.6-3+b3
ii  libldap-2.4-2 2.4.42+dfsg-1
ii  libmythes-1.2-0   2:1.2.4-1
ii  libneon27-gnutls  0.30.1-1
ii  libnspr4  2:4.10.9-2
ii  libnspr4-0d   2:4.10.9-2
ii  libnss3   2:3.20-1
ii  libnss3-1d2:3.20-1
ii  libodfgen-0.1-1   0.1.4-1
ii  libpango-1.0-01.36.8-3
ii  libpangocairo-1.0-0   1.36.8-3
ii  libpangoft2-1.0-0 1.36.8-3
ii  libpcre3  2:8.35-7.1
ii  libpng12-01.2.50-2+b2
ii  librdf0   1.0.17-1+b1
ii  libreoffice-common1:5.0.1-1
ii  librevenge-0.0-0  

Bug#796817: font-manager: version 0.7.2 is available

[Nemo Inis]

Package: font-manager
Severity: important

Dear Maintainer,

The version of font-manager in Debian, 0.5.7-4, is years out of date. Version
0.7.2 is available from the developers. Please consider packaging it.

Thanks!



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

Kernel: Linux 4.0.0-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, 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 font-manager depends on:
ii  libc6   2.19-19
ii  libfontconfig1  2.11.0-6.3
ii  libfreetype62.5.2-4
ii  libglib2.0-02.44.1-1.1
ii  libpango1.0-0   1.36.8-3
ii  libpython2.72.7.10-3
ii  libsqlite3-03.8.10.2-1
ii  python  2.7.9-1
ii  python-dbus 1.2.0-2+b3
ii  python-gobject  3.16.2-1
ii  python-gtk2 2.24.0-4
ii  python-libxml2  2.9.1+dfsg1-5

font-manager recommends no packages.

Versions of packages font-manager suggests:
pn  python-reportlab  none

Bug#750498: cups: server keeps timing out after 30secs idling with no way to change that

[Nemo Inis]

On 04/06/14 12:37 AM, Didier 'OdyX' Raboud wrote:
 That's not entirely accurate: both the Debian NEWS file [0] and the 
 README.Debian [1] (but that one is installed in a bizarre place, 
 arguably) contain instructions on how to disable this behaviour, quoting 
 the first:
 
 - Automatic exit when idle
   When operated under systemd as init, the CUPS daemon will be
   launched when needed (through socket activation) and exit itself
   after being idle for some time (30 seconds by default). The delay
   before exiting on idle can be configured using 'IdleExitTimeout' in
   /etc/cups/cupsd.conf. CUPS can also  be left running continuously
   using 'SystemdIdleExit off' in that same file.
 
 [0] /usr/share/doc/cups-daemon/NEWS.Debian.gz
 [1] /usr/share/doc/libcups2/README.Debian.gz

Indeed; I had checked 'man cupsd' and 'man cupsd.conf' but it never occured to 
me to check
README files for more configurations options.

Setting 'IdleExitTimeout 0' and 'SystemdIdleExit off' in /etc/cups/cupsds.conf 
did restore the
previous behaviour.
Thanks!


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

Bug#750498: cups: server keeps timing out after 30secs idling with no way to change that

[Nemo Inis]

Package: cups
Version: 1.7.2-3
Severity: important

Dear Maintainer,

Ever since cups 1.7.2-2, which contains a patch for bug #742666, and my switch
to systemd, the cups server exits after 30 seconds idling without a
configuration option to prevent that.  In my case, that means:

- when I'm using the cups web interface at localhost:631, if I wait more than
30 seconds before clicking on anything, my browser reports unable to connect
and I've lost whatever work I was in the middle of (for example adding a
printer, etc...);

- cups starts/stops throughout the day, and every time, it triggers colord
(which I also run), which loads all my profiles, etc... and fills my syslog
telling me so;

- since I'm running a desktop machine, I'd rather not have settings meant for
laptops forced down on me; I'd like the option to run cups permanently without
timeout as it did before.

Thanks!



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

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

Versions of packages cups depends on:
ii  cups-client1.7.2-3
ii  cups-common1.7.2-3
ii  cups-core-drivers  1.7.2-3
ii  cups-daemon1.7.2-3
ii  cups-filters   1.0.53-1
ii  cups-ppdc  1.7.2-3
ii  cups-server-common 1.7.2-3
ii  debconf [debconf-2.0]  1.5.53
ii  ghostscript9.05~dfsg-8.1
ii  libavahi-client3   0.6.31-4
ii  libavahi-common3   0.6.31-4
ii  libc-bin   2.18-7
ii  libc6  2.18-7
ii  libcups2   1.7.2-3
ii  libcupscgi11.7.2-3
ii  libcupsimage2  1.7.2-3
ii  libcupsmime1   1.7.2-3
ii  libcupsppdc1   1.7.2-3
ii  libgcc11:4.9.0-4
ii  libstdc++6 4.9.0-4
ii  libusb-1.0-0   2:1.0.18-2
ii  lsb-base   4.1+Debian12
ii  poppler-utils  0.24.5-4
ii  procps 1:3.3.9-2

Versions of packages cups recommends:
ii  avahi-daemon 0.6.31-4
ii  colord   1.0.6-1
ii  cups-filters [ghostscript-cups]  1.0.53-1
ii  printer-driver-gutenprint5.2.10~pre2-2

Versions of packages cups suggests:
ii  cups-bsd   1.7.2-3
ii  cups-pdf   2.6.1-9pdfpatch1
ii  foomatic-db20140325-1
pn  hplip  none
pn  printer-driver-hpcups  none
ii  smbclient  2:4.1.7+dfsg-2
ii  udev   204-8

-- debconf information excluded


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

Bug#744329: x2goclient: Please add user comment field to session preferences

[Nemo Inis]

Package: x2goclient
Version: 4.0.1.1-1
Severity: wishlist

Dear Maintainer,

Would it be possible for x2goclient to store a multi-line comment field in
each session preferences?
It is a convenient place for the user to store some info as to why/how some
prefs were set, some target host info (for people like me who have many
clients), usage tips for that session, etc...

Not a high-priority item but it would increase ease of use.

Thanks!



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

Kernel: Linux 3.13-1-686-pae (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 x2goclient depends on:
ii  libc6   2.18-4
ii  libcups21.7.1-12
ii  libgcc1 1:4.8.2-16
ii  libldap-2.4-2   2.4.39-1
ii  libqt4-network  4:4.8.5+git242-g0315971+dfsg-2
ii  libqt4-svg  4:4.8.5+git242-g0315971+dfsg-2
ii  libqtcore4  4:4.8.5+git242-g0315971+dfsg-2
ii  libqtgui4   4:4.8.5+git242-g0315971+dfsg-2
ii  libssh-40.5.4-3
ii  libstdc++6  4.8.2-16
ii  libx11-62:1.6.2-1
ii  libxpm4 1:3.5.10-1
ii  nxproxy 3.5.0.20-2
ii  openssh-client  1:6.6p1-2

Versions of packages x2goclient recommends:
ii  openssh-server  1:6.6p1-2
ii  rdesktop1.7.1-1

Versions of packages x2goclient suggests:
pn  pinentry-x2go  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#741968: closed by Lars Wirzenius l...@liw.fi (Bug#741968: fixed in obnam 1.7.2-1)

[Nemo Inis]

On 30/03/14 09:39 AM, Lars Wirzenius wrote:
 I've applied a patch from Valery to fix this, I hope. If you can try
 Obnam from git master, could you do so and tell me if obnam mount
 now works for you? You don't need to run a new backup.

That seems to have fixed it; I've tried various ways to get backed data out of, 
or use it
directly from, the repository and everything worked fine.
Thanks for the hard work, gentlemen!


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

Bug#741236: [Pkg-xfce-devel] Bug#741236: lightdm-gtk-greeter: Randomly I cannot log into my systems since the 1.8.2-1 update happened

[Nemo Inis]

when stuck during login, doing this on the console:
kill -SIGUSR1 $(pgrep -x lightdm-gtk-greeter)
...gets it going and login proceeds successfully.


The lightdm-gtk-greeter 1.8.2 seems to be stuck on a mutex (race condition 
maybe??):

Thread 1 (Thread 0xb6236880 (LWP 2261)):
#0  0xb6d6629d in __lll_lock_wait () from /lib/i386-linux-gnu/libpthread.so.0
#1  0xb6d62007 in _L_lock_1154 () from /lib/i386-linux-gnu/libpthread.so.0
#2  0xb6d61f8d in pthread_mutex_lock () from /lib/i386-linux-gnu/libpthread.so.0
#3  0xb6f4afe0 in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb6f082b4 in g_main_loop_quit () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb73cf343 in gtk_main_quit () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
#6  0xb77b9ad4 in _start ()

Sorry I don't have symbols this was on a live-booted USB key which I can't 
change right now.


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

Bug#741236: [Pkg-xfce-devel] Bug#741236: lightdm-gtk-greeter: Randomly I cannot log into my systems since the 1.8.2-1 update happened

[Nemo Inis]

Sorry pgrep has a 15-char limit to that command in message #107 should be
kill -SIGUSR1 $(pgrep -x lightdm-gtk-gre)


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

Bug#741968: closed by Lars Wirzenius l...@liw.fi (Bug#741968: fixed in obnam 1.7.2-1)

[Nemo Inis]

Hi Lars,

I don't think the problem is fully fixed. I'm still getting weird errors 
depending how I read
the backed up files from the fuse-mounted repository.
As an example, I've attached an annoted terminal session showing how if I try 
to read an epub
(with Calibre's ebook-viewer) from a fuse-mounted repo, I get corruption. But 
if I first copy
it out using cp then it's OK. Bizarre stuf...

Cheers
Nemo


backupfuse/Books is an obnam mount of the latest generation
/Books is the folder that was backed up
ebook-viewer is the Calibre ebook-viewer (v1.23), written in python

$ md5 backupfuse/Books/handbook.epub   --A) CHECKSUM OK
06d524ff85facfc2993e67ef6494d05f  backupfuse/Books/handbook.epub
$ ebook-viewer backupfuse/Books/handbook.epub  --B1) TRY TO VIEW THE EPUB
InputFormatPlugin: EPUB Input running
on backupfuse/Books/handbook.epub
EPUB appears to be invalid ZIP file, trying a more forgiving ZIP parser
--B2) EPUB IS CORRUPTED
$ ebook-viewer /Books/handbook.epub  --C1) LET'S GO CHECK THE ORIGINAL
InputFormatPlugin: EPUB Input running
on /Books/handbook.epub
Found HTML cover OEBPS/Text/cover.html--C2) ORIGINAL READS OK
$ md5 /Books/handbook.epub
06d524ff85facfc2993e67ef6494d05f  /Books/handbook.epub  --C3) BUT ORIGINAL HAS 
SAME MD5 WE SAW IN STEP A!
$ md5 backupfuse/Books/handbook.epub --D) CHECK MD5 OF BACKED FILE AGAIN
b8d645db3af61ae2e8de03f496a1788d  backupfuse/Books/handbook.epub   --D2) 
CHECKSUM HAS CHANGED!!
$ sudo -s
# echo 3  /proc/sys/vm/drop_caches  --E) DROP LINUX CACHES
# exit
$ md5 backupfuse/Books/handbook.epub  --F1) CHECK MD5 AGAIN
06d524ff85facfc2993e67ef6494d05f  backupfuse/Books/handbook.epub  --F2) IT'S 
CORRECT AGAIN
$
$ cp backupfuse/Books/handbook.epub /tmp/  --G1) SO NOW COPY IT OUT USING CP
$ md5 /tmp/handbook.epub
06d524ff85facfc2993e67ef6494d05f  /tmp/handbook.epub  --G2) GOOD CHECKSUM
$ ebook-viewer /tmp/handbook.epub
InputFormatPlugin: EPUB Input running
on /tmp/handbook.epub
Found HTML cover OEBPS/Text/cover.html   --G3) NOW IT READS OK
$ ebook-viewer backupfuse/Books/handbook.epub  --H1) TRY READING THE BACKUP 
COPY
InputFormatPlugin: EPUB Input running
on backupfuse/Books/handbook.epub
Found HTML cover OEBPS/Text/cover.html  --H2) BACKUP COPY READS OK PROBABLY 
FROM CACHE
$ sudo -s
# echo 3  /proc/sys/vm/drop_caches  --I) DROPPING CACHE
# exit
$ ebook-viewer backupfuse/Books/handbook.epub  --J1) TRY READING BACKUP COPY 
AGAIN
InputFormatPlugin: EPUB Input running
on backupfuse/Books/handbook.epub
EPUB appears to be invalid ZIP file, trying a more forgiving ZIP parser  --J2) 
CORRUPTED AGAIN

Bug#741968: obnam mount fails to retrieve files over 64KB (obnam restore works fine)

[Nemo Inis]

Package: obnam
Version: 1.7-1
Severity: important

Dear Maintainer,

I upgraded to obnam 1.7.1 (digression here: the Debian changelog for 1.7.1
should have carried the same mention of possible repository corruption that
website News did carry. As a debian user, the Debian changelog/alert mechanism
is the only thing I'm likely to see during a 100+ packages upgrade).

obnam 1.7.1 sees my 1.6.1 repository properly and restores  backup from it
properly.

However, 'obnam mount' fails to properly access any file  64KB.  md5 shows
differing checksums, diff fails, and a 'cp backedfile /tmp/restoredfile'
command either fails silently having copied only part of the file, or else dies
with this error:

cp: error reading ‘backedfile’: Invalid argument
cp: failed to extend ‘/tmp/restoredfile’: Invalid argument

This happens on every file  64KB that I've tried (and all those files restore
properly with obnam restore). Files  64KB appear OK.



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

Kernel: Linux 3.12-1-686-pae (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 obnam depends on:
ii  libc6 2.18-4
ii  python2.7.5-5
ii  python-cliapp 1.20130808-1
ii  python-fuse   2:0.2.1-9
ii  python-larch  1.20131130-1
ii  python-paramiko   1.10.1-1
ii  python-tracing0.8-1
ii  python-ttystatus  0.23-1
ii  python-yaml   3.10-4+b2

obnam recommends no packages.

obnam 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#740361: zenity: please update to new version 3.10 available upstream

[Nemo Inis]

Package: zenity
Version: 3.8.0-1
Severity: normal

Dear Maintainer,

sid and jessie are still on 3.8.0-1 but version 3.10 has been available for
some time, with fixes for some annoying bugs such as debian bug #739248 (702535
upstream), etc...  Can we please update? thanks!



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

Kernel: Linux 3.12-1-686-pae (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 zenity depends on:
ii  libc6   2.17-97
ii  libgdk-pixbuf2.0-0  2.30.5-1
ii  libglib2.0-02.38.2-5
ii  libgtk-3-0  3.10.7-1
ii  libnotify4  0.7.6-2
ii  libpango-1.0-0  1.36.0-1+b1
ii  libwebkitgtk-3.0-0  2.2.3-1+b1
ii  libx11-62:1.6.2-1
ii  zenity-common   3.8.0-1

zenity recommends no packages.

zenity 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#686192: Please add more flexible excluding options

[Nemo Inis]

I think the tag issue is available nowadays via --exclude-caches and adding 
CACHEDIR.TAG files
which conform to http://www.brynosaurus.com/cachedir/spec.html

However I still think obnam needs more flexible excluding options. In 
particular:

-the ability to INCLUDE files to backup via config files, with such inclusions 
taking
precedence over all stated exclusions.  This would allow blanket exclusion of a 
hierarchy, with
specified exceptions. For example, ^/all/, !^/all/except-that would skip 
/all/* but not
/all/except-that

-obnam reads in multiple .conf files (if present in /etc/obnam/ or 
~/.config/obnam/) but the
exclude options in such files clobber each other: the last one read in, wins.  
This prevents me
from having the same generic exclusion list on several machines, complemented 
by a local
exclusion list, for example. It would be better if an exclude option in a later 
file would add
to, rather than replace, exclude options in earlier config files.


Cheers!


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

Bug#715285: gksu man page reference to sudo(1) should be sudo(8)

[Nemo Inis]

Package: gksu
Version: 2.0.2-6
Severity: minor

The man page for gksu refers to sudo(1). On Debian, that should be sudo(8).
This breaks w3mman's and manpages.debian.net's ability to traverse links to the
corresponding man page.




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

Kernel: Linux 3.2.0-4-686-pae (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 gksu depends on:
ii  libatk1.0-0   2.8.0-2
ii  libc6 2.17-6
ii  libcairo2 1.12.14-4
ii  libfontconfig12.9.0-7.1
ii  libfreetype6  2.4.9-1.1
ii  libgconf2-4   3.2.6-1
ii  libgdk-pixbuf2.0-02.28.2-1
ii  libgksu2-02.0.13~pre1-6
ii  libglib2.0-0  2.36.1-2build1
ii  libgnome-keyring0 3.4.1-1
ii  libgtk2.0-0   2.24.18-1
ii  libpango1.0-0 1.32.5-5+b1
ii  libstartup-notification0  0.12-3
ii  sudo  1.8.5p2-1+nmu1

Versions of packages gksu recommends:
ii  gnome-keyring  3.8.2-2

gksu suggests no packages.

-- debconf-show failed


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

Bug#707678: gnome-system-tools: users-admin fails silently to delete a user if a process is running with that uid

[Nemo Inis]

Package: gnome-system-tools
Version: 3.0.0-2
Severity: important

When trying to delete a user, users-admin appeared to have worked: the user was
removed from the list shown by users-admin, and no error message was displayed.
However, a quick command-line check showed the user was still there. Indeed,
after exiting and relaunching users-admin, the user was again shown in the
list. This was repeatable.

Using the deluser command in a terminal provided the answer: deluser failed
because that user was currently used by a running process. After killing that
process, deleting the user in users-admin worked as expected.

The security risk is that users-admin failed to delete the user (when the
process was running) without ANY indication that anything was wrong, and so a
trusting admin -if there is such a person :-) - could be fooled into thinking a
user had been deleted when it had not.



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

Kernel: Linux 3.2.0-4-686-pae (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 gnome-system-tools depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.12.1-3
ii  libatk1.0-0  2.4.0-2
ii  libc62.13-38
ii  libcairo-gobject21.12.2-3
ii  libcairo21.12.2-3
ii  libdbus-1-3  1.6.8-1
ii  libfontconfig1   2.9.0-7.1
ii  libfreetype6 2.4.9-1.1
ii  libgdk-pixbuf2.0-0   2.26.1-1
ii  libglib2.0-0 2.33.12+really2.32.4-5
ii  libgtk-3-0   3.4.2-6
ii  liboobs-1-5  3.0.0-1
ii  libpango1.0-01.30.0-1
ii  libpolkit-gobject-1-00.105-3
ii  perl 5.14.2-21
ii  policykit-1-gnome0.105-2
ii  system-tools-backends2.10.2-1

Versions of packages gnome-system-tools recommends:
pn  gnome-control-center  none

Versions of packages gnome-system-tools suggests:
ii  ntp  1:4.2.6.p5+dfsg-2

-- 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#701841: mp3fs: version 0.32 was released last year

[Nemo Inis]

Package: mp3fs
Version: 0.31-28-g7b30a54-1
Severity: wishlist

Dear Maintainer,

version 0.32 was released 2012-06-18:

Important changes in 0.32 (2012-06-18)

This release has a lot of bug fixes and some code cleanup.

Changes in this release:
* The file size calculation should always be correct.
* A crash affecting programs like scp that might try to access past the
  end of the file has been fixed.
* Too many other little fixes were made to list here. See the ChangeLog
  for full details.



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

Kernel: Linux 3.2.0-4-686-pae (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


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

Bug#681176: live-boot: persistence mounting fails if live-persistence.conf contains source=. stanza

[Nemo Inis]

Package: live-boot
Version: 3.0~a35-1
Severity: important

live-boot fails to mount a persistence volume if the volume's live-
persistence.conf contains the source=. stanza. It wrongly reports an unsafe
custom mount. Since that stanza is also automatically used for compatibility-
mode mounting of old home-rw and live-rw overlays, this bug may affect quite a
few people.

I believe the bug is a typo at line 1307 of lib/boot/misc-helpers.sh, which
reads:
   if echo ${opt_source} | grep -q -e ^/ -e ^\(.*/\)\?\.\.\?\(/.*\)\?$  [
${source} != . ]
but should read instead:
   if echo ${opt_source} | grep -q -e ^/ -e ^\(.*/\)\?\.\.\?\(/.*\)\?$  [
${opt_source} != . ]

This change fixed the problem for my wheezy live build.




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

Kernel: Linux 3.2.0-2-686-pae (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



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

Bug#440516: patch for pam_otpw session module

[Nemo Inis]

The pam_otpw.so session module version 1.3-2 in Wheezy does not print out the 
number of
passwords reminder as expected.
I think this is because the function pam_sm_open_session trying to get the 
challenge data from
the handle provided, but that handle does not contain the challenge (which had 
been setup
during the authentication phase) because we are now running in a different 
process than the one
where the authentication happened. So the challenge data is NULL and the module 
aborts.

The attached patch for pam_otpw.c (v1.3-2) fixes this and issues correct 
password reminders on
my Wheezy system.

--- otpw-1.3-2.orig/pam_otpw.c	2003-10-06 07:47:33.0 -0700
+++ otpw-1.3-2/pam_otpw.c	2012-06-24 14:36:01.0 -0700
@@ -328,24 +328,56 @@
 PAM_EXTERN int pam_sm_open_session(pam_handle_t *pamh, int flags, 
    int argc, const char **argv)
 {
+  const char *username;
+  struct passwd *pwd;
   struct challenge *ch = NULL;
   int retval;
   int i, debug = 0;
+  int otpw_flags = 0;
 
   /* parse option flags */
   for (i = 0; i  argc; i++) {
-if (!strcmp(argv[i], debug))
+if (!strcmp(argv[i], debug)) {
   debug = 1;
+  otpw_flags |= OTPW_DEBUG;
+}
   }
 
   D(log_message(LOG_DEBUG, pamh, pam_sm_open_session called, flags=%d,
 		flags));
 
-  retval = pam_get_data(pamh, MODULE_NAME:ch, (const void **) ch);
-  if (retval != PAM_SUCCESS || !ch) {
-log_message(LOG_ERR, pamh, pam_get_data() failed);
-return PAM_SESSION_ERR;
+  /* get user name */
+  retval = pam_get_user(pamh, username, login: );
+  if (retval == PAM_CONV_AGAIN)
+return PAM_INCOMPLETE;
+  else if (retval != PAM_SUCCESS) {
+log_message(LOG_NOTICE, pamh, no username provided);
+return PAM_USER_UNKNOWN;
   }
+  
+  /* DEBUG */
+  D(log_message(LOG_DEBUG, pamh, username is %s, username));
+  D(log_message(LOG_DEBUG, pamh, uid=%d, euid=%d, gid=%d, egid=%d,
+		getuid(), geteuid(), getgid(), getegid()));
+
+  ch = calloc(1, sizeof(struct challenge));
+  if (!ch)
+return PAM_AUTHINFO_UNAVAIL;
+  retval = pam_set_data(pamh, MODULE_NAME:ch, ch, cleanup);
+  if (retval != PAM_SUCCESS) {
+log_message(LOG_ERR, pamh, pam_set_data() failed);
+return PAM_AUTHINFO_UNAVAIL;
+  }
+
+  /* consult POSIX password database (to find homedir, etc.) */
+  pwd = getpwnam(username);
+  if (!pwd) {
+log_message(LOG_NOTICE, pamh, username not found);
+return PAM_USER_UNKNOWN;
+  }
+
+  /* prepare OTPW challenge */
+  otpw_prepare(ch, pwd, otpw_flags);
 
   if (!(flags  PAM_SILENT)  ch-entries = 0) {
 display_notice(pamh, 0, debug,

Bug#678302: tangerine assigns duplicate IDs to tracks newly added to existing database

[Nemo Inis]

Package: tangerine
Version: 0.3.4-3

Starting from scratch, tangerine correctly scans and imports all the tracks 
from my library folder.
However, if I quit tangerine, add new tracks (or folders of tracks) to my 
library, and start
tangerine again, the new tracks do not show up or do not play in my clients 
(Rhythmbox and
XBMC). But if I delete  ~/.config/tangerine/tracks.db and start tangerine 
again, the tracks
appear correctly in my clients.
I tracked the problem to some code in daap-sharp/src/Database.cs that results 
in a duplicate
track ID being assigned to any new track being added to an existing tracks 
database.
The attached patch fixes that problem for me.

System: Debian GNU/Linux testing (wheezy)
diff --git a/daap-sharp/src/Database.cs b/daap-sharp/src/Database.cs
index 82aca1b..63bae66 100644
--- a/daap-sharp/src/Database.cs
+++ b/daap-sharp/src/Database.cs
@@ -432,8 +432,7 @@ namespace DAAP {
 }
 
 public void AddTrack (Track track) {
-if (track.Id == 0)
-track.SetId (nextTrackId++);
+track.SetId (nextTrackId++);
 
 tracks.Add (track);
 basePlaylist.AddTrack (track);

Bug#611452: xserver-xorg-core: switching to linux console, leaves screen blank

[Nemo Inis]

I had the same problem on an older machine. I was able to work around it by 
adding the
NVreg_UseVBios=0 option to /etc/modprobe.d/nvidia-kernel-common.conf and 
rebooting.



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

Bug#646622: debian-maintainers: Changelog for new upstream release should include summary of upstream changelog

[Nemo Inis]

Package: debian-maintainers
Severity: wishlist

Dear Maintainer,

(first thank you all for the tremendous job you are doing!)

I have a suggestion from an end-user point of view:

All too often when checking incoming updates (in Synaptic or other tools) the
Debian changelog includes a mere mention new upstream release.
From an end-user point of view, this is not very informative and less than
useful in deciding whether or not the update should be installed at this time.
I know that section 9.3 of the Debian New Maintainer's guide only requires
listing the debian bugs that are closed by the new release (or by the
maintainer's changes to that new release) and not anything else that may be in
that new release .  But for the convenience of the end-user, it would be nice
if a summary of the upstream's changelog would be included too (like new
features, UI changes, backward compatibility problems, etc..) This would avoid
having to go hunt for it on every single package, and would make the whole
process more user-friendly.

Thanks, and sorry if this was not the right place to report this - I could not
find a better fit.



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

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



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

Bug#540073: Normal behaviour

[Nemo Inis]

Actually, this is normal behaviour for netcat-openbsd. The man page is quite 
specific that -l
and -p cannot be used together:

 -l  Used to specify that nc should listen for an incoming connection 
rather than initi‐
 ate a connection to a remote host.  It is an error to use this 
option in conjunction
 with the -p, -s, or -z options. 



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