Application does not stay open on Ubuntu 20.04 and closes automatically

Bug #1863184 reported by Edson José dos Santos
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Hello Ubuntu Team

When we click on the totem it opens and closes automatically, as seen in the gif image on the link below.

[img]https://i.imgur.com/TYA8hrg.mp4[/img]

I tried to report this error by ubuntu-bug -w, but an error message appears that can be seen in the gif image below.

[img]https://i.imgur.com/xm9QSb9.mp4[/img]
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-04-28 (291 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: totem 3.34.1-2ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Tags: focal
Uname: Linux 5.4.0-12-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-02-04 (9 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: '/var/log/Xorg.0.log'
_MarkForUpload: True

Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1863184

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

FYI: rather than `ubuntu-bug -w` a `ubuntu-bug totem` may have worked.

Revision history for this message
Edson José dos Santos (serial.com) wrote : Dependencies.txt

apport information

tags: added: apport-collected focal
description: updated
Revision history for this message
Edson José dos Santos (serial.com) wrote : GstreamerVersions.txt

apport information

Revision history for this message
Edson José dos Santos (serial.com) wrote : LogAlsaMixer.txt

apport information

Revision history for this message
Edson José dos Santos (serial.com) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Edson José dos Santos (serial.com) wrote : ProcEnviron.txt

apport information

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

Changed in totem (Ubuntu):
status: New → Incomplete
Revision history for this message
Edson José dos Santos (serial.com) wrote :

I ask you to analyze the content and then delete it.

It was the only way to send crash data to the totem

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I have looked through that crash file and can confirm it is totem crashing, but it does not include a stack trace. To debug the problem further it must be reported with:

  ubuntu-bug YOURFILE.crash

or if that doesn't work then try something like:

  apport-cli YOURFILE.crash

Revision history for this message
Edson José dos Santos (serial.com) wrote :

Both options failed

ubuntu-bug YOURFILE.crash
apport-cli YOURFILE.crash

[img]https://i.imgur.com/8r7VyJW.png[/img]
[img]https://i.imgur.com/ylqY7mD.png[/img]
[img]https://i.imgur.com/CFS4pxJ.png[/img]

The problem exists as can be seen in the attached images when opening this post.
Now I don't know what else to do to try to send bug reports that you require.

The last attempt to open the totem through the terminal presented the following message:

edson @ edson-p6540br: ~ $ totem

(totem: 8692): Clutter-WARNING **: 00: 27: 56.950: Whoever translated default: LTR did so wrongly.
Segmentation failure (core image recorded)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Don't type in "YOURFILE.crash" literally. Replace that with a path to your actual crash file.

Revision history for this message
Edson José dos Santos (serial.com) wrote :

See if that's what you want (!)
If not, please put the correct command to be typed in the terminal

https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1863545

https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1863546

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

If you found the crash file was:

  /var/crash/_usr_bin_totem.1000.crash

then you would run:

  ubuntu-bug /var/crash/_usr_bin_totem.1000.crash

or

  apport-cli /var/crash/_usr_bin_totem.1000.crash

Since I can't see your computer I am unable to verify if that is the correct file name.

Revision history for this message
Edson José dos Santos (serial.com) wrote :

Now yes

[img]https://i.imgur.com/OL6XmXr.png[/img]

[img]https://i.imgur.com/5RpK7B8.png[/img]

totem crashed with SIGSEGV in grl_tracker_setup_key_mappings()

https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1863548

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks. That's bug 1856927 so please subscribe there.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.