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
apparmor kernel null dereference when profile is removed after set to complain
SRU Justicication: this bug can cause a null pointer dereference kernel
oops. This will occur any time children profiles are attached to
running processes. This can occur when change_hat, children profiles or
profile learning is used.
Binary package hint: apparmor
Description: Ubuntu 9.10
Release: 9.10
Package: apparmor
System: Linux tehcomputer 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux
The following will cause a null dereference and a "kernel oops".
Steps:
1. Generate an apparmor profile for empathy (I can send my apparmor profile via email)
2. Make sure empathy can load and no messages are reported in audit.
(Make sure gnome-help isn't allowed to execute by keeping it absent from the apparmor profile)
3. Enforce the empathy apparmor profile
4. Load empathy until empathy UI opens
5. Set empathy profile to complain
6. In empathy, click Help->Contents
7. Verify that audit is sending out complain messages as gnome-help opens with empathy help contents
8. Run apparmor_parser -R /etc/init.d/usr.bin.empathy
Result:
1. Nov 4 16:47:21 tehcomputer kern: [76781.229046] BUG: unable to handle kernel NULL pointer dereference at 0000000000000068
[sru] exceptions.AssertionError: second push failed to complete a fetch set
The recipe to reproduce is simply "bzr get lp:~spiv/+junk/u-k" — no
shared repos or anything else involved on the client! The source branch
is stacked on lp:~vcs-imports/gnome-user-docs/master.
----
Binary package hint: bzr
Hi
branching lp:~ubuntu-core-dev/upstart/ubuntu crashes for me with up-to-date karmic bzr packages:
bzr: ERROR: exceptions.AssertionError: second push failed to complete a fetch set([('texts', 'process.c-20060804042848-002ec799c7183356', 'scott@netsplit.com-20090803220543-yqjmdr9pbuj4yqpn'), ('texts', 'process.c-20060804042848-002ec799c7183356', 'scott@netsplit.com-20090716172238-6mjm2rjvfnocynjf'), ('texts', 'main.c-20060516195723-2691e3b471617c66', 'scott@netsplit.com-20090922161534-0p9jjuv3y885t6yh')]).
*** Bazaar has encountered an internal error. This probably indicates a
bug in Bazaar. You can help us fix it by filing a bug report at
https://bugs.launchpad.net/bzr/+filebug
attaching the crash file
/home/lool/.cache/crash/bzr-20090927123208-25137.crash
and including a description of the problem.
The crash file is plain text and you can inspect or edit it to remove
private information.
I'm attaching the crash file; this happens on a second try as well.
Bye
ProblemType: Bug
Architecture: amd64
Date: Sun Sep 27 14:33:04 2009
DistroRelease: Ubuntu 9.10
Package: bzr 2.0.0-0ubuntu1
ProcEnviron:
LANGUAGE=fr_FR:fr:en_GB:en
PATH=(custom, user)
LANG=fr_FR.UTF-8
SHELL=/bin/zsh
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SourcePackage: bzr
Uname: Linux 2.6.31-11-generic x86_64
TEST CASE:
1. use multi-screen system and enable compiz
2. use it a while -> crash
3. install compiz from karmic-proposed
4. verify that after using it a while it does not crash
Binary package hint: compiz
We need an update to fix this bug,
http://git.compiz.org/compiz/core/commit/?h=compiz-0.8&id=24dea72a395071b533dcf66b2eef37b20522cbba
It's causing compiz to crash 5 or 6 times a day on my multi screen
system
Thanks :)
Binary package hint: upstart
Hi,
I am not sure if this bug is more cryptdisk releated, maybe you can decide when you read the provided solution.
My startup process needs both stages of the cryptdisk scripts. In the
first step (stage early) a /dev/mapper/ entry is created for an USB
Stick asking for a password. On this stick resides all keys for the
second step.
The two step mechanism is not processed by the new upstart script in /etc/init/cryptdisks-enable.conf
Please change /etc/init/cryptdisks-enable.conf:
...
esac
INITSTATE="init"
do_start
end script
to
...
esac
INITSTATE="early"
do_start
INITSTATE="init"
do_start
end script
The second problem is a timing problem. If the Stick is not mounted fast
enough the system fails to read some keys. When this happens the system
hangs completly. I think this might be, because this partitions are
marked as auto in /etc/fstab. If tey don't come up the upstart process
waits endless.
To overcome this I changed /lib/cryptsetup/cryptdisks.functions.
Please change /lib/cryptsetup/cryptdisks.functions:
do_start () {
local dst src key opts result
modprobe -qb dm-mod || true
modprobe -qb dm-crypt || true
dmsetup mknodes > /dev/null 2>&1 || true
log_action_begin_msg "Starting $INITSTATE crypto disks"
mount_fs
...
to
do_start () {
local dst src key opts result
modprobe -qb dm-mod || true
modprobe -qb dm-crypt || true
dmsetup mknodes > /dev/null 2>&1 || true
log_action_begin_msg "Starting $INITSTATE crypto disks"
mount_fs
sleep 1
...
Finally I deleted both symlinks /etc/rcS.d/S26cryptdisks-early and /etc/rcS.d/S28cryptdisks
Hope this helps cheers,
Christoph
ProblemType: Bug
Architecture: i386
Date: Mon Oct 5 21:51:47 2009
DistroRelease: Ubuntu 9.10
Package: upstart 0.6.3-7
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: upstart
Uname: Linux 2.6.31-11-generic i686
XsessionErrors:
(nautilus:5989): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
(polkit-gnome-authentication-agent-1:6001): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
I hope that the tilte is correct.
I have encrypted a sdcard using cryptsetup.
During the boot sequence, it does not ask for the password. I fail to find an error message in the logs.
I think my config is ok because /etc/init.d/cryptdisks start does work:
* Starting remaining crypto disks...
* data (starting)
Enter passphrase to unlock the disk /dev/mmcblk0p1 (data):
(I enter the password)
key slot 0 unlocked.
Command successful.
data (started)... [ OK ]
and then, "mount -a" mounts the encrypted partition.
It looks like cryptsetup starts *before* /dev/mmcblk0p1 is created.
That would explain why cryptsetup fails to see my encrypted disk at boot time.
My config files:
crypttab:
# <target name> <source device> <key file> <options>
data /dev/mmcblk0p1 none luks
fstab:
/dev/mapper/data /home/gnata/data ext4 defaults 0 1
TEST CASE:
1. install the cryptsetup package from karmic
2. Configure a device that will be slow to be initialized by the kernel, such as a USB drive or an SD card, to be used with cryptsetup by running commands such as this:
cryptsetup luksFormat /dev/mmcblk0p1
cryptsetup luksOpen /dev/mmcblk0p1 slowdisk
mkfs.ext4 /dev/mapper/slowdisk
3. Set the device up to be decrypted at boot time by adding a line such as this to /etc/crypttab:
slowdisk /dev/mmcblk0p1 none luks
4. Set the device up to be mounted at boot time by adding a line such as this to /etc/fstab:
/dev/mapper/slowdisk /mnt ext4 defaults,bootwait 0 0
5. reboot a few times (in single user mode, to prevent gdm from starting and killing usplash); verify that the passphrase prompt for decrypting this disk is racy, and does not always appear
6. install the cryptsetup package from karmic-proposed
7. reboot a few times (in single user mode, again); verify that the passphrase prompt now appears reliably.
REGRESSION POTENTIAL:
With this change cryptsetup will no longer be racing udev; however, cryptsetup instances *will* be racing each other. In the unlikely case that a user has CRYPTDISKS_MOUNT set to a non-empty value in /etc/default/cryptdisks, *and* has more than one volume configured in /etc/crypttab, the upstart jobs can race each other and one job can unmount the filesystems before the other job has a chance to use them. However, even in this case the cryptdisks-enable catch-all job should still take care of it, unless the second failed decrypt job then unmounts the filesystem when cryptdisks-enable needs it (a double race).
This change also increases the chance that a filesystem not marked as
'bootwait' in /etc/fstab will get in a race with gdm at boot time,
leading to the passphrase prompt being masked by X, or cryptsetup
fighting X for control of the console. However, that class of race is
already present in karmic and documented in the release notes, so I
don't think this should be a blocker for SRU.
cryptsetup init scripts are redundant and can break the boot
Binary package hint: cryptsetup
The cryptsetup package in karmic includes both init scripts and an
upstart job. The init scripts should be completely redundant, because
the upstart job is written such that it will start all crypted volumes
listed in /etc/crypttab that aren't marked with 'noauto'. And there
have been reports of regressions in 9.10 as a result of these init
scripts being present (reported on bug #430496), due to adverse
interaction between the init script (rcS runs with 'console owner') and
gdm. Removing the init scripts should resolve these hangs, because the
cryptsetup job only requires 'console output', not 'console owner', so
doesn't compete with X for control of the VT.
However, this change is not without risk of regression, because the
upstart job (and the init scripts as well) will skip over any devices
that aren't yet available at the time it's called. The job waits for
udevtrigger to finish, but that doesn't guarantee that all disks have
been detected, so any disks that arrive later won't be decrypted for
use. So both before and after, this is racy... after, the odds of
running into problems because of the race are greater.
ProblemType: Bug
Architecture: amd64
Date: Tue Nov 3 04:07:39 2009
DistroRelease: Ubuntu 9.10
Package: cryptsetup 2:1.0.6+20090405.svn49-1ubuntu7
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48+ureadahead2-generic
SourcePackage: cryptsetup
Uname: Linux 2.6.31-14-generic x86_64
ec2-init selects us-east-1 mirror when running in us-west-1 region
Binary package hint: ec2-init
ec2-init has the following code:
| def get_mirror_from_availability_zone(self, availability_zone):
| if availability_zone.startswith("us"):
| return 'http://us.ec2.archive.ubuntu.com/ubuntu/'
| elif availability_zone.startswith("eu"):
| return 'http://eu.ec2.archive.ubuntu.com/ubuntu/'
|
| return 'http://archive.ubuntu.com/ubuntu/'
The above incorrectly sets the archive to us.ec2.archive.ubuntu.com
which is in us-east-1 region.
Currently that host is not accessible from inside the us-west-1 region.
ProblemType: Bug
Architecture: amd64
Date: Tue Dec 8 20:24:36 2009
DistroRelease: Ubuntu 10.04
Ec2AMI: ami-133c6d56
Ec2AMIManifest: ubuntu-images-testing-us-west-1/ubuntu-lucid-daily-amd64-server-20091207.manifest.xml
Ec2Kernel: aki-0d3c6d48
Package: ec2-init 0.4.999-0ubuntu7
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: User Name 2.6.32-300.1-ec2
SourcePackage: ec2-init
Uname: Linux 2.6.32-300-ec2 x86_64
================
SRU Report (ec2-init):
Background: The UEC Images have code that runs at "first boot" and
customizes an images to the region upon which it is being run. One of
the customizations done is to attempt to select an archive mirror in the
same region that this instance is running in. For example, Canonical
runs 3 archive mirrors in ec2, {us-west-1,us,eu}.ec2.archive.ubuntu.com
. The us and eu mirrors have aliases "us-east-1" and "eu-west-1". The
short names are largely historic now. To limit cost and access to the
ec2 archive mirrors they are configured to only allow systems inside
their region to access them.
An instance is assigned a 'availability zone' within an instance.
These availability zones are currently consistently named as
'<region>[a-z]' (Example: us-east-1a, eu-west-1d). The previous logic
was to select 'us.ec2.archive.ubuntu.com' if the availability zone
started with 'us' and 'eu.ec2.archive.ubuntu.com' if it started with
'eu'. The failure is that availability zones in both us-east-1 and us-
west-1 start with 'us', and would select the 'us.ec2.archive.ubuntu.com'
mirror.
Impact: Instances started in the us-west-1 region incorrectly select the
'us.ec2.archive.ubuntu.com' mirror. That mirror is not accessible
outside of the us-east-1 region, and 'apt-get update' or 'install'
cannot be run without manual modification of /etc/apt/sources.list.
Changes:
Please see the attachment [http://launchpadlibrarian.net/36703733/bug-494185.diff]. The code change is the final hunk of that patch. We modify the 'get_mirror_from_availability_zone' method. The new code selects a mirror based on naming convention of availability zones. Failure or Exception in the logic will selects 'archive.ubuntu.com' as a mirror. Exception in the previous code would end up with no /etc/apt/sources.list.
Test Case:
- Start an instance in us-west-1 region
- ssh to instance, run 'apt-get update'.
- grep "us-west-1" /etc/apt/sources.list
# you *should* see entries for the us-west-1. Currently, there the list shows 'us.ec2.archive.ubuntu.com'
- run 'apt-get update' to verify that the mirrors are functional.
- To verify there is no regression, we should a.) test multiple instance b.) verify that instances in us-east-1 and eu-west-1 do not regress the 'apt-get update' function.
Regression potential:
- The biggest cause for regression is that we are changing logic inside the image. Previously it was all self contained. The change makes the mirror selection depend on dns resolution of a hostname that is dependent upon meta-data available to the image.
This leaves two possible failure paths:
a.) False positive: If the availability zone is named such that a dns entry *does* exist in the .ec2.archive.ubuntu.com subdomain, but there is no mirror running there, the code will falsely write /etc/apt/sources.list to connect to that mirror. This is somewhat unlikely as the availability zones are currently consistently named, and canonical has control over the ec2.archive.ubuntu.com domain.
b.) False negative: Failure in the logic (dns resolution timeout, or temporary un-availability) could result in failure to select the correct mirror. This is mitigated by a selection of 'archive.ubuntu.com' on Exception or failure.
Notes:
- The changes suggested here also reduce the likelyhood that images run in UEC to incorrectly select a ec2 mirror. There is still a possibility of that, but it has been reduced
Previously the code in UEC would fail if the user defined availability zone started with 'us' or 'eu'. Now, the possibility for error is reduced to availability zone names where the folowing is a valid hostname:
"%s.ec2.archive.ubuntu.com" % availability_zone[:-1]
=====
Image store proxy's logrotate config triggers an email every day
Hi
Got an email from cron this morning:
/etc/cron.daily/logrotate:
* Restarting Image Store Proxy image-store-proxy
...done.
This is due to /etc/logrotate.d/image-store-proxy doing:
postrotate
/etc/init.d/image-store-proxy force-reload
endscript
I suggest only reloading if the proxy is running and redirecting non-error output to /dev/null like apache2 does:
postrotate
if [ -f "`. /etc/apache2/envvars ; echo ${APACHE_PID_FILE:-/var/run/apache2.pid}`" ]; then
/etc/init.d/apache2 reload > /dev/null
fi
endscript
Thanks
ProblemType: Bug
Architecture: amd64
Date: Sun Oct 25 08:19:51 2009
DistroRelease: Ubuntu 9.10
Package: python-image-store-proxy 1.0.4-0ubuntu1
PackageArchitecture: all
ProcEnviron:
SHELL=/bin/zsh
PATH=(custom, user)
LANG=fr_FR.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: image-store-proxy
Uname: Linux 2.6.31-11-generic x86_64
==========
Karmic SRU
Impact:
When image-store-proxy are rotated the daemon is restarted which prints a message on stdout. As consequence an email is automatically generated everytime log are rotated.
How the problem has been addressed:
The postrotate script checks whether the daemon is running. If so it restarts it with std out redirected to /dev/null.
TESTCASE:
1. Install image-store-proxy.
2. Force a log rotation:
sudo /usr/sbin/logrotate /etc/logrotate.conf -f
Before the upgrade:
A message should be printed on standard output:
* Restarting Image Store Proxy image-store-proxy
...done.
After the upgrade there shouldn't be any message printed. The image-
store-proxy daemon should have been restarted (new pid).
Regression potential:
The logic used for the fix is similar to the one used in the apache2 package. If the logic fails image-store-proxy daemon will keep writing to existing log file which will be eventually deleted.
==========
Binary package hint: landscape-client
This is on Jaunty beta:
All currently running landscape-* programs currently wake up far more
than is understandable on my machine, accounting for 1.3% of all wakeups
a piece (the sum of four being about 5%). A report from powertop reveals
10 wakeups (per process) during the default period. By comparison,
Rhythmbox which was playing music was consuming an average of 8.2
wakeups, and Transmission actively uploading at 10KBps only had 7.7
wakeups.
As I understand it, the landscape programs don't do much without some
paid support from Ubuntu, and as they are in the default install, care
should be made sure that they behave and should not wake the computer up
far more than it needs to.
We currently have a fetch_async function for downloading a single URL.
It would be nice to have one to retrieve a list of URLs, and have it
callback once all of them have completed. In particular this feature
will be used to fetch the files of the release-ugprade tool used for
dist-upgrades.
The attached branch implements the proposed behaviour, and also add a
helper function to parse the /etc/lsb-release, which is used in a couple
of spots already, and will be used in the release-upgrade feature as
well.
Handle release-upgrade messages in the packagemanager plugin
The client should handle messages for type "release-upgrade", which are
going to be issued by the server for requesting a system upgrade to a
newer release.
The packagemanager plugin should handle this message by enqueuing a task
for a release-upgrader task handler.
affects landscape
status inprogress
importance medium
assignee free.ekanayaka
milestone later
private yes
Landscape daemons fail to start when too many groups are available
Due to a bug in Twisted (http://twistedmatrix.com/trac/ticket/3226),
landscape client takes a long time to start, making the ping fail. Thus,
the watchdog tries to restart the daemons forever.
We should workaround this problem in Landscape by patching the
twisted.python.util to use the real initgroups call.
Add a new landscape-release-upgrader task handler script and class to
perform release upgrades.
The release-upgrader should fetch, verify and run the upgrade tool for
the target release specified by the task being handled.
affects landscape-client
status inprogress
importance medium
assignee free.ekanayaka
milestone 1.4.1
The upgrade-tool supports two useful environment variables, namely
DEBUG_UPDATE_MANAGER and RELEASE_UPRADER_ALLOW_THIRD_PARTY.
If set to "True" they enable respectively debug logging and support for
non-official mirrors in APT sources.list, which won't get disabled
during the upgrade.
We should expose them to the user via the Landscape UI.
affects landscape
status inprogress
importance medium
assignee free.ekanayaka
milestone 1.4.1
private yes
Update intrepid, jaunty and karmic to landscape-client 1.4.0
Landscape Client 1.4.0 has been released. We would like to get these
changes into Karmic, Intrepid and Jaunty. The required pieces of
information for a SRU follow (as laid out in the "Procedure" section of
https://wiki.ubuntu.com/StableReleaseUpdates).
=== Statement explaining the impact ===
New features have been developed since the versions of Landscape Client
that are currently in Intrepid, Jaunty and Karmic. We would like to make
sure all of our supported customers (even those on Intrepid and Jaunty
and Karmic) have access to these features. The notable ones are:
1) Support for release upgrades. From the Landscape web UI, it's now
possible to issue a system upgrade between to subsequent Ubuntu releases
(e.g. from jaunty to karmic), which will be performed using the regular
update-manager code in non-interactive mode.
2) Report Smart locking information. The client will now report the
server about Smart locks set on the system, which the Landscape UI is
going to display with a special icon.
3) Several bug fixes which improve the overall user experience.
For more details see Bug #456124, Bug #340843, Bug #465846, Bug
#476418, Bug #369000, Bug #450629, Bug #455217, Bug #462543, Bug #463321
and Bug #488108 (all mentioned in the debian/changelog of the proposed
packages).
=== How the bug has been addressed ===
We have been following the development procedure laid out in
https://wiki.ubuntu.com/LandscapeUpdates
=== Patches ===
The three branches for the new landscape-client intrepid, jaunty and
karmic source packages are attached to this bug, and are were derived
from
lp:ubuntu/intrepid/landscape-client
lp:ubuntu/jaunty/landscape-client
lp:ubuntu/karmic/landscape-client
respectively.
=== Detailed instructions how to reproduce the bug ===
N/A
=== Discussion ===
All the source packages have been subject to the QA process detailed in
the LandscapeUpdates document linked above.
Please provide squashfs-modules udeb. The kernel generated for d-i does
not have the squashfs kernel module nor is it built in so I can't mount
a squashfs. Debian has the squashfs-modules package and there are
packages in Ubuntu which have dependencies on it. This is also necessary
for the OEM Services team's installer to function properly.
usbstorage: Sony-Ericsson W760i "No sense [current]"
SRU Justification:
Impact: Changes to device detection scan all partitions and the whole
drive for meta-data. When scanning the whole drive for MD signatures
(which are at the end of the drive) this now triggered bugs for many
drives which a) return the wrong size information when queried and b)
return errors without sense data in that case.
Fix: "USB: storage: When a device returns no sense data, call it a
Hardware Error" which is part of 2.6.31.6 changes the USB storage
transport layer to return a hardware error in that case to prevent the
endless loop.
---
(New report requested in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264789/comments/172)
When I connect my phone (Sony-Ericsson W760i in Mass Storage mode) to my
Ubuntu 9.04 system, it fails to mount the device, and dmesg gets flooded
with "No Sense [current]" messages:
[ 1603.224162] sd 3:0:0:0: [sdc] Sense Key : No Sense [current]
[ 1603.224177] sd 3:0:0:0: [sdc] Add. Sense: No additional sense information
[ 1603.232153] sd 3:0:0:1: [sdd] Sense Key : No Sense [current]
[ 1603.232167] sd 3:0:0:1: [sdd] Add. Sense: No additional sense information
[ 1603.322091] sd 3:0:0:0: [sdc] Sense Key : No Sense [current]
[ 1603.322106] sd 3:0:0:0: [sdc] Add. Sense: No additional sense information
Several Huawei USB dongle don't work with kernel 2.6.31-12.40 (2.6.31.1 update related)
SRU Justification:
Impact: The Huawei modem (with a certain firmware it seems) claims to
support a certain sense data format, but does not do so.
Fix: Change to USB storage, which lets the device fallback to a shorter
sense format. This patch went into 2.6.31.5 ("usb-storage: Workaround
devices with bogus sense size").
---
I'm using a Huawei E169 USB dongle to connect to a GSM mobile broadband
network. It used to work out-of-the-box with Jaunty and previous
versions of Karmic (kernel 2.6.31-11 and previous). However the device
doesn't work any more with the latest kernel.
Dmesg gives me repatedly this message:
dmesg:
option: option_instat_callback: error -108
lsusb:
Bus 005 Device 005: ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem
My system: Dell XPS M1530, see attached result of "lshw"
This bug apparently affects other people as well:
http://ubuntuforums.org/showthread.php?p=8070873#post8070873
China Telecom CDMA EVDO USB dangle does not work in Ubuntu
SRU Justification:
Impact: Hardware no working due to missing IDs in driver.
Fix: (from 2.6.31.6) Adding the missing IDs.
---
A new EVDO USB dangle from China Telecom does not work in Karmic latest
kernel. The vendor is Tlaytech Corporation from Shanghai. The USB VID is
0x20B9 and PID is 0x1682.
SRU Justification/Impact: The upstream process for stable tree updates
is quite similar in scope to the Ubuntu SRU process, e.g., each patch
has to demonstrably fix a bug, and each patch is vetted by upstream by
originating either directly from Linus' tree or in a minimally
backported form of that patch. The 2.6.31.5 upstream stable patch set is
now available. It should be included in the Ubuntu kernel as well.
TEST CASE: TBD
http://kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.31.5
http://kernel.org/pub/linux/kernel/v2.6/patch-2.6.31.5.bz2
==========
The 2.6.31.5 Upstream Stable Kernel brings in the following 47 patches:
* SCSI: Retry ADD_TO_MLQUEUE return value for EH commands
* SCSI: Fix protection scsi_data_buffer leak
* SCSI: sg: Free data buffers after calling blk_rq_unmap_user
* ARM: pxa: workaround errata #37 by not using half turbo switching
* tracing/filters: Fix memory leak when setting a filter
* x86/paravirt: Use normal calling sequences for irq enable/disable
* USB: ftdi_sio: remove tty->low_latency
* USB: ftdi_sio: remove unused rx_byte counter
* USB: ftdi_sio: clean up read completion handler
* USB: ftdi_sio: re-implement read processing
* USB: pl2303: fix error characters not being reported to ldisc
* USB: digi_acceleport: Fix broken unthrottle.
* USB: serial: don't call release without attach
* USB: option: Toshiba G450 device id
* USB: ipaq: fix oops when device is plugged in
* USB: cp210x: Add support for the DW700 UART
* USB: Fix throttling in generic usbserial driver
* USB: storage: When a device returns no sense data, call it a Hardware Error
* arm, cris, mips, sparc, powerpc, um, xtensa: fix build with bash 4.0
* intel-iommu: Cope with broken HP DC7900 BIOS
* futex: Detect mismatched requeue targets
* futex: Fix wakeup race by setting TASK_INTERRUPTIBLE before queue_me()
* tpm-fixup-pcrs-sysfs-file-update
* TPM: fix pcrread
* Bluetooth: Disconnect HIDRAW devices on disconnect
* Bluetooth: Add extra device reference counting for connections
* Bluetooth: Let HIDP grab the device reference for connections
* connector: Keep the skb in cn_callback_data
* connector: Provide the sender's credentials to the callback
* connector: Removed the destruct_data callback since it is always kfree_skb()
* dm/connector: Only process connector packages from privileged processes
* dst/connector: Disallow unpliviged users to configure dst
* pohmelfs/connector: Disallow unpliviged users to configure pohmelfs
* uvesafb/connector: Disallow unpliviged users to send netlink packets
* e1000e: swap max hw supported frame size between 82574 and 82583
* MAINTAINERS: Fix Riku Voipio's address
* macintosh: Don't assume i2c device probing always succeeds
* i2c: Hide probe errors caused by ACPI resource conflicts
* ALSA: Don't assume i2c device probing always succeeds
* bsdacct: switch credentials for writing to the accounting file
* sysfs: Allow sysfs_notify_dirent to be called from interrupt context.
* Staging: rt2860sta: prevent a panic when disabling when associated
* usb-storage: Workaround devices with bogus sense size
* iwlwifi: incorrect method used for finding valid OTP blocks
* mac80211: fix vlan and optimise RX
* tty: Make flush_to_ldisc() locking more robust
* Linux 2.6.31.5
SRU justification:
Impact: The mentioned change by upstream (in the Karmic release code)
caused regressions for the detection of some devices.
Fix: "pci: increase alignment to make more space for hidden code" which
comes in through 2.6.31.6 resolves the issue and allows affected devices
to be detected again.
---
Just opening a bug in launchpad to keep this on our radar and also track
the issue upstream:
http://bugzilla.kernel.org/show_bug.cgi?id=14402
https://lists.ubuntu.com/archives/kernel-team/2009-November/007770.html
The Atheros ath9k module is not working with [testing]-kernel 2.6.31.1 on an
Acer Extensa 7630EZ. Downgrading to 2.6.30.x solves this problem
> OK great, now please checkout a clean 2.6.31.5 branch:
>
> git checkout -b linux-2.6.31.y v2.6.31.5
>
> compile and load and confirm that kernel has an issue.
confirmed. wlan-device is disabled on boot
> Then run:
>
> git revert 5d423ccd7ba4285f1084e91b26805e1d0ae978ed
>
> compile and load and confirm the issue is resolved.
confirm, issue is resolved by reverting this commit.
AppArmor does not correctly reenable kernel preemption
SRU Justification: Failing to put_cpu_var means that kernel preemption
is disabled for the task. This will affect all confined processes that
try to audit a capability message (so an process that has capability
violation or is in learning mode and would have a capability violation).
The auditing code of capabilities, has a simple cache to reduce
capability messages flooding the audit logs. Checking and updating the
cache disables kernel preemption (via get_cpu_var). One potential exit
path does not properly put the per cpu var, thus not reenabling
preemption.
ent = &get_cpu_var(audit_cache);
if (sa->base.task == ent->task && cap_raised(ent->caps, sa->cap)) {
--------> needs put_cpu_var(audit_cache); <--------
if (PROFILE_COMPLAIN(profile))
return 0;
return sa->base.error;
} else {
ent->task = sa->base.task;
cap_raise(ent->caps, sa->cap);
}
put_cpu_var(audit_cache);
AppArmor does not put cred reference causing a leak
SRU Justification: Failure to put the cred causes a memory leak that is
larger than the cred struct, as it leaks everything it references. This
happens for every unconfined processes that does an exec, change_hat or
change_profile and passes through this function.
AppArmor fails to drop the cred reference in domain.c:aa_may_change_ptraced_domain
if (tracer)
cred = aa_get_task_policy(tracer, &tracerp);
rcu_read_unlock();
if (!tracerp)
return error; <--------- cred reference needs to be dropped here
SRU Justification: This bug can cause confined process to oops at
address 0. This can occur when executing a process if the
LSM_UNSAFE_PTRACE | LSM_UNSAFE_PTRACE_CAP flags are set. The likely
hood of if/how often this will occur depends on if ptrace is being used.
As reported by Tetsuo Handa on kernel-team mailing list:
In aa_may_change_ptraced_domain, if (!tracer) cred == NULL, and
put_cred(cred) will oops. This will only happen on exec if the task
is marked as LSM_UNSAFE_PTRACE | LSM_UNSAFE_PTRACE_CAP, so should
only happen to ptraced tasks that are confined.
Fix this by returning directly from aa_may_change_ptrace_domain if
there is now tracer.
SRU Justification/Impact: The upstream process for stable tree updates
is quite similar in scope to the Ubuntu SRU process, e.g., each patch
has to demonstrably fix a bug, and each patch is vetted by upstream by
originating either directly from Linus' tree or in a minimally
backported form of that patch. The 2.6.31.6 upstream stable patch set is
now available. It should be included in the Ubuntu kernel as well.
TEST CASE: TBD
http://kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.31.6
http://kernel.org/pub/linux/kernel/v2.6/patch-2.6.31.6.bz2
==========
The 2.6.31.6 Upstream Stable Kernel brings in the following 101 patches:
* fs: pipe.c null pointer dereference
* pci: increase alignment to make more space for hidden code
* libata: fix internal command failure handling
* libata: fix PMP initialization
* sata_nv: make sure link is brough up online when skipping hardreset
* nfs: Fix nfs_parse_mount_options() kfree() leak
* KVM: use proper hrtimer function to retrieve expiration time
* KVM: ignore reads from AMDs C1E enabled MSR
* futex: Handle spurious wake up
* futex: Check for NULL keys in match_futex
* futex: Move drop_futex_key_refs out of spinlock'ed region
* futex: Fix spurious wakeup for requeue_pi really
* ahci: revert "Restore SB600 sata controller 64 bit DMA"
* sparc64: Set IRQF_DISABLED on LDC channel IRQs.
* sparc: Kill PROM console driver.
* watchdog: Fix rio watchdog probe function
* Input: synaptics - add another Protege M300 to rate blacklist
* dm snapshot: free exception store on init failure
* dm snapshot: sort by chunk size to fix race
* dm log: userspace fix incorrect luid cast in userspace_ctr
* dm: add missing del_gendisk to alloc_dev error path
* dm: dec_pending needs locking to save error value
* dm exception store: fix failed set_chunk_size error path
* dm snapshot: lock snapshot while supplying status
* dm snapshot: require non zero chunk size by end of ctr
* dm snapshot: use unsigned integer chunk size
* ray_cs: Fix copy_from_user handling
* mbind(): fix leak of never putback pages
* do_mbind(): fix memory leak
* 8250_pci: add IBM Saturn serial card
* dpt_i2o: Fix up copy*user
* dpt_i2o: Fix typo of EINVAL
* hfsplus: refuse to mount volumes larger than 2TB
* Driver core: fix driver_register() return value
* tty: Mark generic_serial users as BROKEN
* param: fix lots of bugs with writing charp params from sysfs, by leaking mem.
* param: fix NULL comparison on oom
* param: fix setting arrays of bool
* USB: serial: sierra driver send_setup() autopm fix
* USB: option: Patch for Huawei Mobile Broadband E270+ Modem
* USB: option: Support for AIRPLUS MCD650 Datacard
* USB: option: TLAYTECH TUE800 support
* libertas if_usb: Fix crash on 64-bit machines
* cpuidle: always return with interrupts enabled
* virtio: order used ring after used index read
* CIFS: Fixing to avoid invalid kfree() in cifs_get_tcp_session()
* mac80211: fix for incorrect sequence number on hostapd injected frames
* mac80211: check interface is down before type change
* x86, UV: Fix information in __uv_hub_info structure
* x86, UV: Set DELIVERY_MODE=4 for vector=NMI_VECTOR in uv_hub_send_ipi()
* NOMMU: Don't pass NULL pointers to fput() in do_mmap_pgoff()
* mm: remove incorrect swap_count() from try_to_unuse()
* x86-64: Fix register leak in 32-bit syscall audting
* nilfs2: fix dirty page accounting leak causing hang at write
* drm/i915: Fix FDI M/N setting according with correct color depth
* drm/i915: fix to setup display reference clock control on Ironlake
* drm/i915: fix panel fitting filter coefficient select for Ironlake
* agp/intel: Add B43 chipset support
* drm/i915: add B43 chipset support
* xen/hvc: make sure console output is always emitted, with explicit polling
* xen: mask extended topology info in cpuid
* sgi-gru: decrapfiy options_write() function
* KVM: get_tss_base_addr() should return a gpa_t
* fuse: prevent fuse_put_request on invalid pointer
* fuse: fix kunmap in fuse_ioctl_copy_user
* x86/amd-iommu: Workaround for erratum 63
* fsnotify: do not set group for a mark before it is on the i_list
* mips: fix build of vmlinux.lds
* alpha: fix build after vmlinux.lds.S cleanup
* ACPI / PCI: Fix NULL pointer dereference in acpi_get_pci_dev() (rev. 2)
* Revert "ACPI: Attach the ACPI device to the ACPI handle as early as possible"
* KEYS: get_instantiation_keyring() should inc the keyring refcount in all cases
* b43: Fix Bugzilla #14181 and the bug from the previous 'fix'
* pata_sc1200: Fix crash on boot
* AF_UNIX: Fix deadlock on connecting to shutdown socket (CVE-2009-3621)
* ALSA: ice1724 - Make call to set hw params succeed on ESI Juli@
* bonding: fix a race condition in calls to slave MII ioctls
* hwmon: (it87) Fix VID reading on IT8718F/IT8720F
* netlink: fix typo in initialization (CVE-2009-3612)
* nfs: Avoid overrun when copying client IP address string
* nfs: Panic when commit fails
* NFSv4: Fix a bug when the server returns NFS4ERR_RESOURCE
* NFSv4: Fix two unbalanced put_rpccred() issues.
* NFSv4: Kill nfs4_renewd_prepare_shutdown()
* NFSv4: The link() operation should return any delegation on the file
* powerpc: Remove SMP warning from PowerMac cpufreq
* vmscan: limit VM_EXEC protection to file pages
* x86: mce: Clean up thermal throttling state tracking code
* x86: mce: Fix thermal throttling message storm
* iwlwifi: fix potential rx buffer loss
* iwlwifi: reduce noise when skb allocation fails
* x86/amd-iommu: Un__init function required on shutdown
* KVM: Prevent kvm_init from corrupting debugfs structures
* powerpc/pmac: Fix PowerSurge SMP IPI allocation
* powerpc/pmac: Fix issues with sleep on some powerbooks
* powerpc/pci: Fix regression in powerpc MSI-X
* powerpc: Fix some late PowerMac G5 with PCIe ATI graphics
* sata_via: Remove redundant device ID for VIA VT8261
* pata_via: extend the rev_max for VT6330
* PM / yenta: Split resume into early and late parts (rev. 4)
* Linux 2.6.31.6
We are however going to omit pulling in the following 2 patches as they either remove or disable drivers which might result in a regression:
* sparc: Kill PROM console driver.
* tty: Mark generic_serial users as BROKEN
== Fixes ==
Bug 327499: "Revert "ACPI: Attach the ACPI device to the ACPI handle as early as possible"
Bug 456264: " USB: option: TLAYTECH TUE800 support"
Bug 476154: "b43: Fix Bugzilla #14181 and the bug from the previous 'fix'"
Bug 407824: "pci: increase alignment to make more space for hidden code"
Bug 407040: "pci: increase alignment to make more space for hidden code"
Bug 453444: "x86: mce: Fix thermal throttling message storm"
Bug 459265: "NFSv4: Fix two unbalanced put_rpccred() issues."
== Possibly Fixes ==
Bug 442966: "fsnotify: do not set group for a mark before it is on the i_list"
Bug 432860: "fsnotify: do not set group for a mark before it is on the i_list"
Bug 457523 - "mac80211: check interface is down before type change"
Bug 417776: "Linux 2.6.31.6"
Bug 464429: "Linux 2.6.31.6"
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
io/fs errors when launching gdm on imx51 with sata
With the imx51 image on babbage 2.5, if I boot with USB as a disk,
everything works fine. With a sata drive attached, it's a different
story.
My current configuration is that I have a 2.5" sata disk (tested and
shown to work on other systems) connected to the babbage for data, and
the power is coming from an external source.
I can boot the live image, and go all the way through the installation
with no problems. On reboot, when gdm starts to come up, I get as far
as the spinning mouse cursor and it appears to hang.
If I eliminate sreadahead from starting, I'm able to get it to take
longer before hanging, but it still eventually does hang.
If I eliminate both sreadahead and gdm, I'm able to boot to a text
console and use the system just fine.
Starting sreadahead by itself, I didn't see any problems, no hang, no io
errors in dmesg.
Starting gdm by itself, it hangs after several seconds and I start to see errors like this on the serial console within a few minutes:
end_request: I/O error, dev sda, sector 71319871
EXT4-fs error (device sda1): __ext4_get_inode_loc: unable to read inode block - inode=2261007, block=8914976
Aborting journal on device sda1:8.
EXT4-fs error (device sda1): ext4_journal_start_sb: Detected aborted journal
EXT4-fs (sda1): Remounting filesystem read-only
end_request: I/O error, dev sda, sector 71319879
end_request: I/O error, dev sda, sector 71319887
end_request: I/O error, dev sda, sector 239343983
end_request: I/O error, dev sda, sector 239344223
When this happens, I cannot even switch between virtual consoles.
Kernel version signature is 2.6.31-100.7-imx51
Suspend/resume on dove works, kinda. The system seems to power down
into a low power state. However on resume, the system is left in a
nearly unusable state. Everything slows to a crawl, and all processes
seem to be chewing up, at minimum, 1.6% cpu.
ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly. The resume processing hung very near the end and will have appeared to have completed normally.
Architecture: armel
Date: Fri Oct 16 23:34:16 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: late resume
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Alpha armel+dove (20091016)
InterpreterPath: /usr/bin/python2.6
Package: linux-image-2.6.31-208-dove 2.6.31-208.16
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-208.16-hostname
SourcePackage: linux-mvl-dove
Tags: resume suspend resume-late-hang
Title: late resume failure
Uname: Linux 2.6.31-208-dove armv7l
UserGroups:
Booting the Alpha 1 image, I get stuck at a point where I'm seeing
console messages on the screen
...
* Starting init crypto disks...
Alignment trap: not handling instruction ed9f9b93 at [<000626f2>]
Unhandled fault: alignment exception (0x011) at 0x00062942
(The previous two messages repeat 13 more times with the same addresses)
I can alt-f2 and switch to another console, dmesg also shows another message at the end of that:
Recursive core dump detected, aborting
I was able to manually bring up the network, but trying to scp anything
such as dmesg info across to another machine resulted in a few more
Alignment trap/Unhandled fault errors, and ssh failed.
Trying to run some commands, such as apport-cli, fail immediately with these errors.
I straced apport-cli as an example, and at the end, I had:
close(3)
munmap(0x40020000, 4096)
Alignment trap: not handling instruction eddf7a13 at [<0002b8d2>]
Unhandled fault: alignment exception (0x011) at 0x0002b922
--- SIGILL (Illegal instruction) @ 0 (0) ---
Alignment trap: not handling instruction eddf7a13 at [<0002b8d2>]
Unhandled fault: alignment exception (0x011) at 0x0002b922
Does this appear more likely to be kernel, or toolchain? I did not have
this same problem on a different SoC with alpha1
mountall vomits a shell onto virtual console when you run vi
Binary package hint: mountall
I have an awesome bug. On a server upgraded from hardy -> karmic, if
I run vi as root on the console, mountall loses it's mind (because
it's still running and thinks it owns the console, apparently) and
spawns a shell onto the console that vi is running on.
--debug log of mountall attached
"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.
Rhythmbox Notification Bubble shows wrong cover art
Binary package hint: rhythmbox
When switching between songs while the main window is invisible
notification bubble pop up to show me what the current song is.
Unfortunately the notification bubble sometimes shows the wrong cover
art. It seems to me that the main (only?) problem is when switching from
a song with cover art to another song that has no cover art. In that
case all the information from the new song is displayed, but the cover
art of the old song is still displayed (which is obviously no longer
applicable).
ProblemType: Bug
Architecture: amd64
Date: Wed Oct 14 10:35:51 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: nvidia
Package: rhythmbox 0.12.5-0ubuntu3
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=de_AT.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-13.45-generic
SourcePackage: rhythmbox
Uname: Linux 2.6.31-13-generic x86_64
Transmission doesn't prevent suspend when torrent is active
Binary package hint: transmission
"In Karmic, Transmission fails to prevent me from suspending my computer
with active torrents. This error appears in the journal: "the name
org.freedesktop.powermanagement was not provided by any .service
files"."
The bug is Fixed in 1.80 beta1 which is going to be uploaded to Lucid
soon (with a small fix mentioned in the branch log).
TEST CASE: To reproduce bug launch Transmission and enable "Inhibit hibernation when torrents are active" in Desktop tab of settings and start downloading some torrent. Then try to suspend laptop using gnome-session dialog (you can launch it by using "gnome-session-save --shutdown-dialog"). Please note that neither indicator applet nor shutting down lid is affected by inhibitor - only gnome-session dialog.
When updated version is applied a new dialog is going to show up asking user whenever he really want to suspend session.
Regression potential is minimal - patch itself is small and related only
to inhibition which is already broken.
For those not using NetworkManager and are on Karmic, the fix for this
bug is in our beta PPA. Instructions on how to use this PPA instead of
the Karmic Ubuntu One packages can be found at:
https://answers.edge.launchpad.net/ubuntuone-client/+faq/836
kees 9638 2.2 0.3 273056 28324 ? Sl 16:42 0:00
/usr/bin/python /usr/bin/ubuntuone-client-applet --signup
Messages from .xsession-errors:
/usr/lib/python2.6/dist-packages/twisted/internet/_sslverify.py:5: DeprecationWarning: the md5 module is deprecated; use hashlib instead
import itertools, md5
After killing it:
Unhandled error in Deferred:
Traceback (most recent call last):
File "/usr/lib/python2.6/threading.py", line 497, in __bootstrap
self.__bootstrap_inner()
File "/usr/lib/python2.6/threading.py", line 525, in __bootstrap_inner
self.run()
File "/usr/lib/python2.6/threading.py", line 477, in run
self.__target(*self.__args, **self.__kwargs)
--- <exception caught here> ---
File "/usr/lib/python2.6/dist-packages/twisted/python/threadpool.py", line 210, in _worker
result = context.call(ctx, function, *args, **kwargs)
File "/usr/lib/python2.6/dist-packages/twisted/python/context.py", line 59, in callWithContext
return self.currentContext().callWithContext(ctx, func, *args, **kw)
File "/usr/lib/python2.6/dist-packages/twisted/python/context.py", line 37, in callWithContext
return func(*args,**kw)
File "/usr/lib/python2.6/dist-packages/canonical/ubuntuone/oauthdesktop/auth.py", line 306, in ensure_access_token
store=True)
File "/usr/lib/python2.6/dist-packages/canonical/ubuntuone/oauthdesktop/auth.py", line 182, in acquire_access_token_if_online
'/org/freedesktop/NetworkManager')
File "/var/lib/python-support/python2.6/dbus/bus.py", line 244, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/var/lib/python-support/python2.6/dbus/proxies.py", line 241, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/var/lib/python-support/python2.6/dbus/bus.py", line 183, in activate_name_owner
self.start_service_by_name(bus_name)
File "/var/lib/python-support/python2.6/dbus/bus.py", line 281, in start_service_by_name
'su', (bus_name, flags)))
File "/var/lib/python-support/python2.6/dbus/connection.py", line 622, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
Note that I do not use NetworkManager...
no HTTPSConnection._tunnel_host in python <= 2.6.2
The file "ubuntuone/oauthdesktop/auth.py" references
HTTPSConnection._tunnel_host unconditionally that is only available in
python/httplib >= 2.6.3 and therefore fails on Jaunty that has 2.6.2
installed.
xxxxxxxxx~$ ubuntuone-client-applet
Traceback (most recent call last):
File "/var/lib/python-support/python2.6/dbus/connection.py", line 578, in msg_reply_handler
reply_handler(*message.get_args_list(**get_args_opts))
File "/usr/lib/python2.6/dist-packages/ubuntuone/oauthdesktop/auth.py", line 276, in got_state
self.acquire_access_token(description, store)
File "/usr/lib/python2.6/dist-packages/ubuntuone/oauthdesktop/auth.py", line 336, in acquire_access_token
self.request_token = self.make_token_request(oauth_request)
File "/usr/lib/python2.6/dist-packages/ubuntuone/oauthdesktop/auth.py", line 229, in make_token_request
fp = opener.open(oauth_request.http_url, oauth_request.to_postdata())
File "/usr/lib/python2.6/urllib.py", line 205, in open
return getattr(self, name)(url, data)
File "/usr/lib/python2.6/urllib.py", line 437, in open_https
h.endheaders()
File "/usr/lib/python2.6/httplib.py", line 868, in endheaders
self._send_output()
File "/usr/lib/python2.6/httplib.py", line 740, in _send_output
self.send(msg)
File "/usr/lib/python2.6/httplib.py", line 699, in send
self.connect()
File "/usr/lib/python2.6/dist-packages/ubuntuone/oauthdesktop/auth.py", line 58, in _connect_wrapper
if self._tunnel_host:
AttributeError: HTTPSConnection instance has no attribute '_tunnel_host'
ProblemType: Bug
.home.alexei..cache.ubuntuone.log.syncdaemon.exceptions.log:
.home.alexei..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
bookmarked = True
connected = True
connect = 0
show_applet = 1
Architecture: i386
CrashDB: ubuntuone
DistroRelease: Ubuntu 9.04
Package: ubuntuone-client 1.0.0+r255-0ubuntu1~ppa1~jaunty
PackageArchitecture: all
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntuone-client
ThirdParty: True
Uname: Linux 2.6.28-15-generic i686
UnreportableReason: This is not a genuine Ubuntu package
The ubuntuone-client needs to create a POT template on build
Currently the ubuntuone-client package does not generate a POT template
during the build process, which prevents new translations (and string
changes) to be imported into Launchpad.
The package seemed to be generating templates at some point, at least
until the latest template import into Launchpad:
2009-10-04 01:56:59.200198+00:00
For more information, please see:
https://wiki.ubuntu.com/UbuntuDevelopment/Internationalisation#Translation%20templates
https://wiki.ubuntu.com/UbuntuDevelopment/Internationalisation#Verifying%20translation%20uploads
"Protocol version error" - when bandwidth throttling is enabled with the default values
I am always getting "Protocol version error" when I start this client.
* After updating everything
* After removing and reinstalling everything
* After removing and making sure nothing shows up in /usr with find | grep ubuntuone (except some image files) and then installing everything again
Bug is triggered when bandwidth throttling is enabled with the default
values.
The workaround is to either remove or rename:
~/.config/ubuntuone/syncdaemon.conf
This will reset the syncdaemon.conf file. For the time being, don't set
the bandwidth usage preference.
BadTransition: SYS_CONNECTION_MADE - Ubuntu One crashes coming out of sleep/hibernate
Binary package hint: ubuntuone-client
ubuntu one crash on coming out of sleep mode.
NOTE: This bug also appears to affect users when coming out of hibernate
and when the network connection is connected and then disconnected.
Those are the cases I'm finding so far that produce the BadTransition
debug entry.
ProblemType: Bug
.home.shantanu..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
connected = True
connect = 0
show_applet = 1
bookmarked = True
Architecture: i386
CheckboxSubmission: 4e108058a24c96a9948d9eb1f4223902
CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
Date: Wed Oct 21 17:59:52 2009
DistroRelease: Ubuntu 9.10
Package: ubuntuone-client 1.0.2-0ubuntu1
PackageArchitecture: all
ProcEnviron:
LANG=en_IN
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
(gnome-settings-daemon:1979): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(gnome-settings-daemon:1979): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(nautilus:2083): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
(polkit-gnome-authentication-agent-1:2100): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(gnome-panel:2080): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window
Icon does not disappear immediately if switched to never show icon
Binary package hint: ubuntuone-client
If I switch "Show Icon" e.g. from Always to Never, the icon should
disappear immediately. It does not. It does not even disappear if I
click on Close. It only does not appear when I log out and log in again.
ProblemType: Bug
.home.aschildbach..cache.ubuntuone.log.syncdaemon.exceptions.log:
.home.aschildbach..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
connected = False
connect = 2
show_applet = 2
bookmarked = True
Architecture: i386
Date: Wed Oct 21 20:49:23 2009
DistroRelease: Ubuntu 9.10
Package: ubuntuone-client 1.0.2-0ubuntu1
PackageArchitecture: all
ProcEnviron:
LANG=C
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
(gnome-settings-daemon:12159): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(nautilus:12197): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
(polkit-gnome-authentication-agent-1:12210): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(gnome-panel:12193): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window
oauth-login.log sometimes doesn't contain timestamps
An example of this can be found there:
http://launchpadlibrarian.net/34122452/.home.me..cache.ubuntuone.log.oauth.login.log.txt
That log comes from bug 457740 and makes troubleshooting more difficult
as you don't know the timing of when the statements were taking place. I
haven't been able to find any pattern to why most oauth-login.log files
appear to have timestamps but some don't.
Bandwith limit preference doesn't appear to be saved
Binary package hint: ubuntuone-client
When I use the gnome applet preferences dialog to change my bandwidth
limit it doesn't appear to be saved. I go to Preferences, check the
"Limit Bandwidth Usage" box, set the upload and download limits to 128
KB/s and click close. If I then go back into Preferences, the "Limit
Bandwidth Usage" box is unchecked and the grayed out upload and download
limits are back to the default of 2048 KB/s
ProblemType: Bug
.home.herb..cache.ubuntuone.log.syncdaemon.exceptions.log:
.home.herb..config.ubuntuone.syncdaemon.conf:
[bandwidth_throttling]
read_limit = 2097152
write_limit = 131072
on = True
.home.herb..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
bookmarked = True
connected = True
connect = 0
show_applet = 0
Architecture: i386
Date: Fri Oct 30 11:45:13 2009
DistroRelease: Ubuntu 9.10
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-14-generic i686
NIGHTLIES: ValueError: invalid literal for int() with base 10: 'None' on init
Full traceback. Seen on two machines.
2009-11-06 13:24:23,215 - ubuntuone.SyncDaemon - ERROR - Unexpected error
Traceback (most recent call last):
File "/usr/lib/ubuntuone-client/ubuntuone-syncdaemon", line 182, in <module>
main(sys.argv)
File "/usr/lib/ubuntuone-client/ubuntuone-syncdaemon", line 135, in main
throttling_enabled=options.bandwidth_throttling_on)
File "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/main.py", line 101, in __init__
read_limit = user_config.get_throttling_read_limit()
File "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/config.py", line 134, in wrapped
return meth(self, *args, **kwargs)
File "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/config.py", line 206, in get_throttling_read_limit
value = self.getint(THROTTLING, 'read_limit')
File "/usr/lib/python2.6/ConfigParser.py", line 340, in getint
return self._get(section, int, option)
File "/usr/lib/python2.6/ConfigParser.py", line 337, in _get
return conv(self.get(section, option))
ValueError: invalid literal for int() with base 10: 'None'
Applet starts syncdaemon before successful OAuth token retrieval
The applet is currently starting the syncdaemon to get the root
directory, and status, before we actually get the OAuth token. This
should be harmless, but may be causing some interaction issues as well.
Error while creating share from nautilus - _create_share_http in action_queue.py, line 1859 calls callback with missing parameters
This is an error in syncdaemon, not nautilus-ubuntuone.
If the patch fixing #491777 is applied then the user is greeted with the
following message:
Error creating share.
There was an error sharing the folder '$folder':
callback() takes exactly 2 arguments (1 given)
syncdaemon.log contains the following.
Traceback (most recent call last):
File "/usr/lib/python2.6/threading.py", line 497, in __bootstrap
self.__bootstrap_inner()
File "/usr/lib/python2.6/threading.py", line 525, in __bootstrap_inner
self.run()
File "/usr/lib/python2.6/threading.py", line 477, in run
self.__target(*self.__args, **self.__kwargs)
--- <exception caught here> ---
File "/usr/lib/python2.6/dist-packages/twisted/python/threadpool.py", line 210, in _worker
result = context.call(ctx, function, *args, **kwargs)
File "/usr/lib/python2.6/dist-packages/twisted/python/context.py", line 59, in callWithContext
return self.currentContext().callWithContext(ctx, func, *args, **kw)
File "/usr/lib/python2.6/dist-packages/twisted/python/context.py", line 37, in callWithContext
return func(*args,**kw)
File "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/action_queue.py", line 1859, in _create_share_http
deferred.callback()
exceptions.TypeError: callback() takes exactly 2 arguments (1 given)
BadTransition: SYS_CONNECTION_MADE - Ubuntu One crashes coming out of sleep/hibernate
Binary package hint: ubuntuone-client
ubuntu one crash on coming out of sleep mode.
NOTE: This bug also appears to affect users when coming out of hibernate
and when the network connection is connected and then disconnected.
Those are the cases I'm finding so far that produce the BadTransition
debug entry.
ProblemType: Bug
.home.shantanu..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
connected = True
connect = 0
show_applet = 1
bookmarked = True
Architecture: i386
CheckboxSubmission: 4e108058a24c96a9948d9eb1f4223902
CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
Date: Wed Oct 21 17:59:52 2009
DistroRelease: Ubuntu 9.10
Package: ubuntuone-client 1.0.2-0ubuntu1
PackageArchitecture: all
ProcEnviron:
LANG=en_IN
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
(gnome-settings-daemon:1979): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(gnome-settings-daemon:1979): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(nautilus:2083): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
(polkit-gnome-authentication-agent-1:2100): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(gnome-panel:2080): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window
Traceback in logs after uploading a file (OK out of order because of throttling)
After uploading a file, the following traceback appeared in both
syncdaemon logs:
2009-11-09 14:51:37,326 - twisted - ERROR - Unhandled Error
Traceback (most recent call last):
File "/usr/lib/python2.6/dist-packages/twisted/python/log.py", line 84, in callWithLogger
return callWithContext({"system": lp}, func, *args, **kw)
File "/usr/lib/python2.6/dist-packages/twisted/python/log.py", line 69, in callWithContext
return context.call({ILogContext: newCtx}, func, *args, **kw)
File "/usr/lib/python2.6/dist-packages/twisted/python/context.py", line 59, in callWithContext
return self.currentContext().callWithContext(ctx, func, *args, **kw)
File "/usr/lib/python2.6/dist-packages/twisted/python/context.py", line 37, in callWithContext
return func(*args,**kw)
--- <exception caught here> ---
File "/usr/lib/python2.6/dist-packages/twisted/internet/gtk2reactor.py", line 199, in _doReadOrWrite
why = source.doRead()
File "/usr/lib/python2.6/dist-packages/twisted/internet/tcp.py", line 140, in doRead
return Connection.doRead(self)
File "/usr/lib/python2.6/dist-packages/twisted/internet/tcp.py", line 463, in doRead
return self.protocol.dataReceived(data)
File "/usr/lib/python2.6/dist-packages/ubuntuone/storageprotocol/client.py", line 1171, in dataReceived
StorageClient.dataReceived(self, data)
File "/usr/lib/python2.6/dist-packages/ubuntuone/storageprotocol/client.py", line 81, in dataReceived
request.RequestHandler.dataReceived(self, data)
File "/usr/lib/python2.6/dist-packages/ubuntuone/storageprotocol/request.py", line 172, in dataReceived
self.buildMessage(data)
File "/usr/lib/python2.6/dist-packages/ubuntuone/storageprotocol/request.py", line 219, in buildMessage
self.processMessage(message)
File "/usr/lib/python2.6/dist-packages/ubuntuone/syncdaemon/action_queue.py", line 149, in processMessage
result = ThrottlingStorageClient.processMessage(self, message)
File "/usr/lib/python2.6/dist-packages/ubuntuone/storageprotocol/request.py", line 260, in processMessage
str(message).replace("\n"," ")))
exceptions.Exception: peer cant handle message 'OK' {id: 161 type: OK }
Version is 1.1+r274, here's the config:
syncdaemon.conf:
[bandwidth_throttling]
on = True
read_limit = 2097152
write_limit = 24576
ubuntuone-client.conf:
[ubuntuone]
connected = True
connect = 0
show_applet = 0
bookmarked = True
xvfb-run fails to launch any more on karmic. Reverting the patch from
2:1.6.4-2ubuntu3 fixes the problem. This breaks any tool that uses
xvfb-run during its build (like openjdk-6).
impact: tools needing xvfb-run will fail (e.g. openjdk-6 does not perform any testsuite runs)
addressed: refactored to correctly wait for xvfb execution.
patch: see attached
discussion: regression potential is low, since xvfb-run doesn't actually function in karmic.
TEST CASE: the follow command should report "0":
xvfb-run -a -e /dev/null -s "-extension GLX" true; echo $?
ProblemType: Bug
Architecture: amd64
Date: Thu Nov 12 14:02:47 2009
DistroRelease: Ubuntu 10.04
Package: xvfb 2:1.6.4-2ubuntu4
ProcEnviron:
LANGUAGE=en_US.UTF-8
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: xorg-server
Uname: Linux 2.6.31-14-generic x86_64
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: landscape-client
This is on Jaunty beta:
All currently running landscape-* programs currently wake up far more
than is understandable on my machine, accounting for 1.3% of all wakeups
a piece (the sum of four being about 5%). A report from powertop reveals
10 wakeups (per process) during the default period. By comparison,
Rhythmbox which was playing music was consuming an average of 8.2
wakeups, and Transmission actively uploading at 10KBps only had 7.7
wakeups.
As I understand it, the landscape programs don't do much without some
paid support from Ubuntu, and as they are in the default install, care
should be made sure that they behave and should not wake the computer up
far more than it needs to.
We currently have a fetch_async function for downloading a single URL.
It would be nice to have one to retrieve a list of URLs, and have it
callback once all of them have completed. In particular this feature
will be used to fetch the files of the release-ugprade tool used for
dist-upgrades.
The attached branch implements the proposed behaviour, and also add a
helper function to parse the /etc/lsb-release, which is used in a couple
of spots already, and will be used in the release-upgrade feature as
well.
Handle release-upgrade messages in the packagemanager plugin
The client should handle messages for type "release-upgrade", which are
going to be issued by the server for requesting a system upgrade to a
newer release.
The packagemanager plugin should handle this message by enqueuing a task
for a release-upgrader task handler.
affects landscape
status inprogress
importance medium
assignee free.ekanayaka
milestone later
private yes
Landscape daemons fail to start when too many groups are available
Due to a bug in Twisted (http://twistedmatrix.com/trac/ticket/3226),
landscape client takes a long time to start, making the ping fail. Thus,
the watchdog tries to restart the daemons forever.
We should workaround this problem in Landscape by patching the
twisted.python.util to use the real initgroups call.
Add a new landscape-release-upgrader task handler script and class to
perform release upgrades.
The release-upgrader should fetch, verify and run the upgrade tool for
the target release specified by the task being handled.
affects landscape-client
status inprogress
importance medium
assignee free.ekanayaka
milestone 1.4.1
The upgrade-tool supports two useful environment variables, namely
DEBUG_UPDATE_MANAGER and RELEASE_UPRADER_ALLOW_THIRD_PARTY.
If set to "True" they enable respectively debug logging and support for
non-official mirrors in APT sources.list, which won't get disabled
during the upgrade.
We should expose them to the user via the Landscape UI.
affects landscape
status inprogress
importance medium
assignee free.ekanayaka
milestone 1.4.1
private yes
Update intrepid, jaunty and karmic to landscape-client 1.4.0
Landscape Client 1.4.0 has been released. We would like to get these
changes into Karmic, Intrepid and Jaunty. The required pieces of
information for a SRU follow (as laid out in the "Procedure" section of
https://wiki.ubuntu.com/StableReleaseUpdates).
=== Statement explaining the impact ===
New features have been developed since the versions of Landscape Client
that are currently in Intrepid, Jaunty and Karmic. We would like to make
sure all of our supported customers (even those on Intrepid and Jaunty
and Karmic) have access to these features. The notable ones are:
1) Support for release upgrades. From the Landscape web UI, it's now
possible to issue a system upgrade between to subsequent Ubuntu releases
(e.g. from jaunty to karmic), which will be performed using the regular
update-manager code in non-interactive mode.
2) Report Smart locking information. The client will now report the
server about Smart locks set on the system, which the Landscape UI is
going to display with a special icon.
3) Several bug fixes which improve the overall user experience.
For more details see Bug #456124, Bug #340843, Bug #465846, Bug
#476418, Bug #369000, Bug #450629, Bug #455217, Bug #462543, Bug #463321
and Bug #488108 (all mentioned in the debian/changelog of the proposed
packages).
=== How the bug has been addressed ===
We have been following the development procedure laid out in
https://wiki.ubuntu.com/LandscapeUpdates
=== Patches ===
The three branches for the new landscape-client intrepid, jaunty and
karmic source packages are attached to this bug, and are were derived
from
lp:ubuntu/intrepid/landscape-client
lp:ubuntu/jaunty/landscape-client
lp:ubuntu/karmic/landscape-client
respectively.
=== Detailed instructions how to reproduce the bug ===
N/A
=== Discussion ===
All the source packages have been subject to the QA process detailed in
the LandscapeUpdates document linked above.
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
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: xorg
IMPACT: Under certain circumstances, the X server hangs causing the
entire system to be non-responsive (including sysrq)
DEVELOPMENT: Karmic picked up the upstream fix in xserver-xorg-core
2:1.6.3-1ubuntu1
PATCH: Attached at <http://launchpadlibrarian.net/36321173/xorg-
server_1.6.0-0ubuntu14.1.debdiff>. Test builds available in my PPA
(https://launchpad.net/~broder/+archive/ubuntu-tests)
INSTRUCTIONS: There hasn't been a consistent way to reproduce the bug
found, but the hang seems to trigger more frequently under VMWare.
REGRESSION: This is a patch taken directly from upstream. It only
affects a handful of lines.
==
Original bug description:
*apport seems broken right now, so let me know if i need to upload
anything else*
on the xserver in jaunty, i get random hangs where the entire system is
unresponsive, meaning that i can't escape to a tty, restart the
computer, or even do a sysreq-REISUB. this has happened twice, both
times while using my bluetooth mouse, so that might be the cause of it.
in both logs there's a line that seems important:
[xkb] BOGUS LENGTH in write keyboard desc, expected 5976, got 5992
thanks,
matt drake
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.
Binary package hint: landscape-client
This is on Jaunty beta:
All currently running landscape-* programs currently wake up far more
than is understandable on my machine, accounting for 1.3% of all wakeups
a piece (the sum of four being about 5%). A report from powertop reveals
10 wakeups (per process) during the default period. By comparison,
Rhythmbox which was playing music was consuming an average of 8.2
wakeups, and Transmission actively uploading at 10KBps only had 7.7
wakeups.
As I understand it, the landscape programs don't do much without some
paid support from Ubuntu, and as they are in the default install, care
should be made sure that they behave and should not wake the computer up
far more than it needs to.
We currently have a fetch_async function for downloading a single URL.
It would be nice to have one to retrieve a list of URLs, and have it
callback once all of them have completed. In particular this feature
will be used to fetch the files of the release-ugprade tool used for
dist-upgrades.
The attached branch implements the proposed behaviour, and also add a
helper function to parse the /etc/lsb-release, which is used in a couple
of spots already, and will be used in the release-upgrade feature as
well.
Handle release-upgrade messages in the packagemanager plugin
The client should handle messages for type "release-upgrade", which are
going to be issued by the server for requesting a system upgrade to a
newer release.
The packagemanager plugin should handle this message by enqueuing a task
for a release-upgrader task handler.
affects landscape
status inprogress
importance medium
assignee free.ekanayaka
milestone later
private yes
Landscape daemons fail to start when too many groups are available
Due to a bug in Twisted (http://twistedmatrix.com/trac/ticket/3226),
landscape client takes a long time to start, making the ping fail. Thus,
the watchdog tries to restart the daemons forever.
We should workaround this problem in Landscape by patching the
twisted.python.util to use the real initgroups call.
Add a new landscape-release-upgrader task handler script and class to
perform release upgrades.
The release-upgrader should fetch, verify and run the upgrade tool for
the target release specified by the task being handled.
affects landscape-client
status inprogress
importance medium
assignee free.ekanayaka
milestone 1.4.1
The upgrade-tool supports two useful environment variables, namely
DEBUG_UPDATE_MANAGER and RELEASE_UPRADER_ALLOW_THIRD_PARTY.
If set to "True" they enable respectively debug logging and support for
non-official mirrors in APT sources.list, which won't get disabled
during the upgrade.
We should expose them to the user via the Landscape UI.
affects landscape
status inprogress
importance medium
assignee free.ekanayaka
milestone 1.4.1
private yes
Update intrepid, jaunty and karmic to landscape-client 1.4.0
Landscape Client 1.4.0 has been released. We would like to get these
changes into Karmic, Intrepid and Jaunty. The required pieces of
information for a SRU follow (as laid out in the "Procedure" section of
https://wiki.ubuntu.com/StableReleaseUpdates).
=== Statement explaining the impact ===
New features have been developed since the versions of Landscape Client
that are currently in Intrepid, Jaunty and Karmic. We would like to make
sure all of our supported customers (even those on Intrepid and Jaunty
and Karmic) have access to these features. The notable ones are:
1) Support for release upgrades. From the Landscape web UI, it's now
possible to issue a system upgrade between to subsequent Ubuntu releases
(e.g. from jaunty to karmic), which will be performed using the regular
update-manager code in non-interactive mode.
2) Report Smart locking information. The client will now report the
server about Smart locks set on the system, which the Landscape UI is
going to display with a special icon.
3) Several bug fixes which improve the overall user experience.
For more details see Bug #456124, Bug #340843, Bug #465846, Bug
#476418, Bug #369000, Bug #450629, Bug #455217, Bug #462543, Bug #463321
and Bug #488108 (all mentioned in the debian/changelog of the proposed
packages).
=== How the bug has been addressed ===
We have been following the development procedure laid out in
https://wiki.ubuntu.com/LandscapeUpdates
=== Patches ===
The three branches for the new landscape-client intrepid, jaunty and
karmic source packages are attached to this bug, and are were derived
from
lp:ubuntu/intrepid/landscape-client
lp:ubuntu/jaunty/landscape-client
lp:ubuntu/karmic/landscape-client
respectively.
=== Detailed instructions how to reproduce the bug ===
N/A
=== Discussion ===
All the source packages have been subject to the QA process detailed in
the LandscapeUpdates document linked above.
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)
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
Yahoo server authentication changed: Pidgin =<2.5.6 will not connect to Yahoo! servers.
Binary package hint: pidgin
Just hangs trying to connect to yahoo.
all other account types seem to be working fine just not yahoo.
pidgin 2.5.5
====================================
pidgin debug log :
(09:19:46) account: Connecting to account MyYahooAccount
(09:19:46) connection: Connecting. gc = 0x8e3e1c8
(09:19:46) dns: DNS query for 'scs.msg.yahoo.com' queued
(09:19:46) dns: DNS child 5936 no longer exists
(09:19:46) dns: Created new DNS child 6064, there are now 1 children.
(09:19:46) dns: Successfully sent DNS request to child 6064
(09:19:48) dns: Got response for 'scs.msg.yahoo.com'
(09:19:48) dnsquery: IP resolved for scs.msg.yahoo.com
(09:19:48) proxy: Attempting connection to 76.13.15.32
(09:19:48) proxy: Connecting to scs.msg.yahoo.com:5050 with no proxy
(09:19:48) proxy: Connection in progress
(09:19:49) proxy: Connecting to scs.msg.yahoo.com:5050.
(09:19:49) yahoo: 96 bytes to read, rxlen is 116
(09:19:49) yahoo: Yahoo Service: 0x57 Status: 1
(09:19:49) yahoo: yahoo status: 12
====================================
ping to yahoo server :
ping scs.msg.yahoo.com
PING scs.msg.yahoo.com (76.13.15.36) 56(84) bytes of data.
64 bytes from cs108.msg.ac4.yahoo.com (76.13.15.36): icmp_seq=1 ttl=48 time=638 ms
64 bytes from cs108.msg.ac4.yahoo.com (76.13.15.36): icmp_seq=2 ttl=48 time=628 ms
64 bytes from cs108.msg.ac4.yahoo.com (76.13.15.36): icmp_seq=3 ttl=48 time=659 ms
64 bytes from cs108.msg.ac4.yahoo.com (76.13.15.36): icmp_seq=4 ttl=48 time=817 ms
64 bytes from cs108.msg.ac4.yahoo.com (76.13.15.36): icmp_seq=5 ttl=48 time=659 ms
====================================
netstat :
tcp 0 0 xxx.xxx.xxx.xxx:49159 76.13.15.32:5050 ESTABLISHED
tcp 0 0 xxx.xxx.xxx.xxx:52467 68.180.217.8:5050 ESTABLISHED
====================================
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.5.5-1ubuntu8.1
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: pidgin
Uname: Linux 2.6.28-13-generic i686
Smart doesn't import proxy information from Landscape
The Landscape Team has proposed an SRU to solve this bug.
This bug was supposed to be fixed by the smart intrepid SRU for Bug
#236884 (version 1.1.1~bzr20081010-0ubuntu1.8.10.0), but the needed one-
liner patch didn't actually get included in the package. So a new SRU
for intrepid is needed. Jaunty, Karmic and Lucid versions all have the
patch already applied.
=== 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 ===
Setting a smart configuration value in the Landscape smart plugin, that makes smart use the same proxy used in the Landscape configuration if any.
=== Detailed instructions how to reproduce the bug ===
Simply install landscape-client in an environment using a proxy.
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 ]
GRUB installation fails if installing to certain non-ext3 filesystems
Just like Bug #14010 but not just for JFS.
GRUB will fail to install during setup when it is being installed to a
partition (as opposed to a boot sector) formatted as anything but
ext2/3fs, including JFS and ReiserFS.
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
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
BOTH Network controller: Intel Corporation Wireless WiFi Link 5100 AND Ethernet controller: Marvell Technology Group Ltd. 88E8040T PCI-E Fast Ethernet Controller (rev 12) FAIL TO LOAD!
