Bug#271013: console-tools: Cause of problem: unicode_start is too smart

[Maik Zumstrull]

Package: console-tools
Version: 1:0.2.3dbs-55
Followup-For: Bug #271013

I have the same problem on this machine.
I checked out /etc/init.d/console-screen.sh, and it detects the
UTF-8 locale and runs unicode_start just fine.

However, unicode_start uses "fgconsole --next-available" to make
sure it only switches TTYs which are already allocated into UTF-8
mode. Unfortunately, console-screen.sh runs before the gettys
allocate TTYs 2-6.

Possible workarounds:
-- start gettys earlier in the boot process
-- do the actual work in console-screen.sh itself, i.e.
   allocate TTYs 1-n and do a "echo -e '\033%G'"

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (700, 'unstable'), (600, 'testing'), (50, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages console-tools depends on:
ii  console-common 0.7.48Basic infrastructure for text cons
ii  debconf1.4.42Debian configuration management sy
ii  libc6  2.3.2.ds1-20  GNU C Library: Shared libraries an
ii  libconsole 1:0.2.3dbs-55 Shared libraries for Linux console
ii  sysvinit   2.86.ds1-1System-V like init

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#337812: linux-2.6: DVD drive not recognized on IBM ThinkPad T43p

[Maik Zumstrull]

Package: linux-2.6
Severity: wishlist

The T43p uses a PATA DVD drive on a SATA-PATA bridge on a SATA port of the 
chipset (ICH6M).

This setup is supposedly usable with 2.6.14, provided libata is loaded with the 
atapi_enabled=1 module option.

Here is more information about the system:


[EMAIL PROTECTED]:~$ lspci
:00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express 
Processor to DRAM Controller (rev 03)
:00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express 
Root Port (rev 03)
:00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
PCI Express Port 1 (rev 03)
:00:1c.2 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
PCI Express Port 3 (rev 03)
:00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 
Family) USB UHCI #1 (rev 03)
:00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 
Family) USB UHCI #2 (rev 03)
:00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 
Family) USB UHCI #3 (rev 03)
:00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 
Family) USB UHCI #4 (rev 03)
:00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 
Family) USB2 EHCI Controller (rev 03)
:00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
:00:1e.2 Multimedia audio controller: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
:00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 
Modem Controller (rev 03)
:00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface 
Bridge (rev 03)
:00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller 
(rev 03)
:00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus 
Controller (rev 03)
:01:00.0 VGA compatible controller: ATI Technologies Inc M24 1T [FireGL M24 
GL] (rev 80)
:02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751M 
Gigabit Ethernet PCI Express (rev 11)
:04:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 8d)
:04:02.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg 
NIC (rev 01)


Note: Full dmesg is at the end, important stuff for now


[EMAIL PROTECTED]:~$ dmesg | egrep -i '^ata|scsi'
SCSI subsystem initialized
ata_piix version 1.04
ata1: SATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x18C0 irq 14
ata1: dev 0 cfg 49:0f00 82:746b 83:5be8 84:4003 85:f46b 86:1848 87:4003 88:203f
ata1: dev 0 ATA, max UDMA/100, 117210240 sectors:
ata1(0): applying bridge limits
ata1: dev 0 configured for UDMA/100
scsi0 : ata_piix
  Type:   Direct-Access  ANSI SCSI revision: 05
ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x18C8 irq 15
ata2: dev 0 cfg 49:0f00 82: 83: 84: 85: 86: 87: 88:0407
ata2: dev 0 ATAPI, max UDMA/33
ata2(0): applying bridge limits
ata2: dev 0 configured for UDMA/33
scsi1 : ata_piix
SCSI device sda: 117210240 512-byte hdwr sectors (60012 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 117210240 512-byte hdwr sectors (60012 MB)
SCSI device sda: drive cache: write back
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0



[EMAIL PROTECTED]:~$ ll -d /dev/{s*,c*,d*}
crw---  1 root root   5, 1 2005-11-06 17:26 /dev/console
lrwxrwxrwx  1 root root 11 2005-11-06 17:26 /dev/core -> /proc/kcore
drwxr-xr-x  5 root root  0 2005-11-06 17:26 /dev/disk
drwxr-xr-x  2 root root  0 2005-11-06 17:26 /dev/dri
crw-rw  1 root audio 14, 3 2005-11-06 17:26 /dev/dsp
brw-rw  1 root disk   8, 0 2005-11-06 17:26 /dev/sda
brw-rw  1 root disk   8, 1 2005-11-06 17:26 /dev/sda1
brw-rw  1 root disk   8, 2 2005-11-06 17:26 /dev/sda2
drwxrwxrwt  2 root root 40 2005-11-06 17:26 /dev/shm
drwxr-xr-x  2 root root  0 2005-11-06 17:26 /dev/snd
lrwxrwxrwx  1 root root 24 2005-11-06 17:26 /dev/sndstat -> 
/proc/asound/oss/sndstat
lrwxrwxrwx  1 root root 15 2005-11-06 17:26 /dev/stderr -> /proc/self/fd/2
lrwxrwxrwx  1 root root 15 2005-11-06 17:26 /dev/stdin -> /proc/self/fd/0
lrwxrwxrwx  1 root root 15 2005-11-06 17:26 /dev/stdout -> /proc/self/fd/1



[EMAIL PROTECTED]:~$ cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA  Model: HTS726060M9AT00  Rev: MH4O
  Type:   Direct-AccessANSI SCSI revision: 05



[EMAIL PROTECTED]:/sys/class/scsi_device$ ll
total 0
drwxr-xr-x  2 root root 0 2005-11-06 17:26 0:0:0:0




[EMAIL PROTECTED]:/etc/mkinitramfs$ egrep -v '^#|^$' initramfs.conf
MODULES=dep
RESUME=/dev/sda2
BOOT=local
DEVICE=eth0
NFSROOT=auto



[EMAIL PROTECTED]:/etc/mkinitramfs$ egrep -v '^#|^$' modules
libata atapi_enabled=1
ahci
sd_mod
scsi_mod



-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
K

Bug#337988: bluez-utils: Please upload version built against new dbus to experimental

[Maik Zumstrull]

Package: bluez-utils
Severity: wishlist


A dbus transition is happening in experimental right now,
somewhat connected to the introduction of GNOME 2.12 into experimental.

bluez-* is uninstallable right now for me and everyone else with
experimental GNOME 2.12 packages installed.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#332247: Me too

[Maik Zumstrull]

I just ran into this one, too.

Same provider, same symptoms, newest linphone from unstable.

Did anyone who knows a little more about SIP than I do try to
protocol-trace what actually happens, here? Is GMX speaking broken SIP,
or is this a real linphone bug? If it's the first, could linphone be
"fixed", anyway?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#308915: Possible explanation

[Maik Zumstrull]

I believe this and similar problems are caused by websites embedding the
same content twice. In the original vendor plugins this leads to one
embed playing the video, one embed showing the control buttons.
mplayerplug-in, however, just treats the embeds the same and plays the
content twice.

This is probably fixed for the original reporter with vo=xv because his
video card has only one Xv port -- the problem isn't really fixed, but
the second player instance dies because it can't get an Xv port, so it
seems fixed.

This issue probably should be fixed upstream by allowing a seperate
embed for the control panel. (Or, as a workaround, by ignoring multiple
instances of the same content.)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#297821: --disable-checkpath: Not a security risk

[Maik Zumstrull]

> I don't think it's the best choice. Disable this is not a good idea
> for security reasons.

I disagree. A correctly configured php interpreter (meaning:

doc_root = "/var/www"
user_dir = "public_html"

in /etc/php4/cgi/php.ini) will perform the same check -- in the
sensible way: The script is executed if it is found in $DOCUMENT_ROOT or
in $HOME/$user_dir, whereas suphp insists on having the script in
$DOCUMENT_ROOT. Therefore, the added check in the suphp executable only
stops UserDir from working, but doesn't add any security since php
already checks the location of the script. I'm in favor of recompiling
suphp with --disable-checkpath -- in fact, that's what I did on my
system.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#309806: splashy: postinst should also look for grub in /boot/boot/grub

[Maik Zumstrull]

Package: splashy
Version: 0.1.3
Severity: normal
Tags: experimental

If /boot is a seperate filesystem, grub's menu.lst is in
/boot/boot/grub, not in /boot/grub. The postinst script should check both
locations.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-1-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages splashy depends on:
ii  libc6   2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  libdirectfb-0.9-20  0.9.20-5 frame buffer graphics library
ii  libglib2.0-02.6.4-1  The GLib library of C routines

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#307193: gnome-themes: Icon theme Flat-Blue: Missing size field

[Maik Zumstrull]

Package: gnome-themes
Version: 2.10.1-1
Severity: minor


I set the "Mist" theme using the theme manager.
It looks great, but most gnome/gtk applications show the following warning:

Gtk-WARNING **: Theme directory scalable/emblems of theme Flat-Blue has no size 
field

It's nothing serious, the theme works fine, but annoying when starting
applications from the console, especially when doing so with & -- messes up
the next prompt.


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.11-1-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages gnome-themes depends on:
ii  gtk2-engines-crux 1:2.6.1-1  the Crux theme engine for GTK+ 2.x
ii  gtk2-engines-lighthouseblue   1:2.6.1-1  LighthouseBlue theme for GTK+ 2.x
ii  gtk2-engines-mist 1:2.6.1-1  flat theme for GTK+ 2.x
ii  gtk2-engines-pixbuf   2.6.4-1Pixbuf-based theme for GTK+ 2.x
ii  gtk2-engines-redmond951:2.6.1-1  Windows-like theme for GTK+ 2.x
ii  gtk2-engines-smooth   0.6.0.1-3  Smooth Engine for GTK+ 2.x
ii  gtk2-engines-thinice  1:2.6.1-1  the ThinIce theme engine for GTK+ 

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#304232: kmail: Doesn't set Content-Type header in text part of Multipart/Mixed message

[Maik Zumstrull]

Package: kmail
Version: 4:3.3.2-3
Severity: normal

I just send out an eMail with an attachment and noticed that kMail doesn't
display the umlauts in the message correctly when viewing the mail in my
Sent folder. I looked at the source of the message, and the text
part doesn't have a Content-Type header. kMail has used UTF-8 encoding (as it
should), but didn't specify that in the message.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.11-1-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages kmail depends on:
ii  kdelibs4 4:3.3.2-4.0.2   KDE core libraries
ii  libc62.3.2.ds1-20GNU C Library: Shared libraries an
ii  libgcc1  1:3.4.3-12  GCC support library
ii  libice6  4.3.0.dfsg.1-12.0.1 Inter-Client Exchange library
ii  libkcal2a4:3.3.2-3   KDE calendaring library
ii  libkdenetwork2   4:3.3.2-3   KDE Network library
ii  libkdepim1   4:3.3.2-3   KDE PIM library
ii  libkleopatra0a   4:3.3.2-3   KDE GnuPG interface libraries
ii  libkpimidentities1   4:3.3.2-3   KDE PIM user identity information 
ii  libksieve0   4:3.3.2-3   KDE mail/news message filtering li
ii  libmimelib1a 4:3.3.2-3   KDE mime library
ii  libpng12-0   1.2.8rel-1  PNG library - runtime
ii  libqt3c102-mt3:3.3.4-2   Qt GUI Library (Threaded runtime v
ii  libsm6   4.3.0.dfsg.1-12.0.1 X Window System Session Management
ii  libstdc++5   1:3.3.5-12  The GNU Standard C++ Library v3
ii  libx11-6 4.3.0.dfsg.1-12.0.1 X Window System protocol client li
ii  libxext6 4.3.0.dfsg.1-12.0.1 X Window System miscellaneous exte
ii  perl 5.8.4-8 Larry Wall's Practical Extraction 
ii  xlibs4.3.0.dfsg.1-12 X Keyboard Extension (XKB) configu
ii  zlib1g   1:1.2.2-4   compression library - runtime

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#326226: wpasupplicant: WPA no longer works with recent madwifi snapshots

[Maik Zumstrull]

Package: wpasupplicant
Version: 0.4.2-1
Severity: important

Apparently, madwifi changed it's API.

I compiled wpasupplicant 0.4.4 from source against newer madiwifi headers
and it worked again.

I hope all the interface trouble will go away when Wireless Extensions 18
enter sid (with Linux 2.6.13). Please make sure to compile against those
as soon as a 2.6.13 kernel is in sid.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8)

Versions of packages wpasupplicant depends on:
ii  libc6 2.3.5-6GNU C Library: Shared libraries an
ii  libssl0.9.7   0.9.7g-1   SSL shared libraries

wpasupplicant recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#319755: Same problem here

[Maik Zumstrull]

I have the same symptoms here, on a Thinkpad T43p with
Kernel-image-2.6.11-1-686. The genrtc module is definitely loaded by the
initrd, as it is already present when booting with init=/bin/sh.

My mkinitrd config is attached.

I think at this point it would be prefereable to use rtc instead of
genrtc, as a lot of multimedia software uses /dev/rtc which genrtc
doesn't provide.
# /etc/mkinitrd/mkinitrd.conf:
#  Configuration file for mkinitrd(8).  See mkinitrd.conf(5).
#
# This file is meant to be parsed as a shell script.

# What modules to install.
MODULES=most

# The length (in seconds) of the startup delay during which linuxrc may be
# interrupted.
DELAY=0

# If this is set to probe mkinitrd will try to figure out what's needed to
# mount the root file system.  This is equivalent to the old PROBE=on setting.
ROOT=/dev/sda1

# This controls the permission of the resulting initrd image.
UMASK=022

# Command to generate the initrd image.
MKIMAGE='mkcramfs %s %s > /dev/null'

# Set this to yes if you want to use busybox(1).
BUSYBOX=no

# Set this to no if you want to disable /usr/share/initrd-tools/scripts.
PKGSCRIPTS=yes

