Once again Ubuntu has introduced a regression in a release... More and
more reason to switch to fedora or Suse. Very disappointed, not
instilling any confidence in being able to stick with Ubuntu.
--
No option to log in remotely via XDMCP
https://bugs.launchpad.net/bugs/408417
You received this
I am very much disappointed by the decision re: amarok1.4 and Amarok 2.
There is one really glaring issue that I find amazing. The lack of a
resonable media device manager with out Amarok1.4.
It seems to be the flavour of the month and a very Microsoft attitude to
release incomplete software in
An other issue that may be related to this issue is when closing a
remote XDMCP session the vt switches in the same fashion as the
/etc.init/kdm stop issue.
The local session does not end its just the vt switch that is a problem.
If you switch back to vt7 the local session is still there and
*** This bug is a duplicate of bug 164231 ***
https://bugs.launchpad.net/bugs/164231
--
Kernel Oops with nfs4 mount
https://bugs.launchpad.net/bugs/148600
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
This is no longer and issue.
I found that it was some extensions installed in the profile on the nfs
share.. After uninstalling all the extensions and thems then re-
installing the updated ones the problem was solved.
--
[GUTSY] Thunderbird crashes when profile is resident on nfs mount.
This is a known bug in alsa.
I have found a workaround by setting aliases for snd-card-0 snd-usb-
audio and alias snd-card-1 snd-hda-intel in the
/etc/modprobe.d/aliases
Thanks anyway guys. Keep yo the good work.
--
[GUTSY] snd-usb-audio drive fails for Microsoft LifeChat LX-3000
Update:
Booted to 2.6.20-16-generic kernel and found that thunderbird behaves normally
when using the NFS resident profile.
My Guess is that the new kernel has an nfs issue.
uname -a
Linux memme 2.6.20-16-generic #2 SMP Sun Sep 23 18:31:23 UTC 2007 x86_64
GNU/Linux
--
[GUTSY] Thunderbird
Public bug reported:
After upgrading to kernel 2.6.22-14.46 the snd-usb-audio driver reports
the following error when probing my Microsoft LifeChat LX-3000 USB
headset. Thus the headset does not work.
[ 53.422273] snd-usb-audio: probe of 1-1:1.0 failed with error -5
dmesg log attached.
** Attachment added: dmesg log for 2.6.22-14.46 boot.
http://launchpadlibrarian.net/10051490/dmesg.0
--
[GUTSY] snd-usb-audio drive fails for Microsoft LifeChat LX-3000
https://bugs.launchpad.net/bugs/153481
You received this bug notification because you are a member of Ubuntu
Bugs, which is
After some messing around I found that an issue related to the network
configuration was not starting the eth0 interface and thus causing the
LDAP problem. It still does not bode well as now I need to reconfigure
both the network and LDAP so as to prevent the issue from occurring when
my laptop is
I have the same issue. It is related to LDAP. I run an ldap server and
have configured the system to use LDAP. If you disable ldap in the
nsswitch.conf the laptop boot fine. If it is enabled the klogd startup
srcipt seems to pause for a long time. My guess is when the script
changes the ownership
Same sort of issue with my headset. I am using a Microsoft LifeChat
LX-3000 headset with volume controls on the headset lead. After quite a
few hours and re-configuring of the ALSA drivers I was able to get the
volume controls to work through KMix to control the volume on the
headset. But after
Public bug reported:
Binary package hint: mozilla-thunderbird
I have one of my thunderbird profiles on an nfs mounted file system. I
do this to share the profile with a number of machines. When I go to
read an email while using the profile on the nfs share it crashes with a
segmentation fault.
I am experiencing the same. But I am also experiencing random lock ups.
Usually after a couple of days running. Powering down seems to be the
only fix it as the system will not unlock (kscreensaver) and login seems
to hang on the vts. I have been able to prevent the errors showing up by
putting
Public bug reported:
Binary package hint: network-manager
After Setting an interface to not activate at boot time in the network
configuration dialog and verifying that the auto flag is not set on
the interface in the /etc/network/interfaces file, NetworkManager will
still try to start the
Public bug reported:
Binary package hint: network-manager
Network manager will configure an ethernet interface even when it has no
cable connected. This causes issues with certain X based applications
using other network interfaces on the system. EG:
If eth0 is disconnected and configured and
I ran the patch you suggested Joseph.. only issue is the pid that ends
up in the pid file is always one out from the actual idmapd pid.
I am not sure why its doing it.
I added this just under the --exec line to get the real pid. just a temp
solution till a proper patch shows.
ps -ef | grep
17 matches
Mail list logo
