FS#16060 - [gstreamer] Update to new version causes gnome-settings-daemon fail

Attached to Project: Community Packages
Opened by Styx (Styx) - Sunday, 06 September 2009, 20:41 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 29 September 2009, 09:25 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 6
Private No

Details

Description: The following versions of gstreamer's package cause a critical error in gnome-settings-daemon that do not start. (So you cannot start Pidgin for example).

Additional info:
extra/gstreamer0.10-bad 0.10.14-1
extra/gstreamer0.10-bad-plugins 0.10.14-1
extra/gstreamer0.10-good 0.10.16-1
extra/gstreamer0.10-good-plugins 0.10.16-1

Comments: I did not identify the package that cause this problem and I did not paste the logs; I'll do it tomorrow.

Temporary solution: Downgrade to :
extra/gstreamer0.10-bad 0.10.13-1
extra/gstreamer0.10-bad-plugins 0.10.13-1
extra/gstreamer0.10-good 0.10.15-3
extra/gstreamer0.10-good-plugins 0.10.15-3
This task depends upon

Closed by  Sergej Pupykin (sergej)
Tuesday, 29 September 2009, 09:25 GMT
Reason for closing:  Duplicate
Additional comments about closing:  http://bugs.archlinux.org/task/16389
Comment by Jan de Groot (JGC) - Monday, 07 September 2009, 07:27 GMT
Can't reproduce it here, and you don't give much information either. Works fine on both my i686 install with GNOME 2.27.91 and my x86_64 install with GNOME 2.26.x
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 10 September 2009, 16:34 GMT
I can confirm this issue. Please increase the priority and severity since this causes a critical breakage for Gnome users.
Comment by Michel (BeRReGoN) - Thursday, 10 September 2009, 17:04 GMT
Same here, when i update extra/gstreamer0.10-bad 0.10.14-1, xfburn, brasero, totem and probably more won't start anymore.
Comment by Jan de Groot (JGC) - Thursday, 10 September 2009, 17:12 GMT
Without error logs and debug information I can't really help here. Just responding with "me too" and "doesn't work" doesn't solve anything.
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 10 September 2009, 17:25 GMT
I'm willing to debug. What exact debug info and logs do you need to be able to debug this? I guess the usual logs won't be of help here since a particular daemon is causing the problems with the error messages mentioned in this thread: http://bbs.archlinux.org/viewtopic.php?id=79791
I tried my google-fu at this but wasn't able to find anything to resolve this issue. On thing I noticed when downgrading was that there was a file conflict between the different versions of gstreamer-* but that probably didn't cause this problem.
Comment by Styx (Styx) - Saturday, 12 September 2009, 09:47 GMT
http://pastebin.archlinux.fr/359029
Comment by Styx (Styx) - Saturday, 12 September 2009, 09:48 GMT
[styx@Lisa ~]$ gstreamer-properties
Erreur lors de la nouvelle analyse du registre , child terminated by signal
Comment by trapanator (trapanator) - Sunday, 13 September 2009, 10:09 GMT
Confirming, I have this bug, too.

In Archlinux italian forums [1] there's a thread talking about this problem. For now 4 users have this problem.

[1] http://www.archlinux.it/forum/viewtopic.php?pid=45064#p45064

Please set a higher severity, I'm unable to set keyboard to italian.

Comment by Jan de Groot (JGC) - Sunday, 13 September 2009, 10:28 GMT
Try playing a bit with GST_DEBUG, I can't reproduce this bug, so it must be some weird plugin taking gstreamer down on your systems. Without knowing what plugin it is, it can't be fixed. Please stop replying with "me too, fix it!" comments.
Comment by trapanator (trapanator) - Sunday, 13 September 2009, 12:12 GMT
how can I enable GST_DEBUG ?
Comment by Jan de Groot (JGC) - Sunday, 13 September 2009, 12:23 GMT
It's an environment variable. You can launch gnome-settings-daemon with something like GST_DEBUG=3 gnome-settings-daemon, gstreamer will output debug information to the terminal. Raising the debug level gives more output.
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 13 September 2009, 15:01 GMT
Logs of gnome-settings-daemon and gst-launch-0.10 attached. So far I tried removing all gstreamer stuff and then gradually adding components and it really appears the bad/good packages are the whole reason for the trouble. Googling after the errors didnt turn up anything too useful except for many similar problems that seem to somehow be related to the CPU type. I thus tried recompiling the packages from ABS for my CPU (pentium-m) but to no avail.
   gst-launch-0.10.log (0.97 MiB)
   gnome-settings-daemon-all-gst... (52.1 KiB)
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 13 September 2009, 15:11 GMT
A log of gnome-settings-daemon launching with old gstreamer plugins.
   gnome-settings-daemon-old-gst... (18.2 KiB)
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 13 September 2009, 18:06 GMT
Thanks to the awesome help of slomo in #gstreamer, I was able to track down the issue. It is due to old CPUs not being able to execute the gavl library in [community] because it apparently was made using the wrong set of CFLAGS. I'm using a lowly Pentium-M and the highest I can go is SSE2. I then grabbed the gavl PKGBUILD from ABS, changed it to compile 1.1.1 instead of 1.1.0 and was able to successfully finish compilation and installation using mtune=native.
Sure enough, the gstreamer plugins now work!

To conclude: The bug is in the [community] gavl package which was compiled using a wrong -mtune setting. Not an upstream issue!
Comment by Jan de Groot (JGC) - Sunday, 13 September 2009, 20:00 GMT
Which plugin is making use of gavl? Looking at these traces, the only reason why the new -bad-plugins package fails is because it needs to update your registry. The old version is included in the registry, so that doesn't require a plugin scan.
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 13 September 2009, 21:00 GMT
I ran gdb on gst-launch and it crashed with SIGILL which means my CPU wasn't able to continue because it received an instruction it didn't know. The Debian folks told me that they had the same issue and that it was related to gavl. Since compiling gavl 1.1.1 on my own settings fixed it for me, I conclude that it was indeed gavl that is at fault. I think we can close this bug once the gavl maintainer gets around to upload the new version to [community] which this time hopefully is compiled for i686.
Comment by trapanator (trapanator) - Saturday, 19 September 2009, 18:45 GMT
any progress???
Comment by Sven-Hendrik Haase (Svenstaro) - Saturday, 19 September 2009, 22:25 GMT
I posted this working PKGBUILD of the gavl package to the mailing list but so far nobody bothered to actually update it and the original maintainer isn't getting back to me either :(. Jan, can you put it up? I tested it myself and it works fine. Just make sure to compile with neutral mtune settings.
   PKGBUILD (0.7 KiB)
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 20 September 2009, 23:04 GMT
gavl has been updated, can you guys try it and see if it still breaks?
Comment by Michel (BeRReGoN) - Monday, 28 September 2009, 15:35 GMT
Still get the error message:
** (xfburn:3105): CRITICAL **: Failed to initialize gstreamer!

I reinstall every gstreamer file and when i update gavl it's fine. it's when i update frei0r-plugins that gstreamer breaks.

Loading...