Package: php-smbclient
Version: 1.0.6-8
Severity: grave
Justification: renders package unusable
php-smbclient does not work with samba versions 4.17.5 and above:
https://github.com/eduardok/libsmbclient-php/issues/98
https://github.com/nextcloud/server/issues/36773
php-smbclient upstream version
Package: libkf5purpose-bin
Version: 5.86.0-1
Severity: normal
X-Debbugs-Cc: kra...@gmx.at
Dear Maintainer,
when trying to share a file from the Dolphin context menu, entries
Share/Nextcloud..., a error dialog appears, saying:
Failed to load the configuration page for this action:
file://usr/sh
With version 4, tesseract switched to double-dashed command-line parameters,
so it is now --psm instead of -psm.
Upstream addressed the issue in https://gitlab.gnome.org/World/OpenPaperwork/
pyocr/commit/c136838b46cf49f06ac1dc5f2f9bc16232c11213
Until a newer version is packaged, you can get your s
Package: python-mysqldb
Version: 1.3.10-2
Severity: normal
When connecting like this:
connection = MySQLdb.connect(read_default_file=dbconfig)
lines in the option file specifying a remote host are ignored.
Whatever host is specified in the option file, python-mysqldb always attempts a
connection t
Ari Pollak <[EMAIL PROTECTED]> wrote:
> tags 469863 +unreproducible
>
> Some help in tracking this bug down would be appreciated, since I have
> no real way to test or debug pidgin on armel.
I have an armel system, but I don't have the knowledge nor the time for real
debugging. However, I'll be
this is the backtrace of finch segfaulting:
Starting program: /usr/bin/finch
[Thread debugging using libthread_db enabled]
[New Thread 0x400228f0 (LWP 14686)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x400228f0 (LWP 14686)]
0x401cb400 in purple_core_migrate () at
On Sun, 09 Mar 2008 15:29:04 -0400
Ari Pollak <[EMAIL PROTECTED]> wrote:
> This doesn't make much sense since it seems to be in the ~/.gaim
> migration code, and that hasn't changed in a while. Could you run pidgin
> with MALLOC_CHECK_=3 set and see if you get a better backtrace?
>
Still the sam
Starting program: /usr/bin/pidgin
[Thread debugging using libthread_db enabled]
[New Thread 0x410b3580 (LWP 8314)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x410b3580 (LWP 8314)]
0x406f6400 in purple_core_migrate () at ../../libpurple/core.c:412
412 ../../li
Package: pidgin
Version: 2.4.0-1
Severity: important
Both pidgin and finch segfault immediately on startup, without any other output
on the
console before the segfault message.
Deleting ~/.purple/prefs.xml did not help.
Note: architecture is armel.
Version 2.3.1 works ok.
-- System Information:
It works fine in version 2.0.5-1.
As for me, the bug can be closed.
Regards
Alan Krempler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ot;.
I will wait until the latest gnucash release appears in debian to see whether
the bug has been fixed in mainline. If not, I will post a bug report to
gnucash.org.
Regards
Alan Krempler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
g_signal_handlers_block_matched ()
from /usr/lib/libgobject-2.0.so.0
#2 0x40194920 in gnc_date_cell_new ()
from /usr/lib/gnucash/gnucash/libgncmod-register-gnome.so.0
#3 0x004d3f00 in ?? ()
Cannot access memory at address 0x0
regards
Alan Krempler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
12 matches
Mail list logo
