On Mon, Feb 20, 2023 at 5:27 PM Simon McVittie wrote:
> > Feb 20 15:18:32 nuc8 gnome-shell[7963]: Running GNOME Shell (using mutter
> > 44.beta) as a X11 window and compositing manager
> >??? why X11, should be Wayland
>
> mutter is a Wayland compositor, but it's also an X11 window and co
Package: dbus-broker
Version: 29-4
Severity: critical
X-Debbugs-Cc: roderich.sch...@gmail.com
After upgrading to dbus-broker 30-1 every Gnome session is terminated after
a few seconds. coredumpctl shows a coredump of dbus-broker (as system bus)
afterwards. Downgrading to 29-4 fixes the problem.
U
> mark /usr/share/ghostscript/* as not-installed,
> which is clearly bogus but seems the only (simple) way
> to ignore only for arch-dependent builds;
Another way to fix this is to use ${env:GS_DOT_VERSION} in libgs9-common.install
(since you're already using debhelper-compat 13), see patch below
Package: python3-dbussy
Version: 1.2.1-1
Severity: serious
X-Debbugs-Cc: roderich.sch...@gmail.com
dbussy doesn't work if /usr/lib/x86_64-linux-gnu/libdbus-1.so.3
(from libdbus-1-3) isn't installed:
$ sudo mv /usr/lib/x86_64-linux-gnu/libdbus-1.so.3{,-off}
$ python3
Python 3.8.6 (default, Sep 25
Source: lollypop
Version: 1.1.4.16-1
Severity: grave
Tags: patch
without python3-gi installed:
$ lollypop
Traceback (most recent call last):
File "/usr/bin/lollypop", line 14, in
from gi.repository import Gio
ModuleNotFoundError: No module named 'gi.repository'
IOW: the package needs pyth
On Tue, Apr 10, 2018 at 5:25 PM, Jeremy Bicha wrote:
> I can confirm this issue on Ubuntu 18.04. Could you please forward
> this issue to GNOME?
>
Done, https://gitlab.gnome.org/GNOME/gnome-boxes/issues/196
I just realized that I'm running policykit-1 from experimental (0.113-5).
The version in unstable/testing (0.105-7) is not affected, as it isn't
build with JavaScript support.
So may downgrade the severity of this bug.
Cheers, Roderich
Package: libmozjs185-1.0
Version: 1.8.5-1.0.0+dfsg-5.2
Severity: grave
Version 1.8.5-1.0.0+dfsg-5.2 breaks polkitd:
Dec 10 23:31:07 macarthur kernel: traps: polkitd[577] general protection
ip:7fcce2bcdbd1 sp:7ffe4cf4e220 error:0 in
libmozjs185.so.1.0.0[7fcce2ace000+358000]
Dec 10 23:31:07 macarth
Build with gcc-6 of libraw 0.17.2-3 fails with
internal/dcraw_common.cpp: In member function ‘void
LibRaw::vng_interpolate()’:
internal/dcraw_common.cpp:4539:3: error: narrowing conversion of ‘128’ from
‘int’ to ‘signed char’ inside { } [-Wnarrowing]
}, chood[] = { -1,-1, -1,0, -1,+1, 0,+1, +1,
On Tue, Jan 19, 2016 at 7:50 PM, Ben Hutchings wrote:
> I think I understand the problem. Could you try the packages (version
> 0.122~a.test) from https://people.debian.org/~benh/packages/ ?
>
Yes, that works (using the unpatched klibc-utils 2.0.4-7, not my hacked
version). Thanks!
Cheers, Rod
Package: libc6-dev
Version: 2.22-0experimental0
Severity: grave
Tags: patch
Several builds with libc6 2.22-0experimental0 fail with
/usr/bin/ld: cannot find /lib/x86_64-linux-gnu/libmvec_nonshared.a
There are two problems here:
(1) libmvec_nonshared.a is built, but not installed (into libc6-de
Source: openjdk-8
Version: 8u72-b05-1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
A funny thing happened while building openjdk-8 8u72-b05-1. I've included the
relevant tail of the build log below, but the reason is that one of the s
Source: nant
Version: 0.92~rc1+dfsg-4
Severity: serious
Justification: fails to build from source
Build fails, log below.
*** /build/log/d/dbus-sharp_0.8.1-1
dpkg-buildpackage: source package dbus-sharp
dpkg-buildpackage: source version 0.8.1-1
dpkg-buildpackage: source distribution unstable
dpk
Source: dbus-sharp
Version: 0.8.1-1
Severity: serious
Justification: fails to build from source
Build fails, see below.
*** /build/log/d/dbus-sharp_0.8.1-1
dpkg-buildpackage: source package dbus-sharp
dpkg-buildpackage: source version 0.8.1-1
dpkg-buildpackage: source distribution unstable
dpkg-b
Source: libapache2-mod-perl2
Version: 2.0.9~rc2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Building with GCC 5 and Perl 5.22 (also built with GCC 5) from experimental.
Build stops with
[warning] setting ulimit to allow core files
ulimit
Hi,
in Banshee 2.9.1, the preferred GStreamer backend was changed to Gst-Sharp.
Since this is not available in Debian yet, we must use the "native" backend.
However, it's not sufficient to configure with --disable-gst-sharp (which
used to fall back
to the native backend), we must explicitly reque
Package: gucharmap
Version: 1:3.8.2-1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
Building with perl 5.18.0 installed results in:
cd gucharmap && ./gen-guch-unicode-tables.pl 6.1.0 /usr/share/unicode
syntax error at ./gen-guch-
Why is this bug tagged "perl-5.18-transition" (cf.
http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.18-transition;users=debian-p...@lists.debian.org
)?
The buildd errors (as well as the mentioned commits to upstream source) are
in the Ruby bindings
(and were actually caused by changes to the
Package: python-pytest
Version: 2.3.4-1~exp1
Severity: serious
Tags: patch
$ py.test-2.7 -v
Traceback (most recent call last):
File "/usr/bin/py.test-2.7", line 5, in
sys.exit(load_entry_point('pytest==2.3.4* Bump Standards-Version to
3.9.4, no change needed.', 'console_scripts', 'py.te
Package: eglibc
Version: FTBFS with kernels >= 2.6.37 (error in tst-writev)
Severity: serious
Justification: fails to build from source
Tested with (self-built) kernels 2.6.38.6 and 2.6.39.1: tst-writev fails with
Error 1. It succeeds on 2.6.36.4.
On closer inspection the writev() call in tst-wri
The actual problem is that the libdbd*.so libraries are NOT linked
against libdbi.so.
The reason is an incorrect usage of AC_ARG_ENABLE(libdbi,...) in configure.in.
Using "configure --enable-libdbi" thus has the opposite effect: it
disables linking.
BTW --enable-docs suffers from the same mistake
Felix:
> I *think* this didn't happen with previous experimental upload.
Nope, I had "unaligned pointer 0x12404" already with
1.97+experimental.20091110-1.
Cheers, Roderich
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact li
2009/10/10 Josselin Mouette :
> Le samedi 10 octobre 2009 à 12:38 +0200, Roderich Schupp a écrit :
> No, the fix is to upload a new gnome-main-menu. We try to minimize code
> duplication in the archive, so it’s not a reason to increase it.
No argument here, my fix was just simpler to
Hi,
I got my shovel and dug some more into these
"TypeError: Expected argument 1 of type ..., but got Array []" errors.
Here's what I found (warning lengthy explanation ahead).
(1) In general, Swig tries to deliver output parameters (as viewed from
the C level) as multiple return values in the w
Package: svn-load
Version: 0.8-1
Severity: serious
Hi,
please supply at least a rudimentary man page for svn-load.
The online help is not enough to figure out how to use it -
I had to look up information for svn_load_dirs.pl and hope
that the two are very similar. Besides, this is a Debian
policy
FYI,
I dug a little deeper wrt to the test failures in the Ruby bindings.
Comparing the code generated with swig 1.31 and 1.33,
e.g. ./subversion/bindings/swig/ruby/core.c,
swig 1.33 added lines of the form
vresult = rb_ary_new();
to lots of wrapper functions. If I comment out these and rebuil
The problem is the line
NEVER_FAILS_root_set_euid_egid (0, 0);
in the "sanitize .ICEauthority ..." block in daemon/slave.c ~line 3500.
Later on (line 3557) only the process's uid is setuid to the user's uid,
while the gid stays unchanged (and hence fails the setgid check in
the first GTK app
27 matches
Mail list logo
