Avainsanana Launchpad

There’s a bug report about this on Launchpad

16. huhtikuuta 2023 klo 17.27
Sijainti: Muut: Ask Ubuntu
Avainsanat: Launchpad, Snap, Ubuntu

There’s a bug report about this on Launchpad.

Vastaa viestiin sen kontekstissa (Ask Ubuntu)

Here’s the updated steps to reproduce

28. huhtikuuta 2021 klo 14.05
Sijainti: Vianhallintajärjestelmät: Mozilla Bugzilla
Avainsanat: Firefox, Launchpad, Twitch

Steps to reproduce

  1. Open about:config
  2. Search for autoplay in the settings
  3. Set media.autoplay.default to 1 (”Block Audio”, which is the default)
  4. Set media.autoplay.blocking_policy to 2
  5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033
  6. Try to unmute the video (either by clicking Twitch player’s speaker control button, or by dragging the accompanying volume slider)

What I expect to happen

For the audio to be unmuted.

What happens instead

The audio remains muted, and the volume control/indicator remains in the muted position.


I’m unmotivated to report this to Twitch, as I’m unsure about the precise meaning of media.autoplay.blocking_policy, and I currently don’t use the non-working value for it myself. Feel free to downprioritize this as you see fit, unless the original reporter is still affected. Here’s my downstream report over at Launchpad though, just for reference. (I’ll update it too.)

Vastaa viestiin sen kontekstissa (Mozilla Bugzilla)

Sorry, tried to link this with LP #1723881 but failed, because LP #1334

27. marraskuuta 2020 klo 18.33
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Launchpad

Sorry, tried to link this with LP #1723881 but failed, because LP #1334

Vastaa viestiin sen kontekstissa (Launchpad)

I tried enabling the main/debug component for the PPA

1. syyskuuta 2020 klo 20.03
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Launchpad

I tried enabling the main/debug component for the PPA, but it just results in a bunch of ”repository […] doesn’t have the component ’main/debug'” errors when I run apt update. Should I open a separate issue about it?

Vastaa viestiin sen kontekstissa (Github)

Keyboard shortcut restoring shortcut cut short when localized

10. huhtikuuta 2020 klo 15.38
Sijainti: Vianhallintajärjestelmät: Gnome GitLab
Avainsanat: Gnome, Launchpad, Ubuntu

Affected version

I’m using Ubuntu 20.04 and Wayland, with gnome-shell currently at version 3.36.1-4ubuntu1. (I originally filed this on Launchpad.)

Bug summary

When trying to start a virtual machine with Gnome Boxes, I get a prompt about keyboard shortcuts. The prompt text is localized, but translated back to English it says:

Boxes wants to inhibit shortcuts

You can restore shortcuts by pressing Super+Escape.

In my locale (Finnish), it says

Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa.

Voit palauttaa pikanäppäinten toiminnan painamalla Super...

(sic; see attached photo)

So the actual key combination is truncated, defeating the point of that part of the text.

This isn’t a localization error (AFAICT, based on the translation source). Rather, it’s caused by the text being forced to fit on a single line of an arbitrarily fixed width, instead of wrapping to span as many lines as needed.

Screenshot

20200409_180221

Vastaa viestiin sen kontekstissa (Gnome GitLab)

I first reported this against 62 in Launchpad

17. marraskuuta 2018 klo 15.13
Sijainti: Vianhallintajärjestelmät: Mozilla Bugzilla
Avainsanat: Firefox, Launchpad, Ubuntu

I first reported this against 62 in Launchpad: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1798103

Firefox was since updated to 63 in Ubuntu and the issue remains.

Vastaa viestiin sen kontekstissa (Mozilla Bugzilla)

Position of left-tiled windows not restored correctly when another left-tiled window present

18. toukokuuta 2018 klo 15.38
Sijainti: Vianhallintajärjestelmät: Gnome GitLab
Avainsanat: Firefox, Gnome, Launchpad, Nautilus

Background

I’m using Ubuntu 18.04 with Gnome Shell 3.28.1, and was forwarded here from Launchpad, see bug #1767806 there.

The issue

When another window is maximized or tiled to the left side of the screen, re-opening an application whose window was previously tiled to the left side does not restore that windows’ previous position. Instead such windows open at varying distances from the dock, untiled.

Expected behavior

Steps to reproduce (with a newly created user)

  1. open Firefox, drag the window to the left edge of the screen to tile it there (filling up the left half of horizontal screen space)
  2. close Firefox
  3. open Nautilus, make sure that the window floats (i.e. is unmaximized and not tiled to either side of screen)
  4. open Firefox

What happens

As expected, Firefox’s window is tiled to the left edge of screen, immediately to the right side of the dock: screenshot.

Unexpected behavior

Steps to reproduce (with a newly created user)

  1. open Firefox, drag the window to the left edge of the screen to tile it there (filling up the left half of horizontal screen space)
  2. close Firefox
  3. open Nautilus, maximize its window
  4. open Firefox

What happens

Firefox’s window opens slightly to the right off the right edge of the dock (with a gap between the dock and the window): screenshot.

What I expect to happen

I expect Firefox’s window to be tiled to the left edge of screen, immediately to the right side of the dock, just as it did following the first recipe above.

Further information

  • Either maximizing or tiling Nautilus’ window to the left edge of the screen (at step 3) triggers the issue. Tiling it to the right edge of the screen does not.
  • Using Gnome Terminal instead of Nautilus triggers the issue just as well and I suspect any other application will, though I’ve only systematically tested these two so far.
  • From battling with this in my daily use I also know that the distance of incorrectly restored windows from the dock varies: different applications open at different distances. The precise mechanics of this still elude me, though the distances do appear to be multiples of 25 pixels.

Vastaa viestiin sen kontekstissa (Gnome GitLab)

Over at Launchpad, Jamie Strandboge had this to say

21. helmikuuta 2018 klo 19.32
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Jamie Strandboge, Launchpad, Snap, Wekan

Over at Launchpad, Jamie Strandboge had this to say:

”As for install/refresh getting stuck, it seems that the wekan hooks aren’t exiting so snapd has no choice but to wait a while then timeout.

At this point, this seems like the issues are in the wekan snap: it needs to plug hardware-observe and needs to handle error conditions better in the hooks so the exit.”

Vastaa viestiin sen kontekstissa (Github)

I went ahead and reported this on Launchpad

22. tammikuuta 2018 klo 16.01
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Launchpad, Snap, Wekan

I went ahead and reported this on Launchpad, we’ll see if anyone there has any ideas. A new SRU (2.30) of snapd also seems to be in the works, but no release as of yet.

Vastaa viestiin sen kontekstissa (Github)

Typo: ”launchapd.net” in ssh_import_id

9. toukokuuta 2012 klo 17.49
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Launchpad

Attaching a patch to fix this.

Vastaa viestiin sen kontekstissa (Launchpad)

Vanhempia »