Showing diffs for issues.dbk... (ver: 6592:)Index: issues.dbk
===================================================================
--- issues.dbk (revisión: 6592)
+++ issues.dbk (copia de trabajo)
@@ -12,13 +12,14 @@
Potential problems
-
-Sometimes, changes have side-effects we cannot reasonably avoid, or we expose
-bugs somewhere else. We document here the issues we are aware of. Please also
+
+Sometimes, changes introduced in a new release have side-effects
+we cannot reasonably avoid, or they expose
+bugs somewhere else. This section documents issues we are aware of. Please also
read the errata, the relevant packages' documentation, bug reports and other
information mentioned in .
-
+
Problems with devices related to udev
Although udev has been tested
@@ -35,20 +36,65 @@
-
-Some applications may no longer work with a 2.4 kernel
+
+Migration of disk drivers from IDE to PATA subsystem
-Some applications in &releasename; may no longer work with a 2.4 kernel, for example
-because they require epoll() support, which is not available
-in 2.4 kernels. Such applications may either not work at all or not work
-correctly until the system has been rebooted with a 2.6 kernel.
+ The new Linux kernel version provides different drivers for some PATA (IDE)
+ controllers. The names of some hard disk, CD-ROM, and tape devices may
+ change.
-One example is the HTTP proxy squid.
+ It is now recommended to identify disk devices in configuration files by
+ label or UUID (unique identifier) rather than by device name, which will
+ work with both old and new kernel versions. Upon upgrading to the
+ &releasename; version of the Debian kernel packages, the linux-base package will offer to do this
+ conversion for you in the config files for most of the filesystem-related
+ packages on the system, including the various bootloaders included in
+ Debian. If you choose not to update the system configuration
+ automatically, or if you are not using the Debian kernel packages, you must
+ update device IDs yourself before the next system reboot to ensure the
+ system remains bootable.
-
+
+
+
+pam_userdb.so breakage with newer libdb
+
+Some Berkeley Database version 7 files created with libdb3 cannot be read by
+newer libdb versions (see bug #521860).
+As a workaround, the files can be recreated with db4.8_load,
+from the db4.8-util package.
+
+
+
+
Certain network sites cannot be reached by TCP
Since 2.6.17, Linux aggressively uses TCP window scaling which is
@@ -66,7 +112,7 @@
-
+
Automatic poweroff stops working
On some older systems, shutdown -h may not power off the
@@ -104,7 +150,7 @@
-
+
Asynchronous network initialization may cause unpredictable behavior
On systems which use udev to load
@@ -120,7 +166,7 @@
-
+
Trouble when using <acronym>WPA</acronym> secured wireless networks
WPA
@@ -147,7 +193,7 @@
-
+
Problems with non-ASCII characters in filenames
Mounting vfat, ntfs or iso9660 file systems with files that include non-ASCII
@@ -164,7 +210,7 @@
-
+
Sound stops working
In rare cases, sound might stop working after the upgrade. If this happens,
@@ -204,7 +250,8 @@
check whether the command
-cat /dev/urandom > /dev/dsp
+cat /dev/urandom > /dev/audio
+or the command speaker-test
works for root.
@@ -212,7 +259,7 @@
-
+
Potential Filesystem Corruption on upgrade
Starting with Kernel 2.6.25, Linux on the s390 architecture
@@ -233,167 +280,50 @@
-
-
-
-Upgrading to a 2.6 kernel
-TODO: This section can be removed for lenny!
-
-The 2.6 kernel series contains major changes from the 2.4 series. Modules have
-been renamed and a lot of drivers have been partially or sometimes almost
-completely rewritten. Upgrading to a 2.6 kernel from an earlier version is
-therefore not a process to be undertaken lightly. This section aims to make
-you aware of some of the issues you may face.
-
-
-If you compile your own kernel from source, make sure you install module-init-tools before you reboot with the 2.6
-kernel. This package replaces modutils
-for 2.6 kernels. If you install one of the Debian linux-image packages, this package will be
-installed automatically because of dependencies.
-
-
-If you use LVM, you should also install lvm2 before you reboot as the 2.6 kernel does not
-directly support LVM1. To access LVM1 volumes, the compatibility layer of
-lvm2 (the dm-mod module) is used. You
-can leave lvm10 installed; the init
-scripts will detect which kernel is used and execute the appropriate version.
-
-
-If you have entries in the /etc/modules file (the list of
-modules to be loaded during system boot), be aware that some module names may
-have changed. If this happens you will have to update this file with the new
-module names.
-
-
-For some SATA disk controllers, the device assigned to a drive and its
-partitions may change from /dev/hdX to
-/dev/sdX. If this happens, you will have to modify your
-/etc/fstab and bootloader configuration accordingly.
-Unless these changes are made correctly, your system may not boot
-correctly It will boot the kernel but will fail when trying to
-mount the root file system and will abort with an error waiting for
-root file system followed by unable to mount /dev/hdX
-..not found. You can use the initramfs shell to
-fix this issue, after you identify the newly assigned device names in the
-kernel boot messages or by reviewing the contents of
-/dev/disk/. .
-
-
-Once you have installed your 2.6 kernel, but before you reboot, make sure you
-have a recovery method. First, make sure that the bootloader configuration has
-entries for both the new kernel and the old, working 2.4 kernel. You should
-also ensure you have a rescue
floppy or CD-ROM to hand, in case
-misconfiguration of the bootloader prevents you from booting the old kernel.
-
-
-Keyboard configuration
-
-The most invasive change in the 2.6 kernels is a fundamental change of the
-input layer. This change makes all keyboards look like normal
PC keyboards.
-This means that if you currently have a different type of keyboard selected
-(e.g. a USB-MAC or Sun keyboard), you will very likely end up with a
-non-working keyboard after rebooting with the new 2.6 kernel.
-
-
-If you can SSH into the box from another system, you can resolve this issue by
-running dpkg-reconfigure console-data, choosing the option
-Select keymap from full list
and selecting a pc
keyboard.
-
-
-If your console keyboard is affected, you will probably also need to
-reconfigure your keyboard for the X Window System. You can do this either by
-running dpkg-reconfigure xserver-xorg or by editing
-/etc/X11/xorg.conf directly. Don't forget to read the
-documentation referred to in .
-
-
-This issue is unlikely to affect the &arch-title; architecture as all
-PS/2 and most USB keyboards will already be configured as a normal
PC
-keyboard.
-
-Note that if you are using a USB keyboard, this
-may be configured as either a normal
PC keyboard or as a USB-MAC
-keyboard. In the first case you will not be affected by this
-issue.
-
-
-
-Mouse configuration
-
-Again because of the changes in the input layer, you may have to reconfigure
-the X Window System and gpm if your
-mouse is not working after upgrading to a 2.6 kernel. The most likely cause is
-that the device which gets the data from the mouse has changed. You may also
-need to load different modules.
-
-
-
-
-Sound configuration
-TODO: Do we still need this for lenny?
-
-For the 2.6 kernel series the ALSA sound drivers are recommended over the older
-OSS sound drivers. ALSA sound drivers are provided as modules by default. In
-order for sound to work, the ALSA modules appropriate for your sound hardware
-need to be loaded. In general this will happen automatically if you have, in
-addition to the alsa-base package,
-the discover package installed. The
-alsa-base package also blacklists
OSS
-modules to prevent discover
-from loading them. If you have OSS modules listed in
-/etc/modules, you should remove them.
-
-
-
-
-
-
- <acronym>NFS</acronym> mounts now handled by nfs-common
-
+
+ Potential issues with diversions of /bin/sh
- Since util-linux 2.13
- NFS mounts are no longer handled by util-linux itself, but by nfs-common. Since not all systems
- mount NFS shares and to avoid a standard
- portmapper installation util-linux only suggests nfs-common. If you need to mount
- NFS shares, make sure nfs-common is installed on your
- system. The preinstallation script of the mount package checks whether
- NFS mounts exist and aborts if
- /usr/sbin/mount.nfs from nfs-common is not present or if
- nfs-common is
- out-of-date. Either upgrade nfs-common or unmount any
- NFS mounts prior to upgrading mount.
+ If you have previously added a local diversion for /bin/sh,
+ or modified the /bin/sh symlink to point to somewhere
+ other than /bin/bash, then you may encounter problems
+ when upgrading the dash or
+ bash packages.
+ Note that this includes changes made by allowing other packages (for example
+ mksh) to become the default system
+ shell by taking over /bin/sh.
+
+ If you encounter any such issues, please remove the local diversion and
+ ensure that the symlinks for both /bin/sh and its
+ manual page point to the files provided by the bash package and then
+ dpkg-reconfigure --force dash.
+
+
+ dpkg-divert --remove /bin/sh
+ dpkg-divert --remove /usr/share/man/man1/sh.1.gz
+
+ ln -sf bash /bin/sh
+ ln -sf bash.1.gz /usr/share/man/man1/sh.1.gz
+
-
- Change of Romanian (ro) keyboard layout
+
+
+ Change in kernel policy regarding resource conflicts
- Because of the upgrade to xkb-data version 1.3 in &releasename;
- the default variant for Romanian (ro) layout is now producing the
- correct șț characters (comma below) instead of şţ (cedilla
- below). Also some of the variants have been renamed. The old
- variant names still work, but users are encouraged to update their
- /etc/X11/xorg.conf. More info as well as
- possible side effects due to this change are available in the
-
- wiki (Romanian language only).
+ The default setting for the acpi_enforce_resources parameter in the Linux
+ kernel has changed to be strict
by
+ default. This can lead some legacy sensor drivers to be denied access to
+ the sensors' hardware. One workaround is to append
+ acpi_enforce_resources=lax
to the kernel
+ command line.
-
+
+
Upgrading apache2
The apache2 default configuration has changed in some ways that
@@ -440,7 +370,7 @@
-
+
<acronym>NIS</acronym> and Network Manager
NIS
Network Manager
@@ -465,150 +395,376 @@
-
-Security status of Mozilla products
+
+ <acronym>LDAP</acronym> support
+ LDAP
+
+ A feature in the cryptography libraries used in the
+ LDAP libraries causes programs that use
+ LDAP and attempt to change their effective
+ privileges to fail when connecting to an LDAP
+ server using TLS or SSL.
+ This can cause problems for suid programs on systems using
+ libnss-ldap like
+ sudo, su or
+ schroot and for suid programs that perform LDAP
+ searches like sudo-ldap.
+
+
+ It is recommended to replace the
+ libnss-ldap package with
+ libnss-ldapd, a newer library
+ which uses separate daemon (nslcd) for all
+ LDAP lookups. The replacement for
+ libpam-ldap is
+ libpam-ldapd.
+
+
+ Note that libnss-ldapd recommends
+ the NSS caching daemon (nscd)
+ which you should evaluate for suitability in your environment before
+ installing.
+ As an alternative to nscd you
+ can consider unscd.
+
+
+ Further information is available in bugs
+ #566351 and
+ #545414.
+
+
+
+
+
+<literal>sieve</literal> service moving to its IANA-allocated port
-Mozilla
-The Mozilla programs firefox,
-thunderbird, and
-sunbird (rebranded in Debian to
-iceweasel, icedove, and iceowl, respectively), are important tools for
-many users. Unfortunately the upstream security policy is to urge users to
-update to new upstream versions, which conflicts with Debian's policy of not
-shipping large functional changes in security updates. We cannot predict it
-today, but during the lifetime of &releasename; the Debian Security Team may come to a
-point where supporting Mozilla products is no longer feasible and announce the
-end of security support for Mozilla products. You should take this into
-account when deploying Mozilla and consider alternatives available in Debian if
-the absence of security support would pose a problem for you.
+The IANA port allocated for ManageSieve is 4190/tcp, and the old port used
+by timsieved and other managesieve software in many
+distributions (2000/tcp) is allocated for Cisco SCCP usage, according to the IANA registry.
-iceape, the unbranded version
-of the seamonkey internet
-suite has been removed from &releasename; (with the exception of a few
-internal library packages).
+Starting with the version 4.38 of the Debian netbase package, the sieve
+service will be moved from port 2000 to port 4190 in the
+/etc/services file.
+
+Any installs which used the sieve service name instead of a
+numeric port number will switch to the new port number as soon as the services
+are restarted or reloaded, and in some cases, immediately after
+/etc/services is updated.
+
+
+This will affect Cyrus IMAP. This may also affect other sieve-enabled
+software such as DoveCot.
+
+
+In order to avoid downtime problems, mail cluster administrators using
+Debian are urged to verify their Cyrus (and probably also DoveCot) installs,
+and take measures to avoid services moving from port 2000/tcp to port
+4190/tcp by surprise in either servers or clients.
+
+
+It is worth noting that:
+
+
+
+/etc/services will only be automatically updated if you
+never made any modifications to it. Otherwise, you will be presented with a
+prompt by dpkg asking you about the changes.
+
+
+
+
+You can edit /etc/services and change the
+sieve port back to 2000 if you want (this is not
+recommended, though).
+
+
+
+
+You can edit /etc/cyrus.conf and any other relevant
+configuration files for your mail/webmail cluster (e.g. on the sieve web
+frontends) ahead of time to force them all to a static port number.
+
+
+
+
+You can configure cyrus master to listen on both ports (2000 and 4190)
+at the same time, and thus avoid the problem entirely. This also allows for
+a much more smooth migration from port 2000 to port 4190.
+
+
+
+
+
KDE desktop
-There are no huge changes in the KDE Desktop Enviroment from the version
-shipped in etch. Lenny ships an updated translation and service release of KDE
-3.5 that is a mixture of 3.5.9 and 3.5.10. Some modules are labeled as version
-3.5.9, but have been updated and include most of the same changes found in 3.5.10.
-Overall, lenny ships 3.5.10 without the kicker improvements shipped in kdebase
-and some bug fixes in kdepim.
+&Releasename; is the first Debian release to ship with the full support
+for the next generation KDE that is based on Qt 4.
+Most official KDE applications are at version 4.4.5 with the exception
+of kdepim that is at version 4.4.7. You
+can read the announcements from
+the KDE Project to learn more about the changes.
+
+
+Upgrading from KDE 3
+
-Lenny will be the last stable release including a KDE 3 series environment.
+KDE 3 Desktop Environment is no longer supported in Debian &release;.
+It will be automatically replaced by the new 4.4 series on upgrade.
+As this is a major change, users should take some precautions in order
+to ensure as smooth of an upgrade process as possible.
+
+
+
+It is discouraged to upgrade while there is an active KDE 3 session
+on the system. Otherwise, the process might render the running session
+dysfunctional with the possibility of data loss.
+
+
+
+
+Upon the first login on the upgraded system, existing users will
+be prompted with the Debian-KDE guided migration procedure called
+kaboom
+which will assist in the process of migrating the user's personal data
+and optionally backing up old KDE configuration.
+For more information, visit
+the Kaboom homepage.
+
+
+
+While KDE 3 based desktop environment is no longer supported,
+users can still install and use some individual KDE 3 applications
+since the core libraries and binaries of KDE 3
+(kdelibs) and Qt 3 are
+still available in Debian &release;. However, please note that these
+applications might not be well integrated with the new environment.
+What's more, neither KDE 3 nor Qt 3 will be supported in any form in the next
+Debian release so if you are using them, you are strongly advised to port your
+software to the new platform.
+
-
-GNOME desktop changes and support
-TODO: Remove the next three paragraphs for lenny?
-
-If you used the GNOME desktop in &oldreleasename; you will not benefit from some of the
-changes introduced in the default configuration in Debian for &releasename;. In some
-extreme cases the GNOME desktop might not properly handle your old
-configuration and might not behave properly.
+
+
+
+
+
+GNOME desktop changes and support
+
There have been many changes in the GNOME desktop environment from the version
shipped in &oldreleasename; to the version in &releasename;, you can find more information in the
-GNOME 2.22 Release
-Notes.
+GNOME 2.30 Release
+Notes. Specific issues are listed below.
+
+
+GDM 2.20 and 2.30
+
+The GNOME Display Manager (GDM), is kept at version 2.20 for systems upgraded
+from &oldreleasename;. This version will still be maintained for the squeeze
+cycle but it is the last release to do so. Newly installed systems will get
+GDM 2.30 instead, provided by the gdm3
+package. Because of incompatibilities between both versions, this upgrade is
+not automatic, but it is recommended to install gdm3 after the upgrade to &releasename;. This
+should be done from the console, or with only one open GNOME session. Note
+that settings from GDM 2.20 will not be
+migrated. For a standard desktop system, however, simply installing
+gdm3 should be enough.
+
-
-No default support for Unicode in emacs21*
-Unicode
+
+Device and other administrative permissions
-Emacs21 and emacs21-nox are not configured to use Unicode by default. For more
-information and a workaround please see Bug #419490.
-Consider switching to emacs22,
-emacs22-gtk, or emacs22-nox.
+Specific permissions on devices are
+granted automatically to the user currently logged on physically to the
+system: video and audio devices, network roaming, power management,
+device mounting. The cdrom, floppy, audio, video, plugdev and powerdev
+groups are no longer useful. See the consolekit documentation for more information.
+
+Most graphical programs requiring root permissions now rely on PolicyKit to
+do so, instead of gksu. The recommended
+way to give a user administrative rights is to add it to the
+sudo group.
+
-
- slurpd/replica will no longer work
+
+ network-manager and ifupdown interaction
- OpenLDAP has dropped support for LDAP
- replication via the slurpd service in release 2.4.7. Existing
- configurations need to be reconfigured for the
- LDAP Sync Replication engine (syncrepl). More
- verbose documentation can be found at http://www.openldap.org/doc/admin24/replication.html.
+ Upon upgrading the network-manager
+ package, interfaces configured in
+ /etc/network/interfaces to use
+ DHCP with no other options will be disabled in that
+ file, and handled by NetworkManager instead. Therefore the
+ ifup and ifdown commands will not
+ work. These interfaces can be managed using the NetworkManager frontends
+ instead, see the
+ NetworkManager documentation.
-
-
-
- Desktop not using full screen
- The driver for Intel Mobile GM965 may wrongly detect a
- VGA output and set the size of the screen to a
- lower value to accomodate it. The symptom of this bug is that the
- desktop manager will only use a fraction of the screen. Correct
- behaviour can be forced by adding the following lines to the
- /etc/X11/xorg.conf configuration file.
- Section "Monitor"
- Identifier "VGA"
- Option "Ignore" "true"
-EndSection
- Please refer to the bug #496169 for more informations.
+ Conversely, any interfaces configured in
+ /etc/network/interfaces with more options will be
+ ignored by NetworkManager. This applies in particular to wireless
+ interfaces used during the installation of Debian (see bug #606268).
-
- &releasename; kernel fails to boot on Sparc workstations with PCI-Express
+
+
+ Graphics stack changes
- Due to an unfortunate interaction of a kernel fix with PCI Express
- subsystem, Lenny default kernel will fail to boot on Sparc
- workstations with PCI Express slots, like Ultra 25 and Ultra
- 45. As this problem has been discovered very late in the release
- cycle, we were unable to include a fix in the original Lenny
- release, but we'll do our best to eliminate the problem for the
- first point release.
- Sun Ultra 25
- Sun Ultra 45
- PCI Express
+ There have been a number of changes to the X stack in Debian &release;.
+ This section lists the most important and user-visible.
-
-
- <acronym>DHCP</acronym> failover issue
+
+ Obsolete Xorg drivers
+
+ The cyrix, imstt,
+ sunbw2 and vga Xorg video drivers
+ are no longer provided. Users should switch to a generic such as
+ vesa or fbdev instead.
+
+
+ The old via driver was no longer maintained, and has
+ been replaced by the openchrome driver, which will be
+ used automatically after the upgrade.
+
+
+ The nv and radeonhd drivers are
+ still present in this release, but are deprecated. Users should
+ consider the nouveau and radeon
+ drivers instead, respectively.
+
+
+ The calcomp, citron,
+ digitaledge, dmc,
+ dynapro, elo2300,
+ fpit, hyperpen,
+ jamstudio, magellan,
+ microtouch, mutouch,
+ palmax, spaceorb,
+ summa, tek4957 and
+ ur98 X input drivers have been discontinued and are
+ not included in this release. Users of these devices might want to
+ switch to a suitable kernel driver and the evdev X driver. For many
+ serial devices, the inputattach utility allows
+ attaching them to a Linux input device which can be recognized by the
+ evdev X driver.
+
+
-
- When running a failover pair of DHCP servers,
- the peer names need to be consistent, otherwise
- DHCP will crash.
-
-
- Please see and
- for more information.
-
+
+ Kernel mode setting
+
+ Kernel drivers for Intel (starting from i830), ATI/AMD (from the
+ original Radeon to the Radeon HD 5xxx Evergreen
series)
+ and for NVIDIA graphics chipsets now support native mode setting.
+
+
+ Support for old-style userspace mode setting is discontinued in the
+ intel X driver, which requires a recent kernel.
+ Users of custom kernels should make sure that their configuration
+ includes CONFIG_DRM_I915_KMS=y.
+
+
+
+
+ Input device hotplug
+
+ The Xorg X server included in Debian &release; provides improved support
+ for hotplugging of input devices (mice, keyboards, tablets, …). The old
+ xserver-xorg-input-kbd and
+ xserver-xorg-input-mouse
+ packages are replaced by xserver-xorg-input-evdev, which requires a
+ kernel with the CONFIG_INPUT_EVDEV option enabled.
+ Additionally, some of the keycodes produced by this driver differ from
+ those traditionally associated with the same keys. Users of programs
+ like xmodmap and xbindkeys will
+ need to adjust their configurations for the new keycodes.
+
+
+
+
+ X server <quote>zapping</quote>
+
+ Traditionally, the
+ CtrlAltBackspace
+ combination would kill the X server. This combination is no longer
+ active by default, but can be re-enabled by reconfiguring the
+ keyboard-configuration package
+ (system-wide), or using your desktop environment's keyboard preferences
+ application.
+
+
+
+
. Added: 437 Removed: 281