I just ran into this same problem. Running drew's steps, including the
.14 kernel, fixed it:
His workaround:
1. Reboot. (my machine didn't shutdown clearly and had to be powered off)
2. At grub menu choose kernel 2.6.22-14 (not 2.6.22-15)
3. Once booted run dpkg --configure -a
4. wait (it takes
Hello,
I don't mean to reopen this bug after it's (apparently) been fixed.
I was trying to setup a combined LDAP/Kerberos system today, and ran
into this exact problem. I'm running the latest version of Hardy with
all updates. After I applied the fixes to the AppArmor profile suggested
by Ryan,
Hello,
I don't mean to reopen this bug after it's (apparently) been fixed.
I was trying to setup a combined LDAP/Kerberos system today, and ran
into this exact problem. I'm running the latest version of Hardy with
all updates. After I applied the fixes to the AppArmor profile suggested
by Ryan,
I'm also seeing this problem with Hardy.
--
Pidgin SIGSEGV (gnome proxy settings)
https://bugs.launchpad.net/bugs/173886
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
Honestly, I really don't see what the holdup is to get the dbus-x11
package required in backports.
I've yet to see anyone for whom installing dbus-x11 has NOT fixed the
problem. I've marked several bugs as duplicates of this one - they all
say the same thing. How much confirmation do we need,
*** This bug is a duplicate of bug 146946 ***
https://bugs.launchpad.net/bugs/146946
Yeah, it definitely seems that way.
We should try to get this change into backports, at least.
** This bug has been marked a duplicate of bug 146946
[gutsy] Gnome settings daemon randomly does not work
I noticed this bug today, too, on a multiuser LTSP system running Gutsy.
Like others have said, ps doesn't show multiple processes of console-
kit-daemon. In my case, htop showed a range of PIDs from about 6188 to
about 6250 (somewhere along those lines), whereas ps only showed one
single PID.
Like Jordan, I've also bin bitten by this bug on a dual LTSP server
network. We also have NFS home directories, which compounds the
slowness.
I just applied the updates for nautilus and nautilus-data from gutsy-
proposed. I'll see what happens over the next few days.
--
[Gutsy] high processor
I just got bitten by the same problem, though I had it even worse: my
LDAP fuse group conflicted with the local Gutsy fuse group (due to an
LDAP data import from a Feisty server).
I don't think this can be called a bug. Scott is right in that important
system groups like fuse should be replicated
Sebastien, I'll run a test installation within the next week or so and
let you know what happens.
Either way, is there any way to push a backport into Gutsy? Maybe
require a dependency on one of the standard dbus (or even better, gnome)
packages to get this installed?
I'm worried that people are
Paul,
I had a very similar error message. As suggested by Henriël Veldtmann in
bug #146946, installing the dbus-X11 package _in addition to_ the dbus
package fixed the error. It seems like there's a missing dependency with
one of the Gnome packages (gnome-session, from what I can tell, is the
Just to clarify, that's dbus-x11 with a lowercase x.
--
[gutsy] gconfd starts with session, but apps say that gconfd can't be contacted
and user settings are not loaded
https://bugs.launchpad.net/bugs/139368
You received this bug notification because you are a member of Ubuntu
Bugs, which is
After a clean install of Gutsy, I ran into this same problem. I tried
the fix that Henriël_Veldtmann suggested, and after about 2 weeks, I
haven't seen a problem since. I can't confirm the solution 100%, but
anecdotal evidence does suggest that it fixes it.
I'm not sure why the dbus-X11 package
Sebastian, please see my comment on bug #146946. After applying the fix
proposed by Henriël Veldtmann (installing dbus-X11), the problem so far
hasn't reappeared. Perhaps it is, indeed, a dbus issue?
--
[gutsy] gconfd starts with session, but apps say that gconfd can't be contacted
and user
I've been having the same issue on a clean install of Gutsy, even with
the latest updates. Bug #146946 describes my issue perfectly.
Henriël Veldtmann suggested a fix that has solved my problems so far:
installing the dbus-X11 package. I'm not positive why this solves
things, but it does for me.
I encountered the exact same problem, and just like sammiam wrote, it
was the DFE-350TX+ adapter that caused the problem. When I switched to
using an onboard network interface on a server, NFS worked like a charm.
I was using Gutsy with the 2.6.22-14-generic kernel, by the way, so the
problem
Johan, sorry if I wasn't clear. I meant that we still had not tested the
server packages to make sure they work. I ran some tests a while ago
with the backported openafs-fileserver and openafs-dbserver packages -
they work great on Edgy with the backported modules. Here's some
information on the
Johan, allee, and Björn,
I followed the steps that allee posted, and I successfully built the
feisty modules on edgy. I didn't run into any problems, except that I
had to install the devscripts package.
Everything works over here. I installed libpam-openafs-session and
openafs-krb5, so the
Johan, I will test the server packages (openafs-fileserver and openafs-
dbserver) on Edgy and report what I find.
Otherwise, since we have (almost) all the information we need, we just
need to reiterate our request individually - whether it be on IRC or by
email. There's a large enough OpenAFS
For the benefit of English speakers, here's a translation:
I'm not sure exactly what's happening, I'm not an advanced user, but I
can send the report generated by the system... what I do know is that it
says that the problem was in beryl-core, this doesn't always happen.
My system loads beryl
I can confirm that the first problem -still- exists on Edgy, 6.10.
Clicking Become Administrator asks for a password but does nothing
more. Running sudo gnome-cups-manager gets the job done, but that
doesn't solve the problem.
--
Changes needed for sudo model
https://launchpad.net/bugs/24887
--
** Summary changed:
- Changes needed for sudo model
+ gnome-cups-manager doesn't let regular users become administrator for admin
tasks
** Description changed:
- gnome-cups-manager on Breezy needs some changes for sudo model.
+ gnome-cups-manager needs some changes for sudo model.
BECOME
It's so good to know that this problem is being exposed. I share
Madmoose's problem - I have to restart gdm for the mouse taps to stop
working entirely, even when properly configured in xorg.conf.
--
synaptics touch pad(laptop) clicks too easily
https://launchpad.net/bugs/47971
--
ubuntu-bugs
I had this exact problem on Edgy. I shifted around the partitions on my
disk, deleting my original swap partition and creating a larger one. I
modified the swap entry in /etc/fstab, so the new swap space was mounted
with no problem.
However, hibernate stopped working immediately after. It took me
This is probably a duplicate or close relative of Bug #55535.
--
By modifying partition table for install whit Life CD flight 7 hibernating is
not working
https://launchpad.net/bugs/45724
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
For those who want to use TightVNC on amd64 right now, I've built a
binary package, version 1.2.9-21. It was built from a source package
from the Debian testing repository
(http://packages.debian.org/testing/x11/tightvncserver).
The vncserver binary now runs without any problems on my amd64
And here it really is.
** Attachment added: xtightvncviewer 1.2.9-21 binary package for amd64
http://librarian.launchpad.net/6600768/xtightvncviewer_1.2.9-21_amd64.deb
--
tightvnc crashes on 6.10 amd64
https://launchpad.net/bugs/75954
--
ubuntu-bugs mailing list
Here's the xtightvncviewer 1.2.9-21 binary package, too.
--
tightvnc crashes on 6.10 amd64
https://launchpad.net/bugs/75954
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I'm having the same problem on Edgy. I managed to get a crash dump
automatically generated by the Ubuntu bug reporter, but it doesn't seem
to have much information. I've attached it.
I followed the directions on the DebuggingProgramCrash page on the
Ubuntu wiki, but there's no tightvncserver
Like Helge said, the latest package is still 1.4.1-4. If Sam is not the
maintainer for the Ubuntu package (even though the Ubuntu repository
lists him as such), we should find a new maintainer and get this problem
solved.
I built all the OpenAFS packages from the Debian repository, as
suggested
30 matches
Mail list logo
