Open Bug 1749215 Opened 4 years ago Updated 3 years ago

mozregression problem on Ubuntu 21.10

Categories

(Testing :: mozregression, defect, P3)

Firefox 97
Desktop
Linux
defect

Tracking

(Not tracked)

People

(Reporter: erosman, Unassigned)

Details

mozregression 4.0.18
Ubuntu 21.10
Python 3.9.7

STR

  • Downloaded mozregression-gui.tar.gz
  • Unpacked to /home
  • Double-clicking mozregression-gui/mozregression-gui and nothing happens
  • Open a terminal
  • Go to the mozregression-gui folder
  • Run ./mozregression-gui
Glib-GID-ERROR **:200000:59:4:659: Settings schema 'org-gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing' Trace/breakpoint trap (core dumped)
$ loginctl show-session "$XDG_SESSION_ID" -p Type
*** 29209 1.1 4.2 5849828 338336 ? Ssl 14:40 5:08 /usr/bin/gnome-shell

Note: I am posting on windows. Ubuntu is on a new laptop that I am gradually migrating to.

Can confirm here. The right fix might be to upgrade PySide2 upstream

The severity field is not set for this bug.
:wlach, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(wlach)

Apparently I'm not able to set severity on these bugs since I left Mozilla. This is a serious problem (S2), sorry I can't help with this directly.

Flags: needinfo?(wlach)

(In reply to William Lachance (:wlach) from comment #3)

Apparently I'm not able to set severity on these bugs since I left Mozilla. This is a serious problem (S2), sorry I can't help with this directly.

Does the commandline version work? If yes, that's should probably be tagged as S3 instead.

Flags: needinfo?(wlach)
Flags: needinfo?(eros_uk)
OS: Unspecified → Linux
Hardware: Unspecified → Desktop

(In reply to Danny Colin [:sdk] from comment #4)

Does the commandline version work? If yes, that's should probably be tagged as S3 instead.

I have heard on #nightly:mozilla.org that the CLI works fine (I am a CLI novice and tend to avoid it).

Flags: needinfo?(eros_uk)
Flags: needinfo?(wlach)
Severity: -- → S3
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.