from:"Carlos"


Dear maintainer,

Please look at the first line in the last debugging info (bolded).
This is the same CRC mismatch between the files I have already submitted.
Thank you,

*Carlos Kosloff*
Office: (954) 283-8828
Cell: (954) 464-8822
Fax: (888) 854-5440

On 07/26/2015 05:42 PM, Andreas Cadhalpun wrote:

Control: reassign -1 libssl1.0.0
Control: retitle -1 libssl1.0.0: illegal instruction crash on amd64

Hi Carlos,

please keep the bug (793...@bugs.debian.org) in CC.

On 26.07.2015 19:44, Carlos Kosloff wrote:

Please find below requested info.

Thanks.


I have another computer more powerful than this one, 8 core CPU, same OS.
Clamtk works fine there.
For your information, KDE had major breakages after last upgrades, it is 
transitioning from version 4 to 5.

I don't think KDE is related to this problem.


On 07/26/2015 06:51 AM, Andreas Cadhalpun wrote:

On 25.07.2015 04:10, Carlos Kosloff wrote:

* Specs

Using KDE desktop, on a Toshiba laptop with amd64 architecture.

Much more useful would be the information collected by reportbug:
$ reportbug --template clamtk

[...]

Package: clamtk
Version: 5.19-1

[...]

-- System Information:
Debian Release: stretch/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.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 clamtk depends on:
ii  clamav  0.98.7+dfsg-2
ii  clamav-freshclam [clamav-data]  0.98.7+dfsg-2
ii  cron [cron-daemon]  3.0pl1-128
ii  gnome-icon-theme3.12.0-1
ii  libgtk2-perl2:1.2495-1
ii  libjson-perl2.90-1
ii  liblocale-gettext-perl  1.05-9
ii  liblwp-protocol-https-perl  6.06-2
ii  libtext-csv-perl1.33-1
ii  libwww-perl 6.13-1
ii  perl5.20.2-6

clamtk recommends no packages.

Versions of packages clamtk suggests:
ii  cabextract   1.6-1
pn  clamtk-nautilus  none

-- no debconf information

Nothing suspicious here.


* What caused the problem

After a dist-upgrade on 2015/07/24 clamtk does not launch.

What packages were upgraded?
Can you post the relevant parts of /var/log/dpkg.log from that upgrade?

2015-07-24 21:59:13 upgrade clamtk:all 5.19-1 5.19-1

This looks strange. The previous version was already 5.19-1?

The other upgrades look unrelated to the problem. Are you sure this were
all upgrades before the problem occurred?
In particular, when was your last libssl1.0.0:amd64 upgrade?


I am not sure. The fact that the KDE upgrade caused lots of issues, 
prompted me to check all launchers, KDE transition crashes are a known 
issue in the testing branch.

Please post syntax to check on last libssl1.0.0:amd64 upgrade.




* Steps taken to resolve the problem

Reinstalled.
Rebooted computer.
Attempted to launch from CLI.
As user:
command clamtk reports illegal instruction.

This works fine here, thus I'm downgrading the severity.
clamtk is just a perl program, so any illegal instruction error is probably
caused by perl.

What instructions does your CPU support?
Please provide the output of:
$ cat /proc/cpuinfo

ckosloff@notosh:~$ cat /proc/cpuinfo
processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 22
model   : 48
model name  : AMD A6-6310 APU with AMD Radeon R4 Graphics
stepping: 1
microcode   : 0x7030105
cpu MHz : 1000.000
cache size  : 2048 KB
physical id : 0
siblings: 4
core id : 0
cpu cores   : 4
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf 
eagerfpu pni pclmulqdq monitor ssse3 cx16 sse4_1 sse4_2 movbe popcnt aes xsave 
avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 
3dnowprefetch osvw ibs skinit wdt topoext perfctr_nb bpext perfctr_l2 arat cpb 
hw_pstate npt lbrv svm_lock nrip_save tsc_scale flushbyasid decodeassists 
pausefilter pfthreshold vmmcall bmi1 xsaveopt
bugs: fxsave_leak
bogomips: 3593.29
TLB size: 1024 4K pages
clflush size: 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management: ts ttp tm 100mhzsteps hwpstate cpb [12] [13]

This processor doesn't have e.g. avx2.


A backtrace of the crash would most certainly be helpful as well.
Please provide the output of the following command (after installing gdb):
$ gdb --batch -ex r -ex 'bt full' -ex q --args perl /usr/bin/clamtk

ckosloff@notosh:~$ gdb --batch -ex r -ex 'bt full' -ex q --args perl 
/usr/bin

Bug#793557: [Pkg-openssl-devel] Bug#793557: clamtk in testing


Thank you very much

*Carlos Kosloff*
Office: (954) 283-8828
Cell: (954) 464-8822
Fax: (888) 854-5440

On 07/27/2015 03:31 PM, Kurt Roeckx wrote:

On Mon, Jul 27, 2015 at 01:48:53PM -0400, Carlos Kosloff wrote:

Dear maintainer,

Program received signal SIGILL, Illegal instruction.
aesni_cbc_sha256_enc () at aesni-sha256-x86_64.s:29
29  aesni-sha256-x86_64.s: No such file or directory.
#0  aesni_cbc_sha256_enc () at aesni-sha256-x86_64.s:29

I'm not sure why you come in aesni code since your processor
doesn't seem to support that. I'll try to look in to it.


Kurt

Bug#793557: Fwd: Mail delivery failed: returning message to sender





 Forwarded Message 
Subject:Mail delivery failed: returning message to sender
Date:   Mon, 27 Jul 2015 13:49:21 -0400
From:   Mail Delivery System mailer-dae...@eigbox.net
To: ckosl...@hardwarealien.com



This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  pkg-openssl-de...@lists.alioth.debian.org
SMTP error from remote mail server after RCPT 
TO:pkg-openssl-de...@lists.alioth.debian.org:
host lists.alioth.debian.org [5.153.231.21]: 550-Callback setup failed while 
verifying SRS0=tzDPlP=ID=hardwarealien.com=ckosl...@eigbox.net
550-Called:   66.96.140.67
550-Sent: MAIL FROM:
550-Response: 550  Sender rejected.
550-The initial connection, or a HELO or MAIL FROM: command was
550-rejected. Refusing MAIL FROM: does not help fight spam, disregards
550-RFC requirements, and stops you from receiving standard bounce
550-messages. This host does not accept mail from domains whose servers
550-refuse bounces.
550 Sender callout failed: Sender adress can't be verified through SMTP 
check.

-- This is a copy of the message's headers. --

Return-path: ckosl...@hardwarealien.com
Received: from bosmailscan10.eigbox.net ([10.20.15.10])
by bosmailout03.eigbox.net with esmtp (Exim)
id 1ZJmWa-0007cJ-RT
for pkg-openssl-de...@lists.alioth.debian.org; Mon, 27 Jul 2015 
13:49:16 -0400
Received: from [10.115.3.32] (helo=bosimpout12)
by bosmailscan10.eigbox.net with esmtp (Exim)
id 1ZJmWa-000445-Bs
for pkg-openssl-de...@lists.alioth.debian.org; Mon, 27 Jul 2015 
13:49:16 -0400
Received: from bosauthsmtp17.yourhostingaccount.com ([10.20.18.17])
by bosimpout12 with
id xVpC1q00F0N5uqq01VpFWd; Mon, 27 Jul 2015 13:49:16 -0400
X-Authority-Analysis: v=2.1 cv=MLvumapl c=1 sm=1 tr=0
 a=f4kFLigMKr8AH7rIJ//qJA==:117 a=cMCXDfxThjRWy3OEsJgDXg==:17 a=pq4jwCgg:8
 a=QPcu4mC3:8 a=QwNwINJ-:8 a=pcLIrrrK:8 a=J1Z3YnKSiEYA:10
 a=zKzDOiuOpD0A:10 a=zOBTXjUuO1YA:10 a=r77TgQKjGQsHNAKrUKIA:9 a=xNf9USuD:8
 a=xtERp6CF:8 a=sR6aJCHAR0YBqHZXDcoA:9 a=s6AUrMpJEWd9IVR5:21
 a=QoNCVNbh93fH2zOh:21 a=QEXdDO2ut3YA:10 a=CvdHd9amEXEA:10 a=mtm4ZZdaSxsA:10
 a=Oc1XE_3TfnoA:10 a=Joz-sfvf-8UA:10 a=BwHNhgTvz8gA:10 a=QzkQU2KsuUsA:10
 a=mK_AVkan:8 a=9SDOBO0-USaPSSopLd8A:9 a=P8xGlbIQ2C2jx2gk:21
 a=W5XQUX5o-j6lPG92:21 a=RK8KMGcCG4NGj3sB:21 a=_W_S_7VecoQA:10
Received: from 108-227-118-26.lightspeed.miamfl.sbcglobal.net 
([108.227.118.26]:57669 helo=[192.168.1.203])
by bosauthsmtp17.eigbox.net with esmtpa (Exim)
id 1ZJmWU-0004FM-Gm; Mon, 27 Jul 2015 13:49:11 -0400
Message-ID: 55b66f05.2090...@hardwarealien.com
Date: Mon, 27 Jul 2015 13:48:53 -0400
From: Carlos Kosloff ckosl...@hardwarealien.com
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 
Icedove/31.7.0
MIME-Version: 1.0
To: Andreas Cadhalpun andreas.cadhal...@googlemail.com
CC: 793...@bugs.debian.org, pkg-openssl-de...@lists.alioth.debian.org
Subject: Re: Bug#793557: clamtk in testing
References: 55b2f005.2040...@hardwarealien.com 55b4bbc2.8020...@googlemail.com 
55b51c8d.2090...@hardwarealien.com 55b55449.4060...@googlemail.com
In-Reply-To: 55b55449.4060...@googlemail.com
Content-Type: multipart/alternative;
 boundary=010907040504040106050004
X-EN-UserInfo: 631228ba0c4b91a2271946e2548350f9:931c98230c6409dcc37fa7e93b490c27
X-EN-AuthUser: ckosl...@hardwarealien.com
Sender:  Carlos Kosloff ckosl...@hardwarealien.com
X-EN-OrigIP: 108.227.118.26
X-EN-OrigHost: 108-227-118-26.lightspeed.miamfl.sbcglobal.net
X-EN-Class: impinc

Bug#793832: mumble-django

apache2_invoke mumble-django postrm: No action required
+ [ -x /usr/bin/logger ]
+ local LOGGER=/usr/bin/logger -p daemon.info -t mumble-django
+ /usr/bin/logger -p daemon.info -t mumble-django apache2_invoke mumble-django 
postrm: No action required
+ [ -n  ]
+ invoke-rc.d --quiet apache2 reload
Job for apache2.service invalid.
+ [ remove = purge ]
+ [ -e /usr/share/mumble-django/pyweb/settings.pyc ]
Purging configuration files for mumble-django (2.13-1) ...
+ which invoke-rc.d
+ [ -x /usr/sbin/invoke-rc.d -a -x /etc/init.d/apache2 ]
+ [ -e /usr/share/apache2/apache2-maintscript-helper ]
+ . /usr/share/apache2/apache2-maintscript-helper
+ [ -n  ]
+ EXPORT_APACHE2_MAINTSCRIPT_HELPER=1
+ [ -n  ]
+ [ -e /etc/apache2/envvars ]
+ . /etc/apache2/envvars
+ unset HOME
+ [  !=  ]
+ SUFFIX=
+ export APACHE_RUN_USER=www-data
+ export APACHE_RUN_GROUP=www-data
+ export APACHE_PID_FILE=/var/run/apache2/apache2.pid
+ export APACHE_RUN_DIR=/var/run/apache2
+ export APACHE_LOCK_DIR=/var/lock/apache2
+ export APACHE_LOG_DIR=/var/log/apache2
+ export LANG=C
+ export LANG
+ echo
+ APACHE2_MAINTSCRIPT_DEBUG=
+ [ -n  ]
+ APACHE2_MAINTSCRIPT_DEFER=
+ dpkg-query -f ${Status} -W apache2
+ grep -q installed
+ [ -z purge ]
+ APACHE2_MAINTSCRIPT_NAME=postrm
+ [ postrm ]
+ APACHE2_MAINTSCRIPT_PACKAGE=mumble-django
+ [ -z mumble-django ]
+ [ -z  ]
+ APACHE2_MAINTSCRIPT_METHOD=purge
+ [ -z  ]
+ APACHE2_MAINTSCRIPT_ARGUMENT=
+ apache2_invoke disconf mumble-django
+ local CMD=disconf
+ local CONF=mumble-django
+ local RCD_ACTION=
+ local invoke_rcd=0
+ local check_switch=
+ local invoke_string=
+ [ -x /usr/sbin/a2disconf ]
+ [ -x /usr/sbin/a2query ]
+ [ -n  ]
+ check_switch=-c
+ invoke_string=configuration
+ rcd_action=reload
+ local a2query_ret=0
+ a2query -c mumble-django
+ a2query_ret=33
+ [ 33 -eq 0 ]
+ [ 33 -eq 32 ]
+ [ 33 -eq 33 ]
+ [ postrm = postrm ]
+ [ purge = purge ]
+ apache2_msg info apache2_invoke postrm: Purging state for mumble-django
+ local PRIORITY=info
+ local MSG=apache2_invoke postrm: Purging state for mumble-django
+ [ -z  ]
+ echo apache2_invoke postrm: Purging state for mumble-django
apache2_invoke postrm: Purging state for mumble-django
+ [ -x /usr/bin/logger ]
+ local LOGGER=/usr/bin/logger -p daemon.info -t mumble-django
+ /usr/bin/logger -p daemon.info -t mumble-django apache2_invoke postrm: 
Purging state for mumble-django
+ a2disconf -p -f -q mumble-django
+ [ -n  ]
+ invoke-rc.d --quiet apache2 reload
Job for apache2.service invalid.
+ [ purge = purge ]
+ dpkg-statoverride --list /var/lib/mumble-django/mumble-django.db3
+ dpkg-statoverride --list /var/lib/mumble-django/mumble-django.db3
+ dpkg-statoverride --list /var/lib/mumble-django/mumble-django.db3
+ rm -rf /var/lib/mumble-django
+ rm -f /etc/munin/plugins/mumble-django
+ rm -f /usr/share/mumble-django/.secret.txt
+ [ -x /etc/init.d/munin-node ]
+ [ -e /usr/share/mumble-django/pyweb/settings.pyc ]
root@crosshair:/var/lib/dpkg/info#

After this, I could purge and clean up system.
Thank you,
--
*Carlos Kosloff*
Office: (954) 283-8828
Cell: (954) 464-8822
Fax: (888) 854-5440

Bug#792921: [sparc64] linking against libx264 crashes runtime linker

2015-07-21 Thread Carlos O'Donell

On Tue, Jul 21, 2015 at 2:49 PM, Andreas Cadhalpun
andreas.cadhal...@googlemail.com wrote:
 On 20.07.2015 17:18, Carlos O'Donell wrote:
 On Mon, Jul 20, 2015 at 3:35 AM, Andreas Cadhalpun
 andreas.cadhal...@googlemail.com wrote:
 Program received signal SIGBUS, Bus error.
 0xf801cda4 in elf_dynamic_do_Rela (skip_ifunc=optimized out, 
 lazy=0, nrelative=optimized out, relsize=optimized out, 
 reladdr=optimized out, map=0xf80100023570) at do-rel.h:111

 Usually a corrupted library. Check md5sums.

 I don't think this problem is caused by a corrupted libx264.

 First, it's also happening on the sparc64 buildds, see e.g. [1].
 Second, I rebuilt the current x264 locally and it shows the same problem.

Does the problem always reproduce or just sometimes?

If it's just sometimes then it's much much harder to figure out what's wrong.

You'll need a dedicated person to track down exactly what is the
concurrency issue and why it's failing.

Cheers,
Carlos.


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

Bug#793539: KDE system settings

2015-07-24 Thread Carlos Kosloff


Package: systemsettings
Version: 4:5.3.2-2
Severity: grave
Tags: stretch,KDE

* What did I do to cause the bug?

I am using the testing branch on an amd64 system with the KDE desktop.
2015/0724 I made a dist-upgrade and found out that my dual monitor setup 
was no longer recognized.
I tried to launch System Settings to fix but got this error instead: 
http://i.imgur.com/RQAOK4c.png

Several launcher icons were also disabled in desktop.

* What did I do to fix?

Downgraded System Settings to stable version, it launched but did not 
work right as the Display applet still was not seeing my monitors.
After that I dist-upgraded again, it went back to behavior previously 
described.


Please help.
Thank you
--
*Carlos Kosloff*
Office: (954) 283-8828
Cell: (954) 464-8822
Fax: (888) 854-5440

Bug#793557: clamtk in testing

2015-07-24 Thread Carlos Kosloff


Package: clamtk
Version: 5.19-1
Severity: grave
Tags: stretch

Dear maintainer,

* Specs

Using KDE desktop, on a Toshiba laptop with amd64 architecture.

* What caused the problem

After a dist-upgrade on 2015/07/24 clamtk does not launch.

* Steps taken to resolve the problem

Reinstalled.
Rebooted computer.
Attempted to launch from CLI.
As user:
command clamtk reports illegal instruction.
As root:
No protocol specified
Gtk-WARNING **: cannot open display: :0 at 
/usr/lib/x86_64-linux-gnu/perl5/5.20/Gtk2.pm line 126.


Please help.
Thank you,
--
*Carlos Kosloff*
Office: (954) 283-8828
Cell: (954) 464-8822
Fax: (888) 854-5440

Bug#792261: 'gbp pq apply' should preserve patch names, just like import/export

