Snapcrafters snaps call for testing

[Igor]

We have recently updated a number of snaps maintained by the Snapcrafters community, and the new versions are currently available in the edge channel These include: atom, flightgear, jenkins, and opentoonz.

We would like to ask for your help in testing these snaps:

• Install on two systems, preferably one Ubuntu-based and one non-Ubuntu (e.g.: Fedora).
• Test on two different desktop environments, e.g.: GNOME and Plasma.
• Start the application, check for any errors.
• Perform 3 functional tests.

Re: functional tests, we are purposefully keeping this open, as we’d like to invite contribution and ideas from the wider community on which tests ought to be run for these (particular) snaps. Ideally, such tests will be repeatable, measurable, and could be scripted or automated in some fashion.

In the future, we could potentially include these tests in the wider test bundle for all of the Snapcrafters snaps.

Please report back your results by May 20 (7 days from now). If the results are successful, we can then promote from edge and extend the testing.

@om26er @tunix @galgalesh I am tagging you as you may be interested in helping with this effort. That said, contributions and suggestions from everyone are welcome.

[tunix]

I’ll try to test jenkins and atom packages if I can.

[Lin-Buo-Ren]

Test report for atom snap (revision 280)

Test environment

Item	Value
Operating System	Ubuntu 21.04
Hardware Architecture	AMD64
Desktop Environment	GNOME 3.38.4
Locale	zh_TW.UTF-8
Input Method Framework	IBus
Input Method	ibus-chewing

Test results

Launch

No errors

Functional tests

Type with English

Success

Type with Chinese

FAILED (Output isn’t captured by IMF)

Open existing file

Success.

[Lin-Buo-Ren]

Test report for opentoonz snap (revision 140)

Test environment

Item	Value
Operating System	Ubuntu 21.04
Hardware Architecture	AMD64
Desktop Environment	GNOME 3.38.4
Locale	zh_TW.UTF-8
Input Method Framework	IBus
Input Method	ibus-chewing

Test results

Launch

No errors

Functional tests

Type with Chinese

FAILED (Output isn’t captured by IMF)

Create scene

Success.

Save scene

Success

[tunix]

Test report for atom snap (revision 280)

Test environment

Item	Value	Notes
Operating System	Pop!_OS 20.10
Hardware Architecture	AMD64
Desktop Environment	GNOME 3.38.3
Locale	tr_TR.UTF-8
Input Method Framework	?	Where do I get this info from?
Input Method	?	Where do I get this info from?

Test results

Launch

I see an error about spell-check package.

Functional tests

Type with English

Success. Some emojis are shown differently.

Type with Turkish

Success.

Open a project

Success.

View a diff of a changed file via Git tracker

Success.

Revert a change via Git tracker

Success.

[Igor]

Very interesting on the Type with Chinese test. Can you check if this works with the non-snap version? If it doesn’t, maybe this is worth filing as a bug with upstream?

[Igor]

I also do not see an error with the spellchecker with the en_US encoding - looking at the Atom tracker, this is a known issue - https://github.com/atom/spell-check/issues/253.

Which emoji codes did you use for this?

[tunix]

I think that’s because Atom spell-checker uses system locales. I think the snap includes en_US locale by default and it works as expected. Upon using other locales, it shows the error. The solution seems to be either including all locales (or providing a way to do it) or disabling the feature.

The emojis I tried were: (U+1F60A) and (U+1F602)

[Igor]

Makes sense. I do not think this is a snap-specific problem, but maybe something I can bring up internally to see if this is something we could potentially streamline.

[Lin-Buo-Ren]

@tunix

|Input Method Framework|?|Where do I get this info from?

Run the ps ax | grep --extended-regexp '(ibus|fcitx|scim|gcin|hime)' | grep --invert-match grep command in the terminal should give a match:

