Yeah, this has bitten me too. GRUB2 is looking for md devices to use the
new style /dev/md/# device naming, rather than the old /dev/md# style.
As a short-term fix, simply creating the /dev/md directory, and creating
symlinks to the actual device nodes seems to work.
Example:
mkdir /dev/md
ln -s
In response to comment #26 by Michael, keeping sssd 1.5.x out of Natty
seems rather silly, as sssd 1.2.x never, ever worked with Natty in the
first place. sssd 1.2.x might have compiled, and been available for
install, but it was never functional. The restrictions on version
upgrades in SRUs are
Public bug reported:
This is occurring under natty with kernel 2.6.38-8-generic on x86_64.
Under normal light use the system performs fine. However, when
accessing a NFS share fairly heavily (attempting to rebuild my Picasa
DB), the system regularly crashes with the trace below.
Apr 24 10:02:43
** Attachment added: Output of lspci -vnvn
https://bugs.launchpad.net/bugs/769927/+attachment/2086548/+files/lspci.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/769927
Title:
Kernel Oops :
Also happens under 2.6.38-9 from kernel-ppa/pre-proposed
Linux mourneblade.mossholder.com 2.6.38-9-generic
#43~pre201104230901-Ubuntu SMP Sat Apr 23 09:16:31 UTC 2011 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Is there anything else I can do to help move this to towards resolution?
Thanks,
--Matt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/746981
Title:
sssd fails to find
Stephen,
I'm pretty sure 300 seconds is more than enough, because A) it worked
previously, and B) this is a home setup.. I have less that 30 total groups
and users in LDAP.
I did try changing the setting to 600 seconds, and the results are the
same. I also tried setting
Getting closer! I now end up with a /usr/lib/x86_64-linux-gnu/sssd/
directory, full of links like libsss_{ipa,krb5,ldap,proxy,simple}.so, but
the files they actually point to are missing.
Thanks!
--Matt
On Sat, Apr 9, 2011 at 2:20 AM, Fabrice Coutadeur coutade...@gmail.comwrote:
Good
More progress! We seem to be past the stuff that has to do with missing
files now. However, it looks like the patches didn't quite do the trick.
Something is causing the LDAP entries not to get returned. In fact, it
doesn't even seem to try and process anything past the first user found.
Here are
Fabrice,
Thanks for the help! It looks like some of the files are missing from the
packages... in particular the libsss_*.so files that provide the backends
(like libsss_ldap.so and libsss_krb5.so).
Here is a sample log entry:
(Fri Apr 8 16:31:54 2011) [sssd] [monitor_service_init] (3):
Public bug reported:
Binary package hint: sssd
1) Natty Beta 1
2) sssd 1.2.1-4.1ubuntu3
3) sssd works with group memberships in LDAP (worked in maverick, as long as
you worked around the VERY similar bug #658909)
4) sssd exits, complaining that memberof.so cannot be located.
This is NOT the
Another item of note... it doesn't appear to be Network Manager putting
the hostname on the ::1 line. It must be being done by something else...
the installer?
## This is /etc/hosts is the case that causes rpc.svcgssd to fail.
192.168.0.1 mourneblade.mossholder.com mourneblade #
Public bug reported:
Binary package hint: autofs5
Description:Ubuntu 10.10
autofs: Installed: 5.0.5-0ubuntu21
When using autofs5 to mount a directory exported as nfs4 from localhost,
autofs5 attempts to perform a --bind mount, like it would with nfs2 or
nfs3. This does not work
Public bug reported:
Binary package hint: autofs5
Description:Ubuntu 10.10
autofs: Installed: 5.0.5-0ubuntu21
When using autofs5 to mount a directory exported as nfs4 from localhost,
autofs5 attempts to perform a --bind mount, like it would with nfs2 or
nfs3. This does not work
Public bug reported:
Description:Ubuntu 10.10
Release:10.10
nfs-kernel-server: Installed: 1:1.2.2-1ubuntu1
Network Manager creates an entry for localhost6.localdomain6 in
/etc/hosts like the following:
::1mourneblade.mossholder.com mourneblade
I can confirm the one line change in the link provided in comment #21
works.
--
cannot run gdesklets with python2.6
https://bugs.launchpad.net/bugs/344079
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This appears to happen when gnome-keyring-daemon doesn't start up
correctly. In my case, I am using krb5 authentication, and the pam-
gnome-keyring module doesn't startup the daemon properly. This might be
a major problem for enterprise users. In my case, it also impacts Ubuntu
One and Empathy, as
The version that is in Karmic (3.2.5-1ubuntu1) works correctly!
--
Ekiga doesn't recognize webcam with non-UTF chars
https://bugs.launchpad.net/bugs/345192
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: mythtv-status
r...@mythtv:~# mythtv-status -h mythtv.mossholder.com
Unable to find any value for drive_total_total while looking at Total Disk Space
Unable to find any value for drive_total_used while looking at Total Disk Space
Something is wrong
Oh, and this was found on Karmic Alpha 6.
--
mythtv-status script incorrectly attempts to report on storage using protocol
version 32 and 39
https://bugs.launchpad.net/bugs/437803
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
From a user experience standpoint, having xsplash and GDM be aware that
there are two screens is a good thing, in my opinion. The actual issue
is that the important information of the screen ( the throbber) is being
cut is two. A much better proposal would be to have the throbber
centered on one
Does this, by chance, also work with NFS or other network mounted home
directories? This might be a good fix for bug #23002...
--
login-screen has no user-pictures with encrypted home directories
https://bugs.launchpad.net/bugs/426724
You received this bug notification because you are a member
@Ruben - Sorry about that... I was considering the logo to be part of
the throbber. I agree, the logo shouldn't be split.
With regards to the other two options, they are certainly a way to get
things done, but would be sub-optimal from a user experience
perspective(IMHO).
--
New splash looks
All seems good. And by that, I mean all. With a clean rebuild,
everything is working fine. I believe my problems with Ekiga were
related to a bad NAT setting, so that can be discounted. I haven't
experienced any crashes, and echo tests, both locally and vs. EKiga.net
ware working as expected. No
So far, I have been unable to reproduce the crashes. I do have another
data point, however. It looks like the UTF-8 issue is present in the
audio device selection as well. The NX-6000 has a Mic, and it is
suffering from the same issues as the video did prior to the patch.
If I get a chance, I
toto2 is a winner! A few notes:
1) The first few times I ran it, it crashed with stack smashing errors when I
started an echo test. However, I haven't been able to replicate it since.
2) The first time I entered preferences, it gave two pango/utf8 errors, and
hung. I killed it, and restarted,
Here's -d 4 output for an unsuccessful echo test. I did finally manage
to get connected to Ekiga.net from here, once, and when I did, the echo
test was successful. Now if I could only get it to register again
** Attachment added: ekiga -d 4 output
I totally understand. I made the mistake of cutting and pasting the
patch from the browser, which converted it to UTF-8, instead of
downloading it.
This seems to work, although the first three times I ran it, I would end
up with a crash (dumped complaining of stack smashing), after that I
have
After reboot, no more complaints about stack smashing.
Here's the output. Video in all cases, just some mjpeg related messages,
that I would assume are normal...
M i c r o s o f t � L i f e C a m N X - 6 0 0 0
Return code: 0x207a360
libv4lconvert: Error decompressing JPEG: fill_nbits error:
I get local video in all cases. I can't reach ekiga.net from here, so I
will have to test between internal machines later today.
I also noticed that the camera now shows up twice in the video device
settings... once with the (R), and once without. I'm still getting some
pango complaints that may
OK, I've now gotten to the point where doing an echo test works
-sometimes-, to my local Asterisk server. I have no idea why it
sometimes works, and sometimes doesn't. I've looked at the debugging
info from Asterisk, and the video handshaking is occurring, h.261 is
selected as a codec.
Local
*** This bug is a duplicate of bug 345192 ***
https://bugs.launchpad.net/bugs/345192
** This bug has been marked a duplicate of bug 345192
Ekiga doesn't recognize webcam with non-UTF chars
--
Ekiga does not appear to support MJPEG webcams
https://bugs.launchpad.net/bugs/360639
You
I just tested it (same camera, same issues), and while the lovely (R)
symbol is displayed correctly, it doesn't resolve the underlying issue.
I suspect the issue is root in the fact that the NX-6000 pumps out a
MJPEG stream, rather than MPEG or raw. Could this be the case?
--Matt
--
Ekiga
Oh, another note, Ekiga doesn't seem to pick up the resolutions
available on the webcam. I get the following choices:
176x144
352x288
704x576
320x240
640x480
Cheese (which works fine in Jaunty, might have worked in Intrepid, and
definitely didn't before that) has these additional resolutions
Oops... silly me for not exiting the app before posting. The patched
version core dumps on exit. The backtrace/memory map is attached.
** Attachment added: Backtrace/memory map
http://launchpadlibrarian.net/25352047/ekiga.coredump.txt
--
Ekiga doesn't recognize webcam with non-UTF chars
Public bug reported:
Binary package hint: ekiga
The Microsoft NX-6000 webcam only supports MJPEG output, as opposed to
the more popular YUV. While Ekiga can see the camera, it is not capable
of using it.
Here is the associated error message:
=
Error while accessing video device Microsoft®
Here's the -d 4 output. (IPs stripped to protect the innocent :)
--Matt
** Attachment added: ekiga -d 4
http://launchpadlibrarian.net/25352883/ekika.out
--
Ekiga doesn't recognize webcam with non-UTF chars
https://bugs.launchpad.net/bugs/345192
You received this bug notification because
Here's the stdout from the toto patch. I've attached a 'ekiga -d4' patch
s well.
=
77 105 99 114 111 115 111 102 116 -62 -82 32 76 105 102 101 67 97 109 32 78 88
45 54 48 48 48
M i c r o s o f t � � L i f e C a m N X - 6 0 0 0
Return code: (nil)
77 105 99 114 111 115 111 102 116 -62
Public bug reported:
Many corporate environments require the use of proxy servers for
accessing the internet. Additionally, services like apt-cacher-ng work
in a more transparent fashion when used as a proxy rather than rewriting
requests. vm-builder should support these configurations. By more
I can confirm this is still an issue in Intrepid.
#dpkg -l ca-certificates-java openjdk-6-jre
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
Public bug reported:
Binary package hint: tracker
Tracker supports using libexempi to parse XMP metadata. F-Spot uses XMP
data to store tags within images. Tracker should be capable of searching
image metadata placed in images by F-Spot.
Example: User Bob tags an image in F-Spot with the tag
Public bug reported:
Binary package hint: landscape-client
I noticed that update-motd was throwing some errors after I upgraded to
Intrepid Alpha 5. From the looks of things, it doesn't like one of the mounted
filesystems.
2008-09-12 19:41:35,863 ERRORDisk plugin
I just ran into this myself. In my case, the issue was mixing a xen 3.1
hypervisor with xen 3.2 utilities. Make sure you are booting off the
correct kernel in grub mine somehow ended up pointed at the 3.1
hypervisor as the default!
--
Premission denied when trying to init xend
Public bug reported:
Binary package hint: xen-tools
Gutsy's persistent network interface naming udev rules are causing Xen
instances to have a new network interface name each time a DomU is
booted. This is because Xen is dynamically generating a MAC for the
DomU, and the
I would beg to differ with the statement that this does not meet the SRU
criteria. In particular, this seems to be a Bugs which represent severe
regressions from the previous release of Ubuntu. Previous versions
supported these configurations, while with gutsy the follow is the case:
* the
Brian,
I checked the kernel source for Gutsy, and the fix seems to be in
place there. So this issue would appear to be limited to just Feisty. The
Changelogs for 20.6.20-16 don't seem to indicate that the this issue has been
addressed, so I am assuming that the issue is still
I've uncovered some more on this...
http://lists.debian.org/debian-kernel/2007/09/msg00415.html
It appears to be a bug in initramfs. Patch written by the
LinuxFromScratch crew here:
http://wiki.linuxfromscratch.org/lfs/attachment/ticket/2023/initramfs-
add-ide-options.patch
--Matt
--
Public bug reported:
Binary package hint: linux-image
Passing in the ide=nodma boot parameter appears to have no effect in
Gutsy.
Confirmed under Sparc and X86.
See this thread:
http://ubuntuforums.org/showthread.php?p=3752465
For me, at least, this is an installation show stopper.
I am
I'll ditto on this one. I have a 4 port HPT card, and the standard 2
onboard IDE interfaces, and all I can see are the internals and 2 of the
ports on the HPT card. This is particularly problematic in the server
kernel, where you would expect to encounter a larger proportion of users
with lots of
Jeff,
Not my script, all I did was add /usr/lib/xen to the echo statement... The
space might be my fault. I don't remember if I typed it in by hand, or cut and
pasted.
Thanks for the fix, though...
--Matt
--
doesn't manage local machine
https://bugs.launchpad.net/bugs/76500
You
I can confirm the initial report. I haven't tried the posted path.
--Matt
--
krb5-auth-dialog does not auto-renew renewable tickets
https://bugs.launchpad.net/bugs/104815
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Public bug reported:
It appears that the kernel used in Feisty has a bug (based on this LKML thread:
http://www.ussg.iu.edu/hypermail/linux/kernel/0702.3/1351.html), which
can cause some issues if you have a drive in your raid array go off to pasture.
In particular, if you try and run the array
I can confirm this as well. I have several domU's created with xen-
toolsunder feisty which work fine, but for whatever reason, xenman can't
manage the local system. I'm more than willing to provide information to
get this resolved. Just let me know what you need.
--Matt
--
doesn't
I've figured this out...
There are two issues:
1) Shipped xend-config.sxp from the xen-utils package does not enable
the xend-unix-xmlrpc-server
2) The shipped xenman.conf does not have an entry for localhost included
in it. Add the following entry enabled xenman to manage the local
system:
One more on this one... the wrapper in /usr/sbin/xenman is incorrectly
setting the xendir variable. It is picking up /usr/lib/xen-ioemu-3.0 as
xendir, when it is actually /usr/lib/xen. This, in tern, means that the
consoles don't work, as xenconsole can't be located.
Here is what the wrapper
...and now that I have sent that... I realize /proc/xen exists in the domUs as
well. Perhaps one of the other /proc entries?
--Matt
--
doesn't manage local machine
https://bugs.launchpad.net/bugs/76500
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
I come with answers
1. I referenced the unix socket as not being enabled, not the tcp
socket. So we're on the same page, it seems.
2. Ubuntu does not use the string xen anywhere in the
platform.release. For example, on feisty-xen, it is 2.6.19-4-server or
2.6.19-4-generic (for with
I'm not sure what you think your patch does that is different than
mine (I claim no credit for writing it, I just took what was in
upstream and applied it to 0.7.2). The only difference I am seeing is
the one set of {} around the action taken as a result of the first else
if (is_heimdal_entry)...
I don't think it is a dupe... 120514 relates to there not being a set of
scripts to build feisty with xen-tools. The bug that I am reporting
concerns the scripts working incorrectly based on /bin/sh not being BASH
anymore.
However, if you are saying that the solution to this bug is covered by
Public bug reported:
Binary package hint: xen-tools
When feisty changed /etc/sh away from being equivalent to /bin/bash, the
hooks in /usr/lib/xen-tools/edgy.d (and maybe others) broke.
Specifically, 30-disable-gettys started performing exactly the opposite
as expected on this line:
rm
Public bug reported:
When using Heimdal's hdb-ldap system to store the Kerberos DB in LDAP,
there is a situation where the kerberos credentials can become corrupted
if the target DN is both a sambaSAMAccount and a krb5Principal. The
patch below is a backport of what has been included in HEAD to
Looks like this is debian bug #372685, and unresolved there as welll
--
hdb-ldap is broken in 0.7.2 when used with samba-ldap
https://bugs.launchpad.net/bugs/120649
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
And here is the patch, as an attachment, if that helps.
** Attachment added: Fixes issues with hdb-ldap when krb5Principal is also a
sambaSAMAccount
http://launchpadlibrarian.net/8097853/hdb-ldap-enctypes-fix.dpatch
--
hdb-ldap is broken in 0.7.2 when used with samba-ldap
I think I have narrowed this down. It isn't actually a heimdal problem,
it is a libldap problem. In libldap2 (used by slapd), the ldapi socket
is defined as /var/run/slapd/ldapi , but in lipldap, used by heimdal ,
it is defined as /var/run/ldapi . The mismatch in the defaults is
causing the two
Here's the proof, although I had the package names a little off... it is
a difference between libldap-2.3-0 and libldap2
[EMAIL PROTECTED]:~$ strings /usr/lib/libldap_r.so.2 | grep var/run
/var/run/slapd/params_cache_rsa
/var/run/slapd/params_cache_dh
/var/run/ldapi
[EMAIL PROTECTED]:~$ strings
Confirmed on Treo 600
--
[feisty] etodo conduit times out when syncing with a palm device
https://bugs.launchpad.net/bugs/81170
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I can confirm this behavior under stock feisty-server
--
heimdal uses wrong path to ldapi-socket
https://bugs.launchpad.net/bugs/99795
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I think I know what is going on here. When you set the proxy settings in
your Gnome Preferences, it does two different things:
- Sets the /system/http_proxy gconf keys
- Sets the $http_proxy environment variable.
It appears to be the second of these that is causing the problem (at
On Thu, 2007-03-08 at 22:43 +, Chris Wagner wrote:
On looking over this report again, I think it may be another issue that
I see with my static IP connection. Matt, there is a little icon in the
lower-left corner of Evolution. Does this show that you are connected
or disconnected?
On
Here's what was in my paste buffer, as I unsuccessfully tried to avoid
top-posting in the above email :)
Shame on me for not marking this bug resolved. The issue went away in
one of the updates several weeks ago, and I never did the right thing.
I do have the issue with NetworkManager marking me
Public bug reported:
Binary package hint: faac
I have been processing long .wav and raw PCM files lately (on the order
of an hour or two). On many of these files, faac will end up sitting and
spinning, after processing an arbitrary portion of the file.
I have done the following to troubleshoot:
I had seen messages in the .xesssion-errors file that Evolution was
having problems connecting to network manager.Since I have restarted X,
I don't have the old .xsession-errors file to give the exact message.
At this point, it looks like the issue is NOT related to Network
Manager.
I have also
Public bug reported:
Binary package hint: evolution
Evolution seems to have developed an affinity for Network Manager.
Without Network Manager installed, I can usually send an email (via
SMTP) immediately after startup. However, a few minutes later, pressing
send/recieve, or composing a new
I should also mention that the system in question has a static IP
address, so Network Manager shouldn't be required.
--
[feisty] Evolution inconsistant at sending SMTP mail w/o Network Manager
installed
https://launchpad.net/bugs/76873
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Correction: After waiting longer, Evo failed with Network Manager
installed as well.
--
[feisty] Evolution inconsistant at sending SMTP mail w/o Network Manager
installed
https://launchpad.net/bugs/76873
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
*** This bug is a duplicate of bug 38203 ***
You need to put in a statement bind_policy soft in your
/etc/libnss_ldap.conf file. udev is starting before LDAP is available,
and when it tries too lookup the users and groups associated with the
/dev devices, it is attempting to hit the
Excuse my typo... I had meant to change that to common-*, and never did.
I have another datapoint for you as well. Reversing the order of the
statements in /etc/nsswitch.conf enables GDM to work correctly... i.e.
compat ldap rather than ldap compat.
Thanks for your time!
--
GDM does not
Public bug reported:
Unfortunately, I can't do much more than report this, since I am pretty
lost.
Here's the situation:
- Clean install of knot2
- All updates applied
- installed libnss-ldap and libpam-ldap
- configured /etc/nsswitch.conf, /etc/libnss-ldap.conf and /etc/pam_ldap.conf
- updated
Public bug reported:
The nscd package (created from the glibc sources) in edgy does not
create /var/run/nscd in the sysvinit scripts. This causes nscd to fail
on launch. Updating the init script to mkdir /var/run/nscd resolves the
issue.
** Affects: glibc (Ubuntu)
Importance: Untriaged
79 matches
Mail list logo
