[Bug 1772921] Re: freeipa web ui -- incorrect configuration for awesome fonts

[Andreas Ntaflos]

Is this fix going to make it into bionic?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772921

Title:
  freeipa web ui -- incorrect configuration for awesome fonts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1772921/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1511524] Re: OpenVPN PAM authentication broken on 15.10 Server

[Andreas Ntaflos]

This is still a problem in Ubuntu 18.04.

Note: systemd unit files provided by packages should not be modified by
the user after installation, instead systemd's drop-in feature should be
used.

The proper workaround for this bug is to create the file
/etc/systemd/system/openvpn@.service.d/10-pam-capability-fix.conf with
the following contents (notice the added CAP_AUDIT_WRITE keyword):

[Service]
CapabilityBoundingSet=
CapabilityBoundingSet=CAP_IPC_LOCK CAP_NET_ADMIN CAP_NET_BIND_SERVICE 
CAP_NET_RAW CAP_SETGID CAP_SETUID CAP_SYS_CHROOT CAP_DAC_OVERRIDE 
CAP_AUDIT_WRITE

Afterwards issue "systemctl daemon-reload" to make systemd aware of the
drop-in and then restart the OpenVPN service.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511524

Title:
  OpenVPN PAM authentication broken on 15.10 Server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1511524/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon

[Andreas Ntaflos]

Using Kubuntu 16.04 on a Thinkpad X240 with Intel graphics this problem
also causes Yakuake ("Quake-style terminal emulator based on KDE Konsole
technology") to remain invisible when activated. It still accepts input
and the window is in focus, it just is not visible.

Switching the compositor rendering backend from OpenGL to XRender works
around the problem but the XRender backend seems to cause massive screen
tearing when scrolling or watching videos so this workaround is
suboptimal.

Installing xserver-common and xserver-xorg-core from
ppa:canonical-x/testing fixes the issue!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780664

Title:
  Recent libgl-mesa graphics update prevents drop down list menu
  appearing in apps like firefox three line/bar menu icon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780664/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1558166] Re: Xenial installer hangs for a long time with "Setting up the clock" message on IPv6-only systems

[Andreas Ntaflos]

We work around this problem by disabling the clock setup during
installation:

d-i clock-setup/utc boolean true
d-i time/zone string Europe/Vienna
d-i clock-setup/ntp boolean false
d-i clock-setup/ntp-server string pool.ntp.org

And after installation Puppet ensures chrony or ntpd are running.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558166

Title:
  Xenial installer hangs for a long time with "Setting up the clock"
  message on IPv6-only systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1558166/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1558166] Re: Xenial installer hangs for a long time with "Setting up the clock" message on IPv6-only systems

[Andreas Ntaflos]

Definitely still a problem with 16.04, especially with unattended
installs.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558166

Title:
  Xenial installer hangs for a long time with "Setting up the clock"
  message on IPv6-only systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1558166/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1393923] Re: postfix (2.11.0-1) does not LDAP table lookup since libp11-kit0 (0.20.2-2ubuntu2)

[Andreas Ntaflos]

Over a year later this problem still exists. It is impossible to run a
Postfix server that does (SSL/TLS secured) LDAP lookups on Ubuntu
14.04.3.

I wonder how is this not affecting more people?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393923

Title:
  postfix (2.11.0-1) does not LDAP table lookup since libp11-kit0
  (0.20.2-2ubuntu2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1393923/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1414684] Re: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail)

[Andreas Ntaflos]

FWIW, I am content with the updated USN and agree with Won't Fix. Just
wanted to raise the issue here in case I am not the only one bitten by
this change.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1414684

Title:
  bsd-mailx no longer supports sendmail options, thus breaking existing
  scripts (like Bootmail)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bsd-mailx/+bug/1414684/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1414696] Re: mailx commandline broken after recent bsd-mailx security update

[Andreas Ntaflos]

I have implemented the proposed fix in our infrastructure by having
Puppet modify the /usr/sbin/bootmail script and change the last line as
specified above to use the "-a" option for setting the From: header:

print_mail_text | sed -e "s/[^[:print:]]//g" | rootsign | mail -s
"$subject" -a "From: Bootmail <${FROM_MAIL}>" "$recipients"

Works well, FWIW.

** Description changed:

  bsd-mailx recently had a security update that completely removes support
  for specifying classic sendmail options after "--" on the command line.
  See http://changelogs.ubuntu.com/changelogs/pool/main/b/bsd-mailx/bsd-
  mailx_8.1.2-0.2006cvs-1ubuntu0.1/changelog for 8.1.2-0.2006cvs-
  1ubuntu0.1. This is on Ubuntu 12.04.
  
  The update breaks the way Bootmail (and probably quite a few other
  scripts) constructs its mail messages. Currently it looks like this:
  
  print_mail_text | sed -e "s/[^[:print:]]//g" | rootsign | mail -s
  "$subject" "$recipients" -- -F "Bootmail" -f "$FROM_MAIL"
  
  The part after "--", i.e. the switches -F and -f, is now no longer
  supported by bsd-mailx and results in "bad address syntax" error
  messages in /var/log/mail.log:
  
  Jan 26 16:20:09 example01 postfix/error[31885]: 4351640CB7:
  to=<-f...@web01.example.com>, orig_to=<-F>, relay=none, delay=0.16,
  delays=0.12/0/0/0.05, dsn=5.1.3, status=bounced (bad address syntax)
  
  I reported a bug against bsd-mailx in
  https://bugs.launchpad.net/ubuntu/+source/bsd-mailx/+bug/1414684 because
  this change is obviously quite troublesome for any script that relies on
  mailx understanding sendmail options.
  
  To fix this in Bootmail I propose using the "-a" commandline switch to
  set additional mail headers. Something like this:
  
  print_mail_text | sed -e "s/[^[:print:]]//g" | rootsign | mail -s
- "$subject" -a "Bootmail <${FROM_MAIL}>" "$recipients"
+ "$subject" -a "From: Bootmail <${FROM_MAIL}>" "$recipients"
  
  This has the advantage that it works with (probably) all bsd-mailx
  versions and most other mailx variants as well, including those that
  never supported specifying sendmail options.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1414696

Title:
  mailx commandline broken after recent bsd-mailx security update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bootmail/+bug/1414696/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1414684] Re: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail)

[Andreas Ntaflos]

Bug against Bootmail is here:
https://bugs.launchpad.net/ubuntu/+source/bootmail/+bug/1414696

> What do you suggest instead?

I don't really have a suggestion and I am not disputing that this change
was necessary.

But the USN description doesn't even mention that specifying sendmail
options after "--" is no longer supported. After some back and forth
(and seriously doubting my own sanity) I inferred that fact from the
changelog which mentions a "83-nosendmail.patch". I just wish the USN
advertised and documented this change and its full impact better.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1414684

Title:
  bsd-mailx no longer supports sendmail options, thus breaking existing
  scripts (like Bootmail)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bsd-mailx/+bug/1414684/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1414696] [NEW] mailx commandline broken after recent bsd-mailx security update

[Andreas Ntaflos]

Public bug reported:

bsd-mailx recently had a security update that completely removes support
for specifying classic sendmail options after "--" on the command line.
See http://changelogs.ubuntu.com/changelogs/pool/main/b/bsd-mailx/bsd-
mailx_8.1.2-0.2006cvs-1ubuntu0.1/changelog for 8.1.2-0.2006cvs-
1ubuntu0.1. This is on Ubuntu 12.04.

The update breaks the way Bootmail (and probably quite a few other
scripts) constructs its mail messages. Currently it looks like this:

print_mail_text | sed -e "s/[^[:print:]]//g" | rootsign | mail -s
"$subject" "$recipients" -- -F "Bootmail" -f "$FROM_MAIL"

The part after "--", i.e. the switches -F and -f, is now no longer
supported by bsd-mailx and results in "bad address syntax" error
messages in /var/log/mail.log:

Jan 26 16:20:09 example01 postfix/error[31885]: 4351640CB7:
to=<-f...@web01.example.com>, orig_to=<-F>, relay=none, delay=0.16,
delays=0.12/0/0/0.05, dsn=5.1.3, status=bounced (bad address syntax)

I reported a bug against bsd-mailx in
https://bugs.launchpad.net/ubuntu/+source/bsd-mailx/+bug/1414684 because
this change is obviously quite troublesome for any script that relies on
mailx understanding sendmail options.

To fix this in Bootmail I propose using the "-a" commandline switch to
set additional mail headers. Something like this:

print_mail_text | sed -e "s/[^[:print:]]//g" | rootsign | mail -s
"$subject" -a "Bootmail <${FROM_MAIL}>" "$recipients"

This has the advantage that it works with (probably) all bsd-mailx
versions and most other mailx variants as well, including those that
never supported specifying sendmail options.

** Affects: bootmail (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1414696

Title:
  mailx commandline broken after recent bsd-mailx security update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bootmail/+bug/1414696/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1414684] [NEW] bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail)

[Andreas Ntaflos]

Public bug reported:

The security update of bsd-mailx (8.1.2-0.2006cvs-1ubuntu0.1 on
Ubuntu 12.04) removes bsd-mailx's support for specifying sendmail
options after "--" on the commandline.

This breaks any script that supplies classic sendmail options like -F or
-f on the mail commandline. A prominent example is Bootmail, which calls
mailx in the following way:

print_mail_text | sed -e "s/[^[:print:]]//g" | rootsign | mail -s
"$subject" "$recipients" -- -F "Bootmail" -f "$FROM_MAIL"

Here the options -F and -f are used to set the From: header in the
resulting mail message. This is now broken and results in error messages
like these in /var/log/mail.log (on systems that run Postfix):

Jan 26 16:20:09 example01 postfix/error[31885]: 4351640CB7:
to=<-f...@web01.example.com>, orig_to=<-F>, relay=none, delay=0.16,
delays=0.12/0/0/0.05, dsn=5.1.3, status=bounced (bad address syntax)

Is this change going to stay for good? In that case we need to report a
bug against the Bootmail package (and probably quite a few others) to
change the mail commandline to use the "-a" commandline switch for
specifying additional mail headers.

I find it disconcerting that a security update completely removes
functionality that has been available and expected for many years
without providing a proper compatibility layer. Is this really the way
to do this?