2015-07-13 Thread Carlos Maddela

Package: git-buildpackage
Version: 0.6.32
Severity: wishlist
Tags: patch

Hello,

Preserving patch names as the default behaviour for all gbp-pq actions
would simplify its use.

Best regards,

Carlos

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

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

Versions of packages git-buildpackage depends on:
ii  devscripts2.15.5
ii  git   1:2.1.4-2.1
ii  man-db2.7.0.2-5
ii  python2.7.9-1
ii  python-dateutil   2.2-2
ii  python-pkg-resources  17.0-1
ii  python-six1.9.0-3

Versions of packages git-buildpackage recommends:
ii  cowbuilder   0.73
ii  pbuilder 0.215+nmu4
ii  pristine-tar 1.33
ii  python-requests  2.7.0-3

Versions of packages git-buildpackage suggests:
ii  python-notify  0.1.1-4
ii  unzip  6.0-17

-- no debconf information
From 7eeca5adf88254235e8d574a7308a6ec975a57db Mon Sep 17 00:00:00 2001
From: Carlos Maddela madd...@labyrinth.net.au
Date: Mon, 13 Jul 2015 21:02:48 +1000
Subject: [PATCH] Preserve patch name when applying single patch also.

---
 gbp/scripts/common/pq.py | 5 +++--
 tests/13_test_gbp_pq.py  | 2 ++
 2 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/gbp/scripts/common/pq.py b/gbp/scripts/common/pq.py
index 5580426..2bd4187 100644
--- a/gbp/scripts/common/pq.py
+++ b/gbp/scripts/common/pq.py
@@ -296,8 +296,9 @@ def switch_to_pq_branch(repo, branch):
 
 def apply_single_patch(repo, branch, patch, fallback_author, topic=None):
 switch_to_pq_branch(repo, branch)
-apply_and_commit_patch(repo, patch, fallback_author, topic)
-gbp.log.info(Applied %s % os.path.basename(patch.path))
+name = os.path.basename(patch.path)
+apply_and_commit_patch(repo, patch, fallback_author, topic, name=name)
+gbp.log.info(Applied %s % name)
 
 
 def apply_and_commit_patch(repo, patch, fallback_author, topic=None, name=None):
diff --git a/tests/13_test_gbp_pq.py b/tests/13_test_gbp_pq.py
index e78cdd0..70b59f5 100644
--- a/tests/13_test_gbp_pq.py
+++ b/tests/13_test_gbp_pq.py
@@ -101,6 +101,8 @@ class TestApplySinglePatch(testutils.DebianGitTestRepo):
 
 pq.apply_single_patch(self.repo, 'master', patch, None)
 self.assertIn('foo', self.repo.list_files())
+info = self.repo.get_commit_info('HEAD')
+self.assertIn('Gbp-Pq: Name foo.patch', info['body'])
 
 
 class TestWritePatch(testutils.DebianGitTestRepo):
-- 
2.1.4

Bug#788993: Affected by this bug

2015-07-14 Thread Carlos Ramos

Windows 8.1 is pretty common these days. Having this issue fixed is pretty
much required in order to use Debian's samba package as a DC.

Thanks a lot for the hard work.
Cheers.

-- 
Carlos Ramos

Bug#792444: Acknowledgement (postfix-policyd-spf-python doesn't work with IPv6 in /etc/resolv.conf)

2015-07-14 Thread Carlos Carvalho

Scott asked to post the resolv.conf to check. Here it is:

nameserver 192.168.3.18
##nameserver 2801:82:80ff:7f03::2
##nameserver fe80::224:8cff:fe0c:3790%servs
search fisica.ufpr.br

Any of the commented lines doesn't work. They are all local to the mail server
that runs the spf check.


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

Bug#792444: postfix-policyd-spf-python doesn't work with IPv6 in /etc/resolv.conf

2015-07-14 Thread Carlos Carvalho

Package: postfix-policyd-spf-python
Version: 1.3.1-1

Putting a IPv6 address in /etc/resolv.conf breaks spf checks; it always returns
Temperror. Putting the IPv4 address of the same dns server works. It's not a
problem of the dns server because other aplications in the client work
normally with the v6 address.

Perhaps this is a bug in the python3-spf or python3-dns packages but I'm not
sure so I submit the bug here.


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

Bug#792541: 502 Connection closed

2015-07-15 Thread Carlos Maddela

Package: apt-cacher-ng
Version: 0.8.4-1
Severity: important
Tags: patch
Control: found -1 apt-cacher-ng/0.8.2-1

Hello,

Often, when performing 'apt-get update' with apt-cacher-ng, it would
fail with lots of '502 Connection closed' errors, as shown in the attached
apt-cacher.err snippet.  I don't know why no one else has reported this yet,
but maybe it has something to do with slower internet connections.

I thought the bug may have been related to Bug #787289, so I tried different
PipelineDepth values, but it didn't change anything.

I did a bit of debugging and found that the problem first crops up after
this commit:

https://anonscm.debian.org/cgit/apt-cacher-ng/apt-cacher-ng.git/commit/?h=debian/sidid=1716a7a94c0e6bfc0635f2aef6e281c10a30a96c

Without understanding the code entirely, I tried reverting some of the
changes that I thought were suspect, and it seemed to do the trick.
I have attached this patch.  Hopefully, it doesn't cause problems for others.

Best regards,

Carlos

-- Package-specific info:

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

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

Versions of packages apt-cacher-ng depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.56
ii  dpkg   1.18.1
ii  init-system-helpers1.23
ii  libbz2-1.0 1.0.6-8
ii  libc6  2.19-19
ii  libgcc11:5.1.1-13
ii  liblzma5   5.1.1alpha+20120614-2.1
ii  libssl1.0.01.0.2d-1
ii  libstdc++6 5.1.1-13
ii  libsystemd0222-1
ii  libwrap0   7.6.q-25
ii  zlib1g 1:1.2.8.dfsg-2+b1

apt-cacher-ng recommends no packages.

Versions of packages apt-cacher-ng suggests:
ii  avahi-daemon  0.6.31-5
ii  doc-base  0.10.6
ii  libfuse2  2.9.4-1

-- Configuration Files:
/etc/apt-cacher-ng/acng.conf changed [not included]
/etc/apt-cacher-ng/security.conf [Errno 13] Permission denied: 
u'/etc/apt-cacher-ng/security.conf'
/etc/cron.daily/apt-cacher-ng [Errno 2] No such file or directory: 
u'/etc/cron.daily/apt-cacher-ng'

-- debconf information excluded
Sun Jul 12 16:04:11 2015|created socket, fd: 5
Sun Jul 12 16:04:11 2015|Not creating Unix Domain Socket, fifo_path not 
specified
Sun Jul 12 16:04:11 2015|Listening to incoming connections...
Sun Jul 12 16:05:02 2015|Detected incoming connection from the TCP socket
Sun Jul 12 16:05:02 2015|Client name: 192.168.0.1
Sun Jul 12 16:05:02 2015|Detected incoming connection from the TCP socket
Sun Jul 12 16:05:02 2015|Client name: 192.168.0.1
Sun Jul 12 16:05:02 2015|Detected incoming connection from the TCP socket
Sun Jul 12 16:05:02 2015|Client name: 192.168.0.1
Sun Jul 12 16:05:02 2015|Decoded request URI: 
http://ftp.debian.org/debian/dists/experimental/InRelease
Sun Jul 12 16:05:02 2015|Decoded request URI: 
http://www.deb-multimedia.org/dists/sid/InRelease
Sun Jul 12 16:05:02 2015|Decoded request URI: 
http://security.debian.org/dists/testing/updates/InRelease
Sun Jul 12 16:05:02 2015|Processing new job, GET 
http://ftp.debian.org/debian/dists/experimental/InRelease HTTP/1.1
Sun Jul 12 16:05:02 2015|Processing new job, GET 
http://www.deb-multimedia.org/dists/sid/InRelease HTTP/1.1
Sun Jul 12 16:05:02 2015|Processing new job, GET 
http://security.debian.org/dists/testing/updates/InRelease HTTP/1.1
Sun Jul 12 16:05:03 2015|Download started, storeHeader for 
security.debian.org/dists/testing/updates/InRelease, current status: 1
Sun Jul 12 16:05:03 2015|known data hit, don't write to: 
security.debian.org/dists/testing/updates/InRelease
Sun Jul 12 16:05:03 2015|Response header to be sent in the next cycle: 
HTTP/1.1 304 Not Modified
Content-Length: 0
Date: Sun Jul 12 06:05:03 2015
Server: Debian Apt-Cacher NG/0.8.4
X-Original-Source: http://security.debian.org/dists/testing/updates/InRelease
Connection: Keep-Alive


Sun Jul 12 16:05:03 2015|Returning to last state, 6
Sun Jul 12 16:05:03 2015|Download started, storeHeader for 
debmul/dists/sid/InRelease, current status: 1
Sun Jul 12 16:05:03 2015|known data hit, don't write to: 
debmul/dists/sid/InRelease
Sun Jul 12 16:05:03 2015|Response header to be sent in the next cycle: 
HTTP/1.1 304 Not Modified
Content-Length: 0
Date: Sun Jul 12 06:05:03 2015
Server: Debian Apt-Cacher NG/0.8.4
X-Original-Source: http://www.deb-multimedia.org/dists/sid/InRelease
Connection: Keep-Alive


Sun Jul 12 16:05:03 2015|Returning to last state, 6
Sun Jul 12 16:05:04 2015|Decoded request URI: 
http://security.debian.org/dists/testing/updates/main/source/Sources.xz
Sun Jul 12 16:05:04 2015|Processing new job, GET 
http://security.debian.org/dists/testing/updates/main/source/Sources.xz HTTP/1.1
Sun Jul 12 16:05

Bug#792541: 502 Connection closed

2015-07-16 Thread Carlos Maddela

The problem still seems to exist in that version.

More specifically though, I wasn't able to reproduce the bug on my
debian box, which happens to run the apt-cacher-ng proxy. I ran 'apt-get
update' a few times and all seemed okay. However on my ubuntu box, I
still get the error particularly for ppa.launchpad.net repos, and the
problem seemed more pronounced when I was running 'apt-get update' on
both boxes at the same time. These were the repos, if you'd like to
give it a try yourself:

W: Failed to fetch
http://ppa.launchpad.net/webupd8team/java/ubuntu/dists/vivid/main/binary-amd64/Packages

502 Connection closed

W: Failed to fetch
http://ppa.launchpad.net/webupd8team/java/ubuntu/dists/vivid/main/binary-i386/Packages

502 Connection closed

W: Failed to fetch
http://ppa.launchpad.net/webupd8team/tor-browser/ubuntu/dists/vivid/main/binary-amd64/Packages

502 Connection closed

W: Failed to fetch
http://ppa.launchpad.net/webupd8team/tor-browser/ubuntu/dists/vivid/main/binary-i386/Packages

502 Connection closed

Anyway, I've had a look at the code again, and I think I understand now
why the original code which I reverted back to worked for me. No host
would ever be blacklisted since nLostConTolerance always got reset in
the middle of the big while loop. So I understand why your changes were
necessary.

I have retested another build with MAX_RETRY set to 10, and it looks a
little more promising now. Perhaps this would need to be a configurable
variable.

Thanks for all your hard work!

-Carlos

On 17/07/15 02:37, Eduard Bloch wrote:
Control: tags 792541 +pending

Hallo,
* Carlos Maddela [Thu, Jul 16 2015, 09:06:00AM]:
Package: apt-cacher-ng
Version: 0.8.4-1
Severity: important
Tags: patch
Control: found -1 apt-cacher-ng/0.8.2-1

Hello,

Often, when performing 'apt-get update' with apt-cacher-ng, it would
fail with lots of '502 Connection closed' errors, as shown in the attached
apt-cacher.err snippet. I don't know why no one else has reported this yet,
but maybe it has something to do with slower internet connections.

I thought the bug may have been related to Bug #787289, so I tried different
PipelineDepth values, but it didn't change anything.

I did a bit of debugging and found that the problem first crops up after
this commit:

https://anonscm.debian.org/cgit/apt-cacher-ng/apt-cacher-ng.git/commit/?h=debian/sidid=1716a7a94c0e6bfc0635f2aef6e281c10a30a96c

Without understanding the code entirely, I tried reverting some of the
changes that I thought were suspect, and it seemed to do the trick.
I have attached this patch. Hopefully, it doesn't cause problems for others.
Thanks. That's interesting, I found a similar (probably the same) issue
a couple of weeks ago and traced this back to the broken (re)setting of
this nLostConTolerance variable. It seems like the bug has been existing
for a while but the effects were covered up by another code path or just
triggered a reconnection which covered all tracks. When I added TLS
handling, it started shining through.

Could you please test a build from the latest master tree? I guess
https://anonscm.debian.org/cgit/apt-cacher-ng/apt-cacher-ng.git/commit/?h=debian/sidid=f3e8e60f88db4c9aeb6e33acd60da87dca426587
should have fixed your problem (just pushed, wasn't there this morning).

This reminds me on getting out 0.8.5 ASAP :-( ...

Regards,
Eduard.

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

Bug#782559: apt-get complains about unknown options when it's the command that's wrong

2015-07-18 Thread Carlos Maddela

Package: apt
Version: 1.1~exp8
Followup-For: Bug #782559
Control: tags -1 patch

This one has annoyed me a few too many times, so I've had a go at a patch.

Best regards,

Carlos

-- Package-specific info:

-- (no /etc/apt/preferences present) --


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


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

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

Versions of packages apt depends on:
ii  adduser 3.113+nmu3
ii  debian-archive-keyring  2014.3
ii  gnupg   1.4.19-3
ii  gnupg2  2.0.28-3
ii  libapt-pkg4.15  1.1~exp8
ii  libc6   2.19-19
ii  libgcc1 1:5.1.1-14
ii  libstdc++6  5.1.1-14

apt recommends no packages.

Versions of packages apt suggests:
ii  apt-doc 1.1~exp8
ii  dpkg-dev1.18.1
ii  python-apt  1.0.0~beta3
ii  synaptic0.81.4

-- no debconf information
From 0674759ef76eea93a634036b2a0aa2754b164c2d Mon Sep 17 00:00:00 2001
From: Carlos Maddela madd...@labyrinth.net.au
Date: Sat, 18 Jul 2015 07:47:09 +1000
Subject: [PATCH] Fix misleading apt-get error message, when invalid operation
 given.

Bug: http://bugs.debian.org/782559
---
 cmdline/apt-get.cc | 7 ++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/cmdline/apt-get.cc b/cmdline/apt-get.cc
index a285377..cb97193 100644
--- a/cmdline/apt-get.cc
+++ b/cmdline/apt-get.cc
@@ -1702,7 +1702,12 @@ int main(int argc,const char *argv[])	/*{{{*/
    {help,ShowHelp},
{0,0}};
 
-   std::vectorCommandLine::Args Args = getCommandArgs(apt-get, CommandLine::GetCommand(Cmds, argc, argv));
+   const char *Cmd = CommandLine::GetCommand(Cmds, argc, argv);
+   // If no valid command is found, pass empty string instead so
+   // that parsing for apt-get can still be done.
+   if (Cmd == NULL)
+  Cmd = ;
+   std::vectorCommandLine::Args Args = getCommandArgs(apt-get, Cmd);
 
// Set up gettext support
setlocale(LC_ALL,);
-- 
2.1.4

Bug#792921: [sparc64] linking against libx264 crashes runtime linker

2015-07-20 Thread Carlos O'Donell

On Mon, Jul 20, 2015 at 3:35 AM, Andreas Cadhalpun
andreas.cadhal...@googlemail.com wrote:
 Program received signal SIGBUS, Bus error.
 0xf801cda4 in elf_dynamic_do_Rela (skip_ifunc=optimized out, 
 lazy=0, nrelative=optimized out, relsize=optimized out, 
 reladdr=optimized out, map=0xf80100023570) at do-rel.h:111

Usually a corrupted library. Check md5sums.

Cheers,
Carlos.


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

Bug#796820: Package adoption

2015-10-27 Thread Antonio Carlos

Hi,

My name ´s Antonio Carlos and i am interesting on become a maintainer of
this package.


Att,

Antonio Carlos




On Mon, 24 Aug 2015 22:23:31 +0200 Uwe Hermann <u...@hermann-uwe.de> wrote:
> Package: wnpp
> Severity: normal
>
> I request an adopter for the urjtag package.
>
> The package description is:
>  A command line tool for communicating over JTAG (IEEE 1149.1) with
various
>  flash chips, CPUs, boards and JTAG adapters.
>  .
>  It has an open and modular architecture with the ability to write
>  miscellaneous extensions (like board testers, or flash memory
programmers).
>  .
>  This is a (more actively maintained) fork of the 'openwince-jtag'
software.
>
>
> Uwe.
> --
> http://hermann-uwe.de | http://randomprojects.org | http://sigrok.org
>
>

Bug#796820: PACKAGE ADOPTION

2015-10-27 Thread Antonio Carlos

Hi,

I wanna to adopt the package. they  are still disponible ?

Best regards




On Mon, 24 Aug 2015 22:23:31 +0200 Uwe Hermann  wrote:
> Package: wnpp
> Severity: normal
>
> I request an adopter for the urjtag package.
>
> The package description is:
>  A command line tool for communicating over JTAG (IEEE 1149.1) with
various
>  flash chips, CPUs, boards and JTAG adapters.
>  .
>  It has an open and modular architecture with the ability to write
>  miscellaneous extensions (like board testers, or flash memory
programmers).
>  .
>  This is a (more actively maintained) fork of the 'openwince-jtag'
software.
>
>
> Uwe.
> --
> http://hermann-uwe.de | http://randomprojects.org | http://sigrok.org
>
>

Bug#804871: Syslog



Please find syslog here: pastebin.com/dajjZQBc

Bug#804871: syslog


Sorry, botched From header in previous.
Please find syslog here: pastebin.com/dajjZQBc

Bug#804871: Stable installer points to incorrect mirrors



Package: debian-installer
Version: 20150422+deb8u2
Severity: important

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

Kernel: Linux 3.16.0-4-amd64 (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)
ckosloff@8:~$

Dear maintainer,

I recently installed from the latest netinst CD on a VM, the host system 
is Debian Stretch, but the VM is on Jessie.
I selected on install all available options, including backports, but I 
was consistently getting error 100 on updates.

So I checked the sources.list and found two errors:
1.
The second line was pointing to: deb http://ftp.us.debian.org/ 
jessie/updates main contrib non-free
But the correct syntax should replace ftp.us.debian.org with 
security.debian.org

2.
Regarding backports the entry wrote: deb 
http://ftp.us.debian.org/debian/ jessie-backports main contrib non-free
However the backports website reports this: deb 
http://http.debian.net/debian jessie-backports main
Thus there is an extra forward slash after "debian" that should not be 
there, apart from incorrectly addressing the us mirror.

Thank you.

Bug#804871: Stable installer points to incorrect mirrors


Sure, I checked and that is a folder.
Which file exactly do you need?


On 11/12/2015 11:11 AM, Cyril Brulebois wrote:

Is there any chance you could send us the installer's syslog (stored
under /var/log/installer)?

