Bump +1!
--
[needs-packaging] python-ogre
https://bugs.launchpad.net/bugs/199497
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-b
No.
That value just tells gdm how long to wait for X to start up before
deciding that X has hung, to kill it and try starting it again. So my
guess is that if the machine is slow:
1. X takes longer to start than GdmXserverTimeout allows, because other
background processes started during boot are
What's your GdmXserverTimeout now? And does doubling it resolve the
problem?
Steve
On Thu, 2009-12-10 at 06:34 +, .kkursor wrote:
> New results.
> Autologin works...mostly.
> If I shut down the computer using Power button (not long press, just press
> and quick release), the "Welcome to GNO
Hi,
Can you try extending GdmXserverTimeout to see if that helps? Maybe try
setting it to 20 or 30?
Steve
On Tue, 2009-12-01 at 14:11 +, .kkursor wrote:
> This bug affects me too.
>
> >sudo update-rc.d -f gdm remove
> >sudo update-rc.d gdm defaults
> did not help.
>
> I have a specific is
Trying Kazabubu's suggestion to extend GdmXserverTimeout cleared it up
for me. At least it's been fine for the last week plus, I've rebooted
many times.
Okay, here's my hypothesis of what's going on:
1) Note that Rami said boot was slow for him until he turned off AHCI,
and then when he disabled
By the way, GDM was starting on my system with a default sequence number
of 20. I just did:
sudo update-rc.d -f gdm remove
sudo update-rc.d gdm defaults 99
And now the autologin seems to be working... I'll let ya know in a few
days or so if that's still the case.
Steve
On Fri, 2009-07-24 at 12:
Maybe so.
When I emailed earlier that adding "sleep 10" to my /etc/init.d/gdm
script fixed the problem, I celebrated a little too quickly. It worked
for a while, but doesn't work any more. An earlier reporter's assertion
that removing the preload package, as well as my temporary experience of
the
Perhaps this is a silly question, but have you verified that the chip
actually works, using Windows or another kernel for example? It's
possible that the chip has failed in a way which still permits it to
advertise its presence on the PCI-E bus while it is incapable of
actually acting as an interfa
Starting at line 47:
case "$1" in
start)
sleep 10;
if grep -wqs text /proc/cmdline; then
I just added the "sleep 10;" line, everything else in that snippet is
original.
Steve
On Mon, 2009-06-29 at 01:17 +, NoOp wrote:
> Sure - willing to give it a shot. Specifically where
But in the spirit of Philipp's changes, I added "sleep 10;" to the start
section of /etc/init.d/gdm, and that's gotten it working correctly for
three boots in a row. That's progress for me. NoOp, can you give that a
try?
Steve
On Sun, 2009-06-28 at 14:12 +, NoOp wrote:
> On 06/28/2009 01:27
Preload isn't installed on my system, and I'm also having the
problem. :-(
On Sun, 2009-06-28 at 08:27 +, P-Baumgart wrote:
> hell yeah!! I discovered what couses the problem: preload! remove it
> from your system, and autologin will work again! the preload package in
> ubuntu repository is c
No hints in any of those files, and I haven't touched anything in pam
ever...
--
Jaunty's GDM Autologin doesn't work anymore
https://bugs.launchpad.net/bugs/370541
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
Where do you suggest I look? It's true that back in Ibex I did use
Ibex's control panel to set up autologin, but given the contents of
/etc/gdm/gdm.conf (listed above), I'm not sure where the problem could
be other than gdm.
--
Jaunty's GDM Autologin doesn't work anymore
https://bugs.launchpad.ne
Please change this back to an open bug. I had autologin working just
fine under Ibex, then after I upgraded to Jaunty it stopped working,
with no changes on my part.
Additional information: After I boot the machine up, when it arrives at
the login screen, if I ssh in and do "/etc/init.d/gdm stop;
Verified that xawtv works fine (once I disabled xv the video came over
SSH fine), and webcam-server does not.
--
get_cam_image(): len != img->bufsize, just letting you know
https://bugs.launchpad.net/bugs/318187
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Same problem here. xawtv is able to connect and save stills from the
camera. (I'm not seeing video, but that may be because I'm SSHing into
the machine in question.) Relevant lsusb line is:
Bus 004 Device 003: ID 18cd:cafe Ecamm Pico iMage
--
get_cam_image(): len != img->bufsize, just letting yo
16 matches
Mail list logo
