Bug#867757: Updating the powertop Uploaders list

[Jose-Luis Rivas]

Sure, will do.

On 09/07/17, 10:56, Tobias Frost wrote:
> Source: powertop
> Version: 2.8-1
> Severity: minor
> User: m...@qa.debian.org
> Usertags: mia-teammaint
> 
> Patrick Winnertz  has not been working on
> the powertop package for quite some time.
> 
> We are tracking their status in the MIA team and would like to ask you
> to remove them from the Uploaders list of the package so we can close
> that part of the file.
> 
> (If the person is listed as Maintainer, what we are asking is to please
> step in as a new maintainer.)
> 
> Thanks.



-- 
⨳ PGP 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co

Bug#804197: rtorrent no longer depends on libsigc++

[Jose-Luis Rivas]

You are right! Sorry I missed this; I'll get this on a new release this
weekend.

On 06/11/15, 01:37pm, Patrick Li wrote:
> Package: rtorrent
> Version: 0.9.6-1
> 
> Upstream has removed dependency on sigc++ in this commit.
> 
> https://github.com/rakshasa/rtorrent/commit/370bae4b986ce541756491a0934d22db3cc69534
> 
> So the debian control file should no longer list libsigc++-2.0-dev as a
> dependency.

-- 
⨳ PGP 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co


signature.asc
Description: PGP signature

Bug#797866: libtorrent: ABI transition needed for libstdc++ v5

[Jose-Luis Rivas]

On 21/09/15, 09:52am, Simon McVittie wrote:
> On Wed, 09 Sep 2015 at 05:38:16 -0700, Jose-Luis Rivas wrote:
> > The only reverse dependencies are rtorrent and it needs an upgrade as
> > well since there's a newer upstream version (it's the same upstream)
> > depending on the newer version of libtorrent.
> > 
> > Do I really need to do the transition or is it safe then?
> 
> libtorrent needs *some* transition: either the v5 rename, or the new SONAME.
> 
> If you are prepared to deal with both libtorrent and rtorrent, including any
> fallout from regressions in the new upstream version, then you can go the
> new-SONAME route if you prefer.

Yes, I have rtorrent ready, awaiting for libtorrent19 to pass NEW.
-- 
⨳ PGP 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co


signature.asc
Description: Digital signature

Bug#797866: libtorrent: ABI transition needed for libstdc++ v5

[Jose-Luis Rivas]

Nevermind, upstream bumped soname anyway.

On 08/09/15, 10:24pm, Jose-Luis Rivas wrote:
> Just to be clear, if I rebuild this with the source packages from
> unstable with a new upstream version the rename is not necessary?
> 
> On 03/09/15, 08:21am, Simon McVittie wrote:
> > Source: libtorrent
> > Version: 0.13.2-1
> > Severity: serious
> > Justification: breaks ABI without a package rename
> > Tags: sid stretch
> > User: debian-...@lists.debian.org
> > Usertags: libstdc++-cxx11
> > 
> > Background[1]: libstdc++6 introduces a new ABI to conform to the
> > C++11 standard, but keeps the old ABI to not break existing binaries.
> > Packages which are built with g++-5 from experimental (not the one
> > from testing/unstable) are using the new ABI.  Libraries built from
> > this source package export some of the new __cxx11 or B5cxx11 symbols,
> > dropping other symbols.  If these symbols are part of the API of
> > the library, then this rebuild with g++-5 will trigger a transition
> > for the library.
> > 
> > In the case of libtorrent, std::string appears in functions that are
> > explicitly exported, so it seems very likely that a transition is needed.
> > The transition normally consists of renaming the
> > affected library packages, adding a v5 suffix (libtorrent14v5).
> > The SONAME should not be changed when doing this.
> > 
> > If an upgrade to a new upstream SONAME is already planned, and that
> > SONAME has never been available in Debian compiled with g++-4, then an
> > alternative way to carry out the transition would be to bump the
> > SONAME. Please avoid doing this unless the new upstream version
> > is very low-risk.
> > 
> > These follow-up transitions for libstdc++ are not going through exactly
> > the normal transition procedure, because many entangled transitions are
> > going on at the same time, and the usual ordered transition procedure
> > does not scale that far. When all the C++ libraries on which this library
> > depends have started their transitions in unstable if required, this
> > library should do the same, closing this bug; the release team will deal
> > with binNMUs as needed.
> > 
> > Looking at the build-dependencies of libtorrent, the C++ libraries
> > are libcppunit and libsigc++, which have both had their renames
> > already; so this sub-transition is ready to start.
> > 
> > The package might be NMU'd if there is no maintainer response. The
> > release team have declared a 2 day NMU delay[2] for packages involved
> > in the libstdc++ transition, in order to get unstable back to a usable
> > state in a finite time.
> > 
> > Regards,
> > S
> > 
> > [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
> > [2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html
> 
> -- 
> ⨳ PGP 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co



-- 
⨳ PGP 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co


signature.asc
Description: Digital signature

Bug#797866: libtorrent: ABI transition needed for libstdc++ v5

[Jose-Luis Rivas]

On 09/09/15, 07:30am, Simon McVittie wrote:
> On 09/09/15 07:00, Jose-Luis Rivas wrote:
> > On 08/09/15, 10:24pm, Jose-Luis Rivas wrote:
> >> Just to be clear, if I rebuild this with the source packages from
> >> unstable with a new upstream version the rename is not necessary?
> >
> > Nevermind, upstream bumped soname anyway.
> 
> A new upstream SONAME makes the v5 transition rename unnecessary; but if
> upstream have bumped SONAME, then they've broken API/ABI (or are doing
> it wrong), which increases the risk that reverse-dependencies of
> libtorrent will fail to compile or fail to work.
> 
> A new upstream release that does not bump the SONAME does not have any
> effect on the need for a transition/rename.
> 
> I suspect that the lowest-risk approach to getting this transition
> finished in a finite time is to do the v5 rename, then ask the release
> team for a separate transition slot for the new upstream SONAME.
> 

The only reverse dependencies are rtorrent and it needs an upgrade as
well since there's a newer upstream version (it's the same upstream)
depending on the newer version of libtorrent.

Do I really need to do the transition or is it safe then?

-- 
⨳ PGP 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co


signature.asc
Description: Digital signature

Bug#797866: libtorrent: ABI transition needed for libstdc++ v5

[Jose-Luis Rivas]

Just to be clear, if I rebuild this with the source packages from
unstable with a new upstream version the rename is not necessary?

