22.04 Totem crashes on launch (segmentation fault)

Bug #1972991 reported by Aaron Whitehouse
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Hello,

Since upgrading (fresh reinstall) to 22.04, I have had issues with Totem crashing.

I have not been able to pin down when it works and when it doesn't, as playing the same videos seems to work sometimes and not work others. After it crashes, trying to open it again normally does not work and trying to launch totem from the commandline gives a segmentation fault.

Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Segmentation fault (core dumped)

$ totem
Segmentation fault (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May 11 13:10:48 2022
InstallationDate: Installed on 2022-04-24 (16 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: totem
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

Revision history for this message
Aaron Whitehouse (aaron-whitehouse) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Those log messages are from Mesa. I'm seeing them come from other apps like Firefox and Thunderbird in other peoples' bug reports. But in all likelihood the log messages are not related to any crash...

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
Imtiaz Rahi (imtiaz.rahi) wrote (last edit ):

I have the same problem on 22.04 with totem. I ran the ubuntu-bug program with the crash file. It seemed to send it somewhere but i did not get a bug id.
So, I am attaching the crash file here.

Update: got this id '40649a3c-d877-11ec-8c97-fa163e993415' in a .uploaded file. maybe useful.

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

Imtiaz, you have bug 1962630.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for totem (Ubuntu) because there has been no activity for 60 days.]

Changed in totem (Ubuntu):
status: Incomplete → Expired
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.