Bug#804871: Stable installer points to incorrect mirrors


Hi Cyril,

Thanks for answer.
1.
I think that we are not referring to the same line.
jessie-updates is in fact there for volatile, I am referring to the one 
above it, that should read security.debian.org, that is the critical one.

2.
OK, but there is an extra forward slash that should not be there, methinks.
Thank you.



On 11/12/2015 11:11 AM, Cyril Brulebois wrote:
Is there any chance you could send us the installer's syslog (stored 
under /var/log/installer)? As for the first issue, are you sure that 
was jessie/updates and not jessie-updates? (References: 
generators/92updates in apt-setup, and 
https://wiki.debian.org/StableUpdates) As for the second issue, what 
the backports site suggests as a generic URL doesn't mean one cannot 
use a specific mirror instead. Mraw, KiBi.

Bug#803721: kdm stopped working and is now stuck on a lightdm saved session

2015-11-01 Thread Carlos Kosloff


Package: kdm
Version: 4:4.11.22-3
Severity: grave

-- System Information:
Debian Release: stretch/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 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 kdm depends on:
ii  adduser 3.113+nmu3
ii  debconf [debconf-2.0] 1.5.57
ii  kde-runtime 4:15.08.2-1
ii  kde-wallpapers-default 4:15.04.2-1
ii  kde-workspace-kgreet-plugins 4:4.11.22-3
ii  libc6 2.19-22
ii  libkdecore5 4:4.14.13-1
ii  libkdeui5 4:4.14.13-1
ii  libkio5 4:4.14.13-1
ii  libknewstuff3-4 4:4.14.13-1
ii  libkworkspace4abi2 4:4.11.22-3
ii  libpam0g 1.1.8-3.1
ii  libqimageblitz4 1:0.0.6-4
ii  libqt4-svg 4:4.8.7+dfsg-3
ii  libqt4-xml 4:4.8.7+dfsg-3
ii  libqtcore4 4:4.8.7+dfsg-3
ii  libqtgui4 4:4.8.7+dfsg-3
ii  libstdc++6 5.2.1-22
ii  libx11-6 2:1.6.3-1
ii  libxau6 1:1.0.8-1
ii  libxdmcp6 1:1.1.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  lsb-base 9.20150917

Versions of packages kdm recommends:
ii  konsole [x-terminal-emulator] 4:15.08.2-1
ii  logrotate 3.8.7-2
ii  openbox [x-window-manager] 3.6.1-2
ii  xserver-xorg [xserver] 1:7.7+12
ii  xterm [x-terminal-emulator]320-1

Versions of packages kdm suggests:
ii  kde-wallpapers  4:15.04.2-1
ii  kdepasswd   4:15.08.1-1

-- debconf information:
  kdm/daemon_name: /usr/bin/kdm
  kdm/stop_running_server_with_children: false

Dear maintainer:

KDE is migrating to Plasma5 and many things break in the process.
libqt5x11extras5 migrated into testing without their dependencies, but 
even after downgrading kdm did not work.

Computer cannot start normally, I have to start it with: startx startkde.
I tried to get a dm to work so installed lightdm, it did not work either.
Neither does sddm.
I completely purged lightdm, then issued command 'apt-get autoremove 
--purge', also removed all remnants in /usr/share.
Still, kdm starts and goes to a lightdm saved session, which of course 
fails.
I cannot understand how this can happen, as my system settings are set 
to start with a clean session.

How can I delete this saved session that is stuck somewhere?
I have been working on this for a while, some upgrades have been done to 
some nvidia packages and things improved somewhat, kdm still does not 
launch and goes to that saved session.

Please help.

Bug#798906: sddm still not working

2015-11-01 Thread Carlos Kosloff


Dear maintainer,
We are definitely not talking about the same issue.
I never tried to start sddm with another dm running, it just crashes 
after reboot.
After the latest update to nvidia, today Sunday Nov. 1, 2015, it does 
not crash that bad, but it still gives me a garbled and unusable 
display, I cannot complete login through it.
I have to go back to terminal and type as user: startx startkde to get 
to the desktop, sddm will not start normally.
A bug was reported for glx-alternative-nvidia v.0.60, in testing I have 
0.51 and unstable is at 0.63.
I know that this is not reproducible in all systems, as I said before, I 
have another computer with a different type of card and it works.
Please don't downgrade severity just because you cannot reproduce, many 
users are affected.

Bug#798906: still not working after upgrade

2015-11-03 Thread Carlos Kosloff



Today (20151003) brought sddm to version 0.12.0-5, still not working 
with same results.

Bug#803721: More info

2015-11-02 Thread Carlos Kosloff


This is my kdm.log:


Note that your system uses syslog. All of kdm's internally generated 
messages

(i.e., not from libraries and external programs/scripts it uses) go to the
daemon.* syslog facility; check your syslog configuration to find out to 
which
file(s) it is logged. PAM logs messages related to authentication to 
authpriv.*.




X.Org X Server 1.17.2
Release Date: 2015-06-16
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.2.0-1-amd64 x86_64 Debian
Current Operating System: Linux crosshair 4.2.0-1-amd64 #1 SMP Debian 
4.2.3-2 (2015-10-14) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-1-amd64 
root=UUID=fe9296ba-c381-4716-b003-f1c83fb2be16 ro quiet

Build Date: 06 October 2015  07:27:47AM
xorg-server 2:1.17.2-3 (http://www.debian.org/support)
Current version of pixman: 0.33.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Nov  1 09:18:44 2015
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
klauncher(2100) kdemain: No DBUS session-bus found. Check if you have 
started the DBUS server.

kdeinit4: Communication error with launcher. Exiting!
kdmgreet(2072)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned 
initialize() D-Bus call failed:  "Not connected to D-Bus server"


kdmgreet(2072)/kdecore (K*TimeZone*): No time zone information obtained 
from ktimezoned

*Error: "/var/tmp/kdecache-kdm" is owned by uid 107 instead of uid 126.*
(II) Server terminated successfully (0). Closing log file.

X.Org X Server 1.17.2
Release Date: 2015-06-16
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.2.0-1-amd64 x86_64 Debian
Current Operating System: Linux crosshair 4.2.0-1-amd64 #1 SMP Debian 
4.2.3-2 (2015-10-14) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-1-amd64 
root=UUID=fe9296ba-c381-4716-b003-f1c83fb2be16 ro quiet

Build Date: 06 October 2015  07:27:47AM
xorg-server 2:1.17.2-3 (http://www.debian.org/support)
Current version of pixman: 0.33.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Nov  1 10:49:15 2015
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"

X.Org X Server 1.17.2
Release Date: 2015-06-16
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.2.0-1-amd64 x86_64 Debian
Current Operating System: Linux crosshair 4.2.0-1-amd64 #1 SMP Debian 
4.2.3-2 (2015-10-14) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-1-amd64 
root=UUID=fe9296ba-c381-4716-b003-f1c83fb2be16 ro quiet

Build Date: 06 October 2015  07:27:47AM
xorg-server 2:1.17.2-3 (http://www.debian.org/support)
Current version of pixman: 0.33.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Nov  1 10:50:09 2015
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
klauncher(2103) kdemain: No DBUS session-bus found. Check if you have 
started the DBUS server.

kdeinit4: Communication error with launcher. Exiting!
kdmgreet(2078)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned 
initialize() D-Bus call failed:  "Not connected to D-Bus server"


kdmgreet(2078)/kdecore (K*TimeZone*): No time zone information obtained 
from ktimezoned

(II) Server terminated successfully (0). Closing log file.

X.Org X Server 1.17.2
Release Date: 2015-06-16
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.2.0-1-amd64 x86_64 Debian
Current Operating System: Linux crosshair 4.2.0-1-amd64 #1 SMP Debian 
4.2.3-2 (2015-10-14) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-1-amd64 
root=UUID=fe9296ba-c381-4716-b003-f1c83fb2be16 ro quiet

Build Date: 06 October 2015  07:27:47AM
xorg-server 2:1.17.2-3 (http://www.debian.org/support)
Current version of pixman: 0.33.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file,

Bug#803721: Missing directory

2015-11-02 Thread Carlos Kosloff



Today's upgrade (20151002) brought upgrades to the glx-alternative-* 
packages, they are now at version 0.6.93

However, that failed to fix kdm, which still shows a lightdm screen.
However, I think that I understand why this happens.
This is the output of the latest systemctl status kdm.service -l:

● kdm.service - LSB: X display manager for KDE

   Loaded: loaded (/etc/init.d/kdm)

   Active: active (running) since Mon 2015-11-02 20:50:38 EST; 2min 53s ago

 Docs: man:systemd-sysv-generator(8)

  Process: 1195 ExecStart=/etc/init.d/kdm start (code=exited, status=0/SUCCESS)

   CGroup: /system.slice/kdm.service

   ├─1426 /usr/bin/kdm -config /var/run/kdm/kdmrc

   └─1441 /usr/lib/xorg/Xorg :0 vt7 -br -nolisten tcp -auth 
/var/run/xauth/A:0-GFx8Ya

Nov 02 20:50:38 crosshair systemd[1]: Starting LSB: X display manager for KDE...

Nov 02 20:50:38 crosshair kdm[1195]: Starting K Display Manager: kdm.

Nov 02 20:50:38 crosshair systemd[1]: Started LSB: X display manager for KDE.

Nov 02 20:50:40 crosshair kdm_greet[2069]: Cannot load 
/usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory

Nov 02 20:50:48 crosshair kdm[2066]: :0[2066]: pam_unix(kdm:session): session 
opened for user ckosloff by (uid=0)


Please note the line before the last one: .default.face is missing.
So, how fix? I already reinstalled kdm to no avail.

Bug#798906: Acknowledgement (sddm crashes on boot)

2015-11-02 Thread Carlos Kosloff


Hi all,
I do have an nvidia card, as I previously reported.
I did see bug 799948, and entered sddm in the video group, right before 
my user, comma-separated.
Also, today's dist-upgrade brought glx-alternative-* to 0.6.93 so 
nothing happening now is related to that bug.
sddm never worked since I posted this bug, it does not work now either, 
but at least I am not getting a black screen.

The display however is unusable, cannot complete login to my kde desktop.
Kdm does not work either, I have to use startx startkde, to get a 
somewhat usable system.

Any ideas?

Bug#791473: [git-buildpackage/master] import-orig: Honour --debian-branch option when importing into an empty repo.

2015-10-19 Thread Carlos Maddela

tag 791473 pending
thanks

Date:   Fri Aug 14 09:59:29 2015 +0200
Author: Carlos Maddela <madd...@labyrinth.net.au>
Commit ID: 279e946f139c166a7b48a16b89b8cac38d766622
Commit URL: 
https://honk.sigxcpu.org/gitweb/?p=git-buildpackage.git;a=commitdiff;h=279e946f139c166a7b48a16b89b8cac38d766622
Patch URL: 
https://honk.sigxcpu.org/gitweb/?p=git-buildpackage.git;a=commitdiff_plain;h=279e946f139c166a7b48a16b89b8cac38d766622

import-orig: Honour --debian-branch option when importing into an empty 
repo.

Closes: #791473

A snapshot build including this change will be available at
http://honk.sigxcpu.org:8001/job/git-buildpackage/

Bug#790890: [git-buildpackage/master] Allow exported patches to be renumbered and the patch number prefix format to be specified as an option

2015-10-19 Thread Carlos Maddela

tag 790890 pending
thanks

Date:   Fri Jul 3 03:27:39 2015 +1000
Author: Carlos Maddela <madd...@labyrinth.net.au>
Commit ID: 97c7a32d82631dba910d8632478fc093cbe2bcda
Commit URL: 
https://honk.sigxcpu.org/gitweb/?p=git-buildpackage.git;a=commitdiff;h=97c7a32d82631dba910d8632478fc093cbe2bcda
Patch URL: 
https://honk.sigxcpu.org/gitweb/?p=git-buildpackage.git;a=commitdiff_plain;h=97c7a32d82631dba910d8632478fc093cbe2bcda

Allow exported patches to be renumbered and the patch number prefix format 
to be specified as an option

Now that gbp-pq preserves patch names on import and export the
--[no-]patch-numbers options have been rendered largely useless unless
the patch queue commits are amended with the Gbp[-Pq]: Name tags
removed. The options remain useful if support for renumbering is
added. It's also handy to allow the choice of the format to use
for the numeric prefixes.

Closes: #790890
Signed-off-by: Guido GÃ¼nther <a...@sigxcpu.org>

A snapshot build including this change will be available at
http://honk.sigxcpu.org:8001/job/git-buildpackage/

Bug#790889: [git-buildpackage/master] Add support for referencing existing local repositories when cloning repositories

2015-10-19 Thread Carlos Maddela

tag 790889 pending
thanks

Date:   Fri Jul 3 03:27:50 2015 +1000
Author: Carlos Maddela <madd...@labyrinth.net.au>
Commit ID: da4d469012e74936bc930ba7e726d19380411baa
Commit URL: 
https://honk.sigxcpu.org/gitweb/?p=git-buildpackage.git;a=commitdiff;h=da4d469012e74936bc930ba7e726d19380411baa
Patch URL: 
https://honk.sigxcpu.org/gitweb/?p=git-buildpackage.git;a=commitdiff_plain;h=da4d469012e74936bc930ba7e726d19380411baa

Add support for referencing existing local repositories when cloning 
repositories

On the off chance you forget to clone a git repo for a debian package
with gbp-clone instead of git-clone, it is handy to be able to
reference the local copy you already have when re-cloning the repo with
gbp-clone, in the same way that git-clone allows you to with the
--reference option.

Closes: #790889
Signed-off-by: Guido GÃ¼nther <a...@sigxcpu.org>

A snapshot build including this change will be available at
http://honk.sigxcpu.org:8001/job/git-buildpackage/

Bug#737079: nscd crashes on netgroup lookups

2015-10-14 Thread Carlos O'Donell

On Wed, Oct 14, 2015 at 4:28 PM, Arthur de Jong <adej...@debian.org> wrote:
> On Wed, 2015-10-14 at 07:56 +, Mike Gabriel wrote:
>> The Debian Edu team heavily relies on NIS netgroups coming from
>> LDAP. So any help with this in Debian jessie is highly appreciated!!!
>
> The last time I looked at nscd code I was not very happy ;) Also, nscd
> has a long history of instability and returning incorrect results.

The upstream glibc community has been working hard to rectify these
issues, and Red Hat in particular spent a lot of time making the
netgroup caching as bullet-proof as possible. If you have real bugs,
please file them upstream and come talk to the community.

> Btw, if anyone thinks this is something that libnss-ldapd does wrong,
> please let me know. Not all NSS interfaces are consistent in terms of
> memory management, return codes, etc. so there could be something
> wrong.

They should be consistent. Again, if you find something wrong, please
file a bug. The upstream glibc community is radically different now
and certainly more accepting of discussions on these issues.

Cheers,
Carlos.

Bug#790890: [git-buildpackage/master] Allow exported patches to be renumbered and the patch number prefix format to be specified as an option

2015-07-10 Thread Carlos Maddela

tag 790890 pending
thanks

Date:   Fri Jul 3 03:27:39 2015 +1000
Author: Carlos Maddela madd...@labyrinth.net.au
Commit ID: 97c7a32d82631dba910d8632478fc093cbe2bcda
Commit URL: 
https://honk.sigxcpu.org/gitweb/?p=git-buildpackage.git;a=commitdiff;h=97c7a32d82631dba910d8632478fc093cbe2bcda
Patch URL: 
https://honk.sigxcpu.org/gitweb/?p=git-buildpackage.git;a=commitdiff_plain;h=97c7a32d82631dba910d8632478fc093cbe2bcda

Allow exported patches to be renumbered and the patch number prefix format 
to be specified as an option

Now that gbp-pq preserves patch names on import and export the
--[no-]patch-numbers options have been rendered largely useless unless
the patch queue commits are amended with the Gbp[-Pq]: Name tags
removed. The options remain useful if support for renumbering is
added. It's also handy to allow the choice of the format to use
for the numeric prefixes.

Closes: #790890
Signed-off-by: Guido GÃ¼nther a...@sigxcpu.org

A snapshot build including this change will be available at
http://honk.sigxcpu.org:8001/job/git-buildpackage/
  


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

Bug#790889: [git-buildpackage/master] Add support for referencing existing local repositories when cloning repositories

2015-07-10 Thread Carlos Maddela

tag 790889 pending
thanks

Date:   Fri Jul 3 03:27:50 2015 +1000
Author: Carlos Maddela madd...@labyrinth.net.au
Commit ID: da4d469012e74936bc930ba7e726d19380411baa
Commit URL: 
https://honk.sigxcpu.org/gitweb/?p=git-buildpackage.git;a=commitdiff;h=da4d469012e74936bc930ba7e726d19380411baa
Patch URL: 
https://honk.sigxcpu.org/gitweb/?p=git-buildpackage.git;a=commitdiff_plain;h=da4d469012e74936bc930ba7e726d19380411baa

Add support for referencing existing local repositories when cloning 
repositories

On the off chance you forget to clone a git repo for a debian package
with gbp-clone instead of git-clone, it is handy to be able to
reference the local copy you already have when re-cloning the repo with
gbp-clone, in the same way that git-clone allows you to with the
--reference option.

Closes: #790889
Signed-off-by: Guido GÃ¼nther a...@sigxcpu.org

A snapshot build including this change will be available at
http://honk.sigxcpu.org:8001/job/git-buildpackage/
  


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

Bug#797271: Synaptic false positive, does not launch

2015-08-28 Thread Carlos Kosloff


Package: synaptic
Version: 0.81.4
Severity: grave
Tags: stretch

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

Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.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 synaptic depends on:
ii  hicolor-icon-theme   0.13-1
ii  libapt-inst1.5   1.0.9.10
ii  libapt-pkg4.12   1.0.9.10
ii  libatk1.0-0  2.16.0-2
ii  libc62.19-19
ii  libcairo-gobject21.14.2-2
ii  libcairo21.14.2-2
ii  libept1.4.12 1.0.12.1
ii  libgcc1  1:5.1.1-14
ii  libgdk-pixbuf2.0-0   2.31.5-1
ii  libglib2.0-0 2.44.1-1.1
ii  libgtk-3-0   3.16.6-1
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libstdc++6   5.1.1-14
ii  libvte-2.90-91:0.36.3-1
ii  libx11-6 2:1.6.3-1
ii  libxapian22  1.2.21-1
ii  libxext6 2:1.3.3-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages synaptic recommends:
ii  gksu   2.0.2-9
ii  libgtk2-perl   2:1.2495-1
ii  policykit-10.105-11
ii  rarian-compat  0.8.1-6

Versions of packages synaptic suggests:
ii  apt-xapian-index 0.47
ii  deborphan1.7.28.8-0.2
pn  dwww none
ii  menu 2.1.47
pn  software-properties-gtk  none
ii  tasksel  3.33

-- no debconf information

Dear maintainer,

I did not do anything except dist-upgrade my system with apt-get.
All of a sudden synaptic will not launch.
Reports a false positive, bad password given for root.
This is not correct because I can launch synaptic from console as root.
I think that this bug arises from a faulty implementation of policykit-1
Thank you,
--
*Carlos Kosloff*

Bug#797494: gimagereader does not install dependencies

2015-08-30 Thread Carlos Kosloff


Package: gimagereader
Version: 2.93-2
Severity: normal

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

Kernel: Linux 3.16.0-4-amd64 (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 gimagereader depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  libc62.19-18
ii  libcairomm-1.0-1 1.10.0-1.1
ii  libgcc1  1:4.9.2-10
ii  libglib2.0-0 2.42.1-1
ii  libglibmm-2.4-1c2a   2.42.0-1
ii  libgtk-3-0   3.14.5-1
ii  libgtkmm-3.0-1   3.14.0-1
ii  libgtkspellmm-3.0-0  3.0.3+dfsg-1
ii  libpangomm-1.4-1 2.34.0-1.1
ii  libpoppler-glib8 0.26.5-2
ii  libsane  1.0.24-8
ii  libsigc++-2.0-0c2a   2.4.0-1
ii  libstdc++6   4.9.2-10
ii  libtesseract33.03.03-1

Dear maintainer,

The issue is that this package does not install the dependencies it needs.
First, it required to install libtesseract3, which should have been 
installed automatically.
Second, it warns about missing a spellchecker, there is a link to 
install but the link does not work, and I don't know what packages it 
requires.

Thank you,
--
*Carlos Kosloff*
Office: (954) 283-8828
Cell: (954) 464-8822
Fax: (888) 854-5440

Bug#797494: Snapshot 2

2015-08-30 Thread Carlos Kosloff



--
*Carlos Kosloff*

Bug#798906: sddm crashes on boot

2015-09-13 Thread Carlos Kosloff

16:20:54 crosshair sddm[1014]: Socket server stopping...
Sep 12 16:20:54 crosshair sddm[1014]: Socket server stopped.
Sep 12 16:20:54 crosshair sddm[1014]: Display server stopping...
Sep 12 16:20:54 crosshair sddm[1014]: Display server stopped.
Sep 12 16:20:54 crosshair sddm[1014]: Running display stop script  
"/usr/share/sddm/scripts/Xstop"

Sep 12 16:20:54 crosshair sddm[1014]: Greeter stopping...
Sep 12 16:20:54 crosshair sddm[1014]: QProcess: Destroyed while process 
("/usr/lib/x86_64-linux-gnu/sddm/sddm-helper") is still running.
Sep 12 16:20:54 crosshair systemd[1]: Stopped Simple Desktop Display 
Manager.
Sep 12 16:20:54 crosshair polkitd(authority=local)[998]: Unregistered 
Authentication Agent for unix-process:2817:43654 (system bus name :1.28, 
object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale 
en_US.UTF-8) (disconnected from bus)

Sep 12 16:20:57 crosshair systemd-logind[853]: Removed session 1.
Sep 12 16:20:57 crosshair systemd[1]: Stopping User Manager for UID 122...
Sep 12 16:20:57 crosshair systemd[1638]: Stopped target Default.
Sep 12 16:20:57 crosshair systemd[1638]: Reached target Shutdown.
Sep 12 16:20:57 crosshair systemd[1638]: Stopped target Basic System.
Sep 12 16:20:57 crosshair systemd[1638]: Stopped target Paths.
Sep 12 16:20:57 crosshair systemd[1638]: Stopped target Sockets.
Sep 12 16:20:57 crosshair systemd[1638]: Stopped target Timers.
Sep 12 16:20:57 crosshair systemd[1638]: Starting Exit the Session...
Sep 12 16:20:57 crosshair systemd[1638]: Received SIGRTMIN+24 from PID 
2831 (kill).
Sep 12 16:20:57 crosshair systemd[1642]: pam_unix(systemd-user:session): 
session closed for user sddm

Sep 12 16:20:57 crosshair systemd[1]: Stopped User Manager for UID 122.
Sep 12 16:20:57 crosshair systemd[1]: Removed slice user-122.slice.
 
---
●sddm.service - Simple Desktop Display Manager
   Loaded: loaded (/lib/systemd/system/sddm.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: start-limit) since Sat 2015-09-12 21:52:34 
EDT; 12min ago

 Docs: man:sddm(1)
   man:sddm.conf(5)
  Process: 1639 ExecStartPre=/bin/sh -c [ "$(cat 
/etc/X11/default-display-manager 2>/dev/null)" = "/usr/bin/sddm" ] 
(code=exited, status=1/FAILURE)


Thank you,

Carlos Kosloff

Bug#798906: sddm crashes on boot

2015-09-16 Thread Carlos Kosloff


I could not completely understand what the maintainer wrote, because:
1.
The failure occurred after I purged leftovers from packages previously 
removed by dist-upgrade, not after the dist-upgrade itself.

It did start normally after the dist-upgrade.
2.
There was no other dm installed. I installed kdm after the crash, in 
order to get a normal boot.
Anyway, no problem, I will stop kdm from tty1, and attempt to launch 
sddm tomorrow.

Will keep you posted, thank you.

On 09/16/2015 07:11 AM, Maximiliano Curia wrote:
I couldn't reproduce the bug as reported. But since the log showed 
starting sddm from tty1 after an upgrade I tested sddm with a running 
display-manager, it fails in similar ways to the reported error. 
Either having an X on tty7, an non-stopped kdm, lightdm, or any other 
display manager running in tty7 would fail. I think that sddm is 
failing to detect the 'seat' already in use. I'll keep on 
investigating this issue. In the mean time, it would be nice to if you 
could check if stopping a running display manager before starting sddm 
allows sddm to work for you, as this would confirm that we are talking 
about the same issue. Happy hacking,

Bug#798906: sddm crashes on boot


Here is additional info.
From terminal as root I stopped kdm.service and started sddm, which 
failed to start, reports follow.

This is output of 'systemctl status sddm.service'.

● sddm.service - Simple Desktop Display Manager
   Loaded: loaded (/lib/systemd/system/sddm.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: start-limit) since Sat 2015-09-12 21:52:34 
EDT; 12min ago

 Docs: man:sddm(1)
   man:sddm.conf(5)
  Process: 1639 ExecStartPre=/bin/sh -c [ "$(cat 
/etc/X11/default-display-manager 2>/dev/null)" = "/usr/bin/sddm" ] 
(code=exited, status=1/FAILURE)


Output of 'journal -xe' is much larger, Debian paste would not take it 
so had to use pastebin.

pastebin.com/DQ9WBp4Y

After setting sddm as default-display-manager in /etc/X11, and 
rebooting, I got a completely black screen.

Had to tty again and set kdm back as default to get normal boot again.
I think that severity is grave since sddm is unusable.



On 09/16/2015 07:11 AM, Maximiliano Curia wrote:
I couldn't reproduce the bug as reported. But since the log showed 
starting sddm from tty1 after an upgrade I tested sddm with a running 
display-manager, it fails in similar ways to the reported error. 
Either having an X on tty7, an non-stopped kdm, lightdm, or any other 
display manager running in tty7 would fail. I think that sddm is 
failing to detect the 'seat' already in use. I'll keep on 
investigating this issue. In the mean time, it would be nice to if you 
could check if stopping a running display manager before starting sddm 
allows sddm to work for you, as this would confirm that we are talking 
about the same issue. Happy hacking,

Bug#798906: sddm crashes on boot


The following is info from lshw, as root:

 *-display
description: VGA compatible controller
product: GM107 [GeForce GTX 750 Ti]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@:06:00.0
version: a2
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller 
bus_master cap_list rom

configuration: driver=nvidia latency=0
resources: irq:60 memory:fd00-fdff 
memory:c000-cfff memory:d000-d1ff ioport:c000(size=128) 
memory:fe00-fe07


This is output from inxi -G

   Graphics:  Card: NVIDIA GM107 [GeForce GTX 750 Ti]
   Display Server: X.Org 1.17.2 driver: nvidia Resolution: 
1680x1050@59.95hz, 1680x1050@59.95hz
   GLX Renderer: GeForce GTX 750 Ti/PCIe/SSE2 GLX Version: 
4.4.0 NVIDIA 340.76


This is sddm.log

[19:55:07.100] (II) DAEMON: Initializing...
[19:55:07.104] (II) DAEMON: Starting...
[19:55:07.104] (II) DAEMON: Adding new display on vt 7 ...
[19:55:07.104] (II) DAEMON: Display server starting...
[19:55:07.104] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth 
/var/run/sddm/{3a2e4a8d-d349-4df7-be14-44161c6cd3a4} -background none 
-noreset -displayfd 19 vt7
[19:55:07.920] (II) DAEMON: Running display setup script 
"/usr/share/sddm/scripts/Xsetup"

[19:55:07.921] (II) DAEMON: Display server started.
[19:55:07.921] (II) DAEMON: Socket server starting...
[19:55:07.921] (II) DAEMON: Socket server started.
[19:55:07.921] (II) DAEMON: Greeter starting...
[19:55:07.922] (II) DAEMON: Adding cookie to 
"/var/run/sddm/{3a2e4a8d-d349-4df7-be14-44161c6cd3a4}"

[19:55:07.929] (II) DAEMON: Greeter session started successfully
[19:55:08.036] (II) DAEMON: Message received from greeter: Connect
[19:55:41.464] (WW) DAEMON: Signal received: SIGINT
[19:55:41.464] (WW) DAEMON: Error from greeter session: "Process crashed"
[19:55:41.464] (WW) DAEMON: Auth: sddm-helper crashed (exit code 0)
[19:55:41.464] (WW) DAEMON: Error from greeter session: "Process crashed"
[19:55:41.464] (II) DAEMON: Auth: sddm-helper exited successfully
[19:55:41.464] (II) DAEMON: Greeter stopped.
[19:55:41.464] (II) DAEMON: Socket server stopping...
[19:55:41.464] (II) DAEMON: Socket server stopped.
[19:55:41.464] (II) DAEMON: Display server stopping...
[19:55:41.474] (II) DAEMON: Display server stopped.
[19:55:41.474] (II) DAEMON: Running display stop script 
"/usr/share/sddm/scripts/Xstop"


This is /etc/sddm/Xsession

#! /bin/sh
# Xsession - run as user

session=$1

# Note that the respective logout scripts are not sourced.
case $SHELL in
  */bash)
[ -z "$BASH" ] && exec $SHELL $0 "$@"
set +o posix
[ -f /etc/profile ] && . /etc/profile
if [ -f $HOME/.bash_profile ]; then
  . $HOME/.bash_profile
elif [ -f $HOME/.bash_login ]; then
  . $HOME/.bash_login
elif [ -f $HOME/.profile ]; then
  . $HOME/.profile
fi
;;
  */zsh)
[ -z "$ZSH_NAME" ] && exec $SHELL $0 "$@"
emulate -R zsh
[ -d /etc/zsh ] && zdir=/etc/zsh || zdir=/etc
zhome=${ZDOTDIR:-$HOME}
# zshenv is always sourced automatically.
[ -f $zdir/zprofile ] && . $zdir/zprofile
[ -f $zhome/.zprofile ] && . $zhome/.zprofile
[ -f $zdir/zlogin ] && . $zdir/zlogin
[ -f $zhome/.zlogin ] && . $zhome/.zlogin
setopt shwordsplit noextendedglob
;;
  */csh|*/tcsh)
# [t]cshrc is always sourced automatically.
# Note that sourcing csh.login after .cshrc is non-standard.
xsess_tmp=`mktemp /tmp/xsess-env-XX`
$SHELL -c "if (-f /etc/csh.login) source /etc/csh.login; if (-f 
~/.login) source ~/.login; /bin/sh -c 'export -p' >! $xsess_tmp"

. $xsess_tmp
rm -f $xsess_tmp
;;
  *) # Plain sh, ksh, and anything we do not know.