On 03/09/15, 08:21am, Simon McVittie wrote:
> Source: libtorrent
> Version: 0.13.2-1
> Severity: serious
> Justification: breaks ABI without a package rename
> Tags: sid stretch
> User: debian-...@lists.debian.org
> Usertags: libstdc++-cxx11
> 
> Background[1]: libstdc++6 introduces a new ABI to conform to the
> C++11 standard, but keeps the old ABI to not break existing binaries.
> Packages which are built with g++-5 from experimental (not the one
> from testing/unstable) are using the new ABI.  Libraries built from
> this source package export some of the new __cxx11 or B5cxx11 symbols,
> dropping other symbols.  If these symbols are part of the API of
> the library, then this rebuild with g++-5 will trigger a transition
> for the library.
> 
> In the case of libtorrent, std::string appears in functions that are
> explicitly exported, so it seems very likely that a transition is needed.
> The transition normally consists of renaming the
> affected library packages, adding a v5 suffix (libtorrent14v5).
> The SONAME should not be changed when doing this.
> 
> If an upgrade to a new upstream SONAME is already planned, and that
> SONAME has never been available in Debian compiled with g++-4, then an
> alternative way to carry out the transition would be to bump the
> SONAME. Please avoid doing this unless the new upstream version
> is very low-risk.
> 
> These follow-up transitions for libstdc++ are not going through exactly
> the normal transition procedure, because many entangled transitions are
> going on at the same time, and the usual ordered transition procedure
> does not scale that far. When all the C++ libraries on which this library
> depends have started their transitions in unstable if required, this
> library should do the same, closing this bug; the release team will deal
> with binNMUs as needed.
> 
> Looking at the build-dependencies of libtorrent, the C++ libraries
> are libcppunit and libsigc++, which have both had their renames
> already; so this sub-transition is ready to start.
> 
> The package might be NMU'd if there is no maintainer response. The
> release team have declared a 2 day NMU delay[2] for packages involved
> in the libstdc++ transition, in order to get unstable back to a usable
> state in a finite time.
> 
> Regards,
> S
> 
> [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
> [2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html

-- 
⨳ PGP 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co


signature.asc
Description: Digital signature

Bug#754567: rtorrent: new upstream release (0.9.4)

[Jose-Luis Rivas]

On 02/02/15, 12:47am, deb...@chr1s.eu wrote:
 Hi Jose,
 
 do you have any news regarding a new rtorrent package?
 
 

Jonathan McDowell put libtorrent 0.13.4 on experimental and rtorrent is
to follow [0], yet the freeze has stopped it AFAIK.

[0] https://packages.debian.org/experimental/libtorrent-dev

-- 
⨳ PGP 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co


signature.asc
Description: Digital signature

Bug#775382: libtorrent: please add debug package

[Jose-Luis Rivas]

On 15/01/15, 08:32am, Paul Wise wrote:
 Source: libtorrent
 Severity: wishlist
 
 I've recently had rtorrent segfault a few times. Please add a
 libtorrent-dbg package so that I can report a useful bug.
 

ACK, sadly I'm out of time right now so if anybody wants to pick up
these: the source is in collab-maint and I can sponsor uploads for
non-developers.

Kind regards,
-- 
⨳ PGP 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co


signature.asc
Description: Digital signature

Bug#773747: pgpdump: infinite loop on crafted file

[Jose-Luis Rivas]

On 22/12/14, 10:52pm, Jakub Wilk wrote:
 * Jakub Wilk jw...@debian.org, 2014-12-22, 22:41:
 pgpdump hangs when trying to dump the attached crafted file.
 Now really attached.
 
 But my MUA mangled it somehow. :-(
 
 Third time lucky. This command hangs:
 
 printf '\243\003' | pgpdump
 
 -- 
 Jakub Wilk

Just got this messages, thanks, now it's actually attached.

-- 
⨳ PGP 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co


signature.asc
Description: Digital signature

Bug#773747: pgpdump: infinite loop on crafted file

[Jose-Luis Rivas]

On 22/12/14, 10:31pm, Jakub Wilk wrote:
 Package: pgpdump
 Version: 0.28-1
 Usertags: afl
 
 pgpdump hangs when trying to dump the attached crafted file.
 
 strace tells me it's repeatedly trying to read past EOF:
 
 read(0, , 8192)   = 0
 read(0, , 8192)   = 0
 read(0, , 8192)   = 0
 read(0, , 8192)   = 0
 read(0, , 8192)   = 0
 [...ad infinitum...]
 
 This bug was found using American fuzzy lop:
 https://packages.debian.org/experimental/afl

Hi Jakub, what's the precise file you are trying here? Never got
anything attached here.

Kind regards.

-- 
⨳ PGP 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co


signature.asc
Description: Digital signature

Bug#772571: powertop uses /usr/sbin/hciconfig instead of /bin/hciconfig

[Jose-Luis Rivas]

tags 772571 confirmed upstream
quit

On 08/12/14, 06:21pm, Laurent Bigonville wrote:
 Package: powertop
 Version: 2.6.1-1
 Severity: normal
 
 Hi,
 
 It seems that powertop uses /usr/sbin/hciconfig instead of
 /bin/hciconfig when it tries to optimize the bluetooth power usage on
 the Tunables tab.
 
 It path should be fixed and executables should maybe looked inside PATH
 instead of hardcoding the path like that

ACK, working on a patch for it.

Thanks for the report.

-- 
⨳ GPG 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co


signature.asc
Description: Digital signature

Bug#771810: rtorrent: hangs during DNS queries

[Jose-Luis Rivas]

tags 771810 upstream confirmed
forwarded 771810 https://github.com/rakshasa/rtorrent/issues/247
quit

On 02/12/14, 04:48pm, Simon Richter wrote:
 Package: rtorrent
 Version: 0.9.2-1
 Severity: normal
 
 Hi,
 
 one of the trackers for a file I'm hosting appears to be in a domain with a
 broken DNS server, making the query time out in the local recursive resolver.
 
 It appears as if rtorrent hangs the entire time the DNS request is 
 outstanding.

Thanks for your report, this was caused by the the DDoS yesterday on DNSimple.

Not only that, this is already reported to the upstream[0].
[0] https://github.com/rakshasa/rtorrent/issues/247

Kind regards.
-- 
⨳ GPG 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co


signature.asc
Description: Digital signature

Bug#771811: rtorrent: blacklist for discontinued trackers

[Jose-Luis Rivas]

forwarded 771811 https://github.com/rakshasa/rtorrent/issues/256
tags 771811 confirmed upstream
quit

On 02/12/14, 04:52pm, Simon Richter wrote:
 Package: rtorrent
 Version: 0.9.2-1
 Severity: wishlist
 Tags: upstream
 
 Hi,
 
 it would be nice if there were a feature to drop trackers that are
 obviously discontinued, such as when their DNS name starts
 resolving to 127.0.0.1.

Agreed, it would be very nice.

-- 
⨳ GPG 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co


signature.asc
Description: Digital signature

Bug#765074: vagrant: Cannot download self-hosted vagrantcloud box

[Jose Luis Rivas]

I can confirm this bug with a little difference: is downloading an image
from an URL.

The steps to reproduce this is simply trying to `vagrant up` dokku's
Vagrantfile.

```sh
git clone https://github.com/progrium/dokku.git
cd dokku
vagrant up
```

It gives me this error:

8---
== box: Adding box 'trusty' (v0) for provider:
box: Downloading:

https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

The requested URL returned error: 400 Bad Request
---8

I know this URL works because I've been spawning this same Vagrantfile
in several machines, this is the first Debian sid I try it today in a
freshly installed machine.

Plus, it works perfectly with upstream-provided .deb
-- 
Jose Luis Rivas · http://joseluisrivas.net http://ghostbar.co
GPG ∆ 4096R/D278 F9C1 5E54 61AA 3C1E 2FCD 13EC 43EE B9AC 8C43


signature.asc
Description: Digital signature

Bug#754567: rtorrent: new upstream release (0.9.4)

[Jose Luis Rivas]

As a follow up: upstream author told me he would do a release shortly
with this issue solved.

On 12/10/14, 09:43am, Jose Luis Rivas wrote:
 ACK. I haven't made this update because there's a bug with the new
 release, I asked upstream to fix it and he kind of made it but didn't
 made a release tarball for this.
 
 I'm gonna ping him again about this.
 
 Kind Regards.
 
 On 12/10/14, 01:11pm, Goswin von Brederlow wrote:
  Package: rtorrent
  Version: 0.9.2-1
  Followup-For: Bug #754567
  
  Version 0.9.4 fixes an incompatibility with utorrent 3.x that causes
  chunks to be downloaded and ignored. The effect is that a lot more
  data is downloaded than is used and peers stall, not downloading
  anything anymore despite them offering.
  
  Please update rtorrent and libtorrent.
  
  MfG
  Goswin
  
  -- System Information:
  Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386
  
  Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
  Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
  Shell: /bin/sh linked to /bin/dash
  
  Versions of packages rtorrent depends on:
  ii  libc6   2.19-1
  ii  libcurl37.38.0-2
  ii  libgcc1 1:4.9.0-9
  ii  libncursesw55.9+20140913-1
  ii  libsigc++-2.0-0c2a  2.2.11-4
  ii  libstdc++6  4.9.0-9
  ii  libtinfo5   5.9+20140913-1
  ii  libtorrent140.13.2-1
  ii  libxmlrpc-core-c3   1.33.14-0.1
  
  rtorrent recommends no packages.
  
  Versions of packages rtorrent suggests:
  ii  screen  4.2.0-2
  
  -- no debconf information
 
 -- 
 Jose Luis Rivas · http://joseluisrivas.net http://ghostbar.co
 GPG ∆ 4096R/D278 F9C1 5E54 61AA 3C1E 2FCD 13EC 43EE B9AC 8C43

-- 
Jose Luis Rivas · http://joseluisrivas.net http://ghostbar.co
GPG ∆ 4096R/D278 F9C1 5E54 61AA 3C1E 2FCD 13EC 43EE B9AC 8C43


signature.asc
Description: Digital signature

Bug#754567: rtorrent: new upstream release (0.9.4)

[Jose Luis Rivas]

ACK. I haven't made this update because there's a bug with the new
release, I asked upstream to fix it and he kind of made it but didn't
made a release tarball for this.

I'm gonna ping him again about this.

Kind Regards.

On 12/10/14, 01:11pm, Goswin von Brederlow wrote:
 Package: rtorrent
 Version: 0.9.2-1
 Followup-For: Bug #754567
 
 Version 0.9.4 fixes an incompatibility with utorrent 3.x that causes
 chunks to be downloaded and ignored. The effect is that a lot more
 data is downloaded than is used and peers stall, not downloading
 anything anymore despite them offering.
 
 Please update rtorrent and libtorrent.
 
 MfG
   Goswin
 
 -- System Information:
 Debian Release: jessie/sid
   APT prefers unstable
   APT policy: (500, 'unstable'), (1, 'experimental')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386
 
 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
 Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
 Shell: /bin/sh linked to /bin/dash
 
 Versions of packages rtorrent depends on:
 ii  libc6   2.19-1
 ii  libcurl37.38.0-2
 ii  libgcc1 1:4.9.0-9
 ii  libncursesw55.9+20140913-1
 ii  libsigc++-2.0-0c2a  2.2.11-4
 ii  libstdc++6  4.9.0-9
 ii  libtinfo5   5.9+20140913-1
 ii  libtorrent140.13.2-1
 ii  libxmlrpc-core-c3   1.33.14-0.1
 
 rtorrent recommends no packages.
 
 Versions of packages rtorrent suggests:
 ii  screen  4.2.0-2
 
 -- no debconf information

-- 
Jose Luis Rivas · http://joseluisrivas.net http://ghostbar.co
GPG ∆ 4096R/D278 F9C1 5E54 61AA 3C1E 2FCD 13EC 43EE B9AC 8C43


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

Bug#729203: Reintroducing FFmpeg to Debian

[Jose Luis Rivas]

On 28/07/14, 01:20am, Andreas Cadhalpun wrote:
 Hi all,
 
 some of you may have noticed a weird ffmpeg package in the NEW queue[1].
 Let me explain:
 
 In 2011 Libav[2] was forked from FFmpeg[3]. It was a time of great
 uncertainty, the fork happened with much drama that didn't help making a
 technical cut, and at that peculiar time Debian switched to Libav.
 
Hi Andreas and everyone,

FWIW, my experience with this is that I had to make my own FFmpeg
package a while ago [0] because I needed it for a project I was working
on at the moment [1].

[0] https://github.com/ghostbar/FFmpeg.deb
[1] https://github.com/ghostbar/RTSP-Streaming.js

The reason for having to package my own FFmpeg is the current libav
which is taking the space of ffmpeg seemed to conflict with every other
ffmpeg package out there, including marillat's and for my project I
actually needed ffmpeg, not libav since it didn't had the functionality.
(More specifically: the ability to take still images from an rtsp
stream).

Not having FFmpeg available in the debian repositories is a nuissance,
and certainly having libav instead which seems to be a fork yet not
having the full FFmpeg functionality and using the same package name is
worst. I didn't figured this out at first because the binary said
`ffmpeg`. Of course, I'm talking about [2] since now that seems to not
be an issue yet remains the lack of functionality.

[2] https://packages.debian.org/wheezy/ffmpeg

If the issue is that this would mean having to fix security bugs twice
then it would be reasonable to stop shipping libav and instead ship
ffmpeg, since has more functionality and AFAICS from their repos bunch 
of active bug-fixing.

I honestly do not understand why ffmpeg is not in the repos nor why
there seems to be an active movement to block it.

Kind regards.
-- 
Jose Luis Rivas · ghostbar http://ghostbar.co
The Debian Project · http://www.debian.org
GPG · D278 F9C1 5E54 61AA 3C1E  2FCD 13EC 43EE B9AC 8C43


signature.asc
Description: Digital signature

Bug#748610: ITP: node-lodash -- node-lodash

[Jose Luis Rivas]

On 18/05/14, 10:39pm, Matthew Pideil wrote:
 Package: wnpp
 Severity: wishlist
 Owner: Matthew Pideil matthewp_deb...@teledetection.fr
 
 * Package name: node-lodash
   Version : 2.4.1
   Upstream Author : John-David Dalton john.david.dal...@gmail.com
 * URL : http://lodash.com/
 * License : expat
   Programming Lang: js
   Description : Lo-dash is a Node.js utility library
 
 Lo-dash is a Node.js utility library delivering consistency, customization, 
 performance,  extras.
 
 Sponsored by the pkg-javascript-team

Hello Matthew,

Actually lodash works on the browser too.

Why node-lodash? Why not liblodash-js?

-- 
Jose Luis Rivas | ghostbar
The Debian Project → http://www.debian.org
GPG 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118


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

Bug#688816: crash: corrupted double-linked list

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

tag 688816 upstream confirmed
forwarded 688816 https://github.com/rakshasa/rtorrent/issues/180
thanks

El 22/04/14, 06:57am, Damyan Ivanov escribió:
 Package: rtorrent
 Version: 0.9.2-1
 Followup-For: Bug #688816
 
 I have another bit of information about the crash.
 
 It appears to be related to the network interface going down. The host that 
 runs rtorrent uses DHCP to get its IP. When it fails to renew its IP address 
 lease, rtorrent seems to crash some 5-15 minutes after the network interface 
 is 
 deconfigured.
 
 This sounds related to https://bugs.debian.org/721995 -- rtorrent segfaults 
 when IP address changes after a sleep.

Hello Damyan, yes, there are lot of issues with freezes on rtorrent 0.9.x, 
including the latest from the master branch.

Already got forwarded to upstream and is aware of this.

Kind regards.

- -- 
Jose Luis Rivas -- GPG: 0xCACAB118
http://www.joseluisrivas.net/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlNcZ1QACgkQOKCtW8rKsRj5vwCeIpUKIG/pTi7irclBvh2ZAEUU
IDQAn3cSk3DFK2r781n+RGuA6HjLhUNc
=UBpm
-END PGP SIGNATURE-


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

Bug#745792: [PATCH] Fixing FTBFS on i386 and kfreebsd-i386

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160

Package: encfs
Version: 1.7.4-3
Control: tag -1 patch

Hi,

Here's a patch with a workaround for the output of `DEB_HOST_GNU_TYPE`
that's making encfs FTBFS on `linux-i386` and `kfreebsd-i386` since
1.7.4-3.

The output is `i486-linux-gnu` which do not match with
`/usr/lib/i386-linux-gnu` that `--with-libboost-dir` expects during
the `./configure`.

Kind regards.
- -- 
Jose Luis Rivas - @ghostbar
The Debian Project
GPG: 0xCACAB118
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEAREDAAYFAlNZ8jwACgkQOKCtW8rKsRhaLwCfeCxqA9B/diJFiVvh7jYOtcaZ
sCwAoJnhxefjTe77bNCPtuK+LpJ7lBbJ
=1W7V
-END PGP SIGNATURE-
From: Jose Luis Rivas ghost...@debian.org
Date: Thu, 24 Apr 2014 22:06:21 -0700
Subject: [PATCH] Using MOD_ARCH instead of DEB_HOST_GNU_TYPE

DEB_HOST_GNU_TYPE on i386 architectures shows `i486-linux-gnu` or
`i486-kfreebsd-gnu` while configure is expecting `i386-linux-gnu` or
`i486-kfreebsd-gnu` which makes it break when loading the Boost library
during the `./configure` with `--with-boost-libdir`. Using MOD_ARCH
catches this input checking if DEB_HOST_GNU_CPU is `i486` and converting
it then to `i386` while bypassing the other types.
---
 debian/rules | 10 --
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/debian/rules b/debian/rules
index 3255b55..bf6c939 100755
--- a/debian/rules
+++ b/debian/rules
@@ -24,6 +24,12 @@ else
CFLAGS += -O2
 endif
 
+ifeq ($(DEB_HOST_GNU_CPU),i486)
+   MOD_ARCH = i386
+else
+   MOD_ARCH = $(DEB_HOST_GNU_CPU)
+endif
+
 export CFLAGS
 export LDFLAGS
 
@@ -31,7 +37,7 @@ config.status: configure
dh_testdir
# Add here commands to configure the package.
#-autoreconf -fi
-   ./configure $(CONFARG) || ./configure $(CONFARG) 
--with-boost-libdir=/usr/lib/$(DEB_HOST_GNU_TYPE)
+   ./configure $(CONFARG) || ./configure $(CONFARG) 
--with-boost-libdir=/usr/lib/$(MOD_ARCH)-$(DEB_HOST_GNU_SYSTEM)
touch config.status
 
 build: build-stamp
@@ -49,7 +55,7 @@ clean:
dh_testdir
dh_testroot
rm -f build-stamp 
-   ./configure $(CONFARG) || ./configure $(CONFARG) 
--with-boost-libdir=/usr/lib/$(DEB_HOST_GNU_TYPE)
+   ./configure $(CONFARG) || ./configure $(CONFARG) 
--with-boost-libdir=/usr/lib/$(MOD_ARCH)-$(DEB_HOST_GNU_SYSTEM)
$(MAKE) distclean || true
-rm -f config.log
 #ifneq $(wildcard /usr/share/misc/config.sub) 
-- 
2.0.0.rc0

Bug#686699: powertop crashes if it's started with --calibrate

[Jose Luis Rivas]

I know gustavo, thanks for reporting. This is fixed in newer versions
uploaded on unstable
On Nov 27, 2013 10:18 AM, Gustavo Nascimento gdiasnascime...@gmail.com
wrote:

 Package: powertop
 Version: 2.0-0.3
 Followup-For: Bug #686699

 Dear Maintainer,
 My Debian 7 Linux use to much batery than Windows

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



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

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

 Versions of packages powertop depends on:
 ii  libc6 2.13-38
 ii  libgcc1   1:4.7.2-5
 ii  libncursesw5  5.9-10
 ii  libnl-3-200   3.2.7-4
 ii  libnl-genl-3-200  3.2.7-4
 ii  libpci3   1:3.1.9-6
 ii  libstdc++64.7.2-5
 ii  libtinfo5 5.9-10
 ii  zlib1g1:1.2.7.dfsg-13

 powertop recommends no packages.

 Versions of packages powertop suggests:
 pn  cpufrequtils   none
 ii  laptop-mode-tools  1.61-2

 -- no debconf information

Bug#727786: follow-up for: removal of libc6-amd64 makes system unusable

[Jose Luis Rivas]

On 10/26/2013 03:16 PM, Paul Gevers wrote:
 Seems this bug was indeed already reported: 699206 and 707185. However,
 it is not clear to me how I can get my system working again. Obviously,
 I can not remove or create symlinks to the right location as ln and
 friends don't work anymore (not to mention that sudo and getty don't help).
 
 Seems like I need to create a rescue USB drive without the possibility
 to copy files around Hope I can do this. I'll leave my laptop on
 tonight, if anybody has a great idea, feel free to share.
 
 Paul
 
 

Paul, just like recovering a system. Boot from a USB drive live-image
and make a chroot in the disk. Then you can start making the symlinks

-- 
Jose Luis Rivas
http://joseluisrivas.net/


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

Bug#721995: rtorrent segfaults when IP address changes after a sleep

[Jose Luis Rivas]

On Fri Sep  6 11:39:01 2013, Alexander Prokoshev wrote:
 Package: rtorrent
 Version: 0.9.2-1
 Severity: normal

 Dear Maintainer,
 I have a repeating situation when rtorrent being started in screen session
 segfaults after the laptop wakes up from sleep.
 Steps to reproduce:
 1) Start screen
 2) Start rtorrent in screen session, start downloading a torrent.
 3) Detach from the screen session
 4) Suspend the laptop.
 5) Move the laptop to another network with another address space
(for example, if it was connected to a network 192.168.0.0/24,
 move it to a network 192.168.1.0/24).
 6) Wake up the laptop.
 7) Attache the screen session.
 8) See the rtorrent segfaulted.

This is a situation isolated for `screen` or it happens even without 
`screen`?

--
Jose Luis Rivas
http://joseluisrivas.net/


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

Bug#695890: powertop: html output should use libjs-jquery instead of http://ajax.googleapis.com/

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160

On 9/5/13 11:05 AM, Daniel Kahn Gillmor wrote:
 On 09/04/2013 09:43 PM, Jose Luis Rivas wrote:
 Because it's not a requirement to see `powertop.html`. If the
 file is not found then it's not giving errors which put `jquery`
 in the `suggests` field. Less people is installing suggestions
 than have internet while loading and HTML.
 
 If it's not a requirement to see it, then all the more reason to
 avoid interacting with a third-party server for a superfluity.
 Users with no (or intermittent) 'net connections can at least make
 the choice to install libjs-jquery when they are installing the
 machine, as can users *with* robust 'net access.

Making something look ugly, removing usability and making it hard to
get good usability just because you consider it a superfluity is not
something I'm going to do.

I know this is a common path to decisions in free-software, but is a
path I'm not willing to take.

 
 Won't do that. In the package-management paradigm of Operating
 Systems there's no sane way to keep up with how JavaScript
 libraries work.
 
 Sorry, but there's nothing magical about javascript that makes js 
 libraries somehow immune to the various issues that other
 libraries have.

It's very different. So different I actually haven't met the first
person that uses the JS libraries packaged in Debian for big
production systems.

  It does take work to declare and maintain a stable API while
 patching security holes as they are discovered.  And it takes work
 on behalf of the user of a library to choose and depend on a stable
 version of the API.

The paradigm is clearly different in JavaScript.

  Hard-coding a particular version of a library (e.g. by
 embedding it) is the equivalent of static linking, which we agree
 is a bad idea in other applications.

This is a comparison of apples and pears. We are talking about
JavaScript, a scripting language.

 
 Only in this case, we're talking about statically linking to an 
 internet resource that is delivered without any cryptographic
 guarantees of integrity.

So, if it's delivered using https is good enough for you? Or the
paranoic-argument will be transferred to something like but Google is
a private third-party in which I don't trust?

 
 I do development on JavaScript primarily at work, and I can't
 use packaged js-libs because of this, so I refuse to suggest
 people to waste their time. To handle JavaScript libraries
 there's already two sane-ways: use either NPM or Bower. Most of
 this is transparent to the user unless is using a local file
 (which is the case in this report) and when using a local-file
 the suggested way is using a public CDN (which is what is being
 done).
 
 afaict, neither NPM nor Bower does cryptographic authentication of
 the code they fetch from the 'net, and neither of them appears to
 be committed to supporting a stable API while also patching
 security fixes.
 
 We've managed to do all of the above with most other libraries
 within debian for years now.  Why should we ignore these same
 code-management issues for any package just because it's
 javascript?

And anyway, again, people is not using Debian's packages in production
for JavaScript development. Doesn't that tell you something?

 
 That's how it works, the primarily exploits from JavaScript are 
 reading cookies which are not accessible if you are using
 file://. This is served from a public repository widely used, and
 the use of jQuery is limited to show and hide elements;
 
 If the legitimate use of jQuery is only for showing and hiding
 elements, maybe the best thing is just to patch to avoid jquery
 entirely and use native, cross-platform DOM.  Even if you think
 jQuery is the best way to do this, i strongly doubt that the
 jQuery API for showing and hiding elements will change at this
 point, so the concern about what happens if debian moves
 libjs-jquery from 1.7 to 1.10 seems moot.

I think this is actually a good solution. Sadly, I don't have the time
to do it. If you make a patch for it I will implement it and send it
upstream.

 
 not only that, there's no input of data in it. So, what's the
 security risk?
 
 If the code is fetched over the network, then whoever is serving
 the code (including any other machine on your LAN, if they decide
 to spoof traffic) can inject arbitrary code in the .js file.  There
 are lots of other exploits to be had from arbitrary javascript
 besides reading cookies.

Something easily fixable by just using the https version of it.
 
 What other security risks are there? well, anything that your
 browser is vulnerable to; e.g. flash objects, webGL craziness,
 hooks into audio or video elements to exploit your installed
 codecs, etc;

IF there's injection of code, which is not doable with https.

 the server
 deploying that .js file could use it to display advertisements,

Doubt they will. If that were the case shall we change the CDN, but
it's not. (And if this were the case

Bug#695890: powertop: html output should use libjs-jquery instead of http://ajax.googleapis.com/

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 9/3/13 2:04 PM, Daniel Kahn Gillmor wrote:
 i'm sorry to hear you feel this way.  I'm not asking due to
 paranoia -- as i mentioned in the original bug report, there are at
 least three cases that could cause people to want to do this:
 concerns about google, concerns about cleartext code injection by
 someone who controls the network (e.g. in a public wifi zone), and
 concerns about machines that have no internet connection at all.
 You may think that the first two categories are paranoia (though
 others with different network habits or adversary models than you
 may disagree), but the last category is a basic operation
 requirement for some users.   Why not make it friendly for them?

Because it's not a requirement to see `powertop.html`. If the file is
not found then it's not giving errors which put `jquery` in the
`suggests` field. Less people is installing suggestions than have
internet while loading and HTML.

 
 Not only that, I don't like how people believes JavaScript
 libraries are maintained as other languages libraries. Right now
 in unstable is 1.7.2 which isthe compatible with current
 powertop, but as soon as gets updated with 1.10.x it will break.
 That will create more bugs, and I wont create bugs for paranoia
 which will lead to nothing.
 
 If API version compatibility is a problem, and libjquery-js is
 breaking compatibility in ways that it needs to avoid, please
 submit a bug report asking for library-style packaging of core
 javascript libraries (e.g. libjs-jquery-1.7, if 1.7 is where the
 stable API is maintained).  If a given version of jquery API  is
 required for viewing the output, we should be explicit about that.

