Debian Bug Tracking System | 23 Sep 19:57 2014

Processed: severity of 762598 is grave

Processing commands for control <at>

> # unusable
> severity 762598 grave
Bug #762598 {Done: Axel Beckert <abe <at>>} [libswitch-perl] libswitch-perl: "use Switch"
tries to call a method on an unblessed reference
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian Bug Tracking System
Contact owner <at> with problems

Debian Bug Tracking System | 23 Sep 19:51 2014

Processed: tagging 759825

Processing commands for control <at>

> tags 759825 + patch
Bug #759825 [src:audtty] audtty: FTBFS: main.c:20:31: fatal error: audacious/audctrl.h: No such file
or directory
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian Bug Tracking System
Contact owner <at> with problems

Cédric Roux | 23 Sep 18:38 2014

Bug#762604: base: debian testing and unstable don't work with a 486 PC

Package: base
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

I need to boot a linux system on my old 486 to access the parallel
port to do some JTAG debugging.

I use my recent PC as a NFS root server.
I ran:
  debootstrap --arch=i386 stable /tmp/debian.stable
  debootstrap --arch=i386 testing /tmp/debian.testing
  debootstrap --arch=i386 unstable /tmp/debian.unstable
And served those directories to the 486, the one after the other.

Debian stable is working.
Debian testing is not.
Debian unstable is not.

Running "ls" crashes with "illegal instruction".
I found out that the illegal instruction is "cpuid" (this one
does not exist on 486 PC) which is in, function

Why is that called? I don't know. It should not.

I tried to recompile the whole gnu libc beast to not include that
function, but failed. I skip the details, I surely did something
wrong. And I don't have much time nor energy for that thing.
(Continue reading)

Soren Stoutner | 23 Sep 18:15 2014

Bug#760191: Fixed

An update to the latest packages from testing appears to have fixed this 
problem for me.  I have not yet exhaustively checked for remaining errors, but 
I an now receiving new emails.


Soren Stoutner
soren <at>

Guillermo Espertino | 23 Sep 18:05 2014

Bug#759146: (no subject)

Bug #757247 should be merged with this, as it appears that the problem
described has the same origin.
Also, the patch to python-PIL suggested in that bug report fixes this issue.

Louis-David Mitterrand | 23 Sep 17:07 2014

Bug#756155: "ReferenceError: CKEDITOR is not defined"

Package: ckeditor
Version: 4.4.4+dfsg1-1
Followup-For: Bug #756155


Now I get this error 

NetworkError: 404 Not Found -

There is no loader.js on your package.

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

Kernel: Linux 3.17-rc5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_IE <at> euro, LC_CTYPE=fr_FR <at> euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages ckeditor depends on:
ii  libjs-highlight  8.2+ds-1
ii  libjs-swfobject  2.2+dfsg-1

Versions of packages ckeditor recommends:
ii  javascript-common  11

ckeditor suggests no packages.
(Continue reading)

Ant | 23 Sep 16:34 2014

Bug#762547: Same for me...

I got the same results just a few minutes ago. :(

Ying-Chun Liu (PaulLiu | 23 Sep 16:26 2014

Bug#759044: forward to upstream.

forwarded 759044


                                PaulLiu (劉穎駿)
E-mail: Ying-Chun Liu (PaulLiu) <paulliu <at>>

tim schmidt | 23 Sep 16:00 2014

Bug#762592: apper Unable to open database read-only in current debian testing

Package: apper
Version: 0.9.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

lastest update to apper in debian testing resulted in the following error on startup:

Unable to open database read-only: Database action 'prepare app insert statement' failed:
 SQL logic error or missing database (table applications has no column named unique_name)

This renders apper unusable.

Deleting the Listaller cache DB seemed to fix the problem for me. command used:

rm -r /var/lib/listaller/db/

-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

(Continue reading)

Emilio Pozuelo Monfort | 23 Sep 15:44 2014

Bug#762591: freerdp: FTBFS on several arches: test suite errors

Source: freerdp
Version: 1.1.0~git20140921.1.440916e+dfsg1-1
Severity: serious



Steven Chamberlain | 23 Sep 14:58 2014

Bug#762588: glib-networking: FTBFS[kfreebsd]: testsuite race conditions

Package: glib-networking
Version: 2.41.92-2
Severity: serious
User: debian-bsd <at>
Usertags: kfreebsd


glib-networking has failed 4 attempts to build on kfreebsd-amd64 due to
testsuite errors.

Firstly, please `export VERBOSE=1` before running `make check`.  There
is much more detail recorded about failures than is currently output in
the build log.

I was able to reproduce issues locally about 15% of the time, suggesting
a race condition, in three different tests:

    /tls/connection/client-auth-rehandshake: **
    GLib-Net:ERROR:connection.c:413:on_client_connection_close_finish: assertion failed (error ==
NULL): Error closing socket: Connection reset by peer (g-io-error-quark, 0)

    /tls/connection/read-time-out-then-write: **
    GLib-Net:ERROR:connection.c:217:on_server_close_finish: assertion failed (error == NULL): Error
closing socket: Connection reset by peer (g-io-error-quark, 0)

    /tls/connection/close-during-handshake: **
    GLib-Net:ERROR:connection.c:215:on_server_close_finish: assertion failed: (error != NULL)
(Continue reading)