-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, I'm using this same version in unstable and i386 and can't reproduce
this issue surfing the specified web.
Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. PGP: 0xCACAB118
http://ghostbar.ath.cx/{about,acerca} - http://debian.org.ve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pierre Habouzit wrote:
On Fri, May 23, 2008 at 02:55:33AM +, Jose Luis Rivas Contreras wrote:
Pierre Habouzit wrote:
Package: xscreensaver
Version: 5.05-1
Severity: grave
Tags: security
Justification: user security hole
When xrandr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pierre Habouzit wrote:
Package: xscreensaver
Version: 5.05-1
Severity: grave
Tags: security
Justification: user security hole
When xrandr is used to resize the screen on my laptop (because I use
an external 16:9 lcd screen at work, and the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Juergen Kosel wrote:
Hello,
I have started interaggreagate to reproduce the problem again.
It seems to me that it is related to compiz: If compiz doesn't run,
everything is fine.
But with compiz there are also other screensavers which cause
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Juergen Kosel wrote:
Package: xscreensaver
Version: 5.04-2
Severity: critical
Justification: breaks the whole system
Hello,
when /usr/lib/xscreensaver/interaggregate was started,
the local console with gnome session became unusable.
From a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tags 474852 pending
thanks
I already built a fixed version and is available in the meanwhile at
http://debian.ghostbar.ath.cx/rtorrent/0.7.9-2 .
Soon will be uploaded to unstable.
Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. PGP:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vincent Crevot wrote:
tags 471920 -pending
thanks
I just had a look at the diff for 5.05-2; the changelog is wrong as the
patch in #473681 does _not_ fix #417920. See my previous replies to this
bug. Sorry for not being very clear on this - at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vincent Crevot wrote:
Package: xscreensaver
Version: 5.05-1
Followup-For: Bug #471920
Ok, I have narrowed down the bug to the new xinerama sanity code
introduced in 5.05. I'm using the nvidia binary driver in clone mode
(same picture displayed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It just built fine in my pbuilder fully updated in amd64. Here's a quote
of the relevant part:
==
'blib/lib', 'blib/arch') t/*.t
t/00-load.# Testing App::Ack 1.72, Perl 5.008008, /usr/bin/perl
ok
t/ack-1...ok
t/ack-a...ok
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tags 453193 patch
quit
Hi,
{perl:Depends} it's not supposed to be versioned, perl should go along
if you want it with a version, the attached patch should fix this issue.
Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. PGP: 0xCACAB118
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
severity 458145 wishlist
quit
Thomas Koenig wrote:
Subject: webcollage installed without prompting
Package: xscreensaver
Version: 5.04-2
Severity: grave
Hi,
I just found that webcollage had been installed on my system
with the latest
Emil wrote:
Package: xscreensaver
Version: 5.04-2
Severity: grave
Justification: renders package unusable
Launching xscreensaver-demo gives this:
$ xscreensaver-demo
antmaze: couldn't allocate color black: using black.
antmaze: couldn't allocate black either!
When xscreensaver
tags 451790 pending
quit
Ok, I found out wich is the problem, this is because the client needs to
be compiled with -fno-stric-aling too, so with the new upload this
should be fixed.
Regards,
Jose Luis.
--
ghostbar on debian linux 'sid' 2.6.22 x86_64-SMP - #382503
Weblog:
Lucas Nussbaum wrote:
Package: xscreensaver
version: 5.03-3
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20071106 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in sid, your package failed to build on i386.
Is build-depending on gdm really
Lucas Nussbaum wrote:
Package: xscreensaver
version: 5.03-3
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20071106 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in sid, your package failed to build on i386.
Is build-depending on gdm really
Hi Kurt Dean,
I'm checking right now this issue, I haven't get it and I'm using
amd64... Maybe it's related to the gcc version? I will check this
further trying to get the error.
Regards,
Jose Luis.
--
ghostbar on debian linux 'sid' 2.6.22 x86_64-SMP - #382503
Weblog: http://ghostbar.ath.cx/
Hi Kurt,
How does you get this error? When? Some specific shortcut combination?
Regards,
Jose Luis.
--
ghostbar on debian linux 'sid' 2.6.22 x86_64-SMP - #382503
Weblog: http://ghostbar.ath.cx/ - http://linuxtachira.org
http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es
San
severity 450907 important
quit
Hi,
I do not really think this is a serious bug but important since does
lock the screen and I do not believe showing data is a security issue.
Regards,
Jose Luis.
--
ghostbar on debian linux 'sid' 2.6.22 x86_64-SMP - #382503
Weblog: http://ghostbar.ath.cx/ -
Kurt Roeckx wrote:
On Thu, Nov 22, 2007 at 10:17:10AM -0400, Jose Luis Rivas Contreras wrote:
Hi Kurt,
How does you get this error? When? Some specific shortcut combination?
I don't touch anything at all. I'm just seeding a few debian iso
images, and after some time I get that error. I
Francesco Potorti` wrote:
I do not know whether this is a problem of the proprietary Nvidia driver
that I am using or not, but since this is serious I am reporting before
investigating more thoroughly. Any GL screensaver that I have tried
crashes the X server. At the end I append the X
Benjamin Seidenberg wrote:
Package: xscreensaver
Version: 5.03-3
Severity: serious
Tags: security
Justification: Security Hole - Unintended information disclosure
When xcompmgr is running, the fireworxx hack will display over the live screen
(including any changes post screen-lock). This
Francesco Potorti` wrote:
Maybe it should be closed. As I was saying, the latest nvidia
proprietary driver does not exhibit any problem. It could have been a
bug on their part, which now they solved.
I'm closing it as Francesco requested, in case that someone experiment
the same issue feel
Francesco Potorti` wrote:
I do not know whether this is a problem of the proprietary Nvidia driver
that I am using or not, but since this is serious I am reporting before
investigating more thoroughly. Any GL screensaver that I have tried
crashes the X server. At the end I append the X
reassign 448157 rss-glx
thanks
Hi,
There's no such `xscreensaver-gl-extras' package, xscreensaver-gl-helper
is installed with `xscreensaver-gl' so `rss-glx' should really suggests
xscreensaver-gl instead of xscreensaver.
[EMAIL PROTECTED]:~$ dpkg -S /usr/bin/xscreensaver-gl-helper
Nico Golde wrote:
Hi Jose,
* Jose Luis Rivas Contreras [EMAIL PROTECTED] [2007-10-27 17:40]:
There's no such `xscreensaver-gl-extras' package, xscreensaver-gl-helper
is installed with `xscreensaver-gl' so `rss-glx' should really suggests
xscreensaver-gl instead of xscreensaver.
Yes
reassign 448157 xscreensaver
quit
Ari Pollak wrote:
The point here is that xscreensaver should not unlock the screen when
missing xscreensaver-gl-helper, it should just display a blank
screensaver. rss-glx does not NEED to be run with xscreensaver-gl-helper
as it's perfectly feasible to run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
package xscreensaver
severity 430848 important
tags 430848 unreproducible
quit
Sorry, I got them working, this bug it seems as doesn't exists... Try
purging and reinstalling xscreensaver please:
[EMAIL PROTECTED]:~$ xscreensaver-command -restart
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
retitle 429259 amarok: crashes all X window system
quit
- --
ghostbar on Linux/Debian 'sid' i686 - #382503
Weblog: http://ghostbar.ath.cx/ - http://linuxtachira.org
http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es
San Cristóbal,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I upgraded my graphic card drivers and amarok stops crashing, so this
bug doesn't exists anymore.
But I don't understand yet why amarok crashes because of my graphic
drivers... Anyway, you can close this bug, sorry.
Jose Luis.
- --
ghostbar on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
package rubrica
tags 426846 +patch
quit
Hi Sebastien,
There's a patch attached, you only need to add `libxml-parser-perl' as
Build-Depend and then everything works as should. I tested this on a
i386 pbuilder and works just fine.
Regards,
Jose Luis.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
package libpod-webserver-perl
merge 423804 425902
tags 423804 +patch
quit
Hi Alejandro,
Here's a patch that fixes your FTBFS, there's no need to delete the
`make test' command, in fact that would be wrong.
The patch moves `t/03_daemon.t' to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
package libflickr-api-perl
tags 427318 +pending
quit
Lucas Nussbaum escribió:
Package: libflickr-api-perl
version: 0.08-1
Severity: serious
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in sid, your package failed to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
package camstream
tags 427275 +patch
quit
Added build-depend on linux-kernel-headers. Patch attached. Now builds
ok, tested on pbuilders.
Regards,
Jose Luis.
- --
ghostbar on Linux/Debian 'sid' i686 - #382503
Weblog: http://ghostbar.ath.cx/ -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
package centericq
tags 424654 patch
quit
Hi,
This problem is fixed changing on Build-Depends from `libcurl3-dev' to
`libcurl4-gnutls-dev'. There's nothing else to do so I doesn't consider
necessary to make a diff to attach to this email.
Regards,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
package aprsd
tags 427265 +patch
quit
Hi, this is fixed deleting the header `linux/sys.h' since isn't needed
anymore with kernels higher to 2.6.19.
Regards,
Jose Luis.
- --
ghostbar on Linux/Debian 'sid' i686 - #382503
Weblog:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey, BTW, I double checked and servers.cpp have the same problem, now
builds ok on pbuilder. Attached the patch for servers.cpp.
Regards,
Jose Luis.
- --
ghostbar on Linux/Debian 'sid' i686 - #382503
Weblog: http://ghostbar.ath.cx/ -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
package arptables
tags 427264 +patch
quit
Hi,
This problem is fixed deleting linux/config.h header, builds ok on
pbuilders.
Regards,
Jose Luis.
- --
ghostbar on Linux/Debian 'sid' i686 - #382503
Weblog: http://ghostbar.ath.cx/ -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg Wooledge escribió:
Package: rtorrent
Version: 0.7.4-2
Followup-For: Bug #423107
I get the same symptom as the original reporter. Running rtorrent clears
the screen, switches the terminal into some non-canonical mode, and writes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Ablassmeier escribió:
Package: libfile-spec-perl, libpathtools-perl
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-file-conflict
Justification: Policy violation, see section 7.2
hi,
both libfile-spec-perl and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tags 423556 pending
thanks
C. Dominik Bodi escribió:
Package: rtorrent
Version: 0.7.4-1+b1
Severity: grave
Justification: renders package unusable
rtorrent 0.7.4-1+b1 fails to install on sid. It depends on libcurl3
which is no longer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: pbuilder
Version: 0.166
Severity: grave
Justification: Doesn't build anything and gives non-existent error
Hi, I'm using sid and I cannot build anything, gives me some error
related to control file. I've tested with packages already on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Skibbi escribió:
rtorrent fails to start with following error:
rtorrent: symbol lookup error: rtorrent: undefined symbol:
_ZN7torrent21max_download_unchokedEv
Hi, does you have any `~/.rtorrent.rc' ? If this is the case then will
be helpful to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
License is referenced in package/README as well in
package/debian/copyright. I believe there's no violation of policy here.
Original tarball doesn't have the copy of the license. Must *-perl
packages doesn't have the COPYING or LICENSE file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Kowalik escribió:
tags 414292 + patch
thanks
Hi,
Attached is a patch to fix the postinst and postrm for this package
to use, firstly to use /bin/sh, since you don't use any bash-specific
features, secondly to make use of set -e,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Version: 2.0.0-1
Hi, list-2.0.0-1 doesn't have this bug and was in debian repositories
before you submit this bug. Please, could you do your tests against
unstable packages? You're opening an unnecessary and non-existent bug
with high severity.
If
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Paillard escribió:
Package: rtorrent
Version: 0.7.1-1
Severity: grave
Justification: renders package unusable
The last rtorrent (0.7.1-1) is currently not installable, because it
depends on libtorrent10, a package which doesn't exist.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
package libtorrent9
tags 401006 upstream unreproducible
thanks
Hi, this is a problem on a Debian system, I can't confirmed and I have a
2.6.18-3-686 kernel. Could anyone confirmed it?
- Mensaje original
Asunto: Bug#401006:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
package libtorrent9
severity 401006 important
thanks
This problem isn't confirmed and is unreproducible so I downgrade the
severity.
If anyone can confirm this issue, please let me know.
Thanks and Cheers!!
- --
ghostbar @ linux/debian 'unstable'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kurt Roeckx escribió:
On Mon, Dec 04, 2006 at 05:01:38PM -0400, Jose Luis Rivas Contreras wrote:
Can you please give some more information? What error does it give?
From what version to what version are you trying to upgrade?
Kurt
Hi, I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Goswin von Brederlow escribió:
Package: rtorrent
Version: 0.6.2-1
Severity: serious
Hi,
the rtorrent package seems to be missing the upstream changelog completly.
MfG
Goswin
Yes, in the upstream version the changelog have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
package rtorrent
severity 388842 minor
thanks
I don't think this is a policy violation, so I'm changing the severity
from serious to minor.
- --
~ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503
http://ghostbar.ath.cx/ -
53 matches
Mail list logo