Won't do that. In the package-management paradigm of Operating Systems
there's no sane way to keep up with how JavaScript libraries work.
Sorry but that's a no-no. More people is needed in other fields of
Debian than maintaining highly changing JavaScript libraries.

I do development on JavaScript primarily at work, and I can't use
packaged js-libs because of this, so I refuse to suggest people to
waste their time. To handle JavaScript libraries there's already two
sane-ways: use either NPM or Bower. Most of this is transparent to the
user unless is using a local file (which is the case in this report)
and when using a local-file the suggested way is using a public CDN
(which is what is being done).

 
 You can't access to local fs via JavaScript on the browser, and
 the exploit can be done in the same domain. You will read it from
 file:/// so nothing will happen.
 
 I may be misunderstanding what you're saying here, but it sounds to
 me like you're suggesting that there is no way for an attacker who
 can inject arbitrary javascript into a page loaded via a file:///
 URL can do any harm.  Even if this is true in the abstract (i'm not
 convinced it is, given that there are a number of possible attacks
 other than reading from the local filesystem), and if all browsers
 implemented their javascript stacks with the appropriate
 sandboxing, this wouldn't resolve the problem for machines without
 full internet access.

That's how it works, the primarily exploits from JavaScript are
reading cookies which are not accessible if you are using file://.
This is served from a public repository widely used, and the use of
jQuery is limited to show and hide elements; not only that, there's no
input of data in it. So, what's the security risk?

About people without internet, already said my argument in the first
paragraph.
 
 Anyway, it is of course your call on what to do; but i think it's
 a shame that (a) all of the code involved is free software, already
 in debian, yet (b) we're relying on cleartext third-party
 transmissions for this functionality.

And is serving free-software, there's no ties on licensing nor liberty
using a CDN; just isn't bloating the software which is something some
people tend to. My priorities is making a software that will work if
you have internet but don't have libjquery installed from dpkg which
is a bigger use-case than people who does not have internet AND has
libjquery installed from dpkg.

I can see the argument of but that's the Debian-way, but for this
case is not the right way to do it.


Thanks for your feedback Daniel,
Kind Regards.
- -- 
Jose Luis Rivas
http://joseluisrivas.net/
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJSJ+GlAAoJEBPsQ+65rIxD4qgQAIYdWQQH1VOo2PGBodPVpQFf
9Gt5UEqu6BJQLB7N49+MgGPwJu1o0hQRnohKqhkQGIlQTIKnfMneRtUOTqa6Zlj1
kuxgNZbe7BfbLpZu7e6qFTRefNg4xqxEVNRXBLOpXXdkWNtcKeDQRZR+UWu1p39T
1uhWbCVKFb2dZHyaGjo4TopmhdcxgasbQHi7qkfPxqky9ccTgLokbACI2kvuK6dy
Xq5waKUqGorKjiUe1XD8xnNGBBtbpsc1TwEyPJxcwpLaIbNs4GAf96C5f2icoy5i
yecAzQ/Sivt8PlZrzFeU243vfPvOxzoJETsApcygEbl7MS1OYrE9yKCwUxJCJaFl
zM6rS4smpX1c1aJViqO/Ia3zzdCtGa0qEH7ruNP2O6VO94JBVYl63f5MnEB0NHty
NrH96yzup76yoxGdOVX1FMm

Bug#695890: powertop: html output should use libjs-jquery instead of http://ajax.googleapis.com/

[Jose Luis Rivas]

tags 695890 wontfix
severity 695890 wishlist
quit

Sorry Daniel, won't do this.

Can't see a real reason besides paranoia. Specially seeing a report from
your power usage.

Not only that, I don't like how people believes JavaScript libraries are
maintained as other languages libraries. Right now in unstable is 1.7.2
which isthe compatible with current powertop, but as soon as gets
updated with 1.10.x it will break. That will create more bugs, and I
wont create bugs for paranoia which will lead to nothing.

You can't access to local fs via JavaScript on the browser, and the
exploit can be done in the same domain. You will read it from file:///
so nothing will happen.

Kind regards.
-- 
Jose Luis Rivas
http://joseluisrivas.net/


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

Bug#688816: crash: corrupted double-linked list

[Jose Luis Rivas]

Is this happening yet?

Full report at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688816
-- 
Jose Luis Rivas
The Debian Project -- http://debian.org


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

Bug#698554: Crash when parts of a file unreadable

[Jose Luis Rivas]

Is this happening again?

Full report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698554
-- 
Jose Luis Rivas
The Debian Project -- http://debian.org


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

Bug#572485: xscreensaver: should not hardcode screenhacks list

[Jose Luis Rivas]

On 12/06/2011 09:26 PM, Martín Ferrari wrote:
[...]
 José, do you think it is possible to implement Jamie's suggestion?
 There aren't many xscreensaver hacks in the archive, but they will
 benefit from this, and it would make a lot easier to package new
 hacks...
 

Sure Martín, just send me a patch. We maintain everything on
git.debian.org/git/collab-maint/xscreensaver.git

Send it on email or just let me know from where make pull.

Cheers!
-- 
Jose Luis Rivas - GPG: 0x7C4DF50D / 0xCACAB118
The Debian Project Developer -- http://ghostbar.ath.cx
Barquisimeto, Venezuela



signature.asc
Description: OpenPGP digital signature

Bug#647110: xscreensaver: Please Build-Depends on libjpeg-dev, not libjpeg62-dev

[Jose Luis Rivas]

On 10/30/2011 12:45 PM, Tormod Volden wrote:
 tags 647110 pending
 thanks
 
 Hi Bill,
 Thanks for the notification. We will fix this in the next upload.
 

Already uploaded the changes made by Tormod to ftp-master. It will soon
hit the repos.

Thanks for the notification Bill,

Regards.
-- 
Jose Luis Rivas - GPG: 0x7C4DF50D 0xCACAB118
Debian Project Developer -- http://ghostbar.ath.cx
Barquisimeto, Venezuela



signature.asc
Description: OpenPGP digital signature

Bug#628917: xscreensaver exits

[Jose Luis Rivas]

Hi,

So, you upgraded to 5.14 and?

It keeps giving this? It changed? What?

-- 
Jose Luis Rivas - GPG (old/new): 0xCACAB118 / 0x7C4DF50D
San Cristóbal, Venezuela - http://ghostbar.ath.cx/
Debian Project Developer - http://debian.org/



signature.asc
Description: OpenPGP digital signature

Bug#349000: xscreensaver: New Login via gdmflexiserver impossible when 2 or more sessions active

[Jose Luis Rivas]

So, what needs to be done here with this bug?

Check if gdm still support this option and/or find the way to make xss
open to multiple logins?

Regards,
-- 
Jose Luis Rivas - GPG (old/new): 0xCACAB118 / 0x7C4DF50D
San Cristóbal, Venezuela - http://ghostbar.ath.cx/
Debian Project Developer - http://debian.org/



signature.asc
Description: OpenPGP digital signature

Bug#632420: xscreensaver: destroys GDM / X monitors setting

[Jose Luis Rivas]

This is a video-driver bug. If you think it's not please feel free to
re-open and gives us some log so we can trace the source of the issue.
-- 
Jose Luis Rivas - GPG: 0x7C4DF50D
San Cristóbal, Venezuela - http://www.joseluisrivas.net/



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

Bug#517797: xscreensaver: Does not correctly handle differing horizontal and vertical DPI

[Jose Luis Rivas]

Is this still longer true?

Did you found a way to configure your X server correctly?

No one has complained about this and there's a lot of people with
different video-configurations working correctly with xscreensaver.

Regards.
-- 
Jose Luis Rivas - GPG (old/new): 0xCACAB118 / 0x7C4DF50D
San Cristóbal, Venezuela - http://ghostbar.ath.cx/
Debian Project Developer - http://debian.org/



signature.asc
Description: OpenPGP digital signature

Bug#538687: xscreensaver-data: ripples throws trap stack segment error

[Jose Luis Rivas]

Are you still having this issue? I can't reproduce this.
-- 
Jose Luis Rivas - GPG (old/new): 0xCACAB118 / 0x7C4DF50D
San Cristóbal, Venezuela - http://ghostbar.ath.cx/
Debian Project Developer - http://debian.org/



signature.asc
Description: OpenPGP digital signature

Bug#538811: xscreensaver(-demo) does not set cursor

[Jose Luis Rivas]

I can't reproduce this behavior, do you have this kind of issue any longer?
-- 
Jose Luis Rivas - GPG (old/new): 0xCACAB118 / 0x7C4DF50D
San Cristóbal, Venezuela - http://ghostbar.ath.cx/
Debian Project Developer - http://debian.org/



signature.asc
Description: OpenPGP digital signature

Bug#604686: can't return back into my desktop from xscreensaver

[Jose Luis Rivas]

Hi Simon  Kenyon,

Are you guys still able to reproduce this bug? I can't.

To refresh your memory, is this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604686

Regards,
-- 
Jose Luis Rivas - GPG (old/new): 0xCACAB118 / 0x7C4DF50D
San Cristóbal, Venezuela - http://ghostbar.ath.cx/
Debian Project Developer - http://debian.org/



signature.asc
Description: OpenPGP digital signature

Bug#617914: [PING] xscreensaver: fails detecting screen layout with new X server

[Jose Luis Rivas]

Is this still happening to you?
-- 
Jose Luis Rivas - GPG: 0x7C4DF50D
San Cristóbal, Venezuela - http://www.joseluisrivas.net/



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

Bug#615070: xscreensaver and unclutter lock the station

[Jose Luis Rivas]

So, while using unclutter is that this happens?
-- 
Jose Luis Rivas - GPG (old/new): 0xCACAB118 / 0x7C4DF50D
San Cristóbal, Venezuela - http://ghostbar.ath.cx/
Debian Project Developer - http://debian.org/



signature.asc
Description: OpenPGP digital signature

Bug#632162: O: mybashburn -- Burn data and create songs with interactive dialog box

[Jose Luis Rivas]

X-Debbugs-CC: debian-de...@lists.debian.org
package: wnpp
severity: normal

This package has been in very bad shape since long time ago, upstream
is not responding since 2008 and there have been no changes since that
time.

Maybe this should be removed, but there could be someone who would
like to take over upstream and/or debian maintenance.

Regards.
-- 
Jose Luis Rivas. San Cristóbal, Venezuela.
Debian Project Developer
GPG 0xCACAB118 (old) 0x7C4DF50D (new)
http://ghostbar.ath.cx/about



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

Bug#620056: This bug is not grave

[Jose Luis Rivas]

620056 severity wishlist
quit

This bug is not grave, if you don't like it then install 1.13, but
please don't make a RC bug just because you don't like how the app works.

1.99 is on the way, fixing some crashes. The world changes, powertop as
well.
-- 
Jose Luis Rivas - GPG (old/new): 0xCACAB118 / 0x7C4DF50D
San Cristóbal, Venezuela - http://ghostbar.ath.cx/
Debian Project Developer - http://debian.org/



signature.asc
Description: OpenPGP digital signature

Bug#609942: Please add Venezuela's SUSCERTE CA to ca-certificates

[Jose Luis Rivas]

Hi hereby support the request to add SUSCERTE CA to the ca-certificates
package.

Regards,
-- 
Jose Luis Rivas - GPG (old/new): 0xCACAB118 / 0x7C4DF50D
San Cristóbal, Venezuela - http://ghostbar.ath.cx/
Debian Project Developer - http://debian.org/



signature.asc
Description: OpenPGP digital signature

Bug#607595: More information about this bug

[Jose Luis Rivas]

On 12/20/2010 09:00 AM, Juhapekka Tolvanen wrote:
 
 On Mon, 20 Dec 2010, +12:20:22 EET (UTC +0200),
 Jamie Zawinski j...@jwz.org pressed some keys:
 
 I really was running that screenhack called biof.
 
 I've never heard of this, what is it?
 
 Here is text from its settings-dialog:
 
  Clip here 
 This is an attempt to recreate some of the work of William Latham.
 Take a look at the program 'organic art' at this site
 (http://www.artworks.co.uk).
 
 Written by Ronald Hordijk hk at dgmr.nl. Ported to Linux by Tugrul
 Galatali - http://rss-glx.sourceforge.net/.
  Clip here 
 
 That screenhack obviously belongs to Debian-package called rss-glx .
 

Please, separate hacks from xscreensaver-gl of rss-glx. If you found
bugs on XScreenSaver Debian-distribution then please fill them here. If
not please fill a bug against rss-glx.

Regards.
-- 
Jose Luis Rivas - GPG (old/new): 0xCACAB118 / 0x7C4DF50D
San Cristóbal, Venezuela - http://ghostbar.ath.cx/
Debian Project Developer - http://debian.org/



signature.asc
Description: OpenPGP digital signature

Bug#596944: please reconsider xscreensaver *-extra package split

[Jose Luis Rivas]

Tormod from the checks I made I believe we could just drop the split.

-Original Message-
From: Tormod Volden debian.tor...@gmail.com
Date: Fri, 17 Sep 2010 14:27:49 
To: Jamie Zawinskij...@jwz.org; 596...@bugs.debian.org
Reply-To: Tormod Volden debian.tor...@gmail.com, 596...@bugs.debian.org
Subject: Bug#596944: please reconsider xscreensaver *-extra package split

On Wed, Sep 15, 2010 at 11:25 AM, Jamie Zawinski wrote:
 In summary:

 The Debian package of xscreensaver currently excludes many savers from the 
 default install, on the basis of them using too much CPU.  This is no longer 
 the case.  As those savers no longer use too much CPU, the justification for 
 excluding them from the default install no longer exists, and they should be 
 installed by default.

Short response: It is still the case on common hardware...

 Longer version:


 I believe these are the tests they ran, years ago: 
 https://wiki.ubuntu.com/X/Screensavers

Yes, but I have occasionally been running more tests since then, so I
know it is still a problem. I need to update that page though.

 It has always been my goal with xscreensaver that *no* screen saver should 
 use significant CPU when running.  Since he ran his tests, I have fixed those 
 savers that were using too much CPU (mostly by adjusting their default 
 settings to be gentler).

 It is my belief that currently, none of the screen savers included with 
 xscreensaver use significant CPU when running with their default options.

Note that the high CPU usage is often (always) due to lack of
functionality in the graphic card drivers, and not to bugs in
xscreensaver. We rely on our own testing on different hardware and of
reported bugs about high CPU usage. This has not been very systematic
but as often in distribution packaging, a compromise between time
invested and getting most things to work for most people.

Since we are providing a Linux distribution, the end user experience
is what counts. We can not play the blame game (notourbug) and tell
people to fix their graphics drivers. And yes, I try to fix graphics
drivers also, at least by doing some xorg related QA work and smaller
patches.

 Therefore, it is my belief that the -extra packages are unnecessary, and 
 their contents should be folded in to the -data and -gl packages, reducing 
 the number of xscreensaver packages from 5 to 3. I would like this to happen 
 so that the default is to install the *complete* xscreensaver package instead 
 of just an arbitrary subset of it.  Since most users will just take the 
 defaults, they won't even know that the part 2 savers exist, and many of 
 them are pretty cool!  And the justification for excluding them no longer 
 exists.


Yes, the package complexity is not nice for anyone, and it is sad when
some users don't know they can try out all hacks by installing the
extra packages. I would even have liked to see the package count down
to 2 since everybody has GL libraries installed, at least if some
detection of HW acceleration could be done run-time.

However we haven't come up with a better mechanism for us or the
consumers (whether users, system administrators or downstream
packagers) to select which hacks to run by default. Most consumers of
the hacks do not even run the xscreensaver engine and its preferences
dialog. The treatment of the xscreensaver package certainly is made
more complicated by the fact that parts of it are used by other
screensaver engines. Which you probably have mixed feelings about :)

 Over the past 3 years, I have repeatedly asked Jose to re-run the tests he 
 ran by which he decided which savers to push into the extras package, and 
 let me know if he still sees any savers using excessive CPU (because I don't 
 believe there are any, but if there are, I would like to fix that bug.)

 I'm sorry to say that he has never responded.

 In fact, I haven't gotten any mail from him at all since September 2008, so 
 even though he is still listed as the Debian maintainer of xscreensaver, I'm 
 not sure he is still paying attention.

Jamie, I have the impression you are reading some of the xscreensaver
bug mail, so you have certainly seen that Jose is actively maintaining
it together with me. So please no theater. On the other hand it is
better that you route your requests through the bug tracker like you
are doing this time, or to the package maintainer list (which I fail
to remember the address of here and now) rather than sending him
private e-mail. None of us are working full time on this, and in busy
times some things slip through the cracks.


 So -- if there is anyone reading this who considers themselves to be in 
 charge of the Debian xscreensaver package, please reconsider the split 
 between the default and extras packages, because I believe it to be based 
 on old data and on assumptions which are no longer true.


