Bug#636874: gnome-shell bug
This may be the same bug as upstream: https://bugzilla.gnome.org/show_bug.cgi?id=647588 no updates there for a while though, and no resolution -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#398234: closed by Isaac Clerencia [EMAIL PROTECTED] (Fixed in 1.1.13)
Hi Isaac It crashes with 1.1.14 David On Thu, 2006-12-21 at 08:27 +0100, Isaac Clerencia wrote: On Thursday 21 December 2006 05:25, David Meggy wrote: This was fixed in version 1.1.13 No, it isn't fixed. Wesnoth still closes on loading that file. Do you have version 1.1.13 or 1.1.14? I uploaded 1.1.13 to experimental and then (yesterday) 1.1.14 to unstable so it's quite possible you are still using 1.1.12. If it still crashes with 1.1.13 or 1.1.14 we should have a look. Best regards -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#398234: closed by Isaac Clerencia [EMAIL PROTECTED] (Fixed in 1.1.13)
No, it isn't fixed. Wesnoth still closes on loading that file. David On Sun, 2006-12-17 at 07:49 -0800, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report #398234: wesnoth: Crashes with an assert message on loading a particular file, which was filed against the wesnoth package. It has been closed by Isaac Clerencia [EMAIL PROTECTED]. Their explanation is attached below. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Isaac Clerencia [EMAIL PROTECTED] by replying to this email. Debian bug tracking system administrator (administrator, Debian Bugs database) email message attachment Forwarded Message From: Isaac Clerencia [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Fixed in 1.1.13 Date: Sun, 17 Dec 2006 16:26:31 +0100 Version: 1.1.13-1 This was fixed in version 1.1.13 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#398234: wesnoth: Crashes with an assert message on loading a particular file
Package: wesnoth Version: 1.1.12-1 Severity: normal When I start wesnoth, load the following file, it crashes, and the following is displayed $ wesnoth Battle for Wesnoth v1.1.12 Started on Sun Nov 12 08:13:47 2006 started game: 3706857154 Checking video mode: 1278x952x32... 32 setting mode to 1278x952x32 locale could not be determined; defaulting to system locale set locale to found valid cache at '/home/dmeggy/.wesnoth/cache/game.cfg-cache-v1.1.12-MEDIUM-NORMAL' using it loadscreen: filesystem counter = 108 loadscreen: binarywml counter = 11349 loadscreen: setconfig counter = 221 loadscreen: parser counter = 202 started music 588111477 showing title screen... 588111477 Loading tips of day title screen returned result locale could not be determined; defaulting to system locale found valid cache at '/home/dmeggy/.wesnoth/cache/game.cfg-cache-v1.1.12-CAMPAIGN_SON_OF_THE_BLACK_EYE-EASY' using it error config: an animation uses the deprecated [sound] tag, please include sound in the [frame] tag error config: an animation uses the deprecated [sound] tag, please include sound in the [frame] tag error config: an animation uses the deprecated [sound] tag, please include sound in the [frame] tag error config: an animation uses the deprecated [sound] tag, please include sound in the [frame] tag scenario: 'Toward_Mountains_of_Haag' has snapshot: no skipping... error config: an animation uses the deprecated [sound] tag, please include sound in the [frame] tag error config: an animation uses the deprecated [sound] tag, please include sound in the [frame] tag error config: an animation uses the deprecated [sound] tag, please include sound in the [frame] tag error config: an animation uses the deprecated [sound] tag, please include sound in the [frame] tag wesnoth: unit_map.cpp:55: void unit_map::add(std::pairgamemap::location, unit*): Assertion `res.second' failed. Aborted -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-amd64 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages wesnoth depends on: ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries ii libfreetype62.2.1-5 FreeType 2 font engine, shared lib ii libfribidi0 0.10.7-4 Free Implementation of the Unicode ii libgcc1 1:4.1.1-19 GCC support library ii libsdl-image1.2 1.2.5-2+b1 image loading library for Simple D ii libsdl-mixer1.2 1.2.6-1.1+b1 mixer library for Simple DirectMed ii libsdl-net1.2 1.2.5-7+b1 network library for Simple DirectM ii libsdl1.2debian 1.2.11-7 Simple DirectMedia Layer ii libstdc++6 4.1.1-19 The GNU Standard C++ Library v3 ii libx11-62:1.0.3-2X11 client-side library ii python2.4 2.4.4-1 An interactive high-level object-o ii wesnoth-data1.1.12-1 data files for Wesnoth ii zlib1g 1:1.2.3-13 compression library - runtime wesnoth recommends no packages. -- no debconf information Toward_Mountains_of_Haag Description: video/unknown
Bug#388355: closed by [EMAIL PROTECTED] (martin f. krafft) (Bug#388355: fixed in mdadm 2.5.3.git200608202239-6)
Confirmed (by bug reporter), this bug fixes the issue with the segfault David On Thu, 2006-09-21 at 16:20 -0700, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report #388355: mdadm: Segfaults on sid upgrade, which was filed against the mdadm package. It has been closed by [EMAIL PROTECTED] (martin f. krafft). Their explanation is attached below. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact [EMAIL PROTECTED] (martin f. krafft) by replying to this email. Debian bug tracking system administrator (administrator, Debian Bugs database) email message attachment Forwarded Message From: martin f. krafft [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Bug#388355: fixed in mdadm 2.5.3.git200608202239-6 Date: Thu, 21 Sep 2006 15:47:15 -0700 Source: mdadm Source-Version: 2.5.3.git200608202239-6 We believe that the bug you reported is fixed in the latest version of mdadm, which is due to be installed in the Debian FTP archive: mdadm-udeb_2.5.3.git200608202239-6_amd64.udeb to pool/main/m/mdadm/mdadm-udeb_2.5.3.git200608202239-6_amd64.udeb mdadm_2.5.3.git200608202239-6.diff.gz to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-6.diff.gz mdadm_2.5.3.git200608202239-6.dsc to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-6.dsc mdadm_2.5.3.git200608202239-6_amd64.deb to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-6_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. martin f. krafft [EMAIL PROTECTED] (supplier of updated mdadm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 21 Sep 2006 15:25:21 +0200 Source: mdadm Binary: mdadm mdadm-udeb Architecture: source amd64 Version: 2.5.3.git200608202239-6 Distribution: unstable Urgency: high Maintainer: Debian mdadm maintainers [EMAIL PROTECTED] Changed-By: martin f. krafft [EMAIL PROTECTED] Description: mdadm - tool to administer Linux MD arrays (software RAID) mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb) Closes: 388355 Changes: mdadm (2.5.3.git200608202239-6) unstable; urgency=high . * Bumping urgency to high because previous version has been in unstable for three days and this one really only fixes a stupid segfault: * Reworked the parsing of /proc/partitions and spotted a mean segfault (closes: #388355). Files: 287559f4bdec4cf5f9c7b13e21766c02 760 admin optional mdadm_2.5.3.git200608202239-6.dsc a0bae5242e2fdc339e1ec2cf301a4b30 89878 admin optional mdadm_2.5.3.git200608202239-6.diff.gz 3b161283731dc45143ecc6ffc599af25 195896 admin optional mdadm_2.5.3.git200608202239-6_amd64.deb e1c951fbf4fc6ac5194e7e07aac23739 70898 debian-installer optional mdadm-udeb_2.5.3.git200608202239-6_amd64.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFEpaxIgvIgzMMSnURAmaNAKDYfU067wheQZF4cjLOifgwAMASlgCgsjj2 jsaeFCr7eoIsBVaPoa7X2gg= =mW8l -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388355: mdadm: Segfaults on sid upgrade
Package: mdadm Version: 2.5.3.git200608202239-5 Severity: important Here is the output from aptitude of my upgrade of mdadm snip Setting up mdadm (2.5.3.git200608202239-5) ... update-initramfs: Generating /boot/initrd.img-2.6.16-2-amd64-k8 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . /usr/share/mdadm/mkconf: line 77: 8341 Segmentation fault $MDADM --examine --scan --config=partitions W: mdadm: failed to auto-generate temporary mdadm.conf file. W: mdadm: using the unchecked file and hoping for the best... I: mdadm: will start MD array /dev/md1 from the initial ramdisk. I: mdadm: use `dpkg-reconfigure --priority=low mdadm` to change this. /snip I had to hit CTRL-C here as it just hangs snip update-initramfs: Generating /boot/initrd.img-2.6.16-2-amd64-generic W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . /usr/share/mdadm/mkconf: line 77: 10223 Segmentation fault $MDADM --examine --scan --config=partitions W: mdadm: failed to auto-generate temporary mdadm.conf file. W: mdadm: using the unchecked file and hoping for the best... I: mdadm: will start MD array /dev/md1 from the initial ramdisk. I: mdadm: use `dpkg-reconfigure --priority=low mdadm` to change this. /snip I hit CTRL-C again just to tell aptitude to quit trying this package My largest concern right now, is what happens when I reboot? -- Package-specific info: --- mount output /dev/md1 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) /sys on /sys type sysfs (rw,noexec,nosuid,nodev) udev on /dev type tmpfs (rw,mode=0755) usbfs on /proc/bus/usb type usbfs (rw,noexec,nosuid,nodev) /dev/md0 on /boot type ext3 (rw) /dev/md4 on /home type ext3 (rw) /dev/md3 on /usr type ext3 (rw) /dev/md2 on /var type ext3 (rw) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) --- mdadm.conf DEVICE partitions ARRAY /dev/md4 level=raid1 num-devices=2 UUID=9036ff0f:f69b9dff:0366ed22:ac2f9ff9 ARRAY /dev/md3 level=raid1 num-devices=2 UUID=5a95f245:e8ef8ece:ac213102:fec16e93 ARRAY /dev/md2 level=raid1 num-devices=2 UUID=e501db1f:eff938b9:e16fb903:83614185 ARRAY /dev/md1 level=raid1 num-devices=2 UUID=94d4c9bb:76fe218d:958dc611:99fce453 ARRAY /dev/md0 level=raid1 num-devices=2 UUID=a7bc7ae5:b643b1c2:44e1fa02:314d47a9 MAILADDR root --- /proc/mdstat: Personalities : [raid1] md0 : active raid1 sda1[0] sdb1[1] 256896 blocks [2/2] [UU] md2 : active raid1 sda6[0] sdb6[1] 5004096 blocks [2/2] [UU] md3 : active raid1 sda7[0] sdb7[1] 20008832 blocks [2/2] [UU] md4 : active raid1 sda8[0] sdb8[1] 130849280 blocks [2/2] [UU] md1 : active raid1 sda5[0] sdb5[1] 2008000 blocks [2/2] [UU] unused devices: none --- /proc/partitions: major minor #blocks name 8 0 199148544 sda 8 1 257008 sda1 8 31004062 sda3 8 4 1 sda4 8 52008093 sda5 8 65004216 sda6 8 7 20008926 sda7 8 8 130849393 sda8 816 199148544 sdb 817 257008 sdb1 8191004062 sdb3 820 1 sdb4 8212008093 sdb5 8225004216 sdb6 823 20008926 sdb7 824 130849393 sdb8 3 0 80043264 hda 3 16835720 hda1 3 2 1 hda2 3 5 500440 hda5 3 6 62960152 hda6 3 79746824 hda7 9 12008000 md1 9 4 130849280 md4 9 3 20008832 md3 9 25004096 md2 9 0 256896 md0 --- initrd.img-2.6.17-1-amd64-k8: zcat: /boot/initrd.img-2.6.17-1-amd64-k8: unexpected end of file cpio: premature end of file etc/mdadm etc/mdadm/mdadm.conf lib/modules/2.6.17-1-amd64-k8/kernel/drivers/md/md-mod.ko lib/modules/2.6.17-1-amd64-k8/kernel/drivers/md/linear.ko lib/modules/2.6.17-1-amd64-k8/kernel/drivers/md/multipath.ko lib/modules/2.6.17-1-amd64-k8/kernel/drivers/md/raid0.ko lib/modules/2.6.17-1-amd64-k8/kernel/drivers/md/raid1.ko lib/modules/2.6.17-1-amd64-k8/kernel/drivers/md/xor.ko lib/modules/2.6.17-1-amd64-k8/kernel/drivers/md/raid5.ko lib/modules/2.6.17-1-amd64-k8/kernel/drivers/md/raid6.ko lib/modules/2.6.17-1-amd64-k8/kernel/drivers/md/raid10.ko --- /proc/modules: dm_snapshot 17592 0 - Live 0x88153000 dm_mirror 20928 0 - Live 0x8814c000 dm_mod 62256 2 dm_snapshot,dm_mirror, Live 0x8813b000 raid1 22784 5 - Live 0x880f md_mod 80988 6 raid1, Live 0x880db000 --- volume detail: --- /proc/cmdline root=/dev/md1 ro --- grub: kernel /vmlinuz-2.6.17-1-amd64-k8 root=/dev/md1 ro kernel /vmlinuz-2.6.17-1-amd64-k8 root=/dev/md1 ro single kernel /vmlinuz-2.6.16-2-amd64-k8 root=/dev/md1 ro kernel /vmlinuz-2.6.16-2-amd64-k8 root=/dev/md1 ro single kernel /vmlinuz-2.6.16-2-amd64-generic root=/dev/md1 ro kernel
Bug#365560: Acknowledgement (linux-image-2.6.16-1-amd64-k8: Spontaneous reboots when playing audio)
Maybe another thing I should mention, and I have no idea if it is related or not, is that everytime I turn on my computer, the audio is muted. I use the Gnome volume control and unmute all the different options, and crank the volume up. Very very annoying David On Sun, 2006-04-30 at 19:33 -0700, Debian Bug Tracking System wrote: Thank you for the problem report you have sent regarding Debian. This is an automatically generated reply, to let you know your message has been received. It is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian Kernel Team debian-kernel@lists.debian.org If you wish to submit further information on your problem, please send it to [EMAIL PROTECTED] (and *not* to [EMAIL PROTECTED]). Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#365560: linux-image-2.6.16-1-amd64-k8: Spontaneous reboots when playing audio
Hi Fredick Answers are inline below On Mon, 2006-05-01 at 18:54 +0200, Frederik Schueler wrote: On Sun, Apr 30, 2006 at 07:29:27PM -0700, David Meggy wrote: I've been seeing this problem for a long time, but I never could figure out what was the common factor for a long time means since you got the mainboard? which kernel did work for you? My 32 bit system. I did a complete switch to 64 bit, when my old hard drive started failing. The other thing that changed, is I purchased 2 SATA hard drives, and I now use software RAID-1 between them. Does it crash even with idle cpu, when listening some music, or when playing 3D games, or when doing some cpu and/or I/O intensive tasks? It will only crash when audio is playing. If I leave it idle it won't crash, but if I leave it playing music it will eventually crash. Sometimes within a minute, other times within a few hours. This sounds more like a hardware problem to me. What kind of power supply does the box have? I'll have more time tomorrow and I'll open up my case and get back to you on that. Do you have acpi or lm-sensors temperature monitoring set up, how hot does the box get? I can install them Can you add the output of /proc/interrupts to the bug please? no problem $ cat /proc/interrupts CPU0 0: 51119213IO-APIC-edge timer 1: 3321IO-APIC-edge i8042 5: 0IO-APIC-edge MPU401 UART 7: 1IO-APIC-edge parport0 8: 0IO-APIC-edge rtc 9: 0 IO-APIC-level acpi 14:182IO-APIC-edge ide0 15: 457767IO-APIC-edge ide1 169: 0 IO-APIC-level ohci_hcd:usb1 177: 38082 IO-APIC-level ohci_hcd:usb2 185: 0 IO-APIC-level ohci_hcd:usb3 193: 2 IO-APIC-level ehci_hcd:usb4 201: 40204 IO-APIC-level ALi M5455, eth0 209: 396351 IO-APIC-level libata 225:3827751 IO-APIC-level [EMAIL PROTECTED]::01:00.0 NMI:746 LOC: 51113519 ERR: 0 MIS: 0 David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#365560: linux-image-2.6.16-1-amd64-k8: Spontaneous reboots when playing audio
Package: linux-image-2.6.16-1-amd64-k8 Version: 2.6.16-10 Severity: important The subject line says it all Spontaneous reboots when playing audio I see no errors or logs, and it isn't reliably reproduceable. This system is a Debian Sid up to date system, that doesn't run any programs not from the Debian archive I've been seeing this problem for a long time, but I never could figure out what was the common factor I'm not sure what information I need to give, but here is the output of /dev/sndstat $ cat /dev/sndstat Sound Driver:3.8.1a-980706 (ALSA v1.0.11rc2 emulation code) Kernel: Linux TheMachine 2.6.16-1-amd64-k8 #2 Tue Apr 25 20:36:29 UTC 2006 x86_64 Config options: 0 Installed drivers: Type 10: ALSA emulation Card config: ALi M5455 with ALC850 at 0x0, irq 201 MPU-401 UART at 0x330, irq 5 Audio devices: 0: ALi M5455 (DUPLEX) Synth devices: NOT ENABLED IN CONFIG Midi devices: 1: MPU-401 UART MIDI Timers: 7: system timer Mixers: 0: Realtek ALC850 rev 0 1: mixer10 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-amd64-k8 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages linux-image-2.6.16-1-amd64-k8 depends on: ii e2fsprogs 1.38+1.39-WIP-2006.04.09-1 ext2 file system utilities and lib ii initramfs-too 0.60 tools for generating an initramfs ii module-init-t 3.2.2-2tools for managing Linux kernel mo linux-image-2.6.16-1-amd64-k8 recommends no packages. -- debconf information: linux-image-2.6.16-1-amd64-k8/postinst/old-dir-initrd-link-2.6.16-1-amd64-k8: true linux-image-2.6.16-1-amd64-k8/preinst/elilo-initrd-2.6.16-1-amd64-k8: true linux-image-2.6.16-1-amd64-k8/preinst/lilo-has-ramdisk: linux-image-2.6.16-1-amd64-k8/preinst/abort-install-2.6.16-1-amd64-k8: linux-image-2.6.16-1-amd64-k8/postinst/depmod-error-2.6.16-1-amd64-k8: false linux-image-2.6.16-1-amd64-k8/postinst/depmod-error-initrd-2.6.16-1-amd64-k8: false linux-image-2.6.16-1-amd64-k8/preinst/abort-overwrite-2.6.16-1-amd64-k8: * linux-image-2.6.16-1-amd64-k8/preinst/already-running-this-2.6.16-1-amd64-k8: linux-image-2.6.16-1-amd64-k8/postinst/old-system-map-link-2.6.16-1-amd64-k8: true linux-image-2.6.16-1-amd64-k8/preinst/initrd-2.6.16-1-amd64-k8: linux-image-2.6.16-1-amd64-k8/preinst/bootloader-initrd-2.6.16-1-amd64-k8: true linux-image-2.6.16-1-amd64-k8/postinst/create-kimage-link-2.6.16-1-amd64-k8: true linux-image-2.6.16-1-amd64-k8/postinst/kimage-is-a-directory: linux-image-2.6.16-1-amd64-k8/postinst/bootloader-error-2.6.16-1-amd64-k8: linux-image-2.6.16-1-amd64-k8/prerm/removing-running-kernel-2.6.16-1-amd64-k8: true linux-image-2.6.16-1-amd64-k8/prerm/would-invalidate-boot-loader-2.6.16-1-amd64-k8: true linux-image-2.6.16-1-amd64-k8/preinst/overwriting-modules-2.6.16-1-amd64-k8: true linux-image-2.6.16-1-amd64-k8/preinst/failed-to-move-modules-2.6.16-1-amd64-k8: linux-image-2.6.16-1-amd64-k8/postinst/old-initrd-link-2.6.16-1-amd64-k8: true linux-image-2.6.16-1-amd64-k8/preinst/lilo-initrd-2.6.16-1-amd64-k8: true linux-image-2.6.16-1-amd64-k8/postinst/bootloader-test-error-2.6.16-1-amd64-k8: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#321204: ethereal won't start and outputs a capabilities error
On Thu, 2005-04-08 at 10:00 +0200, Frederic Peters wrote: Debian kernel (at least 2.6.12-1-686) has CONFIG_SECURITY_CAPABILITIES=y; older ones may have that option as a module; what is ethereal behaviour after you 'modprobe capability' ? ha ha yes 'modprobe capability' fixes the problem. I guess that is a little inconsistent between different kernels if one has the functionality built in and another has it as a module. Maybe a slight change in the error message of ethereal would help, or since ethereal has root privileges could it just directly run system(modprobe capability);. David -- David Meggy [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#321204: ethereal won't start and outputs a capabilities error
Package: ethereal
Version: 0.10.12-2
I think this says it all
snip
# ethereal
Could not set capabilities: Operation not permitted
/snip
ethereal is version 0.10.12-2
kernel is kernel-image-2.6.11-9-amd64-k8 version 2.6.11-4 (i386 debian
system)
the tail end of strace ethereal is
capget(0x19980330, 0, {CAP_CHOWN|CAP_DAC_OVERRIDE|CAP_DAC_READ_SEARCH|
CAP_FOWNER|CAP_FSETID|CAP_KILL|CAP_SETGID|CAP_SETUID|
CAP_LINUX_IMMUTABLE|CAP_NET_BIND_SERVICE|CAP_NET_BROADCAST|
CAP_NET_ADMIN|CAP_NET_RAW|CAP_IPC_LOCK|CAP_IPC_OWNER|CAP_SYS_MODULE|
CAP_SYS_RAWIO|CAP_SYS_CHROOT|CAP_SYS_PTRACE|CAP_SYS_PACCT|CAP_SYS_ADMIN|
CAP_SYS_BOOT|CAP_SYS_NICE|CAP_SYS_RESOURCE|CAP_SYS_TIME|
CAP_SYS_TTY_CONFIG|0xf800, CAP_CHOWN|CAP_DAC_OVERRIDE|
CAP_DAC_READ_SEARCH|CAP_FOWNER|CAP_FSETID|CAP_KILL|CAP_SETGID|
CAP_SETUID|CAP_SETPCAP|CAP_LINUX_IMMUTABLE|CAP_NET_BIND_SERVICE|
CAP_NET_BROADCAST|CAP_NET_ADMIN|CAP_NET_RAW|CAP_IPC_LOCK|CAP_IPC_OWNER|
CAP_SYS_MODULE|CAP_SYS_RAWIO|CAP_SYS_CHROOT|CAP_SYS_PTRACE|
CAP_SYS_PACCT|CAP_SYS_ADMIN|CAP_SYS_BOOT|CAP_SYS_NICE|CAP_SYS_RESOURCE|
CAP_SYS_TIME|CAP_SYS_TTY_CONFIG|0xf800, 0}) = 0
capset(0x19980330, 0, {CAP_DAC_READ_SEARCH|CAP_NET_RAW,
CAP_DAC_READ_SEARCH|CAP_NET_RAW, 0}) = -1 EPERM (Operation not
permitted)
write(2, Could not set capabilities: Oper..., 52) = 52
exit_group(1) = ?
Maybe this is a Debian kernel issue. I haven't ever look into what
capabilities even are.
David
--
David Meggy [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