# This is the value for LD_LIBRARY_PATH when deciding what goes onto the
# image.
INITRD_LD_LIBRARY_PATH=$LD_LIBRARY_PATH

# Hardcode partition to resume from so it doesn't have to be specified
# on the command line.  The command line will override this setting.
# RESUME=
# /etc/mkinitrd/modules: Kernel modules to load for initrd.
#
# This file should contain the names of kernel modules and their arguments
# (if any) that are needed to mount the root file system, one per line.
# Comments begin with a `#', and everything on the line after them are ignored.
#
# You must run mkinitrd(8) to effect this change.
#
# Examples:
#
#  ext2
#  wd io=0x300
ahci
libata
sd_mod
scsi_mod

Bug#403727: Dropouts have stopped

[Maik Zumstrull]

As of now, for no reason I can see, the dropouts have stopped.

I have neither changed my WPA and ifupdown configuration nor upgraded
directly related packages; but still, the problem is gone. I assume
this is due to some package update that seems unrelated, but somehow
isn't, like avahi-autoipd or dhclient3. Who knows?

With the maintainers blessing, I'm gonna give it another week or two
and if the problem stays gone, I'm gonna close this bug. If you insist
on closing it now, fine, but don't be surprised by a reopen if the
problem returns. :-)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#403190: misdn-modules-2.6.18-3-686: Freezes SMP systems

[Maik Zumstrull]

Package: misdn-modules-2.6.18-3-686
Severity: important

Any systems I have access to with more than one CPU(-core) immediately lock
up completely immediately after inserting mISDN_core. May or may not be
related to 
.
The symptoms there sound very similar.

Note: Makes no difference whether I use the precompiled modules or rebuild
with module-assistant, same results.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#267233: cdrecord: Only -dao and -sao accepted when using cuefile

[Maik Zumstrull]

reassign 267233 wodim
thanks

Joerg Schilling wrote:

> a lot of new features have been added to cdrtools during the past
> two years.

Yes, and I, for one, had completely forgotten about this request.

> RAW mode writing for the CDRWIN CUE file mode has been added recently
> and supports already nearly all sector types. Please test the latest
> cdrtools from:
> 
> ftp://ftp.berlios.de/pub/cdrecord/alpha/
> 
> and report whether your case is now working.

I don't have the file from back then around anymore; I'm not even sure
what it was. In fact, I don't have any bin/cue files around these days
to test this with.

I suggest that, if this feature has been added, you consider this
request "done" as far as cdrecord is concerned. I'm willing to just
assume that it works.

The feature has not yet been added to wodim, so this is where I'm
reassigning this one. (Developers, if you'd like this one closed
instead, fire away, I don't care enough to complain.)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#403727: Disconnects every few seconds on madwifi

[Maik Zumstrull]

Package: wpasupplicant
Version: 0.5.5-4

When using wpa_supplicant in roaming mode on current Debian madwifi
(see attachment: package-versions), the connection drops every thirty
seconds or so.

This behavior is completely reproducible and occurs on any networks I
have tested it with, among them:
- My university WLAN with WPA-EAP
- My home network with WPA-PSK
- My university WLAN without any encryption
- The network of a local cafe using WEP-40

Each test on the university network has been performed in different
buildings, which use compatible configurations, but completely
different hardware (LANCOM vs. Trapeze Networks; DHCP and Radius
servers are shared).

Where this is an option (i.e. the above networks without actual WPA), I
also tested using only the driver and ifupdown, without starting
wpa_supplicant. In this scenario, the dropouts do not occur.

Note: I am aware that madwifi should theoretically be usable with both
-Dmadwifi and -Dwext, and that the latter is actually the recommended
configuration. On my system, -Dwext doesn't work at all, any
association attempt fails. With -Dmadwifi, the network is usable (for
seconds at a time) with the dropouts this report is about.

Further attached information:
- The wpa_supplicant and ifupdown configuration files (shortened to
  relevant sections, with private information removed; access to full
  files can be granted via private mail if this is deemed necessary.)
- The output of a session of wpa_cli with debug level 0, time-stamped.
  I waited for several dropouts to occur before ending the session.
  The time-stamps appear to be pretty useless since wpa_cli seems to
  dump its output in big chunks at a time.

In the hope that I didn't just send this report and it turns out to be
a small dumb misconfiguration on my part,

Maik

etc-network-interfaces
Description: Binary data


package-versions
Description: Binary data
[EMAIL PROTECTED] ~/tmp/wpa_debug % wpa_cli -i ath0 2>&1 | ts
Dez 19 12:01:12 wpa_cli v0.5.5
Dez 19 12:01:12 Copyright (c) 2004-2006, Jouni Malinen <[EMAIL PROTECTED]> and contributors
Dez 19 12:01:12
Dez 19 12:01:12 This program is free software. You can distribute it and/or modify it
Dez 19 12:01:12 under the terms of the GNU General Public License version 2.
Dez 19 12:01:12
Dez 19 12:01:12 Alternatively, this software may be distributed under the terms of the
Dez 19 12:01:12 BSD license. See README and COPYING for more details.
Dez 19 12:01:12
Dez 19 12:01:12
Dez 19 12:01:12 Could not connect to wpa_supplicant - re-trying
Dez 19 12:01:12 Connection established.
Dez 19 12:01:12
Dez 19 12:01:12 Interactive mode
Dez 19 12:01:12
Dez 19 12:01:12 > level 0
Dez 19 12:01:12 OK
Dez 19 12:03:58 > <2>CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
Dez 19 12:03:58 <2>WPA: Key negotiation completed with 0e:0b:6b:30:17:5b [PTK=TKIP GTK=TKIP]
Dez 19 12:03:58 <1>Cancelling authentication timeout
Dez 19 12:03:58 <2>CTRL-EVENT-CONNECTED - Connection to 0e:0b:6b:30:17:5b completed (auth) [id=9 id_str=dukath]
Dez 19 12:03:58 <1>Setting scan request: 0 sec 10 usec
Dez 19 12:03:58 <2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Dez 19 12:03:58 <2>Trying to associate with 0e:0b:6b:30:17:5b (SSID='dukath-mbx' freq=2437 MHz)
Dez 19 12:03:58 <1>Cancelling scan request
Dez 19 12:03:58 <1>WPA: using IEEE 802.11i/D3.0
Dez 19 12:03:58 <1>WPA: using GTK TKIP
Dez 19 12:03:58 <1>WPA: using PTK TKIP
Dez 19 12:03:58 <1>WPA: using KEY_MGMT 802.1X
Dez 19 12:03:58 <2>Association request to the driver failed
Dez 19 12:03:58 <1>Setting authentication timeout: 5 sec 0 usec
Dez 19 12:03:58 <1>Associated to a new BSS: BSSID=0e:0b:6b:30:17:5b
Dez 19 12:03:58 <2>Associated with 0e:0b:6b:30:17:5b
Dez 19 12:03:58 <1>Setting authentication timeout: 10 sec 0 usec
Dez 19 12:03:58 <1>Cancelling scan request
Dez 19 12:03:58 <1>Setting authentication timeout: 70 sec 0 usec
Dez 19 12:03:58 <2>CTRL-EVENT-EAP-STARTED EAP authentication started
Dez 19 12:03:58 <2>CTRL-EVENT-EAP-METHOD EAP vendor 0 method 21 (TTLS) selected
Dez 19 12:03:58 <2>CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
Dez 19 12:03:58 <2>WPA: Key negotiation completed with 0e:0b:6b:30:17:5b [PTK=TKIP GTK=TKIP]
Dez 19 12:03:58 <1>Cancelling authentication timeout
Dez 19 12:03:58 <2>CTRL-EVENT-CONNECTED - Connection to 0e:0b:6b:30:17:5b completed (reauth) [id=9 id_str=dukath]
Dez 19 12:03:58 <1>Setting scan request: 0 sec 10 usec
Dez 19 12:03:58 <2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Dez 19 12:03:58 <2>Trying to associate with 0e:0b:6b:30:17:5b (SSID='dukath-mbx' freq=2437 MHz)
Dez 19 12:03:58 <1>Cancelling scan request
Dez 19 12:03:58 <1>WPA: using IEEE 802.11i/D3.0
Dez 19 12:03:58 <1>WPA: using GTK TKIP
Dez 19 12:03:58 <1>WPA: using PTK TKIP
Dez 19 12:03:58 <1>WPA: using KEY_MGMT 802.1X
Dez 19 12:03:58 <2>Association request to the driver failed
Dez 19 12:03:58 <1>Setting authentication timeout: 5 sec 0 usec
Dez 19 12:03:58 <1>Associated to a new BSS:

Bug#403727: [pkg-wpa-devel] Bug#403727: Disconnects every few seconds on madwifi

[Maik Zumstrull]

Kel Modderman wrote:

> > Where this is an option (i.e. the above networks without actual
> > WPA), I also tested using only the driver and ifupdown, without
> > starting wpa_supplicant. In this scenario, the dropouts do not
> > occur.
> 
> Dropouts do not occur? Or dropouts are not "noticed" because
> ifup/ifdown is not called when the driver borks? The roaming setup
> you use is very sensitive to driver stability, or lack of. Using
> static ifupdown stanzas on the other hand is quite insensitive to
> transient dropouts.

Good question. I'll recheck right now (I'm on the university WLAN
without wpa_supplicant).

> Is it your opinion that these transient lapses in operation _only_
> occur in conjunction with wpa_supplicant?

Yes, I feel 99% sure.

I have looked carefully at a "watch iwconfig" and didn't see it switch
to Non-Associated even once over a few minutes -- with wpa_supplicant,
the connection would have dropped about five times in that time period.

Also, the vpnc VPN client I'm using on top of the link is extremely
sensitive to packet loss and should have frozen up on any dropout, even
if ifupdown isn't called. It didn't.

Of course, none of these actually guarantee that there were no
mini-dropouts. Is there a way to get a complete log of any
(dis)association from the driver? That way I could give you a
definitive answer.

> Do you experience any momentary pauses in operation when not using
> wpa_supplcant?

No.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#400337: ifplugd: Should deal with mounted remote filesystems (NFS/SMB/CIFS)

[Maik Zumstrull]

Package: ifplugd
Version: 0.28-2
Severity: normal

On shutdown, ifplugd takes down the network before remote filesystems
are unmounted, leading to a long hang in the shutdown process (the unmount
has to time out).

The quick fix is to change the order scripts are run in, i.e. keep the
interfaces up until remote file systems have been unmounted.

For a more complete solution, ifplugd should also handle remote file systems
during normal operation: If the cable is pulled, it should check if any
file servers with mounted file systems became unreachable due to this and
do a lazy/forced unmount of these systems, so that requests onto these
systems can fail instead of hanging.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages ifplugd depends on:
ii  debconf [debconf-2.0]1.5.9   Debian configuration management sy
ii  libc62.3.6.ds1-8 GNU C Library: Shared libraries
ii  libdaemon0   0.10-1  lightweight C library for daemons

Versions of packages ifplugd recommends:
ii  ifupdown  0.6.8  high level tools to configure netw

-- debconf information:
* ifplugd/interfaces: eth0
* ifplugd/hotplug_interfaces:
* ifplugd/args: -f -u2 -d10 -w -I
* ifplugd/suspend_action: stop


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#401205: flpsed: New version available: 0.3.9

[Maik Zumstrull]

Package: flpsed
Version: 0.3.7-1
Severity: normal

This is a parallel release to the 0.4 line that does not require FLTK2,
but does fix some of the same bugs, among them #398906. The new version
should also work with both Ghostscripts currently in Debian, gs-esp and gs-gpl.

Assigning "normal" instead of "wishlist" because making flpsed work regardless
of what /usr/bin/gs currently points to seems more important that "wishlist";
downgrade if you disagree.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages flpsed depends on:
ii  libc62.3.6.ds1-8 GNU C Library: Shared libraries
ii  libfltk1.1   1.1.7-2 Fast Light Toolkit shared librarie
ii  libgcc1  1:4.1.1-20  GCC support library
ii  libstdc++6   4.1.1-20The GNU Standard C++ Library v3
ii  libx11-6 2:1.0.3-4   X11 client-side library

flpsed recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#416063: initramfs-tools: MODULES=most does *not* include all framebuffer modules

[Maik Zumstrull]

Package: initramfs-tools
Version: 0.85f
Severity: normal

First, my configuration:
[EMAIL PROTECTED] /tmp/user/1000 % sed 's/#.*$//;/^[[:space:]]*$/d' 
/etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
BOOT=local
DEVICE=eth0
NFSROOT=auto

(You might want to add that command as a reportbug-hook, btw.)

According to the comment in initramfs.conf-as-shipped, which reads

# MODULES: [ most | netboot | dep | list ]
#
# most - Add all framebuffer, acpi, filesystem, and harddrive drivers.

a newly-built initramfs image should contain all framebuffer drivers. However,
when actually building the image as follows, this is not the case:

[EMAIL PROTECTED] /tmp/user/1000 % sudo update-initramfs -v -k all -ct &> 
initramfs-tools.log

