Is it just me, or is he doing a Chubby Bubbles Girl impression?

Further details: mouse cursor is briefly visible just prior to the black (login) screen. GDM does show up on the display, but in too big a resolution, so that I only get some of the grey background visible on screen and still have to log in blindly.

It occurred to me that with lightdm, the symptom appears as I would expect if it failed to do monitor detection properly and thinks it’s displaying the login screen on the (broken) internal display only. Well, apart from the funky ”login screen desktop background” phenomenon (which could be a separate issue though).

(Just to be clear: this same combination of broken internal + working external display did display the login screen correctly on the external one in Precise.)

This is a laptop with a broken internal display (”LVDS1” in xrandr output), and therefore connected to a working external LCD (”VGA1”).

After upgrading from Precise to Trusty, boot ends with a black screen (on the external display). The greeter sound effect is played. Typing my password (I’m the sole user) does log me in, and brings up the desktop on the display.

So the login functionality is there, just the visuals are missing. And they do flash by (corrupted) when the desktop is loading; if I set automatic login for myself, I get a desktop with the login screen as the background image (I’ll attach a screenshot).

There are existing, similar reports but all with subtle differences from this (such as Bug #1252748, where the user only gets black screen half the time) or too vague for me to claim to be the same issue with certainty (such as Bug #1242213). A lightdm restart (such as in Bug #969489) doesn’t fix this (i.e. black screen still after lightdm restart).

I’m not sure whether this is a lightdm issue or a unity-greeter one, so my reporting this against the latter is just a guess.

”To the back, to the front, to the side, don’t hide.”

Funny how he almost missed the biggest thing in the dish. :) Probably had his eye tuned for finding everything below a certain size and the grasshopper was way above that.

I currently have a 100% reliable recipe for reproducing this in 12.04: trying to restore a saved session of Trusty crashes VirtualBox 4.3.2 (from Oracle), after which Apport’s ”TypeError(Error(’Incorrect padding’,),)” pops up. (The recipe works also after removing crash files from /var/crash.)

Richardin sijasta taidat tarkoittaa David Attenborough’ta. Ainakin tuo videopätkä on Nisäkkäiden maailmasta, joka on yksi Sir Davidin sarjoista.

Tämän (ja tähän perustuvan uutisen) mukaan Android-sovellus edellyttää 2.3:n tai uudemman, Playssa esittelyn mukaan sovellus toimii ”laitteilla, joissa Android 2.2 tai uudempi”, eli jompi kumpi väittämä kaivannee päivitystä.

Onko kanavalähetysten tuki tulossa myöhemmin myös 3.0:aa vanhempiin Anteroihin?

Onko CC0 tuolla sitä varten, että vastikään valmistunut käännös kopioidaan sinne vai mitenkä?

Onnittelut valmistumisen johdosta!