** Affects: bsd-mailx (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

- The security update of bsd-mailx (8.1.2-0.2006cvs-1ubuntu0.1)
- removes bsd-mailx's support for specifying sendmail options after "--"
- on the commandline.
+ The security update of bsd-mailx (8.1.2-0.2006cvs-1ubuntu0.1 on
+ Ubuntu 12.04) removes bsd-mailx's support for specifying sendmail
+ options after "--" on the commandline.
  
  This breaks any script that supplies classic sendmail options like -F or
  -f on the mail commandline. A prominent example is Bootmail, which calls
  mailx in the following way:
  
  print_mail_text | sed -e "s/[^[:print:]]//g" | rootsign | mail -s
  "$subject" "$recipients" -- -F "Bootmail" -f "$FROM_MAIL"
  
  Here the options -F and -f are used to set the From: header in the
  resulting mail message. This is now broken and results in error messages
  like these in /var/log/mail.log (on systems that run Postfix):
  
  Jan 26 16:20:09 example01 postfix/error[31885]: 4351640CB7:
  to=<-f...@web01.example.com>, orig_to=<-F>, relay=none, delay=0.16,
  delays=0.12/0/0/0.05, dsn=5.1.3, status=bounced (bad address syntax)
  
  Is this change going to stay for good? In that case we need to report a
  bug against the Bootmail package (and probably quite a few others) to
  change the mail commandline to use the "-a" commandline switch for
  specifying additional mail headers.
  
  I find it disconcerting that a security update completely removes
  functionality that has been available and expected for many years
  without providing a proper compatibility layer. Is this really the way
  to do this?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1414684

Title:
  bsd-mailx no longer supports sendmail options, thus breaking existing
  scripts (like Bootmail)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bsd-mailx/+bug/1414684/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1001798] Re: Remote TLS connection to Libvirt 0.9.8 hangs (possibly a race condition and very possibly a regression)

[Andreas Ntaflos]

After my last comment here over two years ago I haven't had the time and
resources to debug this any more than I already had at that point. We
have since switched to using unencrypted Libvirt connections
(qemu+tcp:///) which is "good enough" since all virtualisation hosts are
on a separate and "secure" management subnet and VLAN.

But I just tried the qemu+tls:/// connections again just now, to six
different virtualisation hosts and I *can't* reproduce this problem any
more.

The hosts are all running Ubuntu 12.04.5, some with the Trusty HWE
kernel (e.g. 3.13.0-40-generic), some with the original Precise kernel
(e.g. 3.2.0-74-generic). Libvirt is installed in version
0.9.8-2ubuntu17.20. The Libvirt client in all cases is also a Ubuntu
12.04.5 machine, also running Libvirt 0.9.8-2ubuntu17.20.

We currently also leverage our Puppet CA and use the issued certificates
not only for Puppet but also for Libvirt and other services. I don't
think this makes a difference but two years ago when I ran into this
problem we were using keys and certificates issued by our own internal
CA.

So to me this looks resolved but since I have no idea what caused the
problem originally and what exactly has changed in Libvirt since then in
that regard I can only really say "WORKSFORME".

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1001798

Title:
  Remote TLS connection to Libvirt 0.9.8 hangs (possibly a race
  condition and very possibly a regression)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1001798/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 287644] Re: tomcat hangs on startup if ssl is enabled

[Andreas Ntaflos]

A possible workaround for this problem is to install an entropy
gathering daemon like haveged (apt-get install haveged) to keep
/dev/random supplied with entropy. Requires no additional configuration
and speeds things up tremendously.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/287644

Title:
  tomcat hangs on startup if ssl is enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tomcat-native/+bug/287644/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1325560] Re: kvm virtio netdevs lose network connectivity under "enough" load

[Andreas Ntaflos]

Installing 3.14.1 as per comment #17 fixed these connectivity issues for
us as well, but it doesn't look like the 3.14.1 kernel made it anywhere
near the 14.04.1 release. There is also no mention of this or any
related bugs in
https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/ChangeSummary/14.04.1.

What else can we do except manually install 3.14.1, which is obviously
not a proper solution?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1325560

Title:
  kvm virtio netdevs lose network connectivity under "enough" load

To manage notifications about this bug go to:
https://bugs.launchpad.net/libvirt/+bug/1325560/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

[Andreas Ntaflos]

@auspex: the GTK2_RC_FILES workaround should work for this bug, how are
you calling it? Should look like this:

$ GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc
/path/to/eclipse/or/whatever

Alternatively you can set the GTK2 theme to Raleigh globally and try
starting your crashing application then.

If neither of these helps then you are probably experiencing a different
bug, or at least a very different manifestation that apparently hasn't
been encountered yet, going by the information in this thread.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101

Title:
  Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1241101/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

[Andreas Ntaflos]

Just so that this doesn't get overlooked: I have this problem with
Apache Directory Studio (an Eclipse RCP application) running on Kubuntu
13.10 using KDE 4.12 and the oxygen-gtk engine. It is definitely not
related to Unity directly, though I don't know how many libraries or how
much code oxygen-gtk and Unity share.

In any case, the workaround of running (in my case)
GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc
ApacheDirectoryStudio still applies.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101

Title:
  Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1241101/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1205452] Re: Eclipse unusable in Kubuntu Saucy (almost immediate JVM segfault)

[Andreas Ntaflos]

"Same here." Freshly updated from Kubuntu 13.04 to Kubuntu 13.10.
Eclipse, or in my case Apache Directory Studio, which is basically
Eclipse, can't be started as the JVM segfaults after a few seconds.
Happens with both OpenJDK 7 and Oracle Java 7.

Changing GTK2 theme to Raleigh makes Eclipse (Apache Directory Studio)
start correctly, but this theme offends my sense of aesthetics :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205452

Title:
  Eclipse unusable in Kubuntu Saucy (almost immediate JVM segfault)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/java-common/+bug/1205452/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1235616] Re: linux-crashdump doesn't actually dump and reboot

[Andreas Ntaflos]

Looking further this memory problem is already tracked in bug #785394,
untouched for almost two years now.

So this bug here should serve as a reminder that the official
documentation (https://help.ubuntu.com/lts/serverguide/kernel-crash-
dump.html) is wrong. It should at least contain links to the bugs
affecting linux-crashdump, like
https://wiki.ubuntu.com/Kernel/CrashdumpRecipe#Release_specific_notes
does, because when just following the documentation the crashdump
functionality just does not work.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235616

Title:
  linux-crashdump doesn't actually dump and reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1235616/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1235616] Re: linux-crashdump doesn't actually dump and reboot

[Andreas Ntaflos]

Very interestingly, when setting `crashkernel=128M` instead of the
default `crashkernel=384M-2G:64M,2G-:128M`, crashing the machine works
correctly and also leaves a crashdump in /var/crash. Unfortunately
setting the crashkernel parameter requires editing /etc/grub.d/10_linux
directly and can not be overridden by means of /etc/default/grub.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235616

Title:
  linux-crashdump doesn't actually dump and reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1235616/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1235616] Re: linux-crashdump doesn't actually dump and reboot

[Andreas Ntaflos]

Just about the same here on a few generic Ubuntu 12.04.2 VMs (using
KVM). Followed the documentation on
https://wiki.ubuntu.com/Kernel/CrashdumpRecipe and
https://help.ubuntu.com/lts/serverguide/kernel-crash-dump.html which
basically says: install linux-crashdump, reboot, check /proc/cmdline,
make sure `/proc/sys/kernel/sysrq` is enabled and then "echo c >
/proc/sysrq_trigger". This certainly crashes the VM but it just stays
crashed: http://i.imgur.com/amCrAZW.png

After forcing a reboot using virt-manager the machine boots fine but
/var/crash is empty. No crash dumps, no nothing.

What gives?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235616

Title:
  linux-crashdump doesn't actually dump and reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1235616/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1150006] [NEW] libnfnetlink (and therefore conntrackd) fails to correctly determine link status

[Andreas Ntaflos]

Public bug reported:

This bug has been reported and recently fixed in Debian
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684863) and discussed
in  specifically
in .

libnfnetlink 1.0.0-1 as used in Ubuntu 12.04 suffers from this bug where
it fails to correctly determine the link status of "special" devices
such as VLANs or bonds. Therefore conntrackd complains about "[ERROR] no
dedicated links available!" when starting, even though a dedicated link
is indeed available. As explained this happens especially when using
bonding or VLAN devices as interfaces for exchanging synchronisation
messages. See this example from conntrackd.conf:

UDP Default {
IPv4_address 10.0.6.4
IPv4_Destination_Address 10.0.6.3
Port 3780
Interface vlan62
SndSocketBuffer 1249280
RcvSocketBuffer 1249280
Checksum on
 }

It seems the bug has been fixed in Debian's libnfnetlink 1.0.0-1.1. It
should also be included in Ubuntu 12.04.

** Affects: libnfnetlink (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1150006

Title:
  libnfnetlink (and therefore conntrackd) fails to correctly determine
  link status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnfnetlink/+bug/1150006/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 692355] Re: fsck doesn't update system info on login

[Andreas Ntaflos]

Still a problem on 12.04.1. Removing /var/lib/update-notifier/fsck-at-
reboot and logging out, then back in works. The /etc/motd is updated and
no longer contains this misleading and wrong message about pending
fscks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692355

Title:
  fsck doesn't update system info on login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/692355/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1076860] [NEW] PostgreSQL init script wrongly returns 0 for "status" when no clusters are running

[Andreas Ntaflos]

Public bug reported:

Because "set +e" is set in the "status" case of the postgresql init
script, running "service postgresql status" or "/etc/init.d/postgresql
status" always returns with exit code 0. Even when no clusters are
running the exit code is 0, when it should really be 3, indicating that
the service is not running (as per LSB specs). This has negative
implications for Pacemaker, Puppet and other applications that expect
init scripts to conform to LSB specifications.

Attached is a simple patch that removes "set +e" and makes the init
script behave properly.

** Affects: postgresql-9.1 (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "Remove "set +e" from init script so the "status" operation 
exits with the proper return codes of 0 when the service is running and 3 when 
it is not"
   
https://bugs.launchpad.net/bugs/1076860/+attachment/3428393/+files/postgresql.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076860

Title:
  PostgreSQL init script wrongly returns 0 for "status" when no clusters
  are running

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1076860/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 445619] Re: slapd should start before kerberos kdc and admin servers, possibly others

[Andreas Ntaflos]

This is still a problem, both in Lucid and Precise.

** Summary changed:

- [karmic] slapd should start before kerberos kdc and admin servers, possibly 
others
+ slapd should start before kerberos kdc and admin servers, possibly others

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/445619

Title:
  slapd should start before kerberos kdc and admin servers, possibly
  others

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/445619/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1001798] Re: Remote TLS connection to Libvirt 0.9.8 hangs (possibly a race condition and very possibly a regression)

[Andreas Ntaflos]

It's funny. I have three machines where I can always reproduce the
behaviour in my original description and two machines where I can
connect and list just fine. All running Precise. The two where it works
are slightly newer, i.e. have been set up some time in the last two
months, whereas the others are from May or so. Otherwise the machines
are identical PowerEdge R710s. Around the same number of VMs, same CPUs,
amount of RAM, network configuration, etc.

