Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1477129

Summary: grilo-plugins Lua sources are missing
Product: Red Hat Enterprise Linux 7 Reporter: Tomas Hudziec <thudziec>
Component: grilo-pluginsAssignee: Bastien Nocera <bnocera>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: jkoten, thudziec, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 15:05:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
totem backtrace
none
bt with fatal_criticals none

Description Tomas Hudziec 2017-08-01 09:58:13 UTC 
Description of problem:
Totem shows Grilo-CRITICAL ** errors to command line on s390x when it is run via command line without arguments.

Version-Release number of selected component (if applicable):
totem-3.22.1-1.el7.s390x
kernel-3.10.0-693.el7.s390x

How reproducible:
100%

Steps to Reproduce:
1. run totem via command line without arguments as normal user

Actual results:
"(totem:$PID): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed" error message is dumped into command line for each video in Videos directory

Expected results:
no errors should happen and no error messages should be dumped

Additional info:
Tested while connected to s390x machine via VNC (tried Vinagre and TigerVNC Viewer).
Comment 2 Bastien Nocera 2017-08-08 09:51:59 UTC 
Please run the command under gdb and set the G_DEBUG=fatal_warnings environment variable to gather the backtrace of those warnings.
Comment 3 Tomas Hudziec 2017-08-10 10:14:31 UTC 
Created attachment 1311656 [details]
totem backtrace
Comment 4 Tomas Hudziec 2017-08-10 10:15:25 UTC 
And here is faf report of the issue:
http://faf.lab.eng.brq.redhat.com/faf/reports/3800/
Comment 5 Bastien Nocera 2017-08-10 12:35:21 UTC 
Right, let's try again with "G_DEBUG=fatal_criticals" because you stopped at an earlier warning that isn't the one you pasted in comment 0.
Comment 9 Tomas Hudziec 2017-09-11 15:12:14 UTC 
Created attachment 1324493 [details]
bt with fatal_criticals

backtrace with G_DEBUG=fatal_criticals
Comment 10 Bastien Nocera 2017-09-19 09:00:35 UTC 
This is the line that fails:
        grl_source_resolve_sync (self->priv->title_parsing_src,
                                 media,
                                 self->priv->metadata_keys,
                                 options,
                                 NULL);

And in grilo-plugins.spec:
%if 0%{?fedora}
BuildRequires:  lua-devel
%endif

Turns out that's not s390x specific, there's just no lua plugins, which are required for totem to be usable, in grilo-plugins.
Comment 11 Bastien Nocera 2017-10-04 11:39:59 UTC 
We'd either need to remove the changes we made to go from lua 5.1 to 5.2 and then to 5.3 (upstream commits d00bfa9581cda2937002f024cfcaaed1e65e3b06 and 8b18594e65fc1196c1d270ee3fcefe55195ea397) or bump lua versions to 5.3.
Comment 12 Bastien Nocera 2017-10-06 09:38:01 UTC 
Fixed in grilo-plugins-0.3.4-3.el7

Tomas, any chance you could relaunch totem with this updated package?
Comment 14 Tomas Hudziec 2017-10-09 09:01:18 UTC 
Can not reproduce with grilo-plugins-0.3.4-3.el7 on x86_64. Closing as fixed.
Comment 16 Tomas Hudziec 2017-10-23 08:58:59 UTC 
Switching to verified.
Comment 19 errata-xmlrpc 2018-04-10 15:05:50 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0844