Onko tämä tilapäistä?

23. huhtikuuta 2012 klo 20.49
Sijainti: Uutissivustot: YLE Uutiset
Avainsanat: Internet, saavutettavuus, Yle

Onko se tilapäistä, vai rikoitteko oikeasti taas kaikki entiset uutislinkit? Eikä tekstiversiota ole enää ollenkaan? Ei tässä uudessa sinänsä mitään vikaa ole, mutta ei tämä tekstiversiota korvaa alkuunkaan.

Vastaa viestiin sen kontekstissa (YLE Uutiset)

Hit the Oops (__ticket_spin_lock+0x9/0x30) with apw’s kernel

22. huhtikuuta 2012 klo 20.16
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Linux

I’ve just hit the Oops (__ticket_spin_lock+0x9/0x30) with apw’s kernel. I’ll attach the syslog from after reboot to this comment. Had been running the apw build since Monday this week (7 days now) without problems.

Vastaa viestiin sen kontekstissa (Launchpad)

You’re probably hitting a WordPress bug in get_search_form()

20. huhtikuuta 2012 klo 20.04
Sijainti: Muut: Stack Overflow
Avainsanat: WordPress

If your theme has a searchform.php, you’re probably hitting Ticket #16541get_search_form() ignores $echo if searchform.php exists.

Your workaround is fine if you’re just echoing the search form anyway, but if you need to capture the output in a variable, you can work around this with output buffering:

<?php ob_start();
get_search_form();
$my_search_form = ob_get_clean(); ?>

Vastaa viestiin sen kontekstissa (Stack Overflow)

I’ve today switched to apw’s build of 3.2.0-23

16. huhtikuuta 2012 klo 18.33
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Linux

Just to note here also that I’ve today switched to apw’s build of 3.2.0-23 [1] linked to from bug 922906. I had been running the upstream 3.3 for more than 7 weeks without hitting this (#917668). The GPU lockup I mentioned in #13 also never reoccurred since that one time.

I’ll report back, should #917668 resurface with the kernel I’m currently running.

* [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/922906/comments/11

Vastaa viestiin sen kontekstissa (Launchpad)

Sure, will do.

16. huhtikuuta 2012 klo 18.15
Sijainti: Blogit: Launchpad
Avainsanat: Linux

Sure, will do.

Vastaa viestiin sen kontekstissa (Launchpad)

Zooming keys hardcoded inconsistently

15. huhtikuuta 2012 klo 21.37
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Chromium, saavutettavuus

Ctrl + 0, Ctrl + Plus Sign and Ctrl + Minus Sign are the designated keyboard shortcuts for controlling the zoom. This works on my setup.

Ctrl + Shift + Minus Sign seems to work identically to Ctrl + Minus Sign, but on my setup, Ctrl + Shift + Plus Sign does nothing, whereas Ctrl + Shift + 0 does what, given Minus Sign’s behaviour, I’d expect Ctrl + Shift + Plus Sign to do: it zooms in.

I’m guessing this is keyboard layout dependent. I’m using the Finnish/Swedish keyboard layout, in which the ’0’ key with Shift is the = character. In US keyboard it seems the Plus Sign has its own key, and that key with the Shift pressed becomes =. This is why Chromium thinks that I’m doing the ’zoom in’ combination when in fact I’m doing the ’reset zoom’ combination with shift.

I came across this while looking for a way to reset the zoom back to my custom default via keyboard. I figured if Ctrl+0 is ’reset to normal’, Ctrl+Shift+0 could be ’reset to default’. (I have yet to find such a keyboard shortcut. That’s a separate issue from the one I’m filing here. I’ll have to file a wishlist bug if said shortcut doesn’t exist.)

Vastaa viestiin sen kontekstissa (Launchpad)

Ambiguous ”Password:” header on Special:ChangeEmail

15. huhtikuuta 2012 klo 10.16
Sijainti: Vianhallintajärjestelmät: Wikimedia Bugzilla
Avainsanat: MediaWiki, saavutettavuus

[[Special:ChangeEmail]] currently says: ”Complete this form to change your e-mail address. You will need to enter your password to confirm this change.”

The password field is located right after the ”New e-mail address” field and simply titled ”Password:”. The preface and this layout makes it unnecessarily easy to think it wants your ”password for your e-mail account” and not the current wiki. (I for one momentarily thought so despite being experienced enough to know it probably didn’t mean to.)

I suggest the ”Password:” header be changed slightly, to say ”Your {{SITENAME}} password:”

Vastaa viestiin sen kontekstissa (Wikimedia Bugzilla)

How to configure Unity/Compiz in 12.04 so that Update Manager opens maximized w/screen bigger than 1024×600?

12. huhtikuuta 2012 klo 20.29
Sijainti: Muut: Ask Ubuntu
Avainsanat: Unity

In Precise, window auto-maximize is disabled on monitors with a resolution above 1024 × 600 [1]. I have a bigger resolution, but I prefer maximized windows anyway. I want Update Manager to start maximized.

What I’ve tried so far:

  1. In Compiz Config Settings Manager, I have Place Windows activated and ’Windows with fixed placement mode’ has windows matching the rule ”(name=gnome-terminal) | (name=update-manager)” set to ’Maximize’. With this, Gnome Terminal starts maximized, Update Manager does not.
  2. In Compiz Config Settings Manager, I have set a Window Rules [2] rule to match ”name=update-manager”. Irregardless of any rules set or not, activating Window Rules results in not being able to bring out Unity Launcher anymore, Alt+Tab window switching becoming slow or nonfunctional entirely and the screen sporadically freezing completely. Not a viable option apparently.
  3. I’ve installed Maximus [3] and started it. Update Manager ignores it (or vice versa).

I’ve not tried devilspie and would prefer not to. Having to configure something external for this would seem stupidly redundant with (the no-brainer) Maximus and all these Compiz options already available. I just can’t seem to make them work.

Vastaa viestiin sen kontekstissa (Ask Ubuntu)

The fbdev workaround is good enough to work with

12. huhtikuuta 2012 klo 6.24
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Intel, Linux

Bryce; no problem (and thanks for your working on this), for me the fbdev workaround is good enough to work and live with on this setup. If others affected by this feel differently, do take over with upstream.

Vastaa viestiin sen kontekstissa (Launchpad)

Scroll Lock key as screen lock hotkey does not work (works in U2D)

10. huhtikuuta 2012 klo 19.18
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: saavutettavuus, Unity

Steps to reproduce:
1. In (gnome-control-center) Keyboard settings’ Shortcuts, set the shortcut for ’Lock screen’ to Scroll Lock.
2. Press Scroll Lock.

What happens:
Nothing (screen doesn’t get locked).

What I expect to happen:
For the screen to get locked.

What works:
* Setting ’Lock screen’ shortcut to Shift + Scroll Lock, Ctrl + Scroll Lock etc.
* Setting ’Lock screen’ shortcut to, for example, the Pause/Break key (which is right next to Scroll Lock on common keyboards).
* Setting Scroll Lock as the ’Lock screen’ shortcut in Unity 2D.

Other notes:
Pressing Scroll Lock does nothing whether set as screen locking hotkey or not, so it shouldn’t be tied to some other function either.

Vastaa viestiin sen kontekstissa (Launchpad)

« Uudempia - Vanhempia »