Bug#319031: Crash on File->Open...

2005-07-19 Thread Max Alekseyev
Package: kino Version: 0.76-2 Severity: grave Justification: renders package unusable Run kino, click File->Open..., kino crashes. Backtrace: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 46912583339152 (LWP 12836)] 0x2e18ac00 in strlen () from /lib/libc.so.6

Bug#319031: Crash on File->Open...

2005-07-19 Thread Max Alekseyev
Paul Brossier wrote: Could you try building this version: http://piem.org/debian/kino/ ? It didn't help. Kino 0.76-3 is still crashing. Backtrace is essentially the same: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 46912583339200 (LWP 3854)] 0x2e18ac00 in

Bug#319031: Crash on File->Open...

2005-07-21 Thread Max Alekseyev
Paul Brossier wrote: - do you have alsa up and running? (contents of /proc/asound/cards) $ cat /proc/asound/cards 0 [Unknown]: EMU10K1 - SB Live [Unknown] SB Live [Unknown] (rev.8, serial:0x80271102) at 0xb400, irq 16 - what does recompiling gives without the

Bug#319031: Crash on File->Open...

2005-07-22 Thread Max Alekseyev
Paul Brossier wrote: the backtrace actually suggests that the bug is somewhere in gtk. what does it look like with libtgtk2.0-0-dbg installed as suggested at http://bugs.debian.org/315083 ? Here it comes: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 4691258334329

Bug#319031: Crash on File->Open...

2005-07-22 Thread Max Alekseyev
Paul Brossier wrote: #8 0x2bbba435 in IA__gtk_file_chooser_dialog_new ( title=0x7fff , parent=0x1, This `title=0x7fff` is odd since in the following function arguments `title` is show as expected #7 0x2bbba361 in gtk_file_chooser_dialog_new_valist (

Bug#299734: broken on 64-bit systems

2005-08-03 Thread Max Alekseyev
Peter Karlsson wrote: Unfortunately, GoldEd+ development seems to have more or less stopped as well. First of all, there is quite fresh snapshot golded+1.1.5-20050419.tgz available for download at http://golded-plus.sourceforge.net/download.html Second, I've made two patches available at ht

Bug#271123: fixed in upstream 1.1.5

2005-10-13 Thread Max Alekseyev
Hi! I believe this bug was fixed in upstream version 1.1.5. While it is not yet released, snapshots are available from http://sourceforge.net/projects/golded-plus/ Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#299734: broken on 64-bit systems

2005-03-15 Thread Max Alekseyev
Package: goldedplus Version: 1.1.4.7+1.1.5.20031012-1 Severity: grave Justification: renders package unusable File: /usr/bin/golded There are multiple problems with goldedplus on 64-bit systems such as segfaults (see bug 251856 as well) and hanling data files. In particular, while golded starts OK

Bug#299734: broken on 64-bit systems

2005-03-16 Thread Max Alekseyev
retty still alive in xUSSR. ;) Max Peter Karlsson wrote: Max Alekseyev: There are multiple problems with goldedplus on 64-bit systems such as segfaults (see bug 251856 as well) and hanling data files. Yeah, this probably is the same problem as in bug 251856. The program was simply not designed for 6

Bug#299902: under debian-amd64 XNC crashes when skin is different from default

2005-03-17 Thread Max Alekseyev
Package: xnc Version: 5.0.4-2 Severity: grave Justification: causes non-serious data loss To reporduce the bug: 1. Run XNC and go to Options -> Configuration -> GUI plugin (skin) and change to anything different from default (e.g., Five Look) 2. Restart XNC $ xnc Plugin LookFive v.1.1.2 registered

Bug#300347: ver. 5.6.1 segfaults on debian-amd64 / new upsteam ver. 5.6.2 is available with many AMD64-related fixes

2005-03-18 Thread Max Alekseyev
Package: biew Version: 5.6.1-1 Severity: grave Justification: renders package unusable Version 5.6.1-1 currently available at debian-amd64 repository is broken on debian-amd64. It segfaults on attempt to open any file. At the same time there is a new upstream version 5.6.2 available at http://sour

Bug#322897: azureus: Unusable because of constant segmentation faults

2005-08-15 Thread Max Alekseyev
Justin Pryzby wrote: Can you provide a GDB backtrace as well? $ gdb $(which azureus) > r ... bt $ file $(which azureus) /usr/bin/azureus: Bourne shell script text executable How can I run shell script under gdb ? It would be ideal if you could locally compile the package with