We are continuously reconsidering the split (ever since before we made
it), but we would need an alternative solution 

Bug#596944: please reconsider xscreensaver *-extra package split

[Jose Luis Rivas]

Hello Jamie, I'm going to check these tonight at home. ;-)

I don't like neither the extra split but too much users were complaining.

Regards
-Original Message-
From: Jamie Zawinski j...@jwz.org
Date: Wed, 15 Sep 2010 02:25:52 
To: sub...@bugs.debian.org
Reply-To: Jamie Zawinski j...@jwz.org, 596...@bugs.debian.org
Subject: Bug#596944: please reconsider xscreensaver *-extra package split

Package: xscreensaver
Version: 5.05-3


In summary: 

The Debian package of xscreensaver currently excludes many savers from the 
default install, on the basis of them using too much CPU.  This is no longer 
the case.  As those savers no longer use too much CPU, the justification for 
excluding them from the default install no longer exists, and they should be 
installed by default.


Longer version:

Currently, Debian divides xscreensaver into five packages:

xscreensaver (base)
xscreensaver-data (non-OpenGL screen savers, part 1)
xscreensaver-data-extra (non-OpenGL screen savers, part 2)
xscreensaver-gl (OpenGL screen savers, part 1)
xscreensaver-gl-extra (OpenGL screen savers, part 2)

The choice of which savers to put in the part 2 packages instead of the part 
1 packages was made by Jose Luis Rivas Contreras ghostba...@gmail.com and 
Tormod Volden debian.tor...@gmail.com back in 2007 or 2008 by running each of 
the screen savers and timing their CPU usage, and putting those with high CPU 
usage in the part 2 packages, not installed by default.

I believe these are the tests they ran, years ago: 
https://wiki.ubuntu.com/X/Screensavers

It has always been my goal with xscreensaver that *no* screen saver should use 
significant CPU when running.  Since he ran his tests, I have fixed those 
savers that were using too much CPU (mostly by adjusting their default settings 
to be gentler).

It is my belief that currently, none of the screen savers included with 
xscreensaver use significant CPU when running with their default options. 

Therefore, it is my belief that the -extra packages are unnecessary, and their 
contents should be folded in to the -data and -gl packages, reducing the number 
of xscreensaver packages from 5 to 3. I would like this to happen so that the 
default is to install the *complete* xscreensaver package instead of just an 
arbitrary subset of it.  Since most users will just take the defaults, they 
won't even know that the part 2 savers exist, and many of them are pretty 
cool!  And the justification for excluding them no longer exists.

Over the past 3 years, I have repeatedly asked Jose to re-run the tests he ran 
by which he decided which savers to push into the extras package, and let me 
know if he still sees any savers using excessive CPU (because I don't believe 
there are any, but if there are, I would like to fix that bug.)  

I'm sorry to say that he has never responded.  

In fact, I haven't gotten any mail from him at all since September 2008, so 
even though he is still listed as the Debian maintainer of xscreensaver, I'm 
not sure he is still paying attention.

So -- if there is anyone reading this who considers themselves to be in charge 
of the Debian xscreensaver package, please reconsider the split between the 
default and extras packages, because I believe it to be based on old data 
and on assumptions which are no longer true.

Thanks...

Bug#593233: xscreensaver-data-extra: segfault in maze

[Jose Luis Rivas]

Hi Marc, thanks for your report; I'll be checking this as soon as I get home. 

Could you please tell me how to reproduce it? When segfaults? What kind of 
machine does you have? Graphic controller? How often does segfaults? Is your 
only screensaver or does you have it configured to cycle?

All this will help us to get into this bug and squash it :-)

Regards,
-Original Message-
From: Marc F. Clemente m...@mclemente.net
Date: Mon, 16 Aug 2010 08:37:48 
To: Debian Bug Tracking Systemsub...@bugs.debian.org
Reply-To: Marc F. Clemente m...@mclemente.net, 593...@bugs.debian.org
Subject: Bug#593233: xscreensaver-data-extra: segfault in maze

Package: xscreensaver-data-extra
Version: 5.11-1
Severity: normal


# dmesg | grep maze
[771455.651377] maze[21281]: segfault at 7f22693318d6 ip 004030c3 sp 
7fff35021490 error 4 in maze[40+16000]
[777213.609964] maze[21445]: segfault at 7f81ed037560 ip 004030c3 sp 
7fff12d79990 error 4 in maze[40+16000]
[965870.889105] maze[568]: segfault at 7f2e2d216554 ip 004030c3 sp 
7fff97830840 error 4 in maze[40+16000]

It doesn't always segfault.  I see it working sometimes.

Questions?  Please email me.

Thanks,

Marc


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

Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages xscreensaver-data-extra depends on:
ii  dictionaries-common  1.5.11  Common utilities for spelling dict
ii  libc62.11.2-2Embedded GNU C Library: Shared lib
ii  libglib2.0-0 2.24.1-1The GLib library of C routines
ii  libgtk2.0-0  2.20.1-1The GTK+ graphical user interface 
ii  libice6  2:1.0.6-1   X11 Inter-Client Exchange library
ii  libjpeg-progs8b-1Programs for manipulating JPEG fil
ii  libsm6   2:1.1.1-1   X11 Session Management library
ii  libx11-6 2:1.3.3-3   X11 client-side library
ii  libxext6 2:1.1.2-1   X11 miscellaneous extension librar
ii  libxmu6  2:1.0.5-1   X11 miscellaneous utility library
ii  libxpm4  1:3.5.8-1   X11 pixmap library
ii  libxt6   1:1.0.7-1   X11 toolkit intrinsics library
ii  netpbm   2:10.0-12.2 Graphics conversion tools between 
ii  xscreensaver-data5.11-1  data files to be shared among scre

xscreensaver-data-extra recommends no packages.

xscreensaver-data-extra suggests no packages.

-- no debconf information

Bug#591414: xscreensaver: error while running deprecated it says

[Jose Luis Rivas]

It's working OK; just a few warnings from Gtk library that doesn't affect how 
xscreensaver-demo works.

This is _not_ a bug.

Thanks
-Original Message-
From: yellow yellowprot...@gmail.com
Date: Mon, 02 Aug 2010 23:22:13 
To: Debian Bug Tracking Systemsub...@bugs.debian.org
Reply-To: yellow yellowprot...@gmail.com, 591...@bugs.debian.org
Subject: Bug#591414: xscreensaver: error while running deprecated it says

Package: xscreensaver
Version: 5.11-1
Severity: normal



$ xscreensaver-demo 
xscreensaver-demo: 23:21:05: Gtk-warning: GtkSpinButton: setting an adjustment 
with non-zero page size is deprecated
xscreensaver-demo: 23:21:05: Gtk-warning: GtkSpinButton: setting an adjustment 
with non-zero page size is deprecated
xscreensaver-demo: 23:21:05: Gtk-warning: GtkSpinButton: setting an adjustment 
with non-zero page size is deprecated
xscreensaver-demo: 23:21:05: Gtk-warning: GtkSpinButton: setting an adjustment 
with non-zero page size is deprecated
xscreensaver-demo: 23:21:05: Gtk-warning: GtkSpinButton: setting an adjustment 
with non-zero page size is deprecated
xscreensaver-demo: 23:21:05: Gtk-warning: GtkSpinButton: setting an adjustment 
with non-zero page size is deprecated
xscreensaver-demo: 23:21:05: Gtk-warning: GtkSpinButton: setting an adjustment 
with non-zero page size is deprecated


it seems that it is not working well. Stable was more stable
or at all

best regards



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

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

Versions of packages xscreensaver depends on:
ii  libatk1.0-0 1.30.0-1 The ATK accessibility toolkit
ii  libc6   2.11.2-2 Embedded GNU C Library: Shared lib
ii  libcairo2   1.8.10-4 The Cairo 2D vector graphics libra
ii  libfontconfig1  2.8.0-2.1generic font configuration library
ii  libfreetype62.3.11-1 FreeType 2 font engine, shared lib
ii  libglade2-0 1:2.6.4-1library to load .glade files at ru
ii  libglib2.0-02.24.1-1 The GLib library of C routines
ii  libgtk2.0-0 2.20.1-1 The GTK+ graphical user interface 
ii  libice6 2:1.0.6-1X11 Inter-Client Exchange library
ii  libpam0g1.1.1-3  Pluggable Authentication Modules l
ii  libpango1.0-0   1.28.1-1 Layout and rendering of internatio
ii  libsm6  2:1.1.1-1X11 Session Management library
ii  libx11-62:1.3.3-3X11 client-side library
ii  libxext62:1.1.1-3X11 miscellaneous extension librar
ii  libxinerama12:1.1-3  X11 Xinerama extension library
ii  libxml2 2.7.7.dfsg-4 GNOME XML library
ii  libxmu6 2:1.0.5-1X11 miscellaneous utility library
ii  libxpm4 1:3.5.8-1X11 pixmap library
ii  libxrandr2  2:1.3.0-3X11 RandR extension library
ii  libxrender1 1:0.9.5-2X Rendering Extension client libra
ii  libxt6  1:1.0.7-1X11 toolkit intrinsics library
ii  libxxf86vm1 1:1.1.0-2X11 XFree86 video mode extension l
ii  xscreensaver-data   5.11-1   data files to be shared among scre

Versions of packages xscreensaver recommends:
ii  libjpeg-progs  8b-1  Programs for manipulating JPEG fil
ii  miscfiles [wordlist]   1.4.2.dfsg.1-9Dictionaries and other interesting
ii  perl [perl5]   5.10.1-13 Larry Wall's Practical Extraction 
ii  xli1.17.0+20061110-3 command line tool for viewing imag

Versions of packages xscreensaver suggests:
ii  elinks [www-browser]0.12~pre5-2  advanced text-mode WWW browser
ii  fortune-mod [fortune]   1:1.99.1-4   provides fortune cookies on demand
ii  galeon [www-browser]2.0.7-2.1+b1 GNOME web browser for advanced use
ii  iceweasel [www-browser] 3.5.10-1 Web browser based on Firefox
ii  lynx-cur [www-browser]  2.8.8dev.4-2 Text-mode WWW Browser with NLS sup
pn  qcam | streamer none   (no description available)
pn  xdaliclock  none   (no description available)
pn  xfishtank   none   (no description available)
pn  xscreensaver-gl none   (no description available)

-- no debconf information

Bug#588288: README.Debian vs 'Obsolete conffile /etc/xdg/autostart/xscreensaver-daemon.desktop ... Saving as .bak'

[Jose Luis Rivas]

Thank you Daniel, you are right and we are going to fix this ASAP!

Thanks again for reporting this!
-Original Message-
From: Daniel Leidert daniel.leid...@wgdd.de
Date: Tue, 06 Jul 2010 23:49:32 
To: Debian Bug Tracking Systemsub...@bugs.debian.org
Reply-To: Daniel Leidert daniel.leid...@wgdd.de, 588...@bugs.debian.org
Subject: Bug#588288: README.Debian vs 'Obsolete conffile 
/etc/xdg/autostart/xscreensaver-daemon.desktop ... Saving as .bak'

Package: xscreensaver
Version: 5.11-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

The README.Debian file says, that one should copy the 
xscreensaver-daemon.desktop
to /etc/xdg/autostart to start the screen saver. I simply link to it. But during
updates this leads to

[..dpkg..]
Obsolete conffile /etc/xdg/autostart/xscreensaver-daemon.desktop has been 
modified by you.
Saving as /etc/xdg/autostart/xscreensaver-daemon.desktop.dpkg-bak ...
[..dpkg..]

So I have to renew the link with every update. I think, this is a  bug in your
preinst script or in RREADME.Debian.

Regards, Daniel


