Bug#1059039: usrmerge: installing usrmerge on a chroot with /usr on a separate partition fails
Package: usrmerge Version: 38 Severity: important howdy, trying to update a debian unstable system, and it breaks due to usrmerge. Preparing to unpack .../archives/usrmerge_38_all.deb ... /usr is a standalone filesystem, this requires using an initramfs. dpkg: error processing archive /var/cache/apt/archives/usrmerge_38_all.deb (--install): new usrmerge package pre-installation script subprocess returned error exit status 1 thx. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.3-0-edge (SMP w/32 CPU threads; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages usrmerge depends on: ii libfile-find-rule-perl 0.34-3 ii perl5.36.0-10 usrmerge recommends no packages. usrmerge suggests no packages.
Bug#1036370: BUGG INSTALL DEBIAN V11.7.0
Package: V11.7.0 Boot method: RESEAU Image version: ONLINE Date: 20/05/2023 8H37 Machine: SIEMENS 6ES7647-8BD31-0CA1 (SIMATIC IPC227E (Nanobox PC); 1x display port; 2x 10/100/1000 Mbit/s Ethernet RJ45; 1 x USB3.0, 3 x USB2.0; CFast slot; 24 V DC industrial power supply Celeron N2930 (4C/4T) with TPM; 8 GB RAM; Box: Basis without COM without operating system 240 GB SSD; without SIMATIC software DIN rail mounting) Processor: Celeron N2930 (4C/4T) with TPM Memory: 8 GB RAM Partitions: ? Résultat de lspci -knn (ou lspci -nn) :? Installation du système de base : bad [O] = OK, [E] = Error (développez plus bas s'il vous plait), [ ] = non essayé Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: installation frozen at 11% discover (amd64) installed
Bug#920976: kdiff3: Some files could not be processed
Hi, I have the same problem. It's easy to replicate. Make a /tmp/test1 and /tmp/test2 directory. Touch a file in both directories and run kdiff3 to compare both directories. You will get the error 'Opening /tmp/test1/test failed. No such file or directory.' Stef
Bug#843530: docker.io: docker broken: oci runtime error: could not synchronize with container process
On 08.11.2016 18:52, Tianon Gravi wrote: > Ouch, looks like we're now hitting > https://github.com/opencontainers/runc/issues/1175, which doesn't > appear to have a Docker or runc workaround yet (although adding > "systemd.legacy_systemd_cgroup_controller=yes" to your system boot > parameters should do the trick for now). :( Thanks. Good to know. In case you're interested: In the Cockpit project we actively integrate Linux (including Debian) and here's a page that will track when this specific issue occurs during integration testing: https://github.com/cockpit-project/cockpit/issues/5340 Stef
Bug#843530: docker.io: docker broken: oci runtime error: could not synchronize with container process
On 07.11.2016 16:44, Tianon Gravi wrote: > On 7 November 2016 at 05:34, Stef Walter <s...@thewalter.net> wrote: >> The docker package is unfortunately currently broken. It fails to run >> containers and instead produces the following message: >> >> rpc error: code = 2 desc = "oci runtime error: could not synchronise with >> container process: no subsystem for mount" >> >> This can be reproduced by running something like: >> >> docker run -ti busybox /bin/sh >> >> Or any similar command. > > Can you please provide the relevant log lines from the daemon? > > (Either "/var/log/docker.log" or "journalctl -u docker.service") Sure thing. Here you go. The full file is attached. The relevant lines are: Nov 08 04:04:29 unassigned-hostname docker[5826]: time="2016-11-08T04:04:29-05:00" level=error msg="containerd: start container" error="oci runtime error: could not synchronise with container process: no subsystem for mount" id=4be1274a79c35a25c0ef70a866f4d20b03e5a7bf3cf60131ae49ef0ef11bfb59 Nov 08 04:04:29 unassigned-hostname docker[5826]: time="2016-11-08T04:04:29.430453214-05:00" level=error msg="Handler for POST /v1.23/containers/4be1274a79c35a25c0ef70a866f4d20b03e5a7bf3cf60131ae49ef0ef11bfb59/start returned error: rpc error: code = 2 desc = \"oci runtime error: could not synchronise with container process: no subsystem for mount\"" In case it helps, here is a compressed qemu/libvirt qcow2 image which replicates this issue: https://fedorapeople.org/groups/cockpit/images/debian-unstable-e20afebbfad06c2ba3d4573c71ec6ece14ead4a6.qcow2.xz Stef -- Logs begin at Tue 2016-11-08 02:16:38 EST, end at Tue 2016-11-08 04:04:29 EST. -- Nov 08 04:04:27 unassigned-hostname systemd[1]: Starting Docker Application Container Engine... Nov 08 04:04:27 unassigned-hostname docker[5826]: time="2016-11-08T04:04:27.737449987-05:00" level=info msg="New containerd process, pid: 5829\n" Nov 08 04:04:28 unassigned-hostname docker[5826]: time="2016-11-08T04:04:28.767716036-05:00" level=info msg="[graphdriver] using prior storage driver \"overlay\"" Nov 08 04:04:28 unassigned-hostname docker[5826]: time="2016-11-08T04:04:28.797969887-05:00" level=info msg="Graph migration to content-addressability took 0.00 seconds" Nov 08 04:04:28 unassigned-hostname docker[5826]: time="2016-11-08T04:04:28.808881857-05:00" level=info msg="Firewalld running: false" Nov 08 04:04:28 unassigned-hostname docker[5826]: time="2016-11-08T04:04:28.924174351-05:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address" Nov 08 04:04:29 unassigned-hostname docker[5826]: time="2016-11-08T04:04:29.013499004-05:00" level=warning msg="Your kernel does not support swap memory limit." Nov 08 04:04:29 unassigned-hostname docker[5826]: time="2016-11-08T04:04:29.017007389-05:00" level=info msg="Loading containers: start." Nov 08 04:04:29 unassigned-hostname docker[5826]: time="2016-11-08T04:04:29.018738290-05:00" level=info msg="Loading containers: done." Nov 08 04:04:29 unassigned-hostname docker[5826]: time="2016-11-08T04:04:29.019102560-05:00" level=info msg="Daemon has completed initialization" Nov 08 04:04:29 unassigned-hostname docker[5826]: time="2016-11-08T04:04:29.019153274-05:00" level=info msg="Docker daemon" commit=b9f10c9 graphdriver=overlay version=1.11.2 Nov 08 04:04:29 unassigned-hostname systemd[1]: Started Docker Application Container Engine. Nov 08 04:04:29 unassigned-hostname docker[5826]: time="2016-11-08T04:04:29.100046437-05:00" level=info msg="API listen on /var/run/docker.sock" Nov 08 04:04:29 unassigned-hostname docker[5826]: time="2016-11-08T04:04:29-05:00" level=error msg="containerd: start container" error="oci runtime error: could not synchronise with container process: no subsystem for mount" id=4be1274a79c35a25c0ef70a866f4d20b03e5a7bf3cf60131ae49ef0ef11bfb59 Nov 08 04:04:29 unassigned-hostname docker[5826]: time="2016-11-08T04:04:29.430453214-05:00" level=error msg="Handler for POST /v1.23/containers/4be1274a79c35a25c0ef70a866f4d20b03e5a7bf3cf60131ae49ef0ef11bfb59/start returned error: rpc error: code = 2 desc = \"oci runtime error: could not synchronise with container process: no subsystem for mount\""
Bug#843530: docker.io: docker broken: oci runtime error: could not synchronize with container process
Package: docker.io Version: 1.11.2~ds1-6 Severity: grave Justification: renders package unusable The docker package is unfortunately currently broken. It fails to run containers and instead produces the following message: rpc error: code = 2 desc = "oci runtime error: could not synchronise with container process: no subsystem for mount" This can be reproduced by running something like: docker run -ti busybox /bin/sh Or any similar command. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages docker.io depends on: ii adduser 3.115 ii containerd 0.2.1~ds1-3 ii init-system-helpers 1.46 ii iptables 1.6.0-4 ii libapparmor1 2.10.95-5 ii libc62.24-5 ii libdevmapper1.02.1 2:1.02.133-1 ii libsqlite3-0 3.15.1-1 ii libsystemd0 232-2 ii runc 0.1.1+dfsg1-1 Versions of packages docker.io recommends: ii ca-certificates 20161102 ii cgroupfs-mount 1.3 ii git 1:2.10.2-2 ii xz-utils 5.2.2-1.2 Versions of packages docker.io suggests: pn aufs-tools pn btrfs-progs ii debootstrap 1.0.86 pn docker-doc pn rinse pn zfs-fuse | zfsutils -- no debconf information
Bug#760102: gnome keyring gpg agent
On 05.06.2015 06:20, Daniel Kahn Gillmor wrote: Control: retitle 760102 gnome-keyring: please build with --disable-gpg-agent Control: block 760102 with 787786 On Thu 2015-06-04 22:30:21 -0400, Neal H. Walfield wrote: At Thu, 04 Jun 2015 22:14:25 -0400, Daniel Kahn Gillmor wrote: - An update to Gnome-Keyring that disables it GPG Agent proxy. Maybe we need to offer them a patch. the goal here is just to disable gnome-keyring's gpg-agent proxy implementation by default, right? That's correct. It should be sufficient to configure gnome keyring with --disable-gpg-agent (but I haven't tested this). that would make it so that users who wanted to use gnome-keyring as the gpg-agent (e.g. those who don't have smartcards, don't use gpgsm, and who otherwise ignore the concerns Werner has raised about gnome-keyring's incomplete gpg-agent support) would be unable to do so. It's a more invasive change than just disabling the functionality as per runtime defaults. Then again, that might keep us from dealing with a lot of extra bug reports :) I spoke with Stef (the maintainer of GNOME Keyring, cc'ed) and he agrees that removing the proxy is the correct way forward. The only reason that the proxy exists is to cache passwords. pinentry-gnome3 does exactly that in a cleaner way. In other words: it makes the proxy completely redundant. A GSoC student is working on finishing the changes to GNOME Keyring and pinentry-gnome3 (e.g., extending GCR to deal with all of GnuPG's prompts). Nevertheless, the current pinentry version already more complete than the proxy. Great, this sounds like a good assessment. I'm forwarding this info to https://bugs.debian.org/760102, which is already asking for some resolution of this situation. If gnome-keyring can Depend: pinentry-gnome3 (#787786), it should be able to build with --disable-gpg-agent. Thanks for your work on this, all the coordination. Great work, Neal. Confirming that I'll be ready to remove the code once the new pinentry makes it into a release. Removing code always makes me smile :) /me guesses there will be a few pieces to pick up. eg: figuring out how to enable the new pinentry by default when running in GNOME. But it's early in the GNOME 3.17 6 month release cycle and we can work that out after removal of the agent. Stef -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751907: Re: Bug#751907: libffi6: cannot enable executable stack as shared object requires: Permission denied
On Fri, Aug 22, 2014 at 02:39:15PM +0200, Matthias Klose wrote: Control: severity -1 important when using grsecurity/pax protections so nothing is broken for a default install. true. but the default install maybe also needs a bugreport for lack of grsec protection. ;) patch should be available from: http://git.overlays.gentoo.org/gitweb/?p=proj/hardened-dev.git;a=blob;f=dev-libs/libffi/files/libffi-3.0.12-emutramp_pax.patch;h=4799b227e8510c3a254a97355f341d7f8af404f0;hb=6eeb6a6c620ee84e411f989cc246212422e8b636 no, it is not. times out. sorry, i hope this one does not time out for you: https://sourceware.org/ml/libffi-discuss/2012/msg00247.html https://sourceware.org/ml/libffi-discuss/2013/msg00130.html cheers,s -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728312: gnome-keyring RC bug – GNOME Bugzilla – Bug 711222
On 16.08.2014 11:35, Martin-Éric Racine wrote: Hey Stef!, As reported at GNOME Bugzilla – Bug 711222 [1] there are some serious issues with gnome-keyring that have resulted in the package being marked as unfit for release. As you seem to be the main contributor to this package, could you please look into this? Makes sense. Commented on the bug. Cheers, Stef -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751907: libffi6: cannot enable executable stack as shared object requires: Permission denied
Package: libffi6 Version: 3.1-2 Severity: critical Tags: security patch Justification: breaks the whole system when using grsecurity/pax protections on debian unstable, the newest libffi6 breaks almost everything. some examples: # emacs emacs: error while loading shared libraries: libffi.so.6: cannot enable executable stack as shared object requires: Permission denied # mutt mutt: error while loading shared libraries: libffi.so.6: cannot enable executable stack as shared object requires: Permission denied similarly ck-session-launch, gsettings, and other binaries are affected. patch should be available from: http://git.overlays.gentoo.org/gitweb/?p=proj/hardened-dev.git;a=blob;f=dev-libs/libffi/files/libffi-3.0.12-emutramp_pax.patch;h=4799b227e8510c3a254a97355f341d7f8af404f0;hb=6eeb6a6c620ee84e411f989cc246212422e8b636 -- System Information: Debian Release: jessie/sid Architecture: i386 (x86_64) Kernel: Linux 3.12.6-grsec (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libffi6 depends on: ii libc6 2.19-2 ii multiarch-support 2.19-2 libffi6 recommends no packages. libffi6 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751907: patch possibly unrelated?
i just downgraded libffi6:i386 3.1-2 - 3.1~rc1+r3.0.13-12 and all seems to be working again. since the patch is against 3.0.12 i suppose it might not be the solution to this problem, will investigate further. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740429: fonts-crosextra-carlito: please backport fonts-crosextra-carlito and fonts-crosextra-caladea to wheezy-backports
Package: fonts-crosextra-carlito Severity: wishlist Dear Maintainer, Would it be possible to backport fonts-crosextra-carlito and fonts-crosextra- caladea from jessie to wheezy-backports? Thanks StefCT -- System Information: Debian Release: 7.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712893: dpkg-reconfigure locales: Add info about using space bar to toggle locales
Package: dpkg Version: 1.16.10 Severity: wishlist Dear Maintainer, In dpkg-reconfigure locales the user can press the space bar to toggle the locale under the cursor. However, this info is not provided by the user interface. Personally I had a rather hard time figuring out how to select more than one locale because of this. Currently there is only the following info: Locales are a framework to switch between multiple languages and allow users to use their language, country, characters, collation order, etc. Please choose which locales to generate. UTF-8 locales should be chosen by default, particularly for new installations. Other character sets may be useful for backwards compatibility with older systems and software. I'd suggest changing the second part to something like this: Please choose which locales to generate. Pressing the space bar toggles the locale under the cursor. (...) Thanks for listening! StefCT -- System Information: Debian Release: 7.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dpkg depends on: ii libbz2-1.0 1.0.6-4 ii libc62.13-38 ii liblzma5 5.1.1alpha+20120614-2 ii libselinux1 2.1.9-5 ii tar 1.26+dfsg-0.1 ii zlib1g 1:1.2.7.dfsg-13 dpkg recommends no packages. Versions of packages dpkg suggests: ii apt 0.9.7.8 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703557: opensc: pls update to 0.13.0
Package: opensc Version: 0.12.2-3 Severity: wishlist Tags: upstream A new was released on 04.12.2012. thanks for packaging! -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Kernel: Linux 3.7.7-grsec (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages opensc depends on: ii libc6 2.13-38 ii libltdl7 2.4.2-1.2 ii libreadline6 6.2+dfsg-0.1 ii libssl1.0.0 1.0.1e-2 ii zlib1g1:1.2.7.dfsg-13 opensc recommends no packages. opensc suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659521: bug confirmed on debian testing installation
I confirm the bug on my laptop, equipped with AR9285 (module ath9k) wireless chip. the laptop (samsung N220 netbook) has a fairly clean debian testing installation, after kernel upgrade from 3.1.0-1-686-pae to 3.2.0-1-686-pae connection to a wifi router with WEP encryption (*) does not work anymore. i can setup the interface with manual ifconfig / iwconfig commands, no errors are reported, some wireless functionality is present, for example running iwlist wlan0 scan gives me router wifi channel, executing 'iwconfig wlan0' shows me the wifi interface is associated with the router, so everything seems correct. But no packets are transmitted nor received over the wireless link. I have manually installed the older 3.1.0-2 kernel (vmlinuz, initrd, /lib/modules/3.1.0-1-686-pae stuff) , added a menu entry in grub, rebooting the laptop with the older kernel fixes the problem, the wifi network works as it used to do before the kernel upgrade. --- .(*) i know , wep is broken and flawed and should be avoided, i know the risk, and the environment where i use this old router is safe enough the router does not support newer protocols (WPA) and i dont want to spend money :-)
Bug#651595: ANNOUNCE: p11-kit 0.9
I gave up trying to build a custom gcc track this down, but here's my thinking, and what I did to get around it: * The optimization bug seems to be in gcc 4.6.1, and is triggered in a corner case. * The bug seems to be fixed in 4.6.2. * I've rearranged the testing code so the bug is no longer triggered on gcc 4.6.1 How does that sound? Acceptable? Cheers, Stef On 12/14/2011 07:08 PM, Andreas Metzler wrote: On 2011-12-14 Stef Walter st...@collabora.co.uk wrote: On 2011-12-10 11:06, Andreas Metzler wrote: [...] The minimal change I found was to just build CuFailInternal() without optimization, by setting __attribute__((optimize(O0))) static void CuFailInternal(CuTest* tc, const char* file, int line, CuString* string) Hmmm, I can see this behavior now. If I slightly rearrange any code it goes away, and that's why it may be that the above seemingly unrelated change fixes the issue. What's happening is that in the test__p11_hash_set_get_clear() gcc is reordering function calls. The line _p11_hash_clear() is running after the last _p11_hash_get() call, even though it's located before it. I've verified this with output to stderr :( So I'm a bit stuck, not sure if I should just refactor the tests to get around the obviously broken compiler, or should I try and take this upstream? Trying to track down where... The gcc version that I can replicate the issue on is Ubuntu/Linaro 4.6.1-9ubuntu3. [...] Hello, FWIW I have tried reporting this to the Debian bts http://bugs.debian.org/651595 (bug report cced) cu andreas ___ p11-glue mailing list p11-g...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/p11-glue -- -- Collabora: http://www.collabora.com Personal: http://stef.thewalter.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629874: fusecompress: workaround
Package: fusecompress Version: 2.6.4 Followup-For: Bug #629874 for those people, how find this via google, here's a workaround, even if the pkg is discontinued in debian: i have tracked down the problem to libboost_serialization1. if i compile with 1.42 (or install from snapshot.debian.org i'm able to read the old files. however files written with the 1.46 version of libboost_serialization need already the new version to read. i guess the serialization format has changed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629874: Unable to open files created with older version
Package: fusecompress Version: 2.6.git913897f4-1 Followup-For: Bug #629874 when accessing files on a mounted fusecompress volume, syslog is splattered with: FuseCompress: int Compress::open(const char*, int): Failed to restore LayerMap of file 'testfile:2,RS', exception: requested integer size exceeds type size: 99 messages. using fusecompress_offline yields: fusecompress_offline testfile Processing file (/home/s/tmp/fc/testfile) Temporary file (/home/s/tmp/fc/MDWC2g) File (/home/s/tmp/fc/testfile) cannot be opened! (Input/output error) while syslog contains the same message as above. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.37-2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages fusecompress depends on: ii libboost-filesystem1.46 1.46.1-6 filesystem operations (portable pa ii libboost-iostreams1.46. 1.46.1-6 Boost.Iostreams Library ii libboost-program-option 1.46.1-6 program options library for C++ ii libboost-serialization1 1.46.1-6 serialization library for C++ ii libboost-system1.46.1 1.46.1-6 Operating system (e.g. diagnostics ii libbz2-1.0 1.0.5-6 high-quality block-sorting file co ii libc6 2.13-10 Embedded GNU C Library: Shared lib ii libfuse22.8.5-4 Filesystem in Userspace (library) ii libgcc1 1:4.6.1-4GCC support library ii liblzma25.0.0-2 XZ-format compression library ii liblzo2-2 2.05-1 data compression library ii libmagic1 5.04-5+b1File type determination library us ii libstdc++6 4.6.1-4 GNU Standard C++ Library v3 ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime fusecompress recommends no packages. fusecompress suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592768: complementary information
Right here is the diagnostic of why it fails: Compiled the stuff with CFLAGS=-g to trace the execution. Here is my diagnostic: run -B . -N locale -E UTF-8 -Epathname 1:1 -Emisc 1:1 -norc -m 2MW -lp -x '(and (load init.lisp) (sys::%saveinitmem) (ext::exit)) (ext::exit t)' Starting program: /home/luigi/comp/dev/clisp/src/lisp.run -B . -N locale -E UTF-8 -Epathname 1:1 -Emisc 1:1 -norc -m 2MW -lp -x '(and (load init.lisp) (sys::%saveinitmem) (ext::exit)) (ext::exit t)' i i i i i i i ooooo o o I I I I I I I 8 8 8 8 8 o 88 I \ `+' / I 8 8 8 888 \ `-+-' / 8 8 8 o 8 `-__|__-'8 8 8 8 8 |8 o 8 8 o 8 8 --+-- o8oo ooo8ooo o 8 Welcome to GNU CLISP 2.49 (2010-07-07) http://clisp.cons.org/ Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998 Copyright (c) Bruno Haible, Sam Steingold 1999-2000 Copyright (c) Sam Steingold, Bruno Haible 2001-2010 Type :h and hit Enter for context help. ;; Loading file defseq.lisp ... ;; Loaded file defseq.lisp ;; Loading file backquote.lisp ... ;; Loaded file backquote.lisp Program received signal SIGSEGV, Segmentation fault. gc_morris2 () at spvw_garcol.d:404 404 var object next_obj = *(gcv_object_t*)p; (gdb) bt #0 gc_morris2 () at spvw_garcol.d:404 #1 gar_col_normal () at spvw_garcol.d:2327 #2 0x10028158 in do_gar_col_simple () at spvw_garcol.d:3028 #3 0x100eecd8 in with_gc_statistics (fun=0x10028110 do_gar_col_simple) at predtype.d:3162 #4 0x10020adc in gar_col_simple (need=184, heapptr=value optimized out) at spvw_garcol.d:3036 #5 make_space_gc_true (need=184, heapptr=value optimized out) at spvw_allocate.d:282 #6 0x10022028 in allocate_xrecord_ (flags_rectype=38, reclen=22, recxlen=88) at spvw_typealloc.d:428 #7 0x100244a8 in allocate_stream (strmflags=value optimized out, strmtype=12 '\f', reclen=value optimized out, recxlen=value optimized out) at spvw_typealloc.d:445 #8 0x10074404 in make_buffered_stream (type=value optimized out, direction=DIRECTION_INPUT_IMMUTABLE, eltype=0x6440, handle_regular=true, handle_blockpositioning=true) at stream.d:7928 #9 0x10075708 in make_file_stream (direction=DIRECTION_INPUT_IMMUTABLE, append_flag=false, handle_fresh=true) at stream.d:8143 #10 0x10057448 in open_file (filename=value optimized out, direction=DIRECTION_INPUT_IMMUTABLE, if_exists=647131784, if_not_exists=value optimized out) at pathname.d:6872 #11 0x10057648 in C_open () at pathname.d:6916 #12 0x1002fafc in eval_fsubr (form=0x69a102c3) at eval.d:3263 #13 eval1 (form=0x69a102c3) at eval.d:3101 #14 0x10030bbc in eval (form=value optimized out) at eval.d:2966 #15 0x1003191c in funcall_iclosure (closure=value optimized out, args_pointer=0xf7d5129c, argcount=1) at eval.d:2744 #16 0x1003bb68 in eval_closure (closure=value optimized out) at eval.d:3935 #17 0x1002fdb8 in eval1 (form=0x69a0f9bb) at eval.d:3091 #18 0x10030bbc in eval (form=value optimized out) at eval.d:2966 #19 0x10047c34 in C_setq () at control.d:199 #20 0x1002fafc in eval_fsubr (form=0x69a0fa0b) at eval.d:3263 #21 eval1 (form=0x69a0fa0b) at eval.d:3101 #22 0x10030bbc in eval (form=value optimized out) at eval.d:2966 #23 0x1003fecc in C_if () at control.d:1200 #24 0x1002fafc in eval_fsubr (form=0x69a0fa1b) at eval.d:3263 #25 eval1 (form=0x69a0fa1b) at eval.d:3101 #26 0x10030bbc in eval (form=value optimized out) at eval.d:2966 #27 0x100439cc in C_tagbody () at control.d:1645 #28 0x1002fafc in eval_fsubr (form=0x69a0fd3b) at eval.d:3263 #29 eval1 (form=0x69a0fd3b) at eval.d:3101 #30 0x10030bbc in eval (form=value optimized out) at eval.d:2966 #31 0x10047138 in C_labels () at control.d:1031 #32 0x1002fafc in eval_fsubr (form=0x69a0d1db) at eval.d:3263 #33 eval1 (form=0x69a0d1db) at eval.d:3101 #34 0x10030bbc in eval (form=value optimized out) at eval.d:2966 #35 0x100449e8 in C_block () at control.d:1318 #36 0x1002fafc in eval_fsubr (form=0x69a0d1bb) at eval.d:3263 #37 eval1 (form=0x69a0d1bb) at eval.d:3101 #38 0x10030bbc in eval (form=value optimized out) at eval.d:2966 #39 0x1003191c in funcall_iclosure (closure=value optimized out, args_pointer=0xf7d51154, argcount=3) at eval.d:2744 #40 0x1003bb68 in eval_closure (closure=value optimized out) at eval.d:3935 #41 0x1002fdb8 in eval1 (form=0x69a0f293) at eval.d:3091 #42 0x10030bbc in eval (form=value optimized out) at eval.d:2966 #43 0x1004536c in C_multiple_value_setq () at control.d:1894 #44 0x1002fafc in eval_fsubr (form=0x69a0f2b3) at eval.d:3263 #45 eval1 (form=0x69a0f2b3) at eval.d:3101 #46 0x10030bbc in eval (form=value optimized out) at eval.d:2966 #47 0x1003191c in funcall_iclosure (closure=value optimized out,
Bug#592768: complementary information
This was a little tricky. I successfully built and installed libsigsegv2_2.8 binary+dev Then the git build-package was successful, nonetheless it is uninstallable: # LANG=C dpkg -i ../clisp_2.49-1_powerpc.deb (Reading database ... 203838 files and directories currently installed.) Preparing to replace clisp 1:2.49-1 (using ../clisp_2.49-1_powerpc.deb) ... Unpacking replacement clisp ... Setting up clisp (1:2.49-1) ... Installing clc... rebuilding /usr/lib/clisp-2.49/base/lispinit.mem from /usr/lib/clisp-2.49/base/lispinit-orig.mem ;; Loading file /usr/lib/clisp-2.49/install-clc.lisp ... ;; Loading file /usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.lisp ... ;; Loaded file /usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.lisp ;; Loading file /var/cache/common-lisp-controller/0/clisp/common-lisp-controller/common-lisp-controller.fas ... ;; Loaded file /var/cache/common-lisp-controller/0/clisp/common-lisp-controller/common-lisp-controller.fasSegmentation fault Building of new image failed! dpkg: error processing clisp (--install): subprocess installed post-installation script returned error exit status 4 Processing triggers for man-db ... Errors were encountered while processing: clisp # Any idea? Something to try in order to help? 2010/9/27 Peter Van Eynde pvane...@debian.org: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Stef, On 22/09/10 21:53, stef louise wrote: I may have some time to check it by the end of the week. I know how to compile stuff, even quite complex projects, but I'm quite unfamiliar with git (even though I shouldn't), and I don't know where to find your git repository (googled a lil' bit but wrong keywords, I guess). You can do: git clone http://git.debian.org/git/pkg-common-lisp/clisp.git git checkout pvaneynd LC_ALL=C LANG=C git-buildpackage -uc -us --git-debian-branch=pvaneynd that should just work (TM). Best regards, Peter -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJMoN9sAAoJEB4VNT76eIlaFW0P/RAK0+hm+WY0wxEb/1ZOUONA AxuXVgn1FsCn9jGzcDuUVYGAVg6fWi93PWlTaX/qPuzOMku3E6N9sZcm3ajRx2Px c/zrS6DAgVwK8OYvofIIwXiyBWX9jwzvNfqIbBTLuAPrp2kEAjJq+31BxZXR9+un H/teNt21vaZwlRCA2URWKOQvnwHeBv0aJqG/wPBycIEbGw/zi8h8uXHFLuQoMlBl n1Dp34InDB3YVx/2t5NTKqbEhsMC6N8wHubd3Cb04gyUWBTxrRte386MqA3zTnS+ mbo0fiyh2qHjZBDphoSsUJJzge/v9NOrrevof6+ZvK6k2ns5utOOKYR+PluGWNEn J5qKh6q8CZ5UEr1tCx+XNK/yrwvstLy1UrOPgi6U7K6ZivDPzbxhNkjomZ7Hewec 3itKo5Ojr/ETfn9sDvqFf4bSzPPbMO89Rh/GIUs/E7tTlmtdhoT6/KubSHg+yKvc 4flfF4/pYIm2fP0ssUfHR8gB17dc8c6Wti+LObwXir/kAdMRnllUqWG2/rg3pkgY UCR7ORlOC/a3ctlg4h/wiFykXOgRPX/FOYyZly6pZKbAjghT9lOrGmaEWsD/BR7j knDsiVHyZROc9UDEOCTbhjw+99kbTy1QLZGs3wqzd6CBlGJiDXslWl1Mll3gVgo5 AS4li1ASyT8iALe2RRGV =5PZM -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592768: complementary information
I may have some time to check it by the end of the week. I know how to compile stuff, even quite complex projects, but I'm quite unfamiliar with git (even though I shouldn't), and I don't know where to find your git repository (googled a lil' bit but wrong keywords, I guess). Stéphane 2010/9/17 Peter Van Eynde pvane...@mailworks.org: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Stef, On 16/09/10 21:57, stef louise wrote: /usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.lisp *** - handle_fault error2 ! address = 0x77dc3ba0 not in [0x699c60d8,0x69aa3000) ! I have a new clisp version prepared with a new upstream version that builds correctly on the build-machine I tried. You can either try the pvaneynd branch in the git repository or wait until I have some time to prepare and upload to experimental. Best regards, Peter -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJMkvrQAAoJEB4VNT76eIla+4IQAIhEVVtx+6w6iYJrQKZl5tPE giEoX9w3Q8+65dkuQHh+9ndw3wj+WU3r0YsbrBh67WMLYMg3UKnGijtqd7i6uZmJ oKnCblYT79G2yGmVtV7AkGjOVU7FVmcIicEgULKZ0plGmsD4RYLoqiEPK61lqEHS zfb7vfXNVUZbc0HjP8Guez9/gW4+jxYnpOixq9G5ctTwD/P+405qFkth7ZFAojcI B7a1QmP5VmmSu+LDiAp8N/3zll4qkIjCq8RphChKIJ6d0fGJ8hmHPfNremnI3YG/ RE0FMG/9fkQ+RK0Y+8v6L8+3GjFvlroWvJIQdIkyLJSmgo4TMIABBATQxrtuQwmO rkdDwLbXAxY3uD1CI6ueAobDYUdDqSCJfqj6fkNbY2i+ktrYJNUxwSEDuB5Axhoz H4jP2F0ZfTZ/HoALk8d97QNoLlfxGJJb+uhWeOXB4zB1J+ttJiMxyZKwuEM/HNUc 5j9qxpcIGuyMtwSbCyTtkRLM0yhkW8eMF54mmHH4fzr6jqMo1fDsSF3MINNi4Nfs nEDRrJHwPptJqnAATBTUZTQO8FkvPXnLbDSzgRd/sy/qNgNu4DruEmroD7E1nSTg drindQSzPTr/KT1Jq0Nrg68UQFPCy262D/4nJOLstK2Lm6rbF/Hdp19YTOSR6n6o 9gnsy7vbGRVRMUyWLOcs =i78Z -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592768: complementary information
Hi,
This bug seems quite quiet for a grave bug (the update manager refuse
to work since then).
I tried to use dpkg which seems to give more accurate messages for
common-lisp installation:
# LANG=C dpkg -i /var/cache/apt/archives/common-lisp-controller_7.4_all.deb
(Reading database ... 196004 files and directories currently installed.)
Preparing to replace common-lisp-controller 7.4 (using
.../common-lisp-controller_7.4_all.deb) ...
Unpacking replacement common-lisp-controller ...
Setting up common-lisp-controller (7.4) ...
Reinstalling for clisp
Recompiling Common Lisp Controller for clisp
Installing clc...
;; Loading file /usr/lib/clisp-2.48/install-clc.lisp ...
;; Loading file
/usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.lisp
...
;; Loaded file
/usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.lisp
*** - handle_fault error2 ! address = 0x77dc3ba0 not in
[0x699c60d8,0x69aa3000) !
SIGSEGV cannot be cured. Fault address = 0x77dc3ba0.
GC count: 0
Space collected by GC: 0 0
Run time: 0 42538
Real time: 0 276550
GC time: 0 0
Permanently allocated: 108736 bytes.
Currently in use: 3721376 bytes.
Free space: 14 bytes.
/usr/lib/common-lisp/bin/clisp.sh: line 16: 4303 Segmentation fault
${builder} -norc -q -M ${orig_mem} -on-error exit -x
(handler-case
(progn
(when (find-package :c-l-c) ; have to remove
(delete-package :c-l-c)) ; for clisp workaround
(load \$clisp_dir/install-clc.lisp\)
(saveinitmem \${target_mem}\)
(ext:exit 0))
(error (e)
(ignore-errors (format t \~install-clc error: ~A~%\ e))
(finish-output)
(ext:exit 1)))
Building of new image failed!
Done rebuilding
Processing triggers for man-db ...
I'd like to help further, but is there some easy way to provide more feedback?
regards
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592768: Fwd: Bug#592768: complementary information
It's an up to date testing system (testing is more reasonable than sid
on unusual architecture like PPC), so it is 2.004 if I understand your
question.
$ apt-cache show cl-asdf
Package: cl-asdf
Priority: optional
Section: lisp
Installed-Size: 1296
Maintainer: Debian Common Lisp Team
pkg-common-lisp-de...@lists.alioth.debian.org
Architecture: all
Version: 2:2.004-1
Replaces: sbcl-common (= 1:0.9.13.0-2)
Depends: common-lisp-controller (= 5.11), dpkg (= 1.15.4) | install-info
Recommends: sbcl | lisp-compiler
Conflicts: common-lisp-controller (= 7.0), sbcl-common (= 1:0.9.13.0-2)
Breaks: common-lisp-controller (= 7.0)
Filename: pool/main/c/cl-asdf/cl-asdf_2.004-1_all.deb
Installing 2.008 doesn't help. Same problem here. Tracking the bug is
a bit time consuming for s.o. who doesn't know very well the system. I
tried a bit, but I must chroot for testing and I didn't suceed
(doesn't find the shell).
Regards
Stephane
2010/9/16 Faré fah...@gmail.com:
What version of clisp are you using? asdf 2.007 is incompatible with
old clisp. asdf 2.008 includes compatibility with old clisp. Does
upgrading asdf to a recent package help?
Otherwise, can you use printf or dichotomy debugging to identify where
precisely this script fails?
[ François-René ÐVB Rideau | ReflectionCybernethics | http://fare.tunes.org ]
Never abandon a theory that explains something until you have a theory that
explains more. — John McCarthy
On 16 September 2010 15:57, stef louise stephane.r.lou...@gmail.com wrote:
Hi,
This bug seems quite quiet for a grave bug (the update manager refuse
to work since then).
I tried to use dpkg which seems to give more accurate messages for
common-lisp installation:
# LANG=C dpkg -i /var/cache/apt/archives/common-lisp-controller_7.4_all.deb
(Reading database ... 196004 files and directories currently installed.)
Preparing to replace common-lisp-controller 7.4 (using
.../common-lisp-controller_7.4_all.deb) ...
Unpacking replacement common-lisp-controller ...
Setting up common-lisp-controller (7.4) ...
Reinstalling for clisp
Recompiling Common Lisp Controller for clisp
Installing clc...
;; Loading file /usr/lib/clisp-2.48/install-clc.lisp ...
;; Loading file
/usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.lisp
...
;; Loaded file
/usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.lisp
*** - handle_fault error2 ! address = 0x77dc3ba0 not in
[0x699c60d8,0x69aa3000) !
SIGSEGV cannot be cured. Fault address = 0x77dc3ba0.
GC count: 0
Space collected by GC: 0 0
Run time: 0 42538
Real time: 0 276550
GC time: 0 0
Permanently allocated: 108736 bytes.
Currently in use: 3721376 bytes.
Free space: 14 bytes.
/usr/lib/common-lisp/bin/clisp.sh: line 16: 4303 Segmentation fault
${builder} -norc -q -M ${orig_mem} -on-error exit -x
(handler-case
(progn
(when (find-package :c-l-c) ; have to remove
(delete-package :c-l-c)) ; for clisp workaround
(load \$clisp_dir/install-clc.lisp\)
(saveinitmem \${target_mem}\)
(ext:exit 0))
(error (e)
(ignore-errors (format t \~install-clc error: ~A~%\ e))
(finish-output)
(ext:exit 1)))
Building of new image failed!
Done rebuilding
Processing triggers for man-db ...
I'd like to help further, but is there some easy way to provide more
feedback?
regards
___
pkg-common-lisp-devel mailing list
pkg-common-lisp-de...@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-common-lisp-devel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550662: Info received (Also on Mac mini / PowerPC)
OK, Sorry: bad copy of bug number... :/ I wanted to address bug #550562 You can erase my previous message. Sorry again and thank you. Stéphane
Bug#550662: Also on Mac mini / PowerPC
Hi, I am a mostly happy owner of (among others) a last model of the Mac Mini - PowerPC edition. These beasts came with a G4 MPC 7447a at 1.5GHz and a AGP Radeon 7250 (R280). I experienced the bug about the same time as Jean-Luc, it got better a little while, but really soon it was deadly again : no more accelerated OpenGL possible. With the last update, things got slightly better: at least the glxgear test doesn't kill the system anymore. That's not to say that it works either: the gears became a bunch of tiny triangles appearing randomly in the window. But it may be only a endianess issue. I am not sure. Of course any real OpenGL application will continue to succeed in freezing the system hard (e.g. any 3D game like NexUIz). I am also clueless about the source of the bug. I tend to remember like Jean-Luc that it was an X/mesa update that triggered the bug. No certainty nonetheless. Also as I read the thread it seems to be a bit tricky between the interaction of the firmware loader, the DRM layer of the kernel, DRI and maybe mesa and X. AFAIK, composing doesn't work either, and I heard some people experiencing some hard freeze also with radeon based mac with Debian testing. Let me know if I can help. Thanks for your attention and for your work. Stéphane
Bug#542858: Additionnal information about the trace
OK, sorry about that. I tried to disassemble the code and follow it a little, but one thing is clear : the level at which the blocking occurs is not the deepest one. It is too tricky for me to follow at assembly level though, as I am not yet fluent in PPC assembly. Moreover, each time I interrupt the program and I relaunch it, there is a bunch of threads being launched. That doesn't help. Hope you'll find the culprit. Regards. -- Stéphane
Bug#542858: Confirming this bug on PowerPC
Hi, I can confirm this bug on PowerPC. When trying to play a song, the processor use raise to 100% and Rhythmbox stalls. It looks like the usual let's assume all char on every plateform are signed char and let's do loops carelessfully kind of bug, but I may be wrong. I tried to make a backtrack in gbd but since it is a multithreaded program, I am not sure it is accurate. Nonetheless, here it is, if it may help: Program received signal SIGINT, Interrupt. 0x0fd0bec8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 (gdb) bt #0 0x0fd0bec8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x0ec2dc94 in ?? () from /usr/lib/libgthread-2.0.so.0 #2 0x0ed1ba7c in gst_bus_timed_pop_filtered () from /usr/lib/libgstreamer-0.10.so.0 #3 0x0ed1c204 in gst_bus_timed_pop () from /usr/lib/libgstreamer-0.10.so.0 #4 0x0ffa4958 in ?? () from /usr/lib/librhythmbox-core.so.0 #5 0x0ffa5dfc in ?? () from /usr/lib/librhythmbox-core.so.0 #6 0x0ffa0210 in rb_player_play () from /usr/lib/librhythmbox-core.so.0 #7 0x1002579c in ?? () #8 0x1002749c in rb_shell_player_playpause () #9 0x10027708 in ?? () #10 0x0ec95c8c in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #11 0x0ec83dc8 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #12 0x0eca0350 in ?? () from /usr/lib/libgobject-2.0.so.0 #13 0x0eca1a14 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #14 0x0eca1fcc in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #15 0x0f61b668 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #16 0x0f61e458 in gtk_action_activate () from /usr/lib/libgtk-x11-2.0.so.0 #17 0x0f811eec in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #18 0x0ec95c8c in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #19 0x0ec83dc8 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #20 0x0eca0350 in ?? () from /usr/lib/libgobject-2.0.so.0 #21 0x0eca1a14 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #22 0x0eca1fcc in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #23 0x0f63c6c8 in gtk_button_clicked () from /usr/lib/libgtk-x11-2.0.so.0 #24 0x0f8060b4 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #25 0x0ec95c8c in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #26 0x0ec81a88 in ?? () from /usr/lib/libgobject-2.0.so.0 #27 0x0ec83dc8 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #28 0x0ec9fb80 in ?? () from /usr/lib/libgobject-2.0.so.0 #29 0x0eca1a14 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #30 0x0eca1fcc in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #31 0x0f63c788 in gtk_button_released () from /usr/lib/libgtk-x11-2.0.so.0 #32 0x0f63c7d4 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #33 0x0f718754 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #34 0x0ec81a88 in ?? () from /usr/lib/libgobject-2.0.so.0 #35 0x0ec83dc8 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #36 0x0ec9ff50 in ?? () from /usr/lib/libgobject-2.0.so.0 #37 0x0eca1850 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #38 0x0eca1fcc in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #39 0x0f86a114 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #40 0x0f70e564 in gtk_propagate_event () from /usr/lib/libgtk-x11-2.0.so.0 #41 0x0f7100a4 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0 #42 0x0f51e058 in ?? () from /usr/lib/libgdk-x11-2.0.so.0 #43 0x0e9c83bc in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #44 0x0e9ccc48 in ?? () from /usr/lib/libglib-2.0.so.0 #45 0x0e9cd374 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #46 0x0f7105f4 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #47 0x10018ddc in main () Regards. -- Stéphane Louise
Bug#272627: Hiliary was happy with her result
Get better action from her every night Make your rod stronger and more powerful than ever http://www.bejuiela.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#408327: RFP: funionfs -- An Overlay or Union filesystem for FUSE
Package: wnpp Severity: wishlist * Package name: funionfs Version : 0.4.2 Upstream Author : Stephane APIOU [EMAIL PROTECTED] * URL : http://funionfs.apiou.org/ * License : GPL Programming Lang: C Description : An Overlay or Union filesystem for FUSE Funionfs is a filesystem which concatenate two or more directories. These directories are hierarchised by Funionfs. Typically, you could use a mounted filesystem wich is in read-only where you only read files and an upper filesystem (empty at the mount time) where you write modifications. Funionfs is very useful for embedded linux (the system must resist powerfail), for live-cd Linux or for diskless system where you mount derived root filesystems on your various remote systems. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing'), (300, 'stable'), (99, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-k7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#361418: [Proposal] new Debian menu structure
Greetings.. On Sun, 2006-04-09 at 07:36 +0200, Christian Perrier wrote: HAM is not an acronym, so Ham Radio would be more appropriate. Even better (IMHO) is the full term Amateur Radio, but some may disagree. I've CC'd debian-hams for their input also. HAM is probably well known among the amateur radio community. However, *outside* this community, the name is pretty cryptic (I have not idea, actually, what this H letter stands for). So, I would also second Amateur radio... I too feel Amateur Radio Would be the preferred Menu item.. rather than Ham. -- Regards - Stef VK5HSX Adelaide, Sth Australia -= Use Open Source Software =- GNU\Linux Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#246288: Getting a very similar segfault here
Hi. I could not run that program due to a segfault in the call to getgrouplist. After googling a little, I changed the 'compat' settings in /etc/nsswitch.conf to 'files nis' and all went well. Now dbus is up and running (and I gotta figure out how to make it do what I want, but that's anothing thing ;) Thanks a lot for your help. I'll probably try to forward this bug to the debian libc6 package. -- Stphane Epardaud
Bug#246288: Getting a very similar segfault here
Hi,
I'm getting a segfault too, rendering dbus useless. Any time a client
connects to it, it segfaults. I didn't manage to get a core dump even
when starting it myself with 'ulimit -c unlimited'.
However I've got some info. When I run the command
DBUS_VERBOSE=1 dbus-daemon-1 --system --nofork
I get this output:
9151: Allocated slot 0 on allocator 0x8090628 total 1 slots allocated 1 used
9151: No cache for UID 0
9151: No cache for UID 4294967295
9151: Using cache for UID 4294967295 information
9151: listening on unix socket /var/run/dbus/system_bus_socket abstract=0
9151: Initialized server on address unix:path=/var/run/dbus/system_bus_socket
9151: Adding a read watch on fd 3 using newly-set add watch function
9151: Allocated slot 0 on allocator 0x80905dc total 1 slots allocated 1 used
9151: No cache for UID 4294967295
9151: full-duplex pipe 4 - 5
9151: We are on D-Bus...
9151: Running main loop, depth 0 - 1
Then it waits, and if I try a connection to it by calling hal-device-manager
it goes on like this:
9151: Handling client connection, flags 0x1
9151: Creating new client connection with fd 6
9151: check_read_watch: fd = 6
9151: setting read watch enabled = 1
9151: check_write_watch(): needed = 0 on connection 0x809bab0 watch 0x809be00
fd = 6 outgoing messages exist 0
9151: Adding a write watch on fd 6 using newly-set add watch function
9151: Adding a read watch on fd 6 using newly-set add watch function
9151: dispatch status = complete is_connected = 1
9151: Connection 0x809bab0 authentication expires in 2 milliseconds
9151: Enabled expire timeout with interval 2
9151: Running expire_incomplete_timeout
9151: Connection 0x809bab0 authentication expires in 2 milliseconds
9151: Enabled expire timeout with interval 2
9151: handling read watch 0x80942e8 flags = 1
9151: read credentials byte
9151: Credentials: pid 9195 uid 1000 gid 1000
9151: server auth state: waiting for input
9151: check_read_watch: fd = 6
9151: setting read watch enabled = 1
9151: check_write_watch(): needed = 0 on connection 0x809bab0 watch 0x809be00
fd = 6 outgoing messages exist 0
9151: do_reading: fd = 6
9151: dispatch status = complete is_connected = 1
9151: handling read watch 0x80942e8 flags = 1
9151: server auth state: waiting for input
9151: read 24 bytes in auth phase
9151: server: got command AUTH EXTERNAL 31303030
9151: server: Trying mechanism EXTERNAL
9151: server: data: '1000'
9151: server: going from state WaitingForAuth to state WaitingForBegin
9151: server: authenticated client with UID 1000 matching socket credentials
UID 1000
9151: server auth state: bytes to send
9151: check_read_watch: fd = 6
9151: setting read watch enabled = 0
9151: check_write_watch(): needed = 1 on connection 0x809bab0 watch 0x809be00
fd = 6 outgoing messages exist 0
9151: do_reading: fd = 6
9151: dispatch status = complete is_connected = 1
9151: handling write watch, have_outgoing_messages = 0
9151: server auth state: bytes to send
9151: server: Sent 4 bytes of: OK
9151: server auth state: waiting for input
9151: check_read_watch: fd = 6
9151: setting read watch enabled = 1
9151: check_write_watch(): needed = 0 on connection 0x809bab0 watch 0x809be00
fd = 6 outgoing messages exist 0
9151: Not authenticated, not writing anything
9151: check_write_watch(): needed = 0 on connection 0x809bab0 watch 0x809be00
fd = 6 outgoing messages exist 0
9151: dispatch status = complete is_connected = 1
9151: handling read watch 0x80942e8 flags = 1
9151: server auth state: waiting for input
9151: read 7 bytes in auth phase
9151: server: got command BEGIN
9151: server: going from state WaitingForBegin to state Authenticated
9151: No cache for UID 1000
Segmentation fault
And there it dies.
If I try an strace around it, I get some calls to NIS (my system is a yp
client) that fail like:
socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 8
bind(8, {sa_family=AF_INET, sin_port=htons(918),
sin_addr=inet_addr(0.0.0.0)}, 16) = -1 EACCES (Permission denied)
connect(8, {sa_family=AF_INET, sin_port=htons(893),
sin_addr=inet_addr(192.168.14.1)}, 16) = 0
write(8, \200\0\0LIw\366\200\0\0\0\0\0\0\0\2\0\1\206\244\0\0\0\2..., 80) = 80
poll([{fd=8, events=POLLIN, revents=POLLIN}], 1, 25000) = 1
read(8, \200\0\10\\Iw\366\200\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0..., 4000) =
2144
close(8)= 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Somehow I'm not sure why it would bind a socket locally before connecting
it to the NIS server, but I'm not sure whether this is wrong or even related
to the segfault.
I'm running the latest debian unstable with dbus 0.23.
Please tell me if I should report this upstream or how to get more info
from my breakage, it's very frustrating.
Thanks.
--
Stphane Epardaud
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#246288: Getting a very similar segfault here
On Sun, Jan 16, 2005 at 07:03:30PM +0100, Sjoerd Simons wrote: The socket opening stuff is something your nisbindings do, not a dbus thing. Could you trace the daemon with ltrace and provide the last part of the output. Ok, thanks for the quick reply, here goes: memmove(0x809bc9d, 0x809bc98, 0, 0x80903d0, 0) = 0x809bc9d memcpy(0x809bc98, BEGIN, 5)= 0x809bc98 memmove(0x8091360, 0x8091365, 2, 0x80903d0, 0x809ba00) = 0x8091360 memmove(0x8091360, 0x8091362, 0, 0x80903d0, 0x809ba00) = 0x8091360 free(0x8093cf8) = void free(0x809bc98) = void calloc(24, 1)= 0x8093c38 getpwuid(1000, 0xb7f9f620, 1, 0xbfffed18, 0xb7ee0014) = 0xb7f9fe9c strlen(stephane) = 8 malloc(9)= 0x8093cf8 memcpy(0x8093cf8, stephane, 9) = 0x8093cf8 strlen(/home/stephane) = 14 malloc(15) = 0x809bc98 memcpy(0x809bc98, /home/stephane, 15) = 0x809bc98 malloc(68) = 0x8094310 getgrouplist(0x8093cf8, 1000, 0x8094310, 0xbfffed08, 0xb7ee0014 unfinished ... --- SIGSEGV (Segmentation fault) --- +++ killed by SIGSEGV +++ that's the last part, if you want what's before (and there's quite a few), do tell :) Your the first to give someusefull feedback :) Getting no feedback is also very frustrating.. Oh don't worry I'll give you all the info I can, thanks a lot for the help! -- Stphane Epardaud
