updates for karmic and lucid needed to get maven plugins building
Binary package hint: antlr
this report holds all updates for karmic needed to get maven plugins
building and working. Test packages can be found in
https://launchpad.net/~ubuntu-java/+archive/maven
Binary package hint: apparmor
Currently (as of Karmic Beta, at least) usr.sbin.dnsmasq reads:
(...)
/etc/dnsmasq.conf r,
/usr/sbin/dnsmasq mr,
/var/run/dnsmasq.pid w,
/var/lib/misc/dnsmasq.leases rw, # Required only for DHCP server usage
}
The line '/var/run/dsnmasq.pid w' will reflect -- at least on my system
-- the wrong interface if I am using wireless. The actual file created
under /var/run has the interface name on it, like
'/var/run/dsnmasq.wlan0.pid'.
c.f., messages issued by audit:
[18682.250062] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
[18682.400783] Registered led device: b43-phy0::tx
[18682.400843] Registered led device: b43-phy0::rx
[18682.400907] Registered led device: b43-phy0::radio
[18682.492454] wlan0: Trigger new scan to find an IBSS to join
[18683.627086] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[18683.627709] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
[18683.627716] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
[18683.627721] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[18683.940921] type=1502 audit(1254949451.286:128): operation="mknod" pid=10379 parent=1841 profile="/usr/sbin/dnsmasq" requested_mask="w::" denied_mask="w::" fsuid=0 ouid=0 name="/var/run/nm-dnsmasq-wlan0.pid"
[18683.941005] type=1502 audit(1254949451.286:129): operation="open" pid=10379 parent=1841 profile="/usr/sbin/dnsmasq" requested_mask="w::" denied_mask="w::" fsuid=0 ouid=0 name="/var/run/nm-dnsmasq-wlan0.pid"
[18683.941124] type=1502 audit(1254949451.286:130): operation="file_perm" pid=10379 parent=1841 profile="/usr/sbin/dnsmasq" requested_mask="w::" denied_mask="w::" fsuid=0 ouid=0 name="/var/run/nm-dnsmasq-wlan0.pid"
[18686.012729] wlan0: Trigger new scan to find an IBSS to join
[18689.010238] wlan0: Trigger new scan to find an IBSS to join
[18689.982701] wlan0: Creating new IBSS network, BSSID 92:56:7a:40:52:69
[18692.560043] wlan0: no IPv6 routers present
ProblemType: Bug
Architecture: amd64
Date: Wed Oct 7 16:24:17 2009
Dependencies:
DistroRelease: Ubuntu 9.10
Package: apparmor-profiles 2.3.1+1403-0ubuntu25
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-12.40-generic
SourcePackage: apparmor
Uname: Linux 2.6.31-12-generic x86_64
[Karmic] After restarting AppArmor, aa-logprof doesn't seem to load the existing profiles.
Binary package hint: apparmor
When I attempt to create a new profile with the "aa-genprof" command, I
find that none of the changes I make through the interactive apparmor
log parser stick (I am using the auditd, by the way). If I try to
generate a profile for my IRC client, for example, I find that whenever
I perform "aa-logprof" that I get asked the same questions over and over
again. They do not stick, even after restarting apparmor or even after
rebooting. And I get the following error when I try to restart apparmor
whenever one of my generated profiles exists in /etc/apparmor.d/:
sudo /etc/init.d/apparmor restart
* Reloading AppArmor profiles
Found reference to variable HOME, but is never declared
Found reference to variable HOME, but is never declared
The above error implies that the #include <tunables/global> line was not
included in the profile. If I add that line, it fixes the problem
temporarily, but after I run aa-logprof again, I encounter the same
audit logs again and again. Further, when I restart apparmor, I find
that the #include <tunables/global> line has disappeared from my
profile.
Also, when I try to put all profiles into enforce mode, I get a bit more
detailed of an error:
sudo aa-enforce /etc/apparmor.d/*
Setting /etc/apparmor.d/usr.bin.kopete to enforce mode.
/sbin/apparmor_parser: cannot use or update cache, disable, or force-complain via stdin
Found reference to variable HOME, but is never declared
So, basically, AppArmor profile generation in Karmic is broken.
Here is my uname -a:
Linux 2.6.31-12-generic #41-Ubuntu SMP Wed Oct 7 19:37:12 UTC 2009
x86_64 GNU/Linux
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
SRU information:
--------------------------
Impact: Causes unhandled exceptions in Apport when trying to report a crash against a program which does not belong to a package any more. (See bug trail for common examples: (1) file disappeared between jaunty and karmic, and (2) program is a hardlink created in postinst).
Fix: http://bazaar.launchpad.net/%7Eapport-
hackers/apport/trunk/revision/1629 ; this does not magically cause the
original crash report to be reportable, but gives a proper error message
instead of just crashing Apport.
Regression potential: Handling this situation in obsolete_packages()
could just cause a similar problem to appear in a later code path. This
would not mean a regression, since the crash is unreportable either way.
So I don't see a real regression potential here.
ProblemType: Crash
Architecture: i386
Date: Sat Sep 5 21:22:30 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apport-gtk
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: wl
Package: apport-gtk 1.8.2-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
PythonArgs: ['/usr/share/apport/apport-gtk']
SourcePackage: apport
Title: apport-gtk crashed with KeyError in __getitem__()
Uname: Linux 2.6.31-9-generic i686
UserGroups: adm admin cdrom dialout dip lpadmin plugdev sambashare
updates for karmic and lucid needed to get maven plugins building
Binary package hint: antlr
this report holds all updates for karmic needed to get maven plugins
building and working. Test packages can be found in
https://launchpad.net/~ubuntu-java/+archive/maven
updates for karmic and lucid needed to get maven plugins building
Binary package hint: antlr
this report holds all updates for karmic needed to get maven plugins
building and working. Test packages can be found in
https://launchpad.net/~ubuntu-java/+archive/maven
Binary package hint: clamav
New upstream release is out. It has gone into Lucid already. Per the
microversion update exception for clamav, it will go to Jaunty and
Karmic in -proposed/updates. Since it has no security fixes, Dapper,
Hardy, and Intrepid will be updated in Backports.
the CC is returning incorrect networkIndex values on describeInstances
the cc was setting instance networkIndex to the *index* of the
networkIndex list, instead of the networkIndex list value itself. This
bug may cause problems with public network addressing. Fixed in revno
933.
[regression] euca_rootwrap fixes affected eucalyptus power management (powerwake)
cluster/handlers.c: euca_rootwrap rework did not whitelist powerwake;
however, powerwake does *not* need root privs, drop euca_rootwrap
wrapper.
===========
SRU Verification
This fix is bundled with a set of unrelated SRU fixes for Eucalyptus.
To test this:
1) From a working UEC cluster, ensure that you have availability on your nodes:
$ euca-describe-availability-zones verbose
2) Ensure that your nodes support:
a) one of [ pm-suspend | pm-hibernate | poweroff ]
b) and wake-on-lan (might need to check bios, sudo ethtool eth0)
3) Adjust your eucalyptus scheduling algorithm to POWERSAVE on the front end
$ sudo sed -i "s/^SCHEDPOLICY=.*/SCHEDPOLICY=POWERSAVE/" /etc/eucalyptus/eucalyptus.conf
4) Restart eucalyptus
$ sudo restart eucalyptus
5) Make sure there are no running instances in your cloud
6) Watch the output of the CC, which will note the status of each node, waiting for 300 seconds of inactivity before putting the node to sleep
$ tail -f /var/log/eucalyptus/cc.log
...
[Tue Nov 3 14:39:09 2009][023511][EUCADEBUG ] node 192.168.1.126 idle since 1257280677: (72/300) seconds
...
[Tue Nov 3 16:09:57 2009][017368][EUCADEBUG ] sending powerdown to node: 192.168.1.126, http://192.168.1.126:8775/axis2/services/EucalyptusNC
...
7) After 300 seconds, you should see the node either suspend, hibernate, or poweroff, based on its capability
8) Once the node(s) are sleeping, run an instance. Eucalyptus should dynamically resume (powerwake) the node and deploy the new instance there.
$ euca-run-instances $EMI -k mykey -t c1.medium
Regression potential should be minimal, and restricted to Eucalyptus SCHEDPOLICY=POWERSAVE users, which is not the default scheduling policy.
===========
Relay denied from eucalyptus registration emails - source address is wrong.
Eucalyptus sends registration emails via SMTP to localhost.
Unfortunately it doesn't set the source IP address to one of the
localhost addresses. Instead it uses the IP address of an ethernet
interface.
That falls foul of the default relay control ACL in postfix, when
postfix is in Smarthost configuration.
Oct 23 14:47:42 gaffer postfix/smtpd[31553]: connect from gaffer.lab.man.cpwn.lan[10.99.67.10]
Oct 23 14:47:42 gaffer postfix/smtpd[31553]: NOQUEUE: reject: RCPT from gaffer.lab.man.cpwn.lan[10.99.67.10]: 554 5.7.1 <xxx@yyy.com>: Relay access denied; from=<xxx@yyy.com> to=<xxx@yyy.com> proto=ESMTP helo=<gaffer.lab.man.cpwn.lan>
Oct 23 14:47:42 gaffer postfix/smtpd[31553]: disconnect from gaffer.lab.man.cpwn.lan[10.99.67.10]
ProblemType: Bug
.etc.eucalyptus.eucalyptus.cc.conf: CC_NAME="isp-lab"
Architecture: amd64
Date: Fri Oct 23 14:48:27 2009
DistroRelease: Ubuntu 9.10
Package: eucalyptus-cloud 1.6~bzr931-0ubuntu7
ProcEnviron:
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-server
SourcePackage: eucalyptus
Uname: Linux 2.6.31-14-server x86_64
==================
Karmic release notes:
Confirmation email for new UEC users not sent
When a new user is created in the UEC admin interface an email is sent
to the user to confirm the registration. A bug in the smtp configuration
of UEC prevents the Cloud controller from accepting and forwarding the
confirmation email to the end user. The workaround is to edit the
postfix configuration file (/etc/postfix/main.cf) to comment the
mynetworks option and add a mynetworks_style option set to host instead
and reload postfix (459101):
#mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
mynetworks_style=host
==================
Eucalyptus SRU
Impact:
When a new user is created an confirmation email is send. However the default configuration of postfix refuses to accept the smtp connection opened by the eucalyptus-cloud process.
How the bug has been addressed:
The local configuration of postfix is modified by eucalyptus-cloud postinst script via the postconf command to accept messages send from the host (mynetwork_style=host).
To reproduce the bug:
1. Create a new user via the web admin interface with a valid email. Check that the email hasn't been accepted in /var/log/mail.log.
2. After the update, /etc/postfix/main.cf should have two of its options modified (mynetwork_style set to host and mynetwork commented).
3. Create a new user via the web admin interface with a valid email. The confirmation email should be accepted (in /var/log/mail.log) and be successfully delivered.
Regression potential:
If the CC has been configured to accept mail from the network for another reason, the configuration will be broken after the upgrade.
Evolution hangs when double-clicking on attachment
Binary package hint: evolution
[9.10 RC + some updates] Evolution hangs when I:
1) select an email with an attachment from an IMAPS account (don't know if its related to IMAP)
2) open the bar that contains the attachments by clicking on the arrow
3) double-click on the attachment
100% reproducible
ProblemType: Bug
Architecture: amd64
Date: Sun Oct 25 23:29:49 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.3)
NonfreeKernelModules: nvidia
Package: evolution 2.28.1-0ubuntu1
ProcEnviron:
LANG=de_AT.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: evolution
Uname: Linux 2.6.31-14-generic x86_64
WORKAROUND:
asac's patch bypasses the consequence (infinite loop, with high CPU
usage and eating up all memory). Of course, *why* height == 0 is another
issue.
fuse-utils postinst fails if fuse-utils is a new install during a release upgrade
Its difficult to trigger this bug, the only way I found is to remove
fuse-utils and ubuntu-standard. But we got at least one report where a
fuse-util upgrade failed so I think this needs fixing. Given how trivial
the diff is I think a regression test is sufficient.
TEST CASE:
- use jaunty install
- enable jaunty-proposed
- perform a release upgrade with kubuntu
- verify that there are no regressions
- verify that fuse-utils is installed afterwards
Binary package hint: update-manager
no idea, el error se produjo en fuse, lirc y otras dependencias
ProblemType: Package
Architecture: i386
Date: Tue Oct 6 19:05:44 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg returned an error code (1)
Package: update-manager 1:0.125.6
PackageArchitecture: all
ProcVersionSignature: Ubuntu 2.6.27-14.41-generic
SourcePackage: update-manager
Title: package update-manager 1:0.125.6 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg returned an error code (1)
Uname: Linux 2.6.27-14-generic i686
after completing the karmic beta install wizard, there appears a dialog box instructing the user to reboot to boot into the new installation.
after confirming a reboot, gdm started dying and respawning in an endless loop (or at least for a few minutes before i shut down the machine).
this does not happen when booting into the installed OS and shutting it down/rebooting, only when rebooting after installing from the CD..
this causes the screen to flicker horribly, and the machine is just
stuck like that until shut down.
this is how it looks like :
http://www.youtube.com/watch?v=VpWpY-0A8Jo
the text flashing on the screen is an endless loop of:
init: gdm main procedd ([pid]) terminated with status 1
init: gdm main process ended, respawning
init: ubiquity main process ([pid]) terminated with status 1
New gdm does not have the FailsafeXServer config option
Binary package hint: gdm
gdm 2.20 had options in /etc/gdm/gdm.conf (in particular
FailsafeXServer) for specifying an action to take when X is failing to
start up. We attached a failsafe session (aka bulletproof-x) to be
invoked by gdm in these situations, which users could use to diagnose
and work around issues.
These options were implemented in the 'deal_with_x_crashes()' function
in gdm.c. Near as I can tell, this gdm feature was not included in the
new gdm rewrite, so we are seeing a regression here. The problem is
that whereas in the past the user would be dumped into a debugging
session, now gdm is simply trying multiple times, failing each time, and
then exiting (which then leads to the quite severe bug 441638).
Anyway, the end result is that we no longer have a debugging failsafe
mode available for users, they're just left with a non-functioning
system. Please either restore the missing functionality, or provide an
analogous mechanism to which we can attach a debugging session mode.
gnome-settings-daemon crashed with SIGSEGV in g_unix_mount_get_mount_path()
Binary package hint: gnome-settings-daemon
Just after update to karmic.
Discovered a SMART error on System HD. System on LVM.
ProblemType: Crash
Architecture: amd64
Date: Wed Aug 26 19:30:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
LiveMediaBuild: Ubuntu 9.04 "Jaunty Jackalope" - Release amd64 (20090420.1)
Package: gnome-settings-daemon 2.27.90-0ubuntu1
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-7.27-generic
SegvAnalysis:
Segfault happened at: 0x7f8fff15e749 <g_unix_mount_get_mount_path+9>: mov (%rdi),%rax
PC (0x7f8fff15e749) ok
source "(%rdi)" (0xab00000132) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
g_unix_mount_get_mount_path ()
?? ()
?? () from /usr/lib/libglib-2.0.so.0
g_main_context_dispatch ()
?? () from /usr/lib/libglib-2.0.so.0
Title: gnome-settings-daemon crashed with SIGSEGV in g_unix_mount_get_mount_path()
Uname: Linux 2.6.31-7-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
*** SRU stuff ***
The patch is located here: http://launchpadlibrarian.net/35063102/gnome-
settings-daemon_2.28.1-0ubuntu2.debdiff
[Impact of bug]
gnome-settings-daemon will crash if you the volume is unmouned whilst a warning is displayed on screen, and then you click the "Examine" button.
[Description of change]
The change makes a copy of the path string returned from g_unix_mount_get_mount_path() before calling gtk_dialog_run(). The saved string is used when gtk_dialog_run() returns, rather than calling g_unix_mount_get_mount_path() on a GUnixMountEntry which might have been free'd if the volume was unmounted whilst in the main loop.
Care is taken to make sure that the copy of the string is not leaked
This will mean that baobab will open to an empty mount path if the user
presses "Examine" on a volume that was just unmounted. Ideally, the low-
disk space warning dialog will just disappear if the volume is unmounted
whilst the warning is on screen, but a patch to implement this would be
much more intrusive (and is something I will pursue separately upstream,
but would not really be suitable for a SRU). This patch just stops
gnome-settings-daemon from crashing.
[Test case]
To test, you need to trigger the low-disk space warning on a mount that is listed in /etc/fstab, and can be unmounted without affecting the rest of the system. To artificially trigger the low disk-space warning, adjust the thresholds in /apps/gnome_settings_daemon/housekeeping.
Test 2.28.1-0ubuntu1 and 2.28.1-0ubuntu2 in turn.
When the low disk-space warning for the particular mount is displayed on screen:
1) Unmount the volume
2) Press the "Examine" button.
With the old version, gnome-settings-daemon will crash at step 2. With
the new version of gnome-settings-daemon, baobab will open successfully
(albeit, pointing to a now empty folder)
[Regression potential]
None - the code change is fairly minimal and self-contained.
Binary package hint: gnome-control-center
The "locate pointer" checkbox in System -> Preferences -> Assistive
Technologies -> Mouse Accessibility window can't be checked. It is
active (with white background), but it remains unchecked when you click
on it.
I'm using Karmic Beta on VirtualBox.
ProblemType: Bug
Architecture: i386
Date: Sat Oct 3 21:08:23 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-at-properties
Package: gnome-control-center 1:2.28.0-0ubuntu3
ProcEnviron:
LANG=es_ES.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: gnome-control-center
Uname: Linux 2.6.31-11-generic i686
*** SRU stuff ***
[Impact of bug]
"locate pointer" checkbox in gnome-mouse-properties dialog cannot be checked, and locate pointer feature does not work
[Description of change]
The bug was caused by g-s-d not honouring libexec at build time, and thus trying to spawn gsd-locate-pointer with an incorrect path. The patch addresses this by making sure that libexec is honoured
[Test case]
With each version of gnome-settings-daemon in turn (2.28.1-0ubuntu1 and 2.28.1-0ubuntu2), do the following:
1) Try to enable "Show the position of pointer when the Control key is pressed" in gnome-mouse properties.
2) Press CTRL key and observe behaviour.
With the old version of gnome-settings-daemon, it is not possible to
check the checkbox in step 1. The CTRL key doesn't show where the
pointer is in step 2.
With the new version of gnome-settings-daemon, it is possible to turn on
the feature. Pressing the CTRL key will show an animation where the
mouse cursor is positioned.
[Regression potential]
None - this patch just makes sure that libexecdir is honoured properly in the mouse plugin. libexecdir is used in only one place in this plugin
updates for karmic and lucid needed to get maven plugins building
Binary package hint: antlr
this report holds all updates for karmic needed to get maven plugins
building and working. Test packages can be found in
https://launchpad.net/~ubuntu-java/+archive/maven
gtkiconview issue, evolution chokes when attaching files sometimes
This is a new bug in karmic, not present in jaunty.
I have a 6mb pdf file which consists of scanned pages. I try to attach
it to an e-mail in evolution but it becomes unresponsive and top shows
it's taking up to 600mb and growing. The same does not happen with 6mb
of random data (courtesy of /dev/urandom). I am not going to attach the
file here since it is copyrighted material, but I can surely provide the
file privately to whoever needs it for debugging purposes.
Update: the same happens with a 900k zip file, again I can't post it
here but can send it privately. This time there are no huge scanned pdfs
involved but there still are pdfs in the zip file.
Evolution hangs when double-clicking on attachment
Binary package hint: evolution
[9.10 RC + some updates] Evolution hangs when I:
1) select an email with an attachment from an IMAPS account (don't know if its related to IMAP)
2) open the bar that contains the attachments by clicking on the arrow
3) double-click on the attachment
100% reproducible
ProblemType: Bug
Architecture: amd64
Date: Sun Oct 25 23:29:49 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.3)
NonfreeKernelModules: nvidia
Package: evolution 2.28.1-0ubuntu1
ProcEnviron:
LANG=de_AT.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: evolution
Uname: Linux 2.6.31-14-generic x86_64
WORKAROUND:
asac's patch bypasses the consequence (infinite loop, with high CPU
usage and eating up all memory). Of course, *why* height == 0 is another
issue.
Evolution hangs when double-clicking on attachment
Binary package hint: evolution
[9.10 RC + some updates] Evolution hangs when I:
1) select an email with an attachment from an IMAPS account (don't know if its related to IMAP)
2) open the bar that contains the attachments by clicking on the arrow
3) double-click on the attachment
100% reproducible
ProblemType: Bug
Architecture: amd64
Date: Sun Oct 25 23:29:49 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.3)
NonfreeKernelModules: nvidia
Package: evolution 2.28.1-0ubuntu1
ProcEnviron:
LANG=de_AT.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: evolution
Uname: Linux 2.6.31-14-generic x86_64
WORKAROUND:
asac's patch bypasses the consequence (infinite loop, with high CPU
usage and eating up all memory). Of course, *why* height == 0 is another
issue.
Desktop entry needs the X-Ubuntu-Gettext-Domain key
Binary package hint: ibus
This bug affects users with a localised version of Ubuntu, in which the
"System > Preferences > IBus Preferences" menu entry of the default
desktop installation appears untranslated (although it is translated in
Launchpad).
TEST CASE:
1. In a localized system using a non-English locale and with complete XSane translations in Launchpad but not complete upstream (e.g. Galician, 'gl'), go to System > Preference
2. The "IBus Preferences" entry appears untranslated
In order for translations in Launchpad to be used in the .desktop menu
entry, bus/ibus.desktop.in (or bus/ibus.desktop after the build) needs
to be added the 'X-Ubuntu-Gettext-Domain=ibus' key. Otherwise
translations cannot be used at runtime and the menu entry for ibus
appears untranslated for those languages not providing an upstream
translation.
See
https://wiki.ubuntu.com/UbuntuDevelopment/Internationalisation#Desktop%20Entries
for more information.
The attached debdiff by LI Daobing addresses this issue by adding the 'X
-Ubuntu-Gettext-Domain=ibus' key to debian/ibus.desktop.in and debian
/ibus-setup.desktop.in
updates for karmic and lucid needed to get maven plugins building
Binary package hint: antlr
this report holds all updates for karmic needed to get maven plugins
building and working. Test packages can be found in
https://launchpad.net/~ubuntu-java/+archive/maven
updates for karmic and lucid needed to get maven plugins building
Binary package hint: antlr
this report holds all updates for karmic needed to get maven plugins
building and working. Test packages can be found in
https://launchpad.net/~ubuntu-java/+archive/maven
apparmor complains about write access to a readonly file
When doing libvirt/apparmor ISO testing, I noticed that if I try to create a VM via an ISO image, I get the following apparmor denied message:
type=APPARMOR_DENIED msg=audit(1255714703.311:56): operation="open" pid=31330 parent=1 profile="libvirt-7e7f916e-ff5a-c997-e9f6-c379793fd5be" requested_mask="::rw" denied_mask="::w" fsuid=0 ouid=1000 name="/home/jamie/vms/isos/karmic/karmic-desktop-i386.iso"
What is happening is that libvirt is for some reason trying to write to this file, but it shouldn't. virt-manager shows this device as readonly and the XML for the VM shows it too:
<disk type='file' device='cdrom'>
<source file='/home/jamie/vms/isos/karmic/karmic-desktop-i386.iso'/>
<target dev='hdc' bus='ide'/>
<readonly/>
</disk>
The installation proceeds just fine and this isn't a regression, but
libvirt should not try to write to installation media like this. I
encountered this when installing via virt-manager using the following:
local ISO, os type: generic/generic, kvm/i686, 512, 1 vcpu, 8GB disk,
don't allocate now
ProblemType: Bug
Architecture: amd64
Date: Fri Oct 16 12:47:32 2009
DistroRelease: Ubuntu 9.10
Package: libvirt-bin 0.7.0-1ubuntu11
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.47-generic
SourcePackage: libvirt
Uname: Linux 2.6.31-14-generic x86_64
updates for karmic and lucid needed to get maven plugins building
Binary package hint: antlr
this report holds all updates for karmic needed to get maven plugins
building and working. Test packages can be found in
https://launchpad.net/~ubuntu-java/+archive/maven
updates for karmic and lucid needed to get maven plugins building
Binary package hint: antlr
this report holds all updates for karmic needed to get maven plugins
building and working. Test packages can be found in
https://launchpad.net/~ubuntu-java/+archive/maven
This bug usually manifests itself as a "sticky keyboard", but the
keyboard is fine.
1) if I disable the "Internal Pointer Device" in the bios of my laptop, the bug goes away completely.
2) by doing "cat /proc/interrupts | grep i8042" I can watch the interrupt count on int 12 climbing. Even a very light touch on the trackpad (too light to even cause the cursor to move), will cause about 600 interrupts. A 1/2 or 1/4 second touch will generate ~600 interrupts and take about 2 to 3 seconds to process. Any cursor movement using the trackpad prevents any typing for at least 2 seconds.
3) I can reproduce the problem 100% by touching the trackpad while typing. Any typing is delayed or lost while the touchpad is being touched.
4) The trackpad and the keyboard both share the i8042, so it seems pretty clear that problem is around here somewhere.
PS. My laptop is a Toshiba Portege M300. I'm running jaunty, but I've had the problem in feist and hardy too.
> lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
For those of us afflicted by this bug it makes the system pretty
difficult to use.
http://ubuntuforums.org/showthread.php?t=772773
Several Huawei USB dongle don't work with kernel 2.6.31-12.40 (2.6.31.1 update related)
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
linux-image-virtual (i386): many modules missing on Karmic
linux-image-virtual doesn't contain module binfmt_misc, whereas linux-
image-generic does.
I am using virtual machine to have "boxed" environment for cross-
compilation with scratchbox, which needs binfmt_misc to execute ARM
binaries.
Currently, I need to use the "generic" flavour of the Linux kernel in
the virtual machine.
$ dpkg -l "*virtual*"
ii linux-image-2.6.31-14-virtual 2.6.31-14.47 Linux kernel image for version 2.6.31 on x86/x86_64
ii linux-image-virtual 2.6.31.14.27 Linux kernel image for virtual machines
ii linux-virtual 2.6.31.14.27 Complete Linux kernel for virtual machines
$ uname -a
Linux vm-xubuntu 2.6.31-14-generic-pae #47-Ubuntu SMP Thu Oct 15 03:26:34 UTC 2009 i686 GNU/Linux
$ cat /proc/version_signature
Ubuntu 2.6.31-14.47-generic-pae
apparmor complains about write access to a readonly file
When doing libvirt/apparmor ISO testing, I noticed that if I try to create a VM via an ISO image, I get the following apparmor denied message:
type=APPARMOR_DENIED msg=audit(1255714703.311:56): operation="open" pid=31330 parent=1 profile="libvirt-7e7f916e-ff5a-c997-e9f6-c379793fd5be" requested_mask="::rw" denied_mask="::w" fsuid=0 ouid=1000 name="/home/jamie/vms/isos/karmic/karmic-desktop-i386.iso"
What is happening is that libvirt is for some reason trying to write to this file, but it shouldn't. virt-manager shows this device as readonly and the XML for the VM shows it too:
<disk type='file' device='cdrom'>
<source file='/home/jamie/vms/isos/karmic/karmic-desktop-i386.iso'/>
<target dev='hdc' bus='ide'/>
<readonly/>
</disk>
The installation proceeds just fine and this isn't a regression, but
libvirt should not try to write to installation media like this. I
encountered this when installing via virt-manager using the following:
local ISO, os type: generic/generic, kvm/i686, 512, 1 vcpu, 8GB disk,
don't allocate now
ProblemType: Bug
Architecture: amd64
Date: Fri Oct 16 12:47:32 2009
DistroRelease: Ubuntu 9.10
Package: libvirt-bin 0.7.0-1ubuntu11
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.47-generic
SourcePackage: libvirt
Uname: Linux 2.6.31-14-generic x86_64
/var/log fills up with "all normal" messages @ about 575/sec fill up the available space
Forum thread is here
http://ubuntuforums.org/showthread.php?t=1284691&page=1
System Karmic Beta i386
Machine Dell Inspiron 1000 Laptop
Celeron 2.4 running 256MB RAM 40 GB HDD
Partitioning:
SDA1 100 MB with /boot
SDA2 764 MB swap
SDA3 6.4 GB with /
SDA4 29.5 GB /home
Problem:
After the initial install from alternate cd, and system update to -14
kernel version, the computer could not boot in to gnome or xterm.
“The configuration defaults for GNOME Power Manager have not been
installed correctly. Please contact your computer administrator."
further investigation showed that the disk is full and in particular the
/var/log directory occupied all available space for root. These
particular files are a problem:
sys.log is 1.7 GB
kern.log is 1.6 GB
messages are 700 mb
copies are available if needed.
Dmesg is attached.
64bit kernels inappropriately reporting they are using NX emulation
At boot, the 64bit kernels are reporting:
[ 0.000000] Using x86 segment limits to approximate NX protection
This is not correct, as NX bits do not need extra work to set up on
64bit. The "nx_enabled" flag is not being correctly set, so the message
is misleading.
The trace event patch I wrote during karmic gave readahead events for
each open() syscall, along with the filename.
It turns out that exec() is kinda useful too. I've updated the patch to
add these, and for completeness uselib() as well.
Please apply in an SRU so we can ship better readahead!
suspend_test_finish warning triggers too easily, increase timeout to match mainline times
Many of these messages are basically cosmetic noise, the average time to
resume is actually 8.2s when older hardware is taken into account. SATA
reconnect alone is allowed to take up to 5s therefore a 5s timeout is
wholy too low for this message. Upstream has upped this limit to 10s.
Using this instance to track the integration of this upstream change
into the lucid and karmic kernels.
If your resume is taking a very long time then please file a new bug.
=== ORIGINAL DESCRIPTION ===
Received message about kernel crash after logging in.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: yossi 2394 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 11'
Mixer name : 'Analog Devices AD1981B'
Components : 'AC97a:41445374'
Controls : 28
Simple ctrls : 20
Date: Thu Oct 29 23:34:16 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=3210adf9-ff09-4dbb-9d3b-dc431a419062
MachineType: TOSHIBA PORTEGE M200
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=9ba59e59-1134-4205-baef-87a673f95ab3 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
linux-backports-modules-2.6.31-14-generic N/A
linux-firmware 1.24
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x80/0x90()
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 10/24/2005
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.80
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.80:bd10/24/2005:svnTOSHIBA:pnPORTEGEM200:pvrPPM20E-0053C-EN:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: PORTEGE M200
dmi.product.version: PPM20E-0053C-EN
dmi.sys.vendor: TOSHIBA
/var/log fills up with "all normal" messages @ about 575/sec fill up the available space
Forum thread is here
http://ubuntuforums.org/showthread.php?t=1284691&page=1
System Karmic Beta i386
Machine Dell Inspiron 1000 Laptop
Celeron 2.4 running 256MB RAM 40 GB HDD
Partitioning:
SDA1 100 MB with /boot
SDA2 764 MB swap
SDA3 6.4 GB with /
SDA4 29.5 GB /home
Problem:
After the initial install from alternate cd, and system update to -14
kernel version, the computer could not boot in to gnome or xterm.
“The configuration defaults for GNOME Power Manager have not been
installed correctly. Please contact your computer administrator."
further investigation showed that the disk is full and in particular the
/var/log directory occupied all available space for root. These
particular files are a problem:
sys.log is 1.7 GB
kern.log is 1.6 GB
messages are 700 mb
copies are available if needed.
Dmesg is attached.
[SRU] [karmic] Authentication failure from Windows 7 when domain joined.
Binary package hint: samba
When authenticating to a domain joined samba server with NTLMv2 from a
Windows 7 client, a valid password is being denied. The same request
succeeded with NTLMv1. The key to this repro is accessing the server
via a hostname so Windows 7 adds a SPN to the target information section
of the NTLMv2 Response.
=================
Karmic release notes:
Windows 7 systems not authenticating to Karmic samba domain controllers
After upgrading a samba domain controller to Karmic Windows 7 domain
members will not be able to authenticate to the domain controller even
if they had their registry settings modified prior to joining the Samba
Domain (as outlined in http://wiki.samba.org/index.php/Windows7). A fix
for this issue is expected to be provided in a post-release update
immediately after the Ubuntu 9.10 release (462626).
=================
Screensaver not inhibited while playing movies in browser
Binary package hint: totem
Using gnome-power-manager 2.26.1-0ubuntu3.
Totem is not capable to stop the screen blanking: after the timeout set in the gconf keys to control gnome-power-manager, the screen is blanked even if totem is playing a video.
This is a karmic problem.
the problem is not in gnome-screensaver, because I've disabled it and
set the time as 2 ours.
ProblemType: Bug
Architecture: amd64
Date: Thu May 28 01:04:23 2009
DistroRelease: Ubuntu 9.10
Package: totem 2.26.2-0ubuntu1
PackageArchitecture: all
ProcEnviron:
PATH=(custom, user)
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.30-6.7-generic
SourcePackage: totem
Uname: Linux 2.6.30-6-generic x86_64
* New upstream release: (LP: #463102)
- Movie Player:
- Fix possible crash on exit when using Python plugins
- Fix warning when displaying file tooltip in the playlist
- Fix help links not showing up in error messages (LP: #452510)
- Fix "disabling screensaver when audio is playing" checkbox
never turning off (or on)
- Fix play order when removing currently playing song
- Web browser plugin:
- Fix screensaver not being stopped when playing movies (LP: #358297)
(LP: #381116)
- Fix parsing of playlist files when using WebKit
- Add support for midi files
- GStreamer backend:
- Fix possible hang on startup
- Fix DVB channels file not being detected properly
- Fix warning when creating a screenshot
- Use cubic volumes when PulseAudio is used
- Fix intermittent pixel-aspect-ratio warnings
Binary package hint: update-manager
TEST CASE:
1. define a proxy server somewhere (gconf, apt.conf, synaptic)
2.use iptables to disallow access to port 80
3. run update-manager and click on the "upgrade" button
4. verify that the upgrade hangs
4. install update-manager from jaunty-proposed
5. repeat step 3
6. verify that it now continues
When updating to 9.10 from from 9.04, the update-manager uses a utility
function called "UpdateManager.Core.utils.url_downloadable". This
function skips urllib2 - which is properly configured to use the proxy
settings - and instead directly interacts with httplib, which requires
the caller to properly set up the request in order to use the proxy.
Changing the url_downloadable function to use the proxy resolves the
issue.
Specifically, I after:
if scheme == "http":
import httplib
try:
I added:
proxy = os.getenv('http_proxy')
if (proxy):
path = scheme + netloc + path
netloc = proxy
This resolved the problem. This, however, isn't really a fix - it relies
on the fact that init_proxy sets the http_proxy environment variable and
ignores anything else that might set up urllib2 to properly use a proxy
server.
"Upgrading Ubuntu to version 9.10" untranslated and missing for translation
Binary package hint: update-manager
TEST CASE:
1. use german (or spanish) locales in jaunty
2. run "update-manager"
3. click on upgrade
4. verify that most of the main upgrader window is localized, but that the main string ""Upgrading Ubuntu to version 9.10" is not
5. repeat step 1
6. run "update-manager --proposed"
7. verify that the main ugprade dialog is now fully localized
When I upgrade my system from Jaunty to Karmic RC, update-manager shows
the "Upgrading Ubuntu to version 9.10" string untranslated in my Spanish
desktop. Translations in Launchpad does not include that string for
translation in the update-manager template for Jaunty. Instead, it has
the "Upgrading Ubuntu to version 9.04" string:
https://translations.launchpad.net/ubuntu/jaunty/+source/update-
manager/+pots/update-manager/es/197/+translate
However, update-manager in Karmic does include the "Upgrading Ubuntu to
version 9.10" string:
https://translations.launchpad.net/ubuntu/karmic/+source/update-
manager/+pots/update-manager/es/204/+translate
ProblemType: Bug
Architecture: i386
Date: Sun Oct 25 18:11:24 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: update-manager 1:0.126.6
PackageArchitecture: all
ProcEnviron:
LANGUAGE=es_ES.UTF-8
PATH=(custom, user)
LANG=es_ES.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: update-manager
Uname: Linux 2.6.31-14-generic i686
update-manager exits on dist-upgrade when tmp is mounted "noexec" and gives useless error message
Binary package hint: update-manager
Today I tried to upgrade my system from 9.04 to 9.10 RC via update-
manager -d. When I clicked the button for the dist-upgrade, I got the
release notes and then a dialog which sais it's downloading 2 files.
After that, update-manager just crashed, without any notice.
TEST CASE:
Steps to reproduce:
run update-manager -d
click the "Upgrade" button in the top right.
click "Upgrade" in the dialog showing the release notes.
enter your password when asked for it.
What should happen:
the system is upgraded to the new distribution release, or a proper error message is shown.
What actually happens:
update-manager crashes.
When I run update-manager -d from the command line, this is the output:
$ update-manager -d
extracting 'karmic.tar.gz'
authenticate 'karmic.tar.gz' against 'karmic.tar.gz.gpg'
/var/lib/python-support/python2.6/dbus/connection.py:242: DeprecationWarning: object.__init__() takes no parameters
super(Connection, self).__init__(*args, **kwargs)
sudo: unable to execute /tmp/tmpx8L0A4/karmic: Permission denied
Since it said something about permissions, I also tried to run it as root directly from the command line instead of entering my password when update-manager asks for it. This is the output:
$ sudo update-manager -d
extracting 'karmic.tar.gz'
authenticate 'karmic.tar.gz' against 'karmic.tar.gz.gpg'
/var/lib/python-support/python2.6/dbus/connection.py:242: DeprecationWarning: object.__init__() takes no parameters
super(Connection, self).__init__(*args, **kwargs)
/usr/lib/python2.6/dist-packages/UpdateManager/DistUpgradeFetcher.py:79: GtkWarning: gtk_scrolled_window_add: assertion `bin->child == NULL' failed
self.parent.scrolled_notes.add(textview_release_notes)
extracting 'karmic.tar.gz'
authenticate 'karmic.tar.gz' against 'karmic.tar.gz.gpg'
But now I also got an error message in the GUI:
Can not run the upgrade
This usually is caused by a system were /tmp is mounted noexec. Please remount without noexec and run the upgrade again.
This error message is right, I do have /tmp mounted with noexec. The
problem is that it doesn't show up when I don't run update-manager as
root, so many users will not know what's the problem when their upgrade
fails.
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: update-manager 1:0.111.9
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: update-manager
Uname: Linux 2.6.28-16-generic x86_64
Rename /etc/X11/Xsession.d/60x11-localhost to match convention
Binary package hint: xorg
There seems to be a mostly-upheld naming convention that files in
/etc/X11/Xsession.d/ should be named as NNpackagename[_suffix]. All of
the other Xsession.d files installed by x11-common follow this
convention, but the new 60x11-localhost added today does not. It
probably should.
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: x11-common 1:7.4~5ubuntu15
PackageArchitecture: all
ProcEnviron:
LC_COLLATE=C
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-8-generic (buildd@yellow) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu1) ) #28-Ubuntu SMP Fri Mar 6 00:09:20 UTC 2009
SourcePackage: xorg
Uname: Linux 2.6.28-8-generic x86_64
New gdm does not have the FailsafeXServer config option
Binary package hint: gdm
gdm 2.20 had options in /etc/gdm/gdm.conf (in particular
FailsafeXServer) for specifying an action to take when X is failing to
start up. We attached a failsafe session (aka bulletproof-x) to be
invoked by gdm in these situations, which users could use to diagnose
and work around issues.
These options were implemented in the 'deal_with_x_crashes()' function
in gdm.c. Near as I can tell, this gdm feature was not included in the
new gdm rewrite, so we are seeing a regression here. The problem is
that whereas in the past the user would be dumped into a debugging
session, now gdm is simply trying multiple times, failing each time, and
then exiting (which then leads to the quite severe bug 441638).
Anyway, the end result is that we no longer have a debugging failsafe
mode available for users, they're just left with a non-functioning
system. Please either restore the missing functionality, or provide an
analogous mechanism to which we can attach a debugging session mode.
Binary package hint: xsane
This bug affects users with a localised version of Ubuntu, in which the
"Applications > Graphics > XSane Image scanning program" menu entry of
the default desktop installation appears untranslated (although it is
translated in Launchpad).
TEST CASE:
1. In a localized system using a non-English locale and with complete XSane translations, go to Applications > Graphics
2. The "XSane Image scanning program" entry appears untranslated
This is due to 13_pot_desktop_msgid.dpatch patch, correctly adding the
"XSane Image Scanner" string to the POT template, but the actual string
in the debian/xsane.desktop package remains unchanged as "XSane Image
scanning program", for which there is no actual translation.
The attached debdiff corrects this by modifying the .desktop file to use
the same "XSane Image Scanner" string as in the message catalog (.mo
file), so that its translation can be loaded.
Binary package hint: clamav
New upstream release is out. It has gone into Lucid already. Per the
microversion update exception for clamav, it will go to Jaunty and
Karmic in -proposed/updates. Since it has no security fixes, Dapper,
Hardy, and Intrepid will be updated in Backports.
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
landscape-sysinfo crashed with ImportError in <module>()
The Landscape Team has requested an SRU for this bug. The required
information follows below, and the original bug description is available
in the link below.
=== Statement explaining the impact ===
This bug is typically triggered by release upgrades from jaunty to
karmic. During the upgrade some Python modules are not importable and
cause a crash in the landscape-sysinfo script, which is in turned run by
pam-motd upon user login. For this reason the bug potentially affects
everyone upgrading from jaunty to karmic. The bug in itself has no other
effect than firing an apport bug, however this is likely to make the
user think that something went wrong, so fixing it is really important
from a user-experience point of view.
=== How the bug has been addressed ===
The landscape-sysinfo script has been modified to catch possible module
import errors and exit in that case. The fix is already included in
version 1.4.0-0ubuntu0.9.10.0 of the landscape-client package, which the
current one in lucid and karmic.
=== Patch ===
The comment #27 of this bug sports a patch created against the
landscape-client 1.3.2.3-0ubuntu0.9.04.0 package currently in jaunty-
updates.
=== How to reproduce the bug ===
Issue a release-upgrade from jaunty to karmic and switch user or login
as a new user.
=== Regression potential ===
The change is very isolated and there's no possibility of regression.
Binary package hint: linux-source-2.6.24
The system locks-up completely at random intervals.
The crash can be triggered by downloading mail with Thunderbird, but happens at any other activity after some random time.
No magic SysRq keys works, and there's nothing in the logs...
It's a 2.6.24-17-generic kernel, but the crash also happens with -16.
Everthing was fine with Gutsy on the same machine.
Booting with acpi=off makes the system work stable,
but acpi=noirq, acpi=ht, acpi=strict, noapic, nolapic, pci=noacpi don't help.
How to debug further ?
scanlogic SL11R USB device won't work with 2.6.27-11 kernel
SRU justification:
Impact: We have an -updates regression for the ScanLogic SL11R-IDE USB
disk. This device worked normally up to 2.6.27-11 kernel where it
regressed.
Fix: Add the required quirk for this device to the unusual devices list.
This has been tested by the device owner and reported to fix the
regression.
---
Using Ubuntu 8.10 with latest kernel 2.6.27-11.
my "Transcend USB Card Reader" does no longer work with this kernel. with the previous kernel 2.6.27-9 everything is ok.
lsusb reports the device as (using kernel 2.6.27-9)
Bus 003 Device 003: ID 04ce:0002 ScanLogic Corp. SL11R-IDE IDE Bridge
with kernel 2.6.27-11 i will get these messages in /var/log/messages, and the device cannot be accessed.
Feb 23 08:18:36 birte kernel: [ 184.799043] USB Mass Storage support registered.
Feb 23 08:18:41 birte kernel: [ 189.854649] scsi scan: INQUIRY result too short (5), using 36
Feb 23 08:18:41 birte kernel: [ 189.854667] scsi 6:0:0:0: Direct-Access CYPRESS SM-CF 0.78 PQ: 0 ANSI: 0
Feb 23 08:18:41 birte kernel: [ 189.904617] scsi scan: INQUIRY result too short (5), using 36
Feb 23 08:18:41 birte kernel: [ 189.904629] scsi 6:0:0:1: Direct-Access CYPRESS SM-CF 0.78 PQ: 0 ANSI: 0
Feb 23 08:18:41 birte kernel: [ 189.944676] sd 6:0:0:0: [sdc] Attached SCSI removable disk
Feb 23 08:18:41 birte kernel: [ 189.946842] sd 6:0:0:0: Attached scsi generic sg3 type 0
Feb 23 08:18:41 birte kernel: [ 189.999577] sd 6:0:0:1: [sdd] Unit Not Ready
Feb 23 08:18:41 birte kernel: [ 189.999590] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
Feb 23 08:18:41 birte kernel: [ 189.999599] sd 6:0:0:1: [sdd] Add. Sense: No additional sense information
Feb 23 08:18:42 birte kernel: [ 190.491616] sd 6:0:0:1: [sdd] 2001889 512-byte hardware sectors (1025 MB)
Feb 23 08:18:42 birte kernel: [ 190.507596] sd 6:0:0:1: [sdd] Write Protect is off
Feb 23 08:18:42 birte kernel: [ 190.569627] sd 6:0:0:1: [sdd] 2001889 512-byte hardware sectors (1025 MB)
Feb 23 08:18:42 birte kernel: [ 190.585625] sd 6:0:0:1: [sdd] Write Protect is off
Feb 23 08:18:42 birte kernel: [ 190.587855] sdd: sdd1
Feb 23 08:18:42 birte kernel: [ 190.629753] sd 6:0:0:1: [sdd] Attached SCSI removable disk
Feb 23 08:18:42 birte kernel: [ 190.631462] sd 6:0:0:1: Attached scsi generic sg4 type 0
Feb 23 08:18:42 birte kernel: [ 190.815572] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
Feb 23 08:18:42 birte kernel: [ 190.815592] sd 6:0:0:1: [sdd] Add. Sense: No additional sense information
Feb 23 08:18:42 birte kernel: [ 190.827561] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
Feb 23 08:18:42 birte kernel: [ 190.827575] sd 6:0:0:1: [sdd] Add. Sense: No additional sense information
Feb 23 08:18:42 birte kernel: [ 190.839581] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
Feb 23 08:18:42 birte kernel: [ 190.839598] sd 6:0:0:1: [sdd] Add. Sense: No additional sense information
Feb 23 08:18:42 birte kernel: [ 190.851585] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
Feb 23 08:18:42 birte kernel: [ 190.851602] sd 6:0:0:1: [sdd] Add. Sense: No additional sense information
Feb 23 08:18:42 birte kernel: [ 190.863581] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
Feb 23 08:18:42 birte kernel: [ 190.863596] sd 6:0:0:1: [sdd] Add. Sense: No additional sense information
Feb 23 08:18:42 birte kernel: [ 190.875581] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
Feb 23 08:18:42 birte kernel: [ 190.875594] sd 6:0:0:1: [sdd] Add. Sense: No additional sense information
Feb 23 08:18:42 birte kernel: [ 190.887581] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
Feb 23 08:18:42 birte kernel: [ 190.887595] sd 6:0:0:1: [sdd] Add. Sense: No additional sense information
Feb 23 08:18:42 birte kernel: [ 190.899583] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
Feb 23 08:18:42 birte kernel: [ 190.899599] sd 6:0:0:1: [sdd] Add. Sense: No additional sense information
Feb 23 08:18:42 birte kernel: [ 190.911582] sd 6:0:0:1: [sdd] Sense Key : No Sense [current]
F
[RS482] low performance due to removal of _tnl_ProgramCacheInit()
[Problem]
Performance regression on Xpress 200M for Jaunty.
[Impact]
Affects users of older R300-based chipsets, causing a performance regression which can make the system unusable in some situations.
[Development Solution]
The proposed patch to solve this is present upstream and has been included in Ubuntu Karmic for some time now with no ill effect.
[Patch]
Minimal patch which is confirmed by 5 users to improve performance with no side effects not already present with existing code:
http://launchpadlibrarian.net/27634168/r300_context_tnlcache_fix.patch
[Reproduction]
With affected hardware, run a GL application such as Neverball. Note the rendering performance and cpu utilization. With patch applied, rendering will be faster and cpu usage lower.
[Regression Potential]
The patch only affects code that is invoked on R300-class hardware, so any regression this could cause will be limited in scope to a narrow subset of users.
Comment #22 indicates that upstream feels there may be some risk of
freeze issues with this patch, however this has not been seen in testing
so far. If the freeze can be reproduced by anyone, then this patch
should not go in, since a freeze regression would be more severe than a
performance regression.
Five people have tested this patch so far. It would be more comfortable
seeing this patch tested more widely, but this may be the limit of what
can be expected with just PPA testing. It is recommended that ample
time be given for testing this patch before putting into -updates.
[Original Report]
My Xpress 200M is almost dead after I upgraded the system to Ubuntu 9.04.
glxgears:
1256 frames in 5.0 seconds = 251.181 FPS
1224 frames in 5.0 seconds = 244.754 FPS
1673 frames in 5.0 seconds = 334.345 FPS
1610 frames in 5.0 seconds = 321.985 FPS
I had above 1100 FPS in 8.10. I deleted the old xorg.conf - did not help. Then did dpkg-reconfigure xserver-xorg - no improvements. I do not see errors in Xorg.log. Everything is working (compiz, some games) but very slow.
I believe that something is wrong with the card detection:
radeontool --debug
Found card 1002:5955 (30000)
(unknown card)
Radeon found. Base control address is b80b2000; base framebuffer address is a7f2d000.
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: xserver-xorg-video-ati 1:6.12.1-0ubuntu1
ProcEnviron:
SHELL=/bin/bash
LANG=ru_RU.UTF-8
ProcVersion: Linux version 2.6.28-11-generic (buildd@rothera) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #36-Ubuntu SMP Fri Mar 20 19:40:40 UTC 2009
SourcePackage: xserver-xorg-video-ati
Uname: Linux 2.6.28-11-generic i686
[lspci]
00:00.0 Host bridge [0600]: ATI Technologies Inc RS480 Host Bridge [1002:5950] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:30a4]
01:05.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon XPRESS 200M 5955 (PCIE) [1002:5955]
Subsystem: Hewlett-Packard Company Device [103c:30a4]
jaunty SRU information follows:
Note that this SRU involves two separate bugs, this one and bug 326532.
Impact: Users who experience problems with PulseAudio often kill it
(using "pulseaudio -k" or "killall pulseaudio", the latter of which is
more reliable). Jaunty's current pm-utils sleep hook looks for the
session-invoked command line. Users who invoke pulseaudio manually,
after killing it, with "pulseaudio -D" (or other variants) do not have
this session-invoked command line, and thus, when they suspend to ram or
disk, the pm-utils sleep hook does not suspend their pulseaudio daemons.
Note that the use case of killing the pulseaudio daemon and allowing it
to autospawn afterward is unaffected; jaunty's existing pm-utils sleep
hook correctly reaps all pulseaudio instances. This SRU only applies to
manually invoked "pulseaudio -D", "pulseaudio -vvv", etc.
Resolution: Modify the pm-utils sleep hook to correctly reap all
pulseaudio instances regardless of pulseaudio invocation command line.
SRU debdiff:
http://launchpadlibrarian.net/25941550/pulseaudio_0.9.14-0ubuntu20.1.debdiff
TEST CASE: Boot into a jaunty install. In a Terminal, issue "killall
pulseaudio;pulseaudio -D". Suspend to ram, then resume. Note the
inaudible audio from PulseAudio.
Regression potential: No regressions have been identified in production.
--
old intrepid SRU information follows:
Impact: A portion of users with a default or updated (intrepid-updates)
Ubuntu 8.10 install experience inaudible audio from PulseAudio after
resuming from suspend-to-ram. This symptom is due to the PulseAudio
daemon not having received proper notification to suspend clients and
release the sound device(s).
Resolution: Configure users' pulseaudio daemons to suspend prior to
suspending to ram and to resume after resuming. This sequence is
accomplished via a pm-utils sleep hook. The corresponding fixed version
(0.9.13-2ubuntu3) is available in jaunty.
SRU debdiff:
http://launchpadlibrarian.net/20316781/pulseaudio_0.9.10-2ubuntu9.2.debdiff
TEST CASE: Boot into a default or updated (intrepid-updates) Ubuntu 8.10
install. Suspend to ram, then resume. Note the inaudible audio from
PulseAudio.
Regression potential: No regressions have been identified in production.
Background information follows:
Binary package hint: pulseaudio
> aplay squish.au
Sonando Audio Sparc 'squish.au' : Mu-Law, Ratio 8000 Hz, Mono
[Suspend to Ram/Resume]
> aplay squish.au
ALSA lib pcm_dmix.c:874:(snd_pcm_dmix_open) unable to open slave
aplay: main:546: error al abrir audio: Dispositivo ó recurso ocupado
Then you need to killall pulseaudio for apps that use pcm starts working again.
(Question: How you can stop/start/restart pulseudio? In Ubuntu /etc/init.d/pulseaudio script is disabled)
If you need more information, please let me know.
Thx.
----------------------------------
Hardy Uptodate
IBM Thinkpad X41 Tablet
pulseaudio 0.9.9-1ubuntu2
[jaunty] Pulseaudio does not start "Failed to open module "module-console-kit": file not found"
jaunty SRU information follows:
Note that this SRU involves two separate bugs, this one and bug 202089.
Impact: Users who perform a distribution upgrade to jaunty sometimes
fail to have audible sound through PulseAudio due to its failure to load
libdbus-util.so. This failure stems from pulseaudio's missing dependency
on the pulseaudio-module-hal package, which contains libdbus-util.so.
Instead, it is a Recommends.
Resolution: Promote pulseaudio-module-hal from a recommendation to a
dependency of the pulseaudio package.
SRU debdiff:
http://launchpadlibrarian.net/25941550/pulseaudio_0.9.14-0ubuntu20.1.debdiff
TEST CASE: Perform a distribution upgrade from intrepid to jaunty. If
the audio from PulseAudio is inaudible, "killall pulseaudio; strace
pulseaudio -v". If "open("/usr/lib/pulse-0.9/modules/libdbus-util.so",
O_RDONLY) = -1 ENOENT (No such file or directory)" appears, then the
symptom has been reproduced.
Regression potential: No regressions have been identified in production.
--
Background information follows:
Binary package hint: pulseaudio
In Jaunty (with latest updates for Sat Feb 7th installed) the pulseaudio
daemon fails to start.
The output I get is:
I: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
I: caps.c: Dropping root privileges.
I: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
N: main.c: Called SUID root and real-time and/or high-priority scheduling was requested in the configuration. However, we lack the necessary privileges:
N: main.c: We are not in group 'pulse-rt', PolicyKit refuse to grant us the requested privileges and we have no increase RLIMIT_NICE/RLIMIT_RTPRIO resource limits.
N: main.c: For enabling real-time/high-priority scheduling please acquire the appropriate PolicyKit privileges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user.
E: module.c: Failed to open module "module-console-kit": file not found
E: main.c: Module load failed.
E: main.c: Failed to initialize daemon.
Binary package hint: update-manager
TEST CASE:
1. define a proxy server somewhere (gconf, apt.conf, synaptic)
2.use iptables to disallow access to port 80
3. run update-manager and click on the "upgrade" button
4. verify that the upgrade hangs
4. install update-manager from jaunty-proposed
5. repeat step 3
6. verify that it now continues
When updating to 9.10 from from 9.04, the update-manager uses a utility
function called "UpdateManager.Core.utils.url_downloadable". This
function skips urllib2 - which is properly configured to use the proxy
settings - and instead directly interacts with httplib, which requires
the caller to properly set up the request in order to use the proxy.
Changing the url_downloadable function to use the proxy resolves the
issue.
Specifically, I after:
if scheme == "http":
import httplib
try:
I added:
proxy = os.getenv('http_proxy')
if (proxy):
path = scheme + netloc + path
netloc = proxy
This resolved the problem. This, however, isn't really a fix - it relies
on the fact that init_proxy sets the http_proxy environment variable and
ignores anything else that might set up urllib2 to properly use a proxy
server.
klamav update dies unexpectedly in intrepid with apparmor active
I ran into a problem with updating klamav this morning (freshly installed Intrepid Ibex/8.10):
"the update process died unexpectedly. did you kill it?"
Running 'dmesg' unearths a problem with apparmor premissions (freshclam
has no read/write permission in /tmp):
[25847.394171] type=1503 audit(1229981927.656:28):
operation="inode_permission" requested_mask="r::" denied_mask="r::"
fsuid=1000 name="/tmp/kde-peter/klamavwGmkJa.tmp" pid=6960
profile="/usr/bin/freshclam"
Adding the following line in '/etc/apparmor.d/usr.bin.freshclam' (just before the closing curly brace) fixed it:
/tmp/** rw,
Cheers, Peter
Binary package hint: clamav
The freshclam command cannot be run by anyone other than root while
apparmor is enabled. So long as freshclam is given writable directories,
it should be able to be run by anyone, like so:
freshclam --log=/home/user --datadir=/home/user
Shutting down apparmor (sudo /etc/init.d/apparmor stop) enables this to
work as it should.
Distro: Ubuntu 8.10
Executable path: /usr/bin/freshclam
SourcePackage: clamav
apparmor denies freshclam access to /var/run/samba/gencache.tdb
Binary package hint: clamav
My /var/log/syslog gets this message every time when freshclam does an
update:
Mar 21 04:14:53 fs1 kernel: [550646.547458] type=1503
audit(1237634093.495:59): operation="inode_permission"
requested_mask="::r" denied_mask="::r" fsuid=5000
name="/var/run/samba/gencache.tdb" pid=6451 profile="/usr/bin/freshclam"
Why freshclam tries to read samba gencache.tdb in the first place?
My guess it may have to do with Samba setup as PDC which uses winbind and modified nsswitch.conf.
# /etc/nsswitch.conf
passwd: files ldap [UNAVAIL=return]
group: files ldap [UNAVAIL=return]
shadow: files ldap [UNAVAIL=return]
hosts: files wins mdns4_minimal [NOTFOUND=return] dns mdns4
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
#/etc/nsswitch.conf (END)
But there is no other package that goes to gencache.tdb directly, at least not from apparmor perspective.
Versions:
Ubuntu 8.10
clamav 0.94.dfsg.2-1ubuntu0.1
clamav-freshclam 0.94.dfsg.2-1ubuntu0.1
apparmor 2.3+1289-0ubuntu4.1
samba 2:3.2.3-1ubuntu3.4
winbind 2:3.2.3-1ubuntu3.4
After upgrading to Intrepid from Hardy on PPC, I cannot print anymore.
I've got a Brother HL-1430 laserjet printer using the recommended PPD.
The "data" LED of the printer blinks for a second, and then shuts off
again.
If I try with the test page, it comes off blank, or with some grey
squares (but in Hardy it came with the Ubuntu logo and all).
For example, trying "man -Tps printf | lpr" doesn't print anything; nor
it works from any other application (e.g. a PDF in evince). The queue is
always empty when using PS files, else when printing PDFs from evince it
stays in queue indefinitely.
In response to what I send to the printer, looking at the logs, I can
see:
D [17/Sep/2008:15:22:01 +0200] PID 8428 (/usr/lib/cups/filter/pstopdf) exited with no errors.
D [17/Sep/2008:15:22:01 +0200] [Job 27] GhostScript: **** Warning: An error occurred while reading an XREF table.
D [17/Sep/2008:15:22:01 +0200] [Job 27] GhostScript: **** The file has been damaged. This may have been caused
D [17/Sep/2008:15:22:01 +0200] [Job 27] GhostScript: **** by a problem while converting or transfering the file.
D [17/Sep/2008:15:22:01 +0200] [Job 27] GhostScript: **** Ghostscript will attempt to recover the data.
D [17/Sep/2008:15:22:01 +0200] [Job 27]
D [17/Sep/2008:15:22:01 +0200] [Job 27] Closing foomatic-rip.
D [17/Sep/2008:15:22:01 +0200] [Job 27] Read 1 bytes of print data...
I'm attaching the cups error_log.
Quite severe in importance, imho. This is a machine shared by a lot of users, so none of them can print as long as this lasts.
ii cups 1.3.8-11 Common UNIX Printing System(tm) - server
ii foomatic-db 20080916-0ubuntu1 OpenPrinting printer support - database
The Landscape Team has proposed an SRU to solve this bug.
Statement explaining the impact
=====================
It's possible to have a client machine in a situation where landscape
itself is using a proxy, but not smart. In networks where the only way
out is via a proxy, this means that that machine would never be able to
perform package operations, nor report the packages it has installed and
available.
Even if smart checks the http_proxy env var, it's entirely possible the
admin didn't set it. A contributing factor is that the landscape-config
wizard explicitly asks for a proxy, so it's not unreasonable for the
admin to assume smart would be setup too.
How the bug has been addressed
======================
Introducing a new smart plugin that inherits the proxy settings from the
landscape-client configuration file.
Detailed instructions how to reproduce the bug
==============================
Simply install landscape-client in an environment using a proxy.
linux-image-2.6.20-16 fails to detect twin usb gamepad
Binary package hint: linux-source-2.6.20
This bug is very similar to bug #106622 reported by Paul Zaremba, but
affects a different device.
I have a Personal Communications Systems, Inc. (Vendor ID 0x0810) Twin
USB Gamepad (Product ID 0x0002).
As detailed in Paul's bug report, the two controllers were muxed
together as one. Adding the vendor and product IDs to drivers/usb/input
/hid-core.c, and setting the "multi input" quirk produced the correct
behaviour.
Unfortunately I'm a bit over my head here, and I don't know how to write
a patch. Have I provided enough information?
Sorry if this is a duplicate of Paul's bug, I wasn't sure. It's the
same basic problem, but with a different product.
Thanks,
Rory
PS, here's the output of lsusb -v:
Bus 003 Device 003: ID 0810:0002 Personal Communication Systems, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0810 Personal Communication Systems, Inc.
idProduct 0x0002
bcdDevice 1.06
iManufacturer 0
iProduct 2 Twin USB Gamepad
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 200mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Devices
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 33 US
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 202
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
Device Status: 0x0000
(Bus Powered)
Bluetooth mouse does not re-establish connection after reboot
Summary:
Bluetooth device connections are not re-established after reboot
Steps to Reproduce:
1) Associate a bluetooth mouse to a system using bluetooth device (PCI ID: 0x0a5c2151)
2) Ensure mouse is now working
3) Reboot system
4) Try to use mouse
Expected result:
All trusted device connections are re-established each time the system is booted
Actual result:
Bluetooth mouse is non-functional until it is deleted from Bluetooth Manager and re-added.
This is a public bug on the kernel package corresponding to the private
bug #241749, for SRU tracking.
Hardware: Montevina(HP-prototype-laptop)
Software: Intrepid-beta-x86
Steps to reproduce:
Click "System-->shutdown...-->Suspend" of Gnome Desktop.Expect the system become S3 status(suspend),but a Login-Window appeared at once after clicking,with screen power on still.
Clicking "System-->shutdown...-->Hibernate" also reproduce the bug.
More debug informations are in attachment.
atl1e.ko missing in initrd, causes kernel panic on thin clients
Binary package hint: initramfs-tools
The atl1e.ko (Attansic Technology Gigabit Ethernet) module is missing in
the default initrd although it's present on an installed system in
/lib/modules/2.6.27-7-generic/kernel/drivers/net/atl1e/
This chipset is present in the latest Asus EEE that we are trying to use
as thin clients, that missing module make them to kernel panic (unable
to mount /) when trying to mount / from the network.
Is there a good reason for it not to be included in the initrd or is
that just a bug of whatever chooses what to put in the initrd ?
Adding it to /etc/initramfs-tools/modules and rebuilding the initrd
fixes the issue but I'd prefer not to have to do that.
Reboot stalls after installing Intrepid from alternate on a Dell Optiplex 330
After installing Intrepid from alternate on a Dell Optiplex 330, the
system seems to stall at the end of powering off. This was apparently
fixed recently to workaround having to use the kernel parameter
reboot=b.
[SRU] Net-SNMP tries to read the obsolete /etc/sensors.conf
Using snmpd_5.4.1~dfsg-4ubuntu2_i386
The command
snmpwalk localhost lmSensors
displays this output:
LM-SENSORS-MIB::lmSensors = No Such Object available on this agent at this OID
strace'ing snmpd -f -Le -Ducd-snmp/lmSensors shows this:
...
time(NULL) = 1203281780
open("/etc/sensors.conf", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
write(2, "=> sensor_init\n", 15=> sensor_init
...
Creating a symlink /etc/sensors3.conf -> /etc/sensors.conf fixes this
problem.
Binary package hint: snmpd
Ubuntu 8.04.1
snmpd 5.4.1~dfsg-4ubuntu4
snmpd 5.4.1 needs to be updated to 5.4.2 to get rid of these errors in
syslog:
snmpd[27689]: error getting netmask for interface 2
Syslog fills with hundreds of these errors if you have a network
interface, e.g. eth2, with no IP address, but you have an alias,
e.g. eth2:1, that does have an IP address (and netmask).
Please pull down the patched version 5.4.2 from upstream?
Or perhaps you can point me at a package repository that has a patched version?
ProblemType: Bug
Architecture: i386
Date: Mon Sep 15 19:46:56 2008
DistroRelease: Ubuntu 8.04
Package: snmpd 5.4.1~dfsg-4ubuntu4
PackageArchitecture: i386
ProcEnviron:
SHELL=/bin/bash
PATH=/home/idallen/bin86:/home/idallen/bin:/usr/local/bin:/usr/local/sbin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LC_COLLATE=C
LANG=C
LC_CTYPE=en_CA.utf8
SourcePackage: net-snmp
Uname: Linux 2.6.24-19-generic i686
Trying to use COUNTER64 in NetSNMP::agent doesn't work. This is a long-
standing bug that has been fixed in SVN for 5.2.x, 5.3.x, 5.4.x and
trunk last year.
I noticed this bug a while ago (it was already reported to net-snmp) and
worked around it by using normal counters. Now it's fixed I'd like to
use them to test some counter-specific functions. It would be awesome if
the patch could get trough normal updates.
Note that Perl do not support 64bit integers ("long long" in C) out of
the box, but Math::Int64 do and the value can be safely passed to
NetSNMP::agent as a string.
See:
http://sourceforge.net/tracker/index.php?func=detail&aid=2022948&group_id=12694&atid=312694
http://net-snmp.svn.sourceforge.net/viewvc/net-snmp?view=rev&revision=17246
I attached the patch for the 5.4.x branch from SVN - from this URL:
http://net-snmp.svn.sourceforge.net/viewvc/net-snmp/branches/V5-4-patches/net-snmp/perl/agent/agent.xs?view=patch&r1=17246&r2=17245&pathrev=17246
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
mod proxy causes duplicate query strings when nocanon option is used
Binary package hint: apache2
When mod proxy is used with the nocanon option apache duplicates the
query string arguments in the URL. This is a known bug in 2.2.8 and
was fixed in 2.2.9, c.f.:
<https://issues.apache.org/bugzilla/show_bug.cgi?id=44803>
<http://mail-archives.apache.org/mod_mbox/httpd-cvs/200806.mbox/%3C20080605124644.4CB3E23889FF@eris.apache.org%3E>
To reproduce:
1) Create an apache.conf file, e.g. like:
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
LoadModule proxy_module /usr/lib/apache2/modules/mod_proxy.so
LoadModule proxy_http_module /usr/lib/apache2/modules/mod_proxy_http.so
Listen 5555
ErrorLog /dev/null
PidFile /dev/null
ProxyPass / http://127.0.0.1:8000/ nocanon
ProxyPassReverse / http://127.0.0.1:8000/
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Then run apache with it, e.g. apache2 -X -f apache.conf
2) run 'python -m SimpleHTTPServer' in another terminal/window/whatever
3) finally run 'wget -q -O /dev/null http://localhost:5555/foo?bar' in
another terminal
Output from hardy(-updates) apache:
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
localhost - - [19/Oct/2009 23:16:09] code 404, message File not found
localhost - - [19/Oct/2009 23:16:09] "GET /foo?bar?bar HTTP/1.1" 404 -
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Expected output:
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
localhost - - [19/Oct/2009 23:16:34] code 404, message File not found
localhost - - [19/Oct/2009 23:16:34] "GET /foo?bar HTTP/1.1" 404 -
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Attached is a dpatch which we're using in production and fixes the
issue for us. Could we please get an SRU with this for hardy?
Alternate CD cdrom-detect.postinst does not consider USB flash drive/key.
We have had support for USB devices that contain the contents of an ISO
being used as installation media for the alternate CD since Intrepid.
Recently it has come to my attention that server users want this feature
for servers that do not have a CDROM drive and are not installed using
PXE.
I've uploaded a new debian-installer-utils and cdrom-detect to hardy-
proposed which will enable the following test case.
TEST CASE:
1. Put the contents of an Ubuntu 8.04.4 image on a USB disk using usb-creator. Other tools can be used to do this, but you need to make sure you add 'cdrom-detect/try-usb=true' to the kernel command line.
2. Boot the USB disk and proceed with the installation. It should progress without complaining that it cannot find the installation media.
Original report:
I wrote a script to copy all the files from Hardy Heron (08.04) Live CD and Alternate CD to a USB flash drive. The Live CD works flawlessly.
However, the Alternate CD fails to mount the "cdrom". This is because
cdrom-detect.postinst does not try to look for disk partitions.
By adding `list-devices partition` in the list of devices to probe, and
by adding an additional mount command for vfat, I managed to get the
Alternate CD working from a USB flash drive.
Attached, a patch to fix the issue. Please consider introducing this
fix soon and release a new Alternate CD with it. I plan to make my
script available and it would be nice to have a proper working Alternate
CD for USB flash drives. Users should not have to mess with initrd to
get this working.
P.S.: If you have a suggestion about a good place to make this script
public, please write to me in an email.
Also, my solution partially resolves:
http://brainstorm.ubuntu.com/idea/16/
I have USB images of 1G which can be `dd` to a USB flash drive.
[ keywords: alternate cd usb flash key stick pen pendrive drive ]
Alternate CD cdrom-detect.postinst does not consider USB flash drive/key.
We have had support for USB devices that contain the contents of an ISO
being used as installation media for the alternate CD since Intrepid.
Recently it has come to my attention that server users want this feature
for servers that do not have a CDROM drive and are not installed using
PXE.
I've uploaded a new debian-installer-utils and cdrom-detect to hardy-
proposed which will enable the following test case.
TEST CASE:
1. Put the contents of an Ubuntu 8.04.4 image on a USB disk using usb-creator. Other tools can be used to do this, but you need to make sure you add 'cdrom-detect/try-usb=true' to the kernel command line.
2. Boot the USB disk and proceed with the installation. It should progress without complaining that it cannot find the installation media.
Original report:
I wrote a script to copy all the files from Hardy Heron (08.04) Live CD and Alternate CD to a USB flash drive. The Live CD works flawlessly.
However, the Alternate CD fails to mount the "cdrom". This is because
cdrom-detect.postinst does not try to look for disk partitions.
By adding `list-devices partition` in the list of devices to probe, and
by adding an additional mount command for vfat, I managed to get the
Alternate CD working from a USB flash drive.
Attached, a patch to fix the issue. Please consider introducing this
fix soon and release a new Alternate CD with it. I plan to make my
script available and it would be nice to have a proper working Alternate
CD for USB flash drives. Users should not have to mess with initrd to
get this working.
P.S.: If you have a suggestion about a good place to make this script
public, please write to me in an email.
Also, my solution partially resolves:
http://brainstorm.ubuntu.com/idea/16/
I have USB images of 1G which can be `dd` to a USB flash drive.
[ keywords: alternate cd usb flash key stick pen pendrive drive ]
Binary package hint: kdepim
Renaming a folder via dimap can cause the folder to be deleted.
upstream bug: https://issues.kolab.org/issue3833 "Mails will vanish, if
a folder is renamed."
>From upstream:
we recently found and fixed an issue in KMail. Under certain circumstances, it
was possible that mails get deleted from the server after renaming a folder
when using disconnected IMAP.
This is obviously a bad bug, and therefore it would be great if you could
include the patch in your packages, if the version you ship is affected.
Affected versions are:
- 3.5 branch
- enterprise branch
- 4.2 branch
- 4.3 branch
- trunk
The KDE 4.1 branch doesn't seem to be affected.
The patch made it into all affected branches already, here are the revision
numbers of the fixes:
3.5: 1022980, 1022986
enterprise: 1021458, 1021464
4.2: 1022968, 1022978
4.3: 1022963, 1022964
trunk: 1022953, 1022954
[MASTER] firefox-3.0b5 received an X Window System error: 'BadIDChoice'
Binary package hint: firefox-3.0
Starting a few days ago, maybe a week or so, FF3 started crashing randomly,
after 1h or so, usually when there are tens of windows and tabs open. It
probably happened after some update of the X server, come to think of it.
Calling it from a terminal and not from the window manager yields the following
trace:
The program 'firefox' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
(Details: serial 73442980 error_code 14 request_code 153 minor_code 4)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
I am not sure what to do with that? Is firefox the program I should run with
the --sync command line option?
Relevant packages (hardy up-to-date):
ii xserver-xorg 1:7.3+10ubuntu10 the X.Org X server
ii xserver-xorg-core 2:1.4.1~git20080131-1ubuntu9 Xorg X server - core server
ii kdm-kde4 4:4.0.3-0ubuntu2 X display manager for KDE 4
ii firefox-3.0 3.0~b5+nobinonly-0ubuntu3 safe and easy web browser from Mozilla
Tell me what to do to help you investigate this issue.
Performance-related changes made by Debian to libxcb 1.1
Debian has recently made a 1.1-1.2 release of libxcb to stable. Since
Hardy derived from the same version and is LTS, I thought these changes
might be worth also applying to Hardy.
The changelog for 1.1-1.2 reads:
libxcb (1.1-1.2) stable; urgency=low
* Non-maintainer upload to fix important performance issues
(closes: #487635).
* Fix some fd leaks in _xcb_open_*()
* Increase libxcb buffer size to 16k from 4k
* Disable Nagle on TCP socket
-- Julien Cristau <jcristau@debian.org> Wed, 27 May 2009 20:06:47
+0200
If you do make an SRU containing these changes, please also ensure that
the version in ia32-libs is updated.
Applications that use libxcb 1.1 cannot open more than 1024 files
Hi,
We have some internal 32-bit applications that end up with a lot of
files open. If they in turn call a program that links with libxcb, more
often than not, that program segfaults.
This has been determined to be because libxcb uses select() and the man
page for select() says this:
"An fd_set is a fixed size buffer. Executing FD_CLR() or FD_SET()
with a value of fd that is negative or is equal to or larger than
FD_SETSIZE will result in undefined behavior. Moreover, POSIX requires
fd to be a valid file descriptor."
Later versions of libxcb address this by using poll()
I'm attaching the patch that we are using internally against libxcb
1.1-1.1
If you make this SRU, please also ensure that the 32-bit version in
ia32-libs gets updated.
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
On my Samsung NC10 Netbook some FN keys do not work.
Working:
Speaker Off. Volume Control, Sleep Buttom, Mousepad off
Not working:
WLAN off, brightness up/down, LCD off, Battery
Brightness down gives an e009
Brightness up gives ab e008
setkeycodes e009 $KEY_BRIGHTNESSDOWN # Fn+Down
setkeycodes e008 $KEY_BRIGHTNESSUP # Fn+Up
This is working, but gives no button release event, so brightness goes
up 100% or down 0%. And it also blocks the keyboard.
Any ideas on this?
TIA
Andreas
Using intreped X86
[SRU] openvpn2.1~rc7 fails to pick up the CN of certificates
Binary package hint: openvpn
In Ubuntu 8.04.1 the version of openvpn available is 2.1~rc7 which has a
pretty serious bug:
>From a reply to the openvpn mailing list after we were having problems:
"try upgrading to 2.1_rc9 ; in 2.1_rc7 the code to extract a common name
from a certificate DN was broken. v2.1_rc8 and higher reverted back to
the old mechanism, as found in 2.0.9."
This means any attempt to use the ccd feature (different options for
different clients based on the name of the client certificate) will
fail. Our setup involved an inter-LAN vpn; we could not push the
appropriate routes as it couldn't identify the clients properly
Manually upgraded to rc9 and our setup now works
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
The program 'gnome-settings-daemon' received an X Window System error. During on a FreeNX server suring a session. The crash does not happen when xrandr plugin is disabled.