- -- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (850, 'unstable'), (700, 'testing'), (560, 'stable'), (110, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xscreensaver depends on:
ii  libatk1.0-0 1.30.0-1 The ATK accessibility toolkit
ii  libc6   2.11.2-2 Embedded GNU C Library: Shared lib
ii  libcairo2   1.8.10-4 The Cairo 2D vector graphics libra
ii  libfontconfig1  2.8.0-2.1generic font configuration library
ii  libfreetype62.3.11-1 FreeType 2 font engine, shared lib
ii  libglade2-0 1:2.6.4-1library to load .glade files at ru
ii  libglib2.0-02.24.1-1 The GLib library of C routines
ii  libgtk2.0-0 2.20.1-1 The GTK+ graphical user interface 
ii  libice6 2:1.0.6-1X11 Inter-Client Exchange library
ii  libpam0g1.1.1-3  Pluggable Authentication Modules l
ii  libpango1.0-0   1.28.1-1 Layout and rendering of internatio
ii  libsm6  2:1.1.1-1X11 Session Management library
ii  libx11-62:1.3.3-3X11 client-side library
ii  libxext62:1.1.1-3X11 miscellaneous extension librar
ii  libxinerama12:1.1-3  X11 Xinerama extension library
ii  libxml2 2.7.7.dfsg-4 GNOME XML library
ii  libxmu6 2:1.0.5-1X11 miscellaneous utility library
ii  libxpm4 1:3.5.8-1X11 pixmap library
ii  libxrandr2  2:1.3.0-3X11 RandR extension library
ii  libxrender1 1:0.9.5-2X Rendering Extension client libra
ii  libxt6  1:1.0.7-1X11 toolkit intrinsics library
ii  libxxf86vm1 1:1.1.0-2X11 XFree86 video mode extension l
ii  xscreensaver-data   5.11-1   data files to be shared among scre

Versions of packages xscreensaver recommends:
ii  libjpeg-progs   8b-1 Programs for manipulating JPEG fil
ii  perl [perl5]5.10.1-13Larry Wall's Practical Extraction 
ii  wamerican [wordlist]6-3  American English dictionary words 
ii  wngerman [wordlist] 20091006-4.1 New German orthography wordlist
pn  xli | xloadimagenone   (no description available)

Versions of packages xscreensaver suggests:
ii  epiphany-browser [www-brows 2.30.2-3 Intuitive GNOME web browser
pn  fortune none   (no description available)
ii  galeon [www-browser]2.0.7-2.1+b1 GNOME web browser for advanced use
ii  iceape-browser [www-browser 2.0.5-1  Iceape Navigator (Internet browser
ii  iceweasel [www-browser] 3.5.10-1 Web browser based on Firefox
ii  kazehakase [www-browser]0.5.8-4  GTK+-based web browser that allows
ii  konqueror [www-browser] 4:4.4.4-1KDE 4's advanced file manager, web
ii  links2 [www-browser]2.2-1+b2 Web browser running in both graphi
ii  lynx-cur [www-browser]  2.8.8dev.4-2 Text-mode WWW Browser with NLS sup
ii  netrik [www-browser]1.16.1-1 text mode WWW browser with vi like
ii  opera [www-browser] 10.60.6386   A fast and secure web browser and 
pn  qcam | streamer none   (no description available)
ii  w3m [www-browser]   0.5.2-6  WWW browsable pager with excellent
pn  xdaliclock  none   (no description available)
pn  xfishtank   none   (no description available)
ii  xscreensaver-gl 5.11-1   GL(Mesa) screen hacks for xscreens

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: 

Bug#519061: New solution

[Jose Luis Rivas]

Thanks Sebastian, I never had a way to reproduce this issue, it should be 
reassigned to whoever is gulty on this. If you could help us on this we would 
be vastly regreted :)
--Mensaje original--
De: Sebastian Weisgerber
Para:519...@bugs.debian.org
Responder a:Sebastian Weisgerber
Responder a:519...@bugs.debian.org
Asunto: Bug#519061: New solution
Enviado: 29 Jun, 2010 3:09 PM

It seems i got some weird Special chars in my password.
A friend of mine proposed to change my password to one with no special chars 
and everything is fine.
He also proposed that different keymaps are active under different 
circumstances.
I don't where to investigate further :(

I use en_US.UTF-8 systemwide.
Write me a mail if i should invesigate in a certain direction.

I repeat: this is no problem of xscreensaver.

Your's sincerely

Sebastian Weisgerber







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

Bug#519061: More info

[Jose Luis Rivas]

Hi Christophe,

Please, could you give me more info about how is built your system?
Which kind of notebook, which system, wich kernel?

Thanks

-- 
Jose Luis Rivas. San Cristóbal, Venezuela.
GPG 0xCACAB118 0x7C4DF50D
http://joseluisrivas.net/acerca - http://ghostbar.ath.cx/about



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

Bug#519061: xscreensaver: Won't unlock my screen at all due to apparent password difficulties.

[Jose Luis Rivas]

Hi,

At the moment I'm not @ home and doesn't have my notebook @ hand, only my PDA, 
tomorrow I'll be at home and try your way for reproducing the bug.

Thanks for your report! :-)
-Original Message-
From: Christophe TROESTLER christophe.troest...@umons.ac.be
Date: Sat, 15 May 2010 20:52:39 
To: 519...@bugs.debian.org
Subject: Bug#519061: xscreensaver: Won't unlock my screen at all due to 
apparent password difficulties.

Hi,

I have the same problem.  Adding the lines

@include common-password
@include common-session

at the end of /etc/pam.d/xscreensaver did not help.  In
/var/log/auth.log, I have the message :

May 15 20:43:14 poincare xscreensaver: pam_unix(xscreensaver:auth): 
authentication failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost=  
user=xxx
May 15 20:43:16 poincare xscreensaver[2125]: FAILED LOGIN 1 ON DISPLAY :0.0, 
FOR xxx

On my machine, an operation that usually triggers the bug is to lock
the screen by closing the lid (locking is activated through
kpowersave) and unplugging then plugging back the AC power.

A workaround is to switch to the console and then back to X.

Any help will be appreciated.

Bug#567738: xscreensaver-data-extra: GNOME menu continues to list screensavers after uninstallation

[Jose Luis Rivas]

Well Don, if /usr/lib/xscreensaver/xjack is there then there's a
problem with xscreensaver, if not I believe is an issue with xlock and
don't know which packages ships it. Please make dpkg -S xlock and
see which is and relocate this bug ticket.

On Sun, Jan 31, 2010 at 4:10 PM, Don Pellegrino d...@drexel.edu wrote:
 On Sat, Jan 30, 2010 at 10:08 PM, Jose Luis Rivas josel...@rivco.net wrote:
 I'm sorry Don, I cannot understand. xlock is not shipped by
 xscreensaver neither by xscreensaver-data-extra.

 What you mean?

 I apologize if I have submitted this bug to the wrong package.
 Perhaps it should have been filed against the xlockmore package?  I
 would appreciate your assistance with identifying the appropriate
 package for this bug report.

 The use case is that the GNOME Applications - Other menu includes the
 following items:

 Anemone
 Ant
 Ant3d
 Ant Truchet
 Apollonian
 Atlantis
 Atunnels
 Available
 Back Soon
 Ball
 Bat
 Bee
 Bee Truchet
 Biof
 Blank
 Blot
 Bomb
 Bouboule
 Bouboule3d
 Bounce
 Braid
 Brilliant!
 Bubble
 Bubble3d
 Bug
 Cage
 Clock
 Coral
 Crazy Boy
 Crazy Girl
 Crystal
 Daisy
 Dclock
 Decay
 Deco
 Deluxe
 Demon
 Dilemma
 Discrete
 Dragon
 Drift
 ...
 Xjack

 The commands associated with these launchers in the GNOME menu take
 the form of /usr/bin/xlock -remote -nice 19 -mode xjack  Performing
 a Debian Package Content Search for xjack finds the
 /usr/lib/xscreensaver/xjack file in the xscreensaver-data-extra
 package.  I have removed the xlockmore and xscreensaver-data-extra
 packages however these menu items persist.  I do not know which
 package establishes these GNOME menu items but presumably that would
 be the package against which this bug should be filed.  I think that
 these menu items should be removed when the packages they depend upon
 are removed however I don't know which package should be responsible
 for the removal scripts.




-- 
Jose Luis Rivas. San Cristóbal, Venezuela.
GPG 0xCACAB118 0x7C4DF50D
http://joseluisrivas.net/acerca - http://ghostbar.ath.cx/about



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

Bug#567738: xscreensaver-data-extra: GNOME menu continues to list screensavers after uninstallation

[Jose Luis Rivas]

I'm sorry Don, I cannot understand. xlock is not shipped by
xscreensaver neither by xscreensaver-data-extra.

What you mean?

On Sat, Jan 30, 2010 at 8:44 PM, Don Pellegrino d...@drexel.edu wrote:
 Package: xscreensaver-data-extra
 Severity: minor

 The GNOME Applications - Other menu continues to list menu entries
 for the xlock screensaver commands after the package has been removed.
  For example the menu item Bouboule exists for command
 /usr/bin/xlock -remote -nice 19 -nolock -mode bouboule +use3d.




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

 Kernel: Linux 2.6.32-trunk-686 (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/bash






-- 
Jose Luis Rivas. San Cristóbal, Venezuela.
GPG 0xCACAB118 0x7C4DF50D
http://joseluisrivas.net/acerca - http://ghostbar.ath.cx/about



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

Bug#566984: xscreensaver: screensaver only shows a black screen instead of the actual animation

[Jose Luis Rivas]

Check on xscreensaver-demo if you have blnak screen instead of any screensaver, 
please.
-Original Message-
From: Hugo A. M. Torres macabr...@gmail.com
Date: Tue, 26 Jan 2010 08:40:33 
To: Debian Bug Tracking Systemsub...@bugs.debian.org
Subject: Bug#566984: xscreensaver: screensaver only shows a black screen 
instead of the actual animation

Package: xscreensaver
Version: 5.10-6
Severity: grave
Justification: renders package unusable

I leave the pc unattended and when I come back I see a black screen instead of 
the screensaver. Porwermanager is set to never blank screen.


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

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

Versions of packages xscreensaver depends on:
ii  libatk1.0-0 1.28.0-1 The ATK accessibility toolkit
ii  libc6   2.10.2-2 GNU C Library: Shared libraries
ii  libcairo2   1.8.8-2  The Cairo 2D vector graphics libra
ii  libfontconfig1  2.8.0-2  generic font configuration library
ii  libfreetype62.3.11-1 FreeType 2 font engine, shared lib
ii  libglade2-0 1:2.6.4-1library to load .glade files at ru
ii  libglib2.0-02.22.4-1 The GLib library of C routines
ii  libgtk2.0-0 2.18.3-1 The GTK+ graphical user interface 
ii  libice6 2:1.0.6-1X11 Inter-Client Exchange library
ii  libpam0g1.1.0-4  Pluggable Authentication Modules l
ii  libpango1.0-0   1.26.2-1 Layout and rendering of internatio
ii  libsm6  2:1.1.1-1X11 Session Management library
ii  libx11-62:1.3.2-1X11 client-side library
ii  libxext62:1.1.1-2X11 miscellaneous extension librar
ii  libxinerama12:1.1-2  X11 Xinerama extension library
ii  libxml2 2.7.6.dfsg-2 GNOME XML library
ii  libxmu6 2:1.0.5-1X11 miscellaneous utility library
ii  libxpm4 1:3.5.8-1X11 pixmap library
ii  libxrandr2  2:1.3.0-2X11 RandR extension library
ii  libxrender1 1:0.9.5-1X Rendering Extension client libra
ii  libxt6  1:1.0.7-1X11 toolkit intrinsics library
ii  libxxf86misc1   1:1.0.2-1X11 XFree86 miscellaneous extensio
ii  libxxf86vm1 1:1.1.0-2X11 XFree86 video mode extension l
ii  xscreensaver-data   5.10-6   data files to be shared among scre

Versions of packages xscreensaver recommends:
ii  libjpeg-progs  7-1   Programs for manipulating JPEG fil
ii  perl [perl5]   5.10.1-8  Larry Wall's Practical Extraction 
ii  wamerican [wordlist]   6-3   American English dictionary words 
ii  xli1.17.0+20061110-3 command line tool for viewing imag

Versions of packages xscreensaver suggests:
pn  fortune none   (no description available)
ii  iceweasel [www-browser] 3.5.6-1  lightweight web browser based on M
ii  lynx-cur [www-browser]  2.8.8dev.2-1 Text-mode WWW Browser with NLS sup
ii  midori [www-browser]0.1.8-1  fast, lightweight graphical web br
pn  qcam | streamer none   (no description available)
ii  w3m [www-browser]   0.5.2-2.1WWW browsable pager with excellent
pn  xdaliclock  none   (no description available)
pn  xfishtank   none   (no description available)
ii  xscreensaver-gl 5.10-6   GL(Mesa) screen hacks for xscreens

-- no debconf information

Bug#566984: xscreensaver: screensaver only shows a black screen instead of the actual animation

[Jose Luis Rivas]

Hugo, did you check it what I told you? Please let me know so I can
close this bug.

Check in xscreensaver-demo if you have blank screensaver instead of
Only One Screensaver or Random Screensaver.

On Tue, Jan 26, 2010 at 6:10 AM, Hugo A. M. Torres macabr...@gmail.com wrote:
 Package: xscreensaver
 Version: 5.10-6
 Severity: grave
 Justification: renders package unusable

 I leave the pc unattended and when I come back I see a black screen instead 
 of the screensaver. Porwermanager is set to never blank screen.


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

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

 Versions of packages xscreensaver depends on:
 ii  libatk1.0-0                 1.28.0-1     The ATK accessibility toolkit
 ii  libc6                       2.10.2-2     GNU C Library: Shared libraries
 ii  libcairo2                   1.8.8-2      The Cairo 2D vector graphics 
 libra
 ii  libfontconfig1              2.8.0-2      generic font configuration 
 library
 ii  libfreetype6                2.3.11-1     FreeType 2 font engine, shared 
 lib
 ii  libglade2-0                 1:2.6.4-1    library to load .glade files at 
 ru
 ii  libglib2.0-0                2.22.4-1     The GLib library of C routines
 ii  libgtk2.0-0                 2.18.3-1     The GTK+ graphical user interface
 ii  libice6                     2:1.0.6-1    X11 Inter-Client Exchange library
 ii  libpam0g                    1.1.0-4      Pluggable Authentication Modules 
 l
 ii  libpango1.0-0               1.26.2-1     Layout and rendering of 
 internatio
 ii  libsm6                      2:1.1.1-1    X11 Session Management library
 ii  libx11-6                    2:1.3.2-1    X11 client-side library
 ii  libxext6                    2:1.1.1-2    X11 miscellaneous extension 
 librar
 ii  libxinerama1                2:1.1-2      X11 Xinerama extension library
 ii  libxml2                     2.7.6.dfsg-2 GNOME XML library
 ii  libxmu6                     2:1.0.5-1    X11 miscellaneous utility library
 ii  libxpm4                     1:3.5.8-1    X11 pixmap library
 ii  libxrandr2                  2:1.3.0-2    X11 RandR extension library
 ii  libxrender1                 1:0.9.5-1    X Rendering Extension client 
 libra
 ii  libxt6                      1:1.0.7-1    X11 toolkit intrinsics library
 ii  libxxf86misc1               1:1.0.2-1    X11 XFree86 miscellaneous 
 extensio
 ii  libxxf86vm1                 1:1.1.0-2    X11 XFree86 video mode extension 
 l
 ii  xscreensaver-data           5.10-6       data files to be shared among 
 scre

 Versions of packages xscreensaver recommends:
 ii  libjpeg-progs          7-1               Programs for manipulating JPEG 
 fil
 ii  perl [perl5]           5.10.1-8          Larry Wall's Practical Extraction
 ii  wamerican [wordlist]   6-3               American English dictionary words
 ii  xli                    1.17.0+20061110-3 command line tool for viewing 
 imag

 Versions of packages xscreensaver suggests:
 pn  fortune                     none       (no description available)
 ii  iceweasel [www-browser]     3.5.6-1      lightweight web browser based on 
 M
 ii  lynx-cur [www-browser]      2.8.8dev.2-1 Text-mode WWW Browser with NLS 
 sup
 ii  midori [www-browser]        0.1.8-1      fast, lightweight graphical web 
 br
 pn  qcam | streamer             none       (no description available)
 ii  w3m [www-browser]           0.5.2-2.1    WWW browsable pager with 
 excellent
 pn  xdaliclock                  none       (no description available)
 pn  xfishtank                   none       (no description available)
 ii  xscreensaver-gl             5.10-6       GL(Mesa) screen hacks for 
 xscreens

 -- no debconf information






-- 
Jose Luis Rivas. San Cristóbal, Venezuela.
GPG 0xCACAB118 0x7C4DF50D
http://joseluisrivas.net/acerca - http://ghostbar.ath.cx/about

Bug#559693: xscreensaver: depends on obsolete libxxf86misc

[Jose Luis Rivas]

On Sun, Jan 24, 2010 at 9:58 AM, Julien Cristau jcris...@debian.org wrote:
 On Sun, Dec  6, 2009 at 12:31:10 +, Jose Luis Rivas wrote:

 Let me check when I get home, thanks for the bug :)

 ping?

 See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559689#15 for some
 more details.

I'm so sorry Julien, I forgot this. I have updated the package and
tested it. Right now is building the final version and will upload it
as soon as finish.

Cheers and keep the good work!

--
Jose Luis Rivas. San Cristóbal, Venezuela.
GPG 0xCACAB118 0x7C4DF50D
http://joseluisrivas.net/acerca - http://ghostbar.ath.cx/about



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

Bug#562884: xscreensaver can be killed with Alt+SysRq+F

[Jose Luis Rivas]

Hi,

I wrote to Jamie about this and he frankly doesn't know how to fix
this without doing it as root. I found that with a binary helper with
SETUID may introduce a new security issue and honestly I don't have
the time right now to write the code to patch this bug.

I would like all the help that people could give me. I compromise to
do the tests and patch this issue. Remember that xscreensaver is
maintained under collab-maint with git so it's very easy to do any
patching and tests on the code.

Regards.
-- 
Jose Luis Rivas. San Cristóbal, Venezuela.
GPG 0xCACAB118 0x7C4DF50D
http://joseluisrivas.net/acerca - http://ghostbar.ath.cx/about



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

Bug#560173: xscreensaver-data-extra package: bsod screensaver missing

[Jose Luis Rivas]

Install xscreensaver-screensaver-bsod
--Mensaje original--
De: Massimo Gagliasso
Para:Debian Bug Tracking System
Responder a:Massimo Gagliasso
Responder a:560...@bugs.debian.org
Asunto: Bug#560173: xscreensaver-data-extra package: bsod screensaver missing
Enviado: 9 Dic, 2009 08:54

Package: xscreensaver-data-extra

Version: 5.10-4

Debian Sid


Regards

MG







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

Bug#559693: xscreensaver: depends on obsolete libxxf86misc

[Jose Luis Rivas]

Let me check when I get home, thanks for the bug :)
--Mensaje original--
De: Julien Cristau
Para:Debian Bug Tracking System
Responder a:Julien Cristau
Responder a:559...@bugs.debian.org
Asunto: Bug#559693: xscreensaver: depends on obsolete libxxf86misc
Enviado: 6 Dic, 2009 07:56

Package: xscreensaver
Severity: normal
User: debia...@lists.debian.org
Usertags: xf86misc

Hi,

your package depends or build-depends on libxxf86misc{1,-dev}.  Recent X
servers don't support the XFree86-Misc X11 extension, so we're
considering removal of the corresponding client library.

Thanks,
Julien







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

Bug#558024: xscreensaver: does not kill running processes when package removed

[Jose Luis Rivas]

You're right, sorry about that, thanks for pointing out this.

I will fix it when I get home :)

Cheers!
--Mensaje original--
De: Michael Gilbert
Para:Debian Bug Tracking System
Responder a:Michael Gilbert
Responder a:558...@bugs.debian.org
Asunto: Bug#558024: xscreensaver: does not kill running processes when package 
removed
Enviado: 25 Nov, 2009 19:04

package: xscreensaver
version: 5.10-3
severity: normal

after remove the xscreensaver package, xscreensaver processes
continue to run.  as a matter of least suprise, the postrm script
should kill all of the existing xscreensaver processes.  thanks.

mike







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

Bug#550042: xscreensaver still starts automatically in KDE sessions

[Jose Luis Rivas]

We are waiting for your answer.

On Mon, Nov 9, 2009 at 11:08 AM, Tormod Volden debian.tor...@gmail.com wrote:
 Yitz,
 Both KDE and GNOME ship by default their own screensaver daemons
 (kscreensaver and gnome-screensaver). I am most familiar with
 gnome-screensaver so I will use it as the example, but I think
 kscreensaver does the same. The gnome-screensaver package ships its
 own desktop file which is active by default. It is not the desktop
 environment which is activating it, it is the desktop file from the
 screensaver package which makes it start.

 We offer the xscreensaver as a substitute, for those who do not like
 gnome-screensaver for some reason. If they remove the
 gnome-screensaver package and install xscreensaver instead, they
 expect xscreensaver to be activated by default. This is also the case.
 Otherwise it would be considered a security issue that a screensaver
 package is not active after installation.

 Users of any other xdg-compliant desktop environment will also expect
 that xscreensaver is starting if they install it.

 We expect those who install both packages, to have a special reason
 for this, because a normal user on the other hand will just use
 gnome-screensaver which comes with GNOME. The special users will have
 to choose which one to use in their sessions.

 I don't know if you fall into any of those categories. Why do you
 install the xscreensaver package?

 If you have an elegant solution which caters for all needs, I would be
 very interested. I don't see why xscreensaver should be more defensive
 than gnome-screensaver in the both-installed corner case. Maybe the
 desktop environments (whatever function is sourcing the desktops)
 should note that two screensavers are installed and only start one of
 them?






-- 
Jose Luis Rivas. San Cristóbal, Venezuela.
GPG 0xCACAB118 0x7C4DF50D
http://joseluisrivas.net/acerca - http://ghostbar.ath.cx/about



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

Bug#550042: xscreensaver still starts automatically in KDE sessions

