Bug 667630 – Totem goes to "Segmentation Fault" if any totem command is execute while an instance is already opened (even if not playing anything).

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 667630 - Totem goes to "Segmentation Fault" if any totem command is execute while an instance is already opened (even if not playing anything).


Summary:	Totem goes to "Segmentation Fault" if any totem command is execute while an i...


Status:	RESOLVED DUPLICATE of bug 666431

Product:	totem
Classification:	Core
Component:	general
Version:	3.0.x
Hardware:	Other Linux

Importance:	High critical
Target Milestone:	---
Assigned To:	General Totem maintainer(s)
QA Contact:	General Totem maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2012-01-10 15:13 UTC by psymole
Modified:	2012-01-10 16:08 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
Backtrace of the Crash (8.31 KB, text/plain) 2012-01-10 16:01 UTC, psymole	Details

Description psymole 2012-01-10 15:13:08 UTC

To replicate the bug:
1) launch totem
2) open terminal and run: "totem --help" or any other command line totem command

Totem crashes and this message is displayed:
"GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)"

Any idea? I would like to control totem through SSH with my smartphone.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: totem 3.0.1-0ubuntu7.1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu3
Date: Wed Nov 2 22:23:42 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" 
SourcePackage: totem

Comment 1 André Klapper 2012-01-10 15:26:25 UTC

Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 psymole 2012-01-10 16:01:21 UTC

Created attachment 204952 [details]
Backtrace of the Crash

Comment 3 psymole 2012-01-10 16:02:17 UTC

Hi, here is the Trace you requested, Let me know if I can be of more help

Comment 4 André Klapper 2012-01-10 16:07:56 UTC

Thanks. Installing the debug package for libglib2 is welcome to make the trace more complete.

Comment 5 Bastien Nocera 2012-01-10 16:08:10 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 666431 ***