I don't know if it makes any difference in these tests, but it seems you
have no VMs running on your virtualisation host. Maybe add some?

It may also be noteworthy that our VMs' disks are all LVM-based, which
is why we are also bitten by bug #1027987. I wouldn't want to presume
anything but maybe there is some relation between this bug and that.

Unfortunately I still need some time before I can test any of this out
on some spare machines running Quantal.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1001798

Title:
  Remote TLS connection to Libvirt 0.9.8 hangs (possibly a race
  condition and very possibly a regression)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1001798/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 989452] Re: oneiric's virt-viewer can't connect to console of precise's virtual machines

[Andreas Ntaflos]

Serge, at the moment it is a bit difficult but in a few weeks I could
have some spare machines available on which I could install Quantal.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989452

Title:
  oneiric's virt-viewer can't connect to console of precise's virtual
  machines

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/989452/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 989452] Re: oneiric's virt-viewer can't connect to console of precise's virtual machines

[Andreas Ntaflos]

Addendum: All this with Precise machines (client and server), no Oneiric
or earlier involved.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989452

Title:
  oneiric's virt-viewer can't connect to console of precise's virtual
  machines

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/989452/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 989452] Re: oneiric's virt-viewer can't connect to console of precise's virtual machines

[Andreas Ntaflos]

There are currently multiple bugs that deal with virt-manager/virt-
viewer not being able to connect to a VNC console of a Libvirt/KVM
domain, such as #837275, #995320 and this one.

The problem remains, however. On a Precise server (12.04.1) where
/etc/libvirt/qemu.conf has set

vnc_listen = "0.0.0.0"
vnc_tls = 0

no VNC connection is possible with neither virt-manager, nor virt-viewer
from a remote client. Virt-manager just displays the dreaded "Error:
viewer connection to hypervisor host got refused or disconnected!" and
virt-viewer says "Unable to connect to the graphic server 0:5916" when
called like this:

virt-viewer -c qemu+tcp://kvmhost04/system domain01.example.com

Libvirt is configured to allow unencrypted TCP connections (because of
bug #1001798) so regular virt-manager interaction works, just not the
VNC console.

This must be a virt-manager, Libvirt or QEMU issue, because using a VNC
viewer like xtightvncviewer to connect to the domain's VNC port works
fine:

xtightvncviewer kvmhost04:5916

So what can we do? I see no interesting log entries anywhere that would
begin to explain what is going on here.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989452

Title:
  oneiric's virt-viewer can't connect to console of precise's virtual
  machines

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/989452/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1027987] Re: Starting libvirtd takes too long because of "udevadm settle" timeout

[Andreas Ntaflos]

Is this going to make it into 12.04.2?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027987

Title:
  Starting libvirtd takes too long because of "udevadm settle" timeout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1027987/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1018538] Re: Byobu 5.20 makes it almost impossible to select text from the terminal

[Andreas Ntaflos]

I just reproduced this again, with a byobu 5.20 running locally and a
byobu 5.21 running remotely. Using both KDE's konsole as well as a
regular xterm. I am running Kubuntu and thus KDE (4.8.4 at the moment),
does this matter any?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1018538

Title:
  Byobu 5.20 makes it almost impossible to select text from the terminal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1018538/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 955164] Re: PostgreSQL resource agent has wrong default paths

[Andreas Ntaflos]

This is not really a bug. Sure, the resource agent has defaults set that
don't match Ubuntu's, but every relevant parameter can (and probably
should) be set explicitly in the CIB. For example:

primitive p_postgresql ocf:heartbeat:pgsql \
params pgctl="/usr/lib/postgresql/9.1/bin/pg_ctl" psql="/usr/bin/psql" 
pgdata="/var/lib/postgresql/9.1/main" 
config="/etc/postgresql/9.1/main/postgresql.conf" 
logfile="/var/log/postgresql/postgresql-9.1-main.log" \
op start interval="0" timeout="120s" \
op stop interval="0" timeout="120s" \
op monitor interval="30s" timeout="30s"

The resource agent is able to start a PostgreSQL server just fine,
having the parameters set to correct values.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955164

Title:
  PostgreSQL resource agent has wrong default paths

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/955164/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1012900] Re: Using SSSD, PAM error when exiting su session

[Andreas Ntaflos]

Mark, thanks for the suggestion, will look into that. I was under the
impression that pam_sss in /etc/pam.d/common-session was needed for
access control as provided by SSSD, but I was wrong, apparently.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012900

Title:
  Using SSSD, PAM error when exiting su session

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1012900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1012900] Re: Using SSSD, PAM error when exiting su session

[Andreas Ntaflos]

Agreed, this is indeed somewhat critical in my opinion. It breaks, for
example, the Pacemaker resource agent for PostgreSQL
(ocf:heartbeat:pgsql), which uses "su" to start and stop a PostgreSQL
instance. Some packages' postinst scripts also fail because "su" doesn't
exit correctly, for example Monkeysphere.

A fix for Precise would be most welcome. That, or a PPA build of 1.9.0.
for Precise. *looks at Timo* :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012900

Title:
  Using SSSD, PAM error when exiting su session

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1012900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1027987] Re: Starting libvirtd takes too long because of "udevadm settle" timeout

[Andreas Ntaflos]

Ryan, what you are missing out on is Libvirt being able to create
volumes (LVs) in that pool (the VG) on command. I assume you create LVs
manually via lvcreate and then tell Libvirt to use them for VMs? If
Libvirt manages the pool you can use virt-manager, virsh or any of the
APIs/bindings to talk to Libvirt and command the creation of volumes for
VMs.

An interesting point you brought up: we have dozens of servers running
Ubuntu 12.04 for many weeks now where either this problem was not
present (or not as promiment) or I simply have not noticed it
consciously before. Unfortunately I can't test and experiment much since
most of these servers are in production. On the servers I can experiment
the problem is definitely present and noticeable.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027987

Title:
  Starting libvirtd takes too long because of "udevadm settle" timeout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1027987/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1027987] Re: Starting libvirtd takes too long because of "udevadm settle" timeout

[Andreas Ntaflos]

Sorry, no idea where this commit is supposed to be. I was going off the
information in the last entry of the Debian bug report, which contains
this:

* [202939f] Reduce udevadm settle timeout to 10 seconds
 (Closes: #663931)

Maybe this is a Debian-only commit that didn't go back into Libvirt?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027987

Title:
  Starting libvirtd takes too long because of "udevadm settle" timeout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1027987/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1027987] [NEW] Starting libvirtd takes too long because of "udevadm settle" timeout

[Andreas Ntaflos]

Public bug reported:

This bug has already been reported in http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=663931 but Libvirt 0.9.8 in Ubuntu Precise suffers
from the same problem.

When an LVM-based storage pool is present libvirtd takes around three
minutes to start up because a timeout occurs when libvirtd calls
"udevadm settle". In the Debian bug report this has been identified as a
problem in Libvirt, additional info is found here:
http://article.gmane.org/gmane.linux.hotplug.devel/17421

 A local workaround is to issue "service udev restart" before starting
libvirtd.

The bug has been worked around in Debian's Libvirt 0.9.12 by reducing
the "udev settle" timeout to ten seconds.

Can we expect this workaround to somehow make it into Libvirt 0.9.8 and
Ubuntu Precise?

** Affects: libvirt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027987

Title:
  Starting libvirtd takes too long because of "udevadm settle" timeout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1027987/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1018538] [NEW] Byobu 5.20 makes it almost impossible to select text from the terminal

[Andreas Ntaflos]

Public bug reported:

Using Byobu 5.20 on Ubuntu 12.04. This problem seems to only occur on
Ubuntu 12.04, not on 10.04. I can't test others.

After starting a byobu instance it is nigh impossible to use the mouse
cursor to do text selections from the terminal window in which byobu
runs. The selection is only active for one second maximum, then it
vanishes. I have created a screencast to illustrate this. See here:
https://daff.ptmx.org/misc/byobu-selection.ogv

If you watch the time display in the lower right corner you can see that
the selection vanishes exactly in the moment the seconds count changes.

I have tested this with the time and date display disabled, same result.
I have also tested it in a plain Xterm window to make sure it is not my
KDE installation that screws things up, same result. And, as I said, it
only occurs on Ubuntu 12.04 servers, not 10.04.

Interestingly everything works fine and as expected when I downgrade to
Byobu 5.17 from the default Precise repos. So this behaviour change
happened some time between 5.17 and 5.20.

What could cause this?

** Affects: byobu (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1018538

Title:
  Byobu 5.20 makes it almost impossible to select text from the terminal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1018538/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1006267] Re: sshfs in 12.04 doesn't like to mount to remote symlinks

[Andreas Ntaflos]

I believe you have to add a trailing slash to the remote path to avoid
this bug, like so:

sshfs -o idmap=user remote_lucid:/data/ ~/mnt/lucid_data

See this discussion from a year ago: http://thread.gmane.org/gmane.comp
.file-systems.fuse.sshfs/1182/focus=1189

Why this bug made it into Ubuntu 12.04 I have no idea.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1006267

Title:
  sshfs in 12.04 doesn't like to mount to remote symlinks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sshfs-fuse/+bug/1006267/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1001798] Re: Remote TLS connection to Libvirt 0.9.8 hangs (possibly a race condition and very possibly a regression)

[Andreas Ntaflos]

In my case, the client was indeed 12.04, but I just tested with a 10.04
client (0.9.2-5ubuntu0+dnjl0~lucid0, from
https://launchpad.net/~dnjl/+archive/virtualization) and the problem is
the same. So what I can say is this:

 * 12.04 virsh client via TLS to 12.04 libvirt host doesn't work
 * 10.04 virsh client via TLS to 12.04 libvirt host doesn't work
 * 12.04 virsh client via TLS to 10.04 libvirt host works
 * 10.04 virsh client via TLS to 10.04 libvirt host works
 * All virsh clients to all libvirt hosts work with TCP or SSH

Anything else I can do?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1001798

Title:
  Remote TLS connection to Libvirt 0.9.8 hangs (possibly a race
  condition and very possibly a regression)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1001798/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1001798] Re: Remote TLS connection to Libvirt 0.9.8 hangs (possibly a race condition and very possibly a regression)

[Andreas Ntaflos]

** Attachment added: "Libvirt daemon strace of successful remote connection 
attempt"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1001798/+attachment/3154339/+files/libvirt-strace-works.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1001798

Title:
  Remote TLS connection to Libvirt 0.9.8 hangs (possibly a race
  condition and very possibly a regression)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1001798/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1001798] Re: Remote TLS connection to Libvirt 0.9.8 hangs (possibly a race condition and very possibly a regression)

