unable to complete login if onboard set as start minimized

Bug #783439 reported by Viljo Seppä on 2011-05-16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
unity (Ubuntu)

Bug Description

I am running Ubuntu 11.04 Desktop (with Unity) on a Intel Atom -based Tablet. If "start onboard minimized" is enabled, the whole shell UI does not appear after typing user password and hitting Enter in the login screen. Cursor can be moved and wallpaper is visible (also SSHing works so the PC does not crash).

steps to recreate:
1) Install Ubuntu 11.04
2) on first boot, in the login screen, open assistive tech and enable on-screen keyboard.
3) login using the on-screen keyboard. Unity comes up as intended.
4) go to application "Assistive Technologies", enable assistive technologies, enable "password dialogs as normal windows", select onboard as the keyboard application and enable "run at start".
4) open onboard, go to settings and enable "start onboard minimized".
5) reboot
6) login screen and on-screen keyboard appears.
7) use keyboard to login, pressing enter after typing password.
8) Unity does not come up, only cursor and wallpaper visible.

steps to revert:
1) reboot
2) in login screen, select "Ubuntu Classic" as the session.
3) login, Gnome 2 comes up as expected.
4) open onboard and disable option "start onboard minimized".
5) logout/reboot
6) login with "Ubuntu" as the session (to use Unity).

So with Gnome 2, onboard's start minimized works as expected, while in Unity the whole shell fails to appear when logging in. Workaround is to not use "start onboard minimized" (or not to use Unity ;).

marmuta (marmuta) wrote :

Hi, thank you for your bug report. I've tried and failed to reproduce that behaviour with an updated Natty install. Does this problem still persist after updating the fresh install?

Changed in onboard:
status: New → Incomplete
Viljo Seppä (vilsep) wrote :

Yes, still happens after sudo apt-get update && apt-get upgrade.

When arriving to the login screen the following gets posted in the syslog:
May 20 16:21:05 Hostname gdm-simple-greeter[1081]: Gtk-WARNING: /build/buildd/gtk+2.0-2.24.4/gtk/gtkwidget.c:5687: widget not within a GtkWindow
May 20 16:21:05 Hostname gdm-simple-greeter[1081]: WARNING: Unable to load CK history: no seat-id found

When logging in and the login gets stuck, the following gets posted in the syslog:
May 20 16:33:38 Hostname gdm-session-worker[1084]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

Hope this helps.

marmuta (marmuta) wrote :

Nope, can't see anything suspicious in your syslog. ~/.xsession-errors may have some unity output. If you like, look through there and try to locate a failed unity startup. I'm going to install a fresh Natty for testing. Not sure if it matters, but yours is a 32bit install, right?

Viljo Seppä (vilsep) wrote :

Yes, 32-bit Ubuntu Natty (11.04) Desktop version.

Some interesting stuff in ~/.xsession-errors: http://pastebin.com/tJEJSaR6 All of this comes after logging in. The stuff before that (from boot to arriving to the login screen) is not that interesting, but here it is just in case: http://pastebin.com/TMqfpMw9

To recap:
- I have set the on-screen keyboard on in the login screen (this seems to act completely separately from onboard when logged in as user)
- From onboard settings, I have all check marks checked.
- I use Unity.

If removing check mark from "start onboard minimized", it will work fine. If using gnome session (Ubuntu classic), it will work fine. Hope this helps.

marmuta (marmuta) wrote :

Thanks. I was able to reproduce it in an almost fresh Natty 32bit install. It wouldn't hang right after the install, only after randomly installing and uninstalling presumably expendable stuff (e.g. mono). It may be a timing thing too, as it would still occasionally start into the unity desktop fine. Mostly it would get stuck at the empty wall paper as you described though.

There are some message in your and my .xsession-errors like

MaximizeIfBigEnough: Onboard window size doesn't fit

but poking that in the unity source didn't lead anywhere. I'm going to just let the unity devs have a look.

Changed in onboard:
status: Incomplete → Confirmed
marmuta (marmuta) wrote :

One more data point. Enabling "Assistive Technologies" isn't even necessary, meaning at-spi is not at fault here.
Adding onboard to Classic Desktop->Preferences->Startup Applications and having it start minimized is all that's needed. On my Natty test install, in at least two of three cases the unity session will hang at an empty desktop.

Omer Akram (om26er) wrote :

>> MaximizeIfBigEnough: Onboard window size doesn't fit

thats not a bug, this message tells that onboard window's size is less than 75% of the screen hence wont be auto-maximized.

tags: added: a11y
Changed in unity:
status: New → Confirmed
Changed in unity (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Alejandro Piñeiro (apinheiro) wrote :

FWIW, there is another bug with the issues on the interrelationship between Onboard and Unity. You can find it here 739812

Sebastien Bacher (seb128) wrote :

duplicate bug #865890 it seems which has a stacktrace

Are you still experiencing this bug in any current supported Ubuntu release? (https://wiki.ubuntu.com/Releases)

If so please execute the following command in a terminal, as it will automatically gather debugging information:
apport-collect 783439

Changed in onboard:
status: Confirmed → Incomplete
Changed in unity:
status: Confirmed → Incomplete
Changed in unity (Ubuntu):
status: Confirmed → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for Unity because there has been no activity for 60 days.]

Changed in unity:
status: Incomplete → Expired
Launchpad Janitor (janitor) wrote :

[Expired for unity (Ubuntu) because there has been no activity for 60 days.]

Changed in unity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers