This has been fixed upstream ages ago, how come the fix never made it to Ubuntu? I’m using up-to-date Precise and this is still an issue: scrollwheel still browses between pictures instead of panning the current picture.

Steps to reproduce:
0. Set up Chromium/Firefox to prompt when it’s not the default browser (e.g. for FF, set browser.shell.checkDefaultBrowser to true)
1. Create/save a file with .html extension
2. From Nautilus, open the file’s properties
3. On the Open With tab, select gedit as default application to open html files with
4. In System settings, select Details and verify that in Default Applications the Default Web Browser hasn’t changed
5. Start Chromium/Firefox

What happens:
The browser thinks it’s not the default browser anymore and prompts you to set it as such.

What I expect to happen:
For the browser to know it still is the default browser and not ask about it.

Has this happened before:
Doesn’t seem to apply to Lucid, so the bug occurs somewhere between 10.04…12.04.

Further info:
I’ll attach a screenshot demonstrating the above result.

I’m not at all sure whether I filed this against the right package, feel free to correct it.

I linked Unity 2D where this problem still remains. As a workaround, Shift+PrtScrn can be used to approximately select the desired window area to grab.

Happened just now as I was reporting another bug. May or may not have been associated with my Internet connection temporarily going offline for some reason at about the same time. No other conspicuous associated details I have right now but will happily provide if more data is needed.

No longer reproducible on two different up-to-date Precise setups here.

Lähtökohtaisesti liian pieni teksti ei skaalaudu muun sisällön mukana Chromiumilla zoomatessa.

From Bug #950645, here’s one somewhat reliable way to trigger this: after login, have some windows open (I have Chromium, Gnome Terminal and Transmission set to start on login, don’t know if this works if you start them manually), then use the workspace switcher. This causes the launcher to stick (i.e. autohide to fail). Interestingly, if I then killall unity-2d-shell, even this recipe then fails to trigger the issue until the next login. But it seems 100% reproducible right after login. (I’m just hoping that #950645 really is a duplicate of this one. For me the trigger’s always been something else in the launcher since I almost never use the workspace switcher.)

I’m feeling unimaginative so I’ll cheat and just answer those here without posting new ones.

1. My island would probably be Greenland, so ”between the Arctic and Atlantic Oceans”.
2. Not doing anything currently but will be learning and doing programming about a week from now.
3. Nope.
4. Nope.
5. Some code for my blog. If programming doesn’t count… must’ve been the amplifier we built back in uni. Didn’t do it all by myself, we did it in teams.
6. I never sleep with the light on, but have to tolerate blue from LEDs from my cell phone charger and sometimes my computer (if I leave it on). It’s kinda nerdy so maybe I’d go with it.
7. Amsterdam.
8. In the forest, on its roots, with natural snow on it.
9. I know the parts I’ve explored pretty well, but there are lots of places I still haven’t here.
10. I like to code. (We’ll see how this answer holds up once it becomes a job.)
11. I would’ve wished for my parents to be able to resolve the problems between them.

Alright, I think this is safe to rule as invalid because the cause is most likely hardware failure: Oneiric boot media now also fails to boot here despite being the one used to install this system initially. I even went so far back as installing Jaunty (didn’t have anything more recent at hand, before Oneiric) and it also segfaults when X should start (though the graphical installer did work). I’ll still do tests if @Joseph disagrees (and has new ideas to test), but for now I’ll just settle for using fbdev (which seems to not trigger the issue).

Se Marjo Jontunin novelihan oli tietysti Untako lienee on.