[ -f /etc/profile ] && . /etc/profile
[ -f $HOME/.profile ] && . $HOME/.profile
;;
esac

# invoke global X session script
. /etc/X11/Xsession

I purged sddm and reinstalled after reboot, mandatory sddm-theme-breeze 
is installed, so is maui.

However, I do not see /etc/sddm.conf file
I have not set sddm as default manager, and will reboot.
Will post next, sddm log after crash.


On 09/17/2015 12:13 PM, Maximiliano Curia wrote:

¡Hola Carlos!

El 2015-09-17 a las 10:32 -0400, Carlos Kosloff escribió:
After setting sddm as default-display-manager in /etc/X11, and 
rebooting, I got a completely black screen.


Having to set the default-display-manager in order to start the 
display manager is working as intended.


The black screen is clearly not. It could be useful to have just the 
sddm related logs of this last error. But there are some known black 
screen bugs see the upstream related issues here:


https://github.com/sddm/sddm/labels/crash%

Bug#798906: reset-failed command did not work



As root: 'systemctl reset-failed sddm' throws error.
Job exited with error code 0, for some reason shell redirection did not 
work for output of this command.

Thank you.

Bug#798906: Correction


Previous message should read 'I have NOW set sddm as default...'

Bug#798906: sddm crashes on boot


This is sddm.log after expected crash.

[19:55:07.100] (II) DAEMON: Initializing...
[19:55:07.104] (II) DAEMON: Starting...
[19:55:07.104] (II) DAEMON: Adding new display on vt 7 ...
[19:55:07.104] (II) DAEMON: Display server starting...
[19:55:07.104] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth 
/var/run/sddm/{3a2e4a8d-d349-4df7-be14-44161c6cd3a4} -background none 
-noreset -displayfd 19 vt7
[19:55:07.920] (II) DAEMON: Running display setup script 
"/usr/share/sddm/scripts/Xsetup"

[19:55:07.921] (II) DAEMON: Display server started.
[19:55:07.921] (II) DAEMON: Socket server starting...
[19:55:07.921] (II) DAEMON: Socket server started.
[19:55:07.921] (II) DAEMON: Greeter starting...
[19:55:07.922] (II) DAEMON: Adding cookie to 
"/var/run/sddm/{3a2e4a8d-d349-4df7-be14-44161c6cd3a4}"

[19:55:07.929] (II) DAEMON: Greeter session started successfully
[19:55:08.036] (II) DAEMON: Message received from greeter: Connect
[19:55:41.464] (WW) DAEMON: Signal received: SIGINT
[19:55:41.464] (WW) DAEMON: Error from greeter session: "Process crashed"
[19:55:41.464] (WW) DAEMON: Auth: sddm-helper crashed (exit code 0)
[19:55:41.464] (WW) DAEMON: Error from greeter session: "Process crashed"
[19:55:41.464] (II) DAEMON: Auth: sddm-helper exited successfully
[19:55:41.464] (II) DAEMON: Greeter stopped.
[19:55:41.464] (II) DAEMON: Socket server stopping...
[19:55:41.464] (II) DAEMON: Socket server stopped.
[19:55:41.464] (II) DAEMON: Display server stopping...
[19:55:41.474] (II) DAEMON: Display server stopped.
[19:55:41.474] (II) DAEMON: Running display stop script 
"/usr/share/sddm/scripts/Xstop"


