Binary package hint: apparmor
When thee change_hat api is used AppArmor fails to log failures and
learning events.
This means failures are not getting properly reported, and the tools can
not be used to profile change_hat behavior.
ProblemType: Bug
ApparmorStatusOutput:
Error: command /usr/sbin/apparmor_status failed with exit code 4: You do not have enough privilege to read the profile set.
apparmor module is loaded.
Architecture: amd64
Date: Wed Oct 28 12:16:18 2009
DistroRelease: Ubuntu 9.10
Package: apparmor 2.3.1+1403-0ubuntu27
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: apparmor
Uname: Linux 2.6.31-14-generic x86_64
XsessionErrors:
(gnome-settings-daemon:1626): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(gnome-settings-daemon:1626): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(polkit-gnome-authentication-agent-1:1697): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(nautilus:1684): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
the CC is returning incorrect networkIndex values on describeInstances
the cc was setting instance networkIndex to the *index* of the
networkIndex list, instead of the networkIndex list value itself. This
bug may cause problems with public network addressing. Fixed in revno
933.
[regression] euca_rootwrap fixes affected eucalyptus power management (powerwake)
cluster/handlers.c: euca_rootwrap rework did not whitelist powerwake;
however, powerwake does *not* need root privs, drop euca_rootwrap
wrapper.
===========
SRU Verification
This fix is bundled with a set of unrelated SRU fixes for Eucalyptus.
To test this:
1) From a working UEC cluster, ensure that you have availability on your nodes:
$ euca-describe-availability-zones verbose
2) Ensure that your nodes support:
a) one of [ pm-suspend | pm-hibernate | poweroff ]
b) and wake-on-lan (might need to check bios, sudo ethtool eth0)
3) Adjust your eucalyptus scheduling algorithm to POWERSAVE on the front end
$ sudo sed -i "s/^SCHEDPOLICY=.*/SCHEDPOLICY=POWERSAVE/" /etc/eucalyptus/eucalyptus.conf
4) Restart eucalyptus
$ sudo restart eucalyptus
5) Make sure there are no running instances in your cloud
6) Watch the output of the CC, which will note the status of each node, waiting for 300 seconds of inactivity before putting the node to sleep
$ tail -f /var/log/eucalyptus/cc.log
...
[Tue Nov 3 14:39:09 2009][023511][EUCADEBUG ] node 192.168.1.126 idle since 1257280677: (72/300) seconds
...
[Tue Nov 3 16:09:57 2009][017368][EUCADEBUG ] sending powerdown to node: 192.168.1.126, http://192.168.1.126:8775/axis2/services/EucalyptusNC
...
7) After 300 seconds, you should see the node either suspend, hibernate, or poweroff, based on its capability
8) Once the node(s) are sleeping, run an instance. Eucalyptus should dynamically resume (powerwake) the node and deploy the new instance there.
$ euca-run-instances $EMI -k mykey -t c1.medium
Regression potential should be minimal, and restricted to Eucalyptus SCHEDPOLICY=POWERSAVE users, which is not the default scheduling policy.
===========
fuse-utils postinst fails if fuse-utils is a new install during a release upgrade
Its difficult to trigger this bug, the only way I found is to remove
fuse-utils and ubuntu-standard. But we got at least one report where a
fuse-util upgrade failed so I think this needs fixing. Given how trivial
the diff is I think a regression test is sufficient.
TEST CASE:
- use jaunty install
- enable jaunty-proposed
- perform a release upgrade with kubuntu
- verify that there are no regressions
- verify that fuse-utils is installed afterwards
Binary package hint: update-manager
no idea, el error se produjo en fuse, lirc y otras dependencias
ProblemType: Package
Architecture: i386
Date: Tue Oct 6 19:05:44 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg returned an error code (1)
Package: update-manager 1:0.125.6
PackageArchitecture: all
ProcVersionSignature: Ubuntu 2.6.27-14.41-generic
SourcePackage: update-manager
Title: package update-manager 1:0.125.6 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg returned an error code (1)
Uname: Linux 2.6.27-14-generic i686
New gdm does not have the FailsafeXServer config option
Binary package hint: gdm
gdm 2.20 had options in /etc/gdm/gdm.conf (in particular
FailsafeXServer) for specifying an action to take when X is failing to
start up. We attached a failsafe session (aka bulletproof-x) to be
invoked by gdm in these situations, which users could use to diagnose
and work around issues.
These options were implemented in the 'deal_with_x_crashes()' function
in gdm.c. Near as I can tell, this gdm feature was not included in the
new gdm rewrite, so we are seeing a regression here. The problem is
that whereas in the past the user would be dumped into a debugging
session, now gdm is simply trying multiple times, failing each time, and
then exiting (which then leads to the quite severe bug 441638).
Anyway, the end result is that we no longer have a debugging failsafe
mode available for users, they're just left with a non-functioning
system. Please either restore the missing functionality, or provide an
analogous mechanism to which we can attach a debugging session mode.
Changes xorg.conf when driver installation fails, no warning
Because of a bug in the nvidia-180 package the installation of the
driver with jockey failed (https://bugs.launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-180/+bug/450493) but i didn't get an error
message when installing the driver with the jockey-gtk.
I think jockey had been able to recognize that the installation wasn't
completely done, cause there are some error messages in the jockey.log:
Setting up patch (2.5.9-5) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
2009-10-13 13:37:47,669 ERROR:
Error! Invalid number of arguments passed.
Usage: add -m <module> -v <module-version>
2009-10-13 13:37:47,837 WARNING: modinfo for module nvidia failed:
ERROR: modinfo: could not find module nvidia
2009-10-13 13:37:47,914 DEBUG: XorgDriverHandler device sections ({0: ['\tIdentifier\t"Default Device"\n', '\tDriver\t"nvidia"\n']})
(https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/450493/comments/4)
There should been at least a warning, better an option to fall-back to
the actually working, installed driver.
I think in case of future bugs in driver-packages, users with no
experience aren't able to boot to console and edit xorg.conf to make
their system boot able again.
ProblemType: Bug
Architecture: i386
CheckboxSubmission: 4d2d0a0a0792a0b9fa942aa82fdaa6d9
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Wed Oct 14 16:07:29 2009
DistroRelease: Ubuntu 9.10
MachineType: Dell Inc. Inspiron 1720
NonfreeKernelModules: nvidia
Package: jockey-gtk 0.5.5-0ubuntu1
PackageArchitecture: all
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=e7d84e81-7c96-4c6c-a44c-ef9d34c7fc0c ro quiet splash
ProcEnviron:
LANG=de_AT.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.46-generic
SourcePackage: jockey
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
(gnome-settings-daemon:2094): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(gnome-settings-daemon:2094): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(polkit-gnome-authentication-agent-1:2204): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(nautilus:2194): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
dmi.bios.date: 02/03/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0UK437
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA07:bd02/03/2008:svnDellInc.:pnInspiron1720:pvr:rvnDellInc.:rn0UK437:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1720
dmi.sys.vendor: Dell Inc.
Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic i686
Distribution: Ubuntu 9.10
What I was doing when the application crashed:
Plasma crashes unexpectedly when closing an application (this happens randomly)
-- Backtrace:
Application: Plasma Workspace (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0xb7838700 (LWP 27091))]
Thread 2 (Thread 0xac77ab70 (LWP 27093)):
#0 0x00a31422 in __kernel_vsyscall ()
#1 0x009abe15 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2 0x0091278d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3 0x00cb3e67 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQtCore.so.4
#4 0x00b62922 in ?? () from /usr/lib/libQtNetwork.so.4
#5 0x00cb2e32 in ?? () from /usr/lib/libQtCore.so.4
#6 0x009a780e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7 0x009057ee in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 1 (Thread 0xb7838700 (LWP 27091)):
[KCrash Handler]
#6 0x052938b9 in ?? () from /usr/lib/libindicate.so.3
#7 0x01fe8d36 in ?? () from /usr/lib/libdbus-glib-1.so.2
#8 0x01ff0c24 in ?? () from /usr/lib/libdbus-glib-1.so.2
#9 0x05d9d072 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#10 0x05db27a8 in ?? () from /usr/lib/libgobject-2.0.so.0
#11 0x05db3b2d in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#12 0x05db3fb6 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#13 0x01ff1e2d in ?? () from /usr/lib/libdbus-glib-1.so.2
#14 0x04c85c8d in dbus_connection_dispatch () from /lib/libdbus-1.so.3
#15 0x01fe875d in ?? () from /usr/lib/libdbus-glib-1.so.2
#16 0x00a6ae78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#17 0x00a6e720 in ?? () from /lib/libglib-2.0.so.0
#18 0x00a6e853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#19 0x00dce02c in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#20 0x065c4be5 in ?? () from /usr/lib/libQtGui.so.4
#21 0x00da1c79 in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/libQtCore.so.4
#22 0x00da20ca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#23 0x00da453f in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#24 0x06523dd7 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#25 0x016a280d in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#26 0x0804dde1 in _start ()
Reported using DrKonqi
/var/log fills up with "all normal" messages @ about 575/sec fill up the available space
Forum thread is here
http://ubuntuforums.org/showthread.php?t=1284691&page=1
System Karmic Beta i386
Machine Dell Inspiron 1000 Laptop
Celeron 2.4 running 256MB RAM 40 GB HDD
Partitioning:
SDA1 100 MB with /boot
SDA2 764 MB swap
SDA3 6.4 GB with /
SDA4 29.5 GB /home
Problem:
After the initial install from alternate cd, and system update to -14
kernel version, the computer could not boot in to gnome or xterm.
“The configuration defaults for GNOME Power Manager have not been
installed correctly. Please contact your computer administrator."
further investigation showed that the disk is full and in particular the
/var/log directory occupied all available space for root. These
particular files are a problem:
sys.log is 1.7 GB
kern.log is 1.6 GB
messages are 700 mb
copies are available if needed.
Dmesg is attached.
Hi,
My Feisty (x86_64) lacks the bluez-firmware package needed to get my
broadcom bluetooth thumb going.
I subscribe to "main restricted universe multiverse". I found the
package in debian, in the non-free repo for all architectures. This
package seems to work fine.
Regards,
Nicolai
"Incomplete Language Support" is still shown when a DVD installation is preseeded with ALL
TEST CASE:
Preseed d-i pkgsel/language-packs string ALL. On reboot after installation, you should not see the "Incomplete Language Support" message.
Original report follows:
Binary package hint: ubiquity
Using the gold Ubuntu 9.10 media and the preseed " d-i pkgsel/language-
packs string ALL", the note
/var/lib/update-notifier/user.d/incomplete-language-support-gnome.note
is created causing this error to show on the first boot.
/var/log fills up with "all normal" messages @ about 575/sec fill up the available space
Forum thread is here
http://ubuntuforums.org/showthread.php?t=1284691&page=1
System Karmic Beta i386
Machine Dell Inspiron 1000 Laptop
Celeron 2.4 running 256MB RAM 40 GB HDD
Partitioning:
SDA1 100 MB with /boot
SDA2 764 MB swap
SDA3 6.4 GB with /
SDA4 29.5 GB /home
Problem:
After the initial install from alternate cd, and system update to -14
kernel version, the computer could not boot in to gnome or xterm.
“The configuration defaults for GNOME Power Manager have not been
installed correctly. Please contact your computer administrator."
further investigation showed that the disk is full and in particular the
/var/log directory occupied all available space for root. These
particular files are a problem:
sys.log is 1.7 GB
kern.log is 1.6 GB
messages are 700 mb
copies are available if needed.
Dmesg is attached.
Binary package hint: sreadahead
This is a tracking bug to improve performance on HDD disks, especially
the really slow ones where sreadahead and the kernel have a deathmatch
Binary package hint: ubiquity
This was an OEM preseeded installation using the preseed located at
http://linux.dell.com/git/?p=ubuntu-
fid.git;a=blob;f=framework/preseed/dell.seed;h=48677d853e9f0dc37dee95329f54f0a771531ea5;hb=HEAD
and the Ubuntu 9.10 gold DVD. For the user name in OEM config, it was
selected to be "test".
test@test-laptop:~$ sudo ifconfig eth0 down
sudo: unable to resolve host test-laptop
"Incomplete Language Support" is still shown when a DVD installation is preseeded with ALL
TEST CASE:
Preseed d-i pkgsel/language-packs string ALL. On reboot after installation, you should not see the "Incomplete Language Support" message.
Original report follows:
Binary package hint: ubiquity
Using the gold Ubuntu 9.10 media and the preseed " d-i pkgsel/language-
packs string ALL", the note
/var/lib/update-notifier/user.d/incomplete-language-support-gnome.note
is created causing this error to show on the first boot.
Binary package hint: update-manager
TEST CASE:
1. define a proxy server somewhere (gconf, apt.conf, synaptic)
2.use iptables to disallow access to port 80
3. run update-manager and click on the "upgrade" button
4. verify that the upgrade hangs
4. install update-manager from jaunty-proposed
5. repeat step 3
6. verify that it now continues
When updating to 9.10 from from 9.04, the update-manager uses a utility
function called "UpdateManager.Core.utils.url_downloadable". This
function skips urllib2 - which is properly configured to use the proxy
settings - and instead directly interacts with httplib, which requires
the caller to properly set up the request in order to use the proxy.
Changing the url_downloadable function to use the proxy resolves the
issue.
Specifically, I after:
if scheme == "http":
import httplib
try:
I added:
proxy = os.getenv('http_proxy')
if (proxy):
path = scheme + netloc + path
netloc = proxy
This resolved the problem. This, however, isn't really a fix - it relies
on the fact that init_proxy sets the http_proxy environment variable and
ignores anything else that might set up urllib2 to properly use a proxy
server.
Binary package hint: sreadahead
This is a tracking bug to improve performance on HDD disks, especially
the really slow ones where sreadahead and the kernel have a deathmatch
Rename /etc/X11/Xsession.d/60x11-localhost to match convention
Binary package hint: xorg
There seems to be a mostly-upheld naming convention that files in
/etc/X11/Xsession.d/ should be named as NNpackagename[_suffix]. All of
the other Xsession.d files installed by x11-common follow this
convention, but the new 60x11-localhost added today does not. It
probably should.
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: x11-common 1:7.4~5ubuntu15
PackageArchitecture: all
ProcEnviron:
LC_COLLATE=C
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-8-generic (buildd@yellow) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu1) ) #28-Ubuntu SMP Fri Mar 6 00:09:20 UTC 2009
SourcePackage: xorg
Uname: Linux 2.6.28-8-generic x86_64
New gdm does not have the FailsafeXServer config option
Binary package hint: gdm
gdm 2.20 had options in /etc/gdm/gdm.conf (in particular
FailsafeXServer) for specifying an action to take when X is failing to
start up. We attached a failsafe session (aka bulletproof-x) to be
invoked by gdm in these situations, which users could use to diagnose
and work around issues.
These options were implemented in the 'deal_with_x_crashes()' function
in gdm.c. Near as I can tell, this gdm feature was not included in the
new gdm rewrite, so we are seeing a regression here. The problem is
that whereas in the past the user would be dumped into a debugging
session, now gdm is simply trying multiple times, failing each time, and
then exiting (which then leads to the quite severe bug 441638).
Anyway, the end result is that we no longer have a debugging failsafe
mode available for users, they're just left with a non-functioning
system. Please either restore the missing functionality, or provide an
analogous mechanism to which we can attach a debugging session mode.
Binary package hint: evolution
I didn't actually do anything - Evolution mail viewer was open on a mail
message with a lot of large embedded images for about an hour and then
it crashed, so I doubt it has anything to do with the content of the
message
ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/evolution
NonfreeKernelModules: nvidia
Package: evolution 2.26.0-0ubuntu4
ProcCmdline: evolution --component=mail
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: evolution
StacktraceTop:
strcmp () from /lib/libc.so.6
g_str_equal () from /usr/lib/libglib-2.0.so.0
org_gnome_mail_new_notify ()
?? () from /usr/lib/evolution/2.26/libeutil.so.0
e_event_emit ()
Title: evolution crashed with SIGSEGV in strcmp()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare vboxusers
Binary package hint: linux-source-2.6.24
The system locks-up completely at random intervals.
The crash can be triggered by downloading mail with Thunderbird, but happens at any other activity after some random time.
No magic SysRq keys works, and there's nothing in the logs...
It's a 2.6.24-17-generic kernel, but the crash also happens with -16.
Everthing was fine with Gutsy on the same machine.
Booting with acpi=off makes the system work stable,
but acpi=noirq, acpi=ht, acpi=strict, noapic, nolapic, pci=noacpi don't help.
How to debug further ?
scanlogic SL11R USB device won't work with 2.6.27-11 kernel
SRU justification:
Impact: We have an -updates regression for the ScanLogic SL11R-IDE USB
disk. This device worked normally up to 2.6.27-11 kernel where it
regressed.
Fix: Add the required quirk for this device to the unusual devices list.
This has been tested by the device owner and reported to fix the
regression.
---
Using Ubuntu 8.10 with latest kernel 2.6.27-11.
my "Transcend USB Card Reader" does no longer work with this kernel. with the previous kernel 2.6.27-9 everything is ok.
lsusb reports the device as (using kernel 2.6.27-9)
Bus 003 Device 003: ID 04ce:0002 ScanLogic Corp. SL11R-IDE IDE Bridge
with kernel 2.6.27-11 i will get these messages in /var/log/messages, and the device cannot be accessed.
Feb 23 08:18:36 birte kernel: [ 184.799043] USB Mass Storage support registered.
Feb 23 08:18:41 birte kernel: [ 189.854649] scsi scan: INQUIRY result too short (5), using 36
Feb 23 08:18:41 birte kernel: [ 189.854667] scsi 6:0:0:0: Direct-Access CYPRESS SM-CF 0.78 PQ: 0 ANSI: 0
Feb 23 08:18:41 birte kernel: [ 189.904617] scsi scan: INQUIRY result too short (5), using 36
Feb 23 08:18:41 birte kernel: [ 189.904629] scsi 6:0:0:1: Direct-Access CYPRESS SM-CF 0.78 PQ: 0 ANSI: 0
Feb 23 08:18:41 birte kernel: [ 189.944676] sd 6:0:0:0: [sdc] Attached SCSI removable disk
Feb 23 08:18:41 birte kernel: [ 189.946842] sd 6:0:0:0: Attached scsi generic sg3 type 0
Feb 23 08:18:41 birte kernel: [ 189.999577] sd 6:0:0:1: [sdd] Unit Not Ready
Feb 23 08:18:41 birte kernel: [ 189.999590] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
Feb 23 08:18:41 birte kernel: [ 189.999599] sd 6:0:0:1: [sdd] Add. Sense: No additional sense information
Feb 23 08:18:42 birte kernel: [ 190.491616] sd 6:0:0:1: [sdd] 2001889 512-byte hardware sectors (1025 MB)
Feb 23 08:18:42 birte kernel: [ 190.507596] sd 6:0:0:1: [sdd] Write Protect is off
Feb 23 08:18:42 birte kernel: [ 190.569627] sd 6:0:0:1: [sdd] 2001889 512-byte hardware sectors (1025 MB)
Feb 23 08:18:42 birte kernel: [ 190.585625] sd 6:0:0:1: [sdd] Write Protect is off
Feb 23 08:18:42 birte kernel: [ 190.587855] sdd: sdd1
Feb 23 08:18:42 birte kernel: [ 190.629753] sd 6:0:0:1: [sdd] Attached SCSI removable disk
Feb 23 08:18:42 birte kernel: [ 190.631462] sd 6:0:0:1: Attached scsi generic sg4 type 0
Feb 23 08:18:42 birte kernel: [ 190.815572] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
Feb 23 08:18:42 birte kernel: [ 190.815592] sd 6:0:0:1: [sdd] Add. Sense: No additional sense information
Feb 23 08:18:42 birte kernel: [ 190.827561] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
Feb 23 08:18:42 birte kernel: [ 190.827575] sd 6:0:0:1: [sdd] Add. Sense: No additional sense information
Feb 23 08:18:42 birte kernel: [ 190.839581] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
Feb 23 08:18:42 birte kernel: [ 190.839598] sd 6:0:0:1: [sdd] Add. Sense: No additional sense information
Feb 23 08:18:42 birte kernel: [ 190.851585] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
Feb 23 08:18:42 birte kernel: [ 190.851602] sd 6:0:0:1: [sdd] Add. Sense: No additional sense information
Feb 23 08:18:42 birte kernel: [ 190.863581] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
Feb 23 08:18:42 birte kernel: [ 190.863596] sd 6:0:0:1: [sdd] Add. Sense: No additional sense information
Feb 23 08:18:42 birte kernel: [ 190.875581] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
Feb 23 08:18:42 birte kernel: [ 190.875594] sd 6:0:0:1: [sdd] Add. Sense: No additional sense information
Feb 23 08:18:42 birte kernel: [ 190.887581] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
Feb 23 08:18:42 birte kernel: [ 190.887595] sd 6:0:0:1: [sdd] Add. Sense: No additional sense information
Feb 23 08:18:42 birte kernel: [ 190.899583] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
Feb 23 08:18:42 birte kernel: [ 190.899599] sd 6:0:0:1: [sdd] Add. Sense: No additional sense information
Feb 23 08:18:42 birte kernel: [ 190.911582] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
F
[RS482] low performance due to removal of _tnl_ProgramCacheInit()
[Problem]
Performance regression on Xpress 200M for Jaunty.
[Impact]
Affects users of older R300-based chipsets, causing a performance regression which can make the system unusable in some situations.
[Development Solution]
The proposed patch to solve this is present upstream and has been included in Ubuntu Karmic for some time now with no ill effect.
[Patch]
Minimal patch which is confirmed by 5 users to improve performance with no side effects not already present with existing code:
http://launchpadlibrarian.net/27634168/r300_context_tnlcache_fix.patch
[Reproduction]
With affected hardware, run a GL application such as Neverball. Note the rendering performance and cpu utilization. With patch applied, rendering will be faster and cpu usage lower.
[Regression Potential]
The patch only affects code that is invoked on R300-class hardware, so any regression this could cause will be limited in scope to a narrow subset of users.
Comment #22 indicates that upstream feels there may be some risk of
freeze issues with this patch, however this has not been seen in testing
so far. If the freeze can be reproduced by anyone, then this patch
should not go in, since a freeze regression would be more severe than a
performance regression.
Five people have tested this patch so far. It would be more comfortable
seeing this patch tested more widely, but this may be the limit of what
can be expected with just PPA testing. It is recommended that ample
time be given for testing this patch before putting into -updates.
[Original Report]
My Xpress 200M is almost dead after I upgraded the system to Ubuntu 9.04.
glxgears:
1256 frames in 5.0 seconds = 251.181 FPS
1224 frames in 5.0 seconds = 244.754 FPS
1673 frames in 5.0 seconds = 334.345 FPS
1610 frames in 5.0 seconds = 321.985 FPS
I had above 1100 FPS in 8.10. I deleted the old xorg.conf - did not help. Then did dpkg-reconfigure xserver-xorg - no improvements. I do not see errors in Xorg.log. Everything is working (compiz, some games) but very slow.
I believe that something is wrong with the card detection:
radeontool --debug
Found card 1002:5955 (30000)
(unknown card)
Radeon found. Base control address is b80b2000; base framebuffer address is a7f2d000.
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: xserver-xorg-video-ati 1:6.12.1-0ubuntu1
ProcEnviron:
SHELL=/bin/bash
LANG=ru_RU.UTF-8
ProcVersion: Linux version 2.6.28-11-generic (buildd@rothera) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #36-Ubuntu SMP Fri Mar 20 19:40:40 UTC 2009
SourcePackage: xserver-xorg-video-ati
Uname: Linux 2.6.28-11-generic i686
[lspci]
00:00.0 Host bridge [0600]: ATI Technologies Inc RS480 Host Bridge [1002:5950] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:30a4]
01:05.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon XPRESS 200M 5955 (PCIE) [1002:5955]
Subsystem: Hewlett-Packard Company Device [103c:30a4]
Binary package hint: nut
Ubuntu release: 9.04
Package: nut 2.4.1-2ubuntu4
When checking the status of nut with
/etc/init.d/nut status
the script gave the output
Checking status of Network UPS Tools
* upsd is not running
* upsmon is not running
even though both upsd and upsmon were indeed running as shown by the ps
command.
I did some digging through the nut init script and found what I believe
to be the problem. The script calls a function status_of_proc as
follows:
status_of_proc "$DESC" upsd
The first argument to that function should be the full pathname of the
daemon. I recommend changing the above line to:
status_of_proc $upsd upsd
Two other uses of the status_of_proc function in the init script
regarding upsmon should be changed in a likewise manner.
Cheers,
Clyde
======
SRU Verification:
1. Install nut
2. Run the /etc/init.d/nut status script
3. Check to see if its running by comparing the output of ps auxwww | grep nut
Note: You should have a UPS to test this with.
jaunty SRU information follows:
Note that this SRU involves two separate bugs, this one and bug 326532.
Impact: Users who experience problems with PulseAudio often kill it
(using "pulseaudio -k" or "killall pulseaudio", the latter of which is
more reliable). Jaunty's current pm-utils sleep hook looks for the
session-invoked command line. Users who invoke pulseaudio manually,
after killing it, with "pulseaudio -D" (or other variants) do not have
this session-invoked command line, and thus, when they suspend to ram or
disk, the pm-utils sleep hook does not suspend their pulseaudio daemons.
Note that the use case of killing the pulseaudio daemon and allowing it
to autospawn afterward is unaffected; jaunty's existing pm-utils sleep
hook correctly reaps all pulseaudio instances. This SRU only applies to
manually invoked "pulseaudio -D", "pulseaudio -vvv", etc.
Resolution: Modify the pm-utils sleep hook to correctly reap all
pulseaudio instances regardless of pulseaudio invocation command line.
SRU debdiff:
http://launchpadlibrarian.net/25941550/pulseaudio_0.9.14-0ubuntu20.1.debdiff
TEST CASE: Boot into a jaunty install. In a Terminal, issue "killall
pulseaudio;pulseaudio -D". Suspend to ram, then resume. Note the
inaudible audio from PulseAudio.
Regression potential: No regressions have been identified in production.
--
old intrepid SRU information follows:
Impact: A portion of users with a default or updated (intrepid-updates)
Ubuntu 8.10 install experience inaudible audio from PulseAudio after
resuming from suspend-to-ram. This symptom is due to the PulseAudio
daemon not having received proper notification to suspend clients and
release the sound device(s).
Resolution: Configure users' pulseaudio daemons to suspend prior to
suspending to ram and to resume after resuming. This sequence is
accomplished via a pm-utils sleep hook. The corresponding fixed version
(0.9.13-2ubuntu3) is available in jaunty.
SRU debdiff:
http://launchpadlibrarian.net/20316781/pulseaudio_0.9.10-2ubuntu9.2.debdiff
TEST CASE: Boot into a default or updated (intrepid-updates) Ubuntu 8.10
install. Suspend to ram, then resume. Note the inaudible audio from
PulseAudio.
Regression potential: No regressions have been identified in production.
Background information follows:
Binary package hint: pulseaudio
> aplay squish.au
Sonando Audio Sparc 'squish.au' : Mu-Law, Ratio 8000 Hz, Mono
[Suspend to Ram/Resume]
> aplay squish.au
ALSA lib pcm_dmix.c:874:(snd_pcm_dmix_open) unable to open slave
aplay: main:546: error al abrir audio: Dispositivo ó recurso ocupado
Then you need to killall pulseaudio for apps that use pcm starts working again.
(Question: How you can stop/start/restart pulseudio? In Ubuntu /etc/init.d/pulseaudio script is disabled)
If you need more information, please let me know.
Thx.
----------------------------------
Hardy Uptodate
IBM Thinkpad X41 Tablet
pulseaudio 0.9.9-1ubuntu2
[jaunty] Pulseaudio does not start "Failed to open module "module-console-kit": file not found"
jaunty SRU information follows:
Note that this SRU involves two separate bugs, this one and bug 202089.
Impact: Users who perform a distribution upgrade to jaunty sometimes
fail to have audible sound through PulseAudio due to its failure to load
libdbus-util.so. This failure stems from pulseaudio's missing dependency
on the pulseaudio-module-hal package, which contains libdbus-util.so.
Instead, it is a Recommends.
Resolution: Promote pulseaudio-module-hal from a recommendation to a
dependency of the pulseaudio package.
SRU debdiff:
http://launchpadlibrarian.net/25941550/pulseaudio_0.9.14-0ubuntu20.1.debdiff
TEST CASE: Perform a distribution upgrade from intrepid to jaunty. If
the audio from PulseAudio is inaudible, "killall pulseaudio; strace
pulseaudio -v". If "open("/usr/lib/pulse-0.9/modules/libdbus-util.so",
O_RDONLY) = -1 ENOENT (No such file or directory)" appears, then the
symptom has been reproduced.
Regression potential: No regressions have been identified in production.
--
Background information follows:
Binary package hint: pulseaudio
In Jaunty (with latest updates for Sat Feb 7th installed) the pulseaudio
daemon fails to start.
The output I get is:
I: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
I: caps.c: Dropping root privileges.
I: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
N: main.c: Called SUID root and real-time and/or high-priority scheduling was requested in the configuration. However, we lack the necessary privileges:
N: main.c: We are not in group 'pulse-rt', PolicyKit refuse to grant us the requested privileges and we have no increase RLIMIT_NICE/RLIMIT_RTPRIO resource limits.
N: main.c: For enabling real-time/high-priority scheduling please acquire the appropriate PolicyKit privileges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user.
E: module.c: Failed to open module "module-console-kit": file not found
E: main.c: Module load failed.
E: main.c: Failed to initialize daemon.
Binary package hint: update-manager
TEST CASE:
1. define a proxy server somewhere (gconf, apt.conf, synaptic)
2.use iptables to disallow access to port 80
3. run update-manager and click on the "upgrade" button
4. verify that the upgrade hangs
4. install update-manager from jaunty-proposed
5. repeat step 3
6. verify that it now continues
When updating to 9.10 from from 9.04, the update-manager uses a utility
function called "UpdateManager.Core.utils.url_downloadable". This
function skips urllib2 - which is properly configured to use the proxy
settings - and instead directly interacts with httplib, which requires
the caller to properly set up the request in order to use the proxy.
Changing the url_downloadable function to use the proxy resolves the
issue.
Specifically, I after:
if scheme == "http":
import httplib
try:
I added:
proxy = os.getenv('http_proxy')
if (proxy):
path = scheme + netloc + path
netloc = proxy
This resolved the problem. This, however, isn't really a fix - it relies
on the fact that init_proxy sets the http_proxy environment variable and
ignores anything else that might set up urllib2 to properly use a proxy
server.
klamav update dies unexpectedly in intrepid with apparmor active
I ran into a problem with updating klamav this morning (freshly installed Intrepid Ibex/8.10):
"the update process died unexpectedly. did you kill it?"
Running 'dmesg' unearths a problem with apparmor premissions (freshclam
has no read/write permission in /tmp):
[25847.394171] type=1503 audit(1229981927.656:28):
operation="inode_permission" requested_mask="r::" denied_mask="r::"
fsuid=1000 name="/tmp/kde-peter/klamavwGmkJa.tmp" pid=6960
profile="/usr/bin/freshclam"
Adding the following line in '/etc/apparmor.d/usr.bin.freshclam' (just before the closing curly brace) fixed it:
/tmp/** rw,
Cheers, Peter
Binary package hint: clamav
The freshclam command cannot be run by anyone other than root while
apparmor is enabled. So long as freshclam is given writable directories,
it should be able to be run by anyone, like so:
freshclam --log=/home/user --datadir=/home/user
Shutting down apparmor (sudo /etc/init.d/apparmor stop) enables this to
work as it should.
Distro: Ubuntu 8.10
Executable path: /usr/bin/freshclam
SourcePackage: clamav
apparmor denies freshclam access to /var/run/samba/gencache.tdb
Binary package hint: clamav
My /var/log/syslog gets this message every time when freshclam does an
update:
Mar 21 04:14:53 fs1 kernel: [550646.547458] type=1503
audit(1237634093.495:59): operation="inode_permission"
requested_mask="::r" denied_mask="::r" fsuid=5000
name="/var/run/samba/gencache.tdb" pid=6451 profile="/usr/bin/freshclam"
Why freshclam tries to read samba gencache.tdb in the first place?
My guess it may have to do with Samba setup as PDC which uses winbind and modified nsswitch.conf.
# /etc/nsswitch.conf
passwd: files ldap [UNAVAIL=return]
group: files ldap [UNAVAIL=return]
shadow: files ldap [UNAVAIL=return]
hosts: files wins mdns4_minimal [NOTFOUND=return] dns mdns4
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
#/etc/nsswitch.conf (END)
But there is no other package that goes to gencache.tdb directly, at least not from apparmor perspective.
Versions:
Ubuntu 8.10
clamav 0.94.dfsg.2-1ubuntu0.1
clamav-freshclam 0.94.dfsg.2-1ubuntu0.1
apparmor 2.3+1289-0ubuntu4.1
samba 2:3.2.3-1ubuntu3.4
winbind 2:3.2.3-1ubuntu3.4
After upgrading to Intrepid from Hardy on PPC, I cannot print anymore.
I've got a Brother HL-1430 laserjet printer using the recommended PPD.
The "data" LED of the printer blinks for a second, and then shuts off
again.
If I try with the test page, it comes off blank, or with some grey
squares (but in Hardy it came with the Ubuntu logo and all).
For example, trying "man -Tps printf | lpr" doesn't print anything; nor
it works from any other application (e.g. a PDF in evince). The queue is
always empty when using PS files, else when printing PDFs from evince it
stays in queue indefinitely.
In response to what I send to the printer, looking at the logs, I can
see:
D [17/Sep/2008:15:22:01 +0200] PID 8428 (/usr/lib/cups/filter/pstopdf) exited with no errors.
D [17/Sep/2008:15:22:01 +0200] [Job 27] GhostScript: **** Warning: An error occurred while reading an XREF table.
D [17/Sep/2008:15:22:01 +0200] [Job 27] GhostScript: **** The file has been damaged. This may have been caused
D [17/Sep/2008:15:22:01 +0200] [Job 27] GhostScript: **** by a problem while converting or transfering the file.
D [17/Sep/2008:15:22:01 +0200] [Job 27] GhostScript: **** Ghostscript will attempt to recover the data.
D [17/Sep/2008:15:22:01 +0200] [Job 27]
D [17/Sep/2008:15:22:01 +0200] [Job 27] Closing foomatic-rip.
D [17/Sep/2008:15:22:01 +0200] [Job 27] Read 1 bytes of print data...
I'm attaching the cups error_log.
Quite severe in importance, imho. This is a machine shared by a lot of users, so none of them can print as long as this lasts.
ii cups 1.3.8-11 Common UNIX Printing System(tm) - server
ii foomatic-db 20080916-0ubuntu1 OpenPrinting printer support - database
The Landscape Team has proposed an SRU to solve this bug.
Statement explaining the impact
=====================
It's possible to have a client machine in a situation where landscape
itself is using a proxy, but not smart. In networks where the only way
out is via a proxy, this means that that machine would never be able to
perform package operations, nor report the packages it has installed and
available.
Even if smart checks the http_proxy env var, it's entirely possible the
admin didn't set it. A contributing factor is that the landscape-config
wizard explicitly asks for a proxy, so it's not unreasonable for the
admin to assume smart would be setup too.
How the bug has been addressed
======================
Introducing a new smart plugin that inherits the proxy settings from the
landscape-client configuration file.
Detailed instructions how to reproduce the bug
==============================
Simply install landscape-client in an environment using a proxy.
linux-image-2.6.20-16 fails to detect twin usb gamepad
Binary package hint: linux-source-2.6.20
This bug is very similar to bug #106622 reported by Paul Zaremba, but
affects a different device.
I have a Personal Communications Systems, Inc. (Vendor ID 0x0810) Twin
USB Gamepad (Product ID 0x0002).
As detailed in Paul's bug report, the two controllers were muxed
together as one. Adding the vendor and product IDs to drivers/usb/input
/hid-core.c, and setting the "multi input" quirk produced the correct
behaviour.
Unfortunately I'm a bit over my head here, and I don't know how to write
a patch. Have I provided enough information?
Sorry if this is a duplicate of Paul's bug, I wasn't sure. It's the
same basic problem, but with a different product.
Thanks,
Rory
PS, here's the output of lsusb -v:
Bus 003 Device 003: ID 0810:0002 Personal Communication Systems, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0810 Personal Communication Systems, Inc.
idProduct 0x0002
bcdDevice 1.06
iManufacturer 0
iProduct 2 Twin USB Gamepad
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 200mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Devices
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 33 US
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 202
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
Device Status: 0x0000
(Bus Powered)
Bluetooth mouse does not re-establish connection after reboot
Summary:
Bluetooth device connections are not re-established after reboot
Steps to Reproduce:
1) Associate a bluetooth mouse to a system using bluetooth device (PCI ID: 0x0a5c2151)
2) Ensure mouse is now working
3) Reboot system
4) Try to use mouse
Expected result:
All trusted device connections are re-established each time the system is booted
Actual result:
Bluetooth mouse is non-functional until it is deleted from Bluetooth Manager and re-added.
This is a public bug on the kernel package corresponding to the private
bug #241749, for SRU tracking.
Hardware: Montevina(HP-prototype-laptop)
Software: Intrepid-beta-x86
Steps to reproduce:
Click "System-->shutdown...-->Suspend" of Gnome Desktop.Expect the system become S3 status(suspend),but a Login-Window appeared at once after clicking,with screen power on still.
Clicking "System-->shutdown...-->Hibernate" also reproduce the bug.
More debug informations are in attachment.
atl1e.ko missing in initrd, causes kernel panic on thin clients
Binary package hint: initramfs-tools
The atl1e.ko (Attansic Technology Gigabit Ethernet) module is missing in
the default initrd although it's present on an installed system in
/lib/modules/2.6.27-7-generic/kernel/drivers/net/atl1e/
This chipset is present in the latest Asus EEE that we are trying to use
as thin clients, that missing module make them to kernel panic (unable
to mount /) when trying to mount / from the network.
Is there a good reason for it not to be included in the initrd or is
that just a bug of whatever chooses what to put in the initrd ?
Adding it to /etc/initramfs-tools/modules and rebuilding the initrd
fixes the issue but I'd prefer not to have to do that.
Reboot stalls after installing Intrepid from alternate on a Dell Optiplex 330
After installing Intrepid from alternate on a Dell Optiplex 330, the
system seems to stall at the end of powering off. This was apparently
fixed recently to workaround having to use the kernel parameter
reboot=b.
[SRU] Net-SNMP tries to read the obsolete /etc/sensors.conf
Using snmpd_5.4.1~dfsg-4ubuntu2_i386
The command
snmpwalk localhost lmSensors
displays this output:
LM-SENSORS-MIB::lmSensors = No Such Object available on this agent at this OID
strace'ing snmpd -f -Le -Ducd-snmp/lmSensors shows this:
...
time(NULL) = 1203281780
open("/etc/sensors.conf", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
write(2, "=> sensor_init\n", 15=> sensor_init
...
Creating a symlink /etc/sensors3.conf -> /etc/sensors.conf fixes this
problem.
Binary package hint: snmpd
Ubuntu 8.04.1
snmpd 5.4.1~dfsg-4ubuntu4
snmpd 5.4.1 needs to be updated to 5.4.2 to get rid of these errors in
syslog:
snmpd[27689]: error getting netmask for interface 2
Syslog fills with hundreds of these errors if you have a network
interface, e.g. eth2, with no IP address, but you have an alias,
e.g. eth2:1, that does have an IP address (and netmask).
Please pull down the patched version 5.4.2 from upstream?
Or perhaps you can point me at a package repository that has a patched version?
ProblemType: Bug
Architecture: i386
Date: Mon Sep 15 19:46:56 2008
DistroRelease: Ubuntu 8.04
Package: snmpd 5.4.1~dfsg-4ubuntu4
PackageArchitecture: i386
ProcEnviron:
SHELL=/bin/bash
PATH=/home/idallen/bin86:/home/idallen/bin:/usr/local/bin:/usr/local/sbin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LC_COLLATE=C
LANG=C
LC_CTYPE=en_CA.utf8
SourcePackage: net-snmp
Uname: Linux 2.6.24-19-generic i686
Trying to use COUNTER64 in NetSNMP::agent doesn't work. This is a long-
standing bug that has been fixed in SVN for 5.2.x, 5.3.x, 5.4.x and
trunk last year.
I noticed this bug a while ago (it was already reported to net-snmp) and
worked around it by using normal counters. Now it's fixed I'd like to
use them to test some counter-specific functions. It would be awesome if
the patch could get trough normal updates.
Note that Perl do not support 64bit integers ("long long" in C) out of
the box, but Math::Int64 do and the value can be safely passed to
NetSNMP::agent as a string.
See:
http://sourceforge.net/tracker/index.php?func=detail&aid=2022948&group_id=12694&atid=312694
http://net-snmp.svn.sourceforge.net/viewvc/net-snmp?view=rev&revision=17246
I attached the patch for the 5.4.x branch from SVN - from this URL:
http://net-snmp.svn.sourceforge.net/viewvc/net-snmp/branches/V5-4-patches/net-snmp/perl/agent/agent.xs?view=patch&r1=17246&r2=17245&pathrev=17246
Alternate CD cdrom-detect.postinst does not consider USB flash drive/key.
We have had support for USB devices that contain the contents of an ISO
being used as installation media for the alternate CD since Intrepid.
Recently it has come to my attention that server users want this feature
for servers that do not have a CDROM drive and are not installed using
PXE.
I've uploaded a new debian-installer-utils and cdrom-detect to hardy-
proposed which will enable the following test case.
TEST CASE:
1. Put the contents of an Ubuntu 8.04.4 image on a USB disk using usb-creator. Other tools can be used to do this, but you need to make sure you add 'cdrom-detect/try-usb=true' to the kernel command line.
2. Boot the USB disk and proceed with the installation. It should progress without complaining that it cannot find the installation media.
Original report:
I wrote a script to copy all the files from Hardy Heron (08.04) Live CD and Alternate CD to a USB flash drive. The Live CD works flawlessly.
However, the Alternate CD fails to mount the "cdrom". This is because
cdrom-detect.postinst does not try to look for disk partitions.
By adding `list-devices partition` in the list of devices to probe, and
by adding an additional mount command for vfat, I managed to get the
Alternate CD working from a USB flash drive.
Attached, a patch to fix the issue. Please consider introducing this
fix soon and release a new Alternate CD with it. I plan to make my
script available and it would be nice to have a proper working Alternate
CD for USB flash drives. Users should not have to mess with initrd to
get this working.
P.S.: If you have a suggestion about a good place to make this script
public, please write to me in an email.
Also, my solution partially resolves:
http://brainstorm.ubuntu.com/idea/16/
I have USB images of 1G which can be `dd` to a USB flash drive.
[ keywords: alternate cd usb flash key stick pen pendrive drive ]
Alternate CD cdrom-detect.postinst does not consider USB flash drive/key.
We have had support for USB devices that contain the contents of an ISO
being used as installation media for the alternate CD since Intrepid.
Recently it has come to my attention that server users want this feature
for servers that do not have a CDROM drive and are not installed using
PXE.
I've uploaded a new debian-installer-utils and cdrom-detect to hardy-
proposed which will enable the following test case.
TEST CASE:
1. Put the contents of an Ubuntu 8.04.4 image on a USB disk using usb-creator. Other tools can be used to do this, but you need to make sure you add 'cdrom-detect/try-usb=true' to the kernel command line.
2. Boot the USB disk and proceed with the installation. It should progress without complaining that it cannot find the installation media.
Original report:
I wrote a script to copy all the files from Hardy Heron (08.04) Live CD and Alternate CD to a USB flash drive. The Live CD works flawlessly.
However, the Alternate CD fails to mount the "cdrom". This is because
cdrom-detect.postinst does not try to look for disk partitions.
By adding `list-devices partition` in the list of devices to probe, and
by adding an additional mount command for vfat, I managed to get the
Alternate CD working from a USB flash drive.
Attached, a patch to fix the issue. Please consider introducing this
fix soon and release a new Alternate CD with it. I plan to make my
script available and it would be nice to have a proper working Alternate
CD for USB flash drives. Users should not have to mess with initrd to
get this working.
P.S.: If you have a suggestion about a good place to make this script
public, please write to me in an email.
Also, my solution partially resolves:
http://brainstorm.ubuntu.com/idea/16/
I have USB images of 1G which can be `dd` to a USB flash drive.
[ keywords: alternate cd usb flash key stick pen pendrive drive ]
Binary package hint: kdepim
Renaming a folder via dimap can cause the folder to be deleted.
upstream bug: https://issues.kolab.org/issue3833 "Mails will vanish, if
a folder is renamed."
>From upstream:
we recently found and fixed an issue in KMail. Under certain circumstances, it
was possible that mails get deleted from the server after renaming a folder
when using disconnected IMAP.
This is obviously a bad bug, and therefore it would be great if you could
include the patch in your packages, if the version you ship is affected.
Affected versions are:
- 3.5 branch
- enterprise branch
- 4.2 branch
- 4.3 branch
- trunk
The KDE 4.1 branch doesn't seem to be affected.
The patch made it into all affected branches already, here are the revision
numbers of the fixes:
3.5: 1022980, 1022986
enterprise: 1021458, 1021464
4.2: 1022968, 1022978
4.3: 1022963, 1022964
trunk: 1022953, 1022954
[MASTER] firefox-3.0b5 received an X Window System error: 'BadIDChoice'
Binary package hint: firefox-3.0
Starting a few days ago, maybe a week or so, FF3 started crashing randomly,
after 1h or so, usually when there are tens of windows and tabs open. It
probably happened after some update of the X server, come to think of it.
Calling it from a terminal and not from the window manager yields the following
trace:
The program 'firefox' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
(Details: serial 73442980 error_code 14 request_code 153 minor_code 4)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
I am not sure what to do with that? Is firefox the program I should run with
the --sync command line option?
Relevant packages (hardy up-to-date):
ii xserver-xorg 1:7.3+10ubuntu10 the X.Org X server
ii xserver-xorg-core 2:1.4.1~git20080131-1ubuntu9 Xorg X server - core server
ii kdm-kde4 4:4.0.3-0ubuntu2 X display manager for KDE 4
ii firefox-3.0 3.0~b5+nobinonly-0ubuntu3 safe and easy web browser from Mozilla
Tell me what to do to help you investigate this issue.
Performance-related changes made by Debian to libxcb 1.1
Debian has recently made a 1.1-1.2 release of libxcb to stable. Since
Hardy derived from the same version and is LTS, I thought these changes
might be worth also applying to Hardy.
The changelog for 1.1-1.2 reads:
libxcb (1.1-1.2) stable; urgency=low
* Non-maintainer upload to fix important performance issues
(closes: #487635).
* Fix some fd leaks in _xcb_open_*()
* Increase libxcb buffer size to 16k from 4k
* Disable Nagle on TCP socket
-- Julien Cristau <jcristau@debian.org> Wed, 27 May 2009 20:06:47
+0200
If you do make an SRU containing these changes, please also ensure that
the version in ia32-libs is updated.
Applications that use libxcb 1.1 cannot open more than 1024 files
Hi,
We have some internal 32-bit applications that end up with a lot of
files open. If they in turn call a program that links with libxcb, more
often than not, that program segfaults.
This has been determined to be because libxcb uses select() and the man
page for select() says this:
"An fd_set is a fixed size buffer. Executing FD_CLR() or FD_SET()
with a value of fd that is negative or is equal to or larger than
FD_SETSIZE will result in undefined behavior. Moreover, POSIX requires
fd to be a valid file descriptor."
Later versions of libxcb address this by using poll()
I'm attaching the patch that we are using internally against libxcb
1.1-1.1
If you make this SRU, please also ensure that the 32-bit version in
ia32-libs gets updated.
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
On my Samsung NC10 Netbook some FN keys do not work.
Working:
Speaker Off. Volume Control, Sleep Buttom, Mousepad off
Not working:
WLAN off, brightness up/down, LCD off, Battery
Brightness down gives an e009
Brightness up gives ab e008
setkeycodes e009 $KEY_BRIGHTNESSDOWN # Fn+Down
setkeycodes e008 $KEY_BRIGHTNESSUP # Fn+Up
This is working, but gives no button release event, so brightness goes
up 100% or down 0%. And it also blocks the keyboard.
Any ideas on this?
TIA
Andreas
Using intreped X86
[SRU] openvpn2.1~rc7 fails to pick up the CN of certificates
Binary package hint: openvpn
In Ubuntu 8.04.1 the version of openvpn available is 2.1~rc7 which has a
pretty serious bug:
>From a reply to the openvpn mailing list after we were having problems:
"try upgrading to 2.1_rc9 ; in 2.1_rc7 the code to extract a common name
from a certificate DN was broken. v2.1_rc8 and higher reverted back to
the old mechanism, as found in 2.0.9."
This means any attempt to use the ccd feature (different options for
different clients based on the name of the client certificate) will
fail. Our setup involved an inter-LAN vpn; we could not push the
appropriate routes as it couldn't identify the clients properly
Manually upgraded to rc9 and our setup now works