[Andreas Ntaflos]

** Attachment added: "Libvirt daemon strace of failed/hung remote connection 
attempt"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1001798/+attachment/3154338/+files/libvirt-strace-hangs.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1001798

Title:
  Remote TLS connection to Libvirt 0.9.8 hangs (possibly a race
  condition and very possibly a regression)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1001798/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1001798] Re: Remote TLS connection to Libvirt 0.9.8 hangs (possibly a race condition and very possibly a regression)

[Andreas Ntaflos]

** Attachment added: "Libvirt daemon debug logs of a successful remote 
connection attempt"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1001798/+attachment/3154337/+files/libvirt-debug-works.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1001798

Title:
  Remote TLS connection to Libvirt 0.9.8 hangs (possibly a race
  condition and very possibly a regression)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1001798/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1001798] Re: Remote TLS connection to Libvirt 0.9.8 hangs (possibly a race condition and very possibly a regression)

[Andreas Ntaflos]

** Attachment added: "Libvirt daemon debug logs of a failed/hung remote 
connection attempt"
   
https://bugs.launchpad.net/bugs/1001798/+attachment/3154335/+files/libvirt-debug-hang.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1001798

Title:
  Remote TLS connection to Libvirt 0.9.8 hangs (possibly a race
  condition and very possibly a regression)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1001798/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1001798] [NEW] Remote TLS connection to Libvirt 0.9.8 hangs (possibly a race condition and very possibly a regression)

[Andreas Ntaflos]

Public bug reported:

Connecting to a remote Libvirt instance on Ubuntu 12.04 (libvirt 0.9.8)
via, e.g., virsh -c qemu+tls://hostname.example.com/system simply hangs.
I have to terminate virsh with Ctrl+C to get my terminal back.

Connecting to the same remote Libvirt instance via unencrypted TCP
(qemu+tcp) or via SSH (qemu+ssh) works. Connecting to a different
Libvirt instance on Ubuntu 10.04 from the same client machine as above
via qemu+tls works fine, too. So this looks like a regression to me, if
that term applies here.

What is interesting is that the remote connection via qemu+tls to the
problematic Libvirt instance *works* in many cases when I run strace on
the daemon process AND the strace output goes to stdout. Could this
indicate a race condition somewhere in the Libvirt (or TLS/SSL) code?
Seeing as tracing system calls and printing them to stdout generally and
noticeably impacts performance?

I will attach debug logs from the problematic remote Libvirt daemon as
well as strace outputs, one of each where the connection worked (thanks
to the strace voodoo) and one of each where the connection hung
(hanged?).

In the "hang" debug logs there is a line "authentication failed: TLS
handshake failed A TLS packet with unexpected length was received." This
indicates my pressing Ctrl+C on the remote client side (terminating the
hanging virsh process). In the "works" debug logs there is also one such
line, which indicates one connection attempt failed in the described
manner, but after it follows a connection attempt that worked. As I
said, the strace voodoo makes *most* connection attempts work, but not
all. Again, this indicates to me some kind of race condition somewhere.

Please let me know what I can do to debug and test this further.

** Affects: libvirt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1001798

Title:
  Remote TLS connection to Libvirt 0.9.8 hangs (possibly a race
  condition and very possibly a regression)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1001798/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 943050] Re: Running byobu within byobu (on different hosts) breaks 256 color support

[Andreas Ntaflos]

Sorry, totally forgot to follow up.

It seems tmux alone, in a single instance (no tmux within tmux) breaks
256 colors as well. NB: I have not configured tmux in any way, just
running it like "tmux" from a fresh SSH shell. I also found that the
problem of broken 256 color support in nested sessions persists when
switching backends to "screen".

So it seems the following is true:

1) Single Byobu instance with tmux backend works with 256 colors
2) Single tmux instance breaks 256 colors (probably a configuration issue)
3) Byobu instance (tmux) within Byobu (tmux) breaks 256 colors
4) Tmux instance within tmux: breaks 256 colors (as before)
5) Single Byobu instance with screen backend works with 256 colors
6) Byobu instance (screen) within Byobu (screen) breaks 256 colors

So I think Byobu is somehow responsible, because it seems to be the
common element here.

Can I do anything else to debug this?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/943050

Title:
  Running byobu within byobu (on different hosts) breaks 256 color
  support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/943050/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 423252] Re: NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2 suexec, and atd

[Andreas Ntaflos]

Just to add something that has nothing to do directly with this bug, but
is related: we have been using SSSD for quite a while now, using Timo
Aaltonen's PPA  and could
not be happier. In my opinion SSSD is the superior solution for all
things authn/authz, tying together LDAP, Kerberos and PAM. There are
still some minor Ubuntu-related issues with the ordering of the involved
PAM modules but everything works very well, apart from that.

I think Ubuntu would do well to properly integrate and incorporate SSSD,
especially in the Server edition.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/423252

Title:
  NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2
  suexec, and atd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/423252/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 771372] Re: procps runs too early in the boot process

[Andreas Ntaflos]

Is this now really fixed in Lucid? As I have mentioned in comment #29 we
had applied this update from lucid-proposed and and continue to see this
error in /var/log/boot.log:

init: procps (virtual-filesystems) main process (670) terminated with
status 255

The initial problem remains the same, the sysctl settings do not get
applied in time.

We need to use this workaround in order to get VLAN trunks into Libvirt-
managed virtual machines (KVM):

/etc/rc.local:

# At this point automatic startup of libvirt-bin.conf is disabled, we start it 
manually below
/sbin/sysctl -p /etc/sysctl.conf
/etc/init.d/networking restart
/etc/init.d/libvirt-bin start
exit 0

This is on Ubuntu 10.04.4, x86_64 on all of our Dell R710 servers.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771372

Title:
  procps runs too early in the boot process

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/771372/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 943050] [NEW] Running byobu within byobu (on different hosts) breaks 256 color support

[Andreas Ntaflos]

Public bug reported:

Using byobu version 5.15/tmux 1.5 on Ubuntu 10.04.4.

It seems that running byobu within an existing byobu session breaks or
disables 256 colors in the inner byobu session.

Scenario:

1) Log into a server (using SSH)
2) Start byobu 
3) From a byobu window, ssh into another server
4) Start byobu on the server just connected to
5) Observe 256colors.pl showing very little color

I have created two screenshots, showing the problem:
https://imgur.com/a/Tlqxv

In the first there is only one byobu session and 256 colors work fine,
both on the first host (adm01) and on the second (puppet01). Starting
byobu on the second host (puppet01) then breaks 256 color support.

** Affects: byobu (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/943050

Title:
  Running byobu within byobu (on different hosts) breaks 256 color
  support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/943050/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 908766] Re: byobu-tmux changes background color in applications

[Andreas Ntaflos]

To chime in here, there still appears to be the problem that Vim doesn't
understand that the terminal is capable of displaying 256 colors
*unless* one explicitly sets 'set t_Co=256' in ~/.vimrc. I don't know if
Byobu can do anything about that but it seems Vim only understands 256
colors if the TERM variable contains a string like "256color". At least
according to http://vim.wikia.com/wiki/256_colors_in_vim if I understood
it correctly.

I can provide screenshots if that helps.

Using byobu version 5.15, tmux 1.5.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908766

Title:
  byobu-tmux changes background color in applications

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/908766/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 771372] Re: procps runs too early in the boot process

[Andreas Ntaflos]

We applied the proposed fix to procps on a test machine but upon
rebooting the problem remained, with the following message appearing in
/var/log/boot.log:

init: procps (virtual-filesystems) main process (670) terminated with
status 255

We use /etc/sysctl.conf to disable frame filtering for bridges and
vlans:

net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0
net.bridge.bridge-nf-filter-vlan-tagged = 0

The machine is a Dell R710, but I don't think that matters. What other
info can we provide?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771372

Title:
  procps runs too early in the boot process

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/771372/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50093] Re: Some sysctl's are ignored on boot

[Andreas Ntaflos]

A possible workaround is putting "sysctl -p /etc/sysctl.conf" in
/etc/rc.local, which is ridiculous and doesn't even solve the problem
that networking and bridges are started *before* the sysctl settings are
applied.

It is even more ridiculous that this bug hasn't had any attention from
anyone except affected users in over five years. *Every* piece of
documentation regarding any kind of sysctl setting refers to
/etc/sysctl.conf as the place to put everything. And for over five years
there has been a really good chance that most of /etc/sysctl.conf gets
ignored because Ubuntu's boot process apparently doesn't know how when
and often to read and apply the settings in there. This isn't just an
upstart problem since upstart wasn't even around in 2006.

Bugs like this make it really difficult to recommend Ubuntu as a server
operating system and I wonder if Canonical really use Ubuntu as their
server OS. If they did it seems this bug would have been fixed years
ago.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/50093

Title:
  Some sysctl's are ignored on boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 551545] Re: PXE netboot not booting localboot from virtio-disk

[Andreas Ntaflos]

Still a problem in Lucid, making automatic installation and deployment
of VMs (using Cobbler or Foreman) pretty much impossible without manual
intervention. This, of course, defeats the whole point of automatic
installation and deployment.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/551545

Title:
  PXE netboot not booting localboot from virtio-disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/551545/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 868474] [NEW] Undefined _UNUSED_PARAMETER_: configure/build fails

[Andreas Ntaflos]

Public bug reported:

A bug in libunistring/libunistring-dev in Ubuntu 10.04 leaves the
_UNUSED_PARAMETER_ macro undefined, resulting in compiler errors when
building or configuring with unistr.h.

See the following bug report for workaround and a patch:
http://lists.gnu.org/archive/html/bug-libunistring/2009-12/msg3.html

I don't know if the LTS policy allows for fixing such bugs in 10.04 but
it would be very nice to have as it allows for backporting sssd to
Lucid.

** Affects: libunistring (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/868474

Title:
  Undefined _UNUSED_PARAMETER_: configure/build fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/868474/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 541512] Re: open-iscsi shutdown failure due to missing dir

[Andreas Ntaflos]

This is still a problem on Ubuntu 10.04.3.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/541512

Title:
  open-iscsi shutdown failure due to missing dir

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/541512/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 350936] Re: Should shut down domains on system shutdown

[Andreas Ntaflos]

Clint, great to hear, thanks. We have many Lucid servers in production,
but no Maverick or Natty, so the fix getting into Lucid is most
important for us. But if time and resources allow it, backporting the
fix to Maverick and Natty would certainly be nice.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/350936

Title:
  Should shut down domains on system shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/350936/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 350936] Re: Should shut down domains on system shutdown

