Public bug reported:
The rdp connection support supposed to be installed with virtualbox-ext-
pack does not work. Logging into the rdp port with telnet shows the
message:
"RFB 003.008"
This indicates a RFB/VNC style display server rather than the RDP server
in the extension pack. This may be
Public bug reported:
Apparently the package appmenu-qt5 interferes with the ability to use
the keyboard shortcuts in the ipe drawing program, if ipe is compiled
with qt5.
Workarounds apparently include recompiling ipe to use qt4, or removing
the appmenu-qt5 from the system. I chose to remove
Public bug reported:
Binary package hint: kile
After installing kile on Intrepid (i386), the Kile Handbook will not launch
from the Help Menu. The error message is Could not launch KDE Helpcenter:
could not find service 'khelpcenter'. Starting the service khelpcenter from
the console does
OK, I found a different machine that doesn't use LVM, and was able to
complete an install, then set up nis. While I didn't set up a nis
login, I was able to use ypcat after a clean reboot, and a local login.
So apparently all is well.
This was using the daily build posted on 3/21. Daily torrents
Hm, well I tried. But I need to actually do an install in order to test
it. That is, I need to install, configure NIS, then boot to test.
But there is a rub. I can't install from the Live CD, because I use
LVM, which isn't supported. I have to use the alternate install, which
isn't
The machine with this problem is not a master in my home setup - the
master is a headless server/router running debian etch. So distributing
maps is not an issue, I just need to attach to the domain.
I have a workaround though - I simply added /etc/init.d/nis restart as
a line in /etc/rc.local.
OK, thanks. I am away from home at the moment, but will try this when I
get back home - I don't want to try rebooting remotely while this
problem exists.
Another thing - there are over 200 open bugs on network manager, and I
was unable to find one that was clearly linked to the issue you
Um, what about a work-around while I am waiting for the real fix? The
current state of this problem requires being at the console to manually
login as a non-nis user with sudo privileges, to rerun the nis startup
command, following any reboot.
--
nis daemon fails to attach to domain the first
OK. BTW, it is /usr/bin/nm-tool, not /usr/sbin/nm-tool.
Output of first run (during boot)
==
NetworkManager Tool
State: connected
- Device: eth0
NM Path: /org/freedesktop/NetworkManager/Devices/eth0
Public bug reported:
Binary package hint: nis
In my Gutsy install (upgraded from beta server install to RC-1) the nis
daemon fails to properly attach to the domain the first time it is run
(at boot). The console prints [failed] instead of [ok], and network
logins don't work (however local
Maybe I need to clarify that I did a fresh install. Currently I have no
files named /etc/iftab or /etc/udev/rules.d/70-persistent-net.rules.
The contents of /etc/network/interfaces:
==
# This file describes the network interfaces available on your system
# and how to activate them.
Initially I did a server install, so the problem was first observed with
the server kernel. Subsequently I installed (by a chroot method) the
generic kernel, and that is what I reported the bug against. But as I
mentioned in the initial bug report, the issue exits with both kernels,
at least
OK, after reading the description of 145382 I agree it is the same bug.
I must have misread the ls output yesterday; there is indeed a file
named 70-persistent-net.rules, and it does refer to eth1.
It is good to see it isn't actually a kernel or module bug.
--
e100 module does not create
Per your request, ifconfig -a yields
===
eth1 Link encap:Ethernet HWaddr 00:02:55:1A:5D:7C
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Public bug reported:
Binary package hint: linux-image-2.6.22-12-generic
In my system, the 2.6.22-12-generic kernel in Gutsy beta1 does not bring
up the e100 ethernet device upon boot. The e100 module is loaded, and
doesn't produce any obvious error messages, but there is no /dev/eth0
created.
Public bug reported:
Binary package hint: python2.5
I'm not sure what happened, I'm just starting with python. I was
working from the console; entered a (possibly bad) command:
$ pydoc -k in
and I saw the following output:
=
__builtin__ - Built-in functions,
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/7758143/Dependencies.txt
** Attachment added: ProcMaps.txt
http://librarian.launchpad.net/7758144/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://librarian.launchpad.net/7758145/ProcStatus.txt
** Attachment
I am experiencing a similar problem on feisty beta.
I think this is very simple. Samba has two daemons: nmbd queries other smb
servers, and smbd is the server for other clients.
When /etc/init.d/samba runs, nmbd successfully starts, but smbd dies!
Since it isn't running, noone can connect
environment.
The repeated crashes under gnome can easily result in data loss.
James R. Phillips
** Affects: Ubuntu
Importance: Undecided
Status: Unconfirmed
--
Openoffice Calc crashes in Edgy under gnome
https://launchpad.net/bugs/70152
--
ubuntu-bugs mailing list
ubuntu-bugs
19 matches
Mail list logo
