After installing mutter 48~rc-3 from experimental and active use for
three hours, the bug appears to be fixed.
Thank you and regards
Stephan
signature.asc
Description: This is a digitally signed message part
I cannot confirm this. Just installed this version on sid and it starts
as expected...
h this patch the testsuite now hangs, not sure if this is related
> or not.
It's not related to the patch. One special test case causes this with the new
recode version.
This one test case is now disabled to make the build work.
Hth!
Stephan
signature.asc
Description: This is a digi
Some more tests confirm the following:
--ozone-platform=waylandworks
--ozone-platform-hint=wayland does not work
Regards
Stephan
Ah shit, ftp-masters reject my new version to DEFERRED without
notifying me but email.
Thanks for the pointer, will fix it ASAP.
Cheers,
Stephan
Hereby I confirm that linux-image-6.1.0-16-amd64 (6.1.67-1) from
bookworm-proposed-updates fixed the problems for me.
Regards
Stephan
signature.asc
Description: This is a digitally signed message part
removing all proprietary
(broadcom-sta) and custom (facetimehd) kernel modules.
Regards
Stephan
signature.asc
Description: This is a digitally signed message part
Are there any guidelines for affected users who already updated before
they got the warning?
Interesting questions for affected users:
- Is it safe to assume that other filesystems (like BTRFS) are not
affected?
- Does this cause filesystem corruption or only file corruption?
- Does this affect me
Caused by dh-python #1055008
e[1]: Entering directory '/<>'
(..)
> > hostname: Name or service not known
is ``hostname [-f]`` not working in the build environment?
I see that ``m-b-self-signed-cerificate --help`` fails, which would add
up. Also, 2.0.8 was a source-only upload and already 'got thru' previousl
tenance facilities
I.e., I don't recommend upgrading production systems just yet, please
wait for a proper 2.0.x release.
Thanks!
Stephan
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel:
Hi Bastian,
On Tue, 2022-11-29 at 21:09 +0100, Bastian Germann wrote:
> Why don't you move the experimental to unstable now?
well, some crucial tests (especially on upgrading) are unfortunately
still pending.
Uploading to unstable always marked "ok to use" in that respect, however...
> The unst
From changelog:
libphonenumber (8.12.57+ds-1+b1) sid; urgency=low, binary-only=yes
* Binary-only non-maintainer upload for amd64; no source changes.
* Rebuild against libicu72
-- amd64 / i386 Build Daemon (x86-csail-01)
Wed, 09 Nov 2022
09:06:01 +
signature.asc
Description: This i
Evolution gives the following confusing error message.
$ evolution
evolution: symbol lookup error: /lib/x86_64-linux-gnu/libebook-
contacts-1.2.so.4: undefined symbol:
_ZN4i18n12phonenumbers11PhoneNumberC1EPN6google8protobuf5ArenaE
However, libebook-contacts has not changed recently.
Regards
s
Package: libphonenumber8
Version: 8.12.57+ds-1+b2
Severity: serious
After updating libphonenumber8 from version 8.12.57+ds-1+b1 to version
8.12.57+ds-1+b2 in Debian Sid, Gnome Evolution fails to launch.
Downgrading to the previous version (still in Bookworm) fixes the
issue.
Regards
signature.
Hi Moritz,
On Fri, 2022-10-28 at 00:12 +0200, Moritz Mühlenhoff wrote:
> Am Fri, Aug 30, 2019 at 07:26:40AM + schrieb Matthias Klose:
> > Package: src:mini-buildd
> > Version: 1.0.41
> > Severity: normal
> > Tags: sid bullseye
> > User: debian-pyt...@lists.debian.org
> > Usertags: py2removal
>
s zeromq3 << 4.3.4-3 anyway and
a) zeromq3 has no dependency on cppzmq at all
b) cppzmq is in a different source package, so dpkg will upgrade zeromq3
and then install cppzmq
At least I had no installation problems. Let me know if I got this wrong.
Regards,
Stephan
-dev in d/control.
Regards,
Stephan
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; P
. Tested on multiple networks and machines.
A debug log is given below. Probably an upstream issue.
Cheers,
Stephan
Debug log:
$ leo --debug test
%DEBUG: connecting to site: dict.leo.org port 443
%DEBUG: GET /dictQuery/m-vocab/ende/query.xml?lp=ende&search=test HTTP/1.0
Connection fa
eleased after that,
I have uploaded the new version instead of adding the patch.
Thanks again,
Stephan
public
domain in their header.
The overall project license might be BSD-3-Clause, but the python files
are licensed differently. Please close this if you agree with my assessment.
Regards,
Stephan
[1]
https://github.com/WojciechMula/pyahocorasick/tree/ec2fb9cb393f571fd4316ea98ed7b65992f16127/py
Hi,
thanks for reporting. I can confirm this. I will fix it with the version
1.6.0, which has been released 3 weeks ago.
Since I don't have much time right now, it will probably stay in this
state for the next couple of weeks (sorry).
Regards
Stephan
On Mon, 16 Aug 2021 09:48:41
I can confirm this.
Regards,
Stephan
post-installation script failed,
but how can I display the line number where it fails?
Stephan
-- System Information:
Debian Release: 10.9
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-14
dress, as it probably is not a
bad idea. But this is more of a wishlist thing, not an actual security
concern (at least to me).
Regards,
Stephan
Control: tags confirmed fixed-upstream
I can confirm the behavior. It has nothing to do with an internet connection
like I assumed before.
I'm upload a new version with a fix from upstream [1][2]. Thanks for reporting
this.
Regards
Stephan Lachnit
[1]
https://github.com/lutris/lutris/c
I have a suspicion, which is that this is due to the Lutris Runtime missing.
Did you have an internet connection when you launched it the first time?
I'll try it on a live image tomorrow as well.
Regards
Stephan
Hi Vasyl,
Am 15.01.21 um 17:47 schrieb Vasyl Gello:
> If that works, the next upload wi.l fix the issue for general public.
Wow, that was fast :-)
Thank you all for your help, everything works fine now!
Cheers
Stephan
Can confirm, currently unusable. Has been fixed upstream [1], but no new
release yet.
The fix should be added as patch or upstream should be asked for a new release
before Bullseye.
Regards,
Stephan
[1]
https://github.com/bluesabre/mugshot/commit/643b3d005a8865c961b836aeae4c1f76711646e9
much time I have.
Regards,
Stephan
This also makes the system fail to boot.
Regards
change the default server.
Shade and sweet water!
Stephan
-- System Information:
Debian Release: bullseye/sid
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel:
On Wed, 25 Mar 2020 10:54:22 +0100 =?utf-8?B?SsO2cmc=?= Sommer
wrote:
>
> A quick and dirty workaround is:
>
> ```
> # egrep '/(ld|lib(d|c|m|pthread|rt|dl))-2.*.so' $I/libc6:amd64.list |sed
> 's,^,/usr,' |tee -a $I/libc6:amd64.list
> /usr/lib/x86_64-linux-gnu/ld-2.30.so
> /usr/lib/x86_64-linux-
Hi Peter,
On Fri, 2019-08-02 at 22:11 +0100, Peter Michael Green wrote:
> Package: mini-buildd
> Version: 1.0.41
> Severity: serious
>
> python-mini-buildd depends on and the mini-buildd source package
> build-depends on the python-django-registration binary package which
> is
> no longer built
Package: blueman
Version: 2.0.6-1
Severity: grave
Tags: newcomer
Justification: renders package unusable
Dear Maintainer,
this package has wrong python dependencies. It should depend on the python3.6
package or python3 (< 3.7), because it doesn't install on latest Debian Sid
(unstable).
-- Sys
Hi Sven,
On Wed, 2018-05-16 at 17:26 +0200, Sven Joachim wrote:
> Source: ui-utilcpp
> Version: 1.8.5-2
> Severity: serious
>
> Your package FTBFS everywhere[1], the reason being that the configure
Ups yes, thanks for the hint ;).
I did not thoroughly check on this after the hasty post-salsa up
Package: tinyproxy
Version: 1.8.4-2
Severity: grave
Tags: patch
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
Hanging tinyproxy, no proxied connections are handled anymore.
* What exactly did you do (or not do) that was effective (or
i
On So, Jan 15, 2017 at 04:43:11 +, Ian Jackson wrote:
I have just uploaded systemd-shim 10-3~exp1 to experimental. I seems
to fix the problem for me. Depending on feedback, I will upload this
to sid in the next few days.
Thank you very much. I don’t have problems either.
Stephan
76f68f4738c01120c91e2255488670ade63a5db3
Author: Stephan Sürken
Date: Thu Sep 29 18:10:06 2016 +
changelog: Prepare 2.1.2-3.
diff --git a/debian/changelog b/debian/changelog
index af55596..ea9f227 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+python-django
CVE-2016-2318
CVE-2016-2317
CVE-2015-8808
Do you think 1.3.25-2 might be the used for a stable update?
Stephan
On Tue, 5 Jul 2016 08:53:29 -0500 (CDT) Bob Friesenhahn
wrote:
On Tue, 5 Jul 2016, László Böszörményi wrote:
>
> I don't think 1.3.24 would be an easy target for Je
others?
> I didn't know about --debug-quick-random, it seems perfect to me.
>
> Stephan, do you think it would be possible to patch mini-buildd so
> that --debug-quick-random is added to gnupg command line, but only
> when the package is doing the tests following the build?
fwi
t.
> >
> > do any of these options sound more appealing than the others?
> I didn't know about --debug-quick-random, it seems perfect to me.
>
> Stephan, do you think it would be possible to patch mini-buildd so
> that --debug-quick-random is added to gnupg command line
Hi Daniel, Santiago,
thx for the answer; I am not 100% satisfied, though ;).
For me, it actually boils down to what notion we have:
(1) The builder hosts must provide reasonable entropy.
(2) Software testsuites generally must work fine even with low entropy.
In the past, I tended to go with (1)
Hi Santiago,
On So, 2016-09-11 at 11:37 +0200, Santiago Vila wrote:
(...)
> This is the changelog entry you wrote:
>
> > * [8ee94bc] gnupg.py: Add extra method to get sec user id. Fixes
> doctest
> > for GPG 2.1. Thanks to Santiago Vila (Closes: 834683)
>
> If this is only intended to wo
t only the last mail is available).
Many greetings,
Stephan
-- Package-specific info:
Mutt 1.6.2-neo (2016-08-08)
Copyright (C) 1996-2016 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to
security fixes in 2016:
https://security-tracker.debian.org/tracker/source-package/graphicsmagick
Is graphicsmagick no longer supported by debian?
Regards,
Stephan Großberndt
--
side by site GmbH & Co. KG
Geo & Web
Barbarastraße 3-9 (Block 6)
50735 Köln
fon: +49 221 27909-68
fax: +49 221
Hi Daniel, Andreas,
On Fri, 17 Jul 2015 00:47:55 +0200 Andreas Beckmann wrote:
> Followup-For: Bug #790274
>
> Similar failure while rebuilding in a clean jessie pbuilder environment:
>
> [...]
[...]
> File "/usr/lib/python2.7/multiprocessing/synchronize.py", line 147, in
> __init__
>
On Sa, 2015-08-01 at 19:46 +0200, Johannes Schauer wrote:
> Hi,
(...)
> I reported it like that because I was not able to recreate ./configure and
> aclocal.m4 from source. When I deleted both files and tried to regenerate
> them,
> I ran into an error and I also got an error when I tried to rebui
how autotools work, and everything can be
rebuild within Debian/main -- but maybe I missed something ;).
Thanks!
Stephan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
water!
Stephan
--
| Stephan Seitz E-Mail: s...@fsing.rootsland.net |
| Public Keys: http://fsing.rootsland.net/~stse/keys.html |
signature.asc
Description: Digital signature
Package: mini-buildd
Version: 1.0.4
Severity: grave
Justification: renders package unusable
FTR:
In sbuild-0.63.3 this bug has been fixed:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607228
Unfortunately, the workaround in mini-buildd for that bug now
actually breaks mini-buildd now the b
Package: mini-buildd
Version: 1.0.4
Severity: grave
Justification: renders package unusable
A reminder to myself, and for those wondering...
grave: As this basically prevents any package building.
Will be fixed asap, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764380
Workarounds:
(1
s/__init__.py", line
22, in register
from size import SizeChecker
File "/usr/lib/pymodules/python2.7/DjangoLint/AstCheckers/size.py", line 19,
in
from pylint.interfaces import IASTNGChecker
ImportError: cannot import name IASTNGChecker
---
Hth,
Stephan
-- System Inform
block 730157 by 718047
thanks
This is likely bug#718047. Removing the --as-needed switch from the ld
invoke is the tentative workaround for that.
Regards
Stephan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
).
Unfortunately it was successfully. The build log had the known
messages about starting of the Apache server and the list of test
steps; each with an 'ok'.
Stephan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trou
ache2-mod-perl2 (2.0.8+httpd24-r1449661-4) package with success.
Stephan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
en on ia64 only, all archs are affected. The other
archs just had more luck.
The patch corrects the problem which we have on ia64. The problem on
mips is likely a completely different one. Please could you file a new
separate bug report for that?
Stephan
ia64_children_test.patch
Description: ia64_children_test.patch
I'm using Debian unstable on ia64.
I built the gtk+3.0 package twice; the test always fails as on the
ia64 buildd:
/usr/bin/make check-local
make[4]: Entering directory
`/home/stephan/gtkplus2/gtk+3.0-3.8.2/debian/build/shared/tests/a11y'
TEST: accessibility-dump... (pid=
Package: freeradius-dialupadmin
Version: 2.1.12+dfsg-1.2
Justification: renders package unusable
Severity: grave
-- System Information:
Debian Release: 7.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd6
Why you don't migrate iceweasel 10.0.12esr-1+nmu1 to testing ;-) ?
It would also please some mipsel users (Bug#680704).
Kind regards
Stephan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
e why.
A user has confimred that on the debian-i...@lists.debian.org list.
I filed a new bug#702641 for the asm register contraints problem above.
Please could you simply close this bug?
Stephan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "u
I'm sorry. Wrong bug number.
Please, ignore my message.
Stephan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
e why.
A user has confimred that on the debian-i...@lists.debian.org list.
I filed a new bug#702641 for the asm register contraints problem above.
Please could you simply close this bug?
Stephan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "u
erver-xorg-video-i740
xserver-xorg-video-mga
xserver-xorg-video-rendition
xserver-xorg-video-s3
xserver-xorg-video-siliconmotion
xserver-xorg-video-sis
xserver-xorg-video-trident
xserver-xorg-video-tseng
xserver-xorg-video-vesa
Stephan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debia
)
Subsystem: Intel Corporation Device [8086:3404]
I tried a fresh installation of wheezy.
I realized that the mach64 and the r128 xorg video drivers aren't
installed automatically on ia64.
Stephan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subje
If you want to test it, you can download the built debs:
http://www.fs-driver.org/debian-ia64/webkitgtk-debs-v3.tar
http://www.fs-driver.org/debian-ia64/seed-debs.tar
http://www.fs-driver.org/debian-ia64/epiphany-debs.tar
Remember to remove both gnash and gnash-common before you test it.
Stephan
package has to depend on
libseed-gtk3-0 again after that.
Please could you check whether enabling seed is also possible on MIPS
since the mentioned bug reports may fix webkit and seed on MIPS as well.
Many thanks.
Stephan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with
ption.
The patch
- fixes the issue with the queue, and
- fixes the mentioned assertion.
Although it was experienced on ia64, the bug affects all archs.
You can find a link to the built debs on bug report#642750.
Stephan
history-thread-startup-race.patch
Description: history-thread-startup-race.patch
del, for example, ia64.
The attached patch is a backport of the upstream's fix.
You can find a link to the built debs on Debian bug report#642750.
Stephan
thread-safe-icon-db.patch
Description: thread-safe-icon-db.patch
I can provide the built debs for ia64 (150MB) after making some room
for it on my webspace:
http://fs-driver.org/debian-ia64/iceweasel-10.0.11esr-debs.tar
Stephan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
shes *sometimes*.
Obviously Epiphany/Webkit still has at least one more bug...
Let me know if additional tests are welcomed.
I think further tests at the level of a user wouldn't have any benefit
at the moment.
(Please could you test the patches for Iceweasel 10.0.11esr at next?)
Stephan
phany/webkit isn't completed because
it doesn't work satisfactory yet.
Regards
Stephan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
cpp_error (pfile, CPP_DL_WARNING,
"%s: had text segment at different address", name);
return 2;
}
...
}
It is experienced on ia64 here, but the bug affects any arch.
Stephan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject
e patches don't change anything on archs other than ia64.
- Please apply 01-fix-map-pages-on-ia64.patch first.
- At next 02-static-str-in-mmem-on-ia64.patch.
You also need the patch of bug#692053.
Stephan
01-fix-map-pages-on-ia64.patch
Description: 01-fix-map-pages-on-ia64.patch
02-static
I appreciate comments on that.
For now I'd prefer the 'wheezy-ignore' rather than removing the ia64
ruby package.
Stephan
If you want to read something pleasing about ia64 for a change, you
can take a look at bug#659186 or #582774.
--
To UNSUBSCRIBE, email to debian
org/debian-ia64/webkitgtk-debs-v2.tar
The patches also fix bug#582774 (seed FTBFS on ia64).
Stephan
01-ia64-wide-ptr.patch
Description: 01-ia64-wide-ptr.patch
02-ia64-use-system-malloc.patch
Description: 02-ia64-use-system-malloc.patch
P issue [2] :-(
I don't believe that we would have much benefit of any stack trace on
this bug.
I'm still using the Kernel 3.2.23 with the futex patch [2] compiled
with GCC4.4. Yet another ia64 problem.
Stephan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.o
teric id in included html documentation
files and the Debian/md5sums file.
All included .h files were identical.
The patches do not change the binary interface.
Stephan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
locations with completely different stack traces. I think it is worth
to check whether this patch solves some other bug reports, for
example, on MIPS.
Stephan
large-mem-page.patch
Description: large-mem-page.patch
y different from the unpatched one with GCC4.6.
GDB doesn't work with the that patched Kernel - still the odd
behaviour with the SIGTRAP.
Summary for today:
The patch of Debian bug#659485 sucks and should be revised since it
can make trouble with future versions of GCC.
I don't know yet whether the considered patches are related with the
GDB problem or not. An if so, how.
I will take a Kernel 3.2.23 at next and revert *all* patches I have
mentioned above, so that the files
arch/ia64/include/asm/futex.h
and
kernel/futex.c
look like on Kernel 2.6.26 or so, and try whether GDB works with it.
Stephan
futex-ia64-fix-of-the-fix.patch
Description: futex-ia64-fix-of-the-fix.patch
Package: gdb
Version: 7.4.1
Severity: serious
Dell PowerEdge 3250
2x Itanium Madison 1.5GHz 6M
4GB RAM
I realized that GDB doesn't work as it should.
When GDB should run *any* target application, it always stops with
SIGTRAP 0x.
Example:
stephan@itanic:~$ gdb man
GN
erver 1.13.
Kind regards
Stephan Schreiber
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
CH64(0): ATI 3D Rage XL or XC graphics controller
detected.
[32.185] (--) MACH64(0): Chip type 4752 "GR", version 7, foundry
TSMC, class 0, revision 0x00.
[32.185] (--) MACH64(0): PCI bus interface detected; block I/O
base is 0xCC00.
[32.185] (--) MACH64(0): ATI Mach64 adapter detected.
[32.185] (!!) MACH64(0): For information on using the multimedia
capabilities
of this adapter, please see http://gatos.sf.net.
[32.185] (--) MACH64(0): Internal RAMDAC (subtype 1) detected.
[32.185] (==) MACH64(0): RGB weight 888
[32.185] (==) MACH64(0): Default visual is TrueColor
It includes successful submodule unloads now:
[32.185] (II) UnloadSubModule: "vbe"
[32.185] (II) Unloading vbe
[32.185] (II) UnloadSubModule: "int10"
[32.185] (II) Unloading int10
Kind regards
Stephan Schreiber
unloadsubmodule.patch
Description: unloadsubmodule.patch
Hi,
tagged fixed-in-experimental.
ftr, both issues are definitely fixed in 1.0.0, alpha3 (still in NEW,
though).
HtH,
Stephan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
that really don't want
to upgrade (would become really relevant for wheezy+1, however ;).
HtH,
Stephan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
6/common/xf86Helper.c of
xorg-server-core 1.11.4:
void
xf86UnloadSubModule(pointer mod)
{
/*
* This is disabled for now. The loader isn't smart enough yet to undo
* relocations.
*/
#if 0
UnloadSubModule(mod);
#endif
}
Conclusion: UnloadSubModule() was and is still buggy.
I commented out UnloadSubModule(mod) tentative in 1.12.3, the X server
started successful after that.
So the solution would be either comment out UnloadSubModule() or fix it...
Kind regards
Stephan Schreiber
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
ead in hw/xfree86/common/xf86Helper.c of
xorg-server-core 1.11.4:
void
xf86UnloadSubModule(pointer mod)
{
/*
* This is disabled for now. The loader isn't smart enough yet to undo
* relocations.
*/
#if 0
UnloadSubModule(mod);
#endif
}
Conclusion: UnloadSubModule() was and is still buggy.
I commented out UnloadSubModule(mod) tentative in 1.12.3, the X server
started successful after that.
So the solution would be either comment out UnloadSubModule() or fix it...
Kind regards
Stephan Schreiber
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
network/if-up.d/mountnfs to
[ "$ADDRFAM" = "inet" ] || [ "$ADDRFAM" = "inet6" ] || [ "$ADDRFAM" =
"NetworkManager" ] || exit 0
it works for me.
However, I don't know what other side effects that might have, I hope
someone who know
nitscripts.
#676473 could probably be merged.
Regards,
Stephan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: gnome-session
Followup-For: Bug #656762
Hi,
I just want to say that I'm too experiencing the issue of massive g-s-d
crashes with the "fail-whale" showing up every now and then.
For that crash window: it seems to be just a stupid application, so a ALT-F4
closes it and you get your desktop
Hi,
please find attached the patch for fixing those format-security errors.
it's applied to ubuntu already, and works just fine.
Just put it as the latest patch in the quilt series.
Regards,
\sh
Index: abiword-2.8.6/src/af/xap/gtk/xap_UnixDialogHelper.cpp
==
Package: selinux-policy-default
Version: 2:0.2.20100524-9
Severity: grave
Justification: renders package unusable
Due to dependencies of initscripts 2.88dsf-13.10 selinux-policy-default
2:0.2.20100524-9 can not be installed.
> The following NEW packages will be installed:
> selinux-policy-defau
Package: fsprotect
Version: 1.0.5
Severity: grave
Justification: renders package unusable
The initramfs scripts of fsprotect use touch to create /fastboot which tells
fsck to skip the filesystem check on boot.
However, /bin/touch is not available in my initrd. So on boot fsck is
complaining abou
Marco d'Itri (14.05.2011, 03:36:51):
>Can you try replacing the kill loop in init-bottom/udev with just
>"udevadm control --exit"?
I tried but it didn't help.
But according to the initramfs-tools manpage, the scripts in
init-bottom are executed last. So why should this help with the timing
issue
Marco d'Itri (26.04.2011, 15:33:00):
>Because they cannot be relevant, and anyway your problem happens in the
>initramfs.
So I first had a look there and enabled debugging.
It looked like the lvm2 script didn't find any VG with udev-168-1:
==
| + /scripts/local-top/mdadm
| Begin: Loading
Marco d'Itri (25.04.2011, 21:16:05):
>Just to be sure, does the boot process stop in the initramfs or is the
>root file system (on LVM or not?) mounted?
the root fs is on a LVM but the volume group does not get activated,
therefore the root fs cannot be mounted.
the boot process stops in the init
Marco d'Itri (25.04.2011, 12:40:45):
>Maybe this is related to the init script change? Try this:
>-udevadm info --cleanup-db
>+rm -rf /dev/.udev/failed/ /run/udev/failed/
sorry, this didn't work
(I did run "update-initramfs" after modifying the init script)
--
To UNSUBSCRIBE
Package: udev
Version: 168-1
Severity: critical
Tags: sid
Justification: breaks the whole system
after updating to udev 168-1 the system stops at boot time because of
the missing root device.
My root is a LVM device which was not activated during the boot process.
After manually activiating it, I
putting it all together we can safely close this bug report or
reassign it to lsb_release, even though I guess this bug has already
been fixed there.
Could someone else do that because I do not have that much time for bug
management right now?
Regards,
Stephan
--
To UNSUBSCRIBE, email to debi
mini-buildd script, of course.
Thx,
Stephan
--
Stephan Sürken
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
1 - 100 of 164 matches
Mail list logo