In order to get back to desktop I had to go Ctl + Alt + F1, login in as 
root and hard code /etc/X11/default-display-manager back to kdm.
I know that sddm works, at least on some computers, in fact I have 
another one with sddm and it works.
Problem is this computer, it did not even want to start with sddm, I had 
to turn it off manually and reboot it.

Thank you.


On 09/17/2015 12:13 PM, Maximiliano Curia wrote:

¡Hola Carlos!

El 2015-09-17 a las 10:32 -0400, Carlos Kosloff escribió:
After setting sddm as default-display-manager in /etc/X11, and 
rebooting, I got a completely black screen.


Having to set the default-display-manager in order to start the 
display manager is working as intended.


The black screen is clearly not. It could be useful to have just the 
sddm related logs of this last error. But there are some known black 
screen bugs see the upstream related issues here:


https://github.com/sddm/sddm/labels/crash%2Fwhitescreen

So the next question is, what video card are you using? Which video 
driver is that using? Is it showing the mouse cursor in the black screen?


Could you test changing the theme to a simpler one, like maui, 
installing the sddm-theme-maui package and setting the current theme 
to it in the /etc/sddm.conf file?


If the file is not created simply adding this to it would be enough:
[Theme]
Current=maui

Happy hacking,

Bug#800409: More on synaptic failures.

2015-10-01 Thread Carlos Kosloff


Dear maintainer,

As user 'gksu synaptic' launches the program, then it asks for root 
password and finishes launch.

Lots of warnings:
https://paste.debian.net/314150/

ckosloff@crosshair:~$ gksu

(synaptic:14435): GLib-GObject-WARNING **: The property GtkImage:stock is 
deprecated and shouldn't be used anymore. It will be removed in a future 
version.

(synaptic:14435): GLib-GObject-WARNING **: The property GtkMisc:yalign is 
deprecated and shouldn't be used anymore. It will be removed in a future 
version.

(synaptic:14435): GLib-GObject-WARNING **: The property 
GtkImageMenuItem:use-stock is deprecated and shouldn't be used anymore. It will 
be removed in a future version.

(synaptic:14435): GLib-GObject-WARNING **: The property GtkImageMenuItem:image 
is deprecated and shouldn't be used anymore. It will be removed in a future 
version.

(synaptic:14435): GLib-GObject-WARNING **: The property 
GtkSettings:gtk-menu-images is deprecated and shouldn't be used anymore. It 
will be removed in a future version.

(synaptic:14435): GLib-GObject-WARNING **: The property GtkToolButton:stock-id 
is deprecated and shouldn't be used anymore. It will be removed in a future 
version.

(synaptic:14435): GLib-GObject-WARNING **: The property GtkButton:xalign is 
deprecated and shouldn't be used anymore. It will be removed in a future 
version.

(synaptic:14435): GLib-GObject-WARNING **: The property 
GtkAlignment:right-padding is deprecated and shouldn't be used anymore. It will 
be removed in a future version.

(synaptic:14435): GLib-GObject-WARNING **: The property 
GtkContainer:resize-mode is deprecated and shouldn't be used anymore. It will 
be removed in a future version.

(synaptic:14435): GLib-GObject-WARNING **: The property 
GtkAlignment:bottom-padding is deprecated and shouldn't be used anymore. It 
will be removed in a future version.

(synaptic:14435): GLib-GObject-WARNING **: The property 
GtkAlignment:left-padding is deprecated and shouldn't be used anymore. It will 
be removed in a future version.

(synaptic:14435): GLib-GObject-WARNING **: The property 
GtkCellRendererText:background-gdk is deprecated and shouldn't be used anymore. 
It will be removed in a future version.


Thank you,

*Carlos Kosloff*

Bug#738901: (no subject)

2015-09-26 Thread David Carlos

I will maintain this package,

Greetings,
-- 
David Carlos
Engenharia de Software - UnB-Gama

Bug#800409: Synaptic not starting, false positive

2015-09-28 Thread Carlos Kosloff


Package: synaptic
Version: 0.81.4+b2
Severity: grave

Dear maintainer,

* What led to this situation?
A failed install of a Java package from Oracle.

* What exactly did you do?
Purged package completely and reinstalled after reboot, issue persists.

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

