I strongly disagree with post #26. It's (yet another) ugly and
embarrassing bug in gnome-keyring that badly needs to be fixed. Usually
it only asks twice. But sometimes will never let the user in at all.
(Before posting this, I entered my gnome-keyring password 20 times
before giving up and rebooti
I have this issue. But I don't see the update in natty-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/744929
Title:
After auto-login, prompted to unlock keyring multiple times
To manage no
This problem still affects Lucid, fully updated with all the latest
updates, on my HP Mini.
cat "acpiphp" >> /etc/modules does, indeed, fix it.
sky2 driver. Marvell 88E8040 PCI-E Fast Ethernet Controller
--
HP Mini 2140 sky2 NIC does not hotplug by default
https://bugs.launchpad.net/bugs/464915
And one more thing. Note that I had my problem solved before I ever
opened this ticket. I opened it, as a courtesy, to report the problem,
give some insight as to things that made it particularly difficult to
track down, and get the workaround published so that others might not
have quite so much d
Well, let me ask you this. Is there someplace where my customers can
take out an official Canonical support contract that would be sufficient
to persuade Canonical support employees to get off their butts and
actually do some troubleshooting instead of looking for any way they can
to put it all bac
What I can do, when my work load permits, is bring up 60+ vncserver
sessions on a test server. Or, really, I supposed anyone else who cares
could do it if they get to it first. I suspect that this is going to be
quite reproduceable. It's not some hard to reproduce problem that only
the bug reporter
I'm sorry you feel that way, but I've already done all I can reasonably
do without doing a disservice to my customer. And if Canonical does not
understand that, then perhaps Ubuntu doesn't belong in the enterprise.
All things considered, RHEL support subscriptions cost a lot less than
this experi
As an admin, the worst part of this issue was the fact that things would
randomly stop working and lock up. Logins would inexplicably fail. All
with no particular pattern, getting worse and worse... and yet the cause
was not at all obvious. Nothing in daemon.log. Nothing in syslog.
Nothing in messa
James, with all due respect that is absolutely out of the question. I
have 70 business users with stable desktops now that "ulimit -n" is set
to an appropriate value. You are asking me to essentially crash 70 users
in three cities, and then clean up all the domino effect problems, like
residual evo
Sprawlgeek's method works for my jaunty netbook insofar as it does
connect. I get a point to point connection and dns servers. And DNS
resolution even works. (I can nslookup sites that I've never been to,
and the ip addresses that come back are correct.) But other than dns
resolution, no other pack
I will file upstream also. I should note that the original reporter
mentions that he upgraded from 8.10 to 9.04. Mine is a fresh install,
but with a big twist. Since I have many users, I copied over the
~/.gnome2/keyring directories from the Fedora 8 that we were coming
from. Also, I moved their en
** Attachment added: "Strace output for gnome-keyring-daemon"
http://launchpadlibrarian.net/27657153/gnome-keyring-daemon.strace
** Bug watch added: Red Hat Bugzilla #498871
https://bugzilla.redhat.com/show_bug.cgi?id=498871
--
Evolution hangs unpredictably, and doesn't restart without a
Here is what I think looks like the same bug over at RedHat/Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=498871
I have about 60 users who would love to see a fix. :-)
--
Evolution hangs unpredictably, and doesn't restart without a reboot
https://bugs.launchpad.net/bugs/374238
You receive
** Attachment added: "gdb output for gnome-keyring-daemon"
http://launchpadlibrarian.net/27657075/gdb-gnome-keyring-daemon.txt
--
Evolution hangs unpredictably, and doesn't restart without a reboot
https://bugs.launchpad.net/bugs/374238
You received this bug notification because you are a mem
** Attachment added: "Strace output for evolution"
http://launchpadlibrarian.net/27657101/evolution.strace
--
Evolution hangs unpredictably, and doesn't restart without a reboot
https://bugs.launchpad.net/bugs/374238
You received this bug notification because you are a member of Ubuntu
Bugs,
OK. I have a gdb and strace output. Since gnome-keyring-daemon is
mentioned in the output, and since I'm pretty sure I saw a bug in
Fedora's bugzilla in which it was suspected that the cause was gnome-
keyring-daemon deadlocking, I collected gdb and strace output for gnome-
keyring-daemon, as well.
I run an XDMCP/NX server which runs about 60 concurrent jaunty gnome
desktops, and I think we are experiencing this problem.
Next time this happens to a user, I'll try to collect more info.
Just to be clear, here is what I intend to do:
Install dbg packages for evolution, evolution-exchange, and
Public bug reported:
Ubuntu 9.04
dbus 1.2.12-0ubuntu2
We're on x86_64, but this is really arch independent
On a multiuser system with many desktop users, the system dbus-daemon
process can easily exceed the 1024 open files allowed by the default
ulimit. When it exceeds that, it goes into a tight
I'm guessing that someone grabbed the "latest" source from the BOINC
site and packaged the binary from that. 6.2.16+ only had changes to fix
problems with the Windows version, and maybe OSX. The binary you get
when you compile that for Linux is completely untested. Not alpha, not
beta, not at al
>From what I can see, as of today, the latest in Debian unstable is
6.2.14. So they are one release behind.
http://packages.debian.org/unstable/boinc-client
--
sync with boinc 6.2.18-1 package from debian (experimental)
https://bugs.launchpad.net/bugs/267636
You received this bug notification b
The latest released Linux version is 6.2.15 as can be seen here:
http://boincdl.ssl.berkeley.edu/dl/
Anything later than that has to be pre-release and *should not* be used!
BTW, there *is* a released 6.2.18 for Mac and Windows. If changes are
made that do not affect a platform, they do not rel
** Attachment added: "Strace output"
http://launchpadlibrarian.net/17540654/X.strace.txt
--
G43/X4500 chipset segfaults when using DVI port
https://bugs.launchpad.net/bugs/269107
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Upstream bug report is at:
https://bugs.freedesktop.org/show_bug.cgi?id=17533
** Attachment added: "X.stdout_stderr.txt"
http://launchpadlibrarian.net/17540645/X.stdout_stderr.txt
--
G43/X4500 chipset segfaults when using DVI port
https://bugs.launchpad.net/bugs/269107
You received this bug
** Attachment added: "lcpci -vv output"
http://launchpadlibrarian.net/17540609/lspci.txt
--
G43/X4500 chipset segfaults when using DVI port
https://bugs.launchpad.net/bugs/269107
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Public bug reported:
I have a Gigabyte EG43M-S2H which uses a G43 chipset and X4500 video. The
board has VGA, DVI, and HDMI. If I use the VGA port everything is fine.
But if I try to use the DVI port, the X server crashes while staring up with a
segfault and a backtrace.
I'm running a fully up
*** This bug is a duplicate of bug 265119 ***
https://bugs.launchpad.net/bugs/265119
** This bug has been marked a duplicate of bug 265119
intel 2.4 / X4500 black screen crash
--
Thinkpad X200 can't start GUI
https://bugs.launchpad.net/bugs/267375
You received this bug notification becaus
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/17367340/xorg.conf
--
intel 2.4 / X4500 black screen crash
https://bugs.launchpad.net/bugs/265119
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: "X.strace.txt"
http://launchpadlibrarian.net/17367328/X.strace.txt
--
intel 2.4 / X4500 black screen crash
https://bugs.launchpad.net/bugs/265119
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
** Attachment added: "X.stdout_stderr.txt"
http://launchpadlibrarian.net/17367302/X.stdout_stderr.txt
--
intel 2.4 / X4500 black screen crash
https://bugs.launchpad.net/bugs/265119
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I'm running the same 64 bit kernel and version of the intel driver on a
completely up to date Intrepid box. The X server actually dies with a
sigsegv and a backtrace, and then the black screen. I have compiled
2.4.2 from upstream and it has the same issues. Chipset is G43 with
X4500 graphics. G
I can confirm this bug on my Radeon Xpress 200M based laptop. Yes, it
only happens with the fglrx driver.
There is a workaround that I have found that perhaps the restricted
device manager could apply for Xpress 200M machines.
System->Administration->Login Window
and then set it to restart the
Public bug reported:
Binary package hint: laptop-mode
I'm not sure how this might or might not apply to a fresh feisty beta
install. I upgraded the edgy install on my compaq presario v2552us
notebook to Herd 5 and am now fully updated, so I should have the
equivalent of the beta.
Laptop mode fa
32 matches
Mail list logo