[Jose Luis Rivas]

On Sun, Nov 8, 2009 at 7:59 AM, Yitzchak Gale g...@sefer.org wrote:
 reopen 550042 =
 severity 550042 important
 thanks

 In the proposed fix for this bug, the Xsession.d item
 was replaced by an xdg autostart item. So xscreensaver
 still starts automatically for every desktop session.

 In a KDE session, this causes a conflict between
 xscreensaver and KDE's own screen saver service.
 The xscreensaver daemon should not be launched
 during a KDE session.

With XscreenSaver 5.10-3 we shipped xdg and the Xsession.d file wasn't
removed, please remove the Xsession.d and test. This bug (shipping
both files) is going to be fixed on next upload.

 On my system, if a KDE session is left untouched for
 a while, the session locks in a way that makes it
 impossible to unlock: any keyboard or mouse activity
 brings up the xscreensaver unlock dialogue, and even
 the correct password is rejected. Unless it is possible
 to log in remotely and take some action as root, the
 system has become completely unusable. Therefore,
 I have upgraded the severity to important, though
 perhaps it ought to be grave.

 In my opinion, this package should not cause any
 automatic startup at all of the xscreensaver
 daemon. It is the responsibility of each desktop
 environment and window manager to decide
 what automatic screen saver services, if any,
 to provide by default.

So KDE will provide it only for kscreensaver and GNOME only
gnome-screensaver. If someone is new and doesn't know how to set it up
automatic startup for xscreensaver it can't do it. Right? Sorry but I
don't think so. With the xdg.desktop it's suppossed you can deactivate
it on your window manager - startup manager.

Regards.
-- 
Jose Luis Rivas. San Cristóbal, Venezuela.
GPG 0xCACAB118 0x7C4DF50D
http://joseluisrivas.net/acerca - http://ghostbar.ath.cx/about



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

Bug#550201: Processed: Re: Bug#550201: this is an xscreensaver package installation script bug

[Jose Luis Rivas]

Just for the record I've fixed this already on my git and will upload this 
fixed (the postinst removal) tonight
--Mensaje original--
De: Tormod Volden
Para:550...@bugs.debian.org
Responder a:Tormod Volden
Responder a:550...@bugs.debian.org
Asunto: Bug#550201: Processed: Re: Bug#550201: this is an xscreensaver package  
installation script bug
Enviado: 4 Nov, 2009 10:04

Thanks for your report. The faulty startup script was already removed
in 5.10-3. However, this reminds me that we did not make sure we clean
it away on upgrades for those who happened to install 5.10-2. We will
take care of this in the next version.

The item in the Startup Applications list is a feature. If people
install xscreensaver they expect it to start. We do not recommend
installing both gnome-screensaver and xscreensaver, but we do not want
to inhibit it for those with special needs. We looked at the
NotShowIn=GNOME option, but some people run Gnome but prefer
xscreensaver to gnome-screensaver.

Bug#553529: xscreensaver: Fake crash screensaver should not be enabled by default

[Jose Luis Rivas]

I'm already separating webcollage and bsod, don't worry. This will be uploaded 
probably this night. I already talked about this with Daniel.
-Original Message-
From: Tormod Volden debian.tor...@gmail.com
Date: Wed, 4 Nov 2009 15:15:50 
To: Daniel Dickinsoncrazycsh...@gmail.com; 553...@bugs.debian.org
Subject: Bug#553529: xscreensaver: Fake crash screensaver should not be  
enabled by default

On Sun, Nov 1, 2009 at 4:08 PM, Daniel Dickinson crazycsh...@gmail.com wrote:
 Another point of what a *package* is supposed to do, is that it is
 supposed to be generally usable without having to vet every options of
 every screen of the package.  That would defeat the point of using
 packages and and distribution over a micromanaged LFS or Gentoo
 system.  If I have to go over every package, in detail, to be sure that
 the maintainer hasn't got a landmine in the package for my users, I
 haven't gained much by using a prepackaged distribution like Debian.

 Debian isn't just for developers.

The -extra package is not included by any installer, so normal users
will not get the BSOD screensaver. They have to actively hunt it down
and install it. If they get so far, there are much worse examples of
what they can install that can be potentially dangerous if used the
wrong way. With reference to prepackaged distribution I do not think
we have to dumb down all packages available in the Debian repository.

This is one of the reasons we have a separate -extra package. Your
suggestion is should not be enabled by default and that is exactly
what we are doing by putting BSOD into -extra.

I think the huge majority of Debian users (developers or not) find
BSOD very entertaining, and they would be upset if we remove it or
make it difficult to use. And frankly, I do not think many people
panic and hit the power button without even move the mouse or press a
key (which would stop the screensaver).

Tormod

Bug#553529: xscreensaver: Fake crash screensaver should not be enabled by default

[Jose Luis Rivas]

reassign 553529 xscreensaver-data-extra
quit
On Sun, Nov 1, 2009 at 2:04 AM, Daniel Dickinson crazycsh...@gmail.com wrote:
 On Sun, 1 Nov 2009 04:05:10 +
 Jose Luis Rivas josel...@rivco.net wrote:

 Severity 553529 wishlist
 Quit

 Haha. This is a problem between the chair and the keyboard, this is
 not a RC bug. ;-)


 This isn't funny.  I have had users mistakenly reboot because they
 didn't know any better. For a *default* screensaver on a system that is
 supposed to be used by people who won't know any better, this *is* an
 RC bug.  I'm bumping the severity, and am quite willing to take this to
 the next level.

 If were not a *default* screensaver I wouldn't be worried, but I have
 had upset users, and I don't blame them.  Even I had a moment of panic
 the first time it happened to me.  It may be a 'joke' but it's from UI
 point of view it's RC.  It doesn't matter that the programming is
 between the chair and the keyboard rather than the computer.  It's a
 natural reaction to see the computer die badly, especially given what
 happens to Windows computers under such circumstances.

It's not a RC, it may be an *important* bug but not a RC. It's *not*
installed by default, is on xscreensaver-data-extra which you have to
manually install yourself. Again, is not installed by default.

It's a RC bug? Let's take some already big bugs that really rendered
to data loss but because of user actions: rm -rf /. [0] Even in that
case it was not a grave bug but a *wishlist* bug, because it wasn't an
issue on the app side but on the user side. It does the package make
you lose information? Or your overreaction? Yes, is the second so is
not on the package part but on the user and you can't report a bug
against an user.

Plus, is the intended behavior, the package was made on that sense,
that's what the screensaver is supposed to do. So it's not a bug but a
feature!

About why it may be an important severity bug
--

If your reasoning is good and users overreaction to expected behavior
of the app counts as bugs then it should be important instead of
grave. The simple reason is because doesn't renders to data loss for
every the users but only to the users that are used to press reset
button before moving the mouse or pressing a key.


 And yes, I'm quite willing to take this the CTTE.

Well, I already asked for advice on #debian-devel and most of their
solutions was to close this bug and tell you to uninstall the package
xscreensaver-data-extra. I'm being nice and I'm willing to unmark it
by default, I never said I was not going to customize it so your users
wouldn't complain, but I'm *not* willing to receive any kind of
threats. And really, *is not even a bug!*.

[0] https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/174283
-- 
Jose Luis Rivas. San Cristóbal, Venezuela.
GPG 0xCACAB118 0x7C4DF50D
http://joseluisrivas.net/acerca - http://ghostbar.ath.cx/about



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

Bug#553529: xscreensaver: Fake crash screensaver should not be enabled by default

[Jose Luis Rivas]

Severity 553529 wishlist
Quit

Haha. This is a problem between the chair and the keyboard, this is not a RC 
bug. ;-)

Cheers!
-Original Message-
From: Daniel Dickinson crazycsh...@gmail.com
Date: Sat, 31 Oct 2009 23:54:55 
To: Debian Bug Tracking Systemsub...@bugs.debian.org
Subject: Bug#553529: xscreensaver: Fake crash screensaver should not be enabled 
by default

Package: xscreensaver
Version: 5.05-3
Severity: grave
Justification: causes non-serious data loss

The fake crash screensaver causes users who don't know about it to panic and 
reboot the system, without necessarily hit other keys first, thereby
potentially causing data loss.  It's really a bad idea to have something that
look like a fatal error and says to reboot, for a user who is not expecting it.

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

Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xscreensaver depends on:
ii  libatk1.0-0 1.22.0-1 The ATK accessibility toolkit
ii  libc6   2.7-18   GNU C Library: Shared libraries
ii  libcairo2   1.6.4-7  The Cairo 2D vector graphics libra
ii  libglade2-0 1:2.6.2-1library to load .glade files at ru
ii  libglib2.0-02.16.6-2 The GLib library of C routines
ii  libgtk2.0-0 2.12.12-1~lenny1 The GTK+ graphical user interface 
ii  libice6 2:1.0.4-1X11 Inter-Client Exchange library
ii  libpam0g1.0.1-5+lenny1   Pluggable Authentication Modules l
ii  libpango1.0-0   1.20.5-5 Layout and rendering of internatio
ii  libsm6  2:1.0.3-2X11 Session Management library
ii  libx11-62:1.1.5-2X11 client-side library
ii  libxext62:1.0.4-1X11 miscellaneous extension librar
ii  libxinerama12:1.0.3-2X11 Xinerama extension library
ii  libxml2 2.6.32.dfsg-5+lenny1 GNOME XML library
ii  libxmu6 2:1.0.4-1X11 miscellaneous utility library
ii  libxpm4 1:3.5.7-1X11 pixmap library
ii  libxrandr2  2:1.2.3-1X11 RandR extension library
ii  libxrender1 1:0.9.4-2X Rendering Extension client libra
ii  libxt6  1:1.0.5-3X11 toolkit intrinsics library
ii  libxxf86misc1   1:1.0.1-3X11 XFree86 miscellaneous extensio
ii  libxxf86vm1 1:1.0.2-1X11 XFree86 video mode extension l
ii  xscreensaver-data   5.05-3   data files to be shared among scre

Versions of packages xscreensaver recommends:
ii  libjpeg-progs  6b-14 Programs for manipulating JPEG fil
ii  perl [perl5]   5.10.0-19lenny2   Larry Wall's Practical Extraction 
ii  wamerican [wordlist]   6-2.3 American English dictionary words 
ii  wcanadian-huge [wordli 6-2.3 Canadian English dictionary words 
ii  xli1.17.0+20061110-3 command line tool for viewing imag
ii  xloadimage 4.1-16.1  Graphics file viewer under X11

Versions of packages xscreensaver suggests:
ii  elinks [www-browser]   0.11.4-3  advanced text-mode WWW browser
ii  fortune-mod [fortune]  1:1.99.1-3.1  provides fortune cookies on demand
ii  iceweasel [www-browser]3.0.6-3   lightweight web browser based on M
ii  lynx-cur [www-browser] 2.8.7dev9-2.1 Text-mode WWW Browser with NLS sup
pn  qcam | streamernone(no description available)
ii  w3m [www-browser]  0.5.2-2+b1WWW browsable pager with excellent
pn  xdaliclock none(no description available)
pn  xfishtank  none(no description available)
pn  xscreensaver-glnone(no description available)

-- no debconf information

Bug#550042: XScreensaver has hooks in Xsession

[Jose Luis Rivas]

Allan there's another ticket about this, please merge it, I'm not at home ;-)
--Mensaje original--
De: Allan Sandfeld Jensen
Para:Debian Bug Tracking System
Responder a:Allan Sandfeld Jensen
Responder a:550...@bugs.debian.org
Asunto: Bug#550042: XScreensaver has hooks in Xsession
Enviado: 7 Oct, 2009 04:46

Package: xscreensaver
Version: 5.10-2

XScreenSaver has an entry in /etc/X11/Xsession.d that starts it automatically. 
This entry has to go.

The problem is that xscreensaver should not start automatical. Many desktop-
environments has wrappers around xscreensaver. When xscreensaver starts by 
itself it no longer respects any user settings which are currently set in the 
desktop environment.

Solution is simple: Remove /etc/X11/Xsession.d/80xscreensaver_start







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

Bug#357297: Please revert this awful feature or fix it.

[Jose Luis Rivas]

On Sat, Oct 3, 2009 at 12:43 PM, Lennart Sorensen
lsore...@csclub.uwaterloo.ca wrote:
 After the latest xscreensaver version which includes this feature,
 I now have xscreensaver being started when X is started no matter what
 user logs in.  That is unacceptable since when I have mythtv logged in I
 specifically do not want a screensaver, and I already made sure I don't
 have one by using a custom .xsession.  Now all of a sudden I have a
 screensaver being forced on me just by installing the xscreensaver
 pacakge (which is a nice screensaver to have, just not for all users
 with no way to disable it).

 At the very least it should be possible to set an environment in the
 .xsession or similar to prevent xscreensaver from starting.  Starting it
 without exception is not acceptable.

 Besides there are other screensavers out there that some users may choose
 to run instead (like the gnome and kde screensavers).
Yah, but we want to take over da world g

 I would prefer this bad change be reverted ASAP though.

Please just remove the file, I will work on this ASAP. Wait at least
until this weekend.

-- 
Jose Luis Rivas. San Cristóbal, Venezuela.
GPG 0xCACAB118 0x7C4DF50D
http://joseluisrivas.net/acerca - http://ghostbar.ath.cx/about



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

Bug#548507: xscreensaver: please restore hypercube

[Jose Luis Rivas]

On Sun, Sep 27, 2009 at 12:38 PM, Michal Suchanek hramr...@centrum.cz wrote:
 Package: xscreensaver
 Version: 5.10-1
 Severity: wishlist


 Hello

 Thei hyperball and hypercube hacks were removed in the recent xscreensaver
 release.

 While I admit they are not particularly brilliant compared to the other
 hacks available these days they are not too bad either.

 Another reason I liked these hacks is that they are good for testing
 line drawing functions in the graphics system. They are excerscising
 line drawing quite a bit and flaws in the implementation are often
 visible. When there was a problem with line drawing on a particular card
 model it was quite easily reporducible using these hacks.

Hi Michal,

They were removed from upstream since 5.10, the reason is that they
are redundant with polytopes. (
http://www.jwz.org/xscreensaver/changelog.html )

Cheers!
-- 
Jose Luis Rivas. San Cristóbal, Venezuela.
GPG 0xCACAB118 0x7C4DF50D
http://joseluisrivas.net/acerca - http://ghostbar.ath.cx/about



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

Bug#548385: xscreensaver-data installation fails (trying to overwrite file from gnome-screensaver)

[Jose Luis Rivas]

Hi Vincent, just for the record this was fixed in the version I just uploaded 
5.10-2.

Regards.
-Original Message-
From: Vincent Lefevre vinc...@vinc17.org

Date: Sat, 26 Sep 2009 01:46:20 
To: Debian Bug Tracking Systemsub...@bugs.debian.org
Subject: Bug#548385: xscreensaver-data installation fails (trying to overwrite 
file from gnome-screensaver)


Package: xscreensaver-data
Version: 5.05-3+nmu1
Severity: grave
Justification: renders package unusable

I get the following error:

# apt-get install xscreensaver-data
[...]
Preparing to replace xscreensaver-data 5.05-3+nmu1 (using 
.../xscreensaver-data_5.10-1_amd64.deb) ...
Unpacking replacement xscreensaver-data ...
dpkg: error processing 
/var/cache/apt/archives/xscreensaver-data_5.10-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/applications/screensavers/popsquares.desktop', 
which is also in package gnome-screensaver 0:2.26.1-1
Processing triggers for desktop-file-utils ...
Errors were encountered while processing:
 /var/cache/apt/archives/xscreensaver-data_5.10-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- System Information:
Debian Release: squeeze/sid
  APT prefers oldstable
  APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26.5-20080922 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages xscreensaver-data depends on:
ii  libc6 2.9-26 GNU C Library: Shared libraries
ii  libglib2.0-0  2.22.0-1   The GLib library of C routines
ii  libgtk2.0-0   2.18.0-1   The GTK+ graphical user interface 
ii  libice6   2:1.0.5-1  X11 Inter-Client Exchange library
ii  libjpeg62 6b-15  The Independent JPEG Group's JPEG 
ii  libsm62:1.1.1-1  X11 Session Management library
ii  libx11-6  2:1.2.2-1  X11 client-side library
ii  libxext6  2:1.0.4-1  X11 miscellaneous extension librar
ii  libxmu6   2:1.0.4-2  X11 miscellaneous utility library
ii  libxpm4   1:3.5.7-2  X11 pixmap library
ii  libxt61:1.0.6-1  X11 toolkit intrinsics library

xscreensaver-data recommends no packages.

xscreensaver-data suggests no packages.

-- no debconf information

Bug#495633: Status?

[Jose Luis Rivas]

2009/7/15 Yves-Alexis Perez cor...@debian.org:
 And, 11 months later, what's the status on this one? Is flurry still
 crashy? I may try to rebuild xscreensaver with it, but if you had chance
 to test it…

 Cheers,

 --
 Yves-Alexis


You're right Yves-Alexis, we haven't been able to reproduce the crash
(nor once) but since was such a severe bug (freezin' all the system!)
we decided to demote it. Anyway I just included it on 5.08-1~pre2, you
can find it on http://debian.rivco.info or directly from the git repo
on alioth [0] I just tagged it debian/5.08-1-pre2. It doesn't crash to
me as ever, anyway I'm BCC'in to Gunnar who reported the freeze so he
can check by himself as well.

If anyone wants to test it and is using i386 or wants to apt-get
source it then can use:

deb{-src} http://reprepro.deb.rivco.info/debian unstable main

Yves-Alexis, thanks for popping out this bug I forgot. :-)

Regards,

[0] http://git.debian.org/?p=collab-maint/xscreensaver.git

-- 
Jose Luis Rivas. San Cristóbal, Venezuela.
GPG 0xCACAB118 0x7C4DF50D
http://joseluisrivas.net/acerca - http://ghostbar.ath.cx/about



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

Bug#505379: Is bug similar to redhat bug #481146?

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160

2009/5/15 Frans Pop :
 tags 505379 + patch fixed-upstream
 thanks

 On Monday 04 May 2009, Frans Pop wrote:
 On Sunday 03 May 2009, Scott Howard wrote:
  If this bug is still around, is it the same as:
  https://bugzilla.redhat.com/show_bug.cgi?id=481146? That bug has
  phosphor SEGV in xscreensaver, apparently fixed in xscreensaver-5.08.

 I've compiled Lenny's phosphor with that patch now and will report if
 it works or not. Thanks for the pointer.

 I've not seen the segfault anymore since applying the patch, so it
 probably is the same issue.
 In the meantime I've also seen the segfault on my i386 laptop, so I'll
 patch it there as well.

 Here's a direct link to the patch:
 https://bugzilla.redhat.com/attachment.cgi?id=329709


Thanks Frans, I'm working right now on it.

Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118
http://ghostbar.ath.cx/about - http://debian.org.ve


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREDAAYFAkoPGV4ACgkQOKCtW8rKsRjG2gCgvyP+9084+aUnR0f2aQ7jw9pB
NSsAnio6NWtmxXX8X0b9tAeY8I3iQPMb
=eH/l
-END PGP SIGNATURE-



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

Bug#527880: libtorrent11: Incorrent version numbers or incorrect package?

[Jose Luis Rivas]

2009/5/10 Victor Song curiouserandcuriou...@gmail.com:
 Package: libtorrent11
 Version: 0.12.4-2
 Severity: normal


 Version number do not seem to match in:
 1) aptitude: libtorrent11 0.12.4
 Is it supposed to be libtorrent12?

No, it's not. The number in the package is the soname version, not the
library version. Anyway, normally this numbers are the same but
libtorrent is not that normal.

 2) The banner on starting rtorrent says rTorrent 0.8.3/0.12.3
 Is 0.12.4 or 0.12.3? Wrong package?
(This is libtorrent's bug page, I'll answer you this on rtorrent's bugs)


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

 Kernel: Linux 2.6.29-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/bash

 Versions of packages libtorrent11 depends on:
 ii  libc6                         2.9-12     GNU C Library: Shared libraries
 ii  libgcc1                       1:4.4.0-4  GCC support library
 ii  libsigc++-2.0-0c2a            2.0.18-2   type-safe Signal Framework for 
 C++
 ii  libssl0.9.8                   0.9.8g-16  SSL shared libraries
 ii  libstdc++6                    4.4.0-4    The GNU Standard C++ Library v3

 Versions of packages libtorrent11 recommends:
 ii  rtorrent                      0.8.4-3    ncurses BitTorrent client based 
 on

 libtorrent11 suggests no packages.

 -- no debconf information






-- 
Jose Luis Rivas. San Cristóbal, Venezuela. PGP: 0xCACAB118
http://ghostbar.ath.cx/{about,acerca} - http://debian.org.ve
`ghostbar' @ irc.debian.org/#debian-ve,#debian-devel-es



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

Bug#527882: rtorrent: Wrong package or wrong version?

[Jose Luis Rivas]

2009/5/10 Victor Song curiouserandcuriou...@gmail.com:
 Package: rtorrent
 Version: 0.8.4-3
 Severity: normal

 Version number do not seem to match.
 The banner on starting rtorrent says rTorrent 0.8.3/0.12.3
 In aptitude the version is shown as 0.8.4-3. Wrong package?

Hello Victor, you're right. There was an issue in the git branchs.

Hey guys, if you're building the packages with git-buildpackage you
need to import new origs tarballs to upstream branch (which is yet at
0.12.3 for unstable, 0.12.4 is only at upstream-experimental). This is
merged in master and this way we have the latest software on master
and upstream tarball uncompressed on a separate branch :)

(If you guys don't answer this at 16H GMT -04:30 I'll do it by myself)


Thanks for your feedback Victor,
Regards.
-- 
Jose Luis Rivas. San Cristóbal, Venezuela. PGP: 0xCACAB118
http://ghostbar.ath.cx/{about,acerca} - http://debian.org.ve
`ghostbar' @ irc.debian.org/#debian-ve,#debian-devel-es



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

Bug#519061: xscreensaver: Won't unlock my screen at all due to apparent password difficulties.

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ben Klein wrote:
 I can reproduce this behaviour on unstable/amd64 with xscreensaver
 5.05-3 and 5.07-1 from experimental. It doesn't occur on unstable/i386
 (version 5.05-3).
 
 Regarding weird PAM settings, I've made no modifications to the PAM
 configuration on either system from what the packages provide. What's
 interesting is that on my laptop, I have a file
 /etc/pam.d/xscreensaver.pam.11612. Contents:
 
 /etc/pam.d/xscreensaver: (this is the same on both i386 and amd64)
 #
 # /etc/pam.d/xscreensaver - PAM behavior for xscreensaver
 #
 
 @include common-auth
 @include common-account

Hi Ben, the .pam file is doing nothing, you can delete it.

Please try adding to pam.d/xscreensaver this lines at the bottom:
@include common-password
@include common-session

And let me know if that works :)

Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118
http://ghostbar.ath.cx/about - http://debian.org.ve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknXpwoACgkQOKCtW8rKsRhMpgCgmBBT0gEfOqBHzRiWF0XKYtyk
UmoAn3Mq7xyELMYCCOCgx5Mi3QA697U8
=CZO2
-END PGP SIGNATURE-



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

Bug#516886: xscreensaver-gl: preview crashes GDM in lenny

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Wolfgang Schulze-Zachau wrote:
 OK, I understand. Had a quick trawl through my logfiles, but can't see any 
 other error messages related to X or GDM. OTOH, currently my xscreensaver is 
 completely disabled. Are there any pointers you could provide for things to 
 try out? Special places to search?
 
 Cheers
 
 Wolfgang
 
 
 -Original Message-
 From: Jose Luis Rivas [mailto:ghostba...@gmail.com] 
 Sent: 31 March 2009 01:37
 To: Wolfgang Schulze-Zachau; 516...@bugs.debian.org
 Subject: Re: Bug#516886: xscreensaver-gl: preview crashes GDM in lenny
 
 Wolfgang Schulze-Zachau wrote:
 Package: xscreensaver-gl
 Version: 5.05-3
 Severity: normal
 
 
 when selecting any of the gl screensavers in preview mode (i.e. after 
 opening System-Preferences-
 Screensaver), GDM crashes, all open windows are closed and I end up back at 
 the login prompt.
 This does not seem to be affected by whatever applications I am running, as 
 it happens all the same when
 all user applications are closed.
 The system log produces:
 gdm[19178]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting 
 :0
 
 There's some issue with your X caused by something XScreenSaver ran,
 probably something related to your graphic card configuration. Please
 check with other GL stuff the logs.
 
 I'll let this bug open but I don't believe is a xscreensaver bug.
 
 Regards.

You could try with any GL app so we could see if there's anything going
on with GL-specific tasks. I've had many gdm issues lately that I think
should not be related but my incapacity to get the source of the issues
had made me to not submit any bug to gdm.

Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118
http://ghostbar.ath.cx/about - http://debian.org.ve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknTk0gACgkQOKCtW8rKsRh5jgCcDBnDGLxn4O4y1bT7Bsr3wI/a
yuMAn0H4UMAnXUoNPZdGyL/e9inJL/C4
=q2Wh
-END PGP SIGNATURE-



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

Bug#516522: xscreensaver: will not start in Lenny

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

Sorry for my late answer, I was pretty busy.

This only happens on mga cards according to what you said, anyway I
tried in an old PC with mga card and worked as should, I'll downgrade
this bug to important while there's more work over debugging of this case.

Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118
http://ghostbar.ath.cx/about - http://debian.org.ve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknRFJcACgkQOKCtW8rKsRhN7QCgjuqsaTivrPFePFrC7dwczpq8
GG8AnRjwsykqnafZVEKo+wQZUJtbwhXR
=FGHp
-END PGP SIGNATURE-



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

Bug#513726: working_directory option doesn't exist

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Rafal Czlonka wrote:
 Package: rtorrent
 Version: 0.7.9-2.2
 Severity: normal
 
 Hi,
 When using 'working_directory' option I get:
 
 % rtorrent 
 rtorrent: Error in option file: ~/.rtorrent.rc:1: Command
 working_directory does not exist.
 
 Please update the manual page and/or fix the missing option.
 

According to the man I've in my machine is cmd instead of
working_directory... Are you sure about this?

Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118
http://ghostbar.ath.cx/about - http://debian.org.ve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknRYO8ACgkQOKCtW8rKsRhzuACgi2TwTEJl+ATlkGkKTsiWswCk
krgAoJE/trg5JfNhkA5R/pLfW8vgI4Zj
=rWAR
-END PGP SIGNATURE-



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

Bug#514527: Generation of non-correct XML on SCGI interface.

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dmitry E. Oboukhov wrote:
 Hi, Luis!
 
 I maintain a package (rtpg) which depends to rtorrent/librtorrent.
 Also there are a lot of people who use rtorrent/rtpg with non-english 
 trackers. This bug delivers bad feeling to those people.
 
 I rebuilt rtorrent with the patch and every time when somebody knocks
 my jabber and tells about errors in my rtpg, I give him to download
 these versions (0.7.9 and 0.8.4).
 
 Could you apply the patch to version 0.8.4 and upload it to
 debian/unstable?
 
 I can become your sponsor if you need. Also I could help to maintain
 the rtorrent :)
 
 PS: there is an obsolete link in rtorrent:debian/control which points
 to VCS: http://bzr.debian.org/collab-maint/rtorrent/debian/. Could you
 make actualization for it, or recreate GIT-repo on git.debian.org?

Hello Dmitry, sorry for my late answer, please feel free, I was lacking
time for debian work, the git repo is at
git://git.debian.org/git/collab-maint/{libtorrent,rtorrent}.git ,
there's no update in qa-page because the git update to debian/control
was on experimental and unstable hasn't been uploaded.

I'll be working on this ASAP, probably tomorrow since I'm getting in
sync with all my packages bugs.

Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118
http://ghostbar.ath.cx/about - http://debian.org.ve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknRZHYACgkQOKCtW8rKsRh7VACgkGrUflRo89pztJnHPJVAXqkZ
h78An3og+vTn2uSdUJ7O74YamCw3U+TH
=2do8
-END PGP SIGNATURE-



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

Bug#515273: rtorrent: Read past initial payload after incoming encrypted handshake

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Kurt Roeckx wrote:
 Package: rtorrent
 Version: 0.7.9-2.2
 Severity: important
 
 Hi,
 
 I've just had rtorrent quit on me 2 times with the following message:
 rtorrent: Read past initial payload after incoming encrypted handshake
 
 I had this in my .rtorrentrc:
 encryption=allow_incoming,enable_retry
 
 I've just disabled it, we'll see if it helps or not.
 
 
 Kurt
 
 
 
Hi Kurt, did this helped you?

- --
Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118
http://ghostbar.ath.cx/about - http://debian.org.ve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknRZN4ACgkQOKCtW8rKsRijVwCgxNppX9F7NFcicGLGPgSwd871
CH8AoL4z/OryYgel6o6Vv0XpWdqRvAlI
=y6bh
-END PGP SIGNATURE-



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

Bug#519061: xscreensaver: Won't unlock my screen at all due to apparent password difficulties.

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Willy Gommel wrote:
 Subject: xscreensaver: Won't unlock my screen at all due to apparent password 
 difficulties.
 Package: xscreensaver
 Version: 5.05-3
 Severity: important
 
 *** Please type your report below this line.
 
 I have been noticing that I cannot break out of the locked screen mode at all 
 without pressing the reset button.
 
 The problem I've been having is that, although I KNOW that I have been 
 supplying the correct password, no possible typing of it will do the trick at 
 all.
 
 If there is a work-around, I have been unable to find it.
 
 I rated this as Important in severity because of the need to press the reset 
 button to break out of the locked screen condition. I much prefer to have the 
 machine shut down normally.
 
 I have noted this on my AMD64 machine ONLY. Two IA-32 machines I have happen 
 to function normally in that regard.

Hello Willy,

Does you use any kind of weird pam configuration? Please give me as many
details as you can.

Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118
http://ghostbar.ath.cx/about - http://debian.org.ve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknRZm4ACgkQOKCtW8rKsRgHQgCguBF58vJ6O1FgNsDgNGedpmxQ
+pMAnicLWc+MitHBFFF129gEBepOJWSa
=KdZJ
-END PGP SIGNATURE-



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

Bug#516886: xscreensaver-gl: preview crashes GDM in lenny

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Wolfgang Schulze-Zachau wrote:
 Package: xscreensaver-gl
 Version: 5.05-3
 Severity: normal
 
 
 when selecting any of the gl screensavers in preview mode (i.e. after opening 
 System-Preferences-
 Screensaver), GDM crashes, all open windows are closed and I end up back at 
 the login prompt.
 This does not seem to be affected by whatever applications I am running, as 
 it happens all the same when
 all user applications are closed.
 The system log produces:
 gdm[19178]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0

There's some issue with your X caused by something XScreenSaver ran,
probably something related to your graphic card configuration. Please
check with other GL stuff the logs.

I'll let this bug open but I don't believe is a xscreensaver bug.

Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118
http://ghostbar.ath.cx/about - http://debian.org.ve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknRZcIACgkQOKCtW8rKsRhucACeIycyfsuO1hVru+ciGCyJfUSq
c80An25gy2TVpJdpLzs7ccadhOvCMumu
=Wn+D
-END PGP SIGNATURE-



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

Bug#521783: RFH: xscreensaver - Automatic screensaver for X (looking for co-maintainers)

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: wnpp
Severity: normal

I request assistance for maintaining XScreenSaver, I've been without too
much time lately and the bugs requests a lot of debugging in several areas.

The main tasks are:
* Debug the tickets and check which ones are yet a bug and which not.
* Checking and applying patches.
* Checking that there are no issues with packages like kdescreensaver
which depends on build-time of xscreensaver.

I use git to maintain it, is hosted at git.debian.org [0], you can fork
it as well from my github account [1], so if you're interested you
should know basic stuff about git and about maintaining packages with
git (in case of not knowing anything this could be useful [2]).

There are remaining tasks like before launching 5.08 (which is basically
ready):
* Complete the debian/copyright file: it was almost empty, most of the
hacks were obviated and in my spare time I've almost filled the file at
50%. This is the main reason why I haven't tried to upload new xscreensaver.
* Checking which bugs were closed with the latest upstream-release.
* Checking with the KDE-team any issue xscreensaver may give during
build-time for kdescreensaver (which often happens)

This includes the xscreensaver source which is conformed by the
following binaries:
* xscreensaver
Automatic screensaver for X
* xscreensaver-data
data files to be shared among screensaver frontends
* xscreensaver-data-extra
data files to be shared among screensaver frontends
* xscreensaver-gl
GL(Mesa) screen hacks for xscreensaver
* xscreensaver-gl-extra
GL(Mesa) screen hacks for xscreensaver

There's currently a pending approval for a project in alioth so there
could be more syncing between co-maintainers.

Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118
http://ghostbar.ath.cx/about - http://debian.org.ve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknQSyIACgkQOKCtW8rKsRhiygCdGy8bqdm+Ggt9tSJ4OjtlaGmu
Ah4An0Ox2ZwxYJYPlZOdFg5NkdY0GgsK
=Klhb
-END PGP SIGNATURE-



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

Bug#521783: RFH: xscreensaver - Automatic screensaver for X (looking for co-maintainers)

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

[0] http://git.debian.org/?p=collab-maint/xscreensaver.git
[1] http://github.com/ghostbar/deb-xscreensaver
[2] http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.html
- --
Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118
http://ghostbar.ath.cx/about - http://debian.org.ve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknQTNMACgkQOKCtW8rKsRjy4QCfVjY0qzOSwZCUeLHlu4iJqcfO
tZAAn1VevtcgDS32KSgJSrnZGExSCqj0
=pNTM
-END PGP SIGNATURE-



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

Bug#490171: Bug#470416: rtorrent: random crash (grave)

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jari Aalto wrote:
 Jose Luis Rivas [EMAIL PROTECTED] writes:
 
 Jari Aalto wrote:

 Confirmed.

 There seesm to be more a serious problem. Not just the rtorrent crash, but
 the whole workstation dies: kernel becomes unresponsive to the point
 where nothing happens.
 Can you please try with experimental release? I'm not in position to
 make this test (starting by my lack of bandwith and lack of hardware,
 I'm not always online in my machine).

 I'm about to push experimental to unstable and this one would make
 another good reason to do this. (Besides of #506748)
 
 Same results with 0.8.4-1. Kernel completely freezes after a while.
 
 Jari
I just noted something, I've got system freezing too with 2.6.26 (and
only with this kernel) but without using rtorrent.

Please, could you try with another kernel? (I'm right now using 2.6.27
and haven't got any freeze) Just for checking

Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118
http://ghostbar.ath.cx/about - http://debian.org.ve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkk8jVYACgkQOKCtW8rKsRi2mQCfVbPlpPm7tvouomOKyvVbOJP2
rfQAn3yqgB9aJZOF74au8JCCrOtXkYuP
=1/D5
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#506748: crash rtorrent by scgi-interface (function: 'fi.get_filename_last')

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dmitry E. Oboukhov wrote:
 I don't mind loading this package (0.8.4) into unstable. However it
 will not be included into lenny. Only 0.7.9 version can be included
 into lenny. Because now it is frozen. :(
 

Well, I believe right now is the only sane way to fix it ASAP, 0.8.2
isn't as good as 0.8.4 (even when upstream says is the stable release)
since has a lot of bugs and in fact it was the most troublesome release
they made so I'm not willing to push something that will make more
errors that what we have right now.

IMO, 0.8.4 could be a nice release at end of december since has passed a
long time without bugs being reported against this version (since
nov-19) and until december is a prudential time.

Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118
http://ghostbar.ath.cx/about - http://debian.org.ve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkk6Zc8ACgkQOKCtW8rKsRioIQCglKhu3pJ+vDZwyI8WZ3mCPYKR
pCAAoLzfEWyZIs1hRqkfPpwtyJkuNWWn
=gkbX
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#506748: closed by Jose Luis Rivas [EMAIL PROTECTED] (Fixed in experimental)

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dmitry E. Oboukhov wrote:
 reopen 506748
 thanks
 
 But this upload does not fix this bug in the testing :(
 lenny is frozen, version for lenny is 0.7.9
 
 If you want to fix this bug unsing upload version != 0.7.9
 you must receive release-team's permission
 
 
 sorry

Mmm... I'm closing it from 0.8.4-1 so remains open for 0.7.9-1+b2 this
way people on experimental knows this bug is indeed fixed, people in
unstable see this bug is open and in fact keeps as RC in bugs overview
since there's a release on Debian with the bug open.

That's the functionality of found while submitting and version while
setting as done (as long as I know) so I'll not need r-t permission for
closing the bug in _experimental_.

Please, let me know if this is wrong and I'll let then the bug as is
right now, open. If not I in 2 days or something will set it as done,
again :)

Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118
http://ghostbar.ath.cx/about - http://debian.org.ve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkk7AD4ACgkQOKCtW8rKsRiXZACg0HM4u/KLWMxjNGF4BzIRYxKY
e4UAn3YznJZRQAtD+THIRtsnbUmyUjE1
=Dhb+
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#507946: xscreensaver: Does not stay operation on the second of a dual screen display

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Daniel Dickinson wrote:
 Package: xscreensaver
 Version: 5.07-1
 Severity: normal
 
 
 xscreensaver, when told to 'blank now' blanks the first and second display, 
 but the second display (which has lower resolution and bit depth and no 
 acceleration) immediately becomes unblanked and sits unblanked.
 
Hello Daniel,

There's a specific hack where this happens? If that's the case, is from
xsscreensaver-glx?

- --
Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118
http://ghostbar.ath.cx/about - http://debian.org.ve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkk7CgoACgkQOKCtW8rKsRgbjgCff1DMoHsFJzI6bm6gugxDUkfF
0NMAn0Bucg4L9Zl0SJmQEjbMRnaBXkkn
=PoUk
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#490171: Bug#470416: rtorrent: random crash (grave)

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jari Aalto wrote:
 
 Confirmed.
 
 There seesm to be more a serious problem. Not just the rtorrent crash, but
 the whole workstation dies: kernel becomes unresponsive to the point
 where nothing happens.

Can you please try with experimental release? I'm not in position to
make this test (starting by my lack of bandwith and lack of hardware,
I'm not always online in my machine).

I'm about to push experimental to unstable and this one would make
another good reason to do this. (Besides of #506748)

Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118
http://ghostbar.ath.cx/about - http://debian.org.ve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkk5zSsACgkQOKCtW8rKsRh3dgCcDIxoLqKd17O8qCr2uA7P5aOZ
TvkAoK2UoqwKXza14HYaK4Vd4sn3lElr
=EMGd
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#506748: crash rtorrent by scgi-interface (function: 'fi.get_filename_last')

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dmitry E. Oboukhov wrote:
 Package: rtorrent
 Severity: grave
 Version: 0.7.9-2+b2
 Architecture: i386
 
 version of libtorrent10 - 0.11.9-1.1 (lenny)
 
 If command 'fi.get_filename_last' received from SCGI interface, then
 rtorrent crashes. Version rtorrent/librtorrent from experimental
 works fine.
 
Hello,

Sorry, I'm short of time (I'm in finals) right now. Experimental version
is stable enough right now like to use it on unstable but no to use it
on lenny so I guess this will make yet another stable release without
rtorrent. I'm not in position to upload new binaries to take into
consideration for lenny next release.

I think (differently to what upstream thinks) that 0.12.4/0.8.4 is more
stable that 0.12.2/0.8.2 (which doesn't build in bsd environments and
don't have several fixes that *.*.4 does have).

Please if any of you have something against me uploading experimental
release to unstable let me know, if not I'm gonna send it to Dmitry
(hoping he's ok with this) to upload it to unstable and leave lenny
without rtorrent/libtorrent (there's not yet a new-release stable enough
for lenny anyway, I think)

Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118
http://ghostbar.ath.cx/about - http://debian.org.ve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkk5zgQACgkQOKCtW8rKsRhKYgCfcftexN86wgomVex3lhT5/TYX
j+gAn0TWWn4NP382tpBm2rjO9Kdd97J2
=XltO
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#506396: new version rtorrent available in upstream

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

tags 506396 pending
quit

Dmitry E. Oboukhov wrote:
 Package: rtorrent
 Version: 0.7.9
 
 Please, package new version rtorrent:
 http://libtorrent.rakshasa.no/
 Stable Release 
 
 * libtorrent-0.12.2.tar.gz
 * rtorrent-0.8.2.tar.gz 
 
 Unstable Release
 
 * libtorrent-0.12.4.tar.gz
 * rtorrent-0.8.4.tar.gz 
 
 many gui-systems for rtorrent (rtgui, rtwi, etc) have 
 depends to rtorrent 0.8.

Hello Dmitry,

Since something like 2 days ago there are packages ready for
0.12.4/0.8.4 [0]. Right now they're waiting for my sponsor to get them
to the archive (experimental).

Since 2 days ago, as well, Jaris upgraded stable to 0.12.3/0.8.3, I
packaged  and yesterday he made a downgrade to 0.12.2/0.8.2 (these goes
to unstable) but I haven't make the downgrade yet in my git[3](but not
pushed 0.8.3 when I noticed this) since I haven't got time to do this
and probably don't gonna have the time until monday (my country is on
elections this weekend and I'm volunteer).

Anyway, experimental packages are tested and ready to be uploaded [1][2]

Regards.

[0] http://ghostbar.ath.cx/node/78
[1] http://debian.rivco.info/libtorrent/0.12.4-1.exp/libtorrent_0.12.4-1.dsc
[2]
http://debian.rivco.info/rtorrent/0.8.4-1.exp/rtorrent_0.8.4-1.dsc
[3]http://git.debian.org/?p=collab-maint/libtorrent.git;a=commit;h=79571f3d3be390f615fd77e60cb2e4371f5cb60f
- --
Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118
http://ghostbar.ath.cx/about - http://debian.org.ve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkkm3X0ACgkQOKCtW8rKsRiHpgCffuT4eDJcm9eU0zLhVIS7Flv5
DEgAn39cvtt2qW19Ljs8vXZ/C+s6I8EK
=8cAA
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#506396: new version rtorrent available in upstream

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dmitry E. Oboukhov wrote:
 If You want, I can become a sponsor for this upload(s) :)

Oh please, I would love that :)

http://debian.rivco.info/libtorrent/0.12.4-1.exp/libtorrent_0.12.4-1.dsc

There's a change of name for binary libtorrent10 to libtorrent11 so will
be delayed a little in NEW then I'll let you now for uploading rtorrent.

Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. GPG 0xCACAB118
http://ghostbar.ath.cx/about - http://debian.org.ve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkknKUgACgkQOKCtW8rKsRjBeACgz7R0hdPcjKYjW6s2OIYDPBBe
hwAAoLORkxiSHsBPADDCvhuUrSuufipO
=ieIT
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#505251: ITP: libnet-amazon-s3-tools-perl -- Command line tools for Amazon AWS S3

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Charles Plessy wrote:

 I did not manage to set ACLs with s3cmd, so I did a Google search and found
 this set of tools that fit my purpose. Is the Perl team interested in having 
 it
 in its repository ? If not, another possibility would be to have it on
 collab-maint or in a co-maintained repository dedicated to computer clouds. I
 strongly believe in team work, and if nobody shows interest to co-maintain, I
 will simply conclude that the package is too trivial and not interesting 
 enough
 for Debian anyway, and close the ITP.

Anyone using some perl module pkg-perl will be glad to have it in its
repository as the wiki page says :)

http://wiki.debian.org/Teams/DebianPerlGroup?highlight=(perl)

Regards.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkkY7SgACgkQOKCtW8rKsRjQhgCg2FN/0u9zYs0Cu3BUIxP1HYeo
RRYAoJzSXzobPe/FCxXwv/I7ftJMhWI6
=/Uc6
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#450907: fireworxx shows live screen contents when xcompmgr is running

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

reassign 450907 xcompmgr
quit

Hello,

I'm reassigning this bug since there's no solution from xscreensaver
side and this only happens when xcompmgr is running.

Please see the feedback at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450907

Regards.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkkO4bUACgkQOKCtW8rKsRjOdwCaAgYZ2gxKsnyWGG694hImduYH
3o8AoKlwzk3XlB86NlE+TIes75kIxu/w
=G+Ow
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#504262: xscreensaver: fails to remove menu items on uninstall

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Greg Auger wrote:
 Package: xscreensaver
 Version: xscreensaver
 Severity: important
 
 When xscreensaver is removed from the system, it leaves several menu items in 
 the 

gnome menu. On my system, there were nine items under 'Other' after
uninstalling.

That's because you just removed xscreensaver, you need to remove as well
the packages of the hacks. Anyway, if you're using gnome-screensaver or
kscreensavers they use those files.

If you want them removed then remove xscreensaver-* packages. This is
not a bug.

Regards.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkkNZBgACgkQOKCtW8rKsRgkSgCfXBKFmZwP2l/jWF26KpJFw3TN
amAAn1NAfHEklSkXwaR5tZ59/4L6SBhW
=3TRC
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#504241: ITP: libb-hooks-endofscope-perl -- Execute code after a scope finished compilation

[Jose Luis Rivas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: wnpp
Severity: wishlist
Owner: Jose Luis Rivas [EMAIL PROTECTED]

* Package name: libb-hooks-endofscope-perl
  Version : 0.04
  Upstream Author : Florian Ragwitz [EMAIL PROTECTED]
* URL : http://search.cpan.org/dist/B-Hooks-EndOfScope/
* License : Perl (GPL/Artistic)
  Programming Lang: Perl
  Description : Execute code after a scope finished compilation

This module allows you to execute code when perl finished compiling the
surrounding scope.

This packages is a build-depend of the new upstream version of
libnamespace-clean-perl and will be maintained by the debian-perl
group.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkkNEHYACgkQOKCtW8rKsRixcwCfeFsaVhd8jvLb3Uwtrc8jx35G
3k8AoIQ9UIafsT55HEScGDF8xhcaKZLa
=1etg
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#497405: [xscreensaver] fails to start when using dual head with different resolutions

[Jose Luis Rivas Contreras]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jamie Zawinski wrote:
 Fixed in 5.07.
 
 Come on already, Debian people -- will you please push out the new
 version so that we stop getting these reports?
 
 
 
Sorry Jamie, I already sent it out to my sponsor, don't know why's the
delay.

- --
Jose Luis Rivas. San Cristóbal, Venezuela. PGP: 0xCACAB118
http://ghostbar.ath.cx/{about,acerca} - http://debian.org.ve
`ghostbar' @ irc.debian.org/#debian-ve,#debian-devel-es
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAki8b4cACgkQOKCtW8rKsRi2YQCfd/tZm3dABtgEJa6++WVCi0nZ
0V0Amwa5JBMBJMpJDEtqejreV4I6Xffa
=x05a
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#494725: RFA: gkrellm -- The GNU Krell Monitors

[Jose Luis Rivas Contreras]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: wnpp
Severity: normal

With a single process, gkrellm manages multiple stacked monitors and
supports applying themes to match the monitors appearance to your window
manager, Gtk, or any other theme.

I'm no longer using gkrellm in my machines, right now is working with a
patch for support of sysfs battery from Leo L. Schwab. (I already sent
it to upstream but haven't respond anything).

At the date there's a RC-bug already fixed in the GIT repository [0] and
sent to my sponsor awaiting to get uploaded [1].

Upstream doesn't seem inactive, even when I sent the new patch for sysfs
battery support and haven't respond anything (the patch is kind of big).

[0] git://git.debian.org/git/collab-maint/gkrellm.git
[1] http://debian.rivco.info/gkrellm/2.3.1-7/gkrellm_2.3.1-7.dsc
- --
Jose Luis Rivas. San Cristóbal, Venezuela. PGP: 0xCACAB118
http://ghostbar.ath.cx/{about,acerca} - http://debian.org.ve
`ghostbar' @ irc.debian.org/#debian-ve,#debian-devel-es
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkigh78ACgkQOKCtW8rKsRhUswCfQYIfCGhVNCbuBJdfk7IVvsJj
SdwAnihPXKyHxblhGPnbwqGvry4Nx0EV
=gdVF
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#492068: Doesn't work for me

[Jose Luis Rivas Contreras]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Javier Barroso wrote:
 Hi, I got the same bug
 
 After applying the patch in
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492068#59 I get with
 dpkg-buildpackage:
 
 screens.c: In function ‘update_screen_layout’:
 screens.c:894: error: expected declaration or statement at end of input
 screens.c:894: error: expected declaration or statement at end of input
 
 Any workaround ?
 
 Thank you!
 
 
Hello Javier,

We didn't found that bug while compiling, in fact that patch is already
part of upstream so I doubt too many people passed that bug without
notice it. Could you please re-check?

Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. PGP: 0xCACAB118
http://ghostbar.ath.cx/{about,acerca} - http://debian.org.ve
`ghostbar' @ irc.debian.org/#debian-ve,#debian-devel-es
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkigvdMACgkQOKCtW8rKsRi1DwCgpQT2LazVxIiWSZ96Lcnny7sp
rNsAoM+rpbUDzzSb7q4ZQ2WUzlyMCqxi
=ezVD
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#484112: [xscreensaver-gl] flurry hack causes the whole system to freeze

[Jose Luis Rivas Contreras]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ana Guerrero wrote:
 Hola José Luis,
 
 On Tue, Jun 17, 2008 at 02:35:32PM -0430, Jose Luis Rivas Contreras wrote:
 Tormod Volden wrote:
 Thanks for your report. The problem has also been reported in
 https://bugs.launchpad.net/bugs/224065

 For now, we'll demote flurry to the -extra package so that it is not
 installed by default.


 This is done in the git-version, I'll reassign this bug to xss-gl-extra
 when that version gets uploaded.

 
 This was like a month ago.
 Could you please address this problem and the serious probleems in
 xscreensaver-gl? My main concern is due to kdeartwork not being able to
 migrate to testing because of this :/
 
 Ana
Hi Ana,

Of course, I was just waiting to get it uploaded as well with the new
patch for other issues of xscreensaver, this weekend is the deadline for
getting it ready and working, so with what's done already xscreensaver
will be sent to a sponsor to get uploaded.

Thanks for asking :)
Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. PGP: 0xCACAB118
http://ghostbar.ath.cx/{about,acerca} - http://debian.org.ve
`ghostbar' @ irc.debian.org/#debian-ve,#debian-devel-es
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkh89eAACgkQOKCtW8rKsRjd9gCgzNzi6zcHyUnVPIExQ16wPfop
EzMAn3QsSAPkH+az/HnqdhYpYYAYyStw
=ln7W
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]