Kernel: Linux 4.1.0-2-amd64 (SMP w/8 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 synaptic depends on:
ii  hicolor-icon-theme 0.13-1
ii  libapt-inst1.7 1.0.10.2
ii  libapt-pkg4.16 1.0.10.2
ii  libatk1.0-0 2.16.0-2
ii  libc6 2.19-22
ii  libcairo-gobject2 1.14.2-2
ii  libcairo2 1.14.2-2
ii  libept1.4.16 1.0.14+b1
ii  libgcc1 1:5.2.1-17
ii  libgdk-pixbuf2.0-0 2.32.0-1
ii  libglib2.0-0 2.44.1-1.1
ii  libgtk-3-0 3.16.6-1
ii  libpango-1.0-0 1.36.8-3
ii  libpangocairo-1.0-0 1.36.8-3
ii  libstdc++6 5.2.1-17
ii  libvte-2.90-9 1:0.36.3-1
ii  libx11-6 2:1.6.3-1
ii  libxapian22v5 1.2.21-1.2
ii  libxext6 2:1.3.3-1
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages synaptic recommends:
ii  gksu   2.0.2-9
ii  libgtk2-perl   2:1.2496-3
ii  policykit-10.105-12
ii  rarian-compat  0.8.1-6

Versions of packages synaptic suggests:
ii  apt-xapian-index 0.47
ii  deborphan1.7.28.8-0.2
pn  dwww 
ii  menu 2.1.47
pn  software-properties-gtk  
ii  tasksel  3.33

-- no debconf information

Purging and reinstalling did not help in this system, I had similar 
issue on another one and that fixed it.

Synaptic throws false positive on root password and will not start.
The root password is correct and these are the errors in terminal:

ckosloff@crosshair:~$ su
Password:
root@crosshair:/home/ckosloff# synaptic
No protocol specified

** (synaptic:3056): WARNING **: Could not open X display
No protocol specified
Unable to init server: Could not connect: Connection refused

(synaptic:3056): Gtk-WARNING **: cannot open display: :0
root@crosshair:/home/ckosloff# exit

The failed processes are synaptic-pkexec and pkexec.

Here is a snapshot: http://imgur.com/rlz0ga4

Please help.

*Carlos Kosloff*

Bug#799542: Gwenview lost editing capabilities

2015-09-19 Thread Carlos Kosloff


Package: gwenview
Version: 4:15.08.0-3
Severity: important


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

Kernel: Linux 4.1.0-2-amd64 (SMP w/8 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 gwenview depends on:
ii  libc6   2.19-20
ii  libexiv2-14 0.25-2
ii  libgcc1 1:5.2.1-17
ii  libjpeg62-turbo 1:1.4.1-2
ii  libkf5activities5   5.13.0-1
ii  libkf5baloo55.13.0-2
ii  libkf5completion5   5.13.0-1
ii  libkf5configcore5   5.13.0-1
ii  libkf5configgui55.13.0-1
ii  libkf5configwidgets55.13.0-2
ii  libkf5coreaddons5   5.13.0-1
ii  libkf5filemetadata3 5.13.0-1
ii  libkf5i18n5 5.13.0-1
ii  libkf5iconthemes5   5.13.0-1
ii  libkf5itemmodels5   5.13.0-1
ii  libkf5itemviews55.13.0-1
ii  libkf5jobwidgets5   5.13.0-1
ii  libkf5kdelibs4support5  5.13.0-3
ii  libkf5kiocore5  5.13.0-1
ii  libkf5kiofilewidgets5   5.13.0-1
ii  libkf5kiowidgets5   5.13.0-1
ii  libkf5notifications55.13.0-1
ii  libkf5parts55.13.0-1
ii  libkf5service5  5.13.0-2
ii  libkf5textwidgets5  5.13.0-1
ii  libkf5widgetsaddons55.13.0-1
ii  libkf5xmlgui5   5.13.0-1
ii  liblcms2-2  2.6-3+b3
ii  libphonon4qt5-4 4:4.8.3-2
ii  libpng12-0  1.2.50-2+b2
ii  libqt5core5a5.4.2+dfsg-9
ii  libqt5gui5  5.4.2+dfsg-9
ii  libqt5opengl5   5.4.2+dfsg-9
ii  libqt5printsupport5 5.4.2+dfsg-9
ii  libqt5svg5  5.4.2-3
ii  libqt5widgets5  5.4.2+dfsg-9
ii  libqt5x11extras55.4.2-2+b1
ii  libstdc++6  5.2.1-17
ii  libx11-62:1.6.3-1
ii  phonon4qt5  4:4.8.3-2

Versions of packages gwenview recommends:
ii  kamera  4:4.14.2-1+b1
ii  kio-extras  4:15.08.0-1

gwenview suggests no packages.

-- no debconf information


Dear maintainer,

I did not do anything special, just tried to edit an image and noticed 
that all the edition capabilties: crop, resize, etc., were gone.

Upgraded to latest version in stretch and same behavior.
Please consider fixing these issues.

--
*Carlos Kosloff*

Bug#799542: Gwenview lost editing capabilities

2015-09-19 Thread Carlos Kosloff


OK, got it, thank you.

*Carlos Kosloff*


On 09/20/2015 12:15 AM, Scott Kitterman wrote:

On Saturday, September 19, 2015 11:47:29 PM Carlos Kosloff wrote:

Package: gwenview
Version: 4:15.08.0-3
Severity: important

...

Dear maintainer,

I did not do anything special, just tried to edit an image and noticed
that all the edition capabilties: crop, resize, etc., were gone.
Upgraded to latest version in stretch and same behavior.
Please consider fixing these issues.

The U/I is somewhat more hidden, but it's there.  Look at the tabs across the
bottom of the left side of the gwenview window and check operations.  All the
edit choices are there and I tested cropping and it works just fine.

Scott K

Bug#605079: netdot in Debian

2015-12-15 Thread Carlos Vicente

Hello Iain,

I originally intended to package it myself. I started with all the missing Perl 
modules that were not included in Debian. That took an enormous amount of time, 
but I believe that most of the modules were included. After that, I changed 
jobs, had more kids… you know how it goes :-)

I would love to continue this work and ultimately have a netdot package 
available in Debian, so I will gladly accept any help you can provide.

Best,

cv

On Dec 15, 2015, at 3:34 PM, Iain R. Learmonth  wrote:

> Hi,
> 
> I saw you filed a bug regarding netdot in Debian. I can't quite tell if you
> were requesting that someone package the software or if you were intending
> to package it yourself as there is not really much information in the bug
> log.
> 
>  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605079
> 
> If you were intending to package the software but just did not recieve much
> in the way of support, I'd like to offer to sponsor this package into the
> archive for you, though I'm not too familiar with Perl and so may not be
> able to help with some of the Perl specific details.
> 
> Please keep the bug email address in CC when you reply so that the
> information can be added to the bug log.
> 
> Thanks,
> Iain.
> 
> --

Bug#808920: [calligra-libs] not installable

2016-01-06 Thread Carlos Reding

The library libilmbase6 has been replaced by libilmbase6v5. 

I’m using the branch `testing´, and Kde-runtime 4:15.08.3-1 depends on 
libopenexr6v5 (1.6.1-8.1+b2 here), which depends on libilmbase6v5 so it is not 
possible to replace the `base6v5' library without messing things up. It’d be 
cool to have calligra back in testing (with or without qt5 support).


On Thu, 24 Dec 2015 13:11:09  0100 Thomas Florek  wrote:
> Package: calligra-libs
> Severity: grave
> 
> --- Please enter the report below this line. ---
> The following packages have unmet dependencies:
>  calligra-libs : Depends: libilmbase6 (>= 1.0.1) but it is not installable
> 
> --- System information. ---
> Architecture: amd64
> Kernel:   Linux 4.2.3-towo.1-siduction-amd64
> 
> Debian Release: stretch/sid
>   500 unstableftp.spline.de
>   500 unstableftp.de.debian.org
>   500 testing ftp.de.debian.org
>   500 buildd-unstable incoming.debian.org
> 1 experimentalftp.de.debian.org
> 
> --- Package information. ---
> Depends (Version) | Installed
> =- 
> -=
> calligra-data(>= 1:2.8.5.repack-90r1) |
> libc6   (>= 2.14) | 2.21-5
> libfontconfig1  (>= 2.11) | 2.11.0-6.3
> libfreetype6   (>= 2.2.1) | 2.6.1-0.1
> libgcc1  (>= 1:4.1.1) | 1:5.3.1-4
> libicu52(>= 52~m1-1~) | 52.1-10
> libilmbase6(>= 1.0.1) |
> libkactivities6   (>= 4:4.12) | 4:4.13.3-1
> libkdecore5   (>= 4:4.12) | 4:4.14.14-1 b1
> libkdeui5 (>= 4:4.12) | 4:4.14.14-1 b1
> libkfile4 (>= 4:4.12) | 4:4.14.14-1 b1
> libkio5   (>= 4:4.12) | 4:4.14.14-1 b1
> libkrosscore4 (>= 4:4.12) | 4:4.14.14-1 b1
> libkrossui4   (>= 4:4.12) |
> liblcms2-2   (>= 2.2 git20110628) | 2.6-3 b3
> libphonon4   (>= 4:4.2.0) | 4:4.8.3-2
> libphononexperimental4(>= 4:4.6.0really4.4.4) |
> libqca2(>= 2.0.2) | 2.1.1-2
> libqt4-dbus  (>= 4:4.5.3) | 4:4.8.7 dfsg-5
> libqt4-network   (>= 4:4.6.1) | 4:4.8.7 dfsg-5
> libqt4-opengl(>= 4:4.5.3) | 4:4.8.7 dfsg-5
> libqt4-svg   (>= 4:4.5.3) | 4:4.8.7 dfsg-5
> libqt4-xml   (>= 4:4.5.3) | 4:4.8.7 dfsg-5
> libqtcore4   (>= 4:4.8.0) | 4:4.8.7 dfsg-5
> libqtgui4(>= 4:4.8.0) | 4:4.8.7 dfsg-5
> libsoprano4   (>= 2.2.69) | 2.9.4 dfsg-3 b1
> libspnav0 |
> libsqlite3-0   (>= 3.6.0) | 3.9.2-1
> libstdc  6   (>= 4.9) | 5.3.1-4
> phonon| 4:4.8.3-2
> phononexperimental-abi-1  |
> 
> 
> Recommends   (Version) | Installed
> ==- -===
> fonts-lyx  | 2.1.4-2
> libqca2-plugin-ossl| 2.1.1-2
> python | 2.7.11-1
> ruby   |

Bug#809001: Konsole segmentation fault

2015-12-25 Thread Carlos Kosloff



Package: konsole
Version: 4:15.08.3-1
Severity: important

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 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 konsole depends on:
ii  konsole-kpart 4:15.08.3-1
ii  libc6 2.21-4
ii  libkf5completion5 5.16.0-1
ii  libkf5configcore5 5.16.0-1
ii  libkf5configgui5 5.16.0-1
ii  libkf5configwidgets55.16.0-1
ii  libkf5coreaddons5   5.16.0-1
ii  libkf5i18n5 5.16.0-1
ii  libkf5iconthemes5   5.16.0-1
ii  libkf5kdelibs4support5  5.16.0-1
ii  libkf5kiowidgets5   5.16.0-1
ii  libkf5notifyconfig5 5.16.0-1
ii  libkf5widgetsaddons55.16.0-1
ii  libkf5windowsystem5 5.16.0-1
ii  libkf5xmlgui5   5.16.0-1
ii  libqt5core5a5.5.1+dfsg-8
ii  libqt5gui5  5.5.1+dfsg-8
ii  libqt5widgets5  5.5.1+dfsg-8
ii  libstdc++6  5.3.1-4

konsole recommends no packages.

konsole suggests no packages.

-- no debconf information

Dear Maintainer,

   * What led up to the situation?

Simply issuing the 'exit' command caused a segfault

Please see the full detail of the error here: http://imgur.com/U7PpLCY
Thank you.

Bug#809001: Konsole segmentation fault

2015-12-25 Thread Carlos Kosloff

I'd rather wait for it to migrate, I will close bug if update resolves 
issue.

Thanks for answer.


On 12/25/2015 09:28 PM, Lisandro Damián Nicanor Pérez Meyer wrote:


Please update your current qt5 stuff to unstable and try again

--
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

El dic 25, 2015 9:30 PM, "Carlos Kosloff" <ckosl...@hardwarealien.com 
<mailto:ckosl...@hardwarealien.com>> escribió:



Package: konsole
Version: 4:15.08.3-1
Severity: important

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 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 konsole depends on:
ii  konsole-kpart 4:15.08.3-1
ii  libc6 2.21-4
ii  libkf5completion5 5.16.0-1
ii  libkf5configcore5 5.16.0-1
ii  libkf5configgui5 5.16.0-1
ii  libkf5configwidgets55.16.0-1
ii  libkf5coreaddons5   5.16.0-1
ii  libkf5i18n5 5.16.0-1
ii  libkf5iconthemes5   5.16.0-1
ii  libkf5kdelibs4support5  5.16.0-1
ii  libkf5kiowidgets5   5.16.0-1
ii  libkf5notifyconfig5 5.16.0-1
ii  libkf5widgetsaddons55.16.0-1
ii  libkf5windowsystem5 5.16.0-1
ii  libkf5xmlgui5   5.16.0-1
ii  libqt5core5a5.5.1+dfsg-8
ii  libqt5gui5  5.5.1+dfsg-8
ii  libqt5widgets5  5.5.1+dfsg-8
ii  libstdc++6  5.3.1-4

konsole recommends no packages.

konsole suggests no packages.

-- no debconf information

Dear Maintainer,

   * What led up to the situation?

Simply issuing the 'exit' command caused a segfault

Please see the full detail of the error here: http://imgur.com/U7PpLCY
Thank you.

Bug#793641: glibc: too few static TLS slots

2015-11-24 Thread Carlos O'Donell

On Mon, Nov 23, 2015 at 7:04 AM, Aurelien Jarno <aurel...@aurel32.net> wrote:
> On 2015-08-17 15:04, Carlos O'Donell wrote:
>> On Sun, Aug 16, 2015 at 12:48 PM, Andreas Cadhalpun
>> <andreas.cadhal...@googlemail.com> wrote:
>> >> until there's a better tested and working way to transition
>> >> to ffmpeg?
>> >
>> > This really doesn't have that much to do with the transition to ffmpeg.
>> > Any other library that (indirectly) links against sufficiently many
>> > STATIC_TLS using ones and is used in some plugin is also affected.
>> >
>> > Note that there are currently 14 STATIC_TLS slots and gst-libav uses 6,
>> > while it used 4 previously. It is a mere coincidence that this increase
>> > causes totem to hit the arbitrary limit in glibc.
>>
>> The math can't be done that easily, it's actually a heuristic, but
>> pretend it works this way for the sake of this discussion.
>>
>> The only immediate solution is for debian's glibc to increase
>> DTV_SURPLUS to 32 or higher. This is exactly what I did for Fedora.
>>
>> The other alternative is to backport Alex's fixes for Sourceware bugs
>> BZ #17090, BZ #17620, BZ #17621, BZ #17628, which corrects the
>> heuristics behind DTV_SURPLUS which prevent the loading of STATIC_TLS.
>
> I have backported these patches to 2.21. Unfortunately they now cause
> nptl/tst-cancel24-static to fail on at least armhf, armel, mips and
> mipsel. The binary segfaults.

Please submit a bug for this.

Is it segfaulting when accessing locales for the first time in the
newly dlopen'd libc.so.6?

There are several known issues regarding statically linked and
dlopened binaries that may impact this.

> According to the wiki [1], the failure seems to be a known issue
> in the 2.22 release, though its cause was marked as unknown. Do you know
> by chance if the problem has been fixed or addressed in the meantime?

No, nobody has fixed this upstream.

Any triage you can provide would be appreciated.

Cheers,
Carlos.

Bug#806771: K3b crashes when requested to verify written data

2015-11-30 Thread Carlos Kosloff


Package: k3b
Version: 2.0.2-8+b1
Severity: important

Dear Maintainer,

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

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 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 k3b depends on:
ii  cdparanoia 3.10.2+debian-11
ii  cdrdao 1:1.2.3-2+b1
ii  genisoimage9:1.1.11-3
ii  k3b-data   2.0.2-8
ii  kde-runtime4:15.08.2-1
ii  libc6  2.19-22
ii  libk3b62.0.2-8+b1
ii  libkcddb4  4:15.08.0-1
ii  libkcmutils4   4:4.14.13-1
ii  libkde3support44:4.14.13-1
ii  libkdecore54:4.14.13-1
ii  libkdeui5  4:4.14.13-1
ii  libkfile4  4:4.14.13-1
ii  libkio54:4.14.13-1
ii  libknotifyconfig4  4:4.14.13-1
ii  libqt4-qt3support  4:4.8.7+dfsg-4
ii  libqt4-xml 4:4.8.7+dfsg-4
ii  libqtcore4 4:4.8.7+dfsg-4
ii  libqtgui4  4:4.8.7+dfsg-4
ii  libqtwebkit4   2.3.4.dfsg-5
ii  libsolid4  4:4.14.13-1
ii  libstdc++6 5.2.1-23
ii  udisks22.1.6-2
ii  wodim  9:1.1.11-3

Versions of packages k3b recommends:
ii  dvd+rw-tools 7.1-11+b1
ii  growisofs7.1-11+b1
ii  libk3b6-extracodecs  2.0.2-8+b1
ii  vcdimager0.7.24+dfsg-0.2

Versions of packages k3b suggests:
ii  k3b-extrathemes  2.0.2-8
ii  k3b-i18n 2.0.2-8
ii  kde-config-cddb  4:15.08.0-1
pn  movixmaker-2 
pn  normalize-audio  
ii  sox  14.4.1-5

-- no debconf information

-- Package-specific info:
Device was not specified. Trying to find an appropriate drive...
Detected CD-R drive: /dev/cdrw
Using /dev/cdrom of unknown capabilities
Device type: Removable CD-ROM
Version: 5
Response Format: 2
Capabilities :
Vendor_info: 'HL-DT-ST'
Identification : 'DVDRAM GH40F '
Revision   : 'MG01'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R96R

Whenever I burn a CD and request written data verification, Kde crashes 
after burning, does not recognize second step as it used to do, 
nevertheless the data in the CD itself does not appear to be corrupt.

Thank you.

Bug#823128: RFP: proxychains-ng -- redirect connections through proxy servers

2016-06-06 Thread Carlos Maddela

Control: retitle -1 ITP: proxychains-ng -- redirect connections through
proxy servers

On Sun, 1 May 2016 02:57:50 -0400 Jason Hennessey wrote:
> Package: wnpp
> Severity: wishlist
>
> The current proxychains package is relatively old, and development has
> continued in a different project called proxychains-ng according to this
> ubuntu report from 2013, the maintainer announced in a forum on the
> original sourceforge site that development had moved to github:
> https://bugs.launchpad.net/ubuntu/+source/proxychains/+bug/1109235
>
> The new repo contains several useful additions, such as the ability to
> specify a config file on the command line as well as using the remote
> host to do DNS resolving (which allows things like resolving TOR onion
> addresses), and may be found at: https://github.com/rofl0r/proxychains-ng
>
> Thanks for any help!
>
>
>

Bug#811296: Okular fails to launc

2016-01-17 Thread Carlos Kosloff


Package: okular
Version: 4:15.08.3-1
Severity: wishlist

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 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 okular depends on:
ii  kde-runtime 4:15.08.3-1
ii  libc6 2.21-6
ii  libfreetype6 2.6.1-0.1
ii  libjpeg62-turbo 1:1.4.1-2
ii  libkactivities6 4:4.13.3-1
ii  libkdecore5 4:4.14.14-1+b1
ii  libkdeui5 4:4.14.14-1+b1
ii  libkexiv2-11 4:15.04.3-1
ii  libkio5 4:4.14.14-1+b1
ii  libkparts4  4:4.14.14-1+b1
ii  libkprintutils4 4:4.14.14-1+b1
ii  libkpty44:4.14.14-1+b1
ii  libokularcore6  4:15.08.3-1
ii  libphonon4  4:4.8.3-2
ii  libpoppler-qt4-40.38.0-2
ii  libqca2 2.1.1-2
ii  libqimageblitz4 1:0.0.6-4
ii  libqmobipocket1 4:14.12.2-2
ii  libqt4-dbus 4:4.8.7+dfsg-5
ii  libqt4-declarative  4:4.8.7+dfsg-5
ii  libqt4-svg  4:4.8.7+dfsg-5
ii  libqt4-xml  4:4.8.7+dfsg-5
ii  libqtcore4  4:4.8.7+dfsg-5
ii  libqtgui4   4:4.8.7+dfsg-5
ii  libsolid4   4:4.14.14-1+b1
ii  libspectre1 0.2.7-3
ii  libstdc++6  5.3.1-5
ii  phonon  4:4.8.3-2
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages okular recommends:
ii  cups-bsd  2.1.2-1

Versions of packages okular suggests:
ii  ghostscript9.16~dfsg-2
ii  jovie  4:15.08.3-1
ii  okular-extra-backends  4:15.08.3-1
ii  poppler-data   0.4.7-7
ii  texlive-binaries   2015.20150524.37493-7+b1
pn  unrar  

-- no debconf information

Dear maintainer,

This issue is very strange because I have laptop with similar 
confiuration: amd64, kde, testing branch.
The failing computer has an nvidia graphic image, I just ran a 
dist-upgrade, nvidia drivers were already the latest version in testing.

Okular takes forever to launch, and when it does it throws errors:

okular(2619)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(2619)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(2619)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(2619)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(2619)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(2619) Bridge::setRootObject: "KAccessibleBridge: setRootObject 
object=" "okular (KApplication)"
okular(2619) Bridge::Private::app: Connected with the 
org.kde.kaccessibleapp dbus-service
okular(2619) Bridge::notifyAccessibilityUpdate: "278" "object=" " 
(QComboBoxListView)" "name=" ""
okular(2619) Bridge::notifyAccessibilityUpdate: "Focus" "object=" 
"okular::pageView (PageView)" "name=" "" "rect=" QRect(253,440 1019x570)
okular(2619) Bridge::notifyAccessibilityUpdate: "NameChanged" "object=" 
" (QToolButton)" "name=" "Close"
okular(2619) Bridge::notifyAccessibilityUpdate: "NameChanged" "object=" 
" (QToolButton)" "name=" "Show Forms"
okular(2619) Bridge::notifyAccessibilityUpdate: "283" "object=" 
"SearchLineEdit (SearchLineEdit)" "name=" ""
okular(2619) Bridge::notifyAccessibilityUpdate: "288" "object=" 
"SearchLineEdit (SearchLineEdit)" "name=" ""
okular(2619) Bridge::notifyAccessibilityUpdate: "ObjectDestroyed" 
"object=" " (QWidget)" "name=" ""
okular(2619) Bridge::notifyAccessibilityUpdate: "ObjectDestroyed" 
"object=" "qt_rubberband (QWidget)" "name=" ""
okular(2619) Bridge::notifyAccessibilityUpdate: "ObjectDestroyed" 
"object=" "KLineEditButton (QWidget)" "name=" ""
okular(2619) Bridge::notifyAccessibilityUpdate: "ObjectDestroyed" 
"object=" " (QWidget)" "name=" ""
okular(2619) Bridge::notifyAccessibilityUpdate: "ObjectDestroyed" 
"object=" "qt_scrollarea_viewport (QWidget)" "name=" ""
okular(2619) Bridge::notifyAccessibilityUpdate: "ObjectDestroyed" 
"object=" " (QWidget)" "name=" ""
okular(2619) Bridge::notifyAccessibilityUpdate: "ObjectDestroyed" 
"object=" "qt_scrollarea_hcontainer (QWidget)" "name=" ""
okular(2619) Bridge::notifyAccessibilityUpdate: "ObjectDestroyed" 
"object=" " (QWidget)" "name=" ""
okular(2619) Bridge::notifyAccessibilityUpdate: "ObjectDestroyed" 
"object=" "qt_scrollarea_vcontainer (QWidget)" "name=" ""
okular(2619) Bridge::notifyAccessibilityUpdate: "ObjectDestroyed" 
"object=" "qt_scrollarea_viewport (QWidget)" "name=" ""
okular(2619) Bridge::notifyAccessibilityUpdate: "ObjectDestroyed" 
"object=" " (QWidget)" "name=" ""
okular(2619) Bridge::notifyAccessibilityUpdate: "ObjectDestroyed" 
"object=" "qt_scrollarea_hcontainer (QWidget)" "name=" ""
okular(2619) Bridge::notifyAccessibilityUpdate: "ObjectDestroyed" 
"object=" " (QWidget)" "name=" ""
okular(2619) Bridge::notifyAccessibilityUpdate: "ObjectDestroyed" 
"object=" "qt_scrollarea_vcontainer (QWidget)" "name=" ""
okular(2619)

Bug#811018: korganizer does not launch

2016-01-14 Thread Carlos Kosloff


Package: korganizer
Version: 4:4.14.10-2
Severity: Important
-

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 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 korganizer depends on:
ii  kde-runtime   4:15.08.3-1
ii  kdepim-runtime4:4.14.10-2
ii  kdepimlibs-kio-plugins4:4.14.10-1
ii  libakonadi-calendar4  4:4.14.10-1
ii  libakonadi-contact4   4:4.14.10-1
ii  libakonadi-kde4   4:4.14.10-1
ii  libakonadi-kmime4 4:4.14.10-1
ii  libc6 2.21-6
ii  libcalendarsupport4   4:4.14.10-2
ii  libeventviews44:4.14.10-2
ii  libgcc1   1:5.3.1-5
ii  libincidenceeditorsng44:4.14.10-2
ii  libkabc4  4:4.14.10-1
ii  libkcalcore4  4:4.14.10-1
ii  libkcalutils4 4:4.14.10-1
ii  libkcmutils4  4:4.14.14-1+b1
ii  libkdecore5   4:4.14.14-1+b1
ii  libkdepim44:4.14.10-2
ii  libkdepimdbusinterfaces4  4:4.14.10-2
ii  libkdeui5 4:4.14.14-1+b1
ii  libkholidays4 4:4.14.10-1
ii  libkio5   4:4.14.14-1+b1
ii  libkmime4 4:4.14.10-1
ii  libknewstuff3-4   4:4.14.14-1+b1
ii  libkontactinterface4a 4:4.14.10-1
ii  libkparts44:4.14.14-1+b1
ii  libkpimidentities44:4.14.10-1
ii  libkpimutils4 4:4.14.10-1
ii  libkprintutils4   4:4.14.14-1+b1
ii  libmailtransport4 4:4.14.10-1
ii  libphonon44:4.8.3-2
ii  libpimcommon4 4:4.14.10-2
ii  libqt4-dbus   4:4.8.7+dfsg-5
ii  libqt4-xml4:4.8.7+dfsg-5
ii  libqtcore44:4.8.7+dfsg-5
ii  libqtgui4 4:4.8.7+dfsg-5
ii  libstdc++65.3.1-5
ii  perl  5.22.1-3
ii  phonon4:4.8.3-2

Versions of packages korganizer recommends:
ii  kdepim-doc 4:4.14.10-2
ii  kdepim-kresources  4:4.14.10-2

korganizer suggests no packages.

-- no debconf information

 Dear maintainer,

korganizer fails to launch, or launches defectively.
When attempting to launch from terminal throws following error:
ckosloff@crosshair:~$ korganizer
QDBusConnection: session D-Bus connection created before 
QCoreApplication. Application may misbehave.

Thank you.

Bug#809001: Konsole segmentation fault

2016-02-01 Thread Carlos Kosloff


OK, please close bug, updating/upgrading fixed issue.
Thank you,

*Carlos Kosloff*
Office: (954) 283-8828
Cell: (954) 464-8822
Fax: (888) 854-5440

On 02/01/2016 03:32 AM, Maximiliano Curia wrote:

Control: tags -1 + unreproducible

On 26/12/15 04:27, Carlos Kosloff wrote:

I'd rather wait for it to migrate, I will close bug if update resolves issue.

I'm not able to reproduce the issue with the current versions of konsole and 
it's dependencies. As mentioned that you'd close the issue if the bug goes 
away, please consider this message a friendly ping.

Happy hacking,

Bug#815974: Segmentation fault in libresolv triggered by php5-fpm

2016-02-26 Thread Carlos O'Donell

On Fri, Feb 26, 2016 at 3:57 AM, Fabian Niepelt <f.niep...@mittwald.de> wrote:
> I'll be gladly providing additional info if you require it.
> Program received signal SIGSEGV, Segmentation fault.
> 0x7f146545e4fa in *__GI___libc_res_nsearch (statp=0x7f14659f7300,
> name=, class=, type=,
> answer=0x7fff6d6c0df0 "2", anslen=,
> answerp=0x7fff6d6c1660,
> answerp2=0x7fff6d6c1658, nanswerp2=0x7fff6d6c167c,
> resplen2=0x7fff6d6c1678, answerp2_malloced=0x20032) at
> res_query.c:393
> 393 res_query.c: No such file or directory.

1) Download the tarball from the official CVE-2015-7547 tests here:
https://sourceware.org/ml/libc-alpha/2016-02/msg00418.html

2) Comment out BUILDDIR (to build against your system libraries)

3) Run 'make' to build the test, and run them all one-by-one.

Do any of them fail on your system?

Cheers,
Carlos.

Bug#815974: Segmentation fault in libresolv triggered by php5-fpm

2016-02-26 Thread Carlos O'Donell

On Fri, Feb 26, 2016 at 7:46 AM, Fabian Niepelt <f.niep...@mittwald.de> wrote:
> This is the correct output, the older one contains a test I thought was
> in an endless loop but succeeded after a few minutes.

The glibc maintainers for debian need to review those failures. They
indicate serious deviation from expected behaviour. At the very least
the bug 18665* tests should not fail. However, the tests are sensitive
to response order.

-address: STREAM/TCP 10.0.3.6 80
-address: STREAM/TCP 2001:db8::4:6 80
+error: Name or service not known

This is a weird failure.

Cheers,
CArlos.

Bug#811296: Please close this bug

2016-01-19 Thread Carlos Kosloff

Unrelated to okular, there was a general sluggishness in kde, caused by 
an incorrect network configuration.
This is what happened, in a dist-upgrade I saw that package ifupdown was 
being held back and not upgraded.
Tried to force upgrade but it wanted to remove half the system, so I 
passed.
Then I saw that there is another package in repo called ifupdown2, so I 
installed that one, which removed ifupdown.

That is when the sluggishness started.
So I dist-upgraded today, purged ifupdown2, installed ifupdown without 
problems, rebooted, and lo (pun intended) and behold, kde was back!

