Bug#403659: sash: no longer statically linked
Package: sash Version: 3.7-7.1 Severity: grave Justification: renders package unusable NMU of this package appears to be no longer statically linked. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (950, 'testing'), (750, 'unstable'), (550, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-k7 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages sash depends on: ii debconf [debconf-2.0] 1.5.8Debian configuration management sy ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries ii lockfile-progs 0.1.10 Programs for locking and unlocking ii passwd 1:4.0.18.1-6 change and administer password and ii zlib1g 1:1.2.3-13 compression library - runtime sash recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#416502: Try to update depends too
You seem to have at least coreutils, libc6 and libldap2 not in their latest version in "testing". Try to update them (or apt-get/aptitude upgrade). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#415414: Raising severity because xmms-flac crashing
Package: flac Version: 1.1.2-5 Severity: grave 1.1.2-6 was uploaded with priority high and should go to etch. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#401774: Raising severity because xmms-flac crashing
Package: flac Severity: grave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#401774: Retrying
Severity: grave 1.1.2-6 was uploaded with priority high and should go to etch. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403871: Is this still relevant?
Is this patch still needed in 2.6.18.dfsg.1-12 or 2.6.20-1 ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#419202: reportbug: "Changed Bug title to...from" lacks quotes
Package: reportbug
Version: 3.35
Severity: wishlist
BTS web reports show for example "Changed Bug title to initamfs-tools:
mkinitramfs fails with some locales from linux-image-2.6.20-1-sparc64:
fails to boot.."
It would make reading easier if to and from titles were in quotes ("').
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (950, 'testing'), (750, 'unstable'), (550, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-4-k7 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages reportbug depends on:
ii apt 0.6.46.4-0.1 Advanced front-end for dpkg
ii python 2.4.4-2 An interactive high-level object-o
ii python-central 0.5.13-0.1 register and build utility for Pyt
reportbug recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#419504: python2.4: Wakes up every 100ms for nothing
Package: python2.4 Version: 2.4.4-3 Severity: normal http://perkypants.org/blog/2006/09/02/rfte-python/ http://lwn.net/Articles/198215/ Tested to still apply. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (950, 'testing'), (750, 'unstable'), (550, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-k7 (SMP w/1 CPU core) Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages python2.4 depends on: ii libbz2-1.0 1.0.3-6 high-quality block-sorting file co ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libdb4.44.4.20-8 Berkeley v4.4 Database Libraries [ ii libncursesw55.5-5Shared libraries for terminal hand ii libreadline55.2-2GNU readline and history libraries ii libssl0.9.8 0.9.8e-4 SSL shared libraries ii mime-support3.39-1 MIME files 'mime.types' & 'mailcap ii python2.4-minimal 2.4.4-3 A minimal subset of the Python lan python2.4 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#419534: libsqlite3-0: New upstream version 3.3.15 available
Package: libsqlite3-0 Version: 3.3.14-1 Severity: important 3.3.15 fixes regression plus other bugs. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (950, 'testing'), (750, 'unstable'), (550, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-k7 (SMP w/1 CPU core) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libsqlite3-0 depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries libsqlite3-0 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#692856: vlc: Endless loop at end of file when file is removed during play
Package: vlc Version: 2.0.5-1 Followup-For: Bug #692856 This issue can be repeated simply by giving non-existing file at command-line. (So bug title is too specific) Yes, I have repeat mode turned on at settings, but this shouldn't still happen. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (500, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) 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 vlc depends on: ii dpkg 1.16.9 ii fonts-freefont-ttf20120503-1 ii libaa11.4p5-40 ii libavcodec53 6:0.8.4-1 ii libavutil51 6:0.8.4-1 ii libc6 2.13-37 ii libcaca0 0.99.beta18-1 ii libfreetype6 2.4.9-1.1 ii libfribidi0 0.19.2-3 ii libgcc1 1:4.7.2-5 ii libgl1-mesa-glx [libgl1] 8.0.5-3 ii libice6 2:1.0.8-2 ii libqtcore44:4.8.2+dfsg-9 ii libqtgui4 4:4.8.2+dfsg-9 ii libsdl-image1.2 1.2.12-2 ii libsdl1.2debian 1.2.15-5 ii libsm62:1.2.1-2 ii libstdc++64.7.2-5 ii libtar0 1.2.16-1 ii libva-x11-1 1.0.15-4 ii libva11.0.15-4 ii libvlccore5 2.0.5-1 ii libx11-6 2:1.5.0-1 ii libxcb-composite0 1.8.1-2 ii libxcb-keysyms1 0.3.9-1 ii libxcb-randr0 1.8.1-2 ii libxcb-render01.8.1-2 ii libxcb-shape0 1.8.1-2 ii libxcb-shm0 1.8.1-2 ii libxcb-xfixes01.8.1-2 ii libxcb-xv01.8.1-2 ii libxcb1 1.8.1-2 ii libxext6 2:1.3.1-2 ii libxinerama1 2:1.1.2-1 ii libxpm4 1:3.5.10-1 ii vlc-nox 2.0.5-1 ii zlib1g1:1.2.7.dfsg-13 Versions of packages vlc recommends: ii vlc-plugin-notify 2.0.5-1 ii vlc-plugin-pulse 2.0.5-1 ii xdg-utils 1.1.0~rc1+git20111210-6 Versions of packages vlc suggests: pn videolan-doc -- 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#649448: udev loading radeon drivers garbles screen output
On Mon, Nov 21, 2011 at 09:33:28AM -0500, Alex Deucher wrote: > On Sun, Nov 20, 2011 at 10:12 PM, Ben Hutchings wrote: > > On Sun, 2011-11-20 at 19:02 -0600, Jonathan Nieder wrote: > >> reassign 649448 src:linux-2.6 linux-2.6/3.0.0-3 > >> severity 649448 important > >> retitle 649448 radeon (evergreen): random-looking pattern of pixels when > >> firmware not installed > >> tags 649448 + upstream > >> quit > >> > >> Hi Martin, > >> > >> Martin von Gagern wrote: > >> > >> > Version: 3.0.0-3 > >> [...] > >> > Just installed a wheezy setup using debootstrap, adding grub-pc and > >> > linux-image-amd64 after the chroot was created. The kernel boots, the > >> > initrd seems all right. When the main system boots up, udev gets launced > >> > pretty early. Soon after it is started, the screen turns into a pretty > >> > random-looking pattern of pixels, making the console pretty unusable. > >> > This also happens in "recovery" i.e. single-user mode. > >> [...] > >> > Possible workarounds seem to include: > >> [...] > >> > - Adding a line "blacklist radeon" to /etc/modprobe.d/blacklist.conf, > >> > followed by running "depmod -a". > >> [...] > >> >> [ 150.125768] r600_cp: Failed to load firmware "radeon/SUMO2_pfp.bin" > >> >> [ 150.125818] [drm:evergreen_startup] *ERROR* Failed to load firmware! > >> >> [ 150.125859] radeon :00:01.0: disabling GPU acceleration > >> > >> Yes, the radeon driver currently copes poorly when firmware is missing. > >> Compare [1], [2], [3]. > >> > >> [...] > >> > Not having GPU accelleration due to lack of free firmware is acceptable. > >> > Not having a usable text console can be a real problem. > >> > >> Agreed. The radeon driver should be bailing out when firmware is > >> missing for cards that need it, but that is not working for some > >> reason. > > [...] > > > > At the time I converted the radeon driver to load external firmware, it > > was apparently only required for 3D acceleration and both KMS and 2D > > acceleration of X worked without it, at least on those systems I tested > > (which were quite old, R100-R300 families). Therefore failure to load > > firmware would only result in DRM (3D acceleration support) being > > disabled. > > > > However, it looks like driver support for the R600 family onward now > > absolutely requires the 'RLC' firmware blobs: > > > > commit d8f60cfc93452d0554f6a701aa8e3236cbee4636 > > Author: Alex Deucher > > Date: Tue Dec 1 13:43:46 2009 -0500 > > > > drm/radeon/kms: Add support for interrupts on r6xx/r7xx chips (v3) > > > > And the 'Northern Islands' GPUs and 'Fusion' APUs appear to require the > > 'MC' firmware blobs: > > > > commit 0af62b0168043896a042b005ff88caa77dd94d04 > > Author: Alex Deucher > > Date: Thu Jan 6 21:19:31 2011 -0500 > > > > drm/radeon/kms: add ucode loader for NI > > > > Therefore I think that at least r600_init(), rv770_init(), > > evergreen_init() and cayman_init() should be treating failure to load > > firmware as a fatal error. > > > > R6xx, r7xx should work ok without the RLC ucode, you just won't get > acceleration. With chips that require the MC ucode, the driver will > bail if the MC ucode is not available. In what kernel versions should that be true? These bugs are reported that question it (some are reported against older kernels). http://bugs.debian.org/607194 http://bugs.debian.org/637943 http://bugs.debian.org/627497 and also my report: http://bugs.debian.org/646306 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#687442: linux-image-3.2.0-3-686-pae: Add Intel Ivy Bridge support
On Fri, Jan 04, 2013 at 05:13:35PM +0100, Julien Cristau wrote: > On Mon, Nov 26, 2012 at 22:28:56 +0100, Julien Cristau wrote: > > > New image is up at > > http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-amd64_3.2.34-1~jcristau.1_amd64.deb > > > > sha1sum is 1bbb6e4590e4f000739af89f3090ffc6bb9cb409. > > diff against svn at > > http://people.debian.org/~jcristau/3.2.34-1~jcristau.1.diff > > > New image: > - rebased on 3.2.35-2 > - updated drm to 3.4.24 > - with additional patches from 3.2.y that were missing in 3.4.y > > diff at > http://people.debian.org/~jcristau/drm-backport-3.2.35-3~jcristau.1.patch > > http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-686-pae_3.2.35-3~jcristau.1_i386.deb > sha1sum 17980ee5bafc40bb4e7bf42576ce40ac81c75833 > > Lightly tested on Dell latitude D520 with intel 945gm graphics, and > squeeze userspace. > > http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-amd64_3.2.35-3~jcristau.1_amd64.deb > sha1sum f6711fe6d0d924aab82ec82fe1a86102a69a8c32 Amd64 deb works fine with Asus 1215B (AMD Radeon 6310 APU), wheezy xfce -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692856: vlc: Endless loop at end of file when file is removed during play
Package: vlc Version: 2.0.4-1 Severity: important This happens also with 2.0.3-3 and earlier VLC versions too. When you reach end of file that is removed during play (such as those with .part suffix when you use Iceweasel to download media file and download completes) error dialog doesn't respond and CPU spins in endless loop. This is very bad when in full screen mode. I had to change to text console with control-alt-F2 to be able to kill stuck vlc process. Terminal has continuous stream of errors (tail of output here): [0x60dc548] main input error: open of `file:///home/touko/Downloads/x.flv.part' failed [0x60f4928] filesystem access error: cannot open file /home/touko/Downloads/x.flv.part (No such file or directory) [0x6101d98] main input error: open of /`file:///home/touko/Downloads/x.flv.part' failed [0x6101048] filesystem access error: cannot open file //home/touko/Downloads/x.flv.part (No such file or directory) [0x60f4168] main input error: open of `file:///home/touko/Downloads/x.flv.part' failed [0x60f8058] filesystem access error: cannot open file /home/touko/Downloads/x.flv.part (No such file or directory) -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (500, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) 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 vlc depends on: ii dpkg 1.16.9 ii fonts-freefont-ttf20120503-1 ii libaa11.4p5-40 ii libavcodec53 6:0.8.4-1 ii libavutil51 6:0.8.4-1 ii libc6 2.13-35 ii libcaca0 0.99.beta18-1 ii libfreetype6 2.4.9-1 ii libfribidi0 0.19.2-3 ii libgcc1 1:4.7.1-7 ii libgl1-mesa-glx [libgl1] 8.0.4-2 ii libice6 2:1.0.8-2 ii libqtcore44:4.8.2+dfsg-2 ii libqtgui4 4:4.8.2+dfsg-2 ii libsdl-image1.2 1.2.12-2 ii libsdl1.2debian 1.2.15-5 ii libsm62:1.2.1-2 ii libstdc++64.7.1-7 ii libtar0 1.2.16-1 ii libva-x11-1 1.0.15-4 ii libva11.0.15-4 ii libvlccore5 2.0.4-1 ii libx11-6 2:1.5.0-1 ii libxcb-composite0 1.8.1-2 ii libxcb-keysyms1 0.3.9-1 ii libxcb-randr0 1.8.1-2 ii libxcb-render01.8.1-2 ii libxcb-shape0 1.8.1-2 ii libxcb-shm0 1.8.1-2 ii libxcb-xfixes01.8.1-2 ii libxcb-xv01.8.1-2 ii libxcb1 1.8.1-2 ii libxext6 2:1.3.1-2 ii libxinerama1 2:1.1.2-1 ii libxpm4 1:3.5.10-1 ii vlc-nox 2.0.4-1 ii zlib1g1:1.2.7.dfsg-13 Versions of packages vlc recommends: ii vlc-plugin-notify 2.0.4-1 ii vlc-plugin-pulse 2.0.4-1 ii xdg-utils 1.1.0~rc1+git20111210-6 Versions of packages vlc suggests: pn videolan-doc -- 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#678254: gamera: FTBFS: fdupes: unrecognized option '--linkhard'
Followup-For: Bug #678254 This happens because: Changes: fdupes (1.50-PR2-4) unstable; urgency=low . [ Sandro Tosi ] * debian/patches/50_bts284274_hardlinkreplace.dpatch - disabled, since it's losing data if files are on different - filesystems; thanks to Mike Hommey for the report; Closes: #677419 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#677419: fdupes: When using -L and traversing filesystems, removes files
Package: fdupes Followup-For: Bug #677419 It's wrong to remove this useful option, removing causes FTBFS #678254 So -L should be fixed to fail gracefully instead -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678347: libffado: FTBFS on powerpc
Package: libffado Version: 2.0.99+svn2163-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Please look at https://buildd.debian.org/status/package.php?p=libffado 2.0.99+svn2163 fails to build on powerpc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664944: changelog credits
Looks like patch came from Nicolas Bourdaud, not from Lucas Nussbaum. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#677121: this bug seems fixed
psmisc seems to build fine now, you should close this bug -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678530: only i386 is broken
Nathan, please fix your build environment. Looks like that binNMU is needed again. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678630: unburden-home-dir: README.md is confusing
Package: unburden-home-dir Version: 0.3 Severity: normal 0.3 has this change: Renamed README to README.md so it will be parsed as Markdown on GitHub This is wrong for user perspective, they can think that file is only relevant for MD (RAID) users and ignore that README. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678636: initramfs-tools: dm-crypt partitions not further working. No asking password to encrypt. System will not boot
On Sat, Jun 23, 2012 at 01:13:04PM +0200, Pierre Bernhardt wrote: > Package: initramfs-tools > Version: 0.106 > Severity: critical > Tags: upstream > Justification: breaks the whole system > > After patching my system 3 days ago it will not further boot up. The initramfs > prompt comes before the keypass has to been normally asked for to decrypt my > root partition with the contained lvm root vol disk group. > Before the upgrade been made I didn't hat the problem. I guess this comes with > the upgrade of the initramfs-tools from 0.103 to 0.106. > > Work around at the moment is to use cryptsetup luksOpen manually and start all > lvmvolumes before continue with the boot process by using Crtl-D. > > > > -- Package-specific info: > -- initramfs sizes > -rw-r--r-- 1 root root 11M Jun 22 13:21 /boot/initrd.img-2.6.32-5-amd64 > -- /proc/cmdline > BOOT_IMAGE=/vmlinuz-3.2.0-2-amd64 root=/dev/mapper/rootdg-root ro This lists both 2.6.32-5 and 3.2.0-2 kernels. What kernel version do you try to boot, and is its initramfs updated? By default only most recent kernel does have initramfs updated when updating packages. Your setup has many moving parts that can go wrong. Please list versions of mdadm, dmsetup, libdevmapper*, *cryptsetup* > > -- /proc/mdstat > Personalities : [raid1] [raid6] [raid5] [raid4] > md50 : active raid5 sda1[0] sdd1[3] sde1[5] > 625137664 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU] > bitmap: 1/3 pages [4KB], 65536KB chunk > > md1 : active raid1 sdc2[0] > 28812480 blocks [1/1] [U] > bitmap: 4/220 pages [16KB], 64KB chunk > > md0 : active raid1 sdc1[0] > 489856 blocks [1/1] [U] > bitmap: 0/60 pages [0KB], 4KB chunk > > > -- System Information: > Debian Release: wheezy/sid > APT prefers proposed-updates > APT policy: (500, 'proposed-updates'), (500, 'stable'), (300, 'testing'), > (200, 'unstable'), (150, 'experimental') > Architecture: amd64 (x86_64) You are using mixed system, packages may have bugs in their depends, so that manual updating or bug reporting is maybe needed. > > Kernel: Linux 3.2.0-2-amd64 (SMP w/6 CPU cores) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages initramfs-tools depends on: > ii cpio 2.11-7 GNU cpio -- a program to manage > ar > ii klibc-utils 2.0-2 small utilities built with klibc > f > ii module-init-tools 3.12-2 tools for managing Linux kernel > mo > ii udev 175-3.1/dev/ and hotplug management > daemo > > Versions of packages initramfs-tools recommends: > ii busybox 1:1.19.3-7 Tiny utilities for small and > embed > > Versions of packages initramfs-tools suggests: > pn bash-completion(no description available) > > -- 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#678636: initramfs-tools: dm-crypt partitions not further working. No asking password to encrypt. System will not boot
On Sat, Jun 23, 2012 at 01:13:04PM +0200, Pierre Bernhardt wrote: > -- /proc/mdstat > Personalities : [raid1] [raid6] [raid5] [raid4] > md50 : active raid5 sda1[0] sdd1[3] sde1[5] > 625137664 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU] > bitmap: 1/3 pages [4KB], 65536KB chunk > > md1 : active raid1 sdc2[0] > 28812480 blocks [1/1] [U] > bitmap: 4/220 pages [16KB], 64KB chunk > > md0 : active raid1 sdc1[0] > 489856 blocks [1/1] [U] > bitmap: 0/60 pages [0KB], 4KB chunk > > unused devices: Your raid1 arrays look strange, with only one component device in each. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678137: git-svn: affected versions?
BTS thinks that this bug affects only unstable and stable? (no wheezy). However tags are "wheezy sid experimental". -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678802: osgi-core: Build does not ensure backwards compatible byte-core
If this bug is now fixed with version 4.3.0-3 , it can be marked so and closed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678795: task-desktop: Flash support should pull in browser-plugin-lightspark
On Sun, Jun 24, 2012 at 12:27:21PM +0200, Petter Reinholdtsen wrote: > [Christian PERRIER] > > So both can coexist peacefully? > > I believe so. I have not checked it myself, but know there were talk about > having lightspark calling gnash when it found AVM1 flash files. Not sure > if both browsers plugin should be installed, or only the lightspark one > and the gnash standalone program. Flash maintainers, can you tell about compatibility of these plugins and what packages should be installed by default in wheezy? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645709: www.debian.org: Debian “squeeze” Installation Information , errata outdated?
On Mon, Oct 17, 2011 at 07:31:39PM -0400, David Prévot wrote: > > > http://www.debian.org/releases/squeeze/debian-installer/ > > > > Errata lists some items as "This will be fixed on the next Squeeze point > > release (6.0.1)". > > Now 6.0.3 is released, so maybe those are now fixed? > > Thanks for your report, Debian Installer team CC: could you please > update the page as needed? I know that you are busy with wheezy installer, but squeeze installer errata list is still at pre 6.0.1 level. Many bugs are now fixed but some remain. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#659948: [initramfs-tools] Fails to upgrade (Sid)
On Wed, Feb 15, 2012 at 12:23:47PM +0200, David Baron wrote: > On Wednesday 15 February 2012 11:40:02 Michael Prokop wrote: > > * David Baron [Wed Feb 15, 2012 at 10:49:53AM +0200]: > > > --- Please enter the report below this line. --- > > > On attempted upgrade > > > > From which initramfs-tools version are you upgrading? > Previous Sid version. > > > > > > update-initramfs: deferring update (trigger activated) > > > Processing triggers for initramfs-tools ... > > > update-initramfs: Generating /boot/initrd.img-3.2.0-1-686-pae > > > /rootfs: No such file or directory > > > mkinitramfs: for root /rootfs missing /rootfs /sys/block/ entry > > > mkinitramfs: workaround is MODULES=most > > > mkinitramfs: Error please report the bug > > > update-initramfs: failed for /boot/initrd.img-3.2.0-1-686-pae with 1. > > > > > > dpkg: error processing initramfs-tools (--configure): > > > subprocess installed post-installation script returned error exit status > > > 1 > > > > > > configured to not write apport reports > > > > > > Errors were encountered while > > > > > > processing: > > > initramfs-tools > > > > Did you recently switch to the usage of > > "root=UUID=df24bea0-5520-4281-b053-021bd5a96628" or did you use the > > very same kernel command line also with the older version of > > initramfs-tools? > No change here. > > > > > > -- /etc/initramfs-tools/initramfs.conf > > > MODULES=dep > > > > Same question for MODULES=dep (and as noted in the error message > > switching to MODULES=most will work around your issue). > This makes things too big for lilo (or at least did so previously) Please try to enable "large-memory" option in lilo.conf. It should help at loading larger initramfs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#549681: bug#549681: mkvmlinuz: use xz to compress vmlinuz-boxed initrd
On Sat, Jun 30, 2012 at 11:01:47PM -0400, Milan Kupcevic wrote: > The attached patch brings vmlinuz from about 13MB to about 9.5MB, which > is well under the 12MB limit. Downside is that xz compressing is > noticeably slower than currently used gzip, but decompressing speed > difference is not noticeable. > > I've tested it on Pegasos II machine, it boots really fast. Updated > mkvmlinuz package is waiting on mentors.debian.net for a willing sponsor > for upload. > ... > +if test "$post_2_6_38"; then > + XZ="xz --check=crc32 -8" > +else > + XZ=false > +fi >From xz(1) manual page (you can ignore DecMem): Preset DictSize CompCPU CompMem DecMem -0 256 KiB 03 MiB1 MiB -1 1 MiB 19 MiB2 MiB -2 2 MiB 2 17 MiB3 MiB -3 4 MiB 3 32 MiB5 MiB -4 4 MiB 4 48 MiB5 MiB -5 8 MiB 5 94 MiB9 MiB -6 8 MiB 6 94 MiB9 MiB -7 16 MiB 6 186 MiB 17 MiB -8 32 MiB 6 370 MiB 33 MiB -9 64 MiB 6 674 MiB 65 MiB Better to use default setting "-6" that has lower memory requirement. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#679774: poppler-data: Uses too memory hungry xz compression
Package: poppler-data Version: 0.4.5-8 Severity: normal poppler-data 0.4.5-8 uses xz compression with "-Sextreme -z9" settings. I think it's overkill (-6e should be enough). Xz memory use when building this package is now 674 MiB and 65 MiB is required when decompressing during installation. xz(1) manual page says: The differences between the presets are more significant than with gzip(1) and bzip2(1). The selected compression settings determine the memory requirements of the decompressor, thus using a too high preset level might make it painful to decompress the file on an old system with little RAM. Specifically, it's not a good idea to blindly use -9 for everything like it often is with gzip(1) and bzip2(1). Here is a table of memory use with different presets: Preset DictSize CompCPU CompMem DecMem -0e 256 KiB 84 MiB1 MiB -1e 1 MiB 8 13 MiB2 MiB -2e 2 MiB 8 25 MiB3 MiB -3e 4 MiB 7 48 MiB5 MiB -4e 4 MiB 8 48 MiB5 MiB -5e 8 MiB 7 94 MiB9 MiB -6e 8 MiB 8 94 MiB9 MiB -7e 16 MiB 8 186 MiB 17 MiB -8e 32 MiB 8 370 MiB 33 MiB -9e 64 MiB 8 674 MiB 65 MiB -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#549681: mkvmlinuz: use xz to compress vmlinuz-boxed initrd
On Sun, Jul 01, 2012 at 11:03:02AM -0400, Milan Kupcevic wrote: > On 07/01/2012 07:05 AM, Touko Korpela wrote: > >> ... > >> +if test "$post_2_6_38"; then > >> + XZ="xz --check=crc32 -8" > >> +else > >> + XZ=false > >> +fi > > > > From xz(1) manual page (you can ignore DecMem): > > Preset DictSize CompCPU CompMem DecMem > >-0 256 KiB 03 MiB1 MiB > >-1 1 MiB 19 MiB2 MiB > >-2 2 MiB 2 17 MiB3 MiB > >-3 4 MiB 3 32 MiB5 MiB > >-4 4 MiB 4 48 MiB5 MiB > >-5 8 MiB 5 94 MiB9 MiB > >-6 8 MiB 6 94 MiB9 MiB > >-7 16 MiB 6 186 MiB 17 MiB > >-8 32 MiB 6 370 MiB 33 MiB > >-9 64 MiB 6 674 MiB 65 MiB > > > > Better to use default setting "-6" that has lower memory requirement. > > > > Here is timing for re-compression from gzip to xz on Pegasos II with > Freescale 7447 1GhZ processor and 1Gb RAM: Use of -8 option isn't a good thing for systems having only 512 Mib or less memory. This operation shouldn't force to use slow swap space or OOM. > > set time compressed size > -91m43.962s9.5MB > -81m44.824s9.5MB > -61m35.097s9.6MB > -31m10.080s10.6MB > -20m45.609s10.7MB > -00m19.286s11.1MB > > I've originally decided to go with -8, mainly because the same preset is > used in mkinitramfs form initramfs-tools package. It may be worth > hearing arguments about the timing given that all presets currently > produce vmlinuz smaller than the 12MB limit, but the compression time is > very different. Your size numbers show that -8 produces only marginally smaller images. If mkinitramfs (initramfs-tools) uses -8 for xz compression, it should be changed too. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#679964: snappy vs. snappy-player and BTS
Looks like this bug belongs to sourcepackage snappy, not binary snappy (src:snappy-player). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#679964: snappy vs. snappy-player and BTS
On Tue, Jul 03, 2012 at 12:47:39AM +0300, Touko Korpela wrote: > Looks like this bug belongs to sourcepackage snappy, not binary snappy > (src:snappy-player). While this bug (#679964) is reported against binary package snappy BTS shows this wrong? information: Package: snappy; Maintainer for snappy is Steinar H. Gunderson ; Source for snappy is src:snappy-player. But maintainer for src:snappy-player should be "Maintainers of GStreamer packages " (Maintainer for src:snappy is Steinar H. Gunderson) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671396: libtiff4: 3.9.6-3 hpcups crashes with signal 11
Does new version 3.9.6-6 work without crashing? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680505: desktop-base: Text has too low contrast with new Grub background
Package: desktop-base Version: 7.0.0 Severity: normal With new light background image, white Grub text has too low contrast making text hard to read. Also image brightness varies in different part of the image. Consider making image use more homogenous brightness when text is printed over it and if using light colour background make text colour darker. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (500, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-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 desktop-base depends on: ii dpkg 1.16.4.3 ii librsvg2-common 2.36.1-1 desktop-base recommends no packages. Versions of packages desktop-base suggests: ii xfce4 4.8.0.3 -- 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#680519: please do depend on gdm3 for lxde-desktop
Daniel Baumann wrote: > Hi, > > I'm one of the lxde maintainers in debian and we have the consens in the > team that we are recommending gdm3 to be used as the display manager for > lxde systems (which can be seen by e.g. looking at > src:lxde-metapackages, until lxdm is in the archive for wheezy+1). > > Hence, please use gdm3 and not xdm in tasksel for lxde-desktop. Isn't it too big? Shouldn't it use lightdm by default like Xfce does? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680519: please do depend on gdm3 for lxde-desktop
On Sat, Jul 07, 2012 at 06:53:13PM +0200, Daniel Baumann wrote: > Touko Korpela wrote: > > Isn't it too big? > > for the live images, we've always been using gdm/gdm3 in lxde-desktop, > for the installer (via tasksel), up to squeeze, gdm was used too. > > i don't think it's to big. > > having lxdm at some later point though, is nice, and i wouldn't mind the > size decrease it bringts, however, until then the size difference > doesn't matter much. > > otoh, choosing xdm is a no-go anyway, it doesn't support autologin > (which is essential for live systems) and i don't think that the the > installer (via tasksel) should use anything different than what we do > with the live systems. > > > Shouldn't it use lightdm by default like Xfce does? > > lightdm is relatively buggy, does not reasonably support autologin yet, > and doesn't bring any advantages over gdm3. gdm3 is even smaller in > footprint size than gdm in squeeze, hence, using gdm3 in wheezy rather > than gdm in squeeze is already an improvement. New lightdm (1.2.2-3) says to support autologin, but I haven't tested that. If you make this change, does it make Xfce+lxde CD-images try to pull Gnome depends in and make too tight to fit all? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680733: liblapack3: Updating to 3.4.1-4 prints dpkg warnings
Package: liblapack3 Version: 3.4.1-4 Severity: important I got warnings from dpkg when updating from 3.4.1-3 to 3.4.1-4 Dpkg version is 1.16.4.3 from wheezy (sid has more recent dpkg) Is this bug in lapack or in dpkg? -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (500, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-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 liblapack3 depends on: ii debconf [debconf-2.0]1.5.44 ii libblas3 [libblas.so.3] 1.2.20110419-3 ii libc62.13-33 ii libgcc1 1:4.7.1-2 ii libgfortran3 4.7.1-2 ii libquadmath0 4.7.1-2 liblapack3 recommends no packages. liblapack3 suggests no packages. -- no debconf information ... reparing to replace liblapack3 3.4.1-3 (using .../liblapack3_3.4.1-4_amd64.deb) ... update-alternatives: error: no alternatives for liblapack.so.3gf. dpkg: warning: subprocess old pre-removal script returned error exit status 2 dpkg - trying script from the new package instead ... dpkg: ... it looks like that went OK. Unpacking replacement liblapack3 ... Preparing to replace liblapack3gf 3.4.1-3 (using .../liblapack3gf_3.4.1-4_all.deb) ... update-alternatives: error: no alternatives for liblapack.so.3gf. dpkg: warning: subprocess old pre-removal script returned error exit status 2 dpkg - trying script from the new package instead ... dpkg: ... it looks like that went OK. Unpacking replacement liblapack3gf ... Processing triggers for man-db ... ... Setting up liblapack3 (3.4.1-4) ... update-alternatives: using /usr/lib/lapack/liblapack.so.3 to provide /usr/lib/liblapack.so.3 (liblapack.so.3) in auto mode. Setting up liblapack3gf (3.4.1-4) ...
Bug#571204: tasksel: Does not install network management software for LXDE
Daniel Baumann wrote: > i don't know why tasksel uses lxde-core, but, if you would depend on > lxde instead, you would get network-manager-gnome that the lxde > maintainers in debian recommend for their users. I think lxde shouldn't use NetworkManager by default. It's Lightweight X11 Desktop Environment, and use wicd instead. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680348: gcc-4.6: ICE on mips when compiling aiccu
Matthias Klose wrote: > On 05.07.2012 11:03, Axel Beckert wrote: > > Package: gcc-4.6 > > Severity: normal > > Affects: aiccu > > > > Dear Maintainer, > > > > gcc-4.6 failed to compile aiccu on mips (but not mipsel) with the > > following error message: > > > > ../common/tun.c:69:1: internal compiler error: Segmentation fault > > > > Full log at > > https://buildd.debian.org/status/fetch.php?pkg=aiccu&arch=mips&ver=20070115-15.1&stamp=1341446386 > > preprocessed source? status in 4.7 and 4.8? Ben Hutchings suspects that mips build machine has hardware fault: https://lists.debian.org/debian-kernel/2012/07/msg00105.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#654957: cpufrequtils doesn't support new AMD cpus
On Sat, Jan 07, 2012 at 03:30:04PM +0200, Touko Korpela wrote: > I think you should also add family 18 (AMD Fusion Llano). > http://www.phoronix.com/vr.php?view=16292 > > > On Sat, Jan 07, 2012 at 12:06:05AM -0600, Robert Keevil wrote: > > Package: cpufrequtils > > Version: 007-2 > > Severity: normal > > Tags: patch > > > > /etc/init.d/loadcpufreq does not support AMD Bulldozer CPUs, which have a > > CPU > > family of 21. The processor is supported by the powernow_k8 module. > > > --- debian/cpufrequtils.loadcpufreq.init.dist 2012-01-06 > > 23:35:24.867961318 -0600 > > +++ debian/cpufrequtils.loadcpufreq.init2012-01-06 23:35:32.759956550 > > -0600 > > @@ -119,7 +119,7 @@ > > # K7 > > MODULE=powernow-k7 > > ;; > > -15|16|17|20) > > +15|16|17|20|21) > > # K8 > > MODULE=powernow-k8 > > ;; I hope that you upload cpufrequtils with support for AMD processor families 18 and 21 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#654957: cpufrequtils doesn't support new AMD cpus
On Fri, Feb 03, 2012 at 04:14:52AM +, Ben Hutchings wrote: > On Fri, 2012-02-03 at 04:16 +0200, Touko Korpela wrote: > > On Sat, Jan 07, 2012 at 03:30:04PM +0200, Touko Korpela wrote: > > > I think you should also add family 18 (AMD Fusion Llano). > > > http://www.phoronix.com/vr.php?view=16292 > > > > > > > > > On Sat, Jan 07, 2012 at 12:06:05AM -0600, Robert Keevil wrote: > > > > Package: cpufrequtils > > > > Version: 007-2 > > > > Severity: normal > > > > Tags: patch > > > > > > > > /etc/init.d/loadcpufreq does not support AMD Bulldozer CPUs, which have > > > > a CPU > > > > family of 21. The processor is supported by the powernow_k8 module. > > > > > > > --- debian/cpufrequtils.loadcpufreq.init.dist 2012-01-06 > > > > 23:35:24.867961318 -0600 > > > > +++ debian/cpufrequtils.loadcpufreq.init2012-01-06 > > > > 23:35:32.759956550 -0600 > > > > @@ -119,7 +119,7 @@ > > > > # K7 > > > > MODULE=powernow-k7 > > > > ;; > > > > -15|16|17|20) > > > > +15|16|17|20|21) > > > > # K8 > > > > MODULE=powernow-k8 > > > > ;; > > > > I hope that you upload cpufrequtils with support for AMD processor families > > 18 and 21 > > There has been some work to generate module aliases and uevents for x86 > CPU features. This would allow udev to load cpufreq drivers just like > any other device, removing the need for cpufrequtils to know which > drivers handle which CPUs. It looks like this will be going into Linux > 3.4 but I would be open to backporting this feature to 3.2 for wheezy. > > The changes I see in linux-next are: Nice, but until kernel has this feature, I think that cpufrequtils should be updated. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#658541: upower: Shouldn't depend on libimobiledevice (that depends on usbmuxd) causing security issue and bloat
Package: upower Version: 0.9.15-1 Severity: normal What is the reason upower depends on libimobiledevice2? That library depends on usbmuxd (daemon which was vulnerable to malicious USB devices, CVE-2012-0065). In my opinion, upower shouldn't require installation of Apple-specific libraries and daemons for all users. So recommends at most, or suggest. PS: You should look also other bugs that aren't answered -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680832: libio-async-perl: FTBFS: unsatisfiable build-dependency: perl (>= 5.15.6) but 5.14.2-12 is to be installed
On Sun, Jul 08, 2012 at 12:02:43PM -0600, gregor herrmann wrote:
> On Sun, 08 Jul 2012 18:59:34 +0200, Lucas Nussbaum wrote:
>
> > > The following packages have unmet dependencies:
> > > sbuild-build-depends-libio-async-perl-dummy : Depends: perl (>= 5.15.6)
> > > but 5.14.2-12 is to be installed
> > > E: Unable to correct problems, you have held broken packages.
> > > apt-get failed.
>
> I'm not sure what's happening here:
> The package has
> libsocket-perl | perl (>= 5.15.6)
> in B-D-I, and libsocket-perl exists in unstable since the end of
> June.
> And AFAICS libsocket-perl is not yet provided by any perl{,-modules}
> packages.
>
> Anyone with ideas?
Actually it has "perl (>= 5.15.6) | libsocket-perl (>= 1.95)" and sbuild
acts on first option only. Maybe put them in reverse?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680922: unblock: libcommons-compress-java/1.4.1-2
On Mon, Jul 09, 2012 at 10:53:19AM +0200, Niels Thykier wrote:
> @@ -14,11 +14,10 @@
> Standards-Version: 3.9.3
> Homepage: http://commons.apache.org/compress/
> Vcs-Browser:
> http://svn.debian.org/wsvn/pkg-java/trunk/libcommons-compress-java/
> -Vcs-Svn: svn://svn.debian.org/pkg-java/trunk/libcommons-compress-java
> +Vcs-Svn: svn://svn.debian.org/svn/pkg-java/trunk/libcommons-compress-java
>
> Package: libcommons-compress-java
> Architecture: all
> -Depends: ${misc:Depends}
> -Suggests: libxz-java
> +Depends: ${misc:Depends}, libxz-java
> Description: Java API for working with tar, zip and bzip2 files
> Commons Compress defines an API for working with tar, zip and bzip2 files.
I think it would be good to list supported filetypes more accurately.
At upstream homepage says:
The Apache Commons Compress library defines an API for working with ar,
cpio, Unix dump, tar, zip, gzip, XZ, Pack200 and bzip2 files.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#651271: your mail
On Sat, Jun 16, 2012 at 04:19:09PM +0200, Artur Rona wrote: > tags 651271 + |moreinfo| |unreproducible > severity minor > > Hello Bernward, > > Unfortunately, I can't reproduce this bug, even with > gst-fluendo-mp3/0.10.14.debian-1. Could you full update your Debian > and try again? By my side mp3splt-gtk and quodlibet work fine. If > you can't already reproduce with latests versions, than I'd like to > close this bug. Bernward reported this bug using squeeze on powerpc. Did you test that architecture? Keep in mind that when sending mail to only bug address, submitter don't get a copy automatically, so you have to cc him. Also severity minor seems wrong. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#651795: linux-3.1 is not supported by upstream
severity 651795 grave thanks On Tue, Jul 10, 2012 at 01:25:16PM +0200, Patrick Winnertz wrote: > severity 651795 wishlist > thanks > > Hey, > > as shown on the support matrix from whamcloud (or of lustre.org) linux > 3.1 is not supported by upstream, thus the compilation of lustre-source > against the kernel source 3.1 is really allowed to fail here. > > The correct title for this bug report should be: "Support for linux 3.1 > is missing." not that it fails to compile... > > In order to use lustre you are supposed to grab your kernel source > either from SLES or from kernel.org and compile manually. Upstream support is irrelavant for this bug. If this package don't work starting from 3.1 , then it probably won't work with 3.2 sources that Debian now ship for wheezy (didn't test myself). This package should be updated to work with 3.2 sources or removed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#651795: linux-3.1 is not supported by upstream
On Tue, Jul 10, 2012 at 04:26:17PM +0200, Patrick Winnertz wrote: > Hey, > > > Upstream support is irrelavant for this bug. > Nope it is not.. > > in fact this situation was exactly the same for the last two debian > releases... lustre didn't support the standard kernel in these > releases. > this is not that bad than it sounds as lustre is a very very specific > kind of software, which is rarely/not at all used by normal users. > > This specific package is needed to build the kernel modules for the > server and the client servers of lustre - and for this you really need > plain kernel.org kernels (or SLES ones). > > I would really appreciate if we could come to the agreement, as done for > the last releases also, that the support of the standard debian kernel > is no RC bug for lustre. Loosing this type of software in debian, would > be not good. Citing wikipedia: > > Because Lustre has high performance capabilities and open licensing, it > is often used in super computers. At the present time, fifteen of the > top 30 supercomputers in the world have Lustre file systems in them, > including the world's fastest TOP500 supercomputer, IBM Sequoia. > (http://en.wikipedia.org/wiki/Lustre_(file_system)) I read some basic information from homepage and Wikipedia. Looks like 2.0, 2.1, 2.2 versions have been released in last years. Shouldn't Debian package been updated to 2.x as well? If staying on 1.8, 1.8.6 and later clients can interoperate 2.x servers. But Debian package is still at 1.8.5 with some bugs that are fixed in later versions. Maybe you should ask wider opinion what to do with Lustre in Debian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#681757: uninstallable meta-packages (prevents testing migration)
On Mon, Jul 16, 2012 at 10:34:06AM +0200, Michael Biebl wrote: > Source: meta-gnome3 > Version: 1:3.4+1 > Severity: serious > > Due to additional dependencies that were added recently, the gnome meta > packages are no longer installable on all architectures: > > > gnome/armel unsatisfiable Depends: aisleriot (>= 3.4) > > gnome/armhf unsatisfiable Depends: aisleriot (>= 3.4) > > gnome/ia64 unsatisfiable Depends: aisleriot (>= 3.4) > > This is due to guile-2.0 failing to build on those architectures. [1] > Afaics no bug has been filed for guile-2.0 about those build failures. Did you ask porters for help? Arm userbase grows and things should work. > > > gnome-core-devel/ia64 unsatisfiable Depends: libseed-gtk3-dev (>= 3.2) > > gnome-core-devel/mips unsatisfiable Depends: libseed-gtk3-dev (>= 3.2) > > seed has been broken on those architectures for a while and I don't > expect a fix any time soon. mips buildd ball had some issues with segfaults, it's now put offline https://lists.debian.org/debian-release/2012/07/msg00887.html so you should ask for mips giveback, maybe ia64 works now too? > > > At this point, I'd probably just arch-qualify those dependencies and > exclude those archs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682167: p7zip: Please enable hardening build flags
Package: p7zip Version: 9.20.1~dfsg.1-4 Severity: wishlist Hardened build flags are a release goal for Wheezy. Because this program deals with possibly untrusted data, it would be good if hardening was enabled during build. Almost all other archivers have done so. http://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags http://wiki.debian.org/Hardening http://wiki.debian.org/HardeningWalkthrough -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682169: libcommons-compress-java: Package description should list more filetypes
Package: libcommons-compress-java Version: 1.4.1-2 Severity: minor Now only tar, zip and bzip2 are listed, but more formats (like xz) are supported. Quote from homepage: The Apache Commons Compress library defines an API for working with ar, cpio, Unix dump, tar, zip, gzip, XZ, Pack200 and bzip2 files. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682255: python-paramiko: html docs use too much disk space
Package: python-paramiko Version: 1.7.7.1-3 Severity: normal python-paramiko was pulled in by obnam dependency. I noticed that /usr/share/doc/python-paramiko/docs/ directory uses 6.8 MB space for html documents that I have no use for. They should be removed, made much smaller or splitted to separate package. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (500, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.4-trunk-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 python-paramiko depends on: ii python 2.7.3~rc2-1 ii python-crypto 2.6-2 python-paramiko recommends no packages. python-paramiko 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#663653: fglrx-driver loads intel driver which doesn't find a configured screen
On Tue, Jul 24, 2012 at 11:31:24AM +0200, Paul Menzel wrote: > Dear Pedro, > > > thank you very much for your answer. Unfortunately Thomas probably did > not get your reply since you did not put him into CC. You can avoid that > problem by downloading all messages belonging to that report > > $ sudo aptitude install devscripts > $ bts show --mbox 663653 > > and import the mbox file under `~/.devscripts-cache/bts/663653.mbox` > into Icedove. Then just do a reply to all to the appropriate message. > That would be awesome. Alternate/easier way is to click mbox link in BTS page: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663653 Other mailreaders can work with mbox files too, like mutt (mutt -f mailbox) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#679252: bugs intended for linux being filed against "src"
On Wed, Jun 27, 2012 at 02:39:29PM +0100, Ben Hutchings wrote: > On Wed, 2012-06-27 at 07:56 -0500, Jonathan Nieder wrote: > > Source: linux > > Version: 3.2.20-1 > > > > Hi kernel maintainers, > > > > Gergely Nagy wrote: > > > > > reassign 679226 src:linux-2.6 3.2.20-1 > > > > Several bugs seem to have been filed against the nonexistent 'src' > > package recently. I am guessing this means reportbug or some related > > tool does not know how to deal with 'src:linux' as a package name. > > Please use plain 'linux' for now. > > reportbug-ng is doing this. Let's get it fixed. Recent bugs reported against 'src' have "X-Mailer: reportbug 6.4" Looks like reportbug is buggy too. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#681157: "reportbug src:foo" files bug against "Package: src"
I think this bug is RC severity and should be fixed for wheezy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#687442: linux-image-3.2.0-3-686-pae: Add Intel Ivy Bridge support
On Mon, Nov 26, 2012 at 10:28:56PM +0100, Julien Cristau wrote: > New image is up at > http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-amd64_3.2.34-1~jcristau.1_amd64.deb > > sha1sum is 1bbb6e4590e4f000739af89f3090ffc6bb9cb409. > diff against svn at > http://people.debian.org/~jcristau/3.2.34-1~jcristau.1.diff Tested working with Asus 1215B (AMD Radeon Brazos APU), wheezy No problems found (compared to 3.2.32-1) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692234: Intel DH77EB (H77): sporadic freeze and increased power consumption
On Sun, Dec 02, 2012 at 01:54:51PM +0100, Ingo wrote: > Since 2 weeks I an running kernel 3.4 from kernel.org. I used config from > Debian's 3.4.4-1~experimental.1 with "make silentoldconfig" and accepted > defaults fo 5 new items. This is a long term kernel as well and thus > still maintained. > > I started with 3.4.18, updated to 3.4.19 and now using 3.4.20. > All without any problems including VirtualBox 4.1.18 from Wheezy repo. > > This also appears a viable alternative to current 3.2? Julien Cristau wrote at bug #687442 --- New image is up at http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-amd64_3.2.34-1~jcristau.1_amd64.deb sha1sum is 1bbb6e4590e4f000739af89f3090ffc6bb9cb409. diff against svn at http://people.debian.org/~jcristau/3.2.34-1~jcristau.1.diff --- That kernel image is based on 3.2 with graphics system backported from 3.4 It would help if you can test that version too. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#469019: This bug should be fixed (worldwind: OpenGL exceptions should be handled better)
severity 469019 important thanks I'm also affected by this in wheezy (Radeon). This package is quite useless now. Maybe upload new version to experimental (and backports)? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701953: closed by Michael Prokop (Bug#700572: fixed in initramfs-tools 0.110)
I think that initramfs-tools 0.110 fixes should go to sid/wheezy. Or make kernels in experimental depend on this version or higher. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#572920: libltdl3: Security update breaks mpg123
Package: libltdl3
Version: 1.5.26-4+lenny1
Severity: grave
Justification: renders package unusable
Libtool security update seems to have broken mpg123 (1.4.3-4). It can't find or
load output plugins. I don't know what package to blame but things should keep
working in stable.
-- System Information:
Debian Release: 5.0.4
APT prefers stable
APT policy: (900, 'stable'), (700, 'unstable'), (500, 'oldstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libltdl3 depends on:
ii libc6 2.7-18lenny2 GNU C Library: Shared libraries
libltdl3 recommends no packages.
libltdl3 suggests no packages.
-- no debconf information
execve("/usr/bin/mpg123-alsa", ["mpg123-alsa", "-v", "../iTunes/iTunes
Music/Chorale/U"...], [/* 34 vars */]) = 0
brk(0) = 0x80f8000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7fc3000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=48713, ...}) = 0
mmap2(NULL, 48713, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7fb7000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/libncurses.so.5", O_RDONLY) = 3
read(3,
"\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0p\243\0\0004\0\0\0\344"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=202188, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7fb6000
mmap2(NULL, 202004, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb7f84000
mmap2(0xb7fb3000, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2f) = 0xb7fb3000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/i686/cmov/libdl.so.2", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`\n\0\0004\0\0\0H"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=9680, ...}) = 0
mmap2(NULL, 12412, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb7f8
mmap2(0xb7f82000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1) = 0xb7f82000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/i686/cmov/libc.so.6", O_RDONLY) = 3
read(3,
"\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260e\1\0004\0\0\0\4"..., 512)
= 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1413540, ...}) = 0
mmap2(NULL, 1418864, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb7e25000
mmap2(0xb7f7a000, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x155) = 0xb7f7a000
mmap2(0xb7f7d000, 9840, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7f7d000
close(3)= 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7e24000
set_thread_area({entry_number:-1 -> 6, base_addr:0xb7e246b0, limit:1048575,
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0,
useable:1}) = 0
mprotect(0xb7f7a000, 4096, PROT_READ) = 0
munmap(0xb7fb7000, 48713) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
open("/dev/tty", O_RDWR|O_NONBLOCK|O_LARGEFILE) = 3
close(3)= 0
brk(0) = 0x80f8000
brk(0x80f9000) = 0x80f9000
open("/usr/lib/locale/locale-archive", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=2721184, ...}) = 0
mmap2(NULL, 2097152, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7c24000
mmap2(NULL, 929792, PROT_READ, MAP_PRIVATE, 3, 0x1b6) = 0xb7b41000
close(3)= 0
brk(0x80fa000) = 0x80fa000
brk(0x80fb000) = 0x80fb000
getuid32() = 1000
getgid32() = 1000
geteuid32() = 1000
getegid32() = 1000
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
time(NULL) = 1267980860
brk(0x80fc000) = 0x80fc000
open("/proc/meminfo", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7fc2000
read(3, "MemTotal: 776044 kB\nMemFree"..., 1024) = 872
close(3)= 0
munmap(0xb7fc2000, 4096)= 0
brk(0x80fd000) = 0x80fd000
rt_sigaction(SIGCHLD, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGCHLD, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt
Bug#572975: mpg123 1.10.1 - "the most wanted maintenance release"
Package: mpg123 Version: 1.10.0-2 Severity: normal Upstream has released mpg123 1.10.1 - "the most wanted maintenance release" You should mention homepage address (mpg123.org) in package description. Also watch file would be nice to have. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#523475: Unfixed bugs in lenny version
Is #523475 and #517792 same bug? And is it still in 1.1.14-6 (lenny)? Also #522811 seems unfixed too. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#627811: loadcpufreq does not support AMD E-350 cpus
Package: cpufrequtils Severity: normal It would be good if at least this was fixed also in squeeze (in next point update). I think it qualifies, but debian-release@l.d.o can answer. -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (900, 'stable'), (700, 'testing'), (600, 'unstable'), (500, 'stable-updates') Architecture: i386 (i686) Kernel: Linux 2.6.39-2-686-pae (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 cpufrequtils depends on: ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy ii libc6 2.11.2-10Embedded GNU C Library: Shared lib ii libcpufreq0 007-1shared library to deal with the cp ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip cpufrequtils recommends no packages. cpufrequtils suggests no packages. -- debconf information: cpufrequtils/enable: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#627811: Bug#637395: linux-image-3.0.0-1-686-pae: EEE-PC 1000H: cpufreq cannot be set to ondemand
On Fri, Aug 12, 2011 at 11:49:44AM -0500, Jonathan Nieder wrote: > Ben Hutchings wrote: > >> Am 11.08.2011 23:27, schrieb Jonathan Nieder: > > >>> I suspect we really want to be using acpi-cpufreq, not p4-clockmod. > >>> So we're closing in. > [...] > > It is not EeePC-specific. > > > > cpufreq modules are loaded by the cpufrequtils package, and it is > > now loading the wrong modules due to a change in the installation > > location of the modules. This is bug #636141, fixed in version > > 007-2. > > Thanks, Ben. I wonder if there's something the kernel can do to help > people who use a sid kernel on squeeze. A Breaks is probably too > heavyweight. Maybe upstream can be convinced to put the cpufreq > drivers in a separate directory from the governors. > > (I wish cpufrequtils had used "ls" instead of "find".) I think that most of the cpufrequtils 007-2 fixes should be also in squeeze (point update maybe). There is also #627811 (AMD family 20 support, i.e. E-350 etc). AMD Fusion Llano is family 18, support for it should be added too. http://www.phoronix.com/vr.php?view=16292 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#644572: sysvinit: Spins disk up briefly from standby during poweroff
Package: sysvinit Version: 2.88dsf-13.1 Severity: normal I have system that mainly runs from SSD. Hard disk partitions are mounted only when needed and disks are put to standby automatically after idle time. However even when no HDD filesystems are mounted (and disk is spun down), during shutdown sequence (when power button is pressed) the disk spins up briefly, only to spin down instantly. It causes unneeded wear to disk mechanics. I suspect that "-h" option that "halt" gets during poweroff is buggy and shouldn't spin disks up that are already at sleep. I'm not 100% sure that this bug belongs to halt, some more debugging (by me if I find extra time) or somebody else is needed. -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (900, 'stable'), (700, 'testing'), (600, 'unstable'), (500, 'stable-updates') Architecture: i386 (x86_64) Kernel: Linux 3.0.0-1-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 sysvinit depends on: ii initscripts 2.88dsf-13.1 scripts for initializing and shutt ii libc6 2.11.2-10Embedded GNU C Library: Shared lib ii libselinux1 2.0.96-1 SELinux runtime shared libraries ii libsepol1 2.0.41-1 SELinux library for manipulating b ii sysv-rc 2.88dsf-13.1 System-V-like runlevel change mech ii sysvinit-utils 2.88dsf-13.1 System-V-like utilities sysvinit recommends no packages. sysvinit 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#644572: [Pkg-sysvinit-devel] Bug#644572: sysvinit: Spins disk up briefly from standby during poweroff
On Thu, Oct 06, 2011 at 09:57:05PM -0300, Henrique de Moraes Holschuh wrote: > On Fri, 07 Oct 2011, Touko Korpela wrote: > > I suspect that "-h" option that "halt" gets during poweroff is buggy and > > shouldn't spin disks up that are already at sleep. > > Nowadays we're supposed to trust the kernel to do it right, and your disk > should spin up only if it has crap firmware (unlikely). Unless you're using > the deprecated "old ide" drivers (/dev/hd*), in which case all bets are off. > > Please edit /etc/init.d/halt and make it not add "-h" to the halt invocation > (but make sure to add "sync ; sleep 5" before the halt command just in > case). Does that fix the issue? It doesn't make a difference. So maybe it's a kernel issue then. Same happens with another laptop that has Hitachi HTS54502 disk, so this issue is more common. This has a Seagate disk. Here is some lines from kernel 3.0.0-1-amd64 (Debian 3.0.0-3) boot dmesg. [1.425212] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [1.651042] SCSI subsystem initialized [1.681254] ahci :00:11.0: AHCI 0001.0200 32 slots 1 ports 3 Gbps 0x1 impl SATA mode [1.690438] scsi0 : ahci [1.690697] ata1: SATA max UDMA/133 abar m1024@0xfeb4c000 port 0xfeb4c100 irq 19 [2.196281] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [2.504191] ata1.00: ATA-8: ST9500325AS, 0003SDM1, max UDMA/133 [2.504199] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32) [2.506494] ata1.00: configured for UDMA/133 [2.507008] scsi 0:0:0:0: Direct-Access ATA ST9500325AS 0003 PQ: 0 ANSI: 5 [2.517044] scsi1 : usb-storage 2-2:1.0 [2.518624] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB) [2.518751] sd 0:0:0:0: [sda] Write Protect is off [2.518757] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [2.518810] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [2.548221] sda: sda1 sda2 sda3 sda4 [2.549024] sd 0:0:0:0: [sda] Attached SCSI disk [3.650505] scsi 1:0:0:0: Direct-Access Multiple Card Reader 1.00 PQ: 0 ANSI: 0 [4.608143] sd 1:0:0:0: [sdb] Attached SCSI removable disk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#644572: Spins disk up briefly from standby during poweroff
On Fri, Oct 07, 2011 at 02:29:06PM +0300, Touko Korpela wrote: > On Thu, Oct 06, 2011 at 09:57:05PM -0300, Henrique de Moraes Holschuh wrote: > > Nowadays we're supposed to trust the kernel to do it right, and your disk > > should spin up only if it has crap firmware (unlikely). Unless you're using > > the deprecated "old ide" drivers (/dev/hd*), in which case all bets are off. > > > > Please edit /etc/init.d/halt and make it not add "-h" to the halt invocation > > (but make sure to add "sync ; sleep 5" before the halt command just in > > case). Does that fix the issue? > > It doesn't make a difference. So maybe it's a kernel issue then. > Same happens with another laptop that has Hitachi HTS54502 disk, so this > issue is more common. This has a Seagate disk. > > Here is some lines from kernel 3.0.0-1-amd64 (Debian 3.0.0-3) boot dmesg. > > [1.425212] Block layer SCSI generic (bsg) driver version 0.4 loaded > (major 253) > [1.651042] SCSI subsystem initialized > [1.681254] ahci :00:11.0: AHCI 0001.0200 32 slots 1 ports 3 Gbps 0x1 > impl SATA mode > [1.690438] scsi0 : ahci > [1.690697] ata1: SATA max UDMA/133 abar m1024@0xfeb4c000 port 0xfeb4c100 > irq 19 > [2.196281] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > [2.504191] ata1.00: ATA-8: ST9500325AS, 0003SDM1, max UDMA/133 > [2.504199] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32) > [2.506494] ata1.00: configured for UDMA/133 > [2.507008] scsi 0:0:0:0: Direct-Access ATA ST9500325AS > 0003 PQ: 0 ANSI: 5 > [2.517044] scsi1 : usb-storage 2-2:1.0 > [2.518624] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 > GB/465 GiB) > [2.518751] sd 0:0:0:0: [sda] Write Protect is off > [2.518757] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 > [2.518810] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, > doesn't support DPO or FUA > [2.548221] sda: sda1 sda2 sda3 sda4 > [2.549024] sd 0:0:0:0: [sda] Attached SCSI disk > [3.650505] scsi 1:0:0:0: Direct-Access Multiple Card Reader > 1.00 PQ: 0 ANSI: 0 > [4.608143] sd 1:0:0:0: [sdb] Attached SCSI removable disk Here is missing ahci lines from that dmesg [1.681098] ahci :00:11.0: version 3.0 [1.681139] ahci :00:11.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 [1.681262] ahci :00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#644572: Spins disk up briefly from standby during poweroff
#reassigning this to kernel, also 2.6.32 behaves this way reassign 644572 src:linux-2.6 found 644572 2.6.32-35 found 644572 3.0.0-3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645466: When running from removable media, udev allows direct access by "floppy" group
Package: udev Version: 164-3 Severity: important Tags: security Udev sets device permissions too loose when system runs from removable media. It should see that root filesystem is there and allow access by disk group only. Here is example (sda is internal disk, sdb is SD memory card where Debian is installed and running now) --- root@lisko:~# ls -l /dev/sd* brw-rw 1 root disk 8, 0 Oct 16 01:17 /dev/sda brw-rw 1 root disk 8, 1 Oct 16 01:17 /dev/sda1 brw-rw 1 root disk 8, 2 Oct 16 01:17 /dev/sda2 brw-rw 1 root disk 8, 3 Oct 16 01:17 /dev/sda3 brw-rw 1 root disk 8, 4 Oct 16 01:17 /dev/sda4 brw-rw 1 root disk 8, 5 Oct 16 01:17 /dev/sda5 brw-rw 1 root floppy 8, 16 Oct 16 01:26 /dev/sdb brw-rw 1 root floppy 8, 17 Oct 16 01:17 /dev/sdb1 root@lisko:~# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdb1 7592316 6055756 1459428 81% / --- -- System Information: Debian Release: 6.0.3 APT prefers stable Architecture: i386 (x86_64) Kernel: Linux 3.0.0-2-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 udev depends on: ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy ii libc6 2.11.2-10Embedded GNU C Library: Shared lib ii libselinux1 2.0.96-1 SELinux runtime shared libraries ii libudev0164-3libudev shared library ii libusb-0.1-42:0.1.12-16 userspace USB programming library ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii util-linux 2.17.2-9 Miscellaneous system utilities Versions of packages udev recommends: ii pciutils 1:3.1.7-6 Linux PCI Utilities ii usbutils 0.87-5squeeze1 Linux USB utilities udev suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645709: www.debian.org: Debian “squeeze” Installation Information , errata outdated?
Package: www.debian.org Severity: normal Tags: d-i http://www.debian.org/releases/squeeze/debian-installer/ Errata lists some items as "This will be fixed on the next Squeeze point release (6.0.1)". Now 6.0.3 is released, so maybe those are now fixed? This line has a typo: netinst (generally 175-240 MB) non-free CD images with --> firmare <-- -- System Information: Debian Release: 6.0.3 APT prefers stable Architecture: i386 (x86_64) Kernel: Linux 3.0.0-2-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#627811: fixed version
# mark fixed version back fixed 627811 007-2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#638878: linux-image-3.0.0-1-amd64: Maybe report Debian kernel version with uname
Package: linux-2.6 Version: 3.0.0-2 Severity: wishlist Would it be possible to report Debian kernel version in uname output? Maybe it can be added to "kernel version" string, uname -v (now it's "#1 SMP Wed Aug 17 05:07:22 UTC 2011". This information is present in /proc/version and could be in uname too. -- Package-specific info: ** Version: Linux version 3.0.0-1-amd64 (Debian 3.0.0-2) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-5) ) #1 SMP Wed Aug 17 05:07:22 UTC 2011 ** Model information sys_vendor: ASUSTeK Computer INC. product_name: 1215B product_version: x.x chassis_vendor: ASUSTeK Computer INC. chassis_version: x.x bios_vendor: American Megatrends Inc. bios_version: 0401 board_vendor: ASUSTeK Computer INC. board_name: 1215B board_version: x.xx ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1510] Subsystem: Advanced Micro Devices [AMD] Device [1022:1510] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- [disabled] Capabilities: Kernel driver in use: radeon 00:01.1 Audio device [0403]: ATI Technologies Inc Device [1002:1314] Subsystem: ASUSTeK Computer Inc. Device [1043:84a5] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: HDA Intel 00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Device [1022:1512] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] [1002:4391] (prog-if 01 [AHCI 1.0]) Subsystem: ATI Technologies Inc Device [1002:4390] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ahci 00:12.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] (prog-if 10 [OHCI]) Subsystem: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Kernel driver in use: ehci_hcd 00:13.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] (prog-if 10 [OHCI]) Subsystem: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Kernel driver in use: ehci_hcd 00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 42) Subsystem: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Kernel driver in use: HDA Intel 00:14.3 ISA bridge [0601]: ATI Technologies Inc SB700/SB800 LPC host controller [1002:439d] (rev 40) Subsystem: ATI Technologies Inc SB700/SB800 LPC host controller [1002:439d] Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:15.0 PCI bridge [0604]: ATI Technologies Inc Device [1002:43a0] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:15.2 PCI bridge [0604]: ATI Technologies Inc Device [1002:43a2] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
Bug#638878: linux-image-3.0.0-1-amd64: Maybe report Debian kernel version with uname
On Mon, Aug 22, 2011 at 01:44:03PM -0500, Jonathan Nieder wrote: > Ben Hutchings wrote: > >> Touko Korpela wrote: > > >>> Would it be possible to report Debian kernel version in uname > >>> output? Maybe it can be added to "kernel version" string, uname -v > >>> (now it's "#1 SMP Wed Aug 17 05:07:22 UTC 2011". > >>> This information is present in /proc/version and could be in uname too. > [...] > > I don't think uname(1) should be changed; it is supposed to report > > just what uname(2) does. We should change the behaviour of the > > latter, if anything. > > Ah, ok. I admit my bias is towards not passing this information back > from uname(2), since application authors could be tempted to parse it > to provide Debian-specific behavior changes (for example, to work > around bugs using the Debian kernel version number instead of finding > some robust way to work around them that applies to other distros, > too). On the other hand, as a human-readable version identifier, > "linux-2.6 3.0.0-2 as compiled by Ben Hutchings on 2011-08-17 > 04:08:52" is more convenient than > > Linux 3.0.0-1-amd64 #1 SMP Wed Aug 17 04:08:52 UTC 2011 x86_64 GNU/Linux > > What is the underlying problem being solved? Is it that it is hard > when reporting bugs to tell the difference between the package version > and ABI version in order to provide the former? For example when reporting bugs upstream and using their scripts. It's true that you can sometimes guess Debian version number from the compile time (that shows in uname) but if Debian version can be added there I say go for it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#638878: linux-image-3.0.0-1-amd64: Maybe report Debian kernel version with uname
On Mon, Aug 22, 2011 at 11:27:10AM -0600, Bob Proulx wrote: > tags 638878 + moreinfo > thanks > > Touko Korpela wrote: > > Would it be possible to report Debian kernel version in uname > > output? Maybe it can be added to "kernel version" string, uname -v > > (now it's "#1 SMP Wed Aug 17 05:07:22 UTC 2011". > > This information is present in /proc/version and could be in uname too. > > Exactly what information is it precisely that you wish included in > 'uname' output? Because uname already includes the kernel version > information. > > $ uname -a > Linux example 3.0.0-1-amd64 #1 SMP Sun Jul 24 02:24:44 UTC 2011 x86_64 > GNU/Linux It shows now only Debian package name (3.0.0-1-amd64 part), not version (3.0.0-2). > > I don't yet know what information you want to access from > /proc/version but since accessing specific information from > /proc/version is intrinsically non-portable it seems bad to hack it > into 'uname' making it more non-portable. And since it is trivial to > read it from /proc/version directly there doesn't seem to be any need > to hack this into 'uname'. Why not read it from /proc/version directly? It's simpler if you don't need to find data from many places. I think "uname -a" should tell version of kernel package used if that information is available. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#638896: clarification
On Mon, Aug 22, 2011 at 08:48:24PM +0100, Luke Kenneth Casson Leighton wrote: > valentijn, hi, > Your messages don't reach valentijn if you only send mail to bugnumber address...people aren't automatically subscribed to bugs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#638896: linux-image-2.6.39-bpo.2-amd64 root filesystem not found on boot [SOLVED?]
On Mon, Aug 22, 2011 at 10:47:24PM +0200, Valentijn Scholten wrote: > After making some backups, I tried to upgrade the kernel again. > Guess what? It just works now. > The term.log section looks nothing like the one above. > Also the old kernel has been retained. Please use reply fuction when posting to existing bug, if possible. Failure to do so breaks threading. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#635826: hda-intel (CX20549 (Venice)): external speaker output and mic inputs mute
On Thu, Aug 25, 2011 at 07:16:34PM +0200, Johann Felix Soden wrote: > Hi, > > Since I have a hardware failure now and have not reported this bug > upstream yet, I would be glad, if you, Antony, could take care of > this. > > For the same reason, I cannot say anything about ogg123. > > Some time ago, I used HDA Analyzer [1] and could enable the external > speaker output by enabling EAPD, unmuting and raising the volume of the > right pin. > > Best regards, > Johann Felix > > [1] http://www.alsa-project.org/main/index.php/HDA_Analyzer Unfortunately, Alsa upstream support seems to be nonexistent lately. Nobody takes any action on bugs reported to bug tracker there. Also if you try to mail alsa-devel list and you're not subscribed, your mail is stuck in some hole (it should be reviewed by moderators instead). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#635826: hda-intel (CX20549 (Venice)): external speaker output and mic inputs mute
On Sun, Aug 28, 2011 at 06:52:44PM +0100, Ben Hutchings wrote: > On Sun, 2011-08-28 at 17:04 +0300, Touko Korpela wrote: > > > [1] http://www.alsa-project.org/main/index.php/HDA_Analyzer > > > > Unfortunately, Alsa upstream support seems to be nonexistent lately. Nobody > > takes any action on bugs reported to bug tracker there. > > The bug tracker is a trap. Bugs reported to the mailing list or a > specific driver maintainer are more likely to get fixed. > It would make sense if driver maintainers were following bugs that are reported under their own section. However many bugs are in wrong section. > > Also if you try to > > mail alsa-devel list and you're not subscribed, your mail is stuck in some > > hole > > (it should be reviewed by moderators instead). > > You can whitelist yourself by subscribing to the list and then setting > the no-mail option. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#641466: modemmanager: ModemManager logs connection stats every two seconds, filling logs
Package: modemmanager Version: 0.4+git.20100624t180933.6e79d15-2 Severity: important ModemManager logs every two seconds amount of data transmitted (even if no data was transmitted). It's way too often as default setting. Maximum once per minute seems more sensible default. -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (900, 'stable'), (700, 'testing'), (600, 'unstable'), (500, 'stable-updates') Architecture: i386 (x86_64) Kernel: Linux 3.0.0-1-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 modemmanager depends on: ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libdbus-1-31.2.24-4+squeeze1 simple interprocess messaging syst ii libdbus-glib-1-2 0.88-2.1 simple interprocess messaging syst ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libgudev-1.0-0 164-3 GObject-based wrapper library for Versions of packages modemmanager recommends: ii usb-modeswitch 1.1.9-2~bpo60+1 mode switching tool for controllin modemmanager 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#641467: modemmanager: Please include relevant changelog entries when uploading to unstable
Package: modemmanager Version: 0.4+git.20100624t180933.6e79d15-2 Severity: wishlist Changelog has in some versions entries like "Upload to unstable.". If new ModemManager versions are uploaded somewhere else, please make sure that no changelogs that are relevant also for Debian unstable version are lost. -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (900, 'stable'), (700, 'testing'), (600, 'unstable'), (500, 'stable-updates') Architecture: i386 (x86_64) Kernel: Linux 3.0.0-1-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 modemmanager depends on: ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libdbus-1-31.2.24-4+squeeze1 simple interprocess messaging syst ii libdbus-glib-1-2 0.88-2.1 simple interprocess messaging syst ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libgudev-1.0-0 164-3 GObject-based wrapper library for Versions of packages modemmanager recommends: ii usb-modeswitch 1.1.9-2~bpo60+1 mode switching tool for controllin modemmanager 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#641469: mobile-broadband-provider-info: Please provide updates for stable distribution, somehow
Package: mobile-broadband-provider-info Version: 20110806-1 Severity: normal This package should receive regular updates also in stable (squeeze). I think it qualifies for point updates (like for example "tzdata"). Other possibility is using backports archive but uploading directly to squeeze is preferred (and low-risk thing because of data-only package). Maybe ask release managers opinion about this? -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (900, 'stable'), (700, 'testing'), (600, 'unstable'), (500, 'stable-updates') Architecture: i386 (x86_64) Kernel: Linux 3.0.0-1-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 -- 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#677655: 3.4-trunk-486: kernel oops: EIP is at __destroy_inode+0x56/0x8d
On Sun, Jul 14, 2013 at 06:32:05PM +0200, Moritz Mühlenhoff wrote: > Version: 3.9-1 > > On Fri, Jul 12, 2013 at 11:19:56AM +0300, Martin-Éric Racine wrote: > > It still does with 3.2 in stable, but not with 3.9 in testing. > > Closing with that version, then. No such version (3.9-1) was uploaded, 3.9.4-1 was first 3.9 upload. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#720119: crda: New upstream version available
Package: crda Version: 1.1.2-1 Severity: wishlist CRDA version 1.1.3 was released in last year. Watch file needs updating also. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#719334: crda: Wrong country selected for wlan regulatory domain (sometimes)
On Sun, Aug 11, 2013 at 01:29:22AM +0200, Ben Hutchings wrote: > Control: tag -1 moreinfo > > On Sun, 2013-08-11 at 01:28 +0300, Touko Korpela wrote: > > Package: crda > > Version: 1.1.2-1 > > Severity: normal > > > > Dear Maintainer, > > for some reason cdra or kernel puts wireless adapter to wrong country mode > > (TW). I use NetworkManager for managing networking in this laptop. I have > > configured to log automatically in primary WPA2 network. When I select other > > WPA2 network, TW setting is used instead of correct (FI). > [...] > > This is not a bug in crda - the kernel is responsible for deciding which > regulatory domain(s) are in effect, and crda only tells it the current > rules for the domain(s) it's interested in. > > I suspect that the access point is a 'parallel import' from Taiwan which > is not configured for the correct region. Does this seem possible? > When the access point and the local configuration specify two different > domains, the kernel is supposed to use the intersection of the rules for > the two domains. I got it from Finnish store. That AP (Telewell TW-EA510) is software designed/customised some way in Finland. And I selected Europe as wireless region in AP settings. And anyway it shouldn't select Taiwan because it has bigger limits for transmit power if I look "max_eirp" number in logs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#719334: crda: Wrong country selected for wlan regulatory domain (sometimes)
Upstream has released CRDA version 1.1.3 but I didn't find changelog for it. Maybe it's a good thing to package it even if no effect for this issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#654957: cpufrequtils: loadcpufreq does not support AMD Bulldozer CPUs
I think you should also add family 18 (AMD Fusion Llano). http://www.phoronix.com/vr.php?view=16292 On Sat, Jan 07, 2012 at 12:06:05AM -0600, Robert Keevil wrote: > Package: cpufrequtils > Version: 007-2 > Severity: normal > Tags: patch > > /etc/init.d/loadcpufreq does not support AMD Bulldozer CPUs, which have a CPU > family of 21. The processor is supported by the powernow_k8 module. > --- debian/cpufrequtils.loadcpufreq.init.dist 2012-01-06 23:35:24.867961318 > -0600 > +++ debian/cpufrequtils.loadcpufreq.init 2012-01-06 23:35:32.759956550 > -0600 > @@ -119,7 +119,7 @@ > # K7 > MODULE=powernow-k7 > ;; > -15|16|17|20) > +15|16|17|20|21) > # K8 > MODULE=powernow-k8 > ;; -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#663269: [3.2.7 -> 3.2.9 regression] rt flavor: Hard freezes when starting KDM
On Sun, Mar 11, 2012 at 07:37:51PM +0400, Boris Pek wrote: > Hi, > > > > startx command launched LXDE (I have both KDE and LXDE) and it > > > worked normally. > > > > Thanks --- this is a very useful detail. So probably non-accelarated > > rendering works fine, and it is something in 3d codepaths that makes it > > freeze. > > Ok. I saw interesting instructions in bug report #663379. Could I help in > a same way? I can build kernel (or few modules) with patches for tests. > Today I have a little free time for this. But I have only 32 system for > tests... > > > > dmesg log is attached. But it also useless I think. > > > When system freezes logs are not updated... > > > > The attached log seems to be for a boot with the non-rt kernel. Am I > > understanding correctly? > > Yes, you are right. Sorry, but I don't know how I can get logs from previous > boot. As I wrote earlier /var/log/Xorg.1.log is outdated. Maybe check /var/log/Xorg.0.log.old (logs between Xorg.0.log and Xorg.1.log)? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645997: installation-reports: Failed install with encrypted LVM (kernel install fails)
On Wed, Oct 26, 2011 at 09:13:11PM +0100, Miguel Figueiredo wrote: > Hi, > > i have been trying to reproduce the bug but i haven't been able to do it > anymore even after several atempts. > Can you still reproduce it? Sorry taking long to answer. It was btrfs issue, I soon made another try with ext4, it worked. I have read that btrfs should now work with current 3.2.x kernel. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645997: installation-reports: Failed install with encrypted LVM (kernel install fails)
On Tue, Mar 20, 2012 at 11:00:45PM +, Miguel Figueiredo wrote: > Hi, > > a few days ago i've tested an installation with btrfs and didn't > failed as before. > Please give also some feedback on your tests. I haven't made any new tests after first try. You can close this. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#596110: cpuid and other packages needs updates (maintainer mia?)
Cpuid hasn't updated in more than five years. Bugs aren't answered. Also other packages by this maintainer (Aurélien GÉRÔME) haven't seen updates for many years. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674435: Please upload new firmware packages
Package: firmware-brcm80211 Version: 0.35 Severity: wishlist Upstream repository has some new/updated firmwares available. Also it would be good to ask if Broadcom has new firmwares available for wireless cards (firmware-brcm80211). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674487: Please enable hardening build flags
Package: arpwatch Version: 2.1a15-1.1 Severity: important Hardened build flags are a release goal for Wheezy. Because this package deals with network connections, it would be good if hardening was enabled during build. Sorry for late report, this package was apparently missed first. It qualifies for "All daemons and libraries accessible from the network" part of release goal. http://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags http://wiki.debian.org/Hardening http://wiki.debian.org/HardeningWalkthrough -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674493: Hardening build flags are appilied only partly
Package: libpcap0.8 Version: 1.2.1-2 Severity: normal I looked libpcap build logs after "hardening-check" tool from hardening-includes shows that Fortify Source (-D_FORTIFY_SOURCE=2) isn't in use in this library. Is it intentional? make[1]: Entering directory `/build/buildd-libpcap_1.2.1-2-i386-uqZbDK/libpcap-1.2.1' gcc -O2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -I. -DH AVE_CONFIG_H -D_U_="__attribute__((unused))" -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wf ormat -Werror=format-security -c -o pcap-linux.o ./pcap-linux.c gcc -O2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -I. -DH AVE_CONFIG_H -D_U_="__attribute__((unused))" -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wf ormat -Werror=format-security -c -o pcap-usb-linux.o ./pcap-usb-linux.c Looks like -O2 option is present three times and other options two times. Could -D_FORTIFY_SOURCE=2 be added to flags too? http://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags http://wiki.debian.org/Hardening http://wiki.debian.org/HardeningWalkthrough -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674537: Hardening build flags are applied only partially
Package: aria2 Version: 1.15.0-1 Severity: normal I looked at build logs and it shows that Fortify Source (-D_FORTIFY_SOURCE=2) is missing from compile flags. And mostly flags are ignored. When compiling in this directory other harnening features are enabled: make[7]: Entering directory `/build/buildd-aria2_1.15.0-1-i386-oexzB9/aria2-1.15.0/deps/wslay/lib' /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -DHAVE_CONFIG_H -I./includes -I./includes -Wall -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -MT wslay_frame.lo -MD -MP -MF .deps/wslay_frame.Tpo -c -o wslay_frame.lo wslay_frame.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -DHAVE_CONFIG_H -I./includes -I./includes -Wall -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -MT wslay_frame.lo -MD -MP -MF .deps/wslay_frame.Tpo -c wslay_frame.c -o wslay_frame.o But when entering directory src it seems that no hardening is enabled. Making all in src make[3]: Entering directory `/build/buildd-aria2_1.15.0-1-i386-oexzB9/aria2-1.15.0/src' g++ -DHAVE_CONFIG_H -I. -I.. -Wall -I../lib -I../intl -DLOCALEDIR=\"/usr/share/locale\" -DCA_BUNDLE=\"/etc/ssl/certs/ca-certificates.crt\" -DHAVE_CONFIG_H -I../deps/wslay/lib/includes -I../deps/wslay/lib/includes -I/usr/include/p11-kit-1 -I/usr/include/libxml2 -g -O2 -MT SocketCore.o -MD -MP -MF .deps/SocketCore.Tpo -c -o SocketCore.o SocketCore.cc Here are some links that maybe help: http://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags http://wiki.debian.org/Hardening http://wiki.debian.org/HardeningWalkthrough -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671578: Hardening build flags are applied only partially
reopen 671578 thanks When looking at build logs it seems that different hardening options are in use in different directories. Under directory dbus-c++ only -D_FORTIFY_SOURCE=2 is in use Under directory mlib also -Wformat -Wformat-security -Werror=format-security is in use. Stack protector isn't in use anywhere. http://wiki.debian.org/Hardening http://wiki.debian.org/HardeningWalkthrough -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674570: Please enable hardening build flags
Package: libvpx Version: 1.1.0-1 Severity: wishlist Hardened build flags are a release goal for Wheezy. Because this package deals with untrusted data, it would be good if hardening was enabled during build. Maybe "All daemons and libraries accessible from the network" part of release goal applies, then bug should have important severity. http://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags http://wiki.debian.org/Hardening http://wiki.debian.org/HardeningWalkthrough -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674577: Please enable hardening build flags
Package: tcptraceroute Version: 1.5beta7+debian-4 Severity: wishlist Hardened build flags are a release goal for Wheezy. Because this package deals with network connections, it would be good if hardening was enabled during build. http://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags http://wiki.debian.org/Hardening http://wiki.debian.org/HardeningWalkthrough -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672891: wireless brcms_c_wait_for_tx_completion warning
On Fri, May 25, 2012 at 11:34:07AM -0500, Jonathan Nieder wrote: > Hi, > > Touko Korpela wrote: > > > Here is log from 3.2.18-1 kernel with X125 laptop. WARNING is there. > [...] > > Linux version 3.2.0-2-686-pae (Debian 3.2.18-1) > > (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-5) ) #1 > > SMP Mon May 21 18:24:12 UTC 2012 > [...] > > [ cut here ] > > WARNING: at [...]/drivers/net/wireless/brcm80211/brcmsmac/main.c:8241 > > brcms_c_wait_for_tx_completion+0x73/0x7d [brcmsmac]() > > Hardware name: X125 > > Modules linked in: cryptd aes_i586 aes_generic bridge stp bnep rfcomm > > powernow_k8 mperf cpufreq_stats cpufreq_userspace cpufreq_conservative > > cpufreq_powersave fuse loop snd_hda_codec_hdmi joydev arc4 brcmsmac > > mac80211 brcmutil snd_hda_codec_realtek radeon snd_hda_intel ttm > > drm_kms_helper drm uvcvideo snd_hda_codec snd_hwdep snd_pcm snd_seq tpm_tis > > tpm tpm_bios snd_timer ac button videodev media btusb evdev sp5100_tco > > snd_seq_device video battery processor k10temp snd samsung_laptop > > i2c_algo_bit pcspkr power_supply i2c_piix4 i2c_core bluetooth cfg80211 > > shpchp rfkill psmouse serio_raw soundcore crc8 snd_page_alloc cordic ext4 > > mbcache jbd2 crc16 usb_storage uas sd_mod crc_t10dif ohci_hcd ahci libahci > > libata ehci_hcd scsi_mod thermal thermal_sys usbcore usb_common sky2 [last > > unloaded: scsi_wait_scan] > > Pid: 3127, comm: kworker/u:2 Not tainted 3.2.0-2-686-pae #1 > > Call Trace: > > [] ? warn_slowpath_common+0x68/0x79 > > [] ? brcms_c_wait_for_tx_completion+0x73/0x7d [brcmsmac] > > [] ? warn_slowpath_null+0xd/0x10 > > [] ? brcms_c_wait_for_tx_completion+0x73/0x7d [brcmsmac] > > [] ? brcms_ops_flush+0x1f/0x29 [brcmsmac] > > [] ? ieee80211_scan_work+0x36a/0x3fb [mac80211] > > [] ? process_one_work+0x112/0x1fa > > [] ? ieee80211_scan_rx+0x139/0x139 [mac80211] > > [] ? worker_thread+0xa9/0x122 > > [] ? manage_workers.isra.23+0x13d/0x13d > > [] ? kthread+0x63/0x68 > > [] ? kthread_worker_fn+0x101/0x101 > > [] ? kernel_thread_helper+0x6/0x10 > > ---[ end trace b3b9484c4306740d ]--- > > This is 20 hours after boot so I'm guessing it's not easy to reproduce. > Alas. Thanks for reporting it. > > Do you think the patch added in 3.2.18 made a difference? How often > were you getting the wait_for_tx_completion WARNING before, and are > you getting it less often now? (I'm asking because this information > would probably be helpful to upstream in diagnosing this.) (last followup was sent to cloned bug by mistake) Hard to say if it made difference, maybe made it more rare. Logs show only a few this kind of warnings in last weeks running 3.2.1x It always happens after many hours of uptime except 3.2.17-1 case that happened sooner but it doesn't mean much. That computer is always on doing some backround calculations that causes small amount of network traffic and is sometimes used locally for browsing and applying updates. But should this bug be opened again? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674594: New upstream version available
Package: nload Version: 0.7.3-1 Severity: normal A new upstream version is available (0.7.4) It should fix Debian bug #651848 Also hardening build flags could be enabled (if not too much extra work) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#672891: brcmsmac wireless brcms_c_wait_for_tx_completion warning
On Thu, May 24, 2012 at 05:44:23PM +0300, Touko Korpela wrote: > I don't know if it's regression or not but when I rebooted 3.2.18-1, kernel > oopsed during shutdown (it wasn't logged). I don't remember that happened > before. False alarm, it wasn't kernel oops, it was X server segfault at shutdown bug #671812, fixed by xorg-server 2:1.12.1.902-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674658: Please enable hardening build flags
Package: procmail Version: 3.22-19 Severity: wishlist Hardened build flags are a release goal for Wheezy. http://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags http://wiki.debian.org/Hardening http://wiki.debian.org/HardeningWalkthrough -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