--- BEGIN initramfs-tools.log ---
Available versions:  2.6.18-4-686 2.6.18-3-686 2.6.18-2-686 2.6.18-1-686 
2.6.17-2-686
Execute: /usr/sbin/update-initramfs -c -k "2.6.18-4-686" -b /boot -v -t
update-initramfs: Generating /boot/initrd.img-2.6.18-4-686
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/usb/core/usbcore.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/usb/host/ehci-hcd.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/usb/host/ohci-hcd.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/usb/host/uhci-hcd.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/usb/input/usbhid.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/ide/ide-core.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/scsi/scsi_mod.ko
Adding module 
/lib/modules/2.6.18-4-686/kernel/drivers/usb/storage/usb-storage.ko
Adding module /lib/modules/2.6.18-4-686/kernel/fs/mbcache.ko
Adding module /lib/modules/2.6.18-4-686/kernel/fs/ext2/ext2.ko
Adding module /lib/modules/2.6.18-4-686/kernel/fs/jbd/jbd.ko
Adding module /lib/modules/2.6.18-4-686/kernel/fs/ext3/ext3.ko
Adding module /lib/modules/2.6.18-4-686/kernel/fs/isofs/isofs.ko
Adding module /lib/modules/2.6.18-4-686/kernel/fs/jfs/jfs.ko
Adding module /lib/modules/2.6.18-4-686/kernel/net/sunrpc/sunrpc.ko
Adding module /lib/modules/2.6.18-4-686/kernel/fs/nfs_common/nfs_acl.ko
Adding module /lib/modules/2.6.18-4-686/kernel/fs/lockd/lockd.ko
Adding module /lib/modules/2.6.18-4-686/kernel/fs/nfs/nfs.ko
Adding module /lib/modules/2.6.18-4-686/kernel/fs/reiserfs/reiserfs.ko
Adding module /lib/modules/2.6.18-4-686/kernel/fs/xfs/xfs.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/mii.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/3c59x.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/8139cp.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/8139too.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/8390.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/b44.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/bnx2.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/defxx.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/dl2k.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/e1000/e1000.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/e100.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/epic100.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/eql.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/fealnx.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/forcedeth.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/hp100.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/base/firmware_class.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/myri10ge/myri10ge.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/natsemi.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/ne2k-pci.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/netconsole.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/ns83820.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/pcnet32.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/r8169.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/s2io.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/sis900.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/skge.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/slhc.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/starfire.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/sundance.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/sungem_phy.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/sungem.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/sunhme.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/tg3.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/tlan.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/tulip/de2104x.ko
Adding module /lib/modules/2.6.18-4-686/kernel/drivers/net/tulip/de4x5.ko
Adding module /lib/modules/2.6.18-4-686/kernel/driv

Bug#416063: Proposed Patch

[Maik Zumstrull]

tags 416063 patch
thanks

This is another way to get the FB modules included that does not
require adding or changing hook scripts.--- hook-functions	2007-03-24 18:31:05.0 +0100
+++ hook-functions.withfb	2007-03-24 19:02:39.0 +0100
@@ -171,6 +171,14 @@
 			manual_add_modules "${x}"
 		done
 	;;
+	fb)
+		for x in arcfb aty128fb atyfb radeonfb cirrusfb cyber2000fb cyblafb \
+		gx1fb gxfb hgafb i810fb intelfb kyrofb matroxfb_base matroxfb_maven \
+		neofb nvidiafb pm2fb s1d13xxxfb savagefb sisfb sstfb tdfxfb tridentfb \
+		vfb; do
+			manual_add_modules "${x}"
+		done
+	;;
 	ide)
 		for x in ide-cd ide-disk ide-generic aec62xx alim15x3 \
 		amd74xx atiixp atuuxo cmd64x cs5520 cs5530 cy82c693 \
@@ -219,6 +227,7 @@
 	*)
 		auto_add_modules base
 		auto_add_modules net
+		auto_add_modules fb
 		auto_add_modules ide
 		auto_add_modules scsi
 		auto_add_modules ata

Bug#416063: Revised Patch

[Maik Zumstrull]

After further experimentation, I discovered additional problems that my
first patch did not address, namely that

1) Some FB drivers need the AGP subsystem up and running before they
   are loaded and
2) intelfb needs intel-agp.ko, but does not have a dependency on it.

This version of the patch includes all AGP modules in the initramfs
image in addition to the framebuffer modules, and includes a workaround
for intelfb's buggy dependencies.

intelfb does not actually *work* on my testsystem after this (it
crashes), but unlike with plain initramfs-tools, it loads (and prints
something useful if loaded with the probeonly option). I'll try to find
out why it fails to work tomorrow; it's probably an unrelated issue.diff -ru initramfs-tools.old/hook-functions initramfs-tools.new/hook-functions
--- initramfs-tools.old/hook-functions	2007-03-24 23:44:01.0 +0100
+++ initramfs-tools.new/hook-functions	2007-03-24 23:39:50.0 +0100
@@ -171,6 +171,15 @@
 			manual_add_modules "${x}"
 		done
 	;;
+	fb)
+		for x in arcfb aty128fb atyfb radeonfb cirrusfb cyber2000fb cyblafb \
+		gx1fb gxfb hgafb i810fb intelfb kyrofb matroxfb_base matroxfb_maven \
+		neofb nvidiafb pm2fb s1d13xxxfb savagefb sisfb sstfb tdfxfb tridentfb \
+		vfb ali-agp amd64-agp amd-k7-agp ati-agp efficeon-agp intel-agp \
+		nvidia-agp sis-agp sworks-agp via-agp; do
+			manual_add_modules "${x}"
+		done
+	;;
 	ide)
 		for x in ide-cd ide-disk ide-generic aec62xx alim15x3 \
 		amd74xx atiixp atuuxo cmd64x cs5520 cs5530 cy82c693 \
@@ -219,6 +228,7 @@
 	*)
 		auto_add_modules base
 		auto_add_modules net
+		auto_add_modules fb
 		auto_add_modules ide
 		auto_add_modules scsi
 		auto_add_modules ata
diff -ru initramfs-tools.old/scripts/init-top/framebuffer initramfs-tools.new/scripts/init-top/framebuffer
--- initramfs-tools.old/scripts/init-top/framebuffer	2007-03-24 23:44:01.0 +0100
+++ initramfs-tools.new/scripts/init-top/framebuffer	2007-03-24 23:39:50.0 +0100
@@ -76,11 +76,17 @@
 	esac
 done
 
-# Map command line name to module name
+# Module-specific workarounds
 case ${FB} in
 matroxfb)
+	# Needs a different module name
 	FB=matroxfb_base
 	;;
+intelfb|i810fb)
+	# Needs a special AGP driver, even though the module does
+	# not specify a dependency on it
+	modprobe -q intel-agp
+	;;
 *)
 	;;
 esac

Bug#403190: Works with mISDN 1.1.0

[Maik Zumstrull]

tags 403190 fixed-upstream
thanks

I recently tried this with mISDN 1.1.0 upstream source and the module
compiles, loads and works just fine. No hangs, no crashes.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#418580: New version available

[Maik Zumstrull]

Package: hellanzb
Version: 0.12
Severity: normal

hellanzb 0.13 has been released on March 26th, 2007.

Severity normal instead of wishlist because this fixes a bad hang
condition (invalid CRC on received yEnc part throws an unhandled
exception, hellanzb hangs forever, needs to be killed), adjust if
necessary.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#418581: Please use accelerated decoding module

[Maik Zumstrull]

Package: hellanzb
Severity: wishlist

hellanzb supports a yEnc decoding module written in C (instead of pure
python) to accelerate decoding. Please provide this module, either as
part of hellanzb or (preferably) as an external python package with
hellanzb having a Recommends: on it.

See: 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#383352: locales-all: Should call localedef with --replace on postinst

[Maik Zumstrull]

Package: locales-all
Version: 2.3.6-19
Severity: normal

The postinst script currently contains the command:

