| Summary: | Totem crashes when opening in KDE | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Olivier FAURAX <olivier> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | Normal | CC: | j.w.r.degoede, wilcal.int |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| URL: | http://dl.free.fr/i3dwUJpEn | ||
| Whiteboard: | |||
| Source RPM: | totem-3.6.3-6.mga3 | CVE: | |
| Status comment: | |||
| Attachments: | Patch fixing this atleast partially | ||
|
Description
Olivier FAURAX
2013-08-01 18:56:30 CEST
Manuel Hiebel
2013-08-06 22:31:09 CEST
Keywords:
(none) =>
Triaged Created attachment 4258 [details]
Patch fixing this atleast partially
Hi,
I encountered more or less the same problem while working on rpmfusion's gstreamer1-libav packages, at least I encountered this warning:
(totem:7294): GLib-GObject-WARNING **: type name `avmux_stream_segment,ssegment' contains invalid characters
This is caused by bullding gstreamer-libav against a system libav (or in the rpmfusion case a system ffmpeg-libs). The attached patch fixes the warning, which will hopefully also fix the crash further on...
Regards,
HansCC:
(none) =>
j.w.r.degoede On real hardware, M5, KDE, 32-bit This issue continues in M5B1 so I'm gonna change the Version to Cauldron. CC:
(none) =>
wilcal.int Ya, this crashes in Gnome too. And that ain't good. @William: how do you test it? (In reply to Olivier FAURAX from comment #4) > @William: how do you test it? Just simply click on the desktop icon in both GUI's. Also tried to launch from a terminal. I've no problem with totem-3.10.1-2.mga4, I'm unable to reproduce. (In reply to Olivier FAURAX from comment #6) > I've no problem with totem-3.10.1-2.mga4, I'm unable to reproduce. My issue is in Cauldron ( M5B1 ). Same issue persists today. I'm gonna wait till M5B2 is released to retest this again. Totem seg faults in KDE, it works just fine in Gnome. Still works fine in gnome in Mageia 5
Samuel Verschelde
2015-09-17 09:30:43 CEST
Summary:
Totem crashes when opening =>
Totem crashes when opening in KDE Unfortunately totem has no maintainer anymore. Feel free to have a look. Assignee:
mageia =>
bugsquad (In reply to William Kenney from comment #8) > Totem seg faults in KDE, it works just fine in Gnome. Does it still segfault in Plasma from cauldron? If yes, please provide a backtrace because it's probably not the same cause as the initial crash Olivier Faurax reported and in this case it would be better in a different bug report. Keywords:
Triaged =>
NEEDINFO (In reply to Samuel Verschelde from comment #11) > Does it still segfault in Plasma from cauldron? If yes, please provide a > backtrace because it's probably not the same cause as the initial crash > Olivier Faurax reported and in this case it would be better in a different > bug report. It no longer sigfaults on launch but launched from a terminal the following error messages are displayed: [wilcal@localhost ~]$ totem (totem:6766): Gtk-WARNING **: Failed to get the GNOME session proxy: The name org.gnome.SessionManager is not owned (totem:6766): Gtk-WARNING **: Failed to get the Xfce session proxy: The name org.xfce.SessionManager is not owned (totem:6766): Gtk-WARNING **: Failed to get an inhibit portal proxy: The name org.freedesktop.portal.Desktop is not owned (totem:6766): Totem-WARNING **: Failed to reset the playback rate to 1.0 (totem:6766): GLib-GObject-WARNING **: invalid (NULL) pointer instance (totem:6766): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (totem:6766): GLib-GObject-WARNING **: invalid (NULL) pointer instance (totem:6766): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (totem:6766): GLib-GObject-WARNING **: invalid (NULL) pointer instance (totem:6766): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed (totem:6766): Totem-CRITICAL **: totem_object_empty_menu_section: assertion 'TOTEM_IS_OBJECT (totem)' failed Closing this old bug report then. Don't hesitate to open a new one for those warnings and errors. Closing Status:
NEW =>
RESOLVED |