Bug#811018: Please close this bug

2016-01-19 Thread Carlos Kosloff



Unrelated to korganizer, sluggishness in kde caused by incorrect network 
configuration.
This is what happened, in a dist-upgrade I saw that package ifupdown was 
being held back and not upgraded.
Tried to force upgrade but it wanted to remove half the system, so I 
passed.
Then I saw that there is another package in repo called ifupdown2, so I 
installed that one, which removed ifupdown.

That is when the sluggishness started.
So I dist-upgraded today, purged ifupdown2, installed ifupdown without 
problems, rebooted, and lo (pun intended) and behold, kde was back!

Bug#812388: Debian man page is out of sync with 'mitmproxy --help' documentation

2016-01-22 Thread Carlos Maddela

Package: mitmproxy
Version: 0.13-1
Severity: normal

In particular, the documentation for -F must be changed to -U.

Cheers

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

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

Versions of packages mitmproxy depends on:
ii  python 2.7.11-1
ii  python-blinker 1.3.dfsg2-1
ii  python-configargparse  0.10.0-1
ii  python-html2text   2016.1.8-1
ii  python-lxml3.5.0-1
ii  python-netlib  0.13.1-1
ii  python-pil 3.0.0-1
ii  python-pyasn1  0.1.9-1
ii  python-pyparsing   2.0.3+dfsg1-1
ii  python-tornado 4.2.1-1+b1
ii  python-urwid   1.3.1-2
pn  python:any 

Versions of packages mitmproxy recommends:
ii  python-pyperclip  1.5.11-1

mitmproxy suggests no packages.

-- no debconf information

Bug#723990: youtube-dl: python3+ requirement

2016-03-01 Thread Carlos Maddela

Package: youtube-dl
Followup-For: Bug #723990

Hello Rogério,

I have worked on a solution to this, which unfortunately splits the
package up into youtube-dl, python3-youtube-dl and python-youtube-dl.
You mentioned that you'd rather not split the package up, but I think
it's the right way to go.

It's available for you to check at
https://github.com/e7appew/youtube-dl/tree/debian/nmu-1.

Let me know what you think.

Cheers,

Carlos

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

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

Versions of packages youtube-dl depends on:
ii  python3-pkg-resources  20.1.1-1
ii  python3-youtube-dl 2016.02.22-1.1
pn  python3:any

youtube-dl recommends no packages.

youtube-dl suggests no packages.

-- no debconf information

Bug#798936: youtube-dl: Expect ffmpeg version numbers, rather than libav

2016-03-01 Thread Carlos Maddela

Package: youtube-dl
Followup-For: Bug #798936

Hello Rogério,

This bug is also fixed in
https://github.com/e7appew/youtube-dl/tree/debian/nmu-1, and I've
forwarded the fix upstream: https://github/rg3/youtube-dl/pull/8720.

Cheers,

Carlos

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

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

Versions of packages youtube-dl depends on:
ii  python3-pkg-resources  20.1.1-1
ii  python3-youtube-dl 2016.02.22-1.1
pn  python3:any

youtube-dl recommends no packages.

youtube-dl suggests no packages.

-- no debconf information

Bug#816412: youtube-dl: add zsh completion

2016-03-01 Thread Carlos Maddela

Package: youtube-dl
Followup-For: Bug #816412

Hello Rogério,

This bug is also fixed in
https://github.com/e7appew/youtube-dl/tree/debian/nmu-1.

Cheers,

Carlos

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

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

Versions of packages youtube-dl depends on:
ii  python3-pkg-resources  20.1.1-1
ii  python3-youtube-dl 2016.02.22-1.1
pn  python3:any

youtube-dl recommends no packages.

youtube-dl suggests no packages.

-- no debconf information

Bug#816742: libc6: sem_post/sem_wait not working for 32bit to 64bit inter-process communication

2016-03-05 Thread Carlos O'Donell

On Sat, Mar 5, 2016 at 7:28 AM, Aurelien Jarno <aurel...@aurel32.net> wrote:
> control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=17980

Semaphore interoperability between two different ABIs has never been
supported. It worked because you were lucky and the implementation was
flawed. To fix the implementation flaws (which are real), we've had to
adopt slightly different algorithms for 32-bit and 64-bit.

Cheers,
Carlos.

Bug#824093: dpkg-reconfigure libdvd-pkg fails to build libdvdcss2 with dpkg 1.18.7

2016-05-12 Thread Carlos Maddela

Package: libdvd-pkg
Version: 1.4.0-1-1
Severity: normal
Tags: patch

With dpkg version 1.18.7 (possibly other versions > 1.18.4 as well),
'dpkg-reconfigure libdvd-pkg' fails to build anything. It always ends up
with the following error:

libdvd-pkg: dpkg database is locked. You may need to use command "sudo 
dpkg-reconfigure libdvd-pkg".
libdvd-pkg: Building and installation of package(s) [libdvdcss2 
libdvdcss-dev] postponed till after next APT operation.

The problem occurs in /usr/lib/libdvd-pkg/b-i_libdvdcss.sh, which uses
"dpkg -i /dev/zero" to determine the lock status of dpkg. Newer versions
of dpkg produce the following error:

dpkg: error: archive '/dev/zero' is not a regular file

which also returns an error status of 2, hence nothing ever builds.

Purging or removing a non-existent package should restore the original
behaviour. I have attached a patch with this fix.

Best regards,

Carlos

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

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

Versions of packages libdvd-pkg depends on:
ii  build-essential12.2
ii  debconf [debconf-2.0]  1.5.59
ii  debhelper  9.20160403
ii  devscripts 2.16.4
ii  dh-autoreconf  12
ii  wget   1.17.1-2

Versions of packages libdvd-pkg recommends:
ii  libcap2-bin  1:2.24-12

libdvd-pkg suggests no packages.

-- debconf information excluded
>From 254f7072153f865e7301b487ebc6024ab1a3e53d Mon Sep 17 00:00:00 2001
From: Carlos Maddela <e7ap...@gmail.com>
Date: Thu, 12 May 2016 16:10:33 +1000
Subject: [PATCH] Use alternative way to check if dpkg database is locked

Version 1.18.7 of dpkg also returns an error status of 2 when
attempting to install /dev/zero, so this method can no longer
be used to check the lock status. Trying to purge a non-existent
package achieves the original behaviour.
---
 debian/b-i_libdvdcss.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/b-i_libdvdcss.sh b/debian/b-i_libdvdcss.sh
index 127799d..8615185 100755
--- a/debian/b-i_libdvdcss.sh
+++ b/debian/b-i_libdvdcss.sh
@@ -17,7 +17,7 @@ if [ -f "${DIR}/${PKGG}-${VERGG}.is-installed" ]; then
 fi
 
 ## check if DPKG database is locked
-dpkg -i /dev/zero 2>/dev/null
+dpkg -P non-existent-package 2>/dev/null
 if [ "$?" -eq 2 ]; then
 echo "${PKGI}: dpkg database is locked. You may need to use command \"sudo dpkg-reconfigure ${PKGI}\"."
 if [ -h "/etc/apt/apt.conf.d/${P88}" ]; then
-- 
2.8.1

Bug#823061: carlos-✉-Message-on-hold-

2016-05-02 Thread Carlos tejeda

Who' this?
On Sat, Apr 30, 2016 at 12:32 PM Angel  wrote:

>
>
>
>
>
>
>
>
>
>
>
> * _Just_saw_something_really_hot_that_made_me_wonder...
> _What_would_you_like_me_to_wear_tonight?_
> _What's_the_hottest_thing_I_can_do_for_you_when_I_see_you?_
> We'll_even_play_some_games_honey_
> _you_just_guess_what_color_my_panties_are,_then_I'll_give_you_whatever_you_want_;)
> register_and_add_my_nickname_:angelicax3 u_ns__ub optout
>  *
>

Bug#823952: dahdi-source: AXE400PL + linux 3.16.0-4-686-pae + dahdi 1:2.10.2-2

2016-05-10 Thread Carlos Martin

Package: dahdi-source
Version: 1:2.10.2~dfsg-1
Severity: important

Dear Maintainer,

This bug is near the same as #780997 but is not solved.

I'm using Debian jessie, I installed dahdi-source from jessie repos but I got 
an error when loading dahdi module, I try also upgrading to the unstable 
version, but I got the same error. So, I get this error with dahdi-source 
Version: 2.10.0.1 and Version: 2.10.2
 

When system loads dahdi module yo can see the message "Warning: Span WCTDM/4 
didn't specify a spantype. Please fix driver!"

dahdi: Version: 2.10.2
dahdi: Telephony Interface Registered on major 196
dahdi: Warning: Span WCTDM/4 didn't specify a spantype. Please fix driver!
No freshmaker chip
Module 0: Installed -- AUTO FXS/DPO
Module 1: Installed -- AUTO FXO (FCC mode)
Module 2: Installed -- AUTO FXO (FCC mode)
Module 3: Installed -- AUTO FXO (FCC mode)
Found a Wildcard TDM: Wildcard TDM400P REV I (4 modules)

--

lshw -vv

02:00.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface
Subsystem: ATCOM Technology co., LTD. Device 0001
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR-

Bug#855256: rmlint-gui: window corrupted: no title bar or widgets

2017-02-19 Thread Carlos Maddela

Tags: moreinfo

Hi Adam,

Thanks for your bug reports. With this one, I would just like to
establish whether or not the problem you're describing is an actual
window corruption. I myself have tried it on Xfce, but can't exactly
reproduce what you describe.

The window I get is a normal sized window with a title bar, but without
the traditional minimise, maximise and close buttons. If you right click
on the title bar, you get the same menu as the one you get from right
clicking the task bar, as you've described. It appears however that this
is by design. If you take a look at the screenshots from the
documentation here: https://rmlint.readthedocs.io/en/latest/gui.html,
that is pretty much the same result I get in Xfce as well as Ubuntu. So
if it's just those buttons that you're missing, perhaps this should be
reclassified as a wishlist bug, and a feature request forwarded upstream.

If this isn't what you mean, can you please provide some screenshots? As
for the window size, the code sets the default size as 1280x660, but it
seems like it automatically gets adjusted depending on your screen size,
and I don't think window sizes are restored from previous sessions. So I
don't know what screen resolution you have that you would describe the
initial window size as small.