Bug#322897: azureus: Unusable because of constant segmentation faults

2005-08-16 Thread Max Alekseyev
Justin Pryzby wrote: A shellscript is segfaulting? Or a command it calls is segfaulting? If so, which? Add "set -x;" as the second line of the script. Segfaulting is the following command that is run from the script exec java -Djava.library.path=/usr/lib \ -classpath $JARS:Azureus2.

Bug#339419: d4x crashes in strlen () from /lib64/libc.so.6

2005-11-18 Thread Max Alekseyev
Cai Qian wrote: d4x on attempt to process a link like ftp://a5:[EMAIL PROTECTED]/e/edbf5d055412df097e9ab4a16a886361/AB_091__E_.part05.rar Please note that this particular link is already expired (i.e., login is incorrect and d4x survives). To get a fresh one, open http://www.filefactory.com/g

Bug#339419: d4x crashes in strlen () from /lib64/libc.so.6

2005-11-18 Thread Max Alekseyev
Cai Qian wrote: To reproduce: 1) open http://www.filefactory.com/get/f.php?f=26f737dbc373854c4a38ac77 in a browser 2) wait 15 sec 3) click at "Click here to continue to the download page." 4) wait another 15 sec 5) find a link to ftp under "FileFactory FTP -- Click here to download" 6) try to do

Bug#339419: d4x crashes in strlen () from /lib64/libc.so.6

2005-11-19 Thread Max Alekseyev
Cai Qian wrote: This bug is caused by mismatch versions between libgtk2.0-0 (2.8.3-1) and libglib2.0-0 (2.6.10-1) in unstable. If use both 2.8 or 2.6, d4x will not crash. Could you provide a simpler testcase? Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe".

Bug#310318: "wget -N" reports "File already exists"

2005-05-23 Thread Max Alekseyev
Hrvoje Niksic wrote: I cannot repeat this bug. I also cannot find this error message ("File already exists") in Wget source code, nor in the Debian patch. $ apt-get source wget Reading Package Lists... Done Building Dependency Tree... Done Need to get 1341kB of source archives. Get:1 ftp://f

Bug#343250: [Bulk] Re: Bug#343250: upx-ucl-beta: broken on 64-bit systems

2005-12-16 Thread Max Alekseyev
Robert Luberda wrote: Thanks for your report. I've just uploaded new CVS snapshot of upx-ucl-beta (1.94+0.20051214cvs-1). Could you please check if the problem still exists in that version? It fails to be build from sources on amd64 with the following error: g++ -O2 -g -DWITH_UCL -o packmast.

Bug#343250: upx-ucl-beta: broken on 64-bit systems

2005-12-18 Thread Max Alekseyev
Robert Luberda wrote: I've just uploaded 1:1.94+0.20051214cvs-2, which fixes the error. The patch is very simple, I'm attaching it in case you didn't want to wait for autobuilders and recompile the package yourself. Please check if this version works for you on amd64. No. It reports: upx: ut

Bug#339419: d4x crashes in strlen () from /lib64/libc.so.6

2005-12-21 Thread Max Alekseyev
Loïc Minier wrote: Please provide a backtrace of the crash with libglib2.0-dbg and libgtk2.0-dbg installed. If these libraries don't appear in the backtrace, it's unlikely a Glib or Gtk bug. They called libglib2.0-0-dbg and libgtk2.0-0-dbg here. These are new backtraces from all 4 threads:

Bug#339419: d4x crashes in strlen () from /lib64/libc.so.6

2005-12-21 Thread Max Alekseyev
Steve Langasek wrote: This is the output of valgrind with libc6-dbg: Ok, most of this looks like pretty typical garbage output, with a few messages related to locales and themes that I don't usually see. Are you using any particular gtk theme here? I use Smokey Blue theme. Do you see the

Bug#339419: d4x crashes in strlen () from /lib64/libc.so.6

2005-12-22 Thread Max Alekseyev
Steve Langasek wrote: Well, after fixing the dialog crash, the link from the bug report works fine for me on alpha. Perhaps you could test using the patch I sent in the last mail, to confirm the bug still exists? Unfortunately it still crashes even with the patch. Max -- To UNSUBSCRIBE,

Bug#368101: (no subject)

2006-05-25 Thread Max Alekseyev
I see this segfault on debian-amd64/unstable as well. Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]