$ ps ax | grep --extended-regexp '(ibus|fcitx|scim|gcin|hime)' | grep --invert-match grep
  11309 ?        Sl    88:36 ibus-daemon --panel disable --xim
  11319 ?        Sl     0:00 /usr/libexec/ibus-memconf
  11320 ?        Sl    19:11 /usr/libexec/ibus-extension-gtk3
  11324 ?        Sl     0:04 /usr/libexec/ibus-x11 --kill-daemon
  11327 ?        Sl     7:27 /usr/libexec/ibus-portal
  11975 ?        Sl    23:21 /usr/lib/ibus/ibus-engine-chewing --ibus
  14433 ?        Sl     0:22 /usr/libexec/ibus-engine-simple

If you’re using GNOME you’re likely using IBus IMF.

@tunix

|Input Method|?|Where do I get this info from?

For IBus IMF, run the ibus read-config | grep preload-engines command in a terminal:

$ ibus read-config | grep preload-engines
  preload-engines: ['xkb:us::eng', 'chewing']

[tunix]

$ ps ax | grep -E '(ibus|fcitx|scim|gcin|hime)' | grep -v grep
   2714 ?        Sl     1:05 ibus-daemon --panel disable --xim
   2719 ?        Sl     0:00 /usr/libexec/ibus-memconf
   2720 ?        Sl     0:10 /usr/libexec/ibus-extension-gtk3
   2722 ?        Sl     0:05 /usr/libexec/ibus-x11 --kill-daemon
   2724 ?        Sl     0:17 /usr/libexec/ibus-portal
   3385 ?        Sl     0:17 /usr/libexec/ibus-engine-simple

$ ibus read-config | grep preload-engines
  preload-engines: @as []

Why is this different than your output?

[Lin-Buo-Ren]

@tunix

Why is this different than your output?

You’re might not be the audience that needs an input method framework in the first place, which is mostly used in CJKV(Chinese, Japanese, Korean, and Vietnamese) locales, refer Compatibility with CJKV input method frameworks for more info.

[Igor]

Thanks! I’ve promoted atom to beta. There’s also a new build for opentoonz and a few other snaps.

Do you have anything for jenkins perhaps?

=====

Open request to anyone else reading this thread:

If you can assist with testing, it would be appreciated.
At the moment the following snaps in edge require testing:

opentoonz opentoonz-vna cumulonimbus auryo nano jenkins flightgear obs-studio

[lucyllewy]

Nano

Fails to launch, with the following output:

locales-launch: Data of en_GB locale not found, generating, please wait...
Error opening terminal: xterm-256color.

---

OBS-Studio

Launches, but has display corruption when resizing window and on initial launch. Not really usable. I have nVidia drivers 460.73.01-0ubuntu1 on Ubuntu 21.04. Running Gnome with two monitors - with each having a different scaling level to the other.

---

Snap version

snap 2.50
snapd 2.50
series 16
ubuntu 21.04
kernel 5.11.0-17-generic

[galgalesh]

Test report for opentoonz snap (revision 140)

Item	Value
Operating System	Ubuntu 21.04
Hardware Architecture	AMD64
Desktop Environment	GNOME 3.38.4
Locale	en_US.UTF-8

Test results

Launch

No errors

Type latin

Success.

Create scene

Success.

Save scene

Success

Render

Failed (Render > Fast Render to MP4)

Note: I fixed this for krita using a layout: https://invent.kde.org/graphics/krita/-/blob/master/packaging/linux/snap/snapcraft.yaml#L26

[Igor]

@lucyllewy What do you mean display corruption btw?

[lucyllewy]

For display corruption, I mean the UI isn’t correctly formed. There are duplicate controls, and the display doesn’t repaint the window properly when resizing:

[Igor]

Rebuilding, let’s see what happens.

[Igor]

Does this happen with older builds btw? And a non-snap version of the app?

[lucyllewy]

I don’t know about older snap builds - I installed anew today, so don’t have access to revert to a previous build.

The version of OBS in the Ubuntu Archive for 21.04 (hirsute) does not exhibit the screen issues.