[Andreas Ntaflos]

So is there any way the proper fix will make it into Lucid? Or has that
ship sailed?

In the meantime I have applied Sebastian Marsching's method which works
quite well. Thanks for that, Sebastian.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/350936

Title:
  Should shut down domains on system shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/350936/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 571444] Re: Boot hangs and unable to continue when automount disk in fstab is not available (Off or Disconnected)

[Andreas Ntaflos]

** Changed in: mountall (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571444

Title:
  Boot hangs and unable to continue when automount disk in fstab is not
  available (Off or Disconnected)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/571444/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 356766] Re: Changing long passwords causes spurious error

[Andreas Ntaflos]

It is now May 2011 and this bug is still present in Ubuntu 10.04.2.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/356766

Title:
  Changing long passwords causes spurious error

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 350936] Re: Should shut down domains on system shutdown

[Andreas Ntaflos]

Orticio, this is an English-speaking forum. Please stop asking people to
speak Spanish.

Translated by Google:

Este es un foro de habla Inglés. Por favor, deje de pedir a la gente a
hablar español.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/350936

Title:
  Should shut down domains on system shutdown

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 337763] Re: virt-manager reboot action is non-functional

[Andreas Ntaflos]

Serge,

why do you think this bug has been fixed? Nowhere is it confirmed that a
fix has been released, not even the associated Red Hat bug has seen any
activity in months.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/337763

Title:
  virt-manager reboot action is non-functional

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 579723] Re: kvm memory ballooning is unusable in Lucid

[Andreas Ntaflos]

This does not seem fixed in 10.04.1. The fix would apparently belong in
Libvirt but the changelogs for the Libvirt package in 10.04.1 don't
indicate anything and no KVM guest processes on my hosts running 10.04.1
show the "-balloon virtio" flag. I had to use a wrapper script around
qemu-system-x86_64 to add the flag as discussed above.

Is this fix in Maverick? Can it perhaps be included in 10.04.2?

-- 
kvm memory ballooning is unusable in Lucid
https://bugs.launchpad.net/bugs/579723
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 81242] Re: postfix-ldap is linked against gnuTLS

[Andreas Ntaflos]

For what it's worth this is still a problem in 10.04.1 and Postfix
2.7.0-1. Manually copying /dev/random and /dev/urandom to
/var/spool/postfix/dev works around the problem.

I also find it quite strange that this doesn't affect more people. In
fact this bug seems to have been completely forgotten. Is nobody using
Postfix, LDAP and SSL/TLS on Ubuntu?

-- 
postfix-ldap is linked against gnuTLS
https://bugs.launchpad.net/bugs/81242
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 655431] Re: PostgreSQL init script make Heartbeat's ResourceManager believe PostgreSQL is running, even when it is not

[Andreas Ntaflos]

** Attachment added: "One-line fix for confusing output of 
/etc/init.d/postgresql-8.4 status"
   
https://bugs.launchpad.net/bugs/655431/+attachment/1674266/+files/init.d-functions.patch

-- 
PostgreSQL init script make Heartbeat's ResourceManager believe PostgreSQL is 
running, even when it is not
https://bugs.launchpad.net/bugs/655431
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 655431] [NEW] PostgreSQL init script make Heartbeat's ResourceManager believe PostgreSQL is running, even when it is not

[Andreas Ntaflos]

Public bug reported:

Binary package hint: postgresql-8.4

The initd-functions of PostgreSQL 8.4.4-0ubuntu10.04 make Heartbeat's
ResouceManager (/usr/share/heartbeat/ResourceManager) believe that
PostgreSQL is running even when it is not, thus breaking clustering of
Postgres instances using Heartbeat. I don't know if the problem is in
Postgres or in Heartbeat but this is the result.

When calling

/etc/init.d/postgresql-8.4 status

the output is like the following:

  Running clusters: 8.4/main

And when no clusters are running:

  Running clusters:

In both cases the word "Running" appears on stdout, making
ResourceManager believe that PostgreSQL is already started.
ResourceManager thus does not try to start it even though it should. The
check is in /usr/share/heartbeat/ResourceManager starting on line 205.

A really old bug filed against Debian's Heartbeat describes a similar
problem: . Sorry for that awful
link but I can't seem to find the original bug report.

A fix to the init.d-functions could be as simple as removing the word
"Running" from the output, as seen in the attached patch.

Again, I don't know if the problem is Postgres or Heartbeat and I don't
know which should be fixed but since Postgres is the package that
changed its behaviour (from previous versions, i.e. from 8.4.4ubuntu9.10
to 8.4.4ubuntu10.04) I think the fix should go here.

** Affects: postgresql-8.4 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
PostgreSQL init script make Heartbeat's ResourceManager believe PostgreSQL is 
running, even when it is not
https://bugs.launchpad.net/bugs/655431
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 495394] Re: autostart almost always fails on boot time host

[Andreas Ntaflos]

Thanks for the new patch! I tested it just now and it seems to work, but
it's always hard to tell when dealing with race conditions. I'll keep
testing.

Out of interest, the only change (apart from the more verbose way of
testing the $interface variable) is the added "break" statement, right?
I am not familiar enough with the Upstart boot process but why does this
change make the job work correctly? I also have not found any info on
what exactly ifquery does. Does it just read /etc/network/interfaces and
extract the interface names?

Anyway, thanks again!

-- 
autostart almost always fails on boot time host
https://bugs.launchpad.net/bugs/495394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 495394] Re: autostart almost always fails on boot time host

[Andreas Ntaflos]

Mika, thank you for the patch and new upstart job. We are trying it out
here and find that the bridged-network job seems to be waiting forever
for a "net-device-up" signal to be emitted, thus keeping libvirtd-bin
from starting.

I only now have begun reading up on upstart but so far I can't find any
obvious flaws in your job definition. Waiting on the "net-device-up"
signal which is emitted every time a network interface comes up
(/etc/network/if-up.d/upstart) and then checking the status of the
bridges seems the correct way but it doesn't work for us.

Did you take any additional steps in order to get this upstart job to
work correctly?

-- 
autostart almost always fails on boot time host
https://bugs.launchpad.net/bugs/495394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot

[Andreas Ntaflos]

*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444

Ah, I see. I must have misunderstood your post, sorry. It is interesting
and disturbing that there seem to be so many conditions that could
result in a server not booting correctly.

-- 
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot

[Andreas Ntaflos]

*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444

Fionn, glad you solved your problem, but it is not this particular
problem.

I want to remind everyone that any kind of mounting problems have
nothing to do with the issue this bug report describes, namely that at
least one specific linux-image package (2.6.32-22-server) caused the
boot process to hang in an early stage. Problems with mountall, missing
console messages and separate partitions in /etc/fstab do not factor in
at all here.

This is evident by the facts that a) /etc/fstab contains no additional
entries that could fail to mount and b) pressing 's' or 'm' does not
result in the boot process continuing regularly.

So please, someone who has the power to do so, unmark this bug as a
duplicate of #571444 or any other mountall/plymouth related bug.

-- 
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot

[Andreas Ntaflos]

*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444

This bug is not a duplicate of #571444. At least not in the
characteristic that I and others who reported here have experienced it.
My /etc/fstab was always in the pristine state that is the result of a
fresh installation so there were no filesystems for which automounting
could have failed.

Additionally, as reported in #571444, pressing 'S' or 'M' when the
system appeared to hang continued and finished the boot sequence
correctly. Not so in the case of this bug, where nothing but Ctrl-Alt-
Delete would have any effect on the hung system.

So this is definitely not a duplicate of #571444. The good news is that
the problem was apparently isolated to the linux-image-2.6.32-22-server
package, i.e. the server kernel image in version 2.6.32-22. We are now
at 2.6.32-24 and I have several Ubuntu Server 10.04.1 machines in
production, all working fine, even with regularly performed reboots. The
same machines would have the problem described at length by us in this
bug report.

Thomas, do you still experience any hangs during boot with a current
-server image package?

-- 
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot

[Andreas Ntaflos]

Chiming in again I am cautiously optimistic that with the latest -server
packages (-23 and recently -24) the problem went away. I have installed
and upgraded two identical DL380 G6 servers and performed many
consecutive reboots since and have yet to experience any hangs. I just
rebooted one of the machines three times in a row, no problem. My hopes
are high.

-- 
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot

[Andreas Ntaflos]

Charles, that's definitely a bug. I believe there have been efforts in
Plymouth to fix it but you need to the splash screen for those error
messages to be displayed. A default server install, or one where the
kernel is instructed to boot with as much text output as possible
(GRUB_CMDLINE_LINUX_DEFAULT="text" in /etc/default/grub), apparently has
no way to display such messages.

However, that seems to be a completely different issue altogether. In my
experiences posted above there were no special or additional entries in
/etc/fstab whatsoever and even pressing "s" or "m" when the server hung
did not do anything. It was just a default install of the Ubuntu server
edition.

On a related note: I've now finally gotten back two servers of the kind
that had the problems described earlier in this thread. I will test them
extensively this week. It also seems that running a -generic kernel
really helps. One machine that had to go into production also runs a
-server kernel but it is 2.6.32-23-server (not -22-server) and on the
(very few) reboots I did on it no hangs would occur. So maybe this has
fixed itself but I'll know more after this week.

-- 
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot

[Andreas Ntaflos]

jgreenso, I will try a -generic kernel image hopefully next week or the
week after that, when I get my hands on one of the machines on which we
experienced the problems.

-- 
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot

[Andreas Ntaflos]

Charles, I'll be trying your idea as soon as I get one of the machines
back (next week probably). Maybe I can find some pattern :)

But I really don't think this is in any way "fixed". All we know is that
there are at least five people affected by it and no solution has been
posted or linked to other than "use a different kernel" and
(paraphrasing) "it seems to be working now, but I have no idea why". One
is a workaround and the other is basically ... nothing. Having this bug
marked as "Fix Released" is either a mistake or some arbitrariness that
I can not comprehend.

I've spoken to a colleague who also runs HP servers and he experienced
apparently the exact same issue. The difference is that he decided that
10.04 is simply not working for them and that they'll check back in six
months. Didn't even start investigating anything. So please, Jeremy or
anybody, tell us what we can do to help debug this issue while we still
have the possibility to do so.

Sorry if I sound desperate. I somewhat am.

-- 
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot

[Andreas Ntaflos]

Charles, thanks for the reply. I do not use dist-upgrade for regular
package upgrades. However there should not be any difference between
dist-upgrade (full-upgrade) and safe-upgrade in this case. The kernel
package gets updated either way.

So you don't seem to see any problems even after a few consecutive
reboots. I guess that's good to know (good for you!) but since nothing
has changed, package-wise, in the last month-and-a-half I am not sure
what to make of it.

Jeremy: Fix Released? Is this an error or is there really a solution to
this problem? Where can I learn more about it?

-- 
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot

[Andreas Ntaflos]

I just want to add that I unfortunately have not been able to test this
further (not even using -generic instead of -server kernels) since the
machines in question needed to go into production. We went back to
Ubuntu 9.10 for that. If I'm lucky I can maybe get one or two of these
machines back in probably a few weeks to try again. Depends on how the
project goes.

In the meantime I see that 2.6.32-22 is still the current version of the
kernel image so I don't suppose anything changed here.

Charles, are you possibly able to reboot your machine a few times (maybe
five or more) in a row and see if the problems really don't reappear?
When I had been testing I found that the occasional reboot (a day or two
apart) generally did not trigger the hang but a few consecutive reboots
one immediately after the other would. This could of course be total
coincidence or BS but I really haven't been able to find any patterns
here. Grasping at straws, as it were.

Maybe of note: I also did pretty much exactly what you describe in
comment #18, more than a few times: a clean install and then aptitude
safe-upgrade (not dist-upgrade). Alas, a few reboots later the machine
would hang again.

Unfortunately I cannot really contribute much more at this point.

-- 
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot

[Andreas Ntaflos]

Interesting, I hadn't tested using non-server kernel images. Thanks for
the suggestion jgreenso, I'll be trying that on our problematic
machines.

-- 
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot

[Andreas Ntaflos]

I just went through that whole mess again and reinstalled one of the
machines. Unfortunately to no avail. Installation went speedy and fine,
aptitude update and aptitude safe-upgrade as well (this includes
installation of the new kernel image), rebooted three or four times and
now it hangs again. It always looks like this:
 and
. Both servers are
identical in configuration and equipment.

I am running out of ideas. This seems to be extremely indeterministic
and is becoming a royal pain in the ass. I really don't want to have to
go back to 9.10.

-- 
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 582145] [NEW] Virtual guests' console is unusably slow due to framebuffer usage

[Andreas Ntaflos]

Public bug reported:

This was also discussed in https://lists.ubuntu.com/archives/ubuntu-
server/2010-May/004172.html

The problem is that the console of a Ubuntu 10.04 (server) virtual
machine/guest becomes incredibly slow and really unusable as soon as it
starts scrolling. This is apparently due to the kernel switching on the
console framebuffer which does not play well with the VNC-based console
viewers of virt-manager. I have created a screencast to demonstrate,
please find it here: https://daff.pseudoterminal.org/misc/console-
slow.ogg

I have experienced this using KVM and virt-manager/virt-viewer on Ubuntu
10.04 and Ubuntu 9.10 hosts (using the server edition, FWIW). Apparently
it also happens with VirtualBox but I have not tested this myself. The
only solution for the time being seems to be to blacklist the vga16fb
module as suggested by Paul Nuffer:

$ echo "blacklist vga16fb" | sudo tee -a /etc/modprobe.d/blacklist

Merely adding "nomodeset" to the kernel boot options is not sufficient.

I don't even know exactly to which package this bug belongs let alone
what to do about it except force the kernel not to use a console
framebuffer. I know Plymouth needs the framebuffer to display splash
screens and whatnot but there should be a proper way to disable it when
running as a virtual machine. And since the splash screen is disabled
anyway when creating a server virtual machine there is really no use in
a framebuffer, especially if it slows everything down to a crawl. So
what to do?

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
Virtual guests' console is unusably slow due to framebuffer usage
https://bugs.launchpad.net/bugs/582145
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot

[Andreas Ntaflos]

Charles, this is exactly what I did in the first place. Clean install of
Ubuntu 10.04 Server, then upgrade to -22-server kernel. More often than
not the system would not come up correctly, as described above.

-- 
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 549751] Re: Hang after update/upgrade of 10.04-beta1-server-i386.iso

[Andreas Ntaflos]

Could this bug be related to bug 576001?

-- 
Hang after update/upgrade of 10.04-beta1-server-i386.iso
https://bugs.launchpad.net/bugs/549751
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 578332] Re: AppArmor blocks hotplugging of USB devices

[Andreas Ntaflos]

** Summary changed:

- AppArmor blocks hot-attaching of USB devices
+ AppArmor blocks hotplugging of USB devices

** Description changed:

  On Ubuntu 10.04 server, after applying the fixes to Libvirt's AppArmor
- profiles as discussed in bug 545795 the hot-attachment of USB devices is
- blocked/denied by AppArmor. Hot-attachment means: a KVM-based VM is
- running and a USB devices connected to the underlying host is to be
- attached/passed-through to the VM while it is running. This can be
- accomplished by using virt-manager:
+ profiles as discussed in bug 545795 the hotplugging of USB devices is
+ blocked/denied by AppArmor. Hotplugging means: a KVM-based VM is running
+ and a USB devices connected to the underlying host is to be attached
+ /passed-through to the VM while it is running. This can be accomplished
+ by using virt-manager:
  
  1. Open the "Details" window of the virtual machine in question
  2. Klick Add Hardware
  3. Select "Physical Host Device", Next
  4. Select "USB device" and choose the device to be attached (in our case a 
USB card reader), Next
  5. Finish
  
  The logfile for the machine in question immediately shows:
  
  usb_create: no bus specified, using "usb.0" for "usb-host"
  husb: open device 5.2
  /dev/bus/usb/005/002: Permission denied
  husb: open device 5.2
  /dev/bus/usb/005/002: Permission denied
  husb: open device 5.2
  /dev/bus/usb/005/002: Permission denied
  husb: open device 5.2
  
  /var/log/kern.log accordingly shows
  
  kernel: [79029.932635] type=1503 audit(1272985279.341:1009):
  operation="open" pid=23782 parent=1 profile="libvirt-959806d1-327a-cd14
  -6b3f-ddeee8a19d0e" requested_mask="rw::" denied_mask="rw::" fsuid=0
  ouid=0 name="/dev/bus/usb/005/002"
  
  This happens because AppArmor doesn't allow Libvirt access to
  /dev/bus/usb/**. Note that this works fine when the machine in question
  is shut down prior to attaching the USB device but that is exactly not
  the desired behaviour of hot-attaching devices.
  
  This can be fixed quite simply by allowing read-write access to
  /dev/bus/usb/**. I don't know if that needs to be added to the profile
  abstractions/libvirt-qemu or usr.lib.libvirt.virt-aa-helper. I believe
  it is the latter, but I am not sure.
  
  apparmor: 2.5-0ubuntu3
  libvirt-bin: 0.7.5-5ubuntu27
  Description:Ubuntu 10.04 LTS
  Release:10.04

-- 
AppArmor blocks hotplugging of USB devices
https://bugs.launchpad.net/bugs/578332
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 578332] [NEW] AppArmor blocks hot-attaching of USB devices

[Andreas Ntaflos]

Public bug reported:

On Ubuntu 10.04 server, after applying the fixes to Libvirt's AppArmor
profiles as discussed in bug 545795 the hot-attachment of USB devices is
blocked/denied by AppArmor. Hot-attachment means: a KVM-based VM is
running and a USB devices connected to the underlying host is to be
attached/passed-through to the VM while it is running. This can be
accomplished by using virt-manager:

1. Open the "Details" window of the virtual machine in question
2. Klick Add Hardware
3. Select "Physical Host Device", Next
4. Select "USB device" and choose the device to be attached (in our case a USB 
card reader), Next
5. Finish

The logfile for the machine in question immediately shows:

usb_create: no bus specified, using "usb.0" for "usb-host"
husb: open device 5.2
/dev/bus/usb/005/002: Permission denied
husb: open device 5.2
/dev/bus/usb/005/002: Permission denied
husb: open device 5.2
/dev/bus/usb/005/002: Permission denied
husb: open device 5.2

/var/log/kern.log accordingly shows

kernel: [79029.932635] type=1503 audit(1272985279.341:1009):
operation="open" pid=23782 parent=1 profile="libvirt-959806d1-327a-cd14
-6b3f-ddeee8a19d0e" requested_mask="rw::" denied_mask="rw::" fsuid=0
ouid=0 name="/dev/bus/usb/005/002"

This happens because AppArmor doesn't allow Libvirt access to
/dev/bus/usb/**. Note that this works fine when the machine in question
is shut down prior to attaching the USB device but that is exactly not
the desired behaviour of hot-attaching devices.

This can be fixed quite simply by allowing read-write access to
/dev/bus/usb/**. I don't know if that needs to be added to the profile
abstractions/libvirt-qemu or usr.lib.libvirt.virt-aa-helper. I believe
it is the latter, but I am not sure.

apparmor: 2.5-0ubuntu3
libvirt-bin: 0.7.5-5ubuntu27
Description:Ubuntu 10.04 LTS
Release:10.04

** Affects: libvirt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
AppArmor blocks hot-attaching of USB devices
https://bugs.launchpad.net/bugs/578332
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot

[Andreas Ntaflos]

This is becoming a bit scary. I have continued experimenting with the HP
DL380 machines I have here and even now even the even with the kernel
image 2.6.32-21-server makes the machine hang.

I can still SSH into it and look at the process list, see attachment.
Does anything in there look suspicious? I notice that

/sbin/plymouthd --mode=boot --attach-to-session

is running, which does not run when the machine has booted completely.
We also don't run VirtualBox but the basic Libvirt/KVM setup to host
virtual machines. All machines have LVM configured and have their root
and swap partitions as logical volumes.

Some more background info: the machines are HP ProLiant DL380 G6
(apparently the most popular ProLiant machines by HP ever). All three
have Smart Array P410 RAID controllers running RAID1 on two disks. The
drivers for the controller are in the kernel, no need for any manual
compilation. Obviously there is no need for mdadm in this case. That
said, I don't think this bug has anything to do with RAID setups.

What else can we provide? I am afraid that if this problem isn't solved
soon we have to revert back to Ubuntu 9.10, which I would really like to
avoid. The improvements made in AppArmor and Libvirt in 10.04 are very
important for us, plus we would like to take advantage of the LTS.

I still have about a week to play with these machines, after that we
need to get them production ready. I hope this bug gets the attention it
needs. Please do tell if we can provide any more information.

** Attachment added: "Process list after SSHing into hanging server"
   http://launchpadlibrarian.net/48216618/ps-aux.txt

-- 
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot

[Andreas Ntaflos]

I don't think this was a fluke.

Reading the description and the symptoms this seems exactly what we have
been experiencing on three of our HP DL380 G6 servers. These three
server are identical (modulo disk capacity) and serve as our test beds
for Ubuntu Server 10.04 (freshly installed as of yesterday). After a
standard upgrade (using aptitude) to the new linux-
image-2.6.32-22-server package, which was the only package upgraded, the
system would almost always hang during the boot sequence after
displaying the messages about fsck/filesystem health:

fsck from util-linux-ng 2.17.2
fsck from util-linux-ng 2.17.2
/dev/mapper/TEST02-root: clean, 52298/2924544 files, 458703/11696128 blocks
/dev/cciss/c0d0p1: clean, 205/124496 files, 32770/248832 blocks

After that it just hangs. We can reboot the server by means of ctrl-alt-
delete as well as connect through SSH, interestingly. No getty processes
are spawned, so no console login. Also interestingly this doesn't happen
on a HL DL120 G5, which has an almost completely different hardware
configuration. Virtual machines (KVM-based, using the -virtual flavour)
also don't seem affected by this.

Reverting back to 2.6.32-21-server (aptitude remove linux-
image-2.6.32-22-server) seems to fix the problem. I am pretty certain
that the problem lies with the -22-server package as I have tested and
reproduced this on three identical servers, as stated above.

How can I help debug this further? We still have about one weeks to run
experiments and tests on these servers so I'll gladly help where I can.

-- 
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 545795] Re: apparmor driver blocks access to hostdev and pcidev devices

[Andreas Ntaflos]

Oh and it seems that disconnecting/detaching an USB device from the
running VM doesn't work at all? virt-manager complains:

Device could not be removed from the running machine.
This change will take effect after the next VM reboot

But this has probably nothing to do with AppArmor and may just be a
shortcoming of Libvirt? Just pointing it out here since it seems to fit.

-- 
apparmor driver blocks access to hostdev and pcidev devices
https://bugs.launchpad.net/bugs/545795
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 545795] Re: apparmor driver blocks access to hostdev and pcidev devices

[Andreas Ntaflos]

Jamie, yes this fixes it. thank you!

I notice however some redundancies between abstractions/libvirt-qemu and
usr.lib.libvirt.virt-aa-helper? At least the line "/sys/bus/usb/devices/
r," appears in both, don't know if that matters any, though. So that's
good :)

But now I have discovered something else. When booting a VM that has a
USB device included in its XML definition (like here:
https://daff.pseudoterminal.org/files/vm-usb.txt) now thanks to this fix
works fine. *However* trying to attach a USB device while the VM is
running (using virt-manager in my case) results in these messages in
/var/log/libvirt/qemu/vm.log:

usb_create: no bus specified, using "usb.0" for "usb-host"
husb: open device 5.2
/dev/bus/usb/005/002: Permission denied
husb: open device 5.2
/dev/bus/usb/005/002: Permission denied
husb: open device 5.2

And in /var/log/kern.log:

May  4 17:01:19 TESTHOST kernel: [79029.932635] type=1503
audit(1272985279.341:1009):  operation="open" pid=23782 parent=1 profile
="libvirt-959806d1-327a-cd14-6b3f-ddeee8a19d0e" requested_mask="rw::"
denied_mask="rw::" fsuid=0 ouid=0 name="/dev/bus/usb/005/002"

So it seems that access to "/dev/bus/usb/**" is needed as well?

-- 
apparmor driver blocks access to hostdev and pcidev devices
https://bugs.launchpad.net/bugs/545795
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 545795] Re: apparmor driver blocks access to hostdev and pcidev devices

[Andreas Ntaflos]

Looks like I found it. The VM in my case is trying to access

/sys/devices/pci:00/:00:1e.0/:01:04.4/usb6/devnum

but the abstractions/libvirt-qemu profile only allows

  /sys/bus/usb/devices/ r,
  /sys/devices/*/*/usb[0-9]*/** r,

when it should (also) allow

  /sys/devices/*/*/*/usb[0-9]*/** r,

With this line added the guest boots fine and immediately gets access to
the USB device.

I have attached a patch for this one-line fix, hope it helps.

** Patch added: "One-line fix for hostdev access to USB devices"
   http://launchpadlibrarian.net/47796844/libvirt-qemu.patch

-- 
apparmor driver blocks access to hostdev and pcidev devices
https://bugs.launchpad.net/bugs/545795
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 545795] Re: apparmor driver blocks access to hostdev and pcidev devices

[Andreas Ntaflos]

Interestingly, or perhaps not, merely running /etc/init.d/apparmor stop
isn't enough. I stop AppArmor, restart Libvirt and then start my VMs.
However upon starting a VM an AppArmor profile still gets loaded and
thus AppArmor denies access to the USB device I want to pass through. I
have to run /etc/init.d/apparmor stop again after the VM has been
started. Then access to the USB device is allowed.

Looks weird to me but I haven't yet fully understood how and when
AppArmor profiles are loaded. But I don't understand why it would deny
access to a directory structure that is explicitly permitted in the
profile:

May  4 15:56:27 TESTHOST kernel: [75138.174346] type=1503
audit(1272981387.661:879):  operation="open" pid=8053 parent=1 profile
="libvirt-959806d1-327a-cd14-6b3f-ddeee8a19d0e" requested_mask="r::"
denied_mask="r::" fsuid=0 ouid=0
name="/sys/devices/pci:00/:00:1e.0/:01:04.4/usb6/devnum"

Unfortunately this is quite the blocker for me.

-- 
apparmor driver blocks access to hostdev and pcidev devices
https://bugs.launchpad.net/bugs/545795
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 545795] Re: apparmor driver blocks access to hostdev and pcidev devices

[Andreas Ntaflos]

I'm sorry to post to this bug that has a status of "Fix released" but I
am not sure it is really fixed. I have a situation similar too the
original poster's concerning a USB card reader that won't make it past
AppArmor it seems. Using libvirt-bin 0.7.5-5ubuntu27.

Situation: one of our servers was upgraded from Ubuntu 9.10 to 10.04
today. The server runs a few Ubuntu 9.10 VMs, nothing fancy or out of
the ordinary. These VMs were defined and installed a few weeks ago,
prior to the release of and update to Ubuntu 10.04 (if that matters at
all).

We've had problems with AppArmor and Libvirt/KVM before so we disabled
AppArmor and pass-through of the USB card readers worked fine this way.
This situation was not ideal from a security point-of-view but since the
host and guests are strictly for internal test and development purposes
we went with it. Now I see that a lot has happened with regards to
AppArmor, USB and PCI pass-through and Libvirt, so tried again enabling
AppArmor. Alas, when starting a VM dmesg and /var/log/kern.log show
these entries, repeating every second it seems:

May  3 19:44:18 TESTHOST kernel: [ 2407.509182] type=1503
audit(1272908658.618:785):  operation="open" pid=1532 parent=1 profile
="libvirt-959806d1-327a-cd14-6b3f-ddeee8a19d0e" requested_mask="r::"
denied_mask="r::" fsuid=0 ouid=0
name="/sys/devices/pci:00/:00:1e.0/:01:04.4/usb6/devnum"

The guest of course does not get to see anything of the USB device in
question. Please find the XML definition of the guest in question here:
https://daff.pseudoterminal.org/files/vm-usb.txt

After disabling AppArmor (/etc/init.d/apparmor stop) the USB device is
again visible in the guest.

Why would this happen? The file /etc/apparmor.d/usr.lib.libvirt.virt-aa-
helper explicitly states that access to /sys/devices/** should be
allowed. Am I missing anything? I can experiment and run tests on this
server for the next week or so, so please tell me if I can help
debugging anything.

-- 
apparmor driver blocks access to hostdev and pcidev devices
https://bugs.launchpad.net/bugs/545795
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 515525] Re: aptitude assert failure: *** glibc detected *** aptitude: double free or corruption (!prev): 0x08f9d658 ***

[Andreas Ntaflos]

Can also confirm the problem still exists and that changing terminal
size "fixed" it.

I only used the commandline interface of aptitude, i.e. the non-ncurses
one. I am somewhat baffled, how can the terminal size crash a program?
Never heard of that before :)

-- 
aptitude assert failure: *** glibc detected *** aptitude: double free or 
corruption (!prev): 0x08f9d658 ***
https://bugs.launchpad.net/bugs/515525
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 517067] Re: Using virtio for block devices makes disks and partitions disappear in KVM/QEMU (using vmbuilder and libvirt)

[Andreas Ntaflos]

You are right of course, /etc/fstab on the guest contains "/dev/sdXY"
entries. These get generated by
/usr/share/pyshared/VMBuilder/plugins/ubuntu/feisty.py as you mentioned.
After changing all "/dev/sdXY" to "/dev/vdXY" I can indeed boot happily
:)

What threw me off was that QEMU did not (and does not) see these virtio-
based drives when booting (see screenshots) and that changing the target
device name in the domain definition (
to  and vice versa) does nothing. I
suppose this has to do with the snippet of documentation I quoted
previously and probably with the fact that the virtio driver is
paravirtualized so QEMU doesn't do any of the emulation it would do with
IDE- or SCSI-based buses. Should have thought of that earlier.

So creating guests in the manner I described in my original post using
vmbuilder works after applying your one-line fix to
/usr/share/pyshared/VMBuilder/plugins/ubuntu/feisty.py.

I am not sure where this bug lies since I am just getting to know the
more advanced aspects of libvirt but I suppose vmbuider is to "blame".
That's understandable given that it is still somewhat young and cannot
consider all possible combinations and varieties of libvirt options. Too
bad virt-install is mostly useless for quickly creating and deploying
guests for testing purposes.

I like your solution b.) but doesn't that add yet another level of
indirection and complicates guest setup even more?

-- 
Using virtio for block devices makes disks and partitions disappear in KVM/QEMU 
(using vmbuilder and libvirt)
https://bugs.launchpad.net/bugs/517067
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 303882] Re: python-vm-builder --raw doesn't set size correctly

[Andreas Ntaflos]

Would also like to see this fixed for karmic. Using python-vmbuilder
0.11.3-0ubuntu1 and the same error occurs when trying to use a 10G LVM
volume as a --raw device. I assume this is the same bug.

sudo vmbuilder kvm ubuntu --debug --verbose -m 2048 --raw=/dev/mapper/vg
--storage-lv--chat_root --rootsize=8G --swapsize=2G --suite=karmic ...

Traceback (most recent call last):
  File "/usr/bin/vmbuilder", line 29, in 
VMBuilder.run()
  File "/usr/lib/python2.6/dist-packages/VMBuilder/__init__.py", line 65, in run
frontend.run()
  File "/usr/lib/python2.6/dist-packages/VMBuilder/plugins/cli/__init__.py", 
line 66, in run
self.set_disk_layout(vm)
  File "/usr/lib/python2.6/dist-packages/VMBuilder/plugins/cli/__init__.py", 
line 105, in set_disk_layout
disk.add_part(offset, vm.swapsize, 'swap', 'swap')
  File "/usr/lib/python2.6/dist-packages/VMBuilder/disk.py", line 189, in 
add_part
raise Exception('Partition is out of bounds. start=%d, end=%d, disksize=%d' 
% (begin,end,self.size))
Exception: Partition is out of bounds. start=8192, end=10239, disksize=5120

-- 
python-vm-builder --raw doesn't set size correctly
https://bugs.launchpad.net/bugs/303882
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 517067] Re: Using virtio for block devices makes disks and partitions disappear in KVM/QEMU (using vmbuilder and libvirt)

[Andreas Ntaflos]

Thanks for the comment, but how do you figure? I did not change anything
after the fact, I modified the template used for installation and setup
of the guest domain.

First, it seems to depend on the bus type whether the virtual disks are
at all visible to QEMU, as can be seen from the screenshots. At that
point logical device names are of no consequence, yet, because the
kernel isn't even booted.

Second, it does not matter whether the disks are called "vda" or "hda"
(the default) in the libvirt domain definition. From the documentation:
"The dev attribute indicates the "logical" device name. The actual
device name specified is not guaranteed to map to the device name in the
guest OS. Treat it as a device ordering hint." This is further supported
by the fact that upon switching the bus type to "ide" the disks are
visible both to QEMU and to the booted guest Linux kernel but the
logical device name in the domain definition is still "vda"-based.

Third, the logical device name is defined and set early during
installation/setup of the guest since it looks at the modified template
in /etc/vmbuilder/libvirt. So the installation procedure is aware that
disks are named "vda" in the definition and takes that into account (or
should take that into account). It does not matter whether it is "hda"
oder "vda" there (I tried both, multiple times), /etc/fstab will always
have "/dev/sdX*" set.

So I don't think that is the problem here, but I will try again. Thanks
for the comment, again!

-- 
Using virtio for block devices makes disks and partitions disappear in KVM/QEMU 
(using vmbuilder and libvirt)
https://bugs.launchpad.net/bugs/517067
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 517067] Re: Using virtio for block devices makes disks and partitions disappear in KVM/QEMU (using vmbuilder and libvirt)

[Andreas Ntaflos]

** Attachment added: "Domain definition for guest "foo", using virtio for block 
devices"
   http://launchpadlibrarian.net/38748978/foo.xml

-- 
Using virtio for block devices makes disks and partitions disappear in KVM/QEMU 
(using vmbuilder and libvirt)
https://bugs.launchpad.net/bugs/517067
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 517067] [NEW] Using virtio for block devices makes disks and partitions disappear in KVM/QEMU (using vmbuilder and libvirt)

[Andreas Ntaflos]

Public bug reported:

Binary package hint: libvirt-bin

I can reproduce that trying to use bus='virtio' for virtual disks in the
definition of a libvirt domain makes virtual disks thus defined
disappear in the eyes of KVM/QEMU. This leads to error messages like the
following when booting, as well as disappearance of all partitions on
that virtual disk, except for the root partition (that means especially
that no swap space will be enabled):

One or more of the mounts listed in /etc/fstab cannot yet be mounted:
(ESC for recovery shell)
swap: waiting for /dev/sda2
/opt: waiting for /dev/sda3

A screenshot is available here:
https://daff.pseudoterminal.org/misc/mountfailed.png

It also appears, just after starting the guest, that QEMU doesn't even
recognize that there are hard disk drives present, it only sees the DVD
drive. See the following screenshots for comparison.

bus='ide' in virtual disk domain definition: 
https://daff.pseudoterminal.org/misc/bus_ide.png
bus='virtio' in virtual disk domain definition: 
https://daff.pseudoterminal.org/misc/bus_virtio.png

The result is that only the root partition, probably because of
initramfs/initrd and GRUB magic, will be available to the guest when
using virtio, and only when no partitions other than a swap partition
have been defined during setup or installation of the guest. When only a
swap partition is present the boot process succeeds but still complains
that it is waiting for the swap partition to become available. When
there are any other partitions the boot process just hangs with the
error message described above.

Background: I like to take advantage of the paravirtualized IO drivers
offered for KVM-based guests. Using "virtio" as bus for block devices or
model type for network interfaces in the right places in a libvirt
domain definition enables those drivers. To facilitate and automate this
when creating guests I edited the libvirt template for vmbuilder to
automatically use virtio. Notice the target line:

#for $disk in $disks

  
  

#end for

Now for creating a guest using vmbuilder, as per the Ubuntu Server
Guide:

# vmbuilder kvm ubuntu --dest=/storage/vms/foo -m 2048 --rootsize=4000
--optsize=4000 --hostname=foo --suite=karmic --bridge=br0 --overwrite
--libvirt=qemu:///system --flavour=virtual --arch=amd64
--mirror=http://host:/ubuntu

Here a root and an /opt partition are defined, both 4GB in size. Swap is
defined automatically and defaults to 1GB. This works fine and results
in the attached foo.xml libvirt domain definition. In particular the
disk definition looks like this (again, notice the target line):


  
  


This is what the libvirt and KVM documentation pages suggest. After
starting this domain the results are as described above, i.e. either a
hanging boot process or a missing swap partition.

When changing the target bus definition to bus='ide' everything works
correctly. The domain boots as expected and contains all partitions
defined during setup. This has been completely reproducible for me and I
can switch between a working guest domain and a non-working by changing
bus='virtio' to bus='ide' in the domain definition.

This is on a Ubuntu Server Edition installation. I have no idea if this
is a libvirt problem or a problem with KVM or QEMU or something else
entirely. More information follows and please also see the attached
files. If there is anything else I can provide please tell me.

lsb_release -rd:
Description:Ubuntu 9.10
Release:9.10

apt-cache policy libvirt-bin
libvirt-bin:
  Installed: 0.7.0-1ubuntu13.1
  Candidate: 0.7.0-1ubuntu13.1
  Version table:
 *** 0.7.0-1ubuntu13.1 0
500 http://at.archive.ubuntu.com karmic-updates/main Packages
100 /var/lib/dpkg/status
 0.7.0-1ubuntu13 0
500 http://at.archive.ubuntu.com karmic/main Packages

uname -a:
Linux dhcp155 2.6.31-17-server #54-Ubuntu SMP Thu Dec 10 18:06:56 UTC 2009 
x86_64 GNU/Linux

** Affects: libvirt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Using virtio for block devices makes disks and partitions disappear in KVM/QEMU 
(using vmbuilder and libvirt)
https://bugs.launchpad.net/bugs/517067
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 368962] Re: [Jaunty] Can't reboot kvm virtual machines using virsh

[Andreas Ntaflos]

This bug doesn't seem to have gotten much attention since July last year
but I can report that the issue still exists on Karmic using libvirt-bin
0.7.0-1ubuntu13.1:

$ virsh reboot foo1
Connecting to uri: qemu:///system
error: Failed to reboot domain foo1
error: this function is not supported by the hypervisor: virDomainReboot

The stack trace printed by virt-manager says the same:

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 523, in 
reboot_domain
vm.reboot()
  File "/usr/share/virt-manager/virtManager/domain.py", line 554, in reboot
self.vm.reboot(0)
  File "/usr/lib/python2.6/dist-packages/libvirt.py", line 398, in reboot
if ret == -1: raise libvirtError ('virDomainReboot() failed', dom=self)
libvirtError: this function is not supported by the hypervisor: virDomainReboot

Anything we users can or should do here?

-- 
[Jaunty] Can't reboot kvm virtual machines using virsh
https://bugs.launchpad.net/bugs/368962
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 153768] Re: External SATA (eSATA) removable disk detected as system-internal

[Andreas Ntaflos]

** Description changed:

-- 
External SATA (eSATA) removable disk detected as system-internal
https://bugs.launchpad.net/bugs/153768
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 86325] Re: alsa mixer Multi Track Internal Clock stuck on IEC958 and operation error

[Andreas Ntaflos]

I just ran into this bug as well. Using Kubuntu 9.04 (KDE 4.2.4) and an
Maudio Delta Audiophile 2496. The funny thing is that this is a quite
fresh install and everything worked fine until a day ago when I
installed, then uninstalled some gstreamer-related packages
(libgstreamer0.10-dev, gstreamer0.10-alsa, ...). Then suddenly the
soundcard was not recognized at all anymore. I had to power down the
machine, remove the card, power it up again, then repeat with the card
reinserted. But now the internal clock rate is stuck at ICE958 (the
S/PDIF) which I don't use so the card has no valid clock rate set. This
results in no output at all from the soundcard and applications that
play sound freeze one way or the other.

Even funnier is that I just rebooted and had a look at alsamixer on a
virtual console, i.e. *before* logging into KDE. There it was no problem
to set the internal clock rate to something other than ICE958. I set it
to 96000 and tested with aplay /usr/share/sounds/k3b_success.wav which
worked fine.

*Then* logging into KDE I found that the problematic control was stuck
again and there was no way to set it to anything else. I have no idea if
this is KDE-specific (Phonon?) or a general problem with desktop
environments that provide some level of control over the sound
hardware/API. But it definitely depends on whether KDE is running or
not: logging out and checking alsamixer on a virtual console I was able
to set the internal clock rate again.

I am not sure how to debug this properly or what part of KDE is
responsible here.

-- 
alsa mixer Multi Track Internal Clock stuck on IEC958 and operation error
https://bugs.launchpad.net/bugs/86325
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 280811] Re: thinkpad bluetooth hotkey fn+F5 regression

[Andreas Ntaflos]

You know, it is really no problem to simply create the necessary file in
/etc/modprobe.d and put the options line in there like Nick suggested. I
find this workaround cleaner than letting the bluetooth module load and
then explicitly unload it later.

The following will create the file /etc/modprobe.d/thinkpad-acpi.conf
(the .conf suffix is common in /etc/modprobe.d), put the options line in
it and redirect the output of the tee command to /dev/null:

$ echo "options thinkpad_acpi experimental=1 hotkey=enable,0x8f
bluetooth=disable" | sudo tee /etc/modprobe.d/thinkpad-acpi.conf >
/dev/null

-- 
thinkpad bluetooth hotkey fn+F5 regression
https://bugs.launchpad.net/bugs/280811
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 332407] Re: network manager broken

[Andreas Ntaflos]

I seem to be able to confirm that problem with the latest Alpha (6) of
Kubuntu. Knetworkmanager shows the network in question but connecting to
it simply doesn't work. The Gnome applet nm-applet on the other hand
works just fine. Hope this gets fixed in time.

-- 
network manager broken
https://bugs.launchpad.net/bugs/332407
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to plasma-widget-network-manager in ubuntu.

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs