Here is a strace. Couldn't make it hang while stracing though:
http://pastebin.com/mQ6Zgja1
Not sure how to produce anything useful with gdb, if you have any
suggestions I'm happy to try. I could connect with gdb to the hanging
program, would that be of any use? And what kind of information would
Probably final comment from me, I found a workaround that "solves" the problem
for me.
If you don't need QT Accessibility:
Edit `/etc/X11/Xsession.d/90qt-a11y', put a `#' in front of all lines:
# -*- sh -*-
# Xsession.d script to set the QT_ACCESSIBILITY env variable when accessibility
# is enab
I guess this is not a lightdm issue, so changing the package to Xorg.
** Package changed: lightdm (Ubuntu) => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870874
Title:
LDAP user wit
I can confirm this on two machines. The command in the above post
contains a typo, the command below is the one at which the login process
hangs:
`gsettings get org.gnome.desktop.interface toolkit-accessibility'
According to `ps aux' the process is in state `Sl'. When I kill that
single process (
I can confirm with Ubuntu 11.10 and Flash player 11 downloaded from
Adobe's website. I don't know whether it is a problem with Adobe's
plugin or whether the problem is on the Ubuntu side.
The problem can be observed very easily in this Flash game:
http://www.adamatomic.com/canabalt
Just wait unti
It seems the system is hanging at:
`gsettings get org.gnome.desktop.interface toolkit-accessiblity'
Once I did a `killall gsettings' the ldap user logged in properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870874
Title:
LDAP user with automounted nfs homedir cannot login
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
Public bug reported:
After installing Ubuntu (Oneiric, development branch) I followed two
guides to setup LDAP authentication and automounting of home directories
using autofs-ldap. This setup was working properly for older Ubuntu
releases (just to be sure I also tried with a fresh, up to date 11.
I changed my upstart script to ensure both the bridge and the md0 device
(on which the LVM volume is located) are started before libvirt is
started. In my situation this makes sure all my virtual machines can be
started. However, different virtual machines can have different
dependencies on (possib
It seems there is another problem with my configuration that causes
libvirt to have problems with autostarting virtual machines. I am using
software RAID 1 with mdadm and my virtual machines are running on an
LVM2 partition on md0. It seems the LVM2 volume is not yet available at
the point where li
I can reproduce this on a fresh Ubuntu 11.04 using two 11.04 virtual
machines (I had better luck with my previous 10.10 install that did work
properly for me).
The patch provided by Mika does not seem to work for me, libvirt does
not seem to be started properly with it (my domains are not shown in
I have this problem as well: Ubuntu 9.10 and reading mount points from
an ldap server. The ldap server is running on a guest virtual machine,
while the host itself needs autofs. Tried moving autofs from S19 in the
init scripts to S30 (after libnss-ldap and after qemu-kvm and libvirt-
bin), but that
Is there anything we can do to help somebody looking into this? I'm
happy to provide more information if necessary. Should we look into
other related packages that might cause the problem and file bug reports
for those? For me this bug is pretty much a show stopper, autostarting
domains is somethin
I tried setting bridge_maxwait=0, I only booted two times thereafter to
see what happened. In both occasions some of the VM's with autostart
booted, but not all of them (first time 2/5, second time 4/5). So, at
best this might have helped a bit, but it is not a solution for the
problem.
The filesy
I've been able to start up all domains consistently on each boot of the
host OS, by changing the parameters of the partition the host OS is
installed on. I've forced a check of this filesystem on each system
boot, and all domains are running consistently after the host is booted.
The filesystem che
Just rebooted the host, which started checking the file system.
Thereafter all domains seemed to be up. Unsure whether this was
coincidence (can't remember seeing all domains up after a reboot
before), or whether the extra boot time somehow caused the domains to
come up as expected.
--
autostart
Public bug reported:
host OS:
lsb_release -rd:
1. Release of Ubuntu:
Description:Ubuntu 9.10
Release:9.10
Linux 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:02:15 UTC 2009 x86_64
GNU/Linux
2. Version of package:
apt-cache policy libvirt-bin
libvirt-bin:
Installed: 0.7.0-1ubuntu13.
I experienced the same problem. Opening a file dialog in any application
causes a 25 second freeze of the program. Thereafter the dialog appears
and can be used.
I am using fully updated Ubuntu 8.04.2 (64 bits) clients and server. The
problem occurs only with user accounts that have NFS mounted ho
After another fresh installation, without installing mdadm my system
also freezes sometimes (allthough not that consequent as when mdadm is
installed). I even got a freeze while I was in the system bios, so I
guess the real problem is with my hardware.
--
installation of mdadm causes freeze durin
Public bug reported:
Binary package hint: mdadm
I have a fresh installation of Ubuntu 8.04 which has three harddisks
(all ide, pata disks):
/dev/sda (contains '/' on /dev/sda1 and swap on /dev/sda2)
/dev/sdb
/dev/sdc
I would like to create a raid 1 array of sdb and sdc.
Everything runs fine unt
20 matches
Mail list logo