localedef --add-to-archive "$tmpdir"/*

This should be changed to:

localedef --replace --add-to-archive "$tmpdir"/*

Otherwise, updates of locales-all will fail because, as documented,
"Without this option, if the locale is in the archive file already,
an error occurs.", i.e. the postinst script fails. The original line of course
works fine on first installs of locales-all, when no locale files are
installed yet.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages locales-all depends on:
ii  libc6 [glibc-2.3.6-2] 2.3.6-19   GNU C Library: Shared libraries

locales-all recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#600280: XKBOPTIONS="compose:rwin" doesn't propagate to X

[Maik Zumstrull]

Julien Pinon wrote:

> Le mardi 23 novembre 2010 à 21:40,
> Cyril Brulebois  écrivait :
> 
> > If you feel like getting this fixed, find the actual culprit (on the
> > gnome side, as suggested by Julien), and reassign it there.
> 
> I digged a little  bit, and found that maybe the problem  is the same
> as #590534, and linked to
> https://bugzilla.gnome.org/show_bug.cgi?id=613681

Sounds plausible.

> Knowing if the bug appears only while using gdm3 would help.

I am using gdm3. I think I tried going into a session without going
through gdm and had the same problem. If you'd like me to test something
in a specific way, let me know.

> Anyway, don't you think that the bug is a real one even if not
> belonging to  xserver-xorg-input-keyboard,  and  that  Maik who
> reported  it  (in keyboard-configuration package) was let without
> answer and without hope ?

Thank you for noticing. Since I have a viable workaround (set the same
keyboard layout and options in GNOME as in keyboard-configuration), I
had decided not to reopen and bitch about aggressive bug-closing this
time and just let it go.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#605246: Built-in 3G modem can prevent sleep mode

[Maik Zumstrull]

Package: eeepc-acpi-scripts
Version: 1.1.11

On the EeePC 1005HAG, the builtin 3G modem (12d1:1001 Huawei
Technologies Co., Ltd. E620 USB Modem) prevents the device from
staying in sleep mode. It goes to sleep fine, according to the logs,
but immediately wakes up. I suspected that the 3G modem is causing
this, because it seems to work for the models without built-in 3G,
according to various reports out there.

I tried putting the device to sleep after telling the kernel to ignore
USB wakeup requests from the 3G modem, and it works, apparently
without nasty side effects, the 3G still works after. I think
eeepc-acpi-scripts should include a sleep.d hook to do this. It's not
enough to set this once at boot, the flag resets itself when returning
from sleep mode. I've attached my own quick-hack attempt at doing
this, feel free to use it, use it as a template, or discard it and
write your own.


80_3Gmodem
Description: Binary data

Bug#605246: [Debian-eeepc-devel] Bug#605246: Built-in 3G modem can prevent sleep mode

[Maik Zumstrull]

>> I tried putting the device to sleep after telling the kernel to ignore
>> USB wakeup requests from the 3G modem, and it works, apparently
>> without nasty side effects, the 3G still works after. I think
>> eeepc-acpi-scripts should include a sleep.d hook to do this.

> A better solution would be to see if this is fixed upstream, and if so,
> backport the fix for the kernel in Squeeze. Would you please try the
> kernel in experimental to see if the problem is resolved there?

Okay, I installed the linux-image-2.6.36-trunk-686-bigmem package
(plus linux-base) and moved my sleep.d hook out of the way. Then I
shut down completely and booted into the new kernel.

The system does stay asleep, so that's fixed. However, after waking
up, the system freezes for a few seconds several times. I didn't see
that with 2.6.32 and hook-disabled wakeup. This seems to go away after
a while, it could be one freeze for each USB device while rebinding it
or something. There are reproducibly (I tested three times) four
freezes, and there are four USB-devices other than root hubs.
According to "gnokii --monitor once", the 3G device came back up and
registered with the network.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#605246: [Debian-eeepc-devel] Bug#605246: Built-in 3G modem can prevent sleep mode

[Maik Zumstrull]

> Please can you test whether the attached patch fixes our package of
> Linux 2.6.32.  You will need to rebuild the kernel package by following
> the instructions at
> .

On it.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#605246: [Debian-eeepc-devel] Bug#605246: Built-in 3G modem can prevent sleep mode

[Maik Zumstrull]

> Please can you test whether the attached patch fixes our package of
> Linux 2.6.32.

The system goes to sleep and doesn't immediately wake up. Good. There
are no freezes as in #605275. Wifi comes back up. 3G needs to be left
alone for a moment (immediate "gnokii --monitor once" fails), but does
come back (second attempt usually works).



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#605275: EeePC 1005HAG freezes briefly after resuming

[Maik Zumstrull]

> Well there's nothing obvious there but it looks like the wifi driver
> takes some time to start up again after resuming.  Could you test
> whether this happens if you disable wifi before suspending?

Doesn't help, the freezes are still there. I used the Fn+F2 shortcut
to disconnect. That leaves the wifi-related modules loaded. I then
tried again after rmmoding all wifi-related modules I could find.
Still freezes.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#605275: EeePC 1005HAG freezes briefly after resuming

[Maik Zumstrull]

> Please report
> this upstream at  under product 'Drivers',
> component 'USB'.  Let us know the bug number or URL so we can track it.

Reported as:




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#689753: linux-image-3.5-trunk-amd64: Please support /boot being vfat, or another way of having the kernel on the EFI system partition

[Maik Zumstrull]

Package: src:linux
Version: 3.5.5-1~experimental.1
Severity: normal

Call me a masochist, but I've been using UEFI boot on systems new enough
to support it. For this, it makes sense to have the kernel and initrd
images on the EFI system partition.

It's not an absolute requirement. One could have grub on the system
partition, and have grub read the kernel off whatever filesystem it's on.

However, as far as I can tell, the direction the boot process is going
is for the kernel to be an EFI executable. No boot loader in the
oldschool sense, just something to select which kernel to run and pass a
command line.

To simply run the kernel as an EFI application, two requirements:
- The kernel image has to be compiled as an EFI executable. Recent
  Debian kernel images are.
- The kernel image has to be on a file system EFI can read. That doesn't
  necessarily mean the system partition, but it does mean vfat.

Now, in linux-image-* packages, the kernel image is simply a file in
/boot. If /boot is the EFI system partition, dpkg will fail to update
the package, because dpkg assumes file systems have hard link support.

When this issue came up back in 2008, it was decided to just accept this
dpkg limitation and officially require /boot to be a POSIX file system.
I suggest to revisit this decision in the context of UEFI boot.

How best to implement this depends on the preferred way of mounting the
system partition. Arguably, the system partition should be /boot, since
that's the point. In that case, one could ship the kernel image beneath
/lib in the package and copy it to /boot from postinst.

Another popular option is to have /boot on the root file system and the
system partition on /boot/efi. In that case, it would be fine to leave
the kernel image in the package as it is now, but the package should
offer to always keep copies of the kernel and the initrd in /boot/efi.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#684767: kernel: missing support for Ivy Bridge GT2 Server

[Maik Zumstrull]

On Sun, Sep 30, 2012 at 1:52 AM, Jonathan Nieder  wrote:
> Hi Maik,
>
> Maik Zumstrull wrote:
>
>> This is on an Ivy Bridge Xeon E3 with GPU.
> [...]
>> 3.2 crashes as well, but not as hard as 3.4. With 3.2, X doesn't come
>> up, but you can switch to a console and reboot.
>
> Sorry for the slow reply.  Please test the attached patch, for example
> using the following instructions.

With those instructions and with the patch, 3.2.30 can bring up i915
KMS. Without the patch, it cannot. Seems to hit the spot.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#694481: opensc: Lacks support for ePass2003 USB token

[Maik Zumstrull]

Package: opensc
Version: 0.12.2-3
Severity: normal


Upstream apparently has this (epass2003.profile), please upload a build
with this support included as soon as it's convenient.

Thanks,

Maik


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#684650: libdrm-intel1: X dies hard on Ivy Bridge GT2 Server graphics

[Maik Zumstrull]

Package: libdrm-intel1
Version: 2.4.33-3
Severity: important

If X is started with this libdrm on a machine with "Ivy Bridge GT2
Server" Intel graphics, it crashes and leaves the machine in an almost
unusable state (network/ssh might remain up). X is certainly completely
unusable, as it won't start.

Please package a version >= 2.4.34 or backport the patches mentioned in
this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=53222

Other related reports:
https://bugzilla.redhat.com/show_bug.cgi?id=840180
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683167

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5-trunk-amd64 (SMP w/4 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 libdrm-intel1 depends on:
ii  libc6  2.13-33
ii  libdrm22.4.33-3
ii  libpciaccess0  0.13.1-2
ii  multiarch-support  2.13-33

libdrm-intel1 recommends no packages.

libdrm-intel1 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#684650: libdrm-intel1: X dies hard on Ivy Bridge GT2 Server graphics

[Maik Zumstrull]

On Sat, Aug 18, 2012 at 6:35 PM, Julien Cristau  wrote:

>> Please package a version >= 2.4.34 or backport the patches mentioned in
>> this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=53222

> Why did you file a duplicate then?

I felt a separate bug against libdrm was more appropriate. Jonathan
disagreed, obviously. Feel free to merge/unmerge/reassign/whatever as
you see fit.

FYI, I finished rebuilding the package with the patch that adds the
PCI ID minutes ago, and I have somewhat working X with intel driver
now. OpenGL seems to work, VA-API doesn't, but that may again be a
problem with outdated versions. I can't use the full resolution of the
display, not sure why. Maybe the DVI port on the board isn't dual
link.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#683167: linux-image-3.4-trunk-amd64: Attempting to start X with intel driver hangs system

[Maik Zumstrull]

Package: src
Version: 3.4.4-1~experimental.1
Severity: important

This is on an Ivy Bridge Xeon E3 with GPU. I thought it was the X
driver, because i915 KMS works fine for the console, it only crashes
when trying to bring up X. But I pulled in the 2.20.2 driver today and
it still happens. So I now think the problem is in the kernel.

It's entirely possible this is fixed in 3.5, which I will test as soon
as it hits experimental.

3.2 crashes as well, but not as hard as 3.4. With 3.2, X doesn't come
up, but you can switch to a console and reboot. 3.4 needs the reset
button.

-- Package-specific info:
** Version:
Linux version 3.4-trunk-amd64 (Debian 3.4.4-1~experimental.1) 
(debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP 
Tue Jun 26 17:23:03 UTC 2012

** Command line:
BOOT_IMAGE=/vmlinuz-3.4-trunk-amd64 root=/dev/mapper/luks-root ro quiet

** Not tainted

** Kernel log:
[   43.319002] Monitor-Mwait will be used to enter C-3 state
[   43.319016] ACPI: acpi_idle registered with cpuidle
[   43.323450] iTCO_vendor_support: vendor-support=0
[   43.324345] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07
[   43.324409] iTCO_wdt: Found a Panther Point TCO device (Version=2, 
TCOBASE=0x0460)
[   43.324449] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   43.329003] ACPI Warning: 0xf040-0xf05f SystemIO 
conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20120320/utaddress-251)
[   43.329008] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   43.344385] wmi: Mapper loaded
[   43.344513] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
[   43.344826] ACPI: Power Button [PWRF]
[   43.345309] Bluetooth: Core ver 2.16
[   43.345318] NET: Registered protocol family 31
[   43.345319] Bluetooth: HCI device and connection manager initialized
[   43.345321] Bluetooth: HCI socket layer initialized
[   43.345322] Bluetooth: L2CAP socket layer initialized
[   43.345325] Bluetooth: SCO socket layer initialized
[   43.347792] input: PC Speaker as /devices/platform/pcspkr/input/input7
[   43.348878] Linux media interface: v0.10
[   43.349854] usbcore: registered new interface driver btusb
[   43.349925] microcode: CPU0 sig=0x306a9, pf=0x2, revision=0x10
[   43.351137] Linux video capture interface: v2.00
[   43.352848] snd_hda_intel :00:1b.0: enabling device ( -> 0002)
[   43.352902] snd_hda_intel :00:1b.0: irq 55 for MSI/MSI-X
[   43.354422] uvcvideo: Found UVC 1.00 device  (046d:081d)
[   43.366279] usb 4-1.6.1: input irq status -75 received
[   43.367115] input: UVC Camera (046d:081d) as 
/devices/pci:00/:00:1d.0/usb4/4-1/4-1.7/4-1.7:1.2/input/input8
[   43.367167] usbcore: registered new interface driver uvcvideo
[   43.367168] USB Video Class driver (1.1.1)
[   43.371842] asus_wmi: ASUS WMI generic driver loaded
[   43.372554] asus_wmi: Initialization: 0x0
[   43.372568] asus_wmi: BIOS WMI version: 0.9
[   43.372592] asus_wmi: SFUN value: 0x0
[   43.372755] input: Eee PC WMI hotkeys as 
/devices/platform/eeepc-wmi/input/input9
[   43.373301] asus_wmi: Backlight controlled by ACPI video driver
[   43.373916] microcode: CPU1 sig=0x306a9, pf=0x2, revision=0x10
[   43.375110] microcode: CPU2 sig=0x306a9, pf=0x2, revision=0x10
[   43.376077] microcode: CPU3 sig=0x306a9, pf=0x2, revision=0x10
[   43.377564] microcode: Microcode Update Driver: v2.00 
, Peter Oruba
[   43.381261] usbcore: registered new interface driver snd-usb-audio
[   43.390225] usb 4-1.6.1: input irq status -75 received
[   43.402028] input: HDA Intel PCH Line as 
/devices/pci:00/:00:1b.0/sound/card0/input10
[   43.402110] input: HDA Intel PCH Front Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input11
[   43.402165] input: HDA Intel PCH Rear Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input12
[   43.402201] input: HDA Intel PCH Front Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input13
[   43.402235] input: HDA Intel PCH Line Out Side as 
/devices/pci:00/:00:1b.0/sound/card0/input14
[   43.402276] input: HDA Intel PCH Line Out CLFE as 
/devices/pci:00/:00:1b.0/sound/card0/input15
[   43.402344] input: HDA Intel PCH Line Out Surround as 
/devices/pci:00/:00:1b.0/sound/card0/input16
[   43.402436] input: HDA Intel PCH Line Out Front as 
/devices/pci:00/:00:1b.0/sound/card0/input17
[   46.841151] XFS (sde2): Mounting Filesystem
[   47.759356] XFS (sde2): Ending clean mount
[   47.828292] FAT-fs (sde1): utf8 is not a recommended IO charset for FAT 
filesystems, filesystem will be case sensitive!
[   47.846638] XFS (dm-8): Mounting Filesystem
[   48.029741] XFS (dm-8): Ending clean mount
[   48.053466] XFS (dm-9): Mounting Filesystem
[   48.167516] XFS (dm-9): Ending clean mount
[   48.178220] XFS (dm-7): Mounting Filesystem
[   48.521452] XFS (dm-7): Ending clean mount
[   49.793502] Bridge firewalling registered
[   49.795766] device eth0 entered pr

Bug#683558: s3cmd: Please cherrypick upstream bugfix

[Maik Zumstrull]

Package: s3cmd
Version: 1.1.0~beta3-1
Severity: normal

Upstream issue: https://github.com/s3tools/s3cmd/issues/24
Upstream fix: 
https://github.com/s3tools/s3cmd/commit/9c57a3ba2163915deb2cc63cefa885a66ac377ab

This prevents using s3cmd sync in a cronjob. Upstream has unfortunately
not cut a release that includes this fix, maybe ask them to do so.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.4-trunk-amd64 (SMP w/4 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 s3cmd depends on:
ii  python  2.7.3-2

s3cmd recommends no packages.

s3cmd 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#683167: Also in 3.5

[Maik Zumstrull]

Now running linux-image-3.5-trunk-amd64 (3.5-1~experimental.1). Still happens.

Note that while I suspect the kernel, I'm in no position to rule out
the X driver. Feel free to loop them in.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#683167: Attempting to start X with intel driver hangs system

[Maik Zumstrull]

On Fri, Aug 3, 2012 at 9:01 PM, Jonathan Nieder  wrote:

> Does the squeeze 2.6.32.y kernel reproduce the same trouble?  (It should run
> fine on a wheezy/sid system.)  Could you retrieve full "dmesg" output
> from the 3.2.y failure?

2.6.32 has never heard of this GPU, so the i915 module doesn't
initialize. The X server exits immediately, saying no device was
found, but doesn't crash. The kernel panics on trying to reboot, but
the stack trace shows a bunch of EFI-related functions, so it's
probably unrelated.

But let's make a note that yes, I installed with EFI boot, which is
probably a lot less tested than legacy BIOS boot. I haven't tried if
it is happier with BIOS boot, I could do that tomorrow if you think
it's important.

3.2 behavior is now similar: i915.ko doesn't know the GPU, and X just
exits because i915 isn't there. My last tests were with a 2.19 X
driver, presumably the update to 2.20 made the 3.2 crash go away.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#683167: Attempting to start X with intel driver hangs system

[Maik Zumstrull]

On Sat, Aug 4, 2012 at 10:04 AM, Jonathan Nieder  wrote:

> Can you get a trace of the crash using a serial console[1] or
> netconsole[2]?

I got netconsole working, and some messages came through (I replugged
a USB device to trigger some), but nothing when it crashes. I don't
have the cabling here for serial (it's only a pinheader on this
board), but I could get it next week if that's what it takes.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#683167: Attempting to start X with intel driver hangs system

[Maik Zumstrull]

On Sat, Aug 4, 2012 at 10:27 PM, Jonathan Nieder  wrote:

> Please attach a full log from netconsole from booting and
> reproducing the problem.  (It's ok if it doesn't say anything
> interesting at the crucial moment.)

Done.

> If you can get the corresponding Xorg log, that would be interesting,
> too.

It doesn't seem to get around to writing one. The existing file was
for a session with the vesa driver.


netconsole.txt.bz2
Description: BZip2 compressed data

Bug#683167: Attempting to start X with intel driver hangs system

[Maik Zumstrull]

On Mon, Aug 6, 2012 at 2:39 AM, Jonathan Nieder  wrote:

> One more test and then we should take this upstream: does a boot
> without attempting to start X work ok?  Do you get a working
> framebuffer console?

Yes, that works fine.

> Either way, please report this upstream following instructions from
>
>   http://intellinuxgraphics.org/how_to_report_bug.html
>
> and let us know the bug number so we can track it.

https://bugs.freedesktop.org/show_bug.cgi?id=53222

> The upstream maintainers will want a kernel log with the boot option
> 'drm.debug=0x0e' appended

Their doc says 0x06? Either way, will do that tomorrow or so.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#700975: RAID is still barely usable

[Maik Zumstrull]

Any way to get some attention on this bug? Unless I'm missing
something, it seems to make a fairly major feature (md) nearly
unusable (for me), with issues of potential data loss.

Maybe my hardware is just too exotic? But as far as I can tell, this
is a popular AHCI chip, and those are popular disks.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#700975: Marvell 88SE9230: Freaks out and drops all disks if sent SMART command during RAID rebuild

[Maik Zumstrull]

On Thu, Apr 4, 2013 at 9:34 PM, Jonathan Nieder  wrote:

> Please send a summary of symptoms to linux-r...@vger.kernel.org,
> cc-ing either me or this bug log so we can track it.

Will do. FWIW I think the underlying issue is likely in the SATA code,
with RAID just providing the tons of background I/O load needed to
trigger the issue. But I'm happy to start on that end.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#700975: RAID barely usable on my home machine

[Maik Zumstrull]

Hello Linux RAID and ATA people,

I've managed to find a configuration on my home desktop where a
particular RAID array is barely usable.

You can find my initial report at:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700975

In summary:

- I create an array across four disks on a Marvell AHCI controller,
which automatically goes into rebuild mode.
- Somebody (e.g. smartd or udisks2 or me, testing) sends a SMART
command to one of the disks.
- The SMART command fails.
- The ATA subsystems freaks out all over the place, until eventually
none of the disks on that controller are responsive.
- The array is dead until reboot. (Curiously, without data loss so
far. Kudos on the RAID code, I guess.)

I've found the issue to be highly reproducible so far. Things mostly
work if the array is not under heavy load (not rebuilding, no big file
copies going on) or I make completely sure nothing sends SMART
commands. I currently do keep real files on that array, but backed-up
ones, so I could wipe it for more tests if really necessary.

I've tried various kernels from Debian (3.2, 3.7, and 3.8 series) and
found them all affected.

Here are some edited excerpts from the kernel log messages as found in
the Debian bug, see unedited transcript there.

Getting our RAID on:

[  122.707833] md127: detected capacity change from 0 to 9001374842880
[  122.707860] RAID conf printout:
[  122.707865]  --- level:5 rd:4 wd:3
[  122.707868]  disk 0, o:1, dev:sde
[  122.707870]  disk 1, o:1, dev:sdf
[  122.707872]  disk 2, o:1, dev:sdg
[  122.707873]  disk 3, o:1, dev:sdh
[  122.707965] md: recovery of RAID array md127
[  122.707968] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
[  122.707970] md: using maximum available idle IO bandwidth (but not
more than 20 KB/sec) for recovery.
[  122.707973] md: using 128k window, over a total of 2930135040k.

We see a SMART we don't like:

[  180.531641] ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[  180.531648] ata9.00: failed command: SMART
[  180.531655] ata9.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in
[  180.531655]  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask
0x4 (timeout)
[  180.531658] ata9.00: status: { DRDY }

Woops, a non-critical command failed? Best shoot the controller in the
face until it stops twitching:

[  180.531666] ata9: hard resetting link
[  185.887433] ata9: link is slow to respond, please be patient (ready=0)
[  190.524871] ata9: COMRESET failed (errno=-16)
[  190.524877] ata9: hard resetting link
[  195.872694] ata9: link is slow to respond, please be patient (ready=0)
[  200.510134] ata9: COMRESET failed (errno=-16)
[  200.510141] ata9: hard resetting link
[  205.857925] ata9: link is slow to respond, please be patient (ready=0)
[  235.470518] ata9: COMRESET failed (errno=-16)
[  235.470526] ata9: limiting SATA link speed to 3.0 Gbps
[  235.470529] ata9: hard resetting link
[  240.483102] ata9: COMRESET failed (errno=-16)
[  240.483110] ata9: reset failed, giving up
[  240.483112] ata9.00: disabled
[  240.483134] ata9: EH complete

So now other stuff goes wrong:

[  301.216814] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[  301.216818] ata7.00: failed command: FLUSH CACHE EXT
[  301.216821] ata7.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[  301.216821]  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask
0x4 (timeout)
[  301.216822] ata7.00: status: { DRDY }
[  301.216827] ata7: hard resetting link
[  301.216842] ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[  301.216845] ata10.00: failed command: FLUSH CACHE EXT
[  301.216849] ata10.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[  301.216849]  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask
0x4 (timeout)
[  301.216851] ata10.00: status: { DRDY }
[  301.216855] ata10: hard resetting link
[  301.216861] ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[  301.216864] ata8.00: failed command: FLUSH CACHE EXT
[  301.216868] ata8.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[  301.216868]  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask
0x4 (timeout)
[  301.216870] ata8.00: status: { DRDY }

Until eventually, the patient's dead…so let's report success:

[  351.917459] md/raid:md127: Disk failure on sde, disabling device.
[  351.917459] md/raid:md127: Operation continuing on 0 devices.
[  351.921299] md: md127: recovery done.

This is on a cheapo PCIe extension board with four internal SATA3
ports. Chip is a "Marvell Technology Group Ltd. 88SE9230 PCIe SATA
6Gb/s Controller [1b4b:9230]" using the ahci driver.

It would be really good to see this fixed. I see two issues:
- That SMART command probably shouldn't fail. Weird drive firmware?
Timeout too tight?
- A failing SMART command should probably not trigger a breakdown of
the whole controller. At least, not such a messy one.

I'll make myself available, as time allows, to provide requested
additional information.


--
To UNSUBSCRIBE

Bug#700975: RAID barely usable on my home machine

[Maik Zumstrull]

On Fri, Apr 5, 2013 at 2:16 AM, Roger Heflin  wrote:

> lspci look like this for the controller:
> SATA controller: Marvell Technology Group Ltd. Device 9230 (rev 10)
>
> 4pt sata3.0 6gbit or is yours a different one?

Mine looks slightly different (included somewhere in my mail), but
should be a device in the same family.

> I have the issue also, I have eliminated all smart hits against the
> disks and no incidents since then.

Not a great workaround as such, first of all, running SMART against
your storage is kind of recommended, and secondly, as I said, udisks2
will also SMART your disks occasionally, which you have to uninstall
parts of GNOME to get rid of.

> I have seagate 1.5tb drives on mine that had had the issues.

Suggests it's not something about my drives, as I have WD Red disks.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#700975: RAID barely usable on my home machine

[Maik Zumstrull]

On Fri, Apr 5, 2013 at 10:23 AM, Robin Hill  wrote:
> On Thu Apr 04, 2013 at 10:13:05 +0200, Maik Zumstrull wrote:

>> I've managed to find a configuration on my home desktop where a
>> particular RAID array is barely usable.

> I used to have the same issues on one of my machines. The solution was
> to buy a decent SAS/SATA HBA (I went with the Intel RS2WC080, but see
> http://blog.zorinaq.com/?e=10 for a more complete list), which now works
> perfectly with exactly the same drives as before.

Calling that a "solution" seems generous, but since it doesn't look
like this'll get fixed any time soon, I decided to go the same way and
just ordered LSI SAS 9211-8i.

Thanks for the list, that seems like a very useful resource.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#671305: New dracut version 026 available

[Maik Zumstrull]

On Mon, Mar 25, 2013 at 2:12 PM, Thomas Lange
 wrote:
> I just uploaded dracut_026+71+g78d1d4f-1. Could you please test if
> your problem is fixed in this version.

Nope.

- Didn't boot at all at first (I suspect non-dracut issue, fixed by power off)
- Didn't activate md devices on its own
- cryptsetup hangs the same way

This is on new hw btw, the old system I reported from is gone.
Apparently the issue isn't hardware specific.

Thanks for following up.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#700975: linux-image-3.7-trunk-amd64: Marvell 88SE9230: Freaks out and drops all disks if sent SMART command during RAID rebuild

[Maik Zumstrull]

Package: src:linux
Version: 3.7.8-1~experimental.1
Severity: normal

Subject says most of it. These are new components: PCIe card with that
Marvell chip, 4 exposed SATA 6G ports, one WD Red 3TB on each port.
Disks are fine according to SMART conveyance test.

Console action:

maik@antares:~/ > sudo mdadm -C linux-data -n 4 -l 5 /dev/sde /dev/sdf /dev/sdg 
/dev/sdh
mdadm: /dev/sde appears to be part of a raid array:
level=raid5 devices=4 ctime=Tue Feb 19 22:47:42 2013
mdadm: /dev/sdf appears to be part of a raid array:
level=raid5 devices=4 ctime=Tue Feb 19 22:47:42 2013
mdadm: /dev/sdg appears to be part of a raid array:
level=raid5 devices=4 ctime=Tue Feb 19 22:47:42 2013
mdadm: /dev/sdh appears to be part of a raid array:
level=raid5 devices=4 ctime=Tue Feb 19 22:47:42 2013
Continue creating array? y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md/linux-data started.
maik@antares:~/ > cat /proc/mdstat 
Personalities : [raid6] [raid5] [raid4] 
md127 : active raid5 sdh[4] sdg[2] sdf[1] sde[0]
  8790405120 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/3] [UUU_]
  [>]  recovery =  0.0% (679936/2930135040) 
finish=574.4min speed=84992K/sec
  
unused devices: 
maik@antares:~/ > sudo smartctl -H /dev/sdg
smartctl 5.43 2012-06-05 r3561 [x86_64-linux-3.7-trunk-amd64] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

maik@antares:~/ > sudo smartctl -H /dev/sdg
smartctl 5.43 2012-06-05 r3561 [x86_64-linux-3.7-trunk-amd64] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

maik@antares:~/ > sudo smartctl -H /dev/sdg
smartctl 5.43 2012-06-05 r3561 [x86_64-linux-3.7-trunk-amd64] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

Error SMART Thresholds Read failed: scsi error aborted command
Smartctl: SMART Read Thresholds failed.

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.


I've extended the kernel log below so it covers everything from the
moment of RAID creation, including the failing SMART command.

The problem seems fairly repeatable, so far every attempt at creating a
RAID has failed this way (because smartd eventually pings the disks).


-- Package-specific info:
** Version:
Linux version 3.7-trunk-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.7.2 (Debian 4.7.2-5) ) #1 SMP Debian 3.7.8-1~experimental.1

** Command line:
BOOT_IMAGE=/vmlinuz-3.7-trunk-amd64 
root=UUID=06cc1c4c-d190-49bb-9219-0ccfa22e2661 ro acpi_os=Linux quiet

** Tainted: PO (4097)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.

** Kernel log:
[  122.445618] md: bind
[  122.445783] md: bind
[  122.445952] md: bind
[  122.456452] md: bind
[  122.459351] async_tx: api initialized (async)
[  122.460092] xor: automatically using best checksumming function:
[  122.499742]avx   : 11990.000 MB/sec
[  122.567597] raid6: sse2x14318 MB/s
[  122.635438] raid6: sse2x25419 MB/s
[  122.703278] raid6: sse2x46137 MB/s
[  122.703280] raid6: using algorithm sse2x4 (6137 MB/s)
[  122.703282] raid6: using ssse3x2 recovery algorithm
[  122.706977] md: raid6 personality registered for level 6
[  122.706981] md: raid5 personality registered for level 5
[  122.706983] md: raid4 personality registered for level 4
[  122.707309] md/raid:md127: device sdg operational as raid disk 2
[  122.707312] md/raid:md127: device sdf operational as raid disk 1
[  122.707314] md/raid:md127: device sde operational as raid disk 0
[  122.707711] md/raid:md127: allocated 4338kB
[  122.707797] md/raid:md127: raid level 5 active with 3 out of 4 devices, 
algorithm 2
[  122.707799] RAID conf printout:
[  122.707801]  --- level:5 rd:4 wd:3
[  122.707803]  disk 0, o:1, dev:sde
[  122.707805]  disk 1, o:1, dev:sdf
[  122.707806]  disk 2, o:1, dev:sdg
[  122.707833] md127: detected capacity change from 0 to 9001374842880
[  122.707860] RAID conf printout:
[  122.707865]  --- level:5 rd:4 wd:3
[  122.707868]  disk 0, o:1, dev:sde
[  122.707870]  disk 1, o:1, dev:sdf
[  122.707872]  disk 2, o:1, dev:sdg
[  122.707873]  disk 3, o:1, dev:sdh
[  122.707965] md: recovery of RAID array md127
[  122.707968] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
[  122.707970] md: using maximum available idle IO bandwidth (but not more than 
20 KB/sec) for recovery.
[  122.707973] md: using 128k window, over a total of 2930135040k.
[  122.740153]  md127: unknown partition table
[  180.531641] ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[  180.531648] ata9.00: failed command: SMART
[  180.531655] ata9.00: cmd b0/d1:01:01:4f:c2/00:00:00:

Bug#700975: Happens with wheezy kernel

[Maik Zumstrull]

Tried building an array with linux-image-3.2.0-4-amd64 / 3.2.35-2, same issue.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#700975: Also happens on 3.8

[Maik Zumstrull]

Just tried with 3.8.2, fresh from experimental.

Bug#629290: unbound: Forwarding doesn't work if the target nameserver is broken

[Maik Zumstrull]

Package: unbound
Version: 1.4.10-1
Severity: normal

I've noticed this on my home router, which has a fairly fresh dnsmasq.
Apparently, unbound can't resolve through this and just SERVFAILs for
everything. Obviously, this is primarily a problem in dnsmasq (I
assume). But since dnsmasq is in tons of home routers and unbound uses
forwarding by default in Debian, I think it's important to have a
workaround in place.

I think a good solution would be for unbound to detect when it can't
reliably resolve through one of the forwarding hosts and stop using
it, falling back to normal recursion if they all end up being dropped.
Ideally, this would happen before the user experiences lookup failures,
for example by immediately resolving a bunch of well-known hosts after
adding new forwarders, so that they will already be dropped with a high
probability if they are broken.

Until this type of workaround is in place, I would suggest disabling
resolvconf forwarders by default, or putting out a clear warning "This
might kill your DNS, stop the unbound daemon if you can't resolve
anything anymore."



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#630145: xserver-xorg-core: Segfault with Intel KMS on Asus netbook

[Maik Zumstrull]

Package: xserver-xorg-core
Version: 2:1.10.2-1
Severity: important

Happens reliably on every startup, not on intermittent problem.

This is a very recent development. I suspect either the new kernel or
the new libc.

-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Nov 13  2010 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 201 May 30 14:10 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME 
Express Integrated Graphics Controller [8086:27ae] (rev 03)

Xorg X server configuration file status:

-rw-r--r-- 1 root root 95 Feb 28 14:30 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
---
Section "Device"
Identifier  "IntelOnboard"
Driver  "intel"
Option  "XvMC" "true"
EndSection

/etc/X11/xorg.conf.d does not exist.

KMS configuration files:

/etc/modprobe.d/i915-kms.conf:
  options i915 modeset=1

Kernel version (/proc/version):
---
Linux version 2.6.39-2-686-pae (Debian 2.6.39-2) (b...@decadent.org.uk) (gcc 
version 4.4.6 (Debian 4.4.6-3) ) #1 SMP Wed Jun 8 11:33:14 UTC 2011

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 35506 Jun 10 22:55 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[40.473] 
X.Org X Server 1.10.1
Release Date: 2011-04-15
[40.473] X Protocol Version 11, Revision 0
[40.474] Build Operating System: Linux 2.6.32-5-686-bigmem i686 Debian
[40.474] Current Operating System: Linux errai 2.6.39-1-686-pae #1 SMP Fri 
May 20 20:40:05 UTC 2011 i686
[40.474] Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.39-1-686-pae 
root=/dev/mapper/croot ro elevator=deadline acpi_osi=Linux splash quiet
[40.474] Build Date: 01 May 2011  10:14:44AM
[40.474] xorg-server 2:1.10.1-2 (Julien Cristau ) 
[40.474] Current version of pixman: 0.21.8
[40.474]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[40.475] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[40.475] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jun 10 17:53:46 
2011
[40.562] (==) Using config file: "/etc/X11/xorg.conf"
[40.562] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[40.600] (==) No Layout section.  Using the first Screen section.
[40.600] (==) No screen section available. Using defaults.
[40.600] (**) |-->Screen "Default Screen Section" (0)
[40.600] (**) |   |-->Monitor ""
[40.601] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[40.601] (**) |   |-->Device "IntelOnboard"
[40.601] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[40.601] (==) Automatically adding devices
[40.601] (==) Automatically enabling devices
[40.721] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[40.721]Entry deleted from font path.
[40.721] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[40.721]Entry deleted from font path.
[40.721] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[40.721]Entry deleted from font path.
[40.828] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[40.828]Entry deleted from font path.
[40.828] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[40.828]Entry deleted from font path.
[40.958] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
built-ins
[40.959] (==) ModulePath set to "/usr/lib/xorg/modules"
[40.959] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[40.959] (II) Loader magic: 0x8232ac0
[40.959] (II) Module ABI versions:
[40.959]X.Org ANSI C Emulation: 0.4
[40.959]X.Org Video Driver: 10.0
[40.959]X.Org XInput driver : 12.2
[40.960]X.Org Server Extension : 5.0
[40.963] (--) PCI:*(0:0:2:0) 8086:27ae:1043:8340 rev 3, Mem @ 
0xf7e0/524288, 0xd000/268435456, 0xf7dc/262144, I/O @ 0xdc00/8
[40.964] (--) PCI: (0:0:2:1) 8086:27a6:1043:8340 rev 3, Mem @ 
0xf7e8/524288
[40.965] (II) Open ACPI successful (/var/run/acpid.socket)
[40.965] (II) LoadModule: "extmod"
[40.968] (II) Load

Bug#630145: Problem gone

[Maik Zumstrull]

The problem has fixed itself with today's updates.

It can't have been the kernel or libc after all, neither was in this
round of updates.

Anyway, feel free to close, unless you still want to isolate the cause.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#671305: (no subject)

[Maik Zumstrull]

On Thu, Oct 10, 2013 at 12:10 PM, Thomas Lange
 wrote:
> Please try the newest dracut version (034-1 atm.) and setting rd.auto=1.

Cryptsetup no longer hangs. Some weirdness handing over to init, which
tries to unlock a device again that dracut already unlocked. But the
issue of this bug seems to be gone.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#605275: EeePC 1005HAG freezes briefly after resuming

[Maik Zumstrull]

On Wed, Feb 22, 2012 at 22:59, Jonathan Nieder  wrote:

> Maik Zumstrull wrote:
>
>> Reported as:
>> <https://bugzilla.kernel.org/show_bug.cgi?id=23962>
>
> Thanks.  Apparently Greg doesn't like the bugzilla interface.  Since
> there has been some BTM elimination work upstream, could you try 3.2
> or newer from unstable?

I tried just a minute ago (the device is next to me) when I saw Greg's
mail, on Debian 3.2. It still happens. That was 3.2.4-1, I will reboot
into 3.2.6-1 and retry. You will loop in linux-usb afterwards?



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#605275: EeePC 1005HAG freezes briefly after resuming

[Maik Zumstrull]

On Wed, Feb 22, 2012 at 23:03, Maik Zumstrull  wrote:

> I tried just a minute ago (the device is next to me) when I saw Greg's
> mail, on Debian 3.2. It still happens. That was 3.2.4-1, I will reboot
> into 3.2.6-1 and retry.

Also happens on 3.2.6-1.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#605275: EeePC 1005HAG still freezes when probing the builtin 3G modem

[Maik Zumstrull]

On Sun, Feb 26, 2012 at 18:07, Greg KH  wrote:
> On Sun, Feb 26, 2012 at 05:38:46PM +0100, Maik Zumstrull wrote:

> I don't see any long delay in your kernel log messages.

The problem isn't visible in dmesg AFAIK. I was asked to include this
output in the report just in case. It's visible in strace (attached to
Bugzilla, can take a fresh trace if you'd like), and to the user
because the whole system ignores user input during the freeze.

> What exactly is stalling so long?

When someone previously looked at the issue with me, the delay seemed
to be in acquiring the big TTY lock.

> Is the device stuck doing something?

Not as far as I know.

> If you enable debugging for usb and/or the driver, what does the kernel
> log show?

I don't think we've done that yet. Quick pointer on how to do this?
I'm reasonably experienced, but not a kernel developer. Just pass
debug=1 to certain modules?

> What driver is bound to this device, the option one?

Yes. The drivers symlink points to bus/usb/drivers/option, anyway, I
hope that's what you meant.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#605275: EeePC 1005HAG still freezes when probing the builtin 3G modem

[Maik Zumstrull]

On Sun, Feb 26, 2012 at 18:57, Greg KH  wrote:
> On Sun, Feb 26, 2012 at 06:35:43PM +0100, Maik Zumstrull wrote:

>> > Is the device stuck doing something?
>>
>> Not as far as I know.
>
> Are two userspace programs trying to access the device at the same time?

The device exports three virtual serial ports. ModemManager accesses
more than one. On the other hand, we were able to reproduce the freeze
accessing only one port from one process, see Bugzilla.

I've attached a fresh strace of opening the device on 3.2.6. The
open() takes 10s, the close takes 5s. Nothing else was accessing any
ttyUSB*; I killed ModemManager and double checked with lsof.

> Yes.  Please try loading the module with:
>        modprobe option debug=1
> and seeing what happens in the kernel log when you open the device.

Output attached. I think it's three "option_send_setup" for one
open()/close(). At least, that's what happens with the C snippet.


kern.log.bz2
Description: BZip2 compressed data


ttytest.strace
Description: Binary data

Bug#605275: EeePC 1005HAG still freezes when probing the builtin 3G modem

[Maik Zumstrull]

On Mon, Feb 27, 2012 at 16:33, Dan Williams  wrote:

> Ah, yeah, that would make sense.  Does this happen for *all* ports on
> the modem, or only a few ports?

Patched the C snippet to open/close all three. Looks like ttyUSB0 is
fine, 1 and 2 hang.
#include 
#include 
#include 
#include 

int main(void)
{
	int fd = -1;
	fd = open("/dev/ttyUSB0", O_RDWR | O_EXCL | O_NOCTTY | O_NONBLOCK);
	close(fd);
	fd = open("/dev/ttyUSB1", O_RDWR | O_EXCL | O_NOCTTY | O_NONBLOCK);
	close(fd);
	fd = open("/dev/ttyUSB2", O_RDWR | O_EXCL | O_NOCTTY | O_NONBLOCK);
	close(fd);
	return 0;
}


ttytest.strace
Description: Binary data

Bug#605275: EeePC 1005HAG still freezes when probing the builtin 3G modem

[Maik Zumstrull]

On Mon, Feb 27, 2012 at 17:19, Dan Williams  wrote:

> Any chance you can get the Windows driver installer for this device?

Weirdly, ASUS doesn't offer it for download. I wiped the included
Windows first thing.

> Looking at the INF files gives us clues as to what the ports are used
> for.  Also, I'd expect at least *two* AT capable ports on a GSM/UMTS
> device, but perhaps only one on a CDMA/EVDO device.  Is this an EM770
> (CDMA/EVDO) or a GSM/UMTS device?

GSM/UMTS

>  Also, again is there any way you can
> get the device model name and firmware version from ATI/AT+GMM/AT+GMR ?

Manufacturer: huawei
Model: EM770
Revision: 11.108.04.01.40
IMEI: [Removed]
+GCAP: +CGSM,+DS,+ES

OK

EM770

OK

11.108.04.01.40



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#605275: EeePC 1005HAG still freezes when probing the builtin 3G modem

[Maik Zumstrull]

On Mon, Feb 27, 2012 at 16:15, Dan Williams  wrote:

> What device is this?

Some kind of embedded Huawei USB thing. lsusb was in my first mail to
the list, don't have the netbook next to me right now.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#605275: EeePC 1005HAG still freezes when probing the builtin 3G modem

[Maik Zumstrull]

On Tue, Feb 28, 2012 at 06:09, Dan Williams  wrote:

> Notes I'd seen from another driver indicate that it's got a modem/PPP
> port (intf 0), a DIAG/DM port (intf 1 or 2) and the PCUI port (intf 1 or
> 2).  At least the PCUI port should be able to respond to AT commands
> too.  Can you talk on ttyUSB1 or ttyUSB2 with AT commands?
>
> Try "AT^GETPORTMODE" on any port that takes AT commands and see what you
> get.

ttyUSB0 acts like a modem. That it opens instantly holds with picocom
as well, the other ones hang for a bit.
ttyUSB1 doesn't seem to take AT commands (no response).
ttyUSB2 takes AT commands.

Both AT-capable ports reply "COMMAND NOT SUPPORT" [sic] to AT^GETPORTMODE.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#605275: EeePC 1005HAG still freezes when probing the builtin 3G modem

[Maik Zumstrull]

On Tue, Feb 28, 2012 at 19:19, Dan Williams  wrote:
> On Tue, 2012-02-28 at 11:14 +0100, Maik Zumstrull wrote:

>> ttyUSB0 acts like a modem. That it opens instantly holds with picocom
>> as well, the other ones hang for a bit.
>> ttyUSB1 doesn't seem to take AT commands (no response).
>> ttyUSB2 takes AT commands.
>>
>> Both AT-capable ports reply "COMMAND NOT SUPPORT" [sic] to AT^GETPORTMODE.
>
> But ttyUSB2 still has the close() blocking problem while ttyUSB0 does
> not?

Yes. ttyUSB2 has the same functionality as 0 and the same timing issues as 1.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#664487: xvba-va-driver: Needs to make the multiarch move

[Maik Zumstrull]

Package: xvba-va-driver
Version: 0.8.0-3
Severity: important

With the recent libva update, xvba-va-driver no longer works by default,
because libva looks for drivers in a multiarch path now. Workaround:
LIBVA_DRIVERS_PATH=/usr/lib/dri
LIBVA_DRIVER_NAME=xvba

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (300, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 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 xvba-va-driver depends on:
ii  libc6 2.13-27
ii  libgl1-mesa-glx [libgl1]  7.11.2-1
ii  libx11-6  2:1.4.4-4
ii  libxext6  2:1.3.0-3
ii  libxvbaw1 1:12-2-2

xvba-va-driver recommends no packages.

xvba-va-driver 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#671305: (no subject)

[Maik Zumstrull]

On Sat, May 26, 2012 at 9:20 AM, Thomas Lange
 wrote:
> I wonder why this does not work, since the xts kernel modules should
> be included. Please call dracut -v and check if the xts module in not
> loaded into the initramfs.

I can confirm that

- dracut attempts to ship the xts module:
D: Installing /lib/modules/3.2.0-2-amd64/kernel/crypto/xts.ko
- the file ends up in the actual image:
-rw-r--r--   1 root root 7144 May 21 20:47
lib/modules/3.2.0-2-amd64/kernel/crypto/xts.ko

I'm not using XTS on my volumes. So this exactly couldn't be my issue anyway.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#646130: parted staleness

[Maik Zumstrull]

How about creating a separate parted3 package, if parted 2.x will be
needed by d-i for the foreseeable future?



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#671305: dracut: cryptsetup just hangs, making the system unbootable

[Maik Zumstrull]

Package: dracut
Version: 018+32+geb6e141-1

So, I had a bit of a bad experience yesterday evening. :-)

I switched from initramfs-tools to dracut 18, because I like the idea
of dracut, and I had successfully used dracut 17. But after reboot and
entering a LUKS password, nothing happened.

I rebooted and added [rd.luks=0 rd.shell] to the kernel command line.
Trying to open any LUKS device manually showed the same behavior: it
just hangs. No reaction to SIGINT. SIGQUIT gets rid of the cryptsetup
process. At that point, a /dev/dm-? node has shown up, but doesn't
work yet, and none of the symlinks are there.

I reverted the machine to initramfs-tools for now.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#818116: Broken fix

[Maik Zumstrull]

reopen 818116
thanks

You replaced "grep" with "grep | true" which not only fixes the return code but 
also eats the output. The intention was probably to use "grep || true".

The package now prints
/var/lib/dpkg/info/uwsgi-plugin-python.postinst: 61: [: Illegal number:

during install (but no longer totally fails to install).

Bug#823530: In favor of keeping the limit

[Maik Zumstrull]

In my opinion, the bugs here are in different packages:

- Packages that provide a way for users to log in to the system, but
don't create a user slice
- Packages that provide services that operate using an unreasonable
number of processes or threads, and can't be bothered to declare as
much in the unit file

The 512 limit is arbitrary, but a plausible point at which to say, if
this isn't an interactive session and the service has not declared
special needs, I should assume it's malfunctioning / fork bombing and
shut it down.

For comparison, RabbitMQ installations also regularly run into the
"1024 open file descriptors" limit, but instead of abolishing that
limit globally, it's been documented that the limit may need to be
raised specifically for RabbitMQ for high-load installations.

Regarding the user slice thing, maybe systemd should consider
depending on libpam-systemd. It's currently quite easy to not install
on custom installations, and not having user slices should break a
number of things. (It's pulled in by ubuntu-standard on Ubuntu, but
people like to remove that because it pulls in things of questionable
usefulness.)

Bug#823530: systemd 228 reduced maximum number of tasks in a cgroup to 512 by default

[Maik Zumstrull]

On Sat, May 7, 2016 at 1:25 PM, Santiago Vila  wrote:

> I'm using a hand-made autobuilder which is triggered by cron, asks a
> server for a package to build and uses sbuild to build the package.
> Should I override this for the cron service only?

cron probably shouldn't be running the actual jobs in its own service
scope, applying its own process limits to the jobs.

As long as cron does, you can try adding
https://www.freedesktop.org/software/systemd/man/systemd-run.html to
your job invocation, as in
systemd-run --scope -p TasksMax=infinity your-original-command --your
--original --args

Bug#822341: steam:i386: steam-devices package was not built

[Maik Zumstrull]

Package: steam
Version: 1.0.0.52-1
Severity: normal

With the last upload (1.0.0.51-1), you added a steam-devices package
that installs udev rules for some Valve hardware like the Steam
Controller. It appears with the current version, this package was not
built or at least didn't end up in the archive:

http://ftp.debian.org/debian/pool/non-free/s/steam/

I'm not sure what went wrong, as I still see steam-devices referenced in
the source package. But it's not there in the final build.

Bug#801869: nvidia-graphics-drivers: setting /dev/nvidia* to root:video 0660 breaks gdm3, sddm, ...

[Maik Zumstrull]

On Thu, 15 Oct 2015 15:14:39 +0200 Andreas Beckmann  wrote:

> For local users logging into X a session-based membership in the video
> group is handled automatically via some consolekit magic (in
> nvidia-kernel-common).

I believe consolekit is deprecated, has this magic been ported to
systemd-logind?

If it has, I don't think it's working quite right - I had to put both
Debian-gdm and my personal account into the video group permanently to
get a GNOME session just now. No magic happening. Consolekit isn't
installed, nothing in the GNOME area seems to depend on it anymore.

Bug#814321: Maybe not totally useless?

[Maik Zumstrull]

reopen 814321
thanks

Dropping this dependency led to one of my machines uninstalling
tex-common, which then made dpkg error out:

# dpkg --configure -a
Setting up fonts-lmodern (2.004.5-2) ...
/var/lib/dpkg/info/fonts-lmodern.postinst: 17:
/var/lib/dpkg/info/fonts-lmodern.postinst: update-texmf-config: not
found
dpkg: error processing package fonts-lmodern (--configure):
 subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
 fonts-lmodern

So I think it either should depend on tex-common after all, or
shouldn't attempt to call update-texmf-config unless tex-common
happens to be there.

Bug#849963: tigervnc-standalone-server: Syntax error in /usr/bin/tigervncserver

[Maik Zumstrull]

Package: tigervnc-standalone-server
Version: 1.7.0-2
Severity: normal


In line 705, in the code path for the -fg option, the script does:

system $cmd[0] (@cmd);

This will lead to a "Can't use string as a subroutine ref" error with
current Perl releases. The correct syntax is

system { $cmd[0] } (@cmd);

or

system { $cmd[0] } @cmd;

The final parentheses are optional but not harmful. The braces are very
not optional. In defense of the author, the Perl documentation for
"system" doesn't indicate this at all; it's in the documentation for the
related "exec" function.

Bug#831390: static global variables are not thread safe

[Maik Zumstrull]

Package: libnss-extrausers
Version: 0.6-3

The implementation uses three static global pointer variables:

static FILE *groupsfile = NULL;
static FILE *shadowfile = NULL;
static FILE *usersfile = NULL;

Since these are used without locks or atomic operations, this is not 
thread-safe, even though NSS functions are supposed to be reentrant. This is 
leading to occasional "double free or corruption" crashes in libvirtd for us, 
specifically in fclose(groupsfile); in _nss_extrausers_endgrent.

As a quick fix, I suggest declaring these variables thread-local:

static __thread FILE *groupsfile = NULL;
static __thread FILE *shadowfile = NULL;
static __thread FILE *usersfile = NULL;

It's not necessarily the most elegant solution, but it should make the code 
fully reentrant.

Bug#831390: static global variables are not thread safe

[Maik Zumstrull]

On 15 Jul 2016, at 15:49, Daniel Kahn Gillmor  wrote:
> 
> On Fri 2016-07-15 14:19:51 +0200, Maik Zumstrull wrote:

>> As a quick fix, I suggest declaring these variables thread-local:
>> 
>> static __thread FILE *groupsfile = NULL;
>> static __thread FILE *shadowfile = NULL;
>> static __thread FILE *usersfile = NULL;
>> 
>> It's not necessarily the most elegant solution, but it should make the code 
>> fully reentrant.
> 
> Are you sure this wouldn't cause the different thread's understanding of
> the underlying file descriptors to get out of sync?  declaring them
> thread-local wouldn't prevent them sharing the same file descriptor,
> right?

It should. The semantics are that every thread "sees" its own version of that 
pointer, so if thread A opens the file, thread B, C, D, etc will still have 
NULL in their version of the variable and will do groupsfile = 
fopen(GROUPSFILE, "r"); which should create a new FILE structure and open a new 
file descriptor, whether any other thread has the file open or not.

That's why I called the solution inelegant - it's not efficient to open the 
file seven times if seven threads want something - but it should be safe 
because nothing is shared between threads.

> This seems like a way to cause some even more subtle bug, for example:
> 
> thread A causes libnss-extrausers to scan the groups file for some
>value, and it reads up to block X, while
> thread B causes libnss-extrausers to scan the groups file for some
>other value, and it reads up to block Y
> 
> then thread A resumes; the underlying file descriptor is advanced to
> position Y but the FILE* buffers in thread A have only cached enough
> data to represent block X.  what happens then?

That's the situation we have now, because everything from the FILE pointer to 
the FILE struct down to the file descriptor is currently shared.

Bug#428404: New (beta) version available

[Maik Zumstrull]

Package: flashplugin-nonfree
Version: 9.0.31.0.4
Severity: wishlist

According to 
, "Flash 
Player Update 3 Beta 1 (build 9.0.60.120) is now ready for download."

The build contains interesting new features such as XEmbed support and 
HW-scaled fullscreen video. However, it is marked as "beta" and is 
already known to introduce incompatiblities to several major browsers, 
though Iceweasel should work. I suggest an upload to experimental.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#468578: gedit: Should have a mode suitable for EDITOR/VISUAL environment variables

[Maik Zumstrull]

Package: gedit
Version: 2.20.4-1
Severity: wishlist

Currently, the gedit binary's behaviour when called when an instance of gedit
ist already open is the following:

1) Files named on the command line open as new tabs in the existing instance
2) The new instance exits

This is problematic for most utilities using an external text editor, because
they usually

1) call $EDITOR and
2) wait for that process to exit and
3) assume that you are now finished editing the file(s).

Obviously, when EDITOR=gedit, there's a good chance that you haven't even
started editing.

Therefore, I suggest that gedit should have an additional mode specifically
for use as $EDITOR, in which the new gedit process stays open (sleeping, if
necessary) until all files mentioned on the command line have been closed in
whatever gedit instance they are being edited in.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (110, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gedit depends on:
ii  gconf2 2.20.1-3  GNOME configuration database syste
ii  gedit-common   2.20.4-1  official text editor of the GNOME 
ii  iso-codes  1.9-1 ISO language, territory, currency,
ii  libart-2.0-2   2.3.20-1  Library of functions for 2D graphi
ii  libatk1.0-01.20.0-1  The ATK accessibility toolkit
ii  libattr1   1:2.4.41-1Extended attribute shared library
ii  libc6  2.7-9 GNU C Library: Shared libraries
ii  libenchant1c2a 1.3.0-5   a wrapper library for various spel
ii  libgconf2-42.20.1-3  GNOME configuration database syste
ii  libglade2-01:2.6.2-1 library to load .glade files at ru
ii  libglib2.0-0   2.14.6-1  The GLib library of C routines
ii  libgnome2-02.20.1.1-1The GNOME 2 library - runtime file
ii  libgnomecanvas2-0  2.20.1.1-1A powerful object-oriented display
ii  libgnomeprint2.2-0 2.18.4-1  The GNOME 2.2 print architecture -
ii  libgnomeprintui2.2-0   2.18.2-1  GNOME 2.2 print architecture User 
ii  libgnomeui-0   2.20.1.1-1The GNOME 2 libraries (User Interf
ii  libgnomevfs2-0 1:2.20.1-2GNOME Virtual File System (runtime
ii  libgtk2.0-02.12.8-1  The GTK+ graphical user interface 
ii  libgtksourceview2.0-0  2.0.2-1   shared libraries for the GTK+ synt
ii  libpango1.0-0  1.18.4-1  Layout and rendering of internatio
ii  libx11-6   2:1.0.3-7 X11 client-side library
ii  libxml22.6.31.dfsg-1 GNOME XML library
ii  python 2.4.4-6   An interactive high-level object-o
ii  python-glade2  2.12.1-1  GTK+ bindings: Glade support
ii  python-gobject 2.14.1-2  Python bindings for the GObject li
ii  python-gtk22.12.1-1  Python bindings for the GTK+ widge
ii  python-gtksourceview2  2.0.0-1   Python bindings for the GtkSourceV
ii  python-support 0.7.6 automated rebuilding support for p
ii  python2.4  2.4.4-7   An interactive high-level object-o
ii  scrollkeeper   0.3.14-16 A free electronic cataloging syste

Versions of packages gedit recommends:
ii  libgnomevfs2-bin  1:2.20.1-2 GNOME Virtual File System (support
ii  python-gnome2 2.20.1-2   Python bindings for the GNOME desk
ii  zenity2.20.1-1   Display graphical dialog boxes fro

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#453066: BlueZ Audio Service

[Maik Zumstrull]

Any chance this could be fast-tracked somewhat?

Among other things, this activates the new (to Debian) BlueZ Audio
Service (for headsets), which I've been waiting for for some time now.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#377845: renameutils: imv does not have large file support

[Maik Zumstrull]

Package: renameutils
Version: 0.8.1-3
Severity: normal

Most users probably don't even notice this, but as I sometimes work with
DVD images, I find it annoying.

It should be an easy fix, maybe even just a recompile with different #defines.

In case you're wondering where LFS would even be an issue for a program that
just renames files: imv does try to stat() the source file before doing
anything with it, and that just won't work for files >= 4 GiB.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (200, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8)

Versions of packages renameutils depends on:
ii  libc6 2.3.6-15   GNU C Library: Shared libraries
ii  libreadline5  5.1-7  GNU readline and history libraries

renameutils recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#355281: New upstream version

[Maik Zumstrull]

Any chance of getting this code into Debian any time soon?

It's been two months (and two upstream versions).


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#372899: sylpheed-claws-gtk2: Creates new folders on IMAP mailboxes without asking (and you can't get rid of them after)

[Maik Zumstrull]

Package: sylpheed-claws-gtk2
Version: 2.2.0-1
Severity: normal

Wenn adding a new IMAP mailbox, s-c checks if the folders Trash, Queue, Drafts
and Sent exist on the server.
If not, they are created without asking for permission.

The problem with that is that folders for most of these purposes already exist
on my IMAP mailbox, but they have German names (Geloescht, Entwuerfe,
Gesendet). They need to have German names because the mailbox is accessed in
parallel by a webinterface and a voice/fax messaging solution, which expect
the German names, and I can't change that.

So, right now the workflow to use this account with s-c is the following:
- Add the account and let s-c build the folderlist
- Change the folders for Drafts, Queue, Sent, Trash to the correct ones
- Exit s-c
- Delete the folders s-c created on the IMAP server using the webinterface
  (s-c refuses to delete any of the "special" folders, even if the specific
  functionality has already been reassigned to a different folder)
- Manually delete the entries for the folders created by s-c from
  folderlist.xml (even after the folders are gone from the server, s-c insists
  they exist; messages from the server that they don't exist are quietly
  ignored for "special" folders, even though the specific functionality etc...)

Steps three through five have to repeated every time I feel like rebuilding the
folderlist in s-c.

I think s-c should ask on creation of an IMAP account whether I want to
a) Create the special folders on the server (assuming they don't exist), 
b) Use existing folders, local or on this or some other account, for these
   purposes,
c) Not have these special folders at all.

I'm classifying this report "normal" instead of "whishlist" because the way
special folders are handled right now seems not only lacking features, but
broken. I shouldn't have to do all of the above just to delete a folder that
happens to be named "Sent", especially not if the Sent folder functionality is
not even assigned to that folder anymore.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8)

Versions of packages sylpheed-claws-gtk2 depends on:
ii  libaspell15   0.60.4-4   GNU Aspell spell-checker runtime l
ii  libc6 2.3.6-15   GNU C Library: Shared libraries
ii  libcompfaceg1 1:1.5.2-3  Compress/decompress images for mai
ii  libetpan6 0.45-3 mail handling library
ii  libglib2.0-0  2.10.3-1   The GLib library of C routines
ii  libgnomeprint2.2-02.12.1-4   The GNOME 2.2 print architecture -
ii  libgnomeprintui2.2-0  2.12.1-3   GNOME 2.2 print architecture User 
ii  libgtk2.0-0   2.8.18-1   The GTK+ graphical user interface 
ii  libldap2  2.1.30-13  OpenLDAP libraries
ii  libpango1.0-0 1.12.3-1   Layout and rendering of internatio
ii  libpisock80.11.8-23  Library for communicating with a P
ii  libssl0.9.8   0.9.8b-2   SSL shared libraries

Versions of packages sylpheed-claws-gtk2 recommends:
ii  aspell-de [aspell-dict 0.60-20030222-1-5 German dictionary for aspell
ii  aspell-en [aspell-dict 6.0-0-5   English dictionary for GNU Aspell
ii  metamail   2.7-51implementation of MIME
ii  sylpheed-claws-gtk2-i1 2.2.0-1   Locale data for Sylpheed-Claws GTK
ii  sylpheed-claws-scripts 1.0.5-2.1 Helper scripts for Sylpheed and Sy
ii  xfonts-100dpi  1:1.0.0-2 100 dpi fonts for X
ii  xfonts-100dpi-transcod 1:1.0.0-2 100 dpi fonts for X (transcoded fr
ii  xfonts-75dpi   1:1.0.0-2 100 dpi fonts for X
ii  xfonts-75dpi-transcode 1:1.0.0-2 75 dpi fonts for X (transcoded fro

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#380248: libchipcard2: chipcardd2 cannot access USB readers by default

[Maik Zumstrull]

Package: libchipcard2
Severity: important

Debian's default udev installation creates USB devices with root:root
ownership and 0660 access rights.

Debian's chipcardd2 is running as chipcard:chipcard by default.

chipcard-tool -v check and chipcard-tool -v atr reproducably fail on my system
after just plugging the reader in, but succeed after chmod'ing the relevant
device, which right now is /dev/bus/usb/002/005 (but that can change,
of course), to 0666.

I suggest the inclusion of udev rules in the package which make CCID USB
devices (and other classes relevant for chipcard access) owned by root:chipcard
by default.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (200, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#485583: Spam filter drops mails to majord...@lists.debian.org with empty subject

[Maik Zumstrull]

Alexander Wirt wrote:

> I tried to reproduce your bugreport about mails without subject to
> majord...@lists.d.o being dropped. Unfortunatly I can't reproduce the
> problem, my mail went through the filter without problems. Is the
> problem still existing for you? 

I sent the attached mail at 14:01 CET today. As of now (15:55) I have
not received any reaction, so yes, I think my mails still get dropped.

Maybe during your test, you used a client that enforces the existence
of a Subject: header, even when no subject is given? Or maybe, the
Subject: header isn't the real issue at all, I don't know.--- Begin Message ---
which m...@zumstrull.net
which li...@zumstrull.net--- End Message ---

Bug#485583: Spam filter drops mails to majord...@lists.debian.org with empty subject

[Maik Zumstrull]

Maik Zumstrull wrote:

> Alexander Wirt wrote:
> 
> > I tried to reproduce your bugreport about mails without subject to
> > majord...@lists.d.o being dropped. Unfortunatly I can't reproduce
> > the problem, my mail went through the filter without problems. Is
> > the problem still existing for you? 
> 
> I sent the attached mail at 14:01 CET today. As of now (15:55) I have
> not received any reaction, so yes, I think my mails still get dropped.

As a positive test, I just sent the attached message, which is
basically the same, except with a real Subject: header.

I received the expected replies instantly (< 1 min delay).--- Begin Message ---
which m...@zumstrull.net
which li...@zumstrull.net--- End Message ---

Bug#421464: pdfetex: Not embedding Base-14 fonts creates somewhat broken files

[Maik Zumstrull]

Package: texlive-base-bin
Version: 2007-5
Severity: normal

When choosing not to embed the Base 14 fonts (Helvetica, Times, etc.) in a
pdfetex-created PDF document, the resulting files are sometimes displayed wrong
in Adobe Reader. Specifically, a serif font is chosen to display Helvetica
instead of a sans-serif font, which obviously changes the visual impression of
any document significantly. The files are interpreted correctly by evince.
They also work correctly on my (Postscript 3-capable) printer after a PDF->PS
conversion with Ghostscript.

Note that PDFs without embedded fonts are, while "not recommended", perfectly
valid, especially when the Base 14 fonts are concerned, which any PDF viewer
is supposed to provide correct versions of anyway.

I cannot guarantee that this behaviour is formally a bug in pdfetex instead of
a weird anomaly of Adobe Reader. However: Since Adobe Reader is *the*
multi-platform standard for displaying PDF files whether we like it or not, it
would be good to create files that work correctly in it. Also, even if the
problem would technically lie with Adobe Reader, just implementing a workaround
in pdfetex would probably be simpler than getting Adobe to do anything.

Sample input including precompiled PDFs with and without the embedded fonts
can be found at 

for the time being. If you would prefer to include the files in the BTS itself,
feel free to do so.

I wasn't entirely sure which texlive subpackage to submit this to, feel free to
reassign.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (110, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.20-1-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages texlive-base-bin depends on:
ii  ed0.2-20 The classic unix line editor
ii  libc6 2.5-4  GNU C Library: Shared libraries
ii  libncurses5   5.5-5  Shared libraries for terminal hand
ii  libpng12-01.2.15~beta5-1 PNG library - runtime
ii  libpoppler0c2 0.4.5-5.1  PDF rendering library
ii  libx11-6  2:1.0.3-7  X11 client-side library
ii  libxaw7   1:1.0.3-3  X11 Athena Widget library
ii  libxmu6   1:1.0.3-1  X11 miscellaneous utility library
ii  libxpm4   1:3.5.6-2  X11 pixmap library
ii  libxt61:1.0.5-2  X11 toolkit intrinsics library
ii  mime-support  3.39-1 MIME files 'mime.types' & 'mailcap
ii  perl  5.8.8-7Larry Wall's Practical Extraction 
ii  texlive-common2007-4 TeX Live: Base component
ii  zlib1g1:1.2.3-13 compression library - runtime

Versions of packages texlive-base-bin recommends:
pn  perl-tk(no description available)

Versions of packages tex-common depends on:
ii  debconf   1.5.13 Debian configuration management sy
ii  ucf   2.0021 Update Configuration File: preserv

Versions of packages texlive-base-bin is related to:
pn  tetex-base (no description available)
pn  tetex-bin  (no description available)
pn  tetex-extra(no description available)

-- debconf information:
  tex-common/check_texmf_wrong:
  tex-common/check_texmf_missing:


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#421541: kaddressbook: GMX import/export filter doesn't use the current .gmxa format

[Maik Zumstrull]

Package: kaddressbook
Version: 4:3.5.6.dfsg.1-2
Severity: normal

The subject pretty much says it all -- it seems GMX changed the file format.

Importing from GMX still works more or less, but exporting and re-importing
into GMX is mostly useless now.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (110, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.20-1-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages kaddressbook depends on:
ii  kdelibs4c2a  4:3.5.6.r1.dfsg.1-4 core libraries and binaries for al
ii  libacl1  2.2.42-1Access control list shared library
ii  libart-2.0-2 2.3.19-3Library of functions for 2D graphi
ii  libattr1 1:2.4.32-1.1Extended attribute shared library
ii  libaudio21.9-1   The Network Audio System (NAS). (s
ii  libbluetooth23.9-1   Library to use the BlueZ Linux Blu
ii  libc62.5-4   GNU C Library: Shared libraries
ii  libfam0  2.7.0-12Client library to control the FAM 
ii  libfontconfig1   2.4.2-1.2   generic font configuration library
ii  libfreetype6 2.2.1-5 FreeType 2 font engine, shared lib
ii  libgcc1  1:4.2-20070405-1GCC support library
ii  libgnokii3   0.6.14-3+b1 Gnokii library
ii  libice6  1:1.0.3-2   X11 Inter-Client Exchange library
ii  libidn11 0.6.5-1 GNU libidn library, implementation
ii  libjpeg626b-13   The Independent JPEG Group's JPEG 
ii  libkcal2b4:3.5.6.dfsg.1-2KDE calendaring library
ii  libkdepim1a  4:3.5.6.dfsg.1-2KDE PIM library
ii  libkleopatra14:3.5.6.dfsg.1-2KDE GnuPG interface libraries
ii  libktnef14:3.5.6.dfsg.1-2Library for handling KTNEF email a
ii  libpng12-0   1.2.15~beta5-1  PNG library - runtime
ii  libqt3-mt3:3.3.7-4+b1Qt GUI Library (Threaded runtime v
ii  libsm6   1:1.0.2-2   X11 Session Management library
ii  libstdc++6   4.2-20070405-1  The GNU Standard C++ Library v3
ii  libx11-6 2:1.0.3-7   X11 client-side library
ii  libxcursor1  1:1.1.8-2   X cursor management library
ii  libxext6 1:1.0.3-2   X11 miscellaneous extension librar
ii  libxft2  2.1.12-2FreeType-based font drawing librar
ii  libxi6   1:1.0.1-4   X11 Input extension library
ii  libxinerama1 1:1.0.2-1   X11 Xinerama extension library
ii  libxpm4  1:3.5.6-2   X11 pixmap library
ii  libxrandr2   2:1.2.1-1   X11 RandR extension library
ii  libxrender1  1:0.9.2-1   X Rendering Extension client libra
ii  libxt6   1:1.0.5-2   X11 toolkit intrinsics library
ii  zlib1g   1:1.2.3-13  compression library - runtime

kaddressbook recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#421464: [Fwd: Bug#421464: pdfetex: Not embedding Base-14 fonts creates somewhat broken files]

[Maik Zumstrull]

Norbert Preining wrote:

> Hi Martin, hi all!
>
> On Mon, 30 Apr 2007, Ralf Stubner wrote:
> > For the record: I cannot reproduce this on two different Windows
> > boxes, one with AR 7, one with Acrobat Profssional 7. In both
> > cases, Arial is used to substitute the missing Helvetica.
>
> I can confirm this for the Windows side:
>
> - on linux Acrobat Reader 7.0.8 uses Serif fonts
> - on windows Acrobat Professional uses correctly ArialSomeThing

FYI, I found a file somewhere that uses a non-embedded Helvetica that 
Linux AR 7 displays correctly, that is, with a sans-serif font. The 
difference I could see at first glance was that it said "Encoding: 
Ansi" instead of "Encoding: Custom" in the file information dialog in 
Adobe Reader. "Producer:" is "FPDF 1.52".


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#444416: Searching for reports by eMail-address has case-sensitivity issues

[Maik Zumstrull]

Package: bugs.debian.org

Searching bdo for bugs submitted from a specific eMail-address currently 
forces all addresses to lower-case.

Compare:
http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED]
http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED]

This behaviour is wrong. Two possible fixes:

1) Make the search case-insensitive. Technically not correct, but probably the 
user-expected behaviour.
2) Keep the search case-sensitive, but compare to the actual submitter 
address, instead of the all-lowercase version of it.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#440318: vpnc: Please activate hybrid authentication support

[Maik Zumstrull]

Package: vpnc
Version: 0.5.0-1

vpnc 0.5.0 supports hybrid auth for the first time. You even mention 
this in the changelog, but it hasn't actually been switched on:

[EMAIL PROTECTED] ~ % sudo vpnc unika-neu
vpnc was built without openssl: Can't do hybrid mode.
1 [EMAIL PROTECTED] ~ %

Please reupload with adjusted build settings.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#440318: Correction

[Maik Zumstrull]

Correction: You actually don't specifically mention this in the 
changelog. I must have been confused.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#440318: vpnc: Please activate hybrid authentication support

[Maik Zumstrull]

reopen 440318
severity 440318 wishlist
retitle 440318 Activate hybrid auth after licensing issues are resolved
thanks

Am Freitag, 31. August 2007 19:55:37 schrieb Eduard Bloch:
> * Maik Zumstrull [Fri, Aug 31 2007, 03:29:24PM]:
> >
> > vpnc 0.5.0 supports hybrid auth for the first time.
[...]
> > but it hasn't actually been switched on: 
>
> This has a reason. [OpenSSL-GPL-Conflict]

*eyeroll* How annoying. One would think people would fix that particular 
problem up front these days with a license exception...but I understand 
that the feature can't be included in Debian for now.

However, I strongly disagree with your assumption that simply pointing 
out the license problem fixes the issue; the fact that this feature is 
disabled in Debian remains and is what the bug report is about.

Therefore, I'm taking the liberty of reopening this report.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#544155: Confirmation

[Maik Zumstrull]

I'm seeing the same issue, also on a T-Series Thinkpad (T43p).
Downgrading grub now.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#544155: please test this GRUB snapshot

[Maik Zumstrull]

Robert Millan wrote:

> > Again, it doesn't go into graphical mode by itself, and boots okay
> > in console mode. Here are the results for different commands on the
> > console:
> > 
> > terminal_output.gfxterm:
> > Clears the screen and prints "error: No suitable mode found."
> > 
> > vbetest:
> > Displays some data and "Press any key to continue". After pressing a
> > key, prints "error: unsupported pixel format 0x0".
> > 
> > vbeinfo:
> > The system hangs for a moment, then reboots. Nothing gets printed.
> > 
> > videotest:
> > Prints "error: No suitable mode found."
> 
> Ok.  We will consider this a failure.  This bug is somewhat hideous,
> so it might fail differently with each version, but we're reasonably
> sure it's the same bug.
> 
> Would you please test the version in squeeze (1.96+20090808-1)?

Fails. Same as above for terminal_output.gfxterm and vbetest, but
vbeinfo actually prints something with this version, the infamous
"unaligned pointer" message, before crashing and rebooting. Right
before the reboot I see another message "No operating system found"
that I think comes from the Thinkpad BIOS, not grub.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#544155: please test this GRUB snapshot

[Maik Zumstrull]

Robert Millan wrote:

> > > Would you please test the version in squeeze (1.96+20090808-1)?
> > 
> > Fails.

> And the one in lenny (1.96+20080724-16)?

Works. I purged before installing this one, because I wouldn't want to
bet that a downgrade that far works cleanly.

It successfully enters graphical mode, the screen looks right
(background image and all) and boots cleanly.

Is snapshots.debian.net back online? If so, I'll write a quick script
that grabs a grub .deb and puts the necessary files on a USB stick.
That should allow me to quickly test a lot of versions to see which one
starts failing.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#544155: please test this GRUB snapshot

[Maik Zumstrull]

Robert Millan wrote:

> Still down.  I guess I'll be your snapshots.debian.net today.

:-)

> Here's the first one:
> 
>   http://people.debian.org/~rmh/ati/2106/

I'm sorry, my T43p is fairly old (2005 model). Its Pentium M processor
is strictly i686, not amd64 compatible.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#544155: please test this GRUB snapshot

[Maik Zumstrull]

Robert Millan wrote:

> On Mon, Sep 07, 2009 at 05:34:25PM +0200, Maik Zumstrull wrote:
> > Robert Millan wrote:
> > 
> > > Still down.  I guess I'll be your snapshots.debian.net today.
> > 
> > :-)
> > 
> > > Here's the first one:
> > > 
> > >   http://people.debian.org/~rmh/ati/2106/
> > 
> > I'm sorry, my T43p is fairly old (2005 model). Its Pentium M
> > processor is strictly i686, not amd64 compatible.
> 
> i386 debs uploaded now.

Thank you.

ii  grub-common  1.96+20090413-1
ii  grub-pc  1.96+20090413-1

Still works.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org