This looks related to a test case I was preparing to demonstrate how flawed the output from wpautop can get inside lists:

<ol>
<li>
foo

bar
</li>
</ol>

renders as:

<ol> 
<li> 
foo</p> 
<p>bar
</li> 
</ol>

whereas I’d expect it to be

<ol> 
<li> 
<p>foo</p> 
<p>bar</p>
</li> 
</ol>

I’m changing the summary to generally cover wpautop’s problems within <li> elements.

I now tried it in Natty, and while at it, in Oneiric as well. In both, GIMP still does exhibit the problem.

I gave it a spin in Natty and yes, the issue is still there. Also, the upstream bug I mentioned seems to be the right one for this, as the discussion there also involves Jamendo’s Ogg streams. I’ll update this one accordingly.

What’s worse is qtpfsgui suggests (or whines, as Darxus more eloquently put it) I look into documentation, and there it tells me ”Linux users have to checkout [hugin] project’s subversion repository and compile the sources”. Perhaps it was helpful at one point, but now it’s so outdated it’s become badly misleading.

(This on Lucid, at least.)

Hi,

The Pinta PPA description currently says: ”It’s goal”. It should say ”Its goal”. (Description inside the package itself has this right.)

Is the PPA still being maintained? I’m asking because ppa:nilarimogard/webupd8 currently has version 0.8-1, but I’d rather use your PPA because Pinta’s all I’m interested in.

According to upstream this has been fixed in Gnome 3.0.

As I reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/524497

There’s a usability issue with the login screen’s panel being at the bottom of the screen. It should be at the top, or at the very least the elements that are present in both the login screen and the desktop (the clock and shutdown menu) should be positioned consistently. It’s very confusing as it stands, with the clock and the shutdown function jumping from the bottom of the login screen to the top of the desktop screen when we log in.

Either the top of the screen is the accessibility-wise better place for these elements, in which case they should be there *during the login screen also*, or it isn’t, in which case they shouldn’t be there when we get to the desktop *either*. They shouldn’t be in one place on one screen, in another place on another screen.

The second paragraph of the package description says ”It’s modular concept is intended to provide”. It should say ”Its modular concept is intended to provide”.

I’m attaching a trivial patch, the first one I’ve ever uploaded to Launchpad, just to see if I did it right, and would appreciate any feedback.

I think the bug manifests itself differently depending on the underlying graphics hardware: I’ve heard a report about the colors being wrong on an Intel platform, whereas on my Radeon trying to play YouTube videos since Friday resulted in my LCD going to power saving mode and not waking up anymore.

Disabling hardware acceleration solved both issues.

If I’m reading it correctly, the submitter actually wants gedit to wrap the text at the *right margin*, and it still doesn’t do so in Lucid. That makes this a duplicate of #329500.