Bug#609535: psiconv: magick/semaphore.c:526: LockSemaphoreInfo: Assertion `semaphore_info->signature == 0xabacadabUL' failed.
On Thu, Jan 27, 2011 at 06:43:27AM +, Adam D. Barratt wrote: > On Mon, 2011-01-24 at 21:00 +, Adam D. Barratt wrote: > > On Mon, 2011-01-24 at 20:53 +0100, Patrik Fimml wrote: > > > I'm fine with the patch for abiword, but not a DD so I can't upload it > > > myself. > > > > I'd be happy to NMU it to t-p-u if that would help, assuming I can > > persuade someone else on the release team to approve it - offering to > > sponsor an upload when I've already got a patched source package locally > > and would be rebuilding it anyway seems a little redundant. > > Please let me know if you'd like me to do that. Obviously if you'd > prefer to find a sponsor and upload yourself then that's fine, but it > would be helpful if that could be within the next couple of days so that > we can get the psiconv situation resolved. Sorry, I did not realise you were implicitly asking for my approval! Please go ahead. Best regards, Patrik -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#609535: psiconv: magick/semaphore.c:526: LockSemaphoreInfo: Assertion `semaphore_info->signature == 0xabacadabUL' failed.
On Mon, Jan 24, 2011 at 07:40:17PM +, Adam D. Barratt wrote: > On Sun, 2011-01-23 at 20:15 +, Adam D. Barratt wrote: > > [re-sending to fix abiword CC] > > > > On Tue, 2011-01-18 at 12:55 +0100, Julien Cristau wrote: > [...] > > > Another option would be to rebuild abiword and gnumeric without psiconv > > > support, if that's easy? > > > > I've verified that with the attached patches, both packages at least > > build on squeeze without any apparent sign of using psiconv. (They're > > both already out of sync wrt unstable so would need tpu uploads). > > abiword / gnumeric maintainers: Do you have any opinions on the > suggested patches? If you're okay with them, would you be able to > perform a testing-proposed-updates upload in the next couple of days > incorporating the patch? I'm fine with the patch for abiword, but not a DD so I can't upload it myself. Regards, Patrik -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#573964: abiword: Abiword does not start - wrong libgoffice version
severity 572043 grave forcemerge 572043 573964 thanks Please check existing bug reports first - for all bugs, but for grave and serious bugs even more carefully! Thanks, Patrik -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#561629: uninstallable in sid
On Sun, Jan 03, 2010 at 06:55:22PM +0900, Hideki Yamane (Debian-JP) wrote: > Is the patch you mean like below? > > [...] Yes, that should suffice. Patrik signature.asc Description: Digital signature
Bug#561629: gnome-office: uninstallable in sid
On Fri, Dec 18, 2009 at 09:50:44PM +0100, Laurent Bonnaud wrote: > The following packages have unmet dependencies: > gnome-office: Depends: abiword-plugin-goffice (>= 2.6) but it is not > installable Sorry for not giving an advance notice. The goffice plugin is now shipped in the "abiword" binary package, so you should probably just depend on abiword (>= 2.8) instead. Kind regards, Patrik Fimml (abiword maintainer) signature.asc Description: Digital signature
Bug#519564: Fixed in 2.6.8
Hey, can you confirm this problem is resolved with abiword-2.6.8? Patrik signature.asc Description: Digital signature
Bug#519564: Fixed in 2.6.8
tags 519564 + fixed-upstream thanks It seems you don't have to debug any further, you can ignore my previous request. The issue seems to be that some GTK functions may be called before g_thread_init(). It has been fixed in abiword SVN with r25684 [1], which is contained in 2.6.8. [1] http://www.abisource.com/viewvc?view=rev&revision=25684 Patrik signature.asc Description: Digital signature
Bug#519564: abiword: hangs on startup
On Fri, Mar 20, 2009 at 05:05:44PM -0400, Brent S. Elmer wrote: > Here it is. Sorry, I have to request some more debugging from you again, as I cannot reproduce it here. $ gdb abiword (gdb) set pagination off (gdb) set logging on (gdb) b main (gdb) run (gdb) p g_thread_self() (gdb) watch default_main_context (gdb) cont (gdb) watch default_main_context->owner (gdb) commands 3 > p *default_main_context > bt full > cont > end (gdb) cont [wait some time until nothing happens anymore and abiword hangs again] [CTRL-C] (gdb) bt full (gdb) p *default_main_context (gdb) p g_thread_self() Thanks, Patrik signature.asc Description: Digital signature
Bug#514525: Fixed upstream
tags 514525 + fixed-upstream thanks Upstream has a duplicate of this bug which was fixed in 2.6.5: http://bugzilla.abisource.com/show_bug.cgi?id=11789 The fix is the same. Regards, Patrik signature.asc Description: Digital signature
Bug#519564: [abiword] toolbars grayed out
Please run gdb abiword again, interrupt it when it hangs, and do the following (please attach the terminal output): (gdb) frame 2 (gdb) p *context (gdb) frame 0 (gdb) step If stepping hangs, you can stop debugging. If it doesn't, please step multiple times (10-20) so I can have a guess where the program's stuck. Kind regards, Patrik signature.asc Description: Digital signature
Bug#519564: [abiword] toolbars grayed out
On Thu, Mar 19, 2009 at 09:14:19PM -0400, Wendy Elmer wrote: > There is no difference when running it as you said. There is no output > to the terminal. I have used abiword before. Thanks for trying. > Whenever I click on the X to kill the abiword window it doesn't > respond and a little while later a window pops up saying the > application is not responding do I want to force quit. Please get me a backtrace of where abiword hangs. You'll have to recompile abiword with debugging symbols and install debugging symbols for various libraries. In short (http://wiki.debian.org/HowToGetABacktrace has background information): $ cd /tmp [or somewhere else where you don't mind stuff lying around] $ sudo aptitude install build-essential fakeroot $ sudo apt-get build-dep abiword $ DEB_BUILD_OPTIONS=nostrip,noopt apt-get --build source abiword $ sudo dpkg -i abiword*.deb $ sudo aptitude install libglib2.0-0-dbg libgtk2.0-0-dbg $ gdb abiword [...] (gdb) set logging on (gdb) set pagination 0 (gdb) run [wait until abiword hangs, interrupt it by hitting Ctrl+C in the terminal] (gdb) thread apply all backtrace full (gdb) quit Do you really want to quit? yes ... and attach gdb.txt, which is located wherever you started gdb, in this case probably /tmp/gdb.txt. Kind regards, Patrik signature.asc Description: Digital signature
Bug#519564: [abiword] toolbars grayed out
On Fri, Mar 13, 2009 at 10:33:20AM -0400, Brent S. Elmer wrote: > When I open abiword, there are no toolbars. I tried opening it from the > command line to see if > there are any errors written and none were. I am attaching a screenshot. Try running abiword without your normal preferences and with verbose messages, i.e. from the terminal with $ abiword -u /tmp/abiword.profile -v 2 Does the problem disappear? Please include any output you see in the terminal in your reply. Please also attach the file .AbiSuite/AbiWord.Profile found in your home directory (it contains your preferences). Is this the first time you're using abiword? If no, what was the last version that you remember working? Do you see this bug in other GTK+ applications as well? (for example in nautilus, the GNOME file manager) Thanks in advance for your help improving Debian! Kind regards, Patrik -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514498: dspam crashes on ds_setall_spamrecords (inside libsqlite3_drv.so)
Hey, On Sat, Feb 07, 2009 at 11:25:49PM -0200, Nicol�Lichtmaier wrote: > Standard configuration. And /usr/bin/dspam crashes with this backtrace: > [...] can you try to reproduce this with dspam in command-line mode? i.e. $ cat
Bug#514525: "free(): invalid pointer" when modifying styles
Hey,
I just found the problem:
abiword is allocating a tree path with gtk_tree_path_new(), but freeing
it with g_free (vs. gtk_tree_path_free). As gtk_tree_path_new does not
necessarily use malloc() but may also utilize faster memory management
functions, this leads to the described free() error. Besides, using
g_free() will leak memory.
A patch is attached. This fixes the problem for me, which I have been
able to reproduce on amd64.
Kind regards,
Patrik
--- abiword-2.6.4.orig/abiword/src/wp/ap/unix/ap_UnixDialog_Styles.cpp 2009-02-10 22:04:53.0 +0100
+++ abiword-2.6.4/abiword/src/wp/ap/unix/ap_UnixDialog_Styles.cpp 2009-02-10 22:04:56.0 +0100
@@ -661,7 +661,7 @@
// select first
GtkTreePath *path = gtk_tree_path_new_from_string("0");
gtk_tree_selection_select_path(selection, path);
- g_free(path);
+ gtk_tree_path_free(path);
}
// selection "changed" doesn't fire here, so hack manually
signature.asc
Description: Digital signature
Bug#512366: eboard hangs up and use 100%CPU on PowerPC
On Thu, Jan 22, 2009 at 02:16:18PM -0500, Simon Valiquette wrote: > By the way, I noticed that the compiler warned that eboard was linked > with a number of apparently unnecessary libraries like libpango. For > Lenny, it is best to keep it like it is now, but it would be a good idea > to look at it for Lenny+1. Pango is part of GTK+ and automatically pulled in by pkg-config. Okay, I think I found the real culprit. In various places, network.cc limits output to non-control characters by comparing with 0x20. On x86, char is signed and 0xFF will be (-1), thus being treated as control character. On ppc, chars are unsigned AFAIK, and 0xFF will be (255), and passed on to the rest of the code. 154 if (buffer.front()>=32) 219 if (c>=0x20) 294 if (c>=0x20) My fix for the time being would be to duplicate behaviour as on x86, using signed chars everywhere (as I suspect that other bugs might arise otherwise). A patch to the source package is attached, would you please try if that fixes the problem? Kind regards, Patrik --- eboard-1.1.1/debian/rules~ 2009-01-22 21:14:25.0 +0100 +++ eboard-1.1.1/debian/rules 2009-01-22 21:15:05.0 +0100 @@ -8,7 +8,8 @@ configure: configure-stamp configure-stamp: patch-stamp dh_testdir - ./configure --prefix=/usr --data-prefix=/usr/share/games --man-prefix=/usr/share/man + ./configure --prefix=/usr --data-prefix=/usr/share/games \ + --man-prefix=/usr/share/man --extra-flags=-fsigned-char touch configure-stamp signature.asc Description: Digital signature
Bug#512366: eboard hangs up and use 100%CPU on PowerPC
>>> If you need any more information or want me to try a patch, just ask me.
>>
>> Please try to get a backtrace with debugging symbols after the freeze
>> occurs and you hit CTRL-C.
>
> Okay, I found out that it was looping inside NText::formatLine exactly
> between the following lines in the file ntext.cc:
>
> 320 while(k-j > 0) {
> 321 fit = false;
> 322
> 323 // try full-fit for for unwrapped of last chunk of wrapping
> 324
> 325 if (j==0 && sl->Width >= 0) {
> 326 w = sl->Width;
> 327 } else {
> 328 if (!g_utf8_validate(tp+j,k-j,NULL)) continue;
>
> Obviously, "g_utf8_validate()" always returns false so the execution
> flow always move back to the start of the "while" loop.
>
> Is it just me that is very tired, or will it always test exactly the
> same string?
Yes, it will.
> The only sane explanation that came to my mind is that on x86, unless
> there is something wrong, the data are almost always valid Unicode on the
> first try (which seems reasonnable).
>
> It looks like a cut&paste error because just after, there is a "for"
> loop with almost exaclty the same code, except that the code makes more
> sense and don't always test the same data.
>
> It would also means that on big endian systems, there is maybe another
> bug somewhere that made this bug show up.
Yeah. The code is weird enough, but we shouldn't even get that far.
> Here the backtrace in case you would still want to see it. On Etch,
> there was also 2 stranges (but innocent looking) caracters appearing just
> after login. I can't remember for sure if it was "ÿû" exactly, but I do
> remember that it was some accented letters.
Do you know where they appeared? After your login name, or after the
"password:" prompt, or anywhere inbetween?
My guess is that the characters used to make a terminal not display its
input (i.e. if you were entering your password over a telnet FICS
session) are upsetting eboard.
Actually, the guide I linked has got it wrong, you need to set
DEB_BUILD_OPTS="nostrip noopt", separated by a space, not a comma.
Please re-compile eboard without optimizations for further debugging,
and get a detailed backtrace (bt full).
Please dump the raw byte contents of the trouble-causing buffer. Assuming
you break in g_utf8_validate again, you could do:
(gdb) p /x *...@10
Besides, a dump of the network traffic would probably be helpful. With
netcat, you could do
$ nc -l -p 5000 -c 'nc -o eboard-tcp-log freechess.org 5000'
and let eboard connect to localhost:5000 to get a hex dump in
eboard-tcp-log.
Kind regards,
Patrik
signature.asc
Description: Digital signature
Bug#512366: eboard hangs up and use 100%CPU on PowerPC
On Tue, Jan 20, 2009 at 02:19:59AM -0500, Simon Valiquette wrote: > After upgrading from Etch to Lenny, eboard stopped working on PowerPC. > Since it works fine on x86, my guess is that there is maybe an > endianness issue somewhere in the networking code of eboard. > > More exactly, it start as usual, but when connecting to a chess server, > it hangs and consume 100% CPU once the user have entered a user name. > [...] > If I press 'return here, the screen draw an additionnal '>' on the next > line, and the window hangs (it cannot be closed except by pressing CTRL-C > twice in a console or by killing it). Are you using a custom login script (~/.eboard/scripts/autofics.pl) that does weird stuff, maybe? If yes, please try without the script. > If you need any more information or want me to try a patch, just ask me. Please try to get a backtrace with debugging symbols after the freeze occurs and you hit CTRL-C. The wiki has a farily comprehensive guide [1], if you need further assistance, just contact me. Thanks in advance! [1] http://wiki.debian.org/HowToGetABacktrace Can anybody else reproduce this on PPC? Kind regards, Patrik signature.asc Description: Digital signature
Bug#193206: Text console-related crashes fixed in new package
It is very likely that these crashes are related to bugs in the text console. These bugs have been fixed some time ago, please also see bug #231759. If you find this bug to persist in eboard-1.1.1-2, please drop me a line. signature.asc Description: Digital signature
Bug#452686: Text console-related crashes fixed in new package
It is very likely that these crashes are related to bugs in the text console. These bugs have been fixed some time ago, please also see bug #231759. If you find this bug to persist in eboard-1.1.1-2, please drop me a line. signature.asc Description: Digital signature