A problem that I have found when running Shredder on Xfce is when you
switch it to full screen mode (something that can't be done in Ubuntu),
you lose the title bar, so you lose access to the right-click menu, and
there doesn't seem to be any way to switch back from full screen mode.
You still have access to keyboard shortcuts, so ALT+F9 minimises the
window, and ALT+F4 closes it, but F11 doesn't seem to toggle full screen
mode. Maximising the window after minimising it just simply returns you
right back to full screen mode. I'm not too familiar with Xfce, so maybe
I'm missing something. Perhaps this problem is due to Shredder's window
handling, but it may well also be an Xfce bug since the same problem is
reproducible in other applications, including Nautilus and Thunar.

Thanks,

Carlos

On 16/02/17 15:28, Adam Borowski wrote:
> Package: rmlint-gui
> Version: 2.4.6-1
> Severity: normal
>
> Hi!
> rmlint-gui starts a small window that lacks the title bar and any window
> manipulation widgets (minimize, maximize, close).
>
> Happens both in XFCE and MATE, didn't test other desktops.
>
> One can still maximize/close it by right-clicking on the task bar window
> list and selecting from that menu, but doing that via the task bar is not
> something that an user who comes from eg. Windows would know about.
>
>
> -- System Information:
> Debian Release: 9.0
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
> (150, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.10.0-rc8-debug+ (SMP w/6 CPU cores)
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
>
> Versions of packages rmlint-gui depends on:
> ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
> ii  gir1.2-gtksource-3.0 3.22.2-1
> ii  gir1.2-polkit-1.00.105-17.0nosystemd1
> ii  gir1.2-rsvg-2.0  2.40.16-1
> ii  python-gi3.22.0-2
> pn  python3:any  
> pn  rmlint:any   
>
> Versions of packages rmlint-gui recommends:
> ii  python3-colorlog  2.10.0-1
>
> rmlint-gui suggests no packages.
>
> -- no debconf information
>
> -- debsums errors found:
> debsums: changed file /usr/share/glib-2.0/schemas/gschemas.compiled (from 
> rmlint-gui package)

Bug#851606: RFS: rmlint/2.4.6-1 [ITP]

2017-02-13 Thread Carlos Maddela

Dear Roger,

Thanks for your suggestions. I have made the fixes and re-uploaded the
source files as the same version (since it still has yet to be
officially released) to mentors. I have applied for access to
collab-maint (just a few minutes ago), so I probably won't be able to
push my changes for another 24 hours. For the meantime, my changes are
available in the debian branch of https://github.com/e7appew/rmlint.git.

This is the updated RFS:

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

 * Package name: rmlint
   Version : 2.4.6-1
   Upstream Author : Christopher Pahl <sa...@online.de>
 * URL : https://rmlint.readthedocs.io/
 * License : GPL-3
   Section : utils

  It builds these binary packages:

 rmlint - Extremely fast tool to remove filesystem lint
 rmlint-doc - HTML documentation for rmlint
 rmlint-gui - GTK+ frontend to rmlint

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

  https://mentors.debian.net/package/rmlint


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

dget -x
https://mentors.debian.net/debian/pool/main/r/rmlint/rmlint_2.4.6-1.dsc

  More information about rmlint can be obtained from
https://rmlint.readthedocs.io/.

  Changes since the last upload:

  rmlint (2.4.6-1) unstable; urgency=medium

  * Initial upload to Debian. Thanks to Axel Beckert for getting
it all started, and to Roger Shimizu for suggested improvements.
(Closes: #845155)

 -- Carlos Maddela <e7ap...@gmail.com>  Tue, 14 Feb 2017 10:04:33 +1100

  Regards,
   Carlos Maddela


On 10/02/17 00:21, Roger Shimizu wrote:
> Control: tag -1 +moreinfo
>
> Dear Carlos,
>
> I cannot sponsor the upload. But here's my review that I hope it's helpful.
>
> On Tue, Jan 17, 2017 at 3:56 AM, Carlos Maddela <e7ap...@gmail.com> wrote:
>>   I am looking for a sponsor for my package "rmlint"
>>
>>  * Package name: rmlint
>>Version : 2.4.6-1
>>Upstream Author : Christopher Pahl <sa...@online.de>
>>  * URL : https://rmlint.readthedocs.io/
>>  * License : GPL-3
>>Section : utils
> Here're the items need to be fixed:
>  - license/copyright
>There're many files not under GPL-3, which need to be mentioned in
> d/copyright
>
>  - There's Vcs-* line set for collab-maint, but I cannot access it.
>Please push your work in collab-maint or other git repo, which make
> the review easier.
>
>  - There's doc/ folder, but you didn't install them?
>
> Cheers,

Bug#851606: RFS: rmlint/2.4.6-1 [ITP]

2017-02-14 Thread Carlos Maddela



On 14/02/17 18:56, Axel Beckert wrote:
> Hi,
>
> Carlos Maddela wrote:
>> Thanks for your suggestions. I have made the fixes and re-uploaded the
>> source files as the same version (since it still has yet to be
>> officially released) to mentors. I have applied for access to
>> collab-maint (just a few minutes ago), so I probably won't be able to
>> push my changes for another 24 hours. For the meantime, my changes are
>> available in the debian branch of https://github.com/e7appew/rmlint.git.
> Carlos: Thanks for the updated package.
>
> Roger: Thanks for the review and the reminder about this RFS.
>
> I've did a short first review. Will have a closer look at it probably
> this evening.
>
> One thing I noticed is that the upstream tar ball available at
> https://github.com/sahib/rmlint/releases and in the source package are
> not identical due to different compression.
>
> Is there a reason not to use the official source tarballs from
> https://github.com/sahib/rmlint/releases? (AFAIK and according to a
> short check, GitHub no more produces different tarballs upon
> subsequent downloads as it did in the past.)
>
> (Contentwise the contained files seem to be identical, so it's ok-ish,
> but such differences always cause extra work on any review of a source
> package, so it's preferred to use official tar balls if possible --
> which seems to be possible here.)
There wasn't any specific reason, except for trying to keep file sizes
as small as possible. I have reverted to using the original tarballs now.
>
> In debian/rules I found this:
>
> # Automatically disable tests in sbuild and pbuilder.
> ifneq (,$(filter /%nonexistent,$(HOME)))
> export DEB_BUILD_MAINT_OPTIONS += nocheck
> endif
>
> If this is to avoid issues with the test suite, it's a very unlucky
> solution as all of Debian's build daemon run sbuild and some sponsors
> upload packages using pbuilder. So when the binary packages are built
> which are to become the official binary packages, the test suite is
> not run. This especially applies to all other architectures than the
> maintainer's one and hence contradicts the idea that the test suite
> should be run at build time on all architectures to find
> architecture-specific issues.
>
> If a non-existent home is really such an issue, I'd rather set it to
> some other value and create that home directory with some sane
> contents, e.g. debian/tmp-home or so.
I only disabled the tests to speed up builds. There was initially some
problems with the tests inside of sbuild, which prevented successful
builds, but they have been resolved. The test suite doesn't make use of
any $HOME directory. It was just my way of detecting if the build was
being done from a chroot.

Anyway, I have removed those lines completely, and the tests are
performed now.

Cheers,

Carlos




signature.asc
Description: OpenPGP digital signature

Bug#851606: RFS: rmlint/2.4.6-1 [ITP]

2017-01-16 Thread Carlos Maddela

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

 * Package name: rmlint
   Version : 2.4.6-1
   Upstream Author : Christopher Pahl <sa...@online.de>
 * URL : https://rmlint.readthedocs.io/
 * License : GPL-3
   Section : utils

  It builds these binary packages:

rmlint - Extremely fast tool to remove filesystem lint
rmlint-gui - GTK+ frontend to rmlint

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

https://mentors.debian.net/package/rmlint


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

dget -x 
https://mentors.debian.net/debian/pool/main/r/rmlint/rmlint_2.4.6-1.dsc

  More information about rmlint can be obtained from 
https://rmlint.readthedocs.io/.

  Initial upload:

   rmlint (2.4.6-1) unstable; urgency=medium

 * Initial upload to Debian. Thanks to Axel Beckert for getting
   it all started. (Closes: #845155)

-- Carlos Maddela <e7ap...@gmail.com>  Tue, 17 Jan 2017 04:45:28 +1100


  Regards,
   Carlos Maddela

Bug#796820: RFA: urjtag -- JTAG programmer for various flash parts and boards

2016-09-13 Thread Antonio Carlos

Good Morning ( at least in SP is morning),

My name is Antonio Carlos

I have been interested in package adoption post by you on the :

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


I wanna be a DD .



Best Regards,

Antonio Carlos

Bug#802487: Aide crash (SIGSEGV) solved by reinstalling

2016-09-27 Thread Carlos Pérez

Hi,

I came across this same problem (the same segmentation fault in the same
place) today and I was able to get a working Aide just by reinstalling
the package:

apt-get install aide --reinstall

I think that the segmentation fault was produced by a corrupt aide
binary, since the aide's SHA256 signature changes after reinstalling the
package (note that it is the same package version that is reinstalled).
In fact, the size in the corrupted file is the same that that of the
correct one.

I was able to detect this because I use two different Debian 8.5 virtual
machines and only in one of them aide crashed. The working system was
created using a standard Debian installation CD while the faulty one was
created using debootstrap (I don't know whether this is relevant or not).

I know it could be a security issue. But, I doubt it, because both
systems are virtual machines behind a NAT router, they don't offer any
service to the Internet and they don't use Internet services either
(apart from the Debian repositories).

The situation before reinstalling in the faulty system:

Working system:
# ls -l $(which aide)
-rwxr-xr-x 1 root root 1597208 Oct 24  2014 /usr/bin/aide
# sha256sum /usr/bin/aide
e382183d9f94e0325af0a8d235445a82f0aab9c3fc134b9219b9b290722db7e5
/usr/bin/aide
# aide
Couldn't open file
/var/lib/aide/please-dont-call-aide-without-parameters/aide.db for reading

Faulty system:
# ls -l $(which aide)
-rwxr-xr-x 1 root root 1597208 Oct 24  2014 /usr/bin/aide
# sha256sum /usr/bin/aide
c2ac6ddeb386376fa2f504e5471fb9880baffd15807060b37b28bcabb91466bd
/usr/bin/aide
# aide
Segmentation fault

After reinstalling aide in the faulty system, the SHA256 matches that of
the working one, and aide works OK.

Further information:
- Both system are Debian 8.5 x86_64
- Aide version: 0.16~a2.git20130520-3
- I upgraded the faulty system to Debian 8.6 (no aide upgrade, however)
and the segmentation fault was still there.
- The faulty one was a User-Mode Linux virtual machine running inside
the working one (a VMware Workstation virtual machine).

Hope it helps.

Sincerely,

-- 
Carlos Pérez

Bug#844055: Doesn't support conversion of images with dimensions of 256x256 or greater.

2016-11-12 Thread Carlos Maddela

When you clone the master branch from the sourceforge repo, the Debian
package won't compile without a whole lot of tweaking. Instead of
belatedly merging Debian changes into the upstream branch, I propose
that it be kept in a separate branch so that it's exactly the same as
(or newer than) what you get with "apt-get source". It would make
contributing code much easier.

If you take a look at the sf/master and debian/sid branches in my github
repo, that's what I suggest the upstream and debian branches look like.

Anyway, I have rebased my fix for this bug based on these new branches
in debian/openjpeg2, as well as sf/openjpeg2, should you want the
changes in the upstream branch as well.

On 12/11/16 15:28, Paul Wise wrote:
> On Sat, 2016-11-12 at 14:53 +1100, Carlos Maddela wrote:
>
>> I will make my changes available at ... on the openjpeg2 branch for
>> your perusal.
> Looks like you forgot to push the branch. Also, please clone from the
> upstream git repo instead of importing the Debian tarballs into git.
>
> https://sourceforge.net/p/icns/code/ci/master/tree/
>
>

signature.asc
Description: OpenPGP digital signature

Bug#844601: python-spyder: "from spyder.plugins.editor import Editor" hangs the machine

2016-11-28 Thread Carlos Pascual

On Sunday, November 27, 2016 6:22:48 PM CET Dmitry Shachnev wrote:
> Such code should not be run on module *import* time, it should be run
> when the spyder code is first *used*.

I completely agree with this. 

Also, I second the opinion that segfaults when using Qt code without a 
QApplication is expected behavior.

So, IMHO, the bug is in the python-spyder package

Cheers,

Carlos

Bug#796361: python-lzma: FTBFS when building with DEB_BUILD_OPTIONS 'nocheck nobench'

2016-11-19 Thread Carlos Maddela

This bug has also been fixed in the 'bugfixes' branch of
https://github.com/e7appew/python-lzma.git.

On Fri, 21 Aug 2015 16:19:40 +0200 John Paul Adrian Glaubitz wrote:
> Package: python-lzma
> Version: 0.5.3-3
> Severity: normal
>
> Hello!
>
> python-lzma fails to build from source when disabling the test suite
by setting the
> appropriate DEB_BUILD_OPTIONS flags 'nocheck nobench':
>
> debian/rules override_dh_auto_test
> make[1]: Entering directory '/Â«PKGBUILDDIRÂ»'
> make[1]: *** No rule to make target 'test2.7', needed by
'override_dh_auto_test'. Stop.
> make[1]: Leaving directory '/Â«PKGBUILDDIRÂ»'
> make: *** [build-arch] Error 2
> debian/rules:42: recipe for target 'build-arch' failed
> dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
>
> While disabling the testsuite is normally not advised, it is often
desirable when
> doing a quick test build, especially when building the package on
slower machines
> like the m68k or sh4 buildds.
>
> Could you please drop the dependency of the override_dh_auto_test
target on the
> target test2.7 such that python-lzma builds fine even when tests are
disabled?
>
> Thanks,
>
> Adrian
>
> --
> .''`. John Paul Adrian Glaubitz
> : :' : Debian Developer - glaub...@debian.org
> `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
> `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
>
>

Bug#845009: Cannot specify a 'check' option [ crc32 | crc64 | sha256 ]

2016-11-19 Thread Carlos Maddela

Package: python-lzma
Version: 0.5.3-3
Severity: normal
Tags: patch

Hello!

python-lzma fails with a ValueError exception if you try to set
the 'check' option to any of the accepted values as stated in the
documentation. I have attached an example script to demonstrate the
problem.

This bug was reported upstream quite a while ago now, here:
https://bugs.launchpad.net/pyliblzma/+bug/1243344, but remains
unfixed.  I have recently forwarded my patch though, here:
https://code.launchpad.net/~e7appew/pyliblzma/bugfix-1243344.

I will soon make my fix to the Debian package along with
other changes in the 'bugfixes' branch of this repo:
https://github.com/e7appew/python-lzma.git.

Best regards,

Carlos

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

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

Versions of packages python-lzma depends on:
ii  libc6   2.24-5
ii  liblzma55.2.2-1.2
ii  python  2.7.11-2
pn  python:any  

python-lzma recommends no packages.

python-lzma suggests no packages.

-- no debconf information
#!/usr/bin/python

import lzma

with open('data.tar', 'rb') as infile:
with open('new-data.tar.xz', 'wb') as outfile:
outfile.write(lzma.compress(infile.read(), options={'check':'crc64'}))

Bug#844055: Doesn't support conversion of images with dimensions of 256x256 or greater.

2016-11-17 Thread Carlos Maddela

Just letting you know I've just done a "git push -f" on my
debian/openjpeg2 which includes changes to allow the package to be built
with hardening options set.


On 13/11/16 06:37, Carlos Maddela wrote:
> When you clone the master branch from the sourceforge repo, the Debian
> package won't compile without a whole lot of tweaking. Instead of
> belatedly merging Debian changes into the upstream branch, I propose
> that it be kept in a separate branch so that it's exactly the same as
> (or newer than) what you get with "apt-get source". It would make
> contributing code much easier.
>
> If you take a look at the sf/master and debian/sid branches in my github
> repo, that's what I suggest the upstream and debian branches look like.
>
> Anyway, I have rebased my fix for this bug based on these new branches
> in debian/openjpeg2, as well as sf/openjpeg2, should you want the
> changes in the upstream branch as well.
>
> On 12/11/16 15:28, Paul Wise wrote:
>> On Sat, 2016-11-12 at 14:53 +1100, Carlos Maddela wrote:
>>
>>> I will make my changes available at ... on the openjpeg2 branch for
>>> your perusal.
>> Looks like you forgot to push the branch. Also, please clone from the
>> upstream git repo instead of importing the Debian tarballs into git.
>>
>> https://sourceforge.net/p/icns/code/ci/master/tree/
>>
>>
>




signature.asc
Description: OpenPGP digital signature

Bug#844055: Doesn't support conversion of images with dimensions of 256x256 or greater.

2016-11-11 Thread Carlos Maddela

Was just about to do that.

I did have a look at that repo too, but it seems like it's out of sync
with the latest Debian source in sid (unless I've missed something).
They both have their own versions of 0.8.1-3.

Also, for now, I have represented my changes as patches in the
debian/patches directory without modifying the upstream source. It seems
a little confusing managing Debian changes upstream as well, unless it
was a native package.

I will push my changes based on the imported Debian source for now, so
you can check the changes. It shouldn't be too difficult to rebase the
changes later on once that repo is in sync. I'll do that as soon as it's
updated.

On 12/11/16 15:28, Paul Wise wrote:
> On Sat, 2016-11-12 at 14:53 +1100, Carlos Maddela wrote:
>
>> I will make my changes available at ... on the openjpeg2 branch for
>> your perusal.
> Looks like you forgot to push the branch. Also, please clone from the
> upstream git repo instead of importing the Debian tarballs into git.
>
> https://sourceforge.net/p/icns/code/ci/master/tree/
>
>

signature.asc
Description: OpenPGP digital signature

Bug#844055: Doesn't support conversion of images with dimensions of 256x256 or greater.

2016-11-11 Thread Carlos Maddela

Package: icnsutils
Version: 0.8.1-3
Severity: normal
Tags: patch

Dear Maintainer,

Support for images with larger dimensions was available when the package
used to link with jasper, and presumably openjpeg1 as well. However, this
feature hasn't been available ever since the package has been mistakenly
trying to compile with openjpeg2.

As it is now, the code doesn't support openjpeg2 and the package may as
well not list openjpeg2 as a build dependency.

I have had a go at getting the code to work with openjpeg2 and
it seems to do the trick. I will make my changes available at
https://github.com/e7appew/libicns.git on the openjpeg2 branch for your
perusal.

Best regards,

Carlos

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

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

Versions of packages icnsutils depends on:
ii  libc62.24-5
ii  libicns1 0.8.1-3
ii  libpng16-16  1.6.26-1

icnsutils recommends no packages.

icnsutils suggests no packages.

-- no debconf information

Bug#845104: 'xz -vv --robot --list' of non-existent file results in printing of an uninitialized buffer

tag -1 patch

thanks


diff -Nru xz-utils-5.2.2/debian/changelog xz-utils-5.2.2/debian/changelog
--- xz-utils-5.2.2/debian/changelog 2016-10-09 00:11:19.0 +1100
+++ xz-utils-5.2.2/debian/changelog 2016-11-20 23:18:37.0 +1100
@@ -1,3 +1,10 @@
+xz-utils (5.2.2-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Stop printing uninitialized buffer. (Closes: #845104)
+
+ -- Carlos Maddela <e7ap...@gmail.com>  Sun, 20 Nov 2016 23:18:37 +1100
+
 xz-utils (5.2.2-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru xz-utils-5.2.2/debian/patches/series 
xz-utils-5.2.2/debian/patches/series
--- xz-utils-5.2.2/debian/patches/series2016-10-09 00:01:46.0 
+1100
+++ xz-utils-5.2.2/debian/patches/series2016-11-20 23:17:49.0 
+1100
@@ -1,3 +1,4 @@
 liblzma-skip-ABI-incompatible-check-when-liblzma.so.patch
 liblzma-make-dlopen-based-liblzma2-compatibility-opt.patch
 kfreebsd-link-against-libfreebsd-glue.patch
+stop-printing-uninitialized-buffer.patch
diff -Nru 
xz-utils-5.2.2/debian/patches/stop-printing-uninitialized-buffer.patch 
xz-utils-5.2.2/debian/patches/stop-printing-uninitialized-buffer.patch
--- xz-utils-5.2.2/debian/patches/stop-printing-uninitialized-buffer.patch  
1970-01-01 10:00:00.0 +1000
+++ xz-utils-5.2.2/debian/patches/stop-printing-uninitialized-buffer.patch  
2016-11-20 23:18:18.0 +1100
@@ -0,0 +1,35 @@
+From: Carlos Maddela <e7ap...@gmail.com>
+Date: Sun, 20 Nov 2016 20:57:44 +1100
+Subject: Stop printing uninitialized buffer.
+
+Description: Stop printing uninitialized buffer.
+ When 'xz -vv --robot --list' is performed on a non-existent
+ file, an uninitialized buffer representing the check method
+ used is dumped. This fix prevents this from happening.
+Author: Carlos Maddela <e7ap...@gmail.com>
+Origin: vendor
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845104
+Forwarded: no
+Last-Update: 2016-11-20
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+---
+ src/xz/list.c | 5 -
+ 1 file changed, 4 insertions(+), 1 deletion(-)
+
+diff --git a/src/xz/list.c b/src/xz/list.c
+index 449c2bc..edf8767 100644
+--- a/src/xz/list.c
 b/src/xz/list.c
+@@ -636,7 +636,10 @@ static void
+ get_check_names(char buf[CHECKS_STR_SIZE],
+   uint32_t checks, bool space_after_comma)
+ {
+-  assert(checks != 0);
++  // If no check mask is specified, assume "None",
++  // so we never return with an uninitialized buffer.
++  if (checks == 0)
++  checks = 1;
+ 
+   char *pos = buf;
+   size_t left = CHECKS_STR_SIZE;

Bug#845104: 'xz -vv --robot --list' of non-existent file results in printing of an uninitialized buffer

Package: xz-utils
Version: 5.2.2-1.2
Severity: normal

The following is an example of the output:

xz: nofile.tar.xz: No such file or directory
totals  0   0   0   0   --- h!P³â  0   0   0   
yes 0

Given that the output is supposed to be machine readable, the output
should be predictable and reproducible.

A patch to follow shortly...

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

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

Versions of packages xz-utils depends on:
ii  libc6 2.24-5
ii  liblzma5  5.2.2-1.2

xz-utils recommends no packages.

xz-utils suggests no packages.

-- no debconf information

Bug#845173: Cannot handle new debs with data component XZ compressed in parallel

Package: debdelta
Version: 0.55
Severity: grave
Tags: patch

Ever since dpkg 1.18.14 or 1.18.15 was released there haven't been too
many usable debdeltas available for download. The reason being that debs
that have their data component compressed in XZ format are now being
done so in parallel, which produces a file that debdelta cannot
reproduce.

For example, trying to create a debdelta results in:

> $ debdelta -vv fluid-soundfont-gm_3.1-5_all.deb 
> fluid-soundfont-gm_3.1-5.1_all.deb /tmp/patch.debdelta
>  OLD: Package: fluid-soundfont-gm Version: 3.1-5 Architecture: all 
> Installed-Size: 145368
>  NEW: Package: fluid-soundfont-gm Version: 3.1-5.1 Architecture: all 
> Installed-Size: 145169
>   debdelta.conf says we will skip:  []
>   studying  debian-binary  of len 0kB
>   studying  control.tar.gz  of len 0kB
>   time lost so far in finding correspondence 0.00
>   compute delta for 0 (1kB) and 1 (10kB)
>   delta is 7.57% of 1, speed: 1942kB /sec
>   studying  data.tar.xz  of len 116822kB
>  Tried XZ options but failed:  --lzma2=dict=8MiB crc64
>  Tried XZ options but failed:  -9e crc64
>  Tried XZ options but failed:  -9 crc64
>  Tried XZ options but failed:  -6e crc64
> debdelta : Cannot guess XZ parameters (non retriable

I have a patch which I will make available shortly...

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

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

Versions of packages debdelta depends on:
ii  binutils2.27.51.20161118-2
ii  bzip2   1.0.6-8
ii  libbz2-1.0  1.0.6-8
ii  libc6   2.24-5
ii  python  2.7.11-2
ii  zlib1g  1:1.2.8.dfsg-2+b3

Versions of packages debdelta recommends:
ii  bsdiff   4.3-19
ii  gnupg-agent  2.1.15-9
ii  gnupg2   2.1.15-9
ii  lzma 9.22-2
ii  python-apt   1.1.0~beta5
ii  python-debian0.1.29
ii  xdelta   1.1.3-9.1
ii  xdelta3  3.0.11-dfsg-1
ii  xz-utils [lzma]  5.2.2-1.3

Versions of packages debdelta suggests:
ii  debdelta-doc  0.55+nmu1

-- no debconf information

Bug#845173: Cannot handle new debs with data component XZ compressed in parallel