AllenS: you can try setting autologin-session=XBMC to see if it fixes
the wrong session problem. About the short timeout, I think that the
timeout starts when lightdm starts, and it starts the greeter afterwards
and on slower computers the greeter may not have enough time to get to
presenting the l
Public bug reported:
Version 1.2.3-0ubuntu1 of lightdm (in Precise) fixed timed autologin for
the initial startup (see bug #902852), but timed autologin still does
not work after logging out from a session.
It is logical that *immediate* autologin doesn't work after logout, but
the purpose of *ti
Installed packages liblightdm-gobject-1-0_1.2.3-0ubuntu1,
lightdm_1.2.3-0ubuntu1 and unity-greeter_0.2.9-0ubuntu1. Timed autologin
works when using unity-greeter, but the following problems remain:
* Only works when lightdm service started, not after logout from a
session.
* No visual countdown/o
I installed liblightdm-gobject-1-0_1.2.3-0ubuntu1 and
lightdm_1.2.3-0ubuntu1 on Precise with the following results:
* Timed autologin does not work at all with unity-greeter (though I see
it's still marked as "In Progress").
* When switched to lightdm-gtk-greeter, the user is authenticated after
Just this Friday I got around to testing compiz 0.9.8.6 on Gentoo (mesa
upgrades did not help), and it fixes this bug for me. Unfortunately
0.9.8 on Gentoo has issues with several plugins not working correctly
(e.g. place windows not working at all, all windows open at top left
corner), so I'll hav
The package from precise-proposed works OK (very simple fix so no
surprise there).
** Description changed:
Impact: gtimer sometimes fails to start and crashes with a segfault
+
Fix: the code does not initialize a variable it later uses causing
memory corruption
+
TEST CASE:
+
s
apport-collect not run: does not use $http_proxy
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1020004
Title:
/initrd.img symlin
Public bug reported:
The /initrd.img symlink is created with absolute target path in Precise.
This makes accessing the latest initrd difficult if the rootfs in
question is not *our* rootfs (e.g. nfsroot server). In Lucid the target
path was relative, and so is the kernel path in Precise:
/initrd.
** Description changed:
The default route cannot be provided via DHCPv6, it must be obtained
from router advertisements. However, when using the dhcp method for
inet6 in /etc/network/interfaces (e.g. "iface eth0 inet6 dhcp"), ifup
will set net.ipv6.conf..accept_ra=0, resulting in no defaul
Public bug reported:
The default route cannot be provided via DHCPv6, it must be obtained
from router advertisements. However, when using the dhcp method for
inet6 in /etc/network/interfaces (e.g. "iface eth0 inet6 dhcp"), ifup
will set net.ipv6.conf..accept_ra=0, resulting in no default
route for
I noticed a focus issue between workspace switches, but (at least for
me, on precise and gnome-classic) it does not have anything to do with
maximized/fullscreen: when switching to a workspace that has no
focusable windows (i.e. empty), the focus is retained on the window and
workspace switched fro
Public bug reported:
This happens on precise with Gnome Classic session and compiz, does not
appear to happen with unity.
When there are three or more horizontal workspaces, a maximized window
is sent to the leftmost workspace in the row whenever a workspace that
is to the right of the maximized
I have this bug on Gentoo, running xterm under compiz, Radeon card with
gallium drivers. Before hardware upgrade the system had nVidia card with
nVidia's proprietary drivers, software otherwise the same, and it did
not have this bug.
When I have time I plan to try upgrading to Gentoo's unstable ve
I ran into this bug while testing Lubuntu precise.
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903490
Title:
Desktop Pager leaves ghost / phantom windows
To manage notific
** Patch added: "patch to fix startup segfault"
https://bugs.launchpad.net/bugs/974038/+attachment/3007800/+files/fix-startup-segfault-on-precise.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Public bug reported:
gtimer segfaults at startup when run on precise beta, with the following
info from gdb:
Program received signal SIGSEGV, Segmentation fault.
create_main_window_menu_bar () at main.c:2055
2055g_message(gettext("Building menu Failed: %s \n"), err->message);
My gues
I ran into this bug on Gentoo. The patch 2 in
https://bugzilla.mozilla.org/show_bug.cgi?id=631518 seems to have fixed
this. That patch was also used to fix
https://bugs.launchpad.net/compiz/+bug/438868 so looks like this bug
should be fixed in Ubuntu (at least Lucid and Maverick).
Also, I found a
This bug is still present on my 32-bit Maverick, with Intel Q35 graphics
chipset. The stutter may not be as severe as the original reporter
described, but it is still there. This did not happen in Lucid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
This seems to only affect i386. On amd64 the linux-image-virtual
installs a -server kernel, which works fine as a Xen domU.
--
Kernel installed by linux-image-virtual isn't usable as Xen DomU kernel
https://bugs.launchpad.net/bugs/461127
You received this bug notification because you are a membe
This might be a duplicate of
https://bugs.launchpad.net/ubuntu/karmic/+source/cairo/+bug/419143,
depending on whether the workaround in comment #56 fixes the issue for
the original reporter. I had a similar problem, i.e. printing from
evince failing silently without any error messages with Dell 510
Public bug reported:
Binary package hint: nut
After upgrading from Jaunty to Karmic, I noticed that UPS monitoring
with nut stopped working. It took me a few moments to figure it out, but
then I noticed that /etc/nut/nut.conf had a new timestamp and in it the
variable MODE was (once again) set to
rdesktop is run inside a VNC session, i.e. connect from desktop with
vncviewer to a server running vncserver, and start rdesktop there. There
was no problem running rdesktop locally (without -y, I did not try with
-y as it worked without it).
I reported the effects of keypresses, perhaps in a conf
@Michael Lazarev: in my separate bug report, which was then marked as a
duplicate of this bug, I described some symptoms with the fi keymap
under VNC:
https://bugs.launchpad.net/ubuntu/+source/rdesktop/+bug/381567
though they may not be the same or similar ones that ktp420 is concerned
about.
Public bug reported:
Binary package hint: rdesktop
If rdesktop 1.6.0-2ubuntu1 is run under VNC (vnc4server or
tightvncserver) the keyboard mapping is broken: keys produce wrong
characters and modifiers may be ignored or assumed (e.g. with a finnish
keymap the '0' key should produce "0=}" with its
24 matches